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

In anticipation of a successful 5.2 release sometime in the near

Browse source 
future, generate a set of HTML release documents.

Not hooked to the Web site build yet.
This commit is contained in:
Bruce A. Mah 2004-01-01 21:19:05 +00:00
parent dafa8789df
commit 471e604694
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=19422
20 changed files with 25415 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

511
en/releases/5.2R/early-adopter.html Normal file
View file

@ -0,0 +1,511 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>Early Adopter's Guide to FreeBSD 5.2-RELEASE</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
<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 id="AEN2" name="AEN2">Early Adopter's Guide to FreeBSD
5.2-RELEASE</a></h1>
<div class="AUTHORGROUP"><a id="AEN4" name="AEN4"></a>
<h3 class="CORPAUTHOR">The FreeBSD Release Engineering Team</h3>
</div>
<p class="COPYRIGHT">Copyright &copy; 2002, 2003 The FreeBSD Release Engineering Team</p>
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/early-adopter/article.sgml,v
1.17 2003/12/02 05:54:35 bmah Exp $<br />
</p>
<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a>
<p>FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to
change soon.</p>
<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States and
other countries.</p>
<p>Microsoft, FrontPage, MS-DOS, Outlook, Windows, Windows Media, and Windows NT are
either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.</p>
<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc
in the United States and other countries. Products bearing SPARC trademarks are based
upon architecture developed by Sun Microsystems, Inc.</p>
<p>Many of the designations used by manufacturers and sellers to distinguish their
products are claimed as trademarks. Where those designations appear in this document, and
the FreeBSD Project was aware of the trademark claim, the designations have been followed
by the ``&trade;'' or the ``&reg;'' symbol.</p>
</div>
<div>
<div class="ABSTRACT"><a id="AEN19" name="AEN19"></a>
<p>This article describes the status of FreeBSD 5.2-RELEASE, from the standpoint of users
who may be new to the 5.<var class="REPLACEABLE">X</var> series of releases or to FreeBSD
in general. It presents some background information on release engineering, some
highlights of new features, and some possible drawbacks that might be faced by early
adopters. It also contains some of the future release engineering plans for the 4-STABLE
development branch and some tips on upgrading existing systems.</p>
</div>
</div>
<hr />
</div>
<div class="SECT1">
<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
<p>FreeBSD 5.<var class="REPLACEABLE">X</var> 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.<var
class="REPLACEABLE">X</var> releases, the first few 5.<var class="REPLACEABLE">X</var>
releases may have regressions in areas of stability, performance, and occasionally
functionality.</p>
<p>For these reasons, the Release Engineering Team <code class="EMAIL">&#60;<a
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&#62;</code> specifically discourages
users from updating from older FreeBSD releases to 5.2-RELEASE unless they are aware of
(and prepared to deal with) possible regressions in the newer releases. Specifically, for
more conservative users, we recommend running 4.<var class="REPLACEABLE">X</var> releases
(such as 4.9-RELEASE) for the near-term future. We feel that such users are probably best
served by upgrading to 5.<var class="REPLACEABLE">X</var> only after a 5-STABLE
development branch has been created; this may be around the time of 5.3-RELEASE.</p>
<p>(FreeBSD 5.<var class="REPLACEABLE">X</var> suffers from what has been described as a
``chicken and egg'' problem. The entire project has a goal of producing releases that are
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.2-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.2-RELEASE, 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.<var
class="REPLACEABLE">X</var> systems to 5.2-RELEASE.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="RELEASE-OVERVIEW" name="RELEASE-OVERVIEW">2 An Overview of the
FreeBSD Release Process</a></h2>
<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 <var class="LITERAL">HEAD</var> 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.<var class="REPLACEABLE">X</var> releases were
based on it. This branch has the tag <var class="LITERAL">RELENG_4</var> in the CVS
repository.</p>
<p>FreeBSD 5.0, 5.1, and 5.2 are based on the CURRENT branch. The first of these releases
was made after over two years of development (prior to these, the last release from HEAD
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 <var class="LITERAL">RELENG_5</var>.
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 to stabilize before the new branches were
created. This in turn resulted in wasted effort porting bug fixes between branches, as
well as some architectural changes that could not be ported between branches at all.</p>
<p>Therefore, the release engineering team will only create the 5-STABLE branch in the
CVS repository after we have found a relatively stable state to use as its basis. It is
likely that there will be multiple releases in the 5.<var class="REPLACEABLE">X</var>
series before this happens; we estimate that the 5-STABLE branch will be created around
the time of 5.3-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 <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/index.html"
target="_top">``FreeBSD Release Engineering''</a> article. Specific issues for the
upcoming 5-STABLE development branch can be found in <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
target="_top">``The Roadmap for 5-STABLE''</a>.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="NEW" name="NEW">3 New Features</a></h2>
<p>A large attraction of FreeBSD 5.<var class="REPLACEABLE">X</var> 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). Ongoing
work aims to perform fine-grained locking of various kernel subsystems to increase the
number of threads of execution that can be running in the kernel. More information can be
found on the <a href="http://www.FreeBSD.org/smp/" target="_top">FreeBSD SMP Project</a>
page.</p>
</li>
<li>
<p>KSE: Kernel Scheduled Entities allow a single process to have multiple kernel-level
threads, similar to Scheduler Activations. The <tt class="FILENAME">libkse</tt> and <tt
class="FILENAME">libthr</tt> threading libraries make this feature available to
multi-threaded userland programs, using the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pthread&amp;sektion=3&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pthread</span>(3)</span></a>
API.</p>
</li>
<li>
<p>New architectures: Support for the sparc64, ia64, and amd64 architectures, in addition
to the i386, pc98, and alpha.</p>
</li>
<li>
<p>GCC: The compiler toolchain is now based on GCC 3.3.<var class="REPLACEABLE">X</var>,
rather than GCC 2.95.<var class="REPLACEABLE">X</var>.</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. The GBDE
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&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<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. UFS2 is now the default format for <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>. On all
platforms except for pc98, filesystems created from within <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
will use UFS2 by default.</p>
</li>
<li>
<p>Cardbus: Support for Cardbus devices.</p>
</li>
<li>
<p>Bluetooth: Support for Bluetooth devices.</p>
</li>
</ul>
<p>A more comprehensive list of new features can be found in the release notes for the
various FreeBSD 5.<var class="REPLACEABLE">X</var> releases.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="DRAWBACKS" name="DRAWBACKS">4 Drawbacks to Early
Adoption</a></h2>
<p>Along with the new features of FreeBSD 5.<var class="REPLACEABLE">X</var> 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. While suitable for testing and experimentation, these features may
not be ready for production use.</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. There is a
possibility of more minor ABI/API changes before the 5-STABLE branch is created,
particularly on newer machine architectures. In some (hopefully rare) cases, user-visible
structures may change, requiring recompiling of applications or reinstallation of
ports/packages.</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>Some parts of the FreeBSD base system have fallen into a state of disrepair due to a
lack of users and maintainers. These have been removed. Specific examples include the
generation of a.out-style executables, XNS networking support, and the X-10 controller
driver.</p>
</li>
<li>
<p>A number of ports and packages do not build or do not run correctly under FreeBSD
5.<var class="REPLACEABLE">X</var>, whereas they did under FreeBSD 4-STABLE. Generally
these problems are caused by compiler toolchain changes or cleanups of header files. In
some cases they are caused by changes in kernel or device support.</p>
</li>
<li>
<p>Many FreeBSD 5.<var class="REPLACEABLE">X</var> features are seeing wide exposure for
the first time. Many of these features (such as SMPng) have broad impacts on the kernel,
and it may be difficult to gauge their effects on stability and performance.</p>
</li>
<li>
<p>A certain amount of debugging and diagnostic code is still in place to help track down
problems in FreeBSD 5.<var class="REPLACEABLE">X</var>'s new features. This may cause
FreeBSD 5.<var class="REPLACEABLE">X</var> 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.<var class="REPLACEABLE">X</var> 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.3-RELEASE.)</p>
</li>
<li>
<p>Documentation (such as the FreeBSD <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/index.html"
target="_top">Handbook</a> and <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html"
target="_top">FAQ</a>) may not reflect changes recently made to FreeBSD 5.<var
class="REPLACEABLE">X</var>.</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.<var class="REPLACEABLE">X</var> series is more polished.
While we believe that many initial problems with stability have been fixed, some issues
with performance are still being addressed by works-in-progress. We also note that best
common practices in system administration call for trying operating system upgrades in a
test environment before upgrading one's production, or ``mission-critical'' systems.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="PLANS-STABLE" name="PLANS-STABLE">5 Plans for the 4-STABLE
Branch</a></h2>
<p>It is important to note that even though releases are being made in the 5.<var
class="REPLACEABLE">X</var> series, support for 4.<var class="REPLACEABLE">X</var>
releases will continue for some time. Indeed, FreeBSD 4.8 was released two months after
5.0, in April 2003, followed by 4.9, in October 2003. Future releases from the 4-STABLE
branch (if any) 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 <var class="LITERAL">HEAD</var> at the discretion of developers,
subject to existing release engineering policies.</p>
<p>To some extent, the release engineering team (as well as the developer community as a
whole) will take into account user demand for future 4-STABLE releases. This demand,
however, will need to be balanced with release engineering resources (particularly
developers' time, computing resources, and mirror archive space). We note that in
general, the FreeBSD community (both users and developers) has shown a preference for
moving forward with new features in the 5.<var class="REPLACEABLE">X</var> branch and
beyond, due to the difficulty involved in backporting (and maintaining) new functionality
in 4.<var class="REPLACEABLE">X</var>.</p>
<p>The Security Officer Team <code class="EMAIL">&#60;<a
href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&#62;</code>
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 for specific issues.</p>
<p>At this point, the release engineering team has no specific plans for future releases
from the 4-STABLE development branch. It seems likely that any future releases (if any)
from this branch will be lightweight, ``point'' releases. These will probably carry
4.9.<var class="REPLACEABLE">X</var> version numbers, to indicate that they are not
intended to provide large amount of new functionality compared to 4.9-RELEASE. In
general, these releases will emphasize security fixes, bug fixes, and device driver
updates (particularly to accommodate new hardware easily supported by existing drivers).
Major new features (especially those requiring infrastructure support added in 5.<var
class="REPLACEABLE">X</var>) will probably not be added in these releases.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">6 Notes on Upgrading from FreeBSD 4.<var
class="REPLACEABLE">X</var></a></h2>
<p>For those users with existing FreeBSD systems, this section offers a few notes on
upgrading a FreeBSD 4.<var class="REPLACEABLE">X</var> system to 5.<var
class="REPLACEABLE">X</var>. 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> in the case of source upgrades.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN165" name="AEN165">6.1 Binary Upgrades</a></h3>
<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. It allows new filesystems to
be created to take advantage of new functionality (most notably, the UFS2 defaults).</p>
<p>As of this time, the binary upgrade option in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<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. In particular, a binary upgrade will leave behind a number of files that are
present in FreeBSD 4.<var class="REPLACEABLE">X</var> but not in 5.<var
class="REPLACEABLE">X</var>. These obsolete files may create some problems. Examples of
these files include old C++ headers, programs moved to the Ports Collection, or shared
libraries that have moved to support dynamically-linked root filesystem executables.</p>
<p>On the <span class="TRADEMARK">i386</span>&#8482; 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.<var class="REPLACEABLE">X</var>, this
functionality has been replaced in part by the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=device.hints&amp;sektion=5&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">device.hints</span>(5)</span></a>
mechanism (it allows specifying the same parameters, but with a very different
interface).</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 <span class="TRADEMARK">i386</span> architecture now
use a ``no-emulation'' boot loader. This allows, among other things, the use of a <var
class="LITERAL">GENERIC</var> kernel, rather than the stripped-down kernel on the floppy
images. In theory, any system capable of booting the <span
class="TRADEMARK">Microsoft</span>&reg; <span
class="TRADEMARK">Windows&nbsp;NT</span>&reg; 4 installation CDROMs should be able to
cope with the FreeBSD 5.<var class="REPLACEABLE">X</var> CDROMs.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN192" name="AEN192">6.2 Source Upgrades</a></h3>
<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 />
<h3 class="SECT2"><a id="AEN198" name="AEN198">6.3 Common Notes</a></h3>
<p><b class="APPLICATION">Perl</b> has been removed from the base system, and should be
installed 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). <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
will now install the Perl package as a part of most distribution sets, so most users will
not notice this change.</p>
<p>It is generally possible to run old 4.<var class="REPLACEABLE">X</var> executables
under 5.<var class="REPLACEABLE">X</var>, but this requires the <tt
class="FILENAME">compat4x</tt> distribution to be installed. Using old ports may be
possible in some cases, although there are a number of known cases of backward
incompatibility. As an example, the <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/devel/gnomevfs2/pkg-descr"><tt
class="FILENAME">devel/gnomevfs2</tt></a>, <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/mail/postfix/pkg-descr"><tt
class="FILENAME">mail/postfix</tt></a>, and <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/security/cfs/pkg-descr"><tt
class="FILENAME">security/cfs</tt></a> ports need to be recompiled due to changes in the
<var class="LITERAL">statfs</var> structure.</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 <var class="LITERAL">installworld</var> 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>
<p><tt class="FILENAME">MAKEDEV</tt> is no longer available, nor is it required. FreeBSD
5.<var class="REPLACEABLE">X</var> uses a device filesystem, which automatically creates
device nodes on demand. For more information, please see <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&amp;sektion=5&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devfs</span>(5)</span></a>.</p>
<p>UFS2 is the default on-disk format for file systems created using <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>. For
all platforms except pc98, it is also the default for file systems created using the disk
labeling screen within <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>.
Because FreeBSD 4.<var class="REPLACEABLE">X</var> only understands UFS1 (not UFS2), disk
partitions that need to be accessed by both 5.<var class="REPLACEABLE">X</var> and 4.<var
class="REPLACEABLE">X</var> must be created with UFS1. This can be specified using the
<var class="OPTION">-O1</var> option to <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>, or on
the disk labeling screen in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>.
This situation most often arises with a a single machine that dual-boots FreeBSD 4.<var
class="REPLACEABLE">X</var> and FreeBSD 5.<var class="REPLACEABLE">X</var>. Note that
there is no way to convert file systems between the two on-disk formats (other than
backing up, re-creating the file system, and restoring).</p>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="SUMMARY" name="SUMMARY">7 Summary</a></h2>
<p>While FreeBSD 5.2-RELEASE 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.<var
class="REPLACEABLE">X</var> 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="ftp://ftp.FreeBSD.org/">ftp://ftp.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>For questions about this documentation, e-mail &#60;<a
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
<br />
<br />
</body>
</html>

4297
en/releases/5.2R/hardware-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

1572
en/releases/5.2R/hardware-amd64.html Normal file
View file

File diff suppressed because it is too large Load diff

2314
en/releases/5.2R/hardware-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

622
en/releases/5.2R/hardware-ia64.html Normal file
View file

@ -0,0 +1,622 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>FreeBSD/ia64 5.2-RELEASE Hardware Notes</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
<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 id="AEN2" name="AEN2">FreeBSD/ia64 5.2-RELEASE Hardware
Notes</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
Project</p>
<hr />
</div>
<div class="TOC">
<dl>
<dt><b>Table of Contents</b></dt>
<dt>1 <a href="#INTRO">Introduction</a></dt>
<dt>2 <a href="#PROC-IA64">Supported Processors and Motherboards</a></dt>
<dd>
<dl>
<dt>2.1 <a href="#AEN38">Supported Devices Overview</a></dt>
</dl>
</dd>
<dt>3 <a href="#SUPPORT">Supported Devices</a></dt>
<dd>
<dl>
<dt>3.1 <a href="#AEN94">Disk Controllers</a></dt>
<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt>
<dt>3.3 <a href="#AEN815">FDDI Interfaces</a></dt>
<dt>3.4 <a href="#AEN825">ATM Interfaces</a></dt>
<dt>3.5 <a href="#AEN844">Wireless Network Interfaces</a></dt>
<dt>3.6 <a href="#AEN870">Miscellaneous Networks</a></dt>
<dt>3.7 <a href="#AEN893">ISDN Interfaces</a></dt>
<dt>3.8 <a href="#AEN957">Serial Interfaces</a></dt>
<dt>3.9 <a href="#AEN1130">Audio Devices</a></dt>
<dt>3.10 <a href="#AEN1252">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="#BLUETOOTH">Bluetooth Devices</a></dt>
<dt>3.14 <a href="#AEN1480">Cryptographic Accelerators</a></dt>
<dt>3.15 <a href="#AEN1498">Miscellaneous</a></dt>
</dl>
</dd>
</dl>
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT"><a id="AEN11" name="AEN11"></a>
<p>This is a preliminary document. It is incomplete, and in need of additional content.
Please send additional information on IA-64 processors, motherboards, and various devices
working on FreeBSD to the <a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ia64" target="_top">FreeBSD IA64
porting mailing list</a>.</p>
</div>
</blockquote>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
<p>This document contains the hardware compatibility notes for FreeBSD 5.2-RELEASE on the
IA-64 hardware platform (also referred to as FreeBSD/ia64 5.2-RELEASE). 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>
<p>More information on FreeBSD/ia64 is contained on the <a
href="http://www.FreeBSD.org/platforms/ia64/index.html" target="_top">FreeBSD/ia64
Project</a> page.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="PROC-IA64" name="PROC-IA64">2 Supported Processors and
Motherboards</a></h2>
<p>Currently supported processors are the <a
href="http://www.intel.com/design/itanium/itanium/index.htm" target="_top">Itanium</a>
and the <a href="http://www.intel.com/design/itanium2/index.htm" target="_top">Itanium
2</a>.</p>
<p>Supported chipsets include:</p>
<ul>
<li>
<p>HP zx1 (only on development branch, see the <a href="http://perforce.freebsd.org/"
target="_top">Perforce repository</a>)</p>
</li>
<li>
<p>HP i2000</p>
</li>
<li>
<p>Intel 460GX</p>
</li>
<li>
<p>Intel E8870</p>
</li>
</ul>
<p>Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) configurations are under
active development. At this time, SMP-enabled systems are considered less stable. The
current priorities are UP fixes to improve stability.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN38" name="AEN38">2.1 Supported Devices Overview</a></h3>
<p>This section contains additional information about what devices may or may not be
supported by FreeBSD/ia64.</p>
<p>Except for the PC chipset embedded <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a>
controllers, most should work out of the box. Eventually, all ia64-compatible ATA
controllers are expected to be fully supported. Refer to the following sections for
various disk controllers and their current status.</p>
<p>In general, ``PC standard'' serial ports supported by the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> driver
are expected to work on Intel legacy machines, but not PA legacy machines. The reason is
that all devices on HP machines are memory-mapped and there is <span class="emphasis"><i
class="EMPHASIS">no</i></span> ISA device support other than the PCI dictated VGA
legacy.</p>
<p>In addition to <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a> devices,
the following devices fail on non-Intel legacy machines (but should work on boxes with an
Intel legacy) because their drivers make ISA-specific assumptions that do not hold:</p>
<div class="INFORMALTABLE"><a id="AEN55" name="AEN55"></a>
<table border="0" frame="void" class="CALSTABLE">
<col />
<col />
<tbody>
<tr>
<td><a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a></td>
<td>No support for memory-mapped I/O</td>
</tr>
<tr>
<td><a
href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a></td>
<td>Expect BIOS, VGA probes, etc.</td>
</tr>
<tr>
<td><a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcm</span>(4)</span></a></td>
<td>Probes MSS ISA ports <span class="emphasis"><i class="EMPHASIS">ad
nauseum</i></span></td>
</tr>
<tr>
<td><a
href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a>, <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">psm</span>(4)</span></a></td>
<td>Fixed ISA port locations</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 Supported Devices</a></h2>
$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.209 2003/12/07
00:54:22 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. Information on specific models of supported devices,
controllers, etc. can be found in the manual pages.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Lists of specific, supported devices are gradually being removed from
this document in order to reduce the amount of duplicated (and potentially out-of-date)
information contained within. When this process is complete, the manual page for each
driver should be consulted for the authoritative list of devices supported that
particular driver.</p>
</blockquote>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN94" name="AEN94">3.1 Disk Controllers</a></h3>
<p>IDE/ATA controllers (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a>
driver)</p>
<ul>
<li>
<p>Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6</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, nForce2 ATA133</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 SATA150 TX2/TX4 Serial ATA/150</p>
</li>
<li>
<p>Promise Ultra-33, -66, -100, -133 TX2/TX2000/TX4000</p>
</li>
<li>
<p>ServerWorks ROSB4 ATA33</p>
</li>
<li>
<p>ServerWorks CSB5 and CSB6 ATA66/ATA100</p>
</li>
<li>
<p>Sil 0680 UDMA6</p>
</li>
<li>
<p>SiS 530, 540, 550, 620</p>
</li>
<li>
<p>SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735,
740, 745, 746, 748, 750, 751, 752, 755</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&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a>
driver)</p>
<p>LSI Logic Fusion/MP architecture Fiber Channel controllers (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a>
driver)</p>
<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&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<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&amp;sektion=1&amp;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&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<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&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acd</span>(4)</span></a>)</p>
</li>
</ul>
<br />
<br />
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 Ethernet Interfaces</a></h3>
<p>Intel 82557-, 82258-, 82559-, 82550- or 82562-based Fast Ethernet NICs (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<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 Broadcom BCM570x (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bge</span>(4)</span></a>
driver)</p>
<p>Gigabit Ethernet NICs based on the Intel 82542 and 82543 controller chips (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=gx&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gx</span>(4)</span></a> and <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=em&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<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&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver
only)</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN815" name="AEN815">3.3 FDDI Interfaces</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN825" name="AEN825">3.4 ATM Interfaces</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN844" name="AEN844">3.5 Wireless Network Interfaces</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN870" name="AEN870">3.6 Miscellaneous Networks</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN893" name="AEN893">3.7 ISDN Interfaces</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN957" name="AEN957">3.8 Serial Interfaces</a></h3>
<p>``PC standard'' 8250, 16450, and 16550-based serial ports (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sio</span>(4)</span></a>
driver)</p>
<p>PCI-Based multi-port serial boards (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=puc&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">puc</span>(4)</span></a>
driver)</p>
<ul>
<li>
<p>Diva Serial (GSP) Multiport UART (development branch only)</p>
</li>
</ul>
<br />
<br />
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN1130" name="AEN1130">3.9 Audio Devices</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN1252" name="AEN1252">3.10 Camera and Video Capture
Devices</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="USB" name="USB">3.11 USB Devices</a></h3>
<p>OHCI 1.0-compliant host controllers (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ohci</span>(4)</span></a>
driver)</p>
<p>UHCI 1.1-compliant host controllers (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">uhci</span>(4)</span></a>
driver)</p>
<p>USB 2.0 controllers using the EHCI interface (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ehci</span>(4)</span></a>
driver)</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 IEEE 1394 (Firewire)
Devices</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.13 Bluetooth Devices</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN1480" name="AEN1480">3.14 Cryptographic Accelerators</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN1498" name="AEN1498">3.15 Miscellaneous</a></h3>
<p>VGA-compatible video cards (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vga&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vga</span>(4)</span></a>
driver)</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Information regarding specific video cards and compatibility with <b
class="APPLICATION">XFree86</b> can be found at <a href="http://www.xfree86.org/"
target="_top">http://www.xfree86.org/</a>.</p>
</blockquote>
</div>
<br />
<br />
<p>Keyboards including:</p>
<ul>
<li>
<p>PS/2 keyboards (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">atkbd</span>(4)</span></a>
driver)</p>
</li>
</ul>
<br />
<br />
<p>Pointing devices including:</p>
<ul>
<li>
<p>PS/2 mice and compatible devices, including many laptop pointing devices (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">psm</span>(4)</span></a>
driver)</p>
</li>
<li>
<p>Serial mice and compatible devices</p>
</li>
</ul>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">moused</span>(8)</span></a> has
more information on using pointing devices with FreeBSD. Information on using pointing
devices with <b class="APPLICATION">XFree86</b> can be found at <a
href="http://www.xfree86.org/" target="_top">http://www.xfree86.org/</a>.</p>
</blockquote>
</div>
<br />
<br />
</div>
</div>
</div>
<hr />
<p align="center"><small>This file, and other release-related documents, can be
downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.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>For questions about this documentation, e-mail &#60;<a
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
<br />
<br />
</body>
</html>

1790
en/releases/5.2R/hardware-pc98.html Normal file
View file

File diff suppressed because it is too large Load diff

633
en/releases/5.2R/hardware-sparc64.html Normal file
View file

@ -0,0 +1,633 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>FreeBSD/sparc64 5.2-RELEASE Hardware Notes</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
<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 id="AEN2" name="AEN2">FreeBSD/sparc64 5.2-RELEASE Hardware
Notes</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Documentation Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
Project</p>
<hr />
</div>
<div class="TOC">
<dl>
<dt><b>Table of Contents</b></dt>
<dt>1 <a href="#INTRO">Introduction</a></dt>
<dt>2 <a href="#SUPPORT-SYS">Supported Systems</a></dt>
<dd>
<dl>
<dt>2.1 <a href="#AEN25">Fully Supported Systems</a></dt>
<dt>2.2 <a href="#AEN75">Partially Supported Systems</a></dt>
<dt>2.3 <a href="#AEN87">Unsupported Systems</a></dt>
</dl>
</dd>
<dt>3 <a href="#SUPPORT">Supported Devices</a></dt>
<dd>
<dl>
<dt>3.1 <a href="#AEN103">Disk Controllers</a></dt>
<dt>3.2 <a href="#ETHERNET">Ethernet Interfaces</a></dt>
<dt>3.3 <a href="#AEN824">FDDI Interfaces</a></dt>
<dt>3.4 <a href="#AEN834">ATM Interfaces</a></dt>
<dt>3.5 <a href="#AEN853">Wireless Network Interfaces</a></dt>
<dt>3.6 <a href="#AEN879">Miscellaneous Networks</a></dt>
<dt>3.7 <a href="#AEN902">ISDN Interfaces</a></dt>
<dt>3.8 <a href="#AEN966">Serial Interfaces</a></dt>
<dt>3.9 <a href="#AEN1139">Audio Devices</a></dt>
<dt>3.10 <a href="#AEN1261">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="#BLUETOOTH">Bluetooth Devices</a></dt>
<dt>3.14 <a href="#AEN1489">Cryptographic Accelerators</a></dt>
<dt>3.15 <a href="#AEN1507">Miscellaneous</a></dt>
</dl>
</dd>
</dl>
</div>
<div class="SECT1">
<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
<p>This document contains the hardware compatibility notes for FreeBSD 5.2-RELEASE on the
UltraSPARC hardware platform (also referred to as FreeBSD/sparc64 5.2-RELEASE). 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 />
<h2 class="SECT1"><a id="SUPPORT-SYS" name="SUPPORT-SYS">2 Supported Systems</a></h2>
<p>This section describes the systems currently known to be supported by FreeBSD on the
UltraSPARC platform. For background information on the various hardware designs see the
<a href="http://sunsolve.sun.com/handbook_pub/" target="_top">Sun System
Handbook</a>.</p>
<p>SMP is supported on all systems with more than 1 processor.</p>
<p>If you have a system that is not listed here, it may not have been tested with FreeBSD
5.2-RELEASE. We encourage you to try it and send a note to the <a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-sparc64" target="_top">FreeBSD
SPARC porting mailing list</a> with your results, including which devices work and which
do not.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN25" name="AEN25">2.1 Fully Supported Systems</a></h3>
<p>The following systems are fully supported by FreeBSD.</p>
<ul>
<li>
<p>Blade 100</p>
</li>
<li>
<p>Blade 150</p>
</li>
<li>
<p>Enterprise 220R</p>
</li>
<li>
<p>Enterprise 250</p>
</li>
<li>
<p>Enterprise 420R</p>
</li>
<li>
<p>Enterprise 450</p>
</li>
<li>
<p>Fire V100</p>
</li>
<li>
<p>Fire V120</p>
</li>
<li>
<p>Netra t1 105</p>
</li>
<li>
<p>Netra T1 AC200/DC200</p>
</li>
<li>
<p>Netra t 1100</p>
</li>
<li>
<p>Netra t 1120</p>
</li>
<li>
<p>Netra t 1125</p>
</li>
<li>
<p>Netra t 1400/1405</p>
</li>
<li>
<p>Netra 120</p>
</li>
<li>
<p>Netra X1</p>
</li>
<li>
<p>SPARCEngine Ultra AXi</p>
</li>
<li>
<p>SPARCEngine Ultra AXmp</p>
</li>
<li>
<p>Ultra 5</p>
</li>
<li>
<p>Ultra 10</p>
</li>
<li>
<p>Ultra 30</p>
</li>
<li>
<p>Ultra 60</p>
</li>
<li>
<p>Ultra 80</p>
</li>
</ul>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN75" name="AEN75">2.2 Partially Supported Systems</a></h3>
<p>The following systems are partially supported by FreeBSD. In particular the onboard
scsi controller in sbus systems is not supported.</p>
<ul>
<li>
<p>Enterprise 3500</p>
</li>
<li>
<p>Enterprise 4500</p>
</li>
<li>
<p>Ultra 1 Enterprise (1E for short)</p>
</li>
<li>
<p>Ultra 2</p>
</li>
</ul>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN87" name="AEN87">2.3 Unsupported Systems</a></h3>
<p>The following systems are not supported by FreeBSD. This may be due to lack of
processor support (UltraSPARC III), due to a quirk in the system design that makes
FreeBSD unstable, or due to lack of support for sufficient onboard devices to make
FreeBSD generally useful.</p>
<ul>
<li>
<p>All systems containing UltraSPARC III processor(s).</p>
</li>
<li>
<p>Ultra 1</p>
</li>
</ul>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 Supported Devices</a></h2>
$FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v 1.209 2003/12/07
00:54:22 bmah 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. Information on specific models of supported devices,
controllers, etc. can be found in the manual pages.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Lists of specific, supported devices are gradually being removed from
this document in order to reduce the amount of duplicated (and potentially out-of-date)
information contained within. When this process is complete, the manual page for each
driver should be consulted for the authoritative list of devices supported that
particular driver.</p>
</blockquote>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN103" name="AEN103">3.1 Disk Controllers</a></h3>
<p>IDE/ATA controllers (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a>
driver)</p>
<ul>
<li>
<p>Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6</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, nForce2 ATA133</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 SATA150 TX2/TX4 Serial ATA/150</p>
</li>
<li>
<p>Promise Ultra-33, -66, -100, -133 TX2/TX2000/TX4000</p>
</li>
<li>
<p>ServerWorks ROSB4 ATA33</p>
</li>
<li>
<p>ServerWorks CSB5 and CSB6 ATA66/ATA100</p>
</li>
<li>
<p>Sil 0680 UDMA6</p>
</li>
<li>
<p>SiS 530, 540, 550, 620</p>
</li>
<li>
<p>SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 730, 733, 735,
740, 745, 746, 748, 750, 751, 752, 755</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>Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880, and AIC789x based SCSI host
adapters (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahc</span>(4)</span></a>
driver)</p>
<p>Ultra-320 SCSI controllers based on the Adaptec AIC7901, AIC7901A, and AIC7902
Ultra320 controller chips (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ahd&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ahd</span>(4)</span></a>
driver)</p>
<p>LSI/Symbios (formerly NCR) 53C8<var class="REPLACEABLE">XX</var> and 53C10<var
class="REPLACEABLE">XX</var> PCI SCSI controllers, either embedded on motherboard or on
add-on boards (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ncr</span>(4)</span></a> and <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sym</span>(4)</span></a>
drivers)</p>
<p>Qlogic controllers and variants (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">isp</span>(4)</span></a>
driver)</p>
<p>LSI Logic Fusion/MP architecture Fiber Channel controllers (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a>
driver)</p>
<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&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<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&amp;sektion=1&amp;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&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<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&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acd</span>(4)</span></a>)</p>
</li>
</ul>
<br />
<br />
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 Ethernet Interfaces</a></h3>
<p>RealTek 8129/8139 Fast Ethernet NICs (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rl</span>(4)</span></a>
driver)</p>
<p>DEC/Intel 21143 Fast Ethernet NICs and clones for PCI, MiniPCI, and CardBus (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dc</span>(4)</span></a>
driver)</p>
<p>Intel 82557-, 82258-, 82559-, 82550- or 82562-based Fast Ethernet NICs (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<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 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>
</ul>
<br />
<br />
<p>3Com Etherlink XL-based NICs (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">xl</span>(4)</span></a>
driver)</p>
<p>Sun HME and QFE Ethernet NICs (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=hme&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hme</span>(4)</span></a>
driver)</p>
<p>Sun GEM (Gigabit Ethernet) and ERI (Fast Ethernet) NICs (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=gem&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gem</span>(4)</span></a>
driver)</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN824" name="AEN824">3.3 FDDI Interfaces</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN834" name="AEN834">3.4 ATM Interfaces</a></h3>
<p>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=fatm&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fatm</span>(4)</span></a>
drivers)</p>
<p>FORE Systems, Inc. HE155 and HE622 ATM interfaces (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=hatm&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hatm</span>(4)</span></a>
driver)</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN853" name="AEN853">3.5 Wireless Network Interfaces</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN879" name="AEN879">3.6 Miscellaneous Networks</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN902" name="AEN902">3.7 ISDN Interfaces</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN966" name="AEN966">3.8 Serial Interfaces</a></h3>
<p>Serial ports based on the SAB82532 serial chip, console only (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sab&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sab</span>(4)</span></a>
driver)</p>
<p>Serial ports based on the Zilog 8530 dual uart, console only (zs driver)</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN1139" name="AEN1139">3.9 Audio Devices</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN1261" name="AEN1261">3.10 Camera and Video Capture
Devices</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="USB" name="USB">3.11 USB Devices</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 IEEE 1394 (Firewire)
Devices</a></h3>
<p>Host Controllers (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=fwohci&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fwohci</span>(4)</span></a>
driver)</p>
<p>Serial Bus Protocol 2 (SBP-2) storage devices (<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sbp&amp;sektion=4&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sbp</span>(4)</span></a>
driver)</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.13 Bluetooth Devices</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN1489" name="AEN1489">3.14 Cryptographic Accelerators</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN1507" name="AEN1507">3.15 Miscellaneous</a></h3>
<p>OpenFirmware console (ofwcons driver)</p>
</div>
</div>
</div>
<hr />
<p align="center"><small>This file, and other release-related documents, can be
downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.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>For questions about this documentation, e-mail &#60;<a
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
<br />
<br />
</body>
</html>

1167
en/releases/5.2R/installation-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

1092
en/releases/5.2R/installation-amd64.html Normal file
View file

File diff suppressed because it is too large Load diff

1562
en/releases/5.2R/installation-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

870
en/releases/5.2R/installation-ia64.html Normal file
View file

