svn commit: r40909 - head/en_US.ISO8859-1/books/faq

[Eitan Adler]

Author: eadler
Date: Fri Feb  8 00:22:44 2013
New Revision: 40909
URL: http://svnweb.freebsd.org/changeset/doc/40909

Log:
  Remove obsolete question
  
  Noted by:	imp
  Approved by:	bcr (mentor, implicit)

Modified:
  head/en_US.ISO8859-1/books/faq/book.xml

Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml	Fri Feb  8 00:22:40 2013	(r40908)
+++ head/en_US.ISO8859-1/books/faq/book.xml	Fri Feb  8 00:22:44 2013	(r40909)
@@ -2225,35 +2225,6 @@ bindkey ^[[3~ delete-char # for xterm</p
       </qandaentry>
 
       <qandaentry>
-	<question id="kmem-map-too-small">
-	  <para>My system has more than 1 GB of RAM, and I'm
-	    getting panics with <errorname>kmem_map too small</errorname>
-	    messages.  What is wrong?</para>
-	</question>
-
-	<answer>
-	  <para>Normally, &os; determines a number of kernel parameters,
-	    such as the maximum number of files that can be open
-	    concurrently, from the amount of memory installed in the
-	    system.  On systems with one gigabyte of RAM or more, this
-	    <quote>auto sizing</quote> mechanism may choose values that
-	    are too high: while starting up, the kernel allocates
-	    various tables and other structures that fill up most of the
-	    available kernel memory.  Later on, while the system is
-	    running, the kernel has no more space left for dynamic
-	    memory allocations, and panics.</para>
-
-	  <para>Compile your own kernel, and add the
-	    <option>VM_KMEM_SIZE_MAX</option> to your kernel
-	    configuration file, increasing the maximum size to
-	    400 MB (<option>options
-	    VM_KMEM_SIZE_MAX=419430400</option>).  400 MB appears
-	    to be sufficient for machines with up to 6 GB of
-	    memory.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="panic-kmemmap-too-small">
 	  <para>My system does not have 1 GB of RAM, and &os; still
 	    panics with <errorname>kmem_map too