Initial restructuring, reorganization, and rewrite of some bits of the
handbook's introduction chapter.
This commit is contained in:
Jim Mock
parent
eb0547d3f8
commit
3ca3c2962e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=6434
2 changed files with 1274 additions and 1064 deletions
|
|
@ -1,32 +1,97 @@
|
||||||
<!--
|
<!--
|
||||||
The FreeBSD Documentation Project
|
The FreeBSD Documentation Project
|
||||||
|
|
||||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.23 2000/01/09 13:23:17 phantom Exp $
|
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.24 2000/01/13 00:09:02 jim Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<chapter id="introduction">
|
<chapter id="introduction">
|
||||||
<title>Introduction</title>
|
<title>Introduction</title>
|
||||||
|
|
||||||
<para>FreeBSD is a 4.4BSD-Lite2 based operating system for Intel architecture
|
<para><emphasis>Restructured, reorganized, and parts rewritten by
|
||||||
(x86) and DEC Alpha based computer systems. For an overview of FreeBSD, see
|
&a.jim;, 17 January 2000.</emphasis></para>
|
||||||
<link linkend="nutshell">FreeBSD in a nutshell</link>. For a history of
|
|
||||||
the project, read <link linkend="history">a brief history of FreeBSD</link>.
|
<sect1>
|
||||||
To see a description of the latest release, read <link
|
<title>Synopsis</title>
|
||||||
linkend="relnotes">about the current release</link>. If you are
|
|
||||||
interested in contributing something to the FreeBSD project (code,
|
<para>Thank you for your interest in FreeBSD! The following chapter
|
||||||
equipment, sacks of unmarked bills), please see about <link
|
covers various items about the FreeBSD Project, such as its history,
|
||||||
linkend="contrib">contributing to FreeBSD</link>.</para>
|
goals, development model, and so on.</para>
|
||||||
|
|
||||||
|
<para>FreeBSD is a 4.4BSD-Lite2 based operating system for the Intel
|
||||||
|
architecture (x86) and DEC Alpha based systems. Ports to other
|
||||||
|
architectures are also underway. For a brief overview of FreeBSD,
|
||||||
|
see the <link linkend="nutshell">next section</link>. You can also
|
||||||
|
read about <link linkend="history">the history of FreeBSD</link>,
|
||||||
|
or the <link linkend="relnotes">the current release</link>. If you
|
||||||
|
are interested in contributing something to the Project (code,
|
||||||
|
hardware, unmarked bills), see the <link
|
||||||
|
linkend="contrib">contributing to FreeBSD</link> section.</para>
|
||||||
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="nutshell">
|
<sect1 id="nutshell">
|
||||||
<title>FreeBSD in a Nutshell</title>
|
<title>Welcome to FreeBSD!</title>
|
||||||
|
|
||||||
<para>FreeBSD is a state of the art operating system for computer
|
<para>Since you are still here reading this, you most likely have some
|
||||||
systems based on both the Intel CPU architecture, which includes
|
idea as to what FreeBSD is and what it can do for you. If you are
|
||||||
the 386 and Pentium family of processors as well as Intel
|
new to FreeBSD, read on for more information.</para>
|
||||||
compatible CPUs from Cyrix and AMD, and the DEC Alpha
|
|
||||||
architecture. FreeBSD provides you with many advanced features
|
<sect2>
|
||||||
previously available only on much more expensive systems.
|
<title>What is FreeBSD?</title>
|
||||||
These features include:</para>
|
|
||||||
|
<para>In general, FreeBSD is a state-of-the-art operating system
|
||||||
|
based on 4.4BSD-Lite2. It runs on computer systems based on the
|
||||||
|
Intel architecture (x86), and also the DEC Alpha
|
||||||
|
architecture.</para>
|
||||||
|
|
||||||
|
<para>FreeBSD is used to power some of the biggest sites on the
|
||||||
|
Internet, including:</para>
|
||||||
|
|
||||||
|
<itemizedlist>
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.yahoo.com/">Yahoo!</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.hotmail.com/">Hotmail</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.apache.org/">Apache</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.be.com/">Be, Inc.</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.bluemountain.com/">Blue Mountain
|
||||||
|
Arts</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.pair.com/">Pair
|
||||||
|
Networks</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.whistle.com/">Whistle
|
||||||
|
Communications</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.wccdrom.com/">Walnut Creek
|
||||||
|
CDROM</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
</itemizedlist>
|
||||||
|
|
||||||
|
<para>and many more.</para>
|
||||||
|
</sect2>
|
||||||
|
|
||||||
|
<sect2>
|
||||||
|
<title>What can FreeBSD do?</title>
|
||||||
|
|
||||||
|
<para>FreeBSD has many noteworthy features. Some of these
|
||||||
|
are:</para>
|
||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -38,7 +103,7 @@
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Multiuser facilities</emphasis> which allow many
|
<para><emphasis>Multiuser facilities</emphasis> which allow many
|
||||||
poeple to use a FreeBSD system simulatenously for a variety
|
people to use a FreeBSD system simulatenously for a variety
|
||||||
of things. This means, for example, that system peripherals
|
of things. This means, for example, that system peripherals
|
||||||
such as printers and tape drives are properly shared between
|
such as printers and tape drives are properly shared between
|
||||||
all users on the system or the network and that individual
|
all users on the system or the network and that individual
|
||||||
|
|
@ -58,9 +123,9 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Memory protection</emphasis> ensures that applications
|
<para><emphasis>Memory protection</emphasis> ensures that
|
||||||
(or users) cannot interfere with each other. One application
|
applications (or users) cannot interfere with each other. One
|
||||||
crashing will not affect others in any way.</para>
|
application crashing will not affect others in any way.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -71,39 +136,42 @@
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The industry standard <emphasis>X Window System</emphasis>
|
<para>The industry standard <emphasis>X Window System</emphasis>
|
||||||
(X11R6) provides a graphical user interface (GUI) for the cost of a
|
(X11R6) provides a graphical user interface (GUI) for the cost
|
||||||
common VGA card and monitor and comes with full sources.</para>
|
of a common VGA card and monitor and comes with full
|
||||||
|
sources.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Binary compatibility</emphasis> with many programs
|
<para><emphasis>Binary compatibility</emphasis> with many
|
||||||
built for Linux, SCO, SVR4, BSDI and NetBSD.</para>
|
programs built for Linux, SCO, SVR4, BSDI and NetBSD.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Thousands of <emphasis>ready-to-run</emphasis> applications are
|
<para>Thousands of <emphasis>ready-to-run</emphasis>
|
||||||
available from the FreeBSD <emphasis>ports</emphasis> and
|
applications are available from the FreeBSD
|
||||||
<emphasis>packages</emphasis> collection. Why search the net when
|
<emphasis>ports</emphasis> and <emphasis>packages</emphasis>
|
||||||
you can find it all right here?</para>
|
collection. Why search the net when you can find it all right
|
||||||
|
here?</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Thousands of additional and <emphasis>easy-to-port</emphasis>
|
<para>Thousands of additional and
|
||||||
applications available on the Internet. FreeBSD is source code
|
<emphasis>easy-to-port</emphasis> applications available on
|
||||||
compatible with most popular commercial Unix systems and thus most
|
the Internet. FreeBSD is source code compatible with most
|
||||||
applications require few, if any, changes to compile.</para>
|
popular commercial Unix systems and thus most applications
|
||||||
|
require few, if any, changes to compile.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Demand paged <emphasis>virtual memory</emphasis> and
|
<para>Demand paged <emphasis>virtual memory</emphasis> and
|
||||||
“merged VM/buffer cache” design efficiently satisfies
|
“merged VM/buffer cache” design efficiently
|
||||||
applications with large appetites for memory while still maintaining
|
satisfies applications with large appetites for memory while
|
||||||
interactive response to other users.</para>
|
still maintaining interactive response to other users.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>SMP</emphasis> support for machines with multiple
|
<para><emphasis>SMP</emphasis> support for machines with
|
||||||
CPUs (Intel only).</para>
|
multiple CPUs (Intel only).</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -116,14 +184,16 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Source code</emphasis> for the entire system means you
|
<para><emphasis>Source code</emphasis> for the entire system
|
||||||
have the greatest degree of control over your environment. Why be
|
means you have the greatest degree of control over your
|
||||||
locked into a proprietary solution and at the mercy of your vendor
|
environment. Why be locked into a proprietary solution and
|
||||||
when you can have a truly Open System?</para>
|
at the mercy of your vendor when you can have a truly Open
|
||||||
|
System?</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Extensive <emphasis>on-line documentation</emphasis>.</para>
|
<para>Extensive <emphasis>on-line
|
||||||
|
documentation</emphasis>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -131,32 +201,34 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
<para>FreeBSD is based on the 4.4BSD-Lite2 release from Computer Systems
|
<para>FreeBSD is based on the 4.4BSD-Lite2 release from Computer
|
||||||
Research Group (CSRG) at the University of California at Berkeley, and
|
Systems Research Group (CSRG) at the University of California at
|
||||||
carries on the distinguished tradition of BSD systems development. In
|
Berkeley, and carries on the distinguished tradition of BSD
|
||||||
addition to the fine work provided by CSRG, the FreeBSD Project has put
|
systems development. In addition to the fine work provided by
|
||||||
in many thousands of hours in fine tuning the system for maximum
|
CSRG, the FreeBSD Project has put in many thousands of hours in
|
||||||
performance and reliability in real-life load situations. As many of
|
fine tuning the system for maximum performance and reliability in
|
||||||
the commercial giants struggle to field PC operating systems with such
|
real-life load situations. As many of the commercial giants
|
||||||
features, performance and reliability, FreeBSD can offer them
|
struggle to field PC operating systems with such features,
|
||||||
|
performance and reliability, FreeBSD can offer them
|
||||||
<emphasis>now</emphasis>!</para>
|
<emphasis>now</emphasis>!</para>
|
||||||
|
|
||||||
<para>The applications to which FreeBSD can be put are truly limited only
|
<para>The applications to which FreeBSD can be put are truly
|
||||||
by your own imagination. From software development to factory
|
limited only by your own imagination. From software development
|
||||||
automation, inventory control to azimuth correction of remote satellite
|
to factory automation, inventory control to azimuth correction of
|
||||||
antennae; if it can be done with a commercial UNIX product then it is
|
remote satellite antennae; if it can be done with a commercial
|
||||||
more than likely that you can do it with FreeBSD, too! FreeBSD also
|
UNIX product then it is more than likely that you can do it with
|
||||||
benefits significantly from the literally thousands of high quality
|
FreeBSD, too! FreeBSD also benefits significantly from the
|
||||||
applications developed by research centers and universities around the
|
literally thousands of high quality applications developed by
|
||||||
world, often available at little to no cost. Commercial applications are
|
research centers and universities around the world, often
|
||||||
also available and appearing in greater numbers every day.</para>
|
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 FreeBSD itself is generally available,
|
<para>Because the source code for FreeBSD itself is generally
|
||||||
the system can also be customized to an almost unheard of degree for
|
available, the system can also be customized to an almost unheard
|
||||||
special applications or projects, and in ways not generally possible
|
of degree for special applications or projects, and in ways not
|
||||||
with operating systems from most major commercial vendors. Here is just
|
generally possible with operating systems from most major
|
||||||
a sampling of some of the applications in which people are currently
|
commercial vendors. Here is just a sampling of some of the
|
||||||
using FreeBSD:</para>
|
applications in which people are currently using FreeBSD:</para>
|
||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -170,11 +242,13 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>World Wide Web servers (standard or secure [SSL])</para>
|
<para>World Wide Web servers (standard or secure
|
||||||
|
[SSL])</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Firewalls and NAT ("IP masquerading") gateways.</para>
|
<para>Firewalls and NAT (“IP masquerading”)
|
||||||
|
gateways.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -197,198 +271,222 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Education:</emphasis> Are you a student of computer
|
<para><emphasis>Education:</emphasis> Are you a student of
|
||||||
science or a related engineering field? There is no better way of
|
computer science or a related engineering field? There is no
|
||||||
learning about operating systems, computer architecture and
|
better way of learning about operating systems, computer
|
||||||
networking than the hands on, under the hood experience that FreeBSD
|
architecture and networking than the hands on, under the hood
|
||||||
can provide. A number of freely available CAD, mathematical and
|
experience that FreeBSD can provide. A number of freely
|
||||||
graphic design packages also make it highly useful to those whose
|
available CAD, mathematical and graphic design packages also
|
||||||
primary interest in a computer is to get <emphasis>other</emphasis>
|
make it highly useful to those whose primary interest in a
|
||||||
work done!</para>
|
computer is to get <emphasis>other</emphasis> work
|
||||||
|
done!</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Research:</emphasis> With source code for the entire
|
<para><emphasis>Research:</emphasis> With source code for the
|
||||||
system available, FreeBSD is an excellent platform for research in
|
entire system available, FreeBSD is an excellent platform for
|
||||||
operating systems as well as other branches of computer science.
|
research in operating systems as well as other branches of
|
||||||
FreeBSD's freely available nature also makes it possible for remote
|
computer science. FreeBSD's freely available nature also makes
|
||||||
groups to collaborate on ideas or shared development without having
|
it possible for remote groups to collaborate on ideas or
|
||||||
to worry about special licensing agreements or limitations on what
|
shared development without having to worry about special
|
||||||
may be discussed in open forums.</para>
|
licensing agreements or limitations on what may be discussed
|
||||||
|
in open forums.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Networking:</emphasis> Need a new router? A name
|
<para><emphasis>Networking:</emphasis> Need a new router? A
|
||||||
server (DNS)? A firewall to keep people out of your internal
|
name server (DNS)? A firewall to keep people out of your
|
||||||
network? FreeBSD can easily turn that unused 386 or 486 PC sitting
|
internal network? FreeBSD can easily turn that unused 386 or
|
||||||
in the corner into an advanced router with sophisticated packet
|
486 PC sitting in the corner into an advanced router with
|
||||||
filtering capabilities.</para>
|
sophisticated packet filtering capabilities.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>X Window workstation:</emphasis> FreeBSD is a fine
|
<para><emphasis>X Window workstation:</emphasis> FreeBSD is a
|
||||||
choice for an inexpensive X terminal solution, either using the
|
fine choice for an inexpensive X terminal solution, either
|
||||||
freely available XFree86 server or one of the excellent commercial
|
using the freely available XFree86 server or one of the
|
||||||
servers provided by X Inside. Unlike an X terminal, FreeBSD allows
|
excellent commercial servers provided by X Inside. Unlike an
|
||||||
many applications to be run locally, if desired, thus relieving the
|
X terminal, FreeBSD allows many applications to be run
|
||||||
burden on a central server. FreeBSD can even boot
|
locally, if desired, thus relieving the burden on a central
|
||||||
“diskless”, making individual workstations even cheaper
|
server. FreeBSD can even boot “diskless”, making
|
||||||
and easier to administer.</para>
|
individual workstations even cheaper and easier to
|
||||||
|
administer.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Software Development:</emphasis> The basic FreeBSD
|
<para><emphasis>Software Development:</emphasis> The basic
|
||||||
system comes with a full complement of development tools including
|
FreeBSD system comes with a full complement of development
|
||||||
the renowned GNU C/C++ compiler and debugger.</para>
|
tools including the renowned GNU C/C++ compiler and
|
||||||
|
debugger.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
<para>FreeBSD is available in both source and binary form on CDROM and via
|
<para>FreeBSD is available in both source and binary form on CDROM
|
||||||
anonymous ftp. See <link linkend="mirrors">Obtaining FreeBSD</link>
|
and via anonymous ftp. See <link linkend="mirrors">Obtaining
|
||||||
for more details.</para>
|
FreeBSD</link> for more details.</para>
|
||||||
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="history">
|
<sect1 id="about">
|
||||||
|
<title>About the FreeBSD Project</title>
|
||||||
|
|
||||||
|
<para>The following section provides some background information on
|
||||||
|
the project, including a brief history, project goals, and the
|
||||||
|
development model of the project.</para>
|
||||||
|
|
||||||
|
<sect2 id="history">
|
||||||
<title>A Brief History of FreeBSD</title>
|
<title>A Brief History of FreeBSD</title>
|
||||||
|
|
||||||
<para><emphasis>Contributed by &a.jkh;</emphasis>.</para>
|
<para><emphasis>Contributed by &a.jkh;</emphasis>.</para>
|
||||||
|
|
||||||
<para>The FreeBSD project had its genesis in the early part of 1993,
|
<para>The FreeBSD project had its genesis in the early part of 1993,
|
||||||
partially as an outgrowth of the “Unofficial 386BSD
|
partially as an outgrowth of the “Unofficial 386BSD
|
||||||
Patchkit” by the patchkit's last 3 coordinators: Nate Williams,
|
Patchkit” by the patchkit's last 3 coordinators: Nate
|
||||||
Rod Grimes and myself.</para>
|
Williams, Rod Grimes and myself.</para>
|
||||||
|
|
||||||
<para>Our original goal was to produce an intermediate snapshot of 386BSD
|
<para>Our original goal was to produce an intermediate snapshot of
|
||||||
in order to fix a number of problems with it that the patchkit mechanism
|
386BSD in order to fix a number of problems with it that the
|
||||||
just was not capable of solving. Some of you may remember the early
|
patchkit mechanism just was not capable of solving. Some of you
|
||||||
working title for the project being “386BSD 0.5” or
|
may remember the early working title for the project being
|
||||||
“386BSD Interim” in reference to that fact.</para>
|
“386BSD 0.5” or “386BSD Interim” in
|
||||||
|
reference to that fact.</para>
|
||||||
|
|
||||||
<para>386BSD was Bill Jolitz's operating system, which had been up to that
|
<para>386BSD was Bill Jolitz's operating system, which had been up
|
||||||
point suffering rather severely from almost a year's worth of neglect.
|
to that point suffering rather severely from almost a year's worth
|
||||||
As the patchkit swelled ever more uncomfortably with each passing day,
|
of neglect. As the patchkit swelled ever more uncomfortably with
|
||||||
we were in unanimous agreement that something had to be done and decided
|
each passing day, we were in unanimous agreement that something
|
||||||
to try and assist Bill by providing this interim “cleanup”
|
had to be done and decided to try and assist Bill by providing
|
||||||
snapshot. Those plans came to a rude halt when Bill Jolitz suddenly
|
this interim “cleanup” snapshot. Those plans came to
|
||||||
decided to withdraw his sanction from the project without any clear
|
a rude halt when Bill Jolitz suddenly decided to withdraw his
|
||||||
indication of what would be done instead.</para>
|
sanction from the project without any clear indication of what
|
||||||
|
would be done instead.</para>
|
||||||
|
|
||||||
<para>It did not take us long to decide that the goal remained worthwhile,
|
<para>It did not take us long to decide that the goal remained
|
||||||
even without Bill's support, and so we adopted the name
|
worthwhile, even without Bill's support, and so we adopted the
|
||||||
“FreeBSD”, coined by David Greenman. Our initial objectives
|
name “FreeBSD”, coined by David Greenman. Our initial
|
||||||
were set after consulting with the system's current users and, once it
|
objectives were set after consulting with the system's current
|
||||||
became clear that the project was on the road to perhaps even becoming a
|
users and, once it became clear that the project was on the road
|
||||||
reality, I contacted Walnut Creek CDROM with an eye towards improving
|
to perhaps even becoming a reality, I contacted Walnut Creek CDROM
|
||||||
FreeBSD's distribution channels for those many unfortunates without easy
|
with an eye towards improving FreeBSD's distribution channels for
|
||||||
access to the Internet. Walnut Creek CDROM not only supported the idea
|
those many unfortunates without easy access to the Internet.
|
||||||
of distributing FreeBSD on CD but went so far as to provide the project
|
Walnut Creek CDROM not only supported the idea of distributing
|
||||||
with a machine to work on and a fast Internet connection. Without
|
FreeBSD on CD but went so far as to provide the project with a
|
||||||
Walnut Creek CDROM's almost unprecedented degree of faith in what was,
|
machine to work on and a fast Internet connection. Without Walnut
|
||||||
at the time, a completely unknown project, it is quite unlikely that
|
Creek CDROM's almost unprecedented degree of faith in what was, at
|
||||||
|
the time, a completely unknown project, it is quite unlikely that
|
||||||
FreeBSD would have gotten as far, as fast, as it has today.</para>
|
FreeBSD would have gotten as far, as fast, as it has today.</para>
|
||||||
|
|
||||||
<para>The first CDROM (and general net-wide) distribution was FreeBSD 1.0,
|
<para>The first CDROM (and general net-wide) distribution was
|
||||||
released in December of 1993. This was based on the 4.3BSD-Lite
|
FreeBSD 1.0, released in December of 1993. This was based on the
|
||||||
(“Net/2”) tape from U.C. Berkeley, with many components also
|
4.3BSD-Lite (“Net/2”) tape from U.C. Berkeley, with
|
||||||
provided by 386BSD and the Free Software Foundation. It was a fairly
|
many components also provided by 386BSD and the Free Software
|
||||||
reasonable success for a first offering, and we followed it with the
|
Foundation. It was a fairly reasonable success for a first
|
||||||
highly successful FreeBSD 1.1 release in May of 1994.</para>
|
offering, and we followed it with the highly successful FreeBSD
|
||||||
|
1.1 release in May of 1994.</para>
|
||||||
|
|
||||||
<para>Around this time, some rather unexpected storm clouds formed on the
|
<para>Around this time, some rather unexpected storm clouds formed
|
||||||
horizon as Novell and U.C. Berkeley settled their long-running lawsuit
|
on the horizon as Novell and U.C. Berkeley settled their
|
||||||
over the legal status of the Berkeley Net/2 tape. A condition of that
|
long-running lawsuit over the legal status of the Berkeley Net/2
|
||||||
settlement was U.C. Berkeley's concession that large parts of Net/2 were
|
tape. A condition of that settlement was U.C. Berkeley's
|
||||||
“encumbered” code and the property of Novell, who had in
|
concession that large parts of Net/2 were “encumbered”
|
||||||
turn acquired it from AT&T some time previously. What Berkeley got
|
code and the property of Novell, who had in turn acquired it from
|
||||||
in return was Novell's “blessing” that the 4.4BSD-Lite
|
AT&T some time previously. What Berkeley got in return was
|
||||||
release, when it was finally released, would be declared unencumbered
|
Novell's “blessing” that the 4.4BSD-Lite release, when
|
||||||
and all existing Net/2 users would be strongly encouraged to switch.
|
it was finally released, would be declared unencumbered and all
|
||||||
This included FreeBSD, and the project was given until the end of July
|
existing Net/2 users would be strongly encouraged to switch. This
|
||||||
1994 to stop shipping its own Net/2 based product. Under the terms of
|
included FreeBSD, and the project was given until the end of July
|
||||||
that agreement, the project was allowed one last release before the
|
1994 to stop shipping its own Net/2 based product. Under the
|
||||||
deadline, that release being FreeBSD 1.1.5.1.</para>
|
terms of that agreement, the project was allowed one last release
|
||||||
|
before the deadline, that release being FreeBSD 1.1.5.1.</para>
|
||||||
|
|
||||||
<para>FreeBSD then set about the arduous task of literally re-inventing
|
<para>FreeBSD then set about the arduous task of literally
|
||||||
itself from a completely new and rather incomplete set of 4.4BSD-Lite
|
re-inventing itself from a completely new and rather incomplete
|
||||||
bits. The “Lite” releases were light in part because
|
set of 4.4BSD-Lite bits. The “Lite” releases were
|
||||||
Berkeley's CSRG had removed large chunks of code required for actually
|
light in part because Berkeley's CSRG had removed large chunks of
|
||||||
constructing a bootable running system (due to various legal
|
code required for actually constructing a bootable running system
|
||||||
requirements) and the fact that the Intel port of 4.4 was highly
|
(due to various legal requirements) and the fact that the Intel
|
||||||
incomplete. It took the project until November of 1994 to make this
|
port of 4.4 was highly incomplete. It took the project until
|
||||||
transition, at which point it released FreeBSD 2.0 to the net
|
November of 1994 to make this transition, at which point it
|
||||||
and on CDROM (in late December). Despite being still more than a little
|
released FreeBSD 2.0 to the net and on CDROM (in late December).
|
||||||
rough around the edges, the release was a significant success and was
|
Despite being still more than a little rough around the edges,
|
||||||
followed by the more robust and easier to install FreeBSD 2.0.5 release
|
the release was a significant success and was followed by the
|
||||||
in June of 1995.</para>
|
more robust and easier to install FreeBSD 2.0.5 release in June of
|
||||||
|
1995.</para>
|
||||||
|
|
||||||
<para>We released FreeBSD 2.1.5 in August of 1996, and it appeared to be
|
<para>We released FreeBSD 2.1.5 in August of 1996, and it appeared
|
||||||
popular enough among the ISP and commercial communities that another
|
to be popular enough among the ISP and commercial communities that
|
||||||
release along the 2.1-STABLE branch was merited. This was FreeBSD
|
another release along the 2.1-STABLE branch was merited. This was
|
||||||
2.1.7.1, released in February 1997 and capping the end of mainstream
|
FreeBSD 2.1.7.1, released in February 1997 and capping the end of
|
||||||
development on 2.1-STABLE. Now in maintenance mode, only security
|
mainstream development on 2.1-STABLE. Now in maintenance mode,
|
||||||
enhancements and other critical bug fixes will be done on this branch
|
only security enhancements and other critical bug fixes will be
|
||||||
(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 2.2 was branched from the development mainline
|
||||||
(“-CURRENT”) in November 1996 as the RELENG_2_2 branch, and
|
(“-CURRENT”) in November 1996 as the RELENG_2_2
|
||||||
the first full release (2.2.1) was released in April, 1997. Further
|
branch, and the first full release (2.2.1) was released in April,
|
||||||
releases along the 2.2 branch were done in the Summer and Fall of '97,
|
1997. Further releases along the 2.2 branch were done in the
|
||||||
the last of which (2.2.8) appeared in November, 1998. The first
|
Summer and Fall of '97, the last of which (2.2.8) appeared in
|
||||||
official 3.0 release appeared in October, 1998 and spelled the beginning
|
November, 1998. The first official 3.0 release appeared in
|
||||||
of the end for the 2.2 branch.</para>
|
October, 1998 and spelled the beginning of the end for the 2.2
|
||||||
|
branch.</para>
|
||||||
|
|
||||||
<para>The tree branched again on Jan 20, 1999, leading to the 4.0-CURRENT
|
<para>The tree branched again on Jan 20, 1999, leading to the
|
||||||
and 3.X-STABLE branches. From 3.X-STABLE, 3.1 was released on February
|
4.0-CURRENT and 3.X-STABLE branches. From 3.X-STABLE, 3.1 was
|
||||||
15th, 1999 and 3.2 on May 15, 1999. The most current release on this
|
released on February 15, 1999, 3.2 on May 15, 1999, and 3.3 on
|
||||||
branch is 3.3, which was released on September 16th, 1999.</para>
|
September 16, 1999. The most current release on this branch is
|
||||||
|
&rel.current;, which was released on December 20, 1999.</para>
|
||||||
|
|
||||||
<para>Long term development projects continue to take place in the
|
<para>Long term development projects continue to take place in the
|
||||||
4.0-CURRENT branch, and SNAPshot releases of 4.0 on CDROM (and,
|
4.0-CURRENT branch, and SNAPshot releases of 4.0 on CDROM (and, of
|
||||||
of course, on the net) are continually made available as work
|
course, on the net) are continually made available as work
|
||||||
progresses.</para>
|
progresses.</para>
|
||||||
</sect1>
|
</sect2>
|
||||||
|
|
||||||
<sect1 id="goals">
|
<sect2 id="goals">
|
||||||
<title>FreeBSD Project Goals</title>
|
<title>FreeBSD Project Goals</title>
|
||||||
|
|
||||||
<para><emphasis>Contributed by &a.jkh;</emphasis>.</para>
|
<para><emphasis>Contributed by &a.jkh;</emphasis>.</para>
|
||||||
|
|
||||||
<para>The goals of the FreeBSD Project are to provide software that may be
|
<para>The goals of the FreeBSD Project are to provide software that
|
||||||
used for any purpose and without strings attached. Many of us have a
|
may be used for any purpose and without strings attached. Many of
|
||||||
significant investment in the code (and project) and would certainly not
|
us have a significant investment in the code (and project) and
|
||||||
mind a little financial compensation now and then, but we are definitely
|
would certainly not mind a little financial compensation now and
|
||||||
not prepared to insist on it. We believe that our first and foremost
|
then, but we are definitely not prepared to insist on it. We
|
||||||
“mission” is to provide code to any and all comers, and for
|
believe that our first and foremost “mission” is to
|
||||||
whatever purpose, so that the code gets the widest possible use and
|
provide code to any and all comers, and for whatever purpose, so
|
||||||
provides the widest possible benefit. This is, I believe, one of the
|
that the code gets the widest possible use and provides the widest
|
||||||
most fundamental goals of Free Software and one that we enthusiastically
|
possible benefit. This is, I believe, one of the most fundamental
|
||||||
|
goals of Free Software and one that we enthusiastically
|
||||||
support.</para>
|
support.</para>
|
||||||
|
|
||||||
<para>That code in our source tree which falls under the GNU General Public
|
<para>That code in our source tree which falls under the GNU General
|
||||||
License (GPL) or Library General Public License (LGPL) comes with slightly
|
Public License (GPL) or Library General Public License (LGPL)
|
||||||
more strings attached, though at least on the side of enforced access
|
comes with slightly more strings attached, though at least on the
|
||||||
rather than the usual opposite. Due to the additional complexities that
|
side of enforced access rather than the usual opposite. Due to
|
||||||
can evolve in the commercial use of GPL software we do, however,
|
the additional complexities that can evolve in the commercial use
|
||||||
prefer software submitted under the more relaxed BSD copyright when it's
|
of GPL software we do, however, prefer software submitted under
|
||||||
a reasonable option to do so.</para>
|
the more relaxed BSD copyright when it's a reasonable option to
|
||||||
</sect1>
|
do so.</para>
|
||||||
|
</sect2>
|
||||||
|
|
||||||
<sect1 id="development">
|
<sect2 id="development">
|
||||||
<title>The FreeBSD Development Model</title>
|
<title>The FreeBSD Development Model</title>
|
||||||
|
|
||||||
<para><emphasis>Contributed by &a.asami;</emphasis>.</para>
|
<para><emphasis>Contributed by &a.asami;</emphasis>.</para>
|
||||||
|
|
||||||
<para>The development of FreeBSD is a very open and flexible process,
|
<para>The development of FreeBSD is a very open and flexible
|
||||||
FreeBSD being literally built from the contributions of hundreds of
|
process, FreeBSD being literally built from the contributions of
|
||||||
people around the world, as can be seen from our <link
|
hundreds of people around the world, as can be seen from our
|
||||||
linkend="staff">list of contributors</link>. We are constantly on the
|
<link linkend="staff">list of contributors</link>. We are
|
||||||
lookout for new developers and ideas, and those interested in becoming
|
constantly on the lookout for new developers and ideas, and those
|
||||||
more closely involved with the project need simply contact us at the
|
interested in becoming more closely involved with the project
|
||||||
&a.hackers;. The &a.announce; is also available to those wishing to
|
need simply contact us at the &a.hackers;. The &a.announce; is
|
||||||
make other FreeBSD users aware of major areas of work.</para>
|
also available to those wishing to make other FreeBSD users aware
|
||||||
|
of major areas of work.</para>
|
||||||
|
|
||||||
<para>Useful things to know about the FreeBSD project and its development
|
<para>Useful things to know about the FreeBSD project and its
|
||||||
process, whether working independently or in close cooperation:</para>
|
development process, whether working independently or in close
|
||||||
|
cooperation:</para>
|
||||||
|
|
||||||
<variablelist>
|
<variablelist>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
@ -396,36 +494,39 @@
|
||||||
id="development-cvs-repository"></term>
|
id="development-cvs-repository"></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The central source tree for FreeBSD is maintained by <ulink
|
<para>The central source tree for FreeBSD is maintained by
|
||||||
url="http://www.cyclic.com/cyclic-pages/CVS-sheet.html">CVS</ulink>
|
<ulink url="http://www.cyclic.com/cyclic-pages/CVS-sheet.html">CVS</ulink>
|
||||||
(Concurrent Version System), a freely available source code
|
(Concurrent Version System), a freely available source code
|
||||||
control tool which comes bundled with FreeBSD. The primary <ulink
|
control tool which comes bundled with FreeBSD. The primary
|
||||||
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS
|
<ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS
|
||||||
repository</ulink> resides on a machine in Concord CA, USA from
|
repository</ulink> resides on a machine in Concord CA, USA
|
||||||
where it is replicated to numerous mirror machines throughout the
|
from where it is replicated to numerous mirror machines
|
||||||
world. The CVS tree, as well as the <link
|
throughout the world. The CVS tree, as well as the <link
|
||||||
linkend="current">-CURRENT</link> and <link
|
linkend="current">-CURRENT</link> and <link
|
||||||
linkend="stable">-STABLE</link> trees which are checked out of
|
linkend="stable">-STABLE</link> trees which are checked out
|
||||||
it, can be easily replicated to your own machine as well. Please
|
of it, can be easily replicated to your own machine as well.
|
||||||
refer to the <link linkend="synching">Synchronizing your source
|
Please refer to the <link linkend="synching">Synchronizing
|
||||||
tree</link> section for more information on doing this.</para>
|
your source tree</link> section for more information on
|
||||||
|
doing this.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>The committers list<anchor id="development-committers"></term>
|
<term>The committers list<anchor
|
||||||
|
id="development-committers"></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The <link linkend="staff-committers">committers</link> are the
|
<para>The <link linkend="staff-committers">committers</link>
|
||||||
people who have <emphasis>write</emphasis> access to the CVS tree,
|
are the people who have <emphasis>write</emphasis> access to
|
||||||
and are thus authorized to make modifications to the FreeBSD
|
the CVS tree, and are thus authorized to make modifications
|
||||||
source (the term “committer” comes from the
|
to the FreeBSD source (the term “committer”
|
||||||
&man.cvs.1; <command>commit</command> command, which is used
|
comes from the &man.cvs.1; <command>commit</command>
|
||||||
to bring new changes into the CVS repository). The best way of
|
command, which is used to bring new changes into the CVS
|
||||||
making submissions for review by the committers list is to use the
|
repository). The best way of making submissions for review
|
||||||
&man.send-pr.1; command, though if something appears to be
|
by the committers list is to use the &man.send-pr.1;
|
||||||
jammed in the system then you may also reach them by sending mail
|
command, though if something appears to be jammed in the
|
||||||
to <email>cvs-committers@FreeBSD.org</email>.</para>
|
system then you may also reach them by sending mail to
|
||||||
|
<email>cvs-committers@FreeBSD.org</email>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
|
@ -433,32 +534,32 @@
|
||||||
<term>The FreeBSD core team<anchor id="development-core"></term>
|
<term>The FreeBSD core team<anchor id="development-core"></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The <link linkend="staff-core">FreeBSD core team</link> would
|
<para>The <link linkend="staff-core">FreeBSD core team</link>
|
||||||
be equivalent to the board of directors if the FreeBSD Project
|
would be equivalent to the board of directors if the FreeBSD
|
||||||
were a company. The primary task of the core team is to make sure
|
Project were a company. The primary task of the core team
|
||||||
the project, as a whole, is in good shape and is heading in the
|
is to make sure the project, as a whole, is in good shape
|
||||||
right directions. Inviting dedicated and responsible developers
|
and is heading in the right directions. Inviting dedicated
|
||||||
to join our group of committers is one of the functions of the
|
and responsible developers to join our group of committers
|
||||||
core team, as is the recruitment of new core team members as
|
is one of the functions of the core team, as is the
|
||||||
others move on. Most current members of the core team started as
|
recruitment of new core team members as others move on. Most
|
||||||
committers whose addiction to the project got the better of
|
current members of the core team started as committers whose
|
||||||
them.</para>
|
addiction to the project got the better of them.</para>
|
||||||
|
|
||||||
<para>Some core team members also have specific <link
|
<para>Some core team members also have specific <link
|
||||||
linkend="staff-who">areas of responsibility</link>, meaning that
|
linkend="staff-who">areas of responsibility</link>, meaning
|
||||||
they are committed to ensuring that some large portion of the
|
that they are committed to ensuring that some large portion
|
||||||
system works as advertised.</para>
|
of the system works as advertised.</para>
|
||||||
|
|
||||||
<note>
|
<note>
|
||||||
<para>Most members of the core team are volunteers when it comes
|
<para>Most members of the core team are volunteers when it
|
||||||
to FreeBSD development and do not benefit from the project
|
comes to FreeBSD development and do not benefit from the
|
||||||
financially, so “commitment” should also not be
|
project financially, so “commitment” should
|
||||||
misconstrued as meaning “guaranteed support.” The
|
also not be misconstrued as meaning “guaranteed
|
||||||
“board of directors” analogy above is not actually
|
support.” The “board of directors”
|
||||||
very accurate, and it may be more suitable to say that these are
|
analogy above is not actually very accurate, and it may be
|
||||||
the people who gave up their lives in favor of FreeBSD against
|
more suitable to say that these are the people who gave up
|
||||||
their better judgement! <!-- smiley
|
their lives in favor of FreeBSD against their better
|
||||||
--><emphasis>;-)</emphasis></para>
|
judgement! <!-- smiley --><emphasis>;-)</emphasis></para>
|
||||||
</note>
|
</note>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
@ -469,89 +570,93 @@
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Last, but definitely not least, the largest group of
|
<para>Last, but definitely not least, the largest group of
|
||||||
developers are the users themselves who provide feedback and
|
developers are the users themselves who provide feedback and
|
||||||
bug-fixes to us on an almost constant basis. The primary way of
|
bug-fixes to us on an almost constant basis. The primary
|
||||||
keeping in touch with FreeBSD's more non-centralized development
|
way of keeping in touch with FreeBSD's more non-centralized
|
||||||
is to subscribe to the &a.hackers; (see <link
|
development is to subscribe to the &a.hackers; (see <link
|
||||||
linkend="eresources-mail">mailing list info</link>) where such
|
linkend="eresources-mail">mailing list info</link>) where
|
||||||
things are discussed.</para>
|
such things are discussed.</para>
|
||||||
|
|
||||||
<para><link linkend="contrib-additional">The list</link> of those
|
<para><link linkend="contrib-additional">The list</link> of
|
||||||
who have contributed something which made its way into our source
|
those who have contributed something which made its way into
|
||||||
tree is a long and growing one, so why not join it by contributing
|
our source tree is a long and growing one, so why not join
|
||||||
something back to FreeBSD today? <!-- smiley
|
it by contributing something back to FreeBSD today?
|
||||||
--><emphasis>:-)</emphasis></para>
|
<!-- smiley --><emphasis>:-)</emphasis></para>
|
||||||
|
|
||||||
<para>Providing code is not the only way of contributing to the
|
<para>Providing code is not the only way of contributing to
|
||||||
project; for a more complete list of things that need doing,
|
the project; for a more complete list of things that need
|
||||||
please refer to the <link linkend="contrib">how to
|
doing, please refer to the <link linkend="contrib">how to
|
||||||
contribute</link> section in this handbook.</para>
|
contribute</link> section in this handbook.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
</variablelist>
|
</variablelist>
|
||||||
|
|
||||||
<para>In summary, our development model is organized as a loose set of
|
<para>In summary, our development model is organized as a loose set
|
||||||
concentric circles. The centralized model is designed for the
|
of concentric circles. The centralized model is designed for the
|
||||||
convenience of the <emphasis>users</emphasis> of FreeBSD, who are
|
convenience of the <emphasis>users</emphasis> of FreeBSD, who are
|
||||||
thereby provided with an easy way of tracking one central code base, not
|
thereby provided with an easy way of tracking one central code
|
||||||
to keep potential contributors out! Our desire is to present a stable
|
base, not to keep potential contributors out! Our desire is to
|
||||||
operating system with a large set of coherent <link
|
present a stable operating system with a large set of coherent
|
||||||
linkend="ports">application programs</link> that the users can easily
|
<link linkend="ports">application programs</link> that the users
|
||||||
install and use, and this model works very well in accomplishing
|
can easily install and use, and this model works very well in
|
||||||
that.</para>
|
accomplishing that.</para>
|
||||||
|
|
||||||
<para>All we ask of those who would join us as FreeBSD developers is some
|
<para>All we ask of those who would join us as FreeBSD developers is
|
||||||
of the same dedication its current people have to its continued
|
some of the same dedication its current people have to its
|
||||||
success!</para>
|
continued success!</para>
|
||||||
</sect1>
|
</sect2>
|
||||||
|
|
||||||
<sect1 id="relnotes">
|
<sect2 id="relnotes">
|
||||||
<title>About the Current Release</title>
|
<title>The Current FreeBSD Release</title>
|
||||||
|
|
||||||
<para>FreeBSD is a freely available, full source 4.4BSD-Lite2 based release
|
<para>FreeBSD is a freely available, full source 4.4BSD-Lite2 based
|
||||||
for Intel i386/i486/Pentium/PentiumPro/Celeron/Pentium II/Pentium III (or
|
release for Intel i386, i486, Pentium, Pentium Pro, Celeron,
|
||||||
compatible) and DEC Alpha based computer systems. It is based primarily
|
Pentium II, Pentium III (or compatible) and DEC Alpha based computer
|
||||||
on software from U.C. Berkeley's CSRG group, with some enhancements from
|
systems. It is based primarily on software from U.C. Berkeley's
|
||||||
NetBSD, OpenBSD, 386BSD, and the Free Software Foundation.</para>
|
CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and
|
||||||
|
the Free Software Foundation.</para>
|
||||||
|
|
||||||
<para>Since our release of FreeBSD 2.0 in late 94, the performance,
|
<para>Since our release of FreeBSD 2.0 in late 94, the performance,
|
||||||
feature set, and stability of FreeBSD has improved dramatically. The
|
feature set, and stability of FreeBSD has improved dramatically.
|
||||||
largest change is a revamped virtual memory system with a merged VM/file
|
The largest change is a revamped virtual memory system with a merged
|
||||||
buffer cache that not only increases performance, but reduces FreeBSD's
|
VM/file buffer cache that not only increases performance, but
|
||||||
memory footprint, making a 5MB configuration a more acceptable minimum.
|
reduces FreeBSD's memory footprint, making a 5MB configuration a
|
||||||
Other enhancements include full NIS client and server support,
|
more acceptable minimum. Other enhancements include full NIS client
|
||||||
transaction TCP support, dial-on-demand PPP, integrated DHCP support,
|
and server support, transaction TCP support, dial-on-demand PPP,
|
||||||
an improved SCSI subsystem, ISDN support, support for ATM, FDDI, Fast
|
integrated DHCP support, an improved SCSI subsystem, ISDN support,
|
||||||
and Gigabit Ethernet (1000Mbit) adapters, improved support for the latest
|
support for ATM, FDDI, Fast and Gigabit Ethernet (1000Mbit)
|
||||||
Adaptec controllers and many hundreds of bug fixes.</para>
|
adapters, improved support for the latest Adaptec controllers and
|
||||||
|
many hundreds of bug fixes.</para>
|
||||||
|
|
||||||
<para>We have also taken the comments and suggestions of many of our users
|
<para>We have also taken the comments and suggestions of many of our
|
||||||
to heart and have attempted to provide what we hope is a more sane and
|
users to heart and have attempted to provide what we hope is a more
|
||||||
easily understood installation process. Your feedback on this
|
sane and easily understood installation process. Your feedback on
|
||||||
(constantly evolving) process is especially welcome!</para>
|
this (constantly evolving) process is especially welcome!</para>
|
||||||
|
|
||||||
<para>In addition to the base distributions, FreeBSD offers a new ported
|
<para>In addition to the base distributions, FreeBSD offers a new
|
||||||
software collection with hundreds of commonly sought-after programs. By
|
ported software collection with hundreds of commonly sought-after
|
||||||
mid-November 1999, there were nearly 2800 ports! The list of
|
programs. By mid-January 2000, there were nearly 3000 ports! The
|
||||||
ports ranges from http (WWW) servers, to games, languages, editors and
|
list of ports ranges from http (WWW) servers, to games, languages,
|
||||||
almost everything in between. The entire ports collection requires
|
editors and almost everything in between. The entire ports
|
||||||
approximately 50MB of storage, all ports being expressed as
|
collection requires approximately 50MB of storage, all ports being
|
||||||
“deltas” to their original sources. This makes it much
|
expressed as “deltas” to their original sources. This
|
||||||
easier for us to update ports, and greatly reduces the disk space
|
makes it much easier for us to update ports, and greatly reduces
|
||||||
demands made by the older 1.0 ports collection. To compile a port, you
|
the disk space demands made by the older 1.0 ports collection. To
|
||||||
simply change to the directory of the program you wish to install, type
|
compile a port, you simply change to the directory of the program
|
||||||
<command>make install</command>, and let the system do the rest. The
|
you wish to install, type <command>make install</command>, and let
|
||||||
full original distribution for each port you build is retrieved
|
the system do the rest. The full original distribution for each
|
||||||
dynamically off the CDROM or a local ftp site, so you need only enough
|
port you build is retrieved dynamically off the CDROM or a local ftp
|
||||||
disk space to build the ports you want. (Almost) every port is also
|
site, so you need only enough disk space to build the ports you
|
||||||
provided as a pre-compiled “package” which can be installed
|
want. Almost every port is also provided as a pre-compiled
|
||||||
with a simple command (pkg_add) by those who do not wish to compile
|
“package” which can be installed with a simple command
|
||||||
their own ports from source.</para>
|
(pkg_add) by those who do not wish to compile their own ports from
|
||||||
|
source.</para>
|
||||||
|
|
||||||
<para>A number of additional documents which you may find very helpful in
|
<para>A number of additional documents which you may find very helpful
|
||||||
the process of installing and using FreeBSD may now also be found in the
|
in the process of installing and using FreeBSD may now also be found
|
||||||
<filename>/usr/share/doc</filename> directory on any machine running
|
in the <filename>/usr/share/doc</filename> directory on any machine
|
||||||
FreeBSD 2.1 or later. You may view the locally installed manuals with
|
running FreeBSD 2.1 or later. You may view the locally installed
|
||||||
any HTML capable browser using the following URLs:</para>
|
manuals with any HTML capable browser using the following
|
||||||
|
URLs:</para>
|
||||||
|
|
||||||
<variablelist>
|
<variablelist>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
@ -577,22 +682,23 @@
|
||||||
copies at <ulink
|
copies at <ulink
|
||||||
url="http://www.FreeBSD.org/">http://www.FreeBSD.org/</ulink>.</para>
|
url="http://www.FreeBSD.org/">http://www.FreeBSD.org/</ulink>.</para>
|
||||||
|
|
||||||
<para>The core of FreeBSD does not contain DES code which would inhibit
|
<para>The core of FreeBSD does not contain DES code which would
|
||||||
its being exported outside the United States. There is an add-on
|
inhibit its being exported outside the United States. There is an
|
||||||
package to the core distribution, for use only in the United States,
|
add-on package to the core distribution, for use only in the United
|
||||||
that contains the programs that normally use DES. The auxiliary
|
States, that contains the programs that normally use DES. The
|
||||||
packages provided separately can be used by anyone. A freely (from
|
auxiliary packages provided separately can be used by anyone. A
|
||||||
outside the U.S.) exportable European distribution of DES for our
|
freely (from outside the U.S.) exportable European distribution of
|
||||||
non-U.S. users also exists and is described in the <ulink
|
DES for our non-U.S. users also exists and is described in the
|
||||||
url="../FAQ/FAQ.html">FreeBSD FAQ</ulink>.</para>
|
<ulink url="../FAQ/FAQ.html">FreeBSD FAQ</ulink>.</para>
|
||||||
|
|
||||||
<para>If password security for FreeBSD is all you need, and you have no
|
<para>If password security for FreeBSD is all you need, and you have
|
||||||
requirement for copying encrypted passwords from different hosts (Suns,
|
no requirement for copying encrypted passwords from different hosts
|
||||||
DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5
|
(Suns, DEC machines, etc) into FreeBSD password entries, then
|
||||||
based security may be all you require! We feel that our default security
|
FreeBSD's MD5 based security may be all you require! We feel that
|
||||||
model is more than a match for DES, and without any messy export issues
|
our default security model is more than a match for DES, and without
|
||||||
to deal with. If you are outside (or even inside) the U.S., give it a
|
any messy export issues to deal with. If you are outside (or even
|
||||||
try!</para>
|
inside) the U.S., give it a try!</para>
|
||||||
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
</chapter>
|
</chapter>
|
||||||
|
|
||||||
|
|
@ -606,4 +712,3 @@
|
||||||
sgml-parent-document: ("../book.sgml" "part" "chapter")
|
sgml-parent-document: ("../book.sgml" "part" "chapter")
|
||||||
End:
|
End:
|
||||||
-->
|
-->
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,32 +1,97 @@
|
||||||
<!--
|
<!--
|
||||||
The FreeBSD Documentation Project
|
The FreeBSD Documentation Project
|
||||||
|
|
||||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.23 2000/01/09 13:23:17 phantom Exp $
|
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.24 2000/01/13 00:09:02 jim Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<chapter id="introduction">
|
<chapter id="introduction">
|
||||||
<title>Introduction</title>
|
<title>Introduction</title>
|
||||||
|
|
||||||
<para>FreeBSD is a 4.4BSD-Lite2 based operating system for Intel architecture
|
<para><emphasis>Restructured, reorganized, and parts rewritten by
|
||||||
(x86) and DEC Alpha based computer systems. For an overview of FreeBSD, see
|
&a.jim;, 17 January 2000.</emphasis></para>
|
||||||
<link linkend="nutshell">FreeBSD in a nutshell</link>. For a history of
|
|
||||||
the project, read <link linkend="history">a brief history of FreeBSD</link>.
|
<sect1>
|
||||||
To see a description of the latest release, read <link
|
<title>Synopsis</title>
|
||||||
linkend="relnotes">about the current release</link>. If you are
|
|
||||||
interested in contributing something to the FreeBSD project (code,
|
<para>Thank you for your interest in FreeBSD! The following chapter
|
||||||
equipment, sacks of unmarked bills), please see about <link
|
covers various items about the FreeBSD Project, such as its history,
|
||||||
linkend="contrib">contributing to FreeBSD</link>.</para>
|
goals, development model, and so on.</para>
|
||||||
|
|
||||||
|
<para>FreeBSD is a 4.4BSD-Lite2 based operating system for the Intel
|
||||||
|
architecture (x86) and DEC Alpha based systems. Ports to other
|
||||||
|
architectures are also underway. For a brief overview of FreeBSD,
|
||||||
|
see the <link linkend="nutshell">next section</link>. You can also
|
||||||
|
read about <link linkend="history">the history of FreeBSD</link>,
|
||||||
|
or the <link linkend="relnotes">the current release</link>. If you
|
||||||
|
are interested in contributing something to the Project (code,
|
||||||
|
hardware, unmarked bills), see the <link
|
||||||
|
linkend="contrib">contributing to FreeBSD</link> section.</para>
|
||||||
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="nutshell">
|
<sect1 id="nutshell">
|
||||||
<title>FreeBSD in a Nutshell</title>
|
<title>Welcome to FreeBSD!</title>
|
||||||
|
|
||||||
<para>FreeBSD is a state of the art operating system for computer
|
<para>Since you are still here reading this, you most likely have some
|
||||||
systems based on both the Intel CPU architecture, which includes
|
idea as to what FreeBSD is and what it can do for you. If you are
|
||||||
the 386 and Pentium family of processors as well as Intel
|
new to FreeBSD, read on for more information.</para>
|
||||||
compatible CPUs from Cyrix and AMD, and the DEC Alpha
|
|
||||||
architecture. FreeBSD provides you with many advanced features
|
<sect2>
|
||||||
previously available only on much more expensive systems.
|
<title>What is FreeBSD?</title>
|
||||||
These features include:</para>
|
|
||||||
|
<para>In general, FreeBSD is a state-of-the-art operating system
|
||||||
|
based on 4.4BSD-Lite2. It runs on computer systems based on the
|
||||||
|
Intel architecture (x86), and also the DEC Alpha
|
||||||
|
architecture.</para>
|
||||||
|
|
||||||
|
<para>FreeBSD is used to power some of the biggest sites on the
|
||||||
|
Internet, including:</para>
|
||||||
|
|
||||||
|
<itemizedlist>
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.yahoo.com/">Yahoo!</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.hotmail.com/">Hotmail</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.apache.org/">Apache</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.be.com/">Be, Inc.</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.bluemountain.com/">Blue Mountain
|
||||||
|
Arts</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.pair.com/">Pair
|
||||||
|
Networks</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.whistle.com/">Whistle
|
||||||
|
Communications</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para><ulink url="http://www.wccdrom.com/">Walnut Creek
|
||||||
|
CDROM</ulink></para>
|
||||||
|
</listitem>
|
||||||
|
</itemizedlist>
|
||||||
|
|
||||||
|
<para>and many more.</para>
|
||||||
|
</sect2>
|
||||||
|
|
||||||
|
<sect2>
|
||||||
|
<title>What can FreeBSD do?</title>
|
||||||
|
|
||||||
|
<para>FreeBSD has many noteworthy features. Some of these
|
||||||
|
are:</para>
|
||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -38,7 +103,7 @@
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Multiuser facilities</emphasis> which allow many
|
<para><emphasis>Multiuser facilities</emphasis> which allow many
|
||||||
poeple to use a FreeBSD system simulatenously for a variety
|
people to use a FreeBSD system simulatenously for a variety
|
||||||
of things. This means, for example, that system peripherals
|
of things. This means, for example, that system peripherals
|
||||||
such as printers and tape drives are properly shared between
|
such as printers and tape drives are properly shared between
|
||||||
all users on the system or the network and that individual
|
all users on the system or the network and that individual
|
||||||
|
|
@ -58,9 +123,9 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Memory protection</emphasis> ensures that applications
|
<para><emphasis>Memory protection</emphasis> ensures that
|
||||||
(or users) cannot interfere with each other. One application
|
applications (or users) cannot interfere with each other. One
|
||||||
crashing will not affect others in any way.</para>
|
application crashing will not affect others in any way.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -71,39 +136,42 @@
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The industry standard <emphasis>X Window System</emphasis>
|
<para>The industry standard <emphasis>X Window System</emphasis>
|
||||||
(X11R6) provides a graphical user interface (GUI) for the cost of a
|
(X11R6) provides a graphical user interface (GUI) for the cost
|
||||||
common VGA card and monitor and comes with full sources.</para>
|
of a common VGA card and monitor and comes with full
|
||||||
|
sources.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Binary compatibility</emphasis> with many programs
|
<para><emphasis>Binary compatibility</emphasis> with many
|
||||||
built for Linux, SCO, SVR4, BSDI and NetBSD.</para>
|
programs built for Linux, SCO, SVR4, BSDI and NetBSD.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Thousands of <emphasis>ready-to-run</emphasis> applications are
|
<para>Thousands of <emphasis>ready-to-run</emphasis>
|
||||||
available from the FreeBSD <emphasis>ports</emphasis> and
|
applications are available from the FreeBSD
|
||||||
<emphasis>packages</emphasis> collection. Why search the net when
|
<emphasis>ports</emphasis> and <emphasis>packages</emphasis>
|
||||||
you can find it all right here?</para>
|
collection. Why search the net when you can find it all right
|
||||||
|
here?</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Thousands of additional and <emphasis>easy-to-port</emphasis>
|
<para>Thousands of additional and
|
||||||
applications available on the Internet. FreeBSD is source code
|
<emphasis>easy-to-port</emphasis> applications available on
|
||||||
compatible with most popular commercial Unix systems and thus most
|
the Internet. FreeBSD is source code compatible with most
|
||||||
applications require few, if any, changes to compile.</para>
|
popular commercial Unix systems and thus most applications
|
||||||
|
require few, if any, changes to compile.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Demand paged <emphasis>virtual memory</emphasis> and
|
<para>Demand paged <emphasis>virtual memory</emphasis> and
|
||||||
“merged VM/buffer cache” design efficiently satisfies
|
“merged VM/buffer cache” design efficiently
|
||||||
applications with large appetites for memory while still maintaining
|
satisfies applications with large appetites for memory while
|
||||||
interactive response to other users.</para>
|
still maintaining interactive response to other users.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>SMP</emphasis> support for machines with multiple
|
<para><emphasis>SMP</emphasis> support for machines with
|
||||||
CPUs (Intel only).</para>
|
multiple CPUs (Intel only).</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -116,14 +184,16 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Source code</emphasis> for the entire system means you
|
<para><emphasis>Source code</emphasis> for the entire system
|
||||||
have the greatest degree of control over your environment. Why be
|
means you have the greatest degree of control over your
|
||||||
locked into a proprietary solution and at the mercy of your vendor
|
environment. Why be locked into a proprietary solution and
|
||||||
when you can have a truly Open System?</para>
|
at the mercy of your vendor when you can have a truly Open
|
||||||
|
System?</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Extensive <emphasis>on-line documentation</emphasis>.</para>
|
<para>Extensive <emphasis>on-line
|
||||||
|
documentation</emphasis>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -131,32 +201,34 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
<para>FreeBSD is based on the 4.4BSD-Lite2 release from Computer Systems
|
<para>FreeBSD is based on the 4.4BSD-Lite2 release from Computer
|
||||||
Research Group (CSRG) at the University of California at Berkeley, and
|
Systems Research Group (CSRG) at the University of California at
|
||||||
carries on the distinguished tradition of BSD systems development. In
|
Berkeley, and carries on the distinguished tradition of BSD
|
||||||
addition to the fine work provided by CSRG, the FreeBSD Project has put
|
systems development. In addition to the fine work provided by
|
||||||
in many thousands of hours in fine tuning the system for maximum
|
CSRG, the FreeBSD Project has put in many thousands of hours in
|
||||||
performance and reliability in real-life load situations. As many of
|
fine tuning the system for maximum performance and reliability in
|
||||||
the commercial giants struggle to field PC operating systems with such
|
real-life load situations. As many of the commercial giants
|
||||||
features, performance and reliability, FreeBSD can offer them
|
struggle to field PC operating systems with such features,
|
||||||
|
performance and reliability, FreeBSD can offer them
|
||||||
<emphasis>now</emphasis>!</para>
|
<emphasis>now</emphasis>!</para>
|
||||||
|
|
||||||
<para>The applications to which FreeBSD can be put are truly limited only
|
<para>The applications to which FreeBSD can be put are truly
|
||||||
by your own imagination. From software development to factory
|
limited only by your own imagination. From software development
|
||||||
automation, inventory control to azimuth correction of remote satellite
|
to factory automation, inventory control to azimuth correction of
|
||||||
antennae; if it can be done with a commercial UNIX product then it is
|
remote satellite antennae; if it can be done with a commercial
|
||||||
more than likely that you can do it with FreeBSD, too! FreeBSD also
|
UNIX product then it is more than likely that you can do it with
|
||||||
benefits significantly from the literally thousands of high quality
|
FreeBSD, too! FreeBSD also benefits significantly from the
|
||||||
applications developed by research centers and universities around the
|
literally thousands of high quality applications developed by
|
||||||
world, often available at little to no cost. Commercial applications are
|
research centers and universities around the world, often
|
||||||
also available and appearing in greater numbers every day.</para>
|
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 FreeBSD itself is generally available,
|
<para>Because the source code for FreeBSD itself is generally
|
||||||
the system can also be customized to an almost unheard of degree for
|
available, the system can also be customized to an almost unheard
|
||||||
special applications or projects, and in ways not generally possible
|
of degree for special applications or projects, and in ways not
|
||||||
with operating systems from most major commercial vendors. Here is just
|
generally possible with operating systems from most major
|
||||||
a sampling of some of the applications in which people are currently
|
commercial vendors. Here is just a sampling of some of the
|
||||||
using FreeBSD:</para>
|
applications in which people are currently using FreeBSD:</para>
|
||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -170,11 +242,13 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>World Wide Web servers (standard or secure [SSL])</para>
|
<para>World Wide Web servers (standard or secure
|
||||||
|
[SSL])</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Firewalls and NAT ("IP masquerading") gateways.</para>
|
<para>Firewalls and NAT (“IP masquerading”)
|
||||||
|
gateways.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
@ -197,198 +271,222 @@
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Education:</emphasis> Are you a student of computer
|
<para><emphasis>Education:</emphasis> Are you a student of
|
||||||
science or a related engineering field? There is no better way of
|
computer science or a related engineering field? There is no
|
||||||
learning about operating systems, computer architecture and
|
better way of learning about operating systems, computer
|
||||||
networking than the hands on, under the hood experience that FreeBSD
|
architecture and networking than the hands on, under the hood
|
||||||
can provide. A number of freely available CAD, mathematical and
|
experience that FreeBSD can provide. A number of freely
|
||||||
graphic design packages also make it highly useful to those whose
|
available CAD, mathematical and graphic design packages also
|
||||||
primary interest in a computer is to get <emphasis>other</emphasis>
|
make it highly useful to those whose primary interest in a
|
||||||
work done!</para>
|
computer is to get <emphasis>other</emphasis> work
|
||||||
|
done!</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Research:</emphasis> With source code for the entire
|
<para><emphasis>Research:</emphasis> With source code for the
|
||||||
system available, FreeBSD is an excellent platform for research in
|
entire system available, FreeBSD is an excellent platform for
|
||||||
operating systems as well as other branches of computer science.
|
research in operating systems as well as other branches of
|
||||||
FreeBSD's freely available nature also makes it possible for remote
|
computer science. FreeBSD's freely available nature also makes
|
||||||
groups to collaborate on ideas or shared development without having
|
it possible for remote groups to collaborate on ideas or
|
||||||
to worry about special licensing agreements or limitations on what
|
shared development without having to worry about special
|
||||||
may be discussed in open forums.</para>
|
licensing agreements or limitations on what may be discussed
|
||||||
|
in open forums.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Networking:</emphasis> Need a new router? A name
|
<para><emphasis>Networking:</emphasis> Need a new router? A
|
||||||
server (DNS)? A firewall to keep people out of your internal
|
name server (DNS)? A firewall to keep people out of your
|
||||||
network? FreeBSD can easily turn that unused 386 or 486 PC sitting
|
internal network? FreeBSD can easily turn that unused 386 or
|
||||||
in the corner into an advanced router with sophisticated packet
|
486 PC sitting in the corner into an advanced router with
|
||||||
filtering capabilities.</para>
|
sophisticated packet filtering capabilities.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>X Window workstation:</emphasis> FreeBSD is a fine
|
<para><emphasis>X Window workstation:</emphasis> FreeBSD is a
|
||||||
choice for an inexpensive X terminal solution, either using the
|
fine choice for an inexpensive X terminal solution, either
|
||||||
freely available XFree86 server or one of the excellent commercial
|
using the freely available XFree86 server or one of the
|
||||||
servers provided by X Inside. Unlike an X terminal, FreeBSD allows
|
excellent commercial servers provided by X Inside. Unlike an
|
||||||
many applications to be run locally, if desired, thus relieving the
|
X terminal, FreeBSD allows many applications to be run
|
||||||
burden on a central server. FreeBSD can even boot
|
locally, if desired, thus relieving the burden on a central
|
||||||
“diskless”, making individual workstations even cheaper
|
server. FreeBSD can even boot “diskless”, making
|
||||||
and easier to administer.</para>
|
individual workstations even cheaper and easier to
|
||||||
|
administer.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para><emphasis>Software Development:</emphasis> The basic FreeBSD
|
<para><emphasis>Software Development:</emphasis> The basic
|
||||||
system comes with a full complement of development tools including
|
FreeBSD system comes with a full complement of development
|
||||||
the renowned GNU C/C++ compiler and debugger.</para>
|
tools including the renowned GNU C/C++ compiler and
|
||||||
|
debugger.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
<para>FreeBSD is available in both source and binary form on CDROM and via
|
<para>FreeBSD is available in both source and binary form on CDROM
|
||||||
anonymous ftp. See <link linkend="mirrors">Obtaining FreeBSD</link>
|
and via anonymous ftp. See <link linkend="mirrors">Obtaining
|
||||||
for more details.</para>
|
FreeBSD</link> for more details.</para>
|
||||||
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="history">
|
<sect1 id="about">
|
||||||
|
<title>About the FreeBSD Project</title>
|
||||||
|
|
||||||
|
<para>The following section provides some background information on
|
||||||
|
the project, including a brief history, project goals, and the
|
||||||
|
development model of the project.</para>
|
||||||
|
|
||||||
|
<sect2 id="history">
|
||||||
<title>A Brief History of FreeBSD</title>
|
<title>A Brief History of FreeBSD</title>
|
||||||
|
|
||||||
<para><emphasis>Contributed by &a.jkh;</emphasis>.</para>
|
<para><emphasis>Contributed by &a.jkh;</emphasis>.</para>
|
||||||
|
|
||||||
<para>The FreeBSD project had its genesis in the early part of 1993,
|
<para>The FreeBSD project had its genesis in the early part of 1993,
|
||||||
partially as an outgrowth of the “Unofficial 386BSD
|
partially as an outgrowth of the “Unofficial 386BSD
|
||||||
Patchkit” by the patchkit's last 3 coordinators: Nate Williams,
|
Patchkit” by the patchkit's last 3 coordinators: Nate
|
||||||
Rod Grimes and myself.</para>
|
Williams, Rod Grimes and myself.</para>
|
||||||
|
|
||||||
<para>Our original goal was to produce an intermediate snapshot of 386BSD
|
<para>Our original goal was to produce an intermediate snapshot of
|
||||||
in order to fix a number of problems with it that the patchkit mechanism
|
386BSD in order to fix a number of problems with it that the
|
||||||
just was not capable of solving. Some of you may remember the early
|
patchkit mechanism just was not capable of solving. Some of you
|
||||||
working title for the project being “386BSD 0.5” or
|
may remember the early working title for the project being
|
||||||
“386BSD Interim” in reference to that fact.</para>
|
“386BSD 0.5” or “386BSD Interim” in
|
||||||
|
reference to that fact.</para>
|
||||||
|
|
||||||
<para>386BSD was Bill Jolitz's operating system, which had been up to that
|
<para>386BSD was Bill Jolitz's operating system, which had been up
|
||||||
point suffering rather severely from almost a year's worth of neglect.
|
to that point suffering rather severely from almost a year's worth
|
||||||
As the patchkit swelled ever more uncomfortably with each passing day,
|
of neglect. As the patchkit swelled ever more uncomfortably with
|
||||||
we were in unanimous agreement that something had to be done and decided
|
each passing day, we were in unanimous agreement that something
|
||||||
to try and assist Bill by providing this interim “cleanup”
|
had to be done and decided to try and assist Bill by providing
|
||||||
snapshot. Those plans came to a rude halt when Bill Jolitz suddenly
|
this interim “cleanup” snapshot. Those plans came to
|
||||||
decided to withdraw his sanction from the project without any clear
|
a rude halt when Bill Jolitz suddenly decided to withdraw his
|
||||||
indication of what would be done instead.</para>
|
sanction from the project without any clear indication of what
|
||||||
|
would be done instead.</para>
|
||||||
|
|
||||||
<para>It did not take us long to decide that the goal remained worthwhile,
|
<para>It did not take us long to decide that the goal remained
|
||||||
even without Bill's support, and so we adopted the name
|
worthwhile, even without Bill's support, and so we adopted the
|
||||||
“FreeBSD”, coined by David Greenman. Our initial objectives
|
name “FreeBSD”, coined by David Greenman. Our initial
|
||||||
were set after consulting with the system's current users and, once it
|
objectives were set after consulting with the system's current
|
||||||
became clear that the project was on the road to perhaps even becoming a
|
users and, once it became clear that the project was on the road
|
||||||
reality, I contacted Walnut Creek CDROM with an eye towards improving
|
to perhaps even becoming a reality, I contacted Walnut Creek CDROM
|
||||||
FreeBSD's distribution channels for those many unfortunates without easy
|
with an eye towards improving FreeBSD's distribution channels for
|
||||||
access to the Internet. Walnut Creek CDROM not only supported the idea
|
those many unfortunates without easy access to the Internet.
|
||||||
of distributing FreeBSD on CD but went so far as to provide the project
|
Walnut Creek CDROM not only supported the idea of distributing
|
||||||
with a machine to work on and a fast Internet connection. Without
|
FreeBSD on CD but went so far as to provide the project with a
|
||||||
Walnut Creek CDROM's almost unprecedented degree of faith in what was,
|
machine to work on and a fast Internet connection. Without Walnut
|
||||||
at the time, a completely unknown project, it is quite unlikely that
|
Creek CDROM's almost unprecedented degree of faith in what was, at
|
||||||
|
the time, a completely unknown project, it is quite unlikely that
|
||||||
FreeBSD would have gotten as far, as fast, as it has today.</para>
|
FreeBSD would have gotten as far, as fast, as it has today.</para>
|
||||||
|
|
||||||
<para>The first CDROM (and general net-wide) distribution was FreeBSD 1.0,
|
<para>The first CDROM (and general net-wide) distribution was
|
||||||
released in December of 1993. This was based on the 4.3BSD-Lite
|
FreeBSD 1.0, released in December of 1993. This was based on the
|
||||||
(“Net/2”) tape from U.C. Berkeley, with many components also
|
4.3BSD-Lite (“Net/2”) tape from U.C. Berkeley, with
|
||||||
provided by 386BSD and the Free Software Foundation. It was a fairly
|
many components also provided by 386BSD and the Free Software
|
||||||
reasonable success for a first offering, and we followed it with the
|
Foundation. It was a fairly reasonable success for a first
|
||||||
highly successful FreeBSD 1.1 release in May of 1994.</para>
|
offering, and we followed it with the highly successful FreeBSD
|
||||||
|
1.1 release in May of 1994.</para>
|
||||||
|
|
||||||
<para>Around this time, some rather unexpected storm clouds formed on the
|
<para>Around this time, some rather unexpected storm clouds formed
|
||||||
horizon as Novell and U.C. Berkeley settled their long-running lawsuit
|
on the horizon as Novell and U.C. Berkeley settled their
|
||||||
over the legal status of the Berkeley Net/2 tape. A condition of that
|
long-running lawsuit over the legal status of the Berkeley Net/2
|
||||||
settlement was U.C. Berkeley's concession that large parts of Net/2 were
|
tape. A condition of that settlement was U.C. Berkeley's
|
||||||
“encumbered” code and the property of Novell, who had in
|
concession that large parts of Net/2 were “encumbered”
|
||||||
turn acquired it from AT&T some time previously. What Berkeley got
|
code and the property of Novell, who had in turn acquired it from
|
||||||
in return was Novell's “blessing” that the 4.4BSD-Lite
|
AT&T some time previously. What Berkeley got in return was
|
||||||
release, when it was finally released, would be declared unencumbered
|
Novell's “blessing” that the 4.4BSD-Lite release, when
|
||||||
and all existing Net/2 users would be strongly encouraged to switch.
|
it was finally released, would be declared unencumbered and all
|
||||||
This included FreeBSD, and the project was given until the end of July
|
existing Net/2 users would be strongly encouraged to switch. This
|
||||||
1994 to stop shipping its own Net/2 based product. Under the terms of
|
included FreeBSD, and the project was given until the end of July
|
||||||
that agreement, the project was allowed one last release before the
|
1994 to stop shipping its own Net/2 based product. Under the
|
||||||
deadline, that release being FreeBSD 1.1.5.1.</para>
|
terms of that agreement, the project was allowed one last release
|
||||||
|
before the deadline, that release being FreeBSD 1.1.5.1.</para>
|
||||||
|
|
||||||
<para>FreeBSD then set about the arduous task of literally re-inventing
|
<para>FreeBSD then set about the arduous task of literally
|
||||||
itself from a completely new and rather incomplete set of 4.4BSD-Lite
|
re-inventing itself from a completely new and rather incomplete
|
||||||
bits. The “Lite” releases were light in part because
|
set of 4.4BSD-Lite bits. The “Lite” releases were
|
||||||
Berkeley's CSRG had removed large chunks of code required for actually
|
light in part because Berkeley's CSRG had removed large chunks of
|
||||||
constructing a bootable running system (due to various legal
|
code required for actually constructing a bootable running system
|
||||||
requirements) and the fact that the Intel port of 4.4 was highly
|
(due to various legal requirements) and the fact that the Intel
|
||||||
incomplete. It took the project until November of 1994 to make this
|
port of 4.4 was highly incomplete. It took the project until
|
||||||
transition, at which point it released FreeBSD 2.0 to the net
|
November of 1994 to make this transition, at which point it
|
||||||
and on CDROM (in late December). Despite being still more than a little
|
released FreeBSD 2.0 to the net and on CDROM (in late December).
|
||||||
rough around the edges, the release was a significant success and was
|
Despite being still more than a little rough around the edges,
|
||||||
followed by the more robust and easier to install FreeBSD 2.0.5 release
|
the release was a significant success and was followed by the
|
||||||
in June of 1995.</para>
|
more robust and easier to install FreeBSD 2.0.5 release in June of
|
||||||
|
1995.</para>
|
||||||
|
|
||||||
<para>We released FreeBSD 2.1.5 in August of 1996, and it appeared to be
|
<para>We released FreeBSD 2.1.5 in August of 1996, and it appeared
|
||||||
popular enough among the ISP and commercial communities that another
|
to be popular enough among the ISP and commercial communities that
|
||||||
release along the 2.1-STABLE branch was merited. This was FreeBSD
|
another release along the 2.1-STABLE branch was merited. This was
|
||||||
2.1.7.1, released in February 1997 and capping the end of mainstream
|
FreeBSD 2.1.7.1, released in February 1997 and capping the end of
|
||||||
development on 2.1-STABLE. Now in maintenance mode, only security
|
mainstream development on 2.1-STABLE. Now in maintenance mode,
|
||||||
enhancements and other critical bug fixes will be done on this branch
|
only security enhancements and other critical bug fixes will be
|
||||||
(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 2.2 was branched from the development mainline
|
||||||
(“-CURRENT”) in November 1996 as the RELENG_2_2 branch, and
|
(“-CURRENT”) in November 1996 as the RELENG_2_2
|
||||||
the first full release (2.2.1) was released in April, 1997. Further
|
branch, and the first full release (2.2.1) was released in April,
|
||||||
releases along the 2.2 branch were done in the Summer and Fall of '97,
|
1997. Further releases along the 2.2 branch were done in the
|
||||||
the last of which (2.2.8) appeared in November, 1998. The first
|
Summer and Fall of '97, the last of which (2.2.8) appeared in
|
||||||
official 3.0 release appeared in October, 1998 and spelled the beginning
|
November, 1998. The first official 3.0 release appeared in
|
||||||
of the end for the 2.2 branch.</para>
|
October, 1998 and spelled the beginning of the end for the 2.2
|
||||||
|
branch.</para>
|
||||||
|
|
||||||
<para>The tree branched again on Jan 20, 1999, leading to the 4.0-CURRENT
|
<para>The tree branched again on Jan 20, 1999, leading to the
|
||||||
and 3.X-STABLE branches. From 3.X-STABLE, 3.1 was released on February
|
4.0-CURRENT and 3.X-STABLE branches. From 3.X-STABLE, 3.1 was
|
||||||
15th, 1999 and 3.2 on May 15, 1999. The most current release on this
|
released on February 15, 1999, 3.2 on May 15, 1999, and 3.3 on
|
||||||
branch is 3.3, which was released on September 16th, 1999.</para>
|
September 16, 1999. The most current release on this branch is
|
||||||
|
&rel.current;, which was released on December 20, 1999.</para>
|
||||||
|
|
||||||
<para>Long term development projects continue to take place in the
|
<para>Long term development projects continue to take place in the
|
||||||
4.0-CURRENT branch, and SNAPshot releases of 4.0 on CDROM (and,
|
4.0-CURRENT branch, and SNAPshot releases of 4.0 on CDROM (and, of
|
||||||
of course, on the net) are continually made available as work
|
course, on the net) are continually made available as work
|
||||||
progresses.</para>
|
progresses.</para>
|
||||||
</sect1>
|
</sect2>
|
||||||
|
|
||||||
<sect1 id="goals">
|
<sect2 id="goals">
|
||||||
<title>FreeBSD Project Goals</title>
|
<title>FreeBSD Project Goals</title>
|
||||||
|
|
||||||
<para><emphasis>Contributed by &a.jkh;</emphasis>.</para>
|
<para><emphasis>Contributed by &a.jkh;</emphasis>.</para>
|
||||||
|
|
||||||
<para>The goals of the FreeBSD Project are to provide software that may be
|
<para>The goals of the FreeBSD Project are to provide software that
|
||||||
used for any purpose and without strings attached. Many of us have a
|
may be used for any purpose and without strings attached. Many of
|
||||||
significant investment in the code (and project) and would certainly not
|
us have a significant investment in the code (and project) and
|
||||||
mind a little financial compensation now and then, but we are definitely
|
would certainly not mind a little financial compensation now and
|
||||||
not prepared to insist on it. We believe that our first and foremost
|
then, but we are definitely not prepared to insist on it. We
|
||||||
“mission” is to provide code to any and all comers, and for
|
believe that our first and foremost “mission” is to
|
||||||
whatever purpose, so that the code gets the widest possible use and
|
provide code to any and all comers, and for whatever purpose, so
|
||||||
provides the widest possible benefit. This is, I believe, one of the
|
that the code gets the widest possible use and provides the widest
|
||||||
most fundamental goals of Free Software and one that we enthusiastically
|
possible benefit. This is, I believe, one of the most fundamental
|
||||||
|
goals of Free Software and one that we enthusiastically
|
||||||
support.</para>
|
support.</para>
|
||||||
|
|
||||||
<para>That code in our source tree which falls under the GNU General Public
|
<para>That code in our source tree which falls under the GNU General
|
||||||
License (GPL) or Library General Public License (LGPL) comes with slightly
|
Public License (GPL) or Library General Public License (LGPL)
|
||||||
more strings attached, though at least on the side of enforced access
|
comes with slightly more strings attached, though at least on the
|
||||||
rather than the usual opposite. Due to the additional complexities that
|
side of enforced access rather than the usual opposite. Due to
|
||||||
can evolve in the commercial use of GPL software we do, however,
|
the additional complexities that can evolve in the commercial use
|
||||||
prefer software submitted under the more relaxed BSD copyright when it's
|
of GPL software we do, however, prefer software submitted under
|
||||||
a reasonable option to do so.</para>
|
the more relaxed BSD copyright when it's a reasonable option to
|
||||||
</sect1>
|
do so.</para>
|
||||||
|
</sect2>
|
||||||
|
|
||||||
<sect1 id="development">
|
<sect2 id="development">
|
||||||
<title>The FreeBSD Development Model</title>
|
<title>The FreeBSD Development Model</title>
|
||||||
|
|
||||||
<para><emphasis>Contributed by &a.asami;</emphasis>.</para>
|
<para><emphasis>Contributed by &a.asami;</emphasis>.</para>
|
||||||
|
|
||||||
<para>The development of FreeBSD is a very open and flexible process,
|
<para>The development of FreeBSD is a very open and flexible
|
||||||
FreeBSD being literally built from the contributions of hundreds of
|
process, FreeBSD being literally built from the contributions of
|
||||||
people around the world, as can be seen from our <link
|
hundreds of people around the world, as can be seen from our
|
||||||
linkend="staff">list of contributors</link>. We are constantly on the
|
<link linkend="staff">list of contributors</link>. We are
|
||||||
lookout for new developers and ideas, and those interested in becoming
|
constantly on the lookout for new developers and ideas, and those
|
||||||
more closely involved with the project need simply contact us at the
|
interested in becoming more closely involved with the project
|
||||||
&a.hackers;. The &a.announce; is also available to those wishing to
|
need simply contact us at the &a.hackers;. The &a.announce; is
|
||||||
make other FreeBSD users aware of major areas of work.</para>
|
also available to those wishing to make other FreeBSD users aware
|
||||||
|
of major areas of work.</para>
|
||||||
|
|
||||||
<para>Useful things to know about the FreeBSD project and its development
|
<para>Useful things to know about the FreeBSD project and its
|
||||||
process, whether working independently or in close cooperation:</para>
|
development process, whether working independently or in close
|
||||||
|
cooperation:</para>
|
||||||
|
|
||||||
<variablelist>
|
<variablelist>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
@ -396,36 +494,39 @@
|
||||||
id="development-cvs-repository"></term>
|
id="development-cvs-repository"></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The central source tree for FreeBSD is maintained by <ulink
|
<para>The central source tree for FreeBSD is maintained by
|
||||||
url="http://www.cyclic.com/cyclic-pages/CVS-sheet.html">CVS</ulink>
|
<ulink url="http://www.cyclic.com/cyclic-pages/CVS-sheet.html">CVS</ulink>
|
||||||
(Concurrent Version System), a freely available source code
|
(Concurrent Version System), a freely available source code
|
||||||
control tool which comes bundled with FreeBSD. The primary <ulink
|
control tool which comes bundled with FreeBSD. The primary
|
||||||
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS
|
<ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS
|
||||||
repository</ulink> resides on a machine in Concord CA, USA from
|
repository</ulink> resides on a machine in Concord CA, USA
|
||||||
where it is replicated to numerous mirror machines throughout the
|
from where it is replicated to numerous mirror machines
|
||||||
world. The CVS tree, as well as the <link
|
throughout the world. The CVS tree, as well as the <link
|
||||||
linkend="current">-CURRENT</link> and <link
|
linkend="current">-CURRENT</link> and <link
|
||||||
linkend="stable">-STABLE</link> trees which are checked out of
|
linkend="stable">-STABLE</link> trees which are checked out
|
||||||
it, can be easily replicated to your own machine as well. Please
|
of it, can be easily replicated to your own machine as well.
|
||||||
refer to the <link linkend="synching">Synchronizing your source
|
Please refer to the <link linkend="synching">Synchronizing
|
||||||
tree</link> section for more information on doing this.</para>
|
your source tree</link> section for more information on
|
||||||
|
doing this.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>The committers list<anchor id="development-committers"></term>
|
<term>The committers list<anchor
|
||||||
|
id="development-committers"></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The <link linkend="staff-committers">committers</link> are the
|
<para>The <link linkend="staff-committers">committers</link>
|
||||||
people who have <emphasis>write</emphasis> access to the CVS tree,
|
are the people who have <emphasis>write</emphasis> access to
|
||||||
and are thus authorized to make modifications to the FreeBSD
|
the CVS tree, and are thus authorized to make modifications
|
||||||
source (the term “committer” comes from the
|
to the FreeBSD source (the term “committer”
|
||||||
&man.cvs.1; <command>commit</command> command, which is used
|
comes from the &man.cvs.1; <command>commit</command>
|
||||||
to bring new changes into the CVS repository). The best way of
|
command, which is used to bring new changes into the CVS
|
||||||
making submissions for review by the committers list is to use the
|
repository). The best way of making submissions for review
|
||||||
&man.send-pr.1; command, though if something appears to be
|
by the committers list is to use the &man.send-pr.1;
|
||||||
jammed in the system then you may also reach them by sending mail
|
command, though if something appears to be jammed in the
|
||||||
to <email>cvs-committers@FreeBSD.org</email>.</para>
|
system then you may also reach them by sending mail to
|
||||||
|
<email>cvs-committers@FreeBSD.org</email>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
|
@ -433,32 +534,32 @@
|
||||||
<term>The FreeBSD core team<anchor id="development-core"></term>
|
<term>The FreeBSD core team<anchor id="development-core"></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The <link linkend="staff-core">FreeBSD core team</link> would
|
<para>The <link linkend="staff-core">FreeBSD core team</link>
|
||||||
be equivalent to the board of directors if the FreeBSD Project
|
would be equivalent to the board of directors if the FreeBSD
|
||||||
were a company. The primary task of the core team is to make sure
|
Project were a company. The primary task of the core team
|
||||||
the project, as a whole, is in good shape and is heading in the
|
is to make sure the project, as a whole, is in good shape
|
||||||
right directions. Inviting dedicated and responsible developers
|
and is heading in the right directions. Inviting dedicated
|
||||||
to join our group of committers is one of the functions of the
|
and responsible developers to join our group of committers
|
||||||
core team, as is the recruitment of new core team members as
|
is one of the functions of the core team, as is the
|
||||||
others move on. Most current members of the core team started as
|
recruitment of new core team members as others move on. Most
|
||||||
committers whose addiction to the project got the better of
|
current members of the core team started as committers whose
|
||||||
them.</para>
|
addiction to the project got the better of them.</para>
|
||||||
|
|
||||||
<para>Some core team members also have specific <link
|
<para>Some core team members also have specific <link
|
||||||
linkend="staff-who">areas of responsibility</link>, meaning that
|
linkend="staff-who">areas of responsibility</link>, meaning
|
||||||
they are committed to ensuring that some large portion of the
|
that they are committed to ensuring that some large portion
|
||||||
system works as advertised.</para>
|
of the system works as advertised.</para>
|
||||||
|
|
||||||
<note>
|
<note>
|
||||||
<para>Most members of the core team are volunteers when it comes
|
<para>Most members of the core team are volunteers when it
|
||||||
to FreeBSD development and do not benefit from the project
|
comes to FreeBSD development and do not benefit from the
|
||||||
financially, so “commitment” should also not be
|
project financially, so “commitment” should
|
||||||
misconstrued as meaning “guaranteed support.” The
|
also not be misconstrued as meaning “guaranteed
|
||||||
“board of directors” analogy above is not actually
|
support.” The “board of directors”
|
||||||
very accurate, and it may be more suitable to say that these are
|
analogy above is not actually very accurate, and it may be
|
||||||
the people who gave up their lives in favor of FreeBSD against
|
more suitable to say that these are the people who gave up
|
||||||
their better judgement! <!-- smiley
|
their lives in favor of FreeBSD against their better
|
||||||
--><emphasis>;-)</emphasis></para>
|
judgement! <!-- smiley --><emphasis>;-)</emphasis></para>
|
||||||
</note>
|
</note>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
@ -469,89 +570,93 @@
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Last, but definitely not least, the largest group of
|
<para>Last, but definitely not least, the largest group of
|
||||||
developers are the users themselves who provide feedback and
|
developers are the users themselves who provide feedback and
|
||||||
bug-fixes to us on an almost constant basis. The primary way of
|
bug-fixes to us on an almost constant basis. The primary
|
||||||
keeping in touch with FreeBSD's more non-centralized development
|
way of keeping in touch with FreeBSD's more non-centralized
|
||||||
is to subscribe to the &a.hackers; (see <link
|
development is to subscribe to the &a.hackers; (see <link
|
||||||
linkend="eresources-mail">mailing list info</link>) where such
|
linkend="eresources-mail">mailing list info</link>) where
|
||||||
things are discussed.</para>
|
such things are discussed.</para>
|
||||||
|
|
||||||
<para><link linkend="contrib-additional">The list</link> of those
|
<para><link linkend="contrib-additional">The list</link> of
|
||||||
who have contributed something which made its way into our source
|
those who have contributed something which made its way into
|
||||||
tree is a long and growing one, so why not join it by contributing
|
our source tree is a long and growing one, so why not join
|
||||||
something back to FreeBSD today? <!-- smiley
|
it by contributing something back to FreeBSD today?
|
||||||
--><emphasis>:-)</emphasis></para>
|
<!-- smiley --><emphasis>:-)</emphasis></para>
|
||||||
|
|
||||||
<para>Providing code is not the only way of contributing to the
|
<para>Providing code is not the only way of contributing to
|
||||||
project; for a more complete list of things that need doing,
|
the project; for a more complete list of things that need
|
||||||
please refer to the <link linkend="contrib">how to
|
doing, please refer to the <link linkend="contrib">how to
|
||||||
contribute</link> section in this handbook.</para>
|
contribute</link> section in this handbook.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
</variablelist>
|
</variablelist>
|
||||||
|
|
||||||
<para>In summary, our development model is organized as a loose set of
|
<para>In summary, our development model is organized as a loose set
|
||||||
concentric circles. The centralized model is designed for the
|
of concentric circles. The centralized model is designed for the
|
||||||
convenience of the <emphasis>users</emphasis> of FreeBSD, who are
|
convenience of the <emphasis>users</emphasis> of FreeBSD, who are
|
||||||
thereby provided with an easy way of tracking one central code base, not
|
thereby provided with an easy way of tracking one central code
|
||||||
to keep potential contributors out! Our desire is to present a stable
|
base, not to keep potential contributors out! Our desire is to
|
||||||
operating system with a large set of coherent <link
|
present a stable operating system with a large set of coherent
|
||||||
linkend="ports">application programs</link> that the users can easily
|
<link linkend="ports">application programs</link> that the users
|
||||||
install and use, and this model works very well in accomplishing
|
can easily install and use, and this model works very well in
|
||||||
that.</para>
|
accomplishing that.</para>
|
||||||
|
|
||||||
<para>All we ask of those who would join us as FreeBSD developers is some
|
<para>All we ask of those who would join us as FreeBSD developers is
|
||||||
of the same dedication its current people have to its continued
|
some of the same dedication its current people have to its
|
||||||
success!</para>
|
continued success!</para>
|
||||||
</sect1>
|
</sect2>
|
||||||
|
|
||||||
<sect1 id="relnotes">
|
<sect2 id="relnotes">
|
||||||
<title>About the Current Release</title>
|
<title>The Current FreeBSD Release</title>
|
||||||
|
|
||||||
<para>FreeBSD is a freely available, full source 4.4BSD-Lite2 based release
|
<para>FreeBSD is a freely available, full source 4.4BSD-Lite2 based
|
||||||
for Intel i386/i486/Pentium/PentiumPro/Celeron/Pentium II/Pentium III (or
|
release for Intel i386, i486, Pentium, Pentium Pro, Celeron,
|
||||||
compatible) and DEC Alpha based computer systems. It is based primarily
|
Pentium II, Pentium III (or compatible) and DEC Alpha based computer
|
||||||
on software from U.C. Berkeley's CSRG group, with some enhancements from
|
systems. It is based primarily on software from U.C. Berkeley's
|
||||||
NetBSD, OpenBSD, 386BSD, and the Free Software Foundation.</para>
|
CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and
|
||||||
|
the Free Software Foundation.</para>
|
||||||
|
|
||||||
<para>Since our release of FreeBSD 2.0 in late 94, the performance,
|
<para>Since our release of FreeBSD 2.0 in late 94, the performance,
|
||||||
feature set, and stability of FreeBSD has improved dramatically. The
|
feature set, and stability of FreeBSD has improved dramatically.
|
||||||
largest change is a revamped virtual memory system with a merged VM/file
|
The largest change is a revamped virtual memory system with a merged
|
||||||
buffer cache that not only increases performance, but reduces FreeBSD's
|
VM/file buffer cache that not only increases performance, but
|
||||||
memory footprint, making a 5MB configuration a more acceptable minimum.
|
reduces FreeBSD's memory footprint, making a 5MB configuration a
|
||||||
Other enhancements include full NIS client and server support,
|
more acceptable minimum. Other enhancements include full NIS client
|
||||||
transaction TCP support, dial-on-demand PPP, integrated DHCP support,
|
and server support, transaction TCP support, dial-on-demand PPP,
|
||||||
an improved SCSI subsystem, ISDN support, support for ATM, FDDI, Fast
|
integrated DHCP support, an improved SCSI subsystem, ISDN support,
|
||||||
and Gigabit Ethernet (1000Mbit) adapters, improved support for the latest
|
support for ATM, FDDI, Fast and Gigabit Ethernet (1000Mbit)
|
||||||
Adaptec controllers and many hundreds of bug fixes.</para>
|
adapters, improved support for the latest Adaptec controllers and
|
||||||
|
many hundreds of bug fixes.</para>
|
||||||
|
|
||||||
<para>We have also taken the comments and suggestions of many of our users
|
<para>We have also taken the comments and suggestions of many of our
|
||||||
to heart and have attempted to provide what we hope is a more sane and
|
users to heart and have attempted to provide what we hope is a more
|
||||||
easily understood installation process. Your feedback on this
|
sane and easily understood installation process. Your feedback on
|
||||||
(constantly evolving) process is especially welcome!</para>
|
this (constantly evolving) process is especially welcome!</para>
|
||||||
|
|
||||||
<para>In addition to the base distributions, FreeBSD offers a new ported
|
<para>In addition to the base distributions, FreeBSD offers a new
|
||||||
software collection with hundreds of commonly sought-after programs. By
|
ported software collection with hundreds of commonly sought-after
|
||||||
mid-November 1999, there were nearly 2800 ports! The list of
|
programs. By mid-January 2000, there were nearly 3000 ports! The
|
||||||
ports ranges from http (WWW) servers, to games, languages, editors and
|
list of ports ranges from http (WWW) servers, to games, languages,
|
||||||
almost everything in between. The entire ports collection requires
|
editors and almost everything in between. The entire ports
|
||||||
approximately 50MB of storage, all ports being expressed as
|
collection requires approximately 50MB of storage, all ports being
|
||||||
“deltas” to their original sources. This makes it much
|
expressed as “deltas” to their original sources. This
|
||||||
easier for us to update ports, and greatly reduces the disk space
|
makes it much easier for us to update ports, and greatly reduces
|
||||||
demands made by the older 1.0 ports collection. To compile a port, you
|
the disk space demands made by the older 1.0 ports collection. To
|
||||||
simply change to the directory of the program you wish to install, type
|
compile a port, you simply change to the directory of the program
|
||||||
<command>make install</command>, and let the system do the rest. The
|
you wish to install, type <command>make install</command>, and let
|
||||||
full original distribution for each port you build is retrieved
|
the system do the rest. The full original distribution for each
|
||||||
dynamically off the CDROM or a local ftp site, so you need only enough
|
port you build is retrieved dynamically off the CDROM or a local ftp
|
||||||
disk space to build the ports you want. (Almost) every port is also
|
site, so you need only enough disk space to build the ports you
|
||||||
provided as a pre-compiled “package” which can be installed
|
want. Almost every port is also provided as a pre-compiled
|
||||||
with a simple command (pkg_add) by those who do not wish to compile
|
“package” which can be installed with a simple command
|
||||||
their own ports from source.</para>
|
(pkg_add) by those who do not wish to compile their own ports from
|
||||||
|
source.</para>
|
||||||
|
|
||||||
<para>A number of additional documents which you may find very helpful in
|
<para>A number of additional documents which you may find very helpful
|
||||||
the process of installing and using FreeBSD may now also be found in the
|
in the process of installing and using FreeBSD may now also be found
|
||||||
<filename>/usr/share/doc</filename> directory on any machine running
|
in the <filename>/usr/share/doc</filename> directory on any machine
|
||||||
FreeBSD 2.1 or later. You may view the locally installed manuals with
|
running FreeBSD 2.1 or later. You may view the locally installed
|
||||||
any HTML capable browser using the following URLs:</para>
|
manuals with any HTML capable browser using the following
|
||||||
|
URLs:</para>
|
||||||
|
|
||||||
<variablelist>
|
<variablelist>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
@ -577,22 +682,23 @@
|
||||||
copies at <ulink
|
copies at <ulink
|
||||||
url="http://www.FreeBSD.org/">http://www.FreeBSD.org/</ulink>.</para>
|
url="http://www.FreeBSD.org/">http://www.FreeBSD.org/</ulink>.</para>
|
||||||
|
|
||||||
<para>The core of FreeBSD does not contain DES code which would inhibit
|
<para>The core of FreeBSD does not contain DES code which would
|
||||||
its being exported outside the United States. There is an add-on
|
inhibit its being exported outside the United States. There is an
|
||||||
package to the core distribution, for use only in the United States,
|
add-on package to the core distribution, for use only in the United
|
||||||
that contains the programs that normally use DES. The auxiliary
|
States, that contains the programs that normally use DES. The
|
||||||
packages provided separately can be used by anyone. A freely (from
|
auxiliary packages provided separately can be used by anyone. A
|
||||||
outside the U.S.) exportable European distribution of DES for our
|
freely (from outside the U.S.) exportable European distribution of
|
||||||
non-U.S. users also exists and is described in the <ulink
|
DES for our non-U.S. users also exists and is described in the
|
||||||
url="../FAQ/FAQ.html">FreeBSD FAQ</ulink>.</para>
|
<ulink url="../FAQ/FAQ.html">FreeBSD FAQ</ulink>.</para>
|
||||||
|
|
||||||
<para>If password security for FreeBSD is all you need, and you have no
|
<para>If password security for FreeBSD is all you need, and you have
|
||||||
requirement for copying encrypted passwords from different hosts (Suns,
|
no requirement for copying encrypted passwords from different hosts
|
||||||
DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5
|
(Suns, DEC machines, etc) into FreeBSD password entries, then
|
||||||
based security may be all you require! We feel that our default security
|
FreeBSD's MD5 based security may be all you require! We feel that
|
||||||
model is more than a match for DES, and without any messy export issues
|
our default security model is more than a match for DES, and without
|
||||||
to deal with. If you are outside (or even inside) the U.S., give it a
|
any messy export issues to deal with. If you are outside (or even
|
||||||
try!</para>
|
inside) the U.S., give it a try!</para>
|
||||||
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
</chapter>
|
</chapter>
|
||||||
|
|
||||||
|
|
@ -606,4 +712,3 @@
|
||||||
sgml-parent-document: ("../book.sgml" "part" "chapter")
|
sgml-parent-document: ("../book.sgml" "part" "chapter")
|
||||||
End:
|
End:
|
||||||
-->
|
-->
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue