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

Stage the HTML rendition of the 5.0-DP1 release documentation, to

Browse source 
allow for some testing before the actual announcement.

These documents were generated from the 5_dp1 Perforce branch,
with the exception of the sparc64-specific documents, which were
generated from HEAD in CVS.
This commit is contained in:
Bruce A. Mah 2002-04-05 22:30:14 +00:00
parent b63c95e63d
commit 2d5bbe99ac
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=12688
18 changed files with 32768 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
en/releases/5.0R/DP1/Makefile Normal file
View file

@ -0,0 +1,26 @@
# $FreeBSD: www/en/releases/4.5R/Makefile,v 1.6 2002/01/30 14:25:02 murray Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
.if exists(../Makefile.inc)
.include "../Makefile.inc"
.endif
DOCS= hardware.sgml relnotes.sgml installation.sgml
# DOCS+= announce.sgml contents.sgml
DATA= docbook.css
DATA+= errata.html
DATA+= hardware-alpha.html
DATA+= hardware-i386.html
DATA+= hardware-sparc64.html
DATA+= relnotes-alpha.html
DATA+= relnotes-i386.html
DATA+= relnotes-sparc64.html
DATA+= installation-alpha.html
DATA+= installation-i386.html
DATA+= installation-sparc64.html
# DATA+= cd1.txt cd2.txt cd3.txt cd4.txt
.include "${WEB_PREFIX}/share/mk/web.site.mk"

161
en/releases/5.0R/DP1/docbook.css Normal file
View file

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

335
en/releases/5.0R/DP1/errata.html Normal file
View file

