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

The third, and final episode in the attack of the spelling police series.

Browse source 
Well, at least for now anyway :-)
This commit is contained in:
Jim Mock 2000-06-14 20:30:40 +00:00
parent 978084693a
commit dfefe8d45b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7362
21 changed files with 170 additions and 170 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.15 2000/03/25 17:02:35 nbm Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.16 2000/06/08 01:56:12 jim Exp $
-->
<chapter id="policies">
@ -91,7 +91,7 @@ MAINTAINER= email-addresses</programlisting>
change can be rather dramatic.</para>
</note>
<para>The <application>Tcl</application> embedded programming
<para>The <application>TCL</application> embedded programming
language will be used as example of how this model works:</para>
<para><filename>src/contrib/tcl</filename> contains the source as

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.29 2000/04/30 22:33:03 nik Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.30 2000/06/08 01:56:11 jim Exp $
-->
<chapter id="linuxemu">
@ -158,12 +158,12 @@ Id Refs Address Size Name
system. Look at the following example:</para>
<informalexample>
<para>Let us assume you have just ftp'd the Linux binary of
<para>Let us assume you used FTP to get the Linux binary of
Doom, and put it on a Linux system you have access to. You
then can check which shared libraries it needs by running
<command>ldd linuxxdoom</command>, like so:</para>
<command>ldd linuxdoom</command>, like so:</para>
<screen>&prompt.user; <userinput>ldd linuxxdoom</userinput>
<screen>&prompt.user; <userinput>ldd linuxdoom</userinput>
libXt.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libXt.so.3.1.0
libX11.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libX11.so.3.1.0
libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
@ -421,7 +421,7 @@ disco.example.com 7115-70839-20412</screen>
5.2 of these packages.</para>
<para>If you want to run the intelligent agent, you'll
also need to install the Red Hat tcl package:
also need to install the Red Hat TCL package:
<filename>tcl-8.0.3-20.i386.rpm</filename>. The general command
for installing packages with the official RPM port is :</para>

