Stage HTML renditions of the 5.0-DP2 release documentation, not hooked

up to the Web site build yet.
This commit is contained in:
Bruce A. Mah 2002-11-16 23:51:22 +00:00
parent b1d7e40981
commit fb282542a3
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=14923
19 changed files with 42243 additions and 0 deletions

View file

@ -0,0 +1,161 @@
/*
* Copyright (c) 2001 The FreeBSD Documentation Project
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* $FreeBSD: doc/share/misc/docbook.css,v 1.4 2001/07/11 12:46:50 nik Exp $
*/
BODY ADDRESS {
line-height: 1.3;
margin: .6em 0;
}
BODY BLOCKQUOTE {
margin-top: .75em;
line-height: 1.5;
margin-bottom: .75em;
}
HTML BODY {
margin: 1em 8% 1em 10%;
line-height: 1.2;
}
.LEGALNOTICE {
font-size: small;
font-variant: small-caps;
}
BODY DIV {
margin: 0;
}
DL {
margin: .8em 0;
line-height: 1.2;
}
BODY FORM {
margin: .6em 0;
}
H1, H2, H3, H4, H5, H6,
DIV.EXAMPLE P B,
.QUESTION,
DIV.TABLE P B,
DIV.PROCEDURE P B {
color: #990000;
}
BODY H1 {
margin: .8em 0 0 -4%;
line-height: 1.3;
}
BODY H2 {
margin: .8em 0 0 -4%;
line-height: 1.3;
}
BODY H3 {
margin: .8em 0 0 -3%;
line-height: 1.3;
}
BODY H4 {
margin: .8em 0 0 -3%;
line-height: 1.3;
}
BODY H5 {
margin: .8em 0 0 -2%;
line-height: 1.3;
}
BODY H6 {
margin: .8em 0 0 -1%;
line-height: 1.3;
}
BODY HR {
margin: .6em
}
BODY IMG.NAVHEADER {
margin: 0 0 0 -4%;
}
OL {
margin: 0 0 0 5%;
line-height: 1.2;
}
BODY P {
margin: .6em 0;
line-height: 1.2;
}
BODY PRE {
margin: .75em 0;
line-height: 1.0;
color: #461b7e;
}
BODY TD {
line-height: 1.2
}
BODY TH {
line-height: 1.2;
}
UL, BODY DIR, BODY MENU {
margin: 0 0 0 5%;
line-height: 1.2;
}
HTML {
margin: 0;
padding: 0;
}
.FILENAME {
color: #007a00;
}
BODY H1, BODY H2, BODY H3, BODY H4, BODY H5, BODY H6 {
margin-left: 0
}
.GUIMENU, .GUIMENUITEM, .GUISUBMENU,
.GUILABEL, .INTERFACE, .GUIBUTTON,
.SHORTCUT, .SHORTCUT .KEYCAP {
background-color: #F0F0F0;
}
.ACCEL {
background-color: #F0F0F0;
text-decoration: underline;
}

View file

