summaryrefslogtreecommitdiff
path: root/hurd/running/debian/faq/ram_limit.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'hurd/running/debian/faq/ram_limit.mdwn')
-rw-r--r--hurd/running/debian/faq/ram_limit.mdwn22
1 files changed, 0 insertions, 22 deletions
diff --git a/hurd/running/debian/faq/ram_limit.mdwn b/hurd/running/debian/faq/ram_limit.mdwn
deleted file mode 100644
index 447ff20c..00000000
--- a/hurd/running/debian/faq/ram_limit.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!meta copyright="Copyright © 2007, 2008, 2013 Free Software Foundation,
-Inc."]]
-
-[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
-id="license" text="Permission is granted to copy, distribute and/or modify this
-document under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no Invariant
-Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
-is included in the section entitled [[GNU Free Documentation
-License|/fdl]]."]]"""]]
-
-[[!meta title="830 MiB RAM Limit"]]
-
-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.
-
-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`.