Wrap long lines. Translators kindly ignore. Whitespace only change.
This commit is contained in:
Murray Stokely
parent
75da6e399b
commit
762346438a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=17731
1 changed files with 63 additions and 48 deletions
|
|
@ -82,12 +82,14 @@
|
|||
then reboot your computer with the new kernel.</para>
|
||||
|
||||
<para>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.</para>
|
||||
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.</para>
|
||||
|
||||
<para>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 @@
|
|||
|
||||
<note>
|
||||
<para>If there is <emphasis>not</emphasis> a
|
||||
<filename>/usr/src/sys</filename> directory on your system, then
|
||||
the kernel source has not been installed. The easiest way to
|
||||
do this is by running <command>/stand/sysinstall</command> as
|
||||
<username>root</username>, choosing <guimenuitem>Configure</guimenuitem>,
|
||||
then <guimenuitem>Distributions</guimenuitem>, then
|
||||
<guimenuitem>src</guimenuitem>, then <guimenuitem>sys</guimenuitem>. If you
|
||||
have an aversion to <application>sysinstall</application> and
|
||||
you have access to an <quote>official</quote> &os; CDROM, then
|
||||
you can also install the source from the command line:</para>
|
||||
<filename>/usr/src/sys</filename> directory on your system,
|
||||
then the kernel source has not been installed. The easiest
|
||||
way to do this is by running
|
||||
<command>/stand/sysinstall</command> as
|
||||
<username>root</username>, choosing
|
||||
<guimenuitem>Configure</guimenuitem>, then
|
||||
<guimenuitem>Distributions</guimenuitem>, then
|
||||
<guimenuitem>src</guimenuitem>, then
|
||||
<guimenuitem>sys</guimenuitem>. If you have an aversion to
|
||||
<application>sysinstall</application> and you have access to
|
||||
an <quote>official</quote> &os; CDROM, then you can also
|
||||
install the source from the command line:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount /cdrom</userinput>
|
||||
&prompt.root; <userinput>mkdir -p /usr/src/sys</userinput>
|
||||
|
|
@ -388,12 +393,13 @@
|
|||
</note>
|
||||
|
||||
<note>
|
||||
<para>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 <filename>/dev</filename> directory before
|
||||
you can use them. For more information, take a look at <link linkend="kernelconfig-nodes">Making
|
||||
Device Nodes</link> section later on in this chapter.</para>
|
||||
<para>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
|
||||
<filename>/dev</filename> directory before you can use
|
||||
them. For more information, take a look at <link
|
||||
linkend="kernelconfig-nodes">Making Device Nodes</link>
|
||||
section later on in this chapter.</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -425,11 +431,12 @@
|
|||
to the purpose or necessity of a line, check first in
|
||||
<filename>LINT</filename>.</para>
|
||||
|
||||
<note><para>In &os; 5.X and above the <filename>LINT</filename> is non-existent.
|
||||
See the <filename>NOTES</filename> file for architecture dependent options.
|
||||
Some options, mainly architecture independent ones, are stored in the
|
||||
<filename>/usr/src/sys/conf/NOTES</filename> file. It's advisable to review
|
||||
the options in here also.</para></note>
|
||||
<note><para>In &os; 5.X and above the <filename>LINT</filename> is
|
||||
non-existent. See the <filename>NOTES</filename> file for
|
||||
architecture dependent options. Some options, mainly
|
||||
architecture independent ones, are stored in the
|
||||
<filename>/usr/src/sys/conf/NOTES</filename> file. It's
|
||||
advisable to review the options in here also.</para></note>
|
||||
|
||||
<indexterm>
|
||||
<primary>kernel</primary>
|
||||
|
|
@ -486,12 +493,13 @@
|
|||
cpu I586_CPU
|
||||
cpu I686_CPU</programlisting>
|
||||
|
||||
<para>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 <literal>I586_CPU</literal> or
|
||||
<literal>I686_CPU</literal>), 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 <filename>/var/run/dmesg.boot</filename> file to view your boot
|
||||
<para>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
|
||||
<literal>I586_CPU</literal> or <literal>I686_CPU</literal>),
|
||||
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
|
||||
<filename>/var/run/dmesg.boot</filename> file to view your boot
|
||||
up messages.</para>
|
||||
|
||||
<indexterm>
|
||||
|
|
@ -693,20 +701,24 @@ options FFS_ROOT #FFS usable as root device [keep this!]</programli
|
|||
|
||||
<programlisting>options UFS_DIRHASH #Improve performance on big directories</programlisting>
|
||||
|
||||
<para>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.</para>
|
||||
<para>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.</para>
|
||||
|
||||
<programlisting>options SOFTUPDATES #Enable FFS Soft Updates support</programlisting>
|
||||
|
||||
<para>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 <literal>soft-updates</literal> option then
|
||||
you will need to activate it using the &man.tunefs.8; (for existing filesystems) or &man.newfs.8; (for new filesystems) commands.</para>
|
||||
<para>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 <literal>soft-updates</literal> option then you will
|
||||
need to activate it using the &man.tunefs.8; (for existing
|
||||
filesystems) or &man.newfs.8; (for new filesystems)
|
||||
commands.</para>
|
||||
|
||||
<programlisting>options MFS #Memory Filesystem
|
||||
options MD_ROOT #MD is a potential root device</programlisting>
|
||||
|
|
@ -833,9 +845,10 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 required</programli
|
|||
<para>This option allows you to boot the visual configuration editor
|
||||
from the boot menu.</para>
|
||||
|
||||
<note><para>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 <xref linkend="device-hints"></para></note>
|
||||
<note><para>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 <xref linkend="device-hints"></para></note>
|
||||
|
||||
<programlisting>options KTRACE #ktrace(1) support</programlisting>
|
||||
|
||||
|
|
@ -907,8 +920,10 @@ options _KPOSIX_PRIORITY_SCHEDULING</programlisting>
|
|||
<programlisting>device isa</programlisting>
|
||||
|
||||
<para>All 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 <filename>/usr/src/sys/i386/conf/LINT</filename>.</para>
|
||||
IBM PS/2 (Micro Channel Architecture), &os; provides some
|
||||
limited support at this time. For more information about the
|
||||
MCA support, see
|
||||
<filename>/usr/src/sys/i386/conf/LINT</filename>.</para>
|
||||
|
||||
<programlisting>device eisa</programlisting>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue