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

Stage 6.3-RELEASE/powerpc release documentation to the Web site.

Browse source 
We'll be doing a follow-up announcement about this soon.
This commit is contained in:
Bruce A. Mah 2008-01-18 20:11:12 +00:00
parent 6e919e0c17
commit 4b16f5434f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=31322
7 changed files with 3825 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
en/releases/6.3R/Makefile
View file

@ -1,4 +1,4 @@
# $FreeBSD: www/en/releases/6.3R/Makefile,v 1.4 2008/01/18 17:49:46 bmah Exp $
# $FreeBSD: www/en/releases/6.3R/Makefile,v 1.5 2008/01/18 18:39:33 bmah Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -22,17 +22,20 @@ DATA+= hardware-alpha.html
DATA+= hardware-amd64.html
DATA+= hardware-i386.html
DATA+= hardware-pc98.html
DATA+= hardware-powerpc.html
DATA+= hardware-sparc64.html
DATA+= installation-alpha.html
DATA+= installation-amd64.html
DATA+= installation-i386.html
DATA+= installation-pc98.html
DATA+= installation-powerpc.html
DATA+= installation-sparc64.html
DATA+= readme.html
DATA+= relnotes-alpha.html
DATA+= relnotes-amd64.html
DATA+= relnotes-i386.html
DATA+= relnotes-pc98.html
DATA+= relnotes-powerpc.html
DATA+= relnotes-sparc64.html
DATA+= docbook.css

2308
en/releases/6.3R/hardware-powerpc.html Normal file
View file

File diff suppressed because it is too large Load diff

3
en/releases/6.3R/hardware.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/6.3R/hardware.sgml,v 1.1 2008/01/17 16:13:58 hrs Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.3R/hardware.sgml,v 1.2 2008/01/18 17:05:08 hrs Exp $">
<!ENTITY title "FreeBSD 6.3-RELEASE Hardware Notes">
<!ENTITY % navinclude.download "INCLUDE">
]>
@ -19,6 +19,7 @@
<li><a href="hardware-amd64.html">amd64</a></li>
<li><a href="hardware-i386.html">i386</a></li>
<li><a href="hardware-pc98.html">pc98</a></li>
<li><a href="hardware-powerpc.html">powerpc</a></li>
<li><a href="hardware-sparc64.html">sparc64</a></li>
</ul>

