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

Created a new set of entities for manual pages.

Browse source 
The construct:

    <citerefentry>
      <refentrytitle>foobar</refentrytitle>
      <manvolnum>1</manvolnum>
    </citerefentry>

is a pain to type, and messes up the pretty-printing of the source code.
Replace every occurence of a entry like that with:

    &man.foobar.1;

Adjusting the manual page name and section number appropriately.

The definitions for these entities are stored in man-refs.ent. This
file is in doc/share/sgml because it is not just specific to the Handbook.
I expect the DocBook'd FAQ and Tutorials (coming RSN) to use them as
well.

A new PUBLIC identifier has been created for these entities, and added to
the catalog file.
This commit is contained in:
Nik Clayton 1999-03-07 16:32:22 +00:00
parent 1c05a644f3
commit 62a7d13816
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=4471
64 changed files with 1392 additions and 2015 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
en/handbook/advanced-networking/chapter.sgml
View file

@ -311,18 +311,18 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
<para>Sometimes, there is a problem with routing propagation, and
some sites are unable to connect to you. Perhaps the most useful
command for trying to figure out where a routing is breaking down
is the <citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. It is equally
is the &man.traceroute.8; command. It is equally
useful if you cannot seem to make a connection to a remote machine
(ie. <citerefentry><refentrytitle>ping</refentrytitle><manvolnum>8</manvolnum></citerefentry> fails).</para>
(i.e. &man.ping.8; fails).</para>
<para>The <citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry> command is run with the
<para>The &man.traceroute.8; command is run with the
name of the remote host you are trying to connect to. It will show
the gateway hosts along the path of the attempt, eventually either
reaching the target host, or terminating because of a lack of
connection.</para>
<para>For more information, see the manual page for
<citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
&man.traceroute.8;.</para>
</sect2>
</sect1>

201
en/handbook/backups/chapter.sgml
View file

@ -179,14 +179,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>Use the front panel button to eject the tape.</para>
<para>Re-insert the tape and
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> data to the tape.</para>
&man.dump.8; data to the tape.</para>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> will report <literal>DUMP:
<para>&man.dump.8; will report <literal>DUMP:
End of tape detected</literal> and the console will show:
<literal>HARDWARE FAILURE info:280 asc:80,96</literal></para>
@ -200,75 +195,35 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<title>Backup Programs</title>
<para>The three major programs are
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>,
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>,
&man.dump.8;,
&man.tar.1;,
and
<citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>.</para>
&man.cpio.1;.</para>
<sect2>
<title>Dump and Restore</title>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>restore</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> are the traditional Unix backup programs. They operate
<para>&man.dump.8; and &man.restore.8; are the traditional Unix backup programs. They operate
on the drive as a collection of disk blocks, below the abstractions of
files, links and directories that are created by the filesystems.
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> backs up devices, entire filesystems, not parts of a
&man.dump.8; backs up devices, entire filesystems, not parts of a
filesystem and not directory trees that span more than one filesystem,
using either soft links <citerefentry>
<refentrytitle>ln</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> or mounting one filesystem onto another.
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> does not write files and directories to tape, but
using either soft links &man.ln.1; or mounting one filesystem onto another.
&man.dump.8; does not write files and directories to tape, but
rather writes the data blocks that are the building blocks of files
and directories. <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> has quirks that remain from its early days in
and directories. &man.dump.8; has quirks that remain from its early days in
Version 6 of ATT Unix (circa 1975). The default parameters are
suitable for 9-track tapes (6250 bpi), not the high-density media
available today (up to 62,182 ftpi). These defaults must be overridden
on the command line to utilize the capacity of current tape
drives.</para>
<para><citerefentry>
<refentrytitle>rdump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>rrestore</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> backup data across the
<para>&man.rdump.8; and &man.rrestore.8; backup data across the
network to a tape drive attached to another computer. Both programs
rely upon <citerefentry>
<refentrytitle>rcmd</refentrytitle>
<manvolnum>3</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>ruserok</refentrytitle>
<manvolnum>3</manvolnum></citerefentry> to access the remote tape
rely upon &man.rcmd.3; and &man.ruserok.3; to access the remote tape
drive. Therefore, the user performing the backup must have
<literal>rhosts</literal> access to the remote computer. The
arguments to <citerefentry>
<refentrytitle>rdump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>rrestore</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> must suitable to use on the remote computer. (e.g.
arguments to &man.rdump.8; and &man.rrestore.8; must suitable to use on the remote computer. (e.g.
When <command>rdump</command>'ing from a FreeBSD computer to an
Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000
@ -280,95 +235,52 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect2>
<title>Tar</title>
<para><citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> also dates back to Version 6 of ATT Unix (circa
1975). <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> operates in cooperation with the filesystem;
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> writes files and directories to tape.
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> does not support the full range of options that are
available from <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>, but <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not require the
unusual command pipeline that <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> uses.</para>
<para>&man.tar.1; also dates back to Version 6 of ATT Unix (circa
1975). &man.tar.1; operates in cooperation with the filesystem;
&man.tar.1; writes files and directories to tape.
&man.tar.1; does not support the full range of options that are
available from &man.cpio.1;, but &man.tar.1; does not require the
unusual command pipeline that &man.cpio.1; uses.</para>
<para>Most versions of <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> do not support backups across the network. The GNU
version of <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>, which FreeBSD utilizes,
<para>Most versions of &man.tar.1; do not support backups across the network. The GNU
version of &man.tar.1;, which FreeBSD utilizes,
supports remote devices using the same syntax as
<command>rdump</command>. To <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> to an Exabyte tape drive connected to a Sun called
komodo, use: <command>/usr/bin/tar cf komodo:/dev/nrst8 .
&man.rdump.8;. To &man.tar.1; to an Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/usr/bin/tar cf komodo:/dev/nrst8 .
2>&amp;1</command>. For versions without remote device support,
you can use a pipeline and <citerefentry>
<refentrytitle>rsh</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> to send the data to a
you can use a pipeline and &man.rsh.1; to send the data to a
remote tape drive. (XXX add an example command)</para>
</sect2>
<sect2>
<title>Cpio</title>
<para><citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> is the original Unix
file interchange tape program for magnetic media. <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> has options (among many
<para>&man.cpio.1; is the original Unix
file interchange tape program for magnetic media. &man.cpio.1; has options (among many
others) to perform byte-swapping, write a number of different
archives format, and pipe the data to other programs. This last
feature makes <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> and excellent choice for
installation media. <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not know how to walk
feature makes &man.cpio.1; and excellent choice for
installation media. &man.cpio.1; does not know how to walk
the directory tree and a list of files must be provided thru
<filename>STDIN</filename>.</para>
<para><citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not support backups
across the network. You can use a pipeline and <citerefentry>
<refentrytitle>rsh</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> to send the data to a
<para>&man.cpio.1; does not support backups
across the network. You can use a pipeline and &man.rsh.1; to send the data to a
remote tape drive. (XXX add an example command)</para>
</sect2>
<sect2>
<title>Pax</title>
<para><citerefentry>
<refentrytitle>pax</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> is IEEE/POSIX's answer to
<command>tar</command> and <command>cpio</command>. Over the years the
various versions of <command>tar</command> and <command>cpio</command>
<para>&man.pax.1; is IEEE/POSIX's answer to
&man.tar.1; and &man.cpio.1;. Over the years the
various versions of &man.tar.1; and &man.cpio.1;
have gotten slightly incompatible. So rather than fight it out to
fully standardize them, POSIX created a new archive utility.
<command>pax</command> attempts to read and write many of the various
cpio and tar formats, plus new formats of its own. Its command set
more resembles <command>cpio</command> than
<command>tar</command>.</para>
&man.pax.1; attempts to read and write many of the various
&man.cpio.1; and &man.tar.1; formats, plus new formats of its own. Its command set
more resembles &man.cpio.1; than
&man.tar.1;.</para>
</sect2>
<sect2 id="backups-programs-amanda">
@ -422,14 +334,10 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect2>
<title>Which Backup Program is Best?</title>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> <emphasis>Period.</emphasis>
<para>&man.dump.8; <emphasis>Period.</emphasis>
Elizabeth D. Zwicky torture tested all the backup programs discussed
here. The clear choice for preserving all your data and all the
peculiarities of Unix filesystems is <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>. Elizabeth created
peculiarities of Unix filesystems is &man.dump.8;. Elizabeth created
filesystems containing a large variety of unusual conditions (and some
not so unusual ones) and tested each program by do a backup and
restore of that filesystems. The peculiarities included: files with
@ -465,22 +373,10 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>Otherwise, you have to create two custom bootable floppies
which has a kernel that can mount your all of your disks and
access your tape drive. These floppies must contain:
<citerefentry>
<refentrytitle>fdisk</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>disklabel</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>newfs</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>mount</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, and whichever backup
&man.fdisk.8;, &man.disklabel.8;, &man.newfs.8;, &man.mount.8;, and whichever backup
program you use. These programs must be statically linked. If you
use <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, the floppy must contain
<citerefentry>
<refentrytitle>restore</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>.</para>
use &man.dump.8;, the floppy must contain
&man.restore.8;.</para>
<para>Third, create backup tapes regularly. Any changes that you make
after your last backup may be irretrievably lost. Write-protect the
@ -686,18 +582,11 @@ chmod 644 /mnt/etc/passwd
<para>Recover each filesystem separately.</para>
<para>Try to <citerefentry>
<refentrytitle>mount</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry>(e.g. <command>mount /dev/sd0a
<para>Try to &man.mount.8; (e.g. <command>mount /dev/sd0a
/mnt</command>) the root partition of your first disk. If the
disklabel was damaged, use <citerefentry>
<refentrytitle>disklabel</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> to re-partition and
disklabel was damaged, use &man.disklabel.8; to re-partition and
label the disk to match the label that your printed and saved. Use
<citerefentry>
<refentrytitle>newfs</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> to re-create the
&man.newfs.8; to re-create the
filesystems. Re-mount the root partition of the floppy read-write
(<command>mount -u -o rw /mnt</command>). Use your backup program
and backup tapes to recover the data for this filesystem (e.g.

6
en/handbook/basics/chapter.sgml
View file

@ -76,9 +76,9 @@
<para>This will display the manual page for the user
command <command>chmod</command>. References to a
particular section of the on-line manual are traditionally placed in
parenthesis in written documentation, so <citerefentry><refentrytitle>chmod</refentrytitle><manvolnum>1</manvolnum></citerefentry> refers to the
parenthesis in written documentation, so &man.chmod.1; refers to the
<command>chmod</command>
user command and <citerefentry><refentrytitle>chmod</refentrytitle><manvolnum>2</manvolnum></citerefentry> refers to the
user command and &man.chmod.2; refers to the
system call.</para>
<para>This is fine if you know the name of the command and simply wish
@ -122,7 +122,7 @@
<command>info</command> command or, if you installed
<command>emacs</command>, the info mode of <command>emacs</command>.</para>
<para>To use the <citerefentry><refentrytitle>info</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, simply type:</para>
<para>To use the &man.info.1; command, simply type:</para>
<screen>&prompt.user; <userinput>info</userinput></screen>

1
en/handbook/boothelp.sgml
View file

@ -2,6 +2,7 @@
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
<!ENTITY % authors SYSTEM "authors.ent"> %authors;
<!ENTITY % mailing-lists SYSTEM "mailing-lists.ent"> %mailing-lists;
<!ENTITY % newsgroups SYSTEM "newsgroups.ent"> %newsgroups;
<!ENTITY % boothelp.only "INCLUDE">
<!ENTITY % handbook.only "IGNORE">

224
en/handbook/contrib/chapter.sgml
View file

@ -458,12 +458,12 @@
information about this and other mailing lists.</para>
<para>If you find a bug or are submitting a specific change, please
report it using the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>program or its
report it using the &man.send-pr.1; program or its
<ulink URL="http://www.freebsd.org/send-pr.html">WEB-based
equivalent</ulink>. Try to fill-in each field of the bug report.
Unless they exceed 65KB, include any patches directly in the
report. Consider compressing them and using
<citerefentry><refentrytitle>uuencode</refentrytitle><manvolnum>1</manvolnum></citerefentry> if they exceed 20KB. Upload very large submissions to <ulink url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp.freebsd.org:/pub/FreeBSD/incoming/</ulink>.</para>
&man.uuencode.1; if they exceed 20KB. Upload very large submissions to <ulink url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp.freebsd.org:/pub/FreeBSD/incoming/</ulink>.</para>
<para>After filing a report, you should receive confirmation along
with a tracking number. Keep this tracking number so that you can
@ -471,7 +471,7 @@
<para>If you do not receive confirmation in a timely fashion (3 days
to a week, depending on your email connection) or are, for some
reason, unable to use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> command,
reason, unable to use the &man.send-pr.1; command,
then you may ask someone to file it for you by sending mail to the
&a.bugs;.</para>
@ -511,7 +511,7 @@
<para>Assuming that you can manage to secure fairly up-to-date
sources to base your changes on, the next step is to produce a set
of diffs to send to the FreeBSD maintainers. This is done with
the <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, with the &ldquo;context diff&rdquo;
the &man.diff.1; command, with the &ldquo;context diff&rdquo;
form being preferred. For example:</para>
<para>
@ -526,11 +526,11 @@
would generate such a set of context diffs for
the given source file or directory hierarchy. See the man page
for <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> for more details.</para>
for &man.diff.1; for more details.</para>
<para>Once you have a set of diffs (which you may test with the
<citerefentry><refentrytitle>patch</refentrytitle><manvolnum>1</manvolnum></citerefentry> command), you should submit them for
inclusion with FreeBSD. Use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
&man.patch.1; command), you should submit them for
inclusion with FreeBSD. Use the &man.send-pr.1;
program as described in
<link linkend="contrib-general">Bug Reports and General
Commentary</link>. <emphasis>Do not</emphasis> just send the diffs to
@ -541,14 +541,14 @@
<para>If you feel it appropriate (e.g. you have added, deleted, or
renamed files), bundle your changes into a <command>tar</command> file and run the
<citerefentry><refentrytitle>uuencode</refentrytitle><manvolnum>1</manvolnum></citerefentry> program on it. Shar archives are
&man.uuencode.1; program on it. Shar archives are
also welcome.</para>
<para>If your change is of a potentially sensitive nature, e.g. you
are unsure of copyright issues governing its further distribution
or you are simply not ready to release it without a tighter review
first, then you should send it to &a.core; directly rather than
submitting it with <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The core
submitting it with &man.send-pr.1;. The core
mailing list reaches a much smaller group of people who do much of
the day-to-day work on FreeBSD. Note that this group is also
<emphasis>very busy</emphasis> and so you should only send mail to
@ -1143,9 +1143,9 @@ box can be opened)</para>
<listitem><para>Adrian Mariano <email>adrian@cam.cornell.edu</email></para></listitem>
<listitem><para>Adrian Steinmann <email>ast@marabu.ch</email></para></listitem>
<listitem><para>Adrian T. Filipi-Martin <email>atf3r@agate.cs.virginia.edu</email></para></listitem>
<listitem><para>Ajit Thyagarajan</para></listitem>
<listitem><para>Ajit Thyagarajan <email>unknown</email></para></listitem>
<listitem><para>Akio Morita <email>amorita@meadow.scphys.kyoto-u.ac.jp</email></para></listitem>
<listitem><para>Akira SAWADA</para></listitem>
<listitem><para>Akira SAWADA <email>unknown</email></para></listitem>
<listitem><para>Akira Watanabe <email>akira@myaw.ei.meisei-u.ac.jp</email></para></listitem>
<listitem><para>Akito Fujita <email>fujita@zoo.ncl.omron.co.jp</email></para></listitem>
<listitem><para>Alain Kalker <email>A.C.P.M.Kalker@student.utwente.nl</email></para></listitem>
@ -1177,10 +1177,10 @@ box can be opened)</para>
<listitem><para>Andreas Haakh <email>ah@alman.robin.de</email></para></listitem>
<listitem><para>Andreas Kohout <email>shanee@rabbit.augusta.de</email></para></listitem>
<listitem><para>Andreas Lohr <email>andreas@marvin.RoBIN.de</email></para></listitem>
<listitem><para>Andreas Schulz</para></listitem>
<listitem><para>Andreas Schulz <email>unknown</email></para></listitem>
<listitem><para>Andreas Wetzel <email>mickey@deadline.snafu.de</email></para></listitem>
<listitem><para>Andreas Wrede <email>andreas@planix.com</email></para></listitem>
<listitem><para>Andres Vega Garcia</para></listitem>
<listitem><para>Andres Vega Garcia <email>unknown</email></para></listitem>
<listitem><para>Andrew Atrens <email>atreand@statcan.ca</email></para></listitem>
<listitem><para>Andrew Gillham <email>gillham@andrews.edu</email></para></listitem>
<listitem><para>Andrew Gordon <email>andrew.gordon@net-tel.co.uk</email></para></listitem>
@ -1212,7 +1212,7 @@ box can be opened)</para>
<listitem><para>Barry Bierbauch <email>pivrnec@vszbr.cz</email></para></listitem>
<listitem><para>Barry Lustig <email>barry@ictv.com</email></para></listitem>
<listitem><para>Ben Hutchinson <email>benhutch@xfiles.org.uk</email></para></listitem>
<listitem><para>Ben Jackson</para></listitem>
<listitem><para>Ben Jackson <email>unknown</email></para></listitem>
<listitem><para>Ben Smithurst <email>ben@scientia.demon.co.uk</email></para></listitem>
<listitem><para>Ben Walter <email>bwalter@itachi.swcp.com</email></para></listitem>
<listitem><para>Benjamin Lewis <email>bhlewis@gte.net</email></para></listitem>
@ -1264,7 +1264,7 @@ box can be opened)</para>
<listitem><para>Chet Ramey <email>chet@odin.INS.CWRU.Edu</email></para></listitem>
<listitem><para>Chia-liang Kao <email>clkao@CirX.ORG</email></para></listitem>
<listitem><para>Chiharu Shibata <email>chi@bd.mbn.or.jp</email></para></listitem>
<listitem><para>Chip Norkus</para></listitem>
<listitem><para>Chip Norkus <email>unknown</email></para></listitem>
<listitem><para>Choi Jun Ho <email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para>Chris Csanady <email>cc@tarsier.ca.sandia.gov</email></para></listitem>
<listitem><para>Chris Dabrowski <email>chris@vader.org</email></para></listitem>
@ -1291,7 +1291,7 @@ box can be opened)</para>
<listitem><para>Cornelis van der Laan <email>nils@guru.ims.uni-stuttgart.de</email></para></listitem>
<listitem><para>Cove Schneider <email>cove@brazil.nbn.com</email></para></listitem>
<listitem><para>Craig Leres <email>leres@ee.lbl.gov</email></para></listitem>
<listitem><para>Craig Loomis</para></listitem>
<listitem><para>Craig Loomis <email>unknown</email></para></listitem>
<listitem><para>Craig Metz <email>cmetz@inner.net</email></para></listitem>
<listitem><para>Craig Spannring <email>cts@internetcds.com</email></para></listitem>
<listitem><para>Craig Struble <email>cstruble@vt.edu</email></para></listitem>
@ -1310,7 +1310,7 @@ box can be opened)</para>
<listitem><para>Daniel O'Connor <email>doconnor@gsoft.com.au</email></para></listitem>
<listitem><para>Daniel Poirot <email>poirot@aio.jsc.nasa.gov</email></para></listitem>
<listitem><para>Daniel Rock <email>rock@cs.uni-sb.de</email></para></listitem>
<listitem><para>Danny Egen</para></listitem>
<listitem><para>Danny Egen <email>unknown</email></para></listitem>
<listitem><para>Danny J. Zerkel <email>dzerkel@phofarm.com</email></para></listitem>
<listitem><para>Darren Reed <email>avalon@coombs.anu.edu.au</email></para></listitem>
<listitem><para>Dave Adkins <email>adkin003@tc.umn.edu</email></para></listitem>
@ -1344,7 +1344,7 @@ box can be opened)</para>
<listitem><para>David Wolfskill <email>dhw@whistle.com</email></para></listitem>
<listitem><para>Dean Gaudet <email>dgaudet@arctic.org</email></para></listitem>
<listitem><para>Dean Huxley <email>dean@fsa.ca</email></para></listitem>
<listitem><para>Denis Fortin</para></listitem>
<listitem><para>Denis Fortin <email>unknown</email></para></listitem>
<listitem><para>Dennis Glatting <email>dennis.glatting@software-munitions.com</email></para></listitem>
<listitem><para>Denton Gentry <email>denny1@home.com</email></para></listitem>
<listitem><para>Derek Inksetter <email>derek@saidev.com</email></para></listitem>
@ -1450,7 +1450,7 @@ box can be opened)</para>
<listitem><para>Harold Barker <email>hbarker@dsms.com</email></para></listitem>
<listitem><para>Havard Eidnes <email>Havard.Eidnes@runit.sintef.no</email></para></listitem>
<listitem><para>Heikki Suonsivu <email>hsu@cs.hut.fi</email></para></listitem>
<listitem><para>Heiko W. Rupp</para></listitem>
<listitem><para>Heiko W. Rupp <email>unknown</email></para></listitem>
<listitem><para>Helmut F. Wirth <email>hfwirth@ping.at</email></para></listitem>
<listitem><para>Henrik Vestergaard Draboel <email>hvd@terry.ping.dk</email></para></listitem>
<listitem><para>Herb Peyerl <email>hpeyerl@NetBSD.org</email></para></listitem>
@ -1464,7 +1464,7 @@ box can be opened)</para>
<listitem><para>Hiroharu Tamaru <email>tamaru@ap.t.u-tokyo.ac.jp</email></para></listitem>
<listitem><para>Hironori Ikura <email>hikura@kaisei.org</email></para></listitem>
<listitem><para>Hiroshi Nishikawa <email>nis@pluto.dti.ne.jp</email></para></listitem>
<listitem><para>Hiroya Tsubakimoto</para></listitem>
<listitem><para>Hiroya Tsubakimoto <email>unknown</email></para></listitem>
<listitem><para>Hiroyuki NAKAJI <email>nakaji@zeisei3.dpri.kyoto-u.ac.jp</email></para></listitem>
<listitem><para>Holger Veit <email>Holger.Veit@gmd.de</email></para></listitem>
<listitem><para>Holm Tiffe <email>holm@geophysik.tu-freiberg.de</email></para></listitem>
@ -1527,7 +1527,7 @@ box can be opened)</para>
<listitem><para>Jeremy Allison <email>jallison@whistle.com</email></para></listitem>
<listitem><para>Jeremy Chatfield <email>jdc@xinside.com</email></para></listitem>
<listitem><para>Jeremy Lea <email>reg@shale.csir.co.za</email></para></listitem>
<listitem><para>Jeremy Prior</para></listitem>
<listitem><para>Jeremy Prior <email>unknown</email></para></listitem>
<listitem><para>Jeroen Ruigrok/Asmodai <email>asmodai@wxs.nl</email></para></listitem>
<listitem><para>Jesse Rosenstock <email>jmr@ugcs.caltech.edu</email></para></listitem>
<listitem><para>Jian-Da Li <email>jdli@csie.nctu.edu.tw</email></para></listitem>
@ -1543,7 +1543,7 @@ box can be opened)</para>
<listitem><para>Jim Wilson <email>wilson@moria.cygnus.com</email></para></listitem>
<listitem><para>Jimbo Bahooli <email>griffin@blackhole.iceworld.org</email></para></listitem>
<listitem><para>Jin Guojun <email>jin@george.lbl.gov</email></para></listitem>
<listitem><para>Joachim Kuebart</para></listitem>
<listitem><para>Joachim Kuebart <email>unknown</email></para></listitem>
<listitem><para>Joao Carlos Mendes Luis <email>jonny@jonny.eng.br</email></para></listitem>
<listitem><para>Jochen Pohl <email>jpo.drs@sni.de</email></para></listitem>
<listitem><para>Joe "Marcus" Clarke <email>marcus@miami.edu</email></para></listitem>
@ -1558,19 +1558,19 @@ box can be opened)</para>
<listitem><para>Johan Karlsson <email>k@numeri.campus.luth.se</email></para></listitem>
<listitem><para>Johan Larsson <email>johan@moon.campus.luth.se</email></para></listitem>
<listitem><para>Johann Tonsing <email>jtonsing@mikom.csir.co.za</email></para></listitem>
<listitem><para>Johannes Helander</para></listitem>
<listitem><para>Johannes Stille</para></listitem>
<listitem><para>Johannes Helander <email>unknown</email></para></listitem>
<listitem><para>Johannes Stille <email>unknown</email></para></listitem>
<listitem><para>John Baldwin <email>jobaldwi@vt.edu</email></para></listitem>
<listitem><para>John Beckett <email>jbeckett@southern.edu</email></para></listitem>
<listitem><para>John Beukema <email>jbeukema@hk.super.net</email></para></listitem>
<listitem><para>John Brezak</para></listitem>
<listitem><para>John Brezak <email>unknown</email></para></listitem>
<listitem><para>John Capo <email>jc@irbs.com</email></para></listitem>
<listitem><para>John F. Woods <email>jfw@jfwhome.funhouse.com</email></para></listitem>
<listitem><para>John Goerzen <email>jgoerzen@alexanderwohl.complete.org</email></para></listitem>
<listitem><para>John Hay <email>jhay@mikom.csir.co.za</email></para></listitem>
<listitem><para>John Heidemann <email>johnh@isi.edu</email></para></listitem>
<listitem><para>John Hood <email>cgull@owl.org</email></para></listitem>
<listitem><para>John Kohl</para></listitem>
<listitem><para>John Kohl <email>unknown</email></para></listitem>
<listitem><para>John Lind <email>john@starfire.mn.org</email></para></listitem>
<listitem><para>John Mackin <email>john@physiol.su.oz.au</email></para></listitem>
<listitem><para>John P <email>johnp@lodgenet.com</email></para></listitem>
@ -1620,10 +1620,10 @@ box can be opened)</para>
<listitem><para>Kazuo Horikawa <email>horikawa@jp.FreeBSD.org</email></para></listitem>
<listitem><para>Kees Jan Koster <email>kjk1@ukc.ac.uk</email></para></listitem>
<listitem><para>Keith Bostic <email>bostic@bostic.com</email></para></listitem>
<listitem><para>Keith E. Walker</para></listitem>
<listitem><para>Keith Moore</para></listitem>
<listitem><para>Keith Sklower</para></listitem>
<listitem><para>Ken Hornstein</para></listitem>
<listitem><para>Keith E. Walker <email>unknown</email></para></listitem>
<listitem><para>Keith Moore <email>unknown</email></para></listitem>
<listitem><para>Keith Sklower <email>unknown</email></para></listitem>
<listitem><para>Ken Hornstein <email>unknown</email></para></listitem>
<listitem><para>Ken Key <email>key@cs.utk.edu</email></para></listitem>
<listitem><para>Ken Mayer <email>kmayer@freegate.com</email></para></listitem>
<listitem><para>Kenji Saito <email>marukun@mx2.nisiq.net</email></para></listitem>
@ -1659,7 +1659,7 @@ box can be opened)</para>
<listitem><para>Louis Mamakos <email>loiue@TransSys.com</email></para></listitem>
<listitem><para>Lucas James <email>Lucas.James@ldjpc.apana.org.au</email></para></listitem>
<listitem><para>Lyndon Nerenberg <email>lyndon@orthanc.com</email></para></listitem>
<listitem><para>M.C. Wong</para></listitem>
<listitem><para>M.C. Wong <email>unknown</email></para></listitem>
<listitem><para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para></listitem>
<listitem><para>MIHIRA Sanpei Yoshiro <email>sanpei@sanpei.org</email></para></listitem>
<listitem><para>MITA Yoshio <email>mita@jp.FreeBSD.ORG</email></para></listitem>
@ -1677,7 +1677,7 @@ box can be opened)</para>
<listitem><para>Marc van Kempen <email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para>Marcel Moolenaar <email>marcel@scc.nl</email></para></listitem>
<listitem><para>Mario Sergio Fujikawa Ferreira <email>lioux@gns.com.br</email></para></listitem>
<listitem><para>Mark Andrews</para></listitem>
<listitem><para>Mark Andrews <email>unknown</email></para></listitem>
<listitem><para>Mark Cammidge <email>mark@gmtunx.ee.uct.ac.za</email></para></listitem>
<listitem><para>Mark Diekhans <email>markd@grizzly.com</email></para></listitem>
<listitem><para>Mark Huizer <email>xaa@stack.nl</email></para></listitem>
@ -1686,7 +1686,7 @@ box can be opened)</para>
<listitem><para>Mark Mayo <email>markm@vmunix.com</email></para></listitem>
<listitem><para>Mark Thompson <email>thompson@tgsoft.com</email></para></listitem>
<listitem><para>Mark Tinguely <email>tinguely@plains.nodak.edu</email></para></listitem>
<listitem><para>Mark Treacy</para></listitem>
<listitem><para>Mark Treacy <email>unknown</email></para></listitem>
<listitem><para>Mark Valentine <email>mark@linus.demon.co.uk</email></para></listitem>
<listitem><para>Martin Birgmeier</para></listitem>
<listitem><para>Martin Ibert <email>mib@ppe.bb-data.de</email></para></listitem>
@ -1694,7 +1694,7 @@ box can be opened)</para>
<listitem><para>Martin Renters <email>martin@tdc.on.ca</email></para></listitem>
<listitem><para>Martti Kuparinen <email>erakupa@kk.etx.ericsson.se</email></para></listitem>
<listitem><para>Masachika ISHIZUKA <email>ishizuka@isis.min.ntt.jp</email></para></listitem>
<listitem><para>Mas.TAKEMURA</para></listitem>
<listitem><para>Mas.TAKEMURA <email>unknown</email></para></listitem>
<listitem><para>Masafumi NAKANE <email>max@wide.ad.jp</email></para></listitem>
<listitem><para>Masahiro Sekiguchi <email>seki@sysrap.cs.fujitsu.co.jp</email></para></listitem>
<listitem><para>Masanobu Saitoh <email>msaitoh@spa.is.uec.ac.jp</email></para></listitem>
@ -1745,7 +1745,7 @@ box can be opened)</para>
<listitem><para>Mike Evans <email>mevans@candle.com</email></para></listitem>
<listitem><para>Mike Grupenhoff <email>kashmir@umiacs.umd.edu</email></para></listitem>
<listitem><para>Mike Hibler <email>mike@marker.cs.utah.edu</email></para></listitem>
<listitem><para>Mike Karels</para></listitem>
<listitem><para>Mike Karels <email>unknown</email></para></listitem>
<listitem><para>Mike McGaughey <email>mmcg@cs.monash.edu.au</email></para></listitem>
<listitem><para>Mike Meyer <email>mwm@shiva.the-park.com</email></para></listitem>
<listitem><para>Mike Mitchell <email>mitchell@ref.tfs.com</email></para></listitem>
@ -1787,71 +1787,71 @@ box can be opened)</para>
<listitem><para>Nickolay N. Dudorov <email>nnd@itfs.nsk.su</email></para></listitem>
<listitem><para>Niklas Hallqvist <email>niklas@filippa.appli.se</email></para></listitem>
<listitem><para>Nisha Talagala <email>nisha@cs.berkeley.edu</email></para></listitem>
<listitem><para><email>ZW6T-KND@j.asahi-net.or.jp</email></para></listitem>
<listitem><para><email>adrian@virginia.edu</email></para></listitem>
<listitem><para><email>alex@elvisti.kiev.ua</email></para></listitem>
<listitem><para><email>anto@netscape.net</email></para></listitem>
<listitem><para><email>bobson@egg.ics.nitch.ac.jp</email></para></listitem>
<listitem><para><email>bovynf@awe.be</email></para></listitem>
<listitem><para><email>burg@is.ge.com</email></para></listitem>
<listitem><para><email>chris@gnome.co.uk</email></para></listitem>
<listitem><para><email>colsen@usa.net</email></para></listitem>
<listitem><para><email>coredump@nervosa.com</email></para></listitem>
<listitem><para><email>dannyman@arh0300.urh.uiuc.edu</email></para></listitem>
<listitem><para><email>davids@SECNET.COM</email></para></listitem>
<listitem><para><email>derek@free.org</email></para></listitem>
<listitem><para><email>devet@adv.IAEhv.nl</email></para></listitem>
<listitem><para><email>djv@bedford.net</email></para></listitem>
<listitem><para><email>dvv@sprint.net</email></para></listitem>
<listitem><para><email>enami@ba2.so-net.or.jp</email></para></listitem>
<listitem><para><email>flash@eru.tubank.msk.su</email></para></listitem>
<listitem><para><email>flash@hway.ru</email></para></listitem>
<listitem><para><email>fn@pain.csrv.uidaho.edu</email></para></listitem>
<listitem><para><email>gclarkii@netport.neosoft.com</email></para></listitem>
<listitem><para><email>gordon@sheaky.lonestar.org</email></para></listitem>
<listitem><para><email>graaf@iae.nl</email></para></listitem>
<listitem><para><email>greg@greg.rim.or.jp</email></para></listitem>
<listitem><para><email>grossman@cygnus.com</email></para></listitem>
<listitem><para><email>gusw@fub46.zedat.fu-berlin.de</email></para></listitem>
<listitem><para><email>hfir@math.rochester.edu</email></para></listitem>
<listitem><para><email>hnokubi@yyy.or.jp</email></para></listitem>
<listitem><para><email>iaint@css.tuu.utas.edu.au</email></para></listitem>
<listitem><para><email>invis@visi.com</email></para></listitem>
<listitem><para><email>ishisone@sra.co.jp</email></para></listitem>
<listitem><para><email>iverson@lionheart.com</email></para></listitem>
<listitem><para><email>jpt@magic.net</email></para></listitem>
<listitem><para><email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para><email>k-sugyou@ccs.mt.nec.co.jp</email></para></listitem>
<listitem><para><email>kenji@reseau.toyonaka.osaka.jp</email></para></listitem>
<listitem><para><email>kfurge@worldnet.att.net</email></para></listitem>
<listitem><para><email>lh@aus.org</email></para></listitem>
<listitem><para><email>lhecking@nmrc.ucc.ie</email></para></listitem>
<listitem><para><email>mrgreen@mame.mu.oz.au</email></para></listitem>
<listitem><para><email>nakagawa@jp.freebsd.org</email></para></listitem>
<listitem><para><email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para></listitem>
<listitem><para><email>owaki@st.rim.or.jp</email></para></listitem>
<listitem><para><email>pechter@shell.monmouth.com</email></para></listitem>
<listitem><para><email>pete@pelican.pelican.com</email></para></listitem>
<listitem><para><email>pritc003@maroon.tc.umn.edu</email></para></listitem>
<listitem><para><email>risner@stdio.com</email></para></listitem>
<listitem><para><email>roman@rpd.univ.kiev.ua</email></para></listitem>
<listitem><para><email>root@ns2.redline.ru</email></para></listitem>
<listitem><para><email>root@uglabgw.ug.cs.sunysb.edu</email></para></listitem>
<listitem><para><email>stephen.ma@jtec.com.au</email></para></listitem>
<listitem><para><email>sumii@is.s.u-tokyo.ac.jp</email></para></listitem>
<listitem><para><email>takas-su@is.aist-nara.ac.jp</email></para></listitem>
<listitem><para><email>tamone@eig.unige.ch</email></para></listitem>
<listitem><para><email>tjevans@raleigh.ibm.com</email></para></listitem>
<listitem><para><email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para></listitem>
<listitem><para><email>torii@tcd.hitachi.co.jp</email></para></listitem>
<listitem><para><email>uenami@imasy.or.jp</email></para></listitem>
<listitem><para><email>uhlar@netlab.sk</email></para></listitem>
<listitem><para><email>vode@hut.fi</email></para></listitem>
<listitem><para><email>wlloyd@mpd.ca</email></para></listitem>
<listitem><para><email>wlr@furball.wellsfargo.com</email></para></listitem>
<listitem><para><email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para><email>yamagata@nwgpc.kek.jp</email></para></listitem>
<listitem><para><email>ziggy@ryan.org</email></para></listitem>
<listitem><para>No Name <email>ZW6T-KND@j.asahi-net.or.jp</email></para></listitem>
<listitem><para>No Name <email>adrian@virginia.edu</email></para></listitem>
<listitem><para>No Name <email>alex@elvisti.kiev.ua</email></para></listitem>
<listitem><para>No Name <email>anto@netscape.net</email></para></listitem>
<listitem><para>No Name <email>bobson@egg.ics.nitch.ac.jp</email></para></listitem>
<listitem><para>No Name <email>bovynf@awe.be</email></para></listitem>
<listitem><para>No Name <email>burg@is.ge.com</email></para></listitem>
<listitem><para>No Name <email>chris@gnome.co.uk</email></para></listitem>
<listitem><para>No Name <email>colsen@usa.net</email></para></listitem>
<listitem><para>No Name <email>coredump@nervosa.com</email></para></listitem>
<listitem><para>No Name <email>dannyman@arh0300.urh.uiuc.edu</email></para></listitem>
<listitem><para>No Name <email>davids@SECNET.COM</email></para></listitem>
<listitem><para>No Name <email>derek@free.org</email></para></listitem>
<listitem><para>No Name <email>devet@adv.IAEhv.nl</email></para></listitem>
<listitem><para>No Name <email>djv@bedford.net</email></para></listitem>
<listitem><para>No Name <email>dvv@sprint.net</email></para></listitem>
<listitem><para>No Name <email>enami@ba2.so-net.or.jp</email></para></listitem>
<listitem><para>No Name <email>flash@eru.tubank.msk.su</email></para></listitem>
<listitem><para>No Name <email>flash@hway.ru</email></para></listitem>
<listitem><para>No Name <email>fn@pain.csrv.uidaho.edu</email></para></listitem>
<listitem><para>No Name <email>gclarkii@netport.neosoft.com</email></para></listitem>
<listitem><para>No Name <email>gordon@sheaky.lonestar.org</email></para></listitem>
<listitem><para>No Name <email>graaf@iae.nl</email></para></listitem>
<listitem><para>No Name <email>greg@greg.rim.or.jp</email></para></listitem>
<listitem><para>No Name <email>grossman@cygnus.com</email></para></listitem>
<listitem><para>No Name <email>gusw@fub46.zedat.fu-berlin.de</email></para></listitem>
<listitem><para>No Name <email>hfir@math.rochester.edu</email></para></listitem>
<listitem><para>No Name <email>hnokubi@yyy.or.jp</email></para></listitem>
<listitem><para>No Name <email>iaint@css.tuu.utas.edu.au</email></para></listitem>
<listitem><para>No Name <email>invis@visi.com</email></para></listitem>
<listitem><para>No Name <email>ishisone@sra.co.jp</email></para></listitem>
<listitem><para>No Name <email>iverson@lionheart.com</email></para></listitem>
<listitem><para>No Name <email>jpt@magic.net</email></para></listitem>
<listitem><para>No Name <email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para>No Name <email>k-sugyou@ccs.mt.nec.co.jp</email></para></listitem>
<listitem><para>No Name <email>kenji@reseau.toyonaka.osaka.jp</email></para></listitem>
<listitem><para>No Name <email>kfurge@worldnet.att.net</email></para></listitem>
<listitem><para>No Name <email>lh@aus.org</email></para></listitem>
<listitem><para>No Name <email>lhecking@nmrc.ucc.ie</email></para></listitem>
<listitem><para>No Name <email>mrgreen@mame.mu.oz.au</email></para></listitem>
<listitem><para>No Name <email>nakagawa@jp.freebsd.org</email></para></listitem>
<listitem><para>No Name <email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para></listitem>
<listitem><para>No Name <email>owaki@st.rim.or.jp</email></para></listitem>
<listitem><para>No Name <email>pechter@shell.monmouth.com</email></para></listitem>
<listitem><para>No Name <email>pete@pelican.pelican.com</email></para></listitem>
<listitem><para>No Name <email>pritc003@maroon.tc.umn.edu</email></para></listitem>
<listitem><para>No Name <email>risner@stdio.com</email></para></listitem>
<listitem><para>No Name <email>roman@rpd.univ.kiev.ua</email></para></listitem>
<listitem><para>No Name <email>root@ns2.redline.ru</email></para></listitem>
<listitem><para>No Name <email>root@uglabgw.ug.cs.sunysb.edu</email></para></listitem>
<listitem><para>No Name <email>stephen.ma@jtec.com.au</email></para></listitem>
<listitem><para>No Name <email>sumii@is.s.u-tokyo.ac.jp</email></para></listitem>
<listitem><para>No Name <email>takas-su@is.aist-nara.ac.jp</email></para></listitem>
<listitem><para>No Name <email>tamone@eig.unige.ch</email></para></listitem>
<listitem><para>No Name <email>tjevans@raleigh.ibm.com</email></para></listitem>
<listitem><para>No Name <email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para></listitem>
<listitem><para>No Name <email>torii@tcd.hitachi.co.jp</email></para></listitem>
<listitem><para>No Name <email>uenami@imasy.or.jp</email></para></listitem>
<listitem><para>No Name <email>uhlar@netlab.sk</email></para></listitem>
<listitem><para>No Name <email>vode@hut.fi</email></para></listitem>
<listitem><para>No Name <email>wlloyd@mpd.ca</email></para></listitem>
<listitem><para>No Name <email>wlr@furball.wellsfargo.com</email></para></listitem>
<listitem><para>No Name <email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para>No Name <email>yamagata@nwgpc.kek.jp</email></para></listitem>
<listitem><para>No Name <email>ziggy@ryan.org</email></para></listitem>
<listitem><para>Nobuhiro Yasutomi <email>nobu@psrc.isac.co.jp</email></para></listitem>
<listitem><para>Nobuyuki Koganemaru <email>kogane@koganemaru.co.jp</email></para></listitem>
<listitem><para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para></listitem>
@ -1873,15 +1873,15 @@ box can be opened)</para>
<listitem><para>Pascal Pederiva <email>pascal@zuo.dec.com</email></para></listitem>
<listitem><para>Pasvorn Boonmark <email>boonmark@juniper.net</email></para></listitem>
<listitem><para>Patrick Gardella <email>patrick@cre8tivegroup.com</email></para></listitem>
<listitem><para>Patrick Hausen</para></listitem>
<listitem><para>Patrick Hausen <email>unknown</email></para></listitem>
<listitem><para>Paul Antonov <email>apg@demos.su</email></para></listitem>
<listitem><para>Paul F. Werkowski</para></listitem>
<listitem><para>Paul F. Werkowski <email>unknown</email></para></listitem>
<listitem><para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para></listitem>
<listitem><para>Paul Koch <email>koch@thehub.com.au</email></para></listitem>
<listitem><para>Paul Kranenburg <email>pk@NetBSD.org</email></para></listitem>
<listitem><para>Paul Mackerras <email>paulus@cs.anu.edu.au</email></para></listitem>
<listitem><para>Paul Popelka <email>paulp@uts.amdahl.com</email></para></listitem>
<listitem><para>Paul S. LaFollette, Jr.</para></listitem>
<listitem><para>Paul S. LaFollette, Jr. <email>unknown</email></para></listitem>
<listitem><para>Paul Saab <email>paul@mu.org</email></para></listitem>
<listitem><para>Paul Sandys <email>myj@nyct.net</email></para></listitem>
<listitem><para>Paul T. Root <email>proot@horton.iaces.com</email></para></listitem>
@ -1897,7 +1897,7 @@ box can be opened)</para>
<listitem><para>Peter Jeremy <email>perer.jeremy@alcatel.com.au</email></para></listitem>
<listitem><para>Peter M. Chen <email>pmchen@eecs.umich.edu</email></para></listitem>
<listitem><para>Peter Much <email>peter@citylink.dinoex.sub.org</email></para></listitem>
<listitem><para>Peter Olsson</para></listitem>
<listitem><para>Peter Olsson <email>unknown</email></para></listitem>
<listitem><para>Peter Philipp <email>pjp@bsd-daemon.net</email></para></listitem>
<listitem><para>Peter Stubbs <email>PETERS@staidan.qld.edu.au</email></para></listitem>
<listitem><para>Phil Maker <email>pjm@cs.ntu.edu.au</email></para></listitem>
@ -1930,7 +1930,7 @@ box can be opened)</para>
<listitem><para>Richard Winkel <email>rich@math.missouri.edu</email></para></listitem>
<listitem><para>Richard Wiwatowski <email>rjwiwat@adelaide.on.net</email></para></listitem>
<listitem><para>Rick Macklem <email>rick@snowhite.cis.uoguelph.ca</email></para></listitem>
<listitem><para>Rick Macklin</para></listitem>
<listitem><para>Rick Macklin <email>unknown</email></para></listitem>
<listitem><para>Rob Austein <email>sra@epilogue.com</email></para></listitem>
<listitem><para>Rob Mallory <email>rmallory@qualcomm.com</email></para></listitem>
<listitem><para>Rob Snow <email>rsnow@txdirect.net</email></para></listitem>
@ -1943,14 +1943,14 @@ box can be opened)</para>
<listitem><para>Robert Swindells <email>swindellsr@genrad.co.uk</email></para></listitem>
<listitem><para>Robert Watson <email>robert@cyrus.watson.org</email></para></listitem>
<listitem><para>Robert Withrow <email>witr@rwwa.com</email></para></listitem>
<listitem><para>Robert Yoder</para></listitem>
<listitem><para>Robert Yoder <email>unknown</email></para></listitem>
<listitem><para>Robin Carey <email>robin@mailgate.dtc.rankxerox.co.uk</email></para></listitem>
<listitem><para>Roger Hardiman <email>roger@cs.strath.ac.uk</email></para></listitem>
<listitem><para>Roland Jesse <email>jesse@cs.uni-magdeburg.de</email></para></listitem>
<listitem><para>Ron Bickers <email>rbickers@intercenter.net</email></para></listitem>
<listitem><para>Ron Lenk <email>rlenk@widget.xmission.com</email></para></listitem>
<listitem><para>Ronald Kuehn <email>kuehn@rz.tu-clausthal.de</email></para></listitem>
<listitem><para>Rudolf Cejka</para></listitem>
<listitem><para>Rudolf Cejka <email>unknown</email></para></listitem>
<listitem><para>Ruslan Belkin <email>rus@home2.UA.net</email></para></listitem>
<listitem><para>Ruslan Ermilov <email>ru@ucb.crimea.ua</email></para></listitem>
<listitem><para>Ruslan Shevchenko <email>rssh@cam.grad.kiev.ua</email></para></listitem>
@ -2008,7 +2008,7 @@ box can be opened)</para>
<listitem><para>Stefan Bethke <email>stb@hanse.de</email></para></listitem>
<listitem><para>Stefan Eggers <email>seggers@semyam.dinoco.de</email></para></listitem>
<listitem><para>Stefan Moeding <email>s.moeding@ndh.net</email></para></listitem>
<listitem><para>Stefan Petri</para></listitem>
<listitem><para>Stefan Petri <email>unknown</email></para></listitem>
<listitem><para>Stefan `Sec` Zehl <email>sec@42.org</email></para></listitem>
<listitem><para>Steinar Haug <email>sthaug@nethelp.no</email></para></listitem>
<listitem><para>Stephane E. Potvin <email>sepotvin@videotron.ca</email></para></listitem>
@ -2021,7 +2021,7 @@ box can be opened)</para>
<listitem><para>Stephen McKay <email>syssgm@devetir.qld.gov.au</email></para></listitem>
<listitem><para>Stephen Melvin <email>melvin@zytek.com</email></para></listitem>
<listitem><para>Steve Bauer <email>sbauer@rock.sdsmt.edu</email></para></listitem>
<listitem><para>Steve Deering</para></listitem>
<listitem><para>Steve Deering <email>unknown</email></para></listitem>
<listitem><para>Steve Gerakines <email>steve2@genesis.tiac.net</email></para></listitem>
<listitem><para>Steve Gericke <email>steveg@comtrol.com</email></para></listitem>
<listitem><para>Steve Piette <email>steve@simon.chi.il.US</email></para></listitem>
@ -2030,7 +2030,7 @@ box can be opened)</para>
<listitem><para>Steven H. Samorodin <email>samorodi@NUXI.com</email></para></listitem>
<listitem><para>Steven McCanne <email>mccanne@cs.berkeley.edu</email></para></listitem>
<listitem><para>Steven Plite <email>splite@purdue.edu</email></para></listitem>
<listitem><para>Steven Wallace</para></listitem>
<listitem><para>Steven Wallace <email>unknown</email></para></listitem>
<listitem><para>Stuart Henderson <email>stuart@internationalschool.co.uk</email></para></listitem>
<listitem><para>Sue Blake <email>sue@welearn.com.au</email></para></listitem>
<listitem><para>Sugiura Shiro <email>ssugiura@duo.co.jp</email></para></listitem>
@ -2055,7 +2055,7 @@ box can be opened)</para>
<listitem><para>Tatsumi HOSOKAWA <email>hosokawa@jp.FreeBSD.org</email></para></listitem>
<listitem><para>Ted Buswell <email>tbuswell@mediaone.net</email></para></listitem>
<listitem><para>Ted Faber <email>faber@isi.edu</email></para></listitem>
<listitem><para>Ted Lemon</para></listitem>
<listitem><para>Ted Lemon <email>unknown</email></para></listitem>
<listitem><para>Terry Lambert <email>terry@lambert.org</email></para></listitem>
<listitem><para>Terry Lee <email>terry@uivlsi.csl.uiuc.edu</email></para></listitem>
<listitem><para>Tetsuya Furukawa <email>tetsuya@secom-sis.co.jp</email></para></listitem>
@ -2067,7 +2067,7 @@ box can be opened)</para>
<listitem><para>Thomas Gellekum <email>thomas@ghpc8.ihf.rwth-aachen.de</email></para></listitem>
<listitem><para>Thomas Graichen <email>graichen@omega.physik.fu-berlin.de</email></para></listitem>
<listitem><para>Thomas K&ouml;nig <email>Thomas.Koenig@ciw.uni-karlsruhe.de</email></para></listitem>
<listitem><para>Thomas Ptacek</para></listitem>
<listitem><para>Thomas Ptacek <email>unknown</email></para></listitem>
<listitem><para>Thomas Stromberg <email>tstrombe@rtci.com</email></para></listitem>
<listitem><para>Thomas Valentino Crimi <email>tcrimi+@andrew.cmu.edu</email></para></listitem>
<listitem><para>Thomas Wintergerst <email>thomas@lemur.nord.de</email></para></listitem>

40
en/handbook/cutting-edge/chapter.sgml
View file

@ -414,7 +414,7 @@ subscribe cvs-all</programlisting>
any detected changes being compressed, stamped with a
sequence-number and encoded for transmission over email (in printable
ASCII only). Once received, these &ldquo;CTM deltas&rdquo; can then be handed
to the <citerefentry><refentrytitle>ctm_rmail</refentrytitle><manvolnum>1</manvolnum></citerefentry> utility which will automatically decode, verify
to the &man.ctm.rmail.1; utility which will automatically decode, verify
and apply the changes to the user's copy of the sources. This
process is far more efficient than <application>CVSup</application>, and places less strain on
our server resources since it is a <emphasis>push</emphasis> rather
@ -447,10 +447,7 @@ subscribe cvs-all</programlisting>
against one of the FreeBSD project's official anoncvs servers. To
use it, one simply sets the <envar>CVSROOT</envar> environment
variable to point at the appropriate anoncvs server and then uses
the <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> command to access it like any local
the &man.cvs.1; command to access it like any local
repository.</para>
<para>While it can also be said that the <link
@ -481,10 +478,7 @@ subscribe cvs-all</programlisting>
<sect3>
<title><anchor id="anoncvs-usage">Using Anonymous CVS</title>
<para>Configuring <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> to use an Anonymous CVS repository is a simple
<para>Configuring &man.cvs.1; to use an Anonymous CVS repository is a simple
matter of setting the <envar>CVSROOT</envar> environment variable
to point to one of the FreeBSD project's
<emphasis>anoncvs</emphasis> servers. At the time of this writing,
@ -500,10 +494,7 @@ subscribe cvs-all</programlisting>
<para>Since CVS allows one to &ldquo;check out&rdquo; virtually any
version of the FreeBSD sources that ever existed (or, in some
cases, will exist <!-- smiley -->:), you need to be familiar with
the revision (<option>-r</option>) flag to <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> and what some of the permissible values for it in
the revision (<option>-r</option>) flag to &man.cvs.1; and what some of the permissible values for it in
the FreeBSD Project repository are.</para>
<para>There are two kinds of tags, revision tags and branch tags. A
@ -655,26 +646,19 @@ subscribe cvs-all</programlisting>
<para>When you specify a branch tag, you normally receive the latest
versions of the files on that line of development. If you wish to
receive some past version, you can do so by specifying a date with
the <option>-D date</option> flag. See the <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> man page for more details.</para>
the <option>-D date</option> flag. See the &man.cvs.1; man page for more details.</para>
</sect3>
<sect3>
<title>Examples</title>
<para>While it really is recommended that you read the manual page
for <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> thoroughly before doing
for &man.cvs.1; thoroughly before doing
anything, here are some quick examples which essentially show how
to use Anonymous CVS:</para>
<example>
<title>Checking out something from -current (<citerefentry>
<refentrytitle>ls</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>) and deleting it
<title>Checking out something from -current (&man.ls.1;) and deleting it
again:</title>
<screen>
@ -694,9 +678,7 @@ subscribe cvs-all</programlisting>
</example>
<example>
<title>Creating a list of changes (as unidiffs) to <citerefentry>
<refentrytitle>ls</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> between FreeBSD 2.2.2
<title>Creating a list of changes (as unidiffs) to &man.ls.1; between FreeBSD 2.2.2
and FreeBSD 2.2.6:</title>
<screen>
@ -1556,7 +1538,7 @@ cvs-crypto</programlisting>
the latest versions of the files on that line of
development. If you wish to receive some past version,
you can do so by specifying a date with the <option>date=</option> value
field. The <citerefentry><refentrytitle>cvsup</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page explains how to do
field. The &man.cvsup.1; manual page explains how to do
that.</para>
<para>For our example, we wish to receive FreeBSD-current.
@ -1657,7 +1639,7 @@ exists before running CVSup. On any particular run of
alone.</para>
<para><literal>use-rel-suffix</literal> is ... arcane. If you really want to
know about it, see the <citerefentry><refentrytitle>cvsup</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page. Otherwise,
know about it, see the &man.cvsup.1; manual page. Otherwise,
just specify it and do not worry about it.</para>
<para><literal>compress</literal> enables the use of gzip-style compression
@ -1751,7 +1733,7 @@ cvs-crypto</programlisting>
see the manual page.</para>
<para>Once you are satisfied with the way updates are working, you
can arrange for regular runs of cvsup using <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Obviously,
can arrange for regular runs of cvsup using &man.cron.8;. Obviously,
you should not let cvsup use its GUI when running it from
cron.</para>

2
en/handbook/eresources/chapter.sgml
View file

@ -540,7 +540,7 @@ help
<para>This is
the mailing list for reporting bugs in FreeBSD Whenever
possible, bugs should be submitted using the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
possible, bugs should be submitted using the &man.send-pr.1;
command or the <ulink
URL="http://www.freebsd.org/send-pr.html">WEB
interface</ulink> to it.</para>

5
en/handbook/handbook.sgml
View file

@ -1,6 +1,9 @@
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.0-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
<!ENTITY % authors SYSTEM "authors.ent"> %authors;
<!ENTITY % authors SYSTEM "authors.ent"> %authors;
<!ENTITY % mailing-lists SYSTEM "mailing-lists.ent"> %mailing-lists;
<!ENTITY % newsgroups SYSTEM "newsgroups.ent"> %newsgroups;

24
en/handbook/hw/chapter.sgml
View file

@ -2628,7 +2628,7 @@ INS8250 -&gt; INS8250B
<para>The <devicename>sio</devicename> driver provides
support for NS8250-, NS16450-, NS16550 and NS16550A-based EIA
RS-232C (CCITT V.24) communications interfaces. Several
multiport cards are supported as well. See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for detailed technical
multiport cards are supported as well. See the &man.sio.4; manual page for detailed technical
documentation.</para>
@ -2719,7 +2719,7 @@ options COM_MULTIPORT</programlisting>
sio<replaceable>n</replaceable></literal> lines are,
you will need to add 16 more devices. Only
the last device includes the interrupt vector for the
board. (See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for detail as
board. (See the &man.sio.4; manual page for detail as
to why.) The following example is for a Boca Board with
an interrupt of 3, and a base IO address 100h. The IO
address for Each port is +8 hexadecimal from the
@ -4387,7 +4387,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
address of the device that is failing, and the desired
debug level in <filename>/sys/scsi/scsidebug.h</filename>.
If it probes but just does not work, you can use the
<citerefentry><refentrytitle>scsi</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to dynamically set a
&man.scsi.8; command to dynamically set a
debug level to it in a running kernel (if <literal>SCSIDEBUG</literal> is
defined). This will give you <emphasis>copious</emphasis> debugging output with
which to confuse the gurus. See <command>man 4
@ -4705,10 +4705,10 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
<sect3>
<title>General tape access commands</title>
<para><citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> provides generic access to the tape
<para>&man.mt.1; provides generic access to the tape
drives. Some of the more common commands are
<command>rewind</command>, <command>erase</command>, and
<command>status</command>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry>
<command>status</command>. See the &man.mt.1;
manual page for a detailed description.</para>
</sect3>
@ -4728,12 +4728,12 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
<sect3>
<title>SCSI drives</title>
<para>The <citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry> driver provides
<para>The &man.st.4; driver provides
support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC
(Quarter-Inch Cartridge), DLT (Digital Linear Tape), QIC
Minicartridge and 9-track (remember the big reels that you see
spinning in Hollywood computer rooms) tape drives. See the
<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for a detailed
&man.st.4; manual page for a detailed
description.</para>
<para>The drives listed below are currently being used by members
@ -4876,7 +4876,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
and QIC-525 (DC6525) tapes as well.</para>
<para>Data transfer rate is 350kB/s using
<citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Rates of 530kB/s have been
&man.dump.8;. Rates of 530kB/s have been
reported when using <link
linkend="backups-programs-amanda">Amanda</link></para>
@ -4982,7 +4982,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
(250MB) tapes.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>).</para>
scsi tape device driver (&man.st.4;).</para>
<para>Under FreeBSD 2.2-current, use <command>mt
blocksize 512</command> to set the blocksize. (The
@ -5513,7 +5513,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
<para>Native capacity is 150/250MB.</para>
<para>This drive has quirks which are known and work around code
is present in the scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>). Upgrading the firmware to XXX
is present in the scsi tape device driver (&man.st.4;). Upgrading the firmware to XXX
version will fix the quirks and provide SCSI 2
capabilities.</para>
@ -5552,7 +5552,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
supported for the 2.5 GB cartridges.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>)
scsi tape device driver (&man.st.4;)
beginning with FreeBSD 2.2-current. For previous versions of
FreeBSD, use <command>mt</command> to read one
block from the tape, rewind the tape, and then execute the
@ -5590,7 +5590,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
erased.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>).</para>
scsi tape device driver (&man.st.4;).</para>
<para>Other firmware revisions that are known to work are:
M75D</para>

4
en/handbook/introduction/chapter.sgml
View file

@ -432,10 +432,10 @@
are the people who have <emphasis>write</emphasis> access to
the CVS tree, and are thus authorized to make modifications
to the FreeBSD source (the term &ldquo;committer&rdquo; comes from the
<citerefentry><refentrytitle>cvs</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>commit</command> command, which is used to
&man.cvs.1; <command>commit</command> command, which is used to
bring new changes into the CVS repository). The best way of
making submissions for review by the committers list is to
use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, though if something appears to be jammed in the system then you may also reach them by sending mail to <email>committers@freebsd.org</email>.</para>
use the &man.send-pr.1; command, though if something appears to be jammed in the system then you may also reach them by sending mail to <email>committers@freebsd.org</email>.</para>
</listitem>
</varlistentry>

26
en/handbook/kernelconfig/chapter.sgml
View file

@ -122,7 +122,7 @@
<note>
<para>If you are trying to upgrade your kernel from an older version
of FreeBSD, you will probably have to get a new version of
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> from the same place you got the new
&man.config.8; from the same place you got the new
kernel sources. It is located in
<filename>/usr/src/usr.sbin</filename>, so you will need to
download those sources as well. Re-build and install it before
@ -430,7 +430,7 @@
hundred bytes to the kernel.</para>
<note>
<para>The <citerefentry><refentrytitle>ipcs</refentrytitle><manvolnum>1</manvolnum></citerefentry> command will tell
<para>The &man.ipcs.1; command will tell
will list any processes using each of these System V
facilities.</para>
</note>
@ -503,7 +503,7 @@
<listitem>
<para>Process filesystem. This is a pretend filesystem
mounted on <filename>/proc</filename> which allows
programs like <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> to give you more
programs like &man.ps.1; to give you more
information on what processes are running.</para>
</listitem>
</varlistentry>
@ -609,7 +609,7 @@
<note>
<para>QIC-80 tape support requires a separate filter
program called <citerefentry><refentrytitle>ft</refentrytitle><manvolnum>8</manvolnum></citerefentry>, see the manual
program called &man.ft.8;, see the manual
page for details.</para>
</note>
</listitem>
@ -975,7 +975,7 @@
modem to 2 (for obscure technical reasons IRQ 2 = IRQ 9)
in order to access it from FreeBSD. If you have a
multiport serial card, check the manual page for
<citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for more information on the
&man.sio.4; for more information on the
proper values for these lines. Some video cards (notably
those based on S3 chips) use IO addresses of the form
<literal>0x*2e8</literal>, and since many cheap serial
@ -1250,7 +1250,7 @@
network interfaces to be placed in promiscuous mode,
capturing every packet on a broadcast network (e.g. an
ethernet). These packets can be captured to disk and/or
examined with the <citerefentry><refentrytitle>tcpdump</refentrytitle><manvolnum>1</manvolnum></citerefentry> program.
examined with the &man.tcpdump.1; program.
Note that implementation of this capability can seriously
compromise your overall network security. The
<replaceable>number</replaceable> after bpfilter is the number
@ -1445,7 +1445,7 @@
<listitem>
<para>Snoop device. This pseudo-device allows one terminal
session to watch another using the
<citerefentry><refentrytitle>watch</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. Note that
&man.watch.8; command. Note that
implementation of this capability has important security
and privacy implications. The <replaceable>number</replaceable>
after snp is the total number of simultaneous snoop
@ -1457,7 +1457,7 @@
<listitem>
<para>Vnode driver. Allows a file to be treated as a device
after being set up with the <citerefentry><refentrytitle>vnconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry>
after being set up with the &man.vnconfig.8;
command. This driver can be useful for manipulating
floppy disk images and using a file as a swap device (e.g.
an MS Windows swap file). Optional.</para>
@ -1473,8 +1473,8 @@
&ldquo;meta&rdquo;-disk. The <replaceable>number</replaceable> after ccd
is the total number of concatenated disks (not total
number of disks that can be concatenated) that can be
created. (See <citerefentry><refentrytitle>ccd</refentrytitle><manvolnum>4</manvolnum></citerefentry> and
<citerefentry><refentrytitle>ccdconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> man pages for more
created. (See &man.ccd.4; and
&man.ccdconfig.8; man pages for more
details.) Optional.</para>
</listitem>
</varlistentry>
@ -1642,7 +1642,7 @@ controller wcd0</programlisting>
resource is the <filename>/var/log/messages</filename> file
which records, among other things, all of the kernel
messages from every successful boot. Also, the
<citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>8</manvolnum></citerefentry> command will print the kernel
&man.dmesg.8; command will print the kernel
messages from the current boot.</para>
<note>
@ -1655,7 +1655,7 @@ controller wcd0</programlisting>
with the last installed kernel which may be
non-functional. Also, as soon as possible, move the
working kernel to the proper <filename>kernel</filename> location or
commands such as <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> will not work
commands such as &man.ps.1; will not work
properly. The proper command to &ldquo;unlock&rdquo; the
kernel file that <command>make</command> installs (in
order to move another kernel back permanently) is:</para>
@ -1683,7 +1683,7 @@ controller wcd0</programlisting>
from the one that the system utilities have been built with,
for example, an experimental &ldquo;2.2.0&rdquo; kernel on a
2.1.0-RELEASE system, many system-status commands like
<citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> and <citerefentry><refentrytitle>vmstat</refentrytitle><manvolnum>8</manvolnum></citerefentry>
&man.ps.1; and &man.vmstat.8;
will not work any more. You must recompile the <filename>libkvm</filename> library as well as these
utilities. This is one reason it is not normally a good
idea to use a different version of the kernel from the rest

17
en/handbook/kerneldebug/chapter.sgml
View file

@ -13,10 +13,7 @@
is too small to hold the dump, you can configure your kernel to use
an alternate dump device (in the <literal>config
kernel</literal> line), or you can specify an alternate using the
<citerefentry><refentrytitle>dumpon</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. The best way to use <citerefentry>
<refentrytitle>dumpon</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> is to set the <literal>dumpdev</literal> variable in
&man.dumpon.8; command. The best way to use &man.dumpon.8; is to set the <literal>dumpdev</literal> variable in
<filename>/etc/rc.conf</filename>. Typically you want to specify one of
the swap devices specified in <filename>/etc/fstab</filename>.
Dumps to non-swap devices, tapes for example,
@ -25,10 +22,10 @@ Dumps to non-swap devices, tapes for example,
Configuration</link> for
details on configuring the FreeBSD kernel.</para>
<para>Use the <citerefentry><refentrytitle>dumpon</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to tell the kernel
<para>Use the &man.dumpon.8; command to tell the kernel
where to dump to (note that this will have to be done after
configuring the partition in question as swap space via
<citerefentry><refentrytitle>swapon</refentrytitle><manvolnum>8</manvolnum></citerefentry>). This is normally arranged via
&man.swapon.8;). This is normally arranged via
<filename>/etc/rc.conf</filename> and <filename>/etc/rc</filename>.
Alternatively, you can hard-code the dump device via the <literal>dump</literal>
clause in the <literal>config</literal> line of your kernel config file. This is
@ -68,7 +65,7 @@ Dumps to non-swap devices, tapes for example,
&prompt.root; <userinput>exit</userinput> # ...to multi-user</screen>
<para>This instructs <citerefentry><refentrytitle>savecore</refentrytitle><manvolnum>8</manvolnum></citerefentry> to
<para>This instructs &man.savecore.8; to
use another kernel for symbol name extraction. It would otherwise
default to the currently running kernel and most likely not do
anything at all since the crash dump and the kernel symbols
@ -279,7 +276,7 @@ Dumps to non-swap devices, tapes for example,
generated code, so you will finally get a new kernel with similar
code to the faulting one but some debugging symbols. You should at
least verify the old and new sizes with the
<citerefentry><refentrytitle>size</refentrytitle><manvolnum>1</manvolnum></citerefentry> command. If there is a mismatch, you
&man.size.1; command. If there is a mismatch, you
probably need to give up here.</para>
<para>Go and examine the dump as described above. The debugging
@ -479,7 +476,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
<para>The return value will be printed.</para>
<para>For a <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> style summary of all running
<para>For a &man.ps.1; style summary of all running
processes, use:</para>
@ -525,7 +522,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
<para>However, it is highly recommended to have a
printed copy of the <citerefentry><refentrytitle>ddb</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page
printed copy of the &man.ddb.4; manual page
ready for a debugging session. Remember that it is hard to read the
on-line manual while single-stepping the kernel.</para>

8
en/handbook/kernelopts/chapter.sgml
View file

@ -19,10 +19,10 @@
the supported options in the kernel into new-style ones, so for
people who correctly did a <command>make depend</command>
in their kernel compile directory after running
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry>, the build process will automatically
&man.config.8;, the build process will automatically
pick up modified options, and only recompile those files where it is
necessary. Wiping out the old compile directory on each run of
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> as it is still done now can then be
&man.config.8; as it is still done now can then be
eliminated again.</para>
<para>Basically, a kernel option is nothing else than the definition
@ -89,7 +89,7 @@ options notyet,notdef</programlisting>
using such an option is responsible himself for knowing about its
implications (and maybe manually forcing the recompilation of parts
of his kernel). Once the transition of all supported options has
been done, <citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> will warn whenever an
been done, &man.config.8; will warn whenever an
unsupported option appears in the config file, but it will
nevertheless include it into the kernel Makefile.</para>
@ -114,7 +114,7 @@ options notyet,notdef</programlisting>
<filename>opt_<replaceable>foo</replaceable>.h</filename> already
available for the intended new option, invent a new name. Make it
meaningful, and comment the new section in the
<filename>options[<replaceable>.&lt;arch&gt;</replaceable>]</filename> file. <citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves..</para>
<filename>options[<replaceable>.&lt;arch&gt;</replaceable>]</filename> file. &man.config.8; will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves..</para>
<para>Packing too many options into a single
<filename>opt_<replaceable>foo</replaceable>.h</filename> will cause

28
en/handbook/l10n/chapter.sgml
View file

@ -49,7 +49,7 @@ font8x8=cp866-8x8</programlisting>
<para>This tuning means KOI8-R keyboard with Alternative
screen font mapped to KOI8-R encoding to preserve
pseudographics, <literal>Gray Delete</literal>
key remapped to match Russian <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry for FreeBSD
key remapped to match Russian &man.termcap.5; entry for FreeBSD
console.</para>
<para>RUS/LAT switch will be <literal>CapsLock</literal>. Old CapsLock function still
@ -83,7 +83,7 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<listitem>
<para><envar>LANG</envar> for POSIX
<citerefentry><refentrytitle>setlocale</refentrytitle><manvolnum>3</manvolnum></citerefentry> family functions;</para>
&man.setlocale.3; family functions;</para>
</listitem>
<listitem>
@ -95,8 +95,8 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<para>The best way is using <filename>/etc/login.conf</filename>
<literal>russian</literal> user's login class in
<citerefentry><refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry login class
position. See <citerefentry><refentrytitle>login.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
&man.passwd.5; entry login class
position. See &man.login.conf.5; for
details.</para>
@ -115,9 +115,9 @@ russian:Russian Users Accounts:\
<sect4>
<title>How to do it with <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.vipw.8;</title>
<para>If you use <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new
<para>If you use &man.vipw.8; for adding new
users, <filename>/etc/master.passwd</filename> entry should
looks like:</para>
@ -127,9 +127,9 @@ user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh</programlisting>
</sect4>
<sect4>
<title>How to do it with <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.adduser.8;</title>
<para>If you use <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new
<para>If you use &man.adduser.8; for adding new
users:</para>
<itemizedlist>
@ -149,7 +149,7 @@ defaultclass = russian</programlisting> in
<screen><prompt>Enter login class:</prompt> default []:</screen>
prompt from
<citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;</para>
&man.adduser.8;;</para>
</listitem>
<listitem>
@ -166,9 +166,9 @@ defaultclass = russian</programlisting> in
</sect4>
<sect4>
<title>How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.pw.8;</title>
<para>If you use <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users,
<para>If you use &man.pw.8; for adding new users,
call it in this form:</para>
@ -245,21 +245,21 @@ lp|Russian local line printer:\
:sh:of=/usr/libexec/lpr/ru/koi2alt:\
:lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:</programlisting>
<para>See <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para>
<para>See &man.printcap.5; for detailed description.</para>
</sect2>
<sect2 id="russian-msdosfs">
<title>MSDOS FS and Russian file names</title>
<para>Look at following example <citerefentry><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry to enable support for Russian
<para>Look at following example &man.fstab.5; entry to enable support for Russian
file names in MSDOS FS:</para>
<programlisting>
/dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0</programlisting>
<para>See
<citerefentry><refentrytitle>mount_msdos</refentrytitle><manvolnum>8</manvolnum></citerefentry>for detailed description of
&man.mount.msdos.8; for detailed description of
<option>-W</option> and <option>-L</option> options.</para>
</sect2>

7
en/handbook/linuxemu/chapter.sgml
View file

@ -404,7 +404,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
check if it needs shared libraries, and if so, whether you have
them installed in the <filename>/compat/linux</filename> tree.
To do this, you run the Linux version <command>ldd</command> on the new program,
and watch its output. <command>ldd</command> (see also the manual page for <citerefentry><refentrytitle>ldd</refentrytitle><manvolnum>1</manvolnum></citerefentry>)
and watch its output. <command>ldd</command> (see also the manual page for &man.ldd.1;)
will print a list of shared libraries that the program depends
on, in the form <literal><replaceable>majorname</replaceable> (<replaceable>jumpversion</replaceable>) =&gt; <replaceable>fullname</replaceable></literal>.</para>
@ -433,10 +433,7 @@ Abort</screen>
<para>To help the FreeBSD kernel distinguish between a FreeBSD ELF
binary from a Linux binary, use the <citerefentry>
<refentrytitle>brandelf</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> utility.</para>
binary from a Linux binary, use the &man.brandelf.1; utility.</para>
<screen>&prompt.user; <userinput>brandelf -t Linux my-linux-elf-binary</userinput></screen>

34
en/handbook/ports/chapter.sgml
View file

@ -522,7 +522,7 @@ do-install:
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
the <citerefentry><refentrytitle>pkg_add</refentrytitle><manvolnum>1</manvolnum></citerefentry> program to install a
the &man.pkg.add.1; program to install a
package file on your system.</para>
</listitem>
@ -1170,7 +1170,7 @@ lib/X11/oneko/cat2.xpm
lib/X11/oneko/mouse.xpm
@dirrm lib/X11/oneko</programlisting>
<para>Refer to the <citerefentry><refentrytitle>pkg_create</refentrytitle><manvolnum>1</manvolnum></citerefentry> man page
<para>Refer to the &man.pkg.create.1; man page
for details on the packing list.</para>
<note>
@ -1290,19 +1290,10 @@ lib/X11/oneko/mouse.xpm
<filename>pkgname.tgz</filename> package, so delete them
now. Next, simply include the output of <command>shar `find
port_dir`</command> in a bug report and send it with the
<citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> program (see <link linkend="contrib-general">Bug
&man.send-pr.1; program (see <link linkend="contrib-general">Bug
Reports and General Commentary</link> for more information
about <citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry>. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use <citerefentry>
<refentrytitle>uuencode</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> before including it in the bug report (uuencoded
about &man.send-pr.1;. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use &man.uuencode.1; before including it in the bug report (uuencoded
tarfiles are acceptable even if the bug report is smaller than
20KB but are not preferred). Be sure to classify the bug report as
category <literal>ports</literal> and class
@ -2805,9 +2796,7 @@ diff -u -r1.15 PLIST
POST-INSTALL</literal>. <literal>&dollar;2</literal> can be
tested to determine which mode the script is being run in. The
<envar>PKG_PREFIX</envar> environmental variable will be set to
the package installation directory. See <citerefentry>
<refentrytitle>pkg_add</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> for additional
the package installation directory. See &man.pkg.add.1; for additional
information.</para>
<note>
@ -3045,7 +3034,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<command>diff -ruN superedit.bak
superedit</command>). Please examine the output to make
sure all the changes make sense. The best way to send us the
diff is by including it to <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
diff is by including it to &man.send-pr.1;
(category <literal>ports</literal>). Please mention any added or deleted files
in the message, as they have to be explicitly specified to CVS
when doing a commit. If the diff is more than about 20KB, please
@ -3053,7 +3042,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
the PR.</para>
<para>Once again, please use
<citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> and not <citerefentry><refentrytitle>shar</refentrytitle><manvolnum>1</manvolnum></citerefentry> to send updates to ports.</para>
&man.diff.1; and not &man.shar.1; to send updates to ports.</para>
</sect2>
<sect2>
@ -3080,10 +3069,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
post-install:
strip ${PREFIX}/bin/xdl</programlisting>
<para>Use the <citerefentry>
<refentrytitle>file</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> command on the installed executable to check
<para>Use the &man.file.1; command on the installed executable to check
whether the binary is stripped or not. If it does not say
<literal>not stripped</literal>, it is stripped.</para>
</sect3>
@ -3788,7 +3774,7 @@ post-install:
(executables for superusers/managers),
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
files). See man &man.hier.7; for
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use

32
en/handbook/ppp-and-slip/chapter.sgml
View file

@ -168,8 +168,8 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
<para>If you have a kernel without the tun device, and you can not
rebuild it for some reason, all is not lost. You should be able
to dynamically load the code. Refer to the appropriate <citerefentry><refentrytitle>modload</refentrytitle><manvolnum>8</manvolnum></citerefentry>
and <citerefentry><refentrytitle>lkm</refentrytitle><manvolnum>4</manvolnum></citerefentry> pages for further details.</para>
to dynamically load the code. Refer to the appropriate &man.modload.8;
and &man.lkm.4; pages for further details.</para>
<para>You may also wish to take this opportunity to configure a
firewall. Details can be found in the <link linkend="firewalls">Firewalls</link> section.</para>
@ -395,7 +395,7 @@ domain <replaceable>bar.com</replaceable></programlisting>
<listitem>
<para>The dial string. User PPP uses an expect-send
syntax similar to the <citerefentry><refentrytitle>chat</refentrytitle><manvolnum>8</manvolnum></citerefentry>
syntax similar to the &man.chat.8;
program. Refer to the manual page for information on
the features of this language.</para>
</listitem>
@ -1023,7 +1023,7 @@ set server /var/run/ppp-tun%d DiagnosticPassword 0177</programlisting>
tun device number that is in use.</para>
<para>Once a socket has been set up, the
<citerefentry><refentrytitle>pppctl</refentrytitle><manvolnum>8</manvolnum></citerefentry> program may be used in scripts that
&man.pppctl.8; program may be used in scripts that
wish to manipulate the running program.</para>
</sect3>
@ -1190,7 +1190,7 @@ sendmail_flags="-bd"</programlisting>
<step>
<para>Create an entry in <filename>/etc/passwd</filename>
(using the <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> program).</para>
(using the &man.vipw.8; program).</para>
</step>
<step>
@ -2014,12 +2014,12 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
otherwise, check the place where you found this document for a
document named <filename>dialup.txt</filename> or something
similar. You may also want to check the manual pages for
<citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for information on the serial
port device driver and <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry>, &amp; <citerefentry><refentrytitle>init</refentrytitle><manvolnum>8</manvolnum></citerefentry> for
&man.sio.4; for information on the serial
port device driver and &man.ttys.5;,
&man.gettytab.5;,
&man.getty.8;, &amp; &man.init.8; for
information relevant to configuring the system to accept logins on
modems, and perhaps <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for information on
modems, and perhaps &man.stty.1; for information on
setting serial port parameters (such as <literal>clocal</literal> for directly-connected serial
interfaces).</para>
@ -2082,8 +2082,8 @@ Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp</programlisting>
goes wrong, <command>sliplogin</command> usually logs
good informational messages via the <literal>daemon</literal> syslog facility,
which usually goes into <filename>/var/log/messages</filename>
(see the manual pages for <citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry> and
<citerefentry><refentrytitle>syslog.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>, and perhaps check
(see the manual pages for &man.syslogd.8; and
&man.syslog.conf.5, and perhaps check
<filename>/etc/syslog.conf</filename> to see to which files
<command>syslogd</command> is logging).</para>
@ -2163,7 +2163,7 @@ pseudo-device sl 2</programlisting>
<para>As mentioned earlier, there are three files in the
<filename>/etc/sliphome</filename> directory that are part of the
configuration for <filename>/usr/sbin/sliplogin</filename> (see
<citerefentry><refentrytitle>sliplogin</refentrytitle><manvolnum>8</manvolnum></citerefentry> for the actual manual page for
&man.sliplogin.8; for the actual manual page for
<command>sliplogin</command>):
<filename>slip.hosts</filename>, which defines the SLIP users
&amp; their associated IP addresses;
@ -2281,7 +2281,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
SLIP server's Ethernet subnet, and you will also need to adjust
your <filename>/etc/sliphome/slip.login</filename> and
<filename>/etc/sliphome/slip.logout</filename> scripts to use
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> to manage the proxy-ARP entries in the
&man.arp.8; to manage the proxy-ARP entries in the
SLIP server's ARP table.</para>
</sect3>
@ -2355,8 +2355,8 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<command>netstat -i</command> must be changed to colons and
leading zeros should be added to each single-digit hexadecimal
number to convert the address into the form that
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> desires; see the manual page on
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> for complete information on
&man.arp.8; desires; see the manual page on
&man.arp.8; for complete information on
usage.</para>
<note>

282
en/handbook/printing/chapter.sgml
View file

@ -448,8 +448,7 @@ sio2: type 16550A</screen>
<procedure>
<step>
<para>Become root with the <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>
<para>Become root with the &man.su.1;
command. Enter the root password when prompted.</para>
</step>
@ -523,8 +522,7 @@ sio2: type 16550A</screen>
works.</para>
<para>You can set the communications mode in two ways: by
configuring the kernel or by using the <citerefentry>
<refentrytitle>lptcontrol</refentrytitle></citerefentry> program.</para>
configuring the kernel or by using the &man.lptcontrol.8; program.</para>
<para><emphasis>To set the communications mode by
configuring the kernel:</emphasis></para>
@ -571,8 +569,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
</procedure>
<para><emphasis>To set the communications mode
with</emphasis> <citerefentry>
<refentrytitle>lptcontrol</refentrytitle></citerefentry>:</para>
with</emphasis> &man.lptcontrol.8;:</para>
<procedure>
@ -601,7 +598,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
<para>You could put these commands in your
<filename>/etc/rc.local</filename> file to set the mode each
time your system boots. See <citerefentry><refentrytitle>lptcontrol</refentrytitle><manvolnum>8</manvolnum></citerefentry> for more information.</para>
time your system boots. See &man.lptcontrol.8; for more information.</para>
</sect4>
@ -615,8 +612,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
<para>To test the printer, we will send some text to it. For
printers that can immediately print characters sent to them,
the program <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> is perfect: it generates all 96 printable ASCII characters in 96 lines.</para>
the program &man.lptest.1; is perfect: it generates all 96 printable ASCII characters in 96 lines.</para>
<para>For a PostScript (or other language-based) printer, we
will need a more sophisticated test. A small PostScript
@ -653,8 +649,7 @@ showpage</programlisting>
<procedure>
<step>
<para>Become root with <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>.</para>
<para>Become root with &man.su.1;.</para>
</step>
<step>
@ -663,8 +658,7 @@ showpage</programlisting>
<listitem>
<para>If the printer can print plain text, then
use <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. Type:</para>
use &man.lptest.1;. Type:</para>
<screen>&prompt.root; <userinput>lptest &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
@ -726,8 +720,7 @@ showpage</programlisting>
<procedure>
<step>
<para>Become root with <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>.</para>
<para>Become root with &man.su.1;.</para>
</step>
<step>
@ -753,8 +746,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
</step>
<step>
<para>Connect to the printer with <citerefentry>
<refentrytitle>tip</refentrytitle></citerefentry>. Type:</para>
<para>Connect to the printer with &man.tip.1;. Type:</para>
<screen>&prompt.root; <userinput>tip printer</userinput></screen>
@ -771,8 +763,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<listitem>
<para>If the printer can print plain text, then
use <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. Type:</para>
use &man.lptest.1;. Type:</para>
<screen><prompt>~</prompt><userinput>$lptest</userinput></screen>
@ -799,8 +790,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<para>Where <replaceable>file</replaceable> is the name of the
file containing the program. After
<citerefentry>
<refentrytitle>tip</refentrytitle></citerefentry> sends the file, press any required end-of-file key.</para>
&man.tip.1; sends the file, press any required end-of-file key.</para>
</listitem>
</itemizedlist>
@ -831,8 +821,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
reads this file each time the spooler is used, so updates to the
file take immediate effect.</para>
<para>The format of the <citerefentry>
<refentrytitle>printcap</refentrytitle></citerefentry> file is straightforward. Use your favorite text editor to make changes to <filename>/etc/printcap</filename>. The format is identical to other capability files like <filename>/usr/share/misc/termcap</filename> and <filename>/etc/remote</filename>. For complete information about the format, see the <citerefentry><refentrytitle>cgetent</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
<para>The format of the &man.printcap.5; file is straightforward. Use your favorite text editor to make changes to <filename>/etc/printcap</filename>. The format is identical to other capability files like <filename>/usr/share/misc/termcap</filename> and <filename>/etc/remote</filename>. For complete information about the format, see the &man.cgetent.3;.</para>
<para>The simple spooler configuration consists of the following
steps:</para>
@ -880,8 +869,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<step>
<para>Test the setup by printing something with the
<citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
&man.lpr.1;
command; see <link linkend="printing-trying">Trying
It Out</link> and <link linkend="printing-troubleshooting">Troubleshooting</link>.</para>
</step>
@ -1006,8 +994,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
is customary to put these directories under
<filename>/var/spool</filename>. It is not necessary to
backup the contents of spooling directories, either.
Recreating them is as simple as running <citerefentry>
<refentrytitle>mkdir</refentrytitle></citerefentry>.</para>
Recreating them is as simple as running &man.mkdir.1;.</para>
<para>It is also customary to make the directory with a name
that is identical to the name of the printer, as shown below:</para>
@ -1294,14 +1281,11 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
Unfortunately, congratulations are not quite yet in order,
since we still have to test the setup and correct any
problems. To test the setup, try printing something. To
print with the LPD system, you use the command <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>,
print with the LPD system, you use the command &man.lpr.1;,
which submits a job for printing.</para>
<para>You can combine <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
with the <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> program, introduced in section <link linkend="printing-testing">Checking Printer Communications</link> to generate some
<para>You can combine &man.lpr.1;
with the &man.lptest.1; program, introduced in section <link linkend="printing-testing">Checking Printer Communications</link> to generate some
test text.</para>
<para><emphasis>To test the simple LPD
@ -1315,17 +1299,14 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>Where <replaceable>printer-name</replaceable> is a the name of a printer
(or an alias) specified in <filename>/etc/printcap</filename>.
To test the default printer, type <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
To test the default printer, type &man.lpr.1;
without any <option>-P</option> argument. Again, if you are
testing a printer that expects PostScript, send a PostScript
program in that language instead of using <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. You
program in that language instead of using &man.lptest.1;. You
can do so by putting the program in a file and typing <command>lpr <replaceable>file</replaceable></command>.</para>
<para>For a PostScript printer, you should get the results of
the program. If you are using <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>, then your results should look like the following:</para>
the program. If you are using &man.lptest.1;, then your results should look like the following:</para>
<programlisting>
!"#$%&amp;'()*+,-./01234
@ -1335,8 +1316,7 @@ $%&amp;'()*+,-./01234567
%&amp;'()*+,-./012345678</programlisting>
<para>To further test the printer, try downloading larger
programs (for language-based printers) or running <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> with different arguments. For example, <command>lptest 80 60</command> will produce 60 lines of 80 characters each.</para>
programs (for language-based printers) or running &man.lptest.1; with different arguments. For example, <command>lptest 80 60</command> will produce 60 lines of 80 characters each.</para>
<para>If the printer did not work, see the next section, <link
linkend="printing-troubleshooting">Troubleshooting</link>.</para>
@ -1346,8 +1326,7 @@ $%&amp;'()*+,-./01234567
<sect4 id="printing-troubleshooting">
<title>Troubleshooting</title>
<para>After performing the simple test with <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>, you
<para>After performing the simple test with &man.lptest.1;, you
might have gotten one of the following results instead of the
correct printout:</para>
@ -1665,23 +1644,20 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
FreeBSD. Here is an overview of the user-level commands:</para>
<variablelist>
<varlistentry><term><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lpr.1;</term>
<listitem>
<para>Print jobs</para>
</listitem>
</varlistentry>
<varlistentry><term><citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lpq.1;</term>
<listitem>
<para>Check printer queues</para>
</listitem>
</varlistentry>
<varlistentry><term><citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lprm.1;</term>
<listitem>
<para>Remove jobs from a printer's queue</para>
@ -1689,16 +1665,12 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
</varlistentry>
</variablelist>
<para>There is also an administrative command, <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>,
<para>There is also an administrative command, &man.lpc.8;,
described in the section <link linkend="printing-lpc">Administrating the
LPD Spooler</link>, used to control printers and their queues.</para>
<para>All three of the commands <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>, and
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>
<para>All three of the commands &man.lpr.1;, &man.lprm.1;, and
&man.lpq.1;
accept an option <option>-P <replaceable>printer-name</replaceable></option> to specify on which
printer/queue to operate, as listed in the
<filename>/etc/printcap</filename> file. This enables you to
@ -1724,8 +1696,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>This prints each of the listed files to the
default printer. If you list no files, <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> reads
default printer. If you list no files, &man.lpr.1; reads
data to print from standard input. For example, this command
prints some important system files:</para>
@ -1747,14 +1718,12 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>Because no files were listed for the
<citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
&man.lpr.1;
command, <command>lpr</command> read the data to print
from standard input, which was the output of the <command>ls
-l</command> command.</para>
<para>The <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
<para>The &man.lpr.1; command
can also accept a wide variety of options to control formatting,
apply file conversions, generate multiple copies, and so forth.
For more information, see the section <link
@ -1765,8 +1734,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<sect2 id="printing-lpq">
<title>Checking Jobs</title>
<para>When you print with <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, the
<para>When you print with &man.lpr.1;, the
data you wish to print is put together in a package called a
&ldquo;print job&rdquo;, which is sent to the LPD spooling
system. Each printer has a queue of jobs, and your job waits in
@ -1775,8 +1743,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
order.</para>
<para>To display the queue for the default printer, type
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>. For a
&man.lpq.1;. For a
specific printer, use the <option>-P</option> option. For
example, the command
@ -1803,29 +1770,24 @@ active kelly 9 /etc/host.conf, /etc/hosts.equiv 88 bytes
details.</para>
<para>Job number nine consists of two files; multiple files given on
the <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
the &man.lpr.1; command
line are treated as part of a single job. It is the currently
active job (note the word <literal>active</literal>
under the &ldquo;Rank&rdquo; column), which means the printer should be
currently printing that job. The second job consists of data
passed as the standard input to the</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>&man.lpr.1;
command. The third job came from user mary; it is a much larger
job. The pathname of the files she's trying to print is too long
to fit, so the <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> command
to fit, so the &man.lpq.1; command
just shows three dots.</para>
<para>The very first line of the output from <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> is also
<para>The very first line of the output from &man.lpq.1; is also
useful: it tells what the printer is currently doing (or at least
what LPD thinks the printer is doing).</para>
<para>The <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> command
<para>The &man.lpq.1; command
also support a <option>-l</option> option to generate a detailed
long listing. Here is an example of <command>lpq -l</command>:</para>
@ -1848,16 +1810,13 @@ mary: 3rd [job 011rose]
<title>Removing Jobs</title>
<para>If you change your mind about printing a job, you can remove
the job from the queue with the <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
command. Often, you can even use <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry> to
the job from the queue with the &man.lprm.1;
command. Often, you can even use &man.lprm.1; to
remove an active job, but some or all of the job might still get
printed.</para>
<para>To remove a job from the default printer, first use
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> to find
&man.lpq.1; to find
the job number. Then type:</para>
@ -1873,8 +1832,7 @@ mary: 3rd [job 011rose]
<screen>&prompt.user; <userinput>lprm -P bamboo 10</userinput></screen>
<para>The <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
<para>The &man.lprm.1;
command has a few shortcuts:</para>
<variablelist>
@ -1900,8 +1858,7 @@ mary: 3rd [job 011rose]
<listitem>
<para>With no job number, user name, or
<option>-</option> appearing on the command line,
<citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry> removes the currently active job on the default printer, if it belongs to you. The superuser can remove any active job.</para>
&man.lprm.1; removes the currently active job on the default printer, if it belongs to you. The superuser can remove any active job.</para>
</listitem>
</varlistentry>
@ -1918,8 +1875,7 @@ mary: 3rd [job 011rose]
<note>
<para>If you are working in a networked
environment, <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
environment, &man.lprm.1;
will let you remove jobs only from the host from which the jobs
were submitted, even if the same printer is available from other
hosts. The following command sequence demonstrates this:</para>
@ -1945,8 +1901,7 @@ cfA013rose dequeued
<sect2 id="printing-lpr-options">
<title>Beyond Plain Text: Printing Options</title>
<para>The <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
<para>The &man.lpr.1; command
supports a number of options that control formatting text,
converting graphic and other file formats, producing multiple
copies, handling of the job, and more. This section describes the
@ -1956,12 +1911,10 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-format">
<title>Formatting and Conversion Options</title>
<para>The following <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>The following &man.lpr.1;
options control formatting of the files in the job. Use these
options if the job does not contain plain text or if you want
plain text formatted through the <citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
plain text formatted through the &man.pr.1;
utility.</para>
<para>For example, the following command prints a DVI file (from
@ -2050,9 +2003,8 @@ cfA013rose dequeued
<varlistentry><term>-p</term>
<listitem>
<para>Format plain text with <citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
before printing. See <citerefentry><refentrytitle>pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> for more information.</para>
<para>Format plain text with &man.pr.1;
before printing. See &man.pr.1; for more information.</para>
</listitem>
</varlistentry>
@ -2061,8 +2013,7 @@ cfA013rose dequeued
<listitem>
<para>Use <replaceable>title</replaceable> on the
<citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
&man.pr.1;
header instead of the file name. This option has effect
only when used with the <option>-p</option>
option.</para>
@ -2086,30 +2037,24 @@ cfA013rose dequeued
<para>Here is an example: this command prints a nicely formatted
version of the <citerefentry>
<refentrytitle>ls</refentrytitle></citerefentry> manual
version of the &man.ls.1; manual
page on the default printer:</para>
<screen>&prompt.user; <userinput>zcat /usr/share/man/man1/ls.1.gz | troff -t -man | lpr -t</userinput></screen>
<para>The <citerefentry>
<refentrytitle>zcat</refentrytitle></citerefentry>
<para>The &man.zcat.1;
command uncompresses the source of the</para>
<para><citerefentry>
<refentrytitle>ls</refentrytitle></citerefentry> manual
page and passes it to the <citerefentry>
<refentrytitle>troff</refentrytitle></citerefentry>
<para>&man.ls.1; manual
page and passes it to the &man.troff.1;
command, which formats that source and makes GNU troff output
and passes it to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>,
and passes it to &man.lpr.1;,
which submits the job to the LPD spooler. Because we used the
<option>-t</option> option to</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, the
<para>&man.lpr.1;, the
spooler will convert the GNU troff output into a format the
default printer can understand when it prints the job.</para>
@ -2118,8 +2063,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-job-handling">
<title>Job Handling Options</title>
<para>The following options to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> tell
<para>The following options to &man.lpr.1; tell
LPD to handle the job specially:</para>
@ -2200,8 +2144,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-misc">
<title>Header Page Options</title>
<para>These options to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>These options to &man.lpr.1;
adjust the text that normally appears on a job's header page.
If header pages are suppressed for the destination printer,
these options have no effect. See section <link
@ -2252,11 +2195,9 @@ cfA013rose dequeued
<title>Administrating Printers</title>
<para>As an administrator for your printers, you have had to
install, set up, and test them. Using the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
install, set up, and test them. Using the &man.lpc.8;
command, you can interact with your printers in yet more ways.
With <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>, you
With &man.lpc.8;, you
can</para>
@ -2290,14 +2231,11 @@ cfA013rose dequeued
in which case it will continue to print jobs in the queue until
the queue is empty.</para>
<para>In general, you have to have root privileges to use the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
command. Ordinary users can use the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> command
<para>In general, you have to have root privileges to use the &man.lpc.8;
command. Ordinary users can use the &man.lpc.8; command
to get printer status and to restart a hung printer only.</para>
<para>Here is a summary of the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
<para>Here is a summary of the &man.lpc.8;
commands. Most of the commands takes a <replaceable>printer-name</replaceable> argument to tell on which
printer to operate. You can use <literal>all</literal>
for the <replaceable>printer-name</replaceable> to mean all
@ -2353,8 +2291,7 @@ cfA013rose dequeued
<command>disable</command> followed by
<command>stop</command>. The <replaceable>message</replaceable> appears as the printer's
status whenever a user checks the printer's queue with
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>
&man.lpq.1;
or status with <command>lpc
status</command>.</para>
</listitem>
@ -2437,11 +2374,9 @@ cfA013rose dequeued
</variablelist>
<para><citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> accepts
<para>&man.lpc.8; accepts
the above commands on the command line. If you do not enter any
commands, <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> enters
commands, &man.lpc.8; enters
an interactive mode, where you can enter commands until you type
<command>exit</command>, <command>quit</command>, or end-of-file.</para>
@ -2570,10 +2505,8 @@ cfA013rose dequeued
<para>Which filter LPD starts and the filter's arguments depend on
what is listed in the <filename>/etc/printcap</filename> file
and what arguments the user specified for the job on the</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
and what arguments the user specified for the job on the
&man.lpr.1;
command line. For example, if the user typed <command>lpr
-t</command>, LPD would start the troff filter, listed in the
<literal>tf</literal> capability for the destination
@ -2854,8 +2787,7 @@ fi</programlisting>
text-to-PostScript program you wish. The FreeBSD ports
collection (see <link linkend="ports">The Ports
Collection</link>) includes a full featured text-to-PostScript
program called <citerefentry>
<refentrytitle>a2ps</refentrytitle></citerefentry> that you might want to investigate.</para>
program called <literal>a2ps</literal> that you might want to investigate.</para>
</sect3>
@ -2886,10 +2818,9 @@ fi</programlisting>
<para>Here is an example: the following script is a text filter
for Hewlett Packard DeskJet 500 printers. For other printers,
substitute the <option>-sDEVICE</option> argument to the</para>
substitute the <option>-sDEVICE</option> argument to the
<para><citerefentry>
<refentrytitle>gs</refentrytitle></citerefentry> (Ghostscript) command. (Type <command>gs -h</command> to get a list of devices the current installation of Ghostscript supports.)</para>
<command>gs</command> (Ghostscript) command. (Type <command>gs -h</command> to get a list of devices the current installation of Ghostscript supports.)</para>
<programlisting>
#!/bin/sh
@ -3127,8 +3058,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
#
exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"</programlisting>
<para>This script runs <citerefentry>
<refentrytitle>dvips</refentrytitle></citerefentry> in filter mode (the <option>-f</option> argument) on standard input, which is the job to print. It then starts the PostScript printer filter <command>lprps</command> (see section <link linkend="printing-advanced-if-conversion">Accommodating Plain Text Jobs on PostScript
<para>This script runs <command>dvips</command> in filter mode (the <option>-f</option> argument) on standard input, which is the job to print. It then starts the PostScript printer filter <command>lprps</command> (see section <link linkend="printing-advanced-if-conversion">Accommodating Plain Text Jobs on PostScript
Printers</link>) with the arguments LPD passed to this script.
<command>lprps</command> will use those arguments
to account for the pages printed.</para>
@ -3238,17 +3168,13 @@ exit 2</programlisting>
<para>Now, for the hard part: making the filter. For that, we
need a DVI-to-LaserJet/PCL conversion program. The FreeBSD
ports collection (see <link linkend="ports">The
Ports Collection</link>) has one: <citerefentry>
<refentrytitle>dvi2xx</refentrytitle></citerefentry> is the
Ports Collection</link>) has one: <command>dvi2xx</command> is the
name of the package. Installing this package gives us the
program we need, <citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry>, which converts DVI into LaserJet IIp, LaserJet III, and LaserJet 2000 compatible codes.</para>
program we need, <command>dvilj2p</command>, which converts DVI into LaserJet IIp, LaserJet III, and LaserJet 2000 compatible codes.</para>
<para><citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> makes
<para><command>dvilj2p</command> makes
the filter <command>hpdf</command> quite complex since
<citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> cannot
<command>dvilj2p</command> cannot
read from standard input. It wants to work with a filename.
What is worse, the filename has to end in
<filename>.dvi</filename> so using
@ -3256,8 +3182,7 @@ exit 2</programlisting>
problematic. We can get around that problem by linking
(symbolically) a temporary file name (one that ends in
<filename>.dvi</filename>) to <filename>/dev/fd/0</filename>,
thereby forcing <citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> to read from standard input.</para>
thereby forcing <command>dvilj2p</command> to read from standard input.</para>
<para>The only other fly in the ointment is the fact that we
cannot use <filename>/tmp</filename> for the temporary link.
@ -3347,8 +3272,7 @@ exit 0</programlisting>
<para>All these conversion filters accomplish a lot for your
printing environment, but at the cost forcing the user to
specify (on the <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
specify (on the &man.lpr.1;
command line) which one to use. If your users are not
particularly computer literate, having to specify a filter
option will become annoying. What is worse, though, is that
@ -3366,8 +3290,8 @@ exit 0</programlisting>
you can still provide conversion filters just for them.</para>
<para>The FreeBSD ports collection has a text filter that
performs automatic conversion called <citerefentry>
<refentrytitle>apsfilter</refentrytitle></citerefentry>. It can detect plain text, PostScript, and DVI files, run the proper conversions, and print.</para>
performs automatic conversion called
<command>apsfilter</command>. It can detect plain text, PostScript, and DVI files, run the proper conversions, and print.</para>
</sect4>
</sect3>
@ -3565,8 +3489,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
they can suppress header pages by submitting the job with
<command>lpr -h</command>; see <link
linkend="printing-lpr-options-misc">Header Page
Options</link> for more <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
Options</link> for more &man.lpr.1;
options.</para>
<note>
@ -4175,8 +4098,7 @@ exit 0;</programlisting>
<para>If you feel multiple copies cause unnecessary wear and tear
on your printers, you can disable the <option>-#</option> option
to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> by
to &man.lpr.1; by
adding the <literal>sc</literal> capability to the
<filename>/etc/printcap</filename> file. When users submit jobs
with the <option>-#</option> option, they will see:</para>
@ -4235,8 +4157,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>By using the <literal>sc</literal>
capability, we prevent the use of <command>lpr -#</command>, but
that still does not prevent users from running <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
that still does not prevent users from running &man.lpr.1;
multiple times, or from submitting the same file multiple times
in one job like this:</para>
@ -4397,10 +4318,8 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
per line. Note that the file
<filename>/etc/hosts.equiv</filename> is also used by
the
<citerefentry><refentrytitle>ruserok</refentrytitle><manvolnum>3</manvolnum></citerefentry> protocol, and affects programs like <citerefentry>
<refentrytitle>rsh</refentrytitle></citerefentry> and
<citerefentry>
<refentrytitle>rcp</refentrytitle></citerefentry>, so be careful.</para>
&man.ruserok.3; protocol, and affects programs like &man.rsh.1; and
&man.rcp.1;, so be careful.</para>
<para>For example, here is the
<filename>/etc/hosts.lpd</filename> file on the host
@ -4567,8 +4486,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
with simple periodic accounting right away. They are the text
filter <command>lpf</command>, described in section
<link linkend="printing-advanced-lpf">lpf: a Text
Filter</link>, and <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>, a
Filter</link>, and &man.pac.8;, a
program to gather and total entries from printer accounting
files.</para>
@ -4606,11 +4524,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<filename>acct</filename>.</para>
<para>When you are ready to charge users for printouts, run
the <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
the &man.pac.8;
program. Just change to the spooling directory for the printer
you want to collect on and type <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>. You
you want to collect on and type <literal>pac</literal>. You
will get a dollar-centric summary like the following:</para>
@ -4626,8 +4542,7 @@ rose:root 26.00 12 $ 0.52
total 337.00 154 $ 6.74</screen>
<para>These are the arguments <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
<para>These are the arguments &man.pac.8;
expects:</para>
<variablelist>
@ -4694,8 +4609,7 @@ total 337.00 154 $ 6.74</screen>
</varlistentry>
</variablelist>
<para>In the default summary that <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
<para>In the default summary that &man.pac.8;
produces, you see the number of pages printed by each user from
various hosts. If, at your site, host does not matter (because
users can use any host), run <command>pac -m</command>, to
@ -4713,15 +4627,13 @@ total 337.00 154 $ 6.74</screen>
<para>To compute the dollar amount due,
<citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry> uses
&man.pac.8; uses
the <literal>pc</literal> capability in the
<filename>/etc/printcap</filename> file (default of 200, or 2
cents per page). Specify, in hundredths of cents, the price per
page or per foot you want to charge for printouts in this
capability. You can override this value when you run
<citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry> with
&man.pac.8; with
the <option>-p</option> option. The units for the
<option>-p</option> option are in dollars, though, not
hundredths of cents. For example,
@ -4738,8 +4650,7 @@ total 337.00 154 $ 6.74</screen>
summary information in a summary accounting file, which is named
the same as the printer's accounting file, but with
<literal>_sum</literal> appended to the name. It then truncates
the accounting file. When you run <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
the accounting file. When you run &man.pac.8;
again, it rereads the summary file to get starting totals, then
adds information from the regular accounting file.</para>
@ -4768,10 +4679,9 @@ total 337.00 154 $ 6.74</screen>
<para>How do you handle other file formats, though?</para>
<para>Well, for DVI-to-LaserJet or DVI-to-PostScript conversion,
you can have your filter parse the diagnostic output of <citerefentry>
<refentrytitle>dvilj</refentrytitle></citerefentry> or
<citerefentry>
<refentrytitle>dvips</refentrytitle></citerefentry> and look to see how many pages were converted. You might be able to do similar things with other file formats and conversion programs.</para>
you can have your filter parse the diagnostic output of
<command>dvilj</command> or
<command>dvips</command> and look to see how many pages were converted. You might be able to do similar things with other file formats and conversion programs.</para>
<para>But these methods suffer from the fact that the printer may
not actually print all those pages. For example, it could jam,

16
en/handbook/security/chapter.sgml
View file

@ -372,7 +372,7 @@ Reminder - Do not use this program while logged in via telnet or rlogin.
can be used to configure restrictions on the use of UNIX passwords
based on the host name, user name, terminal port, or IP address of
a login session. The complete format of the file is documented in
the <citerefentry><refentrytitle>skey.access</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page; there are
the &man.skey.access.5; manual page; there are
also some security cautions there which should be read before
depending on this file for security.</para>
@ -1044,7 +1044,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<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,
<citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Together, they allow you to define and
&man.ipfw.8;. Together, they allow you to define and
query the rules currently used by the kernel in its routing
decisions.</para>
@ -1091,7 +1091,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Enables code to allow logging of packets through
<citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Without this option, even
&man.syslogd.8;. Without this option, even
if you specify that packets should be logged in the filter
rules, nothing will happen.</para>
</listitem>
@ -1101,7 +1101,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Limits the number of packets logged through
<citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry> on a per entry basis. You
&man.syslogd.8; on a per entry basis. You
may wish to use this option in hostile environments in
which you want to log firewall activity, but do not want
to be open to a denial of service attack via syslog
@ -1110,7 +1110,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<para>When a chain entry reaches the packet limit specified,
logging is turned off for that particular entry. To
resume logging, you will need to reset the associated
counter using the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry>
counter using the &man.ipfw.8;
utility:</para>
@ -1135,7 +1135,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<title>Configuring IPFW</title>
<para>The configuration of the <application>IPFW</application> software is
done through the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry> utility. The syntax
done through the &man.ipfw.8; utility. The syntax
for this command looks quite complicated, but it is relatively
simple once you understand its structure.</para>
@ -1443,7 +1443,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<literal>5</literal> redirect, <literal>8</literal> echo request (ping request), and
<literal>11</literal> time exceeded (used to
indicate TTL expiration as with
<citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry>).</para>
&man.traceroute.8;).</para>
</listitem>
</varlistentry>
</variablelist>
@ -1480,7 +1480,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Display the last match times for each chain entry.
The time listing is incompatible with the input syntax
used by the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry> utility.</para>
used by the &man.ipfw.8; utility.</para>
</listitem>
</varlistentry>

28
en/handbook/serialcomms/chapter.sgml
View file

@ -381,7 +381,7 @@
</itemizedlist>
<para>See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for more information.</para>
<para>See the &man.sio.4; manual page for more information.</para>
<para>If you have connected a terminal to the first serial port
(<devicename>COM1</devicename> in DOS parlance), then you want to use
@ -451,7 +451,7 @@
<replaceable>getty</replaceable> type for use in step 2 by making an
entry in <filename>/etc/gettytab</filename>. This document does
not explain how to do so; you are encouraged to see the
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> and the <citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual pages for more
man.gettytab.5; and the &man.getty.8; manual pages for more
information.</para>
<para>The remaining sections detail how to do these steps. We will
@ -463,7 +463,7 @@
port on a multiport serial card).</para>
<para>For more information on the <filename>/etc/ttys</filename>
file, see the <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page.</para>
file, see the &man.ttys.5; manual page.</para>
<sect3 id="term-etcttys">
@ -523,7 +523,7 @@ ttyd5</programlisting>
cases, the entries that start with the text <literal>std</literal> will work for hardwired terminals.
These entries ignore parity. There is a <literal>std</literal> entry for each bps rate from 110 to
115200. Of course, you can add your own entries to this file.
The manual page <citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> provides more information.</para>
The manual page &man.gettytab.5; provides more information.</para>
<para>When setting the <replaceable>getty</replaceable> type in
the <filename>/etc/ttys</filename> file, make sure that the
@ -566,7 +566,7 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
<para>To find out what terminal types FreeBSD supports, see the
file <filename>/usr/share/misc/termcap</filename>. It lists
about 600 terminal types. You can add more if you wish. See
the <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page for information.</para>
the &man.termcap.5; manual page for information.</para>
<para>In our example, the Wyse-50 is a Wyse-50 type of terminal
(although it can emulate others, we will leave it in Wyse-50
@ -1029,7 +1029,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<devicename>COM1:</devicename>, <devicename>COM2:</devicename>,
<devicename>COM3:</devicename>, and <devicename>COM4:</devicename>. FreeBSD can presently also handle
&ldquo;dumb&rdquo; multiport serial interface cards, such as the Boca Board
1008 and 2016 (please see the manual page <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for kernel configuration information
1008 and 2016 (please see the manual page &man.sio.4; for kernel configuration information
if you have a multiport serial card). The default kernel only
looks for the standard COM ports, though.</para>
@ -1089,7 +1089,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>You can comment-out or completely remove lines for devices you
do not have. If you have a multiport serial board, such as the
Boca Board BB2016, please see the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> man page for complete information on
Boca Board BB2016, please see the &man.sio.4; man page for complete information on
how to write configuration lines for multiport boards. Be careful
if you are using a configuration file that was previously used for
a different version of FreeBSD because the device flags have
@ -1112,7 +1112,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>When you are finished adjusting the kernel configuration file,
use the program <command>config</command> as documented
in &ldquo;Building Berkeley Kernels with Config&rdquo; and the
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual page to prepare a kernel
&man.config.8; manual page to prepare a kernel
building directory, then build, install, and test the new
kernel.</para>
@ -1136,7 +1136,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
modems which use <literal>CTS/RTS</literal> signaling for flow
control. The locking devices are used to lock flags on ports to
prevent users or programs changing certain parameters; see the
manual pages <citerefentry><refentrytitle>termios</refentrytitle><manvolnum>4</manvolnum></citerefentry>, <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry>, and <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
manual pages &man.termios.4;, &man.sio.4;, and &man.stty.1; for
information on the terminal settings, locking &amp; initializing
devices, and setting terminal options, respectively.</para>
@ -1146,7 +1146,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>A shell script called <command>MAKEDEV</command> in the
<filename>/dev</filename> directory manages the device special
files. (The manual page for <citerefentry><refentrytitle>MAKEDEV</refentrytitle><manvolnum>8</manvolnum></citerefentry> on
files. (The manual page for &man.MAKEDEV.8; on
FreeBSD 1.1.5 is fairly bogus in its discussion of
<acronym>COM</acronym> ports, so ignore it.) To use
<command>MAKEDEV</command> to make dialup device special files
@ -1237,9 +1237,9 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
<sect3>
<title><filename>/etc/gettytab</filename></title>
<para><filename>/etc/gettytab</filename> is a <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry>-style file of configuration
information for <citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Please see the
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page for
<para><filename>/etc/gettytab</filename> is a &man.termcap.5;-style file of configuration
information for &man.getty.8;. Please see the
&man.gettytab.5; manual page for
complete information on the format of the file and the list of
capabilities.</para>
@ -1348,7 +1348,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
information to <command>login</command> (user
<username>root</username> may only login on ttys marked
<literal>secure</literal>). See the manual page for
<citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more
&man.ttys.5; for more
information.</para>
<para>You will need to either modify existing lines in

224
en_US.ISO8859-1/articles/contributing/article.sgml
View file

@ -458,12 +458,12 @@
information about this and other mailing lists.</para>
<para>If you find a bug or are submitting a specific change, please
report it using the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>program or its
report it using the &man.send-pr.1; program or its
<ulink URL="http://www.freebsd.org/send-pr.html">WEB-based
equivalent</ulink>. Try to fill-in each field of the bug report.
Unless they exceed 65KB, include any patches directly in the
report. Consider compressing them and using
<citerefentry><refentrytitle>uuencode</refentrytitle><manvolnum>1</manvolnum></citerefentry> if they exceed 20KB. Upload very large submissions to <ulink url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp.freebsd.org:/pub/FreeBSD/incoming/</ulink>.</para>
&man.uuencode.1; if they exceed 20KB. Upload very large submissions to <ulink url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp.freebsd.org:/pub/FreeBSD/incoming/</ulink>.</para>
<para>After filing a report, you should receive confirmation along
with a tracking number. Keep this tracking number so that you can
@ -471,7 +471,7 @@
<para>If you do not receive confirmation in a timely fashion (3 days
to a week, depending on your email connection) or are, for some
reason, unable to use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> command,
reason, unable to use the &man.send-pr.1; command,
then you may ask someone to file it for you by sending mail to the
&a.bugs;.</para>
@ -511,7 +511,7 @@
<para>Assuming that you can manage to secure fairly up-to-date
sources to base your changes on, the next step is to produce a set
of diffs to send to the FreeBSD maintainers. This is done with
the <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, with the &ldquo;context diff&rdquo;
the &man.diff.1; command, with the &ldquo;context diff&rdquo;
form being preferred. For example:</para>
<para>
@ -526,11 +526,11 @@
would generate such a set of context diffs for
the given source file or directory hierarchy. See the man page
for <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> for more details.</para>
for &man.diff.1; for more details.</para>
<para>Once you have a set of diffs (which you may test with the
<citerefentry><refentrytitle>patch</refentrytitle><manvolnum>1</manvolnum></citerefentry> command), you should submit them for
inclusion with FreeBSD. Use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
&man.patch.1; command), you should submit them for
inclusion with FreeBSD. Use the &man.send-pr.1;
program as described in
<link linkend="contrib-general">Bug Reports and General
Commentary</link>. <emphasis>Do not</emphasis> just send the diffs to
@ -541,14 +541,14 @@
<para>If you feel it appropriate (e.g. you have added, deleted, or
renamed files), bundle your changes into a <command>tar</command> file and run the
<citerefentry><refentrytitle>uuencode</refentrytitle><manvolnum>1</manvolnum></citerefentry> program on it. Shar archives are
&man.uuencode.1; program on it. Shar archives are
also welcome.</para>
<para>If your change is of a potentially sensitive nature, e.g. you
are unsure of copyright issues governing its further distribution
or you are simply not ready to release it without a tighter review
first, then you should send it to &a.core; directly rather than
submitting it with <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The core
submitting it with &man.send-pr.1;. The core
mailing list reaches a much smaller group of people who do much of
the day-to-day work on FreeBSD. Note that this group is also
<emphasis>very busy</emphasis> and so you should only send mail to
@ -1143,9 +1143,9 @@ box can be opened)</para>
<listitem><para>Adrian Mariano <email>adrian@cam.cornell.edu</email></para></listitem>
<listitem><para>Adrian Steinmann <email>ast@marabu.ch</email></para></listitem>
<listitem><para>Adrian T. Filipi-Martin <email>atf3r@agate.cs.virginia.edu</email></para></listitem>
<listitem><para>Ajit Thyagarajan</para></listitem>
<listitem><para>Ajit Thyagarajan <email>unknown</email></para></listitem>
<listitem><para>Akio Morita <email>amorita@meadow.scphys.kyoto-u.ac.jp</email></para></listitem>
<listitem><para>Akira SAWADA</para></listitem>
<listitem><para>Akira SAWADA <email>unknown</email></para></listitem>
<listitem><para>Akira Watanabe <email>akira@myaw.ei.meisei-u.ac.jp</email></para></listitem>
<listitem><para>Akito Fujita <email>fujita@zoo.ncl.omron.co.jp</email></para></listitem>
<listitem><para>Alain Kalker <email>A.C.P.M.Kalker@student.utwente.nl</email></para></listitem>
@ -1177,10 +1177,10 @@ box can be opened)</para>
<listitem><para>Andreas Haakh <email>ah@alman.robin.de</email></para></listitem>
<listitem><para>Andreas Kohout <email>shanee@rabbit.augusta.de</email></para></listitem>
<listitem><para>Andreas Lohr <email>andreas@marvin.RoBIN.de</email></para></listitem>
<listitem><para>Andreas Schulz</para></listitem>
<listitem><para>Andreas Schulz <email>unknown</email></para></listitem>
<listitem><para>Andreas Wetzel <email>mickey@deadline.snafu.de</email></para></listitem>
<listitem><para>Andreas Wrede <email>andreas@planix.com</email></para></listitem>
<listitem><para>Andres Vega Garcia</para></listitem>
<listitem><para>Andres Vega Garcia <email>unknown</email></para></listitem>
<listitem><para>Andrew Atrens <email>atreand@statcan.ca</email></para></listitem>
<listitem><para>Andrew Gillham <email>gillham@andrews.edu</email></para></listitem>
<listitem><para>Andrew Gordon <email>andrew.gordon@net-tel.co.uk</email></para></listitem>
@ -1212,7 +1212,7 @@ box can be opened)</para>
<listitem><para>Barry Bierbauch <email>pivrnec@vszbr.cz</email></para></listitem>
<listitem><para>Barry Lustig <email>barry@ictv.com</email></para></listitem>
<listitem><para>Ben Hutchinson <email>benhutch@xfiles.org.uk</email></para></listitem>
<listitem><para>Ben Jackson</para></listitem>
<listitem><para>Ben Jackson <email>unknown</email></para></listitem>
<listitem><para>Ben Smithurst <email>ben@scientia.demon.co.uk</email></para></listitem>
<listitem><para>Ben Walter <email>bwalter@itachi.swcp.com</email></para></listitem>
<listitem><para>Benjamin Lewis <email>bhlewis@gte.net</email></para></listitem>
@ -1264,7 +1264,7 @@ box can be opened)</para>
<listitem><para>Chet Ramey <email>chet@odin.INS.CWRU.Edu</email></para></listitem>
<listitem><para>Chia-liang Kao <email>clkao@CirX.ORG</email></para></listitem>
<listitem><para>Chiharu Shibata <email>chi@bd.mbn.or.jp</email></para></listitem>
<listitem><para>Chip Norkus</para></listitem>
<listitem><para>Chip Norkus <email>unknown</email></para></listitem>
<listitem><para>Choi Jun Ho <email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para>Chris Csanady <email>cc@tarsier.ca.sandia.gov</email></para></listitem>
<listitem><para>Chris Dabrowski <email>chris@vader.org</email></para></listitem>
@ -1291,7 +1291,7 @@ box can be opened)</para>
<listitem><para>Cornelis van der Laan <email>nils@guru.ims.uni-stuttgart.de</email></para></listitem>
<listitem><para>Cove Schneider <email>cove@brazil.nbn.com</email></para></listitem>
<listitem><para>Craig Leres <email>leres@ee.lbl.gov</email></para></listitem>
<listitem><para>Craig Loomis</para></listitem>
<listitem><para>Craig Loomis <email>unknown</email></para></listitem>
<listitem><para>Craig Metz <email>cmetz@inner.net</email></para></listitem>
<listitem><para>Craig Spannring <email>cts@internetcds.com</email></para></listitem>
<listitem><para>Craig Struble <email>cstruble@vt.edu</email></para></listitem>
@ -1310,7 +1310,7 @@ box can be opened)</para>
<listitem><para>Daniel O'Connor <email>doconnor@gsoft.com.au</email></para></listitem>
<listitem><para>Daniel Poirot <email>poirot@aio.jsc.nasa.gov</email></para></listitem>
<listitem><para>Daniel Rock <email>rock@cs.uni-sb.de</email></para></listitem>
<listitem><para>Danny Egen</para></listitem>
<listitem><para>Danny Egen <email>unknown</email></para></listitem>
<listitem><para>Danny J. Zerkel <email>dzerkel@phofarm.com</email></para></listitem>
<listitem><para>Darren Reed <email>avalon@coombs.anu.edu.au</email></para></listitem>
<listitem><para>Dave Adkins <email>adkin003@tc.umn.edu</email></para></listitem>
@ -1344,7 +1344,7 @@ box can be opened)</para>
<listitem><para>David Wolfskill <email>dhw@whistle.com</email></para></listitem>
<listitem><para>Dean Gaudet <email>dgaudet@arctic.org</email></para></listitem>
<listitem><para>Dean Huxley <email>dean@fsa.ca</email></para></listitem>
<listitem><para>Denis Fortin</para></listitem>
<listitem><para>Denis Fortin <email>unknown</email></para></listitem>
<listitem><para>Dennis Glatting <email>dennis.glatting@software-munitions.com</email></para></listitem>
<listitem><para>Denton Gentry <email>denny1@home.com</email></para></listitem>
<listitem><para>Derek Inksetter <email>derek@saidev.com</email></para></listitem>
@ -1450,7 +1450,7 @@ box can be opened)</para>
<listitem><para>Harold Barker <email>hbarker@dsms.com</email></para></listitem>
<listitem><para>Havard Eidnes <email>Havard.Eidnes@runit.sintef.no</email></para></listitem>
<listitem><para>Heikki Suonsivu <email>hsu@cs.hut.fi</email></para></listitem>
<listitem><para>Heiko W. Rupp</para></listitem>
<listitem><para>Heiko W. Rupp <email>unknown</email></para></listitem>
<listitem><para>Helmut F. Wirth <email>hfwirth@ping.at</email></para></listitem>
<listitem><para>Henrik Vestergaard Draboel <email>hvd@terry.ping.dk</email></para></listitem>
<listitem><para>Herb Peyerl <email>hpeyerl@NetBSD.org</email></para></listitem>
@ -1464,7 +1464,7 @@ box can be opened)</para>
<listitem><para>Hiroharu Tamaru <email>tamaru@ap.t.u-tokyo.ac.jp</email></para></listitem>
<listitem><para>Hironori Ikura <email>hikura@kaisei.org</email></para></listitem>
<listitem><para>Hiroshi Nishikawa <email>nis@pluto.dti.ne.jp</email></para></listitem>
<listitem><para>Hiroya Tsubakimoto</para></listitem>
<listitem><para>Hiroya Tsubakimoto <email>unknown</email></para></listitem>
<listitem><para>Hiroyuki NAKAJI <email>nakaji@zeisei3.dpri.kyoto-u.ac.jp</email></para></listitem>
<listitem><para>Holger Veit <email>Holger.Veit@gmd.de</email></para></listitem>
<listitem><para>Holm Tiffe <email>holm@geophysik.tu-freiberg.de</email></para></listitem>
@ -1527,7 +1527,7 @@ box can be opened)</para>
<listitem><para>Jeremy Allison <email>jallison@whistle.com</email></para></listitem>
<listitem><para>Jeremy Chatfield <email>jdc@xinside.com</email></para></listitem>
<listitem><para>Jeremy Lea <email>reg@shale.csir.co.za</email></para></listitem>
<listitem><para>Jeremy Prior</para></listitem>
<listitem><para>Jeremy Prior <email>unknown</email></para></listitem>
<listitem><para>Jeroen Ruigrok/Asmodai <email>asmodai@wxs.nl</email></para></listitem>
<listitem><para>Jesse Rosenstock <email>jmr@ugcs.caltech.edu</email></para></listitem>
<listitem><para>Jian-Da Li <email>jdli@csie.nctu.edu.tw</email></para></listitem>
@ -1543,7 +1543,7 @@ box can be opened)</para>
<listitem><para>Jim Wilson <email>wilson@moria.cygnus.com</email></para></listitem>
<listitem><para>Jimbo Bahooli <email>griffin@blackhole.iceworld.org</email></para></listitem>
<listitem><para>Jin Guojun <email>jin@george.lbl.gov</email></para></listitem>
<listitem><para>Joachim Kuebart</para></listitem>
<listitem><para>Joachim Kuebart <email>unknown</email></para></listitem>
<listitem><para>Joao Carlos Mendes Luis <email>jonny@jonny.eng.br</email></para></listitem>
<listitem><para>Jochen Pohl <email>jpo.drs@sni.de</email></para></listitem>
<listitem><para>Joe "Marcus" Clarke <email>marcus@miami.edu</email></para></listitem>
@ -1558,19 +1558,19 @@ box can be opened)</para>
<listitem><para>Johan Karlsson <email>k@numeri.campus.luth.se</email></para></listitem>
<listitem><para>Johan Larsson <email>johan@moon.campus.luth.se</email></para></listitem>
<listitem><para>Johann Tonsing <email>jtonsing@mikom.csir.co.za</email></para></listitem>
<listitem><para>Johannes Helander</para></listitem>
<listitem><para>Johannes Stille</para></listitem>
<listitem><para>Johannes Helander <email>unknown</email></para></listitem>
<listitem><para>Johannes Stille <email>unknown</email></para></listitem>
<listitem><para>John Baldwin <email>jobaldwi@vt.edu</email></para></listitem>
<listitem><para>John Beckett <email>jbeckett@southern.edu</email></para></listitem>
<listitem><para>John Beukema <email>jbeukema@hk.super.net</email></para></listitem>
<listitem><para>John Brezak</para></listitem>
<listitem><para>John Brezak <email>unknown</email></para></listitem>
<listitem><para>John Capo <email>jc@irbs.com</email></para></listitem>
<listitem><para>John F. Woods <email>jfw@jfwhome.funhouse.com</email></para></listitem>
<listitem><para>John Goerzen <email>jgoerzen@alexanderwohl.complete.org</email></para></listitem>
<listitem><para>John Hay <email>jhay@mikom.csir.co.za</email></para></listitem>
<listitem><para>John Heidemann <email>johnh@isi.edu</email></para></listitem>
<listitem><para>John Hood <email>cgull@owl.org</email></para></listitem>
<listitem><para>John Kohl</para></listitem>
<listitem><para>John Kohl <email>unknown</email></para></listitem>
<listitem><para>John Lind <email>john@starfire.mn.org</email></para></listitem>
<listitem><para>John Mackin <email>john@physiol.su.oz.au</email></para></listitem>
<listitem><para>John P <email>johnp@lodgenet.com</email></para></listitem>
@ -1620,10 +1620,10 @@ box can be opened)</para>
<listitem><para>Kazuo Horikawa <email>horikawa@jp.FreeBSD.org</email></para></listitem>
<listitem><para>Kees Jan Koster <email>kjk1@ukc.ac.uk</email></para></listitem>
<listitem><para>Keith Bostic <email>bostic@bostic.com</email></para></listitem>
<listitem><para>Keith E. Walker</para></listitem>
<listitem><para>Keith Moore</para></listitem>
<listitem><para>Keith Sklower</para></listitem>
<listitem><para>Ken Hornstein</para></listitem>
<listitem><para>Keith E. Walker <email>unknown</email></para></listitem>
<listitem><para>Keith Moore <email>unknown</email></para></listitem>
<listitem><para>Keith Sklower <email>unknown</email></para></listitem>
<listitem><para>Ken Hornstein <email>unknown</email></para></listitem>
<listitem><para>Ken Key <email>key@cs.utk.edu</email></para></listitem>
<listitem><para>Ken Mayer <email>kmayer@freegate.com</email></para></listitem>
<listitem><para>Kenji Saito <email>marukun@mx2.nisiq.net</email></para></listitem>
@ -1659,7 +1659,7 @@ box can be opened)</para>
<listitem><para>Louis Mamakos <email>loiue@TransSys.com</email></para></listitem>
<listitem><para>Lucas James <email>Lucas.James@ldjpc.apana.org.au</email></para></listitem>
<listitem><para>Lyndon Nerenberg <email>lyndon@orthanc.com</email></para></listitem>
<listitem><para>M.C. Wong</para></listitem>
<listitem><para>M.C. Wong <email>unknown</email></para></listitem>
<listitem><para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para></listitem>
<listitem><para>MIHIRA Sanpei Yoshiro <email>sanpei@sanpei.org</email></para></listitem>
<listitem><para>MITA Yoshio <email>mita@jp.FreeBSD.ORG</email></para></listitem>
@ -1677,7 +1677,7 @@ box can be opened)</para>
<listitem><para>Marc van Kempen <email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para>Marcel Moolenaar <email>marcel@scc.nl</email></para></listitem>
<listitem><para>Mario Sergio Fujikawa Ferreira <email>lioux@gns.com.br</email></para></listitem>
<listitem><para>Mark Andrews</para></listitem>
<listitem><para>Mark Andrews <email>unknown</email></para></listitem>
<listitem><para>Mark Cammidge <email>mark@gmtunx.ee.uct.ac.za</email></para></listitem>
<listitem><para>Mark Diekhans <email>markd@grizzly.com</email></para></listitem>
<listitem><para>Mark Huizer <email>xaa@stack.nl</email></para></listitem>
@ -1686,7 +1686,7 @@ box can be opened)</para>
<listitem><para>Mark Mayo <email>markm@vmunix.com</email></para></listitem>
<listitem><para>Mark Thompson <email>thompson@tgsoft.com</email></para></listitem>
<listitem><para>Mark Tinguely <email>tinguely@plains.nodak.edu</email></para></listitem>
<listitem><para>Mark Treacy</para></listitem>
<listitem><para>Mark Treacy <email>unknown</email></para></listitem>
<listitem><para>Mark Valentine <email>mark@linus.demon.co.uk</email></para></listitem>
<listitem><para>Martin Birgmeier</para></listitem>
<listitem><para>Martin Ibert <email>mib@ppe.bb-data.de</email></para></listitem>
@ -1694,7 +1694,7 @@ box can be opened)</para>
<listitem><para>Martin Renters <email>martin@tdc.on.ca</email></para></listitem>
<listitem><para>Martti Kuparinen <email>erakupa@kk.etx.ericsson.se</email></para></listitem>
<listitem><para>Masachika ISHIZUKA <email>ishizuka@isis.min.ntt.jp</email></para></listitem>
<listitem><para>Mas.TAKEMURA</para></listitem>
<listitem><para>Mas.TAKEMURA <email>unknown</email></para></listitem>
<listitem><para>Masafumi NAKANE <email>max@wide.ad.jp</email></para></listitem>
<listitem><para>Masahiro Sekiguchi <email>seki@sysrap.cs.fujitsu.co.jp</email></para></listitem>
<listitem><para>Masanobu Saitoh <email>msaitoh@spa.is.uec.ac.jp</email></para></listitem>
@ -1745,7 +1745,7 @@ box can be opened)</para>
<listitem><para>Mike Evans <email>mevans@candle.com</email></para></listitem>
<listitem><para>Mike Grupenhoff <email>kashmir@umiacs.umd.edu</email></para></listitem>
<listitem><para>Mike Hibler <email>mike@marker.cs.utah.edu</email></para></listitem>
<listitem><para>Mike Karels</para></listitem>
<listitem><para>Mike Karels <email>unknown</email></para></listitem>
<listitem><para>Mike McGaughey <email>mmcg@cs.monash.edu.au</email></para></listitem>
<listitem><para>Mike Meyer <email>mwm@shiva.the-park.com</email></para></listitem>
<listitem><para>Mike Mitchell <email>mitchell@ref.tfs.com</email></para></listitem>
@ -1787,71 +1787,71 @@ box can be opened)</para>
<listitem><para>Nickolay N. Dudorov <email>nnd@itfs.nsk.su</email></para></listitem>
<listitem><para>Niklas Hallqvist <email>niklas@filippa.appli.se</email></para></listitem>
<listitem><para>Nisha Talagala <email>nisha@cs.berkeley.edu</email></para></listitem>
<listitem><para><email>ZW6T-KND@j.asahi-net.or.jp</email></para></listitem>
<listitem><para><email>adrian@virginia.edu</email></para></listitem>
<listitem><para><email>alex@elvisti.kiev.ua</email></para></listitem>
<listitem><para><email>anto@netscape.net</email></para></listitem>
<listitem><para><email>bobson@egg.ics.nitch.ac.jp</email></para></listitem>
<listitem><para><email>bovynf@awe.be</email></para></listitem>
<listitem><para><email>burg@is.ge.com</email></para></listitem>
<listitem><para><email>chris@gnome.co.uk</email></para></listitem>
<listitem><para><email>colsen@usa.net</email></para></listitem>
<listitem><para><email>coredump@nervosa.com</email></para></listitem>
<listitem><para><email>dannyman@arh0300.urh.uiuc.edu</email></para></listitem>
<listitem><para><email>davids@SECNET.COM</email></para></listitem>
<listitem><para><email>derek@free.org</email></para></listitem>
<listitem><para><email>devet@adv.IAEhv.nl</email></para></listitem>
<listitem><para><email>djv@bedford.net</email></para></listitem>
<listitem><para><email>dvv@sprint.net</email></para></listitem>
<listitem><para><email>enami@ba2.so-net.or.jp</email></para></listitem>
<listitem><para><email>flash@eru.tubank.msk.su</email></para></listitem>
<listitem><para><email>flash@hway.ru</email></para></listitem>
<listitem><para><email>fn@pain.csrv.uidaho.edu</email></para></listitem>
<listitem><para><email>gclarkii@netport.neosoft.com</email></para></listitem>
<listitem><para><email>gordon@sheaky.lonestar.org</email></para></listitem>
<listitem><para><email>graaf@iae.nl</email></para></listitem>
<listitem><para><email>greg@greg.rim.or.jp</email></para></listitem>
<listitem><para><email>grossman@cygnus.com</email></para></listitem>
<listitem><para><email>gusw@fub46.zedat.fu-berlin.de</email></para></listitem>
<listitem><para><email>hfir@math.rochester.edu</email></para></listitem>
<listitem><para><email>hnokubi@yyy.or.jp</email></para></listitem>
<listitem><para><email>iaint@css.tuu.utas.edu.au</email></para></listitem>
<listitem><para><email>invis@visi.com</email></para></listitem>
<listitem><para><email>ishisone@sra.co.jp</email></para></listitem>
<listitem><para><email>iverson@lionheart.com</email></para></listitem>
<listitem><para><email>jpt@magic.net</email></para></listitem>
<listitem><para><email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para><email>k-sugyou@ccs.mt.nec.co.jp</email></para></listitem>
<listitem><para><email>kenji@reseau.toyonaka.osaka.jp</email></para></listitem>
<listitem><para><email>kfurge@worldnet.att.net</email></para></listitem>
<listitem><para><email>lh@aus.org</email></para></listitem>
<listitem><para><email>lhecking@nmrc.ucc.ie</email></para></listitem>
<listitem><para><email>mrgreen@mame.mu.oz.au</email></para></listitem>
<listitem><para><email>nakagawa@jp.freebsd.org</email></para></listitem>
<listitem><para><email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para></listitem>
<listitem><para><email>owaki@st.rim.or.jp</email></para></listitem>
<listitem><para><email>pechter@shell.monmouth.com</email></para></listitem>
<listitem><para><email>pete@pelican.pelican.com</email></para></listitem>
<listitem><para><email>pritc003@maroon.tc.umn.edu</email></para></listitem>
<listitem><para><email>risner@stdio.com</email></para></listitem>
<listitem><para><email>roman@rpd.univ.kiev.ua</email></para></listitem>
<listitem><para><email>root@ns2.redline.ru</email></para></listitem>
<listitem><para><email>root@uglabgw.ug.cs.sunysb.edu</email></para></listitem>
<listitem><para><email>stephen.ma@jtec.com.au</email></para></listitem>
<listitem><para><email>sumii@is.s.u-tokyo.ac.jp</email></para></listitem>
<listitem><para><email>takas-su@is.aist-nara.ac.jp</email></para></listitem>
<listitem><para><email>tamone@eig.unige.ch</email></para></listitem>
<listitem><para><email>tjevans@raleigh.ibm.com</email></para></listitem>
<listitem><para><email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para></listitem>
<listitem><para><email>torii@tcd.hitachi.co.jp</email></para></listitem>
<listitem><para><email>uenami@imasy.or.jp</email></para></listitem>
<listitem><para><email>uhlar@netlab.sk</email></para></listitem>
<listitem><para><email>vode@hut.fi</email></para></listitem>
<listitem><para><email>wlloyd@mpd.ca</email></para></listitem>
<listitem><para><email>wlr@furball.wellsfargo.com</email></para></listitem>
<listitem><para><email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para><email>yamagata@nwgpc.kek.jp</email></para></listitem>
<listitem><para><email>ziggy@ryan.org</email></para></listitem>
<listitem><para>No Name <email>ZW6T-KND@j.asahi-net.or.jp</email></para></listitem>
<listitem><para>No Name <email>adrian@virginia.edu</email></para></listitem>
<listitem><para>No Name <email>alex@elvisti.kiev.ua</email></para></listitem>
<listitem><para>No Name <email>anto@netscape.net</email></para></listitem>
<listitem><para>No Name <email>bobson@egg.ics.nitch.ac.jp</email></para></listitem>
<listitem><para>No Name <email>bovynf@awe.be</email></para></listitem>
<listitem><para>No Name <email>burg@is.ge.com</email></para></listitem>
<listitem><para>No Name <email>chris@gnome.co.uk</email></para></listitem>
<listitem><para>No Name <email>colsen@usa.net</email></para></listitem>
<listitem><para>No Name <email>coredump@nervosa.com</email></para></listitem>
<listitem><para>No Name <email>dannyman@arh0300.urh.uiuc.edu</email></para></listitem>
<listitem><para>No Name <email>davids@SECNET.COM</email></para></listitem>
<listitem><para>No Name <email>derek@free.org</email></para></listitem>
<listitem><para>No Name <email>devet@adv.IAEhv.nl</email></para></listitem>
<listitem><para>No Name <email>djv@bedford.net</email></para></listitem>
<listitem><para>No Name <email>dvv@sprint.net</email></para></listitem>
<listitem><para>No Name <email>enami@ba2.so-net.or.jp</email></para></listitem>
<listitem><para>No Name <email>flash@eru.tubank.msk.su</email></para></listitem>
<listitem><para>No Name <email>flash@hway.ru</email></para></listitem>
<listitem><para>No Name <email>fn@pain.csrv.uidaho.edu</email></para></listitem>
<listitem><para>No Name <email>gclarkii@netport.neosoft.com</email></para></listitem>
<listitem><para>No Name <email>gordon@sheaky.lonestar.org</email></para></listitem>
<listitem><para>No Name <email>graaf@iae.nl</email></para></listitem>
<listitem><para>No Name <email>greg@greg.rim.or.jp</email></para></listitem>
<listitem><para>No Name <email>grossman@cygnus.com</email></para></listitem>
<listitem><para>No Name <email>gusw@fub46.zedat.fu-berlin.de</email></para></listitem>
<listitem><para>No Name <email>hfir@math.rochester.edu</email></para></listitem>
<listitem><para>No Name <email>hnokubi@yyy.or.jp</email></para></listitem>
<listitem><para>No Name <email>iaint@css.tuu.utas.edu.au</email></para></listitem>
<listitem><para>No Name <email>invis@visi.com</email></para></listitem>
<listitem><para>No Name <email>ishisone@sra.co.jp</email></para></listitem>
<listitem><para>No Name <email>iverson@lionheart.com</email></para></listitem>
<listitem><para>No Name <email>jpt@magic.net</email></para></listitem>
<listitem><para>No Name <email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para>No Name <email>k-sugyou@ccs.mt.nec.co.jp</email></para></listitem>
<listitem><para>No Name <email>kenji@reseau.toyonaka.osaka.jp</email></para></listitem>
<listitem><para>No Name <email>kfurge@worldnet.att.net</email></para></listitem>
<listitem><para>No Name <email>lh@aus.org</email></para></listitem>
<listitem><para>No Name <email>lhecking@nmrc.ucc.ie</email></para></listitem>
<listitem><para>No Name <email>mrgreen@mame.mu.oz.au</email></para></listitem>
<listitem><para>No Name <email>nakagawa@jp.freebsd.org</email></para></listitem>
<listitem><para>No Name <email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para></listitem>
<listitem><para>No Name <email>owaki@st.rim.or.jp</email></para></listitem>
<listitem><para>No Name <email>pechter@shell.monmouth.com</email></para></listitem>
<listitem><para>No Name <email>pete@pelican.pelican.com</email></para></listitem>
<listitem><para>No Name <email>pritc003@maroon.tc.umn.edu</email></para></listitem>
<listitem><para>No Name <email>risner@stdio.com</email></para></listitem>
<listitem><para>No Name <email>roman@rpd.univ.kiev.ua</email></para></listitem>
<listitem><para>No Name <email>root@ns2.redline.ru</email></para></listitem>
<listitem><para>No Name <email>root@uglabgw.ug.cs.sunysb.edu</email></para></listitem>
<listitem><para>No Name <email>stephen.ma@jtec.com.au</email></para></listitem>
<listitem><para>No Name <email>sumii@is.s.u-tokyo.ac.jp</email></para></listitem>
<listitem><para>No Name <email>takas-su@is.aist-nara.ac.jp</email></para></listitem>
<listitem><para>No Name <email>tamone@eig.unige.ch</email></para></listitem>
<listitem><para>No Name <email>tjevans@raleigh.ibm.com</email></para></listitem>
<listitem><para>No Name <email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para></listitem>
<listitem><para>No Name <email>torii@tcd.hitachi.co.jp</email></para></listitem>
<listitem><para>No Name <email>uenami@imasy.or.jp</email></para></listitem>
<listitem><para>No Name <email>uhlar@netlab.sk</email></para></listitem>
<listitem><para>No Name <email>vode@hut.fi</email></para></listitem>
<listitem><para>No Name <email>wlloyd@mpd.ca</email></para></listitem>
<listitem><para>No Name <email>wlr@furball.wellsfargo.com</email></para></listitem>
<listitem><para>No Name <email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para>No Name <email>yamagata@nwgpc.kek.jp</email></para></listitem>
<listitem><para>No Name <email>ziggy@ryan.org</email></para></listitem>
<listitem><para>Nobuhiro Yasutomi <email>nobu@psrc.isac.co.jp</email></para></listitem>
<listitem><para>Nobuyuki Koganemaru <email>kogane@koganemaru.co.jp</email></para></listitem>
<listitem><para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para></listitem>
@ -1873,15 +1873,15 @@ box can be opened)</para>
<listitem><para>Pascal Pederiva <email>pascal@zuo.dec.com</email></para></listitem>
<listitem><para>Pasvorn Boonmark <email>boonmark@juniper.net</email></para></listitem>
<listitem><para>Patrick Gardella <email>patrick@cre8tivegroup.com</email></para></listitem>
<listitem><para>Patrick Hausen</para></listitem>
<listitem><para>Patrick Hausen <email>unknown</email></para></listitem>
<listitem><para>Paul Antonov <email>apg@demos.su</email></para></listitem>
<listitem><para>Paul F. Werkowski</para></listitem>
<listitem><para>Paul F. Werkowski <email>unknown</email></para></listitem>
<listitem><para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para></listitem>
<listitem><para>Paul Koch <email>koch@thehub.com.au</email></para></listitem>
<listitem><para>Paul Kranenburg <email>pk@NetBSD.org</email></para></listitem>
<listitem><para>Paul Mackerras <email>paulus@cs.anu.edu.au</email></para></listitem>
<listitem><para>Paul Popelka <email>paulp@uts.amdahl.com</email></para></listitem>
<listitem><para>Paul S. LaFollette, Jr.</para></listitem>
<listitem><para>Paul S. LaFollette, Jr. <email>unknown</email></para></listitem>
<listitem><para>Paul Saab <email>paul@mu.org</email></para></listitem>
<listitem><para>Paul Sandys <email>myj@nyct.net</email></para></listitem>
<listitem><para>Paul T. Root <email>proot@horton.iaces.com</email></para></listitem>
@ -1897,7 +1897,7 @@ box can be opened)</para>
<listitem><para>Peter Jeremy <email>perer.jeremy@alcatel.com.au</email></para></listitem>
<listitem><para>Peter M. Chen <email>pmchen@eecs.umich.edu</email></para></listitem>
<listitem><para>Peter Much <email>peter@citylink.dinoex.sub.org</email></para></listitem>
<listitem><para>Peter Olsson</para></listitem>
<listitem><para>Peter Olsson <email>unknown</email></para></listitem>
<listitem><para>Peter Philipp <email>pjp@bsd-daemon.net</email></para></listitem>
<listitem><para>Peter Stubbs <email>PETERS@staidan.qld.edu.au</email></para></listitem>
<listitem><para>Phil Maker <email>pjm@cs.ntu.edu.au</email></para></listitem>
@ -1930,7 +1930,7 @@ box can be opened)</para>
<listitem><para>Richard Winkel <email>rich@math.missouri.edu</email></para></listitem>
<listitem><para>Richard Wiwatowski <email>rjwiwat@adelaide.on.net</email></para></listitem>
<listitem><para>Rick Macklem <email>rick@snowhite.cis.uoguelph.ca</email></para></listitem>
<listitem><para>Rick Macklin</para></listitem>
<listitem><para>Rick Macklin <email>unknown</email></para></listitem>
<listitem><para>Rob Austein <email>sra@epilogue.com</email></para></listitem>
<listitem><para>Rob Mallory <email>rmallory@qualcomm.com</email></para></listitem>
<listitem><para>Rob Snow <email>rsnow@txdirect.net</email></para></listitem>
@ -1943,14 +1943,14 @@ box can be opened)</para>
<listitem><para>Robert Swindells <email>swindellsr@genrad.co.uk</email></para></listitem>
<listitem><para>Robert Watson <email>robert@cyrus.watson.org</email></para></listitem>
<listitem><para>Robert Withrow <email>witr@rwwa.com</email></para></listitem>
<listitem><para>Robert Yoder</para></listitem>
<listitem><para>Robert Yoder <email>unknown</email></para></listitem>
<listitem><para>Robin Carey <email>robin@mailgate.dtc.rankxerox.co.uk</email></para></listitem>
<listitem><para>Roger Hardiman <email>roger@cs.strath.ac.uk</email></para></listitem>
<listitem><para>Roland Jesse <email>jesse@cs.uni-magdeburg.de</email></para></listitem>
<listitem><para>Ron Bickers <email>rbickers@intercenter.net</email></para></listitem>
<listitem><para>Ron Lenk <email>rlenk@widget.xmission.com</email></para></listitem>
<listitem><para>Ronald Kuehn <email>kuehn@rz.tu-clausthal.de</email></para></listitem>
<listitem><para>Rudolf Cejka</para></listitem>
<listitem><para>Rudolf Cejka <email>unknown</email></para></listitem>
<listitem><para>Ruslan Belkin <email>rus@home2.UA.net</email></para></listitem>
<listitem><para>Ruslan Ermilov <email>ru@ucb.crimea.ua</email></para></listitem>
<listitem><para>Ruslan Shevchenko <email>rssh@cam.grad.kiev.ua</email></para></listitem>
@ -2008,7 +2008,7 @@ box can be opened)</para>
<listitem><para>Stefan Bethke <email>stb@hanse.de</email></para></listitem>
<listitem><para>Stefan Eggers <email>seggers@semyam.dinoco.de</email></para></listitem>
<listitem><para>Stefan Moeding <email>s.moeding@ndh.net</email></para></listitem>
<listitem><para>Stefan Petri</para></listitem>
<listitem><para>Stefan Petri <email>unknown</email></para></listitem>
<listitem><para>Stefan `Sec` Zehl <email>sec@42.org</email></para></listitem>
<listitem><para>Steinar Haug <email>sthaug@nethelp.no</email></para></listitem>
<listitem><para>Stephane E. Potvin <email>sepotvin@videotron.ca</email></para></listitem>
@ -2021,7 +2021,7 @@ box can be opened)</para>
<listitem><para>Stephen McKay <email>syssgm@devetir.qld.gov.au</email></para></listitem>
<listitem><para>Stephen Melvin <email>melvin@zytek.com</email></para></listitem>
<listitem><para>Steve Bauer <email>sbauer@rock.sdsmt.edu</email></para></listitem>
<listitem><para>Steve Deering</para></listitem>
<listitem><para>Steve Deering <email>unknown</email></para></listitem>
<listitem><para>Steve Gerakines <email>steve2@genesis.tiac.net</email></para></listitem>
<listitem><para>Steve Gericke <email>steveg@comtrol.com</email></para></listitem>
<listitem><para>Steve Piette <email>steve@simon.chi.il.US</email></para></listitem>
@ -2030,7 +2030,7 @@ box can be opened)</para>
<listitem><para>Steven H. Samorodin <email>samorodi@NUXI.com</email></para></listitem>
<listitem><para>Steven McCanne <email>mccanne@cs.berkeley.edu</email></para></listitem>
<listitem><para>Steven Plite <email>splite@purdue.edu</email></para></listitem>
<listitem><para>Steven Wallace</para></listitem>
<listitem><para>Steven Wallace <email>unknown</email></para></listitem>
<listitem><para>Stuart Henderson <email>stuart@internationalschool.co.uk</email></para></listitem>
<listitem><para>Sue Blake <email>sue@welearn.com.au</email></para></listitem>
<listitem><para>Sugiura Shiro <email>ssugiura@duo.co.jp</email></para></listitem>
@ -2055,7 +2055,7 @@ box can be opened)</para>
<listitem><para>Tatsumi HOSOKAWA <email>hosokawa@jp.FreeBSD.org</email></para></listitem>
<listitem><para>Ted Buswell <email>tbuswell@mediaone.net</email></para></listitem>
<listitem><para>Ted Faber <email>faber@isi.edu</email></para></listitem>
<listitem><para>Ted Lemon</para></listitem>
<listitem><para>Ted Lemon <email>unknown</email></para></listitem>
<listitem><para>Terry Lambert <email>terry@lambert.org</email></para></listitem>
<listitem><para>Terry Lee <email>terry@uivlsi.csl.uiuc.edu</email></para></listitem>
<listitem><para>Tetsuya Furukawa <email>tetsuya@secom-sis.co.jp</email></para></listitem>
@ -2067,7 +2067,7 @@ box can be opened)</para>
<listitem><para>Thomas Gellekum <email>thomas@ghpc8.ihf.rwth-aachen.de</email></para></listitem>
<listitem><para>Thomas Graichen <email>graichen@omega.physik.fu-berlin.de</email></para></listitem>
<listitem><para>Thomas K&ouml;nig <email>Thomas.Koenig@ciw.uni-karlsruhe.de</email></para></listitem>
<listitem><para>Thomas Ptacek</para></listitem>
<listitem><para>Thomas Ptacek <email>unknown</email></para></listitem>
<listitem><para>Thomas Stromberg <email>tstrombe@rtci.com</email></para></listitem>
<listitem><para>Thomas Valentino Crimi <email>tcrimi+@andrew.cmu.edu</email></para></listitem>
<listitem><para>Thomas Wintergerst <email>thomas@lemur.nord.de</email></para></listitem>

17
en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
View file

@ -13,10 +13,7 @@
is too small to hold the dump, you can configure your kernel to use
an alternate dump device (in the <literal>config
kernel</literal> line), or you can specify an alternate using the
<citerefentry><refentrytitle>dumpon</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. The best way to use <citerefentry>
<refentrytitle>dumpon</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> is to set the <literal>dumpdev</literal> variable in
&man.dumpon.8; command. The best way to use &man.dumpon.8; is to set the <literal>dumpdev</literal> variable in
<filename>/etc/rc.conf</filename>. Typically you want to specify one of
the swap devices specified in <filename>/etc/fstab</filename>.
Dumps to non-swap devices, tapes for example,
@ -25,10 +22,10 @@ Dumps to non-swap devices, tapes for example,
Configuration</link> for
details on configuring the FreeBSD kernel.</para>
<para>Use the <citerefentry><refentrytitle>dumpon</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to tell the kernel
<para>Use the &man.dumpon.8; command to tell the kernel
where to dump to (note that this will have to be done after
configuring the partition in question as swap space via
<citerefentry><refentrytitle>swapon</refentrytitle><manvolnum>8</manvolnum></citerefentry>). This is normally arranged via
&man.swapon.8;). This is normally arranged via
<filename>/etc/rc.conf</filename> and <filename>/etc/rc</filename>.
Alternatively, you can hard-code the dump device via the <literal>dump</literal>
clause in the <literal>config</literal> line of your kernel config file. This is
@ -68,7 +65,7 @@ Dumps to non-swap devices, tapes for example,
&prompt.root; <userinput>exit</userinput> # ...to multi-user</screen>
<para>This instructs <citerefentry><refentrytitle>savecore</refentrytitle><manvolnum>8</manvolnum></citerefentry> to
<para>This instructs &man.savecore.8; to
use another kernel for symbol name extraction. It would otherwise
default to the currently running kernel and most likely not do
anything at all since the crash dump and the kernel symbols
@ -279,7 +276,7 @@ Dumps to non-swap devices, tapes for example,
generated code, so you will finally get a new kernel with similar
code to the faulting one but some debugging symbols. You should at
least verify the old and new sizes with the
<citerefentry><refentrytitle>size</refentrytitle><manvolnum>1</manvolnum></citerefentry> command. If there is a mismatch, you
&man.size.1; command. If there is a mismatch, you
probably need to give up here.</para>
<para>Go and examine the dump as described above. The debugging
@ -479,7 +476,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
<para>The return value will be printed.</para>
<para>For a <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> style summary of all running
<para>For a &man.ps.1; style summary of all running
processes, use:</para>
@ -525,7 +522,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
<para>However, it is highly recommended to have a
printed copy of the <citerefentry><refentrytitle>ddb</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page
printed copy of the &man.ddb.4; manual page
ready for a debugging session. Remember that it is hard to read the
on-line manual while single-stepping the kernel.</para>

8
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -311,18 +311,18 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
<para>Sometimes, there is a problem with routing propagation, and
some sites are unable to connect to you. Perhaps the most useful
command for trying to figure out where a routing is breaking down
is the <citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. It is equally
is the &man.traceroute.8; command. It is equally
useful if you cannot seem to make a connection to a remote machine
(ie. <citerefentry><refentrytitle>ping</refentrytitle><manvolnum>8</manvolnum></citerefentry> fails).</para>
(i.e. &man.ping.8; fails).</para>
<para>The <citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry> command is run with the
<para>The &man.traceroute.8; command is run with the
name of the remote host you are trying to connect to. It will show
the gateway hosts along the path of the attempt, eventually either
reaching the target host, or terminating because of a lack of
connection.</para>
<para>For more information, see the manual page for
<citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
&man.traceroute.8;.</para>
</sect2>
</sect1>

201
en_US.ISO8859-1/books/handbook/backups/chapter.sgml
View file

@ -179,14 +179,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>Use the front panel button to eject the tape.</para>
<para>Re-insert the tape and
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> data to the tape.</para>
&man.dump.8; data to the tape.</para>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> will report <literal>DUMP:
<para>&man.dump.8; will report <literal>DUMP:
End of tape detected</literal> and the console will show:
<literal>HARDWARE FAILURE info:280 asc:80,96</literal></para>
@ -200,75 +195,35 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<title>Backup Programs</title>
<para>The three major programs are
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>,
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>,
&man.dump.8;,
&man.tar.1;,
and
<citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>.</para>
&man.cpio.1;.</para>
<sect2>
<title>Dump and Restore</title>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>restore</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> are the traditional Unix backup programs. They operate
<para>&man.dump.8; and &man.restore.8; are the traditional Unix backup programs. They operate
on the drive as a collection of disk blocks, below the abstractions of
files, links and directories that are created by the filesystems.
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> backs up devices, entire filesystems, not parts of a
&man.dump.8; backs up devices, entire filesystems, not parts of a
filesystem and not directory trees that span more than one filesystem,
using either soft links <citerefentry>
<refentrytitle>ln</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> or mounting one filesystem onto another.
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> does not write files and directories to tape, but
using either soft links &man.ln.1; or mounting one filesystem onto another.
&man.dump.8; does not write files and directories to tape, but
rather writes the data blocks that are the building blocks of files
and directories. <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> has quirks that remain from its early days in
and directories. &man.dump.8; has quirks that remain from its early days in
Version 6 of ATT Unix (circa 1975). The default parameters are
suitable for 9-track tapes (6250 bpi), not the high-density media
available today (up to 62,182 ftpi). These defaults must be overridden
on the command line to utilize the capacity of current tape
drives.</para>
<para><citerefentry>
<refentrytitle>rdump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>rrestore</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> backup data across the
<para>&man.rdump.8; and &man.rrestore.8; backup data across the
network to a tape drive attached to another computer. Both programs
rely upon <citerefentry>
<refentrytitle>rcmd</refentrytitle>
<manvolnum>3</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>ruserok</refentrytitle>
<manvolnum>3</manvolnum></citerefentry> to access the remote tape
rely upon &man.rcmd.3; and &man.ruserok.3; to access the remote tape
drive. Therefore, the user performing the backup must have
<literal>rhosts</literal> access to the remote computer. The
arguments to <citerefentry>
<refentrytitle>rdump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>rrestore</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> must suitable to use on the remote computer. (e.g.
arguments to &man.rdump.8; and &man.rrestore.8; must suitable to use on the remote computer. (e.g.
When <command>rdump</command>'ing from a FreeBSD computer to an
Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000
@ -280,95 +235,52 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect2>
<title>Tar</title>
<para><citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> also dates back to Version 6 of ATT Unix (circa
1975). <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> operates in cooperation with the filesystem;
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> writes files and directories to tape.
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> does not support the full range of options that are
available from <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>, but <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not require the
unusual command pipeline that <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> uses.</para>
<para>&man.tar.1; also dates back to Version 6 of ATT Unix (circa
1975). &man.tar.1; operates in cooperation with the filesystem;
&man.tar.1; writes files and directories to tape.
&man.tar.1; does not support the full range of options that are
available from &man.cpio.1;, but &man.tar.1; does not require the
unusual command pipeline that &man.cpio.1; uses.</para>
<para>Most versions of <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> do not support backups across the network. The GNU
version of <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>, which FreeBSD utilizes,
<para>Most versions of &man.tar.1; do not support backups across the network. The GNU
version of &man.tar.1;, which FreeBSD utilizes,
supports remote devices using the same syntax as
<command>rdump</command>. To <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> to an Exabyte tape drive connected to a Sun called
komodo, use: <command>/usr/bin/tar cf komodo:/dev/nrst8 .
&man.rdump.8;. To &man.tar.1; to an Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/usr/bin/tar cf komodo:/dev/nrst8 .
2>&amp;1</command>. For versions without remote device support,
you can use a pipeline and <citerefentry>
<refentrytitle>rsh</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> to send the data to a
you can use a pipeline and &man.rsh.1; to send the data to a
remote tape drive. (XXX add an example command)</para>
</sect2>
<sect2>
<title>Cpio</title>
<para><citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> is the original Unix
file interchange tape program for magnetic media. <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> has options (among many
<para>&man.cpio.1; is the original Unix
file interchange tape program for magnetic media. &man.cpio.1; has options (among many
others) to perform byte-swapping, write a number of different
archives format, and pipe the data to other programs. This last
feature makes <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> and excellent choice for
installation media. <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not know how to walk
feature makes &man.cpio.1; and excellent choice for
installation media. &man.cpio.1; does not know how to walk
the directory tree and a list of files must be provided thru
<filename>STDIN</filename>.</para>
<para><citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not support backups
across the network. You can use a pipeline and <citerefentry>
<refentrytitle>rsh</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> to send the data to a
<para>&man.cpio.1; does not support backups
across the network. You can use a pipeline and &man.rsh.1; to send the data to a
remote tape drive. (XXX add an example command)</para>
</sect2>
<sect2>
<title>Pax</title>
<para><citerefentry>
<refentrytitle>pax</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> is IEEE/POSIX's answer to
<command>tar</command> and <command>cpio</command>. Over the years the
various versions of <command>tar</command> and <command>cpio</command>
<para>&man.pax.1; is IEEE/POSIX's answer to
&man.tar.1; and &man.cpio.1;. Over the years the
various versions of &man.tar.1; and &man.cpio.1;
have gotten slightly incompatible. So rather than fight it out to
fully standardize them, POSIX created a new archive utility.
<command>pax</command> attempts to read and write many of the various
cpio and tar formats, plus new formats of its own. Its command set
more resembles <command>cpio</command> than
<command>tar</command>.</para>
&man.pax.1; attempts to read and write many of the various
&man.cpio.1; and &man.tar.1; formats, plus new formats of its own. Its command set
more resembles &man.cpio.1; than
&man.tar.1;.</para>
</sect2>
<sect2 id="backups-programs-amanda">
@ -422,14 +334,10 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect2>
<title>Which Backup Program is Best?</title>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> <emphasis>Period.</emphasis>
<para>&man.dump.8; <emphasis>Period.</emphasis>
Elizabeth D. Zwicky torture tested all the backup programs discussed
here. The clear choice for preserving all your data and all the
peculiarities of Unix filesystems is <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>. Elizabeth created
peculiarities of Unix filesystems is &man.dump.8;. Elizabeth created
filesystems containing a large variety of unusual conditions (and some
not so unusual ones) and tested each program by do a backup and
restore of that filesystems. The peculiarities included: files with
@ -465,22 +373,10 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>Otherwise, you have to create two custom bootable floppies
which has a kernel that can mount your all of your disks and
access your tape drive. These floppies must contain:
<citerefentry>
<refentrytitle>fdisk</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>disklabel</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>newfs</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>mount</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, and whichever backup
&man.fdisk.8;, &man.disklabel.8;, &man.newfs.8;, &man.mount.8;, and whichever backup
program you use. These programs must be statically linked. If you
use <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, the floppy must contain
<citerefentry>
<refentrytitle>restore</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>.</para>
use &man.dump.8;, the floppy must contain
&man.restore.8;.</para>
<para>Third, create backup tapes regularly. Any changes that you make
after your last backup may be irretrievably lost. Write-protect the
@ -686,18 +582,11 @@ chmod 644 /mnt/etc/passwd
<para>Recover each filesystem separately.</para>
<para>Try to <citerefentry>
<refentrytitle>mount</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry>(e.g. <command>mount /dev/sd0a
<para>Try to &man.mount.8; (e.g. <command>mount /dev/sd0a
/mnt</command>) the root partition of your first disk. If the
disklabel was damaged, use <citerefentry>
<refentrytitle>disklabel</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> to re-partition and
disklabel was damaged, use &man.disklabel.8; to re-partition and
label the disk to match the label that your printed and saved. Use
<citerefentry>
<refentrytitle>newfs</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> to re-create the
&man.newfs.8; to re-create the
filesystems. Re-mount the root partition of the floppy read-write
(<command>mount -u -o rw /mnt</command>). Use your backup program
and backup tapes to recover the data for this filesystem (e.g.

6
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -76,9 +76,9 @@
<para>This will display the manual page for the user
command <command>chmod</command>. References to a
particular section of the on-line manual are traditionally placed in
parenthesis in written documentation, so <citerefentry><refentrytitle>chmod</refentrytitle><manvolnum>1</manvolnum></citerefentry> refers to the
parenthesis in written documentation, so &man.chmod.1; refers to the
<command>chmod</command>
user command and <citerefentry><refentrytitle>chmod</refentrytitle><manvolnum>2</manvolnum></citerefentry> refers to the
user command and &man.chmod.2; refers to the
system call.</para>
<para>This is fine if you know the name of the command and simply wish
@ -122,7 +122,7 @@
<command>info</command> command or, if you installed
<command>emacs</command>, the info mode of <command>emacs</command>.</para>
<para>To use the <citerefentry><refentrytitle>info</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, simply type:</para>
<para>To use the &man.info.1; command, simply type:</para>
<screen>&prompt.user; <userinput>info</userinput></screen>

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

@ -1,6 +1,9 @@
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.0-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
<!ENTITY % authors SYSTEM "authors.ent"> %authors;
<!ENTITY % authors SYSTEM "authors.ent"> %authors;
<!ENTITY % mailing-lists SYSTEM "mailing-lists.ent"> %mailing-lists;
<!ENTITY % newsgroups SYSTEM "newsgroups.ent"> %newsgroups;

224
en_US.ISO8859-1/books/handbook/contrib/chapter.sgml
View file

@ -458,12 +458,12 @@
information about this and other mailing lists.</para>
<para>If you find a bug or are submitting a specific change, please
report it using the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>program or its
report it using the &man.send-pr.1; program or its
<ulink URL="http://www.freebsd.org/send-pr.html">WEB-based
equivalent</ulink>. Try to fill-in each field of the bug report.
Unless they exceed 65KB, include any patches directly in the
report. Consider compressing them and using
<citerefentry><refentrytitle>uuencode</refentrytitle><manvolnum>1</manvolnum></citerefentry> if they exceed 20KB. Upload very large submissions to <ulink url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp.freebsd.org:/pub/FreeBSD/incoming/</ulink>.</para>
&man.uuencode.1; if they exceed 20KB. Upload very large submissions to <ulink url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp.freebsd.org:/pub/FreeBSD/incoming/</ulink>.</para>
<para>After filing a report, you should receive confirmation along
with a tracking number. Keep this tracking number so that you can
@ -471,7 +471,7 @@
<para>If you do not receive confirmation in a timely fashion (3 days
to a week, depending on your email connection) or are, for some
reason, unable to use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> command,
reason, unable to use the &man.send-pr.1; command,
then you may ask someone to file it for you by sending mail to the
&a.bugs;.</para>
@ -511,7 +511,7 @@
<para>Assuming that you can manage to secure fairly up-to-date
sources to base your changes on, the next step is to produce a set
of diffs to send to the FreeBSD maintainers. This is done with
the <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, with the &ldquo;context diff&rdquo;
the &man.diff.1; command, with the &ldquo;context diff&rdquo;
form being preferred. For example:</para>
<para>
@ -526,11 +526,11 @@
would generate such a set of context diffs for
the given source file or directory hierarchy. See the man page
for <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> for more details.</para>
for &man.diff.1; for more details.</para>
<para>Once you have a set of diffs (which you may test with the
<citerefentry><refentrytitle>patch</refentrytitle><manvolnum>1</manvolnum></citerefentry> command), you should submit them for
inclusion with FreeBSD. Use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
&man.patch.1; command), you should submit them for
inclusion with FreeBSD. Use the &man.send-pr.1;
program as described in
<link linkend="contrib-general">Bug Reports and General
Commentary</link>. <emphasis>Do not</emphasis> just send the diffs to
@ -541,14 +541,14 @@
<para>If you feel it appropriate (e.g. you have added, deleted, or
renamed files), bundle your changes into a <command>tar</command> file and run the
<citerefentry><refentrytitle>uuencode</refentrytitle><manvolnum>1</manvolnum></citerefentry> program on it. Shar archives are
&man.uuencode.1; program on it. Shar archives are
also welcome.</para>
<para>If your change is of a potentially sensitive nature, e.g. you
are unsure of copyright issues governing its further distribution
or you are simply not ready to release it without a tighter review
first, then you should send it to &a.core; directly rather than
submitting it with <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The core
submitting it with &man.send-pr.1;. The core
mailing list reaches a much smaller group of people who do much of
the day-to-day work on FreeBSD. Note that this group is also
<emphasis>very busy</emphasis> and so you should only send mail to
@ -1143,9 +1143,9 @@ box can be opened)</para>
<listitem><para>Adrian Mariano <email>adrian@cam.cornell.edu</email></para></listitem>
<listitem><para>Adrian Steinmann <email>ast@marabu.ch</email></para></listitem>
<listitem><para>Adrian T. Filipi-Martin <email>atf3r@agate.cs.virginia.edu</email></para></listitem>
<listitem><para>Ajit Thyagarajan</para></listitem>
<listitem><para>Ajit Thyagarajan <email>unknown</email></para></listitem>
<listitem><para>Akio Morita <email>amorita@meadow.scphys.kyoto-u.ac.jp</email></para></listitem>
<listitem><para>Akira SAWADA</para></listitem>
<listitem><para>Akira SAWADA <email>unknown</email></para></listitem>
<listitem><para>Akira Watanabe <email>akira@myaw.ei.meisei-u.ac.jp</email></para></listitem>
<listitem><para>Akito Fujita <email>fujita@zoo.ncl.omron.co.jp</email></para></listitem>
<listitem><para>Alain Kalker <email>A.C.P.M.Kalker@student.utwente.nl</email></para></listitem>
@ -1177,10 +1177,10 @@ box can be opened)</para>
<listitem><para>Andreas Haakh <email>ah@alman.robin.de</email></para></listitem>
<listitem><para>Andreas Kohout <email>shanee@rabbit.augusta.de</email></para></listitem>
<listitem><para>Andreas Lohr <email>andreas@marvin.RoBIN.de</email></para></listitem>
<listitem><para>Andreas Schulz</para></listitem>
<listitem><para>Andreas Schulz <email>unknown</email></para></listitem>
<listitem><para>Andreas Wetzel <email>mickey@deadline.snafu.de</email></para></listitem>
<listitem><para>Andreas Wrede <email>andreas@planix.com</email></para></listitem>
<listitem><para>Andres Vega Garcia</para></listitem>
<listitem><para>Andres Vega Garcia <email>unknown</email></para></listitem>
<listitem><para>Andrew Atrens <email>atreand@statcan.ca</email></para></listitem>
<listitem><para>Andrew Gillham <email>gillham@andrews.edu</email></para></listitem>
<listitem><para>Andrew Gordon <email>andrew.gordon@net-tel.co.uk</email></para></listitem>
@ -1212,7 +1212,7 @@ box can be opened)</para>
<listitem><para>Barry Bierbauch <email>pivrnec@vszbr.cz</email></para></listitem>
<listitem><para>Barry Lustig <email>barry@ictv.com</email></para></listitem>
<listitem><para>Ben Hutchinson <email>benhutch@xfiles.org.uk</email></para></listitem>
<listitem><para>Ben Jackson</para></listitem>
<listitem><para>Ben Jackson <email>unknown</email></para></listitem>
<listitem><para>Ben Smithurst <email>ben@scientia.demon.co.uk</email></para></listitem>
<listitem><para>Ben Walter <email>bwalter@itachi.swcp.com</email></para></listitem>
<listitem><para>Benjamin Lewis <email>bhlewis@gte.net</email></para></listitem>
@ -1264,7 +1264,7 @@ box can be opened)</para>
<listitem><para>Chet Ramey <email>chet@odin.INS.CWRU.Edu</email></para></listitem>
<listitem><para>Chia-liang Kao <email>clkao@CirX.ORG</email></para></listitem>
<listitem><para>Chiharu Shibata <email>chi@bd.mbn.or.jp</email></para></listitem>
<listitem><para>Chip Norkus</para></listitem>
<listitem><para>Chip Norkus <email>unknown</email></para></listitem>
<listitem><para>Choi Jun Ho <email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para>Chris Csanady <email>cc@tarsier.ca.sandia.gov</email></para></listitem>
<listitem><para>Chris Dabrowski <email>chris@vader.org</email></para></listitem>
@ -1291,7 +1291,7 @@ box can be opened)</para>
<listitem><para>Cornelis van der Laan <email>nils@guru.ims.uni-stuttgart.de</email></para></listitem>
<listitem><para>Cove Schneider <email>cove@brazil.nbn.com</email></para></listitem>
<listitem><para>Craig Leres <email>leres@ee.lbl.gov</email></para></listitem>
<listitem><para>Craig Loomis</para></listitem>
<listitem><para>Craig Loomis <email>unknown</email></para></listitem>
<listitem><para>Craig Metz <email>cmetz@inner.net</email></para></listitem>
<listitem><para>Craig Spannring <email>cts@internetcds.com</email></para></listitem>
<listitem><para>Craig Struble <email>cstruble@vt.edu</email></para></listitem>
@ -1310,7 +1310,7 @@ box can be opened)</para>
<listitem><para>Daniel O'Connor <email>doconnor@gsoft.com.au</email></para></listitem>
<listitem><para>Daniel Poirot <email>poirot@aio.jsc.nasa.gov</email></para></listitem>
<listitem><para>Daniel Rock <email>rock@cs.uni-sb.de</email></para></listitem>
<listitem><para>Danny Egen</para></listitem>
<listitem><para>Danny Egen <email>unknown</email></para></listitem>
<listitem><para>Danny J. Zerkel <email>dzerkel@phofarm.com</email></para></listitem>
<listitem><para>Darren Reed <email>avalon@coombs.anu.edu.au</email></para></listitem>
<listitem><para>Dave Adkins <email>adkin003@tc.umn.edu</email></para></listitem>
@ -1344,7 +1344,7 @@ box can be opened)</para>
<listitem><para>David Wolfskill <email>dhw@whistle.com</email></para></listitem>
<listitem><para>Dean Gaudet <email>dgaudet@arctic.org</email></para></listitem>
<listitem><para>Dean Huxley <email>dean@fsa.ca</email></para></listitem>
<listitem><para>Denis Fortin</para></listitem>
<listitem><para>Denis Fortin <email>unknown</email></para></listitem>
<listitem><para>Dennis Glatting <email>dennis.glatting@software-munitions.com</email></para></listitem>
<listitem><para>Denton Gentry <email>denny1@home.com</email></para></listitem>
<listitem><para>Derek Inksetter <email>derek@saidev.com</email></para></listitem>
@ -1450,7 +1450,7 @@ box can be opened)</para>
<listitem><para>Harold Barker <email>hbarker@dsms.com</email></para></listitem>
<listitem><para>Havard Eidnes <email>Havard.Eidnes@runit.sintef.no</email></para></listitem>
<listitem><para>Heikki Suonsivu <email>hsu@cs.hut.fi</email></para></listitem>
<listitem><para>Heiko W. Rupp</para></listitem>
<listitem><para>Heiko W. Rupp <email>unknown</email></para></listitem>
<listitem><para>Helmut F. Wirth <email>hfwirth@ping.at</email></para></listitem>
<listitem><para>Henrik Vestergaard Draboel <email>hvd@terry.ping.dk</email></para></listitem>
<listitem><para>Herb Peyerl <email>hpeyerl@NetBSD.org</email></para></listitem>
@ -1464,7 +1464,7 @@ box can be opened)</para>
<listitem><para>Hiroharu Tamaru <email>tamaru@ap.t.u-tokyo.ac.jp</email></para></listitem>
<listitem><para>Hironori Ikura <email>hikura@kaisei.org</email></para></listitem>
<listitem><para>Hiroshi Nishikawa <email>nis@pluto.dti.ne.jp</email></para></listitem>
<listitem><para>Hiroya Tsubakimoto</para></listitem>
<listitem><para>Hiroya Tsubakimoto <email>unknown</email></para></listitem>
<listitem><para>Hiroyuki NAKAJI <email>nakaji@zeisei3.dpri.kyoto-u.ac.jp</email></para></listitem>
<listitem><para>Holger Veit <email>Holger.Veit@gmd.de</email></para></listitem>
<listitem><para>Holm Tiffe <email>holm@geophysik.tu-freiberg.de</email></para></listitem>
@ -1527,7 +1527,7 @@ box can be opened)</para>
<listitem><para>Jeremy Allison <email>jallison@whistle.com</email></para></listitem>
<listitem><para>Jeremy Chatfield <email>jdc@xinside.com</email></para></listitem>
<listitem><para>Jeremy Lea <email>reg@shale.csir.co.za</email></para></listitem>
<listitem><para>Jeremy Prior</para></listitem>
<listitem><para>Jeremy Prior <email>unknown</email></para></listitem>
<listitem><para>Jeroen Ruigrok/Asmodai <email>asmodai@wxs.nl</email></para></listitem>
<listitem><para>Jesse Rosenstock <email>jmr@ugcs.caltech.edu</email></para></listitem>
<listitem><para>Jian-Da Li <email>jdli@csie.nctu.edu.tw</email></para></listitem>
@ -1543,7 +1543,7 @@ box can be opened)</para>
<listitem><para>Jim Wilson <email>wilson@moria.cygnus.com</email></para></listitem>
<listitem><para>Jimbo Bahooli <email>griffin@blackhole.iceworld.org</email></para></listitem>
<listitem><para>Jin Guojun <email>jin@george.lbl.gov</email></para></listitem>
<listitem><para>Joachim Kuebart</para></listitem>
<listitem><para>Joachim Kuebart <email>unknown</email></para></listitem>
<listitem><para>Joao Carlos Mendes Luis <email>jonny@jonny.eng.br</email></para></listitem>
<listitem><para>Jochen Pohl <email>jpo.drs@sni.de</email></para></listitem>
<listitem><para>Joe "Marcus" Clarke <email>marcus@miami.edu</email></para></listitem>
@ -1558,19 +1558,19 @@ box can be opened)</para>
<listitem><para>Johan Karlsson <email>k@numeri.campus.luth.se</email></para></listitem>
<listitem><para>Johan Larsson <email>johan@moon.campus.luth.se</email></para></listitem>
<listitem><para>Johann Tonsing <email>jtonsing@mikom.csir.co.za</email></para></listitem>
<listitem><para>Johannes Helander</para></listitem>
<listitem><para>Johannes Stille</para></listitem>
<listitem><para>Johannes Helander <email>unknown</email></para></listitem>
<listitem><para>Johannes Stille <email>unknown</email></para></listitem>
<listitem><para>John Baldwin <email>jobaldwi@vt.edu</email></para></listitem>
<listitem><para>John Beckett <email>jbeckett@southern.edu</email></para></listitem>
<listitem><para>John Beukema <email>jbeukema@hk.super.net</email></para></listitem>
<listitem><para>John Brezak</para></listitem>
<listitem><para>John Brezak <email>unknown</email></para></listitem>
<listitem><para>John Capo <email>jc@irbs.com</email></para></listitem>
<listitem><para>John F. Woods <email>jfw@jfwhome.funhouse.com</email></para></listitem>
<listitem><para>John Goerzen <email>jgoerzen@alexanderwohl.complete.org</email></para></listitem>
<listitem><para>John Hay <email>jhay@mikom.csir.co.za</email></para></listitem>
<listitem><para>John Heidemann <email>johnh@isi.edu</email></para></listitem>
<listitem><para>John Hood <email>cgull@owl.org</email></para></listitem>
<listitem><para>John Kohl</para></listitem>
<listitem><para>John Kohl <email>unknown</email></para></listitem>
<listitem><para>John Lind <email>john@starfire.mn.org</email></para></listitem>
<listitem><para>John Mackin <email>john@physiol.su.oz.au</email></para></listitem>
<listitem><para>John P <email>johnp@lodgenet.com</email></para></listitem>
@ -1620,10 +1620,10 @@ box can be opened)</para>
<listitem><para>Kazuo Horikawa <email>horikawa@jp.FreeBSD.org</email></para></listitem>
<listitem><para>Kees Jan Koster <email>kjk1@ukc.ac.uk</email></para></listitem>
<listitem><para>Keith Bostic <email>bostic@bostic.com</email></para></listitem>
<listitem><para>Keith E. Walker</para></listitem>
<listitem><para>Keith Moore</para></listitem>
<listitem><para>Keith Sklower</para></listitem>
<listitem><para>Ken Hornstein</para></listitem>
<listitem><para>Keith E. Walker <email>unknown</email></para></listitem>
<listitem><para>Keith Moore <email>unknown</email></para></listitem>
<listitem><para>Keith Sklower <email>unknown</email></para></listitem>
<listitem><para>Ken Hornstein <email>unknown</email></para></listitem>
<listitem><para>Ken Key <email>key@cs.utk.edu</email></para></listitem>
<listitem><para>Ken Mayer <email>kmayer@freegate.com</email></para></listitem>
<listitem><para>Kenji Saito <email>marukun@mx2.nisiq.net</email></para></listitem>
@ -1659,7 +1659,7 @@ box can be opened)</para>
<listitem><para>Louis Mamakos <email>loiue@TransSys.com</email></para></listitem>
<listitem><para>Lucas James <email>Lucas.James@ldjpc.apana.org.au</email></para></listitem>
<listitem><para>Lyndon Nerenberg <email>lyndon@orthanc.com</email></para></listitem>
<listitem><para>M.C. Wong</para></listitem>
<listitem><para>M.C. Wong <email>unknown</email></para></listitem>
<listitem><para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para></listitem>
<listitem><para>MIHIRA Sanpei Yoshiro <email>sanpei@sanpei.org</email></para></listitem>
<listitem><para>MITA Yoshio <email>mita@jp.FreeBSD.ORG</email></para></listitem>
@ -1677,7 +1677,7 @@ box can be opened)</para>
<listitem><para>Marc van Kempen <email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para>Marcel Moolenaar <email>marcel@scc.nl</email></para></listitem>
<listitem><para>Mario Sergio Fujikawa Ferreira <email>lioux@gns.com.br</email></para></listitem>
<listitem><para>Mark Andrews</para></listitem>
<listitem><para>Mark Andrews <email>unknown</email></para></listitem>
<listitem><para>Mark Cammidge <email>mark@gmtunx.ee.uct.ac.za</email></para></listitem>
<listitem><para>Mark Diekhans <email>markd@grizzly.com</email></para></listitem>
<listitem><para>Mark Huizer <email>xaa@stack.nl</email></para></listitem>
@ -1686,7 +1686,7 @@ box can be opened)</para>
<listitem><para>Mark Mayo <email>markm@vmunix.com</email></para></listitem>
<listitem><para>Mark Thompson <email>thompson@tgsoft.com</email></para></listitem>
<listitem><para>Mark Tinguely <email>tinguely@plains.nodak.edu</email></para></listitem>
<listitem><para>Mark Treacy</para></listitem>
<listitem><para>Mark Treacy <email>unknown</email></para></listitem>
<listitem><para>Mark Valentine <email>mark@linus.demon.co.uk</email></para></listitem>
<listitem><para>Martin Birgmeier</para></listitem>
<listitem><para>Martin Ibert <email>mib@ppe.bb-data.de</email></para></listitem>
@ -1694,7 +1694,7 @@ box can be opened)</para>
<listitem><para>Martin Renters <email>martin@tdc.on.ca</email></para></listitem>
<listitem><para>Martti Kuparinen <email>erakupa@kk.etx.ericsson.se</email></para></listitem>
<listitem><para>Masachika ISHIZUKA <email>ishizuka@isis.min.ntt.jp</email></para></listitem>
<listitem><para>Mas.TAKEMURA</para></listitem>
<listitem><para>Mas.TAKEMURA <email>unknown</email></para></listitem>
<listitem><para>Masafumi NAKANE <email>max@wide.ad.jp</email></para></listitem>
<listitem><para>Masahiro Sekiguchi <email>seki@sysrap.cs.fujitsu.co.jp</email></para></listitem>
<listitem><para>Masanobu Saitoh <email>msaitoh@spa.is.uec.ac.jp</email></para></listitem>
@ -1745,7 +1745,7 @@ box can be opened)</para>
<listitem><para>Mike Evans <email>mevans@candle.com</email></para></listitem>
<listitem><para>Mike Grupenhoff <email>kashmir@umiacs.umd.edu</email></para></listitem>
<listitem><para>Mike Hibler <email>mike@marker.cs.utah.edu</email></para></listitem>
<listitem><para>Mike Karels</para></listitem>
<listitem><para>Mike Karels <email>unknown</email></para></listitem>
<listitem><para>Mike McGaughey <email>mmcg@cs.monash.edu.au</email></para></listitem>
<listitem><para>Mike Meyer <email>mwm@shiva.the-park.com</email></para></listitem>
<listitem><para>Mike Mitchell <email>mitchell@ref.tfs.com</email></para></listitem>
@ -1787,71 +1787,71 @@ box can be opened)</para>
<listitem><para>Nickolay N. Dudorov <email>nnd@itfs.nsk.su</email></para></listitem>
<listitem><para>Niklas Hallqvist <email>niklas@filippa.appli.se</email></para></listitem>
<listitem><para>Nisha Talagala <email>nisha@cs.berkeley.edu</email></para></listitem>
<listitem><para><email>ZW6T-KND@j.asahi-net.or.jp</email></para></listitem>
<listitem><para><email>adrian@virginia.edu</email></para></listitem>
<listitem><para><email>alex@elvisti.kiev.ua</email></para></listitem>
<listitem><para><email>anto@netscape.net</email></para></listitem>
<listitem><para><email>bobson@egg.ics.nitch.ac.jp</email></para></listitem>
<listitem><para><email>bovynf@awe.be</email></para></listitem>
<listitem><para><email>burg@is.ge.com</email></para></listitem>
<listitem><para><email>chris@gnome.co.uk</email></para></listitem>
<listitem><para><email>colsen@usa.net</email></para></listitem>
<listitem><para><email>coredump@nervosa.com</email></para></listitem>
<listitem><para><email>dannyman@arh0300.urh.uiuc.edu</email></para></listitem>
<listitem><para><email>davids@SECNET.COM</email></para></listitem>
<listitem><para><email>derek@free.org</email></para></listitem>
<listitem><para><email>devet@adv.IAEhv.nl</email></para></listitem>
<listitem><para><email>djv@bedford.net</email></para></listitem>
<listitem><para><email>dvv@sprint.net</email></para></listitem>
<listitem><para><email>enami@ba2.so-net.or.jp</email></para></listitem>
<listitem><para><email>flash@eru.tubank.msk.su</email></para></listitem>
<listitem><para><email>flash@hway.ru</email></para></listitem>
<listitem><para><email>fn@pain.csrv.uidaho.edu</email></para></listitem>
<listitem><para><email>gclarkii@netport.neosoft.com</email></para></listitem>
<listitem><para><email>gordon@sheaky.lonestar.org</email></para></listitem>
<listitem><para><email>graaf@iae.nl</email></para></listitem>
<listitem><para><email>greg@greg.rim.or.jp</email></para></listitem>
<listitem><para><email>grossman@cygnus.com</email></para></listitem>
<listitem><para><email>gusw@fub46.zedat.fu-berlin.de</email></para></listitem>
<listitem><para><email>hfir@math.rochester.edu</email></para></listitem>
<listitem><para><email>hnokubi@yyy.or.jp</email></para></listitem>
<listitem><para><email>iaint@css.tuu.utas.edu.au</email></para></listitem>
<listitem><para><email>invis@visi.com</email></para></listitem>
<listitem><para><email>ishisone@sra.co.jp</email></para></listitem>
<listitem><para><email>iverson@lionheart.com</email></para></listitem>
<listitem><para><email>jpt@magic.net</email></para></listitem>
<listitem><para><email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para><email>k-sugyou@ccs.mt.nec.co.jp</email></para></listitem>
<listitem><para><email>kenji@reseau.toyonaka.osaka.jp</email></para></listitem>
<listitem><para><email>kfurge@worldnet.att.net</email></para></listitem>
<listitem><para><email>lh@aus.org</email></para></listitem>
<listitem><para><email>lhecking@nmrc.ucc.ie</email></para></listitem>
<listitem><para><email>mrgreen@mame.mu.oz.au</email></para></listitem>
<listitem><para><email>nakagawa@jp.freebsd.org</email></para></listitem>
<listitem><para><email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para></listitem>
<listitem><para><email>owaki@st.rim.or.jp</email></para></listitem>
<listitem><para><email>pechter@shell.monmouth.com</email></para></listitem>
<listitem><para><email>pete@pelican.pelican.com</email></para></listitem>
<listitem><para><email>pritc003@maroon.tc.umn.edu</email></para></listitem>
<listitem><para><email>risner@stdio.com</email></para></listitem>
<listitem><para><email>roman@rpd.univ.kiev.ua</email></para></listitem>
<listitem><para><email>root@ns2.redline.ru</email></para></listitem>
<listitem><para><email>root@uglabgw.ug.cs.sunysb.edu</email></para></listitem>
<listitem><para><email>stephen.ma@jtec.com.au</email></para></listitem>
<listitem><para><email>sumii@is.s.u-tokyo.ac.jp</email></para></listitem>
<listitem><para><email>takas-su@is.aist-nara.ac.jp</email></para></listitem>
<listitem><para><email>tamone@eig.unige.ch</email></para></listitem>
<listitem><para><email>tjevans@raleigh.ibm.com</email></para></listitem>
<listitem><para><email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para></listitem>
<listitem><para><email>torii@tcd.hitachi.co.jp</email></para></listitem>
<listitem><para><email>uenami@imasy.or.jp</email></para></listitem>
<listitem><para><email>uhlar@netlab.sk</email></para></listitem>
<listitem><para><email>vode@hut.fi</email></para></listitem>
<listitem><para><email>wlloyd@mpd.ca</email></para></listitem>
<listitem><para><email>wlr@furball.wellsfargo.com</email></para></listitem>
<listitem><para><email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para><email>yamagata@nwgpc.kek.jp</email></para></listitem>
<listitem><para><email>ziggy@ryan.org</email></para></listitem>
<listitem><para>No Name <email>ZW6T-KND@j.asahi-net.or.jp</email></para></listitem>
<listitem><para>No Name <email>adrian@virginia.edu</email></para></listitem>
<listitem><para>No Name <email>alex@elvisti.kiev.ua</email></para></listitem>
<listitem><para>No Name <email>anto@netscape.net</email></para></listitem>
<listitem><para>No Name <email>bobson@egg.ics.nitch.ac.jp</email></para></listitem>
<listitem><para>No Name <email>bovynf@awe.be</email></para></listitem>
<listitem><para>No Name <email>burg@is.ge.com</email></para></listitem>
<listitem><para>No Name <email>chris@gnome.co.uk</email></para></listitem>
<listitem><para>No Name <email>colsen@usa.net</email></para></listitem>
<listitem><para>No Name <email>coredump@nervosa.com</email></para></listitem>
<listitem><para>No Name <email>dannyman@arh0300.urh.uiuc.edu</email></para></listitem>
<listitem><para>No Name <email>davids@SECNET.COM</email></para></listitem>
<listitem><para>No Name <email>derek@free.org</email></para></listitem>
<listitem><para>No Name <email>devet@adv.IAEhv.nl</email></para></listitem>
<listitem><para>No Name <email>djv@bedford.net</email></para></listitem>
<listitem><para>No Name <email>dvv@sprint.net</email></para></listitem>
<listitem><para>No Name <email>enami@ba2.so-net.or.jp</email></para></listitem>
<listitem><para>No Name <email>flash@eru.tubank.msk.su</email></para></listitem>
<listitem><para>No Name <email>flash@hway.ru</email></para></listitem>
<listitem><para>No Name <email>fn@pain.csrv.uidaho.edu</email></para></listitem>
<listitem><para>No Name <email>gclarkii@netport.neosoft.com</email></para></listitem>
<listitem><para>No Name <email>gordon@sheaky.lonestar.org</email></para></listitem>
<listitem><para>No Name <email>graaf@iae.nl</email></para></listitem>
<listitem><para>No Name <email>greg@greg.rim.or.jp</email></para></listitem>
<listitem><para>No Name <email>grossman@cygnus.com</email></para></listitem>
<listitem><para>No Name <email>gusw@fub46.zedat.fu-berlin.de</email></para></listitem>
<listitem><para>No Name <email>hfir@math.rochester.edu</email></para></listitem>
<listitem><para>No Name <email>hnokubi@yyy.or.jp</email></para></listitem>
<listitem><para>No Name <email>iaint@css.tuu.utas.edu.au</email></para></listitem>
<listitem><para>No Name <email>invis@visi.com</email></para></listitem>
<listitem><para>No Name <email>ishisone@sra.co.jp</email></para></listitem>
<listitem><para>No Name <email>iverson@lionheart.com</email></para></listitem>
<listitem><para>No Name <email>jpt@magic.net</email></para></listitem>
<listitem><para>No Name <email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para>No Name <email>k-sugyou@ccs.mt.nec.co.jp</email></para></listitem>
<listitem><para>No Name <email>kenji@reseau.toyonaka.osaka.jp</email></para></listitem>
<listitem><para>No Name <email>kfurge@worldnet.att.net</email></para></listitem>
<listitem><para>No Name <email>lh@aus.org</email></para></listitem>
<listitem><para>No Name <email>lhecking@nmrc.ucc.ie</email></para></listitem>
<listitem><para>No Name <email>mrgreen@mame.mu.oz.au</email></para></listitem>
<listitem><para>No Name <email>nakagawa@jp.freebsd.org</email></para></listitem>
<listitem><para>No Name <email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para></listitem>
<listitem><para>No Name <email>owaki@st.rim.or.jp</email></para></listitem>
<listitem><para>No Name <email>pechter@shell.monmouth.com</email></para></listitem>
<listitem><para>No Name <email>pete@pelican.pelican.com</email></para></listitem>
<listitem><para>No Name <email>pritc003@maroon.tc.umn.edu</email></para></listitem>
<listitem><para>No Name <email>risner@stdio.com</email></para></listitem>
<listitem><para>No Name <email>roman@rpd.univ.kiev.ua</email></para></listitem>
<listitem><para>No Name <email>root@ns2.redline.ru</email></para></listitem>
<listitem><para>No Name <email>root@uglabgw.ug.cs.sunysb.edu</email></para></listitem>
<listitem><para>No Name <email>stephen.ma@jtec.com.au</email></para></listitem>
<listitem><para>No Name <email>sumii@is.s.u-tokyo.ac.jp</email></para></listitem>
<listitem><para>No Name <email>takas-su@is.aist-nara.ac.jp</email></para></listitem>
<listitem><para>No Name <email>tamone@eig.unige.ch</email></para></listitem>
<listitem><para>No Name <email>tjevans@raleigh.ibm.com</email></para></listitem>
<listitem><para>No Name <email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para></listitem>
<listitem><para>No Name <email>torii@tcd.hitachi.co.jp</email></para></listitem>
<listitem><para>No Name <email>uenami@imasy.or.jp</email></para></listitem>
<listitem><para>No Name <email>uhlar@netlab.sk</email></para></listitem>
<listitem><para>No Name <email>vode@hut.fi</email></para></listitem>
<listitem><para>No Name <email>wlloyd@mpd.ca</email></para></listitem>
<listitem><para>No Name <email>wlr@furball.wellsfargo.com</email></para></listitem>
<listitem><para>No Name <email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para>No Name <email>yamagata@nwgpc.kek.jp</email></para></listitem>
<listitem><para>No Name <email>ziggy@ryan.org</email></para></listitem>
<listitem><para>Nobuhiro Yasutomi <email>nobu@psrc.isac.co.jp</email></para></listitem>
<listitem><para>Nobuyuki Koganemaru <email>kogane@koganemaru.co.jp</email></para></listitem>
<listitem><para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para></listitem>
@ -1873,15 +1873,15 @@ box can be opened)</para>
<listitem><para>Pascal Pederiva <email>pascal@zuo.dec.com</email></para></listitem>
<listitem><para>Pasvorn Boonmark <email>boonmark@juniper.net</email></para></listitem>
<listitem><para>Patrick Gardella <email>patrick@cre8tivegroup.com</email></para></listitem>
<listitem><para>Patrick Hausen</para></listitem>
<listitem><para>Patrick Hausen <email>unknown</email></para></listitem>
<listitem><para>Paul Antonov <email>apg@demos.su</email></para></listitem>
<listitem><para>Paul F. Werkowski</para></listitem>
<listitem><para>Paul F. Werkowski <email>unknown</email></para></listitem>
<listitem><para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para></listitem>
<listitem><para>Paul Koch <email>koch@thehub.com.au</email></para></listitem>
<listitem><para>Paul Kranenburg <email>pk@NetBSD.org</email></para></listitem>
<listitem><para>Paul Mackerras <email>paulus@cs.anu.edu.au</email></para></listitem>
<listitem><para>Paul Popelka <email>paulp@uts.amdahl.com</email></para></listitem>
<listitem><para>Paul S. LaFollette, Jr.</para></listitem>
<listitem><para>Paul S. LaFollette, Jr. <email>unknown</email></para></listitem>
<listitem><para>Paul Saab <email>paul@mu.org</email></para></listitem>
<listitem><para>Paul Sandys <email>myj@nyct.net</email></para></listitem>
<listitem><para>Paul T. Root <email>proot@horton.iaces.com</email></para></listitem>
@ -1897,7 +1897,7 @@ box can be opened)</para>
<listitem><para>Peter Jeremy <email>perer.jeremy@alcatel.com.au</email></para></listitem>
<listitem><para>Peter M. Chen <email>pmchen@eecs.umich.edu</email></para></listitem>
<listitem><para>Peter Much <email>peter@citylink.dinoex.sub.org</email></para></listitem>
<listitem><para>Peter Olsson</para></listitem>
<listitem><para>Peter Olsson <email>unknown</email></para></listitem>
<listitem><para>Peter Philipp <email>pjp@bsd-daemon.net</email></para></listitem>
<listitem><para>Peter Stubbs <email>PETERS@staidan.qld.edu.au</email></para></listitem>
<listitem><para>Phil Maker <email>pjm@cs.ntu.edu.au</email></para></listitem>
@ -1930,7 +1930,7 @@ box can be opened)</para>
<listitem><para>Richard Winkel <email>rich@math.missouri.edu</email></para></listitem>
<listitem><para>Richard Wiwatowski <email>rjwiwat@adelaide.on.net</email></para></listitem>
<listitem><para>Rick Macklem <email>rick@snowhite.cis.uoguelph.ca</email></para></listitem>
<listitem><para>Rick Macklin</para></listitem>
<listitem><para>Rick Macklin <email>unknown</email></para></listitem>
<listitem><para>Rob Austein <email>sra@epilogue.com</email></para></listitem>
<listitem><para>Rob Mallory <email>rmallory@qualcomm.com</email></para></listitem>
<listitem><para>Rob Snow <email>rsnow@txdirect.net</email></para></listitem>
@ -1943,14 +1943,14 @@ box can be opened)</para>
<listitem><para>Robert Swindells <email>swindellsr@genrad.co.uk</email></para></listitem>
<listitem><para>Robert Watson <email>robert@cyrus.watson.org</email></para></listitem>
<listitem><para>Robert Withrow <email>witr@rwwa.com</email></para></listitem>
<listitem><para>Robert Yoder</para></listitem>
<listitem><para>Robert Yoder <email>unknown</email></para></listitem>
<listitem><para>Robin Carey <email>robin@mailgate.dtc.rankxerox.co.uk</email></para></listitem>
<listitem><para>Roger Hardiman <email>roger@cs.strath.ac.uk</email></para></listitem>
<listitem><para>Roland Jesse <email>jesse@cs.uni-magdeburg.de</email></para></listitem>
<listitem><para>Ron Bickers <email>rbickers@intercenter.net</email></para></listitem>
<listitem><para>Ron Lenk <email>rlenk@widget.xmission.com</email></para></listitem>
<listitem><para>Ronald Kuehn <email>kuehn@rz.tu-clausthal.de</email></para></listitem>
<listitem><para>Rudolf Cejka</para></listitem>
<listitem><para>Rudolf Cejka <email>unknown</email></para></listitem>
<listitem><para>Ruslan Belkin <email>rus@home2.UA.net</email></para></listitem>
<listitem><para>Ruslan Ermilov <email>ru@ucb.crimea.ua</email></para></listitem>
<listitem><para>Ruslan Shevchenko <email>rssh@cam.grad.kiev.ua</email></para></listitem>
@ -2008,7 +2008,7 @@ box can be opened)</para>
<listitem><para>Stefan Bethke <email>stb@hanse.de</email></para></listitem>
<listitem><para>Stefan Eggers <email>seggers@semyam.dinoco.de</email></para></listitem>
<listitem><para>Stefan Moeding <email>s.moeding@ndh.net</email></para></listitem>
<listitem><para>Stefan Petri</para></listitem>
<listitem><para>Stefan Petri <email>unknown</email></para></listitem>
<listitem><para>Stefan `Sec` Zehl <email>sec@42.org</email></para></listitem>
<listitem><para>Steinar Haug <email>sthaug@nethelp.no</email></para></listitem>
<listitem><para>Stephane E. Potvin <email>sepotvin@videotron.ca</email></para></listitem>
@ -2021,7 +2021,7 @@ box can be opened)</para>
<listitem><para>Stephen McKay <email>syssgm@devetir.qld.gov.au</email></para></listitem>
<listitem><para>Stephen Melvin <email>melvin@zytek.com</email></para></listitem>
<listitem><para>Steve Bauer <email>sbauer@rock.sdsmt.edu</email></para></listitem>
<listitem><para>Steve Deering</para></listitem>
<listitem><para>Steve Deering <email>unknown</email></para></listitem>
<listitem><para>Steve Gerakines <email>steve2@genesis.tiac.net</email></para></listitem>
<listitem><para>Steve Gericke <email>steveg@comtrol.com</email></para></listitem>
<listitem><para>Steve Piette <email>steve@simon.chi.il.US</email></para></listitem>
@ -2030,7 +2030,7 @@ box can be opened)</para>
<listitem><para>Steven H. Samorodin <email>samorodi@NUXI.com</email></para></listitem>
<listitem><para>Steven McCanne <email>mccanne@cs.berkeley.edu</email></para></listitem>
<listitem><para>Steven Plite <email>splite@purdue.edu</email></para></listitem>
<listitem><para>Steven Wallace</para></listitem>
<listitem><para>Steven Wallace <email>unknown</email></para></listitem>
<listitem><para>Stuart Henderson <email>stuart@internationalschool.co.uk</email></para></listitem>
<listitem><para>Sue Blake <email>sue@welearn.com.au</email></para></listitem>
<listitem><para>Sugiura Shiro <email>ssugiura@duo.co.jp</email></para></listitem>
@ -2055,7 +2055,7 @@ box can be opened)</para>
<listitem><para>Tatsumi HOSOKAWA <email>hosokawa@jp.FreeBSD.org</email></para></listitem>
<listitem><para>Ted Buswell <email>tbuswell@mediaone.net</email></para></listitem>
<listitem><para>Ted Faber <email>faber@isi.edu</email></para></listitem>
<listitem><para>Ted Lemon</para></listitem>
<listitem><para>Ted Lemon <email>unknown</email></para></listitem>
<listitem><para>Terry Lambert <email>terry@lambert.org</email></para></listitem>
<listitem><para>Terry Lee <email>terry@uivlsi.csl.uiuc.edu</email></para></listitem>
<listitem><para>Tetsuya Furukawa <email>tetsuya@secom-sis.co.jp</email></para></listitem>
@ -2067,7 +2067,7 @@ box can be opened)</para>
<listitem><para>Thomas Gellekum <email>thomas@ghpc8.ihf.rwth-aachen.de</email></para></listitem>
<listitem><para>Thomas Graichen <email>graichen@omega.physik.fu-berlin.de</email></para></listitem>
<listitem><para>Thomas K&ouml;nig <email>Thomas.Koenig@ciw.uni-karlsruhe.de</email></para></listitem>
<listitem><para>Thomas Ptacek</para></listitem>
<listitem><para>Thomas Ptacek <email>unknown</email></para></listitem>
<listitem><para>Thomas Stromberg <email>tstrombe@rtci.com</email></para></listitem>
<listitem><para>Thomas Valentino Crimi <email>tcrimi+@andrew.cmu.edu</email></para></listitem>
<listitem><para>Thomas Wintergerst <email>thomas@lemur.nord.de</email></para></listitem>

40
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -414,7 +414,7 @@ subscribe cvs-all</programlisting>
any detected changes being compressed, stamped with a
sequence-number and encoded for transmission over email (in printable
ASCII only). Once received, these &ldquo;CTM deltas&rdquo; can then be handed
to the <citerefentry><refentrytitle>ctm_rmail</refentrytitle><manvolnum>1</manvolnum></citerefentry> utility which will automatically decode, verify
to the &man.ctm.rmail.1; utility which will automatically decode, verify
and apply the changes to the user's copy of the sources. This
process is far more efficient than <application>CVSup</application>, and places less strain on
our server resources since it is a <emphasis>push</emphasis> rather
@ -447,10 +447,7 @@ subscribe cvs-all</programlisting>
against one of the FreeBSD project's official anoncvs servers. To
use it, one simply sets the <envar>CVSROOT</envar> environment
variable to point at the appropriate anoncvs server and then uses
the <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> command to access it like any local
the &man.cvs.1; command to access it like any local
repository.</para>
<para>While it can also be said that the <link
@ -481,10 +478,7 @@ subscribe cvs-all</programlisting>
<sect3>
<title><anchor id="anoncvs-usage">Using Anonymous CVS</title>
<para>Configuring <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> to use an Anonymous CVS repository is a simple
<para>Configuring &man.cvs.1; to use an Anonymous CVS repository is a simple
matter of setting the <envar>CVSROOT</envar> environment variable
to point to one of the FreeBSD project's
<emphasis>anoncvs</emphasis> servers. At the time of this writing,
@ -500,10 +494,7 @@ subscribe cvs-all</programlisting>
<para>Since CVS allows one to &ldquo;check out&rdquo; virtually any
version of the FreeBSD sources that ever existed (or, in some
cases, will exist <!-- smiley -->:), you need to be familiar with
the revision (<option>-r</option>) flag to <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> and what some of the permissible values for it in
the revision (<option>-r</option>) flag to &man.cvs.1; and what some of the permissible values for it in
the FreeBSD Project repository are.</para>
<para>There are two kinds of tags, revision tags and branch tags. A
@ -655,26 +646,19 @@ subscribe cvs-all</programlisting>
<para>When you specify a branch tag, you normally receive the latest
versions of the files on that line of development. If you wish to
receive some past version, you can do so by specifying a date with
the <option>-D date</option> flag. See the <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> man page for more details.</para>
the <option>-D date</option> flag. See the &man.cvs.1; man page for more details.</para>
</sect3>
<sect3>
<title>Examples</title>
<para>While it really is recommended that you read the manual page
for <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> thoroughly before doing
for &man.cvs.1; thoroughly before doing
anything, here are some quick examples which essentially show how
to use Anonymous CVS:</para>
<example>
<title>Checking out something from -current (<citerefentry>
<refentrytitle>ls</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>) and deleting it
<title>Checking out something from -current (&man.ls.1;) and deleting it
again:</title>
<screen>
@ -694,9 +678,7 @@ subscribe cvs-all</programlisting>
</example>
<example>
<title>Creating a list of changes (as unidiffs) to <citerefentry>
<refentrytitle>ls</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> between FreeBSD 2.2.2
<title>Creating a list of changes (as unidiffs) to &man.ls.1; between FreeBSD 2.2.2
and FreeBSD 2.2.6:</title>
<screen>
@ -1556,7 +1538,7 @@ cvs-crypto</programlisting>
the latest versions of the files on that line of
development. If you wish to receive some past version,
you can do so by specifying a date with the <option>date=</option> value
field. The <citerefentry><refentrytitle>cvsup</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page explains how to do
field. The &man.cvsup.1; manual page explains how to do
that.</para>
<para>For our example, we wish to receive FreeBSD-current.
@ -1657,7 +1639,7 @@ exists before running CVSup. On any particular run of
alone.</para>
<para><literal>use-rel-suffix</literal> is ... arcane. If you really want to
know about it, see the <citerefentry><refentrytitle>cvsup</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page. Otherwise,
know about it, see the &man.cvsup.1; manual page. Otherwise,
just specify it and do not worry about it.</para>
<para><literal>compress</literal> enables the use of gzip-style compression
@ -1751,7 +1733,7 @@ cvs-crypto</programlisting>
see the manual page.</para>
<para>Once you are satisfied with the way updates are working, you
can arrange for regular runs of cvsup using <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Obviously,
can arrange for regular runs of cvsup using &man.cron.8;. Obviously,
you should not let cvsup use its GUI when running it from
cron.</para>

2
en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
View file

@ -540,7 +540,7 @@ help
<para>This is
the mailing list for reporting bugs in FreeBSD Whenever
possible, bugs should be submitted using the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
possible, bugs should be submitted using the &man.send-pr.1;
command or the <ulink
URL="http://www.freebsd.org/send-pr.html">WEB
interface</ulink> to it.</para>

24
en_US.ISO8859-1/books/handbook/hw/chapter.sgml
View file

@ -2628,7 +2628,7 @@ INS8250 -&gt; INS8250B
<para>The <devicename>sio</devicename> driver provides
support for NS8250-, NS16450-, NS16550 and NS16550A-based EIA
RS-232C (CCITT V.24) communications interfaces. Several
multiport cards are supported as well. See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for detailed technical
multiport cards are supported as well. See the &man.sio.4; manual page for detailed technical
documentation.</para>
@ -2719,7 +2719,7 @@ options COM_MULTIPORT</programlisting>
sio<replaceable>n</replaceable></literal> lines are,
you will need to add 16 more devices. Only
the last device includes the interrupt vector for the
board. (See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for detail as
board. (See the &man.sio.4; manual page for detail as
to why.) The following example is for a Boca Board with
an interrupt of 3, and a base IO address 100h. The IO
address for Each port is +8 hexadecimal from the
@ -4387,7 +4387,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
address of the device that is failing, and the desired
debug level in <filename>/sys/scsi/scsidebug.h</filename>.
If it probes but just does not work, you can use the
<citerefentry><refentrytitle>scsi</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to dynamically set a
&man.scsi.8; command to dynamically set a
debug level to it in a running kernel (if <literal>SCSIDEBUG</literal> is
defined). This will give you <emphasis>copious</emphasis> debugging output with
which to confuse the gurus. See <command>man 4
@ -4705,10 +4705,10 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
<sect3>
<title>General tape access commands</title>
<para><citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> provides generic access to the tape
<para>&man.mt.1; provides generic access to the tape
drives. Some of the more common commands are
<command>rewind</command>, <command>erase</command>, and
<command>status</command>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry>
<command>status</command>. See the &man.mt.1;
manual page for a detailed description.</para>
</sect3>
@ -4728,12 +4728,12 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
<sect3>
<title>SCSI drives</title>
<para>The <citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry> driver provides
<para>The &man.st.4; driver provides
support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC
(Quarter-Inch Cartridge), DLT (Digital Linear Tape), QIC
Minicartridge and 9-track (remember the big reels that you see
spinning in Hollywood computer rooms) tape drives. See the
<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for a detailed
&man.st.4; manual page for a detailed
description.</para>
<para>The drives listed below are currently being used by members
@ -4876,7 +4876,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
and QIC-525 (DC6525) tapes as well.</para>
<para>Data transfer rate is 350kB/s using
<citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Rates of 530kB/s have been
&man.dump.8;. Rates of 530kB/s have been
reported when using <link
linkend="backups-programs-amanda">Amanda</link></para>
@ -4982,7 +4982,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
(250MB) tapes.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>).</para>
scsi tape device driver (&man.st.4;).</para>
<para>Under FreeBSD 2.2-current, use <command>mt
blocksize 512</command> to set the blocksize. (The
@ -5513,7 +5513,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
<para>Native capacity is 150/250MB.</para>
<para>This drive has quirks which are known and work around code
is present in the scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>). Upgrading the firmware to XXX
is present in the scsi tape device driver (&man.st.4;). Upgrading the firmware to XXX
version will fix the quirks and provide SCSI 2
capabilities.</para>
@ -5552,7 +5552,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
supported for the 2.5 GB cartridges.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>)
scsi tape device driver (&man.st.4;)
beginning with FreeBSD 2.2-current. For previous versions of
FreeBSD, use <command>mt</command> to read one
block from the tape, rewind the tape, and then execute the
@ -5590,7 +5590,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
erased.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>).</para>
scsi tape device driver (&man.st.4;).</para>
<para>Other firmware revisions that are known to work are:
M75D</para>

4
en_US.ISO8859-1/books/handbook/introduction/chapter.sgml
View file

@ -432,10 +432,10 @@
are the people who have <emphasis>write</emphasis> access to
the CVS tree, and are thus authorized to make modifications
to the FreeBSD source (the term &ldquo;committer&rdquo; comes from the
<citerefentry><refentrytitle>cvs</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>commit</command> command, which is used to
&man.cvs.1; <command>commit</command> command, which is used to
bring new changes into the CVS repository). The best way of
making submissions for review by the committers list is to
use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, though if something appears to be jammed in the system then you may also reach them by sending mail to <email>committers@freebsd.org</email>.</para>
use the &man.send-pr.1; command, though if something appears to be jammed in the system then you may also reach them by sending mail to <email>committers@freebsd.org</email>.</para>
</listitem>
</varlistentry>

26
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -122,7 +122,7 @@
<note>
<para>If you are trying to upgrade your kernel from an older version
of FreeBSD, you will probably have to get a new version of
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> from the same place you got the new
&man.config.8; from the same place you got the new
kernel sources. It is located in
<filename>/usr/src/usr.sbin</filename>, so you will need to
download those sources as well. Re-build and install it before
@ -430,7 +430,7 @@
hundred bytes to the kernel.</para>
<note>
<para>The <citerefentry><refentrytitle>ipcs</refentrytitle><manvolnum>1</manvolnum></citerefentry> command will tell
<para>The &man.ipcs.1; command will tell
will list any processes using each of these System V
facilities.</para>
</note>
@ -503,7 +503,7 @@
<listitem>
<para>Process filesystem. This is a pretend filesystem
mounted on <filename>/proc</filename> which allows
programs like <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> to give you more
programs like &man.ps.1; to give you more
information on what processes are running.</para>
</listitem>
</varlistentry>
@ -609,7 +609,7 @@
<note>
<para>QIC-80 tape support requires a separate filter
program called <citerefentry><refentrytitle>ft</refentrytitle><manvolnum>8</manvolnum></citerefentry>, see the manual
program called &man.ft.8;, see the manual
page for details.</para>
</note>
</listitem>
@ -975,7 +975,7 @@
modem to 2 (for obscure technical reasons IRQ 2 = IRQ 9)
in order to access it from FreeBSD. If you have a
multiport serial card, check the manual page for
<citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for more information on the
&man.sio.4; for more information on the
proper values for these lines. Some video cards (notably
those based on S3 chips) use IO addresses of the form
<literal>0x*2e8</literal>, and since many cheap serial
@ -1250,7 +1250,7 @@
network interfaces to be placed in promiscuous mode,
capturing every packet on a broadcast network (e.g. an
ethernet). These packets can be captured to disk and/or
examined with the <citerefentry><refentrytitle>tcpdump</refentrytitle><manvolnum>1</manvolnum></citerefentry> program.
examined with the &man.tcpdump.1; program.
Note that implementation of this capability can seriously
compromise your overall network security. The
<replaceable>number</replaceable> after bpfilter is the number
@ -1445,7 +1445,7 @@
<listitem>
<para>Snoop device. This pseudo-device allows one terminal
session to watch another using the
<citerefentry><refentrytitle>watch</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. Note that
&man.watch.8; command. Note that
implementation of this capability has important security
and privacy implications. The <replaceable>number</replaceable>
after snp is the total number of simultaneous snoop
@ -1457,7 +1457,7 @@
<listitem>
<para>Vnode driver. Allows a file to be treated as a device
after being set up with the <citerefentry><refentrytitle>vnconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry>
after being set up with the &man.vnconfig.8;
command. This driver can be useful for manipulating
floppy disk images and using a file as a swap device (e.g.
an MS Windows swap file). Optional.</para>
@ -1473,8 +1473,8 @@
&ldquo;meta&rdquo;-disk. The <replaceable>number</replaceable> after ccd
is the total number of concatenated disks (not total
number of disks that can be concatenated) that can be
created. (See <citerefentry><refentrytitle>ccd</refentrytitle><manvolnum>4</manvolnum></citerefentry> and
<citerefentry><refentrytitle>ccdconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> man pages for more
created. (See &man.ccd.4; and
&man.ccdconfig.8; man pages for more
details.) Optional.</para>
</listitem>
</varlistentry>
@ -1642,7 +1642,7 @@ controller wcd0</programlisting>
resource is the <filename>/var/log/messages</filename> file
which records, among other things, all of the kernel
messages from every successful boot. Also, the
<citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>8</manvolnum></citerefentry> command will print the kernel
&man.dmesg.8; command will print the kernel
messages from the current boot.</para>
<note>
@ -1655,7 +1655,7 @@ controller wcd0</programlisting>
with the last installed kernel which may be
non-functional. Also, as soon as possible, move the
working kernel to the proper <filename>kernel</filename> location or
commands such as <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> will not work
commands such as &man.ps.1; will not work
properly. The proper command to &ldquo;unlock&rdquo; the
kernel file that <command>make</command> installs (in
order to move another kernel back permanently) is:</para>
@ -1683,7 +1683,7 @@ controller wcd0</programlisting>
from the one that the system utilities have been built with,
for example, an experimental &ldquo;2.2.0&rdquo; kernel on a
2.1.0-RELEASE system, many system-status commands like
<citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> and <citerefentry><refentrytitle>vmstat</refentrytitle><manvolnum>8</manvolnum></citerefentry>
&man.ps.1; and &man.vmstat.8;
will not work any more. You must recompile the <filename>libkvm</filename> library as well as these
utilities. This is one reason it is not normally a good
idea to use a different version of the kernel from the rest

17
en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml
View file

@ -13,10 +13,7 @@
is too small to hold the dump, you can configure your kernel to use
an alternate dump device (in the <literal>config
kernel</literal> line), or you can specify an alternate using the
<citerefentry><refentrytitle>dumpon</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. The best way to use <citerefentry>
<refentrytitle>dumpon</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> is to set the <literal>dumpdev</literal> variable in
&man.dumpon.8; command. The best way to use &man.dumpon.8; is to set the <literal>dumpdev</literal> variable in
<filename>/etc/rc.conf</filename>. Typically you want to specify one of
the swap devices specified in <filename>/etc/fstab</filename>.
Dumps to non-swap devices, tapes for example,
@ -25,10 +22,10 @@ Dumps to non-swap devices, tapes for example,
Configuration</link> for
details on configuring the FreeBSD kernel.</para>
<para>Use the <citerefentry><refentrytitle>dumpon</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to tell the kernel
<para>Use the &man.dumpon.8; command to tell the kernel
where to dump to (note that this will have to be done after
configuring the partition in question as swap space via
<citerefentry><refentrytitle>swapon</refentrytitle><manvolnum>8</manvolnum></citerefentry>). This is normally arranged via
&man.swapon.8;). This is normally arranged via
<filename>/etc/rc.conf</filename> and <filename>/etc/rc</filename>.
Alternatively, you can hard-code the dump device via the <literal>dump</literal>
clause in the <literal>config</literal> line of your kernel config file. This is
@ -68,7 +65,7 @@ Dumps to non-swap devices, tapes for example,
&prompt.root; <userinput>exit</userinput> # ...to multi-user</screen>
<para>This instructs <citerefentry><refentrytitle>savecore</refentrytitle><manvolnum>8</manvolnum></citerefentry> to
<para>This instructs &man.savecore.8; to
use another kernel for symbol name extraction. It would otherwise
default to the currently running kernel and most likely not do
anything at all since the crash dump and the kernel symbols
@ -279,7 +276,7 @@ Dumps to non-swap devices, tapes for example,
generated code, so you will finally get a new kernel with similar
code to the faulting one but some debugging symbols. You should at
least verify the old and new sizes with the
<citerefentry><refentrytitle>size</refentrytitle><manvolnum>1</manvolnum></citerefentry> command. If there is a mismatch, you
&man.size.1; command. If there is a mismatch, you
probably need to give up here.</para>
<para>Go and examine the dump as described above. The debugging
@ -479,7 +476,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
<para>The return value will be printed.</para>
<para>For a <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> style summary of all running
<para>For a &man.ps.1; style summary of all running
processes, use:</para>
@ -525,7 +522,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
<para>However, it is highly recommended to have a
printed copy of the <citerefentry><refentrytitle>ddb</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page
printed copy of the &man.ddb.4; manual page
ready for a debugging session. Remember that it is hard to read the
on-line manual while single-stepping the kernel.</para>

8
en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml
View file

@ -19,10 +19,10 @@
the supported options in the kernel into new-style ones, so for
people who correctly did a <command>make depend</command>
in their kernel compile directory after running
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry>, the build process will automatically
&man.config.8;, the build process will automatically
pick up modified options, and only recompile those files where it is
necessary. Wiping out the old compile directory on each run of
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> as it is still done now can then be
&man.config.8; as it is still done now can then be
eliminated again.</para>
<para>Basically, a kernel option is nothing else than the definition
@ -89,7 +89,7 @@ options notyet,notdef</programlisting>
using such an option is responsible himself for knowing about its
implications (and maybe manually forcing the recompilation of parts
of his kernel). Once the transition of all supported options has
been done, <citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> will warn whenever an
been done, &man.config.8; will warn whenever an
unsupported option appears in the config file, but it will
nevertheless include it into the kernel Makefile.</para>
@ -114,7 +114,7 @@ options notyet,notdef</programlisting>
<filename>opt_<replaceable>foo</replaceable>.h</filename> already
available for the intended new option, invent a new name. Make it
meaningful, and comment the new section in the
<filename>options[<replaceable>.&lt;arch&gt;</replaceable>]</filename> file. <citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves..</para>
<filename>options[<replaceable>.&lt;arch&gt;</replaceable>]</filename> file. &man.config.8; will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves..</para>
<para>Packing too many options into a single
<filename>opt_<replaceable>foo</replaceable>.h</filename> will cause

28
en_US.ISO8859-1/books/handbook/l10n/chapter.sgml
View file

@ -49,7 +49,7 @@ font8x8=cp866-8x8</programlisting>
<para>This tuning means KOI8-R keyboard with Alternative
screen font mapped to KOI8-R encoding to preserve
pseudographics, <literal>Gray Delete</literal>
key remapped to match Russian <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry for FreeBSD
key remapped to match Russian &man.termcap.5; entry for FreeBSD
console.</para>
<para>RUS/LAT switch will be <literal>CapsLock</literal>. Old CapsLock function still
@ -83,7 +83,7 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<listitem>
<para><envar>LANG</envar> for POSIX
<citerefentry><refentrytitle>setlocale</refentrytitle><manvolnum>3</manvolnum></citerefentry> family functions;</para>
&man.setlocale.3; family functions;</para>
</listitem>
<listitem>
@ -95,8 +95,8 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<para>The best way is using <filename>/etc/login.conf</filename>
<literal>russian</literal> user's login class in
<citerefentry><refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry login class
position. See <citerefentry><refentrytitle>login.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
&man.passwd.5; entry login class
position. See &man.login.conf.5; for
details.</para>
@ -115,9 +115,9 @@ russian:Russian Users Accounts:\
<sect4>
<title>How to do it with <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.vipw.8;</title>
<para>If you use <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new
<para>If you use &man.vipw.8; for adding new
users, <filename>/etc/master.passwd</filename> entry should
looks like:</para>
@ -127,9 +127,9 @@ user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh</programlisting>
</sect4>
<sect4>
<title>How to do it with <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.adduser.8;</title>
<para>If you use <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new
<para>If you use &man.adduser.8; for adding new
users:</para>
<itemizedlist>
@ -149,7 +149,7 @@ defaultclass = russian</programlisting> in
<screen><prompt>Enter login class:</prompt> default []:</screen>
prompt from
<citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;</para>
&man.adduser.8;;</para>
</listitem>
<listitem>
@ -166,9 +166,9 @@ defaultclass = russian</programlisting> in
</sect4>
<sect4>
<title>How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.pw.8;</title>
<para>If you use <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users,
<para>If you use &man.pw.8; for adding new users,
call it in this form:</para>
@ -245,21 +245,21 @@ lp|Russian local line printer:\
:sh:of=/usr/libexec/lpr/ru/koi2alt:\
:lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:</programlisting>
<para>See <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para>
<para>See &man.printcap.5; for detailed description.</para>
</sect2>
<sect2 id="russian-msdosfs">
<title>MSDOS FS and Russian file names</title>
<para>Look at following example <citerefentry><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry to enable support for Russian
<para>Look at following example &man.fstab.5; entry to enable support for Russian
file names in MSDOS FS:</para>
<programlisting>
/dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0</programlisting>
<para>See
<citerefentry><refentrytitle>mount_msdos</refentrytitle><manvolnum>8</manvolnum></citerefentry>for detailed description of
&man.mount.msdos.8; for detailed description of
<option>-W</option> and <option>-L</option> options.</para>
</sect2>

7
en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -404,7 +404,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
check if it needs shared libraries, and if so, whether you have
them installed in the <filename>/compat/linux</filename> tree.
To do this, you run the Linux version <command>ldd</command> on the new program,
and watch its output. <command>ldd</command> (see also the manual page for <citerefentry><refentrytitle>ldd</refentrytitle><manvolnum>1</manvolnum></citerefentry>)
and watch its output. <command>ldd</command> (see also the manual page for &man.ldd.1;)
will print a list of shared libraries that the program depends
on, in the form <literal><replaceable>majorname</replaceable> (<replaceable>jumpversion</replaceable>) =&gt; <replaceable>fullname</replaceable></literal>.</para>
@ -433,10 +433,7 @@ Abort</screen>
<para>To help the FreeBSD kernel distinguish between a FreeBSD ELF
binary from a Linux binary, use the <citerefentry>
<refentrytitle>brandelf</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> utility.</para>
binary from a Linux binary, use the &man.brandelf.1; utility.</para>
<screen>&prompt.user; <userinput>brandelf -t Linux my-linux-elf-binary</userinput></screen>

34
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -522,7 +522,7 @@ do-install:
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
the <citerefentry><refentrytitle>pkg_add</refentrytitle><manvolnum>1</manvolnum></citerefentry> program to install a
the &man.pkg.add.1; program to install a
package file on your system.</para>
</listitem>
@ -1170,7 +1170,7 @@ lib/X11/oneko/cat2.xpm
lib/X11/oneko/mouse.xpm
@dirrm lib/X11/oneko</programlisting>
<para>Refer to the <citerefentry><refentrytitle>pkg_create</refentrytitle><manvolnum>1</manvolnum></citerefentry> man page
<para>Refer to the &man.pkg.create.1; man page
for details on the packing list.</para>
<note>
@ -1290,19 +1290,10 @@ lib/X11/oneko/mouse.xpm
<filename>pkgname.tgz</filename> package, so delete them
now. Next, simply include the output of <command>shar `find
port_dir`</command> in a bug report and send it with the
<citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> program (see <link linkend="contrib-general">Bug
&man.send-pr.1; program (see <link linkend="contrib-general">Bug
Reports and General Commentary</link> for more information
about <citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry>. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use <citerefentry>
<refentrytitle>uuencode</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> before including it in the bug report (uuencoded
about &man.send-pr.1;. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use &man.uuencode.1; before including it in the bug report (uuencoded
tarfiles are acceptable even if the bug report is smaller than
20KB but are not preferred). Be sure to classify the bug report as
category <literal>ports</literal> and class
@ -2805,9 +2796,7 @@ diff -u -r1.15 PLIST
POST-INSTALL</literal>. <literal>&dollar;2</literal> can be
tested to determine which mode the script is being run in. The
<envar>PKG_PREFIX</envar> environmental variable will be set to
the package installation directory. See <citerefentry>
<refentrytitle>pkg_add</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> for additional
the package installation directory. See &man.pkg.add.1; for additional
information.</para>
<note>
@ -3045,7 +3034,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<command>diff -ruN superedit.bak
superedit</command>). Please examine the output to make
sure all the changes make sense. The best way to send us the
diff is by including it to <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
diff is by including it to &man.send-pr.1;
(category <literal>ports</literal>). Please mention any added or deleted files
in the message, as they have to be explicitly specified to CVS
when doing a commit. If the diff is more than about 20KB, please
@ -3053,7 +3042,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
the PR.</para>
<para>Once again, please use
<citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> and not <citerefentry><refentrytitle>shar</refentrytitle><manvolnum>1</manvolnum></citerefentry> to send updates to ports.</para>
&man.diff.1; and not &man.shar.1; to send updates to ports.</para>
</sect2>
<sect2>
@ -3080,10 +3069,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
post-install:
strip ${PREFIX}/bin/xdl</programlisting>
<para>Use the <citerefentry>
<refentrytitle>file</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> command on the installed executable to check
<para>Use the &man.file.1; command on the installed executable to check
whether the binary is stripped or not. If it does not say
<literal>not stripped</literal>, it is stripped.</para>
</sect3>
@ -3788,7 +3774,7 @@ post-install:
(executables for superusers/managers),
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
files). See man &man.hier.7; for
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use

32
en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml
View file

@ -168,8 +168,8 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
<para>If you have a kernel without the tun device, and you can not
rebuild it for some reason, all is not lost. You should be able
to dynamically load the code. Refer to the appropriate <citerefentry><refentrytitle>modload</refentrytitle><manvolnum>8</manvolnum></citerefentry>
and <citerefentry><refentrytitle>lkm</refentrytitle><manvolnum>4</manvolnum></citerefentry> pages for further details.</para>
to dynamically load the code. Refer to the appropriate &man.modload.8;
and &man.lkm.4; pages for further details.</para>
<para>You may also wish to take this opportunity to configure a
firewall. Details can be found in the <link linkend="firewalls">Firewalls</link> section.</para>
@ -395,7 +395,7 @@ domain <replaceable>bar.com</replaceable></programlisting>
<listitem>
<para>The dial string. User PPP uses an expect-send
syntax similar to the <citerefentry><refentrytitle>chat</refentrytitle><manvolnum>8</manvolnum></citerefentry>
syntax similar to the &man.chat.8;
program. Refer to the manual page for information on
the features of this language.</para>
</listitem>
@ -1023,7 +1023,7 @@ set server /var/run/ppp-tun%d DiagnosticPassword 0177</programlisting>
tun device number that is in use.</para>
<para>Once a socket has been set up, the
<citerefentry><refentrytitle>pppctl</refentrytitle><manvolnum>8</manvolnum></citerefentry> program may be used in scripts that
&man.pppctl.8; program may be used in scripts that
wish to manipulate the running program.</para>
</sect3>
@ -1190,7 +1190,7 @@ sendmail_flags="-bd"</programlisting>
<step>
<para>Create an entry in <filename>/etc/passwd</filename>
(using the <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> program).</para>
(using the &man.vipw.8; program).</para>
</step>
<step>
@ -2014,12 +2014,12 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
otherwise, check the place where you found this document for a
document named <filename>dialup.txt</filename> or something
similar. You may also want to check the manual pages for
<citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for information on the serial
port device driver and <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry>, &amp; <citerefentry><refentrytitle>init</refentrytitle><manvolnum>8</manvolnum></citerefentry> for
&man.sio.4; for information on the serial
port device driver and &man.ttys.5;,
&man.gettytab.5;,
&man.getty.8;, &amp; &man.init.8; for
information relevant to configuring the system to accept logins on
modems, and perhaps <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for information on
modems, and perhaps &man.stty.1; for information on
setting serial port parameters (such as <literal>clocal</literal> for directly-connected serial
interfaces).</para>
@ -2082,8 +2082,8 @@ Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp</programlisting>
goes wrong, <command>sliplogin</command> usually logs
good informational messages via the <literal>daemon</literal> syslog facility,
which usually goes into <filename>/var/log/messages</filename>
(see the manual pages for <citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry> and
<citerefentry><refentrytitle>syslog.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>, and perhaps check
(see the manual pages for &man.syslogd.8; and
&man.syslog.conf.5, and perhaps check
<filename>/etc/syslog.conf</filename> to see to which files
<command>syslogd</command> is logging).</para>
@ -2163,7 +2163,7 @@ pseudo-device sl 2</programlisting>
<para>As mentioned earlier, there are three files in the
<filename>/etc/sliphome</filename> directory that are part of the
configuration for <filename>/usr/sbin/sliplogin</filename> (see
<citerefentry><refentrytitle>sliplogin</refentrytitle><manvolnum>8</manvolnum></citerefentry> for the actual manual page for
&man.sliplogin.8; for the actual manual page for
<command>sliplogin</command>):
<filename>slip.hosts</filename>, which defines the SLIP users
&amp; their associated IP addresses;
@ -2281,7 +2281,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
SLIP server's Ethernet subnet, and you will also need to adjust
your <filename>/etc/sliphome/slip.login</filename> and
<filename>/etc/sliphome/slip.logout</filename> scripts to use
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> to manage the proxy-ARP entries in the
&man.arp.8; to manage the proxy-ARP entries in the
SLIP server's ARP table.</para>
</sect3>
@ -2355,8 +2355,8 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<command>netstat -i</command> must be changed to colons and
leading zeros should be added to each single-digit hexadecimal
number to convert the address into the form that
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> desires; see the manual page on
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> for complete information on
&man.arp.8; desires; see the manual page on
&man.arp.8; for complete information on
usage.</para>
<note>

282
en_US.ISO8859-1/books/handbook/printing/chapter.sgml
View file

@ -448,8 +448,7 @@ sio2: type 16550A</screen>
<procedure>
<step>
<para>Become root with the <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>
<para>Become root with the &man.su.1;
command. Enter the root password when prompted.</para>
</step>
@ -523,8 +522,7 @@ sio2: type 16550A</screen>
works.</para>
<para>You can set the communications mode in two ways: by
configuring the kernel or by using the <citerefentry>
<refentrytitle>lptcontrol</refentrytitle></citerefentry> program.</para>
configuring the kernel or by using the &man.lptcontrol.8; program.</para>
<para><emphasis>To set the communications mode by
configuring the kernel:</emphasis></para>
@ -571,8 +569,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
</procedure>
<para><emphasis>To set the communications mode
with</emphasis> <citerefentry>
<refentrytitle>lptcontrol</refentrytitle></citerefentry>:</para>
with</emphasis> &man.lptcontrol.8;:</para>
<procedure>
@ -601,7 +598,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
<para>You could put these commands in your
<filename>/etc/rc.local</filename> file to set the mode each
time your system boots. See <citerefentry><refentrytitle>lptcontrol</refentrytitle><manvolnum>8</manvolnum></citerefentry> for more information.</para>
time your system boots. See &man.lptcontrol.8; for more information.</para>
</sect4>
@ -615,8 +612,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
<para>To test the printer, we will send some text to it. For
printers that can immediately print characters sent to them,
the program <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> is perfect: it generates all 96 printable ASCII characters in 96 lines.</para>
the program &man.lptest.1; is perfect: it generates all 96 printable ASCII characters in 96 lines.</para>
<para>For a PostScript (or other language-based) printer, we
will need a more sophisticated test. A small PostScript
@ -653,8 +649,7 @@ showpage</programlisting>
<procedure>
<step>
<para>Become root with <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>.</para>
<para>Become root with &man.su.1;.</para>
</step>
<step>
@ -663,8 +658,7 @@ showpage</programlisting>
<listitem>
<para>If the printer can print plain text, then
use <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. Type:</para>
use &man.lptest.1;. Type:</para>
<screen>&prompt.root; <userinput>lptest &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
@ -726,8 +720,7 @@ showpage</programlisting>
<procedure>
<step>
<para>Become root with <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>.</para>
<para>Become root with &man.su.1;.</para>
</step>
<step>
@ -753,8 +746,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
</step>
<step>
<para>Connect to the printer with <citerefentry>
<refentrytitle>tip</refentrytitle></citerefentry>. Type:</para>
<para>Connect to the printer with &man.tip.1;. Type:</para>
<screen>&prompt.root; <userinput>tip printer</userinput></screen>
@ -771,8 +763,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<listitem>
<para>If the printer can print plain text, then
use <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. Type:</para>
use &man.lptest.1;. Type:</para>
<screen><prompt>~</prompt><userinput>$lptest</userinput></screen>
@ -799,8 +790,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<para>Where <replaceable>file</replaceable> is the name of the
file containing the program. After
<citerefentry>
<refentrytitle>tip</refentrytitle></citerefentry> sends the file, press any required end-of-file key.</para>
&man.tip.1; sends the file, press any required end-of-file key.</para>
</listitem>
</itemizedlist>
@ -831,8 +821,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
reads this file each time the spooler is used, so updates to the
file take immediate effect.</para>
<para>The format of the <citerefentry>
<refentrytitle>printcap</refentrytitle></citerefentry> file is straightforward. Use your favorite text editor to make changes to <filename>/etc/printcap</filename>. The format is identical to other capability files like <filename>/usr/share/misc/termcap</filename> and <filename>/etc/remote</filename>. For complete information about the format, see the <citerefentry><refentrytitle>cgetent</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
<para>The format of the &man.printcap.5; file is straightforward. Use your favorite text editor to make changes to <filename>/etc/printcap</filename>. The format is identical to other capability files like <filename>/usr/share/misc/termcap</filename> and <filename>/etc/remote</filename>. For complete information about the format, see the &man.cgetent.3;.</para>
<para>The simple spooler configuration consists of the following
steps:</para>
@ -880,8 +869,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<step>
<para>Test the setup by printing something with the
<citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
&man.lpr.1;
command; see <link linkend="printing-trying">Trying
It Out</link> and <link linkend="printing-troubleshooting">Troubleshooting</link>.</para>
</step>
@ -1006,8 +994,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
is customary to put these directories under
<filename>/var/spool</filename>. It is not necessary to
backup the contents of spooling directories, either.
Recreating them is as simple as running <citerefentry>
<refentrytitle>mkdir</refentrytitle></citerefentry>.</para>
Recreating them is as simple as running &man.mkdir.1;.</para>
<para>It is also customary to make the directory with a name
that is identical to the name of the printer, as shown below:</para>
@ -1294,14 +1281,11 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
Unfortunately, congratulations are not quite yet in order,
since we still have to test the setup and correct any
problems. To test the setup, try printing something. To
print with the LPD system, you use the command <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>,
print with the LPD system, you use the command &man.lpr.1;,
which submits a job for printing.</para>
<para>You can combine <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
with the <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> program, introduced in section <link linkend="printing-testing">Checking Printer Communications</link> to generate some
<para>You can combine &man.lpr.1;
with the &man.lptest.1; program, introduced in section <link linkend="printing-testing">Checking Printer Communications</link> to generate some
test text.</para>
<para><emphasis>To test the simple LPD
@ -1315,17 +1299,14 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>Where <replaceable>printer-name</replaceable> is a the name of a printer
(or an alias) specified in <filename>/etc/printcap</filename>.
To test the default printer, type <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
To test the default printer, type &man.lpr.1;
without any <option>-P</option> argument. Again, if you are
testing a printer that expects PostScript, send a PostScript
program in that language instead of using <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. You
program in that language instead of using &man.lptest.1;. You
can do so by putting the program in a file and typing <command>lpr <replaceable>file</replaceable></command>.</para>
<para>For a PostScript printer, you should get the results of
the program. If you are using <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>, then your results should look like the following:</para>
the program. If you are using &man.lptest.1;, then your results should look like the following:</para>
<programlisting>
!"#$%&amp;'()*+,-./01234
@ -1335,8 +1316,7 @@ $%&amp;'()*+,-./01234567
%&amp;'()*+,-./012345678</programlisting>
<para>To further test the printer, try downloading larger
programs (for language-based printers) or running <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> with different arguments. For example, <command>lptest 80 60</command> will produce 60 lines of 80 characters each.</para>
programs (for language-based printers) or running &man.lptest.1; with different arguments. For example, <command>lptest 80 60</command> will produce 60 lines of 80 characters each.</para>
<para>If the printer did not work, see the next section, <link
linkend="printing-troubleshooting">Troubleshooting</link>.</para>
@ -1346,8 +1326,7 @@ $%&amp;'()*+,-./01234567
<sect4 id="printing-troubleshooting">
<title>Troubleshooting</title>
<para>After performing the simple test with <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>, you
<para>After performing the simple test with &man.lptest.1;, you
might have gotten one of the following results instead of the
correct printout:</para>
@ -1665,23 +1644,20 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
FreeBSD. Here is an overview of the user-level commands:</para>
<variablelist>
<varlistentry><term><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lpr.1;</term>
<listitem>
<para>Print jobs</para>
</listitem>
</varlistentry>
<varlistentry><term><citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lpq.1;</term>
<listitem>
<para>Check printer queues</para>
</listitem>
</varlistentry>
<varlistentry><term><citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lprm.1;</term>
<listitem>
<para>Remove jobs from a printer's queue</para>
@ -1689,16 +1665,12 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
</varlistentry>
</variablelist>
<para>There is also an administrative command, <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>,
<para>There is also an administrative command, &man.lpc.8;,
described in the section <link linkend="printing-lpc">Administrating the
LPD Spooler</link>, used to control printers and their queues.</para>
<para>All three of the commands <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>, and
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>
<para>All three of the commands &man.lpr.1;, &man.lprm.1;, and
&man.lpq.1;
accept an option <option>-P <replaceable>printer-name</replaceable></option> to specify on which
printer/queue to operate, as listed in the
<filename>/etc/printcap</filename> file. This enables you to
@ -1724,8 +1696,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>This prints each of the listed files to the
default printer. If you list no files, <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> reads
default printer. If you list no files, &man.lpr.1; reads
data to print from standard input. For example, this command
prints some important system files:</para>
@ -1747,14 +1718,12 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>Because no files were listed for the
<citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
&man.lpr.1;
command, <command>lpr</command> read the data to print
from standard input, which was the output of the <command>ls
-l</command> command.</para>
<para>The <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
<para>The &man.lpr.1; command
can also accept a wide variety of options to control formatting,
apply file conversions, generate multiple copies, and so forth.
For more information, see the section <link
@ -1765,8 +1734,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<sect2 id="printing-lpq">
<title>Checking Jobs</title>
<para>When you print with <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, the
<para>When you print with &man.lpr.1;, the
data you wish to print is put together in a package called a
&ldquo;print job&rdquo;, which is sent to the LPD spooling
system. Each printer has a queue of jobs, and your job waits in
@ -1775,8 +1743,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
order.</para>
<para>To display the queue for the default printer, type
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>. For a
&man.lpq.1;. For a
specific printer, use the <option>-P</option> option. For
example, the command
@ -1803,29 +1770,24 @@ active kelly 9 /etc/host.conf, /etc/hosts.equiv 88 bytes
details.</para>
<para>Job number nine consists of two files; multiple files given on
the <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
the &man.lpr.1; command
line are treated as part of a single job. It is the currently
active job (note the word <literal>active</literal>
under the &ldquo;Rank&rdquo; column), which means the printer should be
currently printing that job. The second job consists of data
passed as the standard input to the</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>&man.lpr.1;
command. The third job came from user mary; it is a much larger
job. The pathname of the files she's trying to print is too long
to fit, so the <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> command
to fit, so the &man.lpq.1; command
just shows three dots.</para>
<para>The very first line of the output from <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> is also
<para>The very first line of the output from &man.lpq.1; is also
useful: it tells what the printer is currently doing (or at least
what LPD thinks the printer is doing).</para>
<para>The <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> command
<para>The &man.lpq.1; command
also support a <option>-l</option> option to generate a detailed
long listing. Here is an example of <command>lpq -l</command>:</para>
@ -1848,16 +1810,13 @@ mary: 3rd [job 011rose]
<title>Removing Jobs</title>
<para>If you change your mind about printing a job, you can remove
the job from the queue with the <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
command. Often, you can even use <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry> to
the job from the queue with the &man.lprm.1;
command. Often, you can even use &man.lprm.1; to
remove an active job, but some or all of the job might still get
printed.</para>
<para>To remove a job from the default printer, first use
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> to find
&man.lpq.1; to find
the job number. Then type:</para>
@ -1873,8 +1832,7 @@ mary: 3rd [job 011rose]
<screen>&prompt.user; <userinput>lprm -P bamboo 10</userinput></screen>
<para>The <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
<para>The &man.lprm.1;
command has a few shortcuts:</para>
<variablelist>
@ -1900,8 +1858,7 @@ mary: 3rd [job 011rose]
<listitem>
<para>With no job number, user name, or
<option>-</option> appearing on the command line,
<citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry> removes the currently active job on the default printer, if it belongs to you. The superuser can remove any active job.</para>
&man.lprm.1; removes the currently active job on the default printer, if it belongs to you. The superuser can remove any active job.</para>
</listitem>
</varlistentry>
@ -1918,8 +1875,7 @@ mary: 3rd [job 011rose]
<note>
<para>If you are working in a networked
environment, <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
environment, &man.lprm.1;
will let you remove jobs only from the host from which the jobs
were submitted, even if the same printer is available from other
hosts. The following command sequence demonstrates this:</para>
@ -1945,8 +1901,7 @@ cfA013rose dequeued
<sect2 id="printing-lpr-options">
<title>Beyond Plain Text: Printing Options</title>
<para>The <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
<para>The &man.lpr.1; command
supports a number of options that control formatting text,
converting graphic and other file formats, producing multiple
copies, handling of the job, and more. This section describes the
@ -1956,12 +1911,10 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-format">
<title>Formatting and Conversion Options</title>
<para>The following <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>The following &man.lpr.1;
options control formatting of the files in the job. Use these
options if the job does not contain plain text or if you want
plain text formatted through the <citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
plain text formatted through the &man.pr.1;
utility.</para>
<para>For example, the following command prints a DVI file (from
@ -2050,9 +2003,8 @@ cfA013rose dequeued
<varlistentry><term>-p</term>
<listitem>
<para>Format plain text with <citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
before printing. See <citerefentry><refentrytitle>pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> for more information.</para>
<para>Format plain text with &man.pr.1;
before printing. See &man.pr.1; for more information.</para>
</listitem>
</varlistentry>
@ -2061,8 +2013,7 @@ cfA013rose dequeued
<listitem>
<para>Use <replaceable>title</replaceable> on the
<citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
&man.pr.1;
header instead of the file name. This option has effect
only when used with the <option>-p</option>
option.</para>
@ -2086,30 +2037,24 @@ cfA013rose dequeued
<para>Here is an example: this command prints a nicely formatted
version of the <citerefentry>
<refentrytitle>ls</refentrytitle></citerefentry> manual
version of the &man.ls.1; manual
page on the default printer:</para>
<screen>&prompt.user; <userinput>zcat /usr/share/man/man1/ls.1.gz | troff -t -man | lpr -t</userinput></screen>
<para>The <citerefentry>
<refentrytitle>zcat</refentrytitle></citerefentry>
<para>The &man.zcat.1;
command uncompresses the source of the</para>
<para><citerefentry>
<refentrytitle>ls</refentrytitle></citerefentry> manual
page and passes it to the <citerefentry>
<refentrytitle>troff</refentrytitle></citerefentry>
<para>&man.ls.1; manual
page and passes it to the &man.troff.1;
command, which formats that source and makes GNU troff output
and passes it to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>,
and passes it to &man.lpr.1;,
which submits the job to the LPD spooler. Because we used the
<option>-t</option> option to</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, the
<para>&man.lpr.1;, the
spooler will convert the GNU troff output into a format the
default printer can understand when it prints the job.</para>
@ -2118,8 +2063,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-job-handling">
<title>Job Handling Options</title>
<para>The following options to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> tell
<para>The following options to &man.lpr.1; tell
LPD to handle the job specially:</para>
@ -2200,8 +2144,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-misc">
<title>Header Page Options</title>
<para>These options to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>These options to &man.lpr.1;
adjust the text that normally appears on a job's header page.
If header pages are suppressed for the destination printer,
these options have no effect. See section <link
@ -2252,11 +2195,9 @@ cfA013rose dequeued
<title>Administrating Printers</title>
<para>As an administrator for your printers, you have had to
install, set up, and test them. Using the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
install, set up, and test them. Using the &man.lpc.8;
command, you can interact with your printers in yet more ways.
With <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>, you
With &man.lpc.8;, you
can</para>
@ -2290,14 +2231,11 @@ cfA013rose dequeued
in which case it will continue to print jobs in the queue until
the queue is empty.</para>
<para>In general, you have to have root privileges to use the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
command. Ordinary users can use the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> command
<para>In general, you have to have root privileges to use the &man.lpc.8;
command. Ordinary users can use the &man.lpc.8; command
to get printer status and to restart a hung printer only.</para>
<para>Here is a summary of the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
<para>Here is a summary of the &man.lpc.8;
commands. Most of the commands takes a <replaceable>printer-name</replaceable> argument to tell on which
printer to operate. You can use <literal>all</literal>
for the <replaceable>printer-name</replaceable> to mean all
@ -2353,8 +2291,7 @@ cfA013rose dequeued
<command>disable</command> followed by
<command>stop</command>. The <replaceable>message</replaceable> appears as the printer's
status whenever a user checks the printer's queue with
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>
&man.lpq.1;
or status with <command>lpc
status</command>.</para>
</listitem>
@ -2437,11 +2374,9 @@ cfA013rose dequeued
</variablelist>
<para><citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> accepts
<para>&man.lpc.8; accepts
the above commands on the command line. If you do not enter any
commands, <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> enters
commands, &man.lpc.8; enters
an interactive mode, where you can enter commands until you type
<command>exit</command>, <command>quit</command>, or end-of-file.</para>
@ -2570,10 +2505,8 @@ cfA013rose dequeued
<para>Which filter LPD starts and the filter's arguments depend on
what is listed in the <filename>/etc/printcap</filename> file
and what arguments the user specified for the job on the</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
and what arguments the user specified for the job on the
&man.lpr.1;
command line. For example, if the user typed <command>lpr
-t</command>, LPD would start the troff filter, listed in the
<literal>tf</literal> capability for the destination
@ -2854,8 +2787,7 @@ fi</programlisting>
text-to-PostScript program you wish. The FreeBSD ports
collection (see <link linkend="ports">The Ports
Collection</link>) includes a full featured text-to-PostScript
program called <citerefentry>
<refentrytitle>a2ps</refentrytitle></citerefentry> that you might want to investigate.</para>
program called <literal>a2ps</literal> that you might want to investigate.</para>
</sect3>
@ -2886,10 +2818,9 @@ fi</programlisting>
<para>Here is an example: the following script is a text filter
for Hewlett Packard DeskJet 500 printers. For other printers,
substitute the <option>-sDEVICE</option> argument to the</para>
substitute the <option>-sDEVICE</option> argument to the
<para><citerefentry>
<refentrytitle>gs</refentrytitle></citerefentry> (Ghostscript) command. (Type <command>gs -h</command> to get a list of devices the current installation of Ghostscript supports.)</para>
<command>gs</command> (Ghostscript) command. (Type <command>gs -h</command> to get a list of devices the current installation of Ghostscript supports.)</para>
<programlisting>
#!/bin/sh
@ -3127,8 +3058,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
#
exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"</programlisting>
<para>This script runs <citerefentry>
<refentrytitle>dvips</refentrytitle></citerefentry> in filter mode (the <option>-f</option> argument) on standard input, which is the job to print. It then starts the PostScript printer filter <command>lprps</command> (see section <link linkend="printing-advanced-if-conversion">Accommodating Plain Text Jobs on PostScript
<para>This script runs <command>dvips</command> in filter mode (the <option>-f</option> argument) on standard input, which is the job to print. It then starts the PostScript printer filter <command>lprps</command> (see section <link linkend="printing-advanced-if-conversion">Accommodating Plain Text Jobs on PostScript
Printers</link>) with the arguments LPD passed to this script.
<command>lprps</command> will use those arguments
to account for the pages printed.</para>
@ -3238,17 +3168,13 @@ exit 2</programlisting>
<para>Now, for the hard part: making the filter. For that, we
need a DVI-to-LaserJet/PCL conversion program. The FreeBSD
ports collection (see <link linkend="ports">The
Ports Collection</link>) has one: <citerefentry>
<refentrytitle>dvi2xx</refentrytitle></citerefentry> is the
Ports Collection</link>) has one: <command>dvi2xx</command> is the
name of the package. Installing this package gives us the
program we need, <citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry>, which converts DVI into LaserJet IIp, LaserJet III, and LaserJet 2000 compatible codes.</para>
program we need, <command>dvilj2p</command>, which converts DVI into LaserJet IIp, LaserJet III, and LaserJet 2000 compatible codes.</para>
<para><citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> makes
<para><command>dvilj2p</command> makes
the filter <command>hpdf</command> quite complex since
<citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> cannot
<command>dvilj2p</command> cannot
read from standard input. It wants to work with a filename.
What is worse, the filename has to end in
<filename>.dvi</filename> so using
@ -3256,8 +3182,7 @@ exit 2</programlisting>
problematic. We can get around that problem by linking
(symbolically) a temporary file name (one that ends in
<filename>.dvi</filename>) to <filename>/dev/fd/0</filename>,
thereby forcing <citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> to read from standard input.</para>
thereby forcing <command>dvilj2p</command> to read from standard input.</para>
<para>The only other fly in the ointment is the fact that we
cannot use <filename>/tmp</filename> for the temporary link.
@ -3347,8 +3272,7 @@ exit 0</programlisting>
<para>All these conversion filters accomplish a lot for your
printing environment, but at the cost forcing the user to
specify (on the <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
specify (on the &man.lpr.1;
command line) which one to use. If your users are not
particularly computer literate, having to specify a filter
option will become annoying. What is worse, though, is that
@ -3366,8 +3290,8 @@ exit 0</programlisting>
you can still provide conversion filters just for them.</para>
<para>The FreeBSD ports collection has a text filter that
performs automatic conversion called <citerefentry>
<refentrytitle>apsfilter</refentrytitle></citerefentry>. It can detect plain text, PostScript, and DVI files, run the proper conversions, and print.</para>
performs automatic conversion called
<command>apsfilter</command>. It can detect plain text, PostScript, and DVI files, run the proper conversions, and print.</para>
</sect4>
</sect3>
@ -3565,8 +3489,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
they can suppress header pages by submitting the job with
<command>lpr -h</command>; see <link
linkend="printing-lpr-options-misc">Header Page
Options</link> for more <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
Options</link> for more &man.lpr.1;
options.</para>
<note>
@ -4175,8 +4098,7 @@ exit 0;</programlisting>
<para>If you feel multiple copies cause unnecessary wear and tear
on your printers, you can disable the <option>-#</option> option
to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> by
to &man.lpr.1; by
adding the <literal>sc</literal> capability to the
<filename>/etc/printcap</filename> file. When users submit jobs
with the <option>-#</option> option, they will see:</para>
@ -4235,8 +4157,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>By using the <literal>sc</literal>
capability, we prevent the use of <command>lpr -#</command>, but
that still does not prevent users from running <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
that still does not prevent users from running &man.lpr.1;
multiple times, or from submitting the same file multiple times
in one job like this:</para>
@ -4397,10 +4318,8 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
per line. Note that the file
<filename>/etc/hosts.equiv</filename> is also used by
the
<citerefentry><refentrytitle>ruserok</refentrytitle><manvolnum>3</manvolnum></citerefentry> protocol, and affects programs like <citerefentry>
<refentrytitle>rsh</refentrytitle></citerefentry> and
<citerefentry>
<refentrytitle>rcp</refentrytitle></citerefentry>, so be careful.</para>
&man.ruserok.3; protocol, and affects programs like &man.rsh.1; and
&man.rcp.1;, so be careful.</para>
<para>For example, here is the
<filename>/etc/hosts.lpd</filename> file on the host
@ -4567,8 +4486,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
with simple periodic accounting right away. They are the text
filter <command>lpf</command>, described in section
<link linkend="printing-advanced-lpf">lpf: a Text
Filter</link>, and <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>, a
Filter</link>, and &man.pac.8;, a
program to gather and total entries from printer accounting
files.</para>
@ -4606,11 +4524,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<filename>acct</filename>.</para>
<para>When you are ready to charge users for printouts, run
the <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
the &man.pac.8;
program. Just change to the spooling directory for the printer
you want to collect on and type <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>. You
you want to collect on and type <literal>pac</literal>. You
will get a dollar-centric summary like the following:</para>
@ -4626,8 +4542,7 @@ rose:root 26.00 12 $ 0.52
total 337.00 154 $ 6.74</screen>
<para>These are the arguments <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
<para>These are the arguments &man.pac.8;
expects:</para>
<variablelist>
@ -4694,8 +4609,7 @@ total 337.00 154 $ 6.74</screen>
</varlistentry>
</variablelist>
<para>In the default summary that <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
<para>In the default summary that &man.pac.8;
produces, you see the number of pages printed by each user from
various hosts. If, at your site, host does not matter (because
users can use any host), run <command>pac -m</command>, to
@ -4713,15 +4627,13 @@ total 337.00 154 $ 6.74</screen>
<para>To compute the dollar amount due,
<citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry> uses
&man.pac.8; uses
the <literal>pc</literal> capability in the
<filename>/etc/printcap</filename> file (default of 200, or 2
cents per page). Specify, in hundredths of cents, the price per
page or per foot you want to charge for printouts in this
capability. You can override this value when you run
<citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry> with
&man.pac.8; with
the <option>-p</option> option. The units for the
<option>-p</option> option are in dollars, though, not
hundredths of cents. For example,
@ -4738,8 +4650,7 @@ total 337.00 154 $ 6.74</screen>
summary information in a summary accounting file, which is named
the same as the printer's accounting file, but with
<literal>_sum</literal> appended to the name. It then truncates
the accounting file. When you run <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
the accounting file. When you run &man.pac.8;
again, it rereads the summary file to get starting totals, then
adds information from the regular accounting file.</para>
@ -4768,10 +4679,9 @@ total 337.00 154 $ 6.74</screen>
<para>How do you handle other file formats, though?</para>
<para>Well, for DVI-to-LaserJet or DVI-to-PostScript conversion,
you can have your filter parse the diagnostic output of <citerefentry>
<refentrytitle>dvilj</refentrytitle></citerefentry> or
<citerefentry>
<refentrytitle>dvips</refentrytitle></citerefentry> and look to see how many pages were converted. You might be able to do similar things with other file formats and conversion programs.</para>
you can have your filter parse the diagnostic output of
<command>dvilj</command> or
<command>dvips</command> and look to see how many pages were converted. You might be able to do similar things with other file formats and conversion programs.</para>
<para>But these methods suffer from the fact that the printer may
not actually print all those pages. For example, it could jam,

16
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -372,7 +372,7 @@ Reminder - Do not use this program while logged in via telnet or rlogin.
can be used to configure restrictions on the use of UNIX passwords
based on the host name, user name, terminal port, or IP address of
a login session. The complete format of the file is documented in
the <citerefentry><refentrytitle>skey.access</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page; there are
the &man.skey.access.5; manual page; there are
also some security cautions there which should be read before
depending on this file for security.</para>
@ -1044,7 +1044,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<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,
<citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Together, they allow you to define and
&man.ipfw.8;. Together, they allow you to define and
query the rules currently used by the kernel in its routing
decisions.</para>
@ -1091,7 +1091,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Enables code to allow logging of packets through
<citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Without this option, even
&man.syslogd.8;. Without this option, even
if you specify that packets should be logged in the filter
rules, nothing will happen.</para>
</listitem>
@ -1101,7 +1101,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Limits the number of packets logged through
<citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry> on a per entry basis. You
&man.syslogd.8; on a per entry basis. You
may wish to use this option in hostile environments in
which you want to log firewall activity, but do not want
to be open to a denial of service attack via syslog
@ -1110,7 +1110,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<para>When a chain entry reaches the packet limit specified,
logging is turned off for that particular entry. To
resume logging, you will need to reset the associated
counter using the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry>
counter using the &man.ipfw.8;
utility:</para>
@ -1135,7 +1135,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<title>Configuring IPFW</title>
<para>The configuration of the <application>IPFW</application> software is
done through the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry> utility. The syntax
done through the &man.ipfw.8; utility. The syntax
for this command looks quite complicated, but it is relatively
simple once you understand its structure.</para>
@ -1443,7 +1443,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<literal>5</literal> redirect, <literal>8</literal> echo request (ping request), and
<literal>11</literal> time exceeded (used to
indicate TTL expiration as with
<citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry>).</para>
&man.traceroute.8;).</para>
</listitem>
</varlistentry>
</variablelist>
@ -1480,7 +1480,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Display the last match times for each chain entry.
The time listing is incompatible with the input syntax
used by the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry> utility.</para>
used by the &man.ipfw.8; utility.</para>
</listitem>
</varlistentry>

28
en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml
View file

@ -381,7 +381,7 @@
</itemizedlist>
<para>See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for more information.</para>
<para>See the &man.sio.4; manual page for more information.</para>
<para>If you have connected a terminal to the first serial port
(<devicename>COM1</devicename> in DOS parlance), then you want to use
@ -451,7 +451,7 @@
<replaceable>getty</replaceable> type for use in step 2 by making an
entry in <filename>/etc/gettytab</filename>. This document does
not explain how to do so; you are encouraged to see the
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> and the <citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual pages for more
man.gettytab.5; and the &man.getty.8; manual pages for more
information.</para>
<para>The remaining sections detail how to do these steps. We will
@ -463,7 +463,7 @@
port on a multiport serial card).</para>
<para>For more information on the <filename>/etc/ttys</filename>
file, see the <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page.</para>
file, see the &man.ttys.5; manual page.</para>
<sect3 id="term-etcttys">
@ -523,7 +523,7 @@ ttyd5</programlisting>
cases, the entries that start with the text <literal>std</literal> will work for hardwired terminals.
These entries ignore parity. There is a <literal>std</literal> entry for each bps rate from 110 to
115200. Of course, you can add your own entries to this file.
The manual page <citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> provides more information.</para>
The manual page &man.gettytab.5; provides more information.</para>
<para>When setting the <replaceable>getty</replaceable> type in
the <filename>/etc/ttys</filename> file, make sure that the
@ -566,7 +566,7 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
<para>To find out what terminal types FreeBSD supports, see the
file <filename>/usr/share/misc/termcap</filename>. It lists
about 600 terminal types. You can add more if you wish. See
the <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page for information.</para>
the &man.termcap.5; manual page for information.</para>
<para>In our example, the Wyse-50 is a Wyse-50 type of terminal
(although it can emulate others, we will leave it in Wyse-50
@ -1029,7 +1029,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<devicename>COM1:</devicename>, <devicename>COM2:</devicename>,
<devicename>COM3:</devicename>, and <devicename>COM4:</devicename>. FreeBSD can presently also handle
&ldquo;dumb&rdquo; multiport serial interface cards, such as the Boca Board
1008 and 2016 (please see the manual page <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for kernel configuration information
1008 and 2016 (please see the manual page &man.sio.4; for kernel configuration information
if you have a multiport serial card). The default kernel only
looks for the standard COM ports, though.</para>
@ -1089,7 +1089,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>You can comment-out or completely remove lines for devices you
do not have. If you have a multiport serial board, such as the
Boca Board BB2016, please see the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> man page for complete information on
Boca Board BB2016, please see the &man.sio.4; man page for complete information on
how to write configuration lines for multiport boards. Be careful
if you are using a configuration file that was previously used for
a different version of FreeBSD because the device flags have
@ -1112,7 +1112,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>When you are finished adjusting the kernel configuration file,
use the program <command>config</command> as documented
in &ldquo;Building Berkeley Kernels with Config&rdquo; and the
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual page to prepare a kernel
&man.config.8; manual page to prepare a kernel
building directory, then build, install, and test the new
kernel.</para>
@ -1136,7 +1136,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
modems which use <literal>CTS/RTS</literal> signaling for flow
control. The locking devices are used to lock flags on ports to
prevent users or programs changing certain parameters; see the
manual pages <citerefentry><refentrytitle>termios</refentrytitle><manvolnum>4</manvolnum></citerefentry>, <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry>, and <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
manual pages &man.termios.4;, &man.sio.4;, and &man.stty.1; for
information on the terminal settings, locking &amp; initializing
devices, and setting terminal options, respectively.</para>
@ -1146,7 +1146,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>A shell script called <command>MAKEDEV</command> in the
<filename>/dev</filename> directory manages the device special
files. (The manual page for <citerefentry><refentrytitle>MAKEDEV</refentrytitle><manvolnum>8</manvolnum></citerefentry> on
files. (The manual page for &man.MAKEDEV.8; on
FreeBSD 1.1.5 is fairly bogus in its discussion of
<acronym>COM</acronym> ports, so ignore it.) To use
<command>MAKEDEV</command> to make dialup device special files
@ -1237,9 +1237,9 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
<sect3>
<title><filename>/etc/gettytab</filename></title>
<para><filename>/etc/gettytab</filename> is a <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry>-style file of configuration
information for <citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Please see the
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page for
<para><filename>/etc/gettytab</filename> is a &man.termcap.5;-style file of configuration
information for &man.getty.8;. Please see the
&man.gettytab.5; manual page for
complete information on the format of the file and the list of
capabilities.</para>
@ -1348,7 +1348,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
information to <command>login</command> (user
<username>root</username> may only login on ttys marked
<literal>secure</literal>). See the manual page for
<citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more
&man.ttys.5; for more
information.</para>
<para>You will need to either modify existing lines in

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

@ -522,7 +522,7 @@ do-install:
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
the <citerefentry><refentrytitle>pkg_add</refentrytitle><manvolnum>1</manvolnum></citerefentry> program to install a
the &man.pkg.add.1; program to install a
package file on your system.</para>
</listitem>
@ -1170,7 +1170,7 @@ lib/X11/oneko/cat2.xpm
lib/X11/oneko/mouse.xpm
@dirrm lib/X11/oneko</programlisting>
<para>Refer to the <citerefentry><refentrytitle>pkg_create</refentrytitle><manvolnum>1</manvolnum></citerefentry> man page
<para>Refer to the &man.pkg.create.1; man page
for details on the packing list.</para>
<note>
@ -1290,19 +1290,10 @@ lib/X11/oneko/mouse.xpm
<filename>pkgname.tgz</filename> package, so delete them
now. Next, simply include the output of <command>shar `find
port_dir`</command> in a bug report and send it with the
<citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> program (see <link linkend="contrib-general">Bug
&man.send-pr.1; program (see <link linkend="contrib-general">Bug
Reports and General Commentary</link> for more information
about <citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry>. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use <citerefentry>
<refentrytitle>uuencode</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> before including it in the bug report (uuencoded
about &man.send-pr.1;. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use &man.uuencode.1; before including it in the bug report (uuencoded
tarfiles are acceptable even if the bug report is smaller than
20KB but are not preferred). Be sure to classify the bug report as
category <literal>ports</literal> and class
@ -2805,9 +2796,7 @@ diff -u -r1.15 PLIST
POST-INSTALL</literal>. <literal>&dollar;2</literal> can be
tested to determine which mode the script is being run in. The
<envar>PKG_PREFIX</envar> environmental variable will be set to
the package installation directory. See <citerefentry>
<refentrytitle>pkg_add</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> for additional
the package installation directory. See &man.pkg.add.1; for additional
information.</para>
<note>
@ -3045,7 +3034,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<command>diff -ruN superedit.bak
superedit</command>). Please examine the output to make
sure all the changes make sense. The best way to send us the
diff is by including it to <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
diff is by including it to &man.send-pr.1;
(category <literal>ports</literal>). Please mention any added or deleted files
in the message, as they have to be explicitly specified to CVS
when doing a commit. If the diff is more than about 20KB, please
@ -3053,7 +3042,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
the PR.</para>
<para>Once again, please use
<citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> and not <citerefentry><refentrytitle>shar</refentrytitle><manvolnum>1</manvolnum></citerefentry> to send updates to ports.</para>
&man.diff.1; and not &man.shar.1; to send updates to ports.</para>
</sect2>
<sect2>
@ -3080,10 +3069,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
post-install:
strip ${PREFIX}/bin/xdl</programlisting>
<para>Use the <citerefentry>
<refentrytitle>file</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> command on the installed executable to check
<para>Use the &man.file.1; command on the installed executable to check
whether the binary is stripped or not. If it does not say
<literal>not stripped</literal>, it is stripped.</para>
</sect3>
@ -3788,7 +3774,7 @@ post-install:
(executables for superusers/managers),
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
files). See man &man.hier.7; for
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use

8
en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -311,18 +311,18 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
<para>Sometimes, there is a problem with routing propagation, and
some sites are unable to connect to you. Perhaps the most useful
command for trying to figure out where a routing is breaking down
is the <citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. It is equally
is the &man.traceroute.8; command. It is equally
useful if you cannot seem to make a connection to a remote machine
(ie. <citerefentry><refentrytitle>ping</refentrytitle><manvolnum>8</manvolnum></citerefentry> fails).</para>
(i.e. &man.ping.8; fails).</para>
<para>The <citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry> command is run with the
<para>The &man.traceroute.8; command is run with the
name of the remote host you are trying to connect to. It will show
the gateway hosts along the path of the attempt, eventually either
reaching the target host, or terminating because of a lack of
connection.</para>
<para>For more information, see the manual page for
<citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
&man.traceroute.8;.</para>
</sect2>
</sect1>

201
en_US.ISO_8859-1/books/handbook/backups/chapter.sgml
View file

@ -179,14 +179,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>Use the front panel button to eject the tape.</para>
<para>Re-insert the tape and
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> data to the tape.</para>
&man.dump.8; data to the tape.</para>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> will report <literal>DUMP:
<para>&man.dump.8; will report <literal>DUMP:
End of tape detected</literal> and the console will show:
<literal>HARDWARE FAILURE info:280 asc:80,96</literal></para>
@ -200,75 +195,35 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<title>Backup Programs</title>
<para>The three major programs are
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>,
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>,
&man.dump.8;,
&man.tar.1;,
and
<citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>.</para>
&man.cpio.1;.</para>
<sect2>
<title>Dump and Restore</title>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>restore</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> are the traditional Unix backup programs. They operate
<para>&man.dump.8; and &man.restore.8; are the traditional Unix backup programs. They operate
on the drive as a collection of disk blocks, below the abstractions of
files, links and directories that are created by the filesystems.
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> backs up devices, entire filesystems, not parts of a
&man.dump.8; backs up devices, entire filesystems, not parts of a
filesystem and not directory trees that span more than one filesystem,
using either soft links <citerefentry>
<refentrytitle>ln</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> or mounting one filesystem onto another.
<citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> does not write files and directories to tape, but
using either soft links &man.ln.1; or mounting one filesystem onto another.
&man.dump.8; does not write files and directories to tape, but
rather writes the data blocks that are the building blocks of files
and directories. <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> has quirks that remain from its early days in
and directories. &man.dump.8; has quirks that remain from its early days in
Version 6 of ATT Unix (circa 1975). The default parameters are
suitable for 9-track tapes (6250 bpi), not the high-density media
available today (up to 62,182 ftpi). These defaults must be overridden
on the command line to utilize the capacity of current tape
drives.</para>
<para><citerefentry>
<refentrytitle>rdump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>rrestore</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> backup data across the
<para>&man.rdump.8; and &man.rrestore.8; backup data across the
network to a tape drive attached to another computer. Both programs
rely upon <citerefentry>
<refentrytitle>rcmd</refentrytitle>
<manvolnum>3</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>ruserok</refentrytitle>
<manvolnum>3</manvolnum></citerefentry> to access the remote tape
rely upon &man.rcmd.3; and &man.ruserok.3; to access the remote tape
drive. Therefore, the user performing the backup must have
<literal>rhosts</literal> access to the remote computer. The
arguments to <citerefentry>
<refentrytitle>rdump</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> and <citerefentry>
<refentrytitle>rrestore</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> must suitable to use on the remote computer. (e.g.
arguments to &man.rdump.8; and &man.rrestore.8; must suitable to use on the remote computer. (e.g.
When <command>rdump</command>'ing from a FreeBSD computer to an
Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000
@ -280,95 +235,52 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect2>
<title>Tar</title>
<para><citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> also dates back to Version 6 of ATT Unix (circa
1975). <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> operates in cooperation with the filesystem;
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> writes files and directories to tape.
<citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> does not support the full range of options that are
available from <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>, but <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not require the
unusual command pipeline that <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> uses.</para>
<para>&man.tar.1; also dates back to Version 6 of ATT Unix (circa
1975). &man.tar.1; operates in cooperation with the filesystem;
&man.tar.1; writes files and directories to tape.
&man.tar.1; does not support the full range of options that are
available from &man.cpio.1;, but &man.tar.1; does not require the
unusual command pipeline that &man.cpio.1; uses.</para>
<para>Most versions of <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> do not support backups across the network. The GNU
version of <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>, which FreeBSD utilizes,
<para>Most versions of &man.tar.1; do not support backups across the network. The GNU
version of &man.tar.1;, which FreeBSD utilizes,
supports remote devices using the same syntax as
<command>rdump</command>. To <citerefentry>
<refentrytitle>tar</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> to an Exabyte tape drive connected to a Sun called
komodo, use: <command>/usr/bin/tar cf komodo:/dev/nrst8 .
&man.rdump.8;. To &man.tar.1; to an Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/usr/bin/tar cf komodo:/dev/nrst8 .
2>&amp;1</command>. For versions without remote device support,
you can use a pipeline and <citerefentry>
<refentrytitle>rsh</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> to send the data to a
you can use a pipeline and &man.rsh.1; to send the data to a
remote tape drive. (XXX add an example command)</para>
</sect2>
<sect2>
<title>Cpio</title>
<para><citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> is the original Unix
file interchange tape program for magnetic media. <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> has options (among many
<para>&man.cpio.1; is the original Unix
file interchange tape program for magnetic media. &man.cpio.1; has options (among many
others) to perform byte-swapping, write a number of different
archives format, and pipe the data to other programs. This last
feature makes <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> and excellent choice for
installation media. <citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not know how to walk
feature makes &man.cpio.1; and excellent choice for
installation media. &man.cpio.1; does not know how to walk
the directory tree and a list of files must be provided thru
<filename>STDIN</filename>.</para>
<para><citerefentry>
<refentrytitle>cpio</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> does not support backups
across the network. You can use a pipeline and <citerefentry>
<refentrytitle>rsh</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> to send the data to a
<para>&man.cpio.1; does not support backups
across the network. You can use a pipeline and &man.rsh.1; to send the data to a
remote tape drive. (XXX add an example command)</para>
</sect2>
<sect2>
<title>Pax</title>
<para><citerefentry>
<refentrytitle>pax</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> is IEEE/POSIX's answer to
<command>tar</command> and <command>cpio</command>. Over the years the
various versions of <command>tar</command> and <command>cpio</command>
<para>&man.pax.1; is IEEE/POSIX's answer to
&man.tar.1; and &man.cpio.1;. Over the years the
various versions of &man.tar.1; and &man.cpio.1;
have gotten slightly incompatible. So rather than fight it out to
fully standardize them, POSIX created a new archive utility.
<command>pax</command> attempts to read and write many of the various
cpio and tar formats, plus new formats of its own. Its command set
more resembles <command>cpio</command> than
<command>tar</command>.</para>
&man.pax.1; attempts to read and write many of the various
&man.cpio.1; and &man.tar.1; formats, plus new formats of its own. Its command set
more resembles &man.cpio.1; than
&man.tar.1;.</para>
</sect2>
<sect2 id="backups-programs-amanda">
@ -422,14 +334,10 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect2>
<title>Which Backup Program is Best?</title>
<para><citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> <emphasis>Period.</emphasis>
<para>&man.dump.8; <emphasis>Period.</emphasis>
Elizabeth D. Zwicky torture tested all the backup programs discussed
here. The clear choice for preserving all your data and all the
peculiarities of Unix filesystems is <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>. Elizabeth created
peculiarities of Unix filesystems is &man.dump.8;. Elizabeth created
filesystems containing a large variety of unusual conditions (and some
not so unusual ones) and tested each program by do a backup and
restore of that filesystems. The peculiarities included: files with
@ -465,22 +373,10 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>Otherwise, you have to create two custom bootable floppies
which has a kernel that can mount your all of your disks and
access your tape drive. These floppies must contain:
<citerefentry>
<refentrytitle>fdisk</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>disklabel</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>newfs</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
<refentrytitle>mount</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, and whichever backup
&man.fdisk.8;, &man.disklabel.8;, &man.newfs.8;, &man.mount.8;, and whichever backup
program you use. These programs must be statically linked. If you
use <citerefentry>
<refentrytitle>dump</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, the floppy must contain
<citerefentry>
<refentrytitle>restore</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>.</para>
use &man.dump.8;, the floppy must contain
&man.restore.8;.</para>
<para>Third, create backup tapes regularly. Any changes that you make
after your last backup may be irretrievably lost. Write-protect the
@ -686,18 +582,11 @@ chmod 644 /mnt/etc/passwd
<para>Recover each filesystem separately.</para>
<para>Try to <citerefentry>
<refentrytitle>mount</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry>(e.g. <command>mount /dev/sd0a
<para>Try to &man.mount.8; (e.g. <command>mount /dev/sd0a
/mnt</command>) the root partition of your first disk. If the
disklabel was damaged, use <citerefentry>
<refentrytitle>disklabel</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> to re-partition and
disklabel was damaged, use &man.disklabel.8; to re-partition and
label the disk to match the label that your printed and saved. Use
<citerefentry>
<refentrytitle>newfs</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> to re-create the
&man.newfs.8; to re-create the
filesystems. Re-mount the root partition of the floppy read-write
(<command>mount -u -o rw /mnt</command>). Use your backup program
and backup tapes to recover the data for this filesystem (e.g.

6
en_US.ISO_8859-1/books/handbook/basics/chapter.sgml
View file

@ -76,9 +76,9 @@
<para>This will display the manual page for the user
command <command>chmod</command>. References to a
particular section of the on-line manual are traditionally placed in
parenthesis in written documentation, so <citerefentry><refentrytitle>chmod</refentrytitle><manvolnum>1</manvolnum></citerefentry> refers to the
parenthesis in written documentation, so &man.chmod.1; refers to the
<command>chmod</command>
user command and <citerefentry><refentrytitle>chmod</refentrytitle><manvolnum>2</manvolnum></citerefentry> refers to the
user command and &man.chmod.2; refers to the
system call.</para>
<para>This is fine if you know the name of the command and simply wish
@ -122,7 +122,7 @@
<command>info</command> command or, if you installed
<command>emacs</command>, the info mode of <command>emacs</command>.</para>
<para>To use the <citerefentry><refentrytitle>info</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, simply type:</para>
<para>To use the &man.info.1; command, simply type:</para>
<screen>&prompt.user; <userinput>info</userinput></screen>

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

@ -1,6 +1,9 @@
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.0-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
<!ENTITY % authors SYSTEM "authors.ent"> %authors;
<!ENTITY % authors SYSTEM "authors.ent"> %authors;
<!ENTITY % mailing-lists SYSTEM "mailing-lists.ent"> %mailing-lists;
<!ENTITY % newsgroups SYSTEM "newsgroups.ent"> %newsgroups;

224
en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml
View file

@ -458,12 +458,12 @@
information about this and other mailing lists.</para>
<para>If you find a bug or are submitting a specific change, please
report it using the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>program or its
report it using the &man.send-pr.1; program or its
<ulink URL="http://www.freebsd.org/send-pr.html">WEB-based
equivalent</ulink>. Try to fill-in each field of the bug report.
Unless they exceed 65KB, include any patches directly in the
report. Consider compressing them and using
<citerefentry><refentrytitle>uuencode</refentrytitle><manvolnum>1</manvolnum></citerefentry> if they exceed 20KB. Upload very large submissions to <ulink url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp.freebsd.org:/pub/FreeBSD/incoming/</ulink>.</para>
&man.uuencode.1; if they exceed 20KB. Upload very large submissions to <ulink url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp.freebsd.org:/pub/FreeBSD/incoming/</ulink>.</para>
<para>After filing a report, you should receive confirmation along
with a tracking number. Keep this tracking number so that you can
@ -471,7 +471,7 @@
<para>If you do not receive confirmation in a timely fashion (3 days
to a week, depending on your email connection) or are, for some
reason, unable to use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> command,
reason, unable to use the &man.send-pr.1; command,
then you may ask someone to file it for you by sending mail to the
&a.bugs;.</para>
@ -511,7 +511,7 @@
<para>Assuming that you can manage to secure fairly up-to-date
sources to base your changes on, the next step is to produce a set
of diffs to send to the FreeBSD maintainers. This is done with
the <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, with the &ldquo;context diff&rdquo;
the &man.diff.1; command, with the &ldquo;context diff&rdquo;
form being preferred. For example:</para>
<para>
@ -526,11 +526,11 @@
would generate such a set of context diffs for
the given source file or directory hierarchy. See the man page
for <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> for more details.</para>
for &man.diff.1; for more details.</para>
<para>Once you have a set of diffs (which you may test with the
<citerefentry><refentrytitle>patch</refentrytitle><manvolnum>1</manvolnum></citerefentry> command), you should submit them for
inclusion with FreeBSD. Use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
&man.patch.1; command), you should submit them for
inclusion with FreeBSD. Use the &man.send-pr.1;
program as described in
<link linkend="contrib-general">Bug Reports and General
Commentary</link>. <emphasis>Do not</emphasis> just send the diffs to
@ -541,14 +541,14 @@
<para>If you feel it appropriate (e.g. you have added, deleted, or
renamed files), bundle your changes into a <command>tar</command> file and run the
<citerefentry><refentrytitle>uuencode</refentrytitle><manvolnum>1</manvolnum></citerefentry> program on it. Shar archives are
&man.uuencode.1; program on it. Shar archives are
also welcome.</para>
<para>If your change is of a potentially sensitive nature, e.g. you
are unsure of copyright issues governing its further distribution
or you are simply not ready to release it without a tighter review
first, then you should send it to &a.core; directly rather than
submitting it with <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The core
submitting it with &man.send-pr.1;. The core
mailing list reaches a much smaller group of people who do much of
the day-to-day work on FreeBSD. Note that this group is also
<emphasis>very busy</emphasis> and so you should only send mail to
@ -1143,9 +1143,9 @@ box can be opened)</para>
<listitem><para>Adrian Mariano <email>adrian@cam.cornell.edu</email></para></listitem>
<listitem><para>Adrian Steinmann <email>ast@marabu.ch</email></para></listitem>
<listitem><para>Adrian T. Filipi-Martin <email>atf3r@agate.cs.virginia.edu</email></para></listitem>
<listitem><para>Ajit Thyagarajan</para></listitem>
<listitem><para>Ajit Thyagarajan <email>unknown</email></para></listitem>
<listitem><para>Akio Morita <email>amorita@meadow.scphys.kyoto-u.ac.jp</email></para></listitem>
<listitem><para>Akira SAWADA</para></listitem>
<listitem><para>Akira SAWADA <email>unknown</email></para></listitem>
<listitem><para>Akira Watanabe <email>akira@myaw.ei.meisei-u.ac.jp</email></para></listitem>
<listitem><para>Akito Fujita <email>fujita@zoo.ncl.omron.co.jp</email></para></listitem>
<listitem><para>Alain Kalker <email>A.C.P.M.Kalker@student.utwente.nl</email></para></listitem>
@ -1177,10 +1177,10 @@ box can be opened)</para>
<listitem><para>Andreas Haakh <email>ah@alman.robin.de</email></para></listitem>
<listitem><para>Andreas Kohout <email>shanee@rabbit.augusta.de</email></para></listitem>
<listitem><para>Andreas Lohr <email>andreas@marvin.RoBIN.de</email></para></listitem>
<listitem><para>Andreas Schulz</para></listitem>
<listitem><para>Andreas Schulz <email>unknown</email></para></listitem>
<listitem><para>Andreas Wetzel <email>mickey@deadline.snafu.de</email></para></listitem>
<listitem><para>Andreas Wrede <email>andreas@planix.com</email></para></listitem>
<listitem><para>Andres Vega Garcia</para></listitem>
<listitem><para>Andres Vega Garcia <email>unknown</email></para></listitem>
<listitem><para>Andrew Atrens <email>atreand@statcan.ca</email></para></listitem>
<listitem><para>Andrew Gillham <email>gillham@andrews.edu</email></para></listitem>
<listitem><para>Andrew Gordon <email>andrew.gordon@net-tel.co.uk</email></para></listitem>
@ -1212,7 +1212,7 @@ box can be opened)</para>
<listitem><para>Barry Bierbauch <email>pivrnec@vszbr.cz</email></para></listitem>
<listitem><para>Barry Lustig <email>barry@ictv.com</email></para></listitem>
<listitem><para>Ben Hutchinson <email>benhutch@xfiles.org.uk</email></para></listitem>
<listitem><para>Ben Jackson</para></listitem>
<listitem><para>Ben Jackson <email>unknown</email></para></listitem>
<listitem><para>Ben Smithurst <email>ben@scientia.demon.co.uk</email></para></listitem>
<listitem><para>Ben Walter <email>bwalter@itachi.swcp.com</email></para></listitem>
<listitem><para>Benjamin Lewis <email>bhlewis@gte.net</email></para></listitem>
@ -1264,7 +1264,7 @@ box can be opened)</para>
<listitem><para>Chet Ramey <email>chet@odin.INS.CWRU.Edu</email></para></listitem>
<listitem><para>Chia-liang Kao <email>clkao@CirX.ORG</email></para></listitem>
<listitem><para>Chiharu Shibata <email>chi@bd.mbn.or.jp</email></para></listitem>
<listitem><para>Chip Norkus</para></listitem>
<listitem><para>Chip Norkus <email>unknown</email></para></listitem>
<listitem><para>Choi Jun Ho <email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para>Chris Csanady <email>cc@tarsier.ca.sandia.gov</email></para></listitem>
<listitem><para>Chris Dabrowski <email>chris@vader.org</email></para></listitem>
@ -1291,7 +1291,7 @@ box can be opened)</para>
<listitem><para>Cornelis van der Laan <email>nils@guru.ims.uni-stuttgart.de</email></para></listitem>
<listitem><para>Cove Schneider <email>cove@brazil.nbn.com</email></para></listitem>
<listitem><para>Craig Leres <email>leres@ee.lbl.gov</email></para></listitem>
<listitem><para>Craig Loomis</para></listitem>
<listitem><para>Craig Loomis <email>unknown</email></para></listitem>
<listitem><para>Craig Metz <email>cmetz@inner.net</email></para></listitem>
<listitem><para>Craig Spannring <email>cts@internetcds.com</email></para></listitem>
<listitem><para>Craig Struble <email>cstruble@vt.edu</email></para></listitem>
@ -1310,7 +1310,7 @@ box can be opened)</para>
<listitem><para>Daniel O'Connor <email>doconnor@gsoft.com.au</email></para></listitem>
<listitem><para>Daniel Poirot <email>poirot@aio.jsc.nasa.gov</email></para></listitem>
<listitem><para>Daniel Rock <email>rock@cs.uni-sb.de</email></para></listitem>
<listitem><para>Danny Egen</para></listitem>
<listitem><para>Danny Egen <email>unknown</email></para></listitem>
<listitem><para>Danny J. Zerkel <email>dzerkel@phofarm.com</email></para></listitem>
<listitem><para>Darren Reed <email>avalon@coombs.anu.edu.au</email></para></listitem>
<listitem><para>Dave Adkins <email>adkin003@tc.umn.edu</email></para></listitem>
@ -1344,7 +1344,7 @@ box can be opened)</para>
<listitem><para>David Wolfskill <email>dhw@whistle.com</email></para></listitem>
<listitem><para>Dean Gaudet <email>dgaudet@arctic.org</email></para></listitem>
<listitem><para>Dean Huxley <email>dean@fsa.ca</email></para></listitem>
<listitem><para>Denis Fortin</para></listitem>
<listitem><para>Denis Fortin <email>unknown</email></para></listitem>
<listitem><para>Dennis Glatting <email>dennis.glatting@software-munitions.com</email></para></listitem>
<listitem><para>Denton Gentry <email>denny1@home.com</email></para></listitem>
<listitem><para>Derek Inksetter <email>derek@saidev.com</email></para></listitem>
@ -1450,7 +1450,7 @@ box can be opened)</para>
<listitem><para>Harold Barker <email>hbarker@dsms.com</email></para></listitem>
<listitem><para>Havard Eidnes <email>Havard.Eidnes@runit.sintef.no</email></para></listitem>
<listitem><para>Heikki Suonsivu <email>hsu@cs.hut.fi</email></para></listitem>
<listitem><para>Heiko W. Rupp</para></listitem>
<listitem><para>Heiko W. Rupp <email>unknown</email></para></listitem>
<listitem><para>Helmut F. Wirth <email>hfwirth@ping.at</email></para></listitem>
<listitem><para>Henrik Vestergaard Draboel <email>hvd@terry.ping.dk</email></para></listitem>
<listitem><para>Herb Peyerl <email>hpeyerl@NetBSD.org</email></para></listitem>
@ -1464,7 +1464,7 @@ box can be opened)</para>
<listitem><para>Hiroharu Tamaru <email>tamaru@ap.t.u-tokyo.ac.jp</email></para></listitem>
<listitem><para>Hironori Ikura <email>hikura@kaisei.org</email></para></listitem>
<listitem><para>Hiroshi Nishikawa <email>nis@pluto.dti.ne.jp</email></para></listitem>
<listitem><para>Hiroya Tsubakimoto</para></listitem>
<listitem><para>Hiroya Tsubakimoto <email>unknown</email></para></listitem>
<listitem><para>Hiroyuki NAKAJI <email>nakaji@zeisei3.dpri.kyoto-u.ac.jp</email></para></listitem>
<listitem><para>Holger Veit <email>Holger.Veit@gmd.de</email></para></listitem>
<listitem><para>Holm Tiffe <email>holm@geophysik.tu-freiberg.de</email></para></listitem>
@ -1527,7 +1527,7 @@ box can be opened)</para>
<listitem><para>Jeremy Allison <email>jallison@whistle.com</email></para></listitem>
<listitem><para>Jeremy Chatfield <email>jdc@xinside.com</email></para></listitem>
<listitem><para>Jeremy Lea <email>reg@shale.csir.co.za</email></para></listitem>
<listitem><para>Jeremy Prior</para></listitem>
<listitem><para>Jeremy Prior <email>unknown</email></para></listitem>
<listitem><para>Jeroen Ruigrok/Asmodai <email>asmodai@wxs.nl</email></para></listitem>
<listitem><para>Jesse Rosenstock <email>jmr@ugcs.caltech.edu</email></para></listitem>
<listitem><para>Jian-Da Li <email>jdli@csie.nctu.edu.tw</email></para></listitem>
@ -1543,7 +1543,7 @@ box can be opened)</para>
<listitem><para>Jim Wilson <email>wilson@moria.cygnus.com</email></para></listitem>
<listitem><para>Jimbo Bahooli <email>griffin@blackhole.iceworld.org</email></para></listitem>
<listitem><para>Jin Guojun <email>jin@george.lbl.gov</email></para></listitem>
<listitem><para>Joachim Kuebart</para></listitem>
<listitem><para>Joachim Kuebart <email>unknown</email></para></listitem>
<listitem><para>Joao Carlos Mendes Luis <email>jonny@jonny.eng.br</email></para></listitem>
<listitem><para>Jochen Pohl <email>jpo.drs@sni.de</email></para></listitem>
<listitem><para>Joe "Marcus" Clarke <email>marcus@miami.edu</email></para></listitem>
@ -1558,19 +1558,19 @@ box can be opened)</para>
<listitem><para>Johan Karlsson <email>k@numeri.campus.luth.se</email></para></listitem>
<listitem><para>Johan Larsson <email>johan@moon.campus.luth.se</email></para></listitem>
<listitem><para>Johann Tonsing <email>jtonsing@mikom.csir.co.za</email></para></listitem>
<listitem><para>Johannes Helander</para></listitem>
<listitem><para>Johannes Stille</para></listitem>
<listitem><para>Johannes Helander <email>unknown</email></para></listitem>
<listitem><para>Johannes Stille <email>unknown</email></para></listitem>
<listitem><para>John Baldwin <email>jobaldwi@vt.edu</email></para></listitem>
<listitem><para>John Beckett <email>jbeckett@southern.edu</email></para></listitem>
<listitem><para>John Beukema <email>jbeukema@hk.super.net</email></para></listitem>
<listitem><para>John Brezak</para></listitem>
<listitem><para>John Brezak <email>unknown</email></para></listitem>
<listitem><para>John Capo <email>jc@irbs.com</email></para></listitem>
<listitem><para>John F. Woods <email>jfw@jfwhome.funhouse.com</email></para></listitem>
<listitem><para>John Goerzen <email>jgoerzen@alexanderwohl.complete.org</email></para></listitem>
<listitem><para>John Hay <email>jhay@mikom.csir.co.za</email></para></listitem>
<listitem><para>John Heidemann <email>johnh@isi.edu</email></para></listitem>
<listitem><para>John Hood <email>cgull@owl.org</email></para></listitem>
<listitem><para>John Kohl</para></listitem>
<listitem><para>John Kohl <email>unknown</email></para></listitem>
<listitem><para>John Lind <email>john@starfire.mn.org</email></para></listitem>
<listitem><para>John Mackin <email>john@physiol.su.oz.au</email></para></listitem>
<listitem><para>John P <email>johnp@lodgenet.com</email></para></listitem>
@ -1620,10 +1620,10 @@ box can be opened)</para>
<listitem><para>Kazuo Horikawa <email>horikawa@jp.FreeBSD.org</email></para></listitem>
<listitem><para>Kees Jan Koster <email>kjk1@ukc.ac.uk</email></para></listitem>
<listitem><para>Keith Bostic <email>bostic@bostic.com</email></para></listitem>
<listitem><para>Keith E. Walker</para></listitem>
<listitem><para>Keith Moore</para></listitem>
<listitem><para>Keith Sklower</para></listitem>
<listitem><para>Ken Hornstein</para></listitem>
<listitem><para>Keith E. Walker <email>unknown</email></para></listitem>
<listitem><para>Keith Moore <email>unknown</email></para></listitem>
<listitem><para>Keith Sklower <email>unknown</email></para></listitem>
<listitem><para>Ken Hornstein <email>unknown</email></para></listitem>
<listitem><para>Ken Key <email>key@cs.utk.edu</email></para></listitem>
<listitem><para>Ken Mayer <email>kmayer@freegate.com</email></para></listitem>
<listitem><para>Kenji Saito <email>marukun@mx2.nisiq.net</email></para></listitem>
@ -1659,7 +1659,7 @@ box can be opened)</para>
<listitem><para>Louis Mamakos <email>loiue@TransSys.com</email></para></listitem>
<listitem><para>Lucas James <email>Lucas.James@ldjpc.apana.org.au</email></para></listitem>
<listitem><para>Lyndon Nerenberg <email>lyndon@orthanc.com</email></para></listitem>
<listitem><para>M.C. Wong</para></listitem>
<listitem><para>M.C. Wong <email>unknown</email></para></listitem>
<listitem><para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para></listitem>
<listitem><para>MIHIRA Sanpei Yoshiro <email>sanpei@sanpei.org</email></para></listitem>
<listitem><para>MITA Yoshio <email>mita@jp.FreeBSD.ORG</email></para></listitem>
@ -1677,7 +1677,7 @@ box can be opened)</para>
<listitem><para>Marc van Kempen <email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para>Marcel Moolenaar <email>marcel@scc.nl</email></para></listitem>
<listitem><para>Mario Sergio Fujikawa Ferreira <email>lioux@gns.com.br</email></para></listitem>
<listitem><para>Mark Andrews</para></listitem>
<listitem><para>Mark Andrews <email>unknown</email></para></listitem>
<listitem><para>Mark Cammidge <email>mark@gmtunx.ee.uct.ac.za</email></para></listitem>
<listitem><para>Mark Diekhans <email>markd@grizzly.com</email></para></listitem>
<listitem><para>Mark Huizer <email>xaa@stack.nl</email></para></listitem>
@ -1686,7 +1686,7 @@ box can be opened)</para>
<listitem><para>Mark Mayo <email>markm@vmunix.com</email></para></listitem>
<listitem><para>Mark Thompson <email>thompson@tgsoft.com</email></para></listitem>
<listitem><para>Mark Tinguely <email>tinguely@plains.nodak.edu</email></para></listitem>
<listitem><para>Mark Treacy</para></listitem>
<listitem><para>Mark Treacy <email>unknown</email></para></listitem>
<listitem><para>Mark Valentine <email>mark@linus.demon.co.uk</email></para></listitem>
<listitem><para>Martin Birgmeier</para></listitem>
<listitem><para>Martin Ibert <email>mib@ppe.bb-data.de</email></para></listitem>
@ -1694,7 +1694,7 @@ box can be opened)</para>
<listitem><para>Martin Renters <email>martin@tdc.on.ca</email></para></listitem>
<listitem><para>Martti Kuparinen <email>erakupa@kk.etx.ericsson.se</email></para></listitem>
<listitem><para>Masachika ISHIZUKA <email>ishizuka@isis.min.ntt.jp</email></para></listitem>
<listitem><para>Mas.TAKEMURA</para></listitem>
<listitem><para>Mas.TAKEMURA <email>unknown</email></para></listitem>
<listitem><para>Masafumi NAKANE <email>max@wide.ad.jp</email></para></listitem>
<listitem><para>Masahiro Sekiguchi <email>seki@sysrap.cs.fujitsu.co.jp</email></para></listitem>
<listitem><para>Masanobu Saitoh <email>msaitoh@spa.is.uec.ac.jp</email></para></listitem>
@ -1745,7 +1745,7 @@ box can be opened)</para>
<listitem><para>Mike Evans <email>mevans@candle.com</email></para></listitem>
<listitem><para>Mike Grupenhoff <email>kashmir@umiacs.umd.edu</email></para></listitem>
<listitem><para>Mike Hibler <email>mike@marker.cs.utah.edu</email></para></listitem>
<listitem><para>Mike Karels</para></listitem>
<listitem><para>Mike Karels <email>unknown</email></para></listitem>
<listitem><para>Mike McGaughey <email>mmcg@cs.monash.edu.au</email></para></listitem>
<listitem><para>Mike Meyer <email>mwm@shiva.the-park.com</email></para></listitem>
<listitem><para>Mike Mitchell <email>mitchell@ref.tfs.com</email></para></listitem>
@ -1787,71 +1787,71 @@ box can be opened)</para>
<listitem><para>Nickolay N. Dudorov <email>nnd@itfs.nsk.su</email></para></listitem>
<listitem><para>Niklas Hallqvist <email>niklas@filippa.appli.se</email></para></listitem>
<listitem><para>Nisha Talagala <email>nisha@cs.berkeley.edu</email></para></listitem>
<listitem><para><email>ZW6T-KND@j.asahi-net.or.jp</email></para></listitem>
<listitem><para><email>adrian@virginia.edu</email></para></listitem>
<listitem><para><email>alex@elvisti.kiev.ua</email></para></listitem>
<listitem><para><email>anto@netscape.net</email></para></listitem>
<listitem><para><email>bobson@egg.ics.nitch.ac.jp</email></para></listitem>
<listitem><para><email>bovynf@awe.be</email></para></listitem>
<listitem><para><email>burg@is.ge.com</email></para></listitem>
<listitem><para><email>chris@gnome.co.uk</email></para></listitem>
<listitem><para><email>colsen@usa.net</email></para></listitem>
<listitem><para><email>coredump@nervosa.com</email></para></listitem>
<listitem><para><email>dannyman@arh0300.urh.uiuc.edu</email></para></listitem>
<listitem><para><email>davids@SECNET.COM</email></para></listitem>
<listitem><para><email>derek@free.org</email></para></listitem>
<listitem><para><email>devet@adv.IAEhv.nl</email></para></listitem>
<listitem><para><email>djv@bedford.net</email></para></listitem>
<listitem><para><email>dvv@sprint.net</email></para></listitem>
<listitem><para><email>enami@ba2.so-net.or.jp</email></para></listitem>
<listitem><para><email>flash@eru.tubank.msk.su</email></para></listitem>
<listitem><para><email>flash@hway.ru</email></para></listitem>
<listitem><para><email>fn@pain.csrv.uidaho.edu</email></para></listitem>
<listitem><para><email>gclarkii@netport.neosoft.com</email></para></listitem>
<listitem><para><email>gordon@sheaky.lonestar.org</email></para></listitem>
<listitem><para><email>graaf@iae.nl</email></para></listitem>
<listitem><para><email>greg@greg.rim.or.jp</email></para></listitem>
<listitem><para><email>grossman@cygnus.com</email></para></listitem>
<listitem><para><email>gusw@fub46.zedat.fu-berlin.de</email></para></listitem>
<listitem><para><email>hfir@math.rochester.edu</email></para></listitem>
<listitem><para><email>hnokubi@yyy.or.jp</email></para></listitem>
<listitem><para><email>iaint@css.tuu.utas.edu.au</email></para></listitem>
<listitem><para><email>invis@visi.com</email></para></listitem>
<listitem><para><email>ishisone@sra.co.jp</email></para></listitem>
<listitem><para><email>iverson@lionheart.com</email></para></listitem>
<listitem><para><email>jpt@magic.net</email></para></listitem>
<listitem><para><email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para><email>k-sugyou@ccs.mt.nec.co.jp</email></para></listitem>
<listitem><para><email>kenji@reseau.toyonaka.osaka.jp</email></para></listitem>
<listitem><para><email>kfurge@worldnet.att.net</email></para></listitem>
<listitem><para><email>lh@aus.org</email></para></listitem>
<listitem><para><email>lhecking@nmrc.ucc.ie</email></para></listitem>
<listitem><para><email>mrgreen@mame.mu.oz.au</email></para></listitem>
<listitem><para><email>nakagawa@jp.freebsd.org</email></para></listitem>
<listitem><para><email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para></listitem>
<listitem><para><email>owaki@st.rim.or.jp</email></para></listitem>
<listitem><para><email>pechter@shell.monmouth.com</email></para></listitem>
<listitem><para><email>pete@pelican.pelican.com</email></para></listitem>
<listitem><para><email>pritc003@maroon.tc.umn.edu</email></para></listitem>
<listitem><para><email>risner@stdio.com</email></para></listitem>
<listitem><para><email>roman@rpd.univ.kiev.ua</email></para></listitem>
<listitem><para><email>root@ns2.redline.ru</email></para></listitem>
<listitem><para><email>root@uglabgw.ug.cs.sunysb.edu</email></para></listitem>
<listitem><para><email>stephen.ma@jtec.com.au</email></para></listitem>
<listitem><para><email>sumii@is.s.u-tokyo.ac.jp</email></para></listitem>
<listitem><para><email>takas-su@is.aist-nara.ac.jp</email></para></listitem>
<listitem><para><email>tamone@eig.unige.ch</email></para></listitem>
<listitem><para><email>tjevans@raleigh.ibm.com</email></para></listitem>
<listitem><para><email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para></listitem>
<listitem><para><email>torii@tcd.hitachi.co.jp</email></para></listitem>
<listitem><para><email>uenami@imasy.or.jp</email></para></listitem>
<listitem><para><email>uhlar@netlab.sk</email></para></listitem>
<listitem><para><email>vode@hut.fi</email></para></listitem>
<listitem><para><email>wlloyd@mpd.ca</email></para></listitem>
<listitem><para><email>wlr@furball.wellsfargo.com</email></para></listitem>
<listitem><para><email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para><email>yamagata@nwgpc.kek.jp</email></para></listitem>
<listitem><para><email>ziggy@ryan.org</email></para></listitem>
<listitem><para>No Name <email>ZW6T-KND@j.asahi-net.or.jp</email></para></listitem>
<listitem><para>No Name <email>adrian@virginia.edu</email></para></listitem>
<listitem><para>No Name <email>alex@elvisti.kiev.ua</email></para></listitem>
<listitem><para>No Name <email>anto@netscape.net</email></para></listitem>
<listitem><para>No Name <email>bobson@egg.ics.nitch.ac.jp</email></para></listitem>
<listitem><para>No Name <email>bovynf@awe.be</email></para></listitem>
<listitem><para>No Name <email>burg@is.ge.com</email></para></listitem>
<listitem><para>No Name <email>chris@gnome.co.uk</email></para></listitem>
<listitem><para>No Name <email>colsen@usa.net</email></para></listitem>
<listitem><para>No Name <email>coredump@nervosa.com</email></para></listitem>
<listitem><para>No Name <email>dannyman@arh0300.urh.uiuc.edu</email></para></listitem>
<listitem><para>No Name <email>davids@SECNET.COM</email></para></listitem>
<listitem><para>No Name <email>derek@free.org</email></para></listitem>
<listitem><para>No Name <email>devet@adv.IAEhv.nl</email></para></listitem>
<listitem><para>No Name <email>djv@bedford.net</email></para></listitem>
<listitem><para>No Name <email>dvv@sprint.net</email></para></listitem>
<listitem><para>No Name <email>enami@ba2.so-net.or.jp</email></para></listitem>
<listitem><para>No Name <email>flash@eru.tubank.msk.su</email></para></listitem>
<listitem><para>No Name <email>flash@hway.ru</email></para></listitem>
<listitem><para>No Name <email>fn@pain.csrv.uidaho.edu</email></para></listitem>
<listitem><para>No Name <email>gclarkii@netport.neosoft.com</email></para></listitem>
<listitem><para>No Name <email>gordon@sheaky.lonestar.org</email></para></listitem>
<listitem><para>No Name <email>graaf@iae.nl</email></para></listitem>
<listitem><para>No Name <email>greg@greg.rim.or.jp</email></para></listitem>
<listitem><para>No Name <email>grossman@cygnus.com</email></para></listitem>
<listitem><para>No Name <email>gusw@fub46.zedat.fu-berlin.de</email></para></listitem>
<listitem><para>No Name <email>hfir@math.rochester.edu</email></para></listitem>
<listitem><para>No Name <email>hnokubi@yyy.or.jp</email></para></listitem>
<listitem><para>No Name <email>iaint@css.tuu.utas.edu.au</email></para></listitem>
<listitem><para>No Name <email>invis@visi.com</email></para></listitem>
<listitem><para>No Name <email>ishisone@sra.co.jp</email></para></listitem>
<listitem><para>No Name <email>iverson@lionheart.com</email></para></listitem>
<listitem><para>No Name <email>jpt@magic.net</email></para></listitem>
<listitem><para>No Name <email>junker@jazz.snu.ac.kr</email></para></listitem>
<listitem><para>No Name <email>k-sugyou@ccs.mt.nec.co.jp</email></para></listitem>
<listitem><para>No Name <email>kenji@reseau.toyonaka.osaka.jp</email></para></listitem>
<listitem><para>No Name <email>kfurge@worldnet.att.net</email></para></listitem>
<listitem><para>No Name <email>lh@aus.org</email></para></listitem>
<listitem><para>No Name <email>lhecking@nmrc.ucc.ie</email></para></listitem>
<listitem><para>No Name <email>mrgreen@mame.mu.oz.au</email></para></listitem>
<listitem><para>No Name <email>nakagawa@jp.freebsd.org</email></para></listitem>
<listitem><para>No Name <email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para></listitem>
<listitem><para>No Name <email>owaki@st.rim.or.jp</email></para></listitem>
<listitem><para>No Name <email>pechter@shell.monmouth.com</email></para></listitem>
<listitem><para>No Name <email>pete@pelican.pelican.com</email></para></listitem>
<listitem><para>No Name <email>pritc003@maroon.tc.umn.edu</email></para></listitem>
<listitem><para>No Name <email>risner@stdio.com</email></para></listitem>
<listitem><para>No Name <email>roman@rpd.univ.kiev.ua</email></para></listitem>
<listitem><para>No Name <email>root@ns2.redline.ru</email></para></listitem>
<listitem><para>No Name <email>root@uglabgw.ug.cs.sunysb.edu</email></para></listitem>
<listitem><para>No Name <email>stephen.ma@jtec.com.au</email></para></listitem>
<listitem><para>No Name <email>sumii@is.s.u-tokyo.ac.jp</email></para></listitem>
<listitem><para>No Name <email>takas-su@is.aist-nara.ac.jp</email></para></listitem>
<listitem><para>No Name <email>tamone@eig.unige.ch</email></para></listitem>
<listitem><para>No Name <email>tjevans@raleigh.ibm.com</email></para></listitem>
<listitem><para>No Name <email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para></listitem>
<listitem><para>No Name <email>torii@tcd.hitachi.co.jp</email></para></listitem>
<listitem><para>No Name <email>uenami@imasy.or.jp</email></para></listitem>
<listitem><para>No Name <email>uhlar@netlab.sk</email></para></listitem>
<listitem><para>No Name <email>vode@hut.fi</email></para></listitem>
<listitem><para>No Name <email>wlloyd@mpd.ca</email></para></listitem>
<listitem><para>No Name <email>wlr@furball.wellsfargo.com</email></para></listitem>
<listitem><para>No Name <email>wmbfmk@urc.tue.nl</email></para></listitem>
<listitem><para>No Name <email>yamagata@nwgpc.kek.jp</email></para></listitem>
<listitem><para>No Name <email>ziggy@ryan.org</email></para></listitem>
<listitem><para>Nobuhiro Yasutomi <email>nobu@psrc.isac.co.jp</email></para></listitem>
<listitem><para>Nobuyuki Koganemaru <email>kogane@koganemaru.co.jp</email></para></listitem>
<listitem><para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para></listitem>
@ -1873,15 +1873,15 @@ box can be opened)</para>
<listitem><para>Pascal Pederiva <email>pascal@zuo.dec.com</email></para></listitem>
<listitem><para>Pasvorn Boonmark <email>boonmark@juniper.net</email></para></listitem>
<listitem><para>Patrick Gardella <email>patrick@cre8tivegroup.com</email></para></listitem>
<listitem><para>Patrick Hausen</para></listitem>
<listitem><para>Patrick Hausen <email>unknown</email></para></listitem>
<listitem><para>Paul Antonov <email>apg@demos.su</email></para></listitem>
<listitem><para>Paul F. Werkowski</para></listitem>
<listitem><para>Paul F. Werkowski <email>unknown</email></para></listitem>
<listitem><para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para></listitem>
<listitem><para>Paul Koch <email>koch@thehub.com.au</email></para></listitem>
<listitem><para>Paul Kranenburg <email>pk@NetBSD.org</email></para></listitem>
<listitem><para>Paul Mackerras <email>paulus@cs.anu.edu.au</email></para></listitem>
<listitem><para>Paul Popelka <email>paulp@uts.amdahl.com</email></para></listitem>
<listitem><para>Paul S. LaFollette, Jr.</para></listitem>
<listitem><para>Paul S. LaFollette, Jr. <email>unknown</email></para></listitem>
<listitem><para>Paul Saab <email>paul@mu.org</email></para></listitem>
<listitem><para>Paul Sandys <email>myj@nyct.net</email></para></listitem>
<listitem><para>Paul T. Root <email>proot@horton.iaces.com</email></para></listitem>
@ -1897,7 +1897,7 @@ box can be opened)</para>
<listitem><para>Peter Jeremy <email>perer.jeremy@alcatel.com.au</email></para></listitem>
<listitem><para>Peter M. Chen <email>pmchen@eecs.umich.edu</email></para></listitem>
<listitem><para>Peter Much <email>peter@citylink.dinoex.sub.org</email></para></listitem>
<listitem><para>Peter Olsson</para></listitem>
<listitem><para>Peter Olsson <email>unknown</email></para></listitem>
<listitem><para>Peter Philipp <email>pjp@bsd-daemon.net</email></para></listitem>
<listitem><para>Peter Stubbs <email>PETERS@staidan.qld.edu.au</email></para></listitem>
<listitem><para>Phil Maker <email>pjm@cs.ntu.edu.au</email></para></listitem>
@ -1930,7 +1930,7 @@ box can be opened)</para>
<listitem><para>Richard Winkel <email>rich@math.missouri.edu</email></para></listitem>
<listitem><para>Richard Wiwatowski <email>rjwiwat@adelaide.on.net</email></para></listitem>
<listitem><para>Rick Macklem <email>rick@snowhite.cis.uoguelph.ca</email></para></listitem>
<listitem><para>Rick Macklin</para></listitem>
<listitem><para>Rick Macklin <email>unknown</email></para></listitem>
<listitem><para>Rob Austein <email>sra@epilogue.com</email></para></listitem>
<listitem><para>Rob Mallory <email>rmallory@qualcomm.com</email></para></listitem>
<listitem><para>Rob Snow <email>rsnow@txdirect.net</email></para></listitem>
@ -1943,14 +1943,14 @@ box can be opened)</para>
<listitem><para>Robert Swindells <email>swindellsr@genrad.co.uk</email></para></listitem>
<listitem><para>Robert Watson <email>robert@cyrus.watson.org</email></para></listitem>
<listitem><para>Robert Withrow <email>witr@rwwa.com</email></para></listitem>
<listitem><para>Robert Yoder</para></listitem>
<listitem><para>Robert Yoder <email>unknown</email></para></listitem>
<listitem><para>Robin Carey <email>robin@mailgate.dtc.rankxerox.co.uk</email></para></listitem>
<listitem><para>Roger Hardiman <email>roger@cs.strath.ac.uk</email></para></listitem>
<listitem><para>Roland Jesse <email>jesse@cs.uni-magdeburg.de</email></para></listitem>
<listitem><para>Ron Bickers <email>rbickers@intercenter.net</email></para></listitem>
<listitem><para>Ron Lenk <email>rlenk@widget.xmission.com</email></para></listitem>
<listitem><para>Ronald Kuehn <email>kuehn@rz.tu-clausthal.de</email></para></listitem>
<listitem><para>Rudolf Cejka</para></listitem>
<listitem><para>Rudolf Cejka <email>unknown</email></para></listitem>
<listitem><para>Ruslan Belkin <email>rus@home2.UA.net</email></para></listitem>
<listitem><para>Ruslan Ermilov <email>ru@ucb.crimea.ua</email></para></listitem>
<listitem><para>Ruslan Shevchenko <email>rssh@cam.grad.kiev.ua</email></para></listitem>
@ -2008,7 +2008,7 @@ box can be opened)</para>
<listitem><para>Stefan Bethke <email>stb@hanse.de</email></para></listitem>
<listitem><para>Stefan Eggers <email>seggers@semyam.dinoco.de</email></para></listitem>
<listitem><para>Stefan Moeding <email>s.moeding@ndh.net</email></para></listitem>
<listitem><para>Stefan Petri</para></listitem>
<listitem><para>Stefan Petri <email>unknown</email></para></listitem>
<listitem><para>Stefan `Sec` Zehl <email>sec@42.org</email></para></listitem>
<listitem><para>Steinar Haug <email>sthaug@nethelp.no</email></para></listitem>
<listitem><para>Stephane E. Potvin <email>sepotvin@videotron.ca</email></para></listitem>
@ -2021,7 +2021,7 @@ box can be opened)</para>
<listitem><para>Stephen McKay <email>syssgm@devetir.qld.gov.au</email></para></listitem>
<listitem><para>Stephen Melvin <email>melvin@zytek.com</email></para></listitem>
<listitem><para>Steve Bauer <email>sbauer@rock.sdsmt.edu</email></para></listitem>
<listitem><para>Steve Deering</para></listitem>
<listitem><para>Steve Deering <email>unknown</email></para></listitem>
<listitem><para>Steve Gerakines <email>steve2@genesis.tiac.net</email></para></listitem>
<listitem><para>Steve Gericke <email>steveg@comtrol.com</email></para></listitem>
<listitem><para>Steve Piette <email>steve@simon.chi.il.US</email></para></listitem>
@ -2030,7 +2030,7 @@ box can be opened)</para>
<listitem><para>Steven H. Samorodin <email>samorodi@NUXI.com</email></para></listitem>
<listitem><para>Steven McCanne <email>mccanne@cs.berkeley.edu</email></para></listitem>
<listitem><para>Steven Plite <email>splite@purdue.edu</email></para></listitem>
<listitem><para>Steven Wallace</para></listitem>
<listitem><para>Steven Wallace <email>unknown</email></para></listitem>
<listitem><para>Stuart Henderson <email>stuart@internationalschool.co.uk</email></para></listitem>
<listitem><para>Sue Blake <email>sue@welearn.com.au</email></para></listitem>
<listitem><para>Sugiura Shiro <email>ssugiura@duo.co.jp</email></para></listitem>
@ -2055,7 +2055,7 @@ box can be opened)</para>
<listitem><para>Tatsumi HOSOKAWA <email>hosokawa@jp.FreeBSD.org</email></para></listitem>
<listitem><para>Ted Buswell <email>tbuswell@mediaone.net</email></para></listitem>
<listitem><para>Ted Faber <email>faber@isi.edu</email></para></listitem>
<listitem><para>Ted Lemon</para></listitem>
<listitem><para>Ted Lemon <email>unknown</email></para></listitem>
<listitem><para>Terry Lambert <email>terry@lambert.org</email></para></listitem>
<listitem><para>Terry Lee <email>terry@uivlsi.csl.uiuc.edu</email></para></listitem>
<listitem><para>Tetsuya Furukawa <email>tetsuya@secom-sis.co.jp</email></para></listitem>
@ -2067,7 +2067,7 @@ box can be opened)</para>
<listitem><para>Thomas Gellekum <email>thomas@ghpc8.ihf.rwth-aachen.de</email></para></listitem>
<listitem><para>Thomas Graichen <email>graichen@omega.physik.fu-berlin.de</email></para></listitem>
<listitem><para>Thomas K&ouml;nig <email>Thomas.Koenig@ciw.uni-karlsruhe.de</email></para></listitem>
<listitem><para>Thomas Ptacek</para></listitem>
<listitem><para>Thomas Ptacek <email>unknown</email></para></listitem>
<listitem><para>Thomas Stromberg <email>tstrombe@rtci.com</email></para></listitem>
<listitem><para>Thomas Valentino Crimi <email>tcrimi+@andrew.cmu.edu</email></para></listitem>
<listitem><para>Thomas Wintergerst <email>thomas@lemur.nord.de</email></para></listitem>

40
en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -414,7 +414,7 @@ subscribe cvs-all</programlisting>
any detected changes being compressed, stamped with a
sequence-number and encoded for transmission over email (in printable
ASCII only). Once received, these &ldquo;CTM deltas&rdquo; can then be handed
to the <citerefentry><refentrytitle>ctm_rmail</refentrytitle><manvolnum>1</manvolnum></citerefentry> utility which will automatically decode, verify
to the &man.ctm.rmail.1; utility which will automatically decode, verify
and apply the changes to the user's copy of the sources. This
process is far more efficient than <application>CVSup</application>, and places less strain on
our server resources since it is a <emphasis>push</emphasis> rather
@ -447,10 +447,7 @@ subscribe cvs-all</programlisting>
against one of the FreeBSD project's official anoncvs servers. To
use it, one simply sets the <envar>CVSROOT</envar> environment
variable to point at the appropriate anoncvs server and then uses
the <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> command to access it like any local
the &man.cvs.1; command to access it like any local
repository.</para>
<para>While it can also be said that the <link
@ -481,10 +478,7 @@ subscribe cvs-all</programlisting>
<sect3>
<title><anchor id="anoncvs-usage">Using Anonymous CVS</title>
<para>Configuring <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> to use an Anonymous CVS repository is a simple
<para>Configuring &man.cvs.1; to use an Anonymous CVS repository is a simple
matter of setting the <envar>CVSROOT</envar> environment variable
to point to one of the FreeBSD project's
<emphasis>anoncvs</emphasis> servers. At the time of this writing,
@ -500,10 +494,7 @@ subscribe cvs-all</programlisting>
<para>Since CVS allows one to &ldquo;check out&rdquo; virtually any
version of the FreeBSD sources that ever existed (or, in some
cases, will exist <!-- smiley -->:), you need to be familiar with
the revision (<option>-r</option>) flag to <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> and what some of the permissible values for it in
the revision (<option>-r</option>) flag to &man.cvs.1; and what some of the permissible values for it in
the FreeBSD Project repository are.</para>
<para>There are two kinds of tags, revision tags and branch tags. A
@ -655,26 +646,19 @@ subscribe cvs-all</programlisting>
<para>When you specify a branch tag, you normally receive the latest
versions of the files on that line of development. If you wish to
receive some past version, you can do so by specifying a date with
the <option>-D date</option> flag. See the <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> man page for more details.</para>
the <option>-D date</option> flag. See the &man.cvs.1; man page for more details.</para>
</sect3>
<sect3>
<title>Examples</title>
<para>While it really is recommended that you read the manual page
for <citerefentry>
<refentrytitle>cvs</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> thoroughly before doing
for &man.cvs.1; thoroughly before doing
anything, here are some quick examples which essentially show how
to use Anonymous CVS:</para>
<example>
<title>Checking out something from -current (<citerefentry>
<refentrytitle>ls</refentrytitle>
<manvolnum>1</manvolnum></citerefentry>) and deleting it
<title>Checking out something from -current (&man.ls.1;) and deleting it
again:</title>
<screen>
@ -694,9 +678,7 @@ subscribe cvs-all</programlisting>
</example>
<example>
<title>Creating a list of changes (as unidiffs) to <citerefentry>
<refentrytitle>ls</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> between FreeBSD 2.2.2
<title>Creating a list of changes (as unidiffs) to &man.ls.1; between FreeBSD 2.2.2
and FreeBSD 2.2.6:</title>
<screen>
@ -1556,7 +1538,7 @@ cvs-crypto</programlisting>
the latest versions of the files on that line of
development. If you wish to receive some past version,
you can do so by specifying a date with the <option>date=</option> value
field. The <citerefentry><refentrytitle>cvsup</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page explains how to do
field. The &man.cvsup.1; manual page explains how to do
that.</para>
<para>For our example, we wish to receive FreeBSD-current.
@ -1657,7 +1639,7 @@ exists before running CVSup. On any particular run of
alone.</para>
<para><literal>use-rel-suffix</literal> is ... arcane. If you really want to
know about it, see the <citerefentry><refentrytitle>cvsup</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page. Otherwise,
know about it, see the &man.cvsup.1; manual page. Otherwise,
just specify it and do not worry about it.</para>
<para><literal>compress</literal> enables the use of gzip-style compression
@ -1751,7 +1733,7 @@ cvs-crypto</programlisting>
see the manual page.</para>
<para>Once you are satisfied with the way updates are working, you
can arrange for regular runs of cvsup using <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Obviously,
can arrange for regular runs of cvsup using &man.cron.8;. Obviously,
you should not let cvsup use its GUI when running it from
cron.</para>

2
en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml
View file

@ -540,7 +540,7 @@ help
<para>This is
the mailing list for reporting bugs in FreeBSD Whenever
possible, bugs should be submitted using the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
possible, bugs should be submitted using the &man.send-pr.1;
command or the <ulink
URL="http://www.freebsd.org/send-pr.html">WEB
interface</ulink> to it.</para>

24
en_US.ISO_8859-1/books/handbook/hw/chapter.sgml
View file

@ -2628,7 +2628,7 @@ INS8250 -&gt; INS8250B
<para>The <devicename>sio</devicename> driver provides
support for NS8250-, NS16450-, NS16550 and NS16550A-based EIA
RS-232C (CCITT V.24) communications interfaces. Several
multiport cards are supported as well. See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for detailed technical
multiport cards are supported as well. See the &man.sio.4; manual page for detailed technical
documentation.</para>
@ -2719,7 +2719,7 @@ options COM_MULTIPORT</programlisting>
sio<replaceable>n</replaceable></literal> lines are,
you will need to add 16 more devices. Only
the last device includes the interrupt vector for the
board. (See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for detail as
board. (See the &man.sio.4; manual page for detail as
to why.) The following example is for a Boca Board with
an interrupt of 3, and a base IO address 100h. The IO
address for Each port is +8 hexadecimal from the
@ -4387,7 +4387,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
address of the device that is failing, and the desired
debug level in <filename>/sys/scsi/scsidebug.h</filename>.
If it probes but just does not work, you can use the
<citerefentry><refentrytitle>scsi</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to dynamically set a
&man.scsi.8; command to dynamically set a
debug level to it in a running kernel (if <literal>SCSIDEBUG</literal> is
defined). This will give you <emphasis>copious</emphasis> debugging output with
which to confuse the gurus. See <command>man 4
@ -4705,10 +4705,10 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
<sect3>
<title>General tape access commands</title>
<para><citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> provides generic access to the tape
<para>&man.mt.1; provides generic access to the tape
drives. Some of the more common commands are
<command>rewind</command>, <command>erase</command>, and
<command>status</command>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry>
<command>status</command>. See the &man.mt.1;
manual page for a detailed description.</para>
</sect3>
@ -4728,12 +4728,12 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
<sect3>
<title>SCSI drives</title>
<para>The <citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry> driver provides
<para>The &man.st.4; driver provides
support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC
(Quarter-Inch Cartridge), DLT (Digital Linear Tape), QIC
Minicartridge and 9-track (remember the big reels that you see
spinning in Hollywood computer rooms) tape drives. See the
<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for a detailed
&man.st.4; manual page for a detailed
description.</para>
<para>The drives listed below are currently being used by members
@ -4876,7 +4876,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
and QIC-525 (DC6525) tapes as well.</para>
<para>Data transfer rate is 350kB/s using
<citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Rates of 530kB/s have been
&man.dump.8;. Rates of 530kB/s have been
reported when using <link
linkend="backups-programs-amanda">Amanda</link></para>
@ -4982,7 +4982,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
(250MB) tapes.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>).</para>
scsi tape device driver (&man.st.4;).</para>
<para>Under FreeBSD 2.2-current, use <command>mt
blocksize 512</command> to set the blocksize. (The
@ -5513,7 +5513,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
<para>Native capacity is 150/250MB.</para>
<para>This drive has quirks which are known and work around code
is present in the scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>). Upgrading the firmware to XXX
is present in the scsi tape device driver (&man.st.4;). Upgrading the firmware to XXX
version will fix the quirks and provide SCSI 2
capabilities.</para>
@ -5552,7 +5552,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
supported for the 2.5 GB cartridges.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>)
scsi tape device driver (&man.st.4;)
beginning with FreeBSD 2.2-current. For previous versions of
FreeBSD, use <command>mt</command> to read one
block from the tape, rewind the tape, and then execute the
@ -5590,7 +5590,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
erased.</para>
<para>This drives quirks are known and pre-compiled into the
scsi tape device driver (<citerefentry><refentrytitle>st</refentrytitle><manvolnum>4</manvolnum></citerefentry>).</para>
scsi tape device driver (&man.st.4;).</para>
<para>Other firmware revisions that are known to work are:
M75D</para>

4
en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml
View file

@ -432,10 +432,10 @@
are the people who have <emphasis>write</emphasis> access to
the CVS tree, and are thus authorized to make modifications
to the FreeBSD source (the term &ldquo;committer&rdquo; comes from the
<citerefentry><refentrytitle>cvs</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>commit</command> command, which is used to
&man.cvs.1; <command>commit</command> command, which is used to
bring new changes into the CVS repository). The best way of
making submissions for review by the committers list is to
use the <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, though if something appears to be jammed in the system then you may also reach them by sending mail to <email>committers@freebsd.org</email>.</para>
use the &man.send-pr.1; command, though if something appears to be jammed in the system then you may also reach them by sending mail to <email>committers@freebsd.org</email>.</para>
</listitem>
</varlistentry>

26
en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -122,7 +122,7 @@
<note>
<para>If you are trying to upgrade your kernel from an older version
of FreeBSD, you will probably have to get a new version of
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> from the same place you got the new
&man.config.8; from the same place you got the new
kernel sources. It is located in
<filename>/usr/src/usr.sbin</filename>, so you will need to
download those sources as well. Re-build and install it before
@ -430,7 +430,7 @@
hundred bytes to the kernel.</para>
<note>
<para>The <citerefentry><refentrytitle>ipcs</refentrytitle><manvolnum>1</manvolnum></citerefentry> command will tell
<para>The &man.ipcs.1; command will tell
will list any processes using each of these System V
facilities.</para>
</note>
@ -503,7 +503,7 @@
<listitem>
<para>Process filesystem. This is a pretend filesystem
mounted on <filename>/proc</filename> which allows
programs like <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> to give you more
programs like &man.ps.1; to give you more
information on what processes are running.</para>
</listitem>
</varlistentry>
@ -609,7 +609,7 @@
<note>
<para>QIC-80 tape support requires a separate filter
program called <citerefentry><refentrytitle>ft</refentrytitle><manvolnum>8</manvolnum></citerefentry>, see the manual
program called &man.ft.8;, see the manual
page for details.</para>
</note>
</listitem>
@ -975,7 +975,7 @@
modem to 2 (for obscure technical reasons IRQ 2 = IRQ 9)
in order to access it from FreeBSD. If you have a
multiport serial card, check the manual page for
<citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for more information on the
&man.sio.4; for more information on the
proper values for these lines. Some video cards (notably
those based on S3 chips) use IO addresses of the form
<literal>0x*2e8</literal>, and since many cheap serial
@ -1250,7 +1250,7 @@
network interfaces to be placed in promiscuous mode,
capturing every packet on a broadcast network (e.g. an
ethernet). These packets can be captured to disk and/or
examined with the <citerefentry><refentrytitle>tcpdump</refentrytitle><manvolnum>1</manvolnum></citerefentry> program.
examined with the &man.tcpdump.1; program.
Note that implementation of this capability can seriously
compromise your overall network security. The
<replaceable>number</replaceable> after bpfilter is the number
@ -1445,7 +1445,7 @@
<listitem>
<para>Snoop device. This pseudo-device allows one terminal
session to watch another using the
<citerefentry><refentrytitle>watch</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. Note that
&man.watch.8; command. Note that
implementation of this capability has important security
and privacy implications. The <replaceable>number</replaceable>
after snp is the total number of simultaneous snoop
@ -1457,7 +1457,7 @@
<listitem>
<para>Vnode driver. Allows a file to be treated as a device
after being set up with the <citerefentry><refentrytitle>vnconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry>
after being set up with the &man.vnconfig.8;
command. This driver can be useful for manipulating
floppy disk images and using a file as a swap device (e.g.
an MS Windows swap file). Optional.</para>
@ -1473,8 +1473,8 @@
&ldquo;meta&rdquo;-disk. The <replaceable>number</replaceable> after ccd
is the total number of concatenated disks (not total
number of disks that can be concatenated) that can be
created. (See <citerefentry><refentrytitle>ccd</refentrytitle><manvolnum>4</manvolnum></citerefentry> and
<citerefentry><refentrytitle>ccdconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> man pages for more
created. (See &man.ccd.4; and
&man.ccdconfig.8; man pages for more
details.) Optional.</para>
</listitem>
</varlistentry>
@ -1642,7 +1642,7 @@ controller wcd0</programlisting>
resource is the <filename>/var/log/messages</filename> file
which records, among other things, all of the kernel
messages from every successful boot. Also, the
<citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>8</manvolnum></citerefentry> command will print the kernel
&man.dmesg.8; command will print the kernel
messages from the current boot.</para>
<note>
@ -1655,7 +1655,7 @@ controller wcd0</programlisting>
with the last installed kernel which may be
non-functional. Also, as soon as possible, move the
working kernel to the proper <filename>kernel</filename> location or
commands such as <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> will not work
commands such as &man.ps.1; will not work
properly. The proper command to &ldquo;unlock&rdquo; the
kernel file that <command>make</command> installs (in
order to move another kernel back permanently) is:</para>
@ -1683,7 +1683,7 @@ controller wcd0</programlisting>
from the one that the system utilities have been built with,
for example, an experimental &ldquo;2.2.0&rdquo; kernel on a
2.1.0-RELEASE system, many system-status commands like
<citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> and <citerefentry><refentrytitle>vmstat</refentrytitle><manvolnum>8</manvolnum></citerefentry>
&man.ps.1; and &man.vmstat.8;
will not work any more. You must recompile the <filename>libkvm</filename> library as well as these
utilities. This is one reason it is not normally a good
idea to use a different version of the kernel from the rest

17
en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml
View file

@ -13,10 +13,7 @@
is too small to hold the dump, you can configure your kernel to use
an alternate dump device (in the <literal>config
kernel</literal> line), or you can specify an alternate using the
<citerefentry><refentrytitle>dumpon</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. The best way to use <citerefentry>
<refentrytitle>dumpon</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry> is to set the <literal>dumpdev</literal> variable in
&man.dumpon.8; command. The best way to use &man.dumpon.8; is to set the <literal>dumpdev</literal> variable in
<filename>/etc/rc.conf</filename>. Typically you want to specify one of
the swap devices specified in <filename>/etc/fstab</filename>.
Dumps to non-swap devices, tapes for example,
@ -25,10 +22,10 @@ Dumps to non-swap devices, tapes for example,
Configuration</link> for
details on configuring the FreeBSD kernel.</para>
<para>Use the <citerefentry><refentrytitle>dumpon</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to tell the kernel
<para>Use the &man.dumpon.8; command to tell the kernel
where to dump to (note that this will have to be done after
configuring the partition in question as swap space via
<citerefentry><refentrytitle>swapon</refentrytitle><manvolnum>8</manvolnum></citerefentry>). This is normally arranged via
&man.swapon.8;). This is normally arranged via
<filename>/etc/rc.conf</filename> and <filename>/etc/rc</filename>.
Alternatively, you can hard-code the dump device via the <literal>dump</literal>
clause in the <literal>config</literal> line of your kernel config file. This is
@ -68,7 +65,7 @@ Dumps to non-swap devices, tapes for example,
&prompt.root; <userinput>exit</userinput> # ...to multi-user</screen>
<para>This instructs <citerefentry><refentrytitle>savecore</refentrytitle><manvolnum>8</manvolnum></citerefentry> to
<para>This instructs &man.savecore.8; to
use another kernel for symbol name extraction. It would otherwise
default to the currently running kernel and most likely not do
anything at all since the crash dump and the kernel symbols
@ -279,7 +276,7 @@ Dumps to non-swap devices, tapes for example,
generated code, so you will finally get a new kernel with similar
code to the faulting one but some debugging symbols. You should at
least verify the old and new sizes with the
<citerefentry><refentrytitle>size</refentrytitle><manvolnum>1</manvolnum></citerefentry> command. If there is a mismatch, you
&man.size.1; command. If there is a mismatch, you
probably need to give up here.</para>
<para>Go and examine the dump as described above. The debugging
@ -479,7 +476,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
<para>The return value will be printed.</para>
<para>For a <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> style summary of all running
<para>For a &man.ps.1; style summary of all running
processes, use:</para>
@ -525,7 +522,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
<para>However, it is highly recommended to have a
printed copy of the <citerefentry><refentrytitle>ddb</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page
printed copy of the &man.ddb.4; manual page
ready for a debugging session. Remember that it is hard to read the
on-line manual while single-stepping the kernel.</para>

8
en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml
View file

@ -19,10 +19,10 @@
the supported options in the kernel into new-style ones, so for
people who correctly did a <command>make depend</command>
in their kernel compile directory after running
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry>, the build process will automatically
&man.config.8;, the build process will automatically
pick up modified options, and only recompile those files where it is
necessary. Wiping out the old compile directory on each run of
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> as it is still done now can then be
&man.config.8; as it is still done now can then be
eliminated again.</para>
<para>Basically, a kernel option is nothing else than the definition
@ -89,7 +89,7 @@ options notyet,notdef</programlisting>
using such an option is responsible himself for knowing about its
implications (and maybe manually forcing the recompilation of parts
of his kernel). Once the transition of all supported options has
been done, <citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> will warn whenever an
been done, &man.config.8; will warn whenever an
unsupported option appears in the config file, but it will
nevertheless include it into the kernel Makefile.</para>
@ -114,7 +114,7 @@ options notyet,notdef</programlisting>
<filename>opt_<replaceable>foo</replaceable>.h</filename> already
available for the intended new option, invent a new name. Make it
meaningful, and comment the new section in the
<filename>options[<replaceable>.&lt;arch&gt;</replaceable>]</filename> file. <citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves..</para>
<filename>options[<replaceable>.&lt;arch&gt;</replaceable>]</filename> file. &man.config.8; will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves..</para>
<para>Packing too many options into a single
<filename>opt_<replaceable>foo</replaceable>.h</filename> will cause

28
en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml
View file

@ -49,7 +49,7 @@ font8x8=cp866-8x8</programlisting>
<para>This tuning means KOI8-R keyboard with Alternative
screen font mapped to KOI8-R encoding to preserve
pseudographics, <literal>Gray Delete</literal>
key remapped to match Russian <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry for FreeBSD
key remapped to match Russian &man.termcap.5; entry for FreeBSD
console.</para>
<para>RUS/LAT switch will be <literal>CapsLock</literal>. Old CapsLock function still
@ -83,7 +83,7 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<listitem>
<para><envar>LANG</envar> for POSIX
<citerefentry><refentrytitle>setlocale</refentrytitle><manvolnum>3</manvolnum></citerefentry> family functions;</para>
&man.setlocale.3; family functions;</para>
</listitem>
<listitem>
@ -95,8 +95,8 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<para>The best way is using <filename>/etc/login.conf</filename>
<literal>russian</literal> user's login class in
<citerefentry><refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry login class
position. See <citerefentry><refentrytitle>login.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
&man.passwd.5; entry login class
position. See &man.login.conf.5; for
details.</para>
@ -115,9 +115,9 @@ russian:Russian Users Accounts:\
<sect4>
<title>How to do it with <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.vipw.8;</title>
<para>If you use <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new
<para>If you use &man.vipw.8; for adding new
users, <filename>/etc/master.passwd</filename> entry should
looks like:</para>
@ -127,9 +127,9 @@ user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh</programlisting>
</sect4>
<sect4>
<title>How to do it with <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.adduser.8;</title>
<para>If you use <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new
<para>If you use &man.adduser.8; for adding new
users:</para>
<itemizedlist>
@ -149,7 +149,7 @@ defaultclass = russian</programlisting> in
<screen><prompt>Enter login class:</prompt> default []:</screen>
prompt from
<citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;</para>
&man.adduser.8;;</para>
</listitem>
<listitem>
@ -166,9 +166,9 @@ defaultclass = russian</programlisting> in
</sect4>
<sect4>
<title>How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title>
<title>How to do it with &man.pw.8;</title>
<para>If you use <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users,
<para>If you use &man.pw.8; for adding new users,
call it in this form:</para>
@ -245,21 +245,21 @@ lp|Russian local line printer:\
:sh:of=/usr/libexec/lpr/ru/koi2alt:\
:lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:</programlisting>
<para>See <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para>
<para>See &man.printcap.5; for detailed description.</para>
</sect2>
<sect2 id="russian-msdosfs">
<title>MSDOS FS and Russian file names</title>
<para>Look at following example <citerefentry><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry to enable support for Russian
<para>Look at following example &man.fstab.5; entry to enable support for Russian
file names in MSDOS FS:</para>
<programlisting>
/dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0</programlisting>
<para>See
<citerefentry><refentrytitle>mount_msdos</refentrytitle><manvolnum>8</manvolnum></citerefentry>for detailed description of
&man.mount.msdos.8; for detailed description of
<option>-W</option> and <option>-L</option> options.</para>
</sect2>

7
en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -404,7 +404,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
check if it needs shared libraries, and if so, whether you have
them installed in the <filename>/compat/linux</filename> tree.
To do this, you run the Linux version <command>ldd</command> on the new program,
and watch its output. <command>ldd</command> (see also the manual page for <citerefentry><refentrytitle>ldd</refentrytitle><manvolnum>1</manvolnum></citerefentry>)
and watch its output. <command>ldd</command> (see also the manual page for &man.ldd.1;)
will print a list of shared libraries that the program depends
on, in the form <literal><replaceable>majorname</replaceable> (<replaceable>jumpversion</replaceable>) =&gt; <replaceable>fullname</replaceable></literal>.</para>
@ -433,10 +433,7 @@ Abort</screen>
<para>To help the FreeBSD kernel distinguish between a FreeBSD ELF
binary from a Linux binary, use the <citerefentry>
<refentrytitle>brandelf</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> utility.</para>
binary from a Linux binary, use the &man.brandelf.1; utility.</para>
<screen>&prompt.user; <userinput>brandelf -t Linux my-linux-elf-binary</userinput></screen>

34
en_US.ISO_8859-1/books/handbook/ports/chapter.sgml
View file

@ -522,7 +522,7 @@ do-install:
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
the <citerefentry><refentrytitle>pkg_add</refentrytitle><manvolnum>1</manvolnum></citerefentry> program to install a
the &man.pkg.add.1; program to install a
package file on your system.</para>
</listitem>
@ -1170,7 +1170,7 @@ lib/X11/oneko/cat2.xpm
lib/X11/oneko/mouse.xpm
@dirrm lib/X11/oneko</programlisting>
<para>Refer to the <citerefentry><refentrytitle>pkg_create</refentrytitle><manvolnum>1</manvolnum></citerefentry> man page
<para>Refer to the &man.pkg.create.1; man page
for details on the packing list.</para>
<note>
@ -1290,19 +1290,10 @@ lib/X11/oneko/mouse.xpm
<filename>pkgname.tgz</filename> package, so delete them
now. Next, simply include the output of <command>shar `find
port_dir`</command> in a bug report and send it with the
<citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> program (see <link linkend="contrib-general">Bug
&man.send-pr.1; program (see <link linkend="contrib-general">Bug
Reports and General Commentary</link> for more information
about <citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry>. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use <citerefentry>
<refentrytitle>uuencode</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> before including it in the bug report (uuencoded
about &man.send-pr.1;. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use &man.uuencode.1; before including it in the bug report (uuencoded
tarfiles are acceptable even if the bug report is smaller than
20KB but are not preferred). Be sure to classify the bug report as
category <literal>ports</literal> and class
@ -2805,9 +2796,7 @@ diff -u -r1.15 PLIST
POST-INSTALL</literal>. <literal>&dollar;2</literal> can be
tested to determine which mode the script is being run in. The
<envar>PKG_PREFIX</envar> environmental variable will be set to
the package installation directory. See <citerefentry>
<refentrytitle>pkg_add</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> for additional
the package installation directory. See &man.pkg.add.1; for additional
information.</para>
<note>
@ -3045,7 +3034,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<command>diff -ruN superedit.bak
superedit</command>). Please examine the output to make
sure all the changes make sense. The best way to send us the
diff is by including it to <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
diff is by including it to &man.send-pr.1;
(category <literal>ports</literal>). Please mention any added or deleted files
in the message, as they have to be explicitly specified to CVS
when doing a commit. If the diff is more than about 20KB, please
@ -3053,7 +3042,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
the PR.</para>
<para>Once again, please use
<citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> and not <citerefentry><refentrytitle>shar</refentrytitle><manvolnum>1</manvolnum></citerefentry> to send updates to ports.</para>
&man.diff.1; and not &man.shar.1; to send updates to ports.</para>
</sect2>
<sect2>
@ -3080,10 +3069,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
post-install:
strip ${PREFIX}/bin/xdl</programlisting>
<para>Use the <citerefentry>
<refentrytitle>file</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> command on the installed executable to check
<para>Use the &man.file.1; command on the installed executable to check
whether the binary is stripped or not. If it does not say
<literal>not stripped</literal>, it is stripped.</para>
</sect3>
@ -3788,7 +3774,7 @@ post-install:
(executables for superusers/managers),
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
files). See man &man.hier.7; for
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use

32
en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml
View file

@ -168,8 +168,8 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
<para>If you have a kernel without the tun device, and you can not
rebuild it for some reason, all is not lost. You should be able
to dynamically load the code. Refer to the appropriate <citerefentry><refentrytitle>modload</refentrytitle><manvolnum>8</manvolnum></citerefentry>
and <citerefentry><refentrytitle>lkm</refentrytitle><manvolnum>4</manvolnum></citerefentry> pages for further details.</para>
to dynamically load the code. Refer to the appropriate &man.modload.8;
and &man.lkm.4; pages for further details.</para>
<para>You may also wish to take this opportunity to configure a
firewall. Details can be found in the <link linkend="firewalls">Firewalls</link> section.</para>
@ -395,7 +395,7 @@ domain <replaceable>bar.com</replaceable></programlisting>
<listitem>
<para>The dial string. User PPP uses an expect-send
syntax similar to the <citerefentry><refentrytitle>chat</refentrytitle><manvolnum>8</manvolnum></citerefentry>
syntax similar to the &man.chat.8;
program. Refer to the manual page for information on
the features of this language.</para>
</listitem>
@ -1023,7 +1023,7 @@ set server /var/run/ppp-tun%d DiagnosticPassword 0177</programlisting>
tun device number that is in use.</para>
<para>Once a socket has been set up, the
<citerefentry><refentrytitle>pppctl</refentrytitle><manvolnum>8</manvolnum></citerefentry> program may be used in scripts that
&man.pppctl.8; program may be used in scripts that
wish to manipulate the running program.</para>
</sect3>
@ -1190,7 +1190,7 @@ sendmail_flags="-bd"</programlisting>
<step>
<para>Create an entry in <filename>/etc/passwd</filename>
(using the <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> program).</para>
(using the &man.vipw.8; program).</para>
</step>
<step>
@ -2014,12 +2014,12 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
otherwise, check the place where you found this document for a
document named <filename>dialup.txt</filename> or something
similar. You may also want to check the manual pages for
<citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for information on the serial
port device driver and <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry>, &amp; <citerefentry><refentrytitle>init</refentrytitle><manvolnum>8</manvolnum></citerefentry> for
&man.sio.4; for information on the serial
port device driver and &man.ttys.5;,
&man.gettytab.5;,
&man.getty.8;, &amp; &man.init.8; for
information relevant to configuring the system to accept logins on
modems, and perhaps <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for information on
modems, and perhaps &man.stty.1; for information on
setting serial port parameters (such as <literal>clocal</literal> for directly-connected serial
interfaces).</para>
@ -2082,8 +2082,8 @@ Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp</programlisting>
goes wrong, <command>sliplogin</command> usually logs
good informational messages via the <literal>daemon</literal> syslog facility,
which usually goes into <filename>/var/log/messages</filename>
(see the manual pages for <citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry> and
<citerefentry><refentrytitle>syslog.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>, and perhaps check
(see the manual pages for &man.syslogd.8; and
&man.syslog.conf.5, and perhaps check
<filename>/etc/syslog.conf</filename> to see to which files
<command>syslogd</command> is logging).</para>
@ -2163,7 +2163,7 @@ pseudo-device sl 2</programlisting>
<para>As mentioned earlier, there are three files in the
<filename>/etc/sliphome</filename> directory that are part of the
configuration for <filename>/usr/sbin/sliplogin</filename> (see
<citerefentry><refentrytitle>sliplogin</refentrytitle><manvolnum>8</manvolnum></citerefentry> for the actual manual page for
&man.sliplogin.8; for the actual manual page for
<command>sliplogin</command>):
<filename>slip.hosts</filename>, which defines the SLIP users
&amp; their associated IP addresses;
@ -2281,7 +2281,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
SLIP server's Ethernet subnet, and you will also need to adjust
your <filename>/etc/sliphome/slip.login</filename> and
<filename>/etc/sliphome/slip.logout</filename> scripts to use
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> to manage the proxy-ARP entries in the
&man.arp.8; to manage the proxy-ARP entries in the
SLIP server's ARP table.</para>
</sect3>
@ -2355,8 +2355,8 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<command>netstat -i</command> must be changed to colons and
leading zeros should be added to each single-digit hexadecimal
number to convert the address into the form that
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> desires; see the manual page on
<citerefentry><refentrytitle>arp</refentrytitle><manvolnum>8</manvolnum></citerefentry> for complete information on
&man.arp.8; desires; see the manual page on
&man.arp.8; for complete information on
usage.</para>
<note>

282
en_US.ISO_8859-1/books/handbook/printing/chapter.sgml
View file

@ -448,8 +448,7 @@ sio2: type 16550A</screen>
<procedure>
<step>
<para>Become root with the <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>
<para>Become root with the &man.su.1;
command. Enter the root password when prompted.</para>
</step>
@ -523,8 +522,7 @@ sio2: type 16550A</screen>
works.</para>
<para>You can set the communications mode in two ways: by
configuring the kernel or by using the <citerefentry>
<refentrytitle>lptcontrol</refentrytitle></citerefentry> program.</para>
configuring the kernel or by using the &man.lptcontrol.8; program.</para>
<para><emphasis>To set the communications mode by
configuring the kernel:</emphasis></para>
@ -571,8 +569,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
</procedure>
<para><emphasis>To set the communications mode
with</emphasis> <citerefentry>
<refentrytitle>lptcontrol</refentrytitle></citerefentry>:</para>
with</emphasis> &man.lptcontrol.8;:</para>
<procedure>
@ -601,7 +598,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
<para>You could put these commands in your
<filename>/etc/rc.local</filename> file to set the mode each
time your system boots. See <citerefentry><refentrytitle>lptcontrol</refentrytitle><manvolnum>8</manvolnum></citerefentry> for more information.</para>
time your system boots. See &man.lptcontrol.8; for more information.</para>
</sect4>
@ -615,8 +612,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
<para>To test the printer, we will send some text to it. For
printers that can immediately print characters sent to them,
the program <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> is perfect: it generates all 96 printable ASCII characters in 96 lines.</para>
the program &man.lptest.1; is perfect: it generates all 96 printable ASCII characters in 96 lines.</para>
<para>For a PostScript (or other language-based) printer, we
will need a more sophisticated test. A small PostScript
@ -653,8 +649,7 @@ showpage</programlisting>
<procedure>
<step>
<para>Become root with <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>.</para>
<para>Become root with &man.su.1;.</para>
</step>
<step>
@ -663,8 +658,7 @@ showpage</programlisting>
<listitem>
<para>If the printer can print plain text, then
use <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. Type:</para>
use &man.lptest.1;. Type:</para>
<screen>&prompt.root; <userinput>lptest &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
@ -726,8 +720,7 @@ showpage</programlisting>
<procedure>
<step>
<para>Become root with <citerefentry>
<refentrytitle>su</refentrytitle></citerefentry>.</para>
<para>Become root with &man.su.1;.</para>
</step>
<step>
@ -753,8 +746,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
</step>
<step>
<para>Connect to the printer with <citerefentry>
<refentrytitle>tip</refentrytitle></citerefentry>. Type:</para>
<para>Connect to the printer with &man.tip.1;. Type:</para>
<screen>&prompt.root; <userinput>tip printer</userinput></screen>
@ -771,8 +763,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<listitem>
<para>If the printer can print plain text, then
use <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. Type:</para>
use &man.lptest.1;. Type:</para>
<screen><prompt>~</prompt><userinput>$lptest</userinput></screen>
@ -799,8 +790,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<para>Where <replaceable>file</replaceable> is the name of the
file containing the program. After
<citerefentry>
<refentrytitle>tip</refentrytitle></citerefentry> sends the file, press any required end-of-file key.</para>
&man.tip.1; sends the file, press any required end-of-file key.</para>
</listitem>
</itemizedlist>
@ -831,8 +821,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
reads this file each time the spooler is used, so updates to the
file take immediate effect.</para>
<para>The format of the <citerefentry>
<refentrytitle>printcap</refentrytitle></citerefentry> file is straightforward. Use your favorite text editor to make changes to <filename>/etc/printcap</filename>. The format is identical to other capability files like <filename>/usr/share/misc/termcap</filename> and <filename>/etc/remote</filename>. For complete information about the format, see the <citerefentry><refentrytitle>cgetent</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
<para>The format of the &man.printcap.5; file is straightforward. Use your favorite text editor to make changes to <filename>/etc/printcap</filename>. The format is identical to other capability files like <filename>/usr/share/misc/termcap</filename> and <filename>/etc/remote</filename>. For complete information about the format, see the &man.cgetent.3;.</para>
<para>The simple spooler configuration consists of the following
steps:</para>
@ -880,8 +869,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<step>
<para>Test the setup by printing something with the
<citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
&man.lpr.1;
command; see <link linkend="printing-trying">Trying
It Out</link> and <link linkend="printing-troubleshooting">Troubleshooting</link>.</para>
</step>
@ -1006,8 +994,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
is customary to put these directories under
<filename>/var/spool</filename>. It is not necessary to
backup the contents of spooling directories, either.
Recreating them is as simple as running <citerefentry>
<refentrytitle>mkdir</refentrytitle></citerefentry>.</para>
Recreating them is as simple as running &man.mkdir.1;.</para>
<para>It is also customary to make the directory with a name
that is identical to the name of the printer, as shown below:</para>
@ -1294,14 +1281,11 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
Unfortunately, congratulations are not quite yet in order,
since we still have to test the setup and correct any
problems. To test the setup, try printing something. To
print with the LPD system, you use the command <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>,
print with the LPD system, you use the command &man.lpr.1;,
which submits a job for printing.</para>
<para>You can combine <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
with the <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> program, introduced in section <link linkend="printing-testing">Checking Printer Communications</link> to generate some
<para>You can combine &man.lpr.1;
with the &man.lptest.1; program, introduced in section <link linkend="printing-testing">Checking Printer Communications</link> to generate some
test text.</para>
<para><emphasis>To test the simple LPD
@ -1315,17 +1299,14 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>Where <replaceable>printer-name</replaceable> is a the name of a printer
(or an alias) specified in <filename>/etc/printcap</filename>.
To test the default printer, type <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
To test the default printer, type &man.lpr.1;
without any <option>-P</option> argument. Again, if you are
testing a printer that expects PostScript, send a PostScript
program in that language instead of using <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>. You
program in that language instead of using &man.lptest.1;. You
can do so by putting the program in a file and typing <command>lpr <replaceable>file</replaceable></command>.</para>
<para>For a PostScript printer, you should get the results of
the program. If you are using <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>, then your results should look like the following:</para>
the program. If you are using &man.lptest.1;, then your results should look like the following:</para>
<programlisting>
!"#$%&amp;'()*+,-./01234
@ -1335,8 +1316,7 @@ $%&amp;'()*+,-./01234567
%&amp;'()*+,-./012345678</programlisting>
<para>To further test the printer, try downloading larger
programs (for language-based printers) or running <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry> with different arguments. For example, <command>lptest 80 60</command> will produce 60 lines of 80 characters each.</para>
programs (for language-based printers) or running &man.lptest.1; with different arguments. For example, <command>lptest 80 60</command> will produce 60 lines of 80 characters each.</para>
<para>If the printer did not work, see the next section, <link
linkend="printing-troubleshooting">Troubleshooting</link>.</para>
@ -1346,8 +1326,7 @@ $%&amp;'()*+,-./01234567
<sect4 id="printing-troubleshooting">
<title>Troubleshooting</title>
<para>After performing the simple test with <citerefentry>
<refentrytitle>lptest</refentrytitle></citerefentry>, you
<para>After performing the simple test with &man.lptest.1;, you
might have gotten one of the following results instead of the
correct printout:</para>
@ -1665,23 +1644,20 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
FreeBSD. Here is an overview of the user-level commands:</para>
<variablelist>
<varlistentry><term><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lpr.1;</term>
<listitem>
<para>Print jobs</para>
</listitem>
</varlistentry>
<varlistentry><term><citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lpq.1;</term>
<listitem>
<para>Check printer queues</para>
</listitem>
</varlistentry>
<varlistentry><term><citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry></term>
<varlistentry><term>&man.lprm.1;</term>
<listitem>
<para>Remove jobs from a printer's queue</para>
@ -1689,16 +1665,12 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
</varlistentry>
</variablelist>
<para>There is also an administrative command, <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>,
<para>There is also an administrative command, &man.lpc.8;,
described in the section <link linkend="printing-lpc">Administrating the
LPD Spooler</link>, used to control printers and their queues.</para>
<para>All three of the commands <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>, and
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>
<para>All three of the commands &man.lpr.1;, &man.lprm.1;, and
&man.lpq.1;
accept an option <option>-P <replaceable>printer-name</replaceable></option> to specify on which
printer/queue to operate, as listed in the
<filename>/etc/printcap</filename> file. This enables you to
@ -1724,8 +1696,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>This prints each of the listed files to the
default printer. If you list no files, <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> reads
default printer. If you list no files, &man.lpr.1; reads
data to print from standard input. For example, this command
prints some important system files:</para>
@ -1747,14 +1718,12 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>Because no files were listed for the
<citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
&man.lpr.1;
command, <command>lpr</command> read the data to print
from standard input, which was the output of the <command>ls
-l</command> command.</para>
<para>The <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
<para>The &man.lpr.1; command
can also accept a wide variety of options to control formatting,
apply file conversions, generate multiple copies, and so forth.
For more information, see the section <link
@ -1765,8 +1734,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<sect2 id="printing-lpq">
<title>Checking Jobs</title>
<para>When you print with <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, the
<para>When you print with &man.lpr.1;, the
data you wish to print is put together in a package called a
&ldquo;print job&rdquo;, which is sent to the LPD spooling
system. Each printer has a queue of jobs, and your job waits in
@ -1775,8 +1743,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
order.</para>
<para>To display the queue for the default printer, type
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>. For a
&man.lpq.1;. For a
specific printer, use the <option>-P</option> option. For
example, the command
@ -1803,29 +1770,24 @@ active kelly 9 /etc/host.conf, /etc/hosts.equiv 88 bytes
details.</para>
<para>Job number nine consists of two files; multiple files given on
the <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
the &man.lpr.1; command
line are treated as part of a single job. It is the currently
active job (note the word <literal>active</literal>
under the &ldquo;Rank&rdquo; column), which means the printer should be
currently printing that job. The second job consists of data
passed as the standard input to the</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>&man.lpr.1;
command. The third job came from user mary; it is a much larger
job. The pathname of the files she's trying to print is too long
to fit, so the <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> command
to fit, so the &man.lpq.1; command
just shows three dots.</para>
<para>The very first line of the output from <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> is also
<para>The very first line of the output from &man.lpq.1; is also
useful: it tells what the printer is currently doing (or at least
what LPD thinks the printer is doing).</para>
<para>The <citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> command
<para>The &man.lpq.1; command
also support a <option>-l</option> option to generate a detailed
long listing. Here is an example of <command>lpq -l</command>:</para>
@ -1848,16 +1810,13 @@ mary: 3rd [job 011rose]
<title>Removing Jobs</title>
<para>If you change your mind about printing a job, you can remove
the job from the queue with the <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
command. Often, you can even use <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry> to
the job from the queue with the &man.lprm.1;
command. Often, you can even use &man.lprm.1; to
remove an active job, but some or all of the job might still get
printed.</para>
<para>To remove a job from the default printer, first use
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry> to find
&man.lpq.1; to find
the job number. Then type:</para>
@ -1873,8 +1832,7 @@ mary: 3rd [job 011rose]
<screen>&prompt.user; <userinput>lprm -P bamboo 10</userinput></screen>
<para>The <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
<para>The &man.lprm.1;
command has a few shortcuts:</para>
<variablelist>
@ -1900,8 +1858,7 @@ mary: 3rd [job 011rose]
<listitem>
<para>With no job number, user name, or
<option>-</option> appearing on the command line,
<citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry> removes the currently active job on the default printer, if it belongs to you. The superuser can remove any active job.</para>
&man.lprm.1; removes the currently active job on the default printer, if it belongs to you. The superuser can remove any active job.</para>
</listitem>
</varlistentry>
@ -1918,8 +1875,7 @@ mary: 3rd [job 011rose]
<note>
<para>If you are working in a networked
environment, <citerefentry>
<refentrytitle>lprm</refentrytitle></citerefentry>
environment, &man.lprm.1;
will let you remove jobs only from the host from which the jobs
were submitted, even if the same printer is available from other
hosts. The following command sequence demonstrates this:</para>
@ -1945,8 +1901,7 @@ cfA013rose dequeued
<sect2 id="printing-lpr-options">
<title>Beyond Plain Text: Printing Options</title>
<para>The <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> command
<para>The &man.lpr.1; command
supports a number of options that control formatting text,
converting graphic and other file formats, producing multiple
copies, handling of the job, and more. This section describes the
@ -1956,12 +1911,10 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-format">
<title>Formatting and Conversion Options</title>
<para>The following <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>The following &man.lpr.1;
options control formatting of the files in the job. Use these
options if the job does not contain plain text or if you want
plain text formatted through the <citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
plain text formatted through the &man.pr.1;
utility.</para>
<para>For example, the following command prints a DVI file (from
@ -2050,9 +2003,8 @@ cfA013rose dequeued
<varlistentry><term>-p</term>
<listitem>
<para>Format plain text with <citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
before printing. See <citerefentry><refentrytitle>pr</refentrytitle><manvolnum>1</manvolnum></citerefentry> for more information.</para>
<para>Format plain text with &man.pr.1;
before printing. See &man.pr.1; for more information.</para>
</listitem>
</varlistentry>
@ -2061,8 +2013,7 @@ cfA013rose dequeued
<listitem>
<para>Use <replaceable>title</replaceable> on the
<citerefentry>
<refentrytitle>pr</refentrytitle></citerefentry>
&man.pr.1;
header instead of the file name. This option has effect
only when used with the <option>-p</option>
option.</para>
@ -2086,30 +2037,24 @@ cfA013rose dequeued
<para>Here is an example: this command prints a nicely formatted
version of the <citerefentry>
<refentrytitle>ls</refentrytitle></citerefentry> manual
version of the &man.ls.1; manual
page on the default printer:</para>
<screen>&prompt.user; <userinput>zcat /usr/share/man/man1/ls.1.gz | troff -t -man | lpr -t</userinput></screen>
<para>The <citerefentry>
<refentrytitle>zcat</refentrytitle></citerefentry>
<para>The &man.zcat.1;
command uncompresses the source of the</para>
<para><citerefentry>
<refentrytitle>ls</refentrytitle></citerefentry> manual
page and passes it to the <citerefentry>
<refentrytitle>troff</refentrytitle></citerefentry>
<para>&man.ls.1; manual
page and passes it to the &man.troff.1;
command, which formats that source and makes GNU troff output
and passes it to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>,
and passes it to &man.lpr.1;,
which submits the job to the LPD spooler. Because we used the
<option>-t</option> option to</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>, the
<para>&man.lpr.1;, the
spooler will convert the GNU troff output into a format the
default printer can understand when it prints the job.</para>
@ -2118,8 +2063,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-job-handling">
<title>Job Handling Options</title>
<para>The following options to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> tell
<para>The following options to &man.lpr.1; tell
LPD to handle the job specially:</para>
@ -2200,8 +2144,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-misc">
<title>Header Page Options</title>
<para>These options to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
<para>These options to &man.lpr.1;
adjust the text that normally appears on a job's header page.
If header pages are suppressed for the destination printer,
these options have no effect. See section <link
@ -2252,11 +2195,9 @@ cfA013rose dequeued
<title>Administrating Printers</title>
<para>As an administrator for your printers, you have had to
install, set up, and test them. Using the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
install, set up, and test them. Using the &man.lpc.8;
command, you can interact with your printers in yet more ways.
With <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>, you
With &man.lpc.8;, you
can</para>
@ -2290,14 +2231,11 @@ cfA013rose dequeued
in which case it will continue to print jobs in the queue until
the queue is empty.</para>
<para>In general, you have to have root privileges to use the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
command. Ordinary users can use the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> command
<para>In general, you have to have root privileges to use the &man.lpc.8;
command. Ordinary users can use the &man.lpc.8; command
to get printer status and to restart a hung printer only.</para>
<para>Here is a summary of the <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry>
<para>Here is a summary of the &man.lpc.8;
commands. Most of the commands takes a <replaceable>printer-name</replaceable> argument to tell on which
printer to operate. You can use <literal>all</literal>
for the <replaceable>printer-name</replaceable> to mean all
@ -2353,8 +2291,7 @@ cfA013rose dequeued
<command>disable</command> followed by
<command>stop</command>. The <replaceable>message</replaceable> appears as the printer's
status whenever a user checks the printer's queue with
<citerefentry>
<refentrytitle>lpq</refentrytitle></citerefentry>
&man.lpq.1;
or status with <command>lpc
status</command>.</para>
</listitem>
@ -2437,11 +2374,9 @@ cfA013rose dequeued
</variablelist>
<para><citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> accepts
<para>&man.lpc.8; accepts
the above commands on the command line. If you do not enter any
commands, <citerefentry>
<refentrytitle>lpc</refentrytitle></citerefentry> enters
commands, &man.lpc.8; enters
an interactive mode, where you can enter commands until you type
<command>exit</command>, <command>quit</command>, or end-of-file.</para>
@ -2570,10 +2505,8 @@ cfA013rose dequeued
<para>Which filter LPD starts and the filter's arguments depend on
what is listed in the <filename>/etc/printcap</filename> file
and what arguments the user specified for the job on the</para>
<para><citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
and what arguments the user specified for the job on the
&man.lpr.1;
command line. For example, if the user typed <command>lpr
-t</command>, LPD would start the troff filter, listed in the
<literal>tf</literal> capability for the destination
@ -2854,8 +2787,7 @@ fi</programlisting>
text-to-PostScript program you wish. The FreeBSD ports
collection (see <link linkend="ports">The Ports
Collection</link>) includes a full featured text-to-PostScript
program called <citerefentry>
<refentrytitle>a2ps</refentrytitle></citerefentry> that you might want to investigate.</para>
program called <literal>a2ps</literal> that you might want to investigate.</para>
</sect3>
@ -2886,10 +2818,9 @@ fi</programlisting>
<para>Here is an example: the following script is a text filter
for Hewlett Packard DeskJet 500 printers. For other printers,
substitute the <option>-sDEVICE</option> argument to the</para>
substitute the <option>-sDEVICE</option> argument to the
<para><citerefentry>
<refentrytitle>gs</refentrytitle></citerefentry> (Ghostscript) command. (Type <command>gs -h</command> to get a list of devices the current installation of Ghostscript supports.)</para>
<command>gs</command> (Ghostscript) command. (Type <command>gs -h</command> to get a list of devices the current installation of Ghostscript supports.)</para>
<programlisting>
#!/bin/sh
@ -3127,8 +3058,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
#
exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"</programlisting>
<para>This script runs <citerefentry>
<refentrytitle>dvips</refentrytitle></citerefentry> in filter mode (the <option>-f</option> argument) on standard input, which is the job to print. It then starts the PostScript printer filter <command>lprps</command> (see section <link linkend="printing-advanced-if-conversion">Accommodating Plain Text Jobs on PostScript
<para>This script runs <command>dvips</command> in filter mode (the <option>-f</option> argument) on standard input, which is the job to print. It then starts the PostScript printer filter <command>lprps</command> (see section <link linkend="printing-advanced-if-conversion">Accommodating Plain Text Jobs on PostScript
Printers</link>) with the arguments LPD passed to this script.
<command>lprps</command> will use those arguments
to account for the pages printed.</para>
@ -3238,17 +3168,13 @@ exit 2</programlisting>
<para>Now, for the hard part: making the filter. For that, we
need a DVI-to-LaserJet/PCL conversion program. The FreeBSD
ports collection (see <link linkend="ports">The
Ports Collection</link>) has one: <citerefentry>
<refentrytitle>dvi2xx</refentrytitle></citerefentry> is the
Ports Collection</link>) has one: <command>dvi2xx</command> is the
name of the package. Installing this package gives us the
program we need, <citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry>, which converts DVI into LaserJet IIp, LaserJet III, and LaserJet 2000 compatible codes.</para>
program we need, <command>dvilj2p</command>, which converts DVI into LaserJet IIp, LaserJet III, and LaserJet 2000 compatible codes.</para>
<para><citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> makes
<para><command>dvilj2p</command> makes
the filter <command>hpdf</command> quite complex since
<citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> cannot
<command>dvilj2p</command> cannot
read from standard input. It wants to work with a filename.
What is worse, the filename has to end in
<filename>.dvi</filename> so using
@ -3256,8 +3182,7 @@ exit 2</programlisting>
problematic. We can get around that problem by linking
(symbolically) a temporary file name (one that ends in
<filename>.dvi</filename>) to <filename>/dev/fd/0</filename>,
thereby forcing <citerefentry>
<refentrytitle>dvilj2p</refentrytitle></citerefentry> to read from standard input.</para>
thereby forcing <command>dvilj2p</command> to read from standard input.</para>
<para>The only other fly in the ointment is the fact that we
cannot use <filename>/tmp</filename> for the temporary link.
@ -3347,8 +3272,7 @@ exit 0</programlisting>
<para>All these conversion filters accomplish a lot for your
printing environment, but at the cost forcing the user to
specify (on the <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
specify (on the &man.lpr.1;
command line) which one to use. If your users are not
particularly computer literate, having to specify a filter
option will become annoying. What is worse, though, is that
@ -3366,8 +3290,8 @@ exit 0</programlisting>
you can still provide conversion filters just for them.</para>
<para>The FreeBSD ports collection has a text filter that
performs automatic conversion called <citerefentry>
<refentrytitle>apsfilter</refentrytitle></citerefentry>. It can detect plain text, PostScript, and DVI files, run the proper conversions, and print.</para>
performs automatic conversion called
<command>apsfilter</command>. It can detect plain text, PostScript, and DVI files, run the proper conversions, and print.</para>
</sect4>
</sect3>
@ -3565,8 +3489,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
they can suppress header pages by submitting the job with
<command>lpr -h</command>; see <link
linkend="printing-lpr-options-misc">Header Page
Options</link> for more <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
Options</link> for more &man.lpr.1;
options.</para>
<note>
@ -4175,8 +4098,7 @@ exit 0;</programlisting>
<para>If you feel multiple copies cause unnecessary wear and tear
on your printers, you can disable the <option>-#</option> option
to <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry> by
to &man.lpr.1; by
adding the <literal>sc</literal> capability to the
<filename>/etc/printcap</filename> file. When users submit jobs
with the <option>-#</option> option, they will see:</para>
@ -4235,8 +4157,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>By using the <literal>sc</literal>
capability, we prevent the use of <command>lpr -#</command>, but
that still does not prevent users from running <citerefentry>
<refentrytitle>lpr</refentrytitle></citerefentry>
that still does not prevent users from running &man.lpr.1;
multiple times, or from submitting the same file multiple times
in one job like this:</para>
@ -4397,10 +4318,8 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
per line. Note that the file
<filename>/etc/hosts.equiv</filename> is also used by
the
<citerefentry><refentrytitle>ruserok</refentrytitle><manvolnum>3</manvolnum></citerefentry> protocol, and affects programs like <citerefentry>
<refentrytitle>rsh</refentrytitle></citerefentry> and
<citerefentry>
<refentrytitle>rcp</refentrytitle></citerefentry>, so be careful.</para>
&man.ruserok.3; protocol, and affects programs like &man.rsh.1; and
&man.rcp.1;, so be careful.</para>
<para>For example, here is the
<filename>/etc/hosts.lpd</filename> file on the host
@ -4567,8 +4486,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
with simple periodic accounting right away. They are the text
filter <command>lpf</command>, described in section
<link linkend="printing-advanced-lpf">lpf: a Text
Filter</link>, and <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>, a
Filter</link>, and &man.pac.8;, a
program to gather and total entries from printer accounting
files.</para>
@ -4606,11 +4524,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<filename>acct</filename>.</para>
<para>When you are ready to charge users for printouts, run
the <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
the &man.pac.8;
program. Just change to the spooling directory for the printer
you want to collect on and type <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>. You
you want to collect on and type <literal>pac</literal>. You
will get a dollar-centric summary like the following:</para>
@ -4626,8 +4542,7 @@ rose:root 26.00 12 $ 0.52
total 337.00 154 $ 6.74</screen>
<para>These are the arguments <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
<para>These are the arguments &man.pac.8;
expects:</para>
<variablelist>
@ -4694,8 +4609,7 @@ total 337.00 154 $ 6.74</screen>
</varlistentry>
</variablelist>
<para>In the default summary that <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
<para>In the default summary that &man.pac.8;
produces, you see the number of pages printed by each user from
various hosts. If, at your site, host does not matter (because
users can use any host), run <command>pac -m</command>, to
@ -4713,15 +4627,13 @@ total 337.00 154 $ 6.74</screen>
<para>To compute the dollar amount due,
<citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry> uses
&man.pac.8; uses
the <literal>pc</literal> capability in the
<filename>/etc/printcap</filename> file (default of 200, or 2
cents per page). Specify, in hundredths of cents, the price per
page or per foot you want to charge for printouts in this
capability. You can override this value when you run
<citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry> with
&man.pac.8; with
the <option>-p</option> option. The units for the
<option>-p</option> option are in dollars, though, not
hundredths of cents. For example,
@ -4738,8 +4650,7 @@ total 337.00 154 $ 6.74</screen>
summary information in a summary accounting file, which is named
the same as the printer's accounting file, but with
<literal>_sum</literal> appended to the name. It then truncates
the accounting file. When you run <citerefentry>
<refentrytitle>pac</refentrytitle></citerefentry>
the accounting file. When you run &man.pac.8;
again, it rereads the summary file to get starting totals, then
adds information from the regular accounting file.</para>
@ -4768,10 +4679,9 @@ total 337.00 154 $ 6.74</screen>
<para>How do you handle other file formats, though?</para>
<para>Well, for DVI-to-LaserJet or DVI-to-PostScript conversion,
you can have your filter parse the diagnostic output of <citerefentry>
<refentrytitle>dvilj</refentrytitle></citerefentry> or
<citerefentry>
<refentrytitle>dvips</refentrytitle></citerefentry> and look to see how many pages were converted. You might be able to do similar things with other file formats and conversion programs.</para>
you can have your filter parse the diagnostic output of
<command>dvilj</command> or
<command>dvips</command> and look to see how many pages were converted. You might be able to do similar things with other file formats and conversion programs.</para>
<para>But these methods suffer from the fact that the printer may
not actually print all those pages. For example, it could jam,

16
en_US.ISO_8859-1/books/handbook/security/chapter.sgml
View file

@ -372,7 +372,7 @@ Reminder - Do not use this program while logged in via telnet or rlogin.
can be used to configure restrictions on the use of UNIX passwords
based on the host name, user name, terminal port, or IP address of
a login session. The complete format of the file is documented in
the <citerefentry><refentrytitle>skey.access</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page; there are
the &man.skey.access.5; manual page; there are
also some security cautions there which should be read before
depending on this file for security.</para>
@ -1044,7 +1044,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<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,
<citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Together, they allow you to define and
&man.ipfw.8;. Together, they allow you to define and
query the rules currently used by the kernel in its routing
decisions.</para>
@ -1091,7 +1091,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Enables code to allow logging of packets through
<citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Without this option, even
&man.syslogd.8;. Without this option, even
if you specify that packets should be logged in the filter
rules, nothing will happen.</para>
</listitem>
@ -1101,7 +1101,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Limits the number of packets logged through
<citerefentry><refentrytitle>syslogd</refentrytitle><manvolnum>8</manvolnum></citerefentry> on a per entry basis. You
&man.syslogd.8; on a per entry basis. You
may wish to use this option in hostile environments in
which you want to log firewall activity, but do not want
to be open to a denial of service attack via syslog
@ -1110,7 +1110,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<para>When a chain entry reaches the packet limit specified,
logging is turned off for that particular entry. To
resume logging, you will need to reset the associated
counter using the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry>
counter using the &man.ipfw.8;
utility:</para>
@ -1135,7 +1135,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<title>Configuring IPFW</title>
<para>The configuration of the <application>IPFW</application> software is
done through the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry> utility. The syntax
done through the &man.ipfw.8; utility. The syntax
for this command looks quite complicated, but it is relatively
simple once you understand its structure.</para>
@ -1443,7 +1443,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<literal>5</literal> redirect, <literal>8</literal> echo request (ping request), and
<literal>11</literal> time exceeded (used to
indicate TTL expiration as with
<citerefentry><refentrytitle>traceroute</refentrytitle><manvolnum>8</manvolnum></citerefentry>).</para>
&man.traceroute.8;).</para>
</listitem>
</varlistentry>
</variablelist>
@ -1480,7 +1480,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>Display the last match times for each chain entry.
The time listing is incompatible with the input syntax
used by the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry> utility.</para>
used by the &man.ipfw.8; utility.</para>
</listitem>
</varlistentry>

28
en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml
View file

@ -381,7 +381,7 @@
</itemizedlist>
<para>See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for more information.</para>
<para>See the &man.sio.4; manual page for more information.</para>
<para>If you have connected a terminal to the first serial port
(<devicename>COM1</devicename> in DOS parlance), then you want to use
@ -451,7 +451,7 @@
<replaceable>getty</replaceable> type for use in step 2 by making an
entry in <filename>/etc/gettytab</filename>. This document does
not explain how to do so; you are encouraged to see the
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> and the <citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual pages for more
man.gettytab.5; and the &man.getty.8; manual pages for more
information.</para>
<para>The remaining sections detail how to do these steps. We will
@ -463,7 +463,7 @@
port on a multiport serial card).</para>
<para>For more information on the <filename>/etc/ttys</filename>
file, see the <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page.</para>
file, see the &man.ttys.5; manual page.</para>
<sect3 id="term-etcttys">
@ -523,7 +523,7 @@ ttyd5</programlisting>
cases, the entries that start with the text <literal>std</literal> will work for hardwired terminals.
These entries ignore parity. There is a <literal>std</literal> entry for each bps rate from 110 to
115200. Of course, you can add your own entries to this file.
The manual page <citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> provides more information.</para>
The manual page &man.gettytab.5; provides more information.</para>
<para>When setting the <replaceable>getty</replaceable> type in
the <filename>/etc/ttys</filename> file, make sure that the
@ -566,7 +566,7 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
<para>To find out what terminal types FreeBSD supports, see the
file <filename>/usr/share/misc/termcap</filename>. It lists
about 600 terminal types. You can add more if you wish. See
the <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page for information.</para>
the &man.termcap.5; manual page for information.</para>
<para>In our example, the Wyse-50 is a Wyse-50 type of terminal
(although it can emulate others, we will leave it in Wyse-50
@ -1029,7 +1029,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<devicename>COM1:</devicename>, <devicename>COM2:</devicename>,
<devicename>COM3:</devicename>, and <devicename>COM4:</devicename>. FreeBSD can presently also handle
&ldquo;dumb&rdquo; multiport serial interface cards, such as the Boca Board
1008 and 2016 (please see the manual page <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for kernel configuration information
1008 and 2016 (please see the manual page &man.sio.4; for kernel configuration information
if you have a multiport serial card). The default kernel only
looks for the standard COM ports, though.</para>
@ -1089,7 +1089,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>You can comment-out or completely remove lines for devices you
do not have. If you have a multiport serial board, such as the
Boca Board BB2016, please see the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> man page for complete information on
Boca Board BB2016, please see the &man.sio.4; man page for complete information on
how to write configuration lines for multiport boards. Be careful
if you are using a configuration file that was previously used for
a different version of FreeBSD because the device flags have
@ -1112,7 +1112,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>When you are finished adjusting the kernel configuration file,
use the program <command>config</command> as documented
in &ldquo;Building Berkeley Kernels with Config&rdquo; and the
<citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual page to prepare a kernel
&man.config.8; manual page to prepare a kernel
building directory, then build, install, and test the new
kernel.</para>
@ -1136,7 +1136,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
modems which use <literal>CTS/RTS</literal> signaling for flow
control. The locking devices are used to lock flags on ports to
prevent users or programs changing certain parameters; see the
manual pages <citerefentry><refentrytitle>termios</refentrytitle><manvolnum>4</manvolnum></citerefentry>, <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry>, and <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
manual pages &man.termios.4;, &man.sio.4;, and &man.stty.1; for
information on the terminal settings, locking &amp; initializing
devices, and setting terminal options, respectively.</para>
@ -1146,7 +1146,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<para>A shell script called <command>MAKEDEV</command> in the
<filename>/dev</filename> directory manages the device special
files. (The manual page for <citerefentry><refentrytitle>MAKEDEV</refentrytitle><manvolnum>8</manvolnum></citerefentry> on
files. (The manual page for &man.MAKEDEV.8; on
FreeBSD 1.1.5 is fairly bogus in its discussion of
<acronym>COM</acronym> ports, so ignore it.) To use
<command>MAKEDEV</command> to make dialup device special files
@ -1237,9 +1237,9 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
<sect3>
<title><filename>/etc/gettytab</filename></title>
<para><filename>/etc/gettytab</filename> is a <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry>-style file of configuration
information for <citerefentry><refentrytitle>getty</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Please see the
<citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page for
<para><filename>/etc/gettytab</filename> is a &man.termcap.5;-style file of configuration
information for &man.getty.8;. Please see the
&man.gettytab.5; manual page for
complete information on the format of the file and the list of
capabilities.</para>
@ -1348,7 +1348,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
information to <command>login</command> (user
<username>root</username> may only login on ttys marked
<literal>secure</literal>). See the manual page for
<citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more
&man.ttys.5; for more
information.</para>
<para>You will need to either modify existing lines in

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

@ -522,7 +522,7 @@ do-install:
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
the <citerefentry><refentrytitle>pkg_add</refentrytitle><manvolnum>1</manvolnum></citerefentry> program to install a
the &man.pkg.add.1; program to install a
package file on your system.</para>
</listitem>
@ -1170,7 +1170,7 @@ lib/X11/oneko/cat2.xpm
lib/X11/oneko/mouse.xpm
@dirrm lib/X11/oneko</programlisting>
<para>Refer to the <citerefentry><refentrytitle>pkg_create</refentrytitle><manvolnum>1</manvolnum></citerefentry> man page
<para>Refer to the &man.pkg.create.1; man page
for details on the packing list.</para>
<note>
@ -1290,19 +1290,10 @@ lib/X11/oneko/mouse.xpm
<filename>pkgname.tgz</filename> package, so delete them
now. Next, simply include the output of <command>shar `find
port_dir`</command> in a bug report and send it with the
<citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> program (see <link linkend="contrib-general">Bug
&man.send-pr.1; program (see <link linkend="contrib-general">Bug
Reports and General Commentary</link> for more information
about <citerefentry>
<refentrytitle>send-pr</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry>. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use <citerefentry>
<refentrytitle>uuencode</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> before including it in the bug report (uuencoded
about &man.send-pr.1;. If the uncompressed port is larger than
20KB, you should compress it into a tarfile and use &man.uuencode.1; before including it in the bug report (uuencoded
tarfiles are acceptable even if the bug report is smaller than
20KB but are not preferred). Be sure to classify the bug report as
category <literal>ports</literal> and class
@ -2805,9 +2796,7 @@ diff -u -r1.15 PLIST
POST-INSTALL</literal>. <literal>&dollar;2</literal> can be
tested to determine which mode the script is being run in. The
<envar>PKG_PREFIX</envar> environmental variable will be set to
the package installation directory. See <citerefentry>
<refentrytitle>pkg_add</refentrytitle>
<manvolnum>1</manvolnum></citerefentry> for additional
the package installation directory. See &man.pkg.add.1; for additional
information.</para>
<note>
@ -3045,7 +3034,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<command>diff -ruN superedit.bak
superedit</command>). Please examine the output to make
sure all the changes make sense. The best way to send us the
diff is by including it to <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
diff is by including it to &man.send-pr.1;
(category <literal>ports</literal>). Please mention any added or deleted files
in the message, as they have to be explicitly specified to CVS
when doing a commit. If the diff is more than about 20KB, please
@ -3053,7 +3042,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
the PR.</para>
<para>Once again, please use
<citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> and not <citerefentry><refentrytitle>shar</refentrytitle><manvolnum>1</manvolnum></citerefentry> to send updates to ports.</para>
&man.diff.1; and not &man.shar.1; to send updates to ports.</para>
</sect2>
<sect2>
@ -3080,10 +3069,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
post-install:
strip ${PREFIX}/bin/xdl</programlisting>
<para>Use the <citerefentry>
<refentrytitle>file</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> command on the installed executable to check
<para>Use the &man.file.1; command on the installed executable to check
whether the binary is stripped or not. If it does not say
<literal>not stripped</literal>, it is stripped.</para>
</sect3>
@ -3788,7 +3774,7 @@ post-install:
(executables for superusers/managers),
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
files). See man &man.hier.7; for
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use

4
share/sgml/catalog
View file

@ -1,4 +1,2 @@
-- Catalog file for FreeBSD Extended DocBook DTD --
PUBLIC "-//FreeBSD//DTD DocBook V3.0-Based Extension//EN" "freebsd.dtd"
PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN" "man-refs.ent"

117
share/sgml/man-refs.ent Normal file
View file

@ -0,0 +1,117 @@
<!--
Names of Unix manual pages. Syntactic sugar making it easier to
pretty print the SGML source.
"_" is not a valid character in an entity name, so use "." instead.
This runs the risk that two manual pages, one for "foo_bar" and one
for "foo.bar" would exist. Hopefully the chance of this is
sufficiently small that it is not an issue.
$Id: man-refs.ent,v 1.1 1999-03-07 16:32:22 nik Exp $
-->
<!ENTITY man.brandelf.1 "<citerefentry/<refentrytitle/brandelf/<manvolnum/1//">
<!ENTITY man.chmod.1 "<citerefentry/<refentrytitle/chmod/<manvolnum/1//">
<!ENTITY man.cpio.1 "<citerefentry/<refentrytitle/cpio/<manvolnum/1//">
<!ENTITY man.ctm.rmail.1 "<citerefentry/<refentrytitle/ctm.rmail/<manvolnum/1//">
<!ENTITY man.cvs.1 "<citerefentry/<refentrytitle/cvs/<manvolnum/1//">
<!ENTITY man.cvsup.1 "<citerefentry/<refentrytitle/cvsup/<manvolnum/1//">
<!ENTITY man.diff.1 "<citerefentry/<refentrytitle/diff/<manvolnum/1//">
<!ENTITY man.file.1 "<citerefentry/<refentrytitle/file/<manvolnum/1//">
<!ENTITY man.info.1 "<citerefentry/<refentrytitle/info/<manvolnum/1//">
<!ENTITY man.ipcs.1 "<citerefentry/<refentrytitle/ipcs/<manvolnum/1//">
<!ENTITY man.ldd.1 "<citerefentry/<refentrytitle/ldd/<manvolnum/1//">
<!ENTITY man.ln.1 "<citerefentry/<refentrytitle/ln/<manvolnum/1//">
<!ENTITY man.lpq.1 "<citerefentry/<refentrytitle/lpq/<manvolnum/1//">
<!ENTITY man.lpr.1 "<citerefentry/<refentrytitle/lpr/<manvolnum/1//">
<!ENTITY man.lprm.1 "<citerefentry/<refentrytitle/lprm/<manvolnum/1//">
<!ENTITY man.lptest.1 "<citerefentry/<refentrytitle/lptest/<manvolnum/1//">
<!ENTITY man.ls.1 "<citerefentry/<refentrytitle/ls/<manvolnum/1//">
<!ENTITY man.mkdir.1 "<citerefentry/<refentrytitle/mkdir/<manvolnum/1//">
<!ENTITY man.mt.1 "<citerefentry/<refentrytitle/mt/<manvolnum/1//">
<!ENTITY man.patch.1 "<citerefentry/<refentrytitle/patch/<manvolnum/1//">
<!ENTITY man.pax.1 "<citerefentry/<refentrytitle/pax/<manvolnum/1//">
<!ENTITY man.pkg.add.1 "<citerefentry/<refentrytitle/pkg.add/<manvolnum/1//">
<!ENTITY man.pkg.create.1 "<citerefentry/<refentrytitle/pkg.create/<manvolnum/1//">
<!ENTITY man.pr.1 "<citerefentry/<refentrytitle/pr/<manvolnum/1//">
<!ENTITY man.ps.1 "<citerefentry/<refentrytitle/ps/<manvolnum/1//">
<!ENTITY man.rcp.1 "<citerefentry/<refentrytitle/rcp/<manvolnum/1//">
<!ENTITY man.rsh.1 "<citerefentry/<refentrytitle/rsh/<manvolnum/1//">
<!ENTITY man.send-pr.1 "<citerefentry/<refentrytitle/send-pr/<manvolnum/1//">
<!ENTITY man.shar.1 "<citerefentry/<refentrytitle/shar/<manvolnum/1//">
<!ENTITY man.size.1 "<citerefentry/<refentrytitle/size/<manvolnum/1//">
<!ENTITY man.stty.1 "<citerefentry/<refentrytitle/stty/<manvolnum/1//">
<!ENTITY man.su.1 "<citerefentry/<refentrytitle/su/<manvolnum/1//">
<!ENTITY man.tar.1 "<citerefentry/<refentrytitle/tar/<manvolnum/1//">
<!ENTITY man.tcpdump.1 "<citerefentry/<refentrytitle/tcpdump/<manvolnum/1//">
<!ENTITY man.tip.1 "<citerefentry/<refentrytitle/tip/<manvolnum/1//">
<!ENTITY man.troff.1 "<citerefentry/<refentrytitle/troff/<manvolnum/1//">
<!ENTITY man.uuencode.1 "<citerefentry/<refentrytitle/uuencode/<manvolnum/1//">
<!ENTITY man.zcat.1 "<citerefentry/<refentrytitle/zcat/<manvolnum/1//">
<!ENTITY man.chmod.2 "<citerefentry/<refentrytitle/chmod/<manvolnum/2//">
<!ENTITY man.cgetent.3 "<citerefentry/<refentrytitle/cgetent/<manvolnum/3//">
<!ENTITY man.rcmd.3 "<citerefentry/<refentrytitle/rcmd/<manvolnum/3//">
<!ENTITY man.ruserok.3 "<citerefentry/<refentrytitle/ruserok/<manvolnum/3//">
<!ENTITY man.setlocale.3 "<citerefentry/<refentrytitle/setlocale/<manvolnum/3//">
<!ENTITY man.ccd.4 "<citerefentry/<refentrytitle/ccd/<manvolnum/4//">
<!ENTITY man.ddb.4 "<citerefentry/<refentrytitle/ddb/<manvolnum/4//">
<!ENTITY man.lkm.4 "<citerefentry/<refentrytitle/lkm/<manvolnum/4//">
<!ENTITY man.sio.4 "<citerefentry/<refentrytitle/sio/<manvolnum/4//">
<!ENTITY man.st.4 "<citerefentry/<refentrytitle/st/<manvolnum/4//">
<!ENTITY man.termios.4 "<citerefentry/<refentrytitle/termios/<manvolnum/4//">
<!ENTITY man.fstab.5 "<citerefentry/<refentrytitle/fstab/<manvolnum/5//">
<!ENTITY man.gettytab.5 "<citerefentry/<refentrytitle/gettytab/<manvolnum/5//">
<!ENTITY man.login.conf.5 "<citerefentry/<refentrytitle/login.conf/<manvolnum/5//">
<!ENTITY man.passwd.5 "<citerefentry/<refentrytitle/passwd/<manvolnum/5//">
<!ENTITY man.printcap.5 "<citerefentry/<refentrytitle/printcap/<manvolnum/5//">
<!ENTITY man.skey.access.5 "<citerefentry/<refentrytitle/skey.access/<manvolnum/5//">
<!ENTITY man.syslog.conf.5 "<citerefentry/<refentrytitle/syslog.conf/<manvolnum/5//">
<!ENTITY man.termcap.5 "<citerefentry/<refentrytitle/termcap/<manvolnum/5//">
<!ENTITY man.ttys.5 "<citerefentry/<refentrytitle/ttys/<manvolnum/5//">
<!ENTITY man.hier.7 "<citerefentry/<refentrytitle/hier/<manvolnum/7//">
<!ENTITY man.MAKEDEV.8 "<citerefentry/<refentrytitle/MAKEDEV/<manvolnum/8//">
<!ENTITY man.adduser.8 "<citerefentry/<refentrytitle/adduser/<manvolnum/8//">
<!ENTITY man.arp.8 "<citerefentry/<refentrytitle/arp/<manvolnum/8//">
<!ENTITY man.ccdconfig.8 "<citerefentry/<refentrytitle/ccdconfig/<manvolnum/8//">
<!ENTITY man.chat.8 "<citerefentry/<refentrytitle/chat/<manvolnum/8//">
<!ENTITY man.config.8 "<citerefentry/<refentrytitle/config/<manvolnum/8//">
<!ENTITY man.cron.8 "<citerefentry/<refentrytitle/cron/<manvolnum/8//">
<!ENTITY man.disklabel.8 "<citerefentry/<refentrytitle/disklabel/<manvolnum/8//">
<!ENTITY man.dmesg.8 "<citerefentry/<refentrytitle/dmesg/<manvolnum/8//">
<!ENTITY man.dump.8 "<citerefentry/<refentrytitle/dump/<manvolnum/8//">
<!ENTITY man.dumpon.8 "<citerefentry/<refentrytitle/dumpon/<manvolnum/8//">
<!ENTITY man.fdisk.8 "<citerefentry/<refentrytitle/fdisk/<manvolnum/8//">
<!ENTITY man.ft.8 "<citerefentry/<refentrytitle/ft/<manvolnum/8//">
<!ENTITY man.getty.8 "<citerefentry/<refentrytitle/getty/<manvolnum/8//">
<!ENTITY man.init.8 "<citerefentry/<refentrytitle/init/<manvolnum/8//">
<!ENTITY man.ipfw.8 "<citerefentry/<refentrytitle/ipfw/<manvolnum/8//">
<!ENTITY man.lpc.8 "<citerefentry/<refentrytitle/lpc/<manvolnum/8//">
<!ENTITY man.lptcontrol.8 "<citerefentry/<refentrytitle/lptcontrol/<manvolnum/8//">
<!ENTITY man.modload.8 "<citerefentry/<refentrytitle/modload/<manvolnum/8//">
<!ENTITY man.mount.8 "<citerefentry/<refentrytitle/mount/<manvolnum/8//">
<!ENTITY man.mount.msdos.8 "<citerefentry/<refentrytitle/mount.msdos/<manvolnum/8//">
<!ENTITY man.newfs.8 "<citerefentry/<refentrytitle/newfs/<manvolnum/8//">
<!ENTITY man.pac.8 "<citerefentry/<refentrytitle/pac/<manvolnum/8//">
<!ENTITY man.ping.8 "<citerefentry/<refentrytitle/ping/<manvolnum/8//">
<!ENTITY man.pppctl.8 "<citerefentry/<refentrytitle/pppctl/<manvolnum/8//">
<!ENTITY man.pw.8 "<citerefentry/<refentrytitle/pw/<manvolnum/8//">
<!ENTITY man.rdump.8 "<citerefentry/<refentrytitle/rdump/<manvolnum/8//">
<!ENTITY man.restore.8 "<citerefentry/<refentrytitle/restore/<manvolnum/8//">
<!ENTITY man.rrestore.8 "<citerefentry/<refentrytitle/rrestore/<manvolnum/8//">
<!ENTITY man.savecore.8 "<citerefentry/<refentrytitle/savecore/<manvolnum/8//">
<!ENTITY man.scsi.8 "<citerefentry/<refentrytitle/scsi/<manvolnum/8//">
<!ENTITY man.sliplogin.8 "<citerefentry/<refentrytitle/sliplogin/<manvolnum/8//">
<!ENTITY man.swapon.8 "<citerefentry/<refentrytitle/swapon/<manvolnum/8//">
<!ENTITY man.syslogd.8 "<citerefentry/<refentrytitle/syslogd/<manvolnum/8//">
<!ENTITY man.traceroute.8 "<citerefentry/<refentrytitle/traceroute/<manvolnum/8//">
<!ENTITY man.vipw.8 "<citerefentry/<refentrytitle/vipw/<manvolnum/8//">
<!ENTITY man.vmstat.8 "<citerefentry/<refentrytitle/vmstat/<manvolnum/8//">
<!ENTITY man.vnconfig.8 "<citerefentry/<refentrytitle/vnconfig/<manvolnum/8//">
<!ENTITY man.watch.8 "<citerefentry/<refentrytitle/watch/<manvolnum/8//">