@ -0,0 +1,486 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>Early Adopter's Guide to FreeBSD 5.0-RELEASE</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.73 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">Early Adopter's Guide to
FreeBSD 5.0-RELEASE</a></h1>
<div class="AUTHORGROUP">
<a name="AEN4"></a>
<h3 class="CORPAUTHOR">The FreeBSD Release Engineering
Team</h3>
</div>
<p class="COPYRIGHT">Copyright &copy; 2002 by The FreeBSD
Release Engineering Team</p>
<p class="PUBDATE">$FreeBSD:
src/release/doc/en_US.ISO8859-1/early-adopter/article.sgml,v
1.5 2002/11/03 22:06:48 ceri Exp $<br>
</p>
<hr>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN10">1 Introduction</a></h1>
<p>FreeBSD 5.0 marks the first new major version of FreeBSD
in over two years. Besides a number of new features, it
also contains a number of major developments in the
underlying system architecture. Along with these advances,
however, comes a system that incorporates a tremendous
amount of new and not-widely-tested code. Compared to the
existing line of 4.<tt class="REPLACEABLE"><i>X</i></tt>
releases, 5.0 may have regressions in areas of stability,
performance, and occasionally functionality.</p>
<p>For these reasons, the Release Engineering Team <tt
class="EMAIL">&#60;<a href=
"mailto:re@FreeBSD.org">re@FreeBSD.org</a>&#62;</tt> does
<span class="emphasis"><i class="EMPHASIS">not</i></span>
encourage users to blindly update from older FreeBSD
releases to 5.0. Specifically, for more conservative users,
we recommend running 4.<tt class=
"REPLACEABLE"><i>X</i></tt> releases (such as 4.7-RELEASE
or the upcoming 4.8-RELEASE) for the near-term future. We
feel that such users are probably best served by upgrading
to 5.<tt class="REPLACEABLE"><i>X</i></tt> only after a
5-STABLE development branch has been created; this may be
around the time of 5.1-RELEASE or 5.2-RELEASE.</p>
<p>(FreeBSD 5.0 suffers from what has been described as a
``chicken and egg'' problem. The entire project has a goal
of producing a 5.0-RELEASE that is as stable and reliable
as possible. This stability and reliability requires
widespread testing, particularly of the system's newer
features. However, getting a large number of users to test
the system, in a practical sense, means building and
distributing a release first!)</p>
<p>This article describes some of the issues involved in
installing and running FreeBSD 5.0-RELEASE. We begin with a
brief overview of the FreeBSD release process. We then
present some of the more noteworthy new features in FreeBSD
5.0, along with some areas that may prove troublesome for
unwary users. For those users choosing to remain with
4-STABLE-based releases, we give some of the short- to
medium-term plans for this development branch. Finally, we
present some notes on upgrading existing 4.<tt class=
"REPLACEABLE"><i>X</i></tt> systems to 5.0.</p>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN23">2 An Overview of the
FreeBSD Release Process</a></h1>
<p>FreeBSD employs a model of development that relies on
multiple development branches within the source code
repository. The main branch is called ``CURRENT'', and is
referred to in the CVS repository with the <tt class=
"LITERAL">HEAD</tt> tag. New features are committed first
to this branch; although this means that CURRENT is the
first to see new functionality, it also means that it
occasionally suffers from breakages as new features are
added and debugged.</p>
<p>Most FreeBSD releases are made from one of several
``STABLE'' branches. Features are only added to these
branches after some amount of testing in CURRENT. At the
moment, only one STABLE branch is under active development;
this branch is referred to as ``4-STABLE'', and all of the
FreeBSD 4.<tt class="REPLACEABLE"><i>X</i></tt> releases
were based on it. This branch has the tag <tt class=
"LITERAL">RELENG_4</tt> in the CVS repository.</p>
<p>FreeBSD 5.0 will be based on the CURRENT branch. This
will be the first release from this branch in over two
years (the last was FreeBSD 4.0, in March 2000).</p>
<p>At some point after the release of FreeBSD 5.0, a
``5-STABLE'' branch will be created in the FreeBSD CVS
repository with the branch tag <tt class=
"LITERAL">RELENG_5</tt>. The past two stable branches
(3-STABLE and 4-STABLE) were created immediately after
their respective ``dot-oh'' releases (3.0 and 4.0,
respectively). In hindsight, this practice did not give
sufficient time for either CURRENT or the new STABLE
branches to stabilize after the new branches were
created.</p>
<p>Therefore, the release engineering team will only create
the 5-STABLE branch in the CVS repository after they have
found a relatively stable state to use as its basis. It is
likely that there will be multiple releases in the 5.<tt
class="REPLACEABLE"><i>X</i></tt> series before this
happens; we estimate that the 5-STABLE branch will be
created sometime after 5.1-RELEASE or 5.2-RELEASE.</p>
<p>More information on FreeBSD release engineering
processes can be found on the <a href=
"http://www.FreeBSD.org/releng/index.html" target=
"_top">Release Engineering Web pages</a> and in the FreeBSD
<a href=
"http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.html"
target="_top">Release Engineering</a> article.</p>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN43">3 New Features</a></h1>
<p>A large attraction of FreeBSD 5.0 is a number of new
features. These new features and functionality generally
involve large architectural changes that were not feasible
to port back to the FreeBSD 4-STABLE development branch.
(By contrast, many self-contained enhancements, such as new
device drivers or userland utilities, have already been
ported.) A brief, but not exhaustive list includes:</p>
<ul>
<li>
<p>SMPng: The ``next generation'' support for SMP
machines (work in progress). There is now partial
support for multiple processors to be running in the
kernel at the same time.</p>
</li>
<li>
<p>KSE: Kernel Scheduled Entities allow a single
process to have multiple kernel-level threads, similar
to Scheduler Activations.</p>
</li>
<li>
<p>New architectures: Support for the sparc64 and ia64
architectures, in addition to the i386, pc98, and
alpha.</p>
</li>
<li>
<p>GCC: The compiler toolchain is now based on GCC
3.<tt class="REPLACEABLE"><i>X</i></tt>, rather than
GCC 2.95.<tt class="REPLACEABLE"><i>X</i></tt>.</p>
</li>
<li>
<p>MAC: Support for extensible, loadable Mandatory
Access Control policies.</p>
</li>
<li>
<p>GEOM: A flexible framework for transformations of
disk I/O requests. An experimental disk encryption
facility has been developed based on GEOM.</p>
</li>
<li>
<p>FFS: The FFS filesystem now supports background <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fsck&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fsck</span>(8)</span></a> operations
(for faster crash recovery) and filesystem
snapshots.</p>
</li>
<li>
<p>UFS2: A new UFS2 on-disk format has been added,
which supports extended per-file attributes and larger
file sizes.</p>
</li>
<li>
<p>Cardbus: Support for Cardbus devices.</p>
</li>
</ul>
<p>A more comprehensive list of new features can be found
in the release notes for FreeBSD 5.0.</p>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN72">4 Drawbacks to Early
Adoption</a></h1>
<p>Along with the new features of FreeBSD 5.0 come some
areas that can cause problems, or at least can lead to
unexpected behavior. Generally, these come from the fact
that a number of features are works-in-progress. A partial
list of these areas of difficulty includes:</p>
<ul>
<li>
<p>A number of features are not yet finished. Examples
from the feature list above include SMPng and KSE.</p>
</li>
<li>
<p>Because of changes in kernel data structures and
ABIs/APIs, third-party binary device drivers will
require modifications to work correctly under FreeBSD
5.0.</p>
</li>
<li>
<p>Several parts of FreeBSD's base system functionality
have been moved to the Ports Collection. Notable
examples include <b class="APPLICATION">Perl</b>, <b
class="APPLICATION">UUCP</b>, and most (but not all)
games. While these programs are still supported, their
removal from the base system may cause some
confusion.</p>
</li>
<li>
<p>A number of ports and packages do not build or do
not run correctly under FreeBSD 5.0, whereas they did
under FreeBSD 4-STABLE. Generally these problems are
caused by compiler toolchain changes or cleanups of
header files.</p>
</li>
<li>
<p>Because FreeBSD 5.0 is the first release from the
CURRENT branch in over two years, many of its features
are seeing wide exposure for the first time. Many of
these features (such as SMPng) have broad impacts on
the kernel.</p>
</li>
<li>
<p>A certain amount of debugging and diagnostic code is
still in place to help track down problems in FreeBSD
5.0's new features. This may cause FreeBSD 5.0 to
perform more slowly than 4-STABLE.</p>
</li>
<li>
<p>Features are only added to the 4-STABLE development
branch after a ``settling time'' in -CURRENT. FreeBSD
5.0 does not have the stabilizing influence of a
-STABLE branch. (It is likely that the 5-STABLE
development branch will be created sometime after
5.1-RELEASE or 5.2-RELEASE.)</p>
</li>
</ul>
<p>Because a number of these drawbacks affect system
stability, the release engineering team recommends that
more conservative sites and users stick to releases based
on the 4-STABLE branch until the 5.<tt class=
"REPLACEABLE"><i>X</i></tt> series is more polished.</p>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN95">5 Plans for the 4-STABLE
Branch</a></h1>
<p>The release of FreeBSD 5.0 does not mean the end of the
4-STABLE branch. There will be at least one more release on
this branch, namely 4.8-RELEASE, currently scheduled for 1
February 2003.</p>
<p>As of this writing, the release engineering team has no
definite plans for future releases (past 4.8) on the
4-STABLE branch. However, a 4.9-RELEASE or even a
4.10-RELEASE are likely possibilities. Any future releases
from this branch will depend on several factors. The most
important of these is the existence and stability of the
5-STABLE branch. If CURRENT is not sufficiently stable to
allow the creation of a 5-STABLE branch, this may require
and permit more releases from the 4-STABLE branch. Until
the last declared release on the 4-STABLE branch, new
features may be merged from HEAD at the discretion of
developers, subject to existing release engineering
policies.</p>
<p>To some extent, the release engineering team will take
into account user demand for future 4-STABLE releases. This
demand, however, will need to be balanced with release
engineering resources (in terms of personnel, computing
resources, and mirror archive space).</p>
<p>The Security Officer Team <tt class="EMAIL">&#60;<a
href=
"mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&#62;</tt>
will continue to support releases made from the 4-STABLE
branch in accordance with their published policies, which
can be found on the <a href=
"http://www.FreeBSD.org/security/index.html" target=
"_top">Security page</a> on the FreeBSD web site.
Generally, the two most recent releases from any branch
will be supported with respect to security advisories and
security fixes. At its discretion, the team may support
other releases.</p>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN103">6 Notes on
Upgrading</a></h1>
<p>For those users with existing FreeBSD systems, this
section offers a few notes on upgrading a FreeBSD 4.<tt
class="REPLACEABLE"><i>X</i></tt> system to 5.<tt class=
"REPLACEABLE"><i>X</i></tt>. As with any FreeBSD upgrade,
it is crucial to read the release notes and the errata for
the version in question, as well as <tt class=
"FILENAME">src/UPDATING</tt> for source upgrades.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN109">6.1 Binary
Upgrades</a></h2>
<p>Probably the most straightforward approach is that of
``backup everything, reformat, reinstall, and restore
everything''. This eliminates problems of incompatible or
obsolete executables or configuration files polluting the
new system.</p>
<p>As of this time, the binary upgrade option in <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a> has not
been well-tested for cross-major-version upgrades. Using
this feature is not recommended.</p>
<p>On the i386 and pc98 platforms, a UserConfig utility
exists on 4-STABLE to allow boot-time configuration of
ISA devices when booting from installation media. Under
FreeBSD 5.0, this functionality has been replaced in part
by the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=device.hints&sektion=5&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">device.hints</span>(5)</span></a>
mechanism (it allows specifying the same parameters, but
is not interactive).</p>
<p>Floppy-based binary installations may require
downloading a third, new floppy image holding additional
device drivers in kernel modules. This <tt class=
"FILENAME">drivers.flp</tt> floppy image will generally
be found in the same location as the usual <tt class=
"FILENAME">kern.flp</tt> and <tt class=
"FILENAME">mfsroot.flp</tt> floppy images.</p>
<p>CDROM-based installations on the i386 architecture now
use a ``no-emulation'' boot loader. This allows, among
other things, the use of a <tt class=
"LITERAL">GENERIC</tt> kernel, rather than the
stripped-down kernel on the floppy images. In theory, any
system capable of booting the Microsoft Windows NT 4
installation CDROMs should be able to cope with the
FreeBSD 5.0 CDROMs.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN128">6.2 Source
Upgrades</a></h2>
<p>Reading <tt class="FILENAME">src/UPDATING</tt> is
absolutely essential. The section entitled ``To upgrade
from 4.x-stable to current'' contains a step-by-step
update procedure. This procedure must be followed
exactly, without making use of the ``shortcuts'' that
some users occasionally employ.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN134">6.3 Common
Notes</a></h2>
<p><b class="APPLICATION">Perl</b> has been removed from
the base system. The recommended way of installing Perl
is either from a pre-built package or from the Ports
Collection. Building Perl as a part of the base system
created a number of difficulties which made updates
problematic. The base system utilities that used Perl
have either been rewritten (if still applicable) or
discarded (if obsolete).</p>
<p>It is generally possible to run old 4.<tt class=
"REPLACEABLE"><i>X</i></tt> executables under 5.<tt
class="REPLACEABLE"><i>X</i></tt>, but this requires the
<tt class="FILENAME">compat4x</tt> distribution to be
installed. Thus, using old ports <span class=
"emphasis"><i class="EMPHASIS">may</i></span> be
possible.</p>
<p>When installing or upgrading over the top of an
existing 4-STABLE-based system, it is extremely important
to clear out old header files in <tt class=
"FILENAME">/usr/include</tt>. Renaming or moving this
directory before a binary installation or an <tt class=
"LITERAL">installworld</tt> is generally sufficient. If
this step is not taken, confusion may result (especially
with C++ programs) as the compiler may wind up using a
mixture of obsolete and current header files.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN146">7 Summary</a></h1>
<p>While FreeBSD 5.0 contains a number of new and exciting
features, it may not be suitable for all users at this
time. In this document, we presented some background on
release engineering, some of the more notable new features
of the 5.0 series, and some drawbacks to early adoption. We
also presented some future plans for the 4-STABLE
development branch and some tips on upgrading for early
adopters.</p>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</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:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small><small>All users of FreeBSD 5-CURRENT
should subscribe to the &#60;<a href=
"mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62;
mailing list.</small></small></p>
<p align="center">For questions about this documentation,
e-mail &#60;<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
<br>
<br>
</body>
</html>