10
en_US.ISO8859-1/books/handbook/mail/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml,v 1.17 1999/12/22 20:06:59 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml,v 1.18 2000/06/08 01:56:12 jim Exp $
-->
<chapter id="mail">
@ -220,7 +220,7 @@ to /etc/sendmail.cf.</programlisting>
<qandaentry>
<question>
<para>How can I do email with a dialup PPP host?</para>
<para>How can I do email with a dial-up PPP host?</para>
</question>
<answer>
@ -272,12 +272,12 @@ bigco.com. MX 10 bigco.com.
<para>Message stolen from the &a.isp;.</para>
<programlisting>
&gt; we provide the secondary mx for a customer. The customer connects to
&gt; we provide the secondary MX for a customer. The customer connects to
&gt; our services several times a day automatically to get the mails to
&gt; his primary mx (We do not call his site when a mail for his domains
&gt; his primary MX (We do not call his site when a mail for his domains
&gt; arrived). Our sendmail sends the mailqueue every 30 minutes. At the
&gt; moment he has to stay 30 minutes online to be sure that all mail is
&gt; gone to the primary mx.
&gt; gone to the primary MX.
&gt;
&gt; Is there a command that would initiate sendmail to send all the mails
&gt; now? The user has not root-privileges on our machine of course.

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.68 2000/06/09 22:54:37 nik Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.69 2000/06/13 07:40:12 kevlo Exp $
-->
<appendix id="mirrors">
@ -303,8 +303,8 @@
<term><anchor id="mirrors-de">Germany</term>
<listitem>
<para>In case of problems, please contact the mirrors admins
<email>de-bsd-hubs@de.freebsd.org </email> for this domain.</para>
<para>In case of problems, please contact the mirror admins
<email>de-bsd-hubs@de.FreeBSD.org </email> for this domain.</para>
<itemizedlist>
<listitem>
@ -1074,7 +1074,7 @@
CTM will operate on it instead of
<filename>foo</filename>.</para>
<para>This behaviour gives us a simple way to maintain local
<para>This behavior gives us a simple way to maintain local
changes: simply copy the files you plan to modify to the
corresponding file names with a <filename>.ctm</filename>
suffix. Then you can freely hack the code, while CTM keeps the
@ -1771,11 +1771,11 @@ cvs-crypto</programlisting>
language-specific files. If you are
<application>CVSup</application>ing the ports collection, you
can get around this by specifying each collection individually
(eg <emphasis>ports-astrology</emphasis>,
(e.g., <emphasis>ports-astrology</emphasis>,
<emphasis>ports-biology</emphasis>, etc instead of simply
saying <emphasis>ports-all</emphasis>). However, since the doc
and www trees do not have language-specific collections, you
must use one of <application>CVSup</application>'s many nify
must use one of <application>CVSup</application>'s many nifty
features; the <emphasis>refuse file</emphasis>.</para>
<para>The <emphasis>refuse file</emphasis> essentially tells
@ -1817,7 +1817,7 @@ cvs-crypto</programlisting>
to download files that they will never use. For more
information on <emphasis>refuse files</emphasis> and other neat
features of <application>CVSup</application>, please view its
manpage.</para>
man page.</para>
</sect3>
</sect2>
@ -3307,7 +3307,7 @@ cvs-crypto</programlisting>
<note>
<para>Because the current version of <application>CTM</application> does
not preserve the timestamps of files, the timestamps at this mirror
not preserve the time stamps of files, the time stamps at this mirror
site are not the same as those at other mirror sites. Switching
between this site and other sites is not recommended. It will work
correctly, but will be somewhat inefficient.</para>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.15 2000/03/25 17:02:35 nbm Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.16 2000/06/08 01:56:12 jim Exp $
-->
<chapter id="policies">
@ -91,7 +91,7 @@ MAINTAINER= email-addresses</programlisting>
change can be rather dramatic.</para>
</note>
<para>The <application>Tcl</application> embedded programming
<para>The <application>TCL</application> embedded programming
language will be used as example of how this model works:</para>
<para><filename>src/contrib/tcl</filename> contains the source as

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.109 2000/06/09 09:23:31 alex Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.110 2000/06/09 18:08:44 nik Exp $
-->
<chapter id="ports">
@ -865,7 +865,7 @@ arcade game.</screen>
<answer>
<para>No, the problem is that some of the ports need to ask
you questions that we cannot answer for you (eg <quote>Do
you questions that we cannot answer for you (e.g., <quote>Do
you want to print on A4 or US letter sized paper?</quote>)
and they need to have someone on hand to answer
them.</para>
@ -954,7 +954,7 @@ arcade game.</screen>
<para>Gripe&mdash;<emphasis>by email only!</emphasis> Send
email to the maintainer of the port first. Type <command>make
maintainer</command> or read the <filename>Makefile</filename>
to find the maintainter's email address. Remember to include
to find the maintainer's email address. Remember to include
the name and version of the port (send the
<literal>$FreeBSD:</literal> line from the
<filename>Makefile</filename>) and the output leading up to the

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.23 2000/04/10 13:34:34 brian Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.24 2000/06/08 01:56:15 jim Exp $
-->
<chapter id="ppp-and-slip">
@ -14,7 +14,7 @@
<title>Synopsis</title>
<para>If you are connecting to the Internet via modem, or wish to
provide dialup connections to the Internet for others using FreeBSD,
provide dial-up connections to the Internet for others using FreeBSD,
you have the option of using PPP or SLIP.</para>
<para>This chapter covers three varieties of PPP;
@ -29,7 +29,7 @@
<para>You may be wondering what the main difference is between User
PPP and kernel PPP. The answer is simple; user PPP does not run as
a daemon, and can run as and when desired. No PPP interface needs
to be compiled into ther kernel; it runs as a user process, and uses
to be compiled into their kernel; it runs as a user process, and uses
the tunnel device driver (<devicename>tun</devicename>) to get data
into and out of the kernel.</para>
@ -63,12 +63,12 @@
</listitem>
<listitem>
<para>The dialup number(s) of your ISP.</para>
<para>The dial-up number(s) of your ISP.</para>
</listitem>
<listitem>
<para>Your login name and password. This can be either a
regular unix style login and password pair, or a PAP or CHAP
regular UNIX-style login and password pair, or a PAP or CHAP
login and password pair.</para>
</listitem>
@ -483,7 +483,7 @@ protocol: ppp</screen>
<term>Line 10:</term>
<listitem>
<para>Adds a default route to your ISPs gateway. The
<para>Adds a default route to your ISP's gateway. The
special word <literal>HISADDR</literal> is replaced with
the gateway address specified on line 9. It is
important that this line appears after line 9,
@ -645,14 +645,14 @@ gateway="YES"</programlisting>
<sect5>
<title>Which getty?</title>
<para><link linkend="dialup">Configuring FreeBSD for Dialup
<para><link linkend="dialup">Configuring FreeBSD for Dial-up
Services</link> provides a good description on enabling
dialup services using getty.</para>
dial-up services using getty.</para>
<para>An alternative to <command>getty</command> is <ulink
url="http://www.leo.org/~doering/mgetty/index.html">mgetty</ulink>,
a smarter version of <command>getty</command> designed with
dialup lines in mind.</para>
dial-up lines in mind.</para>
<para>The advantages of using <command>mgetty</command> is
that it actively <emphasis>talks</emphasis> to modems,

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/security/chapter.sgml,v 1.32 2000/06/12 20:46:08 murray Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/security/chapter.sgml,v 1.33 2000/06/12 21:27:18 jim Exp $
-->
<chapter id="security">
@ -197,7 +197,7 @@
disallowed. If using other login services such as
<application>sshd</application>, make sure that direct root logins
are disabled there as well. Consider every access method &ndash;
services such as ftp often fall through the cracks. Direct root
services such as FTP often fall through the cracks. Direct root
logins should only be allowed via the system console.</para>
<para>Of course, as a sysadmin you have to be able to get to root,
@ -215,7 +215,7 @@
<filename>/etc/group</filename> file. Only those staff members
who actually need to have root access should be placed in the
<literal>wheel</literal> group. It is also possible, when using
an authentication method such as kerberos, to use kerberos's
an authentication method such as kerberos, to use kerberos'
<filename>.k5login</filename> file in the root account to allow a
&man.ksu.1; to root without having to place anyone at all in the
<literal>wheel</literal> group. This may be the better solution
@ -588,7 +588,7 @@
its face. It is also prudent to run sendmail in queued mode
(<option>-ODeliveryMode=queued</option>) and to run the daemon
(<command>sendmail -bd</command>) separate from the queue-runs
(<command>sendmail -q15m</command>). If you still want realtime
(<command>sendmail -q15m</command>). If you still want real-time
delivery you can run the queue at a much lower interval, such as
<option>-q1m</option>, but be sure to specify a reasonable
<literal>MaxDaemonChildren</literal> option for that sendmail to
@ -737,7 +737,7 @@
of the <literal>from=IP/DOMAIN</literal> option that
<application>ssh</application> allows in its
<filename>authorized_keys</filename> file to make the key only
useable to entities logging in from specific machines.</para>
usable to entities logging in from specific machines.</para>
</sect2>
</sect1>
@ -840,8 +840,8 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
or just unqualified <quote>password</quote>.</para>
<para>The secret password does not have anything to do with your UNIX
password; they can be the same but this is not reccomended. S/Key
secret passwords are not limted to 8 characters like UNIX passwords,
password; they can be the same but this is not recommended. S/Key
secret passwords are not limited to 8 characters like UNIX passwords,
they can be as long as you like. Passwords of six or seven word
long phrases are fairly common. For the most part, the S/Key system
operates completely independently of the UNIX password
@ -860,9 +860,9 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
track of the last one-time password used, and the user is
authenticated if the hash of the user-provided password is equal to
the previous password. Because a one-way hash is used it is
impossible to generate future one-time passwords if a sucessfully
used password is captured; the interation count is decremented after
each sucessfull login to keep the user and the login program in
impossible to generate future one-time passwords if a successfully
used password is captured; the iteration count is decremented after
each successful login to keep the user and the login program in
sync. When the iteration count gets down to 1 S/Key must be
reinitialized.</para>
@ -943,7 +943,7 @@ DEFY CLUB PRO NASH LACE SOFT</screen>
<screen>&prompt.user; <userinput>keyinit -s</userinput>
Updating unfurl:
Old key: to17758
Reminder you need the 6 english words from the key command.
Reminder you need the 6 English words from the key command.
Enter sequence count from 1 to 9999: <userinput>100</userinput>
Enter new key [default to17759]:
s/key 100 to 17759
@ -1180,7 +1180,7 @@ ARC.NASA.GOV trident.arc.nasa.gov</screen>
<para>The first line names the realm in which this system works. The
other lines contain realm/host entries. The first item on a line is a
realm, and the second is a host in that realm that is acting as a
<quote>key distribution centre</quote>. The words <literal>admin
<quote>key distribution center</quote>. The words <literal>admin
server</literal> following a hosts name means that host also
provides an administrative database server. For further explanation
of these terms, please consult the Kerberos man pages.</para>
@ -1208,7 +1208,7 @@ grunt.grondar.za GRONDAR.ZA
a particular subdomain to a named realm.</para>
<para>Now we are ready to create the database. This only needs to run
on the Kerberos server (or Key Distribution Centre). Issue the
on the Kerberos server (or Key Distribution Center). Issue the
<command>kdb_init</command> command to do this:</para>
<screen>&prompt.root; <userinput>kdb_init</userinput>
@ -2023,7 +2023,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
supported list of IP options are: <literal>ssrr</literal>
(strict source route), <literal>lsrr</literal> (loose source
route), <literal>rr</literal> (record packet route), and
<literal>ts</literal> (timestamp). The absence of a
<literal>ts</literal> (time stamp). The absence of a
particular option may be denoted with a leading
<literal>!</literal>.</para>
</listitem>
@ -2233,7 +2233,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<para>You should enable your firewall from
<filename>/etc/rc.conf.local</filename> or
<filename>/etc/rc.conf</filename>. The associated manpage explains
<filename>/etc/rc.conf</filename>. The associated man page explains
which knobs to fiddle and lists some preset firewall configurations.
If you do not use a preset configuration, <command>ipfw list</command>
will output the current ruleset into a file that you can

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml,v 1.17 2000/04/03 04:36:10 unfurl Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml,v 1.18 2000/06/08 01:56:19 jim Exp $
-->
<chapter id="serialcomms">
@ -25,7 +25,7 @@
<para>This section should give you some general information about serial
ports. If you do not find what you want here, check into the Terminal
and Dialup sections of the handbook.</para>
and Dial-up sections of the handbook.</para>
<para>The <filename>ttyd<replaceable>X</replaceable></filename> (or
<filename>cuaa<replaceable>X</replaceable></filename>) device is the
@ -357,19 +357,19 @@
<itemizedlist>
<listitem>
<para>Callin ports are named
<para>Call-in ports are named
<filename>/dev/ttyd<replaceable>X</replaceable></filename>
where <replaceable>X</replaceable> is the port number,
starting from zero. Generally, you use the callin port for
terminals. Callin ports require that the serial line assert
starting from zero. Generally, you use the call-in port for
terminals. Call-in ports require that the serial line assert
the data carrier detect (DCD) signal to work.</para>
</listitem>
<listitem>
<para>Callout ports are named
<para>Call-out ports are named
<filename>/dev/cuaa<replaceable>X</replaceable></filename>.
You usually do not use the callout port for terminals, just
for modems. You may use the callout port if the serial cable
You usually do not use the call-out port for terminals, just
for modems. You may use the call-out port if the serial cable
or the terminal does not support the carrier detect
signal.</para>
</listitem>
@ -542,7 +542,7 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
<title>Specifying the Default Terminal Type</title>
<para>The third field in the <filename>/etc/ttys</filename> file lists
the default terminal type for the port. For dialup ports, you
the default terminal type for the port. For dial-up ports, you
typically put <literal>unknown</literal> or
<literal>dialup</literal> in this field because users may dial up
with practically any kind of terminal or software. For hardwired
@ -743,14 +743,14 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
</sect1>
<sect1 id="dialup">
<title>Dialin Service</title>
<title>Dial-in Service</title>
<para><emphasis>Contributed by &a.ghelmer;.</emphasis></para>
<para>This document provides suggestions for configuring a FreeBSD system
to handle dialup modems. This document is written based on the author's
to handle dial-up modems. This document is written based on the author's
experience with FreeBSD versions 1.0, 1.1, and 1.1.5.1 (and experience
with dialup modems on other UNIX-like operating systems); however, this
with dial-up modems on other UNIX-like operating systems); however, this
document may not answer all of your questions or provide examples
specific enough to your environment. The author cannot be responsible if
you damage your system or lose data due to attempting to follow the
@ -833,9 +833,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
</sect3>
<sect3>
<title>External vs. Internal Modems</title>
<title>External v.s. Internal Modems</title>
<para>External modems seem to be more convenient for dialup, because
<para>External modems seem to be more convenient for dial-up, because
external modems often can be semi-permanently configured via
parameters stored in non-volatile RAM and they usually provide
lighted indicators that display the state of important RS-232
@ -959,7 +959,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect2>
<title>Quick Overview</title>
<para>Here is the process that FreeBSD follows to accept dialup logins.
<para>Here is the process that FreeBSD follows to accept dial-up logins.
A <command>getty</command> process, spawned by
<command>init</command>, patiently waits to open the assigned serial
port (<filename>/dev/ttyd0</filename>, for our example). The command
@ -1119,10 +1119,10 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<filename>/dev</filename> directory manages the device special
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
ignore it.) To use <command>MAKEDEV</command> to make dial-up device
special files for <devicename>COM1:</devicename> (port 0),
<command>cd</command> to <filename>/dev</filename> and issue the
command <command>MAKEDEV ttyd0</command>. Likewise, to make dialup
command <command>MAKEDEV ttyd0</command>. Likewise, to make dial-up
device special files for <devicename>COM2:</devicename> (port 1),
use <command>MAKEDEV ttyd1</command>.</para>
@ -1140,7 +1140,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<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 &mdash; you probably do not want to allow your average
user to use your modems to dialout. The default permissions on the
user to use your modems to dial-out. The default permissions on the
<filename>/dev/cua*</filename> files should be sufficient:</para>
<screen>crw-rw---- 1 uucp dialer 28, 129 Feb 15 14:38 /dev/cua01
@ -1158,7 +1158,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
<para>There are three system configuration files in the
<filename>/etc</filename> directory that you will probably need to
edit to allow dialup access to your FreeBSD system. The first,
edit to allow dial-up access to your FreeBSD system. The first,
<filename>/etc/gettytab</filename>, contains configuration information
for the <filename>/usr/libexec/getty</filename> daemon. Second,
<filename>/etc/ttys</filename> holds information that tells
@ -1169,7 +1169,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
or higher; otherwise, you can initialize ports in the
<filename>/etc/rc.local</filename> script.</para>
<para>There are two schools of thought regarding dialup modems on UNIX.
<para>There are two schools of thought regarding dial-up modems on UNIX.
One group likes to configure their modems and system so that no matter
at what speed a remote user dials in, the local computer-to-modem
RS-232 interface runs at a locked speed. The benefit of this
@ -1320,7 +1320,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
<para>You will need to either modify existing lines in
<filename>/etc/ttys</filename> or add new lines to make
<command>init</command> run <command>getty</command> processes
automatically on your new dialup ports. The general format of the
automatically on your new dial-up ports. The general format of the
line will be the same, whether you are using a locked-speed or
matching-speed configuration:</para>
@ -1346,7 +1346,7 @@ ttyd0 "/usr/libexec/getty xxx" dialup on</programlisting>
<para>The default terminal type (<literal>dialup</literal> in the
example above) may depend on local preferences.
<literal>dialup</literal> is the traditional default terminal type
on dialup lines so that users may customize their login scripts to
on dial-up lines so that users may customize their login scripts to
notice when the terminal is <literal>dialup</literal> and
automatically adjust their terminal type. However, the author finds
it easier at his site to specify <literal>vt102</literal> as the
@ -1424,7 +1424,7 @@ stty -f /dev/cuai01 crtscts</programlisting>
<para>This sets the <literal>termios</literal> flag
<literal>crtscts</literal> on serial port #1's
(<devicename>COM2:</devicename>) dialin and dialout initialization
(<devicename>COM2:</devicename>) dial-in and dial-out initialization
devices.</para>
<para>On an old FreeBSD 1.1 system, these entries were added to
@ -1539,7 +1539,7 @@ AT&amp;C1&amp;D2&amp;H1&amp;I0&amp;R2&amp;W</programlisting>
</listitem>
</itemizedlist>
<para>Result codes should be disabled/suppressed for dialup modems to
<para>Result codes should be disabled/suppressed for dial-up modems to
avoid problems that can occur if <command>getty</command> mistakenly
gives a <prompt>login:</prompt> prompt to a modem that is in command
mode and the modem echoes the command or returns a result code. I
@ -1595,7 +1595,7 @@ AT&amp;B2&amp;W</programlisting>
<sect2>
<title>Troubleshooting</title>
<para>Here are a few steps you can follow to check out the dialup modem
<para>Here are a few steps you can follow to check out the dial-up modem
on your system.</para>
<sect3>
@ -1712,7 +1712,7 @@ AT&amp;B2&amp;W</programlisting>
</sect1>
<sect1 id="dialout">
<title>Dialout Service</title>
<title>Dial-out Service</title>
<para><emphasis>Information integrated from FAQ.</emphasis></para>
@ -1723,8 +1723,8 @@ AT&amp;B2&amp;W</programlisting>
<para>This is useful to log onto a BBS.</para>
<para>This kind of connection can be extremely helpful to get a file on
the Internet if you have problems with PPP. If you need to ftp
something and PPP is broken, use the terminal session to ftp it. Then
the Internet if you have problems with PPP. If you need to FTP
something and PPP is broken, use the terminal session to FTP it. Then
use zmodem to transfer it to your machine.</para>
<sect2>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/users/chapter.sgml,v 1.2 2000/04/03 02:15:43 chris Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/users/chapter.sgml,v 1.3 2000/06/12 17:10:36 alex Exp $
-->
<chapter id="users">
@ -36,7 +36,7 @@
the system, or programming.</para>
<para>This is because the superuser, unlike normal user accounts,
can operate without limits, and misuse of the superuse account
can operate without limits, and misuse of the superuser account
may result in spectacular disasters. User accounts are unable
to destroy the system by mistake, so it is generally best to use
normal user accounts whenever possible, unless you especially
@ -92,7 +92,7 @@
what, and prevent people from clobbering each others' settings,
and reading mail meant for the other, and so forth.</para>
<para>Each user can set up their own environment to accomodate
<para>Each user can set up their own environment to accommodate
their use of the system, by using alternate shells, editors, key
bindings, and language.</para>
</sect1>
@ -406,7 +406,7 @@ passwd: done</screen>
linkend="quotas">own chapter</link>.</para>
<para>Localization is an environment set up by the system
administrator or user to accomodate different languages,
administrator or user to accommodate different languages,
character sets, date and time standards, and so on. This is
discussed in the <link linkend="l10n">localization</link>
chapter.</para>

10
en_US.ISO8859-1/books/handbook/x11/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/x11/chapter.sgml,v 1.10 2000/03/21 07:52:43 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/x11/chapter.sgml,v 1.11 2000/06/08 01:56:23 jim Exp $
-->
<chapter id="x11">
@ -53,7 +53,7 @@
</warning>
<para>However, if you know you are in spec, and you have a standard
Super VGA board and a good multifrequency monitor, then you can
Super VGA board and a good multi-frequency monitor, then you can
probably get things up and running without reading this
chapter.</para>
</sect1>
@ -130,7 +130,7 @@
CD set. Alternatively, they are available on our FTP site at
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/Servers/">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/Servers/</ulink> or <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/PC98-Servers/">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/PC98-Servers/</ulink></para>
<para>Available X servers for the standard PC architechture:</para>
<para>Available X servers for the standard PC architecture:</para>
<informaltable>
<tgroup cols="2">
@ -739,7 +739,7 @@ ttyv3 "/usr/libexec/getty Pc" cons25 off secure</screen>
you run it. Running SuperProbe looks like this:</para>
<screen>&prompt.root; <userinput>SuperProbe</userinput>
(warnings and acknowledgements omitted)
(warnings and acknowledgments omitted)
First video: Super-VGA
Chipset: Tseng ET4000 (Port Probed)
Memory: 1024 Kbytes
@ -1103,7 +1103,7 @@ Server: XF86_SVGA
Press enter to continue, or ctrl-c to abort.ENTER
Now you must determine which server to run. Refer to the manpages and
Now you must determine which server to run. Refer to the man pages and
other documentation. The following servers are available (they may not
all be installed on your system):

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.29 2000/04/30 22:33:03 nik Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.30 2000/06/08 01:56:11 jim Exp $
-->
<chapter id="linuxemu">
@ -158,12 +158,12 @@ Id Refs Address Size Name
system. Look at the following example:</para>
<informalexample>
<para>Let us assume you have just ftp'd the Linux binary of
<para>Let us assume you used FTP to get the Linux binary of
Doom, and put it on a Linux system you have access to. You
then can check which shared libraries it needs by running
<command>ldd linuxxdoom</command>, like so:</para>
<command>ldd linuxdoom</command>, like so:</para>
<screen>&prompt.user; <userinput>ldd linuxxdoom</userinput>
<screen>&prompt.user; <userinput>ldd linuxdoom</userinput>
libXt.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libXt.so.3.1.0
libX11.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libX11.so.3.1.0
libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
@ -421,7 +421,7 @@ disco.example.com 7115-70839-20412</screen>
5.2 of these packages.</para>
<para>If you want to run the intelligent agent, you'll
also need to install the Red Hat tcl package:
also need to install the Red Hat TCL package:
<filename>tcl-8.0.3-20.i386.rpm</filename>. The general command
for installing packages with the official RPM port is :</para>

10
en_US.ISO_8859-1/books/handbook/mail/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml,v 1.17 1999/12/22 20:06:59 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml,v 1.18 2000/06/08 01:56:12 jim Exp $
-->
<chapter id="mail">
@ -220,7 +220,7 @@ to /etc/sendmail.cf.</programlisting>
<qandaentry>
<question>
<para>How can I do email with a dialup PPP host?</para>
<para>How can I do email with a dial-up PPP host?</para>
</question>
<answer>
@ -272,12 +272,12 @@ bigco.com. MX 10 bigco.com.
<para>Message stolen from the &a.isp;.</para>
<programlisting>
&gt; we provide the secondary mx for a customer. The customer connects to
&gt; we provide the secondary MX for a customer. The customer connects to
&gt; our services several times a day automatically to get the mails to
&gt; his primary mx (We do not call his site when a mail for his domains
&gt; his primary MX (We do not call his site when a mail for his domains
&gt; arrived). Our sendmail sends the mailqueue every 30 minutes. At the
&gt; moment he has to stay 30 minutes online to be sure that all mail is
&gt; gone to the primary mx.
&gt; gone to the primary MX.
&gt;
&gt; Is there a command that would initiate sendmail to send all the mails
&gt; now? The user has not root-privileges on our machine of course.

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.68 2000/06/09 22:54:37 nik Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.69 2000/06/13 07:40:12 kevlo Exp $
-->
<appendix id="mirrors">
@ -303,8 +303,8 @@
<term><anchor id="mirrors-de">Germany</term>
<listitem>
<para>In case of problems, please contact the mirrors admins
<email>de-bsd-hubs@de.freebsd.org </email> for this domain.</para>
<para>In case of problems, please contact the mirror admins
<email>de-bsd-hubs@de.FreeBSD.org </email> for this domain.</para>
<itemizedlist>
<listitem>
@ -1074,7 +1074,7 @@
CTM will operate on it instead of
<filename>foo</filename>.</para>
<para>This behaviour gives us a simple way to maintain local
<para>This behavior gives us a simple way to maintain local
changes: simply copy the files you plan to modify to the
corresponding file names with a <filename>.ctm</filename>
suffix. Then you can freely hack the code, while CTM keeps the
@ -1771,11 +1771,11 @@ cvs-crypto</programlisting>
language-specific files. If you are
<application>CVSup</application>ing the ports collection, you
can get around this by specifying each collection individually
(eg <emphasis>ports-astrology</emphasis>,
(e.g., <emphasis>ports-astrology</emphasis>,
<emphasis>ports-biology</emphasis>, etc instead of simply
saying <emphasis>ports-all</emphasis>). However, since the doc
and www trees do not have language-specific collections, you
must use one of <application>CVSup</application>'s many nify
must use one of <application>CVSup</application>'s many nifty
features; the <emphasis>refuse file</emphasis>.</para>
<para>The <emphasis>refuse file</emphasis> essentially tells
@ -1817,7 +1817,7 @@ cvs-crypto</programlisting>
to download files that they will never use. For more
information on <emphasis>refuse files</emphasis> and other neat
features of <application>CVSup</application>, please view its
manpage.</para>
man page.</para>
</sect3>
</sect2>
@ -3307,7 +3307,7 @@ cvs-crypto</programlisting>
<note>
<para>Because the current version of <application>CTM</application> does
not preserve the timestamps of files, the timestamps at this mirror
not preserve the time stamps of files, the time stamps at this mirror
site are not the same as those at other mirror sites. Switching
between this site and other sites is not recommended. It will work
correctly, but will be somewhat inefficient.</para>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.15 2000/03/25 17:02:35 nbm Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.16 2000/06/08 01:56:12 jim Exp $
-->
<chapter id="policies">
@ -91,7 +91,7 @@ MAINTAINER= email-addresses</programlisting>
change can be rather dramatic.</para>
</note>
<para>The <application>Tcl</application> embedded programming
<para>The <application>TCL</application> embedded programming
language will be used as example of how this model works:</para>
<para><filename>src/contrib/tcl</filename> contains the source as

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.109 2000/06/09 09:23:31 alex Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.110 2000/06/09 18:08:44 nik Exp $
-->
<chapter id="ports">
@ -865,7 +865,7 @@ arcade game.</screen>
<answer>
<para>No, the problem is that some of the ports need to ask
you questions that we cannot answer for you (eg <quote>Do
you questions that we cannot answer for you (e.g., <quote>Do
you want to print on A4 or US letter sized paper?</quote>)
and they need to have someone on hand to answer
them.</para>
@ -954,7 +954,7 @@ arcade game.</screen>
<para>Gripe&mdash;<emphasis>by email only!</emphasis> Send
email to the maintainer of the port first. Type <command>make
maintainer</command> or read the <filename>Makefile</filename>
to find the maintainter's email address. Remember to include
to find the maintainer's email address. Remember to include
the name and version of the port (send the
<literal>$FreeBSD:</literal> line from the
<filename>Makefile</filename>) and the output leading up to the

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.23 2000/04/10 13:34:34 brian Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.24 2000/06/08 01:56:15 jim Exp $
-->
<chapter id="ppp-and-slip">
@ -14,7 +14,7 @@
<title>Synopsis</title>
<para>If you are connecting to the Internet via modem, or wish to
provide dialup connections to the Internet for others using FreeBSD,
provide dial-up connections to the Internet for others using FreeBSD,
you have the option of using PPP or SLIP.</para>
<para>This chapter covers three varieties of PPP;
@ -29,7 +29,7 @@
<para>You may be wondering what the main difference is between User
PPP and kernel PPP. The answer is simple; user PPP does not run as
a daemon, and can run as and when desired. No PPP interface needs
to be compiled into ther kernel; it runs as a user process, and uses
to be compiled into their kernel; it runs as a user process, and uses
the tunnel device driver (<devicename>tun</devicename>) to get data
into and out of the kernel.</para>
@ -63,12 +63,12 @@
</listitem>
<listitem>
<para>The dialup number(s) of your ISP.</para>
<para>The dial-up number(s) of your ISP.</para>
</listitem>
<listitem>
<para>Your login name and password. This can be either a
regular unix style login and password pair, or a PAP or CHAP
regular UNIX-style login and password pair, or a PAP or CHAP
login and password pair.</para>
</listitem>
@ -483,7 +483,7 @@ protocol: ppp</screen>
<term>Line 10:</term>
<listitem>
<para>Adds a default route to your ISPs gateway. The
<para>Adds a default route to your ISP's gateway. The
special word <literal>HISADDR</literal> is replaced with
the gateway address specified on line 9. It is
important that this line appears after line 9,
@ -645,14 +645,14 @@ gateway="YES"</programlisting>
<sect5>
<title>Which getty?</title>
<para><link linkend="dialup">Configuring FreeBSD for Dialup
<para><link linkend="dialup">Configuring FreeBSD for Dial-up
Services</link> provides a good description on enabling
dialup services using getty.</para>
dial-up services using getty.</para>
<para>An alternative to <command>getty</command> is <ulink
url="http://www.leo.org/~doering/mgetty/index.html">mgetty</ulink>,
a smarter version of <command>getty</command> designed with
dialup lines in mind.</para>
dial-up lines in mind.</para>
<para>The advantages of using <command>mgetty</command> is
that it actively <emphasis>talks</emphasis> to modems,

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/security/chapter.sgml,v 1.32 2000/06/12 20:46:08 murray Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/security/chapter.sgml,v 1.33 2000/06/12 21:27:18 jim Exp $
-->
<chapter id="security">
@ -197,7 +197,7 @@
disallowed. If using other login services such as
<application>sshd</application>, make sure that direct root logins
are disabled there as well. Consider every access method &ndash;
services such as ftp often fall through the cracks. Direct root
services such as FTP often fall through the cracks. Direct root
logins should only be allowed via the system console.</para>
<para>Of course, as a sysadmin you have to be able to get to root,
@ -215,7 +215,7 @@
<filename>/etc/group</filename> file. Only those staff members
who actually need to have root access should be placed in the
<literal>wheel</literal> group. It is also possible, when using
an authentication method such as kerberos, to use kerberos's
an authentication method such as kerberos, to use kerberos'
<filename>.k5login</filename> file in the root account to allow a
&man.ksu.1; to root without having to place anyone at all in the
<literal>wheel</literal> group. This may be the better solution
@ -588,7 +588,7 @@
its face. It is also prudent to run sendmail in queued mode
(<option>-ODeliveryMode=queued</option>) and to run the daemon
(<command>sendmail -bd</command>) separate from the queue-runs
(<command>sendmail -q15m</command>). If you still want realtime
(<command>sendmail -q15m</command>). If you still want real-time
delivery you can run the queue at a much lower interval, such as
<option>-q1m</option>, but be sure to specify a reasonable
<literal>MaxDaemonChildren</literal> option for that sendmail to
@ -737,7 +737,7 @@
of the <literal>from=IP/DOMAIN</literal> option that
<application>ssh</application> allows in its
<filename>authorized_keys</filename> file to make the key only
useable to entities logging in from specific machines.</para>
usable to entities logging in from specific machines.</para>
</sect2>
</sect1>
@ -840,8 +840,8 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
or just unqualified <quote>password</quote>.</para>
<para>The secret password does not have anything to do with your UNIX
password; they can be the same but this is not reccomended. S/Key
secret passwords are not limted to 8 characters like UNIX passwords,
password; they can be the same but this is not recommended. S/Key
secret passwords are not limited to 8 characters like UNIX passwords,
they can be as long as you like. Passwords of six or seven word
long phrases are fairly common. For the most part, the S/Key system
operates completely independently of the UNIX password
@ -860,9 +860,9 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
track of the last one-time password used, and the user is
authenticated if the hash of the user-provided password is equal to
the previous password. Because a one-way hash is used it is
impossible to generate future one-time passwords if a sucessfully
used password is captured; the interation count is decremented after
each sucessfull login to keep the user and the login program in
impossible to generate future one-time passwords if a successfully
used password is captured; the iteration count is decremented after
each successful login to keep the user and the login program in
sync. When the iteration count gets down to 1 S/Key must be
reinitialized.</para>
@ -943,7 +943,7 @@ DEFY CLUB PRO NASH LACE SOFT</screen>
<screen>&prompt.user; <userinput>keyinit -s</userinput>
Updating unfurl:
Old key: to17758
Reminder you need the 6 english words from the key command.
Reminder you need the 6 English words from the key command.
Enter sequence count from 1 to 9999: <userinput>100</userinput>
Enter new key [default to17759]:
s/key 100 to 17759
@ -1180,7 +1180,7 @@ ARC.NASA.GOV trident.arc.nasa.gov</screen>
<para>The first line names the realm in which this system works. The
other lines contain realm/host entries. The first item on a line is a
realm, and the second is a host in that realm that is acting as a
<quote>key distribution centre</quote>. The words <literal>admin
<quote>key distribution center</quote>. The words <literal>admin
server</literal> following a hosts name means that host also
provides an administrative database server. For further explanation
of these terms, please consult the Kerberos man pages.</para>
@ -1208,7 +1208,7 @@ grunt.grondar.za GRONDAR.ZA
a particular subdomain to a named realm.</para>
<para>Now we are ready to create the database. This only needs to run
on the Kerberos server (or Key Distribution Centre). Issue the
on the Kerberos server (or Key Distribution Center). Issue the
<command>kdb_init</command> command to do this:</para>
<screen>&prompt.root; <userinput>kdb_init</userinput>
@ -2023,7 +2023,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
supported list of IP options are: <literal>ssrr</literal>
(strict source route), <literal>lsrr</literal> (loose source
route), <literal>rr</literal> (record packet route), and
<literal>ts</literal> (timestamp). The absence of a
<literal>ts</literal> (time stamp). The absence of a
particular option may be denoted with a leading
<literal>!</literal>.</para>
</listitem>
@ -2233,7 +2233,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<para>You should enable your firewall from
<filename>/etc/rc.conf.local</filename> or
<filename>/etc/rc.conf</filename>. The associated manpage explains
<filename>/etc/rc.conf</filename>. The associated man page explains
which knobs to fiddle and lists some preset firewall configurations.
If you do not use a preset configuration, <command>ipfw list</command>
will output the current ruleset into a file that you can

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml,v 1.17 2000/04/03 04:36:10 unfurl Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml,v 1.18 2000/06/08 01:56:19 jim Exp $
-->
<chapter id="serialcomms">
@ -25,7 +25,7 @@
<para>This section should give you some general information about serial
ports. If you do not find what you want here, check into the Terminal
and Dialup sections of the handbook.</para>
and Dial-up sections of the handbook.</para>
<para>The <filename>ttyd<replaceable>X</replaceable></filename> (or
<filename>cuaa<replaceable>X</replaceable></filename>) device is the
@ -357,19 +357,19 @@
<itemizedlist>
<listitem>
<para>Callin ports are named
<para>Call-in ports are named
<filename>/dev/ttyd<replaceable>X</replaceable></filename>
where <replaceable>X</replaceable> is the port number,
starting from zero. Generally, you use the callin port for
terminals. Callin ports require that the serial line assert
starting from zero. Generally, you use the call-in port for
terminals. Call-in ports require that the serial line assert
the data carrier detect (DCD) signal to work.</para>
</listitem>
<listitem>
<para>Callout ports are named
<para>Call-out ports are named
<filename>/dev/cuaa<replaceable>X</replaceable></filename>.
You usually do not use the callout port for terminals, just
for modems. You may use the callout port if the serial cable
You usually do not use the call-out port for terminals, just
for modems. You may use the call-out port if the serial cable
or the terminal does not support the carrier detect
signal.</para>
</listitem>
@ -542,7 +542,7 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
<title>Specifying the Default Terminal Type</title>
<para>The third field in the <filename>/etc/ttys</filename> file lists
the default terminal type for the port. For dialup ports, you
the default terminal type for the port. For dial-up ports, you
typically put <literal>unknown</literal> or
<literal>dialup</literal> in this field because users may dial up
with practically any kind of terminal or software. For hardwired
@ -743,14 +743,14 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
</sect1>
<sect1 id="dialup">
<title>Dialin Service</title>
<title>Dial-in Service</title>
<para><emphasis>Contributed by &a.ghelmer;.</emphasis></para>
<para>This document provides suggestions for configuring a FreeBSD system
to handle dialup modems. This document is written based on the author's
to handle dial-up modems. This document is written based on the author's
experience with FreeBSD versions 1.0, 1.1, and 1.1.5.1 (and experience
with dialup modems on other UNIX-like operating systems); however, this
with dial-up modems on other UNIX-like operating systems); however, this
document may not answer all of your questions or provide examples
specific enough to your environment. The author cannot be responsible if
you damage your system or lose data due to attempting to follow the
@ -833,9 +833,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
</sect3>
<sect3>
<title>External vs. Internal Modems</title>
<title>External v.s. Internal Modems</title>
<para>External modems seem to be more convenient for dialup, because
<para>External modems seem to be more convenient for dial-up, because
external modems often can be semi-permanently configured via
parameters stored in non-volatile RAM and they usually provide
lighted indicators that display the state of important RS-232
@ -959,7 +959,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect2>
<title>Quick Overview</title>
<para>Here is the process that FreeBSD follows to accept dialup logins.
<para>Here is the process that FreeBSD follows to accept dial-up logins.
A <command>getty</command> process, spawned by
<command>init</command>, patiently waits to open the assigned serial
port (<filename>/dev/ttyd0</filename>, for our example). The command
@ -1119,10 +1119,10 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<filename>/dev</filename> directory manages the device special
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
ignore it.) To use <command>MAKEDEV</command> to make dial-up device
special files for <devicename>COM1:</devicename> (port 0),
<command>cd</command> to <filename>/dev</filename> and issue the
command <command>MAKEDEV ttyd0</command>. Likewise, to make dialup
command <command>MAKEDEV ttyd0</command>. Likewise, to make dial-up
device special files for <devicename>COM2:</devicename> (port 1),
use <command>MAKEDEV ttyd1</command>.</para>
@ -1140,7 +1140,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<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 &mdash; you probably do not want to allow your average
user to use your modems to dialout. The default permissions on the
user to use your modems to dial-out. The default permissions on the
<filename>/dev/cua*</filename> files should be sufficient:</para>
<screen>crw-rw---- 1 uucp dialer 28, 129 Feb 15 14:38 /dev/cua01
@ -1158,7 +1158,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
<para>There are three system configuration files in the
<filename>/etc</filename> directory that you will probably need to
edit to allow dialup access to your FreeBSD system. The first,
edit to allow dial-up access to your FreeBSD system. The first,
<filename>/etc/gettytab</filename>, contains configuration information
for the <filename>/usr/libexec/getty</filename> daemon. Second,
<filename>/etc/ttys</filename> holds information that tells
@ -1169,7 +1169,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
or higher; otherwise, you can initialize ports in the
<filename>/etc/rc.local</filename> script.</para>
<para>There are two schools of thought regarding dialup modems on UNIX.
<para>There are two schools of thought regarding dial-up modems on UNIX.
One group likes to configure their modems and system so that no matter
at what speed a remote user dials in, the local computer-to-modem
RS-232 interface runs at a locked speed. The benefit of this
@ -1320,7 +1320,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
<para>You will need to either modify existing lines in
<filename>/etc/ttys</filename> or add new lines to make
<command>init</command> run <command>getty</command> processes
automatically on your new dialup ports. The general format of the
automatically on your new dial-up ports. The general format of the
line will be the same, whether you are using a locked-speed or
matching-speed configuration:</para>
@ -1346,7 +1346,7 @@ ttyd0 "/usr/libexec/getty xxx" dialup on</programlisting>
<para>The default terminal type (<literal>dialup</literal> in the
example above) may depend on local preferences.
<literal>dialup</literal> is the traditional default terminal type
on dialup lines so that users may customize their login scripts to
on dial-up lines so that users may customize their login scripts to
notice when the terminal is <literal>dialup</literal> and
automatically adjust their terminal type. However, the author finds
it easier at his site to specify <literal>vt102</literal> as the
@ -1424,7 +1424,7 @@ stty -f /dev/cuai01 crtscts</programlisting>
<para>This sets the <literal>termios</literal> flag
<literal>crtscts</literal> on serial port #1's
(<devicename>COM2:</devicename>) dialin and dialout initialization
(<devicename>COM2:</devicename>) dial-in and dial-out initialization
devices.</para>
<para>On an old FreeBSD 1.1 system, these entries were added to
@ -1539,7 +1539,7 @@ AT&amp;C1&amp;D2&amp;H1&amp;I0&amp;R2&amp;W</programlisting>
</listitem>
</itemizedlist>
<para>Result codes should be disabled/suppressed for dialup modems to
<para>Result codes should be disabled/suppressed for dial-up modems to
avoid problems that can occur if <command>getty</command> mistakenly
gives a <prompt>login:</prompt> prompt to a modem that is in command
mode and the modem echoes the command or returns a result code. I
@ -1595,7 +1595,7 @@ AT&amp;B2&amp;W</programlisting>
<sect2>
<title>Troubleshooting</title>
<para>Here are a few steps you can follow to check out the dialup modem
<para>Here are a few steps you can follow to check out the dial-up modem
on your system.</para>
<sect3>
@ -1712,7 +1712,7 @@ AT&amp;B2&amp;W</programlisting>
</sect1>
<sect1 id="dialout">
<title>Dialout Service</title>
<title>Dial-out Service</title>
<para><emphasis>Information integrated from FAQ.</emphasis></para>
@ -1723,8 +1723,8 @@ AT&amp;B2&amp;W</programlisting>
<para>This is useful to log onto a BBS.</para>
<para>This kind of connection can be extremely helpful to get a file on
the Internet if you have problems with PPP. If you need to ftp
something and PPP is broken, use the terminal session to ftp it. Then
the Internet if you have problems with PPP. If you need to FTP
something and PPP is broken, use the terminal session to FTP it. Then
use zmodem to transfer it to your machine.</para>
<sect2>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/users/chapter.sgml,v 1.2 2000/04/03 02:15:43 chris Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/users/chapter.sgml,v 1.3 2000/06/12 17:10:36 alex Exp $
-->
<chapter id="users">
@ -36,7 +36,7 @@
the system, or programming.</para>
<para>This is because the superuser, unlike normal user accounts,
can operate without limits, and misuse of the superuse account
can operate without limits, and misuse of the superuser account
may result in spectacular disasters. User accounts are unable
to destroy the system by mistake, so it is generally best to use
normal user accounts whenever possible, unless you especially
@ -92,7 +92,7 @@
what, and prevent people from clobbering each others' settings,
and reading mail meant for the other, and so forth.</para>
<para>Each user can set up their own environment to accomodate
<para>Each user can set up their own environment to accommodate
their use of the system, by using alternate shells, editors, key
bindings, and language.</para>
</sect1>
@ -406,7 +406,7 @@ passwd: done</screen>
linkend="quotas">own chapter</link>.</para>
<para>Localization is an environment set up by the system
administrator or user to accomodate different languages,
administrator or user to accommodate different languages,
character sets, date and time standards, and so on. This is
discussed in the <link linkend="l10n">localization</link>
chapter.</para>

10
en_US.ISO_8859-1/books/handbook/x11/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/x11/chapter.sgml,v 1.10 2000/03/21 07:52:43 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/x11/chapter.sgml,v 1.11 2000/06/08 01:56:23 jim Exp $
-->
<chapter id="x11">
@ -53,7 +53,7 @@
</warning>
<para>However, if you know you are in spec, and you have a standard
Super VGA board and a good multifrequency monitor, then you can
Super VGA board and a good multi-frequency monitor, then you can
probably get things up and running without reading this
chapter.</para>
</sect1>
@ -130,7 +130,7 @@
CD set. Alternatively, they are available on our FTP site at
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/Servers/">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/Servers/</ulink> or <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/PC98-Servers/">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/PC98-Servers/</ulink></para>
<para>Available X servers for the standard PC architechture:</para>
<para>Available X servers for the standard PC architecture:</para>
<informaltable>
<tgroup cols="2">
@ -739,7 +739,7 @@ ttyv3 "/usr/libexec/getty Pc" cons25 off secure</screen>
you run it. Running SuperProbe looks like this:</para>
<screen>&prompt.root; <userinput>SuperProbe</userinput>
(warnings and acknowledgements omitted)
(warnings and acknowledgments omitted)
First video: Super-VGA
Chipset: Tseng ET4000 (Port Probed)
Memory: 1024 Kbytes
@ -1103,7 +1103,7 @@ Server: XF86_SVGA
Press enter to continue, or ctrl-c to abort.ENTER
Now you must determine which server to run. Refer to the manpages and
Now you must determine which server to run. Refer to the man pages and
other documentation. The following servers are available (they may not
all be installed on your system):