Date: Wed, 30 Jun 1999 22:30:01 -0700 (PDT) From: Chris Costello <chris@calldei.com> To: freebsd-doc@freebsd.org Subject: Re: docs/12181 Message-ID: <199907010530.WAA22955@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR docs/12181; it has been noted by GNATS.
From: Chris Costello <chris@calldei.com>
To: freebsd-gnats-submit@freebsd.org
Cc:
Subject: Re: docs/12181
Date: Thu, 1 Jul 1999 00:27:44 -0500
This patch should deal with the quotes problem.
Index: chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en/handbook/kernelconfig/chapter.sgml,v
retrieving revision 1.16
diff -u -r1.16 chapter.sgml
--- chapter.sgml 1999/05/28 00:31:25 1.16
+++ chapter.sgml 1999/07/01 05:26:13
@@ -21,7 +21,7 @@
<para>Building a custom kernel is one of the most important rites of
passage every Unix system administrator must endure. This process,
while time-consuming, will provide many benefits to your FreeBSD system.
- Unlike the <literal>GENERIC</literal> kernel, which must support every
+ Unlike the <filename>GENERIC</filename> kernel, which must support every
possible SCSI and network card, along with tons of other rarely used
hardware support, a custom kernel only contains support for
<emphasis>your</emphasis> PC's hardware. This has a number of
@@ -195,7 +195,8 @@
<variablelist>
<varlistentry>
- <term><literal>machine "i386"</literal></term>
+ <term><literal>machine <replaceable>arch</replaceable></literal>
+ </term>
<listitem>
<para>The first keyword is <literal>machine</literal>, which,
@@ -272,19 +273,19 @@
<listitem>
<para>Next, we have <literal>ident</literal>, which is the
identification of the kernel. You should change this from
- <literal>GENERIC</literal> to whatever you named your kernel, in
- this example, <literal>MYKERNEL</literal>. The value you put in
+ <filename>GENERIC</filename> to whatever you named your kernel, in
+ this example, <filename>MYKERNEL</filename>. The value you put in
<literal>ident</literal> will print when you boot up the kernel,
so it is useful to give a kernel a different name if you want to
keep it separate from your usual kernel (if you want to build an
experimental kernel, for example). Note that, as with
- <literal>machine</literal> and <literal> cpu</literal>, enclose
+ <literal>machine</literal> and <literal>cpu</literal>, enclose
your kernel's name in quotation marks if it contains any
numbers.</para>
<para>Since this name is passed to the C compiler as a
<option>-D</option> switch, do not use names like
- <literal>DEBUG</literal>, or something that could be confused
+ <filename>DEBUG</filename>, or something that could be confused
with another machine or CPU name, like
<literal>vax</literal>.</para>
</listitem>
@@ -870,7 +871,7 @@
</varlistentry>
<varlistentry>
- <term><literal>device st0</literal></term>
+ <term><literal>device sa0</literal></term>
<listitem>
<para>Support for SCSI tape drives.</para>
@@ -1403,9 +1404,9 @@
<title>Sound cards</title>
<para>This is the first section containing lines that are not in the
- GENERIC kernel. To include sound card support, you will have to copy
- the appropriate lines from the LINT kernel (which contains support for
- <emphasis>every</emphasis> device) as follows:</para>
+ <filename>GENERIC</filename> kernel. To include sound card support, you
+ will have to copy the appropriate lines from the LINT kernel (which
+ support for <emphasis>every</emphasis> device) as follows:</para>
<variablelist>
--
Chris Costello <chris@calldei.com>
If at first you don't succeed, call it version 1.0
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907010530.WAA22955>