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

Examine text marked up as <acronym>, alter markup as appropriate.

Browse source
This commit is contained in:
Nik Clayton 1998-06-19 08:39:18 +00:00
parent 02659c90fd
commit b1405c0516
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=2968
4 changed files with 283 additions and 276 deletions
Download patch file Download diff file Expand all files Collapse all files

7
en/handbook/README
View file

@ -219,4 +219,11 @@ for example,
<note>
<para>The foo file is only used once, and can be deleted.</para>
</note>
13. Look for text marked up as an acronym and alter as necessary. The
automatic conversion tended to mark any string of upper case letters
as acronyms, which is not always right.
The difference between an <acronym> and <abbrev> is subtle -- in a
nutshell, an acronym is pronounceble, and abbreviation isn't.

184
en/handbook/handbook.sgml
View file

@ -1539,7 +1539,7 @@
<para>For as many `DISTS' you wish to install from MS-DOS (and you
have free space for), install each one under
<filename>C:\FREEBSD</filename> - the <acronym>BIN</acronym> dist
<filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist
is only the minimal requirement.</para>
</sect2>
@ -2729,7 +2729,7 @@
into a single file (<filename>.tar</filename>) and optionally
compressed (<filename>.gz</filename>). This technique was
originally used for <emphasis>T</emphasis>ape
<acronym>AR</acronym>chives (hence the name `tar'), but it is
<emphasis>AR</emphasis>chives (hence the name `tar'), but it is
a widely used way of distributing program source code around
the Internet.</para>
@ -3401,7 +3401,7 @@
<para>Since this name is passed to the C compiler as a
<option>-D</option> switch, do not use names like
<acronym>DEBUG</acronym>, or something that could be
<option>DEBUG</option>, or something that could be
confused with another machine or CPU name, like <emphasis
remap=tt>vax</emphasis>.</para>
</listitem>
@ -3785,7 +3785,7 @@
<para><emphasis remap=tt>npx0</emphasis> is the interface to
the floating point math unit in FreeBSD, either the
hardware co-processor or the software math emulator. It
is <acronym>NOT</acronym> optional.</para>
is <emphasis>NOT</emphasis> optional.</para>
</listitem>
</varlistentry>
@ -5789,7 +5789,7 @@
authentication mechanisms.</para>
<para>FreeBSD comes with a kernel packet filter (known as
<acronym>IPFW</acronym>), which is what the rest of this section
<application>IPFW</application>), which is what the rest of this section
will concentrate on. Proxy servers can be built on FreeBSD from
third party software, but there is such a variety of proxy servers
available that it would be impossible to cover them in this
@ -5865,14 +5865,14 @@
<sect2>
<title>What does IPFW allow me to do?</title>
<para><acronym>IPFW</acronym>, the software supplied with FreeBSD,
<para><application>IPFW</application>, the software supplied with FreeBSD,
is a packet filtering and accounting system which resides in the
kernel, and has a user-land control utility,
<command>ipfw(8)</command>. Together, they allow you to define and
query the rules currently used by the kernel in its routing
decisions.</para>
<para>There are two related parts to <acronym>IPFW</acronym>. The
<para>There are two related parts to <application>IPFW</application>. The
firewall section allows you to perform packet filtering. There is
also an IP accounting section which allows you to track usage of
your router, based on similar rules to the firewall section. This
@ -5880,11 +5880,11 @@
getting from a certain machine, or how much WWW (World Wide Web)
traffic it is forwarding.</para>
<para>As a result of the way that <acronym>IPFW</acronym> is
designed, you can use <acronym>IPFW</acronym> on non-router
<para>As a result of the way that <application>IPFW</application> is
designed, you can use <application>IPFW</application> on non-router
machines to perform packet filtering on incoming and outgoing
connections. This is a special case of the more general use of
<acronym>IPFW</acronym>, and the same commands and techniques
<application>IPFW</application>, and the same commands and techniques
should be used in this situation.</para>
</sect2>
@ -5892,7 +5892,7 @@
<sect2>
<title>Enabling IPFW on FreeBSD</title>
<para>As the main part of the <acronym>IPFW</acronym> system lives
<para>As the main part of the <application>IPFW</application> system lives
in the kernel, you will need to add one or more options to your
kernel configuration file, depending on what facilities you want,
and recompile your kernel. See
@ -5960,7 +5960,7 @@
<sect2>
<title>Configuring IPFW</title>
<para>The configuration of the <acronym>IPFW</acronym> software is
<para>The configuration of the <application>IPFW</application> software is
done through the <command>ipfw(8)</command> utility. The syntax
for this command looks quite complicated, but it is relatively
simple once you understand its structure.</para>
@ -6026,7 +6026,7 @@
</variablelist>
</para>
<para>Previous versions of <acronym>IPFW</acronym> used separate
<para>Previous versions of <application>IPFW</application> used separate
firewall and accounting entries. The present version provides
packet accounting with each firewall entry.</para>
@ -6457,7 +6457,7 @@
not the most efficient way, but it works.</para>
<para>The next problem is what your firewall should actually
<acronym>DO</acronym>! This is largely dependent on what access to
<emphasis>DO</emphasis>! This is largely dependent on what access to
your network you want to allow from the outside, and how much
access to the outside world you want to allow from the inside.
Some general rules are:</para>
@ -7543,7 +7543,7 @@
remap=tt>lp</emphasis>, it is also the default printer. The
second is named <emphasis remap=tt>bamboo</emphasis>, and has
as aliases <emphasis remap=tt>ps</emphasis>,
<acronym>PS</acronym>, <emphasis remap=tt>S</emphasis>,
<option>PS</option>, <emphasis remap=tt>S</emphasis>,
<emphasis remap=tt>panasonic</emphasis>, and <emphasis
remap=tt>Panasonic KX-P4455 PostScript
v51.4</emphasis>.</para>
@ -11320,9 +11320,9 @@
<para>The following is an example of what you might see when you run
then <command>edquota</command> command. When the
<command>edquota</command> command is invoked, you are
placed into the editor specified by the <acronym>EDITOR</acronym>
placed into the editor specified by the <envar>EDITOR</envar>
environment variable, or in the <command>vi</command>
editor if the <acronym>EDITOR</acronym> variable is not set, to
editor if the <envar>EDITOR</envar> variable is not set, to
allow you to edit the quota limits. <literallayout># edquota -u test
Quotas for user test: /usr: blocks in use: 65, limits (soft = 50,
hard = 75) inodes in use: 7, limits (soft = 50, hard = 60)
@ -13191,10 +13191,10 @@
</informalexample> The flags entry
<emphasis>must</emphasis> be changed from this example
unless you are using the exact same sio assignments.
Flags are set according to 0x<acronym>MYY</acronym>
where <emphasis>M</emphasis> indicates the minor number
Flags are set according to 0x<option><replaceable>M</replaceable>YY</option>
where <replaceable>M</replaceable> indicates the minor number
of the master port (the last port on a Boca 16) and
<acronym>YY</acronym> indicates if FIFO is enabled or
<replaceable>YY</replaceable> indicates if FIFO is enabled or
disabled(enabled), IRQ sharing is used(yes) and if there
is an AST/4 compatible IRQ control register(no). In this
example,
@ -16443,9 +16443,9 @@
<filename>/usr/obj</filename> and other directory trees that
can be exactly recreated by your computer. An example is the
files that comprise these handbook pages-they have been
generated from <acronym>SGML</acronym> input files. Creating
backups of these <acronym>HTML</acronym> files is not
necessary. The <acronym>SGML</acronym> source files are
generated from <abbrev>SGML</abbrev> input files. Creating
backups of these <abbrev>HTML</abbrev> files is not
necessary. The <abbrev>SGML</abbrev> source files are
backed up regularly.</para>
</sect4>
@ -16739,12 +16739,12 @@
<itemizedlist>
<listitem>
<para><acronym>LANG</acronym> for POSIX
<para><envar>LANG</envar> for POSIX
<function>setlocale(3)</function> family functions;</para>
</listitem>
<listitem>
<para><symbol>MM_CHARSET</symbol> for applications MIME
<para><envar>MM_CHARSET</envar> for applications MIME
chararter set.</para>
</listitem>
@ -17059,7 +17059,7 @@
<para>Naturally, you should make the initial state and lock state
devices writable only by <emphasis remap=tt>root</emphasis>. The
<filename>MAKEDEV</filename> script does <acronym>NOT</acronym> do
<filename>MAKEDEV</filename> script does <emphasis>NOT</emphasis> do
this when it creates the device entries.
</para>
@ -17886,45 +17886,45 @@
<itemizedlist>
<listitem>
<para> Transmitted Data (<acronym>SD</acronym>)</para>
<para> Transmitted Data (<abbrev>SD</abbrev>)</para>
</listitem>
<listitem>
<para> Received Data (<acronym>RD</acronym>)</para>
<para> Received Data (<abbrev>RD</abbrev>)</para>
</listitem>
<listitem>
<para> Request to Send (<acronym>RTS</acronym>)</para>
<para> Request to Send (<abbrev>RTS</abbrev>)</para>
</listitem>
<listitem>
<para> Clear to Send (<acronym>CTS</acronym>)</para>
<para> Clear to Send (<abbrev>CTS</abbrev>)</para>
</listitem>
<listitem>
<para> Data Set Ready (<acronym>DSR</acronym>)</para>
<para> Data Set Ready (<abbrev>DSR</abbrev>)</para>
</listitem>
<listitem>
<para> Data Terminal Ready (<acronym>DTR</acronym>)</para>
<para> Data Terminal Ready (<abbrev>DTR</abbrev>)</para>
</listitem>
<listitem>
<para> Carrier Detect (<acronym>CD</acronym>)</para>
<para> Carrier Detect (<abbrev>CD</abbrev>)</para>
</listitem>
<listitem>
<para> Signal Ground (<acronym>SG</acronym>)</para>
<para> Signal Ground (<abbrev>SG</abbrev>)</para>
</listitem>
</itemizedlist>
</para>
<para>FreeBSD needs the <acronym>RTS</acronym> and
<acronym>CTS</acronym> signals for flow-control at speeds above
2400bps, the <acronym>CD</acronym> signal to detect when a call
<para>FreeBSD needs the <abbrev>RTS</abbrev> and
<abbrev>CTS</abbrev> signals for flow-control at speeds above
2400bps, the <abbrev>CD</abbrev> signal to detect when a call
has been answered or the line has been hung up, and the
<acronym>DTR</acronym> signal to reset the modem after a session
<abbrev>DTR</abbrev> signal to reset the modem after a session
is complete. Some cables are wired without all of the needed
signals, so if you have problems, such as a login session not
going away when the line hangs up, you may have a problem with
@ -17985,7 +17985,7 @@
</para>
<para>When a user dials the modem's line and the modems connect, the
<acronym>CD</acronym> line is asserted by the modem. The kernel
<abbrev>CD</abbrev> line is asserted by the modem. The kernel
notices that carrier has been detected and completes <command>getty</command>'s open of the port. <command>getty</command> sends a <emphasis
remap=tt>login:</emphasis> prompt at the specified initial line
speed. <command>getty</command> watches to see if
@ -18142,13 +18142,13 @@
files. (The manual page for <command>MAKEDEV(8)</command> on
FreeBSD 1.1.5 is fairly bogus in its discussion of
<acronym>COM</acronym> ports, so ignore it.) To use
<acronym>MAKEDEV</acronym> to make dialup device special files
<filename>MAKEDEV</filename> to make dialup device special files
for <filename>COM1:</filename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue
the command <command>MAKEDEV ttyd0</command>.
Likewise, to make dialup device special files for
<filename>COM2:</filename> (port 1), use <command>MAKEDEV ttyd1</command>.</para>
<para><acronym>MAKEDEV</acronym> not only creates the
<para><filename>MAKEDEV</filename> not only creates the
<filename>/dev/ttyd?</filename> device special files, but also
creates the <filename>/dev/cua0?</filename> (and all of the
initializing and locking special files under FreeBSD 1.1.5 and
@ -18513,18 +18513,18 @@
<itemizedlist>
<listitem>
<para> <acronym>CD</acronym> asserted when connected
<para> <abbrev>CD</abbrev> asserted when connected
</para>
</listitem>
<listitem>
<para> <acronym>DTR</acronym> asserted for operation; dropping
<para> <abbrev>DTR</abbrev> asserted for operation; dropping
DTR hangs up line &amp; resets modem
</para>
</listitem>
<listitem>
<para> <acronym>CTS</acronym> transmitted data flow control
<para> <abbrev>CTS</abbrev> transmitted data flow control
</para>
</listitem>
@ -18534,7 +18534,7 @@
</listitem>
<listitem>
<para> <acronym>RTS</acronym> received data flow control
<para> <abbrev>RTS</abbrev> received data flow control
</para>
</listitem>
@ -18674,7 +18674,7 @@
command <emphasis remap=tt>ATI5</emphasis> displays the settings
that are stored in the non-volatile RAM. To see the true
operating parameters of the modem (as influenced by the USR's
DIP switch settings), use the commands <acronym>ATZ</acronym>
DIP switch settings), use the commands <command>ATZ</command>
and then <emphasis remap=tt>ATI4</emphasis>.</para>
<para>If you have a different brand of modem, check your modem's
@ -18696,14 +18696,14 @@
<para>Hook up your modem to your FreeBSD system, boot the system,
and, if your modem has status indication lights, watch to see
whether the modem's <acronym>DTR</acronym> indicator lights when
whether the modem's <abbrev>DTR</abbrev> indicator lights when
the <emphasis remap=tt>login:</emphasis> prompt appears on the
system's console - if it lights up, that should mean that
FreeBSD has started a <command>getty</command>
process on the appropriate communications port and is waiting
for the modem to accept a call.</para>
<para>If the <acronym>DTR</acronym> indicator doesn't light, login
<para>If the <abbrev>DTR</abbrev> indicator doesn't light, login
to the FreeBSD system through the console and issue a <command>ps ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port.
You should see a lines like this among the processes
@ -18731,7 +18731,7 @@
<command>getty</command> has completed its open on
the communications port. This could indicate a problem with the
cabling or a mis-configured modem, because <command>getty</command> should not be able to open the
communications port until <acronym>CD</acronym> (carrier detect)
communications port until <abbrev>CD</abbrev> (carrier detect)
has been asserted by the modem.</para>
<para>If you do not see any <command>getty</command>
@ -18759,7 +18759,7 @@
prompt right away, or get garbage, try pressing <emphasis
remap=tt>&lt;Enter&gt;</emphasis> about once per second. If
you still do not see a <emphasis remap=tt>login:</emphasis>
prompt after a while, try sending a <acronym>BREAK</acronym>.
prompt after a while, try sending a <command>BREAK</command>.
If you are using a high-speed modem to do the dialing, try
dialing again after locking the dialing modem's interface speed
(via <emphasis remap=tt>AT&amp;B1</emphasis> on a USR Sportster,
@ -18797,9 +18797,9 @@
<para>If you dial but the modem on the FreeBSD system will not
answer, make sure that the modem is configured to answer the
phone when <acronym>DTR</acronym> is asserted. If the modem
phone when <abbrev>DTR</abbrev> is asserted. If the modem
seems to be configured correctly, verify that the
<acronym>DTR</acronym> line is asserted by checking the modem's
<abbrev>DTR</abbrev> line is asserted by checking the modem's
indicator lights (if it has any).</para>
<para>If you have gone over everything several times and it still
@ -19187,7 +19187,7 @@
<listitem>
<para>The IP addresses of one or more nameservers. Normally,
you will be given two IP numbers. You
<acronym>MUST</acronym> have this information unless you run
<emphasis>MUST</emphasis> have this information unless you run
your own nameserver.</para>
</listitem>
@ -20161,7 +20161,7 @@
correct name), and <emphasis remap=tt>MyPassword</emphasis> is
the unencrypted password that you wish to use.
<filename>/etc/ppp/ppp.secret</filename> should
<acronym>NOT</acronym> be accessable by anyone without user id
<emphasis>NOT</emphasis> be accessable by anyone without user id
0. This means that <filename>/</filename>,
<filename>/etc</filename> and <filename>/etc/ppp</filename>
should not be writable, and <filename>ppp.secret</filename>
@ -21115,7 +21115,7 @@
have to edit the <filename>/etc/rc.conf</filename> file (called
<filename>/etc/sysconfig</filename> in FreeBSD releases prior to
2.2.2) and change the setting of the <emphasis
remap=bf>gateway</emphasis> variable to <acronym>YES</acronym>.
remap=bf>gateway</emphasis> variable to <option>YES</option>.
If you have an older system which predates even the
<filename>/etc/sysconfig</filename> file, then add the following
command: <literallayout>sysctl -w net.inet.ip.forwarding =
@ -22755,7 +22755,7 @@
</para>
<para>Do not panic, this is only a few hundred kilobytes in size.
The file <acronym>README</acronym> in the <emphasis
The file <filename>README</filename> in the <emphasis
remap=tt>cf</emphasis> directory can serve as a basic
introduction to m4 configuration.</para>
@ -22885,7 +22885,7 @@
``mumble.bar.edu'', instead of just ``mumble''. </para>
<para>Traditionally, this was allowed by BSD BIND resolvers. However
the current version of <acronym>BIND</acronym> that ships with
the current version of <application>BIND</application> that ships with
FreeBSD no longer provides default abbreviations for non-fully
qualified domain names other than the domain you are in. So an
unqualified host <emphasis remap=tt>mumble</emphasis> must either
@ -23083,7 +23083,7 @@
</sect2>
<sect2>
<title>What is FreeBSD-current <acronym>NOT</acronym>?</title>
<title>What is FreeBSD-current <emphasis>NOT</emphasis>?</title>
<para>
<orderedlist>
@ -23378,7 +23378,7 @@
the fly by the server, according to what you have and what you want
to have.</para>
<para><acronym>CTM</acronym>, on the other hand, does not
<para><application>CTM</application>, on the other hand, does not
interactively compare the sources you have with those on the master
archive. Instead, a script which identifies changes in files since
its previous run is executed several times a day on the master
@ -23409,26 +23409,26 @@
<para><emphasis>Contributed by &a.phk;. Updated
19-October-1997.</emphasis></para>
<para><acronym>CTM</acronym> is a method for keeping a remote
<para><application>CTM</application> is a method for keeping a remote
directory tree in sync with a central one. It has been developed
for usage with FreeBSD's source trees, though other people may
find it useful for other purposes as time goes by. Little, if
any, documentation currently exists at this time on the process of
creating deltas, so talk to &a.phk; for more information should
you wish to use <acronym>CTM</acronym> for other things.</para>
you wish to use <application>CTM</application> for other things.</para>
<sect3>
<title>Why should I use <acronym>CTM</acronym>?</title>
<title>Why should I use <application>CTM</application>?</title>
<para><acronym>CTM</acronym> will give you a local copy of the
<para><application>CTM</application> will give you a local copy of the
FreeBSD source trees. There are a number of <quote>flavors</quote> of the
tree available. Whether you wish to track the entire cvs tree or
just one of the branches, <acronym>CTM</acronym> can provide you
just one of the branches, <application>CTM</application> can provide you
the information. If you are an active developer on FreeBSD, but
have lousy or non-existent TCP/IP connectivity, or simply wish
to have the changes automatically sent to you,
<acronym>CTM</acronym> was made for you. You will need to obtain
<application>CTM</application> was made for you. You will need to obtain
up to three deltas per day for the most active branches.
However, you should consider having them sent by automatic
email. The sizes of the updates are always kept as small as
@ -23447,28 +23447,28 @@
</sect3>
<sect3>
<title>What do I need to use <acronym>CTM</acronym>?</title>
<title>What do I need to use <application>CTM</application>?</title>
<para>You will need two things: The ``<acronym>CTM</acronym>''
<para>You will need two things: The ``<application>CTM</application>''
program and the initial deltas to feed it (to get up to
<quote>current</quote> levels).</para>
<para>The <acronym>CTM</acronym> program has been part of FreeBSD
<para>The <application>CTM</application> program has been part of FreeBSD
ever since version 2.0 was released, and lives in
<filename>/usr/src/usr.sbin/<acronym>CTM</acronym></filename> if
<filename>/usr/src/usr.sbin/CTM</filename> if
you have a copy of the source online.</para>
<para>If you are running a pre-2.0 version of FreeBSD, you can
fetch the current <acronym>CTM</acronym> sources directly
fetch the current <application>CTM</application> sources directly
from:</para>
<para><ulink
URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm</ulink></para>
<para>The <quote>deltas</quote> you feed <acronym>CTM</acronym> can be had
<para>The <quote>deltas</quote> you feed <application>CTM</application> can be had
two ways, FTP or e-mail. If you have general FTP access to the
Internet then the following FTP sites support access to
<acronym>CTM</acronym>:</para>
<application>CTM</application>:</para>
<para><ulink
URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/CTM">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/CTM</ulink></para>
@ -23477,12 +23477,12 @@
remap="mirrors">.</para>
<para>FTP the relevant directory and fetch the
<acronym>README</acronym> file, starting from there.</para>
<filename>README</filename> file, starting from there.</para>
<para>If you may wish to get your deltas via email:</para>
<para>Send email to &a.majordomo; to subscribe to one of the
<acronym>CTM</acronym> distribution lists. ``ctm-cvs-cur''
<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
release branch, etc. (If you do not know how to subscribe
@ -23490,7 +23490,7 @@
word ``help'' - it will send you back usage
instructions.)</para>
<para>When you begin receiving your <acronym>CTM</acronym> updates
<para>When you begin receiving your <application>CTM</application> updates
in the mail, you may use the <symbol>ctm_rmail</symbol> program
to unpack and apply them. You can actually use the
<symbol>ctm_rmail</symbol> program directly from a entry in
@ -23500,10 +23500,10 @@
<note>
<para>No matter what method you use to get the
<acronym>CTM</acronym> deltas, you should subscribe to the
<application>CTM</application> deltas, you should subscribe to the
<email>ctm-announce@FreeBSD.ORG</email> mailing list. In the
future, this will be the only place where announcements
concerning the operations of the <acronym>CTM</acronym> system
concerning the operations of the <application>CTM</application> system
will be posted. Send an email to &a.majordomo; with a single
line of ``<emphasis remap=tt>subscribe
ctm-announce</emphasis>'' to get added to the list.</para>
@ -23511,10 +23511,10 @@
</sect3>
<sect3>
<title>Starting off with <acronym>CTM</acronym> for the first
<title>Starting off with <application>CTM</application> for the first
time</title>
<para>Before you can start using <acronym>CTM</acronym> deltas,
<para>Before you can start using <application>CTM</application> deltas,
you will need to get a to a starting point for the deltas
produced subsequently to it.</para>
@ -23527,7 +23527,7 @@
<para>Once you identify a suitable starting point, you must use an
initial <quote>transition</quote> delta to transform your starting point
into a <acronym>CTM</acronym> supported tree.</para>
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
@ -23546,7 +23546,7 @@
</sect3>
<sect3>
<title>Using <acronym>CTM</acronym> in your daily life</title>
<title>Using <application>CTM</application> in your daily life</title>
<para>To apply the deltas, simply say:
<informalexample>
@ -23556,18 +23556,18 @@
</informalexample>
</para>
<para><acronym>CTM</acronym> understands deltas which have been
<para><application>CTM</application> understands deltas which have been
put through <command>gzip</command>, so you do not
need to gunzip them first, this saves disk space.</para>
<para>Unless it feels very secure about the entire process,
<acronym>CTM</acronym> will not touch your tree. To verify a
<application>CTM</application> will not touch your tree. To verify a
delta you can also use the <option>-c</option> flag and
<acronym>CTM</acronym> will not actually touch your tree; it
<application>CTM</application> will not actually touch your tree; it
will merely verify the integrity of the delta and see if it
would apply cleanly to your current tree.</para>
<para>There are other options to <acronym>CTM</acronym> as well,
<para>There are other options to <application>CTM</application> as well,
see the manual pages or look in the sources for more
information.</para>
@ -23577,7 +23577,7 @@
when...</para>
<para>That's really all there is to it. Every time you get a new
delta, just run it through <acronym>CTM</acronym> to keep your
delta, just run it through <application>CTM</application> to keep your
sources up to date.</para>
<para>Do not remove the deltas if they are hard to download again.
@ -23668,7 +23668,7 @@
</sect3>
<sect3>
<title>Future plans for <acronym>CTM</acronym></title>
<title>Future plans for <application>CTM</application></title>
<para>Tons of them:
<itemizedlist>
@ -23679,7 +23679,7 @@
</listitem>
<listitem>
<para>Clean up the options to <acronym>CTM</acronym>, they
<para>Clean up the options to <application>CTM</application>, they
became confusing and counter intuitive.</para>
</listitem>
@ -26227,7 +26227,7 @@
<para>This is <emphasis>not</emphasis> a manual nor an
in-depth description on how to use or compile the port. In
particular, <emphasis>please do not just copy the
<acronym>README</acronym> file here</emphasis>, unless,
<filename>README</filename> file here</emphasis>, unless,
of course, it is a concise description of the port.</para>
</note>
@ -26579,9 +26579,9 @@
<para>If your port requires user input to build, configure or
install, then set <symbol>IS_INTERACTIVE</symbol> in your
Makefile. This will allow `overnight builds' to skip your port
if the user sets the variable <acronym>BATCH</acronym> in his
if the user sets the variable <envar>BATCH</envar> in his
environment (and if the user sets the variable
<acronym>INTERACTIVE</acronym>, then <emphasis>only</emphasis>
<envar>INTERACTIVE</envar>, then <emphasis>only</emphasis>
those ports requiring interaction are built).</para>
</sect4>
@ -31196,7 +31196,7 @@
kernel (but stripped of the debugging information).</para>
<para>You should configure the kernel in question with <command>config
-g</command>, include <acronym>DDB</acronym> into the
-g</command>, include <option>DDB</option> into the
configuration, and compile it as usual. This gives a large blurb of
a binary, due to the debugging information. Copy this kernel to the
target machine, strip the debugging symbols off with <command>strip

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

@ -1539,7 +1539,7 @@
<para>For as many `DISTS' you wish to install from MS-DOS (and you
have free space for), install each one under
<filename>C:\FREEBSD</filename> - the <acronym>BIN</acronym> dist
<filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist
is only the minimal requirement.</para>
</sect2>
@ -2729,7 +2729,7 @@
into a single file (<filename>.tar</filename>) and optionally
compressed (<filename>.gz</filename>). This technique was
originally used for <emphasis>T</emphasis>ape
<acronym>AR</acronym>chives (hence the name `tar'), but it is
<emphasis>AR</emphasis>chives (hence the name `tar'), but it is
a widely used way of distributing program source code around
the Internet.</para>
@ -3401,7 +3401,7 @@
<para>Since this name is passed to the C compiler as a
<option>-D</option> switch, do not use names like
<acronym>DEBUG</acronym>, or something that could be
<option>DEBUG</option>, or something that could be
confused with another machine or CPU name, like <emphasis
remap=tt>vax</emphasis>.</para>
</listitem>
@ -3785,7 +3785,7 @@
<para><emphasis remap=tt>npx0</emphasis> is the interface to
the floating point math unit in FreeBSD, either the
hardware co-processor or the software math emulator. It
is <acronym>NOT</acronym> optional.</para>
is <emphasis>NOT</emphasis> optional.</para>
</listitem>
</varlistentry>
@ -5789,7 +5789,7 @@
authentication mechanisms.</para>
<para>FreeBSD comes with a kernel packet filter (known as
<acronym>IPFW</acronym>), which is what the rest of this section
<application>IPFW</application>), which is what the rest of this section
will concentrate on. Proxy servers can be built on FreeBSD from
third party software, but there is such a variety of proxy servers
available that it would be impossible to cover them in this
@ -5865,14 +5865,14 @@
<sect2>
<title>What does IPFW allow me to do?</title>
<para><acronym>IPFW</acronym>, the software supplied with FreeBSD,
<para><application>IPFW</application>, the software supplied with FreeBSD,
is a packet filtering and accounting system which resides in the
kernel, and has a user-land control utility,
<command>ipfw(8)</command>. Together, they allow you to define and
query the rules currently used by the kernel in its routing
decisions.</para>
<para>There are two related parts to <acronym>IPFW</acronym>. The
<para>There are two related parts to <application>IPFW</application>. The
firewall section allows you to perform packet filtering. There is
also an IP accounting section which allows you to track usage of
your router, based on similar rules to the firewall section. This
@ -5880,11 +5880,11 @@
getting from a certain machine, or how much WWW (World Wide Web)
traffic it is forwarding.</para>
<para>As a result of the way that <acronym>IPFW</acronym> is
designed, you can use <acronym>IPFW</acronym> on non-router
<para>As a result of the way that <application>IPFW</application> is
designed, you can use <application>IPFW</application> on non-router
machines to perform packet filtering on incoming and outgoing
connections. This is a special case of the more general use of
<acronym>IPFW</acronym>, and the same commands and techniques
<application>IPFW</application>, and the same commands and techniques
should be used in this situation.</para>
</sect2>
@ -5892,7 +5892,7 @@
<sect2>
<title>Enabling IPFW on FreeBSD</title>
<para>As the main part of the <acronym>IPFW</acronym> system lives
<para>As the main part of the <application>IPFW</application> system lives
in the kernel, you will need to add one or more options to your
kernel configuration file, depending on what facilities you want,
and recompile your kernel. See
@ -5960,7 +5960,7 @@
<sect2>
<title>Configuring IPFW</title>
<para>The configuration of the <acronym>IPFW</acronym> software is
<para>The configuration of the <application>IPFW</application> software is
done through the <command>ipfw(8)</command> utility. The syntax
for this command looks quite complicated, but it is relatively
simple once you understand its structure.</para>
@ -6026,7 +6026,7 @@
</variablelist>
</para>
<para>Previous versions of <acronym>IPFW</acronym> used separate
<para>Previous versions of <application>IPFW</application> used separate
firewall and accounting entries. The present version provides
packet accounting with each firewall entry.</para>
@ -6457,7 +6457,7 @@
not the most efficient way, but it works.</para>
<para>The next problem is what your firewall should actually
<acronym>DO</acronym>! This is largely dependent on what access to
<emphasis>DO</emphasis>! This is largely dependent on what access to
your network you want to allow from the outside, and how much
access to the outside world you want to allow from the inside.
Some general rules are:</para>
@ -7543,7 +7543,7 @@
remap=tt>lp</emphasis>, it is also the default printer. The
second is named <emphasis remap=tt>bamboo</emphasis>, and has
as aliases <emphasis remap=tt>ps</emphasis>,
<acronym>PS</acronym>, <emphasis remap=tt>S</emphasis>,
<option>PS</option>, <emphasis remap=tt>S</emphasis>,
<emphasis remap=tt>panasonic</emphasis>, and <emphasis
remap=tt>Panasonic KX-P4455 PostScript
v51.4</emphasis>.</para>
@ -11320,9 +11320,9 @@
<para>The following is an example of what you might see when you run
then <command>edquota</command> command. When the
<command>edquota</command> command is invoked, you are
placed into the editor specified by the <acronym>EDITOR</acronym>
placed into the editor specified by the <envar>EDITOR</envar>
environment variable, or in the <command>vi</command>
editor if the <acronym>EDITOR</acronym> variable is not set, to
editor if the <envar>EDITOR</envar> variable is not set, to
allow you to edit the quota limits. <literallayout># edquota -u test
Quotas for user test: /usr: blocks in use: 65, limits (soft = 50,
hard = 75) inodes in use: 7, limits (soft = 50, hard = 60)
@ -13191,10 +13191,10 @@
</informalexample> The flags entry
<emphasis>must</emphasis> be changed from this example
unless you are using the exact same sio assignments.
Flags are set according to 0x<acronym>MYY</acronym>
where <emphasis>M</emphasis> indicates the minor number
Flags are set according to 0x<option><replaceable>M</replaceable>YY</option>
where <replaceable>M</replaceable> indicates the minor number
of the master port (the last port on a Boca 16) and
<acronym>YY</acronym> indicates if FIFO is enabled or
<replaceable>YY</replaceable> indicates if FIFO is enabled or
disabled(enabled), IRQ sharing is used(yes) and if there
is an AST/4 compatible IRQ control register(no). In this
example,
@ -16443,9 +16443,9 @@
<filename>/usr/obj</filename> and other directory trees that
can be exactly recreated by your computer. An example is the
files that comprise these handbook pages-they have been
generated from <acronym>SGML</acronym> input files. Creating
backups of these <acronym>HTML</acronym> files is not
necessary. The <acronym>SGML</acronym> source files are
generated from <abbrev>SGML</abbrev> input files. Creating
backups of these <abbrev>HTML</abbrev> files is not
necessary. The <abbrev>SGML</abbrev> source files are
backed up regularly.</para>
</sect4>
@ -16739,12 +16739,12 @@
<itemizedlist>
<listitem>
<para><acronym>LANG</acronym> for POSIX
<para><envar>LANG</envar> for POSIX
<function>setlocale(3)</function> family functions;</para>
</listitem>
<listitem>
<para><symbol>MM_CHARSET</symbol> for applications MIME
<para><envar>MM_CHARSET</envar> for applications MIME
chararter set.</para>
</listitem>
@ -17059,7 +17059,7 @@
<para>Naturally, you should make the initial state and lock state
devices writable only by <emphasis remap=tt>root</emphasis>. The
<filename>MAKEDEV</filename> script does <acronym>NOT</acronym> do
<filename>MAKEDEV</filename> script does <emphasis>NOT</emphasis> do
this when it creates the device entries.
</para>
@ -17886,45 +17886,45 @@
<itemizedlist>
<listitem>
<para> Transmitted Data (<acronym>SD</acronym>)</para>
<para> Transmitted Data (<abbrev>SD</abbrev>)</para>
</listitem>
<listitem>
<para> Received Data (<acronym>RD</acronym>)</para>
<para> Received Data (<abbrev>RD</abbrev>)</para>
</listitem>
<listitem>
<para> Request to Send (<acronym>RTS</acronym>)</para>
<para> Request to Send (<abbrev>RTS</abbrev>)</para>
</listitem>
<listitem>
<para> Clear to Send (<acronym>CTS</acronym>)</para>
<para> Clear to Send (<abbrev>CTS</abbrev>)</para>
</listitem>
<listitem>
<para> Data Set Ready (<acronym>DSR</acronym>)</para>
<para> Data Set Ready (<abbrev>DSR</abbrev>)</para>
</listitem>
<listitem>
<para> Data Terminal Ready (<acronym>DTR</acronym>)</para>
<para> Data Terminal Ready (<abbrev>DTR</abbrev>)</para>
</listitem>
<listitem>
<para> Carrier Detect (<acronym>CD</acronym>)</para>
<para> Carrier Detect (<abbrev>CD</abbrev>)</para>
</listitem>
<listitem>
<para> Signal Ground (<acronym>SG</acronym>)</para>
<para> Signal Ground (<abbrev>SG</abbrev>)</para>
</listitem>
</itemizedlist>
</para>
<para>FreeBSD needs the <acronym>RTS</acronym> and
<acronym>CTS</acronym> signals for flow-control at speeds above
2400bps, the <acronym>CD</acronym> signal to detect when a call
<para>FreeBSD needs the <abbrev>RTS</abbrev> and
<abbrev>CTS</abbrev> signals for flow-control at speeds above
2400bps, the <abbrev>CD</abbrev> signal to detect when a call
has been answered or the line has been hung up, and the
<acronym>DTR</acronym> signal to reset the modem after a session
<abbrev>DTR</abbrev> signal to reset the modem after a session
is complete. Some cables are wired without all of the needed
signals, so if you have problems, such as a login session not
going away when the line hangs up, you may have a problem with
@ -17985,7 +17985,7 @@
</para>
<para>When a user dials the modem's line and the modems connect, the
<acronym>CD</acronym> line is asserted by the modem. The kernel
<abbrev>CD</abbrev> line is asserted by the modem. The kernel
notices that carrier has been detected and completes <command>getty</command>'s open of the port. <command>getty</command> sends a <emphasis
remap=tt>login:</emphasis> prompt at the specified initial line
speed. <command>getty</command> watches to see if
@ -18142,13 +18142,13 @@
files. (The manual page for <command>MAKEDEV(8)</command> on
FreeBSD 1.1.5 is fairly bogus in its discussion of
<acronym>COM</acronym> ports, so ignore it.) To use
<acronym>MAKEDEV</acronym> to make dialup device special files
<filename>MAKEDEV</filename> to make dialup device special files
for <filename>COM1:</filename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue
the command <command>MAKEDEV ttyd0</command>.
Likewise, to make dialup device special files for
<filename>COM2:</filename> (port 1), use <command>MAKEDEV ttyd1</command>.</para>
<para><acronym>MAKEDEV</acronym> not only creates the
<para><filename>MAKEDEV</filename> not only creates the
<filename>/dev/ttyd?</filename> device special files, but also
creates the <filename>/dev/cua0?</filename> (and all of the
initializing and locking special files under FreeBSD 1.1.5 and
@ -18513,18 +18513,18 @@
<itemizedlist>
<listitem>
<para> <acronym>CD</acronym> asserted when connected
<para> <abbrev>CD</abbrev> asserted when connected
</para>
</listitem>
<listitem>
<para> <acronym>DTR</acronym> asserted for operation; dropping
<para> <abbrev>DTR</abbrev> asserted for operation; dropping
DTR hangs up line &amp; resets modem
</para>
</listitem>
<listitem>
<para> <acronym>CTS</acronym> transmitted data flow control
<para> <abbrev>CTS</abbrev> transmitted data flow control
</para>
</listitem>
@ -18534,7 +18534,7 @@
</listitem>
<listitem>
<para> <acronym>RTS</acronym> received data flow control
<para> <abbrev>RTS</abbrev> received data flow control
</para>
</listitem>
@ -18674,7 +18674,7 @@
command <emphasis remap=tt>ATI5</emphasis> displays the settings
that are stored in the non-volatile RAM. To see the true
operating parameters of the modem (as influenced by the USR's
DIP switch settings), use the commands <acronym>ATZ</acronym>
DIP switch settings), use the commands <command>ATZ</command>
and then <emphasis remap=tt>ATI4</emphasis>.</para>
<para>If you have a different brand of modem, check your modem's
@ -18696,14 +18696,14 @@
<para>Hook up your modem to your FreeBSD system, boot the system,
and, if your modem has status indication lights, watch to see
whether the modem's <acronym>DTR</acronym> indicator lights when
whether the modem's <abbrev>DTR</abbrev> indicator lights when
the <emphasis remap=tt>login:</emphasis> prompt appears on the
system's console - if it lights up, that should mean that
FreeBSD has started a <command>getty</command>
process on the appropriate communications port and is waiting
for the modem to accept a call.</para>
<para>If the <acronym>DTR</acronym> indicator doesn't light, login
<para>If the <abbrev>DTR</abbrev> indicator doesn't light, login
to the FreeBSD system through the console and issue a <command>ps ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port.
You should see a lines like this among the processes
@ -18731,7 +18731,7 @@
<command>getty</command> has completed its open on
the communications port. This could indicate a problem with the
cabling or a mis-configured modem, because <command>getty</command> should not be able to open the
communications port until <acronym>CD</acronym> (carrier detect)
communications port until <abbrev>CD</abbrev> (carrier detect)
has been asserted by the modem.</para>
<para>If you do not see any <command>getty</command>
@ -18759,7 +18759,7 @@
prompt right away, or get garbage, try pressing <emphasis
remap=tt>&lt;Enter&gt;</emphasis> about once per second. If
you still do not see a <emphasis remap=tt>login:</emphasis>
prompt after a while, try sending a <acronym>BREAK</acronym>.
prompt after a while, try sending a <command>BREAK</command>.
If you are using a high-speed modem to do the dialing, try
dialing again after locking the dialing modem's interface speed
(via <emphasis remap=tt>AT&amp;B1</emphasis> on a USR Sportster,
@ -18797,9 +18797,9 @@
<para>If you dial but the modem on the FreeBSD system will not
answer, make sure that the modem is configured to answer the
phone when <acronym>DTR</acronym> is asserted. If the modem
phone when <abbrev>DTR</abbrev> is asserted. If the modem
seems to be configured correctly, verify that the
<acronym>DTR</acronym> line is asserted by checking the modem's
<abbrev>DTR</abbrev> line is asserted by checking the modem's
indicator lights (if it has any).</para>
<para>If you have gone over everything several times and it still
@ -19187,7 +19187,7 @@
<listitem>
<para>The IP addresses of one or more nameservers. Normally,
you will be given two IP numbers. You
<acronym>MUST</acronym> have this information unless you run
<emphasis>MUST</emphasis> have this information unless you run
your own nameserver.</para>
</listitem>
@ -20161,7 +20161,7 @@
correct name), and <emphasis remap=tt>MyPassword</emphasis> is
the unencrypted password that you wish to use.
<filename>/etc/ppp/ppp.secret</filename> should
<acronym>NOT</acronym> be accessable by anyone without user id
<emphasis>NOT</emphasis> be accessable by anyone without user id
0. This means that <filename>/</filename>,
<filename>/etc</filename> and <filename>/etc/ppp</filename>
should not be writable, and <filename>ppp.secret</filename>
@ -21115,7 +21115,7 @@
have to edit the <filename>/etc/rc.conf</filename> file (called
<filename>/etc/sysconfig</filename> in FreeBSD releases prior to
2.2.2) and change the setting of the <emphasis
remap=bf>gateway</emphasis> variable to <acronym>YES</acronym>.
remap=bf>gateway</emphasis> variable to <option>YES</option>.
If you have an older system which predates even the
<filename>/etc/sysconfig</filename> file, then add the following
command: <literallayout>sysctl -w net.inet.ip.forwarding =
@ -22755,7 +22755,7 @@
</para>
<para>Do not panic, this is only a few hundred kilobytes in size.
The file <acronym>README</acronym> in the <emphasis
The file <filename>README</filename> in the <emphasis
remap=tt>cf</emphasis> directory can serve as a basic
introduction to m4 configuration.</para>
@ -22885,7 +22885,7 @@
``mumble.bar.edu'', instead of just ``mumble''. </para>
<para>Traditionally, this was allowed by BSD BIND resolvers. However
the current version of <acronym>BIND</acronym> that ships with
the current version of <application>BIND</application> that ships with
FreeBSD no longer provides default abbreviations for non-fully
qualified domain names other than the domain you are in. So an
unqualified host <emphasis remap=tt>mumble</emphasis> must either
@ -23083,7 +23083,7 @@
</sect2>
<sect2>
<title>What is FreeBSD-current <acronym>NOT</acronym>?</title>
<title>What is FreeBSD-current <emphasis>NOT</emphasis>?</title>
<para>
<orderedlist>
@ -23378,7 +23378,7 @@
the fly by the server, according to what you have and what you want
to have.</para>
<para><acronym>CTM</acronym>, on the other hand, does not
<para><application>CTM</application>, on the other hand, does not
interactively compare the sources you have with those on the master
archive. Instead, a script which identifies changes in files since
its previous run is executed several times a day on the master
@ -23409,26 +23409,26 @@
<para><emphasis>Contributed by &a.phk;. Updated
19-October-1997.</emphasis></para>
<para><acronym>CTM</acronym> is a method for keeping a remote
<para><application>CTM</application> is a method for keeping a remote
directory tree in sync with a central one. It has been developed
for usage with FreeBSD's source trees, though other people may
find it useful for other purposes as time goes by. Little, if
any, documentation currently exists at this time on the process of
creating deltas, so talk to &a.phk; for more information should
you wish to use <acronym>CTM</acronym> for other things.</para>
you wish to use <application>CTM</application> for other things.</para>
<sect3>
<title>Why should I use <acronym>CTM</acronym>?</title>
<title>Why should I use <application>CTM</application>?</title>
<para><acronym>CTM</acronym> will give you a local copy of the
<para><application>CTM</application> will give you a local copy of the
FreeBSD source trees. There are a number of <quote>flavors</quote> of the
tree available. Whether you wish to track the entire cvs tree or
just one of the branches, <acronym>CTM</acronym> can provide you
just one of the branches, <application>CTM</application> can provide you
the information. If you are an active developer on FreeBSD, but
have lousy or non-existent TCP/IP connectivity, or simply wish
to have the changes automatically sent to you,
<acronym>CTM</acronym> was made for you. You will need to obtain
<application>CTM</application> was made for you. You will need to obtain
up to three deltas per day for the most active branches.
However, you should consider having them sent by automatic
email. The sizes of the updates are always kept as small as
@ -23447,28 +23447,28 @@
</sect3>
<sect3>
<title>What do I need to use <acronym>CTM</acronym>?</title>
<title>What do I need to use <application>CTM</application>?</title>
<para>You will need two things: The ``<acronym>CTM</acronym>''
<para>You will need two things: The ``<application>CTM</application>''
program and the initial deltas to feed it (to get up to
<quote>current</quote> levels).</para>
<para>The <acronym>CTM</acronym> program has been part of FreeBSD
<para>The <application>CTM</application> program has been part of FreeBSD
ever since version 2.0 was released, and lives in
<filename>/usr/src/usr.sbin/<acronym>CTM</acronym></filename> if
<filename>/usr/src/usr.sbin/CTM</filename> if
you have a copy of the source online.</para>
<para>If you are running a pre-2.0 version of FreeBSD, you can
fetch the current <acronym>CTM</acronym> sources directly
fetch the current <application>CTM</application> sources directly
from:</para>
<para><ulink
URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm</ulink></para>
<para>The <quote>deltas</quote> you feed <acronym>CTM</acronym> can be had
<para>The <quote>deltas</quote> you feed <application>CTM</application> can be had
two ways, FTP or e-mail. If you have general FTP access to the
Internet then the following FTP sites support access to
<acronym>CTM</acronym>:</para>
<application>CTM</application>:</para>
<para><ulink
URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/CTM">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/CTM</ulink></para>
@ -23477,12 +23477,12 @@
remap="mirrors">.</para>
<para>FTP the relevant directory and fetch the
<acronym>README</acronym> file, starting from there.</para>
<filename>README</filename> file, starting from there.</para>
<para>If you may wish to get your deltas via email:</para>
<para>Send email to &a.majordomo; to subscribe to one of the
<acronym>CTM</acronym> distribution lists. ``ctm-cvs-cur''
<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
release branch, etc. (If you do not know how to subscribe
@ -23490,7 +23490,7 @@
word ``help'' - it will send you back usage
instructions.)</para>
<para>When you begin receiving your <acronym>CTM</acronym> updates
<para>When you begin receiving your <application>CTM</application> updates
in the mail, you may use the <symbol>ctm_rmail</symbol> program
to unpack and apply them. You can actually use the
<symbol>ctm_rmail</symbol> program directly from a entry in
@ -23500,10 +23500,10 @@
<note>
<para>No matter what method you use to get the
<acronym>CTM</acronym> deltas, you should subscribe to the
<application>CTM</application> deltas, you should subscribe to the
<email>ctm-announce@FreeBSD.ORG</email> mailing list. In the
future, this will be the only place where announcements
concerning the operations of the <acronym>CTM</acronym> system
concerning the operations of the <application>CTM</application> system
will be posted. Send an email to &a.majordomo; with a single
line of ``<emphasis remap=tt>subscribe
ctm-announce</emphasis>'' to get added to the list.</para>
@ -23511,10 +23511,10 @@
</sect3>
<sect3>
<title>Starting off with <acronym>CTM</acronym> for the first
<title>Starting off with <application>CTM</application> for the first
time</title>
<para>Before you can start using <acronym>CTM</acronym> deltas,
<para>Before you can start using <application>CTM</application> deltas,
you will need to get a to a starting point for the deltas
produced subsequently to it.</para>
@ -23527,7 +23527,7 @@
<para>Once you identify a suitable starting point, you must use an
initial <quote>transition</quote> delta to transform your starting point
into a <acronym>CTM</acronym> supported tree.</para>
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
@ -23546,7 +23546,7 @@
</sect3>
<sect3>
<title>Using <acronym>CTM</acronym> in your daily life</title>
<title>Using <application>CTM</application> in your daily life</title>
<para>To apply the deltas, simply say:
<informalexample>
@ -23556,18 +23556,18 @@
</informalexample>
</para>
<para><acronym>CTM</acronym> understands deltas which have been
<para><application>CTM</application> understands deltas which have been
put through <command>gzip</command>, so you do not
need to gunzip them first, this saves disk space.</para>
<para>Unless it feels very secure about the entire process,
<acronym>CTM</acronym> will not touch your tree. To verify a
<application>CTM</application> will not touch your tree. To verify a
delta you can also use the <option>-c</option> flag and
<acronym>CTM</acronym> will not actually touch your tree; it
<application>CTM</application> will not actually touch your tree; it
will merely verify the integrity of the delta and see if it
would apply cleanly to your current tree.</para>
<para>There are other options to <acronym>CTM</acronym> as well,
<para>There are other options to <application>CTM</application> as well,
see the manual pages or look in the sources for more
information.</para>
@ -23577,7 +23577,7 @@
when...</para>
<para>That's really all there is to it. Every time you get a new
delta, just run it through <acronym>CTM</acronym> to keep your
delta, just run it through <application>CTM</application> to keep your
sources up to date.</para>
<para>Do not remove the deltas if they are hard to download again.
@ -23668,7 +23668,7 @@
</sect3>
<sect3>
<title>Future plans for <acronym>CTM</acronym></title>
<title>Future plans for <application>CTM</application></title>
<para>Tons of them:
<itemizedlist>
@ -23679,7 +23679,7 @@
</listitem>
<listitem>
<para>Clean up the options to <acronym>CTM</acronym>, they
<para>Clean up the options to <application>CTM</application>, they
became confusing and counter intuitive.</para>
</listitem>
@ -26227,7 +26227,7 @@
<para>This is <emphasis>not</emphasis> a manual nor an
in-depth description on how to use or compile the port. In
particular, <emphasis>please do not just copy the
<acronym>README</acronym> file here</emphasis>, unless,
<filename>README</filename> file here</emphasis>, unless,
of course, it is a concise description of the port.</para>
</note>
@ -26579,9 +26579,9 @@
<para>If your port requires user input to build, configure or
install, then set <symbol>IS_INTERACTIVE</symbol> in your
Makefile. This will allow `overnight builds' to skip your port
if the user sets the variable <acronym>BATCH</acronym> in his
if the user sets the variable <envar>BATCH</envar> in his
environment (and if the user sets the variable
<acronym>INTERACTIVE</acronym>, then <emphasis>only</emphasis>
<envar>INTERACTIVE</envar>, then <emphasis>only</emphasis>
those ports requiring interaction are built).</para>
</sect4>
@ -31196,7 +31196,7 @@
kernel (but stripped of the debugging information).</para>
<para>You should configure the kernel in question with <command>config
-g</command>, include <acronym>DDB</acronym> into the
-g</command>, include <option>DDB</option> into the
configuration, and compile it as usual. This gives a large blurb of
a binary, due to the debugging information. Copy this kernel to the
target machine, strip the debugging symbols off with <command>strip

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

@ -1539,7 +1539,7 @@
<para>For as many `DISTS' you wish to install from MS-DOS (and you
have free space for), install each one under
<filename>C:\FREEBSD</filename> - the <acronym>BIN</acronym> dist
<filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist
is only the minimal requirement.</para>
</sect2>
@ -2729,7 +2729,7 @@
into a single file (<filename>.tar</filename>) and optionally
compressed (<filename>.gz</filename>). This technique was
originally used for <emphasis>T</emphasis>ape
<acronym>AR</acronym>chives (hence the name `tar'), but it is
<emphasis>AR</emphasis>chives (hence the name `tar'), but it is
a widely used way of distributing program source code around
the Internet.</para>
@ -3401,7 +3401,7 @@
<para>Since this name is passed to the C compiler as a
<option>-D</option> switch, do not use names like
<acronym>DEBUG</acronym>, or something that could be
<option>DEBUG</option>, or something that could be
confused with another machine or CPU name, like <emphasis
remap=tt>vax</emphasis>.</para>
</listitem>
@ -3785,7 +3785,7 @@
<para><emphasis remap=tt>npx0</emphasis> is the interface to
the floating point math unit in FreeBSD, either the
hardware co-processor or the software math emulator. It
is <acronym>NOT</acronym> optional.</para>
is <emphasis>NOT</emphasis> optional.</para>
</listitem>
</varlistentry>
@ -5789,7 +5789,7 @@
authentication mechanisms.</para>
<para>FreeBSD comes with a kernel packet filter (known as
<acronym>IPFW</acronym>), which is what the rest of this section
<application>IPFW</application>), which is what the rest of this section
will concentrate on. Proxy servers can be built on FreeBSD from
third party software, but there is such a variety of proxy servers
available that it would be impossible to cover them in this
@ -5865,14 +5865,14 @@
<sect2>
<title>What does IPFW allow me to do?</title>
<para><acronym>IPFW</acronym>, the software supplied with FreeBSD,
<para><application>IPFW</application>, the software supplied with FreeBSD,
is a packet filtering and accounting system which resides in the
kernel, and has a user-land control utility,
<command>ipfw(8)</command>. Together, they allow you to define and
query the rules currently used by the kernel in its routing
decisions.</para>
<para>There are two related parts to <acronym>IPFW</acronym>. The
<para>There are two related parts to <application>IPFW</application>. The
firewall section allows you to perform packet filtering. There is
also an IP accounting section which allows you to track usage of
your router, based on similar rules to the firewall section. This
@ -5880,11 +5880,11 @@
getting from a certain machine, or how much WWW (World Wide Web)
traffic it is forwarding.</para>
<para>As a result of the way that <acronym>IPFW</acronym> is
designed, you can use <acronym>IPFW</acronym> on non-router
<para>As a result of the way that <application>IPFW</application> is
designed, you can use <application>IPFW</application> on non-router
machines to perform packet filtering on incoming and outgoing
connections. This is a special case of the more general use of
<acronym>IPFW</acronym>, and the same commands and techniques
<application>IPFW</application>, and the same commands and techniques
should be used in this situation.</para>
</sect2>
@ -5892,7 +5892,7 @@
<sect2>
<title>Enabling IPFW on FreeBSD</title>
<para>As the main part of the <acronym>IPFW</acronym> system lives
<para>As the main part of the <application>IPFW</application> system lives
in the kernel, you will need to add one or more options to your
kernel configuration file, depending on what facilities you want,
and recompile your kernel. See
@ -5960,7 +5960,7 @@
<sect2>
<title>Configuring IPFW</title>
<para>The configuration of the <acronym>IPFW</acronym> software is
<para>The configuration of the <application>IPFW</application> software is
done through the <command>ipfw(8)</command> utility. The syntax
for this command looks quite complicated, but it is relatively
simple once you understand its structure.</para>
@ -6026,7 +6026,7 @@
</variablelist>
</para>
<para>Previous versions of <acronym>IPFW</acronym> used separate
<para>Previous versions of <application>IPFW</application> used separate
firewall and accounting entries. The present version provides
packet accounting with each firewall entry.</para>
@ -6457,7 +6457,7 @@
not the most efficient way, but it works.</para>
<para>The next problem is what your firewall should actually
<acronym>DO</acronym>! This is largely dependent on what access to
<emphasis>DO</emphasis>! This is largely dependent on what access to
your network you want to allow from the outside, and how much
access to the outside world you want to allow from the inside.
Some general rules are:</para>
@ -7543,7 +7543,7 @@
remap=tt>lp</emphasis>, it is also the default printer. The
second is named <emphasis remap=tt>bamboo</emphasis>, and has
as aliases <emphasis remap=tt>ps</emphasis>,
<acronym>PS</acronym>, <emphasis remap=tt>S</emphasis>,
<option>PS</option>, <emphasis remap=tt>S</emphasis>,
<emphasis remap=tt>panasonic</emphasis>, and <emphasis
remap=tt>Panasonic KX-P4455 PostScript
v51.4</emphasis>.</para>
@ -11320,9 +11320,9 @@
<para>The following is an example of what you might see when you run
then <command>edquota</command> command. When the
<command>edquota</command> command is invoked, you are
placed into the editor specified by the <acronym>EDITOR</acronym>
placed into the editor specified by the <envar>EDITOR</envar>
environment variable, or in the <command>vi</command>
editor if the <acronym>EDITOR</acronym> variable is not set, to
editor if the <envar>EDITOR</envar> variable is not set, to
allow you to edit the quota limits. <literallayout># edquota -u test
Quotas for user test: /usr: blocks in use: 65, limits (soft = 50,
hard = 75) inodes in use: 7, limits (soft = 50, hard = 60)
@ -13191,10 +13191,10 @@
</informalexample> The flags entry
<emphasis>must</emphasis> be changed from this example
unless you are using the exact same sio assignments.
Flags are set according to 0x<acronym>MYY</acronym>
where <emphasis>M</emphasis> indicates the minor number
Flags are set according to 0x<option><replaceable>M</replaceable>YY</option>
where <replaceable>M</replaceable> indicates the minor number
of the master port (the last port on a Boca 16) and
<acronym>YY</acronym> indicates if FIFO is enabled or
<replaceable>YY</replaceable> indicates if FIFO is enabled or
disabled(enabled), IRQ sharing is used(yes) and if there
is an AST/4 compatible IRQ control register(no). In this
example,
@ -16443,9 +16443,9 @@
<filename>/usr/obj</filename> and other directory trees that
can be exactly recreated by your computer. An example is the
files that comprise these handbook pages-they have been
generated from <acronym>SGML</acronym> input files. Creating
backups of these <acronym>HTML</acronym> files is not
necessary. The <acronym>SGML</acronym> source files are
generated from <abbrev>SGML</abbrev> input files. Creating
backups of these <abbrev>HTML</abbrev> files is not
necessary. The <abbrev>SGML</abbrev> source files are
backed up regularly.</para>
</sect4>
@ -16739,12 +16739,12 @@
<itemizedlist>
<listitem>
<para><acronym>LANG</acronym> for POSIX
<para><envar>LANG</envar> for POSIX
<function>setlocale(3)</function> family functions;</para>
</listitem>
<listitem>
<para><symbol>MM_CHARSET</symbol> for applications MIME
<para><envar>MM_CHARSET</envar> for applications MIME
chararter set.</para>
</listitem>
@ -17059,7 +17059,7 @@
<para>Naturally, you should make the initial state and lock state
devices writable only by <emphasis remap=tt>root</emphasis>. The
<filename>MAKEDEV</filename> script does <acronym>NOT</acronym> do
<filename>MAKEDEV</filename> script does <emphasis>NOT</emphasis> do
this when it creates the device entries.
</para>
@ -17886,45 +17886,45 @@
<itemizedlist>
<listitem>
<para> Transmitted Data (<acronym>SD</acronym>)</para>
<para> Transmitted Data (<abbrev>SD</abbrev>)</para>
</listitem>
<listitem>
<para> Received Data (<acronym>RD</acronym>)</para>
<para> Received Data (<abbrev>RD</abbrev>)</para>
</listitem>
<listitem>
<para> Request to Send (<acronym>RTS</acronym>)</para>
<para> Request to Send (<abbrev>RTS</abbrev>)</para>
</listitem>
<listitem>
<para> Clear to Send (<acronym>CTS</acronym>)</para>
<para> Clear to Send (<abbrev>CTS</abbrev>)</para>
</listitem>
<listitem>
<para> Data Set Ready (<acronym>DSR</acronym>)</para>
<para> Data Set Ready (<abbrev>DSR</abbrev>)</para>
</listitem>
<listitem>
<para> Data Terminal Ready (<acronym>DTR</acronym>)</para>
<para> Data Terminal Ready (<abbrev>DTR</abbrev>)</para>
</listitem>
<listitem>
<para> Carrier Detect (<acronym>CD</acronym>)</para>
<para> Carrier Detect (<abbrev>CD</abbrev>)</para>
</listitem>
<listitem>
<para> Signal Ground (<acronym>SG</acronym>)</para>
<para> Signal Ground (<abbrev>SG</abbrev>)</para>
</listitem>
</itemizedlist>
</para>
<para>FreeBSD needs the <acronym>RTS</acronym> and
<acronym>CTS</acronym> signals for flow-control at speeds above
2400bps, the <acronym>CD</acronym> signal to detect when a call
<para>FreeBSD needs the <abbrev>RTS</abbrev> and
<abbrev>CTS</abbrev> signals for flow-control at speeds above
2400bps, the <abbrev>CD</abbrev> signal to detect when a call
has been answered or the line has been hung up, and the
<acronym>DTR</acronym> signal to reset the modem after a session
<abbrev>DTR</abbrev> signal to reset the modem after a session
is complete. Some cables are wired without all of the needed
signals, so if you have problems, such as a login session not
going away when the line hangs up, you may have a problem with
@ -17985,7 +17985,7 @@
</para>
<para>When a user dials the modem's line and the modems connect, the
<acronym>CD</acronym> line is asserted by the modem. The kernel
<abbrev>CD</abbrev> line is asserted by the modem. The kernel
notices that carrier has been detected and completes <command>getty</command>'s open of the port. <command>getty</command> sends a <emphasis
remap=tt>login:</emphasis> prompt at the specified initial line
speed. <command>getty</command> watches to see if
@ -18142,13 +18142,13 @@
files. (The manual page for <command>MAKEDEV(8)</command> on
FreeBSD 1.1.5 is fairly bogus in its discussion of
<acronym>COM</acronym> ports, so ignore it.) To use
<acronym>MAKEDEV</acronym> to make dialup device special files
<filename>MAKEDEV</filename> to make dialup device special files
for <filename>COM1:</filename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue
the command <command>MAKEDEV ttyd0</command>.
Likewise, to make dialup device special files for
<filename>COM2:</filename> (port 1), use <command>MAKEDEV ttyd1</command>.</para>
<para><acronym>MAKEDEV</acronym> not only creates the
<para><filename>MAKEDEV</filename> not only creates the
<filename>/dev/ttyd?</filename> device special files, but also
creates the <filename>/dev/cua0?</filename> (and all of the
initializing and locking special files under FreeBSD 1.1.5 and
@ -18513,18 +18513,18 @@
<itemizedlist>
<listitem>
<para> <acronym>CD</acronym> asserted when connected
<para> <abbrev>CD</abbrev> asserted when connected
</para>
</listitem>
<listitem>
<para> <acronym>DTR</acronym> asserted for operation; dropping
<para> <abbrev>DTR</abbrev> asserted for operation; dropping
DTR hangs up line &amp; resets modem
</para>
</listitem>
<listitem>
<para> <acronym>CTS</acronym> transmitted data flow control
<para> <abbrev>CTS</abbrev> transmitted data flow control
</para>
</listitem>
@ -18534,7 +18534,7 @@
</listitem>
<listitem>
<para> <acronym>RTS</acronym> received data flow control
<para> <abbrev>RTS</abbrev> received data flow control
</para>
</listitem>
@ -18674,7 +18674,7 @@
command <emphasis remap=tt>ATI5</emphasis> displays the settings
that are stored in the non-volatile RAM. To see the true
operating parameters of the modem (as influenced by the USR's
DIP switch settings), use the commands <acronym>ATZ</acronym>
DIP switch settings), use the commands <command>ATZ</command>
and then <emphasis remap=tt>ATI4</emphasis>.</para>
<para>If you have a different brand of modem, check your modem's
@ -18696,14 +18696,14 @@
<para>Hook up your modem to your FreeBSD system, boot the system,
and, if your modem has status indication lights, watch to see
whether the modem's <acronym>DTR</acronym> indicator lights when
whether the modem's <abbrev>DTR</abbrev> indicator lights when
the <emphasis remap=tt>login:</emphasis> prompt appears on the
system's console - if it lights up, that should mean that
FreeBSD has started a <command>getty</command>
process on the appropriate communications port and is waiting
for the modem to accept a call.</para>
<para>If the <acronym>DTR</acronym> indicator doesn't light, login
<para>If the <abbrev>DTR</abbrev> indicator doesn't light, login
to the FreeBSD system through the console and issue a <command>ps ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port.
You should see a lines like this among the processes
@ -18731,7 +18731,7 @@
<command>getty</command> has completed its open on
the communications port. This could indicate a problem with the
cabling or a mis-configured modem, because <command>getty</command> should not be able to open the
communications port until <acronym>CD</acronym> (carrier detect)
communications port until <abbrev>CD</abbrev> (carrier detect)
has been asserted by the modem.</para>
<para>If you do not see any <command>getty</command>
@ -18759,7 +18759,7 @@
prompt right away, or get garbage, try pressing <emphasis
remap=tt>&lt;Enter&gt;</emphasis> about once per second. If
you still do not see a <emphasis remap=tt>login:</emphasis>
prompt after a while, try sending a <acronym>BREAK</acronym>.
prompt after a while, try sending a <command>BREAK</command>.
If you are using a high-speed modem to do the dialing, try
dialing again after locking the dialing modem's interface speed
(via <emphasis remap=tt>AT&amp;B1</emphasis> on a USR Sportster,
@ -18797,9 +18797,9 @@
<para>If you dial but the modem on the FreeBSD system will not
answer, make sure that the modem is configured to answer the
phone when <acronym>DTR</acronym> is asserted. If the modem
phone when <abbrev>DTR</abbrev> is asserted. If the modem
seems to be configured correctly, verify that the
<acronym>DTR</acronym> line is asserted by checking the modem's
<abbrev>DTR</abbrev> line is asserted by checking the modem's
indicator lights (if it has any).</para>
<para>If you have gone over everything several times and it still
@ -19187,7 +19187,7 @@
<listitem>
<para>The IP addresses of one or more nameservers. Normally,
you will be given two IP numbers. You
<acronym>MUST</acronym> have this information unless you run
<emphasis>MUST</emphasis> have this information unless you run
your own nameserver.</para>
</listitem>
@ -20161,7 +20161,7 @@
correct name), and <emphasis remap=tt>MyPassword</emphasis> is
the unencrypted password that you wish to use.
<filename>/etc/ppp/ppp.secret</filename> should
<acronym>NOT</acronym> be accessable by anyone without user id
<emphasis>NOT</emphasis> be accessable by anyone without user id
0. This means that <filename>/</filename>,
<filename>/etc</filename> and <filename>/etc/ppp</filename>
should not be writable, and <filename>ppp.secret</filename>
@ -21115,7 +21115,7 @@
have to edit the <filename>/etc/rc.conf</filename> file (called
<filename>/etc/sysconfig</filename> in FreeBSD releases prior to
2.2.2) and change the setting of the <emphasis
remap=bf>gateway</emphasis> variable to <acronym>YES</acronym>.
remap=bf>gateway</emphasis> variable to <option>YES</option>.
If you have an older system which predates even the
<filename>/etc/sysconfig</filename> file, then add the following
command: <literallayout>sysctl -w net.inet.ip.forwarding =
@ -22755,7 +22755,7 @@
</para>
<para>Do not panic, this is only a few hundred kilobytes in size.
The file <acronym>README</acronym> in the <emphasis
The file <filename>README</filename> in the <emphasis
remap=tt>cf</emphasis> directory can serve as a basic
introduction to m4 configuration.</para>
@ -22885,7 +22885,7 @@
``mumble.bar.edu'', instead of just ``mumble''. </para>
<para>Traditionally, this was allowed by BSD BIND resolvers. However
the current version of <acronym>BIND</acronym> that ships with
the current version of <application>BIND</application> that ships with
FreeBSD no longer provides default abbreviations for non-fully
qualified domain names other than the domain you are in. So an
unqualified host <emphasis remap=tt>mumble</emphasis> must either
@ -23083,7 +23083,7 @@
</sect2>
<sect2>
<title>What is FreeBSD-current <acronym>NOT</acronym>?</title>
<title>What is FreeBSD-current <emphasis>NOT</emphasis>?</title>
<para>
<orderedlist>
@ -23378,7 +23378,7 @@
the fly by the server, according to what you have and what you want
to have.</para>
<para><acronym>CTM</acronym>, on the other hand, does not
<para><application>CTM</application>, on the other hand, does not
interactively compare the sources you have with those on the master
archive. Instead, a script which identifies changes in files since
its previous run is executed several times a day on the master
@ -23409,26 +23409,26 @@
<para><emphasis>Contributed by &a.phk;. Updated
19-October-1997.</emphasis></para>
<para><acronym>CTM</acronym> is a method for keeping a remote
<para><application>CTM</application> is a method for keeping a remote
directory tree in sync with a central one. It has been developed
for usage with FreeBSD's source trees, though other people may
find it useful for other purposes as time goes by. Little, if
any, documentation currently exists at this time on the process of
creating deltas, so talk to &a.phk; for more information should
you wish to use <acronym>CTM</acronym> for other things.</para>
you wish to use <application>CTM</application> for other things.</para>
<sect3>
<title>Why should I use <acronym>CTM</acronym>?</title>
<title>Why should I use <application>CTM</application>?</title>
<para><acronym>CTM</acronym> will give you a local copy of the
<para><application>CTM</application> will give you a local copy of the
FreeBSD source trees. There are a number of <quote>flavors</quote> of the
tree available. Whether you wish to track the entire cvs tree or
just one of the branches, <acronym>CTM</acronym> can provide you
just one of the branches, <application>CTM</application> can provide you
the information. If you are an active developer on FreeBSD, but
have lousy or non-existent TCP/IP connectivity, or simply wish
to have the changes automatically sent to you,
<acronym>CTM</acronym> was made for you. You will need to obtain
<application>CTM</application> was made for you. You will need to obtain
up to three deltas per day for the most active branches.
However, you should consider having them sent by automatic
email. The sizes of the updates are always kept as small as
@ -23447,28 +23447,28 @@
</sect3>
<sect3>
<title>What do I need to use <acronym>CTM</acronym>?</title>
<title>What do I need to use <application>CTM</application>?</title>
<para>You will need two things: The ``<acronym>CTM</acronym>''
<para>You will need two things: The ``<application>CTM</application>''
program and the initial deltas to feed it (to get up to
<quote>current</quote> levels).</para>
<para>The <acronym>CTM</acronym> program has been part of FreeBSD
<para>The <application>CTM</application> program has been part of FreeBSD
ever since version 2.0 was released, and lives in
<filename>/usr/src/usr.sbin/<acronym>CTM</acronym></filename> if
<filename>/usr/src/usr.sbin/CTM</filename> if
you have a copy of the source online.</para>
<para>If you are running a pre-2.0 version of FreeBSD, you can
fetch the current <acronym>CTM</acronym> sources directly
fetch the current <application>CTM</application> sources directly
from:</para>
<para><ulink
URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm</ulink></para>
<para>The <quote>deltas</quote> you feed <acronym>CTM</acronym> can be had
<para>The <quote>deltas</quote> you feed <application>CTM</application> can be had
two ways, FTP or e-mail. If you have general FTP access to the
Internet then the following FTP sites support access to
<acronym>CTM</acronym>:</para>
<application>CTM</application>:</para>
<para><ulink
URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/CTM">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/CTM</ulink></para>
@ -23477,12 +23477,12 @@
remap="mirrors">.</para>
<para>FTP the relevant directory and fetch the
<acronym>README</acronym> file, starting from there.</para>
<filename>README</filename> file, starting from there.</para>
<para>If you may wish to get your deltas via email:</para>
<para>Send email to &a.majordomo; to subscribe to one of the
<acronym>CTM</acronym> distribution lists. ``ctm-cvs-cur''
<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
release branch, etc. (If you do not know how to subscribe
@ -23490,7 +23490,7 @@
word ``help'' - it will send you back usage
instructions.)</para>
<para>When you begin receiving your <acronym>CTM</acronym> updates
<para>When you begin receiving your <application>CTM</application> updates
in the mail, you may use the <symbol>ctm_rmail</symbol> program
to unpack and apply them. You can actually use the
<symbol>ctm_rmail</symbol> program directly from a entry in
@ -23500,10 +23500,10 @@
<note>
<para>No matter what method you use to get the
<acronym>CTM</acronym> deltas, you should subscribe to the
<application>CTM</application> deltas, you should subscribe to the
<email>ctm-announce@FreeBSD.ORG</email> mailing list. In the
future, this will be the only place where announcements
concerning the operations of the <acronym>CTM</acronym> system
concerning the operations of the <application>CTM</application> system
will be posted. Send an email to &a.majordomo; with a single
line of ``<emphasis remap=tt>subscribe
ctm-announce</emphasis>'' to get added to the list.</para>
@ -23511,10 +23511,10 @@
</sect3>
<sect3>
<title>Starting off with <acronym>CTM</acronym> for the first
<title>Starting off with <application>CTM</application> for the first
time</title>
<para>Before you can start using <acronym>CTM</acronym> deltas,
<para>Before you can start using <application>CTM</application> deltas,
you will need to get a to a starting point for the deltas
produced subsequently to it.</para>
@ -23527,7 +23527,7 @@
<para>Once you identify a suitable starting point, you must use an
initial <quote>transition</quote> delta to transform your starting point
into a <acronym>CTM</acronym> supported tree.</para>
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
@ -23546,7 +23546,7 @@
</sect3>
<sect3>
<title>Using <acronym>CTM</acronym> in your daily life</title>
<title>Using <application>CTM</application> in your daily life</title>
<para>To apply the deltas, simply say:
<informalexample>
@ -23556,18 +23556,18 @@
</informalexample>
</para>
<para><acronym>CTM</acronym> understands deltas which have been
<para><application>CTM</application> understands deltas which have been
put through <command>gzip</command>, so you do not
need to gunzip them first, this saves disk space.</para>
<para>Unless it feels very secure about the entire process,
<acronym>CTM</acronym> will not touch your tree. To verify a
<application>CTM</application> will not touch your tree. To verify a
delta you can also use the <option>-c</option> flag and
<acronym>CTM</acronym> will not actually touch your tree; it
<application>CTM</application> will not actually touch your tree; it
will merely verify the integrity of the delta and see if it
would apply cleanly to your current tree.</para>
<para>There are other options to <acronym>CTM</acronym> as well,
<para>There are other options to <application>CTM</application> as well,
see the manual pages or look in the sources for more
information.</para>
@ -23577,7 +23577,7 @@
when...</para>
<para>That's really all there is to it. Every time you get a new
delta, just run it through <acronym>CTM</acronym> to keep your
delta, just run it through <application>CTM</application> to keep your
sources up to date.</para>
<para>Do not remove the deltas if they are hard to download again.
@ -23668,7 +23668,7 @@
</sect3>
<sect3>
<title>Future plans for <acronym>CTM</acronym></title>
<title>Future plans for <application>CTM</application></title>
<para>Tons of them:
<itemizedlist>
@ -23679,7 +23679,7 @@
</listitem>
<listitem>
<para>Clean up the options to <acronym>CTM</acronym>, they
<para>Clean up the options to <application>CTM</application>, they
became confusing and counter intuitive.</para>
</listitem>
@ -26227,7 +26227,7 @@
<para>This is <emphasis>not</emphasis> a manual nor an
in-depth description on how to use or compile the port. In
particular, <emphasis>please do not just copy the
<acronym>README</acronym> file here</emphasis>, unless,
<filename>README</filename> file here</emphasis>, unless,
of course, it is a concise description of the port.</para>
</note>
@ -26579,9 +26579,9 @@
<para>If your port requires user input to build, configure or
install, then set <symbol>IS_INTERACTIVE</symbol> in your
Makefile. This will allow `overnight builds' to skip your port
if the user sets the variable <acronym>BATCH</acronym> in his
if the user sets the variable <envar>BATCH</envar> in his
environment (and if the user sets the variable
<acronym>INTERACTIVE</acronym>, then <emphasis>only</emphasis>
<envar>INTERACTIVE</envar>, then <emphasis>only</emphasis>
those ports requiring interaction are built).</para>
</sect4>
@ -31196,7 +31196,7 @@
kernel (but stripped of the debugging information).</para>
<para>You should configure the kernel in question with <command>config
-g</command>, include <acronym>DDB</acronym> into the
-g</command>, include <option>DDB</option> into the
configuration, and compile it as usual. This gives a large blurb of
a binary, due to the debugging information. Copy this kernel to the
target machine, strip the debugging symbols off with <command>strip