From d548b181fa84b0903a7e623fcbb7dfc28570e0d9 Mon Sep 17 00:00:00 2001 From: Murray Stokely Date: Mon, 30 Sep 2002 15:34:24 +0000 Subject: [PATCH] Use non-breaking spaces. PR: docs/41546 Submitted by: Martin Heinen --- .../books/handbook/security/chapter.sgml | 18 +++---- .../books/handbook/serialcomms/chapter.sgml | 52 +++++++++---------- 2 files changed, 35 insertions(+), 35 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.sgml b/en_US.ISO8859-1/books/handbook/security/chapter.sgml index f13ba66626..026acfe72a 100644 --- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml @@ -998,9 +998,9 @@ Recognizing Your Crypt Mechanism - Before FreeBSD 4.4 libcrypt.a was a + Before FreeBSD 4.4 libcrypt.a was a symbolic link pointing to the library which was used for - encryption. FreeBSD 4.4 changed libcrypt.a to + encryption. FreeBSD 4.4 changed libcrypt.a to provide a configurable password authentication hash library. Currently the library supports DES, MD5 and Blowfish hash functions. By default FreeBSD uses MD5 to encrypt @@ -2682,16 +2682,16 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 any. The per-packet processing overhead in the former case was - approximately 2.703ms/packet, or roughly 2.7 microseconds per + approximately 2.703 ms/packet, or roughly 2.7 microseconds per rule. Thus the theoretical packet processing limit with these - rules is around 370 packets per second. Assuming 10Mbps - Ethernet and a ~1500 byte packet size, we would only be able + rules is around 370 packets per second. Assuming 10 Mbps + Ethernet and a ~1500 byte packet size, we would only be able to achieve a 55.5% bandwidth utilization. For the latter case each packet was processed in - approximately 1.172ms, or roughly 1.2 microseconds per rule. + approximately 1.172 ms, or roughly 1.2 microseconds per rule. The theoretical packet processing limit here would be about - 853 packets per second, which could consume 10Mbps Ethernet + 853 packets per second, which could consume 10 Mbps Ethernet bandwidth. The excessive number of rules tested and the nature of @@ -2728,7 +2728,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 OpenSSL - As of FreeBSD 4.0, the OpenSSL toolkit is a part of the base + As of FreeBSD 4.0, the OpenSSL toolkit is a part of the base system. OpenSSL provides a general-purpose cryptography library, as well as the Secure Sockets Layer v2/v3 (SSLv2/SSLv3) and Transport Layer @@ -3132,7 +3132,7 @@ EOF OpenSSH is maintained by the OpenBSD project, and is based upon SSH v1.2.12 with all the recent bug fixes and updates. It is compatible with both SSH protocols 1 and 2. OpenSSH has been - in the base system since FreeBSD 4.0. + in the base system since FreeBSD 4.0. Advantages of Using OpenSSH diff --git a/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml b/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml index 670e2bc290..d1f7e147e7 100644 --- a/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml @@ -395,7 +395,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr Making Device Special Files - FreeBSD 5.0 includes the devfs + FreeBSD 5.0 includes the devfs filesystem which automatically creates device nodes as needed. If you are running a version of FreeBSD with devfs enabled then you can safely skip @@ -475,13 +475,13 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1 To prevent certain settings from being changed by an application, make adjustments to the lock state device. For example, to lock the speed of - ttyd5 to 57600 bps, type: + ttyd5 to 57600 bps, type: &prompt.root; stty -f /dev/ttyld5 57600 Now, an application that opens ttyd5 and tries to change the speed of - the port will be stuck with 57600 bps. + the port will be stuck with 57600 bps. MAKEDEV @@ -747,8 +747,8 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure match. For our example, the Wyse-50 uses no parity and - connects at 38400 bps. The 286 PC uses no parity and - connects at 19200 bps. + connects at 38400 bps. The 286 PC uses no parity and + connects at 19200 bps. @@ -1012,7 +1012,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure FreeBSD needs the RTS and CTS signals for flow-control at speeds above - 2400bps, the CD signal to detect when a call has + 2400 bps, the CD signal to detect when a call has been answered or the line has been hung up, and the DTR signal to reset the modem after a session is complete. Some cables are wired without all of the needed signals, @@ -1107,9 +1107,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure The other school configures their modems' RS-232 interface to vary its speed based on the remote user's connection speed. For example, - V.32bis (14.4 Kbps) connections to the modem might make the modem run - its RS-232 interface at 19.2 Kbps, while 2400 bps connections make the - modem's RS-232 interface run at 2400 bps. Because + V.32bis (14.4 Kbps) connections to the modem might make the modem run + its RS-232 interface at 19.2 Kbps, while 2400 bps connections make the + modem's RS-232 interface run at 2400 bps. Because getty does not understand any particular modem's connection speed reporting, getty gives a login: message at an initial speed and watches the @@ -1155,7 +1155,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure You will need to setup an entry in /etc/gettytab to give getty information about the speeds you wish to - use for your modem. If you have a 2400 bps modem, you can + use for your modem. If you have a 2400 bps modem, you can probably use the existing D2400 entry. # @@ -1170,8 +1170,8 @@ D2400|d2400|Fast-Dial-2400:\ If you have a higher speed modem, you will probably need to add an entry in /etc/gettytab; here is an - entry you could use for a 14.4 Kbps modem with a top interface - speed of 19.2 Kbps: + entry you could use for a 14.4 Kbps modem with a top interface + speed of 19.2 Kbps: # # Additions for a V.32bis Modem @@ -1189,19 +1189,19 @@ uq|V19200|High Speed Modem at 19200,8-bit:\ This will result in 8-bit, no parity connections. - The example above starts the communications rate at 19.2 Kbps - (for a V.32bis connection), then cycles through 9600 bps (for - V.32), 2400 bps, 1200 bps, 300 bps, and back to 19.2 Kbps. + The example above starts the communications rate at 19.2 Kbps + (for a V.32bis connection), then cycles through 9600 bps (for + V.32), 2400 bps, 1200 bps, 300 bps, and back to 19.2 Kbps. Communications rate cycling is implemented with the nx= (next table) capability. Each of the lines uses a tc= (table continuation) entry to pick up the rest of the standard settings for a particular data rate. - If you have a 28.8 Kbps modem and/or you want to take - advantage of compression on a 14.4 Kbps modem, you need to use a - higher communications rate than 19.2 Kbps. Here is an example of - a gettytab entry starting a 57.6 Kbps: + If you have a 28.8 Kbps modem and/or you want to take + advantage of compression on a 14.4 Kbps modem, you need to use a + higher communications rate than 19.2 Kbps. Here is an example of + a gettytab entry starting a 57.6 Kbps: # # Additions for a V.32bis or V.34 Modem @@ -1221,7 +1221,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ If you have a slow CPU or a heavily loaded system and do not have 16550A-based serial ports, you may receive sio - silo errors at 57.6 Kbps. + silo errors at 57.6 Kbps. @@ -1284,7 +1284,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ For a locked-speed configuration, your ttys entry needs to have a fixed-speed entry provided to getty. For a modem whose port - speed is locked at 19.2 Kbps, the ttys entry + speed is locked at 19.2 Kbps, the ttys entry might look like this: ttyd0 "/usr/libexec/getty std.19200" dialup on @@ -1305,7 +1305,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ beginning auto-baud (sic) entry in /etc/gettytab. For example, if you added the above suggested entry for a matching-speed modem that starts at - 19.2 Kbps (the gettytab entry containing the + 19.2 Kbps (the gettytab entry containing the V19200 starting point), your ttys entry might look like this: @@ -1717,8 +1717,8 @@ tip57600|Dial any phone number at 57600 bps:\ Put in an entry for tip1200 or cu1200, but go ahead and use whatever bps rate is appropriate with the br capability. tip thinks a - good default is 1200 bps which is why it looks for a - tip1200 entry. You do not have to use 1200 bps, + good default is 1200 bps which is why it looks for a + tip1200 entry. You do not have to use 1200 bps, though. @@ -1979,7 +1979,7 @@ raisechar=^^ This is because PS/2 mice share some hardware with the keyboard and leaving the mouse plugged in can fool the keyboard probe into thinking the keyboard is still there. It is said that a - Gateway 2000 Pentium 90MHz system with an AMI BIOS that behaves + Gateway 2000 Pentium 90 MHz system with an AMI BIOS that behaves this way. In general, this is not a problem since the mouse is not much good without the keyboard anyway. @@ -2058,7 +2058,7 @@ raisechar=^^ remote debugging. - In FreeBSD 4.0 or later the semantics of the + In FreeBSD 4.0 or later the semantics of the flag 0x40 are slightly different and there is another flag to specify a serial port for remote debugging.