@ -0,0 +1,335 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD 5.0-DP1 Errata</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.73 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">FreeBSD 5.0-DP1
Errata</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2002 by The FreeBSD
Documentation Project</p>
<p class="PUBDATE">$FreeBSD:
src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.9
2002/03/14 21:52:01 bmah Exp $<br>
</p>
<hr>
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT">
<a name="AEN9"></a>
<p>This document lists known issues for FreeBSD 5.0-DP1.
This information includes information relating to the
software or documentation that could affect its operation
or usability. Also included is a list of areas of the
base system that could benefit from some extra
testing.</p>
<p>Please note that FreeBSD 5.0-DP1 is not an officially
supported release of FreeBSD. Unlike supported releases,
this errata file will not be updated. Testers of FreeBSD
5.0-DP1 should subscribe to the FreeBSD-current mailing
list <tt class="EMAIL">&#60;<a href=
"mailto:freebsd-current@FreeBSD.org">freebsd-current@FreeBSD.org</a>&#62;</tt>
to stay informed about late-breaking issues and
developments.</p>
</div>
</blockquote>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN13">1 Known Problems</a></h1>
<ul>
<li>
<p>Serial GDB is broken.</p>
</li>
<li>
<p>LOMAC doesn't protect against a certain class of
inter-process activities such as signaling, since the
MAC hooks those checks rely on aren't in the base tree
yet.</p>
</li>
<li>
<p><tt class="COMMAND">gcc -O</tt> is known to be
broken.</p>
</li>
<li>
<p>There are two different PCCARD implementations,
OLDCARD and NEWCARD. NEWCARD has support for Cardbus,
but has PCCARD problems.</p>
</li>
<li>
<p>Kernels may have to be built with <tt class=
"LITERAL">-DNO_WERROR=yes</tt> due to warning handling
in the build infrastructure.</p>
</li>
<li>
<p>The system documentation indicates that there is
support for POSIX.1e capabilities, but the kernel
infrastructure is not merged; the documentation and
library may be removed before 5.0 depending on strategy
decisions not yet made.</p>
</li>
<li>
<p>NFS client locking does not interact well with <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">chroot</span>(2)</span></a>
environments; locking only works for processes sharing
the same root as the locking daemon.</p>
</li>
<li>
<p><b class="APPLICATION">Binutils</b> appears to have
some problems compiling software from the ports
collection (specifically, <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ld&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ld</span>(1)</span></a> is known to
have a problem with multiple references to some
symbols).</p>
</li>
</ul>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN41">2 Unfinished
Features</a></h1>
<p>A number of very significant changes to the system will
be made for FreeBSD 5.0-RELEASE. These features, and their
approximate status, are noted here.</p>
<ul>
<li>
<p>The lock-pushdown for fine-grained kernel threading
is in-process, and not complete in this snapshot. As a
result, the full benefits are not yet realized.</p>
</li>
<li>
<p>Scheduler activation support exists only in the
kernel, not in the userland thread library, and in this
snapshot, threads from the same process using KSE can
execute on only one processor at a time.</p>
</li>
<li>
<p>Mandatory access control support from the TrustedBSD
branch is not yet merged.</p>
</li>
<li>
<p>UFS2 (essentially, UFS with extended attributes in
inodes) is not yet ready for inclusion in the
snapshot.</p>
</li>
<li>
<p><b class="APPLICATION">XFree86</b> 4.2.0 is not yet
integrated into <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a>,
although this is planned to be finished for the next
developer preview.</p>
</li>
</ul>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN59">3 Known Pitfalls</a></h1>
<ul>
<li>
<p>FreeBSD 5.0-DP1 has a number of debugging features
enabled. These generally have a negative impact on
performance. One notable example is that the user-level
<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=malloc&sektion=3&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">malloc</span>(3)</span></a> functions
behave, by default, as though the <tt class=
"LITERAL">AJ</tt> debugging flags were set. Those
benchmarking the system should be sure to run without
debugging features enabled.</p>
</li>
<li>
<p>Interrupt latency is high due to on-going SMP work,
this will be fixed prior to the final release.</p>
</li>
<li>
<p>Tighter enforcement of <tt class=
"LITERAL">#include</tt> file deprecation results in a
number of common applications failing to build. In
particular, if you <tt class="LITERAL">#include
&lt;malloc.h&#62;</tt>, you now get a <tt class=
"LITERAL">#error</tt> instead of a <tt class=
"LITERAL">#warning</tt>.</p>
</li>
<li>
<p>The kernel is no longer installed as <tt class=
"FILENAME">/kernel</tt> and <tt class=
"FILENAME">/modules</tt>, these have moved to <tt
class="FILENAME">/boot/kernel</tt>.</p>
</li>
<li>
<p>When upgrading a system, make sure to pay attention
to the change from an <tt class=
"FILENAME">/etc/pam.conf</tt> configure file to
multiple files in <tt class=
"FILENAME">/etc/pam.d/</tt>. Likewise, <b class=
"APPLICATION">OpenPAM</b> has replaced <b class=
"APPLICATION">LinuxPAM</b>, and new PAM modules have
been introduced; this may result in warnings from older
authentication-related applications compiled under <tt
class="LITERAL">RELENG_4</tt>, such as <b class=
"APPLICATION">xdm</b>, <b class="APPLICATION">kdm</b>,
and <b class="APPLICATION">gdm</b>.</p>
</li>
<li>
<p>The <b class="APPLICATION">sendmail</b> startup code
in <tt class="FILENAME">/etc/rc</tt> has been changed
to support the new requirements of <b class=
"APPLICATION">sendmail</b> 8.12. The new setup may
cause problems for users running MTAs other than <b
class="APPLICATION">sendmail</b>. You can prevent any
<b class="APPLICATION">sendmail</b> daemons from
starting at boot time by adding the following to <tt
class="FILENAME">/etc/rc.conf</tt>:</p>
<pre class="PROGRAMLISTING">
sendmail_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"
sendmail_submit_enable="NO"
</pre>
<p>Note that 5.0-DP2 (as well as 5.0-RELEASE) will
support a <tt class=
"LITERAL">sendmail_enable="NONE"</tt> setting to
disable all <b class="APPLICATION">sendmail</b> daemons
with a single variable. This functionality was <span
class="emphasis"><i class="EMPHASIS">not</i></span>
merged to the 5.0-DP1 snapshot.</p>
</li>
</ul>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN104">4 Testing Guide</a></h1>
<p>While testing reports of all aspects of FreeBSD 5.0-DP1
are welcomed, there are several areas which could benefit
from some extra testing:</p>
<ul>
<li>
<p>Basic kernel functionality. The changes for SMPng
are still in progress, and have some far-reaching
effects throughout many parts of the kernel. Testing
the kernel's stability on both UP and SMP machines will
help find any regressions that may have come about.</p>
</li>
<li>
<p>The PAM infrastructure has undergone significant
changes, including a replacement of <b class=
"APPLICATION">Linux PAM</b> with <b class=
"APPLICATION">OpenPAM</b>.</p>
</li>
<li>
<p>FFS snapshots and background <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=fsck&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fsck</span>(8)</span></a>. The latter
feature is enabled by default; a reasonable test for
snapshots is to do backups by creating a snapshot using
the instructions in <tt class=
"FILENAME">src/sys/ufs/ffs/README.snapshot</tt> and
performing a <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dump</span>(8)</span></a> of the
snapshot.</p>
</li>
<li>
<p>Because of API changes, a number of ports in the
FreeBSD Ports Collection are broken under FreeBSD
5-CURRENT. Frequently, there are straightforward fixes
for these ports; submitting these fixes will improve
the state of buildable ports and packages that can be
shipped with FreeBSD 5.0-RELEASE.</p>
</li>
<li>
<p>NFS has undergone some significant code
reorganization, although it is believed to be fairly
stable. NFS client locking is a new feature.</p>
</li>
<li>
<p>The sparc64 platform support is new, and could use
testing on a wider variety of hardware.</p>
</li>
</ul>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"ftp://current.FreeBSD.org/pub/FreeBSD/">ftp://current.FreeBSD.org/pub/FreeBSD/</a>.</small></p>
<p align="center"><small>For questions about FreeBSD, read the
<a href="http://www.FreeBSD.org/docs.html">documentation</a>
before contacting &#60;<a href=
"mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small><small>All users of FreeBSD 5-CURRENT
should subscribe to the &#60;<a href=
"mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62;
mailing list.</small></small></p>
<p align="center">For questions about this documentation,
e-mail &#60;<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
<br>
<br>
</body>
</html>

