Converted appropriate occurences of <emphasis remap=tt>...</emphasis> to
<filename>...</filename> As with most of these conversions, I won't have got all of them in this first pass.
This commit is contained in:
parent
9a50f30a91
commit
f89eaac31c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=2929
4 changed files with 58 additions and 51 deletions
|
@ -3313,7 +3313,7 @@
|
|||
that do not depend on the architecture are listed in
|
||||
<filename>/sys/conf/options</filename>, architecture-dependent ones
|
||||
in
|
||||
<filename>/sys/<replaceable>arch</replaceable>/conf/options.<replaceable>arch</replaceable></filename>, with <emphasis>arch</emphasis> being for example <emphasis remap=tt>i386</emphasis>.</para>
|
||||
<filename>/sys/<replaceable>arch</replaceable>/conf/options.<replaceable>arch</replaceable></filename>, with <emphasis>arch</emphasis> being for example <filename>i386</filename>.</para>
|
||||
|
||||
|
||||
<sect2>
|
||||
|
@ -4750,7 +4750,7 @@
|
|||
<informalexample>
|
||||
<screen># sh MAKEDEV wcd0</screen>
|
||||
</informalexample> When this script finishes, you will find that
|
||||
there are now <emphasis remap=tt>wcd0c</emphasis> and <emphasis
|
||||
there are now <filename>wcd0c</filename> and <emphasis
|
||||
remap=tt>rwcd0c</emphasis> entries in <filename>/dev</filename> so
|
||||
you know that it executed correctly.</para>
|
||||
|
||||
|
@ -4926,7 +4926,7 @@
|
|||
non-regulated password scrambler, and then provide as a separate
|
||||
add-on library the DES-based password hash. The password-scrambling
|
||||
function was moved out of the C library to a separate library,
|
||||
called `<emphasis remap=tt>libcrypt</emphasis>' because the name of
|
||||
called `<filename>libcrypt</filename>' because the name of
|
||||
the C function to implement it is `<emphasis
|
||||
remap=tt>crypt</emphasis>'. In FreeBSD 1.x and some pre-release
|
||||
2.0 snapshots, the non-regulated scrambler uses an insecure function
|
||||
|
@ -5531,7 +5531,7 @@
|
|||
</para>
|
||||
|
||||
<para>Now, this command only generates a temporary file which must
|
||||
be renamed to <emphasis remap=tt>srvtab</emphasis> so that all the
|
||||
be renamed to <filename>srvtab</filename> so that all the
|
||||
server can pick it up. Use the <emphasis remap=tt>mv</emphasis>
|
||||
command to move it into place on the original system:</para>
|
||||
|
||||
|
@ -5545,7 +5545,7 @@
|
|||
deemed safe, then copy the <emphasis
|
||||
remap=tt><client>-new-srvtab</emphasis> to removable media
|
||||
and transport it by secure physical means. Be sure to rename it to
|
||||
<emphasis remap=tt>srvtab</emphasis> in the client's
|
||||
<filename>srvtab</filename> in the client's
|
||||
<filename>/etc/kerberosIV</filename> directory, and make sure it
|
||||
is mode 600:</para>
|
||||
|
||||
|
@ -18117,7 +18117,7 @@
|
|||
in <filename>/usr/src/share/doc/smm</filename>] and <quote>FreeBSD
|
||||
Configuration Options</quote> [in <filename>/sys/conf/options</filename>
|
||||
and in
|
||||
<filename>/sys/<replaceable>arch</replaceable>/conf/options.<replaceable>arch</replaceable></filename>, with <emphasis>arch</emphasis> for example being <emphasis remap=tt>i386</emphasis>] for more information on configuring and building kernels. You may have to unpack the kernel source distribution if have not installed the system sources already (<filename>srcdist/srcsys.??</filename> in FreeBSD 1.1, <filename>srcdist/sys.??</filename> in FreeBSD 1.1.5.1, or the entire source distribution in FreeBSD 2.0) to be able to configure and build kernels.</para>
|
||||
<filename>/sys/<replaceable>arch</replaceable>/conf/options.<replaceable>arch</replaceable></filename>, with <emphasis>arch</emphasis> for example being <filename>i386</filename>] for more information on configuring and building kernels. You may have to unpack the kernel source distribution if have not installed the system sources already (<filename>srcdist/srcsys.??</filename> in FreeBSD 1.1, <filename>srcdist/sys.??</filename> in FreeBSD 1.1.5.1, or the entire source distribution in FreeBSD 2.0) to be able to configure and build kernels.</para>
|
||||
|
||||
<para>Create a kernel configuration file for your system (if you
|
||||
have not already) by <emphasis remap=tt>cd</emphasis>ing to
|
||||
|
@ -18326,7 +18326,7 @@
|
|||
wish to use for your modem. If you have a 2400 bps modem, you
|
||||
can probably use the existing <emphasis
|
||||
remap=tt>D2400</emphasis> entry. This entry already exists
|
||||
in the FreeBSD 1.1.5.1 <emphasis remap=tt>gettytab</emphasis>
|
||||
in the FreeBSD 1.1.5.1 <filename>gettytab</filename>
|
||||
file, so you do not need to add it unless it is missing under
|
||||
your version of FreeBSD:</para>
|
||||
|
||||
|
@ -18378,7 +18378,7 @@
|
|||
<para>If you have a 28.8 Kbps modem and/or you want to take
|
||||
advantage of compression on a 14.4 Kbps modem, you need to use
|
||||
a higher communications rate than 19.2 Kbps. Here is an
|
||||
example of a <emphasis remap=tt>gettytab</emphasis> entry
|
||||
example of a <filename>gettytab</filename> entry
|
||||
starting a 57.6 Kbps:</para>
|
||||
|
||||
<para>
|
||||
|
@ -20420,7 +20420,7 @@
|
|||
|
||||
<listitem>
|
||||
<para>Update your <filename>/etc/rc.conf</filename> (or
|
||||
<emphasis remap=tt>sysconfig</emphasis>) file.</para>
|
||||
<filename>sysconfig</filename>) file.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -20468,7 +20468,7 @@
|
|||
|
||||
<listitem>
|
||||
<para>Update your <filename>/etc/rc.conf</filename> (or
|
||||
<emphasis remap=tt>sysconfig</emphasis>) file.</para>
|
||||
<filename>sysconfig</filename>) file.</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
@ -26250,7 +26250,7 @@
|
|||
<sect4>
|
||||
<title>Writing the <filename>Makefile</filename></title>
|
||||
|
||||
<para>The minimal <emphasis remap=tt>Makefile</emphasis> would
|
||||
<para>The minimal <filename>Makefile</filename> would
|
||||
look something like this:</para>
|
||||
|
||||
<para>
|
||||
|
@ -26388,7 +26388,7 @@
|
|||
everybody else happy about it too. To accomplish this, pack
|
||||
the necessary files (everything described in this section --
|
||||
in particular do <emphasis>not</emphasis> include the original
|
||||
source tarball, the `<emphasis remap=tt>work</emphasis>'
|
||||
source tarball, the `<filename>work</filename>'
|
||||
subdirectory or the package) into a
|
||||
<filename>.tar.gz</filename> file, stick it in the directory
|
||||
<informalexample>
|
||||
|
@ -26449,7 +26449,7 @@
|
|||
remap=tt>${DISTDIR}</emphasis> (typically a gzip'd
|
||||
tarball) and unpacks it into a temporary subdirectory
|
||||
specified by <emphasis remap=tt>${WRKDIR}</emphasis>
|
||||
(defaults to <emphasis remap=tt>work</emphasis>).
|
||||
(defaults to <filename>work</filename>).
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -26518,7 +26518,7 @@
|
|||
define targets `<emphasis
|
||||
remap=tt>pre-<something></emphasis>' or `<emphasis
|
||||
remap=tt>post-<something></emphasis>', or put scripts
|
||||
with those names, in the <emphasis remap=tt>scripts</emphasis>
|
||||
with those names, in the <filename>scripts</filename>
|
||||
subdirectory, and they will be run before or after the default
|
||||
actions are done.</para>
|
||||
|
||||
|
@ -27209,7 +27209,7 @@
|
|||
<filename>Makefile</filename>s don't include correct
|
||||
dependencies for info files. In emacs' case, I had to
|
||||
patch the main <filename>Makefile.in</filename> so it will
|
||||
descend into the <emphasis remap=tt>man</emphasis>
|
||||
descend into the <filename>man</filename>
|
||||
subdirectory to rebuild the info pages.
|
||||
|
||||
<informalexample>
|
||||
|
@ -27247,7 +27247,7 @@
|
|||
<listitem>
|
||||
<para>If there is a place in the
|
||||
<filename>Makefile</filename> that is installing the
|
||||
<emphasis remap=tt>dir</emphasis> file, delete it. Your
|
||||
<filename>dir</filename> file, delete it. Your
|
||||
port may not be doing it. Also, remove any commands that
|
||||
are otherwise mucking around with the
|
||||
<filename>dir</filename> file.
|
||||
|
@ -34350,7 +34350,7 @@
|
|||
it is kept up-to-date by CTM. That means if you CVSup <emphasis
|
||||
remap=tt>cvs-all</emphasis> with <literal>release=cvs</literal>
|
||||
from this site, you get a version of the repository (including the
|
||||
inevitable <emphasis remap=tt>.ctm_status</emphasis> file) which is
|
||||
inevitable <filename>.ctm_status</filename> file) which is
|
||||
suitable for being updated using the CTM <emphasis
|
||||
remap=tt>cvs-cur</emphasis> deltas. This allows users who track
|
||||
the entire <emphasis remap=tt>cvs-all</emphasis> tree to go from
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue