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

Use non-breaking spaces, as appropriate.

Browse source 
PR:		docs/41546
Submitted by:	Martin Heinen <martin@sumuk.de>
This commit is contained in:
Murray Stokely 2002-09-30 15:30:33 +00:00
parent d326dd031e
commit 48286777db
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=14428
2 changed files with 28 additions and 28 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -139,7 +139,7 @@
installed from the &man.ports.7; hierarchy. If you do not installed from the &man.ports.7; hierarchy. If you do not
use ports all that much and do not intend to keep system use ports all that much and do not intend to keep system
source (<filename>/usr/src</filename>) on the machine, you source (<filename>/usr/src</filename>) on the machine, you
can get away with a 1 gigabyte <filename>/usr</filename> can get away with a 1&nbsp;gigabyte <filename>/usr</filename>
partition. However, if you install a lot of ports partition. However, if you install a lot of ports
(especially window managers and Linux binaries), we (especially window managers and Linux binaries), we
recommend at least a two gigabyte <filename>/usr</filename> recommend at least a two gigabyte <filename>/usr</filename>
@ -169,10 +169,10 @@
<para>As a rule of thumb, your swap space should typically be <para>As a rule of thumb, your swap space should typically be
double the amount of main memory. For example, if the machine double the amount of main memory. For example, if the machine
has 128 megabytes of memory, the swap file should be 256 has 128&nbsp;megabytes of memory, the swap file should be
megabytes. Systems with lesser memory may perform better with 256&nbsp;megabytes. Systems with lesser memory may perform better with
a lot more swap. It is not recommended that you configure any a lot more swap. It is not recommended that you configure any
less than 256 megabytes of swap on a system and you should less than 256&nbsp;megabytes of swap on a system and you should
keep in mind future memory expansion when sizing the swap keep in mind future memory expansion when sizing the swap
partition. The kernel's VM paging algorithms are tuned to partition. The kernel's VM paging algorithms are tuned to
perform best when the swap partition is at least two times the perform best when the swap partition is at least two times the
@ -403,7 +403,7 @@ exit 0
<para>Some additional system services may not be covered by the <para>Some additional system services may not be covered by the
toggles in <filename>/etc/rc.conf</filename>. These are toggles in <filename>/etc/rc.conf</filename>. These are
traditionally enabled by placing the command(s) to invoke them traditionally enabled by placing the command(s) to invoke them
in <filename>/etc/rc.local</filename>. As of FreeBSD 3.1 there in <filename>/etc/rc.local</filename>. As of FreeBSD&nbsp;3.1 there
is no default <filename>/etc/rc.local</filename>; if it is is no default <filename>/etc/rc.local</filename>; if it is
created by the administrator it will however be honored in the created by the administrator it will however be honored in the
normal fashion. Note that <filename>rc.local</filename> is normal fashion. Note that <filename>rc.local</filename> is
@ -830,8 +830,8 @@ kern.maxfiles: 2088 -> 5000</screen>
<para>The <varname>vfs.vmiodirenable</varname> sysctl variable <para>The <varname>vfs.vmiodirenable</varname> sysctl variable
may be set to either 0 (off) or 1 (on); it is 1 by default. This variable controls how may be set to either 0 (off) or 1 (on); it is 1 by default. This variable controls how
directories are cached by the system. Most directories are directories are cached by the system. Most directories are
small, using just a single fragment (typically 1K) in the small, using just a single fragment (typically 1&nbsp;K) in the
filesystem and less (typically 512 bytes) in the buffer filesystem and less (typically 512&nbsp;bytes) in the buffer
cache. However, when operating in the default mode the buffer cache. However, when operating in the default mode the buffer
cache will only cache a fixed number of directories even if cache will only cache a fixed number of directories even if
you have a huge amount of memory. Turning on this sysctl you have a huge amount of memory. Turning on this sysctl
@ -839,7 +839,7 @@ kern.maxfiles: 2088 -> 5000</screen>
directories, making all the memory available for caching directories, making all the memory available for caching
directories. However, directories. However,
the minimum in-core memory used to cache a directory is the the minimum in-core memory used to cache a directory is the
physical page size (typically 4K) rather than 512 bytes. We physical page size (typically 4&nbsp;K) rather than 512&nbsp;bytes. We
recommend turning this option on if you are running any recommend turning this option on if you are running any
services which manipulate large numbers of files. Such services which manipulate large numbers of files. Such
services can include web caches, large mail systems, and news services can include web caches, large mail systems, and news
@ -855,7 +855,7 @@ kern.maxfiles: 2088 -> 5000</screen>
<primary><varname>hw.ata.wc</varname></primary> <primary><varname>hw.ata.wc</varname></primary>
</indexterm> </indexterm>
<para>FreeBSD 4.3 flirted with turning off IDE write caching. <para>FreeBSD&nbsp;4.3 flirted with turning off IDE write caching.
This reduced write bandwidth to IDE disks but was considered This reduced write bandwidth to IDE disks but was considered
necessary due to serious data consistency issues introduced necessary due to serious data consistency issues introduced
by hard drive vendors. The problem is that IDE by hard drive vendors. The problem is that IDE
@ -896,7 +896,7 @@ kern.maxfiles: 2088 -> 5000</screen>
it is mounted. A good time to enable Soft Updates is before any it is mounted. A good time to enable Soft Updates is before any
partitions have been mounted, in single-user mode.</para> partitions have been mounted, in single-user mode.</para>
<note><para>As of FreeBSD 4.5, it is possible to enable Soft Updates <note><para>As of FreeBSD&nbsp;4.5, it is possible to enable Soft Updates
at filesystem creation time, through use of the <literal>-U</literal> at filesystem creation time, through use of the <literal>-U</literal>
option to &man.newfs.8;.</para></note> option to &man.newfs.8;.</para></note>
@ -1099,7 +1099,7 @@ kern.maxfiles: 2088 -> 5000</screen>
connected as once, the resources needed may be similar to a connected as once, the resources needed may be similar to a
high-scale web server.</para> high-scale web server.</para>
<note><para>As of FreeBSD 4.5, setting <option>MAXUSERS</option> to <note><para>As of FreeBSD&nbsp;4.5, setting <option>MAXUSERS</option> to
<literal>0</literal> in your kernel configuration file will choose <literal>0</literal> in your kernel configuration file will choose
a reasonable default value based on the amount of RAM present in a reasonable default value based on the amount of RAM present in
your system.</para></note> your system.</para></note>
@ -1113,14 +1113,14 @@ kern.maxfiles: 2088 -> 5000</screen>
option dictates the amount of network mbufs available to the option dictates the amount of network mbufs available to the
system. A heavily-trafficked server with a low number of MBUFs system. A heavily-trafficked server with a low number of MBUFs
will hinder FreeBSD's ability. Each cluster represents will hinder FreeBSD's ability. Each cluster represents
approximately 2K of memory, so a value of 1024 represents 2 approximately 2&nbsp;K of memory, so a value of 1024 represents 2
megabytes of kernel memory reserved for network buffers. A megabytes of kernel memory reserved for network buffers. A
simple calculation can be done to figure out how many are simple calculation can be done to figure out how many are
needed. If you have a web server which maxes out at 1000 needed. If you have a web server which maxes out at 1000
simultaneous connections, and each connection eats a 16K receive simultaneous connections, and each connection eats a 16&nbsp;K receive
and 16K send buffer, you need approximately 32MB worth of and 16&nbsp;K send buffer, you need approximately 32&nbsp;MB worth of
network buffers to cover the web server. A good rule of thumb is network buffers to cover the web server. A good rule of thumb is
to multiply by 2, so 2x32 MB / 2 KB = 64 MB / 2 kB = 32768.</para> to multiply by 2, so 2x32&nbsp;MB&nbsp;/&nbsp;2&nbsp;KB&nbsp;= 64&nbsp;MB&nbsp;/&nbsp;2&nbsp;kB&nbsp;= 32768.</para>
</sect2> </sect2>
</sect1> </sect1>

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

@ -510,7 +510,7 @@
<indexterm><primary>386BSD</primary></indexterm> <indexterm><primary>386BSD</primary></indexterm>
<indexterm><primary>Free Software Foundation</primary></indexterm> <indexterm><primary>Free Software Foundation</primary></indexterm>
<para>The first CDROM (and general net-wide) distribution was <para>The first CDROM (and general net-wide) distribution was
FreeBSD 1.0, released in December of 1993. This was based on the FreeBSD&nbsp;1.0, released in December of 1993. This was based on the
4.3BSD-Lite (<quote>Net/2</quote>) tape from U.C. Berkeley, with 4.3BSD-Lite (<quote>Net/2</quote>) tape from U.C. Berkeley, with
many components also provided by 386BSD and the Free Software many components also provided by 386BSD and the Free Software
Foundation. It was a fairly reasonable success for a first Foundation. It was a fairly reasonable success for a first
@ -534,7 +534,7 @@
included FreeBSD, and the project was given until the end of July included FreeBSD, and the project was given until the end of July
1994 to stop shipping its own Net/2 based product. Under the 1994 to stop shipping its own Net/2 based product. Under the
terms of that agreement, the project was allowed one last release terms of that agreement, the project was allowed one last release
before the deadline, that release being FreeBSD 1.1.5.1.</para> before the deadline, that release being FreeBSD&nbsp;1.1.5.1.</para>
<para>FreeBSD then set about the arduous task of literally <para>FreeBSD then set about the arduous task of literally
re-inventing itself from a completely new and rather incomplete re-inventing itself from a completely new and rather incomplete
@ -544,21 +544,21 @@
(due to various legal requirements) and the fact that the Intel (due to various legal requirements) and the fact that the Intel
port of 4.4 was highly incomplete. It took the project until port of 4.4 was highly incomplete. It took the project until
November of 1994 to make this transition, at which point it November of 1994 to make this transition, at which point it
released FreeBSD 2.0 to the net and on CDROM (in late December). released FreeBSD&nbsp;2.0 to the net and on CDROM (in late December).
Despite being still more than a little rough around the edges, Despite being still more than a little rough around the edges,
the release was a significant success and was followed by the the release was a significant success and was followed by the
more robust and easier to install FreeBSD 2.0.5 release in June of more robust and easier to install FreeBSD&nbsp;2.0.5 release in June of
1995.</para> 1995.</para>
<para>We released FreeBSD 2.1.5 in August of 1996, and it appeared <para>We released FreeBSD&nbsp;2.1.5 in August of 1996, and it appeared
to be popular enough among the ISP and commercial communities that to be popular enough among the ISP and commercial communities that
another release along the 2.1-STABLE branch was merited. This was another release along the 2.1-STABLE branch was merited. This was
FreeBSD 2.1.7.1, released in February 1997 and capping the end of FreeBSD&nbsp;2.1.7.1, released in February 1997 and capping the end of
mainstream development on 2.1-STABLE. Now in maintenance mode, mainstream development on 2.1-STABLE. Now in maintenance mode,
only security enhancements and other critical bug fixes will be only security enhancements and other critical bug fixes will be
done on this branch (RELENG_2_1_0).</para> done on this branch (RELENG_2_1_0).</para>
<para>FreeBSD 2.2 was branched from the development mainline <para>FreeBSD&nbsp;2.2 was branched from the development mainline
(<quote>-CURRENT</quote>) in November 1996 as the RELENG_2_2 (<quote>-CURRENT</quote>) in November 1996 as the RELENG_2_2
branch, and the first full release (2.2.1) was released in April branch, and the first full release (2.2.1) was released in April
1997. Further releases along the 2.2 branch were done in the 1997. Further releases along the 2.2 branch were done in the
@ -816,20 +816,20 @@
</indexterm> </indexterm>
<para>FreeBSD is a freely available, full source 4.4BSD-Lite based <para>FreeBSD is a freely available, full source 4.4BSD-Lite based
release for Intel i386, i486, Pentium, Pentium Pro, Celeron, release for Intel i386, i486, Pentium, Pentium Pro, Celeron,
Pentium II, Pentium III (or compatible) and DEC Alpha based computer Pentium&nbsp;II, Pentium&nbsp;III (or compatible) and DEC Alpha based computer
systems. It is based primarily on software from U.C. Berkeley's systems. It is based primarily on software from U.C. Berkeley's
CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and
the Free Software Foundation.</para> the Free Software Foundation.</para>
<para>Since our release of FreeBSD 2.0 in late 94, the performance, <para>Since our release of FreeBSD&nbsp;2.0 in late 94, the performance,
feature set, and stability of FreeBSD has improved dramatically. feature set, and stability of FreeBSD has improved dramatically.
The largest change is a revamped virtual memory system with a merged The largest change is a revamped virtual memory system with a merged
VM/file buffer cache that not only increases performance, but also VM/file buffer cache that not only increases performance, but also
reduces FreeBSD's memory footprint, making a 5MB configuration a reduces FreeBSD's memory footprint, making a 5&nbsp;MB configuration a
more acceptable minimum. Other enhancements include full NIS client more acceptable minimum. Other enhancements include full NIS client
and server support, transaction TCP support, dial-on-demand PPP, and server support, transaction TCP support, dial-on-demand PPP,
integrated DHCP support, an improved SCSI subsystem, ISDN support, integrated DHCP support, an improved SCSI subsystem, ISDN support,
support for ATM, FDDI, Fast and Gigabit Ethernet (1000Mbit) support for ATM, FDDI, Fast and Gigabit Ethernet (1000&nbsp;Mbit)
adapters, improved support for the latest Adaptec controllers, and adapters, improved support for the latest Adaptec controllers, and
many hundreds of bug fixes.</para> many hundreds of bug fixes.</para>
@ -844,7 +844,7 @@
were over &os.numports; ports! The list of ports ranges from were over &os.numports; ports! The list of ports ranges from
http (WWW) servers, to games, languages, editors, and almost http (WWW) servers, to games, languages, editors, and almost
everything in between. The entire ports collection requires everything in between. The entire ports collection requires
approximately 100MB of storage, all ports being expressed as approximately 100&nbsp;MB of storage, all ports being expressed as
<quote>deltas</quote> to their original sources. This makes <quote>deltas</quote> to their original sources. This makes
it much easier for us to update ports, and greatly reduces the it much easier for us to update ports, and greatly reduces the
disk space demands made by the older 1.0 ports collection. To disk space demands made by the older 1.0 ports collection. To
@ -862,7 +862,7 @@
<para>A number of additional documents which you may find very helpful <para>A number of additional documents which you may find very helpful
in the process of installing and using FreeBSD may now also be found in the process of installing and using FreeBSD may now also be found
in the <filename>/usr/share/doc</filename> directory on any machine in the <filename>/usr/share/doc</filename> directory on any machine
running FreeBSD 2.1 or later. You may view the locally installed running FreeBSD&nbsp;2.1 or later. You may view the locally installed
manuals with any HTML capable browser using the following manuals with any HTML capable browser using the following
URLs:</para> URLs:</para>