os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Replace the last few occurences of curly quoted items (`` and '')

Browse source 
with the right markup.
This commit is contained in:
Nik Clayton 1998-06-29 09:48:32 +00:00
parent f4e931897c
commit b91811480c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=3012
4 changed files with 132 additions and 129 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
en/handbook/README
View file

@ -281,3 +281,6 @@ for example,
markup is correct now, which makes searching for markup that does
need changing much easier.
21. Replace the last few occurences of curly quoted items (`` and '')
with the right markup.

86
en/handbook/handbook.sgml
View file

@ -2502,8 +2502,8 @@
examination of how Makefiles work; suffice it to say that the line
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
space. The original port did not provide an <maketarget>install</maketarget> target,
so the three lines from <maketarget>do-install</maketarget> ensure that the files
produced by this port are placed in the correct
destination.</para>
@ -4012,7 +4012,7 @@
<para>
<variablelist>
<varlistentry><term>device sc0 at isa? port ``IO_KBD' tty irq 1
<varlistentry><term>device sc0 at isa? port "IO_KBD" tty irq 1
vector scintr</term>
<listitem>
<para><emphasis remap=tt>sc0</emphasis> is the default
@ -9371,7 +9371,7 @@
performs two-way communication with the printer. It updates the
printer's status file with verbose information from the printer,
so users and administrators can see exactly what the state of
the printer is (such as ``toner low'' or ``paper jam''). But
the printer is (such as <errorname>toner low</errorname> or <errorname>paper jam</errorname>). But
more importantly, it includes a program called <command>psif</command> which detects whether the incoming
job is plain text and calls <command>textps</command>
(another program that comes with <command>lprps</command>) to convert it to PostScript. It
@ -18918,8 +18918,8 @@
</para>
<para>Or use cu as root with the following command: <literallayout>
cu -l``line'' -s``speed'' </literallayout> with line being the
serial port (e.g.<filename>/dev/cuaa0</filename>) and speed being
cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable> </literallayout> with <replaceable>line</replaceable> being the
serial port (e.g.<filename>/dev/cuaa0</filename>) and <replaceable>speed</replaceable> being
the speed (e.g.<emphasis remap=tt>57600</emphasis>). When you are
done entering the AT commands hit <command>~.</command>
to exit.</para>
@ -19052,7 +19052,7 @@
<para>You must have pressed CTRL+A, <command>tip</command>'s <quote>raise character,</quote> specially
designed for people with broken caps-lock keys. Use <command>~s</command> as above and set the variable
``raisechar'' to something reasonable. In fact, you can set it to
<literal>raisechar</literal> to something reasonable. In fact, you can set it to
the same as the force character, if you never expect to use either
of these features.</para>
@ -19208,7 +19208,7 @@
<sect2>
<title>Building a ppp ready kernel</title>
<para>As the description states, ``ppp'' uses the kernel ``tun''
<para>As the description states, <command>ppp</command> uses the kernel <devicename>tun</devicename>
device. It is necessary to make sure that your kernel has support
for this device compiled in.</para>
@ -19231,8 +19231,8 @@
<para>If your kernel configuration file does not have this line in
it, or you need to configure more than one tun device (for
example, if you are setting up a server and could have 16 dialup
ppp connections at any one time then you will need to use ``16''
instead of ``1''), then you should add the line, re-compile,
ppp connections at any one time then you will need to use <literal>16</literal>
instead of <literal>1</literal>), then you should add the line, re-compile,
re-install and boot the new kernel. Please refer to the
<xref linkend="kernelconfig" remap="Configuring the FreeBSD
Kernel"> section for more information on kernel
@ -19271,13 +19271,13 @@
<sect2>
<title>Check the tun device</title>
<para>Most users will only require one ``tun'' device (tun0). If you
have used more (i.e., a number other than `1' in the pseudo-device
<para>Most users will only require one <devicename>tun</devicename> device (<filename>/dev/tun0</filename>). If you
have used more (i.e., a number other than <literal>1</literal> in the pseudo-device
line in the kernel configuration file) then alter all references
to ``tun0'' below to reflect whichever device number you are
to <devicename>tun0</devicename> below to reflect whichever device number you are
using.</para>
<para>The easiest way to make sure that the tun0 device is
<para>The easiest way to make sure that the <devicename>tun0</devicename> device is
configured correctly is to re-make it. To do this, execute the
following commands:</para>
@ -19390,8 +19390,8 @@
<para>The <emphasis remap="tt">x.x.x.x</emphasis> and <emphasis
remap="tt">y.y.y.y</emphasis> addresses are those given to you
by your ISP. Add as many ``nameserver'' lines as your ISP
provides. The ``domain'' line defaults to your hostname's
by your ISP. Add as many <literal>nameserver</literal> lines as your ISP
provides. The <literal>domain</literal> line defaults to your hostname's
domain, and is probably unnecessary. Refer to the resolv.conf
manual page for details of other possible entries in this
file.</para>
@ -19426,7 +19426,7 @@
to the example below.</para>
<note>
<para>Lines that end in a ``:'' start in the first column, all
<para>Lines that end in a <token>:</token> start in the first column, all
other lines should be indented as shown using spaces or
tabs.</para>
</note>
@ -19493,13 +19493,13 @@
<listitem>
<para>Sets the phone number for this provider. Multiple
phone numbers may be specified using the ``:'' or ``|''
phone numbers may be specified using the <token>:</token> or <token>|</token>
character as a separator. The difference between these
spearators is described in the ppp manual page. To
summarize, if you want to rotate through the numbers,
use the ``:''. If you want to always attempt to dial
use the <token>:</token>. If you want to always attempt to dial
the first number first and only use the other numbers if
the first number fails, use the ``|''. Always quote the
the first number fails, use the <token>|</token>. Always quote the
entire set of phone numbers as shown.</para>
</listitem>
</varlistentry>
@ -19643,7 +19643,7 @@
<variablelist>
<varlistentry><term>Line 10:</term>
<listitem>
<para>The number after the ``/'' character is the number
<para>The number after the <token>/</token> character is the number
of bits of the address that ppp will insist on. You may
wish to use IP numbers more appropriate to your
circumstances, but the above example will almost always
@ -20188,7 +20188,7 @@
<filename>/etc/sysconfig</filename>).</para>
<para>Working from the top down in this file, make sure the
``hostname='' line is set, e.g.:</para>
<literal>hostname=</literal> line is set, e.g.:</para>
<para>
<informalexample>
@ -20228,7 +20228,7 @@
for further details.</para>
</note>
<para>Set the router program to ``NO'' with the line</para>
<para>Set the router program to <literal>NO</literal> with the line</para>
<para>
<informalexample>
@ -20242,7 +20242,7 @@
table entries created by ppp.</para>
<para>It is probably worth your while ensuring that the
``sendmail_flags'' line does not include the ``-q'' option,
<literal>sendmail_flags</literal> line does not include the <option>-q</option> option,
otherwise sendmail will attempt to do a network lookup every now
and then, possibly causing your machine to dial out. You may
try:</para>
@ -20367,7 +20367,7 @@
<listitem>
<para>Create a profile in this users home directory that runs
``ppp -direct direct-server'' or similar.</para>
<command>ppp -direct direct-server</command> or similar.</para>
</listitem>
<listitem>
@ -21100,7 +21100,7 @@
two SLIP interfaces built into the kernel. (The asterisks after
the <emphasis remap=tt>sl0</emphasis> and <emphasis
remap=tt>sl1</emphasis> indicate that the interfaces are
``down''.)</para>
<quote>down</quote>.)</para>
<para>However, FreeBSD's default kernels do not come configured to
forward packets (ie, your FreeBSD machine will not act as a
@ -22824,7 +22824,7 @@
next line handles mail to the local Ethernet domain that can be
delivered using SMTP. Finally, the UUCP neighbors are mentioned
in the .UUCP pseudo-domain notation, to allow for a
``uucp-neighbor!recipient'' override of the default rules. The
<literal>uucp-neighbor!recipient</literal> override of the default rules. The
last line is always a single dot, matching everything else, with
UUCP delivery to a UUCP neighbor that serves as your universal
mail gateway to the world. All of the node names behind the
@ -22841,7 +22841,7 @@
<para>Final hint: if you are uncertain whether some particular mail
routing would work, remember the <option>-bt</option> option to
sendmail. It starts sendmail in <emphasis>address test
mode</emphasis>; simply enter ``0 '', followed by the address
mode</emphasis>; simply enter <token>0</token>, followed by the address
you wish to test for the mail routing. The last line tells you
the used internal mail agent, the destination host this agent will
be called with, and the (possibly translated) address. Leave this
@ -22908,7 +22908,7 @@
</sect2>
<sect2>
<title>Sendmail says ``mail loops back to myself''</title>
<title>Sendmail says <errorname>mail loops back to myself</errorname></title>
<para>This is answered in the sendmail FAQ as follows:-
<literallayout> * I am getting "Local configuration
@ -22948,7 +22948,7 @@
</para>
<para>Only one host should be specified as the final recipient ( add
``Cw bigco.com'' in <filename>/etc/sendmail.cf</filename> on
<literal>Cw bigco.com</literal> in <filename>/etc/sendmail.cf</filename> on
bigco.com).</para>
<para>When the senders sendmail is trying to deliver the mail it
@ -23475,12 +23475,12 @@
<para>If you may wish to get your deltas via email:</para>
<para>Send email to &a.majordomo; to subscribe to one of the
<application>CTM</application> distribution lists. ``ctm-cvs-cur''
supports the entire cvs tree. ``ctm-src-cur'' supports the head
of the development branch. ``ctm-src-2_2'' supports the 2.2
<application>CTM</application> distribution lists. <quote>ctm-cvs-cur</quote>
supports the entire cvs tree. <quote>ctm-src-cur</quote> supports the head
of the development branch. <quote>ctm-src-2_2</quote> supports the 2.2
release branch, etc. (If you do not know how to subscribe
yourself using majordomo, send a message first containing the
word ``help'' - it will send you back usage
word <literal>help</literal> - it will send you back usage
instructions.)</para>
<para>When you begin receiving your <application>CTM</application> updates
@ -30536,7 +30536,7 @@
<para>Stick to version numbers of the form major.minor (x.y). Our
dynamic linker does not handle version numbers of the form x.y.z
well. Any version number after the ``y'' (ie. the third digit) is
well. Any version number after the <quote>y</quote> (ie. the third digit) is
totally ignored when comparing shared lib version numbers to decide
which library to link with. Given two shared libraries that differ
only in the `micro' revision, ld.so will link with the higher one.
@ -30904,7 +30904,7 @@
have a new core dump handy &lt;g&gt;, my kernel has not
panicked for a rather long time.) From looking at the code
in source line 403, there is a high probability that either
the pointer access for ``tp'' was messed up, or the array
the pointer access for <quote>tp</quote> was messed up, or the array
access was out of bounds.</para>
</listitem>
@ -31401,8 +31401,8 @@
<sect2>
<title>Installing Linux Emulation in 2.2.2-RELEASE and later</title>
<para>It is no longer necessary to specify ``options LINUX'' or
``options COMPAT_LINUX''. Linux emulation is done with an LKM
<para>It is no longer necessary to specify <literal>options LINUX</literal> or
<literal>options COMPAT_LINUX</literal>. Linux emulation is done with an LKM
(<quote>Loadable Kernel Module</quote>) so it can be installed on the fly
without having to reboot. You will need the following things in
your startup files, however:
@ -31828,8 +31828,8 @@
<para>So, in this case, you will need the packages ldso, shlibs,
xf_lib and oldlibs. In each of the contents-files for these
packages, look for a line saying ``PACKAGE LOCATION'', it will
tell you on which `disk' the package is, in our case it will tell
packages, look for a line saying <literal>PACKAGE LOCATION</literal>, it will
tell you on which <quote>disk</quote> the package is, in our case it will tell
us in which subdirectory we need to look. For our example, we
would find the following locations:
<table>
@ -31847,7 +31847,7 @@
</table>
</para>
<para>The locations called ``diskXX'' refer to the ``slakware/XX''
<para>The locations called <quote>disk<replaceable>XX</replaceable></quote> refer to the <filename>slakware/<replaceable>XX</replaceable></filename>
subdirectories of the distribution, others may be found in the
<filename>contrib</filename> subdirectory. In this case, we
could now retrieve the packages we need by retrieving the
@ -32135,7 +32135,7 @@
<listitem>
<para>While this is technically possible, it is not
particular useful because of the ``FAT'' filesystem's
particular useful because of the <acronym>FAT</acronym> filesystem's
inability to deal with links, device nodes and other such
<quote>UNIXisms</quote>.</para>
</listitem>
@ -35143,7 +35143,7 @@
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running ``stable''
be taken to remain -stable. Anyone running <quote>stable</quote>
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>

86
en_US.ISO8859-1/books/handbook/book.sgml
View file

@ -2502,8 +2502,8 @@
examination of how Makefiles work; suffice it to say that the line
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
space. The original port did not provide an <maketarget>install</maketarget> target,
so the three lines from <maketarget>do-install</maketarget> ensure that the files
produced by this port are placed in the correct
destination.</para>
@ -4012,7 +4012,7 @@
<para>
<variablelist>
<varlistentry><term>device sc0 at isa? port ``IO_KBD' tty irq 1
<varlistentry><term>device sc0 at isa? port "IO_KBD" tty irq 1
vector scintr</term>
<listitem>
<para><emphasis remap=tt>sc0</emphasis> is the default
@ -9371,7 +9371,7 @@
performs two-way communication with the printer. It updates the
printer's status file with verbose information from the printer,
so users and administrators can see exactly what the state of
the printer is (such as ``toner low'' or ``paper jam''). But
the printer is (such as <errorname>toner low</errorname> or <errorname>paper jam</errorname>). But
more importantly, it includes a program called <command>psif</command> which detects whether the incoming
job is plain text and calls <command>textps</command>
(another program that comes with <command>lprps</command>) to convert it to PostScript. It
@ -18918,8 +18918,8 @@
</para>
<para>Or use cu as root with the following command: <literallayout>
cu -l``line'' -s``speed'' </literallayout> with line being the
serial port (e.g.<filename>/dev/cuaa0</filename>) and speed being
cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable> </literallayout> with <replaceable>line</replaceable> being the
serial port (e.g.<filename>/dev/cuaa0</filename>) and <replaceable>speed</replaceable> being
the speed (e.g.<emphasis remap=tt>57600</emphasis>). When you are
done entering the AT commands hit <command>~.</command>
to exit.</para>
@ -19052,7 +19052,7 @@
<para>You must have pressed CTRL+A, <command>tip</command>'s <quote>raise character,</quote> specially
designed for people with broken caps-lock keys. Use <command>~s</command> as above and set the variable
``raisechar'' to something reasonable. In fact, you can set it to
<literal>raisechar</literal> to something reasonable. In fact, you can set it to
the same as the force character, if you never expect to use either
of these features.</para>
@ -19208,7 +19208,7 @@
<sect2>
<title>Building a ppp ready kernel</title>
<para>As the description states, ``ppp'' uses the kernel ``tun''
<para>As the description states, <command>ppp</command> uses the kernel <devicename>tun</devicename>
device. It is necessary to make sure that your kernel has support
for this device compiled in.</para>
@ -19231,8 +19231,8 @@
<para>If your kernel configuration file does not have this line in
it, or you need to configure more than one tun device (for
example, if you are setting up a server and could have 16 dialup
ppp connections at any one time then you will need to use ``16''
instead of ``1''), then you should add the line, re-compile,
ppp connections at any one time then you will need to use <literal>16</literal>
instead of <literal>1</literal>), then you should add the line, re-compile,
re-install and boot the new kernel. Please refer to the
<xref linkend="kernelconfig" remap="Configuring the FreeBSD
Kernel"> section for more information on kernel
@ -19271,13 +19271,13 @@
<sect2>
<title>Check the tun device</title>
<para>Most users will only require one ``tun'' device (tun0). If you
have used more (i.e., a number other than `1' in the pseudo-device
<para>Most users will only require one <devicename>tun</devicename> device (<filename>/dev/tun0</filename>). If you
have used more (i.e., a number other than <literal>1</literal> in the pseudo-device
line in the kernel configuration file) then alter all references
to ``tun0'' below to reflect whichever device number you are
to <devicename>tun0</devicename> below to reflect whichever device number you are
using.</para>
<para>The easiest way to make sure that the tun0 device is
<para>The easiest way to make sure that the <devicename>tun0</devicename> device is
configured correctly is to re-make it. To do this, execute the
following commands:</para>
@ -19390,8 +19390,8 @@
<para>The <emphasis remap="tt">x.x.x.x</emphasis> and <emphasis
remap="tt">y.y.y.y</emphasis> addresses are those given to you
by your ISP. Add as many ``nameserver'' lines as your ISP
provides. The ``domain'' line defaults to your hostname's
by your ISP. Add as many <literal>nameserver</literal> lines as your ISP
provides. The <literal>domain</literal> line defaults to your hostname's
domain, and is probably unnecessary. Refer to the resolv.conf
manual page for details of other possible entries in this
file.</para>
@ -19426,7 +19426,7 @@
to the example below.</para>
<note>
<para>Lines that end in a ``:'' start in the first column, all
<para>Lines that end in a <token>:</token> start in the first column, all
other lines should be indented as shown using spaces or
tabs.</para>
</note>
@ -19493,13 +19493,13 @@
<listitem>
<para>Sets the phone number for this provider. Multiple
phone numbers may be specified using the ``:'' or ``|''
phone numbers may be specified using the <token>:</token> or <token>|</token>
character as a separator. The difference between these
spearators is described in the ppp manual page. To
summarize, if you want to rotate through the numbers,
use the ``:''. If you want to always attempt to dial
use the <token>:</token>. If you want to always attempt to dial
the first number first and only use the other numbers if
the first number fails, use the ``|''. Always quote the
the first number fails, use the <token>|</token>. Always quote the
entire set of phone numbers as shown.</para>
</listitem>
</varlistentry>
@ -19643,7 +19643,7 @@
<variablelist>
<varlistentry><term>Line 10:</term>
<listitem>
<para>The number after the ``/'' character is the number
<para>The number after the <token>/</token> character is the number
of bits of the address that ppp will insist on. You may
wish to use IP numbers more appropriate to your
circumstances, but the above example will almost always
@ -20188,7 +20188,7 @@
<filename>/etc/sysconfig</filename>).</para>
<para>Working from the top down in this file, make sure the
``hostname='' line is set, e.g.:</para>
<literal>hostname=</literal> line is set, e.g.:</para>
<para>
<informalexample>
@ -20228,7 +20228,7 @@
for further details.</para>
</note>
<para>Set the router program to ``NO'' with the line</para>
<para>Set the router program to <literal>NO</literal> with the line</para>
<para>
<informalexample>
@ -20242,7 +20242,7 @@
table entries created by ppp.</para>
<para>It is probably worth your while ensuring that the
``sendmail_flags'' line does not include the ``-q'' option,
<literal>sendmail_flags</literal> line does not include the <option>-q</option> option,
otherwise sendmail will attempt to do a network lookup every now
and then, possibly causing your machine to dial out. You may
try:</para>
@ -20367,7 +20367,7 @@
<listitem>
<para>Create a profile in this users home directory that runs
``ppp -direct direct-server'' or similar.</para>
<command>ppp -direct direct-server</command> or similar.</para>
</listitem>
<listitem>
@ -21100,7 +21100,7 @@
two SLIP interfaces built into the kernel. (The asterisks after
the <emphasis remap=tt>sl0</emphasis> and <emphasis
remap=tt>sl1</emphasis> indicate that the interfaces are
``down''.)</para>
<quote>down</quote>.)</para>
<para>However, FreeBSD's default kernels do not come configured to
forward packets (ie, your FreeBSD machine will not act as a
@ -22824,7 +22824,7 @@
next line handles mail to the local Ethernet domain that can be
delivered using SMTP. Finally, the UUCP neighbors are mentioned
in the .UUCP pseudo-domain notation, to allow for a
``uucp-neighbor!recipient'' override of the default rules. The
<literal>uucp-neighbor!recipient</literal> override of the default rules. The
last line is always a single dot, matching everything else, with
UUCP delivery to a UUCP neighbor that serves as your universal
mail gateway to the world. All of the node names behind the
@ -22841,7 +22841,7 @@
<para>Final hint: if you are uncertain whether some particular mail
routing would work, remember the <option>-bt</option> option to
sendmail. It starts sendmail in <emphasis>address test
mode</emphasis>; simply enter ``0 '', followed by the address
mode</emphasis>; simply enter <token>0</token>, followed by the address
you wish to test for the mail routing. The last line tells you
the used internal mail agent, the destination host this agent will
be called with, and the (possibly translated) address. Leave this
@ -22908,7 +22908,7 @@
</sect2>
<sect2>
<title>Sendmail says ``mail loops back to myself''</title>
<title>Sendmail says <errorname>mail loops back to myself</errorname></title>
<para>This is answered in the sendmail FAQ as follows:-
<literallayout> * I am getting "Local configuration
@ -22948,7 +22948,7 @@
</para>
<para>Only one host should be specified as the final recipient ( add
``Cw bigco.com'' in <filename>/etc/sendmail.cf</filename> on
<literal>Cw bigco.com</literal> in <filename>/etc/sendmail.cf</filename> on
bigco.com).</para>
<para>When the senders sendmail is trying to deliver the mail it
@ -23475,12 +23475,12 @@
<para>If you may wish to get your deltas via email:</para>
<para>Send email to &a.majordomo; to subscribe to one of the
<application>CTM</application> distribution lists. ``ctm-cvs-cur''
supports the entire cvs tree. ``ctm-src-cur'' supports the head
of the development branch. ``ctm-src-2_2'' supports the 2.2
<application>CTM</application> distribution lists. <quote>ctm-cvs-cur</quote>
supports the entire cvs tree. <quote>ctm-src-cur</quote> supports the head
of the development branch. <quote>ctm-src-2_2</quote> supports the 2.2
release branch, etc. (If you do not know how to subscribe
yourself using majordomo, send a message first containing the
word ``help'' - it will send you back usage
word <literal>help</literal> - it will send you back usage
instructions.)</para>
<para>When you begin receiving your <application>CTM</application> updates
@ -30536,7 +30536,7 @@
<para>Stick to version numbers of the form major.minor (x.y). Our
dynamic linker does not handle version numbers of the form x.y.z
well. Any version number after the ``y'' (ie. the third digit) is
well. Any version number after the <quote>y</quote> (ie. the third digit) is
totally ignored when comparing shared lib version numbers to decide
which library to link with. Given two shared libraries that differ
only in the `micro' revision, ld.so will link with the higher one.
@ -30904,7 +30904,7 @@
have a new core dump handy &lt;g&gt;, my kernel has not
panicked for a rather long time.) From looking at the code
in source line 403, there is a high probability that either
the pointer access for ``tp'' was messed up, or the array
the pointer access for <quote>tp</quote> was messed up, or the array
access was out of bounds.</para>
</listitem>
@ -31401,8 +31401,8 @@
<sect2>
<title>Installing Linux Emulation in 2.2.2-RELEASE and later</title>
<para>It is no longer necessary to specify ``options LINUX'' or
``options COMPAT_LINUX''. Linux emulation is done with an LKM
<para>It is no longer necessary to specify <literal>options LINUX</literal> or
<literal>options COMPAT_LINUX</literal>. Linux emulation is done with an LKM
(<quote>Loadable Kernel Module</quote>) so it can be installed on the fly
without having to reboot. You will need the following things in
your startup files, however:
@ -31828,8 +31828,8 @@
<para>So, in this case, you will need the packages ldso, shlibs,
xf_lib and oldlibs. In each of the contents-files for these
packages, look for a line saying ``PACKAGE LOCATION'', it will
tell you on which `disk' the package is, in our case it will tell
packages, look for a line saying <literal>PACKAGE LOCATION</literal>, it will
tell you on which <quote>disk</quote> the package is, in our case it will tell
us in which subdirectory we need to look. For our example, we
would find the following locations:
<table>
@ -31847,7 +31847,7 @@
</table>
</para>
<para>The locations called ``diskXX'' refer to the ``slakware/XX''
<para>The locations called <quote>disk<replaceable>XX</replaceable></quote> refer to the <filename>slakware/<replaceable>XX</replaceable></filename>
subdirectories of the distribution, others may be found in the
<filename>contrib</filename> subdirectory. In this case, we
could now retrieve the packages we need by retrieving the
@ -32135,7 +32135,7 @@
<listitem>
<para>While this is technically possible, it is not
particular useful because of the ``FAT'' filesystem's
particular useful because of the <acronym>FAT</acronym> filesystem's
inability to deal with links, device nodes and other such
<quote>UNIXisms</quote>.</para>
</listitem>
@ -35143,7 +35143,7 @@
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running ``stable''
be taken to remain -stable. Anyone running <quote>stable</quote>
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>

86
en_US.ISO_8859-1/books/handbook/book.sgml
View file

@ -2502,8 +2502,8 @@
examination of how Makefiles work; suffice it to say that the line
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
space. The original port did not provide an <maketarget>install</maketarget> target,
so the three lines from <maketarget>do-install</maketarget> ensure that the files
produced by this port are placed in the correct
destination.</para>
@ -4012,7 +4012,7 @@
<para>
<variablelist>
<varlistentry><term>device sc0 at isa? port ``IO_KBD' tty irq 1
<varlistentry><term>device sc0 at isa? port "IO_KBD" tty irq 1
vector scintr</term>
<listitem>
<para><emphasis remap=tt>sc0</emphasis> is the default
@ -9371,7 +9371,7 @@
performs two-way communication with the printer. It updates the
printer's status file with verbose information from the printer,
so users and administrators can see exactly what the state of
the printer is (such as ``toner low'' or ``paper jam''). But
the printer is (such as <errorname>toner low</errorname> or <errorname>paper jam</errorname>). But
more importantly, it includes a program called <command>psif</command> which detects whether the incoming
job is plain text and calls <command>textps</command>
(another program that comes with <command>lprps</command>) to convert it to PostScript. It
@ -18918,8 +18918,8 @@
</para>
<para>Or use cu as root with the following command: <literallayout>
cu -l``line'' -s``speed'' </literallayout> with line being the
serial port (e.g.<filename>/dev/cuaa0</filename>) and speed being
cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable> </literallayout> with <replaceable>line</replaceable> being the
serial port (e.g.<filename>/dev/cuaa0</filename>) and <replaceable>speed</replaceable> being
the speed (e.g.<emphasis remap=tt>57600</emphasis>). When you are
done entering the AT commands hit <command>~.</command>
to exit.</para>
@ -19052,7 +19052,7 @@
<para>You must have pressed CTRL+A, <command>tip</command>'s <quote>raise character,</quote> specially
designed for people with broken caps-lock keys. Use <command>~s</command> as above and set the variable
``raisechar'' to something reasonable. In fact, you can set it to
<literal>raisechar</literal> to something reasonable. In fact, you can set it to
the same as the force character, if you never expect to use either
of these features.</para>
@ -19208,7 +19208,7 @@
<sect2>
<title>Building a ppp ready kernel</title>
<para>As the description states, ``ppp'' uses the kernel ``tun''
<para>As the description states, <command>ppp</command> uses the kernel <devicename>tun</devicename>
device. It is necessary to make sure that your kernel has support
for this device compiled in.</para>
@ -19231,8 +19231,8 @@
<para>If your kernel configuration file does not have this line in
it, or you need to configure more than one tun device (for
example, if you are setting up a server and could have 16 dialup
ppp connections at any one time then you will need to use ``16''
instead of ``1''), then you should add the line, re-compile,
ppp connections at any one time then you will need to use <literal>16</literal>
instead of <literal>1</literal>), then you should add the line, re-compile,
re-install and boot the new kernel. Please refer to the
<xref linkend="kernelconfig" remap="Configuring the FreeBSD
Kernel"> section for more information on kernel
@ -19271,13 +19271,13 @@
<sect2>
<title>Check the tun device</title>
<para>Most users will only require one ``tun'' device (tun0). If you
have used more (i.e., a number other than `1' in the pseudo-device
<para>Most users will only require one <devicename>tun</devicename> device (<filename>/dev/tun0</filename>). If you
have used more (i.e., a number other than <literal>1</literal> in the pseudo-device
line in the kernel configuration file) then alter all references
to ``tun0'' below to reflect whichever device number you are
to <devicename>tun0</devicename> below to reflect whichever device number you are
using.</para>
<para>The easiest way to make sure that the tun0 device is
<para>The easiest way to make sure that the <devicename>tun0</devicename> device is
configured correctly is to re-make it. To do this, execute the
following commands:</para>
@ -19390,8 +19390,8 @@
<para>The <emphasis remap="tt">x.x.x.x</emphasis> and <emphasis
remap="tt">y.y.y.y</emphasis> addresses are those given to you
by your ISP. Add as many ``nameserver'' lines as your ISP
provides. The ``domain'' line defaults to your hostname's
by your ISP. Add as many <literal>nameserver</literal> lines as your ISP
provides. The <literal>domain</literal> line defaults to your hostname's
domain, and is probably unnecessary. Refer to the resolv.conf
manual page for details of other possible entries in this
file.</para>
@ -19426,7 +19426,7 @@
to the example below.</para>
<note>
<para>Lines that end in a ``:'' start in the first column, all
<para>Lines that end in a <token>:</token> start in the first column, all
other lines should be indented as shown using spaces or
tabs.</para>
</note>
@ -19493,13 +19493,13 @@
<listitem>
<para>Sets the phone number for this provider. Multiple
phone numbers may be specified using the ``:'' or ``|''
phone numbers may be specified using the <token>:</token> or <token>|</token>
character as a separator. The difference between these
spearators is described in the ppp manual page. To
summarize, if you want to rotate through the numbers,
use the ``:''. If you want to always attempt to dial
use the <token>:</token>. If you want to always attempt to dial
the first number first and only use the other numbers if
the first number fails, use the ``|''. Always quote the
the first number fails, use the <token>|</token>. Always quote the
entire set of phone numbers as shown.</para>
</listitem>
</varlistentry>
@ -19643,7 +19643,7 @@
<variablelist>
<varlistentry><term>Line 10:</term>
<listitem>
<para>The number after the ``/'' character is the number
<para>The number after the <token>/</token> character is the number
of bits of the address that ppp will insist on. You may
wish to use IP numbers more appropriate to your
circumstances, but the above example will almost always
@ -20188,7 +20188,7 @@
<filename>/etc/sysconfig</filename>).</para>
<para>Working from the top down in this file, make sure the
``hostname='' line is set, e.g.:</para>
<literal>hostname=</literal> line is set, e.g.:</para>
<para>
<informalexample>
@ -20228,7 +20228,7 @@
for further details.</para>
</note>
<para>Set the router program to ``NO'' with the line</para>
<para>Set the router program to <literal>NO</literal> with the line</para>
<para>
<informalexample>
@ -20242,7 +20242,7 @@
table entries created by ppp.</para>
<para>It is probably worth your while ensuring that the
``sendmail_flags'' line does not include the ``-q'' option,
<literal>sendmail_flags</literal> line does not include the <option>-q</option> option,
otherwise sendmail will attempt to do a network lookup every now
and then, possibly causing your machine to dial out. You may
try:</para>
@ -20367,7 +20367,7 @@
<listitem>
<para>Create a profile in this users home directory that runs
``ppp -direct direct-server'' or similar.</para>
<command>ppp -direct direct-server</command> or similar.</para>
</listitem>
<listitem>
@ -21100,7 +21100,7 @@
two SLIP interfaces built into the kernel. (The asterisks after
the <emphasis remap=tt>sl0</emphasis> and <emphasis
remap=tt>sl1</emphasis> indicate that the interfaces are
``down''.)</para>
<quote>down</quote>.)</para>
<para>However, FreeBSD's default kernels do not come configured to
forward packets (ie, your FreeBSD machine will not act as a
@ -22824,7 +22824,7 @@
next line handles mail to the local Ethernet domain that can be
delivered using SMTP. Finally, the UUCP neighbors are mentioned
in the .UUCP pseudo-domain notation, to allow for a
``uucp-neighbor!recipient'' override of the default rules. The
<literal>uucp-neighbor!recipient</literal> override of the default rules. The
last line is always a single dot, matching everything else, with
UUCP delivery to a UUCP neighbor that serves as your universal
mail gateway to the world. All of the node names behind the
@ -22841,7 +22841,7 @@
<para>Final hint: if you are uncertain whether some particular mail
routing would work, remember the <option>-bt</option> option to
sendmail. It starts sendmail in <emphasis>address test
mode</emphasis>; simply enter ``0 '', followed by the address
mode</emphasis>; simply enter <token>0</token>, followed by the address
you wish to test for the mail routing. The last line tells you
the used internal mail agent, the destination host this agent will
be called with, and the (possibly translated) address. Leave this
@ -22908,7 +22908,7 @@
</sect2>
<sect2>
<title>Sendmail says ``mail loops back to myself''</title>
<title>Sendmail says <errorname>mail loops back to myself</errorname></title>
<para>This is answered in the sendmail FAQ as follows:-
<literallayout> * I am getting "Local configuration
@ -22948,7 +22948,7 @@
</para>
<para>Only one host should be specified as the final recipient ( add
``Cw bigco.com'' in <filename>/etc/sendmail.cf</filename> on
<literal>Cw bigco.com</literal> in <filename>/etc/sendmail.cf</filename> on
bigco.com).</para>
<para>When the senders sendmail is trying to deliver the mail it
@ -23475,12 +23475,12 @@
<para>If you may wish to get your deltas via email:</para>
<para>Send email to &a.majordomo; to subscribe to one of the
<application>CTM</application> distribution lists. ``ctm-cvs-cur''
supports the entire cvs tree. ``ctm-src-cur'' supports the head
of the development branch. ``ctm-src-2_2'' supports the 2.2
<application>CTM</application> distribution lists. <quote>ctm-cvs-cur</quote>
supports the entire cvs tree. <quote>ctm-src-cur</quote> supports the head
of the development branch. <quote>ctm-src-2_2</quote> supports the 2.2
release branch, etc. (If you do not know how to subscribe
yourself using majordomo, send a message first containing the
word ``help'' - it will send you back usage
word <literal>help</literal> - it will send you back usage
instructions.)</para>
<para>When you begin receiving your <application>CTM</application> updates
@ -30536,7 +30536,7 @@
<para>Stick to version numbers of the form major.minor (x.y). Our
dynamic linker does not handle version numbers of the form x.y.z
well. Any version number after the ``y'' (ie. the third digit) is
well. Any version number after the <quote>y</quote> (ie. the third digit) is
totally ignored when comparing shared lib version numbers to decide
which library to link with. Given two shared libraries that differ
only in the `micro' revision, ld.so will link with the higher one.
@ -30904,7 +30904,7 @@
have a new core dump handy &lt;g&gt;, my kernel has not
panicked for a rather long time.) From looking at the code
in source line 403, there is a high probability that either
the pointer access for ``tp'' was messed up, or the array
the pointer access for <quote>tp</quote> was messed up, or the array
access was out of bounds.</para>
</listitem>
@ -31401,8 +31401,8 @@
<sect2>
<title>Installing Linux Emulation in 2.2.2-RELEASE and later</title>
<para>It is no longer necessary to specify ``options LINUX'' or
``options COMPAT_LINUX''. Linux emulation is done with an LKM
<para>It is no longer necessary to specify <literal>options LINUX</literal> or
<literal>options COMPAT_LINUX</literal>. Linux emulation is done with an LKM
(<quote>Loadable Kernel Module</quote>) so it can be installed on the fly
without having to reboot. You will need the following things in
your startup files, however:
@ -31828,8 +31828,8 @@
<para>So, in this case, you will need the packages ldso, shlibs,
xf_lib and oldlibs. In each of the contents-files for these
packages, look for a line saying ``PACKAGE LOCATION'', it will
tell you on which `disk' the package is, in our case it will tell
packages, look for a line saying <literal>PACKAGE LOCATION</literal>, it will
tell you on which <quote>disk</quote> the package is, in our case it will tell
us in which subdirectory we need to look. For our example, we
would find the following locations:
<table>
@ -31847,7 +31847,7 @@
</table>
</para>
<para>The locations called ``diskXX'' refer to the ``slakware/XX''
<para>The locations called <quote>disk<replaceable>XX</replaceable></quote> refer to the <filename>slakware/<replaceable>XX</replaceable></filename>
subdirectories of the distribution, others may be found in the
<filename>contrib</filename> subdirectory. In this case, we
could now retrieve the packages we need by retrieving the
@ -32135,7 +32135,7 @@
<listitem>
<para>While this is technically possible, it is not
particular useful because of the ``FAT'' filesystem's
particular useful because of the <acronym>FAT</acronym> filesystem's
inability to deal with links, device nodes and other such
<quote>UNIXisms</quote>.</para>
</listitem>
@ -35143,7 +35143,7 @@
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running ``stable''
be taken to remain -stable. Anyone running <quote>stable</quote>
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>