none

1 files changed, 6 insertions, 0 deletions

diff --git a/Distrib/DebianFAQ.mdwn b/Distrib/DebianFAQ.mdwn
index 56996432..e66329ca 100644
--- a/Distrib/DebianFAQ.mdwn
+++ b/Distrib/DebianFAQ.mdwn
@@ -34,6 +34,8 @@ Run \`vmstat' to see memory and swap usage.
 
 GNU Mach does not cope well with lots of memory. The best is to limit the memory it can see via GRUB's upppermem feature. Add \`uppermem 786432' to GRUB's Hurd entry in menu.lst
 
+This should be fixed.
+
 ## <a name="xserver_common"> xserver-common </a>
 
 You need to run \`dpkg-reconfigure xserver-common' and select \`Anybody' for starting X as there is no way to detect console users currently.
@@ -56,10 +58,14 @@ If \`ps' hangs, try \`ps -M' which might still works.
 
 To get debugging information for glibc, you need to install the libc0.3-dbg package. At the place gdb looks for debugging symbols by default (/usr/lib/debug/lib/), Debian's libc0.3-dbg stores only frame unwind information. If you want to step into glibc while debugging, you need to add LD\_LIBRARY\_PATH=/usr/lib/debug to gdb's environment. If that still does not work, try LD\_PRELOAD=/usr/lib/debug/libc.so.0.3 instead. You can add to gdb's environment via "set env FOO bar" from the gdb command line.
 
+It seems that this is no longer needed with the Debian glibc 2.5 packages, but I may as well be wrong. Have to check that again.
+
 ## <a name="debugging_translators"> debugging translators </a>
 
 In order to debug translators and being able to step into glibc during it, you need the hurd-dbg and libc0.3-dbg packages installed. Then 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 gdb to the process.
 
+Is starting the translator like this really needed?
+
 ## <a name="other_repositories"> other repositories </a>
 
 If you want to use the _apt-get source_ facility, make sure that _/etc/apt/sources.list_ contains a line like