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

Add 26 index entries

Browse source 
Submitted by:	Valentino Vaschetto <valentino.vaschetto@windriver.com>
This commit is contained in:
Murray Stokely 2001-06-26 17:46:16 +00:00
parent f8dfb38f76
commit acd83cd066
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9730
1 changed files with 27 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.43 2001/06/21 17:20:59 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.44 2001/06/23 05:20:27 dd Exp $
-->
<chapter id="kernelconfig">
@ -13,7 +13,7 @@
<para><emphasis>Updated and restructured by &a.jim;, March 2000.
Originally contributed by &a.jehamby;, 6 October
1995.</emphasis></para>
<indexterm><primary>kernel</primary><secondary>building a custom kernel</secondary></indexterm>
<para>The following chapter of the handbook covers everything you will
need to know in order to build a custom kernel. If you are
wondering what the benefits of a custom kernel are, or would like to
@ -57,7 +57,7 @@
<sect1 id="kernelconfig-building">
<title>Building and Installing a Custom Kernel</title>
<indexterm><primary>kernel</primary><secondary>building / installing</secondary></indexterm>
<para>First, let us take a quick tour of the kernel build directory.
All directories mentioned will be relative to the main
<filename>/usr/src/sys</filename> directory, which is also
@ -118,6 +118,7 @@
changes you have made to differentiate it from
<filename>GENERIC</filename>.</para>
<indexterm><primary>SunOS</primary></indexterm>
<para>If you have built a kernel under SunOS or some other BSD
operating system, much of this file will be very familiar to you.
If you are coming from some other operating system such as DOS, on
@ -177,6 +178,10 @@
recognize KERNCONF=</para>
</note>
<indexterm><primary>CVSup</primary></indexterm>
<indexterm><primary>anoncvs</primary></indexterm>
<indexterm><primary>CVS</primary><secondary>anonymous</secondary></indexterm>
<indexterm><primary>CTM</primary></indexterm>
<para>If you have <emphasis>not</emphasis> upgraded your source
tree in any way (you have not run <application>CVSup</application>,
<application>CTM</application>, or used
@ -194,7 +199,7 @@
build your kernel if you have updated the
sources!</emphasis></para>
</warning>
<indexterm><primary>kernel.old</primary></indexterm>
<para>The new kernel will be copied to the root directory as
<filename>/kernel</filename> and the old kernel will be moved to
<filename>/kernel.old</filename>. Now, shutdown the system and
@ -214,7 +219,9 @@
<sect1 id="kernelconfig-config">
<title>The Configuration File</title>
<indexterm><primary>kernel</primary><secondary>config file</secondary></indexterm>
<indexterm><primary>kernel</primary><secondary>LINT</secondary></indexterm>
<indexterm><primary>LINT</primary></indexterm>
<para>The general format of a configuration file is quite simple.
Each line contains a keyword and one or more arguments. For
simplicity, most lines only contain one argument. Anything
@ -246,6 +253,7 @@
files on your system for examples.</para>
</important>
<indexterm><primary>kernel</primary><secondary>example config</secondary></indexterm>
<para>The following is an example <filename>GENERIC</filename> kernel
configuration file with various additional comments where needed for
clarity. This example should match your copy in
@ -275,12 +283,14 @@
<para>The following are the mandatory keywords required in
<emphasis>every</emphasis> kernel you build:</para>
<indexterm><primary>kernel options</primary><secondary>machine</secondary></indexterm>
<programlisting>machine i386</programlisting>
<para>This is the machine architecture. It must be either
<literal>i386</literal>, <literal>alpha</literal>, or
<literal>pc98</literal>.</para>
<indexterm><primary>kernel options</primary><secondary>cpu</secondary></indexterm>
<programlisting>cpu I386_CPU
cpu I486_CPU
cpu I586_CPU
@ -294,6 +304,7 @@ cpu I686_CPU</programlisting>
your CPU use, you can use the <command>dmesg</command> command to
view your boot up messages.</para>
<indexterm><primary>kernel options</primary><secondary>cpu type</secondary></indexterm>
<para>The Alpha architecture has different values for
<literal>cpu_type</literal>. They include:</para>
@ -303,6 +314,7 @@ cpu EV5</programlisting>
<para>If you are using an Alpha machine, you should be using one of
the above CPU types.</para>
<indexterm><primary>kernel options</primary><secondary>ident</secondary></indexterm>
<programlisting>ident GENERIC</programlisting>
<para>This is the identification of the kernel. You should change
@ -313,6 +325,7 @@ cpu EV5</programlisting>
want to keep it separate from your usual kernel (i.e., you want to
build an experimental kernel).</para>
<indexterm><primary>kernel options</primary><secondary>maxusers</secondary></indexterm>
<programlisting>maxusers 32</programlisting>
<para>The <literal>maxusers</literal> option sets the size of a number
@ -405,6 +418,8 @@ options MD_ROOT #MD is a potential root device</programlisting>
<para>Now you simply need to either reboot, or run the command
<command>mount /tmp</command>.</para>
<indexterm><primary>kernel options</primary><secondary>NFS</secondary></indexterm>
<indexterm><primary>kernel options</primary><secondary>NFS_ROOT</secondary></indexterm>
<programlisting>options NFS #Network Filesystem
options NFS_ROOT #NFS usable as root device, NFS required</programlisting>
@ -412,6 +427,7 @@ options NFS_ROOT #NFS usable as root device, NFS required</programl
from a UNIX file server over TCP/IP, you can comment these
out.</para>
<indexterm><primary>kernel options</primary><secondary>MSDOSFS</secondary></indexterm>
<programlisting>options MSDOSFS #MSDOS Filesystem</programlisting>
<para>The MS-DOS filesystem. Unless you plan to mount a DOS formatted
@ -505,12 +521,14 @@ options _KPOSIX_PRIORITY_SCHEDULING</programlisting>
applications in the ports collection use these (such as Star
Office).</para>
<indexterm><primary>kernel options</primary><secondary>ICMP_BANDLIM</secondary></indexterm>
<programlisting>options ICMP_BANDLIM #Rate limit bad replies</programlisting>
<para>This option enables ICMP error response bandwidth limiting. You
typically want this option as it will help protect the machine from
denial of service packet attacks.</para>
<indexterm><primary>kernel options</primary><secondary>SMP</secondary></indexterm>
<programlisting># To make an SMP kernel, the next two are needed
#options SMP # Symmetric MultiProcessor Kernel
#options APIC_IO # Symmetric (APIC) I/O</programlisting>
@ -759,6 +777,7 @@ device ppc0 at isa? irq 7</programlisting>
<programlisting>#device vpo # Requires scbus and da</programlisting>
<indexterm><primary>zip drive</primary></indexterm>
<para>This is for an Iomega Zip drive. It requires
<literal>scbus</literal> and <literal>da</literal> support. Best
performance is achieved with ports in EPP 1.9 mode.</para>
@ -926,6 +945,8 @@ pseudo-device bpf # Berkeley packet filter</programlisting>
<sect1 id="kernelconfig-nodes">
<title>Making Device Nodes</title>
<indexterm><primary>device nodes</primary></indexterm>
<indexterm><primary>MAKEDEV</primary></indexterm>
<para>Almost every device in the kernel has a corresponding
<quote>node</quote> entry in the <filename>/dev</filename> directory.
These nodes look like regular files, but are actually special
@ -951,6 +972,7 @@ pseudo-device bpf # Berkeley packet filter</programlisting>
turns out that those files are not there, so you must change to the
<filename>/dev</filename> directory and type:</para>
<indexterm><primary>MAKEDEV</primary></indexterm>
<screen>&prompt.root; <userinput>sh MAKEDEV acd0</userinput></screen>
<para>When this script finishes, you will find that there are now