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

Change all contractions to proper form.

Browse source 
don't -> do not
isn't -> is not
let's -> let us
... and so on
This commit is contained in:
Chern Lee 2001-08-16 18:35:08 +00:00
parent 39348b56a9
commit 6c21f4c1e9
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10378
24 changed files with 159 additions and 159 deletions
en_US.ISO8859-1/books/handbook
advanced-networking
chapter.sgml
backups
chapter.sgml
basics
chapter.sgml
boot
chapter.sgml
config
chapter.sgml
cutting-edge
chapter.sgml
disks
chapter.sgml
eresources
chapter.sgml
install
chapter.sgml
introduction
chapter.sgml
kernelconfig
chapter.sgml
kernelopts
chapter.sgml
linuxemu
chapter.sgml
mail
chapter.sgml
mirrors
chapter.sgml
multimedia
chapter.sgml
policies
chapter.sgml
ports
chapter.sgml
ppp-and-slip
chapter.sgml
security
chapter.sgml
serialcomms
chapter.sgml
sound
chapter.sgml
users
chapter.sgml
x11
chapter.sgml

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.88 2001/08/15 00:51:22 logo Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.89 2001/08/15 17:55:32 chern Exp $
-->
<chapter id="advanced-networking">
@ -440,11 +440,11 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
<title>High Traffic on a Segment</title>
<para>Situation one is where your physical network segment is
overloaded with traffic, but you don't want for whatever reason to
overloaded with traffic, but you do not want for whatever reason to
subnet the network and interconnect the subnets with a
router.</para>
<para>Let's consider an example of a newspaper where the Editorial and
<para>Let us consider an example of a newspaper where the Editorial and
Production departments are on the same subnetwork. The Editorial
users all use server A for file service, and the Production users
are on server B. An Ethernet is used to connect all users together,
@ -560,7 +560,7 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
<para>My bridge/firewall is a Pentium 90 with one 3Com 3C900B and one
3C905B. The protected side of the network runs at 10mbps half duplex
and the connection between the bridge and my router (a Cisco 675) runs
at 100mbps full duplex. With no filtering enabled, I've found that
at 100mbps full duplex. With no filtering enabled, I have found that
the bridge adds about 0.4 milliseconds of latency to pings from the
protected 10mbps network to the Cisco 675.</para>
</sect2>
@ -603,7 +603,7 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
<itemizedlist>
<listitem>
<para>Local workstations don't need as much disk space because
<para>Local workstations do not need as much disk space because
commonly used data can be stored on a single machine and still
remain accessible to everyone on the network.</para>
</listitem>
@ -754,7 +754,7 @@ nfs_client_flags="-n 4"</programlisting>
<option>-maproot=0</option> flag allows
the root user on the remote system to write to the shared
file system as root. Without the -maproot=0 flag even if
someone has root access on the remote system they won't
someone has root access on the remote system they will not
be able to modify files on the shared file system.</para>
<programlisting>/a -maproot=0 host.domain.com box.example.com</programlisting>
@ -763,7 +763,7 @@ nfs_client_flags="-n 4"</programlisting>
have permission to do so. Make sure your client is listed in your
<filename>/etc/exports</filename> file.</para>
<para>It's important to remember that you must restart <command>mountd</command>
<para>It is important to remember that you must restart <command>mountd</command>
whenever you modify <filename>/etc/exports</filename> so that
your changes take effect. This can be accomplished by sending
the hangup signal to the <command>mountd</command> process :</para>
@ -846,7 +846,7 @@ nfs_client_flags="-n 4"</programlisting>
<listitem>
<para>Have a common <filename>/usr/ports/distfiles</filename>
directory that all your machines share. That way, when you go
to install a port that you've already installed on a different
to install a port that you have already installed on a different
machine, you do not have to download the source all over
again!</para>
</listitem>
@ -1087,7 +1087,7 @@ Exports list on foobar:
<itemizedlist>
<indexterm><primary>HP-UX</primary></indexterm>
<listitem>
<para>HP9000/8xx running HP-UX 9.04 or later (pre 9.04 doesn't
<para>HP9000/8xx running HP-UX 9.04 or later (pre 9.04 does not
work)</para>
</listitem>
<indexterm><primary>Solaris</primary></indexterm>
@ -1608,7 +1608,7 @@ ISDN BRI line</literallayout>
<para>This can be very useful feature, for example if you have an
dedicated ISDN connection at your office and would like to
tap into it, but don't want to get another ISDN line at work. A router
tap into it, but do not want to get another ISDN line at work. A router
at the office location can manage a dedicated B channel connection
(64Kbs) to the Internet, as well as a use the other B channel for a
separate data connection. The second B channel can be used for
@ -1678,7 +1678,7 @@ ISDN BRI line</literallayout>
<indexterm><primary>Windows NT</primary></indexterm>
<para>It is similar to Windows NT's domain system; although the
internal implementation of the two aren't at all similar,
internal implementation of the two are not at all similar,
the basic functionality can be compared.</para>
</sect2>
@ -1724,7 +1724,7 @@ ISDN BRI line</literallayout>
server to take over for it).</para>
<note><para>There are some implementations of NIS (but not the
FreeBSD one), that don't try to reconnect to another server
FreeBSD one), that do not try to reconnect to another server
if the server it used before dies. Often, the only thing
that helps in this case is to restart the server process (or
even the whole server) or the <command>ypbind</command> process
@ -1825,7 +1825,7 @@ ISDN BRI line</literallayout>
<sect3>
<title>Planning</title>
<para>Let's assume that you are the administrator of a small
<para>Let us assume that you are the administrator of a small
university lab. This lab, which consists of 15 FreeBSD machines,
currently has no centralized point of administration; each machine
has its own <filename>/etc/passwd</filename> and
@ -1926,7 +1926,7 @@ ISDN BRI line</literallayout>
domain, very often the machine becomes unusable. The lack of
user and group information causes most systems to temporarily
freeze up. With this in mind you should make sure to choose a
machine that won't be prone to being rebooted regularly, or
machine that will not be prone to being rebooted regularly, or
one that might be used for development. The NIS server should
ideally be a stand alone machine whose sole purpose in life is
to be an NIS server. If you have a network that is not very
@ -2007,7 +2007,7 @@ ISDN BRI line</literallayout>
They are generated from configuration files in the
<filename>/etc</filename> directory of the NIS master, with one
exception: the <filename>/etc/master.passwd</filename> file.
This is for a good reason; you don't want to propagate
This is for a good reason; you do not want to propagate
passwords to your root and other administrative accounts to
all the servers in the NIS domain. Therefore, before we
initialize the NIS maps, you should:</para>
@ -2019,7 +2019,7 @@ ISDN BRI line</literallayout>
<para>You should remove all entries regarding system accounts
(<username>bin</username>, <username>tty</username>, <username>kmem</username>,
<username>games</username>, etc), as well as any accounts that you
don't want to be propagated to the NIS clients (for example
do not want to be propagated to the NIS clients (for example
root and any other UID 0 (superuser) accounts).</para>
<note><para>Make sure the
@ -2028,7 +2028,7 @@ ISDN BRI line</literallayout>
<command>chmod</command> command, if appropriate.</para></note>
<indexterm><primary>Tru64 Unix</primary></indexterm>
<para>When you have finished, it's time to initialize the NIS
<para>When you have finished, it is time to initialize the NIS
maps! FreeBSD includes a script named
<command>ypinit</command> to do this for you
(see its manual page for more information). Note that this
@ -2338,7 +2338,7 @@ nis_client_enable="YES"</programlisting>
<title>Barring Some Users from Logging On</title>
<para>In our lab, there is a machine <hostid>basie</hostid> that is
supposed to be a faculty only workstation. We don't want to take this
supposed to be a faculty only workstation. We do not want to take this
machine out of the NIS domain, yet the <filename>passwd</filename>
file on the master NIS server contains accounts for both faculty and
students. What can we do?</para>
@ -2810,9 +2810,9 @@ TWO (,hotel,test-domain)
</listitem>
<listitem>
<para><emphasis>Keep the administration accounts out of the NIS
maps</emphasis>. You don't want to be propagating administrative
maps</emphasis>. You do not want to be propagating administrative
accounts and passwords to machines that will have users that
shouldn't have access to those accounts.</para>
should not have access to those accounts.</para>
</listitem>
<listitem>
<para><emphasis>Keep the NIS master and slave
@ -3007,8 +3007,8 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 libscrypt.so@ -> libscrypt.so.2
linkend="kernelconfig">.</para>
<para>The <devicename>bpf</devicename> device is already
part of the <filename>GENERIC</filename> kernel that is
supplied with FreeBSD, so if you don't have a custom
kernel, you shouldn't need to create one in order to get
supplied with FreeBSD, so if you do not have a custom
kernel, you should not need to create one in order to get
DHCP working.</para>
<note>
<para>For those who are particularly security conscious,
@ -3018,7 +3018,7 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 libscrypt.so@ -> libscrypt.so.2
root). <devicename>bpf</devicename>
<emphasis>is</emphasis> required to use DHCP, but if
you are very sensitive about security, you probably
shouldn't add <devicename>bpf</devicename> to your
should not add <devicename>bpf</devicename> to your
kernel in the expectation that at some point in the
future you will be using DHCP.</para>
</note>
@ -4271,7 +4271,7 @@ natd_flags=""</programlisting>
<para>This section will cover the basics in configuring
<application>inetd</application> through its command-line
options and it's configuration file,
options and its configuration file,
<filename>/etc/inetd.conf</filename>.</para>
</sect2>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v 1.40 2001/08/10 22:58:09 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v 1.41 2001/08/11 20:35:41 jim Exp $
-->
<chapter id="backups">
@ -323,7 +323,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<screen>&prompt.root; <userinput>tar cf - . | rsh <replaceable>hostname</replaceable> dd of=<replaceable>tape-device</replaceable> obs=20b</userinput></screen>
<para>If you're worried about the security of backing over a network
<para>If you are worried about the security of backing over a network
you should use the &man.ssh.1; command instead of &man.rsh.1;.</para>
</sect2>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.39 2001/08/11 20:39:17 jim Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.40 2001/08/11 21:34:51 jim Exp $
-->
<chapter id="basics">
@ -373,7 +373,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
the middle of some task that can not be interrupted.</para>
<para><literal>SIGKILL</literal> can not be ignored by a process. This is
the <quote>I don't care what you are doing, stop right now</quote>
the <quote>I do not care what you are doing, stop right now</quote>
signal. If you send <literal>SIGKILL</literal> to a process then
FreeBSD will stop that process there and then<footnote>
<para>Not quite true&mdash;there are a few things that can not be
@ -499,7 +499,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
<para>Which shell do you use? It is really a matter of taste. If you
are a C programmer you might feel more comfortable with a C-like shell
such as <command>tcsh</command>. If you've come from Linux or are new
such as <command>tcsh</command>. If you have come from Linux or are new
to a Unix command line interface you might try <command>bash</command>.
The point is that each
shell has unique properties that may or may not work with your

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.23 2001/08/11 21:06:48 jim Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.24 2001/08/11 21:49:11 jim Exp $
-->
<chapter id="boot">
@ -433,7 +433,7 @@ boot:</screen>
<para>You can use <filename>kernel.GENERIC</filename> to
refer to the generic kernel that comes on the install
disk, or <filename>kernel.old</filename> to refer to
your previously installed kernel (when you've upgraded
your previously installed kernel (when you have upgraded
or configured your own kernel, for example).</para>
<note>
@ -447,7 +447,7 @@ boot:</screen>
<listitem>
<para>To load a kernel configuration script (an automated
script which does the things you'd normally do in the
script which does the things you would normally do in the
kernel boot-time configurator):</para>
<screen><userinput>load -t userconfig_script
@ -646,7 +646,7 @@ console none unknown off insecure</programlisting>
<command>init</command> will attempt to run the script
<filename>/etc/rc.shutdown</filename>, and then proceed to send
all processes the <literal>TERM</literal> signal, and subsequently
the <literal>KILL</literal> signal to any that don't terminate
the <literal>KILL</literal> signal to any that do not terminate
timely.</para>
</sect1>
</chapter>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.17 2001/08/11 21:50:37 jim Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.18 2001/08/14 00:37:13 chern Exp $
-->
<chapter id="config-tuning">
@ -185,7 +185,7 @@
largest swap partition. Keeping the swap partitions near the
same size will allow the kernel to optimally stripe swap space
across the disks. Do not worry about overdoing it a little,
swap space is the saving grace of Unix. Even if you don't
swap space is the saving grace of Unix. Even if you do not
normally use much swap, it can give you more time to recover
from a runaway program before being forced to reboot.</para>
</sect3>
@ -194,7 +194,7 @@
<title>Why Partition?</title>
<para> Why partition at all? Why not create one big root
partition and be done with it? Then I don't have to worry
partition and be done with it? Then I do not have to worry
about undersizing things!</para>
<para>There are several reasons this is not a good idea.

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.82 2001/08/12 20:16:11 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.83 2001/08/13 06:49:29 jim Exp $
-->
<chapter id="cutting-edge">
@ -266,7 +266,7 @@ subscribe cvs-all</programlisting>
<para>&os.stable; is our development branch from which major releases
are made. Changes go into this branch at a different pace, and
with the general assumption that they've first gone into
with the general assumption that they have first gone into
&os.current; first for testing. This is <emphasis>still</emphasis>
a development branch, however, and this means that at any given time,
the sources for &os.stable; may or may not be suitable for any
@ -477,7 +477,7 @@ subscribe cvs-all</programlisting>
of interest to you. Updates are generated on the fly by the server,
according to what you have and what you want to have.
<application>Anonymous CVS</application> is quite a bit more
simplistic than CVSup in that it's just an extension to
simplistic than CVSup in that it is just an extension to
<application>CVS</application> which allows it to pull changes
directly from a remote CVS repository.
<application>CVSup</application> can do this far more efficiently,
@ -505,8 +505,8 @@ subscribe cvs-all</programlisting>
<para>There are other trade-offs, of course. If you inadvertently
wipe out portions of your archive, <application>CVSup</application>
will detect and rebuild the damaged portions for you.
<application>CTM</application> won't do this, and if you wipe some
portion of your source tree out (and don't have it backed up) then
<application>CTM</application> will not do this, and if you wipe some
portion of your source tree out (and do not have it backed up) then
you will have to start from scratch (from the most recent CVS
<quote>base delta</quote>) and rebuild it all with CTM or, with
anoncvs, simply delete the bad bits and resync.</para>
@ -806,7 +806,7 @@ Script done, &hellip;</screen>
steps necessary to rebuild the system into a number of
sub-steps.</para>
<para>Most of the time you won't need to pass any parameters to
<para>Most of the time you will not need to pass any parameters to
&man.make.1;, and so your command like will look like
this:</para>
@ -1170,7 +1170,7 @@ Script done, &hellip;</screen>
<para>If you used &man.mergemaster.8; to
update <filename>/etc</filename>, then your
<filename>MAKEDEV</filename> script should have been updated
already, though it can't hurt to check (with &man.diff.1;)
already, though it cannot hurt to check (with &man.diff.1;)
and copy it manually if necessary.</para>
</step>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.50 2001/08/11 21:34:51 jim Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.51 2001/08/14 22:06:03 chern Exp $
-->
<chapter id="disks">
@ -35,7 +35,7 @@
. Then, if the
first drive fails, or is attacked by a virus, or is scribbled upon by an
operating system defect, he can easily recover by instructing the BIOS
to logically swap the drives. It's like switching the cables on the
to logically swap the drives. It is like switching the cables on the
drives, but without having to open the case.</para>
<indexterm><primary>SCSI</primary></indexterm>
@ -68,18 +68,18 @@
the older SCSI drive is reporting numerous soft errors, and reports
this fact to Bill.</para>
<para>After several more days, Bill decides it's time to address the
<para>After several more days, Bill decides it is time to address the
situation, so he grabs an identical SCSI drive from the disk drive
"archive" in the back room. An initial surface scan indicates that
this drive is functioning well, so Bill installs this drive as SCSI
unit four, and makes an image copy from drive zero to drive four. Now
that the new drive is installed and functioning nicely, Bill decides
that it's a good idea to start using it, so he uses features in the
that it is a good idea to start using it, so he uses features in the
SCSI BIOS to re-order the disk drives so that the system boots from
SCSI unit four. FreeBSD boots and runs just fine.</para>
<para>Fred continues his work for several days, and soon Bill and Fred
decide that it's time for a new adventure -- time to upgrade to a
decide that it is time for a new adventure -- time to upgrade to a
newer version of FreeBSD. Bill removes SCSI unit zero because it was
a bit flaky, and replaces it with another identical disk drive from
the "archive." Bill then installs the new version of FreeBSD onto the
@ -87,7 +87,7 @@
installation goes well.</para>
<para>Fred uses the new version of FreeBSD for a few days, and certifies
that it is good enough for use in the engineering department...it's
that it is good enough for use in the engineering department...it is
time to copy all of his work from the old version. So Fred mounts
SCSI unit four (the latest copy of the older FreeBSD version). Fred
is dismayed to find that none of his precious work is present on SCSI
@ -239,7 +239,7 @@
<filename>spool/</filename>,
and various types of temporary files, and
as such, may get filled up. Filling up the root filesystem
isn't a good idea, so splitting <filename>/var</filename> from
is not a good idea, so splitting <filename>/var</filename> from
<filename>/</filename> is often favorable.</para>
<para>Another common reason to contain certain directory trees on
@ -471,7 +471,7 @@
<para><option>-a</option> and <option>-A</option> are used to
unmount all mounted filesystems, possibly modified by the
filesystem types listed after <option>-t</option>.
<option>-A</option>, however, doesn't attempt to unmount the
<option>-A</option>, however, does not attempt to unmount the
root filesystem.</para>
</sect2>
</sect1>
@ -502,7 +502,7 @@
wide variations of procedures to do this, the details are beyond
the scope of this document.</para>
<para>Login as user <username>root</username>. After you've installed the
<para>Login as user <username>root</username>. After you have installed the
drive, inspect <filename>/var/run/dmesg.boot</filename> to ensure the new
disk was found. Continuing with our example, the newly added drive will
be <devicename>da1</devicename> and we want to mount it on
@ -609,7 +609,7 @@
disk in post-install mode, <application>Sysinstall</application>
will not create entries
in <filename>/etc/fstab</filename> for you, so the mount point
you specify isn't important.</para>
you specify is not important.</para>
<para>You are now ready to write the new label to the disk and
create a file system on it. Do this by typing
@ -770,7 +770,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para><devicename>md</devicename> is a simple, efficient means to create memory
filesystems.</para>
<para>Simply take a filesystem you've prepared with, for
<para>Simply take a filesystem you have prepared with, for
example, &man.vnconfig.8;, and:</para>
<example>
@ -1065,7 +1065,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<title>Introduction</title>
<para>CDs have a number of features that differentiate them from
conventional disks. Initially, they weren't writable by the
conventional disks. Initially, they were not writable by the
user. They are designed so that they can be read continuously without
delays to move the head between tracks. They are also much easier
to transport between systems than similarly sized media were at the

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v 1.64 2001/08/06 22:59:24 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v 1.65 2001/08/08 17:17:20 dd Exp $
-->
<appendix id="eresources">
@ -357,7 +357,7 @@
more specialized (and demanding) audiences and are probably not of
interest to the general public. It is also a good idea to establish a
presence in the technical lists before joining one of these limited
lists so that you'll understand the communications etiquette involved.</para>
lists so that you will understand the communications etiquette involved.</para>
<informaltable frame="none">
<tgroup cols="2">
@ -516,7 +516,7 @@
<programlisting>subscribe &lt;listname&gt; [&lt;optional address&gt;]</programlisting>
in the body of your message. For example, to subscribe yourself to
<literal>freebsd-announce</literal>, you'd do:</para>
<literal>freebsd-announce</literal>, you would do:</para>
<screen>&prompt.user; <userinput>mail majordomo@FreeBSD.org</userinput>
subscribe freebsd-announce

18
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.89 2001/08/14 22:32:25 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.90 2001/08/16 16:09:16 nik Exp $
-->
<chapter id="install">
@ -1257,7 +1257,7 @@ Mounting root from ufs:/dev/md0c
<title>Select The Distribution Set</title>
<para>I chose to install everything using the "All" option since I
had the hard drive space. If you're concerned about space,
had the hard drive space. If you are concerned about space,
consider the other distribution options.</para>
<para>Select "All" using the arrow keys to highlight the item and
@ -2107,7 +2107,7 @@ Press [ENTER] now to invoke an editor on /etc/exports
[ Yes ] No</screen>
<para>This can be done later using /stand/sysinstall if you don't
<para>This can be done later using /stand/sysinstall if you do not
have graphics card and monitor information handy. Equipment
damage can occur if settings are incorrect. Select [Yes] and
press <keycap>ENTER</keycap> to proceed with configuring the
@ -2260,14 +2260,14 @@ when you've finished.</screen>
<para>If the monitor display needs adjusted,
<application>xvidtune</application> can be ran
to adjust them. There are warnings that improper settings can
damage your equipment. Heed them. If in doubt, don't do
damage your equipment. Heed them. If in doubt, do not do
it. Instead, use the monitor controls to adjust the display for
x-windows. There may be some display differences when switching
back to text mode, but it's better than damaging equipment. The
back to text mode, but it is better than damaging equipment. The
<application>xvidtune</application> can be ran later using
<command>/stand/sysinstall</command>.</para>
<para>If it doesn't appear or is distorted, kill the server with
<para>If it does not appear or is distorted, kill the server with
<keycombo action='simul'>
<keycap>CTRL</keycap><keycap>ALT</keycap><keycap>BACKSPACE</keycap>
</keycombo>
@ -2598,7 +2598,7 @@ when you've finished.</screen>
<title>FreeBSD Bootup</title>
<para>If everything goes well, you will see similar messages scroll
off the screen and you'll arrive at a login prompt. You can view
off the screen and you will arrive at a login prompt. You can view
the content of the messages by pressing <keycap>SCROLL-LOCK</keycap>
and using <keycap>PgUp</keycap> and <keycap>PgDn</keycap>.
Pressing <keycap>SCROLL-LOCK</keycap> again will return
@ -3137,9 +3137,9 @@ Please press any key to reboot.</screen>
<step>
<title>Booting Up for the Install</title>
<para>It's now time to go ahead and start the install. Put
<para>It is now time to go ahead and start the install. Put
the <filename>kern.flp</filename> floppy in the floppy
drive of the machine you're doing the headless install
drive of the machine you are doing the headless install
on, and power on the machine.</para>
</step>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml,v 1.57 2001/08/10 22:58:13 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml,v 1.58 2001/08/14 23:02:37 logo Exp $
-->
<chapter id="introduction">
@ -620,7 +620,7 @@
opposite. Due to the additional complexities that can evolve
in the commercial use of GPL software we do, however, prefer
software submitted under the more relaxed BSD copyright when
it's a reasonable option to do so.</para>
it is a reasonable option to do so.</para>
</sect2>
<sect2 id="development">

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.59 2001/08/10 16:18:59 bmah Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.60 2001/08/11 21:34:51 jim Exp $
-->
<chapter id="kernelconfig">
@ -673,7 +673,7 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 required</programli
<para>This option provides for System V shared memory. The most
common use of this is the XSHM extension in X, which many
graphics-intensive programs will automatically take advantage of for
extra speed. If you use X, you'll definitely want to include
extra speed. If you use X, you will definitely want to include
this.</para>
<programlisting>options SYSVSEM #SYSV-style semaphores</programlisting>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml,v 1.20 2001/08/09 23:42:31 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml,v 1.21 2001/08/10 22:58:14 chern Exp $
-->
<chapter id="kernelopts">
@ -72,7 +72,7 @@
<para>People familiar with the C language will immediately recognize that
everything could be counted as a <quote>config option</quote> where there
is at least a single <literal>#ifdef</literal> referencing it...
However, it's unlikely that many people would put</para>
However, it is unlikely that many people would put</para>
<programlisting>options notyet,notdef</programlisting>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml,v 1.50 2001/08/12 20:13:54 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml,v 1.51 2001/08/12 20:17:49 murray Exp $
-->
<chapter id="linuxemu">
@ -524,7 +524,7 @@ disco.example.com 7115-70839-20412</screen>
<filename>linux_devtools-6.1</filename> you may have to use version
5.2 of these packages.</para>
<para>If you want to run the intelligent agent, you'll
<para>If you want to run the intelligent agent, you will
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>
@ -547,7 +547,7 @@ disco.example.com 7115-70839-20412</screen>
<indexterm><primary>kernel tuning</primary></indexterm>
<para>As described in the Oracle installation guide, you need to set
the maximum size of shared memory. Don't use
the maximum size of shared memory. Do not use
<literal>SHMMAX</literal> under FreeBSD. <literal>SHMMAX</literal>
is merely calculated out of <literal>SHMMAXPGS</literal> and
<literal>PGSIZE</literal>. Therefore define
@ -668,7 +668,7 @@ export PATH</programlisting>
&prompt.root; <userinput>cd $ORACLE_HOME/network/lib</userinput>
&prompt.root; <userinput>make -f ins_network.mk install</userinput></screen>
<para>Don't forget to run <filename>root.sh</filename> again!</para>
<para>Do not forget to run <filename>root.sh</filename> again!</para>
<sect3 id="linuxemu-patch-root">
<title>Patching root.sh</title>
@ -699,7 +699,7 @@ export PATH</programlisting>
#
# Define variables to be used in this script</programlisting>
<para>When you don't install Oracle from CD, you can patch the source
<para>When you do not install Oracle from CD, you can patch the source
for <filename>root.sh</filename>. It is called
<filename>rthd.sh</filename> and is located in the
<filename>orainst</filename> directory in the source tree.</para>
@ -967,7 +967,7 @@ export PATH</programlisting>
<screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput>
&prompt.root; <userinput>dd if=mfsroot.flp of=/dev/fd0</userinput> </screen>
<para>Don't forget to use different disks for the two images,
<para>Do not forget to use different disks for the two images,
then boot from the floppy with the kern.flp-image on it
and follow instructions. I used the following disk
layout:</para>
@ -1069,7 +1069,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
<para>Change the <emphasis>SUPHOST</emphasis>-value
appropriately. The supfiles in
<filename>/usr/share/examples/cvsup</filename> should be
fine. If you don't want to load all the docfiles, leave the
fine. If you do not want to load all the docfiles, leave the
corresponding <emphasis>DOCSUPFILE</emphasis>-entry
inactive. Starting <application>cvsup</application>
to get the latest stable-sources is then very easy:</para>
@ -1128,7 +1128,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
<para>I had some trouble downloading the required RPM-files (for
4.3 stable, 2nd May 2001), so you might try one of the
following locations (if all the others fail and the following
aren't out of date):</para>
are not out of date):</para>
<itemizedlist>
<listitem><para>ftp7.de.freebsd.org/pub/FreeBSD/distfiles/rpm</para></listitem>
@ -1189,7 +1189,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
RedHat Tcl package (as is stated in the FreeBSD Handbook):
<filename>tcl-8.0.5-30.i386.rpm</filename> (otherwise the
relinking during <application>Oracle</application> install
won't work). There are some other issues regarding
will not work). There are some other issues regarding
relinking of <application>Oracle</application>, but that is
a Oracle-Linux issue, not FreeBSD specific as far as I
understand it.</para>
@ -1364,7 +1364,7 @@ Shell: /bin/sh</programlisting>
choose to create them as simple directories, as they are all
located on the same RAID 5 anyway:</para>
<para>First we'll set owners and right of some directories (as
<para>First we will set owners and right of some directories (as
user <username>root</username>):</para>
<screen>&prompt.root; <userinput>chmod 775 /oracle</userinput>
@ -1373,7 +1373,7 @@ Shell: /bin/sh</programlisting>
&prompt.root; <userinput>chown idsadm:sapsys /compat/linux/usr/sap</userinput>
&prompt.root; <userinput>chmow 775 /compat/linux/usr/sap</userinput> </screen>
<para>Second we'll create directories as user ora&lt;sid&gt;. These
<para>Second we will create directories as user ora&lt;sid&gt;. These
will all be subdirectories of /oracle/IDS:</para>
<screen>&prompt.root; <userinput>su - oraids</userinput>
@ -1417,7 +1417,7 @@ sapmsIDS 3600/tcp # SAP Message Server. 3600 + Instance-Number</programlisting>
<title>Necessary Locales</title>
<indexterm><primary>locale</primary></indexterm>
<para>SAP requires at least two locales that aren't part of
<para>SAP requires at least two locales that are not part of
the default RedHat installation. SAP offers the required
RPMs as download from their FTP-server (which is only
accessible if you are a customer with OSS-access). See note
@ -1425,7 +1425,7 @@ sapmsIDS 3600/tcp # SAP Message Server. 3600 + Instance-Number</programlisting>
<para>It is also possible to just create appropriate links
(for example from <emphasis>de_DE</emphasis> and
<emphasis>en_US</emphasis> ), but I wouldn't recommend this
<emphasis>en_US</emphasis> ), but I would not recommend this
for a production system (so far it worked with the IDES
system without any problems, though). The following locales
are needed:</para>
@ -1702,7 +1702,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
</informaltable>
<para>If I had not copied the CDs to the different locations,
then the SAP-Installer can't find the CD needed (identified
then the SAP-Installer cannot find the CD needed (identified
by the <filename>LABEL.ASC</filename>-File on CD) and would
then ask you to insert / mount the CD and confirm or enter
the mount path.</para>
@ -1711,7 +1711,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
error-free. In my case, it requested EXPORT4 again (but
indicated the correct key (6_LOCATI ON, then 7_LOCATION
etc.), so one can just continue with entering the correct
values. Don't get irritated.</para>
values. Do not get irritated.</para>
<para>Apart from some problems mentioned below, everything
should go straight through up to the point where the Oracle
@ -1748,12 +1748,12 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
<para>See the corresponding SAP-Notes or Oracle Readmes for
further information. If this is no option (at the time of
installation I didn't have enough time to check this), one
installation I did not have enough time to check this), one
could use the original binaries, or use the relinked
binaries from an original RedHat System.</para>
<para>For compiling the intelligent agent, the RedHat Tcl
package must be installed. If you can't get
package must be installed. If you cannot get
<filename>tcl-8.0.3-20.i386.rpm</filename>, a newer one like
<filename>tcl-8.0.5-30.i386.rpm</filename> for RedHat 6.1
should also do.</para>
@ -1879,7 +1879,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
<programlisting>umask 0; lsnrctl start</programlisting>
<para>Otherwise you might get ORA-12546 as the sockets won't
<para>Otherwise you might get ORA-12546 as the sockets will not
have the correct permissions. See SAP note 072984.</para>
</sect3>
</sect2>
@ -1891,7 +1891,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
<title>Request SAP R/3 License Key</title>
<para>This is needed, as the temporary license is only valid for
four weeks. Don't forget to enter the correct Operating System:
four weeks. Do not forget to enter the correct Operating System:
(X) Other: <emphasis>FreeBSD 4.3 Stable</emphasis>. First get
the hardware key. Log on as user <username>idsadm</username> and
call <command>saplicense</command>:</para>
@ -2061,7 +2061,7 @@ STATUS=OK (had status ERROR)
<sect3 id="oraviewvrffilenotfound">
<title>oraview.vrf FILE NOT FOUND During Oracle Installation</title>
<para>You haven't deselected <emphasis>Oracle On-Line Text Viewer</emphasis>
<para>You have not deselected <emphasis>Oracle On-Line Text Viewer</emphasis>
before starting the installation. This is marked for installation even
though this option is currently not available for Linux. Deselect this
product inside the Oracle installation menu and restart installation.</para>
@ -2121,7 +2121,7 @@ rscp/TCP0B =TCP0B
<screen>&prompt.root; <userinput>umask 0; lsnrctl start</userinput></screen>
<para>Otherwise one might get ORA-12546 as the sockets won't
<para>Otherwise one might get ORA-12546 as the sockets will not
have the correct permissions. See SAP note 0072984.</para>
</sect3>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.32 2001/08/15 20:08:25 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.33 2001/08/15 20:14:40 logo Exp $
-->
<chapter id="mail">
@ -761,7 +761,7 @@ freefall MX 20 who.cdrom.com</programlisting>
server. If you are not, or cannot, run your own DNS server, talk
to your ISP or whoever does your DNS for you.</para>
<para>If you're doing virtual email hosting, the following
<para>If you are doing virtual email hosting, the following
information will come in handy. For the sake of an example, we
will assume you have a customer with their own domain, in this
case <hostid role="domainname">customer1.org</hostid> and you want

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.144 2001/08/11 21:34:51 jim Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.145 2001/08/12 12:04:21 kuriyama Exp $
-->
<appendix id="mirrors">
@ -1051,7 +1051,7 @@
program (like <command>ls</command> or <command>grep</command>)
by referencing the CVS module name. Of course,
<application>anoncvs</application> is also only good for
read-only operations on the CVS repository, so if it's your
read-only operations on the CVS repository, so if it is your
intention to support local development in one repository shared
with the FreeBSD project bits then
<application>CVSup</application> is really your only
@ -1527,7 +1527,7 @@
Megabytes of <command>gzip</command>'d data is common for the
<filename>XEmpty</filename> deltas.</para>
<para>Once you've picked a base delta to start from, you will also
<para>Once you have picked a base delta to start from, you will also
need all deltas with higher numbers following it.</para>
</sect2>
@ -2323,8 +2323,8 @@ src-all</programlisting>
take every file associated with the collection and tag you
chose in the configuration file. However, this is not always
what you want, especially if you are synching the doc, ports, or
www trees &mdash; most people can't read four or five
languages, and therefore they don't need to download the
www trees &mdash; most people cannot read four or five
languages, and therefore they do not need to download the
language-specific files. If you are
<application>CVSup</application>ing the ports collection, you
can get around this by specifying each collection individually

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml,v 1.13 2001/08/09 23:42:35 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml,v 1.14 2001/08/11 21:34:53 jim Exp $
-->
<chapter id="sound">
@ -323,7 +323,7 @@ pcm0: &lt;Aureal Vortex 8830&gt; at memory 0xfeb40000 irq 5 (4p/1r +channels dup
</question>
<answer>
<para>One or more of the device nodes wasn't created
<para>One or more of the device nodes was not created
correctly. Repeat the steps above.</para>
</answer>
</qandaentry>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v 1.22 2001/07/19 23:18:07 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v 1.23 2001/08/09 23:42:32 chern Exp $
-->
<chapter id="policies">
@ -49,7 +49,7 @@
<para>It is of course not acceptable to add a person or group as
maintainer unless they agree to assume this duty. On the other hand it
doesn't have to be a committer and it can easily be a group of
does not have to be a committer and it can easily be a group of
people.</para>
</sect1>
@ -357,7 +357,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<title>Shared Libraries</title>
<para>If you are adding shared library support to a port or other piece of
software that doesn't have one, the version numbers should follow these
software that does not have one, the version numbers should follow these
rules. Generally, the resulting numbers will have nothing to do with
the release version of the software.</para>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.135 2001/08/10 22:58:16 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.136 2001/08/11 21:34:52 jim Exp $
-->
<chapter id="ports">
@ -136,7 +136,7 @@
<listitem>
<para>Some packages have compile time options relating to what they
can and can't do. For example, <application>Apache</application>
can and cannot do. For example, <application>Apache</application>
can be configured with a wide variety of different builtin options.
By building from the port you do not have to accept the default
options, and can set them yourself.</para>
@ -284,7 +284,7 @@ local: lsof-4.56.4.tgz remote: lsof-4.56.4.tgz
&prompt.root; <userinput>pkg_add <replaceable>lsof-4.56.4.tgz</replaceable></userinput></screen>
</example>
<para>If you don't have a source of local packages (such as a
<para>If you do not have a source of local packages (such as a
FreeBSD CDROM set) then it will probably be easier to use the
-r option to &man.pkg.add.1;. This will cause the utility to
automatically determine the correct object format and release
@ -896,7 +896,7 @@ Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%
<indexterm><primary>imake</primary></indexterm>
<para>Some ports that use &man.imake.1; (a part of the X Windows
System) don't work well with <makevar>PREFIX</makevar>, and will insist on
System) do not work well with <makevar>PREFIX</makevar>, and will insist on
installing under <filename>/usr/X11R6</filename>. Similarly, some Perl ports
ignore <makevar>PREFIX</makevar> and install in the Perl tree. Making these
ports respect <makevar>PREFIX</makevar> is a difficult or impossible
@ -1254,7 +1254,7 @@ arcade game.</screen>
<sect2 id="ports-broken">
<title>Help! This Port Is Broken!</title>
<para>If you come across a port that doesn't work for you, there are
<para>If you come across a port that does not work for you, there are
a few things you can do, including:</para>
<orderedlist>

14
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.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.50 2001/08/15 14:09:06 kuriyama Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.51 2001/08/15 20:14:41 logo Exp $
-->
<chapter id="ppp-and-slip">
@ -206,7 +206,7 @@
configuration values).</para>
<note><para>It should be noted that the tunnel driver creates devices
on demand, so <command>ifconfig -a</command> won't necessarily
on demand, so <command>ifconfig -a</command> will not necessarily
show up with any <devicename>tun</devicename> devices.</para></note>
</sect3>
@ -606,7 +606,7 @@ protocol: ppp</screen>
The string <replaceable>y.y.y.y</replaceable> should be
replaced by the IP address that your ISP indicated for
their gateway (the machine to which you connect). If
your ISP hasn't given you a gateway address, use <hostid
your ISP has not given you a gateway address, use <hostid
role="netmask">10.0.0.2/0</hostid>. If you need to use
a <quote>guessed</quote> address, make sure that you
create an entry in
@ -835,7 +835,7 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting>
<emphasis>shell</emphasis> for all of your dialup users.
This is an example from <filename>/etc/password</filename>
for a dialup PPP user with username
<username>pchilds</username> (remember don't directly edit
<username>pchilds</username> (remember do not directly edit
the password file, use <command>vipw</command>).</para>
<programlisting>pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlisting>
@ -1077,7 +1077,7 @@ set nbns 203.14.100.5</programlisting>
<listitem>
<para>Your ISP will not normally require that you log into
the server if you're using PAP or CHAP. You must
the server if you are using PAP or CHAP. You must
therefore disable your <quote>set login</quote>
string.</para>
</listitem>
@ -1153,7 +1153,7 @@ set nbns 203.14.100.5</programlisting>
<programlisting>hostname="foo.bar.com"</programlisting>
<para>If your ISP has supplied you with a static IP address and
name, it's probably best that you use this name as your host
name, it is probably best that you use this name as your host
name.</para>
<para>Look for the <literal>network_interfaces</literal> variable.
@ -1219,7 +1219,7 @@ set nbns 203.14.100.5</programlisting>
4 !bg sendmail -bd -q30m</programlisting>
<indexterm><primary>SMTP</primary></indexterm>
<para>If you don't like this, it is possible to set up a
<para>If you do not like this, it is possible to set up a
<quote>dfilter</quote> to block SMTP traffic. Refer to the
sample files for further details.</para>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v 1.70 2001/08/14 06:43:35 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v 1.71 2001/08/14 22:06:10 chern Exp $
-->
<chapter id="security">
@ -1118,7 +1118,7 @@ CURE MIKE BANE HIM RACY GORE</screen>
<sect2>
<title>Generating a Single one-time Password</title>
<para>Once you've initialized S/Key, when you login you will be
<para>Once you have initialized S/Key, when you login you will be
presented with a prompt like this:</para>
<screen>&prompt.user; <userinput>telnet example.com</userinput>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.42 2001/08/11 21:34:53 jim Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.43 2001/08/14 22:06:10 chern Exp $
-->
<chapter id="serialcomms">
@ -916,7 +916,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
<indexterm><primary>dial-in service</primary></indexterm>
<para>Configuring your FreeBSD system for dial-in service is very
similar to connecting terminals except that you're dealing with
similar to connecting terminals except that you are dealing with
modems instead of terminals.</para>
<sect2>
@ -1467,7 +1467,7 @@ AT&amp;B2&amp;W</programlisting>
<command>getty</command> process on the appropriate communications
port and is waiting for the modem to accept a call.</para>
<para>If the <acronym>DTR</acronym> indicator doesn't light, login to
<para>If the <acronym>DTR</acronym> indicator does not light, login to
the FreeBSD system through the console and issue a <command>ps
ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port. You should see
@ -2572,8 +2572,8 @@ start</programlisting>
<para>However, many machines do not support this option and will refuse
to boot if you have no display hardware in the system. With these
machines, you'll have to leave some kind of graphics card plugged in,
(even if it's just a junky mono board) although you will not have to
machines, you will have to leave some kind of graphics card plugged in,
(even if it is just a junky mono board) although you will not have to
attach a monitor into it. You might also try installing an AMI
BIOS.</para>
</sect2>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml,v 1.13 2001/08/09 23:42:35 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml,v 1.14 2001/08/11 21:34:53 jim Exp $
-->
<chapter id="sound">
@ -323,7 +323,7 @@ pcm0: &lt;Aureal Vortex 8830&gt; at memory 0xfeb40000 irq 5 (4p/1r +channels dup
</question>
<answer>
<para>One or more of the device nodes wasn't created
<para>One or more of the device nodes was not created
correctly. Repeat the steps above.</para>
</answer>
</qandaentry>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.25 2001/08/10 22:58:17 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.26 2001/08/14 06:48:46 dd Exp $
-->
<chapter id="users">
@ -239,8 +239,8 @@
<para>So, the first thing you should do after reading this
chapter, is to create an unprivileged user account for yourself
for general usage, if you haven't already. This applies equally
whether you're running a multi-user or single-user machine.
for general usage, if you have not already. This applies equally
whether you are running a multi-user or single-user machine.
Later in this chapter, we discuss how to create additional
accounts, and how to change between the normal user and
superuser.</para>
@ -277,7 +277,7 @@
<secondary><username>nobody</username></secondary>
</indexterm>
<para><username>nobody</username> is the generic unprivileged
system user. However, it's important to keep in mind that the
system user. However, it is important to keep in mind that the
more services that use <username>nobody</username>, the more
files and processes that user will become associated with, and
hence the more privileged that user becomes.</para>
@ -416,17 +416,17 @@ Goodbye!
added users. We then saved the configuration, and then
created an account for <username>jru</username>, and we made
sure <username>jru</username> is in <username>wheel</username>
group (which we'll see is important later).</para>
group (which we will see is important later).</para>
<note>
<para>The password you type in isn't echoed, nor are asterisks
displayed. Make sure you don't mistype the password twice.
<para>The password you type in is not echoed, nor are asterisks
displayed. Make sure you do not mistype the password twice.
</para>
</note>
<note>
<para>Just use <command>adduser</command> without arguments
from now on, and you won't have to go through changing the
from now on, and you will not have to go through changing the
defaults. If the program asks you to change the defaults,
exit the program, and try the <option>-s</option>
option.</para>
@ -489,12 +489,12 @@ Goodbye!
</step>
</procedure>
<para><command>rmuser</command> can't be used to remove
<para><command>rmuser</command> cannot be used to remove
superuser accounts, since that is almost always an indication
of massive destruction.</para>
<para>By default, an interactive mode is used, which attempts to
make sure you know what you're doing.</para>
make sure you know what you are doing.</para>
<example>
<title>rmuser Interactive Account Removal</title>
@ -955,11 +955,11 @@ passwd: done</screen>
colon-delimited fields. The first field is the group name, the
second is the encrypted password, the third the group ID, and the
fourth the comma-delimited list of members. It can safely be edited
by hand (assuming, of course, that you don't make any syntax
by hand (assuming, of course, that you do not make any syntax
errors!). For a more complete description of the syntax, see the
&man.group.5; manual page.</para>
<para>If you don't want to edit <filename>/etc/group</filename>
<para>If you do not want to edit <filename>/etc/group</filename>
manually, you can use the &man.pw.8; command to add and edit groups.
For example, to add a group called <groupname>teamtwo</groupname> and
then confirm that it exists you can use:</para>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml,v 1.46 2001/08/15 19:40:17 logo Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml,v 1.47 2001/08/15 20:14:42 logo Exp $
-->
<chapter id="x11">
@ -49,7 +49,7 @@
<para>Your only decision is which version of XFree86 to run.
XFree86 3.X is the maintenance branch of XFree86 development.
It's very stable, and it supports a huge number of graphics
It is very stable, and it supports a huge number of graphics
cards. However, no new development is happening there. XFree86
4.X is a redesign of XFree86. As well as introducing many new
features (including much better support for fonts and
@ -124,7 +124,7 @@
<application>XFree86</application> uses to talk to the graphics
hardware. With most chipsets, this can be automatically
determined, but it is still useful to know in case the automatic
detection doesn't work correctly.</para>
detection does not work correctly.</para>
<para>Video memory on the graphic adapter determines the
resolution and color depth the target system can run at. This
@ -640,7 +640,7 @@ EndSection</programlisting>
files into this directory you need to use
<application>ttmkfdir</application> to create a
<filename>fonts.dir</filename> file so that the X font renderer
knows that you've installed these new files. There is a FreeBSD
knows that you have installed these new files. There is a FreeBSD
port for <port>x11-fonts/ttmkfdir</port> in
<filename>/usr/ports/x11-fonts/ttmkfdir</filename>.</para>
<screen>&prompt.root; <userinput>cd /usr/X11R6/lib/X11/fonts/TrueType</userinput>
@ -690,9 +690,9 @@ EndSection</programlisting>
<programlisting>dir "/usr/X11R6/lib/X11/Type1"</programlisting>
<para>And likewise for the other font directories (URW, truetype, etc)
containing fonts you'd like anti-aliased. Anti-aliasing makes
containing fonts you would like anti-aliased. Anti-aliasing makes
sense only for scalable fonts (basically, Type1 and TrueType) so
don't include bitmap font directories here. The
do not include bitmap font directories here. The
directories which you included here can now be commented out
of your <filename>XF86Config</filename> file.</para>
@ -726,7 +726,7 @@ match any family == "console" edit family =+ "mono";</programlisting>
<para>Supposing you want to use the
<literal>Lucidux</literal> fonts whenever
monospaced fonts are required (these look nice, and don't seem
monospaced fonts are required (these look nice, and do not seem
to suffer from the spacing problem), you could replace that last
line with these:</para>
@ -1066,7 +1066,7 @@ DisplayManager.requestPort: 0</screen>
should simply replace the line that starts your current window
manager with one that starts
<application>/usr/X11R6/bin/gnome-session</application> instead. If you
haven't added anything special to your configuration file,
have not added anything special to your configuration file,
then it is enough to simply type:</para>
<screen>&prompt.root; <userinput>echo "/usr/X11R6/bin/gnome-session" > ~/.xinitrc</userinput></screen>
@ -1074,7 +1074,7 @@ DisplayManager.requestPort: 0</screen>
<para>That's it. Type <command>startx</command> and you will be in the
<application>GNOME</application> desktop environment.</para>
<note><para>If you're running a display manager like
<note><para>If you are running a display manager like
<application>XDM</application>, this will not work. Instead,
you should create an executable <filename>.xsession</filename>
file with the same command in it. To do this, edit your file
@ -1137,7 +1137,7 @@ DisplayManager.requestPort: 0</screen>
<sect3 id="x11-wm-kde2-install">
<title>Installing KDE2</title>
<para>At the time of writing, a package for kde2 doesn't
<para>At the time of writing, a package for kde2 does not
exist yet. No problem! The ports tree hides all the
complexity of building a package from source. To install
<application>KDE2</application>, do this :</para>
@ -1149,7 +1149,7 @@ DisplayManager.requestPort: 0</screen>
Internet, configure and compile <application>KDE2</application>,
install the applications, and then clean up after itself.</para>
<para>Now you're going to have to tell the X server to launch
<para>Now you are going to have to tell the X server to launch
<application>KDE2</application> instead of a default window manager.
Do this by typing this:</para>
@ -1157,7 +1157,7 @@ DisplayManager.requestPort: 0</screen>
<para>Now, whenever you go into X-Windows,
<application>KDE2</application> will be your
desktop. (Note: this will not work if you're logging in via
desktop. (Note: this will not work if you are logging in via
a display manager like <filename>xdm</filename>. In that
case you have two options: create an
<filename>.xsession</filename> file as described in the
@ -1174,7 +1174,7 @@ DisplayManager.requestPort: 0</screen>
<title>More Details on KDE2</title>
<para>Now that <application>KDE2</application> is installed on
your system, you'll find that you can learn a lot from its
your system, you will find that you can learn a lot from its
help pages, or just by pointing and clicking at various menus.
Windows or Mac users will feel quite at home.</para>
@ -1189,7 +1189,7 @@ DisplayManager.requestPort: 0</screen>
<sect3 id="x11-wm-kde2-kdm">
<title>The KDE display manager</title>
<para>If you're an administrator on a multi-user system, you
<para>If you are an administrator on a multi-user system, you
may like to have a graphical login screen to welcome users.
You can use <link
linkend="x-xdm"><filename>xdm</filename></link>, as described
@ -1199,7 +1199,7 @@ DisplayManager.requestPort: 0</screen>
In particular, users can easily choose (via a menu) which
desktop environment (<application>KDE2</application>,
<application>GNOME</application>, or something else) to run
after logging on. If you're slightly adventurous and you want
after logging on. If you are slightly adventurous and you want
this added flexibility and visual appeal, read on.</para>
<para>To begin with, run the <application>KDE2</application>
@ -1216,7 +1216,7 @@ DisplayManager.requestPort: 0</screen>
type <userinput>kcontrol</userinput>.</para>
<para> Click on the icon on the left marked "System", then on
"Login manager". On the right you'll see various configurable
"Login manager". On the right you will see various configurable
options, which the <application>KDE</application> manual will
explain in greater detail. Click on "sessions" on the right.
Depending on what window managers or desktop environments you
@ -1228,7 +1228,7 @@ DisplayManager.requestPort: 0</screen>
Include a label <literal>failsafe</literal>.</para>
<para> Play with the other menus as you like (those are mainly
cosmetic and self-explanatory). When you're done, click on
cosmetic and self-explanatory). When you are done, click on
"Apply" at the bottom, and quit the control center.</para>
<para> To make sure <application>kdm</application> understands
@ -1296,12 +1296,12 @@ esac</screen>
its "RENDER" extension, and starting with version 2.3, Qt (the
toolkit used by <application>KDE</application>) supports this
extension. Configuring this is described in <xref
linkend="antialias"> on antialiasing X11 fonts. So if you're
linkend="antialias"> on antialiasing X11 fonts. So if you are
running up-to-date software, anti-aliasing is possible on your
<application>KDE2</application> desktop. Just go to your KDE2
menu, go to Preferences -> Look and Feel -> Style, and click
on the checkbox "Use Anti-Aliasing for Fonts and Icons".
That's all. If you're running a Qt application which is not
That's all. If you are running a Qt application which is not
part of <application>KDE</application>, you may need to set
the environment variable QT_XFT to true before starting your
program.</para>
@ -1367,7 +1367,7 @@ esac</screen>
<para>The next time you start X, <application>XFCE</application> will be your
desktop. (Note, as before:
if you're logging in via a display manager like
if you are logging in via a display manager like
<filename>xdm</filename>, you should either create an
<filename>.xsession</filename>, as described in the
section on <link linkend="x11-wm-gnome">GNOME</link>, but