899
en/releases/6.3R/installation-powerpc.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/powerpc 6.3-RELEASE Installation Instructions</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" />
<link rel="STYLESHEET" type="text/css" href="docbook.css" />
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
</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/powerpc 6.3-RELEASE Installation
Instructions</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003, 2004, 2005, 2006 The
FreeBSD Documentation Project</p>
<hr />
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT"><a id="AEN14" name="AEN14"></a>
<p>This article gives some brief instructions on installing FreeBSD/powerpc 6.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 6.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">&#8220;Installing FreeBSD&#8221;</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="AEN39" name="AEN39">1.2 Hardware Requirements</a></h3>
<p>If you are not familiar with configuring hardware for FreeBSD, you should be sure to
read the <tt class="FILENAME">HARDWARE.TXT</tt> file; it contains important information
on what hardware is supported by FreeBSD.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 Floppy Disk Image
Instructions</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="START-INSTALLATION" name="START-INSTALLATION">1.4 Installing
FreeBSD from CDROM or the Internet</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN214" name="AEN214">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 &#8220;Usage&#8221; 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
&#8220;Standard&#8221; 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 &#8220;Express&#8221; or
&#8220;Custom&#8221; installation options. If you're upgrading an existing system, use
the &#8220;Upgrade&#8221; 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="AEN253" name="AEN253">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+6.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 <tt class="LITERAL">any</tt>. You may then choose a Media type of <tt
class="LITERAL">FTP</tt> and type in <tt class="FILENAME">ftp://<tt
class="REPLACEABLE"><i>machine</i></tt></tt> after picking &#8220;URL&#8221; 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
&#8220;anonymous FTP&#8221; 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+6.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"><tt class="REPLACEABLE"><i>cdrom-host</i></tt>:/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="AEN285" name="AEN285">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
&#8220;Distribution Format&#8221; 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 &#8220;factory preformatted&#8221;.
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+6.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+6.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 &#8220;Floppy&#8221; and
you'll be prompted for the rest.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN354" name="AEN354">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+6.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 <tt
class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">tar cvf /dev/sa0 <tt
class="REPLACEABLE"><i>dist1</i></tt> .. <tt class="REPLACEABLE"><i>dist2</i></tt></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 &#8220;probe&#8221; 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="AEN379" name="AEN379">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 &#8220;AT commands&#8221; 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="AEN385" name="AEN385">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 &#8220;laplink&#8221; 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 &#8220;real&#8221; 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 <code class="OPTION">link0</code> in the TCP/IP
setup screen's &#8220;extra options for ifconfig&#8221; 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="AEN396" name="AEN396">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 &#8220;hot insertion&#8221; of PCMCIA
cards during installation.</p>
<p>You will also need to know your IP address on the network, the <code
class="OPTION">netmask</code> 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="AEN407" name="AEN407">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 &#8220;privileged port&#8221; 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 &#8220;subdir
mounts&#8221;, 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
<code class="OPTION">-alldirs</code> option. Other NFS servers may have different
conventions. If you are getting <tt class="LITERAL">Permission Denied</tt> 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="AEN424" name="AEN424">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 &#8220;URL&#8221; 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/powerpc/4.2-RELEASE
</pre>
<p>There are three FTP installation modes you can use:</p>
<ul>
<li>
<p>FTP: This method uses the standard &#8220;Active&#8221; 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:<tt
class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</kbd>
</pre>
<p>In the URL above, <tt class="REPLACEABLE"><i>port</i></tt> is the port number of the
proxy FTP server.</p>
</li>
</ul>
</div>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN475" name="AEN475">1.6 Question and Answer Section for
PowerPC 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>These same files are contained in the first CDROM of a multi-disk set, but they are
laid out slightly differently on the disk. On most architectures, the installation CDROM
also contains a &#8220;live filesystem&#8221; in addition to the distribution files. The
live filesystem is useful when repairing or troubleshooting an existing FreeBSD
installation (see <a href="#TROUBLE">Section 4</a> for how to use this).</p>
<p>The <tt class="FILENAME">floppies</tt> directory will be of particular interest to
users who are unable to boot from the CDROM media (but are able to read the CDROM by
other means). It is easy to generate a set of 1.44MB boot floppies from the <tt
class="FILENAME">floppies</tt> directory (see <a href="#FLOPPIES">Section 1.3</a> for
instructions on how to do this) and use these to start an installation from CDROM, FTP,
or NFS. 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">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+6.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>
<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+6.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+6.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+6.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+6.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 6.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 6-STABLE snapshots.</p>
</blockquote>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN704" name="AEN704">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="AEN708" name="AEN708">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="AEN782" name="AEN782">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="AEN785" name="AEN785">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="AEN788" name="AEN788">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 &#8220;newfs flag&#8221;
for any filesystems, as this will cause data loss.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="AEN793" name="AEN793">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 <tt class="LITERAL">base</tt> distribution should be selected for an
update, and the <tt class="LITERAL">man</tt> 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="AEN803" name="AEN803">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 &#8220;fixit&#8221; option in the top menu of the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
installation program. It provides a shell with common programs from the FreeBSD base
system; this environment is useful for repairing or troubleshooting an existing FreeBSD
installation. To use fixit mode, you will also need either the <tt
class="FILENAME">fixit.flp</tt> floppy, generated in the same fashion as the boot
floppies, or the &#8220;live filesystem&#8221; CDROM. In multi-disk FreeBSD
distributions, the live filesystem image is typically located on the installation disk.
Note that some UNIX system administration experience is required to use the fixit
option.</p>
<p>Generally, there are two ways of invoking fixit mode. Users who can boot from the
FreeBSD installation CDROM, should do so and then choose the &#8220;fixit&#8221; item
from the main <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
menu. Then select the &#8220;CDROM/DVD&#8221; option from the fixit menu.</p>
<p>Users who cannot boot from CDROM, but can boot from floppy disk, require a few more
steps. In addition to the <tt class="FILENAME">boot.flp</tt> and <tt
class="FILENAME">kern<tt class="REPLACEABLE"><i>X</i></tt>.flp</tt> disks required for
installation, create the <tt class="FILENAME">fixit.flp</tt> floppy disk, in the same way
as the other floppy disks. Follow the instructions for booting the installation program
from floppy disk until reaching the main <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
menu. At that point, choose the &#8220;fixit&#8221; item from the main <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
menu. Then select the &#8220;Floppy&#8221; option from the fixit menu, and insert the <tt
class="FILENAME">fixit.flp</tt> floppy disk when prompted to do so.</p>
<p>The CDROM and floppy fixit environments are similar, but not identical. Both offer a
shell with a variety of commands available for checking, repairing and examining
filesystems and their contents. The CDROM version of fixit provides all of the commands
and programs available in the FreeBSD base system, through the live filesystem. By
contrast, the floppy fixit environment can only offer a subset of commands due to space
constraints.</p>
<p>In the floppy version of fixit, some standalone utilities can be found in <tt
class="FILENAME">/stand</tt> or <tt class="FILENAME">/mnt2/stand</tt>. In the CDROM
version of fixit, these same programs can be found in <tt class="FILENAME">/stand</tt> or
<tt class="FILENAME">/mnt2/rescue</tt> (as well as the rest of the programs from the live
filesystem, which can be found under <tt class="FILENAME">/mnt</tt>).</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="AEN847" name="AEN847">4.2 Common Installation Problems for
PowerPC 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="http://www.FreeBSD.org/snapshots/">http://www.FreeBSD.org/snapshots/</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 6-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>

