history.html

FreeBSD操作系统的详细使用手册

target="_top">CVS</a> (Concurrent Versions System), a freely available source code
control tool that comes bundled with FreeBSD. The primary <a
href="http://www.FreeBSD.org/cgi/cvsweb.cgi" target="_top">CVS repository</a> resides on
a machine in Santa Clara CA, USA from where it is replicated to numerous mirror machines
throughout the world. The CVS tree, which contains the <a
href="current-stable.html#CURRENT">-CURRENT</a> and <a
href="current-stable.html#STABLE">-STABLE</a> trees, can all be easily replicated to your
own machine as well. Please refer to the <a href="synching.html">Synchronizing your
source tree</a> section for more information on doing this.</p>
</dd>

<dt>The committers list<a id="DEVELOPMENT-COMMITTERS"
name="DEVELOPMENT-COMMITTERS"></a></dt>

<dd>
<p>The <i class="FIRSTTERM">committers</i> are the people who have <span
class="emphasis"><i class="EMPHASIS">write</i></span> access to the CVS tree, and are
authorized to make modifications to the FreeBSD source (the term ``committer'' comes from
the <a href="http://www.FreeBSD.org/cgi/man.cgi?query=cvs&sektion=1"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">cvs</span>(1)</span></a> <tt
class="COMMAND">commit</tt> command, which is used to bring new changes into the CVS
repository). The best way of making submissions for review by the committers list is to
use the <a href="http://www.FreeBSD.org/cgi/man.cgi?query=send-pr&sektion=1"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">send-pr</span>(1)</span></a> command. If
something appears to be jammed in the system, then you may also reach them by sending
mail to the FreeBSD committer's mailing list.</p>
</dd>

<dt>The FreeBSD core team<a id="DEVELOPMENT-CORE" name="DEVELOPMENT-CORE"></a></dt>

<dd>
<p>The <i class="FIRSTTERM">FreeBSD core team</i> would be equivalent to the board of
directors if the FreeBSD Project were a company. The primary task of the core team is to
make sure the project, as a whole, is in good shape and is heading in the right
directions. Inviting dedicated and responsible developers to join our group of committers
is one of the functions of the core team, as is the recruitment of new core team members
as others move on. The current core team was elected from a pool of committer candidates
in July 2004. Elections are held every 2 years.</p>

<p>Some core team members also have specific areas of responsibility, meaning that they
are committed to ensuring that some large portion of the system works as advertised. For
a complete list of FreeBSD developers and their areas of responsibility, please see the
<a href="../../../../doc/en_US.ISO8859-1/articles/contributors/article.html"
target="_top">Contributors List</a></p>

<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Most members of the core team are volunteers when it comes to FreeBSD
development and do not benefit from the project financially, so ``commitment'' should
also not be misconstrued as meaning ``guaranteed support.'' The ``board of directors''
analogy above is not very accurate, and it may be more suitable to say that these are the
people who gave up their lives in favor of FreeBSD against their better judgment!</p>
</blockquote>
</div>
</dd>

<dt>Outside contributors</dt>

<dd>
<p>Last, but definitely not least, the largest group of developers are the users
themselves who provide feedback and bug fixes to us on an almost constant basis. The
primary way of keeping in touch with FreeBSD's more non-centralized development is to
subscribe to the <a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hackers"
target="_top">FreeBSD technical discussions mailing list</a> where such things are
discussed. See <a href="eresources.html">Appendix C</a> for more information about the
various FreeBSD mailing lists.</p>

<p><i class="CITETITLE"><a
href="../../../../doc/en_US.ISO8859-1/articles/contributors/article.html"
target="_top">The FreeBSD Contributors List</a></i> is a long and growing one, so why not
join it by contributing something back to FreeBSD today?</p>

<p>Providing code is not the only way of contributing to the project; for a more complete
list of things that need doing, please refer to the <a href="../../../../index.html"
target="_top">FreeBSD Project web site</a>.</p>
</dd>
</dl>
</div>

<p>In summary, our development model is organized as a loose set of concentric circles.
The centralized model is designed for the convenience of the <span class="emphasis"><i
class="EMPHASIS">users</i></span> of FreeBSD, who are provided with an easy way of
tracking one central code base, not to keep potential contributors out! Our desire is to
present a stable operating system with a large set of coherent <a
href="ports.html">application programs</a> that the users can easily install and use --
this model works very well in accomplishing that.</p>

<p>All we ask of those who would join us as FreeBSD developers is some of the same
dedication its current people have to its continued success!</p>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="RELNOTES" name="RELNOTES">1.3.4 The Current FreeBSD
Release</a></h2>

<p>FreeBSD is a freely available, full source 4.4BSD-Lite based release for Intel <span
class="TRADEMARK">i386</span>&#8482;, <span class="TRADEMARK">i486</span>&#8482;, <span
class="TRADEMARK">Pentium</span>&reg;, <span class="TRADEMARK">Pentium</span>&nbsp;Pro,
<span class="TRADEMARK">Celeron</span>&reg;, <span
class="TRADEMARK">Pentium</span>&nbsp;II, <span
class="TRADEMARK">Pentium</span>&nbsp;III, <span class="TRADEMARK">Pentium</span>&nbsp;4
(or compatible), <span class="TRADEMARK">Xeon</span>&#8482;, DEC <span
class="TRADEMARK">Alpha</span>&#8482; and Sun <span class="TRADEMARK">UltraSPARC</span>
based computer systems. It is based primarily on software from U.C. Berkeley's CSRG
group, with some enhancements from NetBSD, OpenBSD, 386BSD, and the Free Software
Foundation.</p>

<p>Since our release of FreeBSD&nbsp;2.0 in late 94, the performance, feature set, and
stability of FreeBSD has improved dramatically. The largest change is a revamped virtual
memory system with a merged VM/file buffer cache that not only increases performance, but
also reduces FreeBSD's memory footprint, making a 5&nbsp;MB configuration a more
acceptable minimum. Other enhancements include full NIS client and server support,
transaction TCP support, dial-on-demand PPP, integrated DHCP support, an improved SCSI
subsystem, ISDN support, support for ATM, FDDI, Fast and Gigabit Ethernet
(1000&nbsp;Mbit) adapters, improved support for the latest Adaptec controllers, and many
thousands of bug fixes.</p>

<p>In addition to the base distributions, FreeBSD offers a ported software collection
with thousands of commonly sought-after programs. At the time of this printing, there
were over 10,500 ports! The list of ports ranges from http (WWW) servers, to games,
languages, editors, and almost everything in between. The entire ports collection
requires approximately 300&nbsp;MB of storage, all ports being expressed as ``deltas'' to
their original sources. This makes it much easier for us to update ports, and greatly
reduces the disk space demands made by the older 1.0 ports collection. To compile a port,
you simply change to the directory of the program you wish to install, type <tt
class="COMMAND">make install</tt>, and let the system do the rest. The full original
distribution for each port you build is retrieved dynamically off the CDROM or a local
FTP site, so you need only enough disk space to build the ports you want. Almost every
port is also provided as a pre-compiled ``package'', which can be installed with a simple
command (<tt class="COMMAND">pkg_add</tt>) by those who do not wish to compile their own
ports from source. More information on packages and ports can be found in <a
href="ports.html">Chapter 4</a>.</p>

<p>A number of additional documents which you may find very helpful in the process of
installing and using FreeBSD may now also be found in the <tt
class="FILENAME">/usr/share/doc</tt> directory on any recent FreeBSD machine. You may
view the locally installed manuals with any HTML capable browser using the following
URLs:</p>

<div class="VARIABLELIST">
<dl>
<dt>The FreeBSD Handbook</dt>

<dd>
<p><a href="file://localhost/usr/share/doc/handbook/index.html" target="_top"><tt
class="FILENAME">/usr/share/doc/handbook/index.html</tt></a></p>
</dd>

<dt>The FreeBSD FAQ</dt>

<dd>
<p><a href="file://localhost/usr/share/doc/faq/index.html" target="_top"><tt
class="FILENAME">/usr/share/doc/faq/index.html</tt></a></p>
</dd>
</dl>
</div>

<p>You can also view the master (and most frequently updated) copies at <a
href="../../../../index.html" target="_top">http://www.FreeBSD.org/</a>.</p>
</div>
</div>

<div class="NAVFOOTER">
<hr align="LEFT" width="100%" />
<table summary="Footer navigation table" width="100%" border="0" cellpadding="0"
cellspacing="0">
<tr>
<td width="33%" align="left" valign="top"><a href="nutshell.html"
accesskey="P">Prev</a></td>
<td width="34%" align="center" valign="top"><a href="index.html"
accesskey="H">Home</a></td>
<td width="33%" align="right" valign="top"><a href="install.html"
accesskey="N">Next</a></td>
</tr>

<tr>
<td width="33%" align="left" valign="top">Welcome to FreeBSD!</td>
<td width="34%" align="center" valign="top"><a href="introduction.html"
accesskey="U">Up</a></td>
<td width="33%" align="right" valign="top">Installing FreeBSD</td>
</tr>
</table>
</div>

<p align="center"><small>This, and other documents, can be downloaded from <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/</a>.</small></p>

<p align="center"><small>For questions about FreeBSD, read the <a
href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
href="mailto:[e-mail]">[e-mail]</a>&#62;.<br />
For questions about this documentation, e-mail &#60;<a
href="mailto:[e-mail]">[e-mail]</a>&#62;.</small></p>
</body>
</html>