5918
en/releases/5.0R/DP1/hardware-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

3922
en/releases/5.0R/DP1/hardware-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

783
en/releases/5.0R/DP1/hardware-sparc64.html Normal file
View file

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

27
en/releases/5.0R/DP1/hardware.sgml Normal file
View file

@ -0,0 +1,27 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY title "FreeBSD 5.0-DP1 Hardware Notes">
<!ENTITY % includes SYSTEM "../../../includes.sgml"> %includes;
]>
<html>
&header;
<p>The hardware notes for FreeBSD are customized for different
platforms, as some of the changes made to FreeBSD apply only to
specific processor architectures.</p>
<p>Hardware notes for FreeBSD 5.0-DP1 are available for the following
platforms:</p>
<ul>
<li><a href="hardware-i386.html">i386</a></li>
<li><a href="hardware-alpha.html">alpha</a></li>
<li><a href="hardware-sparc64.html">sparc64</a></li>
</ul>
<p>A list of all platforms currently under development can be found
on the <a href="../../../platforms/index.html">Supported
Platforms</a> page.</p>
</html>

2269
en/releases/5.0R/DP1/installation-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

2287
en/releases/5.0R/DP1/installation-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

846
en/releases/5.0R/DP1/installation-sparc64.html Normal file
View file

