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

Whitespace only: Fix several whitespace issues in Handbook's "introduction" chapter.

Browse source 
Approved by:	gabor (mentor)
This commit is contained in:
Manolis Kiagias 2008-09-03 15:28:34 +00:00
parent c555b76519
commit df6b7cab55
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=32814
1 changed files with 209 additions and 210 deletions

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

@ -8,7 +8,7 @@
<chapterinfo>
<authorgroup>
<author>
<firstname>Jim</firstname>
<firstname>Jim</firstname>
<surname>Mock</surname>
<contrib>Restructured, reorganized, and parts
rewritten by </contrib>
@ -31,31 +31,34 @@
<listitem>
<para>How &os; relates to other computer operating systems.</para>
</listitem>
<listitem>
<para>The history of the &os;&nbsp;Project.</para>
</listitem>
<listitem>
<para>The goals of the &os;&nbsp;Project.</para>
</listitem>
<listitem>
<para>The basics of the &os; open-source development model.</para>
</listitem>
<listitem>
<para>And of course: where the name <quote>&os;</quote> comes from.</para>
<para>And of course: where the name <quote>&os;</quote> comes
from.</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="nutshell">
<title>Welcome to &os;!</title>
<indexterm><primary>4.4BSD-Lite</primary></indexterm>
<indexterm><primary>4.4BSD-Lite</primary></indexterm>
<para>&os; is a 4.4BSD-Lite based operating system for
Intel (x86 and &itanium;), AMD64, <trademark>Alpha</trademark>, Sun
&ultrasparc; computers. Ports to other
architectures are also underway.
You can also
architectures are also underway. You can also
read about <link linkend="history">the history of &os;</link>,
or the <link linkend="relnotes">current release</link>. If you
are interested in contributing something to the Project (code,
@ -66,10 +69,10 @@
<title>What Can &os; Do?</title>
<para>&os; has many noteworthy features. Some of these
are:</para>
are:</para>
<itemizedlist>
<indexterm><primary>preemptive multitasking</primary></indexterm>
<indexterm><primary>preemptive multitasking</primary></indexterm>
<listitem>
<para><emphasis>Preemptive multitasking</emphasis> with
dynamic priority adjustment to ensure smooth and fair
@ -87,36 +90,37 @@
resource limits can be placed on users or groups of users,
protecting critical system resources from over-use.</para>
</listitem>
<indexterm><primary>TCP/IP networking</primary></indexterm>
<listitem>
<para>Strong <emphasis>TCP/IP networking</emphasis> with
support for industry standards such as SCTP, DHCP, NFS,
NIS, PPP, SLIP, IPsec, and IPv6. This means that your &os; machine can
interoperate easily with other systems as well as act as an
enterprise server, providing vital functions such as NFS
NIS, PPP, SLIP, IPsec, and IPv6. This means that your &os;
machine can interoperate easily with other systems as well as
act as an enterprise server, providing vital functions such as NFS
(remote file access) and email services or putting your
organization on the Internet with WWW, FTP, routing and
firewall (security) services.</para>
</listitem>
<indexterm><primary>memory protection</primary></indexterm>
<indexterm><primary>memory protection</primary></indexterm>
<listitem>
<para><emphasis>Memory protection</emphasis> ensures that
applications (or users) cannot interfere with each other. One
applications (or users) cannot interfere with each other. One
application crashing will not affect others in any way.</para>
</listitem>
<listitem>
<para>&os; is a <emphasis>32-bit</emphasis> operating
system (<emphasis>64-bit</emphasis> on the Alpha, &itanium;, AMD64, and &ultrasparc;) and was
designed as such from the ground up.</para>
system (<emphasis>64-bit</emphasis> on the Alpha, &itanium;,
AMD64, and &ultrasparc;) and was designed as such from the ground
up.</para>
</listitem>
<indexterm>
<primary>X Window System</primary>
<seealso>XFree86</seealso>
</indexterm>
<primary>X Window System</primary>
<seealso>XFree86</seealso>
</indexterm>
<listitem>
<para>The industry standard <emphasis>X Window System</emphasis>
@ -149,15 +153,15 @@
<para><emphasis>Binary compatibility</emphasis> with many
programs built for Linux, SCO, SVR4, BSDI and NetBSD.</para>
</listitem>
<listitem>
<para>Thousands of <emphasis>ready-to-run</emphasis>
applications are available from the &os;
applications are available from the &os;
<emphasis>ports</emphasis> and <emphasis>packages</emphasis>
collection. Why search the net when you can find it all right
here?</para>
</listitem>
<listitem>
<para>Thousands of additional and
<emphasis>easy-to-port</emphasis> applications are available
@ -165,7 +169,7 @@
popular commercial &unix; systems and thus most applications
require few, if any, changes to compile.</para>
</listitem>
<indexterm><primary>virtual memory</primary></indexterm>
<listitem>
<para>Demand paged <emphasis>virtual memory</emphasis> and
@ -173,8 +177,8 @@
satisfies applications with large appetites for memory while
still maintaining interactive response to other users.</para>
</listitem>
<indexterm>
<indexterm>
<primary>Symmetric Multi-Processing (SMP)</primary>
</indexterm>
<listitem>
@ -211,24 +215,24 @@
at the mercy of your vendor when you can have a truly open
system?</para>
</listitem>
<listitem>
<para>Extensive <emphasis>online
documentation</emphasis>.</para>
</listitem>
<listitem>
<para><emphasis>And many more!</emphasis></para>
</listitem>
</itemizedlist>
<indexterm><primary>4.4BSD-Lite</primary></indexterm>
<indexterm>
<primary>Computer Systems Research Group (CSRG)</primary>
<primary>Computer Systems Research Group (CSRG)</primary>
</indexterm>
<indexterm><primary>U.C. Berkeley</primary></indexterm>
<para>&os; is based on the 4.4BSD-Lite release from Computer
Systems Research Group (CSRG) at the University of California at
Systems Research Group (CSRG) at the University of California at
Berkeley, and carries on the distinguished tradition of BSD
systems development. In addition to the fine work provided by
CSRG, the &os;&nbsp;Project has put in many thousands of hours in
@ -239,23 +243,23 @@
<emphasis>now</emphasis>!</para>
<para>The applications to which &os; can be put are truly
limited only by your own imagination. From software development
limited only by your own imagination. From software development
to factory automation, inventory control to azimuth correction of
remote satellite antennae; if it can be done with a commercial
&unix; product then it is more than likely that you can do it with
&os; too! &os; also benefits significantly from
literally thousands of high quality applications developed by
research centers and universities around the world, often
available at little to no cost. Commercial applications are also
available at little to no cost. Commercial applications are also
available and appearing in greater numbers every day.</para>
<para>Because the source code for &os; itself is generally
available, the system can also be customized to an almost unheard
available, the system can also be customized to an almost unheard
of degree for special applications or projects, and in ways not
generally possible with operating systems from most major
commercial vendors. Here is just a sampling of some of the
applications in which people are currently using &os;:</para>
<itemizedlist>
<listitem>
<para><emphasis>Internet Services:</emphasis> The robust TCP/IP
@ -267,11 +271,11 @@
<listitem>
<para>FTP servers</para>
</listitem>
<indexterm><primary>web servers</primary></indexterm>
<listitem>
<para>World Wide Web servers (standard or secure
[SSL])</para>
[SSL])</para>
</listitem>
<listitem>
@ -282,9 +286,9 @@
<indexterm><primary>NAT</primary></indexterm>
<listitem>
<para>Firewalls and NAT (<quote>IP masquerading</quote>)
gateways</para>
gateways</para>
</listitem>
<indexterm>
<primary>electronic mail</primary>
<see>email</see>
@ -295,12 +299,12 @@
<listitem>
<para>Electronic Mail servers</para>
</listitem>
<indexterm><primary>USENET</primary></indexterm>
<listitem>
<para>USENET News or Bulletin Board Systems</para>
</listitem>
<listitem>
<para>And more...</para>
</listitem>
@ -311,7 +315,7 @@
quad-processor Xeon with RAID storage as your enterprise
grows.</para>
</listitem>
<listitem>
<para><emphasis>Education:</emphasis> Are you a student of
computer science or a related engineering field? There is no
@ -323,7 +327,7 @@
computer is to get <emphasis>other</emphasis> work
done!</para>
</listitem>
<listitem>
<para><emphasis>Research:</emphasis> With source code for the
entire system available, &os; is an excellent platform for
@ -334,7 +338,7 @@
licensing agreements or limitations on what may be discussed
in open forums.</para>
</listitem>
<indexterm><primary>router</primary></indexterm>
<indexterm><primary>DNS Server</primary></indexterm>
<listitem>
@ -344,7 +348,7 @@
486 PC sitting in the corner into an advanced router with
sophisticated packet-filtering capabilities.</para>
</listitem>
<indexterm>
<primary>X Window System</primary>
<secondary>XFree86</secondary>
@ -357,14 +361,13 @@
<para><emphasis>X Window workstation:</emphasis> &os; is a
fine choice for an inexpensive X terminal solution,
using the freely available X11 server.
Unlike an
X terminal, &os; allows many applications to be run
Unlike an X terminal, &os; allows many applications to be run
locally if desired, thus relieving the burden on a central
server. &os; can even boot <quote>diskless</quote>, making
individual workstations even cheaper and easier to
administer.</para>
</listitem>
<indexterm><primary>GNU Compiler Collection</primary></indexterm>
<listitem>
<para><emphasis>Software Development:</emphasis> The basic
@ -373,11 +376,10 @@
debugger.</para>
</listitem>
</itemizedlist>
<para>&os; is available in both source and binary form on CD-ROM,
DVD,
and via anonymous FTP. Please see <xref linkend="mirrors">
for more information about obtaining &os;.</para>
DVD, and via anonymous FTP. Please see <xref linkend="mirrors">
for more information about obtaining &os;.</para>
</sect2>
<sect2>
@ -389,11 +391,11 @@
</indexterm>
<para>&os; is used to power some of the biggest sites on the
Internet, including:</para>
Internet, including:</para>
<itemizedlist>
<indexterm><primary>Yahoo!</primary></indexterm>
<listitem>
<indexterm><primary>Yahoo!</primary></indexterm>
<listitem>
<para><ulink url="http://www.yahoo.com/">Yahoo!</ulink></para>
</listitem>
@ -410,31 +412,28 @@
<indexterm><primary>Pair Networks</primary></indexterm>
<listitem>
<para><ulink url="http://www.pair.com/">Pair
Networks</ulink></para>
<para><ulink url="http://www.pair.com/">Pair Networks</ulink></para>
</listitem>
<indexterm><primary>Sony Japan</primary></indexterm>
<listitem>
<para><ulink url="http://www.sony.co.jp/">Sony
Japan</ulink></para>
<para><ulink url="http://www.sony.co.jp/">Sony Japan</ulink></para>
</listitem>
<indexterm><primary>Netcraft</primary></indexterm>
<listitem>
<para><ulink url="http://www.netcraft.com/">Netcraft</ulink>
</para>
<para><ulink url="http://www.netcraft.com/">Netcraft</ulink></para>
</listitem>
<indexterm><primary>Weathernews</primary></indexterm>
<listitem>
<para><ulink url="http://www.wni.com/">Weathernews</ulink>
</para></listitem>
<para><ulink url="http://www.wni.com/">Weathernews</ulink></para>
</listitem>
<indexterm><primary>Supervalu</primary></indexterm>
<listitem>
<para><ulink
url="http://www.supervalu.com/">Supervalu</ulink></para>
url="http://www.supervalu.com/">Supervalu</ulink></para>
</listitem>
<indexterm><primary>TELEHOUSE America</primary></indexterm>
@ -451,16 +450,14 @@
<indexterm><primary>JMA Wired</primary></indexterm>
<listitem>
<para><ulink
url="http://www.jmawired.com/">JMA Wired</ulink></para>
<para><ulink url="http://www.jmawired.com/">JMA Wired</ulink></para>
</listitem>
</itemizedlist>
<para>and many more.</para>
</sect2>
</sect1>
<sect1 id="history">
<title>About the &os;&nbsp;Project</title>
@ -486,14 +483,14 @@
<indexterm><primary>Williams, Nate</primary></indexterm>
<indexterm><primary>Grimes, Rod</primary></indexterm>
<indexterm>
<primary>FreeBSD Project</primary>
<secondary>history</secondary>
<primary>FreeBSD Project</primary>
<secondary>history</secondary>
</indexterm>
<para>The &os;&nbsp;Project had its genesis in the early part of 1993,
partially as an outgrowth of the <quote>Unofficial 386BSD
Patchkit</quote> by the patchkit's last 3 coordinators: Nate
Patchkit</quote> by the patchkit's last 3 coordinators: Nate
Williams, Rod Grimes and myself.</para>
<indexterm><primary>386BSD</primary></indexterm>
<para>Our original goal was to produce an intermediate snapshot of
386BSD in order to fix a number of problems with it that the
@ -501,7 +498,7 @@
may remember the early working title for the project being
<quote>386BSD 0.5</quote> or <quote>386BSD Interim</quote> in
reference to that fact.</para>
<indexterm><primary>Jolitz, Bill</primary></indexterm>
<para>386BSD was Bill Jolitz's operating system, which had been up
to that point suffering rather severely from almost a year's worth
@ -528,7 +525,7 @@
machine to work on and a fast Internet connection. Without Walnut
Creek CDROM's almost unprecedented degree of faith in what was, at
the time, a completely unknown project, it is quite unlikely that
&os; would have gotten as far, as fast, as it has today.</para>
&os; would have gotten as far, as fast, as it has today.</para>
<indexterm><primary>4.3BSD-Lite</primary></indexterm>
<indexterm><primary>Net/2</primary></indexterm>
@ -540,7 +537,7 @@
4.3BSD-Lite (<quote>Net/2</quote>) tape from U.C. Berkeley, with
many components also provided by 386BSD and the Free Software
Foundation. It was a fairly reasonable success for a first
offering, and we followed it with the highly successful &os;
offering, and we followed it with the highly successful &os;
1.1 release in May of 1994.</para>
<indexterm><primary>Novell</primary></indexterm>
@ -589,7 +586,7 @@
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
summer and fall of '97, the last of which (2.2.8) appeared in
November 1998. The first official 3.0 release appeared in
November 1998. The first official 3.0 release appeared in
October 1998 and spelled the beginning of the end for the 2.2
branch.</para>
@ -599,7 +596,7 @@
September 16, 1999, 3.4 on December 20, 1999, and 3.5 on
June 24, 2000, which was followed a few days later by a minor
point release update to 3.5.1, to incorporate some last-minute
security fixes to Kerberos. This will be the final release in the
security fixes to Kerberos. This will be the final release in the
3.X branch.</para>
<para>There was another branch on March 13, 2000, which saw the
@ -608,16 +605,16 @@
the last 4.11-RELEASE came out in January 2005.</para>
<para>The long-awaited 5.0-RELEASE was announced on January 19,
2003. The culmination of nearly three years of work, this
release started &os; on the path of advanced multiprocessor
and application thread support and introduced support for the
&ultrasparc; and <literal>ia64</literal> platforms. This release
was followed by 5.1 in June of 2003. The last 5.X release from the
-CURRENT branch was 5.2.1-RELEASE, introduced in February 2004.</para>
2003. The culmination of nearly three years of work, this
release started &os; on the path of advanced multiprocessor
and application thread support and introduced support for the
&ultrasparc; and <literal>ia64</literal> platforms. This release
was followed by 5.1 in June of 2003. The last 5.X release from the
-CURRENT branch was 5.2.1-RELEASE, introduced in February 2004.</para>
<para>The RELENG_5 branch, created in August 2004, was followed by
5.3-RELEASE, which marked the beginning of the 5-STABLE branch releases.
The most recent 5.5-RELEASE release came out in May 2006.
5.3-RELEASE, which marked the beginning of the 5-STABLE branch
releases. The most recent 5.5-RELEASE release came out in May 2006.
There will be no additional releases from the RELENG_5 branch.</para>
<para>The tree was branched again in July 2005, this time for RELENG_6.
@ -631,29 +628,30 @@
out in &rel.current.date;. There will be additional releases from the
RELENG_7 branch.</para>
<para>For now, long-term development projects continue to take place in the
8.X-CURRENT (trunk) branch, and SNAPshot releases of 8.X on
<para>For now, long-term development projects continue to take place
in the 8.X-CURRENT (trunk) branch, and SNAPshot releases of 8.X on
CD-ROM (and, of course, on the net) are continually made available
from <ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">
the snapshot server</ulink> as work progresses.</para>
from <ulink
url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">the snapshot
server</ulink> as work progresses.</para>
</sect2>
<sect2 id="goals">
<sect2info>
<authorgroup>
<author>
<firstname>Jordan</firstname>
<authorgroup>
<author>
<firstname>Jordan</firstname>
<surname>Hubbard</surname>
<contrib>Contributed by </contrib>
<contrib>Contributed by </contrib>
</author>
</authorgroup>
</authorgroup>
</sect2info>
<title>&os;&nbsp;Project Goals</title>
<indexterm>
<primary>FreeBSD Project</primary>
<secondary>goals</secondary>
<primary>FreeBSD Project</primary>
<secondary>goals</secondary>
</indexterm>
<para>The goals of the &os;&nbsp;Project are to provide software that
may be used for any purpose and without strings attached. Many of
@ -668,45 +666,45 @@
support.</para>
<indexterm>
<primary>GNU General Public License (GPL)</primary>
<primary>GNU General Public License (GPL)</primary>
</indexterm>
<indexterm>
<primary>GNU Lesser General Public License (LGPL)</primary>
<primary>GNU Lesser General Public License (LGPL)</primary>
</indexterm>
<indexterm><primary>BSD Copyright</primary></indexterm>
<para>That code in our source tree which falls under the GNU
General Public License (GPL) or Library General Public License
(LGPL) comes with slightly more strings attached, though at
least on the side of enforced access rather than the usual
opposite. Due to the additional complexities that can evolve
in the commercial use of GPL software we do, however, prefer
software submitted under the more relaxed BSD copyright when
it is a reasonable option to do so.</para>
General Public License (GPL) or Library General Public License
(LGPL) comes with slightly more strings attached, though at
least on the side of enforced access rather than the usual
opposite. Due to the additional complexities that can evolve
in the commercial use of GPL software we do, however, prefer
software submitted under the more relaxed BSD copyright when
it is a reasonable option to do so.</para>
</sect2>
<sect2 id="development">
<sect2info>
<authorgroup>
<author>
<firstname>Satoshi</firstname>
<authorgroup>
<author>
<firstname>Satoshi</firstname>
<surname>Asami</surname>
<contrib>Contributed by </contrib>
<contrib>Contributed by </contrib>
</author>
</authorgroup>
</authorgroup>
</sect2info>
<title>The &os; Development Model</title>
<indexterm>
<primary>FreeBSD Project</primary>
<secondary>development model</secondary>
<primary>FreeBSD Project</primary>
<secondary>development model</secondary>
</indexterm>
<para>The development of &os; is a very open and flexible
process, being literally built from the contributions
of hundreds of people around the world, as can be seen from
our <ulink
url="&url.articles.contributors;/article.html">list of
contributors</ulink>. &os;'s development infrastructure allow
url="&url.articles.contributors;/article.html">list of
contributors</ulink>. &os;'s development infrastructure allow
these hundreds of developers to collaborate over the Internet.
We are constantly on the lookout for
new developers and ideas, and those interested in becoming
@ -725,12 +723,12 @@
id="development-cvs-repository"></term>
<indexterm>
<primary>CVS</primary>
<secondary>repository</secondary>
</indexterm>
<primary>CVS</primary>
<secondary>repository</secondary>
</indexterm>
<indexterm>
<primary>Concurrent Versions System</primary>
<see>CVS</see>
<see>CVS</see>
</indexterm>
<indexterm>
<primary>SVN</primary>
@ -741,12 +739,13 @@
<see>SVN</see>
</indexterm>
<listitem>
<para>For several years, the central source tree for &os; was maintained by
<para>For several years, the central source tree for &os;
was maintained by
<ulink url="http://ximbiot.com/cvs/wiki/">CVS</ulink>
(Concurrent Versions System), a freely available source code
control tool that comes bundled with &os;. In June 2008, the
Project switched to using <ulink
url="http://subversion.tigris.org">SVN</ulink> (Subversion).
url="http://subversion.tigris.org">SVN</ulink> (Subversion).
The switch was deemed necessary, as the technical limitations
imposed by <application>CVS</application> were becoming obvious
due to the rapid expansion of the source tree and the amount
@ -763,23 +762,23 @@
The documentation, World Wide Web, and Ports repositories are
still using <application>CVS</application>. The primary
<ulink
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">repository</ulink>
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">repository</ulink>
resides on a machine in Santa Clara CA, USA
from where it is replicated to numerous mirror machines
throughout the world. The <application>SVN</application> tree, which contains the <link
linkend="current">-CURRENT</link> and <link
linkend="stable">-STABLE</link> trees,
throughout the world. The <application>SVN</application> tree,
which contains the <link linkend="current">-CURRENT</link> and
<link linkend="stable">-STABLE</link> trees,
can all be easily replicated to your own machine as well.
Please refer to the <link linkend="synching">Synchronizing
your source tree</link> section for more information on
doing this.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>The committers list<anchor
id="development-committers"></term>
<indexterm><primary>committers</primary></indexterm>
<listitem>
<para>The <firstterm>committers</firstterm>
@ -790,38 +789,40 @@
command, which is used to bring new changes into the CVS
repository). The best way of making submissions for review
by the committers list is to use the &man.send-pr.1;
command. If something appears to be jammed in the
command. If something appears to be jammed in the
system, then you may also reach them by sending mail to
the &a.committers;.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>The FreeBSD core team<anchor id="development-core"></term>
<indexterm><primary>core team</primary></indexterm>
<listitem>
<para>The <firstterm>&os; core team</firstterm>
would be equivalent to the board of directors if the &os;&nbsp;Project were a company. The primary task of the core team
is to make sure the project, as a whole, is in good shape
would be equivalent to the board of directors if the
&os;&nbsp;Project were a company. The primary task of the core
team is to make sure the project, as a whole, is in good shape
and is heading in the right directions. Inviting dedicated
and responsible developers to join our group of committers
is one of the functions of the core team, as is the
recruitment of new core team members as others move on.
The current core team was elected from a pool of committer
candidates in July 2008. Elections are held every 2 years.</para>
candidates in July 2008. Elections are held
every 2 years.</para>
<para>Some core team members also have specific areas of
responsibility, meaning that they are committed to
ensuring that some large portion of the system works as
advertised. For a complete list of &os; developers
and their areas of responsibility, please see the <ulink
url="&url.articles.contributors;/article.html">Contributors
List</ulink></para>
url="&url.articles.contributors;/article.html">Contributors
List</ulink></para>
<note>
<para>Most members of the core team are volunteers when it
comes to &os; development and do not benefit from the
comes to &os; development and do not benefit from the
project financially, so <quote>commitment</quote> should
also not be misconstrued as meaning <quote>guaranteed
support.</quote> The <quote>board of directors</quote>
@ -832,7 +833,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term>Outside contributors</term>
@ -843,37 +844,36 @@
bug fixes to us on an almost constant basis. The primary
way of keeping in touch with &os;'s more non-centralized
development is to subscribe to the &a.hackers; where such
things are discussed. See <xref
linkend="eresources"> for more information about
the various &os; mailing lists.</para>
things are discussed. See <xref linkend="eresources"> for
more information about the various &os; mailing lists.</para>
<para><citetitle><ulink
url="&url.articles.contributors;/article.html">The
&os; Contributors List</ulink></citetitle> is a long
url="&url.articles.contributors;/article.html">The
&os; Contributors List</ulink></citetitle> is a long
and growing one, so why not join it by contributing
something back to &os; today?</para>
<para>Providing code is not the only way of contributing to
the project; for a more complete list of things that need
doing, please refer to the <ulink
url="&url.base;/index.html">&os;&nbsp;Project web
site</ulink>.</para>
url="&url.base;/index.html">&os;&nbsp;Project web
site</ulink>.</para>
</listitem>
</varlistentry>
</variablelist>
<para>In summary, our development model is organized as a loose set
of concentric circles. The centralized model is designed for the
convenience of the <emphasis>users</emphasis> of &os;, who are
provided with an easy way of tracking one central code
of concentric circles. The centralized model is designed for the
convenience of the <emphasis>users</emphasis> of &os;, who are
provided with an easy way of tracking one central code
base, not to keep potential contributors out! Our desire is to
present a stable operating system with a large set of coherent
<link linkend="ports">application programs</link> that the users
can easily install and use &mdash; this model works very well in
accomplishing that.</para>
<para>All we ask of those who would join us as &os; developers is
some of the same dedication its current people have to its
some of the same dedication its current people have to its
continued success!</para>
</sect2>
@ -886,91 +886,90 @@
<indexterm><primary>Free Software Foundation</primary></indexterm>
<indexterm><primary>U.C. Berkeley</primary></indexterm>
<indexterm>
<primary>Computer Systems Research Group (CSRG)</primary>
<primary>Computer Systems Research Group (CSRG)</primary>
</indexterm>
<para>&os; is a freely available, full source 4.4BSD-Lite based
release for Intel &i386;, &i486;, &pentium;,
&pentium;&nbsp;Pro,
&celeron;,
&pentium;&nbsp;II,
&pentium;&nbsp;III,
&pentium;&nbsp;4 (or compatible),
&xeon;, DEC <trademark>Alpha</trademark>
and Sun &ultrasparc; based computer
systems. It is based primarily on software from U.C. Berkeley's
CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and
the Free Software Foundation.</para>
release for Intel &i386;, &i486;, &pentium;,
&pentium;&nbsp;Pro,
&celeron;,
&pentium;&nbsp;II,
&pentium;&nbsp;III,
&pentium;&nbsp;4 (or compatible),
&xeon;, DEC <trademark>Alpha</trademark>
and Sun &ultrasparc; based computer
systems. It is based primarily on software from U.C. Berkeley's
CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and
the Free Software Foundation.</para>
<para>Since our release of &os;&nbsp;2.0 in late 1994, the performance,
feature set, and stability of &os; has improved dramatically.
feature set, and stability of &os; has improved dramatically.
<!-- XXX is the rest of this paragraph still true ? -->
The largest change is a revamped virtual memory system with a merged
VM/file buffer cache that not only increases performance, but also
reduces &os;'s memory footprint, making a 5&nbsp;MB configuration a
more acceptable minimum. Other enhancements include full NIS client
and server support, transaction TCP support, dial-on-demand PPP,
integrated DHCP support, an improved SCSI subsystem, ISDN support,
support for ATM, FDDI, Fast and Gigabit Ethernet (1000&nbsp;Mbit)
adapters, improved support for the latest Adaptec controllers, and
many thousands of bug fixes.</para>
The largest change is a revamped virtual memory system with a merged
VM/file buffer cache that not only increases performance, but also
reduces &os;'s memory footprint, making a 5&nbsp;MB configuration a
more acceptable minimum. Other enhancements include full NIS client
and server support, transaction TCP support, dial-on-demand PPP,
integrated DHCP support, an improved SCSI subsystem, ISDN support,
support for ATM, FDDI, Fast and Gigabit Ethernet (1000&nbsp;Mbit)
adapters, improved support for the latest Adaptec controllers, and
many thousands of bug fixes.</para>
<para>In addition to the base distributions, &os; offers a
ported software collection with thousands of commonly
sought-after programs. At the time of this printing, there
were over &os.numports; ports! The list of ports ranges from
http (WWW) servers, to games, languages, editors, and almost
everything in between. The entire Ports Collection requires
approximately &ports.size; of storage, all ports being expressed as
<quote>deltas</quote> to their original sources. This makes
it much easier for us to update ports, and greatly reduces the
disk space demands made by the older 1.0 Ports Collection. To
compile a port, you simply change to the directory of the
program you wish to install, type <command>make
install</command>, and let the system do the rest. The full
original distribution for each port you build is retrieved
dynamically off the CD-ROM or a local FTP site, so you need
only enough disk space to build the ports you want. Almost
every port is also provided as a pre-compiled
<quote>package</quote>, which can be installed with a simple
command (<command>pkg_add</command>) by those who do not wish
to compile their own ports from source. More information on
ported software collection with thousands of commonly
sought-after programs. At the time of this printing, there
were over &os.numports; ports! The list of ports ranges from
http (WWW) servers, to games, languages, editors, and almost
everything in between. The entire Ports Collection requires
approximately &ports.size; of storage, all ports being expressed as
<quote>deltas</quote> to their original sources. This makes
it much easier for us to update ports, and greatly reduces the
disk space demands made by the older 1.0 Ports Collection. To
compile a port, you simply change to the directory of the
program you wish to install, type <command>make install</command>,
and let the system do the rest. The full
original distribution for each port you build is retrieved
dynamically off the CD-ROM or a local FTP site, so you need
only enough disk space to build the ports you want. Almost
every port is also provided as a pre-compiled
<quote>package</quote>, which can be installed with a simple
command (<command>pkg_add</command>) by those who do not wish
to compile their own ports from source. More information on
packages and ports can be found in <xref linkend="ports">.</para>
<para>A number of additional documents which you may find very helpful
in the process of installing and using &os; may now also be found
in the <filename>/usr/share/doc</filename> directory on any recent
&os; machine. You may view the locally installed
manuals with any HTML capable browser using the following
URLs:</para>
in the process of installing and using &os; may now also be found
in the <filename>/usr/share/doc</filename> directory on any recent
&os; machine. You may view the locally installed
manuals with any HTML capable browser using the following
URLs:</para>
<variablelist>
<varlistentry>
<varlistentry>
<term>The FreeBSD Handbook</term>
<listitem>
<para><ulink type="html"
url="file://localhost/usr/share/doc/handbook/index.html"><filename>/usr/share/doc/handbook/index.html</filename></ulink></para>
url="file://localhost/usr/share/doc/handbook/index.html"><filename>/usr/share/doc/handbook/index.html</filename></ulink></para>
</listitem>
</varlistentry>
<varlistentry>
</varlistentry>
<varlistentry>
<term>The FreeBSD FAQ</term>
<listitem>
<para><ulink type="html"
url="file://localhost/usr/share/doc/faq/index.html"><filename>/usr/share/doc/faq/index.html</filename></ulink></para>
url="file://localhost/usr/share/doc/faq/index.html"><filename>/usr/share/doc/faq/index.html</filename></ulink></para>
</listitem>
</varlistentry>
</varlistentry>
</variablelist>
<para>You can also view the master (and most frequently updated)
copies at <ulink
url="http://www.FreeBSD.org/"></ulink>.</para>
copies at <ulink url="http://www.FreeBSD.org/"></ulink>.</para>
</sect2>
</sect1>
</chapter>
<!--
<!--
Local Variables:
mode: sgml
sgml-declaration: "../chapter.decl"