Use non-breaking spaces.
PR: docs/41546 Submitted by: Martin Heinen <martin@sumuk.de>
This commit is contained in:
Murray Stokely
parent
eae1c44ff0
commit
d548b181fa
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=14431
2 changed files with 35 additions and 35 deletions
|
|
@ -998,9 +998,9 @@
|
|||
<sect2>
|
||||
<title>Recognizing Your Crypt Mechanism</title>
|
||||
|
||||
<para>Before FreeBSD 4.4 <filename>libcrypt.a</filename> was a
|
||||
<para>Before FreeBSD 4.4 <filename>libcrypt.a</filename> was a
|
||||
symbolic link pointing to the library which was used for
|
||||
encryption. FreeBSD 4.4 changed <filename>libcrypt.a</filename> to
|
||||
encryption. FreeBSD 4.4 changed <filename>libcrypt.a</filename> 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</screen>
|
|||
any</literal>.</para>
|
||||
|
||||
<para>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.</para>
|
||||
|
||||
<para>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.</para>
|
||||
|
||||
<para>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</screen>
|
|||
</indexterm>
|
||||
<indexterm><primary>OpenSSL</primary></indexterm>
|
||||
|
||||
<para>As of FreeBSD 4.0, the OpenSSL toolkit is a part of the base
|
||||
<para>As of FreeBSD 4.0, the OpenSSL toolkit is a part of the base
|
||||
system. <ulink url="http://www.openssl.org/">OpenSSL</ulink>
|
||||
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</userinput></screen>
|
|||
<para>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.</para>
|
||||
in the base system since FreeBSD 4.0.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Advantages of Using OpenSSH</title>
|
||||
|
|
|
|||
|
|
@ -395,7 +395,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
|
|||
<sect3>
|
||||
<title>Making Device Special Files</title>
|
||||
|
||||
<note><para>FreeBSD 5.0 includes the <literal>devfs</literal>
|
||||
<note><para>FreeBSD 5.0 includes the <literal>devfs</literal>
|
||||
filesystem which automatically creates device nodes as
|
||||
needed. If you are running a version of FreeBSD with
|
||||
<literal>devfs</literal> enabled then you can safely skip
|
||||
|
|
@ -475,13 +475,13 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
<para>To prevent certain settings from being changed by an
|
||||
application, make adjustments to the <quote>lock state</quote>
|
||||
device. For example, to lock the speed of
|
||||
<devicename>ttyd5</devicename> to 57600 bps, type:</para>
|
||||
<devicename>ttyd5</devicename> to 57600 bps, type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
|
||||
|
||||
<para>Now, an application that opens
|
||||
<devicename>ttyd5</devicename> and tries to change the speed of
|
||||
the port will be stuck with 57600 bps.</para>
|
||||
the port will be stuck with 57600 bps.</para>
|
||||
|
||||
<indexterm>
|
||||
<primary><command>MAKEDEV</command></primary>
|
||||
|
|
@ -747,8 +747,8 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
match.</para>
|
||||
|
||||
<para>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.</para>
|
||||
connects at 38400 bps. The 286 PC uses no parity and
|
||||
connects at 19200 bps.</para>
|
||||
|
||||
</callout>
|
||||
|
||||
|
|
@ -1012,7 +1012,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
|
||||
<para>FreeBSD needs the <acronym>RTS</acronym> and
|
||||
<acronym>CTS</acronym> signals for flow-control at speeds above
|
||||
2400bps, the <acronym>CD</acronym> signal to detect when a call has
|
||||
2400 bps, the <acronym>CD</acronym> signal to detect when a call has
|
||||
been answered or the line has been hung up, and the
|
||||
<acronym>DTR</acronym> 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
|
|||
|
||||
<para>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
|
||||
<command>getty</command> does not understand any particular modem's
|
||||
connection speed reporting, <command>getty</command> gives a
|
||||
<prompt>login:</prompt> message at an initial speed and watches the
|
||||
|
|
@ -1155,7 +1155,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
<para>You will need to setup an entry in
|
||||
<filename>/etc/gettytab</filename> to give
|
||||
<command>getty</command> 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 <literal>D2400</literal> entry.</para>
|
||||
|
||||
<programlisting>#
|
||||
|
|
@ -1170,8 +1170,8 @@ D2400|d2400|Fast-Dial-2400:\
|
|||
|
||||
<para>If you have a higher speed modem, you will probably need to
|
||||
add an entry in <filename>/etc/gettytab</filename>; here is an
|
||||
entry you could use for a 14.4 Kbps modem with a top interface
|
||||
speed of 19.2 Kbps:</para>
|
||||
entry you could use for a 14.4 Kbps modem with a top interface
|
||||
speed of 19.2 Kbps:</para>
|
||||
|
||||
<programlisting>#
|
||||
# Additions for a V.32bis Modem
|
||||
|
|
@ -1189,19 +1189,19 @@ uq|V19200|High Speed Modem at 19200,8-bit:\
|
|||
|
||||
<para>This will result in 8-bit, no parity connections.</para>
|
||||
|
||||
<para>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.
|
||||
<para>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
|
||||
<literal>nx=</literal> (<quote>next table</quote>) capability.
|
||||
Each of the lines uses a <literal>tc=</literal> (<quote>table
|
||||
continuation</quote>) entry to pick up the rest of the
|
||||
<quote>standard</quote> settings for a particular data rate.</para>
|
||||
|
||||
<para>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 <filename>gettytab</filename> entry starting a 57.6 Kbps:</para>
|
||||
<para>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 <filename>gettytab</filename> entry starting a 57.6 Kbps:</para>
|
||||
|
||||
<programlisting>#
|
||||
# Additions for a V.32bis or V.34 Modem
|
||||
|
|
@ -1221,7 +1221,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
<para>If you have a slow CPU or a heavily loaded system and do
|
||||
not have 16550A-based serial ports, you may receive
|
||||
<errorname>sio</errorname>
|
||||
<quote>silo</quote> errors at 57.6 Kbps.</para>
|
||||
<quote>silo</quote> errors at 57.6 Kbps.</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -1284,7 +1284,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
<para>For a locked-speed configuration, your
|
||||
<filename>ttys</filename> entry needs to have a fixed-speed entry
|
||||
provided to <command>getty</command>. For a modem whose port
|
||||
speed is locked at 19.2 Kbps, the <filename>ttys</filename> entry
|
||||
speed is locked at 19.2 Kbps, the <filename>ttys</filename> entry
|
||||
might look like this:</para>
|
||||
|
||||
<programlisting>ttyd0 "/usr/libexec/getty std.19200" dialup on</programlisting>
|
||||
|
|
@ -1305,7 +1305,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
beginning <quote>auto-baud</quote> (sic) entry in
|
||||
<filename>/etc/gettytab</filename>. For example, if you added the
|
||||
above suggested entry for a matching-speed modem that starts at
|
||||
19.2 Kbps (the <filename>gettytab</filename> entry containing the
|
||||
19.2 Kbps (the <filename>gettytab</filename> entry containing the
|
||||
<literal>V19200</literal> starting point), your
|
||||
<filename>ttys</filename> entry might look like this:</para>
|
||||
|
||||
|
|
@ -1717,8 +1717,8 @@ tip57600|Dial any phone number at 57600 bps:\
|
|||
<para>Put in an entry for <literal>tip1200</literal> or
|
||||
<literal>cu1200</literal>, but go ahead and use whatever bps rate is
|
||||
appropriate with the br capability. <command>tip</command> thinks a
|
||||
good default is 1200 bps which is why it looks for a
|
||||
<literal>tip1200</literal> entry. You do not have to use 1200 bps,
|
||||
good default is 1200 bps which is why it looks for a
|
||||
<literal>tip1200</literal> entry. You do not have to use 1200 bps,
|
||||
though.</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -1979,7 +1979,7 @@ raisechar=^^</programlisting>
|
|||
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.</para>
|
||||
</note>
|
||||
|
|
@ -2058,7 +2058,7 @@ raisechar=^^</programlisting>
|
|||
remote debugging.</para>
|
||||
|
||||
<note>
|
||||
<para>In FreeBSD 4.0 or later the semantics of the
|
||||
<para>In FreeBSD 4.0 or later the semantics of the
|
||||
flag <literal>0x40</literal> are slightly different and
|
||||
there is another flag to specify a serial port for remote
|
||||
debugging.</para>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue