From da6ef2fb7c74e017ea505ba62cb6ebdc4d94d322 Mon Sep 17 00:00:00 2001 From: Murray Stokely Date: Mon, 30 Sep 2002 15:42:53 +0000 Subject: [PATCH] Use non-breaking spaces. PR: docs/41546 Submitted by: Martin Heinen --- .../handbook/advanced-networking/chapter.sgml | 26 ++++++------ .../books/handbook/linuxemu/chapter.sgml | 42 +++++++++---------- .../books/handbook/ports/chapter.sgml | 2 +- .../books/handbook/printing/chapter.sgml | 2 +- 4 files changed, 36 insertions(+), 36 deletions(-) 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 d2020bf052..54f0b71931 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -560,7 +560,7 @@ host2.example.com link#1 UC 0 0 Network Interface Card Selection A bridge requires at least two network cards to function. - Unfortunately, not all network interface cards as of FreeBSD 4.0 + Unfortunately, not all network interface cards as of FreeBSD 4.0 support bridging. Read &man.bridge.4; for details on the cards that are supported. @@ -635,11 +635,11 @@ host2.example.com link#1 UC 0 0 Performance My bridge/firewall is a Pentium 90 with one 3Com 3C900B and one - 3C905B. The protected side of the network runs at 10mbps half duplex + 3C905B. The protected side of the network runs at 10 mbps half duplex and the connection between the bridge and my router (a Cisco 675) runs - at 100mbps full duplex. With no filtering enabled, I have found that - the bridge adds about 0.4 milliseconds of latency to pings from the - protected 10mbps network to the Cisco 675. + at 100 mbps full duplex. With no filtering enabled, I have found that + the bridge adds about 0.4 milliseconds of latency to pings from the + protected 10 mbps network to the Cisco 675. @@ -1143,9 +1143,9 @@ Exports list on foobar: For anyone who cares, here is what happens when the failure occurs, which also explains why it is unrecoverable. NFS - typically works with a block size of 8k (though it + typically works with a block size of 8 k (though it may do fragments of smaller sizes). Since the maximum Ethernet - packet is around 1500 bytes, the NFS block gets + packet is around 1500 bytes, the NFS block gets split into multiple Ethernet packets, even though it is still a single unit to the upper-level code, and must be received, assembled, and acknowledged as a unit. The @@ -1156,7 +1156,7 @@ Exports list on foobar: unit before they can be transferred to the host and the unit as a whole cannot be reconstructed or acknowledged. As a result, the workstation will time out and try again, but it will try again - with the entire 8K unit, and the process will be repeated, ad + with the entire 8 K unit, and the process will be repeated, ad infinitum. By keeping the unit size below the Ethernet packet size @@ -1710,7 +1710,7 @@ Exports list on foobar: FreeBSD's ISDN implementation supports only the DSS1/Q.931 (or Euro-ISDN) standard using passive cards. Starting with - FreeBSD 4.4, some active cards are supported where the firmware + FreeBSD 4.4, some active cards are supported where the firmware also supports other signaling protocols; this also includes the first supported Primary Rate (PRI) ISDN card. @@ -1819,8 +1819,8 @@ Exports list on foobar: synchronous serial ports. A TA running off a standard PC serial port (asynchronous) limits - you to 115.2Kbs, even though you have a 128Kbs connection. To fully - utilize the 128Kbs that ISDN is capable of, you must move the TA to a + you to 115.2 Kbs, even though you have a 128 Kbs connection. To fully + utilize the 128 Kbs that ISDN is capable of, you must move the TA to a synchronous serial card. Do not be fooled into buying an internal TA and thinking you have @@ -1960,7 +1960,7 @@ ISDN BRI line dedicated ISDN connection at your office and would like to tap into it, but do not want to get another ISDN line at work. A router at the office location can manage a dedicated B channel connection - (64Kbps) to the Internet and use the other B channel for a + (64 Kbps) to the Internet and use the other B channel for a separate data connection. The second B channel can be used for dial-in, dial-out or dynamically bonding (MPP, etc.) with the first B channel for more bandwidth. @@ -2180,7 +2180,7 @@ ISDN BRI line This section will deal with setting up a sample NIS environment. - This section assumes that you are running FreeBSD 3.3 + This section assumes that you are running FreeBSD 3.3 or later. The instructions given here will probably work for any version of FreeBSD greater than 3.0, but there are no guarantees that this is diff --git a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml index bd7a9fc329..8bf94b4038 100644 --- a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml @@ -698,7 +698,7 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \ Make sure you have both linux_base and linux_devtools from the ports collection installed. These ports are added to the collection after the release - of FreeBSD 3.2. If you are using FreeBSD 3.2 or an older version for + of FreeBSD 3.2. If you are using FreeBSD 3.2 or an older version for that matter, update your ports collection. You may want to consider updating your FreeBSD version too. If you run into difficulties with linux_base-6.1 or @@ -1280,7 +1280,7 @@ export PATH high-speed disk access (SCSI, RAID hardware controller), USV and ECC-RAM is recommended. The large amount of hard disk space is due to the preconfigured IDES System, which creates - 27 GB of database files during installation. This space is + 27 GB of database files during installation. This space is also sufficient for initial production systems and application data. @@ -1288,21 +1288,21 @@ export PATH SAP R/3 4.6B, Oracle 8.0.5 The following off-the-shelf hardware was used: a dual processor - board with 2 800MHz Pentium III processors, Adaptec 29160 Ultra160 - SCSI adapter (for accessing a 40/80 GB DLT tape drive and CDROM), - Mylex AcceleRAID (2 channels, firmware 6.00-1-00 with 32MB RAM). - To the Mylex Raid-controller are attached two 17GB hard disks - (mirrored) and four 36GB hard disks (RAID level 5). + board with 2 800 MHz Pentium III processors, Adaptec 29160 Ultra160 + SCSI adapter (for accessing a 40/80 GB DLT tape drive and CDROM), + Mylex AcceleRAID (2 channels, firmware 6.00-1-00 with 32 MB RAM). + To the Mylex Raid-controller are attached two 17 GB hard disks + (mirrored) and four 36 GB hard disks (RAID level 5). SAP R/3 4.6C, Oracle 8.1.7 For this installation a DELL PowerEdge 2500 was used: a - dual processor board with two 1000MHz Pentium III processors - (256kB Cache), 2GB PC133 ECC SDRAM, PERC/3 DC PCI Raid Controller - with 128MB, and an EIDE DVD-ROM drive. To the RAID-controller are - attached two 18GB hard disks (mirrored) and four 36GB hard disks + dual processor board with two 1000 MHz Pentium III processors + (256 kB Cache), 2 GB PC133 ECC SDRAM, PERC/3 DC PCI Raid Controller + with 128 MB, and an EIDE DVD-ROM drive. To the RAID-controller are + attached two 18 GB hard disks (mirrored) and four 36 GB hard disks (RAID level 5). @@ -1311,7 +1311,7 @@ export PATH Installation of FreeBSD First you have to install FreeBSD. There are several ways to do - this (FreeBSD 4.3 was installed via FTP, FreeBSD 4.5 directly from + this (FreeBSD 4.3 was installed via FTP, FreeBSD 4.5 directly from release-CD). @@ -1821,8 +1821,8 @@ options SEMUME=100 #number of UNDO keys and Oracle, therefore choose a larger number of shared memory pages. - With the default installation of FreeBSD 4.5 on x386, - leave MAXDSIZ and DFLDSIZ at 1GB maximum. Otherwise, strange + With the default installation of FreeBSD 4.5 on x386, + leave MAXDSIZ and DFLDSIZ at 1 GB maximum. Otherwise, strange errors like ORA-27102: out of memory and Linux Error: 12: Cannot allocate memory might happen. @@ -2541,9 +2541,9 @@ tape_address_rew = /dev/sa0 bad. cpio_flags Default is to use -B which - sets blocksize to 5120 Bytes. For DLT-Tapes, HP recommends at - least 32K blocksize, so I used --block-size=128 for - 64K. --format=newc is needed I have inode numbers greater than + sets blocksize to 5120 Bytes. For DLT-Tapes, HP recommends at + least 32 K blocksize, so I used --block-size=128 for + 64 K. --format=newc is needed I have inode numbers greater than 65535. The last option --quiet is needed as otherwise brbackup complains as soon as cpio outputs the @@ -2569,7 +2569,7 @@ tape_address_rew = /dev/sa0 Configuration Issues after Installation The following SAP-parameters should be tuned after - installation (examples for IDES 46B, 1GB memory): + installation (examples for IDES 46B, 1 GB memory): @@ -2649,7 +2649,7 @@ tape_address_rew = /dev/sa0 - With the above parameters, on a system with 1 gigabyte + With the above parameters, on a system with 1 gigabyte of memory, one may find memory consumption similar to: Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free @@ -2786,7 +2786,7 @@ rscp/TCP0B = TCP0B ORA-00001 This error only happened with - Oracle 8.1.7 on FreeBSD 4.5. + Oracle 8.1.7 on FreeBSD 4.5. The reason was that the Oracle database could not initialize itself properly and crashed, leaving semaphores and shared memory on the system. The next try to start the database then returned @@ -2832,7 +2832,7 @@ SVRMGR> exit This error happend whilst trying to use values for MAXDSIZ and DFLDSIZ - greater than 1GB (1024x1024x1024). Additionally, I got + greater than 1 GB (1024x1024x1024). Additionally, I got Linux Error 12: Cannot allocate memory. diff --git a/en_US.ISO8859-1/books/handbook/ports/chapter.sgml b/en_US.ISO8859-1/books/handbook/ports/chapter.sgml index b1865d772d..49fa7de695 100644 --- a/en_US.ISO8859-1/books/handbook/ports/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/ports/chapter.sgml @@ -1270,7 +1270,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch Yes, with version 2.6.3 of gcc (the - version shipped with FreeBSD 2.1.0 and 2.1.5), the + version shipped with FreeBSD 2.1.0 and 2.1.5), the option could result in buggy code unless you used the option as well. (Most of the ports do not use diff --git a/en_US.ISO8859-1/books/handbook/printing/chapter.sgml b/en_US.ISO8859-1/books/handbook/printing/chapter.sgml index a0e628a9b5..e4324407d0 100644 --- a/en_US.ISO8859-1/books/handbook/printing/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/printing/chapter.sgml @@ -794,7 +794,7 @@ showpage zero). Here is a sample entry for a printer connected via - a serial line to the third serial port at 19200 bps with + a serial line to the third serial port at 19200 bps with no parity: printer:dv=/dev/ttyd2:br#19200:pa=none