View file

@ -0,0 +1,153 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD 5.0-DP2 Errata</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.73 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">FreeBSD 5.0-DP2
Errata</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002 by
The FreeBSD Documentation Project</p>
<p class="PUBDATE">$FreeBSD:
src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.9
2002/03/14 21:52:01 bmah Exp $<br>
</p>
<hr>
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT">
<a name="AEN11"></a>
<p>This document lists known issues for FreeBSD 5.0-DP2.
This information includes information relating to the
software or documentation that could affect its operation
or usability. Also included is a list of areas of the
base system that could benefit from some extra
testing.</p>
<p>Please note that FreeBSD 5.0-DP2 is not an officially
supported release of FreeBSD. Unlike supported releases,
this errata file will not be updated. Testers of FreeBSD
5.0-DP2 should subscribe to the FreeBSD-CURRENT mailing
list <tt class="EMAIL">&#60;<a href=
"mailto:freebsd-current@FreeBSD.org">freebsd-current@FreeBSD.org</a>&#62;</tt>
to stay informed about late-breaking issues and
developments.</p>
</div>
</blockquote>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN15">1 Introduction</a></h1>
<p>This errata document lists known problems relating to
FreeBSD 5.0-DP2. Before installing this version, it is
important to consult this document to learn about any
post-release discoveries or problems that may already have
been found and fixed.</p>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN18">2 Known Problems</a></h1>
<p>This section describes some known issues and problems
with FreeBSD 5.0-DP2. The Release Engineering Team <tt
class="EMAIL">&#60;<a href=
"mailto:re@FreeBSD.org">re@FreeBSD.org</a>&#62;</tt>
intends to address these problems in some manner before
FreeBSD 5.0-RELEASE. All users of FreeBSD 5.0-DP2 should be
subscribed to the FreeBSD-CURRENT mailing list <tt class=
"EMAIL">&#60;<a href=
"mailto:freebsd-current@FreeBSD.org">freebsd-current@FreeBSD.org</a>&#62;</tt>
to remain informed about developments regarding these and
other issues.</p>
<p>Packages in FreeBSD 5.0-RELEASE will be compressed using
<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bzip2&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bzip2</span>(1)</span></a>. In some cases,
<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pkg_add</span>(1)</span></a> has some
difficulties working with packages compressed using <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=gzip&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">gzip</span>(1)</span></a> (typical cases
are from within <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a>, and when
using the <tt class="OPTION">-r</tt> flag). This does not
affect the default package sets provided with
snapshots.</p>
<p>The <tt class="LITERAL">NWFS</tt> feature is broken.</p>
<p>Various documents may not reflect differences between
the line of FreeBSD 4-STABLE releases and FreeBSD 5.0-DP2.
In addition, the architecture-specific files in the release
documentation are likely incomplete for new architectures
(sparc64 and ia64).</p>
<p>Installations from boot floppies are no longer supported
on the alpha platform. The combination of the boot loader
and a (highly stripped-down) kernel is too large to fit on
a 1.44&nbsp;MB floppy disk. Some work in this area is
ongoing; this feature <span class="emphasis"><i class=
"EMPHASIS">may</i></span> return before FreeBSD
5.0-RELEASE.</p>
<p>The <tt class="VARNAME">__sF</tt> symbol in <tt class=
"FILENAME">libc</tt> has been made static, as part of work
to make <tt class="VARNAME">FILE</tt> expandable.
Applications built on FreeBSD 4-STABLE-based systems on on
FreeBSD -CURRENT systems before 13 August 2001 may need to
be recompiled. Due to previously unforseen compatability
problems, this change <span class="emphasis"><i class=
"EMPHASIS">may</i></span> be reverted prior to 5.0-RELEASE
and postponed for another release or two.</p>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</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:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small><small>All users of FreeBSD 5-CURRENT
should subscribe to the &#60;<a href=
"mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62;
mailing list.</small></small></p>
<p align="center">For questions about this documentation,
e-mail &#60;<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
<br>
<br>
</body>
</html>

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff

View file