3
en/releases/6.3R/installation.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/6.3R/installation.sgml,v 1.1 2008/01/17 16:13:58 hrs Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.3R/installation.sgml,v 1.2 2008/01/18 17:05:08 hrs Exp $">
<!ENTITY title "FreeBSD 6.3-RELEASE Installation Notes">
<!ENTITY % navinclude.download "INCLUDE">
]>
@ -19,6 +19,7 @@
<li><a href="installation-amd64.html">amd64</a></li>
<li><a href="installation-i386.html">i386</a></li>
<li><a href="installation-pc98.html">pc98</a></li>
<li><a href="installation-powerpc.html">powerpc</a></li>
<li><a href="installation-sparc64.html">sparc64</a></li>
</ul>

608
en/releases/6.3R/relnotes-powerpc.html Normal file
View file

@ -0,0 +1,608 @@
<!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/powerpc 6.3-RELEASE Release Notes</title>
<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79" />
<link rel="STYLESHEET" type="text/css" href="docbook.css" />
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
</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/powerpc 6.3-RELEASE Release
Notes</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
2008 The FreeBSD Documentation Project</p>
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
1.883.2.87.2.7 2008/01/15 02:34:11 hrs Exp $<br />
</p>
<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a>
<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</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>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 &#8220;&trade;&#8221; or the &#8220;&reg;&#8221; symbol.</p>
</div>
<div>
<div class="ABSTRACT"><a id="AEN26" name="AEN26"></a>
<p>The release notes for FreeBSD 6.3-RELEASE contain a summary of the changes made to the
FreeBSD base system on the 6.3-STABLE development line. This document lists applicable
security advisories that were issued since the last release, as well as significant
changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also
presented.</p>
</div>
</div>
<hr />
</div>
<div class="TOC">
<dl>
<dt><b>Table of Contents</b></dt>
<dt>1 <a href="#INTRO">Introduction</a></dt>
<dt>2 <a href="#NEW">What's New</a></dt>
<dd>
<dl>
<dt>2.1 <a href="#SECURITY">Security Advisories</a></dt>
<dt>2.2 <a href="#KERNEL">Kernel Changes</a></dt>
<dd>
<dl>
<dt>2.2.1 <a href="#BOOT">Boot Loader Changes</a></dt>
<dt>2.2.2 <a href="#PROC">Hardware Support</a></dt>
<dt>2.2.3 <a href="#NET-PROTO">Network Protocols</a></dt>
<dt>2.2.4 <a href="#DISKS">Disks and Storage</a></dt>
<dt>2.2.5 <a href="#FS">File Systems</a></dt>
</dl>
</dd>
<dt>2.3 <a href="#USERLAND">Userland Changes</a></dt>
<dd>
<dl>
<dt>2.3.1 <a href="#RC-SCRIPTS"><tt class="FILENAME">/etc/rc.d</tt> Scripts</a></dt>
</dl>
</dd>
<dt>2.4 <a href="#CONTRIB">Contributed Software</a></dt>
<dt>2.5 <a href="#PORTS">Ports/Packages Collection Infrastructure</a></dt>
<dt>2.6 <a href="#RELENG">Release Engineering and Integration</a></dt>
<dt>2.7 <a href="#DOC">Documentation</a></dt>
</dl>
</dd>
<dt>3 <a href="#UPGRADE">Upgrading from previous releases of FreeBSD</a></dt>
</dl>
</div>
<div class="SECT1">
<h2 class="SECT1"><a id="INTRO" name="INTRO">1 Introduction</a></h2>
<p>This document contains the release notes for FreeBSD 6.3-RELEASE on the PowerPC
hardware platform. It describes recently added, changed, or deleted features of FreeBSD.
It also provides some notes on upgrading from previous versions of FreeBSD.</p>
<p>This distribution of FreeBSD 6.3-RELEASE is a release distribution. It can be found at
<a href="ftp://ftp.FreeBSD.org/" target="_top">ftp://ftp.FreeBSD.org/</a> or any of its
mirrors. More information on obtaining this (or other) release distributions of FreeBSD
can be found in the <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html"
target="_top">&#8220;Obtaining FreeBSD&#8221; appendix</a> to the <a
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" target="_top">FreeBSD
Handbook</a>.</p>
<p>All users are encouraged to consult the release errata before installing FreeBSD. The
errata document is updated with &#8220;late-breaking&#8221; information discovered late
in the release cycle or after the release. Typically, it contains information on known
bugs, security advisories, and corrections to documentation. An up-to-date copy of the
errata for FreeBSD 6.3-RELEASE can be found on the FreeBSD Web site.</p>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="NEW" name="NEW">2 What's New</a></h2>
<p>This section describes the most user-visible new or changed features in FreeBSD since
6.2-RELEASE.</p>
<p>Typical release note items document recent security advisories issued after
6.2-RELEASE, new drivers or hardware support, new commands or options, major bug fixes,
or contributed software upgrades. They may also list changes to major ports/packages or
release engineering practices. Clearly the release notes cannot list every single change
made to FreeBSD between releases; this document focuses primarily on security advisories,
user-visible changes, and major architectural improvements.</p>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 Security Advisories</a></h3>
<p>Two remote denials of service in BIND (one involving DNSSEC and one involving
recursive DNS queries) have been fixed. For more information, see security advisory <a
href="http://security.FreeBSD.org/advisories/FreeBSD-SA-07:02.bind.asc"
target="_top">FreeBSD-SA-07:02.bind</a>.</p>
<p>Processing of IPv6 type 0 Routing Headers is now controlled by the <code
class="VARNAME">net.inet6.ip6.rthdr0_allowed</code> sysctl variable, which defaults to
<tt class="LITERAL">0</tt> (off). For more information, see security advisory <a
href="http://security.FreeBSD.org/advisories/FreeBSD-SA-07:03.ipv6.asc"
target="_top">FreeBSD-SA-07:03.ipv6</a>.</p>
<p>Problems with <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=libarchive&sektion=3&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">libarchive</span>(3)</span></a>
and <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tar</span>(1)</span></a> handling
corrupted <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=5&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tar</span>(5)</span></a> archive
files have been fixed. More details can be found in security advisory <a
href="http://security.FreeBSD.org/advisories/FreeBSD-SA-07:05.libarchive.asc"
target="_top">FreeBSD-SA-07:05.libarchive</a>.</p>
<p>A buffer overflow in OpenSSL (fixed incorrectly in a previously security patch) has
been corrected. More details can be found in security advisory <a
href="http://security.FreeBSD.org/advisories/FreeBSD-SA-07:08.openssl.asc"
target="_top">FreeBSD-SA-07:08.openssl</a>.</p>
<p>An flaw that could lead to the disclosure of previously-generated <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=random&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">random</span>(4)</span></a> data
has been corrected. Information regarding this issue can be found in security advisory <a
href="http://security.FreeBSD.org/advisories/FreeBSD-SA-07:09.random.asc"
target="_top">FreeBSD-SA-07:09.random</a>.</p>
<p>Information disclosure issues found in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=openpty&sektion=3&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">openpty</span>(3)</span></a> and
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ptsname&sektion=3&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ptsname</span>(3)</span></a> have
been corrected. Information regarding this issue can be found in security advisory <a
href="http://security.FreeBSD.org/advisories/FreeBSD-SA-08:01.pty.asc"
target="_top">FreeBSD-SA-08:01.pty</a>.</p>
<p>A programming error in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=inet_network&sektion=3&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">inet_network</span>(3)</span></a>
Internet address manipulation function that could lead to overwriting a region of memory
with user defined data has been corrected. Information regarding this issue can be found
in security advisory <a
href="http://security.FreeBSD.org/advisories/FreeBSD-SA-08:02.libc.asc"
target="_top">FreeBSD-SA-08:02.libc</a>.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel Changes</a></h3>
<p><a
href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi</span>(4)</span></a> now has
support for the HPET time counter.</p>
<p>Support for Message Signaled Interrupts (MSI) and Extended Message Signaled Interrupts
(MSI-X) has been added to the kernel's PCI support code.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="BOOT" name="BOOT">2.2.1 Boot Loader Changes</a></h4>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="PROC" name="PROC">2.2.2 Hardware Support</a></h4>
<p>An <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi_dock&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">acpi_dock</span>(4)</span></a>
driver has been added to provide support for controlling laptop docking station functions
via ACPI.</p>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="MM" name="MM">2.2.2.1 Multimedia Support</a></h5>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_envy24&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_envy24</span>(4)</span></a>
driver has been added to support the Envy24 series of audio chips.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_envy24ht&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_envy24ht</span>(4)</span></a>
driver has been added to support the VIA Envy24HT series of audio chips.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_hda&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_hda</span>(4)</span></a>
driver has been added. It supports devices that conform to revision 1.0 of the Intel High
Definition Audio specification.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=snd_spicds&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">snd_spicds</span>(4)</span></a>
driver has been added to support I2S SPI audio codec chips.</p>
</div>
<div class="SECT4">
<hr />
<h5 class="SECT4"><a id="NET-IF" name="NET-IF">2.2.2.2 Network Interface Support</a></h5>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ath</span>(4)</span></a> driver
has been updated to HAL version 0.9.20.3.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">axe</span>(4)</span></a> driver
now supports <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=altq&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">altq</span>(4)</span></a>.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=cxgb&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cxgb</span>(4)</span></a> driver
has been added. It provides support for 10 Gigabit Ethernet adapters based on the Chelsio
T3 and T3B chipsets.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=edsc&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">edsc</span>(4)</span></a> driver,
which provides Ethernet discard network interfaces, has been added.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+6.3-RELEASE"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">em</span>(4)</span></a> driver has been
updated to version 6.7.2 from Intel.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=msk&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">msk</span>(4)</span></a> driver
has been added. It supports network interfaces using the Marvell/SysKonnect Yukon II
Gigabit Ethernet controller.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=vge&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">vge</span>(4)</span></a> driver
now supports <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=altq&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">altq</span>(4)</span></a>.</p>
<p>The 802.11 protocol stack now has support for 900 MHz cards, as well as quarter- and
half-channel support for 802.11a.</p>
</div>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="NET-PROTO" name="NET-PROTO">2.2.3 Network Protocols</a></h4>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a>
driver now supports RSTP, the Rapid Spanning Tree Protocol (802.1w).</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=lagg&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">lagg</span>(4)</span></a> driver,
ported from OpenBSD and NetBSD, has been added to support a variety of protocols and
algorithms for link aggregation, failover, and fault tolerance.</p>
<p>A new <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_deflate&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_deflate</span>(4)</span></a>
NetGraph node type has been added. It implements Deflate PPP compression.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_ppp&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_ppp</span>(4)</span></a>
Netgraph node is now MPSAFE.</p>
<p>A new <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_pred1&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ng_pred1</span>(4)</span></a>
NetGraph node type has been added to implement Predictor-1 PPP compression.</p>
<p>A bug which prevented FreeBSD 6.2-RELEASE from running IPv6 correctly over <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=gif&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gif</span>(4)</span></a> tunnels
has been fixed.</p>
<p>The <code class="VARNAME">net.link.tap.up_on_open</code> sysctl variable has been
added to the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tap&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tap</span>(4)</span></a> driver.
If enabled, new tap devices will marked <tt class="LITERAL">up</tt> upon creation.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="DISKS" name="DISKS">2.2.4 Disks and Storage</a></h4>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> driver
has been updated to support various new features such as RAID volume and RAID member
state/settings reporting, periodic volume re-synchronization status reporting, and sysctl
variables for volume re-synchronization rate, volume member write cache status, and
volume transaction queue depth.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mpt&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mpt</span>(4)</span></a> driver
now supports SAS HBA (partially), 64-bit PCI, and large data transfer.</p>
<p>The scsi_sg driver, which emulates a significant subset of the Linux SCSI SG
passthrough device API, has been added. It is intended to allow programs running under
Linux emulation (as well as native FreeBSD applications) to access the <tt
class="FILENAME">/dev/sg<tt class="REPLACEABLE"><i>*</i></tt></tt> devices supported by
Linux.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=twa&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">twa</span>(4)</span></a> driver
has been updated to the 3.60.03.006 release on the 3ware Web site. It now supports AMCC's
3ware 9650 series of SATA controllers.</p>
</div>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="FS" name="FS">2.2.5 File Systems</a></h4>
<p>The unionfs file system has been re-implemented. This version solves many crashing and
locking issues compared to the previous implementation. It also adds new
&#8220;transparent&#8221; and &#8220;masquerade&#8221; modes for automatically creating
files in the upper file system layer of unions. More information can be found in the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_unionfs&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mount_unionfs</span>(8)</span></a>
manual page.</p>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 Userland Changes</a></h3>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=camcontrol&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">camcontrol</span>(8)</span></a>
utility now supports a <tt class="COMMAND">readcap</tt> command to display the size of
devices.</p>
<p>A bug in <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=freebsd-update&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span
class="REFENTRYTITLE">freebsd-update</span>(8)</span></a>, which caused it not to update
SMP kernels correctly, has been fixed.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=fdisk&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">fdisk</span>(8)</span></a> program
now supports a <code class="OPTION">-p</code> flag to print the slice table in fdisk
configuration format.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=freebsd-update&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span
class="REFENTRYTITLE">freebsd-update</span>(8)</span></a> utility now supports an <tt
class="COMMAND">upgrade</tt> command to perform binary upgrades between different
versions of FreeBSD.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ftpd</span>(8)</span></a> utility
now has support for RFC2389 (FEAT) and rudimentary support for RFC2640 (UTF8). The
RFC2640 support is optional and can be enabled using the new <code
class="OPTION">-8</code> flag. More information can be found in the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ftpd</span>(8)</span></a> manual
page.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfwpcap&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfwpcap</span>(8)</span></a>
utility has been added; it captures packets on a <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=divert&sektion=4&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">divert</span>(4)</span></a> socket
and writes them as <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pcap&sektion=3&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pcap</span>(3)</span></a> (also
known as <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=tcpdump&sektion=1&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">tcpdump</span>(1)</span></a>)
format data to a file or pipe.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=rpc.lockd&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rpc.lockd</span>(8)</span></a> and
<a
href="http://www.FreeBSD.org/cgi/man.cgi?query=rpc.statd&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">rpc.statd</span>(8)</span></a>
programs now accept <code class="OPTION">-p</code> options to indicate which port they
should bind to.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=pw&sektion=8&manpath=FreeBSD+6.3-RELEASE"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">pw</span>(8)</span></a> program now
supports a <code class="OPTION">-M</code> option to set the permissions of a user's newly
created home directory.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=top&sektion=1&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">top</span>(1)</span></a> program
now supports a <code class="OPTION">-j</code> flag to display the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">jail</span>(8)</span></a> ID for
each process.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=touch&sektion=1&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">touch</span>(1)</span></a> utility
now supports a <code class="OPTION">-A</code> flag that allows the access and
modification times of a file be adjusted by a specified value.</p>
<p>The <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=wpa_passphrase&sektion=8&manpath=FreeBSD+6.3-RELEASE">
<span class="CITEREFENTRY"><span
class="REFENTRYTITLE">wpa_passphrase</span>(8)</span></a> utility has been added. It
generates a 256-bit pre-shared WPA key from an ASCII passphrase.</p>
<div class="SECT3">
<hr />
<h4 class="SECT3"><a id="RC-SCRIPTS" name="RC-SCRIPTS">2.3.1 <tt
class="FILENAME">/etc/rc.d</tt> Scripts</a></h4>
<p>The <tt class="FILENAME">sendmail</tt> script can be instructed not to rebuild the
aliases database if it is missing or older than the aliases file. If desired, set the new
rc.conf option <code class="VARNAME">sendmail_rebuild_aliases</code> to "NO" to turn off
that functionality.</p>
<p>The <tt class="FILENAME">/etc/rc.d/nfslocking</tt> script has been deprecated and will
be removed in a future release. It has been replaced by the <tt
class="FILENAME">/etc/rc.d/lockd</tt> and <tt class="FILENAME">/etc/rc.d/statd</tt>
scripts.</p>
</div>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="CONTRIB" name="CONTRIB">2.4 Contributed Software</a></h3>
<p><b class="APPLICATION">awk</b> has been updated from the 24 April 2005 release to the
1 May 2007 release.</p>
<p><b class="APPLICATION">BIND</b> has been updated from 9.3.3 to 9.3.4-p1.</p>
<p><b class="APPLICATION">BZIP2</b> has been updated from 1.0.3 to 1.0.4.</p>
<p>GNU <b class="APPLICATION">Diffutils</b> has been updated from 2.7 to 2.8.7.</p>
<p>The GNU version of <b class="APPLICATION">gzip</b> has been replaced with a modified
version of gzip ported from NetBSD.</p>
<p><b class="APPLICATION">IPFilter</b> has been updated from 4.1.13 to 4.1.28.</p>
<p><b class="APPLICATION">less</b> has been updated from v381 to v416.</p>
<p><b class="APPLICATION">ncurses</b> has been updated from 5.2-20020615 to 5.6-20061217.
ncurses now also has wide character support.</p>
<p><b class="APPLICATION">netcat</b> has been updated from the version in a 4 February
2005 OpenBSD snapshot to the version included in OpenBSD 4.1.</p>
<p><b class="APPLICATION">GNU Readline library</b> has been updated from 5.0 to 5.2 patch
2.</p>
<p><b class="APPLICATION">sendmail</b> has been updated from 8.13.8 to 8.14.2.</p>
<p>The timezone database has been updated from the <b class="APPLICATION">tzdata2006g</b>
release to the <b class="APPLICATION">tzdata2007k</b> release.</p>
<p>TrustedBSD <b class="APPLICATION">OpenBSM</b> has been updated from 1.0 alpha 12 to
1.0.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="PORTS" name="PORTS">2.5 Ports/Packages Collection
Infrastructure</a></h3>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="RELENG" name="RELENG">2.6 Release Engineering and
Integration</a></h3>
<p>The supported version of the <b class="APPLICATION">GNOME</b> desktop environment (<a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/gnome2/pkg-descr"><tt
class="FILENAME">x11/gnome2</tt></a>) has been updated from 2.16.1 to 2.20.1.</p>
<p>The supported version of the <b class="APPLICATION">KDE</b> desktop environment (<a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/kde3/pkg-descr"><tt
class="FILENAME">x11/kde3</tt></a>) has been updated from 3.5.4 to 3.5.7.</p>
<p>The supported version of the <b class="APPLICATION">Xorg</b> windowing system (<a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/x11/xorg/pkg-descr"><tt
class="FILENAME">x11/xorg</tt></a>) has been updated from 6.9.0 to 7.3.0.</p>
<p>The default value of <code class="VARNAME">X11BASE</code> has been changed from <tt
class="FILENAME">/usr/X11R6</tt> to <tt class="FILENAME">/usr/local</tt>, the default
value of <code class="VARNAME">LOCALBASE</code>.</p>
</div>
<div class="SECT2">
<hr />
<h3 class="SECT2"><a id="DOC" name="DOC">2.7 Documentation</a></h3>
</div>
</div>
<div class="SECT1">
<hr />
<h2 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 Upgrading from previous releases of
FreeBSD</a></h2>
<p>Source upgrades to FreeBSD 6.3-RELEASE are only supported from FreeBSD 5.3-RELEASE or
later. Users of older systems wanting to upgrade 6.3-RELEASE will need to update to
FreeBSD 5.3 or newer first, then to FreeBSD 6.3-RELEASE.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> Upgrading FreeBSD should, of course, only be attempted after backing
up <span class="emphasis"><i class="EMPHASIS">all</i></span> data and configuration
files.</p>
</blockquote>
</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>

3
en/releases/6.3R/relnotes.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/6.3R/relnotes.sgml,v 1.1 2008/01/17 16:13:58 hrs Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.3R/relnotes.sgml,v 1.2 2008/01/18 17:05:09 hrs Exp $">
<!ENTITY title "FreeBSD 6.3-RELEASE Release Notes">
<!ENTITY % navinclude.download "INCLUDE">
]>
@ -19,6 +19,7 @@
<li><a href="relnotes-amd64.html">amd64</a></li>
<li><a href="relnotes-i386.html">i386</a></li>
<li><a href="relnotes-pc98.html">pc98</a></li>
<li><a href="relnotes-powerpc.html">powerpc</a></li>
<li><a href="relnotes-sparc64.html">sparc64</a></li>
</ul>