diff options
-rw-r--r-- | faq/debugging_translators.mdwn | 10 | ||||
-rw-r--r-- | faq/kernel_logs.mdwn | 2 | ||||
-rw-r--r-- | faq/ram_limit.mdwn | 4 | ||||
-rw-r--r-- | faq/release.mdwn | 2 | ||||
-rw-r--r-- | hurd/running/debian/after_install.mdwn | 2 |
5 files changed, 12 insertions, 8 deletions
diff --git a/faq/debugging_translators.mdwn b/faq/debugging_translators.mdwn index b55484e1..262fd6aa 100644 --- a/faq/debugging_translators.mdwn +++ b/faq/debugging_translators.mdwn @@ -9,7 +9,11 @@ is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] In order to [[debug|debugging]] translators and being able to step into glibc -during it, you need the `hurd-dbg` and `libc0.3-dbg` packages installed. If you need to debug the initialization of the translator, -start the translator like `settrans -P /foo /usr/bin/env -LD\_LIBRARY\_PATH=/usr/lib/debug /hurd/foofs`. The `-P` option will make it +during it, you need the `hurd-dbg` and `libc0.3-dbg` packages installed. +If you need to debug the initialization of the translator, start the translator +like + + $ settrans -P /foo /usr/bin/env LD_LIBRARY_PATH=/usr/lib/debug /hurd/foofs + +The `-P` option will make it pause and you will be able to attach [[debugging/GDB]] to the process. diff --git a/faq/kernel_logs.mdwn b/faq/kernel_logs.mdwn index d539bf1b..93df42bb 100644 --- a/faq/kernel_logs.mdwn +++ b/faq/kernel_logs.mdwn @@ -11,4 +11,4 @@ License|/fdl]]."]]"""]] [[!meta title="dmesg, kernel logs"]] -There is no dmesg command: the kernel does not keep a buffer of its messages. syslog however dumps them into `/var/log/dmesg`, so you can simply cat that. +There is no `dmesg` command: the kernel does not keep a buffer of its messages. syslog however dumps them into `/var/log/dmesg`, so you can simply cat that. diff --git a/faq/ram_limit.mdwn b/faq/ram_limit.mdwn index 447ff20c..458a047d 100644 --- a/faq/ram_limit.mdwn +++ b/faq/ram_limit.mdwn @@ -13,8 +13,8 @@ License|/fdl]]."]]"""]] Just like any 32bit OS without bad tricks, GNU Mach does not cope well with lots of memory. Latest versions of the Debian `gnumach` package will limit themselves -to around 1.7 GiB of memory. If you want more, you can twiddle the VM_MAX_ADDRESS -limit between kernelland and userland in i386/include/mach/i386/vm_param.h. +to around 1.7 GiB of memory. If you want more, you can twiddle the `VM_MAX_ADDRESS` +limit between kernelland and userland in `i386/include/mach/i386/vm_param.h`. If you have an older version, or still experience problems with `vmstat` (see above) reported much less memory than you have, the best is to limit the memory diff --git a/faq/release.mdwn b/faq/release.mdwn index d80c6825..878a476f 100644 --- a/faq/release.mdwn +++ b/faq/release.mdwn @@ -12,4 +12,4 @@ is included in the section entitled Next year. -Save that, read about the Hurd's [[status]]. +Save that, read about the Hurd's [[hurd/status]]. diff --git a/hurd/running/debian/after_install.mdwn b/hurd/running/debian/after_install.mdwn index 72ea70a9..d3d32a6f 100644 --- a/hurd/running/debian/after_install.mdwn +++ b/hurd/running/debian/after_install.mdwn @@ -14,4 +14,4 @@ you. See [[GRUB]]'s page for this. # Setup `apt-get` Installing packages without having a network connection is described -[[Distrib/DebianAptOffline]]. +[[DebianAptOffline]]. |