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

Add release documentation for 5.3-RELEASE in advance of the

Browse source 
release.  They are not hooked up the www build yet.
This commit is contained in:
Hiroki Sato 2004-11-05 21:44:27 +00:00
parent 1df8c0dd28
commit 579f412fbe
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=22796
19 changed files with 45507 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

297
en/releases/5.3R/errata.html Normal file
View file

@ -0,0 +1,297 @@
<!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.3-RELEASE Errata</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.3-RELEASE Errata</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003, 2004 The FreeBSD
Documentation Project</p>
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v
1.69.2.7 2004/11/05 21:21:29 hrs 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>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 lists errata items for FreeBSD 5.3-RELEASE, containing significant
information discovered after the release or too late in the release cycle to be otherwise
included in the release documentation. This information includes security advisories, as
well as news relating to the software or documentation that could affect its operation or
usability. An up-to-date version of this document should always be consulted before
installing this version of FreeBSD.</p>
<p>This errata document for FreeBSD 5.3-RELEASE will be maintained until the release of
FreeBSD 5.4-RELEASE.</p>
</div>
</blockquote>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
<p>This errata document contains ``late-breaking news'' about FreeBSD 5.3-RELEASE. Before
installing this version, it is important to consult this document to learn about any
post-release discoveries or problems that may already have been found and fixed.</p>
<p>Any version of this errata document actually distributed with the release (for
example, on a CDROM distribution) will be 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>, plus any sites which keep up-to-date
mirrors of this location.</p>
<p>Source and binary snapshots of FreeBSD 5-STABLE also contain up-to-date copies of this
document (as of the time of the snapshot).</p>
<p>For a list of all FreeBSD CERT security advisories, see <a
href="http://www.FreeBSD.org/security/"
target="_top">http://www.FreeBSD.org/security/</a> or <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"
target="_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/</a>.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="SECURITY" name="SECURITY">2 Security Advisories</a></h2>
<p>No advisories.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="OPEN-ISSUES" name="OPEN-ISSUES">3 Open Issues</a></h2>
<p>(31 Oct 2004) Sometimes the performance of the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=re&sektion=4&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">re</span>(4)</span></a> and <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> drivers can
become poor under heavy load. Especially, there are reports of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> on the IBM
ThinkPad T40 locking up under such conditions.</p>
<p>(31 Oct 2004) There are reports of the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&sektion=4&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">sk</span>(4)</span></a> driver locking
up under heavy load, especially when on-board NICs of ASUStek motherboards are used. To
clear the condition, bringing the interface down then back up and/or rebooting the system
are needed.</p>
<p>(31 Oct 2004) The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=burncd&sektion=8&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">burncd</span>(8)</span></a>
utility is functional but may behave erratically on some systems. Reported symptoms
include that <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=burncd&sektion=8&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">burncd</span>(8)</span></a> can
appear to hang up and never complete while the operation actually does complete, and the
progress indicator does not show the correct value. Workarounds include:</p>
<ul>
<li>
<p>Eject and re-insert a media after burning a CD.</p>
</li>
<li>
<p>Press Ctrl-C when <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=burncd&sektion=8&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">burncd</span>(8)</span></a>
appears to hang up in spite the access LED goes inactive.</p>
</li>
</ul>
<p>(31 Oct 2004) When the user/group rule modificators in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a> and <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> are
used, the loader tunable <var class="VARNAME">debug.mpsafenet</var> must be set to <var
class="LITERAL">0</var> (this is <var class="LITERAL">1</var> by default). For example,
the following rules are affected:</p>
<p>for <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a>:</p>
<pre class="PROGRAMLISTING">
count ip from any to 192.168.2.1 uid root
</pre>
<p>for <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a>:</p>
<pre class="PROGRAMLISTING">
block log quick proto { tcp, udp } all user root
</pre>
<p>To set <var class="VARNAME">debug.mpsafenet</var> to <var class="LITERAL">0</var> on
every boot, add the following line into <tt class="FILENAME">/boot/loader.conf</tt>:</p>
<pre class="PROGRAMLISTING">
debug.mpsafenet=0
</pre>
<p>More specifically, the <var class="LITERAL">group</var> and <var
class="LITERAL">user</var> filter parameters in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a>, and the <var
class="LITERAL">gid</var>, <var class="LITERAL">jail</var>, and <var
class="LITERAL">uid</var> rule options in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> are
relevant. If <var class="VARNAME">debug.mpsafenet</var> is set to <var
class="LITERAL">1</var>, the system can hang up when the rule is evaluated due to a lock
order reversal with the socket layer. More details can be found in the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> and <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pf.conf&sektion=5&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pf.conf</span>(5)</span></a>
manual pages.</p>
<p>(31 Oct 2004) The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vinum</span>(4)</span></a>
subsystem works fine on 5.3, but it can cause a system panic at boot time. As a
workaround you can add <var class="LITERAL">vinum_load="YES"</var> to <tt
class="FILENAME">/boot/loader.conf</tt>.</p>
<p>As an alternative you can also use the new, <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geom</span>(4)</span></a>-based <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vinum</span>(4)</span></a>
subsystem. To activate the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geom</span>(4)</span></a>-aware
vinum at boot time, add <var class="LITERAL">geom_vinum_load="YES"</var> to <tt
class="FILENAME">/boot/loader.conf</tt>.</p>
<p>While some sort of uncommon configurations such as multiple vinum drives in a disk are
not supported, it is basically backward compatible. Note that for the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">geom</span>(4)</span></a>-aware
vinum the new userland control program, <tt class="COMMAND">gvinum</tt> should be used,
and it still lacks some functionality.</p>
<p>(31 Oct 2004) The results of <tt class="COMMAND">netstat -m</tt> can become incorrect
on SMP systems when <var class="VARNAME">debug.mpsafenet</var> is set to <var
class="LITERAL">1</var> (default). This is an error in the statistics gathering because
of a race condition in the counters, not an actual memory leak.</p>
<p>(31 Oct 2004, updated on 5 Nov 2004) For FreeBSD/i386 and FreeBSD/amd64, when
installing FreeBSD 5.3 using an USB keyboard the keyboard will stop working once the
kernel boots, because a PS/2 keyboard is always attached. As a workaround, select
``Escape to loader prompt'' in the boot loader menu and enter the following lines at the
prompt:</p>
<pre class="SCREEN">
set hint.atkbd.0.flags="0x1"
boot
</pre>
<p>Note that if you use the boot floppies, this is set by default.</p>
<p>After the installation, add the following line into <tt
class="FILENAME">/boot/loader.conf</tt>:</p>
<pre class="PROGRAMLISTING">
hint.atkbd.0.flags="0x1"
</pre>
<p>(1 Nov 2004) The ULE scheduler described in the release note has been completely
disabled to discourage its use because it has several stability problems.</p>
<p>(1 Nov 2004) Programs linked with <b class="APPLICATION">libpthread</b> may not report
any CPU usage statistics according to <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=top&sektion=1&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">top</span>(1)</span></a>, while ones
linked with <b class="APPLICATION">libthr</b> have the correct statistics.</p>
<p>(1 Nov 2004) When CMD649 or SiI0680 ATA controller is used, the ATA RAID support of <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">ata</span>(4)</span></a> (ataraid) on
5.3 can corrupt the existing RAID configuration which was created on 5.2 or prior. The
ATA RAID support for these controllers is non-functional for this release.</p>
<p>(3 Nov 2004) For FreeBSD/i386 and FreeBSD/amd64, the SMP support in the <tt
class="FILENAME">GENERIC</tt> kernel has been disabled by default because the SMP kernel
can degrade the performance on UP machines. A kernel configuration file <tt
class="FILENAME">SMP</tt> which can be used to enable the SMP support has been added.
More details on building the custom kernel can be found in <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html"
target="_top">http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html</a>.</p>
<p>(4 Nov 2004) The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.3-stable"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">tar</span>(1)</span></a> (also known as
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdtar&sektion=1&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">bsdtar</span>(1)</span></a>)
utility does not detect the end of a recording medium such as a tape and a floppy disk
properly when it is specified in the <var class="OPTION">-f</var> option. As an
alternative <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=gtar&sektion=1&manpath=FreeBSD+5.3-stable">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gtar</span>(1)</span></a> (<b
class="APPLICATION">GNU tar</b>) can be used.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="LATE-NEWS" name="LATE-NEWS">4 Late-Breaking News</a></h2>
<p>No news.</p>
</div>
</div>
<hr />
<p align="center"><small>This file, and other release-related documents, can be
downloaded from <a
href="http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</a>.</small></p>
<p align="center"><small>For questions about FreeBSD, read the <a
href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small>All users of FreeBSD 5-STABLE should subscribe to the &#60;<a
href="mailto:stable@FreeBSD.org">stable@FreeBSD.org</a>&#62; mailing list.</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>
</body>
</html>

