os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- maxusers is optional in 5.X kernel configs

Browse source 
- describe the 'hints' keyword of kernel config files in the 5.X branch
- split makeoptions DEBUG='-g' from MATH_EMULATE and describe what it does
This commit is contained in:
Giorgos Keramidas 2003-05-11 22:08:18 +00:00
parent 41dd7161fc
commit 7d4ef3cea6
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=16880
1 changed files with 34 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

39
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -554,7 +554,7 @@ cpu I686_CPU</programlisting>
instructions of the previous examples. The value you put in the
<literal>ident</literal> string will print when you boot up the
kernel, so it is useful to give the new kernel a different name if you
want to keep it separate from your usual kernel (i.e., you want to
want to keep it separate from your usual kernel (i.e. you want to
build an experimental kernel).</para>
<indexterm>
<primary>kernel options</primary>
@ -572,8 +572,10 @@ cpu I686_CPU</programlisting>
for you if you explicitly set it to <literal>0</literal><footnote>
<para>The auto-tuning algorithm sets <literal>maxuser</literal> equal
to the amount of memory in the system, with a minimum of 32, and a
maximum of 384.</para></footnote>. If you are
using an earlier version of &os;, or you want to manage it
maximum of 384.</para></footnote>.
In &os;-5.x, <literal>maxusers</literal> will default to
<literal>0</literal> if not specified. If you are using an
version of &os; earlier than 4.5, or you want to manage it
yourself you will want to set
<literal>maxusers</literal> to at least 4, especially if you are
using the X Window System or compiling software. The reason is that
@ -624,8 +626,35 @@ pseudo-device loop # Network loopback</programlisting>
<para>Everything that follows is more or less optional. See the notes
underneath or next to each option for more information.</para>
<programlisting>#makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols
options MATH_EMULATE #Support for x87 emulation</programlisting>
<programlisting>#To statically compile in device wiring instead of /boot/device.hints
#hints "GENERIC.hints" #Default places to look for devices.</programlisting>
<para>In &os; 5.x and newer versions the &man.device.hints.5; is
used to configure options of the device drivers. The default
location that &man.loader.8; will check at boot time is
<filename>/boot/device.hints</filename>. Using the
<literal>hints</literal> option you can compile these hints
statically into your kernel. Then there is no need to create a
<filename>device.hints</filename> file in
<filename>/boot</filename>.</para>
<!-- XXX: Add a comment here that explains when compiling hints into the kernel is a good idea and why. -->
<programlisting>#makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</programlisting>
<para>The normal build process of the &os; does not include
debugging information when building the kernel and strips most
symbols after the resulting kernel is linked, to save some space
at the install location. If you are going to do tests of kernels
in the -CURRENT branch or develop changes of your own for the &os;
kernel, you might want to uncomment this line. It will enable the
use of the <option>-g</option> option which enables debugging
information when passed to &man.gcc.1;. The same can be
accomplished by the &man.config.8; <option>-g</option> option, if
you're using the old procedure of building your kernels (config;
make depend; etc.).</para>
<programlisting>options MATH_EMULATE #Support for x87 emulation</programlisting>
<para>This line allows the kernel to simulate a math co-processor if
your computer does not have one (386 or 486SX). If you have a