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

Use the correct ISO entities for dashes. According to a TeX manual I have

Browse source 
kicking around here,

    daughter-in-law, X-rated    = hyphen      =  -
    pages 13--67                = en-dash     = –
    yes---or no?                = em-dash     = —
    0, 1, and -1                = minus sign  = −
This commit is contained in:
Nik Clayton 1998-10-26 23:51:03 +00:00
parent aefedf6246
commit 950e361ac7
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=3679
4 changed files with 279 additions and 270 deletions
Download patch file Download diff file Expand all files Collapse all files

9
en/handbook/README
View file

@ -484,3 +484,12 @@ for example,
\s-+</title> -> </title>
<title>\s-+ -> <title>
48. Use the correct ISO entities for dashes. According to a TeX manual I have
kicking around here,
daughter-in-law, X-rated = hyphen = -
pages 13--67 = en-dash = &ndash;
yes---or no? = em-dash = &mdash;
0, 1, and -1 = minus sign = &minus;

180
en/handbook/handbook.sgml
View file

@ -731,7 +731,7 @@
<para>If either of the two proceeding methods work then you
can simply skip the rest of this section, otherwise your
final option is to create a boot floppy from the
<filename>floppies\boot.flp</filename> image - proceed to
<filename>floppies\boot.flp</filename> image&mdash;proceed to
step 4 for instructions on how to do this.</para>
</listitem>
@ -1489,7 +1489,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent
<para>For as many <abbrev>DISTS</abbrev> you wish to install from MS-DOS (and you
have free space for), install each one under
<filename>C:\FREEBSD</filename> - the <abbrev>BIN</abbrev> dist
<filename>C:\FREEBSD</filename> &mdash; the <abbrev>BIN</abbrev> dist
is only the minimal requirement.</para>
</sect2>
@ -2520,16 +2520,16 @@ do-install:
<itemizedlist>
<listitem>
<para><filename>COMMENT</filename> - a one-line description of
<para><filename>COMMENT</filename> &mdash; a one-line description of
the program.</para>
</listitem>
<listitem>
<para><filename>DESCR</filename> - a more detailed description.</para>
<para><filename>DESCR</filename> &mdash; a more detailed description.</para>
</listitem>
<listitem>
<para><filename>PLIST</filename> - a list of all the files
<para><filename>PLIST</filename> &mdash; a list of all the files
that will be created when the program is installed.</para>
</listitem>
@ -2562,7 +2562,7 @@ do-install:
</listitem>
<listitem>
<para>Forget it. This is the easiest for most - very few of the
<para>Forget it. This is the easiest for most &mdash; very few of the
programs in ports can be classified as essential!</para>
</listitem>
@ -2646,7 +2646,7 @@ do-install:
<listitem>
<para>You might have opinions on how a program should be
compiled that differ from the person who did the package
- some people have strong views on what optimisation
&mdash; some people have strong views on what optimisation
setting should be used, whether to build debug versions
and then strip them or not, etc. etc.</para>
</listitem>
@ -2735,7 +2735,7 @@ do-install:
<para>A. The licensing terms for kermit do not allow us to put
the tarball for it on the CDROM, so you will have to fetch it
by hand - sorry! The reason why you got all those error
by hand &mdash; sorry! The reason why you got all those error
messages was because you were not connected to the Internet at
the time. Once you have downloaded it from any of the sites
above, you can re-start the process (try and choose the
@ -2822,7 +2822,7 @@ do-install:
&prompt.root; <userinput>make fetch</userinput></screen>
</informalexample>
<para>and for just one port - well, I think you have guessed
<para>and for just one port &mdash; well, I think you have guessed
already.</para>
</listitem>
@ -2910,7 +2910,7 @@ do-install:
port. What's going on?</para>
<para>A. The <literal>foo</literal> port needs something that is supplied with
<literal>bar</literal> - for instance, if <literal>foo</literal> uses graphics, <literal>bar</literal> might have
<literal>bar</literal> &mdash; for instance, if <literal>foo</literal> uses graphics, <literal>bar</literal> might have
a library with useful graphics processing routines. Or <literal>bar</literal>
might be a tool that is needed to compile the <literal>foo</literal>
port.</para>
@ -3974,7 +3974,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
of different machines over the network, where the
<filename>termcap</filename> or
<filename>terminfo</filename> entries for the <devicename>sc0</devicename> device are often not available
-- <literal>vt100</literal> should be available on virtually any
&mdash; <literal>vt100</literal> should be available on virtually any
platform.</para>
@ -6761,8 +6761,8 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<listitem>
<para>If you do not need two-way communication and can pick
parallel or serial, prefer the parallel interface. It
keeps a serial port free for other peripherals---such as a
terminal or a modem---and is faster most of the time. It
keeps a serial port free for other peripherals&mdash;such as a
terminal or a modem&mdash;and is faster most of the time. It
is also easier to configure.</para>
</listitem>
@ -7395,7 +7395,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none
print jobs in the printer language <emphasis>and</emphasis>
print plain text jobs, you are strongly urged to add an
additional step to the simple setup outlined above: install an
automatic plain-text--to--PostScript (or other printer language)
automatic plain-text-to-PostScript (or other printer language)
conversion program. Section <xref
linkend="printing-advanced-if-conversion" remap="Accommodating
Plain Text Jobs on PostScript Printers"> tells how to do
@ -8975,7 +8975,7 @@ cfA013rose dequeued
<emphasis>filters</emphasis>. Filters are programs that
communicate with the printer and handle its device dependencies
and special requirements. In the simple printer setup, we
installed a plain text filter---an extremely simple one that
installed a plain text filter&mdash;an extremely simple one that
should work with most printers (section <xref
linkend="printing-textfilter" remap="Installing the
Text Filter">).</para>
@ -9902,7 +9902,7 @@ exit 0
then automatically run the right conversion filter. Tools
such as <command>file</command> can be of help
here. Of course, it will be hard to determine the differences
between <emphasis>some</emphasis> file types---and, of course,
between <emphasis>some</emphasis> file types&mdash;and, of course,
you can still provide conversion filters just for them.</para>
<para>The FreeBSD ports collection has a text filter that
@ -10285,7 +10285,7 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995
<para>As described above, LPD can generate a plain text header
page suitable for many printers. Of course, PostScript cannot
directly print plain text, so the header page feature of LPD is
useless---or mostly so.</para>
useless&mdash;or mostly so.</para>
<para>One obvious way to get header pages is to have every
conversion filter and the text filter generate the header page.
@ -11074,7 +11074,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>So, you need to charge for printouts. And why not? Paper
and ink cost money. And then there are maintenance
costs---printers are loaded with moving parts and tend to break
costs&mdash;printers are loaded with moving parts and tend to break
down. You have examined your printers, usage patterns, and
maintenance fees and have come up with a per-page (or per-foot,
per-meter, or per-whatever) cost. Now, how do you actually start
@ -11354,7 +11354,7 @@ total 337.00 154 $ 6.74</screen>
<para>But these methods suffer from the fact that the printer may
not actually print all those pages. For example, it could jam,
run out of toner, or explode---and the user would still get
run out of toner, or explode&mdash;and the user would still get
charged.</para>
<para>So, what can you do?</para>
@ -11389,7 +11389,7 @@ total 337.00 154 $ 6.74</screen>
FreeBSD)?</quote></para>
<para>Unfortunately, I have located only <emphasis>two</emphasis>
alternatives---and they are almost identical to each other! They
alternatives&mdash;and they are almost identical to each other! They
are:</para>
<variablelist>
@ -11932,7 +11932,7 @@ Disk quotas for user test (uid 1002):
drives (though I believe they all ultimately come from Phillips
anyway): The Phillips CDD 522 (Acts like a Plasmon), the PLASMON
RF4100 and the HP 6020i. I myself use the HP 6020i for burning
CDROMs (with 2.2-current - it does not work with 2.1.5 or
CDROMs (with 2.2-current &mdash; it does not work with 2.1.5 or
earlier releases of the SCSI code) and it works very well. See
<ulink
URL="file:/usr/share/examples/worm">/usr/share/examples/worm</ulink> on your 2.2 system for example scripts used to created ISO9660 filesystem images (with RockRidge extensions) and burn them onto an HP6020i CDR.</para>
@ -11964,7 +11964,7 @@ Disk quotas for user test (uid 1002):
URL="http://www.matrox.com/mgaweb/brochure.htm">Millenium</ulink> card. Note that support for this card is also excellent with the <ulink URL="http://www.xfree86.org/">XFree86</ulink> server, which is now at version 3.3.2.</para>
<para>You also certainly can't go wrong with one of <ulink
URL="http://www.nine.com/">Number 9's</ulink> cards - their S3
URL="http://www.nine.com/">Number 9's</ulink> cards &mdash; their S3
Vision 868 and 968 based cards (the 9FX series) also being quite
fast and very well supported by XFree86's S3 server.</para>
@ -12043,7 +12043,7 @@ Disk quotas for user test (uid 1002):
id="hw-vgrabbers">
<title>Video</title>
<para>For video capture, there are two good choices - any card
<para>For video capture, there are two good choices &mdash; any card
based on the Brooktree BT848 chip, such as the Hauppage or WinTV
boards, will work very nicely with FreeBSD. Another board which
works for me is the <ulink
@ -14452,7 +14452,7 @@ device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr
</orderedlist>
<para>One important note - the actual UART chips for the Boca 16
<para>One important note &mdash; the actual UART chips for the Boca 16
are in the connector box, not on the internal board itself. So
if you have it unplugged, probes of those ports will fail. I
have never tested booting with the box unplugged and plugging
@ -16238,7 +16238,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
</listitem>
<listitem>
<para>Small Computer System Interface - 2 (SCSI-2)
<para>Small Computer System Interface &mdash; 2 (SCSI-2)
[X3.131-1994] (<emphasis>Approved</emphasis>)</para>
</listitem>
@ -18718,7 +18718,7 @@ XkbKeymap "xfree86(ru)"
<title>Cables</title>
<para>Because terminals use serial ports, you need to use
serial---also known as RS-232C---cables to connect the terminal
serial&mdash;also known as RS-232C&mdash;cables to connect the terminal
to the FreeBSD system.</para>
<para>There are a couple of kinds of serial cables. Which one
@ -18941,7 +18941,7 @@ XkbKeymap "xfree86(ru)"
<para>This section describes what you need to configure on your
FreeBSD system to enable a login session on a terminal. It
assumes you have already configured your kernel to support the
serial port to which the terminal is connected---and that you have
serial port to which the terminal is connected&mdash;and that you have
connected it.</para>
<para>In a nutshell, you need to tell the <command>init</command> process, which is responsible for
@ -19079,8 +19079,8 @@ ttyd1 "/usr/libexec/getty std.38400" unknown off secure
ttyd5 "/usr/libexec/getty std.19200"
</programlisting>
<para>Note that the second field---where we specify
what program to run---appears in quotes. This is important,
<para>Note that the second field&mdash;where we specify
what program to run&mdash;appears in quotes. This is important,
otherwise the type argument to <command>getty</command> might be interpreted as the next
field.</para>
@ -19351,7 +19351,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
<variablelist>
<varlistentry><term>bps</term>
<listitem>
<para>Bits per Second - the rate at which data is
<para>Bits per Second &mdash; the rate at which data is
transmitted</para>
</listitem>
</varlistentry>
@ -19359,7 +19359,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
<varlistentry><term>DTE</term>
<listitem>
<para>Data Terminal Equipment - for example, your
<para>Data Terminal Equipment &mdash; for example, your
computer</para>
</listitem>
</varlistentry>
@ -19367,7 +19367,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
<varlistentry><term>DCE</term>
<listitem>
<para>Data Communications Equipment - your modem</para>
<para>Data Communications Equipment &mdash; your modem</para>
</listitem>
</varlistentry>
@ -19442,7 +19442,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
</itemizedlist>
<para>The first, connecting your modem, is usually simple - most
<para>The first, connecting your modem, is usually simple &mdash; most
straight-through serial cables work without any problems. You
need to have a cable with appropriate connectors (DB-25 or DB-9,
male or female) on each end, and the cable must be a DCE-to-DTE
@ -19716,7 +19716,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr
permissions on the files (especially the
<filename>/dev/cua*</filename> files) to make sure that only
users who should have access to those device special files can
read &amp; write on them - you probably do not want to allow
read &amp; write on them &mdash; you probably do not want to allow
your average user to use your modems to dialout. The default
permissions on the <filename>/dev/cua*</filename> files should
be sufficient:</para>
@ -19917,7 +19917,7 @@ ttyd0 "/usr/libexec/getty xxx" dialup on
</programlisting>
<para>The first item in the above line is the device special file
for this entry - <literal>ttyd0</literal> means
for this entry &mdash; <literal>ttyd0</literal> means
<filename>/dev/ttyd0</filename> is the file that this <command>getty</command> will be watching. The second item,
<literal>"/usr/libexec/getty
<replaceable>xxx</replaceable>"</literal>
@ -20108,7 +20108,7 @@ AT&amp;C1&amp;D2&amp;H1&amp;I0&amp;R2&amp;W
<itemizedlist>
<listitem>
<para>Switch 1: UP - DTR Normal</para>
<para>Switch 1: UP &mdash; DTR Normal</para>
</listitem>
<listitem>
@ -20117,23 +20117,23 @@ AT&amp;C1&amp;D2&amp;H1&amp;I0&amp;R2&amp;W
</listitem>
<listitem>
<para>Switch 3: UP - Suppress Result Codes</para>
<para>Switch 3: UP &mdash; Suppress Result Codes</para>
</listitem>
<listitem>
<para>Switch 4: DOWN - No echo, offline commands</para>
<para>Switch 4: DOWN &mdash; No echo, offline commands</para>
</listitem>
<listitem>
<para>Switch 5: UP - Auto Answer</para>
<para>Switch 5: UP &mdash; Auto Answer</para>
</listitem>
<listitem>
<para>Switch 6: UP - Carrier Detect Normal</para>
<para>Switch 6: UP &mdash; Carrier Detect Normal</para>
</listitem>
<listitem>
<para>Switch 7: UP - Load NVRAM Defaults</para>
<para>Switch 7: UP &mdash; Load NVRAM Defaults</para>
</listitem>
<listitem>
@ -20218,7 +20218,7 @@ AT&amp;B2&amp;W
and, if your modem has status indication lights, watch to see
whether the modem's <abbrev>DTR</abbrev> indicator lights when
the <prompt>login:</prompt> prompt appears on the
system's console - if it lights up, that should mean that
system's console &mdash; if it lights up, that should mean that
FreeBSD has started a <command>getty</command>
process on the appropriate communications port and is waiting
for the modem to accept a call.</para>
@ -20387,7 +20387,7 @@ AT&amp;B2&amp;W
<filename>/etc/remote</filename> file.</para>
<para>The Hayes driver is not smart enough to recognize some of the
advanced features of newer modems--messages like
advanced features of newer modems&mdash;messages like
<literal>BUSY</literal>, <literal>NO
DIALTONE</literal>, or <literal>CONNECT
115200</literal> will just confuse it. You should turn those
@ -22821,7 +22821,7 @@ Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp
<filename>/etc/syslog.conf</filename> to see to which files
<command>syslogd</command> is logging).</para>
<para>OK, enough of the examples -- let us dive into setting up
<para>OK, enough of the examples &mdash; let us dive into setting up
the system.</para>
</sect3>
@ -22857,7 +22857,7 @@ sl1* 296 &lt;Link&gt; 0 0 0 0
forward packets (ie, your FreeBSD machine will not act as a
router) due to Internet RFC requirements for Internet hosts (see
RFC's 1009 [Requirements for Internet Gateways], 1122
[Requirements for Internet Hosts -- Communication Layers], and
[Requirements for Internet Hosts &mdash; Communication Layers], and
perhaps 1127 [A Perspective on the Host Requirements RFCs]), so if
you want your FreeBSD SLIP Server to act as a router, you will
have to edit the <filename>/etc/rc.conf</filename> file (called
@ -22962,22 +22962,22 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp
<itemizedlist>
<listitem>
<para><option>normal</option> - no header
<para><option>normal</option> &mdash; no header
compression</para>
</listitem>
<listitem>
<para><option>compress</option> - compress
<para><option>compress</option> &mdash; compress
headers</para>
</listitem>
<listitem>
<para><option>autocomp</option> - compress
<para><option>autocomp</option> &mdash; compress
headers if the remote end allows it</para>
</listitem>
<listitem>
<para><option>noicmp</option> - disable ICMP
<para><option>noicmp</option> &mdash; disable ICMP
packets (so any <quote>ping</quote> packets will be dropped instead
of using up your bandwidth)</para>
</listitem>
@ -23090,7 +23090,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp
</informalexample>
<para>This indicates that this particular system's Ethernet MAC
address is <hostid role="mac">00:02:c1:28:5f:4a</hostid> --
address is <hostid role="mac">00:02:c1:28:5f:4a</hostid> &mdash;
the periods in the Ethernet MAC address given by
<command>netstat -i</command> must be changed to colons and
leading zeros should be added to each single-digit hexadecimal
@ -24085,7 +24085,7 @@ hostname myclient.mydomain
</listitem>
<listitem>
<para>Dr. Neuhaus - Niccy 1016</para>
<para>Dr. Neuhaus &mdash; Niccy 1016</para>
</listitem>
</itemizedlist>
@ -24390,7 +24390,7 @@ ISDN BRI line
</sect2>
<sect2>
<title>DNS - Name Service</title>
<title>DNS &mdash; Name Service</title>
<para>The Domain Name System and its daemon <command>named</command>, contain the database mapping
hostname to IP address, and hostname to mailhost. The IP address
@ -25414,7 +25414,7 @@ subscribe freebsd-stable
of the development branch. <quote>ctm-src-2_2</quote> supports the 2.2
release branch, etc. (If you do not know how to subscribe
yourself using majordomo, send a message first containing the
word <literal>help</literal> - it will send you back usage
word <literal>help</literal> &mdash; it will send you back usage
instructions.)</para>
<para>When you begin receiving your <application>CTM</application> updates
@ -27517,7 +27517,7 @@ cvs-crypto
<listitem>
<para>If you run FreeBSD-current and have a good Internet
connection, there is a machine <hostid role="fqdn">current.freebsd.org</hostid> which
builds a full release once a day - every now and again, try
builds a full release once a day &mdash; every now and again, try
and install the latest release from it and report any
failures in the process.</para>
</listitem>
@ -27539,10 +27539,10 @@ cvs-crypto
<listitem>
<para>Help translate FreeBSD documentation into your native
language (if not already available) - just send an email to
language (if not already available) &mdash; just send an email to
&a.doc; asking if anyone is working on it. Note that you
are not committing yourself to translating every single
FreeBSD document by doing this - in fact, the documentation
FreeBSD document by doing this &mdash; in fact, the documentation
most in need of translation is the installation
instructions.</para>
</listitem>
@ -28160,7 +28160,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# Date created: 5 December 1994
# Whom: asami
#
# $Id: handbook.sgml,v 1.47 1998-10-26 23:50:32 nik Exp $
# $Id: handbook.sgml,v 1.48 1998-10-26 23:51:02 nik Exp $
#
DISTNAME= oneko-1.1b
@ -28300,7 +28300,7 @@ lib/X11/oneko/mouse.xpm
<para>Now that you are happy with your port, the only thing
remaining is to put it in the main FreeBSD ports tree and make
everybody else happy about it too. To accomplish this, pack
the necessary files (everything described in this section --
the necessary files (everything described in this section &mdash;
in particular do <emphasis>not</emphasis> include the original
source tarball, the <filename>work</filename>
subdirectory or the package) into a
@ -28516,7 +28516,7 @@ lib/X11/oneko/mouse.xpm
should be collected into a file named
<filename>patch-<replaceable>xx</replaceable></filename> where
<replaceable>xx</replaceable> denotes the sequence in which
the patches will be applied -- these are done in
the patches will be applied &mdash; these are done in
<emphasis>alphabetical order</emphasis>, thus
<literal>aa</literal> first, <literal>ab</literal> second and so on. These files
should be stored in <makevar>&#36;{PATCHDIR}</makevar>, from where they will be
@ -32112,7 +32112,7 @@ pre-install:
</listitem>
<listitem>
<para>John Dyson - <ulink
<para>John Dyson <ulink
URL="mailto:formerly dyson@ref.tfs.com">&lt;formerly
dyson@ref.tfs.com&gt;</ulink></para>
</listitem>
@ -33761,7 +33761,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
</sect3>
<sect3>
<title>Configuring the <filename>ld.so</filename> -- for FreeBSD
<title>Configuring the <filename>ld.so</filename> &mdash; for FreeBSD
2.2-RELEASE only</title>
<para>This section applies only to FreeBSD 2.2-RELEASE and later.
@ -34432,7 +34432,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
<filename>/sbin/init</filename> which...</para>
<variablelist>
<varlistentry><term>A -- Using DOS</term>
<varlistentry><term>A &mdash; Using DOS</term>
<listitem>
<itemizedlist>
@ -34471,7 +34471,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
</listitem>
</varlistentry>
<varlistentry><term>B -- Using NFS</term>
<varlistentry><term>B &mdash; Using NFS</term>
<listitem>
<para>NFS mounts your
@ -34485,7 +34485,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
</listitem>
</varlistentry>
<varlistentry><term>C -- Start an X-server</term>
<varlistentry><term>C &mdash; Start an X-server</term>
<listitem>
<para>Now you have an X-terminal, which is better than that
@ -34495,7 +34495,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
</listitem>
</varlistentry>
<varlistentry><term>D -- Using a tape</term>
<varlistentry><term>D &mdash; Using a tape</term>
<listitem>
<para>Takes a copy of <filename>/dev/rwd0</filename> and
@ -34506,7 +34506,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
</listitem>
</varlistentry>
<varlistentry><term>E -- Acts as a firewall/web-server/what do I
<varlistentry><term>E &mdash; Acts as a firewall/web-server/what do I
know...</term>
<listitem>
@ -34541,7 +34541,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
work below <literal>0x1fff0</literal>. After this, it jumps to the
entry of boot2 within that code. I.e., it jumps over itself and the
(dummy) partition table, and it is going to adjust the %cs
selector---we are still in 16-bit mode there.</para>
selector&mdash;we are still in 16-bit mode there.</para>
<para>boot2 asks for the boot file, and examines the
<filename>a.out</filename> header. It masks the file entry point
@ -35029,7 +35029,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
<sect3>
<title>0x00 - 0x1f DMA Controller #1 (Channels 0, 1, 2 and
<title>0x00&ndash;0x1f DMA Controller #1 (Channels 0, 1, 2 and
3)</title>
<para>DMA Address and Count Registers</para>
@ -35243,7 +35243,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
</sect3>
<sect3>
<title>0xc0 - 0xdf DMA Controller #2 (Channels 4, 5, 6 and
<title>0xc0&ndash;0xdf DMA Controller #2 (Channels 4, 5, 6 and
7)</title>
<para>DMA Address and Count Registers</para>
@ -35458,7 +35458,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
</sect3>
<sect3>
<title>0x80 - 0x9f DMA Page Registers</title>
<title>0x80&ndash;0x9f DMA Page Registers</title>
<informaltable frame="none">
<tgroup cols="3">
@ -35516,7 +35516,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
</sect3>
<sect3>
<title>0x400 - 0x4ff 82374 Enhanced DMA Registers</title>
<title>0x400&ndash;0x4ff 82374 Enhanced DMA Registers</title>
<para>The Intel 82374 EISA System Component (ESC) was introduced
in early 1996 and includes a DMA controller that provides a
@ -37674,7 +37674,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
<listitem>
<para>Don Libes, Sandy Ressler <emphasis>Life with
UNIX</emphasis> - special edition. Prentice-Hall, Inc.,
UNIX</emphasis> &mdash; special edition. Prentice-Hall, Inc.,
1989.<!-- <br> --> ISBN 0-13-536657-7</para>
</listitem>
@ -37713,7 +37713,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen>
</listitem>
<listitem>
<para><emphasis>Sys Admin - The Journal for UNIX System
<para><emphasis>Sys Admin &mdash; The Journal for UNIX System
Administrators</emphasis> Miller Freeman, Inc., ISSN
1061-2688</para>
</listitem>
@ -38823,87 +38823,87 @@ help
<listitem>
<para><ulink
URL="http://www.FreeBSD.ORG/">http://www.FreeBSD.ORG/</ulink> - Central Server.</para>
URL="http://www.FreeBSD.ORG/">http://www.FreeBSD.ORG/</ulink> &mdash; Central Server.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> - Australia.</para>
URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.br.freebsd.org/">http://www.br.freebsd.org/</ulink> - Brazil.</para>
URL="http://www.br.freebsd.org/">http://www.br.freebsd.org/</ulink> &mdash; Brazil.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ca.freebsd.org/">http://www.ca.freebsd.org/</ulink> - Canada.</para>
URL="http://www.ca.freebsd.org/">http://www.ca.freebsd.org/</ulink> &mdash; Canada.</para>
</listitem>
<listitem>
<para><ulink
URL="http://sunsite.mff.cuni.cz/www.freebsd.org/">http://sunsite.mff.cuni.cz/www.freebsd.org/</ulink> - Czech Republic.</para>
URL="http://sunsite.mff.cuni.cz/www.freebsd.org/">http://sunsite.mff.cuni.cz/www.freebsd.org/</ulink> &mdash; Czech Republic.</para>
</listitem>
<listitem>
<para><ulink
URL="http://sunsite.auc.dk/www.freebsd.org/">http://sunsite.auc.dk/www.freebsd.org/</ulink> - Denmark.</para>
URL="http://sunsite.auc.dk/www.freebsd.org/">http://sunsite.auc.dk/www.freebsd.org/</ulink> &mdash; Denmark.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ee.freebsd.org/">http://www.ee.freebsd.org/</ulink> - Estonia.</para>
URL="http://www.ee.freebsd.org/">http://www.ee.freebsd.org/</ulink> &mdash; Estonia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.fi.freebsd.org/">http://www.fi.freebsd.org/</ulink> - Finland.</para>
URL="http://www.fi.freebsd.org/">http://www.fi.freebsd.org/</ulink> &mdash; Finland.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.de.freebsd.org/">http://www.de.freebsd.org/</ulink> - Germany.</para>
URL="http://www.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ie.freebsd.org/">http://www.ie.freebsd.org/</ulink> - Ireland.</para>
URL="http://www.ie.freebsd.org/">http://www.ie.freebsd.org/</ulink> &mdash; Ireland.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.jp.freebsd.org/">http://www.jp.freebsd.org/</ulink> - Japan.</para>
URL="http://www.jp.freebsd.org/">http://www.jp.freebsd.org/</ulink> &mdash; Japan.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.kr.freebsd.org/">http://www.kr.freebsd.org/</ulink> - Korea.</para>
URL="http://www.kr.freebsd.org/">http://www.kr.freebsd.org/</ulink> &mdash; Korea.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.nl.freebsd.org/">http://www.nl.freebsd.org/</ulink> - Netherlands.</para>
URL="http://www.nl.freebsd.org/">http://www.nl.freebsd.org/</ulink> &mdash; Netherlands.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.pt.freebsd.org/">http://www.pt.freebsd.org/</ulink> - Portugal.</para>
URL="http://www.pt.freebsd.org/">http://www.pt.freebsd.org/</ulink> &mdash; Portugal.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.se.freebsd.org/www.freebsd.org/">http://www.se.freebsd.org/www.freebsd.org/</ulink> - Sweden.</para>
URL="http://www.se.freebsd.org/www.freebsd.org/">http://www.se.freebsd.org/www.freebsd.org/</ulink> &mdash; Sweden.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.tw.freebsd.org/freebsd.html">http://www.tw.freebsd.org/freebsd.html</ulink> - Taiwan.</para>
URL="http://www.tw.freebsd.org/freebsd.html">http://www.tw.freebsd.org/freebsd.html</ulink> &mdash; Taiwan.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ua.freebsd.org/">http://www2.ua.freebsd.org/</ulink> - Ukraine.</para>
URL="http://www2.ua.freebsd.org/">http://www2.ua.freebsd.org/</ulink> &mdash; Ukraine.</para>
</listitem>
</itemizedlist>