More things that should be filenames marked up as such.
This commit is contained in:
Nik Clayton
parent
190d8f54c8
commit
4649264b1d
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=3009
4 changed files with 61 additions and 72 deletions
|
|
@ -261,4 +261,5 @@ for example,
|
|||
Changed the declaration at the top of the handbook to use this new
|
||||
DTD.
|
||||
|
||||
18. Yet more things that should be filenames marked up as such.
|
||||
|
||||
|
|
|
|||
|
|
@ -1861,8 +1861,7 @@
|
|||
|
||||
<para>If your machine is already running MS-DOS and has little or no
|
||||
free space available for FreeBSD's installation, all is not lost!
|
||||
You may find the FIPS utility, provided in the <emphasis
|
||||
remap=tt>tools</emphasis> directory on the FreeBSD CDROM or on the
|
||||
You may find the FIPS utility, provided in the <filename>tools</filename> directory on the FreeBSD CDROM or on the
|
||||
various FreeBSD ftp sites, to be quite useful.</para>
|
||||
|
||||
<para>FIPS allows you to split an existing MS-DOS partition into two
|
||||
|
|
@ -1894,10 +1893,10 @@
|
|||
partitions?</emphasis></para>
|
||||
|
||||
<para>Yes. DOS extended partitions are mapped in at the end of the
|
||||
other <quote>slices</quote> in FreeBSD, e.g. your D: drive might be /dev/sd0s5,
|
||||
your E: drive /dev/sd0s6, and so on. This example assumes, of
|
||||
other <quote>slices</quote> in FreeBSD, e.g. your <filename>D:</filename> drive might be <filename>/dev/sd0s5</filename>,
|
||||
your <filename>E:</filename> drive <filename>/dev/sd0s6</filename>, and so on. This example assumes, of
|
||||
course, that your extended partition is on SCSI drive 0. For IDE
|
||||
drives, substitute ``wd'' for ``sd'' appropriately. You otherwise
|
||||
drives, substitute <filename>wd</filename> for <filename>sd</filename> appropriately. You otherwise
|
||||
mount extended partitions exactly like you would mount any other DOS
|
||||
drive, e.g.:</para>
|
||||
|
||||
|
|
@ -2501,7 +2500,7 @@
|
|||
|
||||
<para>This is probably not the place to go into a detailed
|
||||
examination of how Makefiles work; suffice it to say that the line
|
||||
starting with ``MAN3'' ensures that the ElectricFence man page is
|
||||
starting with <literal>MAN3</literal> ensures that the ElectricFence man page is
|
||||
compressed after installation, to help conserve your precious disk
|
||||
space. The original port did not provide an ``install'' target,
|
||||
so the three lines from ``do-install'' ensure that the files
|
||||
|
|
@ -3735,8 +3734,8 @@
|
|||
|
||||
<listitem>
|
||||
<para>Floppy drive controller: <emphasis
|
||||
remap=tt>fd0</emphasis> is the <hardware>A:</hardware> floppy drive, and
|
||||
<emphasis remap=tt>fd1</emphasis> is the <hardware>B:</hardware> drive.
|
||||
remap=tt>fd0</emphasis> is the <filename>A:</filename> floppy drive, and
|
||||
<emphasis remap=tt>fd1</emphasis> is the <filename>B:</filename> drive.
|
||||
<emphasis remap=tt>ft0</emphasis> is a QIC-80 tape drive
|
||||
attached to the floppy controller. Comment out any lines
|
||||
corresponding to devices you do not have.</para>
|
||||
|
|
@ -4709,7 +4708,7 @@
|
|||
<informalexample>
|
||||
<screen>controller wcd0</screen>
|
||||
</informalexample> This means that you should look for some entries
|
||||
that start with <emphasis remap=tt>wcd0</emphasis> in the
|
||||
that start with <filename>wcd0</filename> in the
|
||||
<filename>/dev</filename> directory, possibly followed by a letter,
|
||||
such as <token>c</token>, or preceded by the letter <token>r</token>, which means a <quote>raw</quote>
|
||||
device. It turns out that those files are not there, so I must
|
||||
|
|
@ -4717,8 +4716,7 @@
|
|||
<informalexample>
|
||||
<screen># sh MAKEDEV wcd0</screen>
|
||||
</informalexample> When this script finishes, you will find that
|
||||
there are now <filename>wcd0c</filename> and <emphasis
|
||||
remap=tt>rwcd0c</emphasis> entries in <filename>/dev</filename> so
|
||||
there are now <filename>wcd0c</filename> and <filename>rwcd0c</filename> entries in <filename>/dev</filename> so
|
||||
you know that it executed correctly.</para>
|
||||
|
||||
<para>For sound cards, the command:
|
||||
|
|
@ -8785,7 +8783,7 @@
|
|||
<para>Replace the job name on the header page with
|
||||
<emphasis remap=it>text</emphasis>. The job name is
|
||||
normally the name of the first file of the job, or
|
||||
``stdin'' if you are printing standard input.</para>
|
||||
<filename>stdin</filename> if you are printing standard input.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -18806,13 +18804,13 @@
|
|||
|
||||
<listitem>
|
||||
<para> Each <literal>nx=</literal> entry matches another
|
||||
<emphasis remap=tt>gettytab</emphasis> capability name
|
||||
<filename>gettytab</filename> capability name
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para> Each <literal>tc=</literal> entry matches another
|
||||
<emphasis remap=tt>gettytab</emphasis> capability name
|
||||
<filename>gettytab</filename> capability name
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -22576,8 +22574,7 @@
|
|||
<listitem>
|
||||
<para>Get pop software from the <ulink
|
||||
URL="../ports/mail.html">Ports collection</ulink> that
|
||||
can be found in <emphasis remap=tt><emphasis
|
||||
remap=bf>/usr/ports </emphasis></emphasis> or packages
|
||||
can be found in <filename>/usr/ports</filename> or packages
|
||||
collection. This handbook section has a complete reference
|
||||
on the <xref linkend="ports"
|
||||
remap="Ports"> system.</para>
|
||||
|
|
@ -22780,8 +22777,7 @@
|
|||
</para>
|
||||
|
||||
<para>Do not panic, this is only a few hundred kilobytes in size.
|
||||
The file <filename>README</filename> in the <emphasis
|
||||
remap=tt>cf</emphasis> directory can serve as a basic
|
||||
The file <filename>README</filename> in the <filename>cf</filename> directory can serve as a basic
|
||||
introduction to m4 configuration.</para>
|
||||
|
||||
<para>For UUCP delivery, you are best advised to use the
|
||||
|
|
@ -23555,15 +23551,15 @@
|
|||
into a <application>CTM</application> supported tree.</para>
|
||||
|
||||
<para>You can recognize these transition deltas by the
|
||||
<emphasis remap=tt>X</emphasis> appended to the number
|
||||
<filename>X</filename> appended to the number
|
||||
(<filename>src-cur.3210XEmpty.gz</filename> for instance). The
|
||||
designation following the <emphasis remap=tt>X</emphasis>
|
||||
corresponds to the origin of your initial <quote>seed</quote>. ``Empty'' is
|
||||
an empty directory, ``R225'' would designate the 2.2.5 release,
|
||||
etc. As a rule a base transition from ``Empty'' is producted
|
||||
designation following the <filename>X</filename>
|
||||
corresponds to the origin of your initial <quote>seed</quote>. <filename>Empty</filename> is
|
||||
an empty directory, <filename>R225</filename> would designate the 2.2.5 release,
|
||||
etc. As a rule a base transition from <filename>Empty</filename> is producted
|
||||
every 100 deltas. By the way, they are large! 25 to 30
|
||||
Megabytes of <command>gzip</command>'ed data is
|
||||
common for the ``XEmpty'' deltas.</para>
|
||||
common for the <filename>XEmpty</filename> deltas.</para>
|
||||
|
||||
<para>Once you've picked a base delta to start from, you will also
|
||||
need all deltas with higher numbers following it.</para>
|
||||
|
|
|
|||
|
|
@ -1861,8 +1861,7 @@
|
|||
|
||||
<para>If your machine is already running MS-DOS and has little or no
|
||||
free space available for FreeBSD's installation, all is not lost!
|
||||
You may find the FIPS utility, provided in the <emphasis
|
||||
remap=tt>tools</emphasis> directory on the FreeBSD CDROM or on the
|
||||
You may find the FIPS utility, provided in the <filename>tools</filename> directory on the FreeBSD CDROM or on the
|
||||
various FreeBSD ftp sites, to be quite useful.</para>
|
||||
|
||||
<para>FIPS allows you to split an existing MS-DOS partition into two
|
||||
|
|
@ -1894,10 +1893,10 @@
|
|||
partitions?</emphasis></para>
|
||||
|
||||
<para>Yes. DOS extended partitions are mapped in at the end of the
|
||||
other <quote>slices</quote> in FreeBSD, e.g. your D: drive might be /dev/sd0s5,
|
||||
your E: drive /dev/sd0s6, and so on. This example assumes, of
|
||||
other <quote>slices</quote> in FreeBSD, e.g. your <filename>D:</filename> drive might be <filename>/dev/sd0s5</filename>,
|
||||
your <filename>E:</filename> drive <filename>/dev/sd0s6</filename>, and so on. This example assumes, of
|
||||
course, that your extended partition is on SCSI drive 0. For IDE
|
||||
drives, substitute ``wd'' for ``sd'' appropriately. You otherwise
|
||||
drives, substitute <filename>wd</filename> for <filename>sd</filename> appropriately. You otherwise
|
||||
mount extended partitions exactly like you would mount any other DOS
|
||||
drive, e.g.:</para>
|
||||
|
||||
|
|
@ -2501,7 +2500,7 @@
|
|||
|
||||
<para>This is probably not the place to go into a detailed
|
||||
examination of how Makefiles work; suffice it to say that the line
|
||||
starting with ``MAN3'' ensures that the ElectricFence man page is
|
||||
starting with <literal>MAN3</literal> ensures that the ElectricFence man page is
|
||||
compressed after installation, to help conserve your precious disk
|
||||
space. The original port did not provide an ``install'' target,
|
||||
so the three lines from ``do-install'' ensure that the files
|
||||
|
|
@ -3735,8 +3734,8 @@
|
|||
|
||||
<listitem>
|
||||
<para>Floppy drive controller: <emphasis
|
||||
remap=tt>fd0</emphasis> is the <hardware>A:</hardware> floppy drive, and
|
||||
<emphasis remap=tt>fd1</emphasis> is the <hardware>B:</hardware> drive.
|
||||
remap=tt>fd0</emphasis> is the <filename>A:</filename> floppy drive, and
|
||||
<emphasis remap=tt>fd1</emphasis> is the <filename>B:</filename> drive.
|
||||
<emphasis remap=tt>ft0</emphasis> is a QIC-80 tape drive
|
||||
attached to the floppy controller. Comment out any lines
|
||||
corresponding to devices you do not have.</para>
|
||||
|
|
@ -4709,7 +4708,7 @@
|
|||
<informalexample>
|
||||
<screen>controller wcd0</screen>
|
||||
</informalexample> This means that you should look for some entries
|
||||
that start with <emphasis remap=tt>wcd0</emphasis> in the
|
||||
that start with <filename>wcd0</filename> in the
|
||||
<filename>/dev</filename> directory, possibly followed by a letter,
|
||||
such as <token>c</token>, or preceded by the letter <token>r</token>, which means a <quote>raw</quote>
|
||||
device. It turns out that those files are not there, so I must
|
||||
|
|
@ -4717,8 +4716,7 @@
|
|||
<informalexample>
|
||||
<screen># sh MAKEDEV wcd0</screen>
|
||||
</informalexample> When this script finishes, you will find that
|
||||
there are now <filename>wcd0c</filename> and <emphasis
|
||||
remap=tt>rwcd0c</emphasis> entries in <filename>/dev</filename> so
|
||||
there are now <filename>wcd0c</filename> and <filename>rwcd0c</filename> entries in <filename>/dev</filename> so
|
||||
you know that it executed correctly.</para>
|
||||
|
||||
<para>For sound cards, the command:
|
||||
|
|
@ -8785,7 +8783,7 @@
|
|||
<para>Replace the job name on the header page with
|
||||
<emphasis remap=it>text</emphasis>. The job name is
|
||||
normally the name of the first file of the job, or
|
||||
``stdin'' if you are printing standard input.</para>
|
||||
<filename>stdin</filename> if you are printing standard input.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -18806,13 +18804,13 @@
|
|||
|
||||
<listitem>
|
||||
<para> Each <literal>nx=</literal> entry matches another
|
||||
<emphasis remap=tt>gettytab</emphasis> capability name
|
||||
<filename>gettytab</filename> capability name
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para> Each <literal>tc=</literal> entry matches another
|
||||
<emphasis remap=tt>gettytab</emphasis> capability name
|
||||
<filename>gettytab</filename> capability name
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -22576,8 +22574,7 @@
|
|||
<listitem>
|
||||
<para>Get pop software from the <ulink
|
||||
URL="../ports/mail.html">Ports collection</ulink> that
|
||||
can be found in <emphasis remap=tt><emphasis
|
||||
remap=bf>/usr/ports </emphasis></emphasis> or packages
|
||||
can be found in <filename>/usr/ports</filename> or packages
|
||||
collection. This handbook section has a complete reference
|
||||
on the <xref linkend="ports"
|
||||
remap="Ports"> system.</para>
|
||||
|
|
@ -22780,8 +22777,7 @@
|
|||
</para>
|
||||
|
||||
<para>Do not panic, this is only a few hundred kilobytes in size.
|
||||
The file <filename>README</filename> in the <emphasis
|
||||
remap=tt>cf</emphasis> directory can serve as a basic
|
||||
The file <filename>README</filename> in the <filename>cf</filename> directory can serve as a basic
|
||||
introduction to m4 configuration.</para>
|
||||
|
||||
<para>For UUCP delivery, you are best advised to use the
|
||||
|
|
@ -23555,15 +23551,15 @@
|
|||
into a <application>CTM</application> supported tree.</para>
|
||||
|
||||
<para>You can recognize these transition deltas by the
|
||||
<emphasis remap=tt>X</emphasis> appended to the number
|
||||
<filename>X</filename> appended to the number
|
||||
(<filename>src-cur.3210XEmpty.gz</filename> for instance). The
|
||||
designation following the <emphasis remap=tt>X</emphasis>
|
||||
corresponds to the origin of your initial <quote>seed</quote>. ``Empty'' is
|
||||
an empty directory, ``R225'' would designate the 2.2.5 release,
|
||||
etc. As a rule a base transition from ``Empty'' is producted
|
||||
designation following the <filename>X</filename>
|
||||
corresponds to the origin of your initial <quote>seed</quote>. <filename>Empty</filename> is
|
||||
an empty directory, <filename>R225</filename> would designate the 2.2.5 release,
|
||||
etc. As a rule a base transition from <filename>Empty</filename> is producted
|
||||
every 100 deltas. By the way, they are large! 25 to 30
|
||||
Megabytes of <command>gzip</command>'ed data is
|
||||
common for the ``XEmpty'' deltas.</para>
|
||||
common for the <filename>XEmpty</filename> deltas.</para>
|
||||
|
||||
<para>Once you've picked a base delta to start from, you will also
|
||||
need all deltas with higher numbers following it.</para>
|
||||
|
|
|
|||
|
|
@ -1861,8 +1861,7 @@
|
|||
|
||||
<para>If your machine is already running MS-DOS and has little or no
|
||||
free space available for FreeBSD's installation, all is not lost!
|
||||
You may find the FIPS utility, provided in the <emphasis
|
||||
remap=tt>tools</emphasis> directory on the FreeBSD CDROM or on the
|
||||
You may find the FIPS utility, provided in the <filename>tools</filename> directory on the FreeBSD CDROM or on the
|
||||
various FreeBSD ftp sites, to be quite useful.</para>
|
||||
|
||||
<para>FIPS allows you to split an existing MS-DOS partition into two
|
||||
|
|
@ -1894,10 +1893,10 @@
|
|||
partitions?</emphasis></para>
|
||||
|
||||
<para>Yes. DOS extended partitions are mapped in at the end of the
|
||||
other <quote>slices</quote> in FreeBSD, e.g. your D: drive might be /dev/sd0s5,
|
||||
your E: drive /dev/sd0s6, and so on. This example assumes, of
|
||||
other <quote>slices</quote> in FreeBSD, e.g. your <filename>D:</filename> drive might be <filename>/dev/sd0s5</filename>,
|
||||
your <filename>E:</filename> drive <filename>/dev/sd0s6</filename>, and so on. This example assumes, of
|
||||
course, that your extended partition is on SCSI drive 0. For IDE
|
||||
drives, substitute ``wd'' for ``sd'' appropriately. You otherwise
|
||||
drives, substitute <filename>wd</filename> for <filename>sd</filename> appropriately. You otherwise
|
||||
mount extended partitions exactly like you would mount any other DOS
|
||||
drive, e.g.:</para>
|
||||
|
||||
|
|
@ -2501,7 +2500,7 @@
|
|||
|
||||
<para>This is probably not the place to go into a detailed
|
||||
examination of how Makefiles work; suffice it to say that the line
|
||||
starting with ``MAN3'' ensures that the ElectricFence man page is
|
||||
starting with <literal>MAN3</literal> ensures that the ElectricFence man page is
|
||||
compressed after installation, to help conserve your precious disk
|
||||
space. The original port did not provide an ``install'' target,
|
||||
so the three lines from ``do-install'' ensure that the files
|
||||
|
|
@ -3735,8 +3734,8 @@
|
|||
|
||||
<listitem>
|
||||
<para>Floppy drive controller: <emphasis
|
||||
remap=tt>fd0</emphasis> is the <hardware>A:</hardware> floppy drive, and
|
||||
<emphasis remap=tt>fd1</emphasis> is the <hardware>B:</hardware> drive.
|
||||
remap=tt>fd0</emphasis> is the <filename>A:</filename> floppy drive, and
|
||||
<emphasis remap=tt>fd1</emphasis> is the <filename>B:</filename> drive.
|
||||
<emphasis remap=tt>ft0</emphasis> is a QIC-80 tape drive
|
||||
attached to the floppy controller. Comment out any lines
|
||||
corresponding to devices you do not have.</para>
|
||||
|
|
@ -4709,7 +4708,7 @@
|
|||
<informalexample>
|
||||
<screen>controller wcd0</screen>
|
||||
</informalexample> This means that you should look for some entries
|
||||
that start with <emphasis remap=tt>wcd0</emphasis> in the
|
||||
that start with <filename>wcd0</filename> in the
|
||||
<filename>/dev</filename> directory, possibly followed by a letter,
|
||||
such as <token>c</token>, or preceded by the letter <token>r</token>, which means a <quote>raw</quote>
|
||||
device. It turns out that those files are not there, so I must
|
||||
|
|
@ -4717,8 +4716,7 @@
|
|||
<informalexample>
|
||||
<screen># sh MAKEDEV wcd0</screen>
|
||||
</informalexample> When this script finishes, you will find that
|
||||
there are now <filename>wcd0c</filename> and <emphasis
|
||||
remap=tt>rwcd0c</emphasis> entries in <filename>/dev</filename> so
|
||||
there are now <filename>wcd0c</filename> and <filename>rwcd0c</filename> entries in <filename>/dev</filename> so
|
||||
you know that it executed correctly.</para>
|
||||
|
||||
<para>For sound cards, the command:
|
||||
|
|
@ -8785,7 +8783,7 @@
|
|||
<para>Replace the job name on the header page with
|
||||
<emphasis remap=it>text</emphasis>. The job name is
|
||||
normally the name of the first file of the job, or
|
||||
``stdin'' if you are printing standard input.</para>
|
||||
<filename>stdin</filename> if you are printing standard input.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -18806,13 +18804,13 @@
|
|||
|
||||
<listitem>
|
||||
<para> Each <literal>nx=</literal> entry matches another
|
||||
<emphasis remap=tt>gettytab</emphasis> capability name
|
||||
<filename>gettytab</filename> capability name
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para> Each <literal>tc=</literal> entry matches another
|
||||
<emphasis remap=tt>gettytab</emphasis> capability name
|
||||
<filename>gettytab</filename> capability name
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -22576,8 +22574,7 @@
|
|||
<listitem>
|
||||
<para>Get pop software from the <ulink
|
||||
URL="../ports/mail.html">Ports collection</ulink> that
|
||||
can be found in <emphasis remap=tt><emphasis
|
||||
remap=bf>/usr/ports </emphasis></emphasis> or packages
|
||||
can be found in <filename>/usr/ports</filename> or packages
|
||||
collection. This handbook section has a complete reference
|
||||
on the <xref linkend="ports"
|
||||
remap="Ports"> system.</para>
|
||||
|
|
@ -22780,8 +22777,7 @@
|
|||
</para>
|
||||
|
||||
<para>Do not panic, this is only a few hundred kilobytes in size.
|
||||
The file <filename>README</filename> in the <emphasis
|
||||
remap=tt>cf</emphasis> directory can serve as a basic
|
||||
The file <filename>README</filename> in the <filename>cf</filename> directory can serve as a basic
|
||||
introduction to m4 configuration.</para>
|
||||
|
||||
<para>For UUCP delivery, you are best advised to use the
|
||||
|
|
@ -23555,15 +23551,15 @@
|
|||
into a <application>CTM</application> supported tree.</para>
|
||||
|
||||
<para>You can recognize these transition deltas by the
|
||||
<emphasis remap=tt>X</emphasis> appended to the number
|
||||
<filename>X</filename> appended to the number
|
||||
(<filename>src-cur.3210XEmpty.gz</filename> for instance). The
|
||||
designation following the <emphasis remap=tt>X</emphasis>
|
||||
corresponds to the origin of your initial <quote>seed</quote>. ``Empty'' is
|
||||
an empty directory, ``R225'' would designate the 2.2.5 release,
|
||||
etc. As a rule a base transition from ``Empty'' is producted
|
||||
designation following the <filename>X</filename>
|
||||
corresponds to the origin of your initial <quote>seed</quote>. <filename>Empty</filename> is
|
||||
an empty directory, <filename>R225</filename> would designate the 2.2.5 release,
|
||||
etc. As a rule a base transition from <filename>Empty</filename> is producted
|
||||
every 100 deltas. By the way, they are large! 25 to 30
|
||||
Megabytes of <command>gzip</command>'ed data is
|
||||
common for the ``XEmpty'' deltas.</para>
|
||||
common for the <filename>XEmpty</filename> deltas.</para>
|
||||
|
||||
<para>Once you've picked a base delta to start from, you will also
|
||||
need all deltas with higher numbers following it.</para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue