Add the 6.1 release documentation.
This commit is contained in:
parent
af29c64846
commit
44d517116e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=27757
20 changed files with 42925 additions and 0 deletions
en/releases/6.1R
errata.htmlhardware-alpha.htmlhardware-amd64.htmlhardware-i386.htmlhardware-ia64.htmlhardware-pc98.htmlhardware-sparc64.htmlinstallation-alpha.htmlinstallation-amd64.htmlinstallation-i386.htmlinstallation-ia64.htmlinstallation-pc98.htmlinstallation-sparc64.htmlreadme.htmlrelnotes-alpha.htmlrelnotes-amd64.htmlrelnotes-i386.htmlrelnotes-ia64.htmlrelnotes-pc98.htmlrelnotes-sparc64.html
445
en/releases/6.1R/errata.html
Normal file
445
en/releases/6.1R/errata.html
Normal file
|
@ -0,0 +1,445 @@
|
|||
<!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 6.0-RELEASE Errata</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 6.0-RELEASE Errata</a></h1>
|
||||
|
||||
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
|
||||
|
||||
<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006 The
|
||||
FreeBSD Documentation Project</p>
|
||||
|
||||
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v
|
||||
1.73.2.15.2.1 2006/04/24 01:05:46 delphij Exp $<br />
|
||||
</p>
|
||||
|
||||
<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a>
|
||||
<p>FreeBSD is a registered trademark of the FreeBSD Foundation.</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 “™” or the “®” symbol.</p>
|
||||
</div>
|
||||
|
||||
<hr />
|
||||
</div>
|
||||
|
||||
<blockquote class="ABSTRACT">
|
||||
<div class="ABSTRACT"><a id="AEN22" name="AEN22"></a>
|
||||
<p>This document lists errata items for FreeBSD 6.0-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 6.0-RELEASE will be maintained until the release of
|
||||
FreeBSD 6.2-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
|
||||
6.0-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 6.1-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="LATE-NEWS" name="LATE-NEWS">2 Update Information</a></h2>
|
||||
|
||||
<p>No news.</p>
|
||||
</div>
|
||||
|
||||
<div class="SECT1">
|
||||
<hr />
|
||||
<h2 class="SECT1"><a id="SECURITY" name="SECURITY">3 Security Advisories</a></h2>
|
||||
|
||||
<p>The following security advisories pertain to FreeBSD 6.0-RELEASE. For more
|
||||
information, consult the individual advisories available from <a
|
||||
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/"
|
||||
target="_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/</a>.</p>
|
||||
|
||||
<div class="INFORMALTABLE"><a id="AEN43" name="AEN43"></a>
|
||||
<table border="0" frame="void" class="CALSTABLE">
|
||||
<col width="1*" />
|
||||
<col width="1*" />
|
||||
<col width="3*" />
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Advisory</th>
|
||||
<th>Date</th>
|
||||
<th>Topic</th>
|
||||
</tr>
|
||||
</thead>
|
||||
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:14.fpu.asc"
|
||||
target="_top">06:14.fpu</a></td>
|
||||
<td>19 April 2006</td>
|
||||
<td>
|
||||
<p>FPU information disclosure</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a
|
||||
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc"
|
||||
target="_top">06:13.sendmail</a></td>
|
||||
<td>22 March 2006</td>
|
||||
<td>
|
||||
<p>Race condition in sendmail</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:12.opie.asc"
|
||||
target="_top">06:12.opie</a></td>
|
||||
<td>22 March 2006</td>
|
||||
<td>
|
||||
<p>OPIE arbitrary password change</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a
|
||||
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:11.ipsec.asc"
|
||||
target="_top">06:11.ipsec</a></td>
|
||||
<td>22 March 2006</td>
|
||||
<td>
|
||||
<p>IPsec replay attack vulnerability</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:10.nfs.asc"
|
||||
target="_top">06:10.nfs</a></td>
|
||||
<td>1 March 2006</td>
|
||||
<td>
|
||||
<p>Remote denial of service in NFS server</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:07.pf.asc"
|
||||
target="_top">06:07.pf</a></td>
|
||||
<td>25 January 2006</td>
|
||||
<td>
|
||||
<p>IP fragment handling panic in <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span
|
||||
class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a></p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:06.kmem.asc"
|
||||
target="_top">06:06.kmem</a></td>
|
||||
<td>25 January 2006</td>
|
||||
<td>
|
||||
<p>Local kernel memory disclosure</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a
|
||||
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:05.80211.asc"
|
||||
target="_top">06:05.80211</a></td>
|
||||
<td>18 January 2006</td>
|
||||
<td>
|
||||
<p>IEEE 802.11 buffer overflow</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:04.ipfw.asc"
|
||||
target="_top">06:04.ipfw</a></td>
|
||||
<td>11 January 2006</td>
|
||||
<td>
|
||||
<p><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IP
|
||||
fragment denial of service</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:03.cpio.asc"
|
||||
target="_top">06:03.cpio</a></td>
|
||||
<td>11 January 2006</td>
|
||||
<td>
|
||||
<p>Multiple vulnerabilities in <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=cpio&sektion=1&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">cpio</span>(1)</span></a></p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:02.ee.asc"
|
||||
target="_top">06:02.eex</a></td>
|
||||
<td>11 January 2006</td>
|
||||
<td>
|
||||
<p><a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ee&sektion=1&manpath=FreeBSD+6.1-RELEASE"><span
|
||||
class="CITEREFENTRY"><span class="REFENTRYTITLE">ee</span>(1)</span></a> temporary file
|
||||
privilege escalation</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><a
|
||||
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:01.texindex.asc"
|
||||
target="_top">06:01.texindex</a></td>
|
||||
<td>11 January 2006</td>
|
||||
<td>
|
||||
<p>Texindex temporary file privilege escalation</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="SECT1">
|
||||
<hr />
|
||||
<h2 class="SECT1"><a id="KNOWN-PROBLEMS" name="KNOWN-PROBLEMS">4 Known Problems and
|
||||
Solutions</a></h2>
|
||||
|
||||
<p>(2005/11/26) On 6.0-RELEASE, the following <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> rule is
|
||||
interpreted in a different way from the previous releases:</p>
|
||||
|
||||
<pre class="PROGRAMLISTING">
|
||||
allow ipv6 from 192.168.0.2 to me
|
||||
</pre>
|
||||
|
||||
<p>When <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> does not
|
||||
support IPv6 (see the next entry for the details), <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> accepts
|
||||
this rule and this blocks an IPv6 packet encapsulated in an IPv4 packet (IPv6-over-IPv4
|
||||
tunneling, protocol number 41) whose source address is <tt
|
||||
class="LITERAL">192.168.0.2</tt>. When it supports IPv6, on the other hand, this means a
|
||||
rule to allow an IPv6 packet from <tt class="LITERAL">192.168.0.2</tt>, and actually <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> rejects
|
||||
this rule because the syntax is incorrect (“an IPv6 packet from an IPv4
|
||||
address” never happens). Unfortunately there is no simple workaround for this
|
||||
problem.</p>
|
||||
|
||||
<p>The <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> IPv6
|
||||
support still has rough edges and there are other problems due to incompatibility between
|
||||
the two. As a workaround for them, you can use a combination of IPv4-only <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> and <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ip6fw&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ip6fw</span>(8)</span></a>, which
|
||||
is almost compatible with the prior releases, instead of <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> with
|
||||
IPv6 support. To disable IPv6 support of <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a>, use the
|
||||
<tt class="FILENAME">ipfw.ko</tt> kernel module and do not use the kernel option <tt
|
||||
class="LITERAL">IPFIREWALL</tt>.</p>
|
||||
|
||||
<p>(2005/11/19) Although the FreeBSD 6.0-RELEASE Release Notes states that <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a>
|
||||
subsystem now supports IPv6, the combination of the <tt class="FILENAME">GENERIC</tt>
|
||||
kernel and a kernel module <tt class="FILENAME">ipfw.ko</tt> does not support the <tt
|
||||
class="LITERAL">ip6</tt> protocol keyword for packet filtering rule. This is because the
|
||||
kernel option <tt class="LITERAL">INET6</tt> in the kernel configuration file is not
|
||||
recognized when the <tt class="FILENAME">ipfw.ko</tt> is built. To enable IPv6 support of
|
||||
<a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a>, rebuild
|
||||
the kernel with kernel options <tt class="LITERAL">INET6</tt> and <tt
|
||||
class="LITERAL">IPFIREWALL</tt> instead of using the <tt class="FILENAME">ipfw.ko</tt>
|
||||
module.</p>
|
||||
|
||||
<p>(2005/11/16) Using <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=if_bridge&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">if_bridge</span>(4)</span></a> in
|
||||
combination with a packet filter such as <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> and <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=pf&sektion=4&manpath=FreeBSD+6.1-RELEASE"><span
|
||||
class="CITEREFENTRY"><span class="REFENTRYTITLE">pf</span>(4)</span></a> can prevent the
|
||||
network stack from working and/or lead to a system panic after a certain period of time.
|
||||
This is because it allocates <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=mbuf&sektion=9&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">mbuf</span>(9)</span></a> buffers
|
||||
for network packets and never releases a part of them, so eventually all of the buffer
|
||||
memory will be exhausted. This problem has been fixed in the HEAD and the RELENG_6 branch
|
||||
after 10:17:15 2005/11/16 UTC.</p>
|
||||
|
||||
<p>(2005/11/16, updated on 2005/11/19) When an <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt
|
||||
class="LITERAL">divert</tt> rule is specified with the protocol keyword <tt
|
||||
class="LITERAL">ip</tt> or <tt class="LITERAL">all</tt>, IPv6 packets are silently
|
||||
discarded at that rule since the <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=divert&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">divert</span>(4)</span></a> socket
|
||||
does not support IPv6. This can be a problem especially for an IPv4 and IPv6 dual-stack
|
||||
host with <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=natd&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">natd</span>(8)</span></a> enabled.
|
||||
<span class="bold"><b class="EMPHASIS">Note that the kernel module <tt
|
||||
class="FILENAME">ipfw.ko</tt> does not have this problem because it does not support
|
||||
IPv6.</b></span> To avoid this problem, use an IPv4 specific divert rule such as <tt
|
||||
class="LITERAL">divert natd ipv4</tt> instead of <tt class="LITERAL">divert natd
|
||||
all</tt>.</p>
|
||||
|
||||
<p>(2005/11/6) The FreeBSD 6.0-RELEASE Release Notes wrongly states a kernel option
|
||||
related to <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(8)</span></a> as <tt
|
||||
class="LITERAL">IPFIRWALL_FORWARD</tt>. The correct option keyword is <tt
|
||||
class="LITERAL">IPFIREWALL_FORWARD</tt>.</p>
|
||||
|
||||
<p>(2005/11/5) The FreeBSD 6.0-RELEASE Release Notes wrongly states the version number of
|
||||
OpenSSH and IPFilter integrated into FreeBSD as 4.1p1 and 4.1.18. The correct versions
|
||||
are 4.2p1 and 4.1.8 respectively.</p>
|
||||
|
||||
<p>(2005/11/5) Distribution of 6.0-RELEASE contains <tt
|
||||
class="FILENAME">CHECKSUM.MD5</tt> and <tt class="FILENAME">CHECKSUM.SHA256</tt> files
|
||||
for protecting the integrity of data. However, these files in 6.0-RELEASE erroneously
|
||||
include checksums for the checksum files themselves. Although the checksums look like
|
||||
wrong, they can be safely ignored because a checksum for the checksum file never
|
||||
corresponds to one in the file. This problem will be fixed in the next releases.</p>
|
||||
|
||||
<p>(2005/11/5, FreeBSD/amd64 specific) The <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=pmcstat&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">pmcstat</span>(8)</span></a>
|
||||
utility cannot yet handle 32-bit executables when converting <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=hwpmc&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">hwpmc</span>(4)</span></a> log
|
||||
files to <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=gprof&sektion=1&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">gprof</span>(1)</span></a>
|
||||
format.</p>
|
||||
|
||||
<p>(2005/11/5, FreeBSD/powerpc specific) The following panic may occur at boot-time on
|
||||
some older PowerMac G4 systems:</p>
|
||||
|
||||
<pre class="SCREEN">
|
||||
...
|
||||
KDB: current backend: ddb
|
||||
panic: Assertion curthread != NULL failed at
|
||||
/usr/src/sys/kern/kern_mutex.c:268
|
||||
KDB: enter panic
|
||||
</pre>
|
||||
|
||||
<p>This is a known problem with no workaround, and will be fixed in the next release.</p>
|
||||
|
||||
<p>(2005/11/5) Changes of on-disk format of <tt
|
||||
class="FILENAME">/usr/share/locale/*/LC_*</tt> files in 6.0-RELEASE prevent third-party
|
||||
software which uses <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=setlocale&sektion=3&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">setlocale</span>(3)</span></a> for
|
||||
its localization from working after a 5.x system upgraded. The software includes ones
|
||||
installed into the 5.x system by using FreeBSD Ports Collection and so on. To solve this
|
||||
problem, perform one of the following:</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Install misc/compat5x package into the upgraded 6.0 system. This package installs a
|
||||
library <tt class="FILENAME">lib/compat/libc.so.5</tt> which makes the software complied
|
||||
in a 5.x system use the old locale files to keep compatibility. Note that you need to
|
||||
remove <tt class="FILENAME">/lib/libc.so.5</tt> after upgrading.</p>
|
||||
|
||||
<p>This package is available only for Tier-1 platforms.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>Recompile the software on the 6.0 system.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>(2005/10/3) At boot time the FreeBSD/sparc64 GENERIC kernel may output the following
|
||||
messages when the machine has no framebuffer:</p>
|
||||
|
||||
<pre class="SCREEN">
|
||||
Aug 26 19:31:27 hostname getty[429]: open /dev/ttyv1: No such file or directory
|
||||
</pre>
|
||||
|
||||
<p>This is because the machine with no supported graphics hardware does not recognize <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">syscons</span>(4)</span></a> and
|
||||
<tt class="FILENAME">/dev/ttyv*</tt> device nodes are not created. This is not a harmful
|
||||
error and can be suppressed by disabling <tt class="FILENAME">/dev/ttyv*</tt> entries in
|
||||
<tt class="FILENAME">/etc/ttys</tt>.</p>
|
||||
|
||||
<p>(2005/10/3) Kernel modules do not work on FreeBSD/sparc64 when the machine has more
|
||||
than 4GB memory. There is no workaround for this issue except for compiling the modules
|
||||
statically into your custom kernel in advance.</p>
|
||||
|
||||
<p>(2005/10/3) The <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=kgdb&sektion=1&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">kgdb</span>(1)</span></a> utility
|
||||
does not work properly on FreeBSD/sparc64 for debugging panics which include traps. As a
|
||||
workaround you can use <tt class="FILENAME">devel/gdb53</tt>.</p>
|
||||
</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 <<a
|
||||
href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p>
|
||||
|
||||
<p align="center"><small>For questions about this documentation, e-mail <<a
|
||||
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p>
|
||||
</body>
|
||||
</html>
|
||||
|
5701
en/releases/6.1R/hardware-alpha.html
Normal file
5701
en/releases/6.1R/hardware-alpha.html
Normal file
File diff suppressed because it is too large
Load diff
5877
en/releases/6.1R/hardware-amd64.html
Normal file
5877
en/releases/6.1R/hardware-amd64.html
Normal file
File diff suppressed because it is too large
Load diff
7537
en/releases/6.1R/hardware-i386.html
Normal file
7537
en/releases/6.1R/hardware-i386.html
Normal file
File diff suppressed because it is too large
Load diff
2674
en/releases/6.1R/hardware-ia64.html
Normal file
2674
en/releases/6.1R/hardware-ia64.html
Normal file
File diff suppressed because it is too large
Load diff
5018
en/releases/6.1R/hardware-pc98.html
Normal file
5018
en/releases/6.1R/hardware-pc98.html
Normal file
File diff suppressed because it is too large
Load diff
2008
en/releases/6.1R/hardware-sparc64.html
Normal file
2008
en/releases/6.1R/hardware-sparc64.html
Normal file
File diff suppressed because it is too large
Load diff
1202
en/releases/6.1R/installation-alpha.html
Normal file
1202
en/releases/6.1R/installation-alpha.html
Normal file
File diff suppressed because it is too large
Load diff
1407
en/releases/6.1R/installation-amd64.html
Normal file
1407
en/releases/6.1R/installation-amd64.html
Normal file
File diff suppressed because it is too large
Load diff
1630
en/releases/6.1R/installation-i386.html
Normal file
1630
en/releases/6.1R/installation-i386.html
Normal file
File diff suppressed because it is too large
Load diff
902
en/releases/6.1R/installation-ia64.html
Normal file
902
en/releases/6.1R/installation-ia64.html
Normal file
|
@ -0,0 +1,902 @@
|
|||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml">
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org" />
|
||||
<title>FreeBSD/ia64 6.1-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/ia64 6.1-RELEASE Installation
|
||||
Instructions</a></h1>
|
||||
|
||||
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
|
||||
|
||||
<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD
|
||||
Documentation Project</p>
|
||||
|
||||
<hr />
|
||||
</div>
|
||||
|
||||
<blockquote class="ABSTRACT">
|
||||
<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a>
|
||||
<p>This article gives some brief instructions on installing FreeBSD/ia64 6.1-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.1-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="AEN38" name="AEN38">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="AEN213" name="AEN213">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="AEN252" name="AEN252">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.1-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 “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+6.1-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="AEN284" name="AEN284">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+6.1-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.1-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="AEN353" name="AEN353">1.5.4 Installing from QIC/SCSI
|
||||
Tape</a></h4>
|
||||
|
||||
<p>When installing from tape, the installation program expects the files to be simply
|
||||
tar'ed onto it, so after fetching all of the files for the distributions you're
|
||||
interested in, simply use <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+6.1-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 “probe” may otherwise fail to find it.</p>
|
||||
</blockquote>
|
||||
</div>
|
||||
|
||||
<p>Now create a boot floppy as described in <a href="#FLOPPIES">Section 1.3</a> and
|
||||
proceed with the installation.</p>
|
||||
</div>
|
||||
|
||||
<div class="SECT3">
|
||||
<hr />
|
||||
<h4 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 Installing over a Network using FTP
|
||||
or NFS</a></h4>
|
||||
|
||||
<p>After making the boot floppies as described in the first section, you can load the
|
||||
rest of the installation over a network using one of 3 types of connections: serial port,
|
||||
parallel port, or Ethernet.</p>
|
||||
|
||||
<div class="SECT4">
|
||||
<hr />
|
||||
<h5 class="SECT4"><a id="AEN378" name="AEN378">1.5.5.1 Serial Port</a></h5>
|
||||
|
||||
<p>SLIP support is rather primitive, and is limited primarily to hard-wired links, such
|
||||
as a serial cable running between two computers. The link must be hard-wired because the
|
||||
SLIP installation doesn't currently offer a dialing capability. If you need to dial out
|
||||
with a modem or otherwise dialog with the link before connecting to it, then 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="AEN384" name="AEN384">1.5.5.2 Parallel Port</a></h5>
|
||||
|
||||
<p>If a hard-wired connection to another FreeBSD or Linux machine is available, you might
|
||||
also consider installing over a “laplink” style parallel port cable. The data
|
||||
rate over the parallel port is much higher than what is typically possible over a serial
|
||||
line (up to 50k/sec), thus resulting in a quicker installation. It's not typically
|
||||
necessary to use “real” IP addresses when using a point-to-point parallel
|
||||
cable in this way and you can generally just use RFC 1918 style addresses for the ends of
|
||||
the link (e.g. <tt class="HOSTID">10.0.0.1</tt>, <tt class="HOSTID">10.0.0.2</tt>,
|
||||
etc).</p>
|
||||
|
||||
<div class="IMPORTANT">
|
||||
<blockquote class="IMPORTANT">
|
||||
<p><b>Important:</b> If you use a Linux machine rather than a FreeBSD machine as your
|
||||
PLIP peer, you will also have to specify <code class="OPTION">link0</code> in the TCP/IP
|
||||
setup screen's “extra options for ifconfig” field in order to be compatible
|
||||
with Linux's slightly different PLIP protocol.</p>
|
||||
</blockquote>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="SECT4">
|
||||
<hr />
|
||||
<h5 class="SECT4"><a id="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5>
|
||||
|
||||
<p>FreeBSD supports 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 <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="AEN406" name="AEN406">1.5.5.4 NFS installation tips</a></h5>
|
||||
|
||||
<p>NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution
|
||||
files you want onto a server somewhere and then point the NFS media selection at it.</p>
|
||||
|
||||
<p>If this server supports only “privileged port” access (this is generally
|
||||
the default for Sun and Linux workstations), you 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
|
||||
<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="AEN423" name="AEN423">1.5.5.5 FTP Installation tips</a></h5>
|
||||
|
||||
<p>FTP installation may be done from any mirror site containing a reasonably up-to-date
|
||||
version of FreeBSD. A full menu of reasonable choices for almost any location in the
|
||||
world is provided in the FTP site menu during installation.</p>
|
||||
|
||||
<p>If you are installing from some other FTP site not listed in this menu, or you are
|
||||
having troubles getting your name server configured properly, you can also specify your
|
||||
own URL by selecting the “URL” choice in that menu. A URL can contain a
|
||||
hostname or an IP address, so something like the following would work in the absence of a
|
||||
name server:</p>
|
||||
|
||||
<pre class="SCREEN">
|
||||
ftp://216.66.64.162/pub/FreeBSD/releases/ia64/4.2-RELEASE
|
||||
</pre>
|
||||
|
||||
<p>There are three FTP installation modes you can use:</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>FTP: This method uses the standard “Active” mode for transfers, in which
|
||||
the server initiates a connection to the client. This will not work through most
|
||||
firewalls but will often work best with older FTP servers that do not support passive
|
||||
mode. If your connection hangs with passive mode, try this one.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening
|
||||
connections to the client. This option is best for users to pass through firewalls that
|
||||
do not allow incoming connections on random port addresses.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy
|
||||
for all FTP operations. The proxy will translate the requests and send them to the FTP
|
||||
server. This allows the user to pass through firewalls that do not allow FTP at all, but
|
||||
offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP
|
||||
server.</p>
|
||||
|
||||
<p>In the rare case that you have an FTP proxy that does not go through HTTP, you can
|
||||
specify the URL as something like:</p>
|
||||
|
||||
<pre class="SCREEN">
|
||||
<kbd class="USERINPUT">ftp://foo.bar.com:<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>
|
||||
|
||||
<br />
|
||||
<br />
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="SECT2">
|
||||
<hr />
|
||||
<h3 class="SECT2"><a id="AEN474" name="AEN474">1.6 Question and Answer Section for IA-64
|
||||
Architecture Users</a></h3>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="SECT1">
|
||||
<hr />
|
||||
<h2 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 Distribution Format</a></h2>
|
||||
|
||||
<p>A typical FreeBSD distribution directory looks something like this (exact details may
|
||||
vary depending on version, architecture, and other factors):</p>
|
||||
|
||||
<pre class="SCREEN">
|
||||
ERRATA.HTM README.TXT compat1x dict kernel
|
||||
ERRATA.TXT RELNOTES.HTM compat20 doc manpages
|
||||
HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages
|
||||
HARDWARE.TXT base compat22 filename.txt ports
|
||||
INSTALL.HTM boot compat3x floppies proflibs
|
||||
INSTALL.TXT catpages compat4x games src
|
||||
README.HTM cdrom.inf crypto info tools
|
||||
</pre>
|
||||
|
||||
<p>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 “live filesystem” 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">/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+6.1-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+6.1-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.1-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.1-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.1-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.1-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.1-STABLE snapshots.</p>
|
||||
</blockquote>
|
||||
</div>
|
||||
|
||||
<div class="SECT2">
|
||||
<hr />
|
||||
<h3 class="SECT2"><a id="AEN702" name="AEN702">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="AEN706" name="AEN706">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="AEN780" name="AEN780">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="AEN783" name="AEN783">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="AEN786" name="AEN786">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="AEN791" name="AEN791">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="AEN801" name="AEN801">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 <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-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 “live filesystem” 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 “fixit” item
|
||||
from the main <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
|
||||
menu. Then select the “CDROM/DVD” 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.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
|
||||
menu. At that point, choose the “fixit” item from the main <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
|
||||
menu. Then select the “Floppy” 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="AEN845" name="AEN845">4.2 Common Installation Problems for IA-64
|
||||
Architecture Users</a></h3>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<hr />
|
||||
<p align="center"><small>This file, and other release-related documents, can be
|
||||
downloaded from <a
|
||||
href="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 <<a
|
||||
href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p>
|
||||
|
||||
<p align="center"><small>For questions about this documentation, e-mail <<a
|
||||
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p>
|
||||
</body>
|
||||
</html>
|
||||
|
1025
en/releases/6.1R/installation-pc98.html
Normal file
1025
en/releases/6.1R/installation-pc98.html
Normal file
File diff suppressed because it is too large
Load diff
957
en/releases/6.1R/installation-sparc64.html
Normal file
957
en/releases/6.1R/installation-sparc64.html
Normal file
|
@ -0,0 +1,957 @@
|
|||
<!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 6.1-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/sparc64 6.1-RELEASE Installation
|
||||
Instructions</a></h1>
|
||||
|
||||
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
|
||||
|
||||
<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD
|
||||
Documentation Project</p>
|
||||
|
||||
<hr />
|
||||
</div>
|
||||
|
||||
<blockquote class="ABSTRACT">
|
||||
<div class="ABSTRACT"><a id="AEN13" name="AEN13"></a>
|
||||
<p>This article gives some brief instructions on installing FreeBSD/sparc64 6.1-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.1-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="AEN38" name="AEN38">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>
|
||||
|
||||
<p>Floppy disk based install is not supported on FreeBSD/sparc64.</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>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+6.1-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+6.1-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="AEN213" name="AEN213">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="AEN252" name="AEN252">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.1-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 “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+6.1-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="AEN284" name="AEN284">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+6.1-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.1-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="AEN353" name="AEN353">1.5.4 Installing from QIC/SCSI
|
||||
Tape</a></h4>
|
||||
|
||||
<p>When installing from tape, the installation program expects the files to be simply
|
||||
tar'ed onto it, so after fetching all of the files for the distributions you're
|
||||
interested in, simply use <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+6.1-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 “probe” may otherwise fail to find it.</p>
|
||||
</blockquote>
|
||||
</div>
|
||||
|
||||
<p>Now create a boot floppy as described in <a href="#FLOPPIES">Section 1.3</a> and
|
||||
proceed with the installation.</p>
|
||||
</div>
|
||||
|
||||
<div class="SECT3">
|
||||
<hr />
|
||||
<h4 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 Installing over a Network using FTP
|
||||
or NFS</a></h4>
|
||||
|
||||
<p>After making the boot floppies as described in the first section, you can load the
|
||||
rest of the installation over a network using one of 3 types of connections: serial port,
|
||||
parallel port, or Ethernet.</p>
|
||||
|
||||
<div class="SECT4">
|
||||
<hr />
|
||||
<h5 class="SECT4"><a id="AEN378" name="AEN378">1.5.5.1 Serial Port</a></h5>
|
||||
|
||||
<p>SLIP support is rather primitive, and is limited primarily to hard-wired links, such
|
||||
as a serial cable running between two computers. The link must be hard-wired because the
|
||||
SLIP installation doesn't currently offer a dialing capability. If you need to dial out
|
||||
with a modem or otherwise dialog with the link before connecting to it, then 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="AEN384" name="AEN384">1.5.5.2 Parallel Port</a></h5>
|
||||
|
||||
<p>If a hard-wired connection to another FreeBSD or Linux machine is available, you might
|
||||
also consider installing over a “laplink” style parallel port cable. The data
|
||||
rate over the parallel port is much higher than what is typically possible over a serial
|
||||
line (up to 50k/sec), thus resulting in a quicker installation. It's not typically
|
||||
necessary to use “real” IP addresses when using a point-to-point parallel
|
||||
cable in this way and you can generally just use RFC 1918 style addresses for the ends of
|
||||
the link (e.g. <tt class="HOSTID">10.0.0.1</tt>, <tt class="HOSTID">10.0.0.2</tt>,
|
||||
etc).</p>
|
||||
|
||||
<div class="IMPORTANT">
|
||||
<blockquote class="IMPORTANT">
|
||||
<p><b>Important:</b> If you use a Linux machine rather than a FreeBSD machine as your
|
||||
PLIP peer, you will also have to specify <code class="OPTION">link0</code> in the TCP/IP
|
||||
setup screen's “extra options for ifconfig” field in order to be compatible
|
||||
with Linux's slightly different PLIP protocol.</p>
|
||||
</blockquote>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="SECT4">
|
||||
<hr />
|
||||
<h5 class="SECT4"><a id="AEN395" name="AEN395">1.5.5.3 Ethernet</a></h5>
|
||||
|
||||
<p>FreeBSD supports 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 <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="AEN406" name="AEN406">1.5.5.4 NFS installation tips</a></h5>
|
||||
|
||||
<p>NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution
|
||||
files you want onto a server somewhere and then point the NFS media selection at it.</p>
|
||||
|
||||
<p>If this server supports only “privileged port” access (this is generally
|
||||
the default for Sun and Linux workstations), you 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
|
||||
<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="AEN423" name="AEN423">1.5.5.5 FTP Installation tips</a></h5>
|
||||
|
||||
<p>FTP installation may be done from any mirror site containing a reasonably up-to-date
|
||||
version of FreeBSD. A full menu of reasonable choices for almost any location in the
|
||||
world is provided in the FTP site menu during installation.</p>
|
||||
|
||||
<p>If you are installing from some other FTP site not listed in this menu, or you are
|
||||
having troubles getting your name server configured properly, you can also specify your
|
||||
own URL by selecting the “URL” choice in that menu. A URL can contain a
|
||||
hostname or an IP address, so something like the following would work in the absence of a
|
||||
name server:</p>
|
||||
|
||||
<pre class="SCREEN">
|
||||
ftp://216.66.64.162/pub/FreeBSD/releases/sparc64/4.2-RELEASE
|
||||
</pre>
|
||||
|
||||
<p>There are three FTP installation modes you can use:</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>FTP: This method uses the standard “Active” mode for transfers, in which
|
||||
the server initiates a connection to the client. This will not work through most
|
||||
firewalls but will often work best with older FTP servers that do not support passive
|
||||
mode. If your connection hangs with passive mode, try this one.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>FTP Passive: This sets the FTP "Passive" mode which prevents the server from opening
|
||||
connections to the client. This option is best for users to pass through firewalls that
|
||||
do not allow incoming connections on random port addresses.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to connect to a proxy
|
||||
for all FTP operations. The proxy will translate the requests and send them to the FTP
|
||||
server. This allows the user to pass through firewalls that do not allow FTP at all, but
|
||||
offer an HTTP proxy. You must specify the hostname of the proxy in addition to the FTP
|
||||
server.</p>
|
||||
|
||||
<p>In the rare case that you have an FTP proxy that does not go through HTTP, you can
|
||||
specify the URL as something like:</p>
|
||||
|
||||
<pre class="SCREEN">
|
||||
<kbd class="USERINPUT">ftp://foo.bar.com:<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>
|
||||
|
||||
<br />
|
||||
<br />
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="SECT2">
|
||||
<hr />
|
||||
<h3 class="SECT2"><a id="AEN474" name="AEN474">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>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 “live filesystem” 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">/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+6.1-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+6.1-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.1-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.1-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.1-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.1-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.1-STABLE snapshots.</p>
|
||||
</blockquote>
|
||||
</div>
|
||||
|
||||
<div class="SECT2">
|
||||
<hr />
|
||||
<h3 class="SECT2"><a id="AEN702" name="AEN702">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="AEN706" name="AEN706">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="AEN780" name="AEN780">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="AEN783" name="AEN783">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="AEN786" name="AEN786">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="AEN791" name="AEN791">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="AEN801" name="AEN801">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 <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-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 “live filesystem” 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 “fixit” item
|
||||
from the main <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
|
||||
menu. Then select the “CDROM/DVD” 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.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
|
||||
menu. At that point, choose the “fixit” item from the main <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
|
||||
menu. Then select the “Floppy” 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="AEN845" name="AEN845">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="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 <<a
|
||||
href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p>
|
||||
|
||||
<p align="center"><small>For questions about this documentation, e-mail <<a
|
||||
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p>
|
||||
</body>
|
||||
</html>
|
||||
|
416
en/releases/6.1R/readme.html
Normal file
416
en/releases/6.1R/readme.html
Normal file
|
@ -0,0 +1,416 @@
|
|||
<!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 6.1-RELEASE README</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 6.1-RELEASE README</a></h1>
|
||||
|
||||
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
|
||||
|
||||
<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003, 2004, 2005 The FreeBSD
|
||||
Documentation Project</p>
|
||||
|
||||
<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/readme/article.sgml,v 1.37
|
||||
2005/04/19 09:43:53 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>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 “™” or the “®” symbol.</p>
|
||||
</div>
|
||||
|
||||
<hr />
|
||||
</div>
|
||||
|
||||
<blockquote class="ABSTRACT">
|
||||
<div class="ABSTRACT"><a id="AEN22" name="AEN22"></a>
|
||||
<p>This document gives a brief introduction to FreeBSD 6.1-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 snapshot of FreeBSD 6.1-RELEASE, the latest point along the
|
||||
6.1-STABLE branch.</p>
|
||||
|
||||
<div class="SECT2">
|
||||
<hr />
|
||||
<h3 class="SECT2"><a id="AEN27" name="AEN27">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>® machines (sparc64). Versions for the <span
|
||||
class="TRADEMARK">PowerPC</span>® (powerpc), and <span
|
||||
class="TRADEMARK">MIPS</span>® (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>® 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 13,300 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="AEN41" name="AEN41">1.2 Target Audience</a></h3>
|
||||
|
||||
<p>This snapshot 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="AEN47" name="AEN47">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="AEN54" name="AEN54">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"><<a
|
||||
href="mailto:freebsd-admin@FreeBSD.org">freebsd-admin@FreeBSD.org</a>></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="AEN68" name="AEN68">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 6.1-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="AEN86" name="AEN86">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+6.1-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+6.1-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+6.1-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 snapshot
|
||||
distribution. These files are provided in various formats. Most distributions will
|
||||
include both ASCII text (<tt class="FILENAME">.TXT</tt>) and HTML (<tt
|
||||
class="FILENAME">.HTM</tt>) renditions. Some distributions may also include other formats
|
||||
such as PostScript (<tt class="FILENAME">.PS</tt>) or Portable Document Format (<tt
|
||||
class="FILENAME">.PDF</tt>).</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p><tt class="FILENAME">README.TXT</tt>: This file, which gives some general information
|
||||
about FreeBSD as well as some cursory notes about obtaining a distribution.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p><tt class="FILENAME">RELNOTES.TXT</tt>: The release notes, showing what's new and
|
||||
different in FreeBSD 6.1-RELEASE compared to the previous release (FreeBSD
|
||||
6.0-RELEASE).</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p><tt class="FILENAME">HARDWARE.TXT</tt>: The hardware compatibility list, showing
|
||||
devices with which FreeBSD has been tested and is known to work.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p><tt class="FILENAME">INSTALL.TXT</tt>: Installation instructions for installing
|
||||
FreeBSD from its distribution media.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p><tt class="FILENAME">ERRATA.TXT</tt>: Release errata. Late-breaking, post-release
|
||||
information can be found in this file, which is principally applicable to releases (as
|
||||
opposed to snapshots). It is important to consult this file before installing a release
|
||||
of FreeBSD, as it contains the latest information on problems which have been found and
|
||||
fixed since the release was created.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="NOTE">
|
||||
<blockquote class="NOTE">
|
||||
<p><b>Note:</b> Several of these documents (in particular, <tt
|
||||
class="FILENAME">RELNOTES.TXT</tt>, <tt class="FILENAME">HARDWARE.TXT</tt>, and <tt
|
||||
class="FILENAME">INSTALL.TXT</tt>) contain information that is specific to a particular
|
||||
hardware architecture. For example, the alpha release notes contain information not
|
||||
applicable to the <span class="TRADEMARK">i386</span>™, and vice versa. The
|
||||
architecture for which each document applies will be listed in that document's title.</p>
|
||||
</blockquote>
|
||||
</div>
|
||||
|
||||
<br />
|
||||
<br />
|
||||
<p>On platforms that support <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-RELEASE">
|
||||
<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a>
|
||||
(currently alpha, <span class="TRADEMARK">i386</span>, ia64, pc98, and <span
|
||||
class="TRADEMARK">Sparc64</span>®), these documents are generally available via the
|
||||
Documentation menu during installation. Once the system is installed, you can revisit
|
||||
this menu by re-running the <a
|
||||
href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+6.1-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="AEN152" name="AEN152">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+6.1-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+6.1-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+6.1-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+6.1-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="AEN170" name="AEN170">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
|
||||
snapshot. For a complete list of FreeBSD developers and contributors, please see <a
|
||||
href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/"
|
||||
target="_top">“Contributors to FreeBSD”</a> on the FreeBSD Web site or any of
|
||||
its mirrors.</p>
|
||||
|
||||
<p>Special thanks also go to the many thousands of FreeBSD users and testers all over the
|
||||
world, without whom this snapshot simply would not have been possible.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<hr />
|
||||
<p align="center"><small>This file, and other release-related documents, can be
|
||||
downloaded from <a
|
||||
href="http://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 <<a
|
||||
href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p>
|
||||
|
||||
<p align="center"><small>For questions about this documentation, e-mail <<a
|
||||
href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p>
|
||||
</body>
|
||||
</html>
|
||||
|
1011
en/releases/6.1R/relnotes-alpha.html
Normal file
1011
en/releases/6.1R/relnotes-alpha.html
Normal file
File diff suppressed because it is too large
Load diff
1035
en/releases/6.1R/relnotes-amd64.html
Normal file
1035
en/releases/6.1R/relnotes-amd64.html
Normal file
File diff suppressed because it is too large
Load diff
1042
en/releases/6.1R/relnotes-i386.html
Normal file
1042
en/releases/6.1R/relnotes-i386.html
Normal file
File diff suppressed because it is too large
Load diff
1011
en/releases/6.1R/relnotes-ia64.html
Normal file
1011
en/releases/6.1R/relnotes-ia64.html
Normal file
File diff suppressed because it is too large
Load diff
1016
en/releases/6.1R/relnotes-pc98.html
Normal file
1016
en/releases/6.1R/relnotes-pc98.html
Normal file
File diff suppressed because it is too large
Load diff
1011
en/releases/6.1R/relnotes-sparc64.html
Normal file
1011
en/releases/6.1R/relnotes-sparc64.html
Normal file
File diff suppressed because it is too large
Load diff
Loading…
Reference in a new issue