Fix some spelling errors and some other minor nits.

This commit is contained in:
Jim Mock 2000-12-15 21:52:35 +00:00
parent fdaefa031b
commit 6b86823ee6
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=8512
15 changed files with 66 additions and 66 deletions

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.343 2000/12/10 15:33:33 ben Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.344 2000/12/14 22:42:52 dmlb Exp $
-->
<chapter id="contrib">
@ -910,7 +910,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para>TRW Financial Systems, Inc. provided 130 PCs, three 68 GB
fileservers, twelve Ethernets, two routers and an ATM switch for
file servers, twelve Ethernets, two routers and an ATM switch for
debugging the diskless code.</para>
</listitem>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.31 2000/09/19 17:05:47 ben Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.32 2000/09/19 17:06:59 ben Exp $
-->
<chapter id="advanced-networking">
@ -1324,7 +1324,7 @@ ISDN BRI line</programlisting>
<title>What is it?</title>
<para>NIS, which stands for Network Information Services, was
developed by Sun Microsystems to centralize adminstration of Unix
developed by Sun Microsystems to centralize administration of Unix
(originally SunOS) systems. It has now essentially become an
industry standard; all major Unices (Solaris, HP-UX, AIX, Linux,
NetBSD, OpenBSD, FreeBSD, etc) support NIS.</para>
@ -1442,7 +1442,7 @@ ISDN BRI line</programlisting>
Similar to NT's backup domain
controllers, NIS slave servers maintain copies of the NIS
master's data files. NIS slave servers provide the redundancy,
which is needed in important enviroments. They also help
which is needed in important environments. They also help
to balance the load of the master server: NIS Clients always
attach to the NIS server, whose response they get first, and
this includes slave-server-replies.</para>
@ -1450,7 +1450,7 @@ ISDN BRI line</programlisting>
<listitem>
<para><emphasis>NIS clients</emphasis>. NIS clients, like most
NT workstations, authenticate against the NIS server (or the NT
domain controller in the NT Workstation case) to logon.</para>
domain controller in the NT Workstation case) to log on.</para>
</listitem>
</itemizedlist>
</sect3>
@ -1474,7 +1474,7 @@ ISDN BRI line</programlisting>
<para>Let's assume that you are the administrator of a small
university lab. This lab, which consists of 15 FreeBSD machines,
currently has no centralised point of administration; each machine
currently has no centralized point of administration; each machine
has its own <filename>/etc/passwd</filename> and
<filename>/etc/master.passwd</filename>. These files are kept in
sync with each other only through manual intervention;
@ -1643,7 +1643,7 @@ ISDN BRI line</programlisting>
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 propogate
This is for a good reason; you don't 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>
@ -1656,7 +1656,7 @@ ISDN BRI line</programlisting>
<para>You should remove all entries regarding system accounts
(bin, tty, kmem, games, etc), as well as any accounts that you
don't want to be propogated to the NIS clients (for example
don't want to be propagated to the NIS clients (for example
root and any other UID 0 (superuser) accounts).</para>
<note><para>Make sure the
@ -1724,7 +1724,7 @@ ellington&prompt.root; <userinput>vi /var/yp/Makefile</userinput>
<title>Setting up a NIS slave server</title>
<para>Setting up an NIS slave server is even more simple than
setting up the master. Logon to the slave server and edit the
setting up the master. Log on to the slave server and edit the
file <filename>/etc/rc.conf</filename> as you did before.
The only difference is that we now must use the
<option>-s</option> option when running <command>ypinit</command>.
@ -2036,7 +2036,7 @@ basie&prompt.root;</screen>
<emphasis>will</emphasis> forget to bar some users from logging
onto sensitive machines, or you may even have to modify each
machine separately, thus loosing the main benefit of NIS,
<emphasis>centralised</emphasis> administration.</para>
<emphasis>centralized</emphasis> administration.</para>
<para>The NIS developers' solution for this problem is called
<emphasis>netgroups</emphasis>. Their purpose and semantics
@ -2106,7 +2106,7 @@ basie&prompt.root;</screen>
<row>
<!-- Names taken from "Good Omens" by Neil Gaiman and Terry
Pratchett. Many thanks for a brilliant book. -->
<entry>war, death, famine, polution</entry>
<entry>war, death, famine, pollution</entry>
<entry>Your most important servers. Only the IT
employees are allowed to log onto these
machines.</entry>
@ -2127,7 +2127,7 @@ basie&prompt.root;</screen>
<row>
<entry>trashcan</entry>
<entry>A very old machine without any critcal data.
<entry>A very old machine without any critical data.
Even the intern is allowed to use this box.</entry>
</row>
</tbody>
@ -2156,7 +2156,7 @@ basie&prompt.root;</screen>
carefully, you will only have to modify exactly one central
configuration file to grant or deny access to machines.</para>
<para>The first step is the initialisation of the NIS map
<para>The first step is the initialization of the NIS map
netgroup. FreeBSD's ypinit does not create this map by
default, but its NIS implementation will support it once it has
been created. To create an empty map, simply type</para>
@ -2203,7 +2203,7 @@ INTERNS (,able,test-domain) (,baker,test-domain)
</listitem>
</orderedlist>
<para>Each of this fields can contain wildcards, see
<para>Each of these fields can contain wildcards. See
&man.netgroup.5; for details.</para>
<note>
@ -2336,7 +2336,7 @@ ellington&prompt.user; <userinput>ypcat -k netgroup.byuser</userinput>
add a new netgroup IT_INTERN, add the new IT interns to this
netgroup and start to change the config on each and every
machine... As the old saying goes: <quote>Errors in
centralised planning lead to global mess</quote>.</para>
centralized planning lead to global mess</quote>.</para>
<para>NIS' ability to create netgroups from other netgroups can
be used to prevent situations like these. One possibility
@ -2403,7 +2403,7 @@ SMALLSRV IT_EMP IT_APP ITINTERN
USERBOX IT_EMP ITINTERN USERS
#
# And a groups for a special tasks
# Allow echo und golf to access our anti-virus-machine
# Allow echo and golf to access our anti-virus-machine
SECURITY IT_EMP (,echo,test-domain) (,golf,test-domain)
#
# machine-based netgroups
@ -2411,7 +2411,7 @@ SECURITY IT_EMP (,echo,test-domain) (,golf,test-domain)
WAR BIGSRV
FAMINE BIGSRV
# User india needs access to this server
POLUTION BIGSRV (,india,test-domain)
POLLUTION BIGSRV (,india,test-domain)
#
# This one is really important and needs more access restrictions
DEATH IT_EMP
@ -2463,7 +2463,7 @@ TWO (,hotel,test-domain)
</listitem>
<listitem>
<para><emphasis>Keep the administration accounts out of the NIS
maps</emphasis>. You don't want to be propogating administrative
maps</emphasis>. You don't want to be propagating administrative
accounts and passwords to machines that will have users that
shouldn't have access to those accounts.</para>
</listitem>
@ -2474,7 +2474,7 @@ TWO (,hotel,test-domain)
these machines, they have effectively rendered many people without
the ability to login to the lab.</para>
<para>This is the chief weakness of any centralised administration
<para>This is the chief weakness of any centralized administration
system, and it is probably the most important weakness. If you do
not protect your NIS servers, you will have a lot of angry
users!</para>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.25 2000/06/14 23:20:38 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.26 2000/09/18 17:05:13 marko Exp $
-->
<chapter id="backups">
@ -238,7 +238,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
Therefore, the user performing the backup must have
<literal>rhosts</literal> access to the remote computer. The
arguments to &man.rdump.8; and &man.rrestore.8; must suitable to use
on the remote computer. (e.g. When <command>rdump</command>'ing from
on the remote computer. (e.g. When <command>rdump</command>ing from
a FreeBSD computer to an Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000 13000
126 komodo:/dev/nrsa8 /dev/rda0a 2>&amp;1</command>) Beware: there

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.21 2000/08/08 23:23:06 marko Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.22 2000/08/20 17:18:41 chris Exp $
-->
<chapter id="basics">
@ -11,7 +11,7 @@
<title>Synopsis</title>
<para><emphasis>Rewritten by Chris Shumway
<email>cshumway@cdrom.com</email>, 10 Mar 2000.</emphasis></para>
<email>cshumway@osd.bsdi.com</email>, 10 Mar 2000.</emphasis></para>
<para>The following chapter will cover the basic commands and
functionality of the FreeBSD operating system. If you are new to

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v 1.8 2000/06/15 23:13:33 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v 1.9 2000/11/26 05:16:52 dannyboy Exp $
-->
<chapter id="boot">
@ -162,7 +162,7 @@ boot:</screen>
selected.</para>
<para>Finally, by default, the loader issues a 10 second wait
for keypresses, and boots the kernel if it is not interrupted.
for key presses, and boots the kernel if it is not interrupted.
If interrupted, the user is presented with a prompt which
understands the easy-to-use command set, where the user may
adjust variables, unload all modules, load modules, and then

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.343 2000/12/10 15:33:33 ben Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.344 2000/12/14 22:42:52 dmlb Exp $
-->
<chapter id="contrib">
@ -910,7 +910,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para>TRW Financial Systems, Inc. provided 130 PCs, three 68 GB
fileservers, twelve Ethernets, two routers and an ATM switch for
file servers, twelve Ethernets, two routers and an ATM switch for
debugging the diskless code.</para>
</listitem>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.23 2000/07/19 02:07:46 hanai Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.24 2000/12/05 12:54:46 jim Exp $
-->
<chapter id="disks">
@ -528,7 +528,7 @@
&prompt.root; <userinput>mount -t ufs /dev/da1s1e /1</userinput> # Mount the partition(s)
&prompt.root; <userinput>vi /etc/fstab</userinput> # When satisfied, add the appropriate entry/entries to your <filename>/etc/fstab</filename>.</screen>
<para>If you have an IDE disk, subsitute <filename>ad</filename>
<para>If you have an IDE disk, substitute <filename>ad</filename>
for <filename>da</filename>. On pre-4.x systems use
<filename>wd</filename>.</para>
</sect3>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.62 2000/11/29 14:15:41 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.63 2000/11/29 14:41:04 jim Exp $
-->
<chapter id="install">
@ -117,7 +117,7 @@
<title>Prepare the floppy disks</title>
<para>You must prepare one floppy disk per image file you had to
download. It is imperitive that these disks are free from
download. It is imperative that these disks are free from
defects. The easiest way to test this is to format the disks
for yourself. Do not trust pre-formatted floppies.</para>
@ -590,7 +590,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<title>Check your BIOS drive numbering</title>
<para>If you have used features in your BIOS to renumber your disk
drives without recabling them then you should read <xref
drives without re-cabling them then you should read <xref
linkend="disks-bios-numbering"> first to avoid confusion.</para>
</sect3>
</sect2>
@ -838,7 +838,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<listitem>
<para><devicename>matcd</devicename> - Matsushita/Panasonic
(Creative Soundblaster) proprietary interface (562/563
(Creative SoundBlaster) proprietary interface (562/563
models)</para>
</listitem>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.31 2000/09/19 17:05:47 ben Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.32 2000/09/19 17:06:59 ben Exp $
-->
<chapter id="advanced-networking">
@ -1324,7 +1324,7 @@ ISDN BRI line</programlisting>
<title>What is it?</title>
<para>NIS, which stands for Network Information Services, was
developed by Sun Microsystems to centralize adminstration of Unix
developed by Sun Microsystems to centralize administration of Unix
(originally SunOS) systems. It has now essentially become an
industry standard; all major Unices (Solaris, HP-UX, AIX, Linux,
NetBSD, OpenBSD, FreeBSD, etc) support NIS.</para>
@ -1442,7 +1442,7 @@ ISDN BRI line</programlisting>
Similar to NT's backup domain
controllers, NIS slave servers maintain copies of the NIS
master's data files. NIS slave servers provide the redundancy,
which is needed in important enviroments. They also help
which is needed in important environments. They also help
to balance the load of the master server: NIS Clients always
attach to the NIS server, whose response they get first, and
this includes slave-server-replies.</para>
@ -1450,7 +1450,7 @@ ISDN BRI line</programlisting>
<listitem>
<para><emphasis>NIS clients</emphasis>. NIS clients, like most
NT workstations, authenticate against the NIS server (or the NT
domain controller in the NT Workstation case) to logon.</para>
domain controller in the NT Workstation case) to log on.</para>
</listitem>
</itemizedlist>
</sect3>
@ -1474,7 +1474,7 @@ ISDN BRI line</programlisting>
<para>Let's assume that you are the administrator of a small
university lab. This lab, which consists of 15 FreeBSD machines,
currently has no centralised point of administration; each machine
currently has no centralized point of administration; each machine
has its own <filename>/etc/passwd</filename> and
<filename>/etc/master.passwd</filename>. These files are kept in
sync with each other only through manual intervention;
@ -1643,7 +1643,7 @@ ISDN BRI line</programlisting>
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 propogate
This is for a good reason; you don't 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>
@ -1656,7 +1656,7 @@ ISDN BRI line</programlisting>
<para>You should remove all entries regarding system accounts
(bin, tty, kmem, games, etc), as well as any accounts that you
don't want to be propogated to the NIS clients (for example
don't want to be propagated to the NIS clients (for example
root and any other UID 0 (superuser) accounts).</para>
<note><para>Make sure the
@ -1724,7 +1724,7 @@ ellington&prompt.root; <userinput>vi /var/yp/Makefile</userinput>
<title>Setting up a NIS slave server</title>
<para>Setting up an NIS slave server is even more simple than
setting up the master. Logon to the slave server and edit the
setting up the master. Log on to the slave server and edit the
file <filename>/etc/rc.conf</filename> as you did before.
The only difference is that we now must use the
<option>-s</option> option when running <command>ypinit</command>.
@ -2036,7 +2036,7 @@ basie&prompt.root;</screen>
<emphasis>will</emphasis> forget to bar some users from logging
onto sensitive machines, or you may even have to modify each
machine separately, thus loosing the main benefit of NIS,
<emphasis>centralised</emphasis> administration.</para>
<emphasis>centralized</emphasis> administration.</para>
<para>The NIS developers' solution for this problem is called
<emphasis>netgroups</emphasis>. Their purpose and semantics
@ -2106,7 +2106,7 @@ basie&prompt.root;</screen>
<row>
<!-- Names taken from "Good Omens" by Neil Gaiman and Terry
Pratchett. Many thanks for a brilliant book. -->
<entry>war, death, famine, polution</entry>
<entry>war, death, famine, pollution</entry>
<entry>Your most important servers. Only the IT
employees are allowed to log onto these
machines.</entry>
@ -2127,7 +2127,7 @@ basie&prompt.root;</screen>
<row>
<entry>trashcan</entry>
<entry>A very old machine without any critcal data.
<entry>A very old machine without any critical data.
Even the intern is allowed to use this box.</entry>
</row>
</tbody>
@ -2156,7 +2156,7 @@ basie&prompt.root;</screen>
carefully, you will only have to modify exactly one central
configuration file to grant or deny access to machines.</para>
<para>The first step is the initialisation of the NIS map
<para>The first step is the initialization of the NIS map
netgroup. FreeBSD's ypinit does not create this map by
default, but its NIS implementation will support it once it has
been created. To create an empty map, simply type</para>
@ -2203,7 +2203,7 @@ INTERNS (,able,test-domain) (,baker,test-domain)
</listitem>
</orderedlist>
<para>Each of this fields can contain wildcards, see
<para>Each of these fields can contain wildcards. See
&man.netgroup.5; for details.</para>
<note>
@ -2336,7 +2336,7 @@ ellington&prompt.user; <userinput>ypcat -k netgroup.byuser</userinput>
add a new netgroup IT_INTERN, add the new IT interns to this
netgroup and start to change the config on each and every
machine... As the old saying goes: <quote>Errors in
centralised planning lead to global mess</quote>.</para>
centralized planning lead to global mess</quote>.</para>
<para>NIS' ability to create netgroups from other netgroups can
be used to prevent situations like these. One possibility
@ -2403,7 +2403,7 @@ SMALLSRV IT_EMP IT_APP ITINTERN
USERBOX IT_EMP ITINTERN USERS
#
# And a groups for a special tasks
# Allow echo und golf to access our anti-virus-machine
# Allow echo and golf to access our anti-virus-machine
SECURITY IT_EMP (,echo,test-domain) (,golf,test-domain)
#
# machine-based netgroups
@ -2411,7 +2411,7 @@ SECURITY IT_EMP (,echo,test-domain) (,golf,test-domain)
WAR BIGSRV
FAMINE BIGSRV
# User india needs access to this server
POLUTION BIGSRV (,india,test-domain)
POLLUTION BIGSRV (,india,test-domain)
#
# This one is really important and needs more access restrictions
DEATH IT_EMP
@ -2463,7 +2463,7 @@ TWO (,hotel,test-domain)
</listitem>
<listitem>
<para><emphasis>Keep the administration accounts out of the NIS
maps</emphasis>. You don't want to be propogating administrative
maps</emphasis>. You don't want to be propagating administrative
accounts and passwords to machines that will have users that
shouldn't have access to those accounts.</para>
</listitem>
@ -2474,7 +2474,7 @@ TWO (,hotel,test-domain)
these machines, they have effectively rendered many people without
the ability to login to the lab.</para>
<para>This is the chief weakness of any centralised administration
<para>This is the chief weakness of any centralized administration
system, and it is probably the most important weakness. If you do
not protect your NIS servers, you will have a lot of angry
users!</para>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.25 2000/06/14 23:20:38 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.26 2000/09/18 17:05:13 marko Exp $
-->
<chapter id="backups">
@ -238,7 +238,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
Therefore, the user performing the backup must have
<literal>rhosts</literal> access to the remote computer. The
arguments to &man.rdump.8; and &man.rrestore.8; must suitable to use
on the remote computer. (e.g. When <command>rdump</command>'ing from
on the remote computer. (e.g. When <command>rdump</command>ing from
a FreeBSD computer to an Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000 13000
126 komodo:/dev/nrsa8 /dev/rda0a 2>&amp;1</command>) Beware: there

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.21 2000/08/08 23:23:06 marko Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.22 2000/08/20 17:18:41 chris Exp $
-->
<chapter id="basics">
@ -11,7 +11,7 @@
<title>Synopsis</title>
<para><emphasis>Rewritten by Chris Shumway
<email>cshumway@cdrom.com</email>, 10 Mar 2000.</emphasis></para>
<email>cshumway@osd.bsdi.com</email>, 10 Mar 2000.</emphasis></para>
<para>The following chapter will cover the basic commands and
functionality of the FreeBSD operating system. If you are new to

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v 1.8 2000/06/15 23:13:33 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v 1.9 2000/11/26 05:16:52 dannyboy Exp $
-->
<chapter id="boot">
@ -162,7 +162,7 @@ boot:</screen>
selected.</para>
<para>Finally, by default, the loader issues a 10 second wait
for keypresses, and boots the kernel if it is not interrupted.
for key presses, and boots the kernel if it is not interrupted.
If interrupted, the user is presented with a prompt which
understands the easy-to-use command set, where the user may
adjust variables, unload all modules, load modules, and then

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.343 2000/12/10 15:33:33 ben Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.344 2000/12/14 22:42:52 dmlb Exp $
-->
<chapter id="contrib">
@ -910,7 +910,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para>TRW Financial Systems, Inc. provided 130 PCs, three 68 GB
fileservers, twelve Ethernets, two routers and an ATM switch for
file servers, twelve Ethernets, two routers and an ATM switch for
debugging the diskless code.</para>
</listitem>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.23 2000/07/19 02:07:46 hanai Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.24 2000/12/05 12:54:46 jim Exp $
-->
<chapter id="disks">
@ -528,7 +528,7 @@
&prompt.root; <userinput>mount -t ufs /dev/da1s1e /1</userinput> # Mount the partition(s)
&prompt.root; <userinput>vi /etc/fstab</userinput> # When satisfied, add the appropriate entry/entries to your <filename>/etc/fstab</filename>.</screen>
<para>If you have an IDE disk, subsitute <filename>ad</filename>
<para>If you have an IDE disk, substitute <filename>ad</filename>
for <filename>da</filename>. On pre-4.x systems use
<filename>wd</filename>.</para>
</sect3>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.62 2000/11/29 14:15:41 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.63 2000/11/29 14:41:04 jim Exp $
-->
<chapter id="install">
@ -117,7 +117,7 @@
<title>Prepare the floppy disks</title>
<para>You must prepare one floppy disk per image file you had to
download. It is imperitive that these disks are free from
download. It is imperative that these disks are free from
defects. The easiest way to test this is to format the disks
for yourself. Do not trust pre-formatted floppies.</para>
@ -590,7 +590,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<title>Check your BIOS drive numbering</title>
<para>If you have used features in your BIOS to renumber your disk
drives without recabling them then you should read <xref
drives without re-cabling them then you should read <xref
linkend="disks-bios-numbering"> first to avoid confusion.</para>
</sect3>
</sect2>
@ -838,7 +838,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<listitem>
<para><devicename>matcd</devicename> - Matsushita/Panasonic
(Creative Soundblaster) proprietary interface (562/563
(Creative SoundBlaster) proprietary interface (562/563
models)</para>
</listitem>