Update GENERIC config file header comments. Also remove I386_CPU from

the cpu lines shown in the sample, but expand the <note> we previously
had to describe in detail it's current state in FreeBSD.

en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml

@@ -467,14 +467,15 @@
 #
 # The handbook is also available locally in /usr/share/doc/handbook
 # if you've installed the doc distribution, otherwise always see the
-# &os; World Wide Web server (http://www.&os;.ORG/) for the
+# &os; World Wide Web server (http://www.FreeBSD.org/) for the
 # latest information.
 #
 # An exhaustive list of options and more detailed explanations of the
-# device lines is also present in the ./LINT configuration file. If you are
+# device lines is also present in the ../../conf/NOTES and NOTES files. 
-# in doubt as to the purpose or necessity of a line, check first in LINT.
+# If you are in doubt as to the purpose or necessity of a line, check first 
+# in NOTES.
 #
-# &dollar;&os;: src/sys/i386/conf/GENERIC,v 1.246 2000/03/09 16:32:55 jlemon Exp &dollar;</programlisting>
+# &dollar;FreeBSD: src/sys/i386/conf/GENERIC,v 1.380 2003/03/29 13:36:41 mdodd Exp $</programlisting>
 
     <para>The following are the mandatory keywords required in
       <emphasis>every</emphasis> kernel you build:</para>
@@ -493,8 +494,7 @@
       <primary>kernel options</primary>
       <secondary>cpu</secondary>
     </indexterm>
-    <programlisting>cpu          I386_CPU
+    <programlisting>cpu          I486_CPU
-cpu          I486_CPU
 cpu          I586_CPU
 cpu          I686_CPU</programlisting>
 
@@ -506,12 +506,38 @@ cpu          I686_CPU</programlisting>
       CPU type, you can check the <filename>/var/run/dmesg.boot</filename> file to view your boot
       up messages.</para>
 
-    <note><para>In &os; 5.0, support for <literal>I386_CPU</literal>
-      is disabled by default.</para></note>
     <indexterm>
       <primary>kernel options</primary>
       <secondary>cpu type</secondary>
     </indexterm>
+    <para>Support for <literal>I386_CPU</literal> is still provided in the
+      source of &os;, but it is disabled by default in both -STABLE and
+      -CURRENT.  This means that to install &os; with a 386-class cpu, you now
+      have the following options:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Install an older &os; release and rebuild from source as
+	  described in <xref linkend="kernelconfig-building"></para>
+
+      </listitem>
+
+      <listitem>
+        <para>Build the userland and kernel on a newer machine and install on
+          the 386 using the precompiled <filename>/usr/obj</filename>
+          files.</para>
+      </listitem>
+
+      <listitem>
+        <para>Roll your own release of FreeBSD which includes
+          <literal>I386_CPU</literal> support in the kernels of the
+          installation CD-ROM.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>The first of these options is probably the easiest of all, but you
+      will need a lot of disk space on a 386-class machine which may be
+      difficult to find.</para>
 
     <indexterm>
       <primary>kernel options</primary>
@@ -521,8 +547,9 @@ cpu          I686_CPU</programlisting>
     <programlisting>ident          GENERIC</programlisting>
 
     <para>This is the identification of the kernel.  You should change
-      this to whatever you named your kernel, as in our previous example,
+      this to whatever you named your kernel,
-      <literal>MYKERNEL</literal>.  The value you put in the
+      i.e. <literal>MYKERNEL</literal> if you have followed the
+      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