From aca13e8771c6dc314353710ea104e4fe1e758257 Mon Sep 17 00:00:00 2001 From: Jim Mock Date: Tue, 13 Jun 2000 18:05:39 +0000 Subject: [PATCH] Attack of the spelling police. The grammar police were also occasionally called onto the scene. --- .../articles/contributing/article.sgml | 20 +-- .../handbook/advanced-networking/chapter.sgml | 124 +++++++++--------- .../books/handbook/backups/chapter.sgml | 12 +- .../books/handbook/contrib/chapter.sgml | 20 +-- .../books/handbook/cutting-edge/chapter.sgml | 30 ++--- .../books/handbook/disks/chapter.sgml | 10 +- .../books/handbook/eresources/chapter.sgml | 12 +- .../books/handbook/hw/chapter.sgml | 124 +++++++++--------- .../handbook/advanced-networking/chapter.sgml | 124 +++++++++--------- .../books/handbook/backups/chapter.sgml | 12 +- .../books/handbook/contrib/chapter.sgml | 20 +-- .../books/handbook/cutting-edge/chapter.sgml | 30 ++--- .../books/handbook/disks/chapter.sgml | 10 +- .../books/handbook/eresources/chapter.sgml | 12 +- .../books/handbook/hw/chapter.sgml | 124 +++++++++--------- 15 files changed, 340 insertions(+), 344 deletions(-) diff --git a/en_US.ISO8859-1/articles/contributing/article.sgml b/en_US.ISO8859-1/articles/contributing/article.sgml index da26d06487..41322bc613 100644 --- a/en_US.ISO8859-1/articles/contributing/article.sgml +++ b/en_US.ISO8859-1/articles/contributing/article.sgml @@ -1,7 +1,7 @@ @@ -284,7 +284,7 @@ NetWare Server (protected mode ODI driver) loader and - subservices to allow the use of ODI card drivers supplied with + sub-services to allow the use of ODI card drivers supplied with network cards. The same thing for NDIS drivers and NetWare SCSI drivers. @@ -303,7 +303,7 @@ A concerted effort at support for portable computers. This is somewhat handled by changing PCMCIA bridging rules and power management event handling. But there are things like detecting - internal vs. external display and picking a different screen + internal v.s.. external display and picking a different screen resolution based on that fact, not spinning down the disk if the machine is in dock, and allowing dock-based cards to disappear without affecting the machines ability to boot (same issue for @@ -363,7 +363,7 @@ - If you know of any bugfixes which have been successfully + If you know of any bug fixes which have been successfully applied to -current but have not been merged into -stable after a decent interval (normally a couple of weeks), send the committer a polite reminder. @@ -546,7 +546,7 @@ In the rare case of a significant contribution of a large body work, or the addition of an important new feature to FreeBSD, it - becomes almost always necessary to either send changes as uuencode'd + becomes almost always necessary to either send changes as uuencoded tar files or upload them to our ftp site ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/. @@ -731,7 +731,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donors Gallery The FreeBSD Project is indebted to the following donors and would - like to publically thank them here! + like to publicly thank them here! @@ -846,7 +846,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Laser5 of Japan (a portion of the profits from sales of their various FreeBSD - CD-ROMs). + CDROMs). @@ -983,10 +983,10 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The interface business GmbH, Dresden has been patiently supporting - &a.joerg; who has often preferred FreeBSD work over paywork, and + &a.joerg; who has often preferred FreeBSD work over paid work, and used to fall back to their (quite expensive) EUnet Internet connection whenever his private connection became too slow or - flakey to work with it... + flaky to work with it... @@ -1126,7 +1126,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - Adrian Chadd adrian@freebsd.org + Adrian Chadd adrian@FreeBSD.org diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml index 2268cea7d6..0070cb3e44 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -1,7 +1,7 @@ @@ -399,7 +399,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) Luckily for us, on a FreeBSD system this setup is a snap. The processes that need to be running can all be run at boot time with - a few modificationss to your /etc/rc.conf + a few modifications to your /etc/rc.conf file. On the NFS server make sure you have: @@ -758,7 +758,7 @@ diskless:\ swapsize - set diskless swapsize in Kbytes + set diskless swapsize in KBytes @@ -827,7 +827,7 @@ hostname myclient.mydomain as in the example above, the swapfile for myclient will be called /swapfs/swap.X.X.X.X where X.X.X.X is the client's IP addr, - eg: + e.g.: &prompt.root; dd if=/dev/zero of=/swapfs/swap.192.1.2.4 bs=1k count=20000 @@ -900,7 +900,7 @@ hostname myclient.mydomain Dan Kegel's ISDN Page. - A quick simple roadmap to ISDN follows: + A quick simple road map to ISDN follows: @@ -910,14 +910,14 @@ hostname myclient.mydomain If you are planning to use ISDN primarily to connect to the - Internet with an Internet Provider on a dialup non-dedicated basis, + Internet with an Internet Provider on a dial-up non-dedicated basis, I suggest you look into Terminal Adapters. This will give you the most flexibility, with the fewest problems, if you change providers. - If you are connecting two lans together, or connecting to the + If you are connecting two LANs together, or connecting to the Internet with a dedicated ISDN connection, I suggest you consider the stand alone router/bridge option. @@ -991,7 +991,7 @@ subscribe freebsd-isdn The main advantage of using a TA to connect to an Internet Provider is that you can do Dynamic PPP. As IP address space becomes more and more scarce, most providers are not willing to provide you - with a static IP anymore. Most standalone routers are not able to + with a static IP anymore. Most stand-alone routers are not able to accommodate dynamic IP allocation. TA's completely rely on the PPP daemon that you are running for @@ -1039,11 +1039,11 @@ subscribe freebsd-isdn save you having to buy another serial cable, and find another empty electrical socket. - A synchronous card with a TA is at least as fast as a standalone + A synchronous card with a TA is at least as fast as a stand-alone router, and with a simple 386 FreeBSD box driving it, probably more flexible. - The choice of sync/TA vs standalone router is largely a religious + The choice of sync/TA v.s. stand-alone router is largely a religious issue. There has been some discussion of this in the mailing lists. I suggest you search the archives for the @@ -1051,7 +1051,7 @@ subscribe freebsd-isdn - Standalone ISDN Bridges/Routers + Stand-alone ISDN Bridges/Routers ISDN bridges or routers are not at all specific to FreeBSD or any other operating system. For a more complete description of routing @@ -1097,12 +1097,12 @@ subscribe freebsd-isdn | ---Windows 95 (Do not admit to owning it) | -Standalone router +Stand-alone router | ISDN BRI line If your home/branch office is only one computer you can use a - twisted pair crossover cable to connect to the standalone router + twisted pair crossover cable to connect to the stand-alone router directly. @@ -1121,7 +1121,7 @@ ISDN BRI line | | | ---Windows 95 | B | - |___---Standalone router + |___---Stand-alone router | ISDN BRI line @@ -1134,12 +1134,12 @@ ISDN BRI line etc. This can be very useful feature, for example if you have an - dedicated internet ISDN connection at your office and would like to + 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 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 - dialin, dialout or dynamically bond(MPP etc.) with the first B channel + dial-in, dial-out or dynamically bond(MPP etc.) with the first B channel for more bandwidth. An Ethernet bridge will also allow you to transmit more than just @@ -1167,10 +1167,10 @@ ISDN BRI line How does it work? - There are 3 types of hosts in an NIS enviornment; master + There are 3 types of hosts in an NIS environment; master servers, slave servers, and clients. Servers act as a central repository for host configuration information. Master servers - hold the authoritatve copy of this information, while slave + hold the authoritative copy of this information, while slave servers mirror this information for redundancy. Clients rely on the servers to provide this information to them. @@ -1217,7 +1217,7 @@ ISDN BRI line Physical Server Requirements - There are several things to keep in mind when chosing a + There are several things to keep in mind when choosing a machine to use as a NIS server. One of the unfortunate things about NIS is the level of dependency the clients have on the server. If a client cannot contact the server for its NIS @@ -1259,7 +1259,7 @@ ISDN BRI line Setting up a NIS master server - Setting up a master NIS server can be relativly straight + Setting up a master NIS server can be relatively straight forward, depending on your needs. FreeBSD comes with a handy script called ypinit that makes the initial setup procedure very easy. A few steps are needed ahead of @@ -1392,46 +1392,46 @@ Ok, please remember to go back and redo manually whatever fails. If you don't, something might not work. There will be no further questions. The remainder of the procedure should take a few minutes, to copy the databases from master.example.com. -Transfering netgroup... -ypxfr: Exiting: Map successfully transfered -Transfering netgroup.byuser... -ypxfr: Exiting: Map successfully transfered -Transfering netgroup.byhost... -ypxfr: Exiting: Map successfully transfered -Transfering master.passwd.byuid... -ypxfr: Exiting: Map successfully transfered -Transfering passwd.byuid... -ypxfr: Exiting: Map successfully transfered -Transfering passwd.byname... -ypxfr: Exiting: Map successfully transfered -Transfering group.bygid... -ypxfr: Exiting: Map successfully transfered -Transfering group.byname... -ypxfr: Exiting: Map successfully transfered -Transfering services.byname... -ypxfr: Exiting: Map successfully transfered -Transfering rpc.bynumber... -ypxfr: Exiting: Map successfully transfered -Transfering rpc.byname... -ypxfr: Exiting: Map successfully transfered -Transfering protocols.byname... -ypxfr: Exiting: Map successfully transfered -Transfering master.passwd.byname... -ypxfr: Exiting: Map successfully transfered -Transfering networks.byname... -ypxfr: Exiting: Map successfully transfered -Transfering networks.byaddr... -ypxfr: Exiting: Map successfully transfered -Transfering netid.byname... -ypxfr: Exiting: Map successfully transfered -Transfering hosts.byaddr... -ypxfr: Exiting: Map successfully transfered -Transfering protocols.bynumber... -ypxfr: Exiting: Map successfully transfered -Transfering ypservers... -ypxfr: Exiting: Map successfully transfered -Transfering hosts.byname... -ypxfr: Exiting: Map successfully transfered +Transferring netgroup... +ypxfr: Exiting: Map successfully transferred +Transferring netgroup.byuser... +ypxfr: Exiting: Map successfully transferred +Transferring netgroup.byhost... +ypxfr: Exiting: Map successfully transferred +Transferring master.passwd.byuid... +ypxfr: Exiting: Map successfully transferred +Transferring passwd.byuid... +ypxfr: Exiting: Map successfully transferred +Transferring passwd.byname... +ypxfr: Exiting: Map successfully transferred +Transferring group.bygid... +ypxfr: Exiting: Map successfully transferred +Transferring group.byname... +ypxfr: Exiting: Map successfully transferred +Transferring services.byname... +ypxfr: Exiting: Map successfully transferred +Transferring rpc.bynumber... +ypxfr: Exiting: Map successfully transferred +Transferring rpc.byname... +ypxfr: Exiting: Map successfully transferred +Transferring protocols.byname... +ypxfr: Exiting: Map successfully transferred +Transferring master.passwd.byname... +ypxfr: Exiting: Map successfully transferred +Transferring networks.byname... +ypxfr: Exiting: Map successfully transferred +Transferring networks.byaddr... +ypxfr: Exiting: Map successfully transferred +Transferring netid.byname... +ypxfr: Exiting: Map successfully transferred +Transferring hosts.byaddr... +ypxfr: Exiting: Map successfully transferred +Transferring protocols.bynumber... +ypxfr: Exiting: Map successfully transferred +Transferring ypservers... +ypxfr: Exiting: Map successfully transferred +Transferring hosts.byname... +ypxfr: Exiting: Map successfully transferred slave.example.com has been setup as an YP slave server without any errors. Don't forget to update map ypservers on master.example.com. @@ -1622,7 +1622,7 @@ Don't forget to update map ypservers on master.example.com. - libscrypt vs. libdescrypt + libscrypt v.s. libdescrypt One of the most common issues that people run into when trying to implement NIS is crypt library compatibility. If your NIS @@ -1644,7 +1644,7 @@ lrwxr-xr-x 1 root wheel 16 Nov 8 14:27 /usr/lib/libdescrypt.so@ -> libdes -r--r--r-- 1 root wheel 14750 Nov 8 14:27 /usr/lib/libdescrypt_p.a If the machine is configured to use the standard FreeBSD MD5 - crypt libraries they will look somethine like this: + crypt libraries they will look something like this: &prompt.user; ls -l /usr/lib/*crypt* diff --git a/en_US.ISO8859-1/books/handbook/backups/chapter.sgml b/en_US.ISO8859-1/books/handbook/backups/chapter.sgml index b6c5c3c292..12de057851 100644 --- a/en_US.ISO8859-1/books/handbook/backups/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/backups/chapter.sgml @@ -1,7 +1,7 @@ @@ -33,7 +33,7 @@ x 12 mm) than 8mm cartridges. 4mm, like 8mm, has comparatively short head life for the same reason, both use helical scan. - Data thruput on these drives starts ~150kB/s, peaking at ~500kB/s. + Data throughput on these drives starts ~150kB/s, peaking at ~500kB/s. Data capacity starts at 1.3 GB and ends at 2.0 GB. Hardware compression, available with most of these drives, approximately doubles the capacity. Multi-drive tape library units can have 6 @@ -60,7 +60,7 @@ One downside of 8mm tape is relatively short head and tape life due to the high rate of relative motion of the tape across the heads. - Data thruput ranges from ~250kB/s to ~500kB/s. Data sizes start + Data throughput ranges from ~250kB/s to ~500kB/s. Data sizes start at 300 MB and go up to 7 GB. Hardware compression, available with most of these drives, approximately doubles the capacity. These drives are available as single units or multi-drive tape libraries @@ -99,7 +99,7 @@ also use 1/4" wide tape are discussed separately. Tape libraries and changers are not available. - Data thruput ranges from ~150kB/s to ~500kB/s. Data capacity + Data throughput ranges from ~150kB/s to ~500kB/s. Data capacity ranges from 40 MB to 15 GB. Hardware compression is available on many of the newer QIC drives. QIC drives are less frequently installed; they are being supplanted by DAT drives. @@ -139,7 +139,7 @@ both the supply and take-up spools located inside the tape cartridge itself. - Data thruput is approximately 1.5MB/s, three times the thruput of + Data throughput is approximately 1.5MB/s, three times the throughput of 4mm, 8mm, or QIC tape drives. Data capacities range from 10GB to 20GB for a single drive. Drives are available in both multi-tape changers and multi-tape, multi-drive tape libraries containing from 5 to 900 @@ -381,7 +381,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready two copies of each. - Second, determine that the boot and fixit floppies + Second, determine that the boot and fix-it floppies (boot.flp and fixit.flp) have all your devices. The easiest way to check is to reboot your machine with the boot floppy in the floppy drive and check the boot diff --git a/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml b/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml index da26d06487..41322bc613 100644 --- a/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml @@ -1,7 +1,7 @@ @@ -284,7 +284,7 @@ NetWare Server (protected mode ODI driver) loader and - subservices to allow the use of ODI card drivers supplied with + sub-services to allow the use of ODI card drivers supplied with network cards. The same thing for NDIS drivers and NetWare SCSI drivers. @@ -303,7 +303,7 @@ A concerted effort at support for portable computers. This is somewhat handled by changing PCMCIA bridging rules and power management event handling. But there are things like detecting - internal vs. external display and picking a different screen + internal v.s.. external display and picking a different screen resolution based on that fact, not spinning down the disk if the machine is in dock, and allowing dock-based cards to disappear without affecting the machines ability to boot (same issue for @@ -363,7 +363,7 @@ - If you know of any bugfixes which have been successfully + If you know of any bug fixes which have been successfully applied to -current but have not been merged into -stable after a decent interval (normally a couple of weeks), send the committer a polite reminder. @@ -546,7 +546,7 @@ In the rare case of a significant contribution of a large body work, or the addition of an important new feature to FreeBSD, it - becomes almost always necessary to either send changes as uuencode'd + becomes almost always necessary to either send changes as uuencoded tar files or upload them to our ftp site ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/. @@ -731,7 +731,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donors Gallery The FreeBSD Project is indebted to the following donors and would - like to publically thank them here! + like to publicly thank them here! @@ -846,7 +846,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Laser5 of Japan (a portion of the profits from sales of their various FreeBSD - CD-ROMs). + CDROMs). @@ -983,10 +983,10 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The interface business GmbH, Dresden has been patiently supporting - &a.joerg; who has often preferred FreeBSD work over paywork, and + &a.joerg; who has often preferred FreeBSD work over paid work, and used to fall back to their (quite expensive) EUnet Internet connection whenever his private connection became too slow or - flakey to work with it... + flaky to work with it... @@ -1126,7 +1126,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - Adrian Chadd adrian@freebsd.org + Adrian Chadd adrian@FreeBSD.org diff --git a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml index 35bf891f54..6d56021fa1 100644 --- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml @@ -1,7 +1,7 @@ @@ -24,7 +24,7 @@ - -CURRENT vs. -STABLE + -CURRENT v.s.. -STABLE There are two development branches to FreeBSD; -CURRENT and -STABLE. This section will explain a bit about each and describe @@ -183,7 +183,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/. We also use wu-ftpd which allows - compressed/tar'd grabbing of whole trees. e.g. you + compressed/tarred grabbing of whole trees. e.g. you see: usr.bin/lex @@ -354,7 +354,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/ We also use wu-ftpd which allows - compressed/tar'd grabbing of whole trees. e.g. you + compressed/tarred grabbing of whole trees. e.g. you see: usr.bin/lex @@ -707,7 +707,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - Creating a list of changes (as unidiffs) to &man.ls.1; + Creating a list of changes (as unified diffs) to &man.ls.1; &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs @@ -764,7 +764,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Using <command>make world</command> - Once you have synchronised your local source tree against a + Once you have synchronized your local source tree against a particular version of FreeBSD (stable, current and so on) you must then use the source tree to rebuild the system. @@ -779,7 +779,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - Make sure you have taken a backup. And have a fixit floppy to + Make sure you have taken a backup. And have a fix-it floppy to hand. I have never needed to use them, and, touch wood, I never will, but it is always better to be safe than sorry. @@ -1006,7 +1006,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz&prompt.root; make -DNOPROFILE=true target - is another way of specifying that profiled libaries should + is another way of specifying that profiled libraries should not be built, and corresponds with the NOPROFILE= true @@ -1261,7 +1261,7 @@ Script done, … Name the new root directory - (<filename>/var/tmp/root</filename>)with a timestamp, so you can + (<filename>/var/tmp/root</filename>)with a time stamp, so you can easily compare differences between versions Frequently remaking the world means that you have to update @@ -1348,7 +1348,7 @@ Script done, … If you are using DEVFS then this is probably unnecessary. - For safety's sake, this is a multistep process. + For safety's sake, this is a multi-step process. @@ -1362,7 +1362,7 @@ Script done, … Now, take a snapshot of your current /dev. This snapshot needs to contain the permissions, ownerships, major and minor numbers of each filename, - but it should not contain the timestamps. The easiest way to do + but it should not contain the time stamps. The easiest way to do this is to use &man.awk.1; to strip out some of the information. @@ -1399,11 +1399,11 @@ Script done, … Update <filename>/stand</filename> - This step is included only for completeness, it can safely be + This step is included only for completeness. It can safely be omitted. - For completenesses sake you may want to update the files in + For the sake of completeness, you may want to update the files in /stand as well. These files consist of hard links to the /stand/sysinstall binary. This binary should be statically linked, so that it can work when no other @@ -1769,8 +1769,8 @@ Antonio Also in /etc/make.conf, set CFLAGS to something like -O - -pipe. The optimisation -O2 is much - slower, and the optimisation difference between + -pipe. The optimization -O2 is much + slower, and the optimization difference between -O and -O2 is normally negligible. -pipe lets the compiler use pipes rather than temporary files for communication, which diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.sgml b/en_US.ISO8859-1/books/handbook/disks/chapter.sgml index 24c97212b4..bca1791fdd 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.sgml @@ -1,7 +1,7 @@ @@ -54,7 +54,7 @@ An illustration from the files of Bill and Fred's Exceptional Adventures: - Bill breaks-down an older WIntel box to make another FreeBSD box + Bill breaks-down an older Wintel box to make another FreeBSD box for Fred. Bill installs a single SCSI drive as SCSI unit zero, and installs FreeBSD on it. @@ -75,7 +75,7 @@ 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 newer version of FreeBSD. Bill removes SCSI unit zero because it was - a bit flakey, and replaces it with another identical disk drive from + a bit flaky, and replaces it with another identical disk drive from the "archive." Bill then installs the new version of FreeBSD onto the new SCSI unit zero using Fred's magic internet FTP floppies. The installation goes well. @@ -104,7 +104,7 @@ We are delighted to mention that no data bytes were killed or harmed in any way by our discovery of this phenomenon. The older SCSI - unit zero was retrieved from the bonepile, and all of Fred's work was + unit zero was retrieved from the bone pile, and all of Fred's work was returned to him, (and now Bill knows that he can count as high as zero). @@ -116,7 +116,7 @@ Disk Naming - Physical drives come in two main flavours, + Physical drives come in two main flavors, IDE, or SCSI; but there are also drives backed by RAID controllers, flash memory, and so forth. Since these behave quite differently, they have their diff --git a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml index 4a90d4b5d9..739d6adc18 100644 --- a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml @@ -1,7 +1,7 @@ @@ -434,7 +434,7 @@ help subscriber overlap and except for the most esoteric mixes (say "-stable & -scsi"), there really is no reason to post to more than one list at a time. If a message is sent to you in such a - way that multiple mailing lists appear on the Cc line then the cc + way that multiple mailing lists appear on the Cc line then the Cc line should also be trimmed before sending it out again. You are still responsible for your own cross-postings, no matter who the originator might have @@ -1235,7 +1235,7 @@ help http://www.nz.FreeBSD.org/ — New Zeland. + url="http://www.nz.FreeBSD.org/">http://www.nz.FreeBSD.org/ — New Zealand. @@ -1423,15 +1423,15 @@ help storm.uk.FreeBSD.org - ssh only - Read-only cvs, personal webspace, email + SSH only + Read-only cvs, personal web space, email &a.brian dogma.freebsd-uk.eu.org Telnet/FTP/SSH - E-Mail, Webspace, Anonymous FTP + E-Mail, Web space, Anonymous FTP Lee Johnston lee@uk.FreeBSD.org diff --git a/en_US.ISO8859-1/books/handbook/hw/chapter.sgml b/en_US.ISO8859-1/books/handbook/hw/chapter.sgml index b2f9347a91..06c7ea9e2e 100644 --- a/en_US.ISO8859-1/books/handbook/hw/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/hw/chapter.sgml @@ -1,7 +1,7 @@ @@ -74,7 +74,7 @@ For Pentium Pro (P6) systems, I'm quite fond of the Tyan S1668 dual-processor motherboard as well as the Intel PR440FX motherboard - with on-board SCSI WIDE and 100/10MB Intel Etherexpress NIC. You + with on-board SCSI WIDE and 100/10MB Intel EtherExpress NIC. You can build a dandy little single or dual processor system (which is supported in FreeBSD 3.0) for very little cost now that the Pentium Pro 180/256K chips have fallen so greatly in price, but no telling @@ -153,7 +153,7 @@ My SCSI preferences extend to SCSI CDROM drives as well, and while the Toshiba drives - have always been favourites of mine (in whatever speed is hot that + have always been favorites of mine (in whatever speed is hot that week), I'm still fond of my good old Plextor PX-12CS drive. It's only a 12 speed, but it's offered excellent performance and @@ -263,13 +263,13 @@ then Digi International makes the SYNC/570 - series, with drivers now in FreeBSD-current. Emerging Technologies also manufactures a board with T1/E1 capabilities, using software they provide. I have no direct experience using either product, however. - Multiport card options are somewhat more numerous, though it has + multiport card options are somewhat more numerous, though it has to be said that FreeBSD's support for Cyclades's products is probably the tightest, primarily as a result of that company's @@ -291,7 +291,7 @@ Labs AWE32 though just about anything from Creative Labs will generally work these days. This is not to say that other types of sound cards don't also work, simply that I have little experience - with them (I was a former GUS fan, but Gravis's soundcard situation + with them (I was a former GUS fan, but Gravis's sound card situation has been dire for some time). @@ -379,10 +379,11 @@ Works fine, but many MB manufactures leave out the - external dirty bit SRAM needed for write back operation. Work - arounds are either run it in write through mode, or get the - dirty bit SRAM installed. (I have these for the ASUS - PCI/I-486SP3G rev 1.6 and later boards). + external dirty bit SRAM needed for write back operation. + You can work around this either by running it in write + through mode, or get the dirty bit SRAM installed (I + have these for the ASUS PCI/I-486SP3G rev 1.6 and later + boards). @@ -460,7 +461,7 @@ P6 class (Pentium Pro/Pentium II) Both the Pentium Pro and Pentium II work fine with FreeBSD. In - fact, our main ftp site ftp.FreeBSD.org (also known as "ftp.cdrom.com", world's largest ftp site) runs FreeBSD on a Pentium Pro. The Intel Pentium (P54C), Pentium MMX (P55C), AMD K6 and Cyrix/IBM 6x86MX processors are all reported to work with FreeBSD. I will not go into details of which processor is faster than what, - there are zillions of web sites on the Internet that tells you one + there are millions of web sites on the Internet that tells you one way or another. :) @@ -656,7 +657,7 @@ 286 class Sorry, FreeBSD does not run on 80286 machines. It is nearly - impossible to run today's large full-featured UNIXes on such + impossible to run today's large full-featured unices on such hardware. @@ -840,7 +841,7 @@ when the device connected to the UART is a modem, the modem may report the presence of a carrier on the phone line while the computer may be able to instruct the modem to reset itself or to - not take calls by asserting or deasserting one more more of these + not take calls by asserting or disasserting one more more of these extra signals. The function of each of these additional signals is defined in the EIA RS232-C standard. @@ -1622,7 +1623,7 @@ INS8250 -> INS8250B combinations of events occur that were not well tested or considered in the Windows driver. This is because most modem vendors and 16550-clone makers use the Microsoft drivers from - Windows for Workgroups 3.11 and the Microsoft MSD utility as the + Windows for Workgroups 3.11 and the Microsoft MS-DOS utility as the primary tests for compatibility with the NS16550A. This over-simplistic criteria means that if a different operating system is used, problems could appear due to subtle differences @@ -2549,7 +2550,7 @@ INS8250 -> INS8250B By default this part is similar to the NS16550A, but an extended 32-byte send and receive buffer can be optionally - enabled. Made by Startech. + enabled. Made by StarTech. @@ -2769,7 +2770,7 @@ sio16: type 16550A (multiport master) &prompt.root; ./MAKEDEV ttyg &prompt.root; ./MAKEDEV cuag - If you do not want or need callout devices for some + If you do not want or need call-out devices for some reason, you can dispense with making the cua* devices. @@ -2806,7 +2807,7 @@ sio16: type 16550A (multiport master) need to configure them as COM2 (aka sio1–I/O address 0x2F8 and IRQ 3), and the third port (aka sio2) as I/O - 0x3E8 and IRQ 5. Obviously this is a waste of IRQ ressources, as + 0x3E8 and IRQ 5. Obviously this is a waste of IRQ resources, as it should be basically possible to run both extension board ports using a single IRQ with the COM_MULTIPORT configuration described in the previous sections. @@ -2838,7 +2839,7 @@ IRQ 2 3 4 5 You need to decouple the IRQ drivers for the two UARTs, so that the IRQ line of the board only goes up if (and only if) one of the UARTs asserts a IRQ, and stays low otherwise. The solution - was proposed by Jrg Wunsch + was proposed by Joerg Wunsch j@ida.interface-business.de: To solder up a wired-or consisting of two diodes (Germanium or Schottky-types strongly preferred) and a 1 kOhm resistor. Here is the schematic, @@ -2873,7 +2874,7 @@ device sio2 at isa? port "IO_COM3" tty flags 0x205 irq 3Note that the flags setting for sio1 and sio2 is - truely essential; refer to + truly essential; refer to &man.sio.4; for details. (Generally, the 2 in the "flags" attribute refers to sio2 which holds the IRQ, and you surely want a 5 @@ -2895,7 +2896,7 @@ sio2: type 16550A (multiport master) the basic idea is that you observe 0x1 in the first, third, and fourth place. This means that the corresponding IRQ was set upon output and cleared after, which is just what we - would expect. If your kernel does not display this behaviour, most + would expect. If your kernel does not display this behavior, most likely there is something wrong with your wiring. @@ -2980,7 +2981,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure use I/O locations, but instead require a 32K chunk of memory. The factory configuration for ISA cards places this at 0xd0000-0xd7fff. - They also require an IRQ. PCI cards will, of course, autoconfigure + They also require an IRQ. PCI cards will, of course, auto-configure themselves. You can attach up to 4 external modules to each host card. The @@ -3127,7 +3128,7 @@ moused_port="/dev/psm0" mouse daemon you will need to include the following text in /etc/rc.conf. This example assumes that the mouse is connected to COM1: and can be - automatically recognised by the mouse daemon. + automatically recognized by the mouse daemon. moused_enable="YES" moused_type="auto" @@ -3165,7 +3166,7 @@ moused_port="/dev/cuaa0" The USB device drivers are a relatively new addition to FreeBSD and have not yet been included in the GENERIC kernel. The - following prodecure is an example of how to setup the relevant + following procedure is an example of how to setup the relevant drivers on a typical system. @@ -3350,7 +3351,7 @@ moused_port="/dev/ums0" Mainstream ESDI drives use 34 to 36 sectors per track. Most (older) controllers cannot handle more than this number of sectors. Newer, higher capacity, drives use higher numbers of - sectors per track. For instance, I own a 670 Mb drive that has 54 + sectors per track. For instance, I own a 670 MB drive that has 54 sectors per track. In my case, the controller could not handle this number of @@ -3582,7 +3583,7 @@ disk wd3 at wdc1 drive 1 BIOS to allow the BIOS to boot it. Before using NEFMT.EXE I tried to format - the disk using the ACB-2320 BIOS builtin formatter. This proved + the disk using the ACB-2320 BIOS built-in formatter. This proved to be a show stopper, because it did not give me an option to disable spare sectoring. With spare sectoring enabled the FreeBSD installation process broke down on the bad144 @@ -3675,7 +3676,7 @@ disk wd3 at wdc1 drive 1 After some time an industry effort was started to come to a more strict standard allowing devices from different vendors to work together. This effort was recognized in the ANSI SCSI-1 standard. - The SCSI-1 standard (approx 1985) is rapidly becoming obsolete. The + The SCSI-1 standard (approximately 1985) is rapidly becoming obsolete. The current standard is SCSI-2 (see Further reading), with SCSI-3 on the drawing boards. @@ -3711,7 +3712,7 @@ disk wd3 at wdc1 drive 1 In SCSI-3 even faster bus types are introduced, along with a serial SCSI busses that reduces the cabling overhead and allows a higher maximum bus length. You might see names like SSA and - Fiberchannel in this context. None of the serial buses are currently + fibre channel in this context. None of the serial buses are currently in widespread use (especially not in the typical FreeBSD environment). For this reason the serial bus types are not discussed any further. @@ -3981,7 +3982,7 @@ disk wd3 at wdc1 drive 1 On modern devices, sometimes integrated terminators are used. These things are special purpose integrated circuits that can be - dis/en-abled with a control pin. It is not necessary to + enabled or disabled with a control pin. It is not necessary to physically remove them from a device. You may find them on newer host adapters, sometimes they are software configurable, using some sort of setup tool. Some will even auto-detect the cables @@ -4052,7 +4053,7 @@ disk wd3 at wdc1 drive 1 A narrow SCSI device can not communicate with a SCSI device with a target ID larger than 7. This means it is generally not a good idea to move your SCSI host adapter's target ID to - something higher than 7 (or your CD-ROM will stop + something higher than 7 (or your CDROM will stop working). @@ -4210,7 +4211,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) On top of the card drivers there are a number of more generic drivers for a class of devices. More specific: a driver for tape - devices (abbreviation: st), magnetic disks (sd), CD-ROMs (cd) etc. + devices (abbreviation: st), magnetic disks (sd), CDROMs (cd) etc. In case you are wondering where you can find this stuff, it all lives in /sys/scsi. See the man pages in section 4 for more details. @@ -4288,7 +4289,7 @@ disk sd1 at scbus0 target 1 [implicit LUN 0 if omitted] disk sd2 at scbus1 target 3 [SCSI disk on the uha0] disk sd3 at scbus2 target 4 [SCSI disk on the ncr0] tape st1 at scbus0 target 6 [SCSI tape at target 6] -device cd0 at scbus? [the first ever CD-ROM found, no wiring] +device cd0 at scbus? [the first ever CDROM found, no wiring] The example above tells the kernel to look for a ahc (Adaptec 274x) controller, then for an NCR/Symbios board, and so on. The @@ -4349,7 +4350,7 @@ controller scbus0 device sd0 [support for 4 SCSI harddisks, sd0 up sd3] device st0 [support for 2 SCSI tapes] -[for the CD-ROM] +[for the CDROM] device cd0 #Only need one of these, the code dynamically grows Both examples support SCSI disks. If during boot more devices @@ -4361,7 +4362,7 @@ device cd0 #Only need one of these, the code dynamically growsUse man 4 scsi to check for the latest info on the SCSI subsystem. For more detailed info on host adapter - drivers use eg man 4 ahc for info on the + drivers use e.g., man 4 ahc for info on the Adaptec 294x driver. @@ -4371,7 +4372,7 @@ device cd0 #Only need one of these, the code dynamically growsExperience has shown that some devices are slow to respond to INQUIRY commands after a SCSI bus reset (which happens at boot time). An INQUIRY command is sent by the kernel on boot to see - what kind of device (disk, tape, CD-ROM etc) is connected to a + what kind of device (disk, tape, CDROM etc.) is connected to a specific target ID. This process is called device probing by the way. @@ -4384,7 +4385,7 @@ device cd0 #Only need one of these, the code dynamically grows This line sets the delay time to 15 seconds. On my own system - I had to use 3 seconds minimum to get my trusty old CD-ROM drive + I had to use 3 seconds minimum to get my trusty old CDROM drive to be recognized. Start with a high value (say 30 seconds or so) when you have problems with device recognition. If this helps, tune it back until it just stays working. @@ -4426,7 +4427,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue This scheme works fine, but keep in mind that it of course only works for devices that are known to be weird. If you are the - first to connect your bogus Mumbletech SCSI CD-ROM you might be + first to connect your bogus Mumbletech SCSI CDROM you might be the one that has to define which workaround is needed. After you got your Mumbletech working, please send the @@ -4473,14 +4474,14 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue - Tagged command queueing + Tagged command queuing Modern SCSI devices, particularly magnetic disks, support what is called tagged command queuing (TCQ). In a nutshell, TCQ allows the device to have multiple I/O requests outstanding at the same time. Because the device is - intelligent, it can optimise its operations (like head + intelligent, it can optimize its operations (like head positioning) based on its own request queue. On SCSI devices like RAID (Redundant Array of Independent Disks) arrays the TCQ function is indispensable to take advantage of the device's @@ -4513,7 +4514,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue different transfer speeds on the host bus (ISA or AT in this case). The controller is settable to different rates because not all motherboards can handle the higher speeds. Problems like - hangups, bad data etc might be the result of using a higher data + hang-ups, bad data etc might be the result of using a higher data transfer rate then your motherboard can stomach. The solution is of course obvious: switch to a lower data @@ -4575,7 +4576,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Disable tagged command queuing to make things as simple as - possible (for a NCR hostadapter based system see man + possible (for a NCR host adapter based system see man ncrcontrol) @@ -4782,7 +4783,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed (If you are a speed maniac and want a 10,000RPM drive for your - cute little peecee, be my guest; however, those drives become + cute little PC, be my guest; however, those drives become extremely hot. Don't even think about it if you don't have a fan blowing air directly at the drive or a properly ventilated disk enclosure.) @@ -4827,7 +4828,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedMost SCSI drives sold today are of 3.5" form factor. They come in two different heights; 1.6" (half-height) or 1" (low-profile). The half-height drive is the same - height as a CD-ROM drive. However, don't forget the spacing rule + height as a CDROM drive. However, don't forget the spacing rule mentioned in the previous section. If you have three standard 3.5" drive bays, you will not be able to put three half-height drives in there (without frying them, that is). @@ -4908,7 +4909,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedThe &man.st.4; driver provides support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT - (Digital Linear Tape), QIC Minicartridge and 9-track (remember the + (Digital Linear Tape), QIC Mini cartridge and 9-track (remember the big reels that you see spinning in Hollywood computer rooms) tape drives. See the &man.st.4; manual page for a detailed description. @@ -4955,7 +4956,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed QIC (Quarter-Inch Cartridge) - Archive Ananconda + Archive Anaconda 2750 Archive Viper @@ -5176,7 +5177,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedThis drives quirks are known and pre-compiled into the scsi tape device driver (&man.st.4;). - Under FreeBSD 2.2-current, use mt blocksize + Under FreeBSD 2.2-CURRENT, use mt blocksize 512 to set the blocksize. (The particular drive had firmware revision 21247 -005. Other firmware revisions may behave differently) Previous versions of FreeBSD did not have this @@ -5187,8 +5188,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Pedro A M Vazquez vazquez@IQM.Unicamp.BR - Mike Smith - msmith@atrad.adelaide.edu.au + &a.msmith; @@ -5219,7 +5219,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedThe boot message identifier for this drive is Conner tape. - This is a floppy controller, minicartridge tape drive. + This is a floppy controller, mini cartridge tape drive. Native capacity is XXXX @@ -5238,7 +5238,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed type 1 removable SCSI 2. - This is a minicartridge tape drive. + This is a mini cartridge tape drive. Native capacity is XXXX @@ -5283,12 +5283,12 @@ options "TUNE_1542" #dynamic tune of bus DMA speedThis is a mini-cartridge tape drive. Native capacity is 1GB when using MC3000XL - minicartridges. + mini cartridges. Data transfer rate is XXX This drive can read and write DC2300 (550MB), DC2750 (750MB), - MC3000 (750MB), and MC3000XL (1GB) minicartridges. + MC3000 (750MB), and MC3000XL (1GB) mini cartridges. WARNING: This drive does not meet the SCSI-2 specifications. The drive locks up completely in response to a SCSI MODE_SELECT @@ -5297,8 +5297,8 @@ options "TUNE_1542" #dynamic tune of bus DMA speed&prompt.root; mt -f /dev/st0ctl.0 blocksize 1024 - Before using a minicartridge for the first time, the - minicartridge must be formated. FreeBSD 2.1.0-RELEASE and + Before using a mini cartridge for the first time, the + mini cartridge must be formated. FreeBSD 2.1.0-RELEASE and earlier: &prompt.root; /sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0" @@ -5340,8 +5340,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedProduction of this drive has been discontinued. - Reported by: Mike Smith - msmith@atrad.adelaide.edu.au + Reported by: &a.msmith; @@ -5580,7 +5579,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Data transfer rate is 160kB/s. - Reported by: mark thompson + Reported by: Mark Thompson mark.a.thompson@pobox.com @@ -5674,10 +5673,10 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" In order to get this drive to stream, set the blocksize to 512 bytes (mt blocksize 512) reported by Kenneth - Merry ken@ulc199.residence.gatech.edu + Merry ken@ulc199.residence.gatech.edu. SONY SDT-5000 327M information reported by - Charles Henrich henrich@msu.edu + Charles Henrich henrich@msu.edu. Reported by: &a.jmz; @@ -5703,8 +5702,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" IBM and Emerald units will not work. Replacing the firmware EPROM of these units will solve the problem. - Reported by: Michael Smith - msmith@atrad.adelaide.edu.au + Reported by: &a.msmith; @@ -5747,7 +5745,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" This drives quirks are known and pre-compiled into the scsi tape device driver (&man.st.4;) beginning with FreeBSD - 2.2-current. For previous versions of FreeBSD, use + 2.2-CURRENT. For previous versions of FreeBSD, use mt to read one block from the tape, rewind the tape, and then execute the backup program (mt fsr 1; mt rewind; dump ...) @@ -5820,7 +5818,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" - CD-ROM drives + CDROM drives Contributed by &a.obrien;. 23 November 1997. diff --git a/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml index 2268cea7d6..0070cb3e44 100644 --- a/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml @@ -1,7 +1,7 @@ @@ -399,7 +399,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) Luckily for us, on a FreeBSD system this setup is a snap. The processes that need to be running can all be run at boot time with - a few modificationss to your /etc/rc.conf + a few modifications to your /etc/rc.conf file. On the NFS server make sure you have: @@ -758,7 +758,7 @@ diskless:\ swapsize - set diskless swapsize in Kbytes + set diskless swapsize in KBytes @@ -827,7 +827,7 @@ hostname myclient.mydomain as in the example above, the swapfile for myclient will be called /swapfs/swap.X.X.X.X where X.X.X.X is the client's IP addr, - eg: + e.g.: &prompt.root; dd if=/dev/zero of=/swapfs/swap.192.1.2.4 bs=1k count=20000 @@ -900,7 +900,7 @@ hostname myclient.mydomain Dan Kegel's ISDN Page. - A quick simple roadmap to ISDN follows: + A quick simple road map to ISDN follows: @@ -910,14 +910,14 @@ hostname myclient.mydomain If you are planning to use ISDN primarily to connect to the - Internet with an Internet Provider on a dialup non-dedicated basis, + Internet with an Internet Provider on a dial-up non-dedicated basis, I suggest you look into Terminal Adapters. This will give you the most flexibility, with the fewest problems, if you change providers. - If you are connecting two lans together, or connecting to the + If you are connecting two LANs together, or connecting to the Internet with a dedicated ISDN connection, I suggest you consider the stand alone router/bridge option. @@ -991,7 +991,7 @@ subscribe freebsd-isdn The main advantage of using a TA to connect to an Internet Provider is that you can do Dynamic PPP. As IP address space becomes more and more scarce, most providers are not willing to provide you - with a static IP anymore. Most standalone routers are not able to + with a static IP anymore. Most stand-alone routers are not able to accommodate dynamic IP allocation. TA's completely rely on the PPP daemon that you are running for @@ -1039,11 +1039,11 @@ subscribe freebsd-isdn save you having to buy another serial cable, and find another empty electrical socket. - A synchronous card with a TA is at least as fast as a standalone + A synchronous card with a TA is at least as fast as a stand-alone router, and with a simple 386 FreeBSD box driving it, probably more flexible. - The choice of sync/TA vs standalone router is largely a religious + The choice of sync/TA v.s. stand-alone router is largely a religious issue. There has been some discussion of this in the mailing lists. I suggest you search the archives for the @@ -1051,7 +1051,7 @@ subscribe freebsd-isdn - Standalone ISDN Bridges/Routers + Stand-alone ISDN Bridges/Routers ISDN bridges or routers are not at all specific to FreeBSD or any other operating system. For a more complete description of routing @@ -1097,12 +1097,12 @@ subscribe freebsd-isdn | ---Windows 95 (Do not admit to owning it) | -Standalone router +Stand-alone router | ISDN BRI line If your home/branch office is only one computer you can use a - twisted pair crossover cable to connect to the standalone router + twisted pair crossover cable to connect to the stand-alone router directly. @@ -1121,7 +1121,7 @@ ISDN BRI line | | | ---Windows 95 | B | - |___---Standalone router + |___---Stand-alone router | ISDN BRI line @@ -1134,12 +1134,12 @@ ISDN BRI line etc. This can be very useful feature, for example if you have an - dedicated internet ISDN connection at your office and would like to + 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 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 - dialin, dialout or dynamically bond(MPP etc.) with the first B channel + dial-in, dial-out or dynamically bond(MPP etc.) with the first B channel for more bandwidth. An Ethernet bridge will also allow you to transmit more than just @@ -1167,10 +1167,10 @@ ISDN BRI line How does it work? - There are 3 types of hosts in an NIS enviornment; master + There are 3 types of hosts in an NIS environment; master servers, slave servers, and clients. Servers act as a central repository for host configuration information. Master servers - hold the authoritatve copy of this information, while slave + hold the authoritative copy of this information, while slave servers mirror this information for redundancy. Clients rely on the servers to provide this information to them. @@ -1217,7 +1217,7 @@ ISDN BRI line Physical Server Requirements - There are several things to keep in mind when chosing a + There are several things to keep in mind when choosing a machine to use as a NIS server. One of the unfortunate things about NIS is the level of dependency the clients have on the server. If a client cannot contact the server for its NIS @@ -1259,7 +1259,7 @@ ISDN BRI line Setting up a NIS master server - Setting up a master NIS server can be relativly straight + Setting up a master NIS server can be relatively straight forward, depending on your needs. FreeBSD comes with a handy script called ypinit that makes the initial setup procedure very easy. A few steps are needed ahead of @@ -1392,46 +1392,46 @@ Ok, please remember to go back and redo manually whatever fails. If you don't, something might not work. There will be no further questions. The remainder of the procedure should take a few minutes, to copy the databases from master.example.com. -Transfering netgroup... -ypxfr: Exiting: Map successfully transfered -Transfering netgroup.byuser... -ypxfr: Exiting: Map successfully transfered -Transfering netgroup.byhost... -ypxfr: Exiting: Map successfully transfered -Transfering master.passwd.byuid... -ypxfr: Exiting: Map successfully transfered -Transfering passwd.byuid... -ypxfr: Exiting: Map successfully transfered -Transfering passwd.byname... -ypxfr: Exiting: Map successfully transfered -Transfering group.bygid... -ypxfr: Exiting: Map successfully transfered -Transfering group.byname... -ypxfr: Exiting: Map successfully transfered -Transfering services.byname... -ypxfr: Exiting: Map successfully transfered -Transfering rpc.bynumber... -ypxfr: Exiting: Map successfully transfered -Transfering rpc.byname... -ypxfr: Exiting: Map successfully transfered -Transfering protocols.byname... -ypxfr: Exiting: Map successfully transfered -Transfering master.passwd.byname... -ypxfr: Exiting: Map successfully transfered -Transfering networks.byname... -ypxfr: Exiting: Map successfully transfered -Transfering networks.byaddr... -ypxfr: Exiting: Map successfully transfered -Transfering netid.byname... -ypxfr: Exiting: Map successfully transfered -Transfering hosts.byaddr... -ypxfr: Exiting: Map successfully transfered -Transfering protocols.bynumber... -ypxfr: Exiting: Map successfully transfered -Transfering ypservers... -ypxfr: Exiting: Map successfully transfered -Transfering hosts.byname... -ypxfr: Exiting: Map successfully transfered +Transferring netgroup... +ypxfr: Exiting: Map successfully transferred +Transferring netgroup.byuser... +ypxfr: Exiting: Map successfully transferred +Transferring netgroup.byhost... +ypxfr: Exiting: Map successfully transferred +Transferring master.passwd.byuid... +ypxfr: Exiting: Map successfully transferred +Transferring passwd.byuid... +ypxfr: Exiting: Map successfully transferred +Transferring passwd.byname... +ypxfr: Exiting: Map successfully transferred +Transferring group.bygid... +ypxfr: Exiting: Map successfully transferred +Transferring group.byname... +ypxfr: Exiting: Map successfully transferred +Transferring services.byname... +ypxfr: Exiting: Map successfully transferred +Transferring rpc.bynumber... +ypxfr: Exiting: Map successfully transferred +Transferring rpc.byname... +ypxfr: Exiting: Map successfully transferred +Transferring protocols.byname... +ypxfr: Exiting: Map successfully transferred +Transferring master.passwd.byname... +ypxfr: Exiting: Map successfully transferred +Transferring networks.byname... +ypxfr: Exiting: Map successfully transferred +Transferring networks.byaddr... +ypxfr: Exiting: Map successfully transferred +Transferring netid.byname... +ypxfr: Exiting: Map successfully transferred +Transferring hosts.byaddr... +ypxfr: Exiting: Map successfully transferred +Transferring protocols.bynumber... +ypxfr: Exiting: Map successfully transferred +Transferring ypservers... +ypxfr: Exiting: Map successfully transferred +Transferring hosts.byname... +ypxfr: Exiting: Map successfully transferred slave.example.com has been setup as an YP slave server without any errors. Don't forget to update map ypservers on master.example.com. @@ -1622,7 +1622,7 @@ Don't forget to update map ypservers on master.example.com. - libscrypt vs. libdescrypt + libscrypt v.s. libdescrypt One of the most common issues that people run into when trying to implement NIS is crypt library compatibility. If your NIS @@ -1644,7 +1644,7 @@ lrwxr-xr-x 1 root wheel 16 Nov 8 14:27 /usr/lib/libdescrypt.so@ -> libdes -r--r--r-- 1 root wheel 14750 Nov 8 14:27 /usr/lib/libdescrypt_p.a If the machine is configured to use the standard FreeBSD MD5 - crypt libraries they will look somethine like this: + crypt libraries they will look something like this: &prompt.user; ls -l /usr/lib/*crypt* diff --git a/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml b/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml index b6c5c3c292..12de057851 100644 --- a/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml @@ -1,7 +1,7 @@ @@ -33,7 +33,7 @@ x 12 mm) than 8mm cartridges. 4mm, like 8mm, has comparatively short head life for the same reason, both use helical scan. - Data thruput on these drives starts ~150kB/s, peaking at ~500kB/s. + Data throughput on these drives starts ~150kB/s, peaking at ~500kB/s. Data capacity starts at 1.3 GB and ends at 2.0 GB. Hardware compression, available with most of these drives, approximately doubles the capacity. Multi-drive tape library units can have 6 @@ -60,7 +60,7 @@ One downside of 8mm tape is relatively short head and tape life due to the high rate of relative motion of the tape across the heads. - Data thruput ranges from ~250kB/s to ~500kB/s. Data sizes start + Data throughput ranges from ~250kB/s to ~500kB/s. Data sizes start at 300 MB and go up to 7 GB. Hardware compression, available with most of these drives, approximately doubles the capacity. These drives are available as single units or multi-drive tape libraries @@ -99,7 +99,7 @@ also use 1/4" wide tape are discussed separately. Tape libraries and changers are not available. - Data thruput ranges from ~150kB/s to ~500kB/s. Data capacity + Data throughput ranges from ~150kB/s to ~500kB/s. Data capacity ranges from 40 MB to 15 GB. Hardware compression is available on many of the newer QIC drives. QIC drives are less frequently installed; they are being supplanted by DAT drives. @@ -139,7 +139,7 @@ both the supply and take-up spools located inside the tape cartridge itself. - Data thruput is approximately 1.5MB/s, three times the thruput of + Data throughput is approximately 1.5MB/s, three times the throughput of 4mm, 8mm, or QIC tape drives. Data capacities range from 10GB to 20GB for a single drive. Drives are available in both multi-tape changers and multi-tape, multi-drive tape libraries containing from 5 to 900 @@ -381,7 +381,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready two copies of each. - Second, determine that the boot and fixit floppies + Second, determine that the boot and fix-it floppies (boot.flp and fixit.flp) have all your devices. The easiest way to check is to reboot your machine with the boot floppy in the floppy drive and check the boot diff --git a/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml b/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml index da26d06487..41322bc613 100644 --- a/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml @@ -1,7 +1,7 @@ @@ -284,7 +284,7 @@ NetWare Server (protected mode ODI driver) loader and - subservices to allow the use of ODI card drivers supplied with + sub-services to allow the use of ODI card drivers supplied with network cards. The same thing for NDIS drivers and NetWare SCSI drivers. @@ -303,7 +303,7 @@ A concerted effort at support for portable computers. This is somewhat handled by changing PCMCIA bridging rules and power management event handling. But there are things like detecting - internal vs. external display and picking a different screen + internal v.s.. external display and picking a different screen resolution based on that fact, not spinning down the disk if the machine is in dock, and allowing dock-based cards to disappear without affecting the machines ability to boot (same issue for @@ -363,7 +363,7 @@ - If you know of any bugfixes which have been successfully + If you know of any bug fixes which have been successfully applied to -current but have not been merged into -stable after a decent interval (normally a couple of weeks), send the committer a polite reminder. @@ -546,7 +546,7 @@ In the rare case of a significant contribution of a large body work, or the addition of an important new feature to FreeBSD, it - becomes almost always necessary to either send changes as uuencode'd + becomes almost always necessary to either send changes as uuencoded tar files or upload them to our ftp site ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/. @@ -731,7 +731,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donors Gallery The FreeBSD Project is indebted to the following donors and would - like to publically thank them here! + like to publicly thank them here! @@ -846,7 +846,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Laser5 of Japan (a portion of the profits from sales of their various FreeBSD - CD-ROMs). + CDROMs). @@ -983,10 +983,10 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The interface business GmbH, Dresden has been patiently supporting - &a.joerg; who has often preferred FreeBSD work over paywork, and + &a.joerg; who has often preferred FreeBSD work over paid work, and used to fall back to their (quite expensive) EUnet Internet connection whenever his private connection became too slow or - flakey to work with it... + flaky to work with it... @@ -1126,7 +1126,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - Adrian Chadd adrian@freebsd.org + Adrian Chadd adrian@FreeBSD.org diff --git a/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml b/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml index 35bf891f54..6d56021fa1 100644 --- a/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml @@ -1,7 +1,7 @@ @@ -24,7 +24,7 @@ - -CURRENT vs. -STABLE + -CURRENT v.s.. -STABLE There are two development branches to FreeBSD; -CURRENT and -STABLE. This section will explain a bit about each and describe @@ -183,7 +183,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/. We also use wu-ftpd which allows - compressed/tar'd grabbing of whole trees. e.g. you + compressed/tarred grabbing of whole trees. e.g. you see: usr.bin/lex @@ -354,7 +354,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/ We also use wu-ftpd which allows - compressed/tar'd grabbing of whole trees. e.g. you + compressed/tarred grabbing of whole trees. e.g. you see: usr.bin/lex @@ -707,7 +707,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - Creating a list of changes (as unidiffs) to &man.ls.1; + Creating a list of changes (as unified diffs) to &man.ls.1; &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs @@ -764,7 +764,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Using <command>make world</command> - Once you have synchronised your local source tree against a + Once you have synchronized your local source tree against a particular version of FreeBSD (stable, current and so on) you must then use the source tree to rebuild the system. @@ -779,7 +779,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - Make sure you have taken a backup. And have a fixit floppy to + Make sure you have taken a backup. And have a fix-it floppy to hand. I have never needed to use them, and, touch wood, I never will, but it is always better to be safe than sorry. @@ -1006,7 +1006,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz&prompt.root; make -DNOPROFILE=true target - is another way of specifying that profiled libaries should + is another way of specifying that profiled libraries should not be built, and corresponds with the NOPROFILE= true @@ -1261,7 +1261,7 @@ Script done, … Name the new root directory - (<filename>/var/tmp/root</filename>)with a timestamp, so you can + (<filename>/var/tmp/root</filename>)with a time stamp, so you can easily compare differences between versions Frequently remaking the world means that you have to update @@ -1348,7 +1348,7 @@ Script done, … If you are using DEVFS then this is probably unnecessary. - For safety's sake, this is a multistep process. + For safety's sake, this is a multi-step process. @@ -1362,7 +1362,7 @@ Script done, … Now, take a snapshot of your current /dev. This snapshot needs to contain the permissions, ownerships, major and minor numbers of each filename, - but it should not contain the timestamps. The easiest way to do + but it should not contain the time stamps. The easiest way to do this is to use &man.awk.1; to strip out some of the information. @@ -1399,11 +1399,11 @@ Script done, … Update <filename>/stand</filename> - This step is included only for completeness, it can safely be + This step is included only for completeness. It can safely be omitted. - For completenesses sake you may want to update the files in + For the sake of completeness, you may want to update the files in /stand as well. These files consist of hard links to the /stand/sysinstall binary. This binary should be statically linked, so that it can work when no other @@ -1769,8 +1769,8 @@ Antonio Also in /etc/make.conf, set CFLAGS to something like -O - -pipe. The optimisation -O2 is much - slower, and the optimisation difference between + -pipe. The optimization -O2 is much + slower, and the optimization difference between -O and -O2 is normally negligible. -pipe lets the compiler use pipes rather than temporary files for communication, which diff --git a/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml b/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml index 24c97212b4..bca1791fdd 100644 --- a/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml @@ -1,7 +1,7 @@ @@ -54,7 +54,7 @@ An illustration from the files of Bill and Fred's Exceptional Adventures: - Bill breaks-down an older WIntel box to make another FreeBSD box + Bill breaks-down an older Wintel box to make another FreeBSD box for Fred. Bill installs a single SCSI drive as SCSI unit zero, and installs FreeBSD on it. @@ -75,7 +75,7 @@ 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 newer version of FreeBSD. Bill removes SCSI unit zero because it was - a bit flakey, and replaces it with another identical disk drive from + a bit flaky, and replaces it with another identical disk drive from the "archive." Bill then installs the new version of FreeBSD onto the new SCSI unit zero using Fred's magic internet FTP floppies. The installation goes well. @@ -104,7 +104,7 @@ We are delighted to mention that no data bytes were killed or harmed in any way by our discovery of this phenomenon. The older SCSI - unit zero was retrieved from the bonepile, and all of Fred's work was + unit zero was retrieved from the bone pile, and all of Fred's work was returned to him, (and now Bill knows that he can count as high as zero). @@ -116,7 +116,7 @@ Disk Naming - Physical drives come in two main flavours, + Physical drives come in two main flavors, IDE, or SCSI; but there are also drives backed by RAID controllers, flash memory, and so forth. Since these behave quite differently, they have their diff --git a/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml b/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml index 4a90d4b5d9..739d6adc18 100644 --- a/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml @@ -1,7 +1,7 @@ @@ -434,7 +434,7 @@ help subscriber overlap and except for the most esoteric mixes (say "-stable & -scsi"), there really is no reason to post to more than one list at a time. If a message is sent to you in such a - way that multiple mailing lists appear on the Cc line then the cc + way that multiple mailing lists appear on the Cc line then the Cc line should also be trimmed before sending it out again. You are still responsible for your own cross-postings, no matter who the originator might have @@ -1235,7 +1235,7 @@ help http://www.nz.FreeBSD.org/ — New Zeland. + url="http://www.nz.FreeBSD.org/">http://www.nz.FreeBSD.org/ — New Zealand. @@ -1423,15 +1423,15 @@ help storm.uk.FreeBSD.org - ssh only - Read-only cvs, personal webspace, email + SSH only + Read-only cvs, personal web space, email &a.brian dogma.freebsd-uk.eu.org Telnet/FTP/SSH - E-Mail, Webspace, Anonymous FTP + E-Mail, Web space, Anonymous FTP Lee Johnston lee@uk.FreeBSD.org diff --git a/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml b/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml index b2f9347a91..06c7ea9e2e 100644 --- a/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml @@ -1,7 +1,7 @@ @@ -74,7 +74,7 @@ For Pentium Pro (P6) systems, I'm quite fond of the Tyan S1668 dual-processor motherboard as well as the Intel PR440FX motherboard - with on-board SCSI WIDE and 100/10MB Intel Etherexpress NIC. You + with on-board SCSI WIDE and 100/10MB Intel EtherExpress NIC. You can build a dandy little single or dual processor system (which is supported in FreeBSD 3.0) for very little cost now that the Pentium Pro 180/256K chips have fallen so greatly in price, but no telling @@ -153,7 +153,7 @@ My SCSI preferences extend to SCSI CDROM drives as well, and while the Toshiba drives - have always been favourites of mine (in whatever speed is hot that + have always been favorites of mine (in whatever speed is hot that week), I'm still fond of my good old Plextor PX-12CS drive. It's only a 12 speed, but it's offered excellent performance and @@ -263,13 +263,13 @@ then Digi International makes the SYNC/570 - series, with drivers now in FreeBSD-current. Emerging Technologies also manufactures a board with T1/E1 capabilities, using software they provide. I have no direct experience using either product, however. - Multiport card options are somewhat more numerous, though it has + multiport card options are somewhat more numerous, though it has to be said that FreeBSD's support for Cyclades's products is probably the tightest, primarily as a result of that company's @@ -291,7 +291,7 @@ Labs AWE32 though just about anything from Creative Labs will generally work these days. This is not to say that other types of sound cards don't also work, simply that I have little experience - with them (I was a former GUS fan, but Gravis's soundcard situation + with them (I was a former GUS fan, but Gravis's sound card situation has been dire for some time). @@ -379,10 +379,11 @@ Works fine, but many MB manufactures leave out the - external dirty bit SRAM needed for write back operation. Work - arounds are either run it in write through mode, or get the - dirty bit SRAM installed. (I have these for the ASUS - PCI/I-486SP3G rev 1.6 and later boards). + external dirty bit SRAM needed for write back operation. + You can work around this either by running it in write + through mode, or get the dirty bit SRAM installed (I + have these for the ASUS PCI/I-486SP3G rev 1.6 and later + boards). @@ -460,7 +461,7 @@ P6 class (Pentium Pro/Pentium II) Both the Pentium Pro and Pentium II work fine with FreeBSD. In - fact, our main ftp site ftp.FreeBSD.org (also known as "ftp.cdrom.com", world's largest ftp site) runs FreeBSD on a Pentium Pro. The Intel Pentium (P54C), Pentium MMX (P55C), AMD K6 and Cyrix/IBM 6x86MX processors are all reported to work with FreeBSD. I will not go into details of which processor is faster than what, - there are zillions of web sites on the Internet that tells you one + there are millions of web sites on the Internet that tells you one way or another. :) @@ -656,7 +657,7 @@ 286 class Sorry, FreeBSD does not run on 80286 machines. It is nearly - impossible to run today's large full-featured UNIXes on such + impossible to run today's large full-featured unices on such hardware. @@ -840,7 +841,7 @@ when the device connected to the UART is a modem, the modem may report the presence of a carrier on the phone line while the computer may be able to instruct the modem to reset itself or to - not take calls by asserting or deasserting one more more of these + not take calls by asserting or disasserting one more more of these extra signals. The function of each of these additional signals is defined in the EIA RS232-C standard. @@ -1622,7 +1623,7 @@ INS8250 -> INS8250B combinations of events occur that were not well tested or considered in the Windows driver. This is because most modem vendors and 16550-clone makers use the Microsoft drivers from - Windows for Workgroups 3.11 and the Microsoft MSD utility as the + Windows for Workgroups 3.11 and the Microsoft MS-DOS utility as the primary tests for compatibility with the NS16550A. This over-simplistic criteria means that if a different operating system is used, problems could appear due to subtle differences @@ -2549,7 +2550,7 @@ INS8250 -> INS8250B By default this part is similar to the NS16550A, but an extended 32-byte send and receive buffer can be optionally - enabled. Made by Startech. + enabled. Made by StarTech. @@ -2769,7 +2770,7 @@ sio16: type 16550A (multiport master) &prompt.root; ./MAKEDEV ttyg &prompt.root; ./MAKEDEV cuag - If you do not want or need callout devices for some + If you do not want or need call-out devices for some reason, you can dispense with making the cua* devices. @@ -2806,7 +2807,7 @@ sio16: type 16550A (multiport master) need to configure them as COM2 (aka sio1–I/O address 0x2F8 and IRQ 3), and the third port (aka sio2) as I/O - 0x3E8 and IRQ 5. Obviously this is a waste of IRQ ressources, as + 0x3E8 and IRQ 5. Obviously this is a waste of IRQ resources, as it should be basically possible to run both extension board ports using a single IRQ with the COM_MULTIPORT configuration described in the previous sections. @@ -2838,7 +2839,7 @@ IRQ 2 3 4 5 You need to decouple the IRQ drivers for the two UARTs, so that the IRQ line of the board only goes up if (and only if) one of the UARTs asserts a IRQ, and stays low otherwise. The solution - was proposed by Jrg Wunsch + was proposed by Joerg Wunsch j@ida.interface-business.de: To solder up a wired-or consisting of two diodes (Germanium or Schottky-types strongly preferred) and a 1 kOhm resistor. Here is the schematic, @@ -2873,7 +2874,7 @@ device sio2 at isa? port "IO_COM3" tty flags 0x205 irq 3Note that the flags setting for sio1 and sio2 is - truely essential; refer to + truly essential; refer to &man.sio.4; for details. (Generally, the 2 in the "flags" attribute refers to sio2 which holds the IRQ, and you surely want a 5 @@ -2895,7 +2896,7 @@ sio2: type 16550A (multiport master) the basic idea is that you observe 0x1 in the first, third, and fourth place. This means that the corresponding IRQ was set upon output and cleared after, which is just what we - would expect. If your kernel does not display this behaviour, most + would expect. If your kernel does not display this behavior, most likely there is something wrong with your wiring. @@ -2980,7 +2981,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure use I/O locations, but instead require a 32K chunk of memory. The factory configuration for ISA cards places this at 0xd0000-0xd7fff. - They also require an IRQ. PCI cards will, of course, autoconfigure + They also require an IRQ. PCI cards will, of course, auto-configure themselves. You can attach up to 4 external modules to each host card. The @@ -3127,7 +3128,7 @@ moused_port="/dev/psm0" mouse daemon you will need to include the following text in /etc/rc.conf. This example assumes that the mouse is connected to COM1: and can be - automatically recognised by the mouse daemon. + automatically recognized by the mouse daemon. moused_enable="YES" moused_type="auto" @@ -3165,7 +3166,7 @@ moused_port="/dev/cuaa0" The USB device drivers are a relatively new addition to FreeBSD and have not yet been included in the GENERIC kernel. The - following prodecure is an example of how to setup the relevant + following procedure is an example of how to setup the relevant drivers on a typical system. @@ -3350,7 +3351,7 @@ moused_port="/dev/ums0" Mainstream ESDI drives use 34 to 36 sectors per track. Most (older) controllers cannot handle more than this number of sectors. Newer, higher capacity, drives use higher numbers of - sectors per track. For instance, I own a 670 Mb drive that has 54 + sectors per track. For instance, I own a 670 MB drive that has 54 sectors per track. In my case, the controller could not handle this number of @@ -3582,7 +3583,7 @@ disk wd3 at wdc1 drive 1 BIOS to allow the BIOS to boot it. Before using NEFMT.EXE I tried to format - the disk using the ACB-2320 BIOS builtin formatter. This proved + the disk using the ACB-2320 BIOS built-in formatter. This proved to be a show stopper, because it did not give me an option to disable spare sectoring. With spare sectoring enabled the FreeBSD installation process broke down on the bad144 @@ -3675,7 +3676,7 @@ disk wd3 at wdc1 drive 1 After some time an industry effort was started to come to a more strict standard allowing devices from different vendors to work together. This effort was recognized in the ANSI SCSI-1 standard. - The SCSI-1 standard (approx 1985) is rapidly becoming obsolete. The + The SCSI-1 standard (approximately 1985) is rapidly becoming obsolete. The current standard is SCSI-2 (see Further reading), with SCSI-3 on the drawing boards. @@ -3711,7 +3712,7 @@ disk wd3 at wdc1 drive 1 In SCSI-3 even faster bus types are introduced, along with a serial SCSI busses that reduces the cabling overhead and allows a higher maximum bus length. You might see names like SSA and - Fiberchannel in this context. None of the serial buses are currently + fibre channel in this context. None of the serial buses are currently in widespread use (especially not in the typical FreeBSD environment). For this reason the serial bus types are not discussed any further. @@ -3981,7 +3982,7 @@ disk wd3 at wdc1 drive 1 On modern devices, sometimes integrated terminators are used. These things are special purpose integrated circuits that can be - dis/en-abled with a control pin. It is not necessary to + enabled or disabled with a control pin. It is not necessary to physically remove them from a device. You may find them on newer host adapters, sometimes they are software configurable, using some sort of setup tool. Some will even auto-detect the cables @@ -4052,7 +4053,7 @@ disk wd3 at wdc1 drive 1 A narrow SCSI device can not communicate with a SCSI device with a target ID larger than 7. This means it is generally not a good idea to move your SCSI host adapter's target ID to - something higher than 7 (or your CD-ROM will stop + something higher than 7 (or your CDROM will stop working). @@ -4210,7 +4211,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) On top of the card drivers there are a number of more generic drivers for a class of devices. More specific: a driver for tape - devices (abbreviation: st), magnetic disks (sd), CD-ROMs (cd) etc. + devices (abbreviation: st), magnetic disks (sd), CDROMs (cd) etc. In case you are wondering where you can find this stuff, it all lives in /sys/scsi. See the man pages in section 4 for more details. @@ -4288,7 +4289,7 @@ disk sd1 at scbus0 target 1 [implicit LUN 0 if omitted] disk sd2 at scbus1 target 3 [SCSI disk on the uha0] disk sd3 at scbus2 target 4 [SCSI disk on the ncr0] tape st1 at scbus0 target 6 [SCSI tape at target 6] -device cd0 at scbus? [the first ever CD-ROM found, no wiring] +device cd0 at scbus? [the first ever CDROM found, no wiring] The example above tells the kernel to look for a ahc (Adaptec 274x) controller, then for an NCR/Symbios board, and so on. The @@ -4349,7 +4350,7 @@ controller scbus0 device sd0 [support for 4 SCSI harddisks, sd0 up sd3] device st0 [support for 2 SCSI tapes] -[for the CD-ROM] +[for the CDROM] device cd0 #Only need one of these, the code dynamically grows Both examples support SCSI disks. If during boot more devices @@ -4361,7 +4362,7 @@ device cd0 #Only need one of these, the code dynamically growsUse man 4 scsi to check for the latest info on the SCSI subsystem. For more detailed info on host adapter - drivers use eg man 4 ahc for info on the + drivers use e.g., man 4 ahc for info on the Adaptec 294x driver. @@ -4371,7 +4372,7 @@ device cd0 #Only need one of these, the code dynamically growsExperience has shown that some devices are slow to respond to INQUIRY commands after a SCSI bus reset (which happens at boot time). An INQUIRY command is sent by the kernel on boot to see - what kind of device (disk, tape, CD-ROM etc) is connected to a + what kind of device (disk, tape, CDROM etc.) is connected to a specific target ID. This process is called device probing by the way. @@ -4384,7 +4385,7 @@ device cd0 #Only need one of these, the code dynamically grows This line sets the delay time to 15 seconds. On my own system - I had to use 3 seconds minimum to get my trusty old CD-ROM drive + I had to use 3 seconds minimum to get my trusty old CDROM drive to be recognized. Start with a high value (say 30 seconds or so) when you have problems with device recognition. If this helps, tune it back until it just stays working. @@ -4426,7 +4427,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue This scheme works fine, but keep in mind that it of course only works for devices that are known to be weird. If you are the - first to connect your bogus Mumbletech SCSI CD-ROM you might be + first to connect your bogus Mumbletech SCSI CDROM you might be the one that has to define which workaround is needed. After you got your Mumbletech working, please send the @@ -4473,14 +4474,14 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue - Tagged command queueing + Tagged command queuing Modern SCSI devices, particularly magnetic disks, support what is called tagged command queuing (TCQ). In a nutshell, TCQ allows the device to have multiple I/O requests outstanding at the same time. Because the device is - intelligent, it can optimise its operations (like head + intelligent, it can optimize its operations (like head positioning) based on its own request queue. On SCSI devices like RAID (Redundant Array of Independent Disks) arrays the TCQ function is indispensable to take advantage of the device's @@ -4513,7 +4514,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue different transfer speeds on the host bus (ISA or AT in this case). The controller is settable to different rates because not all motherboards can handle the higher speeds. Problems like - hangups, bad data etc might be the result of using a higher data + hang-ups, bad data etc might be the result of using a higher data transfer rate then your motherboard can stomach. The solution is of course obvious: switch to a lower data @@ -4575,7 +4576,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Disable tagged command queuing to make things as simple as - possible (for a NCR hostadapter based system see man + possible (for a NCR host adapter based system see man ncrcontrol) @@ -4782,7 +4783,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed (If you are a speed maniac and want a 10,000RPM drive for your - cute little peecee, be my guest; however, those drives become + cute little PC, be my guest; however, those drives become extremely hot. Don't even think about it if you don't have a fan blowing air directly at the drive or a properly ventilated disk enclosure.) @@ -4827,7 +4828,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedMost SCSI drives sold today are of 3.5" form factor. They come in two different heights; 1.6" (half-height) or 1" (low-profile). The half-height drive is the same - height as a CD-ROM drive. However, don't forget the spacing rule + height as a CDROM drive. However, don't forget the spacing rule mentioned in the previous section. If you have three standard 3.5" drive bays, you will not be able to put three half-height drives in there (without frying them, that is). @@ -4908,7 +4909,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedThe &man.st.4; driver provides support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT - (Digital Linear Tape), QIC Minicartridge and 9-track (remember the + (Digital Linear Tape), QIC Mini cartridge and 9-track (remember the big reels that you see spinning in Hollywood computer rooms) tape drives. See the &man.st.4; manual page for a detailed description. @@ -4955,7 +4956,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed QIC (Quarter-Inch Cartridge) - Archive Ananconda + Archive Anaconda 2750 Archive Viper @@ -5176,7 +5177,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedThis drives quirks are known and pre-compiled into the scsi tape device driver (&man.st.4;). - Under FreeBSD 2.2-current, use mt blocksize + Under FreeBSD 2.2-CURRENT, use mt blocksize 512 to set the blocksize. (The particular drive had firmware revision 21247 -005. Other firmware revisions may behave differently) Previous versions of FreeBSD did not have this @@ -5187,8 +5188,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Pedro A M Vazquez vazquez@IQM.Unicamp.BR - Mike Smith - msmith@atrad.adelaide.edu.au + &a.msmith; @@ -5219,7 +5219,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedThe boot message identifier for this drive is Conner tape. - This is a floppy controller, minicartridge tape drive. + This is a floppy controller, mini cartridge tape drive. Native capacity is XXXX @@ -5238,7 +5238,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed type 1 removable SCSI 2. - This is a minicartridge tape drive. + This is a mini cartridge tape drive. Native capacity is XXXX @@ -5283,12 +5283,12 @@ options "TUNE_1542" #dynamic tune of bus DMA speedThis is a mini-cartridge tape drive. Native capacity is 1GB when using MC3000XL - minicartridges. + mini cartridges. Data transfer rate is XXX This drive can read and write DC2300 (550MB), DC2750 (750MB), - MC3000 (750MB), and MC3000XL (1GB) minicartridges. + MC3000 (750MB), and MC3000XL (1GB) mini cartridges. WARNING: This drive does not meet the SCSI-2 specifications. The drive locks up completely in response to a SCSI MODE_SELECT @@ -5297,8 +5297,8 @@ options "TUNE_1542" #dynamic tune of bus DMA speed&prompt.root; mt -f /dev/st0ctl.0 blocksize 1024 - Before using a minicartridge for the first time, the - minicartridge must be formated. FreeBSD 2.1.0-RELEASE and + Before using a mini cartridge for the first time, the + mini cartridge must be formated. FreeBSD 2.1.0-RELEASE and earlier: &prompt.root; /sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0" @@ -5340,8 +5340,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedProduction of this drive has been discontinued. - Reported by: Mike Smith - msmith@atrad.adelaide.edu.au + Reported by: &a.msmith; @@ -5580,7 +5579,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Data transfer rate is 160kB/s. - Reported by: mark thompson + Reported by: Mark Thompson mark.a.thompson@pobox.com @@ -5674,10 +5673,10 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" In order to get this drive to stream, set the blocksize to 512 bytes (mt blocksize 512) reported by Kenneth - Merry ken@ulc199.residence.gatech.edu + Merry ken@ulc199.residence.gatech.edu. SONY SDT-5000 327M information reported by - Charles Henrich henrich@msu.edu + Charles Henrich henrich@msu.edu. Reported by: &a.jmz; @@ -5703,8 +5702,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" IBM and Emerald units will not work. Replacing the firmware EPROM of these units will solve the problem. - Reported by: Michael Smith - msmith@atrad.adelaide.edu.au + Reported by: &a.msmith; @@ -5747,7 +5745,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" This drives quirks are known and pre-compiled into the scsi tape device driver (&man.st.4;) beginning with FreeBSD - 2.2-current. For previous versions of FreeBSD, use + 2.2-CURRENT. For previous versions of FreeBSD, use mt to read one block from the tape, rewind the tape, and then execute the backup program (mt fsr 1; mt rewind; dump ...) @@ -5820,7 +5818,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" - CD-ROM drives + CDROM drives Contributed by &a.obrien;. 23 November 1997.