@ -0,0 +1,846 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD/sparc64 5.0-CURRENT Installation
Instructions</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.73 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">FreeBSD/sparc64
5.0-CURRENT Installation Instructions</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright &copy; 2000, 2001, 2002 by
The FreeBSD Documentation Project</p>
<hr>
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT">
<a name="AEN10"></a>
<p>This article gives some brief instructions on
installing FreeBSD/sparc64 5.0-CURRENT. Please keep in
mind that this port is a work in progress, and as such,
the installation procedure is much more involved than for
FreeBSD/i386 or FreeBSD/alpha.</p>
</div>
</blockquote>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN12">1 Installing
FreeBSD</a></h1>
<p>This text describes how to install and boot the sparc64
port. Users of this port are encouraged to subscribe to the
FreeBSD SPARC porting mailing list <tt class=
"EMAIL">&#60;<a href=
"mailto:freebsd-sparc@FreeBSD.org">freebsd-sparc@FreeBSD.org</a>&#62;</tt>.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> The kernel and userland binaries
mentioned below are highly experimental (for example,
the kernel contains some ATA changes and EEPROM
handling code which could potentially be dangerous).
Unless you know what you are doing and are willing to
cope with any damage that might arise, you should
probably not be trying this.</p>
</blockquote>
</div>
<p>Unlike FreeBSD/i386 or FreeBSD/alpha, there is no
version of <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a> for
FreeBSD/sparc64. The installation procedure consists of
loading a kernel (either from CDROM or the network) onto
the sparc64 machine, with a root filesystem on CDROM or
exported via NFS. The utilities on the root filesystem can
then be used to partition the local disk on the sparc64
machine and optionally to copy the FreeBSD distribution to
the local disk to make a stand-alone machine.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN22">1.1
Preparation</a></h2>
<p>Currently, there are two ways to install
FreeBSD/sparc64 on a new machine. By far the easier of
the two is to install from CDROM; this method allows you
to install FreeBSD without any dependencies on any other
computers.</p>
<p>If installing from CDROM is impossible or undesirable,
the alternative is to install over the network. This
requires another machine, suitably configured, to serve
the boot loader, kernel, and root file system to the new
machine, via a combination of RARP, TFTP, and either
BOOTP or DHCP. This netboot server can be another FreeBSD
machine, but is not required to be.</p>
<p>You will need to decide which of these methods you
want to use for installation, as this will determine the
set of files you need to download (if any), as well as
the steps required to do the installation.</p>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="DOWNLOADING">1.1.1
Downloading Required Files</a></h3>
<p>This section describes the files you will need for a
FreeBSD/sparc64 installation. The links in this
document point to the main FreeBSD FTP server. Please
use a mirror site instead if possible.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> The URLs in this section are
provisional and subject to change. Please see the
archives of the FreeBSD SPARC porting mailing list
<tt class="EMAIL">&#60;<a href=
"mailto:freebsd-sparc@FreeBSD.org">freebsd-sparc@FreeBSD.org</a>&#62;</tt>
for the most recent locations of files. This notice
will be removed when more permanent URLs have been
determined.</p>
</blockquote>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN33">1.1.1.1 Required
Files for CDROM Installation</a></h4>
<p>If you want to do a CDROM installation, an ISO
image with a snapshot of FreeBSD/sparc64 can be found
at <a href=
"ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/"
target=
"_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/</a>.
This file can be used to create a bootable CDROM
which contains everything necessary to boot and load
at least a minimal FreeBSD installation.</p>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN37">1.1.1.2 Required
Files for Network Installation</a></h4>
<p>For a network installation, you will need several
files. First, you will need to download a
FreeBSD/sparc64 loader for <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tftpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tftpd</span>(8)</span></a> to serve
to your sparc64 client. The loader will use either
TFTP or NFS to retrieve the FreeBSD kernel from the
netboot server. There is a separate loader for each
of these methods (i.e. a loader for TFTP and a loader
for NFS). You should download one of the following
files, as appropriate:</p>
<ul>
<li>
<p><a href=
"ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-tftp.gz"
target=
"_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-tftp.gz</a></p>
</li>
<li>
<p><a href=
"ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-nfs.gz"
target=
"_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-nfs.gz</a></p>
</li>
</ul>
<p>A network installation also requires a kernel to
be served to the netboot client. A suitable kernel
can be found at <a href=
"ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/"
target=
"_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/</a>.</p>
<p>Finally, you will need a <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tar</span>(1)</span></a> archive
which contains the binaries and configuration files
from the base system. This file is available from <a
href=
"ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/distrib.tar.gz"
target=
"_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/distrib.tar.gz</a>.</p>
</div>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name=
"GETTING-TO-PROM-PROMPT">1.1.2 Getting to the PROM
Prompt</a></h3>
<p>Most sparc64 systems are set up to boot
automatically from disk. To install FreeBSD, you need
to boot over the network or from a CDROM, which
requires you to break into the PROM (OpenFirmware).</p>
<p>To do this, reboot the system, and wait until the
boot message appears. It depends on the model, but
should look about like:</p>
<pre class="SCREEN">
Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.
</pre>
<p>If your system proceeds to boot from disk at this
point, you need to press <b class="KEYCAP">L1</b>+<b
class="KEYCAP">A</b> or <b class="KEYCAP">Stop</b>+<b
class="KEYCAP">A</b> on the keyboard, or send a <tt
class="COMMAND">BREAK</tt> over the serial console
(using for example <tt class="COMMAND">~#</tt> in <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tip&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tip</span>(1)</span></a> or <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=cu&sektion=1&manpath=FreeBSD+5.0-current">
<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">
<tt class="PROMPT">ok </tt> <a name=
"PROMPT-SINGLE"><b>(1)</b></a>
<tt class="PROMPT">ok {0}</tt> <a 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>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN89">1.2 Installing from
CDROM</a></h2>
<p>Place the CDROM into your drive, and break into the
PROM as described above. On the PROM prompt, type <tt
class="COMMAND">boot cdrom</tt>. The system should boot
into single-user mode now, and you can create the disk
label and install the base system archive as described in
<a href="#CREATING-DISK-LABEL">Section 1.4</a> and <a
href="#CREATING-ROOT-FILESYSTEM">Section 1.5</a>.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN95">1.3 Installing over the
Network</a></h2>
<div class="SECT3">
<h3 class="SECT3"><a name="AEN97">1.3.1 Configuring the
Netboot Server</a></h3>
<p>A FreeBSD/sparc64 kernel is booted by having the
firmware retrieve and execute a <b class=
"APPLICATION">loader</b>, which in turn fetches and
executes the actual kernel. For this boot process, you
need to set up <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=rarpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">rarpd</span>(8)</span></a> and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tftpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tftpd</span>(8)</span></a> (for the
firmware) and <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bootpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bootpd</span>(8)</span></a> (for the <b
class="APPLICATION">loader</b>) on another networked
system. The loader can fetch a kernel using TFTP or
NFS. All of this is covered in detail below.</p>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN111">1.3.1.1
rarpd</a></h4>
<p>You need to add the Ethernet address of your
FreeBSD/sparc64 system to <tt class=
"FILENAME">/etc/ethers</tt> on the netboot server. An
entry looks like:</p>
<pre class="PROGRAMLISTING">
0:3:ba:b:92:d4 your.host.name
</pre>
<p>The Ethernet address is usually displayed in the
boot message.</p>
<p>Make sure <tt class="HOSTID">your.host.name</tt>
is in <tt class="FILENAME">/etc/hosts</tt> or has a
valid DNS entry (or use an IP address). Then, start
<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=rarpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">rarpd</span>(8)</span></a> on a
network interface that is on the same subnet as the
FreeBSD/sparc64 system.</p>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN123">1.3.1.2
tftpd</a></h4>
<p>Activate <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tftpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tftpd</span>(8)</span></a> in your <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=inetd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">inetd</span>(8)</span></a>
configuration by uncommenting the following line in
<tt class="FILENAME">/etc/inetd.conf</tt>:</p>
<pre class="PROGRAMLISTING">
tftp dgram udp wait nobody /usr/libexec/tftpd tftpd /tftpboot
</pre>
<p>Copy the unpacked loader to your <tt class=
"FILENAME">/tftpboot</tt> directory, and name it with
the FreeBSD/sparc64 host's IP address in upper-case
hexadecimal notation without dots (or use
appropriately-named symbolic links). For example,
your setup may look like this, for an IP address of
<tt class="HOSTID">192.168.0.16</tt>:</p>
<pre class="SCREEN">
lrwx------ 1 tmm users 9 Jul 24 17:05 /tftpboot/C0A80010 -&#62; boot/loader
-rw-r--r-- 1 tmm users 1643021 Oct 20 18:04 /tftpboot/boot/loader
</pre>
<p>If you have trouble booting, it is very helpful to
use <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tcpdump&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tcpdump</span>(1)</span></a> to
monitor the TFTP requests. This will allow you to see
the file name you need to use for the loader. Error
replies by the TFTP server are most often due to
incorrect file permissions.</p>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN142">1.3.1.3 Setting up
bootpd/dhcpd</a></h4>
<p>You can use either BOOTP or DHCP (both not both)
to provide some parameters to the boot loader, such
as a machine's IP address. If you are using another
FreeBSD machine as a netboot server, the BOOTP
functionality is provided by <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bootpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bootpd</span>(8)</span></a>, which is
a part of the FreeBSD base system. Several DHCP
servers are provided in the FreeBSD Ports
Collection.</p>
<p>If you are going to use <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bootpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bootpd</span>(8)</span></a>, create
entries for your FreeBSD/sparc64 system in the
server's <tt class="FILENAME">/etc/bootptab</tt> (see
<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=bootptab&sektion=5&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">bootptab</span>(5)</span></a> for
more details):</p>
<pre class="PROGRAMLISTING">
.default:\
:bf="kernel":dn=local:ds=<tt class=
"REPLACEABLE"><i>name-server-ip-address</i></tt>:\
:gw=<tt class=
"REPLACEABLE"><i>gateway-ip-address</i></tt>:ht=ether:hd="/tftpboot/boot/kernel":hn:\
:sa="<tt class=
"REPLACEABLE"><i>tftp-server-ip-address</i></tt>":\
:rp="<tt class=
"REPLACEABLE"><i>tftp-server-ip-address</i></tt>:<tt class=
"REPLACEABLE"><i>nfs-root-directory</i></tt>":\
:sm=<tt class="REPLACEABLE"><i>ip-netmask</i></tt>
<tt class="REPLACEABLE"><i>name-of-the-entry</i></tt>:\
ha=<tt class=
"REPLACEABLE"><i>sparc64-ethernet-address</i></tt>:ip=<tt class=
"REPLACEABLE"><i>sparc64-ip-address</i></tt>:tc=.default
</pre>
<p>The Ethernet address must be the same as the one
in the TFTP example above, but it is specified
hexadecimal notation without colons (for the example
above, this would be <tt class=
"LITERAL">0003ba0b92d4</tt>). NFS/TFTP specific
entries can be omitted if the given method is not
used. The strings given in the <tt class=
"LITERAL">hd</tt> and <tt class="LITERAL">bf</tt>
properties are concatenated to give the boot file
name. If your kernel is named differently or you use
another directory, change these values as required.
If you are booting using NFS, remove the <tt class=
"LITERAL">bf</tt> and <tt class="LITERAL">hd</tt>
settings (or change them to specify the directory and
file inside the NFS root hierarchy in which the
kernel will reside). The name of the host entry is
conventionally the host name without the domain
appended.</p>
<p>For a DHCP server, add an entry similar to the
following to your <tt class=
"FILENAME">dhcpd.conf</tt> file. An example entry for
<b class="APPLICATION">ISC DHCP</b> version 2
(available in the FreeBSD Ports Collection as <a
href=
"http://www.FreeBSD.org/cgi/url.cgi?ports/net/isc-dhcp2/pkg-descr">
<tt class="FILENAME">net/isc-dhcp2</tt></a>) is shown
below:</p>
<pre class="PROGRAMLISTING">
host <tt class="REPLACEABLE"><i>name-of-entry</i></tt> {
hardware ethernet <tt class=
"REPLACEABLE"><i>sparc64-ethernet-address</i></tt>;
option host-name "<tt class=
"REPLACEABLE"><i>sparc64-fully-qualified-domain-name</i></tt>";
fixed-address <tt class=
"REPLACEABLE"><i>sparc64-ip-address</i></tt>;
always-reply-rfc1048 on;
filename "kernel";
option root-path "<tt class=
"REPLACEABLE"><i>tftp-server-ip-address</i></tt>:<tt class=
"REPLACEABLE"><i>nfs-root-directory</i></tt>";
}
</pre>
<p>The <tt class="LITERAL">filename</tt> option
corresponds to the concatenation of <tt class=
"LITERAL">hd</tt> and <tt class="LITERAL">bf</tt> in
<tt class="FILENAME">/etc/bootptab</tt>. The Ethernet
address is specified in hexadecimal with colons, just
like in the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=rarpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">rarpd</span>(8)</span></a> example
above. <tt class="LITERAL">options root-path</tt>
corresponds to <tt class="LITERAL">rp</tt> in <tt
class="FILENAME">/etc/bootptab</tt>. If the name
given in <tt class="LITERAL">option host-name</tt> is
resolvable, i.e. has a DNS entry or is associated
with an address in <tt class=
"FILENAME">/etc/hosts</tt>, the <tt class=
"LITERAL">fixed-address</tt> specification can be
omitted.</p>
</div>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN197">1.3.2 Loading the
Kernel</a></h3>
<p>With the daemons on the netboot server configured,
the next step is to copy the kernel (obtained during
the steps of <a href="#DOWNLOADING">Section 1.1.1</a>)
to an appropriate directory. There are two ways of
retrieving a kernel over the network: TFTP and NFS.
(You specified one of these two alternatives by picking
a loader.)</p>
<p>For both TFTP and NFS, the loader will use the
parameters that it obtained via BOOTP or DHCP to find
the kernel.</p>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN202">1.3.2.1 Loading
the Kernel over TFTP</a></h4>
<p>Place the kernel in the directory you specified
using <tt class="LITERAL">bf</tt> and <tt class=
"LITERAL">hd</tt> in the <tt class=
"FILENAME">/etc/bootptab</tt> or the <tt class=
"LITERAL">filename</tt> parameter to <tt class=
"FILENAME">dhcpd.conf</tt>.</p>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN210">1.3.2.2 Loading
the Kernel over NFS</a></h4>
<p>Export the directory that was specified by the <tt
class="LITERAL">rp</tt> property in <tt class=
"FILENAME">/etc/bootptab</tt> or the <tt class=
"LITERAL">root-path</tt> parameter in <tt class=
"FILENAME">dhcpd.conf</tt> (see <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=exports&sektion=5&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">exports</span>(5)</span></a>). Copy
the kernel to the directory you specified using <tt
class="LITERAL">bf</tt> and <tt class=
"LITERAL">hd</tt> in the <tt class=
"FILENAME">/etc/bootptab</tt> or the <tt class=
"LITERAL">filename</tt> parameter to <tt class=
"FILENAME">dhcpd.conf</tt>.</p>
</div>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN225">1.3.3 Loading the
Base System to the Netboot Server</a></h3>
<p>You must extract the base system distribution image
to the NFS root directory specified either by the <tt
class="LITERAL">rp</tt> option in <tt class=
"FILENAME">/etc/bootptab</tt> or the <tt class=
"LITERAL">root-path</tt> option in <tt class=
"FILENAME">dhcpd.conf</tt>. This directory tree will
become the sparc64's root filesystem once the kernel is
booted. Besides providing a normal userland
environment, it also contains all of the necessary
utilities for you to install the distribution on the
sparc64 client's local disk.</p>
<p>Using whatever editing tools you have on the netboot
server, you probably will want to edit the sparc64's
<tt class="FILENAME">/etc/fstab</tt> and <tt class=
"FILENAME">/etc/rc.conf</tt> and set a <tt class=
"USERNAME">root</tt> password.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN236">1.3.4
Booting</a></h3>
<p>If all goes well, you can now boot the FreeBSD on
your sparc64 machine by dropping into the PROM prompt
as described in <a href=
"#GETTING-TO-PROM-PROMPT">Section 1.1.2</a>. Now, just
type <tt class="COMMAND">boot net</tt> and the system
should boot. Specifically, the loader is retrieved via
TFTP, it then does a BOOTP request and will proceed to
load the kernel (either using TFTP or NFS, depending on
your choice of loader). Then, it should wait 10 seconds
for user input and proceed to execute the kernel.</p>
<p>If something does not work in between, and you
suspect TFTP/NFS/BOOTP problems, <b class=
"APPLICATION">Ethereal</b> (available in the FreeBSD
Ports Collection as <a href=
"http://www.FreeBSD.org/cgi/url.cgi?ports/ net/ethereal/pkg-descr">
<tt class="FILENAME">net/ethereal</tt></a>) is usually
helpful. The most common problems are related to bad
file permissions. Also note that <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=rarpd&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">rarpd</span>(8)</span></a> will not
answer to packets under some circumstances, refer to
the manual page for details.</p>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="CREATING-DISK-LABEL">1.4
Creating a Disk Label</a></h2>
<p>The kernel supports the Sun disk label format, so you
can label the disks you want to use with FreeBSD from
Solaris.</p>
<p>FreeBSD disk labels must currently be created by hand,
as <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a> is not
yet available on FreeBSD/sparc64. Please refer to the <a
href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
target="_top">FreeBSD Handbook</a> for more information
about labels and special partitions.</p>
<p>On FreeBSD/sparc64, a Sun compatibility label is
embedded in the FreeBSD label; this is needed for the
PROM to boot from disk. This imposes an additional
restriction on the disk label format: partitions are
required to start on a cylinder boundary.</p>
<p>To create a disk label, the following procedure is the
easiest:</p>
<div class="PROCEDURE">
<ol type="1">
<li>
<p>Run <tt class="COMMAND">disklabel -w -r <tt
class="REPLACEABLE"><i>device</i></tt> auto</tt> to
create a basic disk label. The third argument you
need specify here is just the name of the device,
not the complete path to the device node (e.g. <tt
class="DEVICENAME">ad0</tt> for the first ATA
disk).</p>
</li>
<li>
<p>Use <tt class="COMMAND">disklabel -e <tt class=
"REPLACEABLE"><i>device</i></tt></tt> to open an
editor in which you can edit the disk label. The
information presented to you should look like:</p>
<pre class="SCREEN">
# /dev/ad6c:
type: unknown
disk: amnesiac
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 79780
sectors/unit: 80418240
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 80418240 0 unused 0 0 # (Cyl. 0 - 79779)
</pre>
<p>You can now add new partitions in the same
format as the already present line. Using <tt
class="LITERAL">*</tt> in the offset field makes
the procedure easier; please refer to the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">disklabel</span>(8)</span></a>
manual page for more information.</p>
<p>To make sure the restriction mentioned above is
met, the size of each partition must be a multiple
of the number of sectors per cylinder as shown in
the information that is presented in the editor
(1008 in the example above).</p>
<p>When you are done, save your changes and quit
the editor. This will cause the disk label to be
written.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> This procedure will
overwrite any disk label that may be already
present on the disk. Any existing filesystems
on this disk must have their respective
partition entries in the old and new label
match <span class="emphasis"><i class=
"EMPHASIS">exactly</i></span>, or they will be
lost.</p>
</blockquote>
</div>
</li>
<li>
<p>Use <tt class="COMMAND">disklabel -B</tt> if you
want to make the disk bootable for
FreeBSD/sparc64.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> Using <tt class=
"COMMAND">disklabel -B</tt> on a disk will
overwrite any preexisting boot block, so it
will likely render any other operating system
installed on the same disk unbootable.</p>
</blockquote>
</div>
<p>If you do not want to overwrite the boot block,
it is possible to load the <b class=
"APPLICATION">loader</b> via TFTP as described
above, but have it boot the kernel from disk. This
requires a special loader binary, which is
available at <a href=
"ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-ufs.gz"
target=
"_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-ufs.gz</a></p>
</li>
</ol>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="CREATING-ROOT-FILESYSTEM">1.5
Creating the Root Fileystem</a></h2>
<p>If you want to boot from a local disk, you will need
to create a root file system to hold the base system
binaries and configuration files (and optionally other
file systems mounted in places such as <tt class=
"FILENAME">/usr</tt> and <tt class=
"FILENAME">/var</tt>).</p>
<p>The kernel contains support for Sun disklabels, so you
can use Solaris disks, which may even be prepared using
<b class="APPLICATION">newfs</b> under Solaris. NetBSD
disk labels and file systems are also usable from
FreeBSD.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> Do <span class="emphasis"><i
class="EMPHASIS">not</i></span> run Solaris <b class=
"APPLICATION">fsck</b> on file systems modified by
FreeBSD. Doing so will damage the file
permissions.</p>
</blockquote>
</div>
<p>To create file systems and to install the base system,
boot from CDROM or via NFS and create a disk label as
described in <a href="#CREATING-DISK-LABEL">Section
1.4</a>.</p>
<p>When booting the first time and you have not entered
your root partition into <tt class=
"FILENAME">/etc/fstab</tt> yet, you may need to specify
your root partition on the mountroot prompt when booting
(use a format like <tt class="COMMAND">ufs:<tt class=
"REPLACEABLE"><i>disk</i></tt><tt class=
"REPLACEABLE"><i>partition</i></tt></tt>, i.e. leave the
slice specification out). If the kernel does
automatically attempt to boot from another file system,
press a key other than <b class="KEYCAP">Enter</b> on the
<b class="APPLICATION">loader</b> prompt:</p>
<pre class="SCREEN">
Hit [Enter] to boot immediately, or any other key for command prompt.
</pre>
<p>Then, boot the kernel using <tt class="COMMAND">boot
-a -s</tt>, which will cause the kernel to ask you for
the root partition and then boot into single-user mode.
Once the root file system has been entered into <tt
class="FILENAME">/etc/fstab</tt>, it should be
automatically mounted as <tt class="FILENAME">/</tt> on
the next boot.</p>
<p>If you are booting over the network (via NFS), the
above BOOTP entries should suffice to have the kernel
find and mount the root filesystem via NFS.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="INSTALLING-BASE-SYSTEM">1.6
Installing the Base System</a></h2>
<p>If you booted the kernel from the network, you
downloaded a <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tar</span>(1)</span></a> archive with the
base system and exported it from the netboot server via
NFS. You can unpack this same archive to your local disk
to create a stand-alone system (remember to copy the
kernel over as well).</p>
<p>If you booted from CDROM, the same archive is
available in <tt class="FILENAME">/root/</tt> on the
CDROM.</p>
<p>Before booting the system stand-alone, you will want
to edit <tt class="FILENAME">/etc/fstab</tt> and <tt
class="FILENAME">/etc/rc.conf</tt> and set a <tt class=
"USERNAME">root</tt> password.</p>
<p>Note that some programs from the base system may not
be present in the archive, or may not work properly
yet.</p>
</div>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/</a>.</small></p>
<p align="center"><small>For questions about FreeBSD, read the
<a href="http://www.FreeBSD.org/docs.html">documentation</a>
before contacting &#60;<a href=
"mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>&#62;.</small></p>
<p align="center"><small><small>All users of FreeBSD 5-CURRENT
should subscribe to the &#60;<a href=
"mailto:current@FreeBSD.org">current@FreeBSD.org</a>&#62;
mailing list.</small></small></p>
<p align="center">For questions about this documentation,
e-mail &#60;<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&#62;.</p>
<br>
<br>
</body>
</html>

27
en/releases/5.0R/DP1/installation.sgml Normal file
View file

@ -0,0 +1,27 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY title "FreeBSD 5.0-DP1 Installation Notes">
<!ENTITY % includes SYSTEM "../../../includes.sgml"> %includes;
]>
<html>
&header;
<p>The installation notes for FreeBSD are customized for different
platforms, as some of the changes made to FreeBSD apply only to
specific processor architectures.</p>
<p>Installation notes for FreeBSD 5.0-DP1 are available for the following
platforms:</p>
<ul>
<li><a href="installation-i386.html">i386</a></li>
<li><a href="installation-alpha.html">alpha</a></li>
<li><a href="installation-sparc64.html">sparc64</a></li>
</ul>
<p>A list of all platforms currently under development can be found
on the <a href="../../../platforms/index.html">Supported
Platforms</a> page.</p>
</html>