@ -0,0 +1,576 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD/ia64 5.0-DP2 Hardware Notes</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.73 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">FreeBSD/ia64 5.0-DP2
Hardware Notes</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Documentation
Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002 by
The FreeBSD Documentation Project</p>
<hr>
</div>
<div class="TOC">
<dl>
<dt><b>Table of Contents</b></dt>
<dt>1 <a href="#AEN12">Introduction</a></dt>
<dt>2 <a href="#AEN17">Supported Processors and
Motherboards</a></dt>
<dt>3 <a href="#AEN20">Supported Devices</a></dt>
<dd>
<dl>
<dt>3.1 <a href="#AEN26">Disk Controllers</a></dt>
<dt>3.2 <a href="#ETHERNET">Ethernet
Interfaces</a></dt>
<dt>3.3 <a href="#AEN1493">FDDI Interfaces</a></dt>
<dt>3.4 <a href="#AEN1503">ATM Interfaces</a></dt>
<dt>3.5 <a href="#AEN1545">Wireless Network
Interfaces</a></dt>
<dt>3.6 <a href="#AEN1670">Miscellaneous
Networks</a></dt>
<dt>3.7 <a href="#AEN1680">ISDN Interfaces</a></dt>
<dt>3.8 <a href="#AEN1744">Serial Interfaces</a></dt>
<dt>3.9 <a href="#AEN1904">Audio Devices</a></dt>
<dt>3.10 <a href="#AEN2030">Camera and Video Capture
Devices</a></dt>
<dt>3.11 <a href="#USB">USB Devices</a></dt>
<dt>3.12 <a href="#FIREWIRE">IEEE 1394 (Firewire)
Devices</a></dt>
<dt>3.13 <a href="#AEN2287">Cryptographic
Accelerators</a></dt>
<dt>3.14 <a href="#AEN2312">Miscellaneous</a></dt>
</dl>
</dd>
</dl>
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT">
<a name="AEN10"></a>
<p>This document is in a very preliminary state. It is
incomplete, and is almost certainly not be an accurate
reflection of reality.</p>
</div>
</blockquote>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN12">1 Introduction</a></h1>
<p>This document contains the hardware compatibility notes
for FreeBSD 5.0-DP2 on the IA-64 hardware platform (also
referred to as FreeBSD/ia64 5.0-DP2). It lists devices
known to work on this platform, as well as some notes on
boot-time kernel customization that may be useful when
attempting to configure support for new devices.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> This document includes information
specific to the IA-64 hardware platform. Versions of
the hardware compatibility notes for other
architectures will differ in some details.</p>
</blockquote>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN17">2 Supported Processors
and Motherboards</a></h1>
<p>Need to write this section.</p>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN20">3 Supported
Devices</a></h1>
$FreeBSD:
src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v
1.114 2002/11/07 22:11:00 bmah Exp $
<p>This section describes the devices currently known to be
supported by with FreeBSD on the IA-64 platform. Other
configurations may also work, but simply have not been
tested yet. Feedback, updates, and corrections to this list
are encouraged.</p>
<p>Where possible, the drivers applicable to each device or
class of devices is listed. If the driver in question has a
manual page in the FreeBSD base distribution (most should),
it is referenced here.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN26">3.1 Disk
Controllers</a></h2>
<p>IDE/ATA controllers (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ata</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Acerlabs Aladdin</p>
</li>
<li>
<p>AMD 756 ATA66, 766 ATA100, 768 ATA100</p>
</li>
<li>
<p>Cenatek Rocket Drive</p>
</li>
<li>
<p>CMD 646, 648 ATA66, and 649 ATA100</p>
</li>
<li>
<p>Cypress 82C693</p>
</li>
<li>
<p>Cyrix 5530 ATA33</p>
</li>
<li>
<p>HighPoint HPT366 ATA66, HPT370 ATA100, HPT372
ATA133, HPT374 ATA133</p>
</li>
<li>
<p>Intel PIIX, PIIX3, PIIX4</p>
</li>
<li>
<p>Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4
ATA100</p>
</li>
<li>
<p>nVidia nForce ATA100</p>
</li>
<li>
<p>Promise ATA100 OEM chip (pdc20265)</p>
</li>
<li>
<p>Promise ATA133 OEM chip (pdc20269)</p>
</li>
<li>
<p>Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133
TX2/TX2000</p>
</li>
<li>
<p>Promise Ultra-33, -66, -100, -133 TX2/TX2000</p>
</li>
<li>
<p>ServerWorks ROSB4 ATA33</p>
</li>
<li>
<p>ServerWorks CSB5 ATA66/ATA100</p>
</li>
<li>
<p>Sil 0680 UDMA6</p>
</li>
<li>
<p>SiS 530, 540, 620</p>
</li>
<li>
<p>SiS 630, 633, 635, 645, 730, 733, 735, 740, 745,
750</p>
</li>
<li>
<p>SiS 5591 ATA100</p>
</li>
<li>
<p>VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66,
82C686b ATA100</p>
</li>
<li>
<p>VIA 8233, 8235 ATA133</p>
</li>
</ul>
<br>
<br>
<p>Qlogic controllers and variants (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">isp</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Qlogic 1020, 1040 SCSI and Ultra SCSI host
adapters</p>
</li>
<li>
<p>Qlogic 1240 dual Ultra SCSI controllers</p>
</li>
<li>
<p>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD
controllers</p>
</li>
<li>
<p>Qlogic 12160 Ultra3 LVD controllers</p>
</li>
<li>
<p>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI
controllers</p>
</li>
<li>
<p>Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre
Channel SCSI controllers</p>
</li>
<li>
<p>Performance Technology SBS440 ISP1000 variants</p>
</li>
<li>
<p>Performance Technology SBS450 ISP1040 variants</p>
</li>
<li>
<p>Performance Technology SBS470 ISP2100 variants</p>
</li>
<li>
<p>Antares Microsystems P-0033 ISP2100 variants</p>
</li>
</ul>
<br>
<br>
<p>With all supported SCSI controllers, full support is
provided for SCSI-I, SCSI-II, and SCSI-III peripherals,
including hard disks, optical disks, tape drives
(including DAT, 8mm Exabyte, Mammoth, and DLT), medium
changers, processor target devices and CD-ROM drives.
WORM devices that support CD-ROM commands are supported
for read-only access by the CD-ROM drivers (such as <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">cd</span>(4)</span></a>). WORM/CD-R/CD-RW
writing support is provided by <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&sektion=1&manpath=FreeBSD+Ports">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">cdrecord</span>(1)</span></a>, which is a
part of the <a href=
"http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/cdrtools/pkg-descr">
<tt class="FILENAME">sysutils/cdrtools</tt></a> port in
the Ports Collection.</p>
<p>The following CD-ROM type systems are supported at
this time:</p>
<ul>
<li>
<p>SCSI interface (also includes ProAudio Spectrum
and SoundBlaster SCSI) (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">cd</span>(4)</span></a>)</p>
</li>
<li>
<p>ATAPI IDE interface (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=acd&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">acd</span>(4)</span></a>)</p>
</li>
</ul>
<br>
<br>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="ETHERNET">3.2 Ethernet
Interfaces</a></h2>
<p>Intel 82557-, 82258-, 82559-, 82550- or 82562-based
Fast Ethernet NICs (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fxp</span>(4)</span></a> driver)</p>
<ul>
<li>
<p>Intel EtherExpress Pro/100B PCI Fast Ethernet</p>
</li>
<li>
<p>Intel InBusiness 10/100 PCI Network Adapter</p>
</li>
<li>
<p>Intel PRO/100+ Management Adapter</p>
</li>
<li>
<p>Intel Pro/100 VE Desktop Adapter</p>
</li>
<li>
<p>Intel Pro/100 M Desktop Adapter</p>
</li>
<li>
<p>Intel Pro/100 S Desktop, Server and Dual-Port
Server Adapters</p>
</li>
<li>
<p>On-board Ethernet NICs on many Intel
motherboards.</p>
</li>
</ul>
<br>
<br>
<p>Gigabit Ethernet NICs based on the Intel 82542 and
82543 controller chips (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=gx&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">gx</span>(4)</span></a> and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">em</span>(4)</span></a> drivers), plus
NICs supported by the Intel 82540EM, 82544, 82545EM, and
82546EB controller chips (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">em</span>(4)</span></a> driver only)</p>
<ul>
<li>
<p>Intel PRO/1000 Gigabit Ethernet</p>
</li>
</ul>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> The <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">em</span>(4)</span></a> driver is
officially supported by Intel, but is only supported
on the i386.</p>
</blockquote>
</div>
<br>
<br>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1493">3.3 FDDI
Interfaces</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1503">3.4 ATM
Interfaces</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1545">3.5 Wireless Network
Interfaces</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1670">3.6 Miscellaneous
Networks</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1680">3.7 ISDN
Interfaces</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1744">3.8 Serial
Interfaces</a></h2>
<p>``PC standard'' 8250, 16450, and 16550-based serial
ports (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sio</span>(4)</span></a> driver)</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN1904">3.9 Audio
Devices</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN2030">3.10 Camera and Video
Capture Devices</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="USB">3.11 USB Devices</a></h2>
<p>A range of USB peripherals are supported; devices
known to work are listed in this section. Owing to the
generic nature of most USB devices, with some exceptions
any device of a given class will be supported, even if
not explicitly listed here.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> USB Ethernet adapters can be found in
the section listing <a href="#ETHERNET">Ethernet
interfaces</a>.</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="FIREWIRE">3.12 IEEE 1394
(Firewire) Devices</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN2287">3.13 Cryptographic
Accelerators</a></h2>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN2312">3.14
Miscellaneous</a></h2>
<p>Keyboards including:</p>
<ul>
<li>
<p>PS/2 keyboards</p>
</li>
</ul>
<br>
<br>
<p>Mice including:</p>
<ul>
<li>
<p>PS/2 mice (<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=psm&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">psm</span>(4)</span></a> driver)</p>
</li>
<li>
<p>Serial mice</p>
</li>
</ul>
<br>
<br>
</div>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</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:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small><small>All users of FreeBSD 5-CURRENT
should subscribe to the &#60;<a href=
"mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62;
mailing list.</small></small></p>
<p align="center">For questions about this documentation,
e-mail &#60;<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
<br>
<br>
</body>
</html>

File diff suppressed because it is too large Load diff

View file

@ -0,0 +1,783 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD/sparc64 5.0-DP2 Hardware Notes</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.73 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">FreeBSD/sparc64 5.0-DP2
Hardware Notes</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Documentation
Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002 by
The FreeBSD Documentation Project</p>
<hr>
</div>
<div class="TOC">
<dl>
<dt><b>Table of Contents</b></dt>
<dt>1 <a href="#AEN10">Introduction</a></dt>
<dt>2 <a href="#AEN15">Supported Systems</a></dt>
<dd>
<dl>
<dt>2.1 <a href="#AEN18">Overview</a></dt>
<dt>2.2 <a href="#AEN29">In general, what do you need
to run FreeBSD on a sparc64</a></dt>
<dt>2.3 <a href="#AEN56">System-specific
information</a></dt>
<dd>
<dl>
<dt>2.3.1 <a href="#AEN60">Ultra 1</a></dt>
<dt>2.3.2 <a href="#AEN64">Ultra 2</a></dt>
<dt>2.3.3 <a href="#AEN81">Ultra 5/10</a></dt>
<dt>2.3.4 <a href="#AEN109">Ultra 60</a></dt>
<dt>2.3.5 <a href="#AEN133">Blade 100</a></dt>
</dl>
</dd>
<dt>2.4 <a href="#AEN172">Supported Hardware
Overview</a></dt>
</dl>
</dd>
<dt>3 <a href="#AEN195">Supported Devices</a></dt>
<dd>
<dl>
<dt>3.1 <a href="#AEN201">PCI Hardware</a></dt>
<dt>3.2 <a href="#AEN239">SBus Hardware</a></dt>
<dt>3.3 <a href="#AEN249">ISA Hardware</a></dt>
<dt>3.4 <a href="#AEN259">EBus Hardware</a></dt>
<dt>3.5 <a href="#AEN272">Unsupported
Hardware</a></dt>
</dl>
</dd>
<dt>4 <a href="#AEN300">Acknowledgments</a></dt>
</dl>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN10">1 Introduction</a></h1>
<p>This document contains the hardware compatibility notes
for FreeBSD 5.0-DP2 on the UltraSPARC hardware platform
(also referred to as FreeBSD/sparc64 5.0-DP2). It lists
devices known to work on this platform, as well as some
notes on boot-time kernel customization that may be useful
when attempting to configure support for new devices.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> This document includes information
specific to the UltraSPARC hardware platform. Versions
of the hardware compatibility notes for other
architectures will differ in some details.</p>
</blockquote>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN15">2 Supported
Systems</a></h1>
<p>Additions, corrections and constructive criticism are
invited. In particular, information on system quirks is
more than welcome.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN18">2.1 Overview</a></h2>
<p>This document tries to provide a starting point for
those who want to run FreeBSD on an UltraSPARC-based
machine. It is aimed at providing background information
on the various hardware designs. It is not a replacement
for the systems manuals.</p>
<p>The information is structured as follows:</p>
<ul>
<li>
<p>General hardware requirements to run FreeBSD on
sparc64.</p>
</li>
<li>
<p>System specific information for each of the
systems/boards supported by FreeBSD.</p>
</li>
<li>
<p>Information on expansion boards for FreeBSD,
including things that differ from what is in the
generic supported hardware list.</p>
</li>
</ul>
<br>
<br>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN29">2.2 In general, what do
you need to run FreeBSD on a sparc64</a></h2>
<p>FreeBSD/sparc64 requires an UltraSPARC system.
Currently, the newer PCI-based systems are supported
better than the older SBus based systems. The following
systems are known to work to varying degrees:</p>
<ul>
<li>
<p>Sun Ultra 1 workstations</p>
</li>
<li>
<p>Sun Ultra 2 workstations</p>
</li>
<li>
<p>Sun Ultra 5 workstations</p>
</li>
<li>
<p>Sun Ultra 10 workstations</p>
</li>
<li>
<p>Sun Ultra 30 workstations</p>
</li>
<li>
<p>Sun Ultra 60 workstations</p>
</li>
<li>
<p>Sun Blade 100 workstations</p>
</li>
<li>
<p>Sun Netra t1 series servers</p>
</li>
<li>
<p>Sun Enterprise 220R servers</p>
</li>
<li>
<p>Sun Enterprise 250 servers</p>
</li>
<li>
<p>Sun Enterprise 420R servers</p>
</li>
</ul>
<p>Ultra 80 and Blade 1000 are expected to work, maybe
with minor modifications. SMP is supported on Ultra 2 and
60 workstations and Enterprise 220R, 250 and 420R
servers.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN56">2.3 System-specific
information</a></h2>
<p>Below is an overview of the UltraSPARC hardware that
FreeBSD runs on. The GENERIC kernel configuration file in
<tt class="FILENAME">/sys/sparc64/conf/GENERIC</tt> may
contain additional information about supported
devices.</p>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN60">2.3.1 Ultra
1</a></h3>
<p>UltraSPARC Ultra1-family systems have not been
thoroughly tested with FreeBSD. These systems are not
very well supported, but it is possible to install
FreeBSD onto an Ultra-1e with a <tt class=
"DEVICENAME">hme</tt> Ethernet interface.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN64">2.3.2 Ultra
2</a></h3>
<p>UltraSPARC Ultra2-family systems include the
following hardware:</p>
<ul>
<li>
<p>1 or 2 UltraSPARC II CPUs</p>
</li>
<li>
<p>Built-in Ethernet (<tt class=
"DEVICENAME">hme</tt> compatible) interface</p>
</li>
<li>
<p>4 SBus slots</p>
</li>
<li>
<p>1 UPA Slot</p>
</li>
<li>
<p>Serial and Parallel ports</p>
</li>
<li>
<p>16-bit audio</p>
</li>
</ul>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN81">2.3.3 Ultra
5/10</a></h3>
<p>UltraSPARC Ultra5/10-family systems include the
following hardware:</p>
<ul>
<li>
<p>UltraSPARC IIi CPU</p>
</li>
<li>
<p>Three PCI busses</p>
</li>
<li>
<p>Built-in Ethernet (<tt class=
"DEVICENAME">hme</tt> compatible) interface</p>
</li>
<li>
<p>Built-in PCI-IDE controller <span class=
"emphasis"><i class="EMPHASIS">(not yet committed -
in Perforce tree)</i></span></p>
</li>
<li>
<p>Two PC-AT style `com' ports for the mouse and
keyboard</p>
</li>
<li>
<p>Floppy driver controller</p>
</li>
<li>
<p>Siemens SAB82532 dual-channel serial ports for
ttya and ttyb</p>
</li>
<li>
<p>One CS4231 audio device</p>
</li>
<li>
<p>One PC-AT style parallel port</p>
</li>
<li>
<p>Sun `ffb' frame buffer (Ultra10 only)</p>
</li>
<li>
<p>EBus (Sun proprietary bus for slow devices)</p>
</li>
</ul>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN109">2.3.4 Ultra
60</a></h3>
<p>Sun Ultra 60 workstations include the following
hardware:</p>
<ul>
<li>
<p>1 or 2 UltraSPARC II CPUs</p>
</li>
<li>
<p>4 PCI slots</p>
</li>
<li>
<p>2 UPA slots</p>
</li>
<li>
<p><a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sym</span>(4)</span></a>-based
UltraSCSI controller</p>
</li>
<li>
<p>Built-in Ethernet (<tt class=
"DEVICENAME">hme</tt> compatible) interface</p>
</li>
<li>
<p>Serial and Parallel ports</p>
</li>
<li>
<p>16-bit audio</p>
</li>
<li>
<p>EBus (Sun proprietary bus for slow devices)</p>
</li>
</ul>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN133">2.3.5 Blade
100</a></h3>
<p>Sun Blade 100 workstations include the following
hardware:</p>
<ul>
<li>
<p>UltraSPARC IIe CPU</p>
</li>
<li>
<p>Three PCI busses</p>
</li>
<li>
<p>Built-in Ethernet (<tt class=
"DEVICENAME">gem</tt> compatible) interface</p>
</li>
<li>
<p>Two USB ports <span class="emphasis"><i class=
"EMPHASIS">(unsupported)</i></span></p>
</li>
<li>
<p>Two Firewire ports <span class="emphasis"><i
class="EMPHASIS">(unsupported)</i></span></p>
</li>
<li>
<p>Built-in PCI-IDE controller <span class=
"emphasis"><i class="EMPHASIS">(not yet committed -
in Perforce tree)</i></span></p>
</li>
<li>
<p>Two PC-AT style `com' ports for the mouse and
keyboard</p>
</li>
<li>
<p>Floppy driver controller</p>
</li>
<li>
<p><a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sio</span>(4)</span></a> supported
serial ports for ttya and ttyb</p>
</li>
<li>
<p>One CS4231 audio device</p>
</li>
<li>
<p>One PC-AT style parallel port</p>
</li>
<li>
<p>Built-in PGX64 (ATI) graphics</p>
</li>
<li>
<p>EBus (Sun proprietary bus for slow devices)</p>
</li>
<li>
<p>ISA bus</p>
</li>
</ul>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN172">2.4 Supported Hardware
Overview</a></h2>
<p>A word of caution: the installed base for
FreeBSD/sparc64 is not nearly as large as for
FreeBSD/Intel. This means that the enormous variation of
PCI/ISA expansion cards out there has much less chance of
having been tested on sparc64 than on Intel. This is not
to imply they are doomed to fail, just that the chance of
running into something never tested before is much
higher. <tt class="FILENAME">GENERIC</tt> contains things
that are known to work on sparc64 only.</p>
<p>The PCI bus is fully supported. SBus support is
limited, but is reported to work well enough to netboot
an SBus-based Ultra 2 workstation.</p>
<p>1.44 Mbyte floppy drives are <span class="emphasis"><i
class="EMPHASIS">not</i></span> yet supported.</p>
<p>ATA and ATAPI (IDE) devices are supported via the <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ata</span>(4)</span></a> driver
framework. <span class="emphasis"><i class=
"EMPHASIS">(not yet committed - in Perforce
tree)</i></span></p>
<p>There is full SCSI support via the CAM layer. However,
only NCR/Symbios cards are currently working. Adaptec
2940x (AIC 7xxx chip-based) and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">isp</span>(4)</span></a> cards should be
supported soon. Be aware that SCSI cards must contain Sun
FCODE in order to use them as a boot device from
OpenBoot.</p>
<p>If you want to boot your sparc64 over the Ethernet you
will obviously need an Ethernet card that the OpenBoot
console recognizes.</p>
<p><tt class="DEVICENAME">hme</tt>, <tt class=
"DEVICENAME">gem</tt>, and <tt class=
"DEVICENAME">eri</tt> based network devices.</p>
<p>The ``PC standard'' serial ports found on most newer
Sun workstations are supported.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN195">3 Supported
Devices</a></h1>
$FreeBSD:
src/release/doc/en_US.ISO8859-1/hardware/sparc64/dev-sparc64.sgml,v
1.1 2002/02/25 07:25:38 murray Exp $
<p>This section describes the devices currently known to be
supported by with FreeBSD on the UltraSPARC platform. Other
configurations may also work, but simply have not been
tested yet. Feedback, updates, and corrections to this list
are encouraged.</p>
<p>Where possible, the drivers applicable to each device or
class of devices is listed. If the driver in question has a
manual page in the FreeBSD base distribution (most should),
it is referenced here.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN201">3.1 PCI
Hardware</a></h2>
<p>In general, any device for which there is a driver can
be made to work on sparc64. Some drivers might just work,
others might require some changes (because this is the
first big-endian architecture to be supported by
FreeBSD).</p>
<p>The following drivers are known to work:</p>
<ul>
<li>
<p><tt class="LITERAL">apb</tt> (Sun PCI-PCI
bridge)</p>
</li>
<li>
<p>generic PCI-PCI bridges</p>
</li>
<li>
<p><a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ahc</span>(4)</span></a> (coming real
soon).</p>
</li>
<li>
<p><a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ata</span>(4)</span></a>, <tt class=
"DEVICENAME">atadisk</tt>, <tt class=
"DEVICENAME">atapicd</tt> (but not atapifd,
atapist)</p>
</li>
<li>
<p><tt class="DEVICENAME">gem</tt> (Sun GEM/ERI
ethernet, on-board on Blade 100)</p>
</li>
<li>
<p><tt class="LITERAL">hme</tt> (Sun HME ethernet,
on-board on Ultra 5, 10)</p>
</li>
<li>
<p><a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sio</span>(4)</span></a></p>
</li>
<li>
<p><a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sym</span>(4)</span></a></p>
</li>
</ul>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN239">3.2 SBus
Hardware</a></h2>
<p>The following drivers have SBus front ends:</p>
<ul>
<li>
<p><tt class="LITERAL">hme</tt> Ethernet</p>
</li>
<li>
<p><tt class="LITERAL">mk48txx</tt> ('eeprom' device;
time-of-day clock)</p>
</li>
</ul>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN249">3.3 ISA
Hardware</a></h2>
<p>The paragraph about PCI drivers apply to ISA drivers
as well, but with the notable exception that ISA DMA is
not yet supported. This are generally on-board devices;
there are no UltraSPARC boxes with ISA slots that the
authors are aware of.</p>
<p>The following drivers are known to work:</p>
<ul>
<li>
<p><a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sio</span>(4)</span></a></p>
</li>
</ul>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN259">3.4 EBus
Hardware</a></h2>
<p>The EBus is specific to Sun hardware, so drivers need
to have support added to work with these devices. It is
quite similar to ISA, so that ISA drivers can usually be
easily ported, provided that they use the bus space
interface, and not in[bwl]/out[bwl] and related
functions. DMA is not yet supported.</p>
<p>The following drivers are known to work:</p>
<ul>
<li>
<p><a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sio</span>(4)</span></a></p>
</li>
<li>
<p><tt class="LITERAL">mk48txx</tt> ('eeprom' device;
time-of-day clock)</p>
</li>
</ul>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN272">3.5 Unsupported
Hardware</a></h2>
<p>The following hardware, which is built-in in Sun
UltraSPARC boxes, is not currently supported:</p>
<ul>
<li>
<p>graphics/frame buffer devices, keyboards (except
indirectly in text mode using the <tt class=
"DEVICENAME">ofw_console</tt> device)</p>
</li>
<li>
<p>Siemens sab82532 serial ports (Ultra 5/10; the
keyboard/mouse ports are also RS232 ones and
supported by the sio driver though; a driver, 'se',
is being worked on).</p>
</li>
<li>
<p>serial keyboards (except indirectly using the <tt
class="DEVICENAME">ofw_console</tt> device)</p>
</li>
<li>
<p>Zilog z8530 serial ports (keyboard/mouse, ttya and
ttyb in Ultra 1 and Ultra 2 boxen)</p>
</li>
<li>
<p>fas (Fast SCSI controller builtin in most Ultra 1
and Ultra 2 boxen)</p>
</li>
<li>
<p>USB ports (have issues, should be easy to get to
work though)</p>
</li>
<li>
<p>all floppy drives/controllers</p>
</li>
<li>
<p>smart card readers (the Blade 100 has one, don't
know much about it)</p>
</li>
<li>
<p>FireWire/IEEE1394</p>
</li>
<li>
<p>sound cards</p>
</li>
<li>
<p>parallel ports</p>
</li>
</ul>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN300">4
Acknowledgments</a></h1>
<p>This document is based in part on the FreeBSD/Alpha and
NetBSD/sparc64 release documentation. Information about
specific system models was obtained from <a href=
"http://www.sun.com" target="_top">Sun</a>.</p>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</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:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small><small>All users of FreeBSD 5-CURRENT
should subscribe to the &#60;<a href=
"mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62;
mailing list.</small></small></p>
<p align="center">For questions about this documentation,
e-mail &#60;<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
<br>
<br>
</body>
</html>

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff

View file

@ -0,0 +1,550 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD 5.0-DP2 README</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.73 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">FreeBSD 5.0-DP2
README</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002 by
The FreeBSD Documentation Project</p>
<p class="PUBDATE">$FreeBSD:
src/release/doc/en_US.ISO8859-1/readme/article.sgml,v 1.18
2002/10/26 17:00:39 bmah Exp $<br>
</p>
<hr>
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT">
<a name="AEN11"></a>
<p>This document gives a brief introduction to FreeBSD
5.0-DP2. It includes some information on how to obtain
FreeBSD, a listing of various ways to contact the FreeBSD
Project, and pointers to some other sources of
information.</p>
</div>
</blockquote>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN13">1 Introduction</a></h1>
<p>This distribution is a snapshot of FreeBSD 5.0-DP2, the
latest point along the 5-CURRENT branch.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN16">1.1 About
FreeBSD</a></h2>
<p>FreeBSD is an operating system based on 4.4 BSD Lite
for Intel, AMD, Cyrix or NexGen ``x86'' based PC
hardware, Compaq (formerly DEC) Alpha computers, and
UltraSPARC machines. Versions for the IA64 and PowerPC
architectures are currently under development as well.
FreeBSD works with a wide variety of peripherals and
configurations and can be used for everything from
software development to games to Internet Service
Provision.</p>
<p>This release of FreeBSD contains everything you need
to run such a system, including full source code for the
kernel and all utilities in the base distribution. With
the source distribution installed, you can literally
recompile the entire system from scratch with one
command, making it ideal for students, researchers, or
users who simply want to see how it all works.</p>
<p>A large collection of third-party ported software (the
``Ports Collection'') is also provided to make it easy to
obtain and install all your favorite traditional UNIX
utilities for FreeBSD. Each ``port'' consists of a set of
scripts to retrieve, configure, build, and install a
piece of software, with a single command. Over 7,600
ports, from editors to programming languages to graphical
applications, make FreeBSD a powerful and comprehensive
operating environment that extends far beyond what's
provided by many commercial versions of UNIX. Most ports
are also available as pre-compiled ``packages'', which
can be quickly installed from the installation
program.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN25">1.2 Target
Audience</a></h2>
<p>This snapshot is aimed primarily at early adopters and
various other users who want to get involved with the
ongoing development of FreeBSD. While the FreeBSD
development team tries its best to ensure that each
snapshot works as advertised, 5-CURRENT is very much a
work-in-progress.</p>
<p>The basic requirements for using this snapshot are
technical proficiency with FreeBSD and an understanding
of the ongoing development process of FreeBSD 5-CURRENT
(as discussed on the FreeBSD-CURRENT mailing list <tt
class="EMAIL">&#60;<a href=
"mailto:freebsd-current@FreeBSD.org">freebsd-current@FreeBSD.org</a>&#62;</tt>).</p>
<p>For those more interested in doing business with
FreeBSD than in experimenting with new FreeBSD
technology, formal releases (such as 4.5-RELEASE) are
frequently more appropriate. Releases undergo a period of
testing and quality assurance checking to ensure high
reliability and dependability.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN31">2 Obtaining
FreeBSD</a></h1>
<p>FreeBSD may be obtained in a variety of ways. This
section focuses on those ways that are primarily useful for
obtaining a complete FreeBSD distribution, rather than
updating an existing installation.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN34">2.1 CDROM and
DVD</a></h2>
<p>FreeBSD -RELEASE distributions may be ordered on CDROM
or DVD from several publishers. This is frequently the
most convenient way to obtain FreeBSD for new
installations, as it provides a convenient way to quickly
reinstall the system if necessary. Some distributions
include some of the optional, precompiled ``packages''
from the FreeBSD Ports Collection.</p>
<p>A list of the CDROM and DVD publishers known to the
project are listed in the <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html"
target="_top">``Obtaining FreeBSD''</a> appendix to the
Handbook.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN41">2.2 FTP</a></h2>
<p>You can use FTP to retrieve FreeBSD and any or all of
its optional packages from <a href=
"ftp://ftp.FreeBSD.org/" target=
"_top">ftp://ftp.FreeBSD.org/</a>, which is the official
FreeBSD release site, or any of its ``mirrors''.</p>
<p>Lists of locations that mirror FreeBSD can be found in
the <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"
target="_top">FTP Sites</a> section of the Handbook, or
on the <a href="http://www.freebsdmirrors.org/" target=
"_top">http://www.freebsdmirrors.org/</a> Web pages.
Finding a close (in networking terms) mirror from which
to download the distribution is highly recommended.</p>
<p>Additional mirror sites are always welcome. Contact
<tt class="EMAIL">&#60;<a href=
"mailto:freebsd-admin@FreeBSD.org">freebsd-admin@FreeBSD.org</a>&#62;</tt>
for more details on becoming an official mirror site. You
can also find useful information for mirror sites at the
<a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/hubs/"
target="_top">Mirroring FreeBSD</a> article.</p>
<p>Mirrors generally contain the floppy disk images
necessary to begin an installation, as well as the
distribution files needed for the install process itself.
Many mirrors also contain the ISO images necessary to
create a CDROM of a FreeBSD release.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="CONTACTING">3 Contacting the
FreeBSD Project</a></h1>
<div class="SECT2">
<h2 class="SECT2"><a name="AEN55">3.1 Email and Mailing
Lists</a></h2>
<p>For any questions or general technical support issues,
please send mail to the FreeBSD general questions mailing
list <tt class="EMAIL">&#60;<a href=
"mailto:freebsd-questions@FreeBSD.org">freebsd-questions@FreeBSD.org</a>&#62;</tt>.</p>
<p>If you're tracking the 5-CURRENT development efforts,
you <span class="emphasis"><i class=
"EMPHASIS">must</i></span> join the FreeBSD-CURRENT
mailing list <tt class="EMAIL">&#60;<a href=
"mailto:freebsd-current@FreeBSD.org">freebsd-current@FreeBSD.org</a>&#62;</tt>,
in order to keep abreast of recent developments and
changes that may affect the way you use and maintain the
system.</p>
<p>Being a largely-volunteer effort, the FreeBSD Project
is always happy to have extra hands willing to
help--there are already far more desired enhancements
than there is time to implement them. To contact the
developers on technical matters, or with offers of help,
please send mail to the FreeBSD technical discussions
mailing list <tt class="EMAIL">&#60;<a href=
"mailto:freebsd-hackers@FreeBSD.org">freebsd-hackers@FreeBSD.org</a>&#62;</tt>.</p>
<p>Please note that these mailing lists can experience
<span class="emphasis"><i class=
"EMPHASIS">significant</i></span> amounts of traffic. If
you have slow or expensive mail access, or are only
interested in keeping up with major FreeBSD events, you
may find it preferable to subscribe instead to the
FreeBSD announcements mailing list <tt class=
"EMAIL">&#60;<a href=
"mailto:freebsd-announce@FreeBSD.org">freebsd-announce@FreeBSD.org</a>&#62;</tt>.</p>
<p>All of the mailing lists can be freely joined by
anyone wishing to do so. Send mail to <tt class=
"EMAIL">&#60;<a href=
"mailto:majordomo@FreeBSD.org">majordomo@FreeBSD.org</a>&#62;</tt>
and include the keyword <tt class="LITERAL">help</tt> on
a line by itself somewhere in the body of the message.
This will give you more information on joining the
various lists, accessing archives, etc. There are a
number of mailing lists targeted at special interest
groups not mentioned here; more information can be
obtained either through majordomo or the <a href=
"http://www.FreeBSD.org/support.html#mailing-list"
target="_top">mailing lists section</a> of the FreeBSD
Web site.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> Do <span class="emphasis"><i
class="EMPHASIS">not</i></span> send email to the
lists asking to be subscribed. Use the <tt class=
"EMAIL">&#60;<a href=
"mailto:majordomo@FreeBSD.org">majordomo@FreeBSD.org</a>&#62;</tt>
address instead.</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN75">3.2 Submitting Problem
Reports</a></h2>
<p>Suggestions, bug reports and contributions of code are
always valued--please do not hesitate to report any
problems you may find. Bug reports with attached fixes
are of course even more welcome.</p>
<p>The preferred method to submit bug reports from a
machine with Internet mail connectivity is to use the <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=send-pr&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">send-pr</span>(1)</span></a> command or
use the Web form at <a href=
"http://www.FreeBSD.org/send-pr.html" target=
"_top">http://www.FreeBSD.org/send-pr.html</a>. ``Problem
Reports'' (PRs) submitted in this way will be filed and
their progress tracked; the FreeBSD developers will do
their best to respond to all reported bugs as soon as
possible. <a href=
"http://www.FreeBSD.org/cgi/query-pr-summary.cgi" target=
"_top">A list of all active PRs</a> is available on the
FreeBSD Web site; this list is useful to see what
potential problems other users have encountered.</p>
<p>Note that <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=send-pr&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">send-pr</span>(1)</span></a> itself is a
shell script that should be easy to move even onto a
non-FreeBSD system. Using this interface is highly
preferred. If, for some reason, you are unable to use <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=send-pr&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">send-pr</span>(1)</span></a> to submit a
bug report, you can try to send it to the FreeBSD problem
reports mailing list <tt class="EMAIL">&#60;<a href=
"mailto:freebsd-bugs@FreeBSD.org">freebsd-bugs@FreeBSD.org</a>&#62;</tt>.</p>
<p>For more information, <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/problem-reports/"
target="_top">``Writing FreeBSD Problem Reports''</a>,
available on the FreeBSD Web site, has a number of
helpful hints on writing and submitting effective problem
reports.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN96">4 Further
Reading</a></h1>
<p>There are many sources of information about FreeBSD;
some are included with this distribution, while others are
available on-line or in print versions.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="RELEASE-DOCS">4.1 Release
Documentation</a></h2>
<p>A number of other files provide more specific
information about this snapshot distribution. These files
are provided in various formats. Most distributions will
include both ASCII text (<tt class="FILENAME">.TXT</tt>)
and HTML (<tt class="FILENAME">.HTM</tt>) renditions.
Some distributions may also include other formats such as
PostScript (<tt class="FILENAME">.PS</tt>) or Portable
Document Format (<tt class="FILENAME">.PDF</tt>).</p>
<ul>
<li>
<p><tt class="FILENAME">README.TXT</tt>: This file,
which gives some general information about FreeBSD as
well as some cursory notes about obtaining a
distribution.</p>
</li>
<li>
<p><tt class="FILENAME">EARLY.TXT</tt>: A guide for
early adopters of FreeBSD 5.0-RELEASE. Highly
recommended reading for users new to FreeBSD
5-CURRENT and/or the 5.<tt class=
"REPLACEABLE"><i>X</i></tt> series of releases.</p>
</li>
<li>
<p><tt class="FILENAME">RELNOTES.TXT</tt>: The
release notes, showing what's new and different in
FreeBSD 5.0-DP2 compared to the previous release
(FreeBSD 4.0-RELEASE).</p>
</li>
<li>
<p><tt class="FILENAME">HARDWARE.TXT</tt>: The
hardware compatibility list, showing devices with
which FreeBSD has been tested and is known to
work.</p>
</li>
<li>
<p><tt class="FILENAME">INSTALL.TXT</tt>:
Installation instructions for installing FreeBSD from
its distribution media.</p>
</li>
<li>
<p><tt class="FILENAME">ERRATA.TXT</tt>: Release
errata. Late-breaking, post-release information can
be found in this file, which is principally
applicable to releases (as opposed to snapshots). It
is important to consult this file before installing a
release of FreeBSD, as it contains the latest
information on problems which have been found and
fixed since the release was created.</p>
</li>
</ul>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Several of these documents (in
particular, <tt class="FILENAME">RELNOTES.TXT</tt>,
<tt class="FILENAME">HARDWARE.TXT</tt>, and <tt
class="FILENAME">INSTALL.TXT</tt>) contain
information that is specific to a particular hardware
architecture. For example, the alpha release notes
contain information not applicable to the i386, and
vice versa. The architecture for which each document
applies will be listed in that document's title.</p>
</blockquote>
</div>
<br>
<br>
<p>On platforms that support <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a>
(currently the i386 and alpha), these documents are
generally available via the Documentation menu during
installation. Once the system is installed, you can
revisit this menu by re-running the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a>
utility.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> It is extremely important to read the
errata for any given release before installing it, to
learn about any ``late-breaking news'' or
post-release problems. The errata file accompanying
each release (most likely right next to this file) is
already out of date by definition, but other copies
are kept updated on the Internet and should be
consulted as the ``current errata'' for this release.
These other copies of the errata are located at <a
href="http://www.FreeBSD.org/releases/" target=
"_top">http://www.FreeBSD.org/releases/</a> (as well
as any sites which keep up-to-date mirrors of this
location).</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN143">4.2 Manual
Pages</a></h2>
<p>As with almost all UNIX-like operating systems,
FreeBSD comes with a set of on-line manual pages,
accessed through the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=man&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">man</span>(1)</span></a> command or
through the <a href="http://www.FreeBSD.org/cgi/man.cgi"
target="_top">hypertext manual pages gateway</a> on the
FreeBSD Web site. In general, the manual pages provide
information on the different commands and APIs available
to the FreeBSD user.</p>
<p>In some cases, manual pages are written to given
information on particular topics. Notable examples of
such manual pages are <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tuning&sektion=7&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tuning</span>(7)</span></a> (a guide to
performance tuning), <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=security&sektion=7&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">security</span>(7)</span></a> (an
introduction to FreeBSD security), and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=style&sektion=9&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">style</span>(9)</span></a> (a style guide
to kernel coding).</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN160">4.3 Books and
Articles</a></h2>
<p>Two highly-useful collections of FreeBSD-related
information, maintained by the FreeBSD Project, are the
FreeBSD Handbook and FreeBSD FAQ (Frequently Asked
Questions document). On-line versions of the <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
target="_top">Handbook</a> and <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/"
target="_top">FAQ</a> are always available from the <a
href="http://www.FreeBSD.org/docs.html" target=
"_top">FreeBSD Documentation page</a> or its mirrors. If
you install the <tt class="FILENAME">doc</tt>
distribution set, you can use a Web browser to read the
Handbook and FAQ locally.</p>
<p>A number of on-line books and articles, also
maintained by the FreeBSD Project, cover
more-specialized, FreeBSD-related topics. This material
spans a wide range of topics, from effective use of the
mailing lists, to dual-booting FreeBSD with other
operating systems, to guidelines for new committers. Like
the Handbook and FAQ, these documents are available from
the FreeBSD Documentation Page or in the <tt class=
"FILENAME">doc</tt> distribution set.</p>
<p>A listing of other books and documents about FreeBSD
can be found in the <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/bibliography.html"
target="_top">bibliography</a> of the FreeBSD Handbook.
Because of FreeBSD's strong UNIX heritage, many other
articles and books written for UNIX systems are
applicable as well, some of which are also listed in the
bibliography.</p>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN171">5
Acknowledgments</a></h1>
<p>FreeBSD represents the cumulative work of many hundreds,
if not thousands, of individuals from around the world who
have worked countless hours to bring about this snapshot.
For a complete list of FreeBSD developers and contributors,
please see <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/"
target="_top">``Contributors to FreeBSD''</a> on the
FreeBSD Web site or any of its mirrors.</p>
<p>Special thanks also go to the many thousands of FreeBSD
users and testers all over the world, without whom this
snapshot simply would not have been possible.</p>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</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:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small><small>All users of FreeBSD 5-CURRENT
should subscribe to the &#60;<a href=
"mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62;
mailing list.</small></small></p>
<p align="center">For questions about this documentation,
e-mail &#60;<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
<br>
<br>
</body>
</html>

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff

File diff suppressed because it is too large Load diff