diff --git a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
index 4d8a00b4e9..ea17837806 100644
--- a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
@@ -82,12 +82,14 @@
then reboot your computer with the new kernel.
Today, &os; is rapidly moving to a model where much of the
- kernel's functionality is contained in modules which can be dynamically
- loaded and unloaded from the kernel as necessary. This allows the
- kernel to adapt to new hardware suddenly becoming available (such as
- PCMCIA cards in a laptop), or for new functionality to be brought into
- the kernel that was not necessary when the kernel was originally
- compiled. This is known as a modular kernel. Colloquially these are called KLDs.
+ kernel's functionality is contained in modules which can be
+ dynamically loaded and unloaded from the kernel as necessary.
+ This allows the kernel to adapt to new hardware suddenly
+ becoming available (such as PCMCIA cards in a laptop), or for
+ new functionality to be brought into the kernel that was not
+ necessary when the kernel was originally compiled. This is
+ known as a modular kernel. Colloquially these are called
+ KLDs.
Despite this, it is still necessary to carry out some static kernel
configuration. In some cases this is because the functionality is so
@@ -156,15 +158,18 @@
If there is not a
- /usr/src/sys directory on your system, then
- the kernel source has not been installed. The easiest way to
- do this is by running /stand/sysinstall as
- root, choosing Configure,
- then Distributions, then
- src, then sys. If you
- have an aversion to sysinstall and
- you have access to an official &os; CDROM, then
- you can also install the source from the command line:
+ /usr/src/sys directory on your system,
+ then the kernel source has not been installed. The easiest
+ way to do this is by running
+ /stand/sysinstall as
+ root, choosing
+ Configure, then
+ Distributions, then
+ src, then
+ sys. If you have an aversion to
+ sysinstall and you have access to
+ an official &os; CDROM, then you can also
+ install the source from the command line:&prompt.root; mount /cdrom
&prompt.root; mkdir -p /usr/src/sys
@@ -388,12 +393,13 @@
- If you have added any new devices (such as sound cards) and you
- are running &os; 4.X or previous versions, you
- may have to add some device
- nodes to your /dev directory before
- you can use them. For more information, take a look at Making
- Device Nodes section later on in this chapter.
+ If you have added any new devices (such as sound cards)
+ and you are running &os; 4.X or previous versions, you
+ may have to add some device nodes to your
+ /dev directory before you can use
+ them. For more information, take a look at Making Device Nodes
+ section later on in this chapter.
@@ -425,11 +431,12 @@
to the purpose or necessity of a line, check first in
LINT.
- In &os; 5.X and above the LINT is non-existent.
- See the NOTES file for architecture dependent options.
- Some options, mainly architecture independent ones, are stored in the
- /usr/src/sys/conf/NOTES file. It's advisable to review
- the options in here also.
+ In &os; 5.X and above the LINT is
+ non-existent. See the NOTES file for
+ architecture dependent options. Some options, mainly
+ architecture independent ones, are stored in the
+ /usr/src/sys/conf/NOTES file. It's
+ advisable to review the options in here also.kernel
@@ -486,12 +493,13 @@
cpu I586_CPU
cpu I686_CPU
- The above option specifies the type of CPU you have in your system.
- You may have multiple instances of the CPU line (i.e., you are not
- sure whether you should use I586_CPU or
- I686_CPU), however, for a custom kernel, it is
- best to specify only the CPU you have. If you are unsure of your
- CPU type, you can check the /var/run/dmesg.boot file to view your boot
+ The above option specifies the type of CPU you have in your
+ system. You may have multiple instances of the CPU line (i.e.,
+ you are not sure whether you should use
+ I586_CPU or I686_CPU),
+ however, for a custom kernel, it is best to specify only the CPU
+ you have. If you are unsure of your CPU type, you can check the
+ /var/run/dmesg.boot file to view your boot
up messages.
@@ -693,20 +701,24 @@ options FFS_ROOT #FFS usable as root device [keep this!]options UFS_DIRHASH #Improve performance on big directories
- This option includes functionality to speed up disk operations on large
- directories, at the expense of using additional memory. You
- would normally keep this for a large server, or interactive workstation,
- and remove it if you are using &os; on a smaller system where memory
- is at a premium and disk access speed is less important, such as a
- firewall.
+ This option includes functionality to speed up disk
+ operations on large directories, at the expense of using
+ additional memory. You would normally keep this for a large
+ server, or interactive workstation, and remove it if you are
+ using &os; on a smaller system where memory is at a premium and
+ disk access speed is less important, such as a firewall.options SOFTUPDATES #Enable FFS Soft Updates support
- This option enables Soft Updates in the kernel, this will help speed
- up write access on the disks. Even when this functionality is provided by the kernel, it must be turned on for specific disks.
- Review the output from &man.mount.8; to see
- if SoftUpdates is enabled for your system disks. If you do not see the soft-updates option then
- you will need to activate it using the &man.tunefs.8; (for existing filesystems) or &man.newfs.8; (for new filesystems) commands.
+ This option enables Soft Updates in the kernel, this will
+ help speed up write access on the disks. Even when this
+ functionality is provided by the kernel, it must be turned on
+ for specific disks. Review the output from &man.mount.8; to see
+ if SoftUpdates is enabled for your system disks. If you do not
+ see the soft-updates option then you will
+ need to activate it using the &man.tunefs.8; (for existing
+ filesystems) or &man.newfs.8; (for new filesystems)
+ commands.options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
@@ -833,9 +845,10 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 requiredThis option allows you to boot the visual configuration editor
from the boot menu.
- From &os; versions 5.0 and later, userconfig has been depreciated
- in favor of the new &man.device.hints.5; method. For more information
- on &man.device.hints.5; please visit
+ From &os; versions 5.0 and later, userconfig has
+ been depreciated in favor of the new &man.device.hints.5;
+ method. For more information on &man.device.hints.5; please
+ visit options KTRACE #ktrace(1) support
@@ -907,8 +920,10 @@ options _KPOSIX_PRIORITY_SCHEDULING
device isaAll PCs supported by &os; have one of these. If you have an
- IBM PS/2 (Micro Channel Architecture), &os; provides some limited support at
- this time. For more information about the MCA support, see /usr/src/sys/i386/conf/LINT.
+ IBM PS/2 (Micro Channel Architecture), &os; provides some
+ limited support at this time. For more information about the
+ MCA support, see
+ /usr/src/sys/i386/conf/LINT.
device eisa