542
en/releases/5.0R/DP1/readme.html Normal file
View file

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

5039
en/releases/5.0R/DP1/relnotes-alpha.html Normal file
View file

File diff suppressed because it is too large Load diff

5441
en/releases/5.0R/DP1/relnotes-i386.html Normal file
View file

File diff suppressed because it is too large Load diff

5111
en/releases/5.0R/DP1/relnotes-sparc64.html Normal file
View file

File diff suppressed because it is too large Load diff

27
en/releases/5.0R/DP1/relnotes.sgml Normal file
View file

@ -0,0 +1,27 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY title "FreeBSD 5.0-DP1 Release Notes">
<!ENTITY % includes SYSTEM "../../../includes.sgml"> %includes;
]>
<html>
&header;
<p>The release notes for FreeBSD are customized for different
platforms, as some of the changes made to FreeBSD apply only to
specific processor architectures.</p>
<p>Release notes for FreeBSD 5.0-DP1 are available for the following
platforms:</p>
<ul>
<li><a href="relnotes-i386.html">i386</a></li>
<li><a href="relnotes-alpha.html">alpha</a></li>
<li><a href="relnotes-sparc64.html">sparc64</a></li>
</ul>
<p>A list of all platforms currently under development can be found
on the <a href="../../../platforms/index.html">Supported
Platforms</a> page.</p>
</html>

4
en/releases/5.0R/Makefile
View file

@ -1,4 +1,4 @@
# $FreeBSD$
# $FreeBSD: www/en/releases/5.0R/Makefile,v 1.1 2002/03/04 08:17:50 murray Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -9,4 +9,6 @@
DOCS= schedule.sgml
SUBDIR= DP1
.include "${WEB_PREFIX}/share/mk/web.site.mk"

4
en/releases/5.0R/Makefile.inc Normal file
View file

@ -0,0 +1,4 @@
# $FreeBSD$
WEBBASE?= /data/releases/5.0R
WEB_PREFIX?= ${.CURDIR}/../../../..