@ -0,0 +1,870 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>FreeBSD/ia64 5.2-RELEASE Installation Instructions</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
<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 id="AEN2" name="AEN2">FreeBSD/ia64 5.2-RELEASE Installation
Instructions</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
Project</p>
<hr />
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT"><a id="AEN11" name="AEN11"></a>
<p>This article gives some brief instructions on installing FreeBSD/ia64 5.2-RELEASE,
with particular emphasis given to obtaining a FreeBSD distribution. Some notes on
troubleshooting and frequently-asked questions are also given.</p>
</div>
</blockquote>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="INSTALL" name="INSTALL">1 Installing FreeBSD</a></h2>
<p>This section documents the process of installing a new distribution of FreeBSD. These
instructions pay particular emphasis to the process of obtaining the FreeBSD 5.2-RELEASE
distribution and to beginning the installation procedure. The <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"
target="_top">``Installing FreeBSD''</a> chapter of the <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
Handbook</a> provides more in-depth information about the installation program itself,
including a guided walkthrough with screenshots.</p>
<p>If you are upgrading from a previous release of FreeBSD, please see <a
href="#UPGRADING">Section 3</a> for instructions on upgrading.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="GETTING-STARTED" name="GETTING-STARTED">1.1 Getting
Started</a></h3>
<p>Probably the most important pre-installation step that can be taken is that of reading
the various instruction documents provided with FreeBSD. A roadmap of documents
pertaining to this release of FreeBSD can be found in <tt
class="FILENAME">README.TXT</tt>, which can usually be found in the same location as this
file; most of these documents, such as the release notes and the hardware compatibility
list, are also accessible in the Documentation menu of the installer.</p>
<p>Note that on-line versions of the FreeBSD <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/" target="_top">FAQ</a> and <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
target="_top">Handbook</a> are also available from the <a href="http://www.FreeBSD.org/"
target="_top">FreeBSD Project Web site</a>, if you have an Internet connection.</p>
<p>This collection of documents may seem daunting, but the time spent reading them will
likely be saved many times over. Being familiar with what resources are available can
also be helpful in the event of problems during installation.</p>
<p>The best laid plans sometimes go awry, so if you run into trouble take a look at <a
href="#TROUBLE">Section 4</a>, which contains valuable troubleshooting information. You
should also read an updated copy of <tt class="FILENAME">ERRATA.TXT</tt> before
installing, since this will alert you to any problems which have reported in the interim
for your particular release.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> While FreeBSD does its best to safeguard against accidental loss of
data, it's still more than possible to <span class="emphasis"><i class="EMPHASIS">wipe
out your entire disk</i></span> with this installation if you make a mistake. Please do
not proceed to the final FreeBSD installation menu unless you've adequately backed up any
important data first.</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware Requirements</a></h3>
<p>If you are not familiar with configuring hardware for FreeBSD, you should be sure to
read the <tt class="FILENAME">HARDWARE.TXT</tt> file; it contains important information
on what hardware is supported by FreeBSD.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 Floppy Disk Image
Instructions</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="START-INSTALLATION" name="START-INSTALLATION">1.4 Installing
FreeBSD from CDROM or the Internet</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN212" name="AEN212">1.5 Detail on various installation
types</a></h3>
<p>Once you've gotten yourself to the initial installation screen somehow, you should be
able to follow the various menu prompts and go from there. If you've never used the
FreeBSD installation before, you are also encouraged to read some of the documentation in
the Documentation submenu as well as the general ``Usage'' instructions on the first
menu.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> If you get stuck at a screen, press the <b class="KEYCAP">F1</b> key for
online documentation relevant to that specific section.</p>
</blockquote>
</div>
<p>If you've never installed FreeBSD before, or even if you have, the ``Standard''
installation mode is the most recommended since it makes sure that you'll visit all the
various important checklist items along the way. If you're much more comfortable with the
FreeBSD installation process and know <span class="emphasis"><i
class="EMPHASIS">exactly</i></span> what you want to do, use the ``Express'' or
``Custom'' installation options. If you're upgrading an existing system, use the
``Upgrade'' option.</p>
<p>The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS
and UFS partitions as installation media; further tips on installing from each type of
media are listed below.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN251" name="AEN251">1.5.1 Installing from a Network
CDROM</a></h4>
<p>If you simply wish to install from a local CDROM drive then see <a
href="#START-INSTALLATION">Section 1.4</a>. If you don't have a CDROM drive on your
system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to
which you have network connectivity, there are also several ways of going about it:</p>
<ul>
<li>
<p>If you would be able to FTP install FreeBSD directly from the CDROM drive in some
FreeBSD machine, it's quite easy: You simply add the following line to the password file
(using the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vipw</span>(8)</span></a>
command):</p>
<pre class="SCREEN">
ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
</pre>
<p>On the machine on which you are running the install, go to the Options menu and set
Release Name to <var class="LITERAL">any</var>. You may then choose a Media type of <var
class="LITERAL">FTP</var> and type in <tt class="FILENAME">ftp://<var
class="REPLACEABLE">machine</var></tt> after picking ``URL'' in the ftp sites menu.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> This may allow anyone on the local network (or Internet) to make
``anonymous FTP'' connections to this machine, which may not be desirable.</p>
</blockquote>
</div>
</li>
<li>
<p>If you would rather use NFS to export the CDROM directly to the machine(s) you'll be
installing from, you need to first add an entry to the <tt
class="FILENAME">/etc/exports</tt> file (on the machine with the CDROM drive). The
example below allows the machine <tt class="HOSTID">ziggy.foo.com</tt> to mount the CDROM
directly via NFS during installation:</p>
<pre class="SCREEN">
/cdrom -ro ziggy.foo.com
</pre>
<p>The machine with the CDROM must also be configured as an NFS server, of course, and if
you're not sure how to do that then an NFS installation is probably not the best choice
for you unless you're willing to read up on <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.conf&amp;sektion=5&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rc.conf</span>(5)</span></a> and
configure things appropriately. Assuming that this part goes smoothly, you should be able
to enter: <tt class="FILENAME"><var class="REPLACEABLE">cdrom-host</var>:/cdrom</tt> as
the path for an NFS installation when the target machine is installed, e.g. <tt
class="FILENAME">wiggy:/cdrom</tt>.</p>
</li>
</ul>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN283" name="AEN283">1.5.2 Installing from Floppies</a></h4>
<p>If you must install from floppy disks, either due to unsupported hardware or just
because you enjoy doing things the hard way, you must first prepare some floppies for the
install.</p>
<p>First, make your boot floppies as described in <a href="#FLOPPIES">Section
1.3</a>.</p>
<p>Second, peruse <a href="#LAYOUT">Section 2</a> and pay special attention to the
``Distribution Format'' section since it describes which files you're going to need to
put onto floppy and which you can safely skip.</p>
<p>Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files
in the <tt class="FILENAME">bin</tt> (binary distribution) directory. If you're preparing
these floppies under DOS, then these floppies <span class="emphasis"><i
class="EMPHASIS">must</i></span> be formatted using the MS-DOS <tt
class="FILENAME">FORMAT</tt> command. If you're using Windows, use the Windows File
Manager format command.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> Frequently, floppy disks come ``factory preformatted''. While
convenient, many problems reported by users in the past have resulted from the use of
improperly formatted media. Re-format them yourself, just to make sure.</p>
</blockquote>
</div>
<p>If you're creating the floppies from another FreeBSD machine, a format is still not a
bad idea though you don't need to put a DOS filesystem on each floppy. You can use the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>
commands to put a UFS filesystem on a floppy, as the following sequence of commands
illustrates:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">fdformat -f 1440 fd0.1440</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">disklabel -w -r fd0.1440 floppy3</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</kbd>
</pre>
<p>After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto
them. The distribution files are split into chunks conveniently sized so that 5 of them
will fit on a conventional 1.44MB floppy. Go through all your floppies, packing as many
files as will fit on each one, until you've got all the distributions you want packed up
in this fashion. Each distribution should go into its own subdirectory on the floppy,
e.g.: <tt class="FILENAME">a:\bin\bin.inf</tt>, <tt class="FILENAME">a:\bin\bin.aa</tt>,
<tt class="FILENAME">a:\bin\bin.ab</tt>, ...</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> The <tt class="FILENAME">bin.inf</tt> file also needs to go on the
first floppy of the <tt class="FILENAME">bin</tt> set since it is read by the
installation program in order to figure out how many additional pieces to look for when
fetching and concatenating the distribution. When putting distributions onto floppies,
the <tt class="FILENAME">distname.inf</tt> file <span class="emphasis"><i
class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set. This
is also covered in <tt class="FILENAME">README.TXT</tt>.</p>
</blockquote>
</div>
<p>Once you come to the Media screen of the install, select ``Floppy'' and you'll be
prompted for the rest.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN353" name="AEN353">1.5.4 Installing from QIC/SCSI
Tape</a></h4>
<p>When installing from tape, the installation program expects the files to be simply
tar'ed onto it, so after fetching all of the files for the distributions you're
interested in, simply use <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tar</span>(1)</span></a> to get
them onto the tape with a command something like this:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd <var
class="REPLACEABLE">/where/you/have/your/dists</var></kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/rsa0 <var
class="REPLACEABLE">dist1</var> .. <var class="REPLACEABLE">dist2</var></kbd>
</pre>
<p>When you go to do the installation, you should also make sure that you leave enough
room in some temporary directory (which you'll be allowed to choose) to accommodate the
<span class="emphasis"><i class="EMPHASIS">full</i></span> contents of the tape you've
created. Due to the non-random access nature of tapes, this method of installation
requires quite a bit of temporary storage. You should expect to require as much temporary
storage as you have stuff written on tape.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> When going to do the installation, the tape must be in the drive <span
class="emphasis"><i class="EMPHASIS">before</i></span> booting from the boot floppies.
The installation ``probe'' may otherwise fail to find it.</p>
</blockquote>
</div>
<p>Now create a boot floppy as described in <a href="#FLOPPIES">Section 1.3</a> and
proceed with the installation.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 Installing over a Network using FTP
or NFS</a></h4>
<p>After making the boot floppies as described in the first section, you can load the
rest of the installation over a network using one of 3 types of connections: serial port,
parallel port, or Ethernet.</p>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN378" name="AEN378">1.5.5.1 Serial Port</a></h5>
<p>SLIP support is rather primitive, and is limited primarily to hard-wired links, such
as a serial cable running between two computers. The link must be hard-wired because the
SLIP installation doesn't currently offer a dialing capability. If you need to dial out
with a modem or otherwise dialog with the link before connecting to it, then I recommend
that the PPP utility be used instead.</p>
<p>If you're using PPP, make sure that you have your Internet Service Provider's IP
address and DNS information handy as you'll need to know it fairly early in the
installation process. You may also need to know your own IP address, though PPP supports
dynamic address negotiation and may be able to pick up this information directly from
your ISP if they support it.</p>
<p>You will also need to know how to use the various ``AT commands'' for dialing out with
your particular brand of modem as the PPP dialer provides only a very simple terminal
emulator.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN384" name="AEN384">1.5.5.2 Parallel Port</a></h5>
<p>If a hard-wired connection to another FreeBSD or Linux machine is available, you might
also consider installing over a ``laplink'' style parallel port cable. The data rate over
the parallel port is much higher than what is typically possible over a serial line (up
to 50k/sec), thus resulting in a quicker installation. It's not typically necessary to
use ``real'' IP addresses when using a point-to-point parallel cable in this way and you
can generally just use RFC 1918 style addresses for the ends of the link (e.g. <tt
class="HOSTID">10.0.0.1</tt>, <tt class="HOSTID">10.0.0.2</tt>, etc).</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> If you use a Linux machine rather than a FreeBSD machine as your
PLIP peer, you will also have to specify <var class="OPTION">link0</var> in the TCP/IP
setup screen's ``extra options for ifconfig'' field in order to be compatible with
Linux's slightly different PLIP protocol.</p>
</blockquote>
</div>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5>
<p>FreeBSD supports many common Ethernet cards; a table of supported cards is provided as
part of the FreeBSD Hardware Notes (see <tt class="FILENAME">HARDWARE.TXT</tt> in the
Documentation menu on the boot floppy or the top level directory of the CDROM). If you
are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in
<span class="emphasis"><i class="EMPHASIS">before</i></span> the laptop is powered on.
FreeBSD does not, unfortunately, currently support ``hot insertion'' of PCMCIA cards
during installation.</p>
<p>You will also need to know your IP address on the network, the <var
class="OPTION">netmask</var> value for your subnet and the name of your machine. Your
system administrator can tell you which values are appropriate to your particular network
setup. If you will be referring to other hosts by name rather than IP address, you'll
also need a name server and possibly the address of a gateway (if you're using PPP, it's
your provider's IP address) to use in talking to it. If you want to install by FTP via an
HTTP proxy (see below), you will also need the proxy's address.</p>
<p>If you do not know the answers to these questions then you should really probably talk
to your system administrator <span class="emphasis"><i class="EMPHASIS">first</i></span>
before trying this type of installation. Using a randomly chosen IP address or netmask on
a live network is almost guaranteed not to work, and will probably result in a lecture
from said system administrator.</p>
<p>Once you have a network connection of some sort working, the installation can continue
over NFS or FTP.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN406" name="AEN406">1.5.5.4 NFS installation tips</a></h5>
<p>NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution
files you want onto a server somewhere and then point the NFS media selection at it.</p>
<p>If this server supports only ``privileged port'' access (this is generally the default
for Sun and Linux workstations), you will need to set this option in the Options menu
before installation can proceed.</p>
<p>If you have a poor quality Ethernet card which suffers from very slow transfer rates,
you may also wish to toggle the appropriate Options flag.</p>
<p>In order for NFS installation to work, the server must also support ``subdir mounts'',
e.g. if your FreeBSD distribution directory lives on <tt
class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, then <tt
class="HOSTID">wiggy</tt> will have to allow the direct mounting of <tt
class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not just <tt class="FILENAME">/usr</tt>
or <tt class="FILENAME">/usr/archive/stuff</tt>.</p>
<p>In FreeBSD's <tt class="FILENAME">/etc/exports</tt> file this is controlled by the
<var class="OPTION">-alldirs</var> option. Other NFS servers may have different
conventions. If you are getting <var class="LITERAL">Permission Denied</var> messages
from the server then it's likely that you don't have this properly enabled.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN423" name="AEN423">1.5.5.5 FTP Installation tips</a></h5>
<p>FTP installation may be done from any mirror site containing a reasonably up-to-date
version of FreeBSD. A full menu of reasonable choices for almost any location in the
world is provided in the FTP site menu during installation.</p>
<p>If you are installing from some other FTP site not listed in this menu, or you are
having troubles getting your name server configured properly, you can also specify your
own URL by selecting the ``URL'' choice in that menu. A URL can contain a hostname or an
IP address, so something like the following would work in the absence of a name
server:</p>
<pre class="SCREEN">
ftp://216.66.64.162/pub/FreeBSD/releases/ia64/4.2-RELEASE
</pre>
<p>There are three FTP installation modes you can use:</p>
<ul>
<li>
<p>FTP: This method uses the standard ``Active'' mode for transfers, in which the server
initiates a connection to the client. This will not work through most firewalls but will
often work best with older FTP servers that do not support passive mode. If your
connection hangs with passive mode, try this one.</p>
</li>
<li>
<p>FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening
connections to the client. This option is best for users to pass through firewalls that
do not allow incoming connections on random port addresses.</p>
</li>
<li>
<p>FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy
for all FTP operations. The proxy will translate the requests and send them to the FTP
server. This allows the user to pass through firewalls that do not allow FTP at all, but
offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP
server.</p>
<p>In the rare case that you have an FTP proxy that does not go through HTTP, you can
specify the URL as something like:</p>
<pre class="SCREEN">
<kbd class="USERINPUT">ftp://foo.bar.com:<var
class="REPLACEABLE">port</var>/pub/FreeBSD</kbd>
</pre>
<p>In the URL above, <var class="REPLACEABLE">port</var> is the port number of the proxy
FTP server.</p>
</li>
</ul>
<br />
<br />
</div>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN466" name="AEN466">1.6 Question and Answer Section for IA-64
Architecture Users</a></h3>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 Distribution Format</a></h2>
<p>A typical FreeBSD distribution directory looks something like this (exact details may
vary depending on version, architecture, and other factors):</p>
<pre class="SCREEN">
ERRATA.HTM README.TXT compat1x dict kernel
ERRATA.TXT RELNOTES.HTM compat20 doc manpages
HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages
HARDWARE.TXT base compat22 filename.txt ports
INSTALL.HTM boot compat3x floppies proflibs
INSTALL.TXT catpages compat4x games src
README.HTM cdrom.inf crypto info tools
</pre>
<p>If you want to do a CDROM, FTP or NFS installation from this distribution directory,
all you need to do is make the 1.44MB boot floppies from the floppies directory (see <a
href="#FLOPPIES">Section 1.3</a> for instructions on how to do this), boot them and
follow the instructions. The rest of the data needed during the installation will be
obtained automatically based on your selections. If you've never installed FreeBSD
before, you also want to read the entirety of this document (the installation
instructions) file.</p>
<p>If you're trying to do some other type of installation or are merely curious about how
a distribution is organized, what follows is a more thorough description of some of these
items in more detail:</p>
<ol type="1">
<li>
<p>The <tt class="FILENAME">*.TXT</tt> and <tt class="FILENAME">*.HTM</tt> files contain
documentation (for example, this document is contained in both <tt
class="FILENAME">INSTALL.TXT</tt> and <tt class="FILENAME">INSTALL.HTM</tt>) and should
be read before starting an installation. The <tt class="FILENAME">*.TXT</tt> files are
plain text, while the <tt class="FILENAME">*.HTM</tt> files are HTML files that can be
read by almost any Web browser. Some distributions may contain documentation in other
formats as well, such as PDF or PostScript.</p>
</li>
<li>
<p><tt class="FILENAME">docbook.css</tt> is a Cascading Style Sheet (CSS) file used by
some Web browsers for formatting the HTML documentation.</p>
</li>
<li>
<p>The <tt class="FILENAME">base</tt>, <tt class="FILENAME">catpages</tt>, <tt
class="FILENAME">crypto</tt>, <tt class="FILENAME">dict</tt>, <tt
class="FILENAME">doc</tt>, <tt class="FILENAME">games</tt>, <tt
class="FILENAME">info</tt>, <tt class="FILENAME">manpages</tt>, <tt
class="FILENAME">proflibs</tt>, and <tt class="FILENAME">src</tt> directories contain the
primary distribution components of FreeBSD itself and are split into smaller files for
easy packing onto floppies (should that be necessary).</p>
</li>
<li>
<p>The <tt class="FILENAME">compat1x</tt>, <tt class="FILENAME">compat20</tt>, <tt
class="FILENAME">compat21</tt>, <tt class="FILENAME">compat22</tt>, <tt
class="FILENAME">compat3x</tt>, and <tt class="FILENAME">compat4x</tt> directories
contain distributions for compatibility with older releases and are distributed as single
gzip'd tar files - they can be installed during release time or later by running their
<tt class="FILENAME">install.sh</tt> scripts.</p>
</li>
<li>
<p>The <tt class="FILENAME">floppies/</tt> subdirectory contains the floppy installation
images; further information on using them can be found in <a href="#FLOPPIES">Section
1.3</a>.</p>
</li>
<li>
<p>The <tt class="FILENAME">packages</tt> and <tt class="FILENAME">ports</tt> directories
contain the FreeBSD Packages and Ports Collections. Packages may be installed from the
packages directory by running the command:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp><kbd
class="USERINPUT">/stand/sysinstall configPackages</kbd>
</pre>
<p>Packages can also be installed by feeding individual filenames in <tt
class="FILENAME">packages</tt>/ to the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>
command.</p>
<p>The Ports Collection may be installed like any other distribution and requires about
100MB unpacked. More information on the ports collection may be obtained from <a
href="http://www.FreeBSD.org/ports/" target="_top">http://www.FreeBSD.org/ports/</a> or
locally from <tt class="FILENAME">/usr/share/doc/handbook</tt> if you've installed the
<tt class="FILENAME">doc</tt> distribution.</p>
</li>
<li>
<p>Last of all, the <tt class="FILENAME">tools</tt> directory contains various DOS tools
for discovering disk geometries, installing boot managers and the like. It is purely
optional and provided only for user convenience.</p>
</li>
</ol>
<br />
<br />
<p>A typical distribution directory (for example, the <tt class="FILENAME">info</tt>
distribution) looks like this internally:</p>
<pre class="SCREEN">
CHECKSUM.MD5 info.ab info.ad info.inf install.sh
info.aa info.ac info.ae info.mtree
</pre>
<p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains MD5 signatures for each file,
should data corruption be suspected, and is purely for reference. It is not used by the
actual installation and does not need to be copied with the rest of the distribution
files. The <tt class="FILENAME">info.a*</tt> files are split, gzip'd tar files, the
contents of which can be viewed by doing:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cat info.a* | tar tvzf -</kbd>
</pre>
<p>During installation, they are automatically concatenated and extracted by the
installation procedure.</p>
<p>The <tt class="FILENAME">info.inf</tt> file is also necessary since it is read by the
installation program in order to figure out how many pieces to look for when fetching and
concatenating the distribution. When putting distributions onto floppies, the <tt
class="FILENAME">.inf</tt> file <span class="emphasis"><i
class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set!</p>
<p>The <tt class="FILENAME">info.mtree</tt> file is another non-essential file which is
provided for user reference. It contains the MD5 signatures of the <span
class="emphasis"><i class="EMPHASIS">unpacked</i></span> distribution files and can be
later used with the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mtree</span>(8)</span></a> program
to verify the installation permissions and checksums against any possible modifications
to the file. When used with the <tt class="FILENAME">base</tt> distribution, this can be
an excellent way of detecting trojan horse attacks on your system.</p>
<p>Finally, the <tt class="FILENAME">install.sh</tt> file is for use by those who want to
install the distribution after installation time. To install the info distribution from
CDROM after a system was installed, for example, you'd do:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /cdrom/info</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">sh install.sh</kbd>
</pre>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 Upgrading FreeBSD</a></h2>
<p>These instructions describe a procedure for doing a binary upgrade from an older
version of FreeBSD.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> While the FreeBSD upgrade procedure does its best to safeguard against
accidental loss of data, it is still more than possible to <span class="emphasis"><i
class="EMPHASIS">wipe out your entire disk</i></span> with this installation! Please do
not accept the final confirmation request unless you have adequately backed up any
important data files.</p>
</blockquote>
</div>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> These notes assume that you are using the version of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched
version of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> is
almost guaranteed to cause problems and has been known to leave systems in an unusable
state. The most commonly made mistake in this regard is the use of an old copy of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
from an existing installation to upgrade to a newer version of FreeBSD. This is <span
class="emphasis"><i class="EMPHASIS">not</i></span> recommended.</p>
</blockquote>
</div>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> Binary upgrades to FreeBSD 5.2-RELEASE from FreeBSD 4-STABLE are not
supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence
can be disruptive, but are not removed by a binary upgrade. One notable example is that
an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to
compile incorrectly (or not at all).</p>
<p></p>
<p>These upgrade instructions are provided for the use of users upgrading from relatively
recent FreeBSD 5-CURRENT snapshots.</p>
</blockquote>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN667" name="AEN667">3.1 Introduction</a></h3>
<p>The upgrade procedure replaces distributions selected by the user with those
corresponding to the new FreeBSD release. It preserves standard system configuration
data, as well as user data, installed packages and other software.</p>
<p>Administrators contemplating an upgrade are encouraged to study this section in its
entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or
loss of data.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN671" name="AEN671">3.1.1 Upgrade Overview</a></h4>
<p>Upgrading of a distribution is performed by extracting the new version of the
component over the top of the previous version. Files belonging to the old distribution
are not deleted.</p>
<p>System configuration is preserved by retaining and restoring the previous version of
the following files:</p>
<p><tt class="FILENAME">Xaccel.ini</tt>, <tt class="FILENAME">XF86Config</tt>, <tt
class="FILENAME">adduser.conf</tt>, <tt class="FILENAME">aliases</tt>, <tt
class="FILENAME">aliases.db</tt>, <tt class="FILENAME">amd.map</tt>, <tt
class="FILENAME">crontab</tt>, <tt class="FILENAME">csh.cshrc</tt>, <tt
class="FILENAME">csh.login</tt>, <tt class="FILENAME">csh.logout</tt>, <tt
class="FILENAME">cvsupfile</tt>, <tt class="FILENAME">dhclient.conf</tt>, <tt
class="FILENAME">disktab</tt>, <tt class="FILENAME">dm.conf</tt>, <tt
class="FILENAME">dumpdates</tt>, <tt class="FILENAME">exports</tt>, <tt
class="FILENAME">fbtab</tt>, <tt class="FILENAME">fstab</tt>, <tt
class="FILENAME">ftpusers</tt>, <tt class="FILENAME">gettytab</tt>, <tt
class="FILENAME">gnats</tt>, <tt class="FILENAME">group</tt>, <tt
class="FILENAME">hosts</tt>, <tt class="FILENAME">hosts.allow</tt>, <tt
class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt
class="FILENAME">inetd.conf</tt>, <tt class="FILENAME">localtime</tt>, <tt
class="FILENAME">login.access</tt>, <tt class="FILENAME">login.conf</tt>, <tt
class="FILENAME">mail</tt>, <tt class="FILENAME">mail.rc</tt>, <tt
class="FILENAME">make.conf</tt>, <tt class="FILENAME">manpath.config</tt>, <tt
class="FILENAME">master.passwd</tt>, <tt class="FILENAME">motd</tt>, <tt
class="FILENAME">namedb</tt>, <tt class="FILENAME">networks</tt>, <tt
class="FILENAME">newsyslog.conf</tt>, <tt class="FILENAME">nsmb.conf</tt>, <tt
class="FILENAME">nsswitch.conf</tt>, <tt class="FILENAME">pam.conf</tt>, <tt
class="FILENAME">passwd</tt>, <tt class="FILENAME">periodic</tt>, <tt
class="FILENAME">ppp</tt>, <tt class="FILENAME">printcap</tt>, <tt
class="FILENAME">profile</tt>, <tt class="FILENAME">pwd.db</tt>, <tt
class="FILENAME">rc.conf</tt>, <tt class="FILENAME">rc.conf.local</tt>, <tt
class="FILENAME">rc.firewall</tt>, <tt class="FILENAME">rc.local</tt>, <tt
class="FILENAME">remote</tt>, <tt class="FILENAME">resolv.conf</tt>, <tt
class="FILENAME">rmt</tt>, <tt class="FILENAME">sendmail.cf</tt>, <tt
class="FILENAME">sendmail.cw</tt>, <tt class="FILENAME">services</tt>, <tt
class="FILENAME">shells</tt>, <tt class="FILENAME">skeykeys</tt>, <tt
class="FILENAME">spwd.db</tt>, <tt class="FILENAME">ssh</tt>, <tt
class="FILENAME">syslog.conf</tt>, <tt class="FILENAME">ttys</tt>, <tt
class="FILENAME">uucp</tt></p>
<p>The versions of these files which correspond to the new version are moved to <tt
class="FILENAME">/etc/upgrade/</tt>. The system administrator may peruse these new
versions and merge components as desired. Note that many of these files are
interdependent, and the best merge procedure is to copy all site-specific data from the
current files into the new.</p>
<p>During the upgrade procedure, the administrator is prompted for a location into which
all files from <tt class="FILENAME">/etc/</tt> are saved. In the event that local
modifications have been made to other files, they may be subsequently retrieved from this
location.</p>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN745" name="AEN745">3.2 Procedure</a></h3>
<p>This section details the upgrade procedure. Particular attention is given to items
which substantially differ from a normal installation.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN748" name="AEN748">3.2.1 Backup</a></h4>
<p>User data and system configuration should be backed up before upgrading. While the
upgrade procedure does its best to prevent accidental mistakes, it is possible to
partially or completely destroy data and configuration information.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN751" name="AEN751">3.2.2 Mount Filesystems</a></h4>
<p>The disklabel editor is entered with the nominated disk's filesystem devices listed.
Prior to commencing the upgrade, the administrator should make a note of the device names
and corresponding mountpoints. These mountpoints should be entered here. <span
class="emphasis"><i class="EMPHASIS">Do not</i></span> set the ``newfs flag'' for any
filesystems, as this will cause data loss.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN756" name="AEN756">3.2.3 Select Distributions</a></h4>
<p>When selecting distributions, there are no constraints on which must be selected. As a
general rule, the <var class="LITERAL">base</var> distribution should be selected for an
update, and the <var class="LITERAL">man</var> distribution if manpages are already
installed. Other distributions may be selected beyond those originally installed if the
administrator wishes to add additional functionality.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 After Installation</a></h4>
<p>Once the installation procedure has completed, the administrator is prompted to
examine the new configuration files. At this point, checks should be made to ensure that
the system configuration is valid. In particular, the <tt
class="FILENAME">/etc/rc.conf</tt> and <tt class="FILENAME">/etc/fstab</tt> files should
be checked.</p>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN766" name="AEN766">3.3 Upgrading from Source Code</a></h3>
<p>Those interested in an upgrade method that allows more flexibility and sophistication
should take a look at <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html"
target="_top">The Cutting Edge</a> in the FreeBSD Handbook. This procedure involves
rebuilding all of FreeBSD from source code. It requires reliable network connectivity,
extra disk space, and time, but has advantages for networks and other more complex
installations. This is roughly the same procedure as is used for track the -STABLE or
-CURRENT development branches.</p>
<p><tt class="FILENAME">/usr/src/UPDATING</tt> contains important information on updating
a FreeBSD system from source code. It lists various issues resulting from changes in
FreeBSD that may affect an upgrade.</p>
<p></p>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 Troubleshooting</a></h2>
<div class="SECT2">
<h3 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 Repairing an Existing FreeBSD
Installation</a></h3>
<p>FreeBSD features a ``Fixit'' option in the top menu of the boot floppy. To use it, you
will also need either a <tt class="FILENAME">fixit.flp</tt> image floppy, generated in
the same fashion as the boot floppy, or the ``live filesystem'' CDROM; typically the
second CDROM in a multi-disc FreeBSD distribution.</p>
<p>To invoke fixit, simply boot the <tt class="FILENAME">kern.flp</tt> floppy, choose the
``Fixit'' item and insert the fixit floppy or CDROM when asked. You will then be placed
into a shell with a wide variety of commands available (in the <tt
class="FILENAME">/stand</tt> and <tt class="FILENAME">/mnt2/stand</tt> directories) for
checking, repairing and examining filesystems and their contents. Some UNIX
administration experience <span class="emphasis"><i class="EMPHASIS">is</i></span>
required to use the fixit option.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN787" name="AEN787">4.2 Common Installation Problems for IA-64
Architecture Users</a></h3>
</div>
</div>
</div>
<hr />
<p align="center"><small>This file, and other release-related documents, can be
downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.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>For questions about this documentation, e-mail &#60;<a
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
<br />
<br />
</body>
</html>

990
en/releases/5.2R/installation-pc98.html Normal file
View file

@ -0,0 +1,990 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>FreeBSD/pc98 5.2-RELEASE Installation Instructions</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
<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 id="AEN2" name="AEN2">FreeBSD/pc98 5.2-RELEASE Installation
Instructions</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
Project</p>
<hr />
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT"><a id="AEN11" name="AEN11"></a>
<p>This article gives some brief instructions on installing FreeBSD/pc98 5.2-RELEASE,
with particular emphasis given to obtaining a FreeBSD distribution. Some notes on
troubleshooting and frequently-asked questions are also given.</p>
</div>
</blockquote>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="INSTALL" name="INSTALL">1 Installing FreeBSD</a></h2>
<p>This section documents the process of installing a new distribution of FreeBSD. These
instructions pay particular emphasis to the process of obtaining the FreeBSD 5.2-RELEASE
distribution and to beginning the installation procedure. The <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"
target="_top">``Installing FreeBSD''</a> chapter of the <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
Handbook</a> provides more in-depth information about the installation program itself,
including a guided walkthrough with screenshots.</p>
<p>If you are upgrading from a previous release of FreeBSD, please see <a
href="#UPGRADING">Section 3</a> for instructions on upgrading.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="GETTING-STARTED" name="GETTING-STARTED">1.1 Getting
Started</a></h3>
<p>Probably the most important pre-installation step that can be taken is that of reading
the various instruction documents provided with FreeBSD. A roadmap of documents
pertaining to this release of FreeBSD can be found in <tt
class="FILENAME">README.TXT</tt>, which can usually be found in the same location as this
file; most of these documents, such as the release notes and the hardware compatibility
list, are also accessible in the Documentation menu of the installer.</p>
<p>Note that on-line versions of the FreeBSD <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/" target="_top">FAQ</a> and <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
target="_top">Handbook</a> are also available from the <a href="http://www.FreeBSD.org/"
target="_top">FreeBSD Project Web site</a>, if you have an Internet connection.</p>
<p>This collection of documents may seem daunting, but the time spent reading them will
likely be saved many times over. Being familiar with what resources are available can
also be helpful in the event of problems during installation.</p>
<p>The best laid plans sometimes go awry, so if you run into trouble take a look at <a
href="#TROUBLE">Section 4</a>, which contains valuable troubleshooting information. You
should also read an updated copy of <tt class="FILENAME">ERRATA.TXT</tt> before
installing, since this will alert you to any problems which have reported in the interim
for your particular release.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> While FreeBSD does its best to safeguard against accidental loss of
data, it's still more than possible to <span class="emphasis"><i class="EMPHASIS">wipe
out your entire disk</i></span> with this installation if you make a mistake. Please do
not proceed to the final FreeBSD installation menu unless you've adequately backed up any
important data first.</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware Requirements</a></h3>
<p>FreeBSD for the NEC PC-98x1 requires a 386 or better processor to run (sorry, there is
no support for 286 processors) and at least 5 megs of RAM to install and 4 megs of RAM to
run. You will need at least 100MB of free hard drive space for the most minimal
installation. See below for ways of shrinking existing DOS partitions in order to install
FreeBSD.</p>
<p>If you are not familiar with configuring hardware for FreeBSD, you should be sure to
read the <tt class="FILENAME">HARDWARE.TXT</tt> file; it contains important information
on what hardware is supported by FreeBSD.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 Floppy Disk Image
Instructions</a></h3>
<p>Depending on how you choose to install FreeBSD, you may need to create a set of floppy
disks (usually two) to begin the installation process. This section briefly describes how
to create these disks, either from a CDROM installation or from the Internet. Note that
in the common case of installing FreeBSD from CDROM, on a machine that supports bootable
CDROMs, the steps outlined in this section will not be needed and can be skipped.</p>
<p>For a normal CDROM or network installation, all you need to copy onto actual floppies
from the <tt class="FILENAME">floppies/</tt> directory are the <tt
class="FILENAME">kern.flp</tt> and <tt class="FILENAME">mfsroot.flp</tt> images (for
1.44MB floppies) or <tt class="FILENAME">kern-small.flp</tt> and <tt
class="FILENAME">mfsroot-small.flp</tt> images (for 1.2MB floppies).</p>
<p>Getting these images over the network is easy. Simply fetch the <var
class="REPLACEABLE">release</var><tt class="FILENAME">/floppies/kern.flp</tt>, <var
class="REPLACEABLE">release</var><tt class="FILENAME">/floppies/mfsroot.flp</tt>, and
<var class="REPLACEABLE">release</var><tt class="FILENAME">/floppies/drivers.flp</tt>
files from <a href="ftp://ftp.FreeBSD.org/" target="_top">ftp://ftp.FreeBSD.org/</a> or
one of the many mirrors listed at <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.</p>
<p>Get two blank, freshly formatted floppies and image copy <tt
class="FILENAME">kern.flp</tt> onto one and <tt class="FILENAME">mfsroot.flp</tt> onto
the other. These images are <span class="emphasis"><i class="EMPHASIS">not</i></span> DOS
files. You cannot simply copy them to a DOS or UFS floppy as regular files, you need to
``image'' copy them to the floppy with <tt class="FILENAME">rawrite.exe</tt> under DOS
(see the <tt class="FILENAME">tools</tt> directory on your CDROM or FreeBSD FTP mirror)
or the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=dd&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dd</span>(1)</span></a> command in
UNIX.</p>
<p>For example, to create the kernel floppy image from DOS, you'd do something like
this:</p>
<pre class="SCREEN">
<samp class="PROMPT">A&#62;</samp> <kbd class="USERINPUT">rawrite</kbd>
</pre>
<p>Assuming that you'd copied <tt class="FILENAME">rawrite.exe</tt> and <tt
class="FILENAME">kern.flp</tt> into a directory somewhere. You would do the same for <tt
class="FILENAME">mfsroot.flp</tt>, of course.</p>
<p>If you're creating the boot floppy from a UNIX machine, you may find that:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">dd if=floppies/kern.flp of=/dev/rfd0.1440</kbd>
</pre>
<p>or</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">dd if=floppies/kern-small.flp of=/dev/rfd0.1200</kbd>
</pre>
<p>work well, depending on your hardware and operating system environment (different
versions of UNIX have different names for the floppy drive).</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="START-INSTALLATION" name="START-INSTALLATION">1.4 Installing
FreeBSD from CDROM or the Internet</a></h3>
<p>The easiest type of installation is from CDROM. If you have a supported CDROM drive
and a FreeBSD installation CDROM, there is a next way of starting the installation from
it:</p>
<ul>
<li>
<p>Build a set of FreeBSD boot floppies from the <tt class="FILENAME">floppies/</tt>
directory in every FreeBSD distribution. Read <a href="#FLOPPIES">Section 1.3</a> for
more information on creating the bootable floppies under different operating systems.
Then you simply boot from the first floppy and you should soon be in the FreeBSD
installation.</p>
</li>
</ul>
<br />
<br />
<p>If you don't have a CDROM and would like to simply install over the net using PPP,
SLIP or a dedicated connection. You should start the installation by building a set of
FreeBSD boot floppies from the files <tt class="FILENAME">floppies/kern.flp</tt> and <tt
class="FILENAME">floppies/mfsroot.flp</tt> using the instructions found in <a
href="#FLOPPIES">Section 1.3</a>. Restart your computer using the <tt
class="FILENAME">kern.flp</tt> disk; when prompted, insert the <tt
class="FILENAME">mfsroot.flp</tt> disk. Then, please go to <a href="#FTPNFS">Section
1.5.5</a> for additional tips on installing via FTP or NFS.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN212" name="AEN212">1.5 Detail on various installation
types</a></h3>
<p>Once you've gotten yourself to the initial installation screen somehow, you should be
able to follow the various menu prompts and go from there. If you've never used the
FreeBSD installation before, you are also encouraged to read some of the documentation in
the Documentation submenu as well as the general ``Usage'' instructions on the first
menu.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> If you get stuck at a screen, press the <b class="KEYCAP">F1</b> key for
online documentation relevant to that specific section.</p>
</blockquote>
</div>
<p>If you've never installed FreeBSD before, or even if you have, the ``Standard''
installation mode is the most recommended since it makes sure that you'll visit all the
various important checklist items along the way. If you're much more comfortable with the
FreeBSD installation process and know <span class="emphasis"><i
class="EMPHASIS">exactly</i></span> what you want to do, use the ``Express'' or
``Custom'' installation options. If you're upgrading an existing system, use the
``Upgrade'' option.</p>
<p>The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS
and UFS partitions as installation media; further tips on installing from each type of
media are listed below.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN251" name="AEN251">1.5.1 Installing from a Network
CDROM</a></h4>
<p>If you simply wish to install from a local CDROM drive then see <a
href="#START-INSTALLATION">Section 1.4</a>. If you don't have a CDROM drive on your
system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to
which you have network connectivity, there are also several ways of going about it:</p>
<ul>
<li>
<p>If you would be able to FTP install FreeBSD directly from the CDROM drive in some
FreeBSD machine, it's quite easy: You simply add the following line to the password file
(using the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vipw</span>(8)</span></a>
command):</p>
<pre class="SCREEN">
ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
</pre>
<p>On the machine on which you are running the install, go to the Options menu and set
Release Name to <var class="LITERAL">any</var>. You may then choose a Media type of <var
class="LITERAL">FTP</var> and type in <tt class="FILENAME">ftp://<var
class="REPLACEABLE">machine</var></tt> after picking ``URL'' in the ftp sites menu.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> This may allow anyone on the local network (or Internet) to make
``anonymous FTP'' connections to this machine, which may not be desirable.</p>
</blockquote>
</div>
</li>
<li>
<p>If you would rather use NFS to export the CDROM directly to the machine(s) you'll be
installing from, you need to first add an entry to the <tt
class="FILENAME">/etc/exports</tt> file (on the machine with the CDROM drive). The
example below allows the machine <tt class="HOSTID">ziggy.foo.com</tt> to mount the CDROM
directly via NFS during installation:</p>
<pre class="SCREEN">
/cdrom -ro ziggy.foo.com
</pre>
<p>The machine with the CDROM must also be configured as an NFS server, of course, and if
you're not sure how to do that then an NFS installation is probably not the best choice
for you unless you're willing to read up on <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.conf&amp;sektion=5&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rc.conf</span>(5)</span></a> and
configure things appropriately. Assuming that this part goes smoothly, you should be able
to enter: <tt class="FILENAME"><var class="REPLACEABLE">cdrom-host</var>:/cdrom</tt> as
the path for an NFS installation when the target machine is installed, e.g. <tt
class="FILENAME">wiggy:/cdrom</tt>.</p>
</li>
</ul>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN283" name="AEN283">1.5.2 Installing from Floppies</a></h4>
<p>If you must install from floppy disks, either due to unsupported hardware or just
because you enjoy doing things the hard way, you must first prepare some floppies for the
install.</p>
<p>First, make your boot floppies as described in <a href="#FLOPPIES">Section
1.3</a>.</p>
<p>Second, peruse <a href="#LAYOUT">Section 2</a> and pay special attention to the
``Distribution Format'' section since it describes which files you're going to need to
put onto floppy and which you can safely skip.</p>
<p>Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files
in the <tt class="FILENAME">bin</tt> (binary distribution) directory. If you're preparing
these floppies under DOS, then these floppies <span class="emphasis"><i
class="EMPHASIS">must</i></span> be formatted using the MS-DOS <tt
class="FILENAME">FORMAT</tt> command. If you're using Windows, use the Windows File
Manager format command.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> Frequently, floppy disks come ``factory preformatted''. While
convenient, many problems reported by users in the past have resulted from the use of
improperly formatted media. Re-format them yourself, just to make sure.</p>
</blockquote>
</div>
<p>If you're creating the floppies from another FreeBSD machine, a format is still not a
bad idea though you don't need to put a DOS filesystem on each floppy. You can use the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>
commands to put a UFS filesystem on a floppy, as the following sequence of commands
illustrates:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">fdformat -f 1440 fd0.1440</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">disklabel -w -r fd0.1440 floppy3</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</kbd>
</pre>
<p>After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto
them. The distribution files are split into chunks conveniently sized so that 5 of them
will fit on a conventional 1.44MB floppy. Go through all your floppies, packing as many
files as will fit on each one, until you've got all the distributions you want packed up
in this fashion. Each distribution should go into its own subdirectory on the floppy,
e.g.: <tt class="FILENAME">a:\bin\bin.inf</tt>, <tt class="FILENAME">a:\bin\bin.aa</tt>,
<tt class="FILENAME">a:\bin\bin.ab</tt>, ...</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> The <tt class="FILENAME">bin.inf</tt> file also needs to go on the
first floppy of the <tt class="FILENAME">bin</tt> set since it is read by the
installation program in order to figure out how many additional pieces to look for when
fetching and concatenating the distribution. When putting distributions onto floppies,
the <tt class="FILENAME">distname.inf</tt> file <span class="emphasis"><i
class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set. This
is also covered in <tt class="FILENAME">README.TXT</tt>.</p>
</blockquote>
</div>
<p>Once you come to the Media screen of the install, select ``Floppy'' and you'll be
prompted for the rest.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN325" name="AEN325">1.5.3 Installing from a DOS
partition</a></h4>
<p>To prepare for installation from an MS-DOS partition you should simply copy the files
from the distribution into a directory called <tt class="FILENAME">FREEBSD</tt> on the
Primary DOS partition (<tt class="DEVICENAME">A:</tt>). For example, to do a minimal
installation of FreeBSD from DOS using files copied from the CDROM, you might do
something like this:</p>
<pre class="SCREEN">
<samp class="PROMPT">A:\&#62;</samp> <kbd class="USERINPUT">MD A:\FREEBSD</kbd>
<samp class="PROMPT">A:\&#62;</samp> <kbd
class="USERINPUT">XCOPY /S E:\BASE A:\FREEBSD\BASE</kbd>
</pre>
<p>Assuming that <tt class="DEVICENAME">E:</tt> was where your CD was mounted.</p>
<p>For as many distributions as you wish to install from DOS (and you have free space
for), install each one in a directory under <tt class="FILENAME">A:\FREEBSD</tt> - the
<tt class="FILENAME">BIN</tt> dist is only the minimal requirement.</p>
<p>Once you've copied the directories, you can simply launch the installation from
floppies as normal and select ``DOS'' as your media type when the time comes.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN353" name="AEN353">1.5.4 Installing from QIC/SCSI
Tape</a></h4>
<p>When installing from tape, the installation program expects the files to be simply
tar'ed onto it, so after fetching all of the files for the distributions you're
interested in, simply use <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tar</span>(1)</span></a> to get
them onto the tape with a command something like this:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd <var
class="REPLACEABLE">/where/you/have/your/dists</var></kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/rsa0 <var
class="REPLACEABLE">dist1</var> .. <var class="REPLACEABLE">dist2</var></kbd>
</pre>
<p>When you go to do the installation, you should also make sure that you leave enough
room in some temporary directory (which you'll be allowed to choose) to accommodate the
<span class="emphasis"><i class="EMPHASIS">full</i></span> contents of the tape you've
created. Due to the non-random access nature of tapes, this method of installation
requires quite a bit of temporary storage. You should expect to require as much temporary
storage as you have stuff written on tape.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> When going to do the installation, the tape must be in the drive <span
class="emphasis"><i class="EMPHASIS">before</i></span> booting from the boot floppies.
The installation ``probe'' may otherwise fail to find it.</p>
</blockquote>
</div>
<p>Now create a boot floppy as described in <a href="#FLOPPIES">Section 1.3</a> and
proceed with the installation.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 Installing over a Network using FTP
or NFS</a></h4>
<p>After making the boot floppies as described in the first section, you can load the
rest of the installation over a network using one of 3 types of connections: serial port,
parallel port, or Ethernet.</p>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN378" name="AEN378">1.5.5.1 Serial Port</a></h5>
<p>SLIP support is rather primitive, and is limited primarily to hard-wired links, such
as a serial cable running between two computers. The link must be hard-wired because the
SLIP installation doesn't currently offer a dialing capability. If you need to dial out
with a modem or otherwise dialog with the link before connecting to it, then I recommend
that the PPP utility be used instead.</p>
<p>If you're using PPP, make sure that you have your Internet Service Provider's IP
address and DNS information handy as you'll need to know it fairly early in the
installation process. You may also need to know your own IP address, though PPP supports
dynamic address negotiation and may be able to pick up this information directly from
your ISP if they support it.</p>
<p>You will also need to know how to use the various ``AT commands'' for dialing out with
your particular brand of modem as the PPP dialer provides only a very simple terminal
emulator.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN384" name="AEN384">1.5.5.2 Parallel Port</a></h5>
<p>If a hard-wired connection to another FreeBSD or Linux machine is available, you might
also consider installing over a ``laplink'' style parallel port cable. The data rate over
the parallel port is much higher than what is typically possible over a serial line (up
to 50k/sec), thus resulting in a quicker installation. It's not typically necessary to
use ``real'' IP addresses when using a point-to-point parallel cable in this way and you
can generally just use RFC 1918 style addresses for the ends of the link (e.g. <tt
class="HOSTID">10.0.0.1</tt>, <tt class="HOSTID">10.0.0.2</tt>, etc).</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> If you use a Linux machine rather than a FreeBSD machine as your
PLIP peer, you will also have to specify <var class="OPTION">link0</var> in the TCP/IP
setup screen's ``extra options for ifconfig'' field in order to be compatible with
Linux's slightly different PLIP protocol.</p>
</blockquote>
</div>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5>
<p>FreeBSD supports many common Ethernet cards; a table of supported cards is provided as
part of the FreeBSD Hardware Notes (see <tt class="FILENAME">HARDWARE.TXT</tt> in the
Documentation menu on the boot floppy or the top level directory of the CDROM). If you
are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in
<span class="emphasis"><i class="EMPHASIS">before</i></span> the laptop is powered on.
FreeBSD does not, unfortunately, currently support ``hot insertion'' of PCMCIA cards
during installation.</p>
<p>You will also need to know your IP address on the network, the <var
class="OPTION">netmask</var> value for your subnet and the name of your machine. Your
system administrator can tell you which values are appropriate to your particular network
setup. If you will be referring to other hosts by name rather than IP address, you'll
also need a name server and possibly the address of a gateway (if you're using PPP, it's
your provider's IP address) to use in talking to it. If you want to install by FTP via an
HTTP proxy (see below), you will also need the proxy's address.</p>
<p>If you do not know the answers to these questions then you should really probably talk
to your system administrator <span class="emphasis"><i class="EMPHASIS">first</i></span>
before trying this type of installation. Using a randomly chosen IP address or netmask on
a live network is almost guaranteed not to work, and will probably result in a lecture
from said system administrator.</p>
<p>Once you have a network connection of some sort working, the installation can continue
over NFS or FTP.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN406" name="AEN406">1.5.5.4 NFS installation tips</a></h5>
<p>NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution
files you want onto a server somewhere and then point the NFS media selection at it.</p>
<p>If this server supports only ``privileged port'' access (this is generally the default
for Sun and Linux workstations), you will need to set this option in the Options menu
before installation can proceed.</p>
<p>If you have a poor quality Ethernet card which suffers from very slow transfer rates,
you may also wish to toggle the appropriate Options flag.</p>
<p>In order for NFS installation to work, the server must also support ``subdir mounts'',
e.g. if your FreeBSD distribution directory lives on <tt
class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, then <tt
class="HOSTID">wiggy</tt> will have to allow the direct mounting of <tt
class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not just <tt class="FILENAME">/usr</tt>
or <tt class="FILENAME">/usr/archive/stuff</tt>.</p>
<p>In FreeBSD's <tt class="FILENAME">/etc/exports</tt> file this is controlled by the
<var class="OPTION">-alldirs</var> option. Other NFS servers may have different
conventions. If you are getting <var class="LITERAL">Permission Denied</var> messages
from the server then it's likely that you don't have this properly enabled.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN423" name="AEN423">1.5.5.5 FTP Installation tips</a></h5>
<p>FTP installation may be done from any mirror site containing a reasonably up-to-date
version of FreeBSD. A full menu of reasonable choices for almost any location in the
world is provided in the FTP site menu during installation.</p>
<p>If you are installing from some other FTP site not listed in this menu, or you are
having troubles getting your name server configured properly, you can also specify your
own URL by selecting the ``URL'' choice in that menu. A URL can contain a hostname or an
IP address, so something like the following would work in the absence of a name
server:</p>
<pre class="SCREEN">
ftp://216.66.64.162/pub/FreeBSD/releases/pc98/4.2-RELEASE
</pre>
<p>There are three FTP installation modes you can use:</p>
<ul>
<li>
<p>FTP: This method uses the standard ``Active'' mode for transfers, in which the server
initiates a connection to the client. This will not work through most firewalls but will
often work best with older FTP servers that do not support passive mode. If your
connection hangs with passive mode, try this one.</p>
</li>
<li>
<p>FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening
connections to the client. This option is best for users to pass through firewalls that
do not allow incoming connections on random port addresses.</p>
</li>
<li>
<p>FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy
for all FTP operations. The proxy will translate the requests and send them to the FTP
server. This allows the user to pass through firewalls that do not allow FTP at all, but
offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP
server.</p>
<p>In the rare case that you have an FTP proxy that does not go through HTTP, you can
specify the URL as something like:</p>
<pre class="SCREEN">
<kbd class="USERINPUT">ftp://foo.bar.com:<var
class="REPLACEABLE">port</var>/pub/FreeBSD</kbd>
</pre>
<p>In the URL above, <var class="REPLACEABLE">port</var> is the port number of the proxy
FTP server.</p>
</li>
</ul>
<br />
<br />
</div>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN466" name="AEN466">1.6 Question and Answer Section for NEC
PC-98x1 Architecture Users</a></h3>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 Distribution Format</a></h2>
<p>A typical FreeBSD distribution directory looks something like this (exact details may
vary depending on version, architecture, and other factors):</p>
<pre class="SCREEN">
ERRATA.HTM README.TXT compat1x dict kernel
ERRATA.TXT RELNOTES.HTM compat20 doc manpages
HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages
HARDWARE.TXT base compat22 filename.txt ports
INSTALL.HTM boot compat3x floppies proflibs
INSTALL.TXT catpages compat4x games src
README.HTM cdrom.inf crypto info tools
</pre>
<p>If you want to do a CDROM, FTP or NFS installation from this distribution directory,
all you need to do is make the 1.44MB boot floppies from the floppies directory (see <a
href="#FLOPPIES">Section 1.3</a> for instructions on how to do this), boot them and
follow the instructions. The rest of the data needed during the installation will be
obtained automatically based on your selections. If you've never installed FreeBSD
before, you also want to read the entirety of this document (the installation
instructions) file.</p>
<p>If you're trying to do some other type of installation or are merely curious about how
a distribution is organized, what follows is a more thorough description of some of these
items in more detail:</p>
<ol type="1">
<li>
<p>The <tt class="FILENAME">*.TXT</tt> and <tt class="FILENAME">*.HTM</tt> files contain
documentation (for example, this document is contained in both <tt
class="FILENAME">INSTALL.TXT</tt> and <tt class="FILENAME">INSTALL.HTM</tt>) and should
be read before starting an installation. The <tt class="FILENAME">*.TXT</tt> files are
plain text, while the <tt class="FILENAME">*.HTM</tt> files are HTML files that can be
read by almost any Web browser. Some distributions may contain documentation in other
formats as well, such as PDF or PostScript.</p>
</li>
<li>
<p><tt class="FILENAME">docbook.css</tt> is a Cascading Style Sheet (CSS) file used by
some Web browsers for formatting the HTML documentation.</p>
</li>
<li>
<p>The <tt class="FILENAME">base</tt>, <tt class="FILENAME">catpages</tt>, <tt
class="FILENAME">crypto</tt>, <tt class="FILENAME">dict</tt>, <tt
class="FILENAME">doc</tt>, <tt class="FILENAME">games</tt>, <tt
class="FILENAME">info</tt>, <tt class="FILENAME">manpages</tt>, <tt
class="FILENAME">proflibs</tt>, and <tt class="FILENAME">src</tt> directories contain the
primary distribution components of FreeBSD itself and are split into smaller files for
easy packing onto floppies (should that be necessary).</p>
</li>
<li>
<p>The <tt class="FILENAME">compat1x</tt>, <tt class="FILENAME">compat20</tt>, <tt
class="FILENAME">compat21</tt>, <tt class="FILENAME">compat22</tt>, <tt
class="FILENAME">compat3x</tt>, and <tt class="FILENAME">compat4x</tt> directories
contain distributions for compatibility with older releases and are distributed as single
gzip'd tar files - they can be installed during release time or later by running their
<tt class="FILENAME">install.sh</tt> scripts.</p>
</li>
<li>
<p>The <tt class="FILENAME">floppies/</tt> subdirectory contains the floppy installation
images; further information on using them can be found in <a href="#FLOPPIES">Section
1.3</a>.</p>
</li>
<li>
<p>The <tt class="FILENAME">packages</tt> and <tt class="FILENAME">ports</tt> directories
contain the FreeBSD Packages and Ports Collections. Packages may be installed from the
packages directory by running the command:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp><kbd
class="USERINPUT">/stand/sysinstall configPackages</kbd>
</pre>
<p>Packages can also be installed by feeding individual filenames in <tt
class="FILENAME">packages</tt>/ to the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>
command.</p>
<p>The Ports Collection may be installed like any other distribution and requires about
100MB unpacked. More information on the ports collection may be obtained from <a
href="http://www.FreeBSD.org/ports/" target="_top">http://www.FreeBSD.org/ports/</a> or
locally from <tt class="FILENAME">/usr/share/doc/handbook</tt> if you've installed the
<tt class="FILENAME">doc</tt> distribution.</p>
</li>
<li>
<p>Last of all, the <tt class="FILENAME">tools</tt> directory contains various DOS tools
for discovering disk geometries, installing boot managers and the like. It is purely
optional and provided only for user convenience.</p>
</li>
</ol>
<br />
<br />
<p>A typical distribution directory (for example, the <tt class="FILENAME">info</tt>
distribution) looks like this internally:</p>
<pre class="SCREEN">
CHECKSUM.MD5 info.ab info.ad info.inf install.sh
info.aa info.ac info.ae info.mtree
</pre>
<p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains MD5 signatures for each file,
should data corruption be suspected, and is purely for reference. It is not used by the
actual installation and does not need to be copied with the rest of the distribution
files. The <tt class="FILENAME">info.a*</tt> files are split, gzip'd tar files, the
contents of which can be viewed by doing:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cat info.a* | tar tvzf -</kbd>
</pre>
<p>During installation, they are automatically concatenated and extracted by the
installation procedure.</p>
<p>The <tt class="FILENAME">info.inf</tt> file is also necessary since it is read by the
installation program in order to figure out how many pieces to look for when fetching and
concatenating the distribution. When putting distributions onto floppies, the <tt
class="FILENAME">.inf</tt> file <span class="emphasis"><i
class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set!</p>
<p>The <tt class="FILENAME">info.mtree</tt> file is another non-essential file which is
provided for user reference. It contains the MD5 signatures of the <span
class="emphasis"><i class="EMPHASIS">unpacked</i></span> distribution files and can be
later used with the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mtree</span>(8)</span></a> program
to verify the installation permissions and checksums against any possible modifications
to the file. When used with the <tt class="FILENAME">base</tt> distribution, this can be
an excellent way of detecting trojan horse attacks on your system.</p>
<p>Finally, the <tt class="FILENAME">install.sh</tt> file is for use by those who want to
install the distribution after installation time. To install the info distribution from
CDROM after a system was installed, for example, you'd do:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /cdrom/info</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">sh install.sh</kbd>
</pre>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 Upgrading FreeBSD</a></h2>
<p>These instructions describe a procedure for doing a binary upgrade from an older
version of FreeBSD.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> While the FreeBSD upgrade procedure does its best to safeguard against
accidental loss of data, it is still more than possible to <span class="emphasis"><i
class="EMPHASIS">wipe out your entire disk</i></span> with this installation! Please do
not accept the final confirmation request unless you have adequately backed up any
important data files.</p>
</blockquote>
</div>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> These notes assume that you are using the version of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched
version of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> is
almost guaranteed to cause problems and has been known to leave systems in an unusable
state. The most commonly made mistake in this regard is the use of an old copy of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
from an existing installation to upgrade to a newer version of FreeBSD. This is <span
class="emphasis"><i class="EMPHASIS">not</i></span> recommended.</p>
</blockquote>
</div>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> Binary upgrades to FreeBSD 5.2-RELEASE from FreeBSD 4-STABLE are not
supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence
can be disruptive, but are not removed by a binary upgrade. One notable example is that
an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to
compile incorrectly (or not at all).</p>
<p></p>
<p>These upgrade instructions are provided for the use of users upgrading from relatively
recent FreeBSD 5-CURRENT snapshots.</p>
</blockquote>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN667" name="AEN667">3.1 Introduction</a></h3>
<p>The upgrade procedure replaces distributions selected by the user with those
corresponding to the new FreeBSD release. It preserves standard system configuration
data, as well as user data, installed packages and other software.</p>
<p>Administrators contemplating an upgrade are encouraged to study this section in its
entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or
loss of data.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN671" name="AEN671">3.1.1 Upgrade Overview</a></h4>
<p>Upgrading of a distribution is performed by extracting the new version of the
component over the top of the previous version. Files belonging to the old distribution
are not deleted.</p>
<p>System configuration is preserved by retaining and restoring the previous version of
the following files:</p>
<p><tt class="FILENAME">Xaccel.ini</tt>, <tt class="FILENAME">XF86Config</tt>, <tt
class="FILENAME">adduser.conf</tt>, <tt class="FILENAME">aliases</tt>, <tt
class="FILENAME">aliases.db</tt>, <tt class="FILENAME">amd.map</tt>, <tt
class="FILENAME">crontab</tt>, <tt class="FILENAME">csh.cshrc</tt>, <tt
class="FILENAME">csh.login</tt>, <tt class="FILENAME">csh.logout</tt>, <tt
class="FILENAME">cvsupfile</tt>, <tt class="FILENAME">dhclient.conf</tt>, <tt
class="FILENAME">disktab</tt>, <tt class="FILENAME">dm.conf</tt>, <tt
class="FILENAME">dumpdates</tt>, <tt class="FILENAME">exports</tt>, <tt
class="FILENAME">fbtab</tt>, <tt class="FILENAME">fstab</tt>, <tt
class="FILENAME">ftpusers</tt>, <tt class="FILENAME">gettytab</tt>, <tt
class="FILENAME">gnats</tt>, <tt class="FILENAME">group</tt>, <tt
class="FILENAME">hosts</tt>, <tt class="FILENAME">hosts.allow</tt>, <tt
class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt
class="FILENAME">inetd.conf</tt>, <tt class="FILENAME">localtime</tt>, <tt
class="FILENAME">login.access</tt>, <tt class="FILENAME">login.conf</tt>, <tt
class="FILENAME">mail</tt>, <tt class="FILENAME">mail.rc</tt>, <tt
class="FILENAME">make.conf</tt>, <tt class="FILENAME">manpath.config</tt>, <tt
class="FILENAME">master.passwd</tt>, <tt class="FILENAME">motd</tt>, <tt
class="FILENAME">namedb</tt>, <tt class="FILENAME">networks</tt>, <tt
class="FILENAME">newsyslog.conf</tt>, <tt class="FILENAME">nsmb.conf</tt>, <tt
class="FILENAME">nsswitch.conf</tt>, <tt class="FILENAME">pam.conf</tt>, <tt
class="FILENAME">passwd</tt>, <tt class="FILENAME">periodic</tt>, <tt
class="FILENAME">ppp</tt>, <tt class="FILENAME">printcap</tt>, <tt
class="FILENAME">profile</tt>, <tt class="FILENAME">pwd.db</tt>, <tt
class="FILENAME">rc.conf</tt>, <tt class="FILENAME">rc.conf.local</tt>, <tt
class="FILENAME">rc.firewall</tt>, <tt class="FILENAME">rc.local</tt>, <tt
class="FILENAME">remote</tt>, <tt class="FILENAME">resolv.conf</tt>, <tt
class="FILENAME">rmt</tt>, <tt class="FILENAME">sendmail.cf</tt>, <tt
class="FILENAME">sendmail.cw</tt>, <tt class="FILENAME">services</tt>, <tt
class="FILENAME">shells</tt>, <tt class="FILENAME">skeykeys</tt>, <tt
class="FILENAME">spwd.db</tt>, <tt class="FILENAME">ssh</tt>, <tt
class="FILENAME">syslog.conf</tt>, <tt class="FILENAME">ttys</tt>, <tt
class="FILENAME">uucp</tt></p>
<p>The versions of these files which correspond to the new version are moved to <tt
class="FILENAME">/etc/upgrade/</tt>. The system administrator may peruse these new
versions and merge components as desired. Note that many of these files are
interdependent, and the best merge procedure is to copy all site-specific data from the
current files into the new.</p>
<p>During the upgrade procedure, the administrator is prompted for a location into which
all files from <tt class="FILENAME">/etc/</tt> are saved. In the event that local
modifications have been made to other files, they may be subsequently retrieved from this
location.</p>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN745" name="AEN745">3.2 Procedure</a></h3>
<p>This section details the upgrade procedure. Particular attention is given to items
which substantially differ from a normal installation.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN748" name="AEN748">3.2.1 Backup</a></h4>
<p>User data and system configuration should be backed up before upgrading. While the
upgrade procedure does its best to prevent accidental mistakes, it is possible to
partially or completely destroy data and configuration information.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN751" name="AEN751">3.2.2 Mount Filesystems</a></h4>
<p>The disklabel editor is entered with the nominated disk's filesystem devices listed.
Prior to commencing the upgrade, the administrator should make a note of the device names
and corresponding mountpoints. These mountpoints should be entered here. <span
class="emphasis"><i class="EMPHASIS">Do not</i></span> set the ``newfs flag'' for any
filesystems, as this will cause data loss.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN756" name="AEN756">3.2.3 Select Distributions</a></h4>
<p>When selecting distributions, there are no constraints on which must be selected. As a
general rule, the <var class="LITERAL">base</var> distribution should be selected for an
update, and the <var class="LITERAL">man</var> distribution if manpages are already
installed. Other distributions may be selected beyond those originally installed if the
administrator wishes to add additional functionality.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 After Installation</a></h4>
<p>Once the installation procedure has completed, the administrator is prompted to
examine the new configuration files. At this point, checks should be made to ensure that
the system configuration is valid. In particular, the <tt
class="FILENAME">/etc/rc.conf</tt> and <tt class="FILENAME">/etc/fstab</tt> files should
be checked.</p>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN766" name="AEN766">3.3 Upgrading from Source Code</a></h3>
<p>Those interested in an upgrade method that allows more flexibility and sophistication
should take a look at <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html"
target="_top">The Cutting Edge</a> in the FreeBSD Handbook. This procedure involves
rebuilding all of FreeBSD from source code. It requires reliable network connectivity,
extra disk space, and time, but has advantages for networks and other more complex
installations. This is roughly the same procedure as is used for track the -STABLE or
-CURRENT development branches.</p>
<p><tt class="FILENAME">/usr/src/UPDATING</tt> contains important information on updating
a FreeBSD system from source code. It lists various issues resulting from changes in
FreeBSD that may affect an upgrade.</p>
<p></p>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 Troubleshooting</a></h2>
<div class="SECT2">
<h3 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 Repairing an Existing FreeBSD
Installation</a></h3>
<p>FreeBSD features a ``Fixit'' option in the top menu of the boot floppy. To use it, you
will also need either a <tt class="FILENAME">fixit.flp</tt> image floppy, generated in
the same fashion as the boot floppy, or the ``live filesystem'' CDROM; typically the
second CDROM in a multi-disc FreeBSD distribution.</p>
<p>To invoke fixit, simply boot the <tt class="FILENAME">kern.flp</tt> floppy, choose the
``Fixit'' item and insert the fixit floppy or CDROM when asked. You will then be placed
into a shell with a wide variety of commands available (in the <tt
class="FILENAME">/stand</tt> and <tt class="FILENAME">/mnt2/stand</tt> directories) for
checking, repairing and examining filesystems and their contents. Some UNIX
administration experience <span class="emphasis"><i class="EMPHASIS">is</i></span>
required to use the fixit option.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN787" name="AEN787">4.2 Common Installation Problems for NEC
PC-98x1 Architecture Users</a></h3>
</div>
</div>
</div>
<hr />
<p align="center"><small>This file, and other release-related documents, can be
downloaded from <a href="ftp://ftp.FreeBSD.org/">ftp://ftp.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>For questions about this documentation, e-mail &#60;<a
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
<br />
<br />
</body>
</html>

924
en/releases/5.2R/installation-sparc64.html Normal file
View file

@ -0,0 +1,924 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>FreeBSD/sparc64 5.2-RELEASE Installation Instructions</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
<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 id="AEN2" name="AEN2">FreeBSD/sparc64 5.2-RELEASE Installation
Instructions</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
Project</p>
<hr />
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT"><a id="AEN11" name="AEN11"></a>
<p>This article gives some brief instructions on installing FreeBSD/sparc64 5.2-RELEASE,
with particular emphasis given to obtaining a FreeBSD distribution. Some notes on
troubleshooting and frequently-asked questions are also given.</p>
</div>
</blockquote>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="INSTALL" name="INSTALL">1 Installing FreeBSD</a></h2>
<p>This section documents the process of installing a new distribution of FreeBSD. These
instructions pay particular emphasis to the process of obtaining the FreeBSD 5.2-RELEASE
distribution and to beginning the installation procedure. The <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"
target="_top">``Installing FreeBSD''</a> chapter of the <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
Handbook</a> provides more in-depth information about the installation program itself,
including a guided walkthrough with screenshots.</p>
<p>If you are upgrading from a previous release of FreeBSD, please see <a
href="#UPGRADING">Section 3</a> for instructions on upgrading.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="GETTING-STARTED" name="GETTING-STARTED">1.1 Getting
Started</a></h3>
<p>Probably the most important pre-installation step that can be taken is that of reading
the various instruction documents provided with FreeBSD. A roadmap of documents
pertaining to this release of FreeBSD can be found in <tt
class="FILENAME">README.TXT</tt>, which can usually be found in the same location as this
file; most of these documents, such as the release notes and the hardware compatibility
list, are also accessible in the Documentation menu of the installer.</p>
<p>Note that on-line versions of the FreeBSD <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/" target="_top">FAQ</a> and <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
target="_top">Handbook</a> are also available from the <a href="http://www.FreeBSD.org/"
target="_top">FreeBSD Project Web site</a>, if you have an Internet connection.</p>
<p>This collection of documents may seem daunting, but the time spent reading them will
likely be saved many times over. Being familiar with what resources are available can
also be helpful in the event of problems during installation.</p>
<p>The best laid plans sometimes go awry, so if you run into trouble take a look at <a
href="#TROUBLE">Section 4</a>, which contains valuable troubleshooting information. You
should also read an updated copy of <tt class="FILENAME">ERRATA.TXT</tt> before
installing, since this will alert you to any problems which have reported in the interim
for your particular release.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> While FreeBSD does its best to safeguard against accidental loss of
data, it's still more than possible to <span class="emphasis"><i class="EMPHASIS">wipe
out your entire disk</i></span> with this installation if you make a mistake. Please do
not proceed to the final FreeBSD installation menu unless you've adequately backed up any
important data first.</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware Requirements</a></h3>
<p>FreeBSD for the UltraSPARC supports the platforms described in <tt
class="FILENAME">HARDWARE.TXT</tt>.</p>
<p>You will need a dedicated disk for FreeBSD/sparc64. It is not possible to share a disk
with another operating system at this time.</p>
<p>If you are not familiar with configuring hardware for FreeBSD, you should be sure to
read the <tt class="FILENAME">HARDWARE.TXT</tt> file; it contains important information
on what hardware is supported by FreeBSD.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 Floppy Disk Image
Instructions</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="START-INSTALLATION" name="START-INSTALLATION">1.4 Installing
FreeBSD from CDROM or the Internet</a></h3>
<p>Most sparc64 systems are set up to boot automatically from disk. To install FreeBSD,
you need to boot over the network or from a CDROM, which requires you to break into the
PROM (OpenFirmware).</p>
<p>To do this, reboot the system, and wait until the boot message appears. It depends on
the model, but should look about like:</p>
<pre class="SCREEN">
Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.
</pre>
<p>If your system proceeds to boot from disk at this point, you need to press <b
class="KEYCAP">L1</b>+<b class="KEYCAP">A</b> or <b class="KEYCAP">Stop</b>+<b
class="KEYCAP">A</b> on the keyboard, or send a <tt class="COMMAND">BREAK</tt> over the
serial console (using for example <tt class="COMMAND">~#</tt> in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tip&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tip</span>(1)</span></a> or <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=cu&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cu</span>(1)</span></a>) to get to
the PROM prompt. It looks like this:</p>
<pre class="SCREEN">
<samp class="PROMPT">ok </samp> <a id="PROMPT-SINGLE"
name="PROMPT-SINGLE"><b>(1)</b></a>
<samp class="PROMPT">ok {0}</samp> <a id="PROMPT-SMP"
name="PROMPT-SMP"><b>(2)</b></a>
</pre>
<div class="CALLOUTLIST">
<dl compact="COMPACT">
<dt><a href="#PROMPT-SINGLE"><b>(1)</b></a></dt>
<dd>This is the prompt used on systems with just one CPU.</dd>
<dt><a href="#PROMPT-SMP"><b>(2)</b></a></dt>
<dd>This is the prompt used on SMP systems, the digit indicates the number of the active
CPU.</dd>
</dl>
</div>
<p>At this point, place the CDROM into your drive, and from the PROM prompt, type <tt
class="COMMAND">boot cdrom</tt>.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN212" name="AEN212">1.5 Detail on various installation
types</a></h3>
<p>Once you've gotten yourself to the initial installation screen somehow, you should be
able to follow the various menu prompts and go from there. If you've never used the
FreeBSD installation before, you are also encouraged to read some of the documentation in
the Documentation submenu as well as the general ``Usage'' instructions on the first
menu.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> If you get stuck at a screen, press the <b class="KEYCAP">F1</b> key for
online documentation relevant to that specific section.</p>
</blockquote>
</div>
<p>If you've never installed FreeBSD before, or even if you have, the ``Standard''
installation mode is the most recommended since it makes sure that you'll visit all the
various important checklist items along the way. If you're much more comfortable with the
FreeBSD installation process and know <span class="emphasis"><i
class="EMPHASIS">exactly</i></span> what you want to do, use the ``Express'' or
``Custom'' installation options. If you're upgrading an existing system, use the
``Upgrade'' option.</p>
<p>The FreeBSD installer supports the direct use of floppy, DOS, tape, CDROM, FTP, NFS
and UFS partitions as installation media; further tips on installing from each type of
media are listed below.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN251" name="AEN251">1.5.1 Installing from a Network
CDROM</a></h4>
<p>If you simply wish to install from a local CDROM drive then see <a
href="#START-INSTALLATION">Section 1.4</a>. If you don't have a CDROM drive on your
system and wish to use a FreeBSD distribution CD in the CDROM drive of another system to
which you have network connectivity, there are also several ways of going about it:</p>
<ul>
<li>
<p>If you would be able to FTP install FreeBSD directly from the CDROM drive in some
FreeBSD machine, it's quite easy: You simply add the following line to the password file
(using the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vipw</span>(8)</span></a>
command):</p>
<pre class="SCREEN">
ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
</pre>
<p>On the machine on which you are running the install, go to the Options menu and set
Release Name to <var class="LITERAL">any</var>. You may then choose a Media type of <var
class="LITERAL">FTP</var> and type in <tt class="FILENAME">ftp://<var
class="REPLACEABLE">machine</var></tt> after picking ``URL'' in the ftp sites menu.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> This may allow anyone on the local network (or Internet) to make
``anonymous FTP'' connections to this machine, which may not be desirable.</p>
</blockquote>
</div>
</li>
<li>
<p>If you would rather use NFS to export the CDROM directly to the machine(s) you'll be
installing from, you need to first add an entry to the <tt
class="FILENAME">/etc/exports</tt> file (on the machine with the CDROM drive). The
example below allows the machine <tt class="HOSTID">ziggy.foo.com</tt> to mount the CDROM
directly via NFS during installation:</p>
<pre class="SCREEN">
/cdrom -ro ziggy.foo.com
</pre>
<p>The machine with the CDROM must also be configured as an NFS server, of course, and if
you're not sure how to do that then an NFS installation is probably not the best choice
for you unless you're willing to read up on <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.conf&amp;sektion=5&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rc.conf</span>(5)</span></a> and
configure things appropriately. Assuming that this part goes smoothly, you should be able
to enter: <tt class="FILENAME"><var class="REPLACEABLE">cdrom-host</var>:/cdrom</tt> as
the path for an NFS installation when the target machine is installed, e.g. <tt
class="FILENAME">wiggy:/cdrom</tt>.</p>
</li>
</ul>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN283" name="AEN283">1.5.2 Installing from Floppies</a></h4>
<p>If you must install from floppy disks, either due to unsupported hardware or just
because you enjoy doing things the hard way, you must first prepare some floppies for the
install.</p>
<p>First, make your boot floppies as described in <a href="#FLOPPIES">Section
1.3</a>.</p>
<p>Second, peruse <a href="#LAYOUT">Section 2</a> and pay special attention to the
``Distribution Format'' section since it describes which files you're going to need to
put onto floppy and which you can safely skip.</p>
<p>Next you will need, at minimum, as many 1.44MB floppies as it takes to hold all files
in the <tt class="FILENAME">bin</tt> (binary distribution) directory. If you're preparing
these floppies under DOS, then these floppies <span class="emphasis"><i
class="EMPHASIS">must</i></span> be formatted using the MS-DOS <tt
class="FILENAME">FORMAT</tt> command. If you're using Windows, use the Windows File
Manager format command.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> Frequently, floppy disks come ``factory preformatted''. While
convenient, many problems reported by users in the past have resulted from the use of
improperly formatted media. Re-format them yourself, just to make sure.</p>
</blockquote>
</div>
<p>If you're creating the floppies from another FreeBSD machine, a format is still not a
bad idea though you don't need to put a DOS filesystem on each floppy. You can use the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>
commands to put a UFS filesystem on a floppy, as the following sequence of commands
illustrates:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">fdformat -f 1440 fd0.1440</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">disklabel -w -r fd0.1440 floppy3</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</kbd>
</pre>
<p>After you've formatted the floppies for DOS or UFS, you'll need to copy the files onto
them. The distribution files are split into chunks conveniently sized so that 5 of them
will fit on a conventional 1.44MB floppy. Go through all your floppies, packing as many
files as will fit on each one, until you've got all the distributions you want packed up
in this fashion. Each distribution should go into its own subdirectory on the floppy,
e.g.: <tt class="FILENAME">a:\bin\bin.inf</tt>, <tt class="FILENAME">a:\bin\bin.aa</tt>,
<tt class="FILENAME">a:\bin\bin.ab</tt>, ...</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> The <tt class="FILENAME">bin.inf</tt> file also needs to go on the
first floppy of the <tt class="FILENAME">bin</tt> set since it is read by the
installation program in order to figure out how many additional pieces to look for when
fetching and concatenating the distribution. When putting distributions onto floppies,
the <tt class="FILENAME">distname.inf</tt> file <span class="emphasis"><i
class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set. This
is also covered in <tt class="FILENAME">README.TXT</tt>.</p>
</blockquote>
</div>
<p>Once you come to the Media screen of the install, select ``Floppy'' and you'll be
prompted for the rest.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN353" name="AEN353">1.5.4 Installing from QIC/SCSI
Tape</a></h4>
<p>When installing from tape, the installation program expects the files to be simply
tar'ed onto it, so after fetching all of the files for the distributions you're
interested in, simply use <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tar</span>(1)</span></a> to get
them onto the tape with a command something like this:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd <var
class="REPLACEABLE">/where/you/have/your/dists</var></kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/rsa0 <var
class="REPLACEABLE">dist1</var> .. <var class="REPLACEABLE">dist2</var></kbd>
</pre>
<p>When you go to do the installation, you should also make sure that you leave enough
room in some temporary directory (which you'll be allowed to choose) to accommodate the
<span class="emphasis"><i class="EMPHASIS">full</i></span> contents of the tape you've
created. Due to the non-random access nature of tapes, this method of installation
requires quite a bit of temporary storage. You should expect to require as much temporary
storage as you have stuff written on tape.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> When going to do the installation, the tape must be in the drive <span
class="emphasis"><i class="EMPHASIS">before</i></span> booting from the boot floppies.
The installation ``probe'' may otherwise fail to find it.</p>
</blockquote>
</div>
<p>Now create a boot floppy as described in <a href="#FLOPPIES">Section 1.3</a> and
proceed with the installation.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 Installing over a Network using FTP
or NFS</a></h4>
<p>After making the boot floppies as described in the first section, you can load the
rest of the installation over a network using one of 3 types of connections: serial port,
parallel port, or Ethernet.</p>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN378" name="AEN378">1.5.5.1 Serial Port</a></h5>
<p>SLIP support is rather primitive, and is limited primarily to hard-wired links, such
as a serial cable running between two computers. The link must be hard-wired because the
SLIP installation doesn't currently offer a dialing capability. If you need to dial out
with a modem or otherwise dialog with the link before connecting to it, then I recommend
that the PPP utility be used instead.</p>
<p>If you're using PPP, make sure that you have your Internet Service Provider's IP
address and DNS information handy as you'll need to know it fairly early in the
installation process. You may also need to know your own IP address, though PPP supports
dynamic address negotiation and may be able to pick up this information directly from
your ISP if they support it.</p>
<p>You will also need to know how to use the various ``AT commands'' for dialing out with
your particular brand of modem as the PPP dialer provides only a very simple terminal
emulator.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN384" name="AEN384">1.5.5.2 Parallel Port</a></h5>
<p>If a hard-wired connection to another FreeBSD or Linux machine is available, you might
also consider installing over a ``laplink'' style parallel port cable. The data rate over
the parallel port is much higher than what is typically possible over a serial line (up
to 50k/sec), thus resulting in a quicker installation. It's not typically necessary to
use ``real'' IP addresses when using a point-to-point parallel cable in this way and you
can generally just use RFC 1918 style addresses for the ends of the link (e.g. <tt
class="HOSTID">10.0.0.1</tt>, <tt class="HOSTID">10.0.0.2</tt>, etc).</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> If you use a Linux machine rather than a FreeBSD machine as your
PLIP peer, you will also have to specify <var class="OPTION">link0</var> in the TCP/IP
setup screen's ``extra options for ifconfig'' field in order to be compatible with
Linux's slightly different PLIP protocol.</p>
</blockquote>
</div>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5>
<p>FreeBSD supports many common Ethernet cards; a table of supported cards is provided as
part of the FreeBSD Hardware Notes (see <tt class="FILENAME">HARDWARE.TXT</tt> in the
Documentation menu on the boot floppy or the top level directory of the CDROM). If you
are using one of the supported PCMCIA Ethernet cards, also be sure that it's plugged in
<span class="emphasis"><i class="EMPHASIS">before</i></span> the laptop is powered on.
FreeBSD does not, unfortunately, currently support ``hot insertion'' of PCMCIA cards
during installation.</p>
<p>You will also need to know your IP address on the network, the <var
class="OPTION">netmask</var> value for your subnet and the name of your machine. Your
system administrator can tell you which values are appropriate to your particular network
setup. If you will be referring to other hosts by name rather than IP address, you'll
also need a name server and possibly the address of a gateway (if you're using PPP, it's
your provider's IP address) to use in talking to it. If you want to install by FTP via an
HTTP proxy (see below), you will also need the proxy's address.</p>
<p>If you do not know the answers to these questions then you should really probably talk
to your system administrator <span class="emphasis"><i class="EMPHASIS">first</i></span>
before trying this type of installation. Using a randomly chosen IP address or netmask on
a live network is almost guaranteed not to work, and will probably result in a lecture
from said system administrator.</p>
<p>Once you have a network connection of some sort working, the installation can continue
over NFS or FTP.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN406" name="AEN406">1.5.5.4 NFS installation tips</a></h5>
<p>NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution
files you want onto a server somewhere and then point the NFS media selection at it.</p>
<p>If this server supports only ``privileged port'' access (this is generally the default
for Sun and Linux workstations), you will need to set this option in the Options menu
before installation can proceed.</p>
<p>If you have a poor quality Ethernet card which suffers from very slow transfer rates,
you may also wish to toggle the appropriate Options flag.</p>
<p>In order for NFS installation to work, the server must also support ``subdir mounts'',
e.g. if your FreeBSD distribution directory lives on <tt
class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, then <tt
class="HOSTID">wiggy</tt> will have to allow the direct mounting of <tt
class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not just <tt class="FILENAME">/usr</tt>
or <tt class="FILENAME">/usr/archive/stuff</tt>.</p>
<p>In FreeBSD's <tt class="FILENAME">/etc/exports</tt> file this is controlled by the
<var class="OPTION">-alldirs</var> option. Other NFS servers may have different
conventions. If you are getting <var class="LITERAL">Permission Denied</var> messages
from the server then it's likely that you don't have this properly enabled.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="AEN423" name="AEN423">1.5.5.5 FTP Installation tips</a></h5>
<p>FTP installation may be done from any mirror site containing a reasonably up-to-date
version of FreeBSD. A full menu of reasonable choices for almost any location in the
world is provided in the FTP site menu during installation.</p>
<p>If you are installing from some other FTP site not listed in this menu, or you are
having troubles getting your name server configured properly, you can also specify your
own URL by selecting the ``URL'' choice in that menu. A URL can contain a hostname or an
IP address, so something like the following would work in the absence of a name
server:</p>
<pre class="SCREEN">
ftp://216.66.64.162/pub/FreeBSD/releases/sparc64/4.2-RELEASE
</pre>
<p>There are three FTP installation modes you can use:</p>
<ul>
<li>
<p>FTP: This method uses the standard ``Active'' mode for transfers, in which the server
initiates a connection to the client. This will not work through most firewalls but will
often work best with older FTP servers that do not support passive mode. If your
connection hangs with passive mode, try this one.</p>
</li>
<li>
<p>FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening
connections to the client. This option is best for users to pass through firewalls that
do not allow incoming connections on random port addresses.</p>
</li>
<li>
<p>FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy
for all FTP operations. The proxy will translate the requests and send them to the FTP
server. This allows the user to pass through firewalls that do not allow FTP at all, but
offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP
server.</p>
<p>In the rare case that you have an FTP proxy that does not go through HTTP, you can
specify the URL as something like:</p>
<pre class="SCREEN">
<kbd class="USERINPUT">ftp://foo.bar.com:<var
class="REPLACEABLE">port</var>/pub/FreeBSD</kbd>
</pre>
<p>In the URL above, <var class="REPLACEABLE">port</var> is the port number of the proxy
FTP server.</p>
</li>
</ul>
<br />
<br />
</div>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN466" name="AEN466">1.6 Question and Answer Section for
UltraSPARC Architecture Users</a></h3>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 Distribution Format</a></h2>
<p>A typical FreeBSD distribution directory looks something like this (exact details may
vary depending on version, architecture, and other factors):</p>
<pre class="SCREEN">
ERRATA.HTM README.TXT compat1x dict kernel
ERRATA.TXT RELNOTES.HTM compat20 doc manpages
HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages
HARDWARE.TXT base compat22 filename.txt ports
INSTALL.HTM boot compat3x floppies proflibs
INSTALL.TXT catpages compat4x games src
README.HTM cdrom.inf crypto info tools
</pre>
<p>If you want to do a CDROM, FTP or NFS installation from this distribution directory,
all you need to do is make the 1.44MB boot floppies from the floppies directory (see <a
href="#FLOPPIES">Section 1.3</a> for instructions on how to do this), boot them and
follow the instructions. The rest of the data needed during the installation will be
obtained automatically based on your selections. If you've never installed FreeBSD
before, you also want to read the entirety of this document (the installation
instructions) file.</p>
<p>If you're trying to do some other type of installation or are merely curious about how
a distribution is organized, what follows is a more thorough description of some of these
items in more detail:</p>
<ol type="1">
<li>
<p>The <tt class="FILENAME">*.TXT</tt> and <tt class="FILENAME">*.HTM</tt> files contain
documentation (for example, this document is contained in both <tt
class="FILENAME">INSTALL.TXT</tt> and <tt class="FILENAME">INSTALL.HTM</tt>) and should
be read before starting an installation. The <tt class="FILENAME">*.TXT</tt> files are
plain text, while the <tt class="FILENAME">*.HTM</tt> files are HTML files that can be
read by almost any Web browser. Some distributions may contain documentation in other
formats as well, such as PDF or PostScript.</p>
</li>
<li>
<p><tt class="FILENAME">docbook.css</tt> is a Cascading Style Sheet (CSS) file used by
some Web browsers for formatting the HTML documentation.</p>
</li>
<li>
<p>The <tt class="FILENAME">base</tt>, <tt class="FILENAME">catpages</tt>, <tt
class="FILENAME">crypto</tt>, <tt class="FILENAME">dict</tt>, <tt
class="FILENAME">doc</tt>, <tt class="FILENAME">games</tt>, <tt
class="FILENAME">info</tt>, <tt class="FILENAME">manpages</tt>, <tt
class="FILENAME">proflibs</tt>, and <tt class="FILENAME">src</tt> directories contain the
primary distribution components of FreeBSD itself and are split into smaller files for
easy packing onto floppies (should that be necessary).</p>
</li>
<li>
<p>The <tt class="FILENAME">compat1x</tt>, <tt class="FILENAME">compat20</tt>, <tt
class="FILENAME">compat21</tt>, <tt class="FILENAME">compat22</tt>, <tt
class="FILENAME">compat3x</tt>, and <tt class="FILENAME">compat4x</tt> directories
contain distributions for compatibility with older releases and are distributed as single
gzip'd tar files - they can be installed during release time or later by running their
<tt class="FILENAME">install.sh</tt> scripts.</p>
</li>
<li>
<p>The <tt class="FILENAME">floppies/</tt> subdirectory contains the floppy installation
images; further information on using them can be found in <a href="#FLOPPIES">Section
1.3</a>.</p>
</li>
<li>
<p>The <tt class="FILENAME">packages</tt> and <tt class="FILENAME">ports</tt> directories
contain the FreeBSD Packages and Ports Collections. Packages may be installed from the
packages directory by running the command:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp><kbd
class="USERINPUT">/stand/sysinstall configPackages</kbd>
</pre>
<p>Packages can also be installed by feeding individual filenames in <tt
class="FILENAME">packages</tt>/ to the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_add</span>(1)</span></a>
command.</p>
<p>The Ports Collection may be installed like any other distribution and requires about
100MB unpacked. More information on the ports collection may be obtained from <a
href="http://www.FreeBSD.org/ports/" target="_top">http://www.FreeBSD.org/ports/</a> or
locally from <tt class="FILENAME">/usr/share/doc/handbook</tt> if you've installed the
<tt class="FILENAME">doc</tt> distribution.</p>
</li>
<li>
<p>Last of all, the <tt class="FILENAME">tools</tt> directory contains various DOS tools
for discovering disk geometries, installing boot managers and the like. It is purely
optional and provided only for user convenience.</p>
</li>
</ol>
<br />
<br />
<p>A typical distribution directory (for example, the <tt class="FILENAME">info</tt>
distribution) looks like this internally:</p>
<pre class="SCREEN">
CHECKSUM.MD5 info.ab info.ad info.inf install.sh
info.aa info.ac info.ae info.mtree
</pre>
<p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains MD5 signatures for each file,
should data corruption be suspected, and is purely for reference. It is not used by the
actual installation and does not need to be copied with the rest of the distribution
files. The <tt class="FILENAME">info.a*</tt> files are split, gzip'd tar files, the
contents of which can be viewed by doing:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cat info.a* | tar tvzf -</kbd>
</pre>
<p>During installation, they are automatically concatenated and extracted by the
installation procedure.</p>
<p>The <tt class="FILENAME">info.inf</tt> file is also necessary since it is read by the
installation program in order to figure out how many pieces to look for when fetching and
concatenating the distribution. When putting distributions onto floppies, the <tt
class="FILENAME">.inf</tt> file <span class="emphasis"><i
class="EMPHASIS">must</i></span> occupy the first floppy of each distribution set!</p>
<p>The <tt class="FILENAME">info.mtree</tt> file is another non-essential file which is
provided for user reference. It contains the MD5 signatures of the <span
class="emphasis"><i class="EMPHASIS">unpacked</i></span> distribution files and can be
later used with the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mtree</span>(8)</span></a> program
to verify the installation permissions and checksums against any possible modifications
to the file. When used with the <tt class="FILENAME">base</tt> distribution, this can be
an excellent way of detecting trojan horse attacks on your system.</p>
<p>Finally, the <tt class="FILENAME">install.sh</tt> file is for use by those who want to
install the distribution after installation time. To install the info distribution from
CDROM after a system was installed, for example, you'd do:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /cdrom/info</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">sh install.sh</kbd>
</pre>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 Upgrading FreeBSD</a></h2>
<p>These instructions describe a procedure for doing a binary upgrade from an older
version of FreeBSD.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> While the FreeBSD upgrade procedure does its best to safeguard against
accidental loss of data, it is still more than possible to <span class="emphasis"><i
class="EMPHASIS">wipe out your entire disk</i></span> with this installation! Please do
not accept the final confirmation request unless you have adequately backed up any
important data files.</p>
</blockquote>
</div>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> These notes assume that you are using the version of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
supplied with the version of FreeBSD to which you intend to upgrade. Using a mismatched
version of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> is
almost guaranteed to cause problems and has been known to leave systems in an unusable
state. The most commonly made mistake in this regard is the use of an old copy of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
from an existing installation to upgrade to a newer version of FreeBSD. This is <span
class="emphasis"><i class="EMPHASIS">not</i></span> recommended.</p>
</blockquote>
</div>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> Binary upgrades to FreeBSD 5.2-RELEASE from FreeBSD 4-STABLE are not
supported at this time. There are some files present in a FreeBSD 4-STABLE whose presence
can be disruptive, but are not removed by a binary upgrade. One notable example is that
an old <tt class="FILENAME">/usr/include/g++</tt> directory will cause C++ programs to
compile incorrectly (or not at all).</p>
<p></p>
<p>These upgrade instructions are provided for the use of users upgrading from relatively
recent FreeBSD 5-CURRENT snapshots.</p>
</blockquote>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN667" name="AEN667">3.1 Introduction</a></h3>
<p>The upgrade procedure replaces distributions selected by the user with those
corresponding to the new FreeBSD release. It preserves standard system configuration
data, as well as user data, installed packages and other software.</p>
<p>Administrators contemplating an upgrade are encouraged to study this section in its
entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or
loss of data.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN671" name="AEN671">3.1.1 Upgrade Overview</a></h4>
<p>Upgrading of a distribution is performed by extracting the new version of the
component over the top of the previous version. Files belonging to the old distribution
are not deleted.</p>
<p>System configuration is preserved by retaining and restoring the previous version of
the following files:</p>
<p><tt class="FILENAME">Xaccel.ini</tt>, <tt class="FILENAME">XF86Config</tt>, <tt
class="FILENAME">adduser.conf</tt>, <tt class="FILENAME">aliases</tt>, <tt
class="FILENAME">aliases.db</tt>, <tt class="FILENAME">amd.map</tt>, <tt
class="FILENAME">crontab</tt>, <tt class="FILENAME">csh.cshrc</tt>, <tt
class="FILENAME">csh.login</tt>, <tt class="FILENAME">csh.logout</tt>, <tt
class="FILENAME">cvsupfile</tt>, <tt class="FILENAME">dhclient.conf</tt>, <tt
class="FILENAME">disktab</tt>, <tt class="FILENAME">dm.conf</tt>, <tt
class="FILENAME">dumpdates</tt>, <tt class="FILENAME">exports</tt>, <tt
class="FILENAME">fbtab</tt>, <tt class="FILENAME">fstab</tt>, <tt
class="FILENAME">ftpusers</tt>, <tt class="FILENAME">gettytab</tt>, <tt
class="FILENAME">gnats</tt>, <tt class="FILENAME">group</tt>, <tt
class="FILENAME">hosts</tt>, <tt class="FILENAME">hosts.allow</tt>, <tt
class="FILENAME">hosts.equiv</tt>, <tt class="FILENAME">hosts.lpd</tt>, <tt
class="FILENAME">inetd.conf</tt>, <tt class="FILENAME">localtime</tt>, <tt
class="FILENAME">login.access</tt>, <tt class="FILENAME">login.conf</tt>, <tt
class="FILENAME">mail</tt>, <tt class="FILENAME">mail.rc</tt>, <tt
class="FILENAME">make.conf</tt>, <tt class="FILENAME">manpath.config</tt>, <tt
class="FILENAME">master.passwd</tt>, <tt class="FILENAME">motd</tt>, <tt
class="FILENAME">namedb</tt>, <tt class="FILENAME">networks</tt>, <tt
class="FILENAME">newsyslog.conf</tt>, <tt class="FILENAME">nsmb.conf</tt>, <tt
class="FILENAME">nsswitch.conf</tt>, <tt class="FILENAME">pam.conf</tt>, <tt
class="FILENAME">passwd</tt>, <tt class="FILENAME">periodic</tt>, <tt
class="FILENAME">ppp</tt>, <tt class="FILENAME">printcap</tt>, <tt
class="FILENAME">profile</tt>, <tt class="FILENAME">pwd.db</tt>, <tt
class="FILENAME">rc.conf</tt>, <tt class="FILENAME">rc.conf.local</tt>, <tt
class="FILENAME">rc.firewall</tt>, <tt class="FILENAME">rc.local</tt>, <tt
class="FILENAME">remote</tt>, <tt class="FILENAME">resolv.conf</tt>, <tt
class="FILENAME">rmt</tt>, <tt class="FILENAME">sendmail.cf</tt>, <tt
class="FILENAME">sendmail.cw</tt>, <tt class="FILENAME">services</tt>, <tt
class="FILENAME">shells</tt>, <tt class="FILENAME">skeykeys</tt>, <tt
class="FILENAME">spwd.db</tt>, <tt class="FILENAME">ssh</tt>, <tt
class="FILENAME">syslog.conf</tt>, <tt class="FILENAME">ttys</tt>, <tt
class="FILENAME">uucp</tt></p>
<p>The versions of these files which correspond to the new version are moved to <tt
class="FILENAME">/etc/upgrade/</tt>. The system administrator may peruse these new
versions and merge components as desired. Note that many of these files are
interdependent, and the best merge procedure is to copy all site-specific data from the
current files into the new.</p>
<p>During the upgrade procedure, the administrator is prompted for a location into which
all files from <tt class="FILENAME">/etc/</tt> are saved. In the event that local
modifications have been made to other files, they may be subsequently retrieved from this
location.</p>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN745" name="AEN745">3.2 Procedure</a></h3>
<p>This section details the upgrade procedure. Particular attention is given to items
which substantially differ from a normal installation.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN748" name="AEN748">3.2.1 Backup</a></h4>
<p>User data and system configuration should be backed up before upgrading. While the
upgrade procedure does its best to prevent accidental mistakes, it is possible to
partially or completely destroy data and configuration information.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN751" name="AEN751">3.2.2 Mount Filesystems</a></h4>
<p>The disklabel editor is entered with the nominated disk's filesystem devices listed.
Prior to commencing the upgrade, the administrator should make a note of the device names
and corresponding mountpoints. These mountpoints should be entered here. <span
class="emphasis"><i class="EMPHASIS">Do not</i></span> set the ``newfs flag'' for any
filesystems, as this will cause data loss.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN756" name="AEN756">3.2.3 Select Distributions</a></h4>
<p>When selecting distributions, there are no constraints on which must be selected. As a
general rule, the <var class="LITERAL">base</var> distribution should be selected for an
update, and the <var class="LITERAL">man</var> distribution if manpages are already
installed. Other distributions may be selected beyond those originally installed if the
administrator wishes to add additional functionality.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 After Installation</a></h4>
<p>Once the installation procedure has completed, the administrator is prompted to
examine the new configuration files. At this point, checks should be made to ensure that
the system configuration is valid. In particular, the <tt
class="FILENAME">/etc/rc.conf</tt> and <tt class="FILENAME">/etc/fstab</tt> files should
be checked.</p>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN766" name="AEN766">3.3 Upgrading from Source Code</a></h3>
<p>Those interested in an upgrade method that allows more flexibility and sophistication
should take a look at <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html"
target="_top">The Cutting Edge</a> in the FreeBSD Handbook. This procedure involves
rebuilding all of FreeBSD from source code. It requires reliable network connectivity,
extra disk space, and time, but has advantages for networks and other more complex
installations. This is roughly the same procedure as is used for track the -STABLE or
-CURRENT development branches.</p>
<p><tt class="FILENAME">/usr/src/UPDATING</tt> contains important information on updating
a FreeBSD system from source code. It lists various issues resulting from changes in
FreeBSD that may affect an upgrade.</p>
<p></p>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 Troubleshooting</a></h2>
<div class="SECT2">
<h3 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 Repairing an Existing FreeBSD
Installation</a></h3>
<p>FreeBSD features a ``Fixit'' option in the top menu of the boot floppy. To use it, you
will also need either a <tt class="FILENAME">fixit.flp</tt> image floppy, generated in
the same fashion as the boot floppy, or the ``live filesystem'' CDROM; typically the
second CDROM in a multi-disc FreeBSD distribution.</p>
<p>To invoke fixit, simply boot the <tt class="FILENAME">kern.flp</tt> floppy, choose the
``Fixit'' item and insert the fixit floppy or CDROM when asked. You will then be placed
into a shell with a wide variety of commands available (in the <tt
class="FILENAME">/stand</tt> and <tt class="FILENAME">/mnt2/stand</tt> directories) for
checking, repairing and examining filesystems and their contents. Some UNIX
administration experience <span class="emphasis"><i class="EMPHASIS">is</i></span>
required to use the fixit option.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN787" name="AEN787">4.2 Common Installation Problems for
UltraSPARC Architecture Users</a></h3>
</div>
</div>
</div>
<hr />
<p align="center"><small>This file, and other release-related documents, can be
downloaded from <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/</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>For questions about this documentation, e-mail &#60;<a
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
<br />
<br />
</body>
</html>

422
en/releases/5.2R/readme.html Normal file
View file

@ -0,0 +1,422 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>FreeBSD 5.2-RELEASE README</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
<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 id="AEN2" name="AEN2">FreeBSD 5.2-RELEASE README</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003 The FreeBSD Documentation
Project</p>
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/readme/article.sgml,v 1.27
2003/09/08 14:53:02 simon Exp $<br />
</p>
<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a>
<p>FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to
change soon.</p>
<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States and
other countries.</p>
<p>Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The Open Group
are trademarks of The Open Group in the United States and other countries.</p>
<p>Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc
in the United States and other countries. Products bearing SPARC trademarks are based
upon architecture developed by Sun Microsystems, Inc.</p>
<p>Many of the designations used by manufacturers and sellers to distinguish their
products are claimed as trademarks. Where those designations appear in this document, and
the FreeBSD Project was aware of the trademark claim, the designations have been followed
by the ``&trade;'' or the ``&reg;'' symbol.</p>
</div>
<hr />
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT"><a id="AEN20" name="AEN20"></a>
<p>This document gives a brief introduction to FreeBSD 5.2-RELEASE. 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 />
<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
<p>This distribution is a release of FreeBSD 5.2-RELEASE, the latest point along the
5-CURRENT branch.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN25" name="AEN25">1.1 About FreeBSD</a></h3>
<p>FreeBSD is an operating system based on 4.4 BSD Lite for Intel, AMD, Cyrix or NexGen
``x86'' based PC hardware (<span class="TRADEMARK">i386</span>&#8482;), NEC PC-9801/9821
series PCs and compatibles (pc98), DEC/Compaq/HP Alpha computers (alpha), and <span
class="TRADEMARK">UltraSPARC</span>&reg; machines (<span
class="TRADEMARK">Sparc64</span>&reg;). Versions for the IA64 (ia64), <span
class="TRADEMARK">PowerPC</span>&reg; (<span class="TRADEMARK">PowerPC</span>), and AMD
``Hammer'' (amd64) 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 <span
class="TRADEMARK">UNIX</span>&reg; 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 10,000 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 <span
class="TRADEMARK">UNIX</span>. Most ports are also available as pre-compiled
``packages'', which can be quickly installed from the installation program.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN42" name="AEN42">1.2 Target Audience</a></h3>
<p>This release of FreeBSD is suitable for all users. It has undergone a period of
testing and quality assurance checking to ensure the highest reliability and
dependability.</p>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="OBTAIN" name="OBTAIN">2 Obtaining FreeBSD</a></h2>
<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 />
<h3 class="SECT2"><a id="AEN48" name="AEN48">2.1 CDROM and DVD</a></h3>
<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 />
<h3 class="SECT2"><a id="AEN55" name="AEN55">2.2 FTP</a></h3>
<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 <code class="EMAIL">&#60;<a
href="mailto:freebsd-admin@FreeBSD.org">freebsd-admin@FreeBSD.org</a>&#62;</code> 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 />
<h2 class="SECT1"><a id="CONTACTING" name="CONTACTING">3 Contacting the FreeBSD
Project</a></h2>
<div class="SECT2">
<h3 class="SECT2"><a id="AEN69" name="AEN69">3.1 Email and Mailing Lists</a></h3>
<p>For any questions or general technical support issues, please send mail to the <a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-questions" target="_top">FreeBSD
general questions mailing list</a>.</p>
<p>If you're tracking the 5-CURRENT development efforts, you <span class="emphasis"><i
class="EMPHASIS">must</i></span> join the <a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-current"
target="_top">FreeBSD-CURRENT mailing list</a>, 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 <a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hackers" target="_top">FreeBSD
technical discussions mailing list</a>.</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 <a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-announce" target="_top">FreeBSD
announcements mailing list</a>.</p>
<p>All of the mailing lists can be freely joined by anyone wishing to do so. Visit the <a
href="http://www.FreeBSD.org/mailman/listinfo" target="_top">FreeBSD Mailman Info
Page</a>. 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 from the Mailman pages 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 Mailman interface instead.</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN87" name="AEN87">3.2 Submitting Problem Reports</a></h3>
<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&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">send-pr</span>(1)</span></a>
command. ``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&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<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&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<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 <a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-bugs" target="_top">FreeBSD
problem reports mailing list</a>.</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 />
<h2 class="SECT1"><a id="SEEALSO" name="SEEALSO">4 Further Reading</a></h2>
<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 />
<h3 class="SECT2"><a id="RELEASE-DOCS" name="RELEASE-DOCS">4.1 Release
Documentation</a></h3>
<p>A number of other files provide more specific information about this release
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.2-RELEASE. Highly recommended reading for users new to FreeBSD 5-CURRENT and/or the
5.<var class="REPLACEABLE">X</var> 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.2-RELEASE compared to the previous release (FreeBSD
5.1-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 <span class="TRADEMARK">i386</span>, 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&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
(currently alpha, <span class="TRADEMARK">i386</span>, ia64, pc98, and <span
class="TRADEMARK">Sparc64</span>), 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&amp;sektion=8&amp;manpath=FreeBSD+5.2-RELEASE">
<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 />
<h3 class="SECT2"><a id="AEN157" name="AEN157">4.2 Manual Pages</a></h3>
<p>As with almost all <span class="TRADEMARK">UNIX</span> 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&amp;sektion=1&amp;manpath=FreeBSD+5.2-RELEASE">
<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 give information on particular topics.
Notable examples of such manual pages are <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tuning&amp;sektion=7&amp;manpath=FreeBSD+5.2-RELEASE">
<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&amp;sektion=7&amp;manpath=FreeBSD+5.2-RELEASE">
<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&amp;sektion=9&amp;manpath=FreeBSD+5.2-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">style</span>(9)</span></a> (a
style guide to kernel coding).</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN175" name="AEN175">4.3 Books and Articles</a></h3>
<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 <span
class="TRADEMARK">UNIX</span> heritage, many other articles and books written for <span
class="TRADEMARK">UNIX</span> systems are applicable as well, some of which are also
listed in the bibliography.</p>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="ACKNOWLEDGEMENTS" name="ACKNOWLEDGEMENTS">5
Acknowledgments</a></h2>
<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
release. 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 release 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="ftp://ftp.FreeBSD.org/">ftp://ftp.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>For questions about this documentation, e-mail &#60;<a
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</small></p>
<br />
<br />
</body>
</html>

1075
en/releases/5.2R/relnotes-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

1082
en/releases/5.2R/relnotes-amd64.html Normal file
View file

File diff suppressed because it is too large Load diff

1181
en/releases/5.2R/relnotes-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

1076
en/releases/5.2R/relnotes-ia64.html Normal file
View file

File diff suppressed because it is too large Load diff

1137
en/releases/5.2R/relnotes-pc98.html Normal file
View file

File diff suppressed because it is too large Load diff

1098
en/releases/5.2R/relnotes-sparc64.html Normal file
View file

File diff suppressed because it is too large Load diff