os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Use non-breaking spaces.

Browse source 
PR:		docs/41546
Submitted by:	Martin Heinen <martin@sumuk.de>
This commit is contained in:
Murray Stokely 2002-09-30 15:42:53 +00:00
parent d548b181fa
commit da6ef2fb7c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=14433
4 changed files with 36 additions and 36 deletions
Download patch file Download diff file Expand all files Collapse all files

26
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -560,7 +560,7 @@ host2.example.com link#1 UC 0 0
<title>Network Interface Card Selection</title>
<para>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&nbsp;4.0
support bridging. Read &man.bridge.4; for details on the cards that
are supported.</para>
@ -635,11 +635,11 @@ host2.example.com link#1 UC 0 0
<title>Performance</title>
<para>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&nbsp;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.</para>
at 100&nbsp;mbps full duplex. With no filtering enabled, I have found that
the bridge adds about 0.4&nbsp;milliseconds of latency to pings from the
protected 10&nbsp;mbps network to the Cisco 675.</para>
</sect2>
<sect2>
@ -1143,9 +1143,9 @@ Exports list on foobar:
<para>For anyone who cares, here is what happens when the failure
occurs, which also explains why it is unrecoverable. NFS
typically works with a <quote>block</quote> size of 8k (though it
typically works with a <quote>block</quote> size of 8&nbsp;k (though it
may do fragments of smaller sizes). Since the maximum Ethernet
packet is around 1500 bytes, the NFS <quote>block</quote> gets
packet is around 1500&nbsp;bytes, the NFS <quote>block</quote> 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 <emphasis>acknowledged</emphasis> 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&nbsp;K unit, and the process will be repeated, ad
infinitum.</para>
<para>By keeping the unit size below the Ethernet packet size
@ -1710,7 +1710,7 @@ Exports list on foobar:
<para>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&nbsp;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.</para>
@ -1819,8 +1819,8 @@ Exports list on foobar:
synchronous serial ports.</para>
<para>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&nbsp;Kbs, even though you have a 128&nbsp;Kbs connection. To fully
utilize the 128&nbsp;Kbs that ISDN is capable of, you must move the TA to a
synchronous serial card.</para>
<para>Do not be fooled into buying an internal TA and thinking you have
@ -1960,7 +1960,7 @@ ISDN BRI line</literallayout>
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&nbsp;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.</para>
@ -2180,7 +2180,7 @@ ISDN BRI line</literallayout>
<para>This section will deal with setting up a sample NIS
environment.</para>
<note><para>This section assumes that you are running FreeBSD 3.3
<note><para>This section assumes that you are running FreeBSD&nbsp;3.3
or later. The instructions given here will
<emphasis>probably</emphasis> work for any version of FreeBSD greater
than 3.0, but there are no guarantees that this is

42
en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -698,7 +698,7 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \
<para>Make sure you have both <filename>linux_base</filename> and
<filename>linux_devtools</filename> 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&nbsp;3.2. If you are using FreeBSD&nbsp;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
<filename>linux_base-6.1</filename> or
@ -1280,7 +1280,7 @@ export PATH</programlisting>
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&nbsp;GB of database files during installation. This space is
also sufficient for initial production systems and application
data.</para>
@ -1288,21 +1288,21 @@ export PATH</programlisting>
<title>SAP R/3 4.6B, Oracle 8.0.5</title>
<para>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).</para>
board with 2 800&nbsp;MHz Pentium&nbsp;III processors, Adaptec 29160 Ultra160
SCSI adapter (for accessing a 40/80&nbsp;GB DLT tape drive and CDROM),
Mylex AcceleRAID (2 channels, firmware 6.00-1-00 with 32&nbsp;MB RAM).
To the Mylex Raid-controller are attached two 17&nbsp;GB hard disks
(mirrored) and four 36&nbsp;GB hard disks (RAID level 5).</para>
</sect3>
<sect3 id="hardware-46c">
<title>SAP R/3 4.6C, Oracle 8.1.7</title>
<para>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&nbsp;MHz Pentium&nbsp;III processors
(256&nbsp;kB Cache), 2&nbsp;GB PC133 ECC SDRAM, PERC/3 DC PCI Raid Controller
with 128&nbsp;MB, and an EIDE DVD-ROM drive. To the RAID-controller are
attached two 18&nbsp;GB hard disks (mirrored) and four 36&nbsp;GB hard disks
(RAID level 5).</para>
</sect3>
</sect2>
@ -1311,7 +1311,7 @@ export PATH</programlisting>
<title>Installation of FreeBSD</title>
<para>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&nbsp;4.3 was installed via FTP, FreeBSD&nbsp;4.5 directly from
release-CD).</para>
<sect3 id="disk-layout">
@ -1821,8 +1821,8 @@ options SEMUME=100 #number of UNDO keys</programlisting>
and <application>Oracle</application>, therefore choose a larger
number of shared memory pages.</para>
<note><para>With the default installation of FreeBSD 4.5 on x386,
leave MAXDSIZ and DFLDSIZ at 1GB maximum. Otherwise, strange
<note><para>With the default installation of FreeBSD&nbsp;4.5 on x386,
leave MAXDSIZ and DFLDSIZ at 1&nbsp;GB maximum. Otherwise, strange
errors like <emphasis>ORA-27102: out of memory</emphasis> and
<emphasis>Linux Error: 12: Cannot allocate memory</emphasis>
might happen.</para></note>
@ -2541,9 +2541,9 @@ tape_address_rew = /dev/sa0</programlisting>
bad.</para>
<para><emphasis>cpio_flags</emphasis> 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&nbsp;Bytes. For DLT-Tapes, HP recommends at
least 32&nbsp;K blocksize, so I used --block-size=128 for
64&nbsp;K. --format=newc is needed I have inode numbers greater than
65535. The last option --quiet is needed as otherwise
<command>brbackup</command>
complains as soon as <command>cpio</command> outputs the
@ -2569,7 +2569,7 @@ tape_address_rew = /dev/sa0</programlisting>
<title>Configuration Issues after Installation</title>
<para>The following SAP-parameters should be tuned after
installation (examples for IDES 46B, 1GB memory):</para>
installation (examples for IDES 46B, 1&nbsp;GB memory):</para>
<informaltable frame="none">
<tgroup cols="2">
@ -2649,7 +2649,7 @@ tape_address_rew = /dev/sa0</programlisting>
</informaltable>
<note>
<para>With the above parameters, on a system with 1 gigabyte
<para>With the above parameters, on a system with 1&nbsp;gigabyte
of memory, one may find memory consumption similar to:
<programlisting>Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free</programlisting></para>
@ -2786,7 +2786,7 @@ rscp/TCP0B = TCP0B</programlisting>
<sect3 id="ora-00001">
<title>ORA-00001</title>
<para>This error only happened with
<application>Oracle 8.1.7</application> on FreeBSD 4.5.
<application>Oracle 8.1.7</application> on FreeBSD&nbsp;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&gt; <userinput>exit</userinput></screen>
<para>This error happend whilst trying to use values for
<emphasis>MAXDSIZ</emphasis> and <emphasis>DFLDSIZ</emphasis>
greater than 1GB (1024x1024x1024). Additionally, I got
greater than 1&nbsp;GB (1024x1024x1024). Additionally, I got
<emphasis>Linux Error 12: Cannot allocate memory</emphasis>.</para>
</sect3>

2
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -1270,7 +1270,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
<answer>
<para>Yes, with version 2.6.3 of <command>gcc</command> (the
version shipped with FreeBSD 2.1.0 and 2.1.5), the
version shipped with FreeBSD&nbsp;2.1.0 and 2.1.5), the
<option>-O2</option> option could result in buggy code
unless you used the <option>-fno-strength-reduce</option>
option as well. (Most of the ports do not use

2
en_US.ISO8859-1/books/handbook/printing/chapter.sgml
View file

@ -794,7 +794,7 @@ showpage</programlisting>
<literal>zero</literal>).</para>
<para>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&nbsp;bps with
no parity:</para>
<programlisting>printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>