5827
en/releases/5.3R/hardware-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

5081
en/releases/5.3R/hardware-amd64.html Normal file
View file

File diff suppressed because it is too large Load diff

6392
en/releases/5.3R/hardware-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

4752
en/releases/5.3R/hardware-pc98.html Normal file
View file

File diff suppressed because it is too large Load diff

1862
en/releases/5.3R/hardware-sparc64.html Normal file
View file

File diff suppressed because it is too large Load diff

1153
en/releases/5.3R/installation-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

1550
en/releases/5.3R/installation-amd64.html Normal file
View file

File diff suppressed because it is too large Load diff

1607
en/releases/5.3R/installation-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

978
en/releases/5.3R/installation-pc98.html Normal file
View file

@ -0,0 +1,978 @@
<!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.3-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.3-RELEASE Installation
Instructions</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003, 2004 The FreeBSD
Documentation Project</p>
<hr />
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT"><a id="AEN12" name="AEN12"></a>
<p>This article gives some brief instructions on installing FreeBSD/pc98 5.3-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.3-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="AEN37" name="AEN37">1.2 Hardware Requirements</a></h3>
<p>FreeBSD for the NEC PC-98x1 requires a 486 or better processor to install and run
(although FreeBSD can run on 386 processors with a custom kernel) and at least 8 megs of
RAM to install and 7 megs to run. You will need at least 150MB 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 three) 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">boot.flp</tt> and <tt class="FILENAME">kernX.flp</tt> images (for 1.44MB
floppies) or <tt class="FILENAME">boot-small.flp</tt> and <tt
class="FILENAME">kern-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/boot.flp</tt>, and all of
the <var class="REPLACEABLE">release</var><tt class="FILENAME">/floppies/kernX.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://mirrorlist.FreeBSD.org/" target="_top">http://mirrorlist.FreeBSD.org/</a>
Web pages.</p>
<p>Get approximately three blank, freshly formatted floppies and image copy <tt
class="FILENAME">boot.flp</tt> onto one and the <tt class="FILENAME">kernX.flp</tt> files
onto the others. 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&sektion=1&manpath=FreeBSD+5.3-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">boot.flp</tt> into a directory somewhere. You would do the same for the
<tt class="FILENAME">kernX.flp</tt> files, 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/boot.flp of=/dev/rfd0.1440</kbd>
</pre>
<p>or</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">dd if=floppies/boot-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/boot.flp</tt> and <tt
class="FILENAME">floppies/kernX.flp</tt> using the instructions found in <a
href="#FLOPPIES">Section 1.3</a>. Restart your computer using the <tt
class="FILENAME">boot.flp</tt> disk; when prompted, insert the other disks as required.
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="AEN202" name="AEN202">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="AEN241" name="AEN241">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 ensure an FTP server is running and then simply add
the following line to the password file (using the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+5.3-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&sektion=5&manpath=FreeBSD+5.3-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="AEN273" name="AEN273">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&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.3-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</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">disklabel -w fd0 floppy3</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs -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 sized so that a floppy disk will hold a single file.
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.</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="AEN314" name="AEN314">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="AEN342" name="AEN342">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&sektion=1&manpath=FreeBSD+5.3-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/sa0 <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="AEN367" name="AEN367">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 the PPP
utility should 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="AEN373" name="AEN373">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="AEN384" name="AEN384">1.5.5.3 Ethernet</a></h5>
<p>FreeBSD supports most 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="AEN395" name="AEN395">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 may 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="AEN412" name="AEN412">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="AEN460" name="AEN460">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&sektion=1&manpath=FreeBSD+5.3-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
190MB 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&sektion=8&manpath=FreeBSD+5.3-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&sektion=8&manpath=FreeBSD+5.3-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&sektion=8&manpath=FreeBSD+5.3-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&sektion=8&manpath=FreeBSD+5.3-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.3-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>These upgrade instructions are provided for the use of users upgrading from relatively
recent FreeBSD 5-STABLE snapshots.</p>
</blockquote>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN683" name="AEN683">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="AEN687" name="AEN687">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="AEN761" name="AEN761">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="AEN764" name="AEN764">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="AEN767" name="AEN767">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="AEN772" name="AEN772">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="AEN782" name="AEN782">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>
</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="AEN802" name="AEN802">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>
</body>
</html>

911
en/releases/5.3R/installation-sparc64.html Normal file
View file

@ -0,0 +1,911 @@
<!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.3-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.3-RELEASE Installation
Instructions</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003, 2004 The FreeBSD
Documentation Project</p>
<hr />
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT"><a id="AEN12" name="AEN12"></a>
<p>This article gives some brief instructions on installing FreeBSD/sparc64 5.3-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.3-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="AEN37" name="AEN37">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&sektion=1&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tip</span>(1)</span></a> or <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=cu&sektion=1&manpath=FreeBSD+5.3-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="AEN202" name="AEN202">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="AEN241" name="AEN241">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 ensure an FTP server is running and then simply add
the following line to the password file (using the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+5.3-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&sektion=5&manpath=FreeBSD+5.3-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="AEN273" name="AEN273">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&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">disklabel</span>(8)</span></a> and
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.3-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</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">disklabel -w fd0 floppy3</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs -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 sized so that a floppy disk will hold a single file.
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.</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="AEN342" name="AEN342">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&sektion=1&manpath=FreeBSD+5.3-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/sa0 <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="AEN367" name="AEN367">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 the PPP
utility should 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="AEN373" name="AEN373">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="AEN384" name="AEN384">1.5.5.3 Ethernet</a></h5>
<p>FreeBSD supports most 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="AEN395" name="AEN395">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 may 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="AEN412" name="AEN412">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="AEN460" name="AEN460">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&sektion=1&manpath=FreeBSD+5.3-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
190MB 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&sektion=8&manpath=FreeBSD+5.3-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&sektion=8&manpath=FreeBSD+5.3-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&sektion=8&manpath=FreeBSD+5.3-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&sektion=8&manpath=FreeBSD+5.3-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.3-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>These upgrade instructions are provided for the use of users upgrading from relatively
recent FreeBSD 5-STABLE snapshots.</p>
</blockquote>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN683" name="AEN683">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="AEN687" name="AEN687">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="AEN761" name="AEN761">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="AEN764" name="AEN764">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="AEN767" name="AEN767">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="AEN772" name="AEN772">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="AEN782" name="AEN782">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>
</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="AEN802" name="AEN802">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/">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>
</body>
</html>

899
en/releases/5.3R/migration-guide.html Normal file
View file

@ -0,0 +1,899 @@
<!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.3-RELEASE Migration Guide</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.3-RELEASE Migration Guide</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, 2004 The FreeBSD Release Engineering
Team</p>
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/early-adopter/article.sgml,v
1.21.2.4 2004/10/06 05:55:51 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>Apple, FireWire, Mac, Macintosh, Mac OS, Quicktime, and TrueType are trademarks of
Apple Computer, Inc., registered in the United States and other countries.</p>
<p>IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks
of International Business Machines Corporation in the United States, other countries, or
both.</p>
<p>IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and
Electronics Engineers, Inc. in the United States.</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, IntelliMouse, 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="AEN23" name="AEN23"></a>
<p>This article describes major differences between FreeBSD 4.<var
class="REPLACEABLE">X</var> and FreeBSD 5.3-RELEASE, from the viewpoint of a user or
administrator upgrading an existing system. It provides a brief overview of FreeBSD
release engineering. It then describes some of the new features in FreeBSD 5.<var
class="REPLACEABLE">X</var>, as well as some changes that might be of particular interest
to users accustomed to working with the 4.<var class="REPLACEABLE">X</var> series of
releases. This article also describes binary- and source-based upgrading procedures for
existing systems. An earlier version of this article appeared in prior FreeBSD 5.<var
class="REPLACEABLE">X</var> releases as the ``Early Adopters Guide''.</p>
</div>
</div>
<hr />
</div>
<div class="SECT1">
<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
<p>FreeBSD 5.3-RELEASE marks the beginning of a new ``FreeBSD-STABLE'' series of
releases. This and future releases in the 5.<var class="REPLACEABLE">X</var> series will
be targeted toward production usage in much the same way as the prior 4.<var
class="REPLACEABLE">X</var> series of releases.</p>
<p>This article addresses a number of topics and issues of interest to users updating
from a 4.<var class="REPLACEABLE">X</var> release to 5.3-RELEASE. It begins with a brief
overview of current release engineering practices and then describes some of the new
features available with the FreeBSD 5.<var class="REPLACEABLE">X</var> series. Perhaps
the most important section lists issues where major changes have taken place,
user-visible behavior has changed, or external software interfaces have been modified.
Last are some notes on upgrading existing FreeBSD 4.<var class="REPLACEABLE">X</var>
systems to FreeBSD 5.3-RELEASE, from binaries or from source.</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 development model relying on multiple 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 CURRENT is the first to see new functionality, it also
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
added to these branches only after some amount of testing in CURRENT. For the past two
years, the only STABLE branch under active development was known 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>The past two stable branches (3-STABLE and 4-STABLE) were created very early in their
development cycles (their branchpoints were 3.1 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 creating some architectural changes that could not be ported between
branches at all.</p>
<p>The 5.<var class="REPLACEABLE">X</var> releases have been handled slightly
differently. FreeBSD 5.0, 5.1, and 5.2 were 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>Unlike prior ``STABLE'' branches, the ``5-STABLE'' branch in CVS (with the branch tag
<var class="LITERAL">RELENG_5</var>) was created more than a year after the first 5.<var
class="REPLACEABLE">X</var> release (specifically, during the 5.3 release cycle). This
delay gave time for the development team to complete needed architectural changes,
stabilize the system, finalize various interfaces, and create a good starting point for
the remaining 5.<var class="REPLACEABLE">X</var> releases.</p>
<p>Aside from general improvements and bug fixes, a major priority for development on the
5-STABLE branch is the preservation of Application Binary Interface (ABI) and Application
Program Interface (API) compatibility. Any changes that could break backward
compatibility (including kernel or library interfaces) are strongly discouraged, and will
not be permitted except as a last-resort solution to a critical problem.</p>
<p>The next release from CURRENT will likely be 6.0-RELEASE, created from CVS <var
class="LITERAL">HEAD</var>. There is no firm date for 6.0, as of the 5.3 release date,
although it is expected sometime in 2006.</p>
<p>A limited amount of development will continue on the 4-STABLE development branch, with
at least one more release (4.11) planned at some point after 5.3-RELEASE. For especially
conservative users, it may be reasonable to continue using the 4.<var
class="REPLACEABLE">X</var> releases for a time. 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.</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.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="NEW" name="NEW">3 New Features</a></h2>
<p>A major attraction of FreeBSD 5.<var class="REPLACEABLE">X</var> is a number of new
features, generally involving 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 updates to userland utilities, have already
been ported.) A brief, but not exhaustive list includes:</p>
<ul>
<li>
<p>SMPng: The ``next generation'' support for Symmetric MultiProcessor (SMP) machines.
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. Particular
attention has been paid to the performance of the network stack. More information can be
found on the <a href="http://www.FreeBSD.org/smp/index.html" 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">libpthread</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&sektion=3&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pthread</span>(3)</span></a> API.
<tt class="FILENAME">libpthread</tt> is now the default threading library.</p>
</li>
<li>
<p>New architectures: Support for the amd64, ia64, pc98, and sparc64 architectures, in
addition to the i386 and alpha. Other platforms under development include powerpc (which
runs on many <span class="TRADEMARK">PowerPC</span>&reg;-based <span
class="TRADEMARK">Macintosh</span>&reg; platforms) and arm.</p>
</li>
<li>
<p>GCC: The compiler toolchain is now based on GCC 3.4.<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, modular framework for transformation of disk I/O requests. This
system supports a number of features related to disks and volumes, such as: recognition
of disk partitions, the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=gbde&sektion=4&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gbde</span>(4)</span></a> disk
encryption facility, various levels of RAID functionality, network export of disk devices
(with <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ggated&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ggated</span>(8)</span></a> and
related utilities), and transparent disk decompression.</p>
</li>
<li>
<p>FFS: The FFS file system now supports background <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=fsck&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fsck</span>(8)</span></a>
operations (for faster crash recovery) and file system 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&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">newfs</span>(8)</span></a>. On all
platforms except pc98, file systems created from within <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
will use UFS2 by default.</p>
</li>
<li>
<p>New networking features: A number of new networking features have made their debut in
5.<var class="REPLACEABLE">X</var> releases, including support for TCP SACK (selective
acknowledgements), the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+5.3-RELEASE"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a> packet filter
from OpenBSD, and the ALTQ packet queueing system.</p>
</li>
<li>
<p>New hardware support: Support for more hardware devices, such as Cardbus, Bluetooth
devices, and IEEE 802.11a/b/g network interfaces based on Atheros chipsets. Also, on the
i386 architecture, some network devices not explicitly supported by FreeBSD drivers may
be supported using vendor drivers for <span class="TRADEMARK">Microsoft</span>&reg; <span
class="TRADEMARK">Windows</span>&reg; and the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ndis&sektion=4&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ndis</span>(4)</span></a>
compatibility layer.</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 Notable Changes</a></h2>
<p>Some of the differences between FreeBSD 4.<var class="REPLACEABLE">X</var> and 5.<var
class="REPLACEABLE">X</var> deserve special mention because they involve major
architectural changes, or break backwards compatibility in some way. While these changes
are unlikely to cause a loss of data, they could cause some confusion for the unwary.
Some notable examples are:</p>
<ul>
<li>
<p>Several parts of FreeBSD's base system functionality have been moved to the FreeBSD
Ports Collection, usually because they are easier to maintain in that form or because
they were not really essential parts of the system. The most noticeable example of this
is <b class="APPLICATION">Perl</b> (available in the FreeBSD Ports Collection as <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/perl5.8/pkg-descr"><tt
class="FILENAME">lang/perl5.8</tt></a>), whose former location in the base system made
upgrades problematic. Utilities in the base system that formerly relied on <b
class="APPLICATION">Perl</b> have been either rewritten (if still applicable) or removed
(if obsolete).</p>
<p>&#13;</p>
<p>Other examples include <b class="APPLICATION">UUCP</b> (available in the Ports
Collection as <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/net/freebsd-uucp/pkg-descr"><tt
class="FILENAME">net/freebsd-uucp</tt></a>), the <tt class="COMMAND">doscmd</tt> utility
(<a href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/doscmd/pkg-descr"><tt
class="FILENAME">emulators/doscmd</tt></a>), and many of the traditional games (<a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/games/freebsd-games/pkg-descr"><tt
class="FILENAME">games/freebsd-games</tt></a>).</p>
</li>
<li>
<p>Changes in kernel data structures and ABIs/APIs meant many third-party binary device
drivers had to be modified before they would work correctly under FreeBSD 5.<var
class="REPLACEABLE">X</var>. In some (hopefully rare) cases, user-visible data structures
have changed, requiring recompilation of applications or reinstallation of
ports/packages. As with the 4.<var class="REPLACEABLE">X</var> series, the FreeBSD
development team has the goal of not allowing incompatible changes in future releases on
the 5.<var class="REPLACEABLE">X</var> branch.</p>
</li>
<li>
<p>A shortage of users and maintainers caused some parts of the FreeBSD base system to
fall into disrepair. These have been removed. Examples include the generation of <tt
class="FILENAME">a.out</tt>-style executables, <a id="AEN159" name="AEN159"
href="#FTN.AEN159"><span class="footnote">[1]</span></a> XNS networking support, and the
X-10 controller driver. A number of other drivers for old ISA-based devices have been
discovered to be non-working and have been removed. More details are given in the release
notes.</p>
</li>
<li>
<p>On FreeBSD/i386 4.<var class="REPLACEABLE">X</var>, the configuration of ISA devices
was initially specified in the kernel configuration. These could be modified at boot-time
with an interactive <b class="APPLICATION">UserConfig</b> utility. On FreeBSD 5.<var
class="REPLACEABLE">X</var>, both of these mechanisms have been replaced by the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=device.hints&sektion=5&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">device.hints</span>(5)</span></a>
mechanism, which eliminates the need to hard-code ISA configuration parameters in the
kernel. Boot-time ISA configuration is no longer menu-driven, but is performed by
entering new parameters to the boot loader command line prompt.</p>
</li>
<li>
<p><tt class="FILENAME">MAKEDEV</tt> is no longer available, nor is it required. FreeBSD
5.<var class="REPLACEABLE">X</var> uses a device file system, which automatically creates
device nodes on demand. Configuration of the entries in the device filesystem can be
performed with the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devfs</span>(8)</span></a> utility
or with the <tt class="FILENAME">/etc/devfs.conf</tt> mechanism. More information can be
found in the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">devfs</span>(5)</span></a> manual
page.</p>
</li>
<li>
<p>UFS2 is the default on-disk format for file systems created using <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.3-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&sektion=8&manpath=FreeBSD+5.3-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 must 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&sektion=8&manpath=FreeBSD+5.3-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&sektion=8&manpath=FreeBSD+5.3-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>
</li>
<li>
<p>Due to the upgraded <b class="APPLICATION">GCC</b> compiler, C++ programs generally
need to be recompiled and reinstalled. This requirement comes from changes in the C++
ABI.</p>
</li>
<li>
<p>Running executables compiled for FreeBSD 4.<var class="REPLACEABLE">X</var> may be
possible with the aid of the <tt class="FILENAME">compat4x</tt> distribution (or the
equivalent <a href="http://www.FreeBSD.org/cgi/url.cgi?ports/misc/compat4x/pkg-descr"><tt
class="FILENAME">misc/compat4x</tt></a> package/port). However, if any of the ports or
packages on a system require upgrading, rebuilding and reinstalling <span
class="emphasis"><i class="EMPHASIS">all</i></span> of the installed ports on a system is
generally advised. This will prevent problems that can occur with programs being linked
against some combination of old and new libraries. The <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/portupgrade/pkg-descr"><tt
class="FILENAME">sysutils/portupgrade</tt></a> utility may be helpful in reinstalling
ports.</p>
<p>Note that in any case, there are a number of known instances of backward
incompatibility. For 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>
</li>
<li>
<p>The <tt class="FILENAME">host.conf</tt> resolver services configuration file has been
replaced by the (much more general) <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=nsswitch.conf&sektion=5&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nsswitch.conf</span>(5)</span></a>
name-service switch configuration mechanism.</p>
</li>
<li>
<p><b class="APPLICATION">BIND</b> has been updated from version 8 to version 9. There
are numerous differences between BIND 8 and 9. Users with critical <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=named&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">named</span>(8)</span></a>
installations should read the migration documentation in <tt
class="FILENAME">/usr/share/doc/bind9/misc/migration</tt>. There is also a new
instruction manual in <tt class="FILENAME">/usr/share/doc/bind9/arm</tt>. On systems that
run <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=named&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">named</span>(8)</span></a>, it now
runs by default in a <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">chroot</span>(8)</span></a>
environment in <tt class="FILENAME">/var/named</tt>. Users with existing <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=named&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">named</span>(8)</span></a>
configurations in <tt class="FILENAME">/var/named</tt> should back up the contents of
this directory before upgrading to avoid them being overwritten by the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=named&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">named</span>(8)</span></a> startup
script.</p>
</li>
<li>
<p>The <b class="APPLICATION">Xorg</b> implementation of the X Window System is the
default for FreeBSD 5.<var class="REPLACEABLE">X</var> beginning with 5.3-RELEASE. As of
this writing, <b class="APPLICATION"><span class="TRADEMARK">XFree86</span>&#8482;</b>
remains the default for FreeBSD 4.<var class="REPLACEABLE">X</var>. More information on
the differences between these versions, as well as upgrade information for existing
systems, can be found in the <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/x11.html" target="_top">X
Window System</a> chapter in the FreeBSD Handbook.</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>) is still being updated to reflect changes recently made to FreeBSD
5.<var class="REPLACEABLE">X</var>.</p>
</li>
</ul>
<p>More information can be found in the release notes for the various FreeBSD 5.<var
class="REPLACEABLE">X</var> releases, as well as the <tt
class="FILENAME">src/UPDATING</tt> file in the FreeBSD source tree. Notable changes to
the FreeBSD Ports Collection are listed in the <tt class="FILENAME">ports/UPDATING</tt>
and <tt class="FILENAME">ports/CHANGES</tt> files in the ports tree.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">5 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="AEN272" name="AEN272">5.1 Binary Upgrades</a></h3>
<p>Probably the most straightforward approach is that of ``backup everything, reformat,
reinstall, and restore user data''. This eliminates problems of incompatible or obsolete
executables and configuration files polluting the new system. It allows new file systems
to be created to take advantage of new functionality (most notably, the UFS2
defaults).</p>
<p>As of this writing, the binary upgrade option in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
has not been well-tested for cross-major-version upgrades. Use of this feature is not
recommended.</p>
<p>Several changes may be of interest to those users accustomed to the FreeBSD 4.<var
class="REPLACEABLE">X</var> boot media. Installation floppies (on platforms that support
them, such as i386), are organized somewhat differently than on prior releases. On 4.<var
class="REPLACEABLE">X</var> releases, the floppy set contained a stripped-down kernel
with just enough functionality to install the system. This arrangement allowed the kernel
to fit on a single floppy disk, but it lacked the device drivers required by certain
hardware configurations. Beginning with FreeBSD 5.3-RELEASE, the installation floppies
contain a standard <var class="LITERAL">GENERIC</var> kernel segmented across multiple
disks, with a much more complete set of drivers and features. The boot loader prompts for
the insertion of additional disks as required. Users downloading floppy images (perhaps
to perform a network-based installation) should note that the floppy disk set now
includes three disks: <tt class="FILENAME">boot.flp</tt>, <tt
class="FILENAME">kern1.flp</tt>, and <tt class="FILENAME">kern2.flp</tt>.</p>
<p>The installation CDROMs for the i386 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 kernels used on the floppy images in previous
versions. Generally, any system capable of booting the <span
class="TRADEMARK">Microsoft</span> <span
class="TRADEMARK">Windows&nbsp;NT</span>&reg;&nbsp;4, <span
class="TRADEMARK">Windows</span>&nbsp;2000, or <span
class="TRADEMARK">Windows</span>&nbsp;XP installation CDROMs should be able to boot the
FreeBSD 5.<var class="REPLACEABLE">X</var> CDROMs.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN295" name="AEN295">5.2 Source Upgrades</a></h3>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Many users and developers have found it easier to backup all their data
and configuration files (a wise precaution in any case), perform a binary installation
(such as from CDROM), and restore their data. Compared to a source upgrade, the binary
upgrade removes the need to deal with leftover files and programs on the disk, and allows
the system to take advantage of new file system features such as the UFS2 file system
layout.</p>
<p>Users unfamiliar with the <var class="LITERAL">buildworld</var>/<var
class="LITERAL">installworld</var> procedures for updating FreeBSD from source should
<span class="emphasis"><i class="EMPHASIS">not</i></span> attempt a source upgrade, but
should instead perform a binary installation after backing up all data.</p>
</blockquote>
</div>
<p>A source-based upgrade procedure builds and installs a set of binaries compiled from
source on the local machine. It is based on the <var
class="LITERAL">buildworld</var>/<var class="LITERAL">installworld</var> procedure often
used by advanced FreeBSD users to track changes along a development branch (such as
FreeBSD-STABLE or FreeBSD-CURRENT). In general, this procedure involves more effort than
the binary upgrade procedure, but may be useful when a system's configuration files are
complex or have been highly customized. A source upgrade can also be useful for a remote
system where an administrator has remote console access but no physical access (and
therefore cannot insert installation media).</p>
<p>Reading <tt class="FILENAME">src/UPDATING</tt> is absolutely essential. The section
entitled ``To upgrade in-place from 4.x-stable to current'' contains a step-by-step
update procedure, which must be followed exactly, without making use of the ``shortcuts''
that some users occasionally employ. An annotated list of these steps is presented
below:</p>
<ol type="1">
<li>
<p>Make backups.</p>
<p>The importance of this step cannot be overstated. It is important to make backups of
all user data and configuration files. Level zero dumps with <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">dump</span>(8)</span></a> are an
excellent way to do this, although there are of course many workable alternatives.</p>
</li>
<li>
<p>Ensure that there is about 30MB of free disk space on the <tt class="FILENAME">/</tt>
file system.</p>
<p>FreeBSD 5.<var class="REPLACEABLE">X</var> uses more space than FreeBSD 4.<var
class="REPLACEABLE">X</var>. If the <tt class="FILENAME">/tmp</tt> directory resides on
the <tt class="FILENAME">/</tt> file system (as is frequently the case), deleting all of
the content from this directory may help to free up needed space.</p>
</li>
<li>
<p>Fix <tt class="FILENAME">/etc/fstab</tt> if required.</p>
<p>This item probably only affects older FreeBSD/i386 systems. On systems that use
MBR-style disk slices, FreeBSD used to support ``compatibility slices'', where disk
partition names could take the form <tt class="FILENAME">/dev/ad0a</tt> (without
specifying a slice name explicitly). These are no longer supported; disk partitions must
be named according to the form <tt class="FILENAME">/dev/ad0s1a</tt>. In other words,
disk partitions must now completely specify a disk device, a slice number, and a
partition letter.</p>
<p>Note that ``compatibility slices'' have generally not been used by default since
FreeBSD 2.2.6-RELEASE. This item does not apply to FreeBSD/alpha at all, or to systems
using ``dangerously dediated'' mode.</p>
</li>
<li>
<p>Using <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=cvs&sektion=1&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cvs</span>(1)</span></a> or other
means, obtain a copy of the FreeBSD base system sources (the <tt
class="FILENAME">src/</tt> module). To check out 5.3-RELEASE from the FreeBSD CVS
repository, use the <var class="LITERAL">RELENG_5_3_0_RELEASE</var> tag. For the 5.3
release and security fix branch, use the <var class="LITERAL">RELENG_5_3</var> tag. To
track the FreeBSD 5-STABLE development branch, use the <var
class="LITERAL">RELENG_5</var> branch tag. When using CVS to check out the source tree,
it is important to pass the <var class="OPTION">-P</var> flag to CVS so that it prunes
away empty directories.</p>
</li>
<li>
<p>FreeBSD 5.<var class="REPLACEABLE">X</var> requires some new entries in the system
password and group files, corresponding to various system services. They should be
installed by running:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">mergemaster -p</kbd>
</pre>
<p>This step must be performed to give some new files the correct usernames and
groupnames.</p>
<p>Note that in FreeBSD 5.<var class="REPLACEABLE">X</var>, the location of the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=nologin&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nologin</span>(8)</span></a>
utility has moved from <tt class="FILENAME">/sbin/nologin</tt> to <tt
class="FILENAME">/usr/sbin/nologin</tt>. Because a number of pseudo-users have <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=nologin&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">nologin</span>(8)</span></a> as
their login shell, this change generates additional differences in <tt
class="FILENAME">/etc/passwd</tt>.</p>
</li>
<li>
<p>Build the new userland using:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /usr/src</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make buildworld</kbd>
</pre>
<p>If <var class="VARNAME">CPUTYPE</var> is defined in <tt
class="FILENAME">/etc/make.conf</tt>, it should be defined using the <var
class="LITERAL">?=</var> operator, so the <var class="LITERAL">buildworld</var> process
can override this variable if necessary.</p>
<p>Note that the <var class="VARNAME">MAKEOBJDIRPREFIX</var> must <span
class="emphasis"><i class="EMPHASIS">not</i></span> be defined in <tt
class="FILENAME">/etc/make.conf</tt>.</p>
<p>In general, most of the build ``knobs'' defined in <tt
class="FILENAME">/etc/make.conf</tt> should be commented out or removed. This statement
especially applies to those that directly affect the build or basic operation of FreeBSD,
such as <var class="VARNAME">NO_TOOLCHAIN</var>.</p>
</li>
<li>
<p>Build and install a new kernel using:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make buildkernel</kbd>
</pre>
<p>Note that the <var class="LITERAL">buildkernel</var> <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=make&sektion=1&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">make</span>(1)</span></a> target
must be used in order to ensure that the resulting kernel is compiled with the toolchain
built in the <var class="LITERAL">buildworld</var> step above. Manually using <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">config</span>(8)</span></a> to set
up a kernel build area and attempting to build a kernel will not work.</p>
<p>Although building (and later installing) a custom kernel at this point is feasible,
upgrading using the <var class="LITERAL">GENERIC</var> kernel and installing a custom
kernel configuration later may be less error-prone. When trying to build a custom kernel
for the first time, using the <var class="LITERAL">GENERIC</var> kernel from FreeBSD
5.<var class="REPLACEABLE">X</var> as a template is highly recommended, due to the number
of device and options that have been added or changed since 4.<var
class="REPLACEABLE">X</var>. In any case, including the <var
class="LITERAL">COMPAT_FREEBSD4</var> kernel configuration option is crucial for a
successful upgrade.</p>
</li>
<li>
<p>Set up a device hints file for ISA devices with a variant of the following command.
Substitute the appropriate architecture name (e.g. <var class="LITERAL">i386</var>) for
<var class="REPLACEABLE">MACHINE</var>.</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cp sys/<var
class="REPLACEABLE">MACHINE</var>/conf/GENERIC.hints /boot/device.hints</kbd>
</pre>
<p>While an empty device hint file may be sufficient for modern hardware, ISA hints are
needed for systems with custom ISA non-PNP cards (with custom hints being needed), for
non-PNPBIOS systems, or for floppy disks to work correctly on PNPBIOS systems.</p>
</li>
<li>
<p>Install the new kernel with:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make installkernel</kbd>
</pre>
<p>Note that while the FreeBSD 4.<var class="REPLACEABLE">X</var> kernel installs to <tt
class="FILENAME">/kernel</tt> by default, the FreeBSD 5.<var class="REPLACEABLE">X</var>
kernel installs to <tt class="FILENAME">/boot/kernel/kernel</tt>. Kernel modules under
4.<var class="REPLACEABLE">X</var> normally install to the <tt
class="FILENAME">/modules</tt> directory, whereas under 5.<var
class="REPLACEABLE">X</var> they install to <tt class="FILENAME">/boot/kernel</tt>.</p>
</li>
<li>
<p>Install the FreeBSD 5.<var class="REPLACEABLE">X</var> boot loader with:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /usr/src/sys/boot</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make STRIP="" install</kbd>
</pre>
<p>This step, though optional, is highly recommended.</p>
</li>
<li>
<p>Disable third-party modules (such as those for VMware) to prevent crashes caused by
changes in kernel ABIs or other incompatibilities.</p>
</li>
<li>
<p>Reboot to single-user mode. Rebooting at this point is absolutely required because the
new kernel must be running to install the new userland. Being in single-user mode will
drastically decrease the potential for unexpected things to happen during the upgrade
because there will be no other programs running.</p>
</li>
<li>
<p>Mount the required file systems using:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">fsck -p</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">mount -uw /</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">mount -at ufs</kbd>
</pre>
<p>Note that the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=fsck&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fsck</span>(8)</span></a>
invocation is necessary to update certain fields in the file system superblocks for
FreeBSD 5.<var class="REPLACEABLE">X</var>. If the system clock tracks local time rather
than UTC time, also perform:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">adjkerntz -i</kbd>
</pre>
<p>During this step, the following warning message may appear on the console (numerous
times).</p>
<pre class="SCREEN">
WARNING: userland calling deprecated sysctl, please rebuild world
</pre>
<p>This message can be safely ignored.</p>
</li>
<li>
<p>Delete the C++ header files with:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">rm -rf /usr/include/g++</kbd>
</pre>
<p>This step keeps future compilations from accidentally picking up old header files from
the <b class="APPLICATION">GCC</b> 2.95 C++ compiler.</p>
</li>
<li>
<p>Install the new userland utilities with:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /usr/src</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make installworld</kbd>
</pre>
</li>
<li>
<p>On systems running <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=named&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">named</span>(8)</span></a>, its
configuration files need to be moved into a <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">chroot</span>(8)</span></a> area
in <tt class="FILENAME">/var/named</tt>. If any files exist in <tt
class="FILENAME">/var/named</tt>, they should be backed up at this point.</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /etc</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">mv named named.bak</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">mkdir -p /var/named/etc/namedb</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">cp -Rp named.bak/* /var/named/etc/namedb</kbd>
</pre>
<p>If the configuration uses the generated <tt class="FILENAME">localhost</tt> files, the
following steps may be needed to regenerate them:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /var/named/etc/namedb</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">/bin/sh make-localhost</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">rm -f localhost-v6.rev localhost.rev</kbd>
</pre>
</li>
<li>
<p>Update the system configuration files by running:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">mergemaster -i</kbd>
</pre>
<p>This step is non-optional. It is required to make the startup and configuration files
in <tt class="FILENAME">/etc</tt> consistent with the new kernel and world.</p>
<p>After invoking <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mergemaster</span>(8)</span></a>,
it is a good idea to inspect (and possibly modify) <tt
class="FILENAME">/etc/rc.conf</tt>. A number of default values for the variables defined
in this file have changed; in particular, some services that were enabled by default in
4.<var class="REPLACEABLE">X</var> are now disabled by default in 5.<var
class="REPLACEABLE">X</var>.</p>
</li>
<li>
<p>Remove leftover <b class="APPLICATION">BIND 8</b> files:</p>
<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">rm /usr/bin/dnskeygen /usr/bin/dnsquery</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">rm /usr/libexec/named-xfer</kbd>
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">rm /usr/sbin/named.restart /usr/sbin/ndc</kbd>
</pre>
</li>
<li>
<p>Reboot.</p>
</li>
</ol>
<p>After upgrading the base system, upgrades to some non-base-system components are
generally needed to restore normal functionality. <b class="APPLICATION">Perl</b> is no
longer a part of the base system and should be installed from the Ports Collection
(specifically, the <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/perl5.8/pkg-descr"><tt
class="FILENAME">lang/perl5.8</tt></a> port) or from a package. After this installation,
all ports and/or packages depending on <b class="APPLICATION">Perl</b> need to be
reinstalled.</p>
<p>Running FreeBSD 4.<var class="REPLACEABLE">X</var> binaries requires a set of
compatability libraries. These are available by installing the <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/misc/compat4x/pkg-descr"><tt
class="FILENAME">misc/compat4x</tt></a> package/port.</p>
<p>As mentioned in a prior section, <b class="APPLICATION">Xorg</b> is the default
implementation of the X Window System. The Ports Collection (as well as packages) rely on
this change to satisfy dependencies. To convert the installed windowing system from <b
class="APPLICATION"><span class="TRADEMARK">XFree86</span></b> to <b
class="APPLICATION">Xorg</b>, refer to the <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/x-install.html"
target="_top">Installing X11</a> section in the FreeBSD Handbook.</p>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="SUMMARY" name="SUMMARY">6 Summary</a></h2>
<p>This article presents some of the more notable new features in FreeBSD 5.<var
class="REPLACEABLE">X</var>, and lists some areas of particular concern to those users
upgrading existing FreeBSD 4.<var class="REPLACEABLE">X</var> systems. It also presents
two sets of upgrade instructions, one using binaries from installation media and one
based on recompiling the base system from source code.</p>
</div>
</div>
<h3 class="FOOTNOTES">Notes</h3>
<table border="0" class="FOOTNOTES" width="100%">
<tr>
<td align="LEFT" valign="TOP" width="5%"><a id="FTN.AEN159" name="FTN.AEN159"
href="#AEN159"><span class="footnote">[1]</span></a></td>
<td align="LEFT" valign="TOP" width="95%">
<p>Note that execution of <tt class="FILENAME">a.out</tt> executables on the i386 and
pc98 is still supported with the <var class="LITERAL">COMPAT_AOUT</var> kernel option.
Some of the compilers in the Ports Collection (for example, <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/lang/gcc28/pkg-descr"><tt
class="FILENAME">lang/gcc28</tt></a>) are still capable of generating <tt
class="FILENAME">a.out</tt> format executables.</p>
</td>
</tr>
</table>
<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>
</body>
</html>

419
en/releases/5.3R/readme.html Normal file
View file

@ -0,0 +1,419 @@
<!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.3-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.3-RELEASE README</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003, 2004 The FreeBSD
Documentation Project</p>
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/readme/article.sgml,v
1.31.2.2 2004/09/17 16:28:58 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>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="AEN21" name="AEN21"></a>
<p>This document gives a brief introduction to FreeBSD 5.3-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.3-RELEASE, the latest point along the
5-STABLE branch.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN26" name="AEN26">1.1 About FreeBSD</a></h3>
<p>FreeBSD is an operating system based on 4.4 BSD Lite for DEC/Compaq/HP Alpha/AXP
computers (alpha), AMD64 and Intel EM64T based PC hardware (amd64), Intel, AMD, Cyrix or
NexGen ``x86'' based PC hardware (i386), Intel Itanium Processor based computers (ia64),
NEC PC-9801/9821 series PCs and compatibles (pc98), and <span
class="TRADEMARK">UltraSPARC</span>&reg; machines (sparc64). Versions for the <span
class="TRADEMARK">PowerPC</span>&reg; (powerpc), and <span
class="TRADEMARK">MIPS</span>&reg; (mips) 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,500 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="AEN40" name="AEN40">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="AEN46" name="AEN46">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="AEN53" name="AEN53">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://mirrorlist.FreeBSD.org/" target="_top">http://mirrorlist.FreeBSD.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="AEN67" name="AEN67">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-STABLE 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="AEN85" name="AEN85">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&sektion=1&manpath=FreeBSD+5.3-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&sektion=1&manpath=FreeBSD+5.3-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&sektion=1&manpath=FreeBSD+5.3-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 migration guide for users of FreeBSD 4.<var
class="REPLACEABLE">X</var> who are new to FreeBSD 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.3-RELEASE compared to the previous release (FreeBSD
5.2.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>&#8482;, and vice versa. The
architecture for which each document applies will be listed in that document's title.</p>
</blockquote>
</div>
<br />
<br />
<p>On platforms that support <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.3-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>&reg;), these documents are generally available via the
Documentation menu during installation. Once the system is installed, you can revisit
this menu by re-running the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.3-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="AEN156" name="AEN156">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&sektion=1&manpath=FreeBSD+5.3-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&sektion=7&manpath=FreeBSD+5.3-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&sektion=7&manpath=FreeBSD+5.3-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&sektion=9&manpath=FreeBSD+5.3-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="AEN174" name="AEN174">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>
</body>
</html>

2238
en/releases/5.3R/relnotes-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

2277
en/releases/5.3R/relnotes-amd64.html Normal file
View file

File diff suppressed because it is too large Load diff

2433
en/releases/5.3R/relnotes-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

2253
en/releases/5.3R/relnotes-ia64.html Normal file
View file

File diff suppressed because it is too large Load diff

2315
en/releases/5.3R/relnotes-pc98.html Normal file
View file

File diff suppressed because it is too large Load diff

2263
en/releases/5.3R/relnotes-sparc64.html Normal file
View file

File diff suppressed because it is too large Load diff