Remove remains of previous 2 ways used to build a custom kernel (since

only 1 way is now documented in this book).

Found by:	Paco Cubi <francisco.cubi@gmail.com>
This commit is contained in:
Marc Fonvieille 2007-03-11 10:58:21 +00:00
parent 881218b612
commit 8474e8d299
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=29767

View file

@ -253,48 +253,7 @@
with new information than this handbook.</para>
</note>
<para>You must now compile the source code for the kernel. There are two
procedures you can use to do this, and the one you will use depends on
why you are rebuilding the kernel and the version of &os; that you are
running.</para>
<itemizedlist>
<listitem>
<para>If you have installed <emphasis>only</emphasis> the kernel
source code, use procedure 1.</para>
</listitem>
<listitem>
<para>If you are building a new kernel without updating the source
code (perhaps just to add a new option, such as
<literal>IPFIREWALL</literal>) you can use either procedure.</para>
</listitem>
<listitem>
<para>If you are rebuilding the kernel as part of a
<command>make buildworld</command> process, use procedure 2.
</para>
</listitem>
</itemizedlist>
<indexterm>
<primary><command>cvsup</command></primary>
</indexterm>
<indexterm><primary>CTM</primary></indexterm>
<indexterm>
<primary>CVS</primary>
<secondary>anonymous</secondary>
</indexterm>
<para>If you have <emphasis>not</emphasis> upgraded your source
tree in any way since the last time you successfully completed
a <maketarget>buildworld</maketarget>-<maketarget>installworld</maketarget> cycle
(you have not run <application>CVSup</application>,
<application>CTM</application>, or used
<application>anoncvs</application>), then it is safe to use the
<command>config</command>, <command>make depend</command>,
<command>make</command>, <command>make install</command> sequence.
</para>
<para>You must now compile the source code for the kernel.</para>
<procedure>
<title>Building a Kernel</title>