diff options
| author | GNU Hurd wiki engine <web-hurd@gnu.org> | 2007-09-03 19:19:37 +0000 |
|---|---|---|
| committer | GNU Hurd wiki engine <web-hurd@gnu.org> | 2007-09-03 19:19:37 +0000 |
| commit | a5769c335ff2ce3c8750bbee0c287eeabca8c349 (patch) | |
| tree | dd19da44ca03a6e01ddbcfa100712ee0b9a2ebb0 | |
| parent | 6842e8cb0184b84b059742b238f4e6a3d4136ccc (diff) | |
web commit by MichaelBanck: Updates
| -rw-r--r-- | Distrib/DebianFAQ.mdwn | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/Distrib/DebianFAQ.mdwn b/Distrib/DebianFAQ.mdwn index f302ed9d..d8190f90 100644 --- a/Distrib/DebianFAQ.mdwn +++ b/Distrib/DebianFAQ.mdwn @@ -20,7 +20,7 @@ Edit /etc/default/hurd-console to configure the Hurd console and enable it on bo ## <a name="swap"> swap </a> -## <a name="2GB_harddisk_limit"> 2GB harddisk limit </a> +## <a name="2GB_partition_limit"> 2GB harddisk limit </a> The 2GB limit has been removed in Debian GNU/Hurd. @@ -32,7 +32,7 @@ Run \`vmstat' to see memory and swap usage. ## <a name="512MB_RAM_limit"> </a> 512MB RAM limit -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 +GNU Mach does not cope well with lots of memory. Newer versions of the Debian gnumach package will limit themselves to around 1GB of memory. 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 it can see via GRUB's upppermem feature. Add \`uppermem 786432' to GRUB's Hurd entry in menu.lst This should be fixed. @@ -40,8 +40,6 @@ This should be fixed. You need to run \`dpkg-reconfigure xserver-common' and select \`Anybody' for starting X as there is no way to detect console users currently. -## <a name="emacs_snapshot_uninstallable"> emacs-snapshot uninstallable </a> - ## <a name="reporting_Bugs"> reporting Bugs </a> Please try to reproduce bugs which are not obviously Hurd-specific on Debian GNU/Linux and then file them there. @@ -80,7 +78,7 @@ The kernel logs are written to /dev/klog by Mach. Run "cat /dev/klog > foo" a ## <a name="_bad_hypermeta_data_"> \`bad hypermeta data' </a> -If you get the error \`bad hypermeta data' when trying to mount an ext3 partition from GNU/Linux, that is usually because the file system has not been unmonted cleanly (maybe GNU/Linux got suspended to disk) and the Hurd cannot mount it as ext2 without checking. Either boot back into GNU/Linux remount it once or you can try to run "fsck.ext3" from GNU/Hurd directly. +If you get the error \`bad hypermeta data' when trying to mount an ext3 partition from GNU/Linux, that is usually because the file system has not been unmounted cleanly (maybe GNU/Linux got suspended to disk) and the Hurd cannot mount it as ext2 without checking. Either boot back into GNU/Linux and unmount it or you can try to run "fsck.ext3" from GNU/Hurd directly. ---- |