diff options
Diffstat (limited to 'en_US.ISO8859-1/htdocs/releases/5.1R')
26 files changed, 33796 insertions, 0 deletions
diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/Makefile b/en_US.ISO8859-1/htdocs/releases/5.1R/Makefile new file mode 100644 index 0000000000..9fc3baf57f --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/Makefile @@ -0,0 +1,37 @@ +# $FreeBSD: www/en/releases/5.1R/Makefile,v 1.4 2004/04/05 23:52:13 phantom Exp $ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= announce.sgml +DOCS+= hardware.sgml +DOCS+= installation.sgml +DOCS+= relnotes.sgml +DOCS+= schedule.sgml +DOCS+= todo.sgml + +DATA= docbook.css +DATA+= errata.html +DATA+= early-adopter.html +DATA+= hardware-alpha.html +DATA+= hardware-ia64.html +DATA+= hardware-i386.html +DATA+= hardware-pc98.html +DATA+= hardware-sparc64.html +DATA+= installation-alpha.html +DATA+= installation-ia64.html +DATA+= installation-i386.html +DATA+= installation-pc98.html +DATA+= installation-sparc64.html +DATA+= readme.html +DATA+= relnotes-alpha.html +DATA+= relnotes-ia64.html +DATA+= relnotes-i386.html +DATA+= relnotes-pc98.html +DATA+= relnotes-sparc64.html + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/5.1R/announce.sgml new file mode 100644 index 0000000000..30abce9c5f --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/announce.sgml @@ -0,0 +1,238 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/releases/5.1R/announce.sgml,v 1.4 2005/10/04 06:52:23 murray Exp $"> +<!ENTITY title "FreeBSD 5.1-RELEASE Announcement"> +<!ENTITY % navinclude.download "INCLUDE"> +]> +<html> +&header; + +<p><b>Date:</b> Mon, 9 Jun 2003 09:36:57 -0700 (PDT)<br> + <b>From:</b> Scott Long <scottl@FreeBSD.org><br> + <b>To:</b> freebsd-announce@FreeBSD.org<br> + <b>Subject:</b> [FreeBSD-Announce] ]FreeBSD 5.1 Released!</p> + +<p> +It is my great privilege and pleasure to announce the availability of +FreeBSD 5.1-RELEASE. This release continues FreeBSD on the path of +advanced multiprocessor and application thread support and includes +many improved and widely-sought features: +</p> + +<ul> + <li>Experimental 1:1 and M:N thread libraries provide kernel support for + efficient application multithreading.</li> + + <li>Support for Physical Address Extensions enables Pentium Pro and + higher CPUs to access up to 64GB of RAM.</li> + + <li>Experimental Name Service Switch infrastructure allows enterprises + to seamlessly integrate with LDAP and Active Directory services.</li> + + <li>Enhanced "jail" management, allowing one server to provide many + different "virtual machines" with reduced administrator workload.</li> + + <li>New device drivers include support for IBM/Adaptec ServeRAID + controllers, expanded support for USB 2.0 and USB Ethernet adapters, + and Promise Serial ATA controllers.</li> + + <li>Experimental support for the amd64 platform allows FreeBSD to run + on single processor AMD Opteron systems.</li> +</ul> + +<p> +Although stability is greatly improved and many bugs have been fixed, +FreeBSD 5.1 might not be suitable for all users. More conservative users +may prefer to continue using FreeBSD 4.X. Information on the various +trade-offs involved, as well as some notes on future plans for both +FreeBSD 4.X and 5.X, can be found in the Early Adopter's Guide, available +here: +</p> + +<p> +<tt><a href="http://www.FreeBSD.org/releases/5.1R/early-adopter.html">http://www.FreeBSD.org/releases/5.1R/early-adopter.html</a></tt> +</p> + +<p> +For a complete list of new features and known problems, please see the +release notes and errata list, available here: +</p> + +<p><tt><a href="http://www.FreeBSD.org/releases/5.1R/relnotes.html">http://www.FreeBSD.org/releases/5.1R/relnotes.html</a></tt></p> +<p><tt><a href="http://www.FreeBSD.org/releases/5.1R/errata.html">http://www.FreeBSD.org/releases/5.1R/errata.html</a></tt></p> + +<p> +For more information about FreeBSD release engineering activities, +please see: +</p> + +<p> +<tt><a href="http://www.FreeBSD.org/releng/">http://www.FreeBSD.org/releng/</a></tt> +</p> + +<p> +This release is dedicated to the memory of Alan Eldridge. Alan was a +talented and dedicated member of the KDE On FreeBSD team and the FreeBSD +community, and his passing is mourned by all of us. For more information, +please see +<tt><a href="http://freebsd.kde.org/memoriam/alane.php">http://freebsd.kde.org/memoriam/alane.php</a></tt>. +</p> + +<p><b>Availability</b><p> + +<p> +FreeBSD 5.1-RELEASE supports the i386, pc98, alpha, sparc64, and +ia64 architectures and can be installed directly over the net using the +boot floppies or copied to a local NFS/FTP server. Distributions for +all architectures are available now. +</p> + +<p> +Please continue to support the FreeBSD Project by purchasing media +from one of our supporting vendors. The following companies will be +offering FreeBSD 5.1 based products: +</p> + +<table border="0"> + <tbody> + <tr> + <td>FreeBSD Mall, Inc.</td> + <td><tt><a href="http://www.freebsdmall.com/">http://www.freebsdmall.com/</a></tt></td> + </tr> + <tr> + <td>Daemonnews, Inc.</td> + <td><tt><a href="http://www.bsdmall.com/freebsd1.html">http://www.bsdmall.com/freebsd1.html</a></tt></td> + </tr> + </tbody> +</table> + +<p> +If you can't afford FreeBSD on media, are impatient, or just want to +use it for evangelism purposes, then by all means download the ISO +images. We can't promise that all the mirror sites will carry the +larger ISO images, but they will at least be available from: +</p> + +<ul> + <li><tt><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp://ftp.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp12.FreeBSD.org/pub/FreeBSD/">ftp://ftp12.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/">ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp2.jp.freebsd.org/pub/FreeBSD/">ftp://ftp2.jp.freebsd.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp3.jp.freebsd.org/pub/FreeBSD/">ftp://ftp3.jp.freebsd.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp4.jp.freebsd.org/pub/FreeBSD/">ftp://ftp4.jp.freebsd.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp5.jp.freebsd.org/pub/FreeBSD/">ftp://ftp5.jp.freebsd.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/">ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp7.de.FreeBSD.org/pub/FreeBSD/">ftp://ftp7.de.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp.lt.FreeBSD.org/pub/FreeBSD/">ftp://ftp.lt.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp2.za.FreeBSD.org/pub/FreeBSD/">ftp://ftp2.za.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp.se.FreeBSD.org/pub/FreeBSD/">ftp://ftp.se.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp1.ru.FreeBSD.org/pub/FreeBSD/">ftp://ftp1.ru.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD/">ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD/</a></tt></li> + <li><tt><a href="ftp://ftp4.ru.FreeBSD.org/pub/FreeBSD/">ftp://ftp4.ru.FreeBSD.org/pub/FreeBSD/</a></tt></li> +</ul> + +<p> +FreeBSD is also available via anonymous FTP from mirror sites in the +following countries: Argentina, Australia, Brazil, Bulgaria, Canada, +China, Czech Republic, Denmark, Estonia, Finland, France, Germany, +Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, +Saraville, the Netherlands, New Zealand, Poland, Portugal, Romania, +Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, +Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom. +<p> + +<p> +Before trying the central FTP site, please check your regional +mirror(s) first by going to: +</p> + +<p> +<tt>ftp://ftp.<em><yourdomain></em>.FreeBSD.org/pub/FreeBSD</tt> +</p> + +<p> +Any additional mirror sites will be labeled ftp2, ftp3 and so on. +<p> + +<p> +More information about FreeBSD mirror sites can be found at: +<p> + +<p> +<tt><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html">http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html</a></tt> +</p> + +<p> +For instructions on installing FreeBSD, please see Chapter 2 of The +FreeBSD Handbook. It provides a complete installation walk-through +for users new to FreeBSD, and can be found online at: +<p> + +<p> +<tt><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html">http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html</a></tt> +</p> + +<p><b>Acknowledgments</b></p> + +<p> +Many companies donated equipment, network access, or man-hours to +finance the release engineering activities for FreeBSD 5.1 including +The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and +NTT/Verio. +<p> + +<p>The release engineering team for 5.1-RELEASE includes:</p> + +<table border="0"> + <tbody> + <tr> + <td>Scott Long <<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>></td> + <td>Release Engineering, IA32 and Alpha Release Building</td> + </tr> + <tr> + <td>Bruce A. Mah <<a href="mailto:bmah@FreeBSD.org">bmah@FreeBSD.org</a>></td> + <td>Release Engineering, Documentation</td> + </tr> + <tr> + <td>Robert Watson <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>></td> + <td>Release Engineering, Security</td> + </tr> + <tr> + <td>John Baldwin <<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>></td> + <td>Release Engineering</td> + </tr> + <tr> + <td>Murray Stokely <<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>></td> + <td>Release Engineering</td> + </tr> + <tr> + <td>Bill Fenner <<a href="mailto:fenner@FreeBSD.org">fenner@FreeBSD.org</a>></td> + <td>Sparc64 Release Building</td> + </tr> + <tr> + <td>Marcel Moolenaar <<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>></td> + <td>IA64 Release Building</td> + </tr> + <tr> + <td>Peter Wemm <<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>></td> + <td>AMD64 Release Building</td> + </tr> + <tr> + <td>Takahashi Yoshihiro <<a href="mailto:nyan@FreeBSD.org">nyan@FreeBSD.org</a>></td> + <td>PC98 Release Building</td> + </tr> + <tr> + <td>Kris Kennaway <<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>></td> + <td>Package Building</td> + </tr> + <tr> + <td>Jacques A. Vidrine <<a href="mailto:nectar@FreeBSD.org">nectar@FreeBSD.org</a>></td> + <td>Security Officer</td> + </tr> + </tbody> +</table> + +&footer; + +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/docbook.css b/en_US.ISO8859-1/htdocs/releases/5.1R/docbook.css new file mode 100644 index 0000000000..786c745a10 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/docbook.css @@ -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: www/en/releases/5.0R/docbook.css,v 1.1 2003/01/16 18:23:51 bmah 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; +} diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/early-adopter.html b/en_US.ISO8859-1/htdocs/releases/5.1R/early-adopter.html new file mode 100644 index 0000000000..8a4825639a --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/early-adopter.html @@ -0,0 +1,611 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>Early Adopter's Guide to FreeBSD 5.1-RELEASE</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 id="AEN2" name="AEN2">Early Adopter's + Guide to FreeBSD 5.1-RELEASE</a></h1> + + <div class="AUTHORGROUP"> + <a id="AEN4" name="AEN4"></a> + + <h3 class="CORPAUTHOR">The FreeBSD Release Engineering + Team</h3> + </div> + + <p class="COPYRIGHT">Copyright © 2002, 2003 by The + FreeBSD Release Engineering Team</p> + + <p class="PUBDATE">$FreeBSD: + src/release/doc/en_US.ISO8859-1/early-adopter/article.sgml,v + 1.15 2003/05/03 22:14:55 bmah Exp $<br /> + </p> + + <div> + <div class="ABSTRACT"> + <a id="AEN11" name="AEN11"></a> + + <p>This article describes the status of FreeBSD + 5.1-RELEASE, from the standpoint of users who may be + new to the 5.<tt class="REPLACEABLE"><i>X</i></tt> + series of releases or to FreeBSD in general. It + presents some background information on release + engineering, some highlights of new features, and some + possible drawbacks that might be faced by early + adopters. It also contains some of the future release + engineering plans for the 4-STABLE development branch + and some tips on upgrading existing systems.</p> + </div> + </div> + <hr /> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> marks + the first new major version of FreeBSD in over two years. + Besides a number of new features, it also contains a number + of major developments in the underlying system + architecture. Along with these advances, however, comes a + system that incorporates a tremendous amount of new and + not-widely-tested code. Compared to the existing line of + 4.<tt class="REPLACEABLE"><i>X</i></tt> releases, the first + few 5.<tt class="REPLACEABLE"><i>X</i></tt> releases may + have regressions in areas of stability, performance, and + occasionally functionality.</p> + + <p>For these reasons, the Release Engineering Team <tt + class="EMAIL"><<a + href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>></tt> + specifically discourages users from updating from older + FreeBSD releases to 5.1-RELEASE unless they are aware of + (and prepared to deal with) possible regressions in the + newer releases. Specifically, for more conservative users, + we recommend running 4.<tt + class="REPLACEABLE"><i>X</i></tt> releases (such as + 4.8-RELEASE) for the near-term future. We feel that such + users are probably best served by upgrading to 5.<tt + class="REPLACEABLE"><i>X</i></tt> only after a 5-STABLE + development branch has been created; this may be around the + time of 5.2-RELEASE.</p> + + <p>(FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> suffers + from what has been described as a ``chicken and egg'' + problem. The entire project has a goal of producing + releases that are as stable and reliable as possible. This + stability and reliability requires widespread testing, + particularly of the system's newer features. However, + getting a large number of users to test the system, in a + practical sense, means building and distributing a release + first!)</p> + + <p>This article describes some of the issues involved in + installing and running FreeBSD 5.1-RELEASE. We begin with a + brief overview of the FreeBSD release process. We then + present some of the more noteworthy new features in FreeBSD + 5.1-RELEASE, along with some areas that may prove + troublesome for unwary users. For those users choosing to + remain with 4-STABLE-based releases, we give some of the + short- to medium-term plans for this development branch. + Finally, we present some notes on upgrading existing 4.<tt + class="REPLACEABLE"><i>X</i></tt> systems to + 5.1-RELEASE.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="RELEASE-OVERVIEW" + name="RELEASE-OVERVIEW">2 An Overview of the FreeBSD + Release Process</a></h1> + + <p>FreeBSD employs a model of development that relies on + multiple development branches within the source code + repository. The main branch is called ``CURRENT'', and is + referred to in the CVS repository with the <tt + class="LITERAL">HEAD</tt> tag. New features are committed + first to this branch; although this means that CURRENT is + the first to see new functionality, it also means that it + occasionally suffers from breakages as new features are + added and debugged.</p> + + <p>Most FreeBSD releases are made from one of several + ``STABLE'' branches. Features are only added to these + branches after some amount of testing in CURRENT. At the + moment, only one STABLE branch is under active development; + this branch is referred to as ``4-STABLE'', and all of the + FreeBSD 4.<tt class="REPLACEABLE"><i>X</i></tt> releases + were based on it. This branch has the tag <tt + class="LITERAL">RELENG_4</tt> in the CVS repository.</p> + + <p>FreeBSD 5.0 and 5.1 are based on the CURRENT branch. + These are the first releases from this branch in over two + years (the last was FreeBSD 4.0, in March 2000).</p> + + <p>At some point after the release of FreeBSD 5.0, a + ``5-STABLE'' branch will be created in the FreeBSD CVS + repository with the branch tag <tt + class="LITERAL">RELENG_5</tt>. The past two stable branches + (3-STABLE and 4-STABLE) were created immediately after + their respective ``dot-oh'' releases (3.0 and 4.0, + respectively). In hindsight, this practice did not give + sufficient time for either CURRENT to stabilize before the + new branches were created. This in turn resulted in wasted + effort porting bug fixes between branches, as well as some + architectural changes that could not be ported between + branches at all.</p> + + <p>Therefore, the release engineering team will only create + the 5-STABLE branch in the CVS repository after we have + found a relatively stable state to use as its basis. It is + likely that there will be multiple releases in the 5.<tt + class="REPLACEABLE"><i>X</i></tt> series before this + happens; we estimate that the 5-STABLE branch will be + created sometime after 5.2-RELEASE.</p> + + <p>More information on FreeBSD release engineering + processes can be found on the <a + href="http://www.FreeBSD.org/releng/index.html" + target="_top">Release Engineering Web pages</a> and in the + <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/index.html" + target="_top">``FreeBSD Release Engineering''</a> article. + Specific issues for the upcoming 5-STABLE development + branch can be found in <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html" + target="_top">``The Roadmap for 5-STABLE''</a>.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="NEW" name="NEW">3 New + Features</a></h1> + + <p>A large attraction of FreeBSD 5.<tt + class="REPLACEABLE"><i>X</i></tt> is a number of new + features. These new features and functionality generally + involve large architectural changes that were not feasible + to port back to the FreeBSD 4-STABLE development branch. + (By contrast, many self-contained enhancements, such as new + device drivers or userland utilities, have already been + ported.) A brief, but not exhaustive list includes:</p> + + <ul> + <li> + <p>SMPng: The ``next generation'' support for SMP + machines (work in progress). There is now partial + support for multiple processors to be running in the + kernel at the same time. This work is ongoing.</p> + </li> + + <li> + <p>KSE: Kernel Scheduled Entities allow a single + process to have multiple kernel-level threads, similar + to Scheduler Activations. The (experimental) <tt + class="FILENAME">libkse</tt> and <tt + class="FILENAME">libthr</tt> libraries make this + feature available to multi-threaded userland + programs.</p> + </li> + + <li> + <p>New architectures: Support for the sparc64 and ia64 + architectures, in addition to the i386, pc98, and + alpha.</p> + </li> + + <li> + <p>GCC: The compiler toolchain is now based on GCC + 3.2.2, rather than GCC 2.95.<tt + class="REPLACEABLE"><i>X</i></tt>.</p> + </li> + + <li> + <p>MAC: Support for extensible, loadable Mandatory + Access Control policies.</p> + </li> + + <li> + <p>GEOM: A flexible framework for transformations of + disk I/O requests. An experimental disk encryption + facility has been developed based on GEOM.</p> + </li> + + <li> + <p>FFS: The FFS filesystem now supports background <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fsck&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fsck</span>(8)</span></a> + operations (for faster crash recovery) and filesystem + snapshots.</p> + </li> + + <li> + <p>UFS2: A new UFS2 on-disk format has been added, + which supports extended per-file attributes and larger + file sizes. UFS2 is now the default format for <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a>. On + all platforms except for pc98, filesystems created from + within <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + will use UFS2 by default.</p> + </li> + + <li> + <p>Cardbus: Support for Cardbus devices.</p> + </li> + </ul> + + <p>A more comprehensive list of new features can be found + in the release notes for FreeBSD 5.0-RELEASE and FreeBSD + 5.1-RELEASE.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="DRAWBACKS" name="DRAWBACKS">4 + Drawbacks to Early Adoption</a></h1> + + <p>Along with the new features of FreeBSD 5.<tt + class="REPLACEABLE"><i>X</i></tt> come some areas that can + cause problems, or at least can lead to unexpected + behavior. Generally, these come from the fact that a number + of features are works-in-progress. A partial list of these + areas of difficulty includes:</p> + + <ul> + <li> + <p>A number of features are not yet finished. Examples + from the feature list above include SMPng and KSE. + While suitable for testing and experimentation, these + features may not be ready for production use.</p> + </li> + + <li> + <p>Because of changes in kernel data structures and + ABIs/APIs, third-party binary device drivers will + require modifications to work correctly under FreeBSD + 5.0. There is a possibility of more minor ABI/API + changes before the 5-STABLE branch is created.</p> + </li> + + <li> + <p>Several parts of FreeBSD's base system functionality + have been moved to the Ports Collection. Notable + examples include <b class="APPLICATION">Perl</b>, <b + class="APPLICATION">UUCP</b>, and most (but not all) + games. While these programs are still supported, their + removal from the base system may cause some + confusion.</p> + </li> + + <li> + <p>Some parts of the FreeBSD base system have fallen + into a state of disrepair due to a lack of users and + maintainers. These have been removed. Specific examples + include the generation of a.out-style executables, XNS + networking support, and the X-10 controller driver.</p> + </li> + + <li> + <p>A number of ports and packages do not build or do + not run correctly under FreeBSD 5.0, whereas they did + under FreeBSD 4-STABLE. Generally these problems are + caused by compiler toolchain changes or cleanups of + header files.</p> + </li> + + <li> + <p>Many FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> + features are seeing wide exposure for the first time. + Many of these features (such as SMPng) have broad + impacts on the kernel.</p> + </li> + + <li> + <p>A certain amount of debugging and diagnostic code is + still in place to help track down problems in FreeBSD + 5.0's new features. This may cause FreeBSD 5.0 to + perform more slowly than 4-STABLE.</p> + </li> + + <li> + <p>Features are only added to the 4-STABLE development + branch after a ``settling time'' in -CURRENT. FreeBSD + 5.0 does not have the stabilizing influence of a + -STABLE branch. (It is likely that the 5-STABLE + development branch will be created sometime after + 5.2-RELEASE.)</p> + </li> + + <li> + <p>Documentation (such as the FreeBSD <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/index.html" + target="_top">Handbook</a> and <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html" + target="_top">FAQ</a>) may not reflect changes + recently made to FreeBSD 5.<tt + class="REPLACEABLE"><i>X</i></tt>.</p> + </li> + </ul> + + <p>Because a number of these drawbacks affect system + stability, the release engineering team recommends that + more conservative sites and users stick to releases based + on the 4-STABLE branch until the 5.<tt + class="REPLACEABLE"><i>X</i></tt> series is more + polished.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="PLANS-STABLE" + name="PLANS-STABLE">5 Plans for the 4-STABLE + Branch</a></h1> + + <p>The release of FreeBSD 5.0 does not mean the end of the + 4-STABLE branch. Indeed, FreeBSD 4.8 was released two + months after 5.0, in April 2003. There will most likely be + at least one more release on this branch, namely + 4.9-RELEASE, currently scheduled for summer 2003. A + 4.10-RELEASE is a likely possibility as well. Future + releases from this branch will depend on several factors. + The most important of these is the existence and stability + of the 5-STABLE branch. If CURRENT is not sufficiently + stable to allow the creation of a 5-STABLE branch, this may + require and permit more releases from the 4-STABLE branch. + Until the last declared release on the 4-STABLE branch, new + features may be merged from <tt class="LITERAL">HEAD</tt> + at the discretion of developers, subject to existing + release engineering policies.</p> + + <p>To some extent, the release engineering team (as well as + the developer community as a whole) will take into account + user demand for future 4-STABLE releases. This demand, + however, will need to be balanced with release engineering + resources (particularly developers' time, computing + resources, and mirror archive space).</p> + + <p>The Security Officer Team <tt class="EMAIL"><<a + href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>></tt> + will continue to support releases made from the 4-STABLE + branch in accordance with their published policies, which + can be found on the <a + href="http://www.FreeBSD.org/security/index.html" + target="_top">Security page</a> on the FreeBSD web site. + Generally, the two most recent releases from any branch + will be supported with respect to security advisories and + security fixes. At its discretion, the team may support + other releases for specific issues.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADE" name="UPGRADE">6 Notes on + Upgrading from FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt></a></h1> + + <p>For those users with existing FreeBSD systems, this + section offers a few notes on upgrading a FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt> system to 5.<tt + class="REPLACEABLE"><i>X</i></tt>. As with any FreeBSD + upgrade, it is crucial to read the release notes and the + errata for the version in question, as well as <tt + class="FILENAME">src/UPDATING</tt> in the case of source + upgrades.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN136" name="AEN136">6.1 Binary + Upgrades</a></h2> + + <p>Probably the most straightforward approach is that of + ``backup everything, reformat, reinstall, and restore + everything''. This eliminates problems of incompatible or + obsolete executables or configuration files polluting the + new system. It allows new filesystems to be created to + take advantage of new functionality (most notably, the + UFS2 defaults).</p> + + <p>As of this time, the binary upgrade option in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> has + not been well-tested for cross-major-version upgrades. + Using this feature is not recommended. In particular, a + binary upgrade will leave behind a number of files that + are present in FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt> but not in 5.<tt + class="REPLACEABLE"><i>X</i></tt>. These obsolete files + may create some problems.</p> + + <p>On the i386 and pc98 platforms, a UserConfig utility + exists on 4-STABLE to allow boot-time configuration of + ISA devices when booting from installation media. Under + FreeBSD 5.0, this functionality has been replaced in part + by the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=device.hints&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">device.hints</span>(5)</span></a> + mechanism (it allows specifying the same parameters, but + with a very different interface).</p> + + <p>Floppy-based binary installations may require + downloading a third, new floppy image holding additional + device drivers in kernel modules. This <tt + class="FILENAME">drivers.flp</tt> floppy image will + generally be found in the same location as the usual <tt + class="FILENAME">kern.flp</tt> and <tt + class="FILENAME">mfsroot.flp</tt> floppy images.</p> + + <p>CDROM-based installations on the i386 architecture now + use a ``no-emulation'' boot loader. This allows, among + other things, the use of a <tt + class="LITERAL">GENERIC</tt> kernel, rather than the + stripped-down kernel on the floppy images. In theory, any + system capable of booting the Microsoft Windows NT 4 + installation CDROMs should be able to cope with the + FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> + CDROMs.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN158" name="AEN158">6.2 Source + Upgrades</a></h2> + + <p>Reading <tt class="FILENAME">src/UPDATING</tt> is + absolutely essential. The section entitled ``To upgrade + from 4.x-stable to current'' contains a step-by-step + update procedure. This procedure must be followed + exactly, without making use of the ``shortcuts'' that + some users occasionally employ.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN164" name="AEN164">6.3 Common + Notes</a></h2> + + <p><b class="APPLICATION">Perl</b> has been removed from + the base system, and should be installed either from a + pre-built package or from the Ports Collection. Building + Perl as a part of the base system created a number of + difficulties which made updates problematic. The base + system utilities that used Perl have either been + rewritten (if still applicable) or discarded (if + obsolete). <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + will now install the Perl package as a part of most + distribution sets, so most users will not notice this + change.</p> + + <p>It is generally possible to run old 4.<tt + class="REPLACEABLE"><i>X</i></tt> executables under 5.<tt + class="REPLACEABLE"><i>X</i></tt>, but this requires the + <tt class="FILENAME">compat4x</tt> distribution to be + installed. Thus, using old ports <span + class="emphasis"><i class="EMPHASIS">may</i></span> be + possible.</p> + + <p>When installing or upgrading over the top of an + existing 4-STABLE-based system, it is extremely important + to clear out old header files in <tt + class="FILENAME">/usr/include</tt>. Renaming or moving + this directory before a binary installation or an <tt + class="LITERAL">installworld</tt> is generally + sufficient. If this step is not taken, confusion may + result (especially with C++ programs) as the compiler may + wind up using a mixture of obsolete and current header + files.</p> + + <p><tt class="FILENAME">MAKEDEV</tt> is no longer + available, nor is it required. FreeBSD 5.<tt + class="REPLACEABLE"><i>X</i></tt> uses a device + filesystem, which automatically creates device nodes on + demand. For more information, please see <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a>.</p> + + <p>UFS2 is the default on-disk format for file systems + created using <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a>. For all + platforms except pc98, it is also the default for file + systems created using the disk labeling screen within <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a>. + Because FreeBSD 4.<tt class="REPLACEABLE"><i>X</i></tt> + only understands UFS1 (not UFS2), disk partitions that + need to be accessed by both 5.<tt + class="REPLACEABLE"><i>X</i></tt> and 4.<tt + class="REPLACEABLE"><i>X</i></tt> must be created with + UFS1. This can be specified using the <tt + class="OPTION">-O1</tt> option to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a>, or on + the disk labeling screen in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a>. + This situation most often arises with a a single machine + that dual-boots FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt> and FreeBSD 5.<tt + class="REPLACEABLE"><i>X</i></tt>. Note that there is no + way to convert file systems between the two on-disk + formats (other than backing up, re-creating the file + system, and restoring).</p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="SUMMARY" name="SUMMARY">7 + Summary</a></h1> + + <p>While FreeBSD 5.1-RELEASE contains a number of new and + exciting features, it may not be suitable for all users at + this time. In this document, we presented some background + on release engineering, some of the more notable new + features of the 5.<tt class="REPLACEABLE"><i>X</i></tt> + series, and some drawbacks to early adoption. We also + presented some future plans for the 4-STABLE development + branch and some tips on upgrading for early adopters.</p> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/errata.html b/en_US.ISO8859-1/htdocs/releases/5.1R/errata.html new file mode 100644 index 0000000000..b65a6180ec --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/errata.html @@ -0,0 +1,266 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<meta name="generator" content="HTML Tidy, see www.w3.org" /> +<title>FreeBSD 5.1-RELEASE Errata</title> +<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" /> +<link rel="STYLESHEET" type="text/css" href="docbook.css" /> +</head> +<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084" +alink="#0000FF"> +<div class="ARTICLE"> +<div class="TITLEPAGE"> +<h1 class="TITLE"><a id="AEN2" name="AEN2">FreeBSD 5.1-RELEASE Errata</a></h1> + +<h3 class="CORPAUTHOR">The FreeBSD Project</h3> + +<p class="COPYRIGHT">Copyright © 2000, 2001, 2002, 2003 The FreeBSD Documentation +Project</p> + +<p class="PUBDATE">$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.54 +2003/12/04 23:53:54 bmah Exp $<br /> +</p> + +<div class="LEGALNOTICE"><a id="TRADEMARKS" name="TRADEMARKS"></a> +<p>FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to +change soon.</p> + +<p>Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or +registered trademarks of Intel Corporation or its subsidiaries in the United States and +other countries.</p> + +<p>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="AEN19" name="AEN19"></a> +<p>This document lists errata items for FreeBSD 5.1-RELEASE, containing significant +information discovered after the release or too late in the release cycle to be otherwise +included in the release documentation. This information includes security advisories, as +well as news relating to the software or documentation that could affect its operation or +usability. An up-to-date version of this document should always be consulted before +installing this version of FreeBSD.</p> + +<p>This errata document for FreeBSD 5.1-RELEASE will be maintained until the release of +FreeBSD 5.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 5.1-RELEASE. Before +installing this version, it is important to consult this document to learn about any +post-release discoveries or problems that may already have been found and fixed.</p> + +<p>Any version of this errata document actually distributed with the release (for +example, on a CDROM distribution) will be out of date by definition, but other copies are +kept updated on the Internet and should be consulted as the ``current errata'' for this +release. These other copies of the errata are located at <a +href="http://www.FreeBSD.org/releases/" +target="_top">http://www.FreeBSD.org/releases/</a>, plus any sites which keep up-to-date +mirrors of this location.</p> + +<p>Source and binary snapshots of FreeBSD 5-CURRENT also contain up-to-date copies of +this document (as of the time of the snapshot).</p> + +<p>For a list of all FreeBSD CERT security advisories, see <a +href="http://www.FreeBSD.org/security/" +target="_top">http://www.FreeBSD.org/security/</a> or <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/" +target="_top">ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/</a>.</p> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="SECURITY" name="SECURITY">2 Security Advisories</a></h2> + +<p>The implementation of the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=realpath&sektion=3&manpath=FreeBSD+5.1-current"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">realpath</span>(3)</span></a> +function contained a single-byte buffer overflow bug. This had various impacts, depending +on the application using <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=realpath&sektion=3&manpath=FreeBSD+5.1-current"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">realpath</span>(3)</span></a> and +other factors. This bug was fixed on the 5-CURRENT development branch before 5.1-RELEASE; +FreeBSD 5.1-RELEASE is therefore not affected. However, this change was not noted in the +release documentation. For more information, see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:08.realpath.asc" +target="_top">FreeBSD-SA-03:08</a>.</p> + +<p>The kernel contains a bug that could allow it to attempt delivery of invalid signals, +leading to a kernel panic or, under some circumstances, unauthorized modification of +kernel memory. This bug has been fixed on the 5-CURRENT development branch and the +5.1-RELEASE security fix branch. For more information, see security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:09.signal.asc" +target="_top">FreeBSD-SA-03:09</a>.</p> + +<p>A bug in the iBCS2 emulation module could result in disclosing the contents of kernel +memory. (Note that this module is not enabled in FreeBSD by default.) This bug has been +fixed on the 5-CURRENT development branch and the 5.1-RELEASE security fix branch. More +information can be found in security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:10.ibcs2.asc" +target="_top">FreeBSD-SA-03:10</a>.</p> + +<p><b class="APPLICATION">OpenSSH</b> contains a bug in its buffer management code that +could potentially cause it to crash. This bug has been fixed via a vendor-supplied patch +on the 5-CURRENT development branch and the 5.1-RELEASE security fix branch. For more +details, refer to security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:12.openssh.asc" +target="_top">FreeBSD-SA-03:12</a>.</p> + +<p><b class="APPLICATION">sendmail</b> contains a remotely-exploitable buffer overflow. +This bug has been fixed via a new version import on the 5-CURRENT development branch and +via a vendor-supplied patch on the 5.1-RELEASE security fix branch. More details can be +found in security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:13.sendmail.asc" +target="_top">FreeBSD-SA-03:13</a>.</p> + +<p>The FreeBSD ARP code contains a bug that could allow the kernel to cause resource +starvation which eventually results in a system panic. This bug has been fixed on the +5-CURRENT development branch and the 5.1-RELEASE security fix branch. More information +can be found in security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:14.arp.asc" +target="_top">FreeBSD-SA-03:14</a>.</p> + +<p>Several bugs in the <b class="APPLICATION">OpenSSH</b> PAM authentication code could +have impacts ranging from incorrect authentication to a stack corruption. These have been +corrected via vendor-supplied patches; details can be found in security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:15.openssh.asc" +target="_top">FreeBSD-SA-03:15</a>.</p> + +<p>The implementation of the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=procfs&sektion=5&manpath=FreeBSD+5.1-current"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">procfs</span>(5)</span></a> and +the <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=linprocfs&sektion=5&manpath=FreeBSD+5.1-current"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">linprocfs</span>(5)</span></a> +contain a bug that could result in disclosing the contents of kernel memory. This bug has +been fixed on the 5-CURRENT development branch and the 5.1-RELEASE security fix branch. +More information can be found in security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:17.procfs.asc" +target="_top">FreeBSD-SA-03:17</a>.</p> + +<p><b class="APPLICATION">OpenSSL</b> contains several bugs which could allow a remote +attacker to crash an <b class="APPLICATION">OpenSSL</b>-using application or to execute +arbitrary code with the privileges of the application. These bugs have been fixed via a +vendor-supplied patch on the 5-CURRENT development branch and the 5.1-RELEASE security +fix branch. Note that only applications that use <b class="APPLICATION">OpenSSL</b>'s +ASN.1 or X.509 handling code are affected (<b class="APPLICATION">OpenSSH</b> is +unaffected, for example). More information can be found in security advisory <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:18.openssl.asc" +target="_top">FreeBSD-SA-03:18</a>.</p> + +<p><b class="APPLICATION">BIND</b> contains the potential for a denial-of-service attack. +This vulnerability has been addressed by a vendor patch on the 5.1-RELEASE security fix +branch and by the import of a new version to the 5-CURRENT development branch. For more +information, see <a +href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:19.bind.asc" +target="_top">FreeBSD-SA-03:19</a>.</p> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="OPEN-ISSUES" name="OPEN-ISSUES">3 Open Issues</a></h2> + +<p>The RAIDframe disk driver described in <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=raid&sektion=4&manpath=FreeBSD+5.1-current"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">raid</span>(4)</span></a> is +non-functional for this release.</p> + +<p>ACPI seems to make some <span class="TRADEMARK">i386</span>™ machines unstable. +Turning off ACPI support may help solve some of these problems; see an item in <a +href="#LATE-NEWS">Section 4</a>.</p> + +<p>An integer overflow could cause kernel panics on PAE-using machines with certain +memory sizes. This bug has been corrected on both the <var +class="LITERAL">RELENG_5_1</var> and <var class="LITERAL">HEAD</var> branches. A +workaround for this problem is to remove some memory, update the system in question, and +reinstall the memory.</p> + +<p>Attempting to write to an <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=msdosfs&sektion=5&manpath=FreeBSD+5.1-current"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">msdosfs</span>(5)</span></a> file +system that has been upgraded from read-only to read-write via <tt class="COMMAND">mount +-u</tt> will cause the system to lock up. To work around this problem, unmount the file +system first, then mount it again with the appropriate options instead of using <tt +class="COMMAND">mount -u</tt>.</p> +</div> + +<div class="SECT1"> +<hr /> +<h2 class="SECT1"><a id="LATE-NEWS" name="LATE-NEWS">4 Late-Breaking News</a></h2> + +<p><a +href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-current"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">ipfw</span>(4)</span></a> should +work correctly on strict-alignment 64-bit architectures such as alpha and <span +class="TRADEMARK">Sparc64</span>®.</p> + +<p>The release notes should have stated that the <tt class="FILENAME">libthr</tt> library +is built by default for the <span class="TRADEMARK">i386</span> platform.</p> + +<p>FreeBSD 5.1-RELEASE includes some new boot loader scripts designed to make booting +FreeBSD with different options easier. This may help diagnose bootstrapping problems. +These scripts build on the existing Forth-based boot loader scripts (thus, <tt +class="FILENAME">/boot/loader.conf</tt> and other existing loader configuration files +still apply). They are only installed by default for new binary installs on <span +class="TRADEMARK">i386</span> machines. The new scripts present a boot-time menu that +controls how FreeBSD is booted, and include options to turn off ACPI, a ``safe mode'' +boot, single-user booting, and verbose booting. ``Safe mode'' booting can be particularly +useful when compatibility with a system's hardware is uncertain, and sets the following +kernel tunable variables:</p> + +<pre class="PROGRAMLISTING"> +hint.acpi.0.disabled=1 # disable ACPI (i386 only) +hw.ata.ata_dma=0 # disable IDE DMA +hw.ata.atapi_dma=0 # disable ATAPI/IDE DMA +hw.ata.wc=0 # disable IDE disk write cache +hw.eisa_slots=0 # disable probing for EISA devices +</pre> + +<p>For new installs on <span class="TRADEMARK">i386</span> architecture machines, <a +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-current"> +<span class="CITEREFENTRY"><span class="REFENTRYTITLE">sysinstall</span>(8)</span></a> +will try to determine if ACPI was disabled via the new boot loader scripts mentioned +above, and if so, ask if this change should be made permanent.</p> + +<p>The release notes should have mentioned that work on the following features was +sponsored by the Defense Advanced Research Projects Agency (DARPA): OpenPAM, NSS support, +PAE support, various MAC framework updates, the GEOM disk geometry system.</p> +</div> +</div> + +<hr /> +<p align="center"><small>This file, and other release-related documents, can be +downloaded from <a +href="http://snapshots.jp.FreeBSD.org/">http://snapshots.jp.FreeBSD.org/</a>.</small></p> + +<p align="center"><small>For questions about FreeBSD, read the <a +href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting <<a +href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + +<p align="center"><small><small>All users of FreeBSD 5-CURRENT should subscribe to the +<<a href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> mailing +list.</small></small></p> + +<p align="center">For questions about this documentation, e-mail <<a +href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + +<br /> +<br /> +</body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-alpha.html b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-alpha.html new file mode 100644 index 0000000000..aa9ee4df82 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-alpha.html @@ -0,0 +1,5842 @@ +<!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/alpha 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/alpha + 5.1-RELEASE Hardware Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Documentation + Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#SUPPORT-PROC">Supported processors and + motherboards</a></dt> + + <dd> + <dl> + <dt>2.1 <a href="#AEN27">Overview</a></dt> + + <dt>2.2 <a href="#AEN46">In general, what do you need + to run FreeBSD on an Alpha?</a></dt> + + <dt>2.3 <a href="#AEN107">System-specific + information</a></dt> + + <dd> + <dl> + <dt>2.3.1 <a href="#AEN112">AXPpci33 + (``NoName'')</a></dt> + + <dt>2.3.2 <a href="#AEN187">Universal Desktop Box + (UDB or ``Multia'')</a></dt> + + <dt>2.3.3 <a href="#AEN276">Personal Workstation + (``Miata'')</a></dt> + + <dt>2.3.4 <a href="#AEN386">Evaluation Board 64 + family</a></dt> + + <dt>2.3.5 <a href="#AEN441">Evaluation Board 164 + (``EB164, PC164, PC164LX, PC164SX'') + family</a></dt> + + <dt>2.3.6 <a href="#AEN508">AlphaStation 200 + (``Mustang'') and 400 (``Avanti'') + series</a></dt> + + <dt>2.3.7 <a href="#AEN575">AlphaStation 500 and + 600 (``Alcor'' & ``Maverick'' for EV5, + ``Bret'' for EV56)</a></dt> + + <dt>2.3.8 <a href="#AEN687">AlphaServer 1000 + (``Mikasa''), 1000A (``Noritake'') and + 800(``Corelle'')</a></dt> + + <dt>2.3.9 <a href="#AEN743">DS10/VS10/XP900 + (``Webbrick'') / XP1000 (``Monet'') / DS10L + (``Slate'')</a></dt> + + <dt>2.3.10 <a href="#AEN894">DS20/DS20E + (``Goldrush'')</a></dt> + + <dt>2.3.11 <a href="#AEN963">AlphaPC 264DP / + UP2000</a></dt> + + <dt>2.3.12 <a href="#AEN1009">AlphaServer 2000 + (``DemiSable''), 2100 (``Sable''), 2100A + (``Lynx'')</a></dt> + + <dt>2.3.13 <a href="#AEN1080">AlphaServer 4x00 + (``Rawhide'')</a></dt> + + <dt>2.3.14 <a href="#AEN1113">AlphaServer 1200 + (``Tincup'') and AlphaStation 1200 + (``DaVinci'')</a></dt> + + <dt>2.3.15 <a href="#AEN1143">AlphaServer 8200 + and 8400 (``TurboLaser'')</a></dt> + + <dt>2.3.16 <a href="#AEN1186">Alpha Processor + Inc. UP1000</a></dt> + + <dt>2.3.17 <a href="#AEN1235">Alpha Processor + Inc. UP1100</a></dt> + + <dt>2.3.18 <a href="#AEN1283">Alpha Processor + Inc. CS20, Compaq DS20L</a></dt> + + <dt>2.3.19 <a href="#AEN1330">Compaq AlphaServer + ES40 (``Clipper'')</a></dt> + </dl> + </dd> + + <dt>2.4 <a href="#AEN1367">Supported Hardware + Overview</a></dt> + + <dt>2.5 <a href="#AEN1399">Acknowledgments</a></dt> + </dl> + </dd> + + <dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + + <dd> + <dl> + <dt>3.1 <a href="#AEN1446">Disk Controllers</a></dt> + + <dt>3.2 <a href="#ETHERNET">Ethernet + Interfaces</a></dt> + + <dt>3.3 <a href="#AEN3012">FDDI Interfaces</a></dt> + + <dt>3.4 <a href="#AEN3022">ATM Interfaces</a></dt> + + <dt>3.5 <a href="#AEN3066">Wireless Network + Interfaces</a></dt> + + <dt>3.6 <a href="#AEN3194">Miscellaneous + Networks</a></dt> + + <dt>3.7 <a href="#AEN3225">ISDN Interfaces</a></dt> + + <dt>3.8 <a href="#AEN3289">Serial Interfaces</a></dt> + + <dt>3.9 <a href="#AEN3484">Audio Devices</a></dt> + + <dt>3.10 <a href="#AEN3607">Camera and Video Capture + Devices</a></dt> + + <dt>3.11 <a href="#USB">USB Devices</a></dt> + + <dt>3.12 <a href="#FIREWIRE">IEEE 1394 (Firewire) + Devices</a></dt> + + <dt>3.13 <a href="#BLUETOOTH">Bluetooth + Devices</a></dt> + + <dt>3.14 <a href="#AEN3987">Cryptographic + Accelerators</a></dt> + + <dt>3.15 <a href="#AEN4012">Miscellaneous</a></dt> + </dl> + </dd> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the hardware compatibility notes + for FreeBSD 5.1-RELEASE on the Alpha/AXP hardware platform + (also referred to as FreeBSD/alpha 5.1-RELEASE). It lists + devices known to work on this platform, as well as some + notes on boot-time kernel customization that may be useful + when attempting to configure support for new devices.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> This document includes information + specific to the Alpha/AXP 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 id="SUPPORT-PROC" + name="SUPPORT-PROC">2 Supported processors and + motherboards</a></h1> + <i class="AUTHORGROUP"><span class="CONTRIB">Maintained + by</span> Wilko Bulte.</i> + + <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 id="AEN27" name="AEN27">2.1 + Overview</a></h2> + + <p>This document tries to provide a starting point for + those who want to run FreeBSD on an Alpha-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 + alpha;</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> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> You will see references to DEC, + Digital Equipment Corporation and Compaq used more or + less interchangeably. Now that Compaq has acquired + Digital Equipment it would be more correct to refer + to Compaq only. To be completely politically correct + given that Hewlett Packard in turn has acquired + Compaq I probably should be using HP everywhere. + Given the fact that you will see the mix of names + everywhere, I don't bother.</p> + </blockquote> + </div> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> SRM commands will be in <tt + class="USERINPUT"><b>UPPER CASE</b></tt>. Lower case + input is also acceptable to SRM. Upper case is used + for clarity.</p> + </blockquote> + </div> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Compaq has put information on the Web + for Linux developers that is also very useful for + FreeBSD users. Please check at <a + href="http://www.support.compaq.com/alpha-tools/" + target="_top">Linux Alpha Power tools</a>.</p> + </blockquote> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN46" name="AEN46">2.2 In + general, what do you need to run FreeBSD on an + Alpha?</a></h2> + + <p>Obviously you will need an Alpha machine that FreeBSD + knows about. Alpha machines are NOT like PCs. There are + considerable differences between the various core logic + chip sets and mainboard designs. This means that a kernel + needs to know the intimate details of a particular + machine before it can run on it. Throwing some odd <tt + class="FILENAME">GENERIC</tt> kernel at unknown hardware + is almost guaranteed to fail miserably.</p> + + <p>For a machine even to be considered for FreeBSD use + please make sure it has the SRM console firmware + installed. Or at least make sure that SRM console + firmware is available for the particular machine type. If + FreeBSD does not currently support your machine type, + there is a good chance that this will change at some + point in time, assuming SRM is available. All bets are + off when SRM console firmware is not available.</p> + + <p>Machines with the ARC or AlphaBIOS console firmware + were intended for WindowsNT. Some have SRM console + firmware available in the system ROMs which you only have + to select (via an ARC or AlphaBIOS menu). In other cases + you will have to re-flash the ROMs with SRM code. Check + on http://ftp.digital.com/pub/DEC/Alpha/firmware to see + what is available for your particular system. In any + case: no SRM means <span class="emphasis"><i + class="EMPHASIS">no</i></span> FreeBSD (or NetBSD, + OpenBSD, Tru64 Unix or OpenVMS for that matter). With the + demise of WindowsNT/alpha a lot of former NT boxes are + sold on the second hand market. They have little or no + trade-in value when they are NT-only from the console + firmware perspective. So, be suspicious if the price + appears too good.</p> + + <p>Known non-SRM machines are:</p> + + <ul> + <li> + <p>Digital XL series</p> + </li> + + <li> + <p>Digital XLT series</p> + </li> + + <li> + <p>Samsung PC164UX (``Ruffian'')</p> + </li> + + <li> + <p>Samsung 164B</p> + </li> + </ul> + + <p>Machines that have SRM but are not supported by + FreeBSD are:</p> + + <ul> + <li> + <p>DECpc 150 (``Jensen'')</p> + </li> + + <li> + <p>DEC 2000/300 (``Jensen'')</p> + </li> + + <li> + <p>DEC 2000/500 (``Culzean'')</p> + </li> + + <li> + <p>AXPvme series (``Medulla'')</p> + </li> + </ul> + + <p>To complicate things a bit further: Digital used to + have so called ``white-box'' Alpha machines destined as + NT-only and ``blue-box'' Alpha machines destined for + OpenVMS and Digital Unix. These names are based on the + color of the cabinets, ``FrostWhite'' and ``TopGunBlue'' + respectively. Although you could put the SRM console + firmware on a whitebox, OpenVMS and Digital Unix will + refuse to boot on them. FreeBSD in post-4.0-RELEASE will + run on both the white and the blue-box variants. Before + someone asks: the white ones had a rather different + (read: cheaper) Digital price tag.</p> + + <p>As part of the SRM you will get the so called OSF/1 + PAL code (OSF/1 being the initial name of Digital's UNIX + offering on Alpha). The PAL code can be thought of as a + software abstraction layer between the hardware and the + operating system. It uses normal CPU instruction plus a + handful of privileged instructions specific for PAL use. + PAL is not microcode. The ARC console firmware contains a + different PAL code, geared towards WinNT and in no way + suitable for use by FreeBSD (or more generic: Unix or + OpenVMS). Before someone asks: Linux/alpha brings its own + PAL code, allowing it to boot on ARC and AlphaBIOS. There + are various reasons why this is not a very good idea in + the eyes of the *BSD folks. I don't want to go into + details here. If you are interested in the gory details + search the FreeBSD and NetBSD web sites.</p> + + <p>There is another pitfall ahead: you will need a disk + adapter that the SRM console firmware recognizes in order + to be able to boot from a disk. What is acceptable to SRM + as a boot adapter is unfortunately highly system and SRM + version dependent. For older PCI based machines it means + you will need either a NCR/Symbios 53C810 based adapter, + or a Qlogic 1020/1040 based adapter. Some machines come + with a SCSI chip embedded on the mainboard. Newer machine + designs and SRM versions will be able to work with more + modern SCSI chips/adapters. Check out the machine + specific info below. Please note that the rest of this + discussion only refers to Symbios chips, this is meant to + include the older chips that still have NCR stamped on + them. Symbios bought NCR sometime.</p> + + <p>The problem might bite those who have machines that + started their lives as WindowsNT boxes. The ARC or + AlphaBIOS knows about <span class="emphasis"><i + class="EMPHASIS">other</i></span> adapter types that it + can boot from than the SRM. For example you can boot from + an Adaptec 2940UW with ARC/AlphaBios but (generally) not + with SRM. Some newer machine types have introduced + Adaptec boot support. Please consult the machine specific + section for details.</p> + + <p>Most adapters that cannot be booted from work fine for + data-only disks. The differences between SRM and ARC + could also get you pre-packaged IDE CDROMs and hard + drives in some (former WindowsNT) systems. SRM versions + exist (depends on the machine type) that can boot from + IDE disks and CDROMs. Check the machine specific section + for details.</p> + + <p>FreeBSD 4.0 and later can be booted from the + distribution CDROM. Earlier versions needed booting from + a 2 disk floppy set.</p> + + <p>In order to be bootable the root partition (partition + a) must be at offset 0 of the disk drive. This means you + have to use the installer's partitioning menu and start + with assigning partition a at offset 0 to the root + partition. Subsequently layout the rest of the partitions + to your liking. If you do not adhere to this rule the + install will proceed just fine, but the system will not + be bootable from the freshly installed disk.</p> + + <p>If you don't have/want a local disk drive you can boot + via the Ethernet. This assumes an Ethernet adapter/chip + that is recognized by the SRM console. Generally speaking + this boils down to either a 21040 or 21142 or 21143 based + Ethernet interface. Older machines or SRM versions may + not recognize the 21142 / 21143 Fast Ethernet chips, you + are then limited to using 10Mbit Ethernet for net booting + those machines. Non-DEC cards based on said chips will + generally (but are not guaranteed to) work. Note that + Intel took over the 21x4x chips when it bought Digital + Semiconductor. So you might see an Intel logo on them + these days. Recent machine designs have SRM support for + Intel 8255x Ethernet chips.</p> + + <p>Alpha machines can be run with SRM on a graphics + console or on a serial console. ARC can also be run on a + serial consoles if need be. VT100 emulation with 8 bit + controls should at least allow you to switch from + ARC/AlphaBIOS to SRM mode without having to install a + graphics card first.</p> + + <p>If you want to run your Alpha machine without a + monitor/graphics card just don't connect a keyboard/mouse + to the machine. Instead hook up a serial + terminal[emulator] to serial port #1. The SRM will talk + 9600N81 to you. This can also be really practical for + debugging purposes. Beware: some/most (?) SRMs will also + present you with a console prompt at serial port #2. The + booting kernel, however, will display the boot messages + on serial port #1 and will also put the console there. + <span class="emphasis"><i class="EMPHASIS">This can be + extremely confusing.</i></span></p> + + <p>Most PCI based Alphas can use ordinary PC-type VGA + cards. The SRM contains enough smarts to make that work. + It does not, however, mean that each and every PCI VGA + card out on the street will work in an Alpha machine. + Things like S3 Trio64, Mach64, and Matrox Millennium + generally work. Old ET4000 based ISA cards have also + worked for me. But ask around first before buying.</p> + + <p>Most PCI devices from the PC-world will also work in + FreeBSD PCI-based machines. Check the <tt + class="FILENAME">/sys/alpha/conf/GENERIC</tt> file for + the latest word on this. Check the appropriate machine + type's discussion in case you want to use PCI cards that + have PCI bridge chips on them. In some cases you might + encounter problems with PCI cards not handling PCI parity + correctly. This can lead to panics. PCI parity checking + can be disabled using the following SRM command:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET PCI_PARITY OFF</b></tt> +</pre> + + <p>This is not a FreeBSD problem, all operating systems + running on Alpha hardware will need this workaround.</p> + + <p>If your system (also) contains EISA expansion slots + you will need to run the EISA Configuration Utility (ECU) + after you have installed EISA cards or after you have + upgraded your console firmware.</p> + + <p>For Alpha CPUs you will find multiple generations. The + original Alpha design is the 21064. It was produced in a + chip process called MOS4, chips made in this process are + nicknamed EV4. Newer CPUs are 21164, 21264 etc. You will + see designations like EV4S, EV45, EV5, EV56, EV6, EV67, + EV68. The EVs with double digit numbers are slightly + improved versions. For example EV45 has an improved FPU + and 16 kByte on-chip separate I & D caches compared + to the EV4 on which it is based. Rule of thumb: the + higher the digit immediately following ``EV'' the more + desirable (read: faster / more modern).</p> + + <p>For memory you want at least 32 Mbytes. I have had + FreeBSD run on a 16 Mbyte system but you will not enjoy + that. Kernel build times halved when I went to 32 Mbytes. + Note that the SRM console steals 2Mbyte from the total + system memory (and keeps it). For more serious work 64 + Mbytes or more are recommended.</p> + + <p>While on the subject of memory: pay close attention to + the type of memory your machine uses. There are very + different memory configurations and requirements for the + various machines.</p> + + <p>Final word: I expect the above to sound a bit daunting + to the first-time Alpha user. Don't be daunted too much. + And do feel free to ask questions if something is not + clear after reading this document.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN107" name="AEN107">2.3 + System-specific information</a></h2> + + <p>Below is an overview of the hardware that FreeBSD runs + on. This list will definitely grow, a look in <tt + class="FILENAME">/sys/alpha/conf/GENERIC</tt> can be + enlightening.</p> + + <p>Alpha machines are often best known by their project + code name. Where known these are listed below in + parentheses.</p> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN112" name="AEN112">2.3.1 + AXPpci33 (``NoName'')</a></h3> + + <p>The NoName is a baby-AT mainboard based on the 21066 + LCA (Low Cost Alpha) processor. NoName was originally + designed for OEM-use. The LCA chip includes almost all + of the logic to drive a PCI bus and the memory + subsystem. All of this makes for a low-priced + design.</p> + + <p>Due to the limited memory interface the system is + not particularly fast in case of cache misses. As long + as you stay inside the on-chip cache the CPU is + comparable to a 21064 (first generation Alpha). These + boards should be very cheap to obtain these days. It is + a full-fledged 64 bit CPU, just don't expect miracles + as far as speed goes.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21066 Alpha CPU at 166 MHz or 21066A CPU at + 233MHz. 21068 CPUs are also possible, but are even + slower.</p> + </li> + + <li> + <p>on-board Bcache / L2 cache: 0, 256k or 1 Mbyte + (uses DIL chips)</p> + </li> + + <li> + <p>PS/2 mouse & keyboard port OR 5pin DIN + keyboard (2 mainboard models)</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>bus width: 64 bits</p> + </li> + + <li> + <p>PS/2 style 72 pin 36 bit Fast Page Mode + SIMMs</p> + </li> + + <li> + <p>70ns or better</p> + </li> + + <li> + <p>installed in pairs of 2</p> + </li> + + <li> + <p>4 SIMM sockets</p> + </li> + + <li> + <p>uses ECC</p> + </li> + </ul> + </li> + + <li> + <p>512kB Flash ROM for the console code.</p> + </li> + + <li> + <p>2 16550A serial ports</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>floppy interface</p> + </li> + + <li> + <p>1 embedded IDE interface</p> + </li> + + <li> + <p>expansion:</p> + + <ul> + <li> + <p>3 32 bit PCI slots (1 shared with ISA)</p> + </li> + + <li> + <p>5 ISA slots (1 shared with PCI)</p> + </li> + </ul> + </li> + + <li> + <p>embedded Fast SCSI using a Symbios 53C810 + chip</p> + </li> + </ul> + + <p>NoNames can either have SRM <span + class="emphasis"><i class="EMPHASIS">or</i></span> ARC + console firmware in their Flash ROM. The Flash ROM is + not big enough to hold both ARC and SRM at the same + time and allow software selection of alternate console + code. But you only need SRM anyway.</p> + + <p>Cache for the NoNames are 15 or 20 ns DIL chips. For + a 256 kByte cache you want to check your junked 486 + mainboard. Chips for a 1 Mbyte cache are a rarer breed + unfortunately. Getting at least a 256kByte cache is + recommended performance wise. Cache-less they are + really slow.</p> + + <p>The NoName mainboard has a PC/AT-standard power + connector. It also has a power connector for 3.3 Volts. + No need to rush out to get a new power supply. The 3.3 + Volts is only needed in case you run 3.3 Volts PCI + expansion boards. These are quite rare.</p> + + <p>The IDE interface is supported by FreeBSD and + requires a line in the kernel configuration file as + follows:</p> +<pre class="PROGRAMLISTING"> +device ata +</pre> + + <p>The ATA interface uses irq 14.</p> + + <p>The SRM console unfortunately <span + class="emphasis"><i class="EMPHASIS">cannot + boot</i></span> from IDE disks. This means you will + have to use a SCSI disk as the boot device.</p> + + <p>The NoName is somewhat stubborn when it comes to + serial consoles. It needs</p> +<pre class="SCREEN"> +>>> <tt class="USERINPUT"><b>SET CONSOLE SERIAL</b></tt> +</pre> + + <p>before it goes for a serial console. Pulling the + keyboard from the machine is not sufficient, like it is + on most other Alpha models. Going back to a graphical + console needs</p> +<pre class="SCREEN"> +>>> <tt class="USERINPUT"><b>SET CONSOLE GRAPHICS</b></tt> +</pre> + + <p>at the serial console.</p> + + <p>There have been reports that you sometimes need to + press <b class="KEYCAP">Control</b>-<b + class="KEYCAP">Alt</b>-<b class="KEYCAP">Del</b> to + capture the SRM's attention. I have never seen this + myself, but it is worth trying if you are greeted by a + blank screen after powerup.</p> + + <p>Make sure you use true 36 bit SIMMs, and only FPM + (Fast Page Mode) DRAM. EDO DRAM or SIMMs with fake + parity <span class="emphasis"><i class="EMPHASIS">will + not work</i></span>. The board uses the 4 extra bits + for ECC. 33 bit FPM SIMMs will for the same reason not + work.</p> + + <p>Given the choice, get the PS/2-variant mainboard. + Apart from giving you a mouse port as bonus it is + directly supported by Tru64 Unix in case you ever want + or need to run it. The ``DIN-plug''-variant should work + OK for FreeBSD.</p> + + <p>The <a + href="ftp://ftp.digital.com/pub/DEC/axppci/design_guide.ps" + target="_top">OEM manual</a> is recommended + reading.</p> + + <p>The kernel configuration file for a NoName kernel + must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_AXPPCI_33 +cpu EV4 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN187" name="AEN187">2.3.2 + Universal Desktop Box (UDB or ``Multia'')</a></h3> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Multia can be either Intel or Alpha + CPU based. We assume Alpha based ones here for + obvious reasons.</p> + </blockquote> + </div> + + <p>Multia is a small desktop box intended as a sort of + personal workstation. They come in a considerable + number of variations, check closely what you get.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21066 Alpha CPU at 166 MHz or 21066A CPU at + 233MHz</p> + </li> + + <li> + <p>on-board Bcache / L2 cache: COAST-like 256 kByte + cache module; 233MHz models have 512kByte of cache; + 166MHz models have soldered-on 256kB caches</p> + </li> + + <li> + <p>PS/2 mouse & keyboard port</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>bus width: 64 bits</p> + </li> + + <li> + <p>PS/2 style 72 pin 36 bit Fast Page Mode + SIMMs</p> + </li> + + <li> + <p>70ns or better</p> + </li> + + <li> + <p>SIMMs are installed in pairs of 2</p> + </li> + + <li> + <p>4 SIMM sockets</p> + </li> + + <li> + <p>uses ECC</p> + </li> + </ul> + </li> + + <li> + <p>2 16550A serial ports</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>floppy interface</p> + </li> + + <li> + <p>Intel 82378ZB PCI to ISA bridge</p> + </li> + + <li> + <p>1 embedded 21040 based 10Mbit Ethernet, AUI and + 10base2 connector</p> + </li> + + <li> + <p>expansion:</p> + + <ul> + <li> + <p>1 32 bit PCI slot</p> + </li> + + <li> + <p>2 PCMCIA slots</p> + </li> + </ul> + </li> + + <li> + <p>on-board Crystal CS4231 or AD1848 sound chip</p> + </li> + + <li> + <p>embedded Fast SCSI, using a Symbios 53C810[A] + chip on the PCI riser card</p> + </li> + </ul> + + <p>Multia has enough Flash ROM to store both SRM and + ARC code at the same time and allow software selection + of one of them.</p> + + <p>The embeded TGA video adapter is <span + class="emphasis"><i class="EMPHASIS">not</i></span> + currently usable as a FreeBSD console. You will need to + use a serial console.</p> + + <p>Multia has only one 32 bit PCI slot for expansion, + and it is only suitable for a small form factor PCI + card. By sacrificing the PCI slot space you can mount a + 3.5" hard disk drive. Mounting stuff may have come + with your Multia. Adding a 3.5" disk is <span + class="emphasis"><i class="EMPHASIS">not</i></span> a + recommended upgrade due to the limited power rating of + the power supply and the extremely marginal cooling of + the system box.</p> + + <p>Multia also has 2 PCMCIA expansion slots. These are + currently not supported by FreeBSD.</p> + + <p>The CPU might or might not be socketed, check this + before considering CPU upgrade hacks. The low-end + Multias have a soldered-in CPU.</p> + + <p>Multia has 2 serial ports but routes both of them to + the outside world on a single 25 pin sub-D connector. + The Multia FAQ explains how to build your own Y-cable + to allow both ports to be used.</p> + + <p>Although the Multia SRM supports booting from floppy + this can be problematic. Typically the errors look + like:</p> +<pre class="SCREEN"> +*** Soft Error - Error #10 - FDC: Data overrun or underrun +</pre> + + <p>This is not a FreeBSD problem, it is a SRM problem. + The best available workaround to install FreeBSD is to + boot from a SCSI CDROM.</p> + + <p>There have been reports that you sometimes need to + press <b class="KEYCAP">Control</b>-<b + class="KEYCAP">Alt</b>-<b class="KEYCAP">Del</b> to + capture the SRM's attention. I have never seen this + myself, but it is worth trying when you are greeted by + a blank screen after powerup.</p> + + <p>Sound works fine using <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a> driver + and a line in the kernel configuration file as follows + for the Crystal CS4231 chip:</p> +<pre class="PROGRAMLISTING"> +device pcm +</pre> + + <p>The sound device lives at port 0x530, and uses irq 9 + along with drq 3. You also need to specify flags 0x15 + in the <tt class="FILENAME">device.hints</tt> file.</p> + + <p>I have not yet been successful in getting my Multia + with the AD1848 to play any sound.</p> + + <p>While verifying playback I was reminded of the lack + of CPU power of the 166MHz CPU. MP3 only plays + acceptable using 22kHz down-sampling.</p> + + <p>Multias are somewhat notorious for dying of heat + strokes. The very compact box does not really allow + access to cooling air. Please use the Multia on its + vertical stand, don't put it horizontally (``pizza + style''). Replacing the fan with something which pushes + around more air is really recommended. You can also cut + one of the wires to the fan speed sensor. Once cut, the + fan runs at a (loud) full speed. Beware of PCI cards + with high power consumption. If your system has died + you might want to check the Multia-Heat-Death pages at + the <a href="http://www.netbsd.org/" + target="_top">NetBSD Web site</a> for help in reviving + it.</p> + + <p>The Intel 82378ZB PCI to ISA bridge enables the use + of an IDE disk. This requires a line in the kernel + configuration file as follows:</p> +<pre class="PROGRAMLISTING"> +device ata +</pre> + + <p>The ATA interface uses IRQ 14.</p> + + <p>The IDE connector pin spacing is thought for + 2.5" laptop disks. A 3.5" IDE disk would not + fit in the case anyway. At least not without + sacrificing your only PCI slot. The SRM console + unfortunately does not know how to boot from IDE disks. + You will need to use a SCSI disk as the boot disk.</p> + + <p>In case you want to change the internal hard drive: + the internal flat cable running from the PCI riser + board to the <span class="emphasis"><i + class="EMPHASIS">2.5"</i></span> hard drive has a + finer pitch than the standard SCSI flat cables. + Otherwise it would not fit on the 2.5" drives. + There are also riser cards that have a standard-pitch + SCSI cable attached to it, which will fit an ordinary + SCSI disk.</p> + + <p>Again, I recommend against trying to cram a + replacement hard disk inside. Use the external SCSI + connector and put your disk in an external enclosure. + Multias run hot enough as-is. In most cases you will + have the external high density 50-pin SCSI connector + but some Multia models came without disk and may lack + the connector. Something to check before buying + one.</p> + + <p>The kernel configuration file for a Multia kernel + must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_AXPPCI_33 +cpu EV4 +</pre> + + <p>Recommended reading on Multia can be found at <a + href="http://www.netbsd.org/Ports/alpha/multiafaq.html" + target="_top">http://www.netbsd.org/Ports/alpha/multiafaq.html</a> + or <a + href="http://www.brouhaha.com/~eric/computers/udb.html" + target="_top">http://www.brouhaha.com/~eric/computers/udb.html</a>.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN276" name="AEN276">2.3.3 + Personal Workstation (``Miata'')</a></h3> + + <p>The Miata is a small tower machine intended to be + put under a desk. There are multiple Miata variants. + The original Miata is the MX5 model. Because it suffers + from a number of hardware design flaws a redesign was + done, yielding the MiataGL. Unfortunately the variants + are not easily distinguishable at first sight from the + outside of the case. An easy check is to see if the + back of the machine sports two USB connectors. If yes, + it is a MiataGL. MX5 models tend to be more common in + the used system market place.</p> + + <p>System designations look like ``Personal Workstation + 433a''. Personal Workstation, being a bit of a + mouthful, is often abbreviated to PWS. This means it + has a 433 MHz CPU, and started life as a WinNT + workstation (the trailing ``a''). Systems designated + from day 1 to run Tru64 Unix or OpenVMS will sport + ``433au''. WinNT-Miatas are likely to come + pre-configured with an IDE CDROM drive. So, in general + systems are named like PWS[433,500,600]a[u].</p> + + <p>There was also a Miata model with a special CPU + cooling system by Kryotech. The Kryotech has a special + cooling system and is housed in a different + enclosure.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21164A EV56 Alpha CPU at 433, 500 or 600MHz</p> + </li> + + <li> + <p>21174 core logic (``Pyxis'') chip</p> + </li> + + <li> + <p>on-board Bcache / L3 cache: 0, 2 or 4 Mbytes + (uses a cache module)</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>bus width: 128 bits wide, ECC protected</p> + </li> + + <li> + <p>unbuffered 72 bit wide SDRAMs DIMMs, + installed in pairs of 2</p> + </li> + + <li> + <p>6 DIMM sockets</p> + </li> + + <li> + <p>maximum memory 1.5 GBytes</p> + </li> + </ul> + </li> + + <li> + <p>on-board Fast Ethernet:</p> + + <ul> + <li> + <p>MX5 uses a 21142 or 21143 Ethernet chip, + dependent on the version of the PCI riser + card</p> + </li> + + <li> + <p>MiataGL has a 21143 chip</p> + </li> + + <li> + <p>the bulkhead can be 10/100 Mbit UTP, or 10 + Mbit UTP/BNC</p> + </li> + </ul> + </li> + + <li> + <p>2 on-board [E]IDE disk interfaces, based on the + CMD646 (MX5) or the Cypress 82C693 (MiataGL)</p> + </li> + + <li> + <p>1 Ultra-Wide SCSI Qlogic 1040 [MiataGL only]</p> + </li> + + <li> + <p>2 64-bit PCI slots</p> + </li> + + <li> + <p>3 32-bit PCI slots (behind a DEC PCI-PCI bridge + chip)</p> + </li> + + <li> + <p>3 ISA slots (physically shared with the 32 bit + PCI slots, via an Intel 82378IB PCI to ISA bridge + chip)</p> + </li> + + <li> + <p>2 16550A serial port</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>PS/2 keyboard & mouse port</p> + </li> + + <li> + <p>USB interface [MiataGL only]</p> + </li> + + <li> + <p>embedded sound based on an ESS1888 chip</p> + </li> + </ul> + + <p>The Miata logic is divided into two printed circuit + boards. The lower board in the bottom of the machine + has the PCI and ISA slots and things like the sound + chip etc. The top board has the CPU, the Pyxis chip, + memory etc. Note that MX5 and the MiataGL use a + different PCI riser board. This means that you cannot + just upgrade to a MiataGL CPU board (with the newer + Pyxis chip) but that you will also need a different + riser board. Apparently an MX5 riser with a MiataGL CPU + board will work but it is definitely not a supported or + tested configuration. Everything else (cabinet, wiring, + etc.) is identical for MX5 and MiataGL.</p> + + <p>MX5 has problems with DMA via the 2 64-bit PCI slots + when this DMA crosses a page boundary. The 32 bit slots + don't have this problem because the PCI-PCI bridge chip + does not allow the offending transfers. The SRM code + knows about the problem and refuses to start the system + if there is a PCI card in one of the 64bit slots that + it does not know about. Cards that are ``known good'' + to the SRM are allowed to be used in the 64bit + slots.</p> + + <p>If you want to fool the SRM you can type <tt + class="USERINPUT"><b>set pci_device_override</b></tt> + at the SRM prompt. Just don't complain if your data + mysteriously gets mangled.</p> + + <p>The complete command is:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET PCI_DEVICE_OVERRIDE <tt +class="REPLACEABLE"><i><vendor_id></i></tt><tt +class="REPLACEABLE"><i><device_id></i></tt></b></tt> +</pre> + + <p>For example:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET PCI_DEVICE_OVERRIDE 88c15333</b></tt> +</pre> + + <p>The most radical approach is to use:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET PCI_DEVICE_OVERRIDE -1</b></tt> +</pre> + + <p>This disables PCI ID checking altogether, so that + you can install any PCI card without its ID getting + checked. For this to work you need a reasonable current + SRM version.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Do this on your own risk..</p> + </blockquote> + </div> + + <p>The FreeBSD kernel reports it when it sees a buggy + Pyxis chip:</p> +<pre class="SCREEN"> +Sep 16 18:39:43 miata /kernel: cia0: Pyxis, pass 1 +Sep 16 18:39:43 miata /kernel: cia0: extended capabilities: 1<BWEN> +Sep 16 18:39:43 miata /kernel: cia0: WARNING: Pyxis pass 1 DMA bug; no bets... +</pre> + + <p>A MiataGL probes as:</p> +<pre class="SCREEN"> +Jan 3 12:22:32 miata /kernel: cia0: Pyxis, pass 1 +Jan 3 12:22:32 miata /kernel: cia0: extended capabilities: 1<BWEN> +Jan 3 12:22:32 miata /kernel: pcib0: <2117x PCI host bus adapter> on cia0 +</pre> + + <p>MiataGL does not have the DMA problems of the MX5. + PCI cards that make the MX5 SRM choke when installed in + the 64bit slots are accepted without problems by the + MiataGL SRM.</p> + + <p>The latest mainboard revisions of MX5 contain a + hardware workaround for the bug. The SRM does not know + about the ECO and will complain about unknown cards as + before. So does the FreeBSD kernel by the way.</p> + + <p>The Miata SRM can boot from IDE CDROM drives. IDE + hard disk boot is known to work for both MiataGL and + MX5 disks, so you can root FreeBSD from an IDE disk. + Speeds on MX5 are around 14 Mbytes/sec assuming a + suitable drive. Miata's CMD646 chip will support up to + WDMA2 mode as the chip is too buggy for use with + UDMA.</p> + + <p>Miata MX5s generally use Qlogic 1040 based SCSI + adapters. These are bootable by the SRM console. Note + that Adaptec cards are <span class="emphasis"><i + class="EMPHASIS">not</i></span> bootable by the Miata + SRM console.</p> + + <p>The MiataGL has a faster PCI-PCI bridge chip on the + PCI riser card than some of the MX5 riser card + versions. Some of the MX5 risers have the <span + class="emphasis"><i class="EMPHASIS">same</i></span> + chip as the MiataGL. All in all there is a lot of + variation.</p> + + <p>Not all VGA cards will work behind the PCI-PCI + bridge. This manifests itself as no video at all. + Workaround is to put the VGA card ``before'' the + bridge, in one of the 64 bit PCI slots. Graphics + performance using a 64 bit slot is generally + substantially better.</p> + + <p>Both MX5 and MiataGL have an on-board sound chip, an + ESS1888. It emulates a SoundBlaster and can be enabled + by putting</p> +<pre class="PROGRAMLISTING"> +device pcm +device sbc +</pre> + + <p>in your kernel configuration file:</p> + + <p>in case your Miata has the optional cache board + installed make sure it is firmly seated. A slightly + loose cache has been observed to cause weird crashes + (not surprising obviously, but maybe not so obvious + when troubleshooting). The cache module is identical + between MX5 and MiataGL.</p> + + <p>Installing a 2Mb cache module achieves, apart from a + 10-15% speed increase (based on buildworld elapsed + time), a <span class="emphasis"><i + class="EMPHASIS">decrease</i></span> for PCI DMA read + bandwidth from 64bit PCI cards. A benchmark on a 64-bit + Myrinet card resulted in a decrease from 149 Mbytes/sec + to 115 Mbytes/sec. Something to keep in mind when doing + really high speed things with 64 bit PCI adapters.</p> + + <p>Although the hardware allows you to install up to + 1.5Gbyte of memory, FreeBSD is limited to 1Gbyte + because the DMA code does not correctly handle memory + above 1Gbyte.</p> + + <p>Moving to a faster CPU is quite simple, swap out the + CPU chip and set the clock multiplier dipswitch to the + speed of the new CPU.</p> + + <p>If you experience SRM errors like</p> +<pre class="SCREEN"> +ERROR: scancode 0xa3 not supported on PCXAL +</pre> + + <p>after halting FreeBSD you should update your SRM + firmware to V7.2-1 or later. This SRM version is first + available on the Firmware Update CD V5.7, or on <a + href="http://www.compaq.com/" + target="_top">http://www.compaq.com/</a> This SRM + problem is fixed on both Miata MX5 and Miata GL.</p> + + <p>USB is supported by FreeBSD 4.1 and later.</p> + + <p>Disconnect the power cord before dismantling the + machine, the soft-power switch keeps part of the logic + powered <span class="emphasis"><i + class="EMPHASIS">even</i></span> when the machine is + switched off.</p> + + <p>The kernel configuration file for a Miata kernel + must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_ST550 +cpu EV5 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN386" name="AEN386">2.3.4 + Evaluation Board 64 family</a></h3> + + <p>In its attempts to popularize the Alpha CPU DEC + produced a number of so called Evaluation Boards. + Members of this family are EB64, EB64+, AlphaPC64 + (codename ``Cabriolet''). A non-DEC member of this + family is the Aspen Alpine. The EB64 family of + evaluation boards has the following feature set:</p> + + <ul> + <li> + <p>21064 or 21064A CPU, 150 to 275 MHz</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>memory buswidth: 128 bit</p> + </li> + + <li> + <p>PS/2 style 72 pin 33 bit Fast Page Mode + SIMMs</p> + </li> + + <li> + <p>70ns or better</p> + </li> + + <li> + <p>installed in sets of 4</p> + </li> + + <li> + <p>8 SIMM sockets</p> + </li> + + <li> + <p>uses parity memory</p> + </li> + </ul> + </li> + + <li> + <p>Bcache / L2 cache: 0, 512 kByte, 1 Mbyte or 2 + Mbytes</p> + </li> + + <li> + <p>21072 (``APECS'') chip set</p> + </li> + + <li> + <p>Intel 82378ZB PCI to ISA bridge chip + (``Saturn'')</p> + </li> + + <li> + <p>dual 16550A serial ports</p> + </li> + + <li> + <p>parallel printer port</p> + </li> + + <li> + <p>Symbios 53C810 Fast-SCSI (not on AlphaPC64)</p> + </li> + + <li> + <p>IDE interface (only on AlphaPC64)</p> + </li> + + <li> + <p>embedded 10 Mbit Ethernet (not on AlphaPC64)</p> + </li> + + <li> + <p>2 PCI slots (4 slots on AlphaPC64)</p> + </li> + + <li> + <p>3 ISA slots</p> + </li> + </ul> + + <p>Aspen Alpine is slightly different, but is close + enough to the EB64+ to run an EB64+ SRM EPROM (mine + did..). The Aspen Alpine does not have an embedded + Ethernet, has 3 instead of 2 PCI slots. It comes with 2 + Mbytes of cache already soldered onto the mainboard. It + has jumpers to select the use of 60, 70 or 80ns SIMM + speeds.</p> + + <p>36 bits SIMMs work fine, 3 bits simply remain + unused. Note the systems use Fast Page Mode memory, not + EDO memory.</p> + + <p>The EB64+ SRM console code is housed in an + UV-erasable EPROM. No easy flash SRM upgrades for the + EB64+ The latest SRM version available for EB64+ is + quite ancient anyway.</p> + + <p>The EB64+ SRM can boot both 53C810 and Qlogic1040 + SCSI adapters. Pitfall for the Qlogic is that the + firmware that is down-loaded by the SRM onto the Qlogic + chip is very old. There are no updates for the EB64+ + SRM available. So you are stuck with old Qlogic bits + too. I have had quite some problems when I wanted to + use Ultra-SCSI drives on the Alpine with Qlogic. The + FreeBSD kernel can be compiled to include a much newer + Qlogic firmware revision. This is not the default + because it adds hundreds of kBytes worth of bloat to + the kernel. In FreeBSD 4.1 and later the isp firmware + is contained in a kernel loadable module. All of this + might mean that you need to use a non-Qlogic adapter to + boot from.</p> + + <p>AlphaPC64 boards generally come with ARC console + firmware. SRM console code can be loaded from floppy + into the Flash ROM.</p> + + <p>The IDE interface of the AlphaPC64 is not bootable + from the SRM console. Enabling it requires the + following line in the kernel configuration file:</p> +<pre class="PROGRAMLISTING"> +device ata +</pre> + + <p>The ATA interface uses irq 14.</p> + + <p>Note that the boards require a power supply that + supplies 3.3 Volts for the CPU.</p> + + <p>For the EB64 family machines the kernel config file + must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_EB64PLUS +cpu EV4 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN441" name="AEN441">2.3.5 + Evaluation Board 164 (``EB164, PC164, PC164LX, + PC164SX'') family</a></h3> + + <p>EB164 is a newer design evaluation board, based on + the 21164A CPU. This design has been used to ``spin + off'' multiple variations, some of which are used by + OEM manufacturers/assembly shops. Samsung did its own + PC164LX which has only 32 bit PCI, whereas the Digital + variant has 64 bit PCI.</p> + + <ul> + <li> + <p>21164A, multiple speed variants [EB164, PC164, + PC164LX]</p> + </li> + + <li> + <p>21164PC [only on PC164SX]</p> + </li> + + <li> + <p>21171 (Alcor) chip set [EB164]</p> + + <p>21172 (Alcor2) chip set [PC164]</p> + + <p>21174 (Pyxis) chip [164LX, 164SX]</p> + </li> + + <li> + <p>Bcache / L3 cache: EB164 uses special + cache-SIMMs</p> + </li> + + <li> + <p>memory bus: 128 bit / 256 bit</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>PS/2 style SIMMs in sets of 4 or 8</p> + </li> + + <li> + <p>36 bit, Fast Page Mode, uses ECC, [EB164 / + PC164]</p> + </li> + + <li> + <p>SDRAM DIMMs in sets of 2, uses ECC [PC164SX + / PC164LX]</p> + </li> + </ul> + </li> + + <li> + <p>2 16550A serial ports</p> + </li> + + <li> + <p>PS/2 style keyboard & mouse</p> + </li> + + <li> + <p>floppy controller</p> + </li> + + <li> + <p>parallel port</p> + </li> + + <li> + <p>32 bits PCI</p> + </li> + + <li> + <p>64 bits PCI [some models]</p> + </li> + + <li> + <p>ISA slots via an Intel 82378ZB PCI to ISA bridge + chip</p> + </li> + </ul> + + <p>Using 8 SIMMs for a 256bit wide memory can yield + interesting speedups over a 4 SIMM/128bit wide memory. + Obviously all 8 SIMMs must be of the same type to make + this work. The system must be explicitly setup to use + the 8 SIMM memory arrangement. You must have 8 SIMMs, 4 + SIMMs distributed over 2 banks will not work. For the + AlphaPC164 you can have a maximum of 1Gbyte of RAM, + using 8 128Mbyte SIMMs. The manual indicates the + maximum is 512 Mbyte.</p> + + <p>The SRM can boot from Qlogic 10xx boards or the + Symbios 53C810[A]. Newer Symbios 810 revisions like the + Symbios 810AE are not recognized by the SRM on PC164. + PC164 SRM does not appear to recognize a Symbios 53C895 + based host adapter (tested with a Tekram DC-390U2W). On + the other hand some no-name Symbios 53C985 board has + been reported to work. Cards like the Tekram DC-390F + (Symbios875 based) have been confirmed to work fine on + the PC164. Unfortunately this seems to be dependent on + the actual version of the chip/board.</p> + + <p>Symbios 53C825[a] will also work as boot adapter. + Diamond FirePort, although based on Symbios chips, is + not bootable by the PC164SX SRM. PC164SX is reported to + boot fine with Symbios825, Symbios875, Symbios895 and + Symbios876 based cards. In addition, Adaptec 2940U and + 2940UW are reported to work for booting (verified on + SRM V5.7-1). Adaptec 2930U2 and 2940U2[W] do not + work.</p> + + <p>164LX and 164SX with SRM firmware version 5.8 or + later can boot from Adaptec 2940-series adapters.</p> + + <p>In summary: this family of machines is ``blessed'' + with a challenging compatibility as far as SCSI + adapters go.</p> + + <p>On 164SX you can have a maximum of 1 Gbyte of RAM. 4 + regular 256MB PC133 ECC DIMMs are reported to work just + fine. Whether 512MB DIMMs will also work is currently + unknown.</p> + + <p>PCI bridge chips are sometimes not appreciated by + the 164SX, they cause SRM errors and kernel panics in + those cases. This seems to depend on the fact if the + card is recognised, and therefore correctly + initialised, by the SRM console. The 164SX' onboard IDE + interface is quite slow, a Promise card gives a 3-4 + times speed improvement.</p> + + <p>On PC164 the SRM sometimes seems to lose its + variable settings. ``For PC164, current superstition + says that, to avoid losing settings, you want to first + downgrade to SRM 4.x and then upgrade to 5.x.'' One + sample error that was observed was:</p> +<pre class="SCREEN"> +ERROR: ISA table corrupt! +</pre> + + <p>A sequence of a downgrade to SRM4.9, an</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>ISACFG -INIT</b></tt> +</pre> + + <p>followed by</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>INIT</b></tt> +</pre> + + <p>made the problem go away. Some PC164 owners report + they have never seen the problem.</p> + + <p>On PC164SX the AlphaBIOS allows you a selection to + select SRM to be used as console on the next power up. + This selection does not appear to have any effect. In + other words, you will get the AlphaBIOS regardless of + what you select. The fix is to reflash the console ROM + with the SRM code for PC164SX. This will overwrite the + AlphaBIOS and will get you the SRM console you desire. + The SRM code can be found on the Compaq Web site.</p> + + <p>164LX can either have the SRM console code or the + AlphaBIOS code in its flash ROM because the flash ROM + is too small to hold both at the same time.</p> + + <p>PC164 can boot from IDE disks assuming your SRM + version is recent enough.</p> + + <p>EB164 needs a power supply that supplies 3.3 Volts. + PC164 does not implement the PS_ON signal that ATX + power supplies need to switch on. A simple switch + pulling this signal to ground allows you to run a + standard ATX power supply.</p> + + <p>For the EB164 class machines the kernel config file + must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_EB164 +cpu EV5 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN508" name="AEN508">2.3.6 + AlphaStation 200 (``Mustang'') and 400 (``Avanti'') + series</a></h3> + + <p>The Digital AlphaStation 200 and 400 series systems + are early low end PCI based workstations. The 200 and + 250 series are desktop boxes, the 400 series is a + desk-side mini-tower.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21064 or 21064A CPU at speeds of 166 up to 333 + MHz</p> + </li> + + <li> + <p>DECchip 21071-AA core logic chip set</p> + </li> + + <li> + <p>Bcache / L2 cache: 512 Kbytes (200 and 400 + series) or 2048KBytes (250 series)</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>64 bit bus width</p> + </li> + + <li> + <p>8 to 384 MBytes of RAM</p> + </li> + + <li> + <p>70 ns or better Fast Page DRAM</p> + </li> + + <li> + <p>in three pairs (200 and 400 series)</p> + </li> + + <li> + <p>in two quads, so banks of four. (250 + series)</p> + </li> + + <li> + <p>the memory subsystem uses parity</p> + </li> + </ul> + </li> + + <li> + <p>PS/2 keyboard and mouse port</p> + </li> + + <li> + <p>two 16550 serial ports</p> + </li> + + <li> + <p>parallel port</p> + </li> + + <li> + <p>floppy disk interface</p> + </li> + + <li> + <p>32 bit PCI expansion slots (3 for the + AS400-series, 2 for the AS200 & 250-series)</p> + </li> + + <li> + <p>ISA expansion slots (4 for the AS400-series, 2 + for the AS200 & 250-series) (some ISA/PCI slots + are physically shared)</p> + </li> + + <li> + <p>embedded 21040-based Ethernet (200 & 250 + series)</p> + </li> + + <li> + <p>embedded Symbios 53c810 Fast SCSI-2 chip</p> + </li> + + <li> + <p>Intel 82378IB (``Saturn'') PCI-ISA bridge + chip</p> + </li> + + <li> + <p>graphics is embedded TGA or PCI VGA (model + dependent)</p> + </li> + + <li> + <p>16 bit sound (on 200 & 250 series)</p> + </li> + </ul> + + <p>The systems use parity memory SIMMs, but these do + not need 36 bit wide SIMMs. 33 bit wide SIMMs are + sufficient, 36 bit SIMMs are acceptable too. EDO or 32 + bit SIMMs will not work. 4, 8, 16, 32 and 64 Mbyte + SIMMs are supported.</p> + + <p>The AS200 & AS250 sound hardware is reported to + work OK assuming you have the following line in your + kernel config file:</p> +<pre class="PROGRAMLISTING"> +device pcm +</pre> + + <p>The sound device uses port 0x530, IRQ 10 and drq 0. + You also need to specify flags 0x10011 in the <tt + class="FILENAME">device.hints</tt> file.</p> + + <p>AlphaStation 200 & 250 series have an automatic + SCSI terminator. This means that as soon as you plug a + cable onto the external SCSI connector the internal + terminator of the system is disabled. It also means + that you should not leave unterminated cables plugged + into the machine.</p> + + <p>AlphaStation 400 series have an SRM variable that + controls termination. In case you have external SCSI + devices connected you must set this SRM variable + using</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET CONTROL_SCSI_TERM EXTERNAL</b></tt>. +</pre> + + <p>If only internal SCSI devices are present use:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET CONTROL_SCSI_TERM INTERNAL</b></tt> +</pre> + + <p>For the AlphaStation-[24][05]00 machines the kernel + config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_2100_A50 +cpu EV4 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN575" name="AEN575">2.3.7 + AlphaStation 500 and 600 (``Alcor'' & ``Maverick'' + for EV5, ``Bret'' for EV56)</a></h3> + + <p>AS500 and 600 were the high-end EV5 / PCI based + workstations. EV6 based machines have in the meantime + taken their place as front runners. AS500 is a desktop + in a dark blue case (TopGun blue), AS600 is a sturdy + desk-side box. AS600 has a nice LCD panel to observe + the early stages of SRM startup.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21164 EV5 CPU at 266, 300, 333, 366, 400, 433, + 466, or 500 MHz (AS500) or at 266, 300 or 333 MHz + (AS600)</p> + </li> + + <li> + <p>21171 (Alcor) or 21172 (Alcor2) core logic chip + set</p> + </li> + + <li> + <p>Cache:</p> + + <ul> + <li> + <p>2 or 4 Mb L3 / Bcache (AS600 at 266 MHz)</p> + </li> + + <li> + <p>4 Mb L3 / Bcache (AS600 at 300 MHz)</p> + </li> + + <li> + <p>2 or 8 Mb L3 / Bcache (8 Mb on 500 MHz + version only)</p> + </li> + + <li> + <p>2 to 16 Mb L3 / Bcache (AS600; 3 cache-SIMM + slots)</p> + </li> + </ul> + </li> + + <li> + <p>memory buswidth: 256 bits</p> + </li> + + <li> + <p>AS500 memory:</p> + + <ul> + <li> + <p>industry standard 72 bit wide buffered Fast + Page Mode DIMMs</p> + </li> + + <li> + <p>8 DIMM slots</p> + </li> + + <li> + <p>installed in sets of 4</p> + </li> + + <li> + <p>maximum memory is 1 GB (512 Mb max on 333 + MHz CPUs)</p> + </li> + + <li> + <p>uses ECC</p> + </li> + </ul> + </li> + + <li> + <p>AS600 memory:</p> + + <ul> + <li> + <p>industry standard 36 bit Fast Page Mode + SIMMs</p> + </li> + + <li> + <p>32 SIMM slots</p> + </li> + + <li> + <p>installed in sets of 8</p> + </li> + + <li> + <p>maximum memory is 1 GB</p> + </li> + + <li> + <p>uses ECC</p> + </li> + </ul> + </li> + + <li> + <p>Qlogic 1020 based wide SCSI bus (1 bus/chip for + AS500, 2 buses/chip for AS600)</p> + </li> + + <li> + <p>21040 based 10 Mbit Ethernet adapter, both + Thinwire and UTP connectors</p> + </li> + + <li> + <p>expansion:</p> + + <ul> + <li> + <p>AS500:</p> + + <ul> + <li> + <p>3 32-bit PCI slots</p> + </li> + + <li> + <p>1 64-bit PCI slot</p> + </li> + </ul> + </li> + + <li> + <p>AS600:</p> + + <ul> + <li> + <p>2 32-bit PCI slot</p> + </li> + + <li> + <p>3 64-bit PCI slots</p> + </li> + + <li> + <p>1 PCI/EISA physically shared slot</p> + </li> + + <li> + <p>3 EISA slots</p> + </li> + + <li> + <p>1 PCI and 1 EISA slot are occupied by + default</p> + </li> + </ul> + </li> + </ul> + </li> + + <li> + <p>21050 PCI-to-PCI bridge chip</p> + </li> + + <li> + <p>Intel 82375EB PCI-EISA bridge (AS600 only)</p> + </li> + + <li> + <p>2 16550A serial ports</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>16 bit audio Windows Sound System, in a + dedicated slot (AS500) in EISA slot (AS600, this is + an ISA card)</p> + </li> + + <li> + <p>PS/2 keyboard and mouse port</p> + </li> + </ul> + + <p>Early machines had Fast SCSI interfaces, later ones + are Ultra SCSI capable. AS500 shares its single SCSI + bus with internal and external devices. For a Fast SCSI + bus you are limited to 1.8 meters bus length external + to the box. The AS500 Qlogic ISP1020A chip can be set + to run in Ultra mode by setting a SRM variable. FreeBSD + however follows the Qlogic chip errata and limits the + bus speed to Fast.</p> + + <p>Beware of ancient SRM versions on AS500. When you + see weird SCSI speeds being reported by FreeBSD + like</p> +<pre class="PROGRAMLISTING"> +cd0 at isp0 bus 0 target 4 lun 0 +cd0: <DEC RRD45 DEC 0436> Removable CD-ROM SCSI-2 device +cd0: 250.000MB/s transfers (250.000MHz, offset 12) +</pre> + + <p>it is time to do a SRM console firmware upgrade.</p> + + <p>AS600 has one Qlogic SCSI chip dedicated to the + internal devices whereas the other Qlogic SCSI chip is + dedicated to external SCSI devices.</p> + + <p>In AS500 DIMMs are installed in sets of 4, in + ``physically interleaved'' layout. So, a bank of 4 + DIMMs is <span class="emphasis"><i + class="EMPHASIS">not</i></span> 4 physically adjacent + DIMMs. Note that the DIMMs are <span + class="emphasis"><i class="EMPHASIS">not</i></span> + SDRAM DIMMs.</p> + + <p>In AS600 the memory SIMMs are placed onto two memory + daughter cards. SIMMs are installed in sets of 8. Both + memory daughter cards must be populated + identically.</p> + + <p>Note that both AS500 and AS600 are EISA machines. + This means you have to run the EISA Configuration + Utility (ECU) from floppy after adding EISA cards or to + change things like the configuration settings of the + onboard I/O. For AS500 which does not have a physical + EISA slot the ECU is used to configure the onboard + sound interface etc.</p> + + <p>AS500 onboard sound can be used by adding a line + like</p> +<pre class="PROGRAMLISTING"> +device pcm +</pre> + + <p>to the kernel configuration file.</p> + + <p>Using the ECU I configured my AS500 to use IRQ 10, + port 0x530, drq 0. Corresponding entries along with + flags 0x10011 must go into the <tt + class="FILENAME">device.hints</tt> file. Note that the + flags value is rather non-standard.</p> + + <p>AS600 has a peculiarity for its PCI slots. AS600 (or + rather the PCI expansion card containing the SCSI + adapters) does not allow I/O port mapping, therefore + all devices behind it must use memory mapping. If you + have problems getting the Qlogic SCSI adapters to work, + add the following option to <tt + class="FILENAME">/boot/loader.rc</tt>:</p> +<pre class="PROGRAMLISTING"> +set isp_mem_map=0xff +</pre> + + <p>This may need to be typed at the boot loader prompt + before booting the installation kernel.</p> + + <p>For the AlphaStation-[56]00 machines the kernel + config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_KN20AA +cpu EV5 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN687" name="AEN687">2.3.8 + AlphaServer 1000 (``Mikasa''), 1000A (``Noritake'') and + 800(``Corelle'')</a></h3> + + <p>The AlphaServer 1000 and 800 range of machines are + intended as departmental servers. They come in quite + some variations in packaging and mainboard/cpu. + Generally speaking there are 21064 (EV4) CPU based + machines and 21164 (EV5) based ones. The CPU is on a + daughter card, and the type of CPU (EV4 or EV5) must + match the mainboard in use.</p> + + <p>AlphaServer 800 has a much smaller mini tower case, + it lacks the StorageWorks SCSI hot-plug chassis. The + main difference between AS1000 and AS1000A is that + AS1000A has 7 PCI slots whereas AS1000 only has 3 PCI + slots and has EISA slots instead.</p> + + <p>AS800 with an EV5/400 MHz CPU was later re-branded + to become a ``DIGITAL Server 3300[R]'', AS800 with an + EV5/500 MHz CPU was later re-branded to become a + ``DIGITAL Server 3305[R]''.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21064 EV4[5] CPU at 200, 233 or 266 MHz 21164 + EV5[6] CPU at 300, 333 or 400 MHz (or 500 MHz for + AS800 only)</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>buswidth: 128 bit with ECC</p> + </li> + + <li> + <p>AS1000[A]:</p> + + <ul> + <li> + <p>72pin 36 bit Fast Page Mode SIMMs, 70ns + or better</p> + </li> + + <li> + <p>16 (EV5 machines) or 20 (EV4 machines) + SIMM slots</p> + </li> + + <li> + <p>max memory is 1 GB</p> + </li> + + <li> + <p>uses ECC</p> + </li> + </ul> + </li> + + <li> + <p>AS800: Uses 60ns 3.3 Volts EDO DIMMs</p> + </li> + </ul> + </li> + + <li> + <p>embedded VGA (on some mainboard models)</p> + </li> + + <li> + <p>3 PCI, 2 EISA, 1 64-bit PCI/EISA combo + (AS800)</p> + </li> + + <li> + <p>7 PCI, 2 EISA (AS1000A)</p> + </li> + + <li> + <p>2 PCI, 1 EISA/PCI, 7 EISA (AS1000)</p> + </li> + + <li> + <p>embedded SCSI based on Symbios 810 [AS1000] or + Qlogic 1020 [AS1000A]</p> + </li> + </ul> + + <p>AS1000 based machines come in multiple enclosure + types. Floor standing, rack-mount, with or without + StorageWorks SCSI chassis etc. The electronics are the + same.</p> + + <p>AS1000-systems: All EV4 based machines use standard + PS/2 style 36 bit 72pin SIMMs in sets of 5. The fifth + SIMM is used for ECC. All EV5 based machines use + standard PS/2 style 36 bit 72pin SIMMs in sets of 4. + The ECC is done based on the 4 extra bits per SIMM (4 + bits out of 36). The EV5 mainboards have 16 SIMM slots, + the EV4 mainboards have 20 slots.</p> + + <p>AS800 machines use DIMMs in sets of 4. DIMM + installation must start in slots marked bank 0. A bank + is four physically adjacent slots. The biggest size + DIMMs must be installed in bank 0 in case 2 banks of + different DIMM sizes are used. Max memory size is 2GB. + Note that these are EDO DIMMs.</p> + + <p>The AS1000/800 are somewhat stubborn when it comes + to serial consoles. They need</p> +<pre class="SCREEN"> +>>> <tt class="USERINPUT"><b>SET CONSOLE SERIAL</b></tt> +</pre> + + <p>before they go for a serial console. Pulling the + keyboard from the machine is not sufficient, like it is + on most other Alpha models. Going back to a graphical + console needs</p> +<pre class="SCREEN"> +>>> <tt class="USERINPUT"><b>SET CONSOLE GRAPHICS</b></tt> +</pre> + + <p>at the serial console.</p> + + <p>For AS800 you want to check if your Ultra-Wide SCSI + is indeed in Ultra mode. This can be done using the <tt + class="FILENAME">EEROMCFG.EXE</tt> utility that is on + the Console Firmware Upgrade CDROM.</p> + + <p>For the AlphaServer1000/1000A/800 machines the + kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_1000A +cpu EV4 # depends on the CPU model installed +cpu EV5 # depends on the CPU model installed +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN743" name="AEN743">2.3.9 + DS10/VS10/XP900 (``Webbrick'') / XP1000 (``Monet'') / + DS10L (``Slate'')</a></h3> + + <p>Webbrick and Monet are high performance + workstations/servers based on the EV6 CPU and the + Tsunami chipset. Tsunami is also used in much + higher-end systems and as such has plenty of + performance to offer. DS10, VS10 and XP900 are + different names for essentially the same system. The + differences are the software and options that are + supported. DS10L is a DS10 based machine in a 1U high + rackmount enclosure. DS10L is intended for ISPs and for + HPTC clusters (e.g. Beowulf)</p> + + <div class="SECT4"> + <hr /> + + <h4 class="SECT4"><a id="AEN749" + name="AEN749">2.3.9.1 ``Webbrick / Slate''</a></h4> + + <ul> + <li> + <p>21264 EV6 CPU at 466 MHz</p> + </li> + + <li> + <p>L2 / Bcache: 2MB, ECC protected</p> + </li> + + <li> + <p>memory bus: 128 bit via crossbar, 1.3GB/sec + memory bandwidth</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>industry standard 200 pin 83 MHz buffered + ECC SDRAM DIMMs</p> + </li> + + <li> + <p>4 DIMM slots for DS10; 2GB max memory</p> + </li> + + <li> + <p>2 DIMM slots for DS10L; 1GB max memory</p> + </li> + + <li> + <p>DIMMs are installed in pairs of 2</p> + </li> + </ul> + </li> + + <li> + <p>21271 Core Logic chipset (``Tsunami'')</p> + </li> + + <li> + <p>2 on-board 21143 Fast Ethernet controllers</p> + </li> + + <li> + <p>AcerLabs M5237 (Aladdin-V) USB controller + (disabled)</p> + </li> + + <li> + <p>AcerLabs M1533 PCI-ISA bridge</p> + </li> + + <li> + <p>AcerLabs Aladdin ATA-33 controller</p> + </li> + + <li> + <p>embedded dual EIDE</p> + </li> + + <li> + <p>expansion: 3 64-bit PCI slots and 1 32-bit PCI + slot. DS10L has a single 64bit PCI slot</p> + </li> + + <li> + <p>2 16550A serial ports</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>2 USB</p> + </li> + + <li> + <p>PS/2 keyboard & mouse port</p> + </li> + </ul> + + <p>The system has a smart power controller. This + means that parts of the system remain powered when it + is switched off (like an ATX-style PC power supply). + Before servicing the machine remove the power + cord.</p> + + <p>The smart power controller is called the RMC. When + enabled, typing <b class="KEYCAP">Escape</b><b + class="KEYCAP">Escape</b>RMC on serial port 1 will + bring you to the RMC prompt. RMC allows you to + powerup or powerdown, reset the machine, monitor and + set temperature trip levels etc. RMC has its own + builtin help.</p> + + <p>Webbrick is shipped in a desktop-style case + similar to the older 21164 ``Maverick'' workstations + but this case offers much better access to the + components. If you intend to build a farm you can + rackmount them in a 19-inch rack; they are 3U high. + Slate is 1U high but has only one PCI slot.</p> + + <p>DS10 has 4 DIMM slots. DIMMs are installed as + pairs. Please note that DIMM pairs are not installed + in adjacent DIMM sockets but rather physically + interleaved. DIMM sizes of 32, 64, 128, 256 and 512 + Mbytes are supported.</p> + + <p>When 2 pairs of identical-sized DIMMs are + installed DS10 will use memory interleaving for + increased performance. DS10L, which has only 2 DIMM + slots cannot do interleaving.</p> + + <p>Starting with SRM firmware version 5.9 you can + boot from Adaptec 2940-series adapters in addition to + the usual set of Qlogic and Symbios/NCR adapters.</p> + + <p>The base model comes with a FUJITSU 9.5GB ATA disk + as its boot device. FreeBSD works just fine using + EIDE disks on Webbrick. DS10 has 2 IDE interfaces on + the mainboard. Machines destined for Tru64 Unix or + VMS are standard equipped with Qlogic-driven + Ultra-SCSI disks</p> + + <p>On the PCI bus 32 and 64 bit cards are supported, + in 3.3V and 5V variants.</p> + + <p>The USB ports are not supported and are disabled + by the SRM console in all recent SRM versions.</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_ST6600 +cpu EV5 +</pre> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Contrary to expectation there is + no <tt class="LITERAL">cpu EV6</tt> defined for + inclusion in the kernel config file. The <tt + class="LITERAL">cpu EV5</tt> is mandatory to keep + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> + happy.</p> + </blockquote> + </div> + </div> + + <div class="SECT4"> + <hr /> + + <h4 class="SECT4"><a id="AEN814" + name="AEN814">2.3.9.2 ``Monet''</a></h4> + + <ul> + <li> + <p>21264 EV6 at 500 MHz 21264 EV67 at 500 or 667 + MHz (XP1000G, codenamed Brisbane) CPU is mounted + on a daughter-card which is field-upgradable</p> + </li> + + <li> + <p>L2 / Bcache: 4MB, ECC protected</p> + </li> + + <li> + <p>memory bus: 256 bit</p> + </li> + + <li> + <p>memory: 128 or 256 Mbytes 100 MHz (PC100) 168 + pin JEDEC standard, registered ECC SDRAM + DIMMs</p> + </li> + + <li> + <p>21271 core logic chip set (``Tsunami'')</p> + </li> + + <li> + <p>1 on-board 21143 Ethernet controller</p> + </li> + + <li> + <p>Cypress 82C693 USB controller</p> + </li> + + <li> + <p>Cypress 82C693 PCI-ISA bridge</p> + </li> + + <li> + <p>Cypress 82C693 controller</p> + </li> + + <li> + <p>expansion: 2 independent PCI buses, driven by + high-speed I/O channels called ``hoses'':</p> + + <ul> + <li> + <p>hose 0: (the upper 3 slots) 2 64-bit PCI + slots 1 32-bit PCI slot</p> + </li> + + <li> + <p>hose 1: (the bottom 2 slots) 2 32-bit PCI + slots (behind a 21154 PCI-PCI bridge)</p> + </li> + + <li> + <p>2 of the 64-bit PCI slots are for + full-length cards</p> + </li> + + <li> + <p>all of the 32-bit PCI slots are for short + cards</p> + </li> + + <li> + <p>1 of the 32-bit PCI slots is physically + shared with an ISA slot</p> + </li> + + <li> + <p>all PCI slots run at 33MHz</p> + </li> + </ul> + </li> + + <li> + <p>1 Ultra-Wide SCSI port based on a Qlogic 1040 + chip</p> + </li> + + <li> + <p>2 16550A serial port</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>PS/2 keyboard & mouse port</p> + </li> + + <li> + <p>embedded 16-bit ESS ES1888 sound chip</p> + </li> + + <li> + <p>2 USB ports</p> + </li> + + <li> + <p>graphics options: ELSA Gloria Synergy or + DEC/Compaq PowerStorm 3D accelerator cards</p> + </li> + </ul> + + <p>Monet is housed in a mini-tower like enclosure + quite similar to the Miata box.</p> + + <p>The on-board Qlogic UW-SCSI chip supports up to 4 + internal devices. There is no external connector for + the on-board SCSI.</p> + + <p>For 500 MHz CPUs 83 MHz DIMMs will do. Compaq + specifies PC100 DIMMs for all CPU speeds. DIMMs are + installed in sets of 4, starting with the DIMM slots + marked ``0'' Memory capacity is max 4 GB. DIMMs are + installed ``physically interleaved'', note the + markings of the slots. Memory bandwidth of Monet is + twice that of Webbrick. The DIMMs live on the CPU + daughter-card. Note that the system uses ECC RAM so + you need DIMMs with 72 bits (not the generic PC-class + 64 bit DIMMs)</p> + + <p>The EIDE interface is usable / SRM bootable so + FreeBSD can be rooted on an EIDE disk. Although the + Cypress chip has potential for 2 EIDE channels Monet + uses only one of them.</p> + + <p>The USB interface is supported by FreeBSD.If you + experience problems trying to use the USB interface + please check if the SRM variable <tt + class="VARNAME">usb_enable</tt> is set to <tt + class="LITERAL">on</tt>. You can change this by + performing:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET USB_ENABLE ON</b></tt> +</pre> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Don"t try to use + Symbios-chip based SCSI adapters in the PCI slots + connected to hose 1. There is a not-yet-found + FreeBSD bug that prevents this from working + correctly.</p> + </blockquote> + </div> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Not all VGA cards will work + behind the PCI-PCI bridge (so in slots 4 and 5). + Only cards that implement VGA-legacy addressing + correctly will work. Workaround is to put the VGA + card ``before'' the bridge.</p> + </blockquote> + </div> + + <p>The sound chip is not currently supported with + FreeBSD.</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_ST6600 +cpu EV5 +</pre> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Contrary to expectation there is + no <tt class="LITERAL">cpu EV6</tt> defined for + inclusion in the kernel config file. The <tt + class="LITERAL">cpu EV5</tt> is mandatory to keep + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> + happy.</p> + </blockquote> + </div> + </div> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN894" name="AEN894">2.3.10 + DS20/DS20E (``Goldrush'')</a></h3> + + <p>Features:</p> + + <ul> + <li> + <p>21264 EV6 CPU at 500 or 670 MHz</p> + </li> + + <li> + <p>dual CPU capable machine</p> + </li> + + <li> + <p>L2 / Bcache: 4 Mbytes per CPU</p> + </li> + + <li> + <p>memory bus: dual 256 bit wide with crossbar + switch</p> + </li> + + <li> + <p>memory:</p> + + <ul> + <li> + <p>SDRAM DIMMs</p> + </li> + + <li> + <p>installed in sets of 4</p> + </li> + + <li> + <p>16 DIMM slots, max. 4GB</p> + </li> + + <li> + <p>uses ECC</p> + </li> + </ul> + </li> + + <li> + <p>21271 core logic chip set (``Tsunami'')</p> + </li> + + <li> + <p>embedded Adaptec ? Wide Ultra SCSI</p> + </li> + + <li> + <p>expansion:</p> + + <ul> + <li> + <p>2 independent PCI buses, driven by + high-speed I/O channels called ``hoses''</p> + </li> + + <li> + <p>6 64-bit PCI slots, 3 per hose</p> + </li> + + <li> + <p>1 ISA slot</p> + </li> + </ul> + </li> + </ul> + + <p>DS20 needs</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET CONSOLE SERIAL</b></tt> +</pre> + + <p>before it goes for a serial console. Pulling the + keyboard from the machine is not sufficient. Going back + to a graphical console needs</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET CONSOLE GRAPHICS</b></tt> +</pre> + + <p>at the serial console. Confusing is the fact that + you will get SRM console output on the graphics console + with the console set to serial, but when FreeBSD boots + it honors the <tt class="LITERAL">CONSOLE</tt> variable + setting and all the boot messages as well as the login + prompt will go to the serial port.</p> + + <p>The DS20 is housed in a fat cube-like enclosure. The + enclosure also contains a StorageWorks SCSI hot-swap + shelf for a maximum of seven 3.5" SCSI devices. + The DS20E is in a sleeker case, and lacks the + StorageWorks shelf.</p> + + <p>The system has a smart power controller. This means + that parts of the system remain powered when it is + switched off (like an ATX-style PC power supply). + Before servicing the machine remove the power + cord(s).</p> + + <p>The smart power controller is called the RMC. When + enabled, typing <b class="KEYCAP">Escape</b><b + class="KEYCAP">Escape</b>RMC on serial port 1 will + bring you to the RMC prompt. RMC allows you to powerup + or powerdown, reset the machine, monitor and set + temperature trip levels etc. RMC has its own builtin + help.</p> + + <p>The embedded Adaptec SCSI chip on the DS20 is + disabled and is therefore not usable under FreeBSD.</p> + + <p>Starting with SRM firmware version 5.9 you can boot + from Adaptec 2940-series adapters in addition to the + usual set of Qlogic and Symbios/NCR adapters. This + unfortunately does not include the embedded Adaptec + SCSI chips.</p> + + <p>If you are using banks of DIMMs of different sizes + the biggest DIMMs should be installed in the DIMM slots + marked <tt class="LITERAL">0</tt> on the mainboard. The + DIMM slots should be filled ``in order'' so after bank + 0 install in bank 1 and so on.</p> + + <p>Don't try to use Symbios-chip based SCSI adapters in + the PCI slots connected to hose 1. There is a + not-yet-found FreeBSD bug that prevents this from + working correctly. DS20 ships by default with a Symbios + on hose 1 so you have to move this card before you can + install/boot FreeBSD on it.</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_ST6600 +cpu EV5 +</pre> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Contrary to expectation there is no + <tt class="LITERAL">cpu EV6</tt> defined for + inclusion in the kernel config file. The <tt + class="LITERAL">cpu EV5</tt> is mandatory to keep + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> + happy.</p> + </blockquote> + </div> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN963" name="AEN963">2.3.11 + AlphaPC 264DP / UP2000</a></h3> + + <p>UP2000 is built by Alpha Processor Inc.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21264 EV6 CPU at 670 MHz</p> + </li> + + <li> + <p>dual CPU capable</p> + </li> + + <li> + <p>L2 / Bcache: 4 Mbytes per CPU</p> + </li> + + <li> + <p>memory bus: 256 bit</p> + </li> + + <li> + <p>memory: SDRAM DIMMs installed in sets of 4, uses + ECC, 16 DIMM slots, max. 4GB</p> + </li> + + <li> + <p>21272 core logic chip set (``Tsunami'')</p> + </li> + + <li> + <p>embedded Adaptec AIC7890/91 Wide Ultra SCSI</p> + </li> + + <li> + <p>2 embedded IDE based on Cypress 82C693 chips</p> + </li> + + <li> + <p>embedded USB via Cypress 82C693</p> + </li> + + <li> + <p>expansion:</p> + + <ul> + <li> + <p>2 independent PCI buses, driven by + high-speed I/O channels called ``hoses''</p> + </li> + + <li> + <p>6 64-bit PCI slots, 3 per hose</p> + </li> + + <li> + <p>1 ISA slot</p> + </li> + </ul> + </li> + </ul> + + <p>Currently a maximum of 2GB memory is supported by + FreeBSD.</p> + + <p>The on-board Adaptec is not bootable but works with + FreeBSD 4.0 and later as a datadisk-only SCSI bus.</p> + + <p>Busmaster DMA is supported on the first IDE + interface only.</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_ST6600 +cpu EV5 +</pre> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Contrary to expectation there is no + <tt class="LITERAL">cpu EV6</tt> defined for + inclusion in the kernel config file. The <tt + class="LITERAL">cpu EV5</tt> is mandatory to keep + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> + happy.</p> + </blockquote> + </div> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN1009" name="AEN1009">2.3.12 + AlphaServer 2000 (``DemiSable''), 2100 (``Sable''), + 2100A (``Lynx'')</a></h3> + + <p>The AlphaServer 2[01]00 machines are intended as + departmental servers. This is medium iron. They are + multi-CPU machines, up to 2 CPUs (AS2000) or 4 CPUs + (2100[A]) can be installed. Both floor-standing and + 19" rackmount boxes exist. Rackmount variations + have different numbers of I/O expansion slots, + different max number of CPUs and different maximum + memory size. Some of the boxes come with an integral + StorageWorks shelf to house hot-swap SCSI disks. There + was an upgrade program available to convert your Sable + machine into a Lynx by swapping the I/O backplane (the + C-bus backplane remains). CPU upgrades were available + as well.</p> + + <ul> + <li> + <p>21064 EV4[5] CPU[s] at 200, 233, 275 MHz or + 21164 EV5[6] CPU[s]s at 250, 300, 375, 400 MHz</p> + </li> + + <li> + <p>cache: varies in size with the CPU model; 1, 4 + or 8Mbyte per CPU</p> + </li> + + <li> + <p>embedded floppy controller driving a 2.88 Mbytes + drive</p> + </li> + + <li> + <p>embedded 10Mbit 21040 Ethernet [AS2100 only]</p> + </li> + + <li> + <p>2 serial ports</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>PS/2 style keyboard & mouse port</p> + </li> + </ul> + + <p>The CPUs spec-ed as 200 MHz are in reality running + at 190 MHz. Maximum number of CPUs is 4. All CPUs must + be of the same type/speed.</p> + + <p>If any of the processors are ever marked as failed, + they will remain marked as failed even after they have + been replaced (or reseated) until you issue the + command</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>CLEAR_ERROR ALL</b></tt> +</pre> + + <p>on the SRM console and power-cycle the machine. This + may be true for other modules (IO and memory) as well, + but it has not been verified.</p> + + <p>The machines use dedicated memory boards. These + boards live on a 128 bit C-bus shared with the CPU + boards. DemiSable supports up to 1GB, Sable up to 2GB. + One of the memory bus slots can either hold a CPU or a + memory card. A 4 CPU machine can have a maximum of 2 + memory boards.</p> + + <p>Some memory board models house SIMMs. These are + called SIMM carriers. There are also memory modules + that have soldered-on memory chips instead of SIMMs. + These are called ``flat memory modules''.</p> + + <p>SIMM boards are used in sets of eight 72-pin 36 bit + FPM memory of 70ns or faster. SIMM types supported are + 1M x36 bit (4 Mbyte), 2M x36bit (8 Mbyte) and 4M x36 + bit (16 Mbyte). Each memory board can house 4 banks of + SIMMs. SIMM sizes can not be mixed on a single memory + board. The first memory module must be filled with + SIMMs before starting to fill the next memory module. + Note that the spacing between the slots is not that + big, so make sure your SIMMs fit physically (before + buying them..)</p> + + <p>Both Lynx and Sable are somewhat stubborn when it + comes to serial consoles. They need</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET CONSOLE SERIAL</b></tt> +</pre> + + <p>before they go for a serial console. Pulling the + keyboard from the machine is not sufficient, like it is + on many other Alpha models. Going back to a graphical + console needs</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET CONSOLE GRAPHICS</b></tt> +</pre> + + <p>at the serial console. On Lynx keep the VGA card in + one of the primary PCI slots. EISA VGA cards are not + slot sensitive.</p> + + <p>The machines are equipped with a small OCP (Operator + Control Panel) LCD screen. On this screen the self-test + messages are displayed during system initialization. + You can put your own little text there by using the + SRM:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET OCP_TEXT "FreeBSD" + </b></tt> +</pre> + + <p>The SRM</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SHOW FRU</b></tt> +</pre> + + <p>command produces an overview of your configuration + with module serial numbers, hardware revisions and + error log counts.</p> + + <p>Both Sable, DemiSable and Lynx have Symbios 810 + based Fast SCSI on-board. Check if it is set to Fast + SCSI speed by</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SHOW PKA0_FAST</b></tt> +</pre> + + <p>When set to 1 it is negotiating for Fast speeds.</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>SET PKA0_FAST 1</b></tt> +</pre> + + <p>enables Fast SCSI speeds.</p> + + <p>AS2100[A] come equipped with a StorageWorks 7 slot + SCSI cage. A second cage can be added inside the + cabinet. AS2000 has a single 7 slot SCSI cage, which + cannot be expanded with an additional one. Note that + the slot locations in these cages map differently to + SCSI IDs compared to the standard StorageWorks shelves. + Slot IDs from top to bottom are 0, 4, 1, 5, 2, 6, 3 + when using a single bus configuration.</p> + + <p>The cage can also be set to provide two independent + SCSI buses. This is used for embedded RAID controllers + like the KZPSC (Mylex DAC960). Slot ID assignments for + split bus are, from top to bottom: 0A, 0B, 1A, 1B, 2A, + 2B, 3A, 3B. Where A and B signify a SCSI bus. In a + single bus configuration the terminator module on the + back of the SCSI cage is on the TOP. The jumper module + is on the BOTTOM. For split bus operation these two + modules are reversed. The terminator can be + distinguished from the jumper by noting the chips on + the terminator. The jumper does not have any active + components on it.</p> + + <p>DemiSable has 7 EISA slots and 3 PCI slots. Sable + has 8 EISA and 3 PCI slots. Lynx, being newer, has 8 + PCI and 3 EISA slots. The Lynx PCI slots are grouped in + sets of 4. The 4 PCI slots closest to the CPU/memory + slots are the primary slots, so logically before the + PCI bridge chip. Note that contrary to expectation the + primary PCI slots are the highest numbered ones (PCI4 - + PCI7).</p> + + <p>Make sure you run the EISA Configuration Utility + (from floppy) when adding/change expansion cards in + EISA slots or after upgrading your console firmware. + This is done by inserting the ECU floppy and typing</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>RUNECU</b></tt> +</pre> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> EISA slots are currently + unsupported, but the Compaq Qvision EISA VGA + adapter is treated as an ISA device. It therefore + works OK as a console.</p> + </blockquote> + </div> + + <p>A special Extended I/O module for use on the C-bus + was planned-for. If they ever saw daylight is unknown. + In any case FreeBSD has never been verified with an + ExtIO module.</p> + + <p>The machines can be equipped with redundant power + supplies. Note that the enclosure is equipped with + interlock switches that switch off power when the + enclosure is opened. The system's cooling fans are + speed controlled. When the machine has more than 2 CPUs + and more than 1 memory board dual power supplies are + mandatory.</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_2100_A500 +cpu EV4 #dependent on CPU model installed +cpu EV5 #dependent on CPU model installed +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN1080" name="AEN1080">2.3.13 + AlphaServer 4x00 (``Rawhide'')</a></h3> + + <p>The AlphaServer 4x00 machines are intended as small + enterprise servers. Expect a 30" high pedestal + cabinet or alternatively the same system box in a + 19" rack. Rawhides are multi-CPU machines, up to 4 + CPUs can be in a single machine. Basic disk storage is + housed in one or two StorageWorks shelves at the bottom + of the pedestal. The Rawhides intended for the NT + market are designated DIGITAL Server 7300 (5/400 CPU), + DIGITAL Server 7305 (5/533 CPU). A trailing R on the + part-number means a rackmount variant.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21164 EV5 CPUs at 266, 300, 333 MHz or 21164A + EV56 CPUs at 400, 466, 533, 600 Mhz</p> + </li> + + <li> + <p>cache: 4 Mbytes per CPU. EV5 300 MHz was also + available cache-less. 8 Mbytes for EV56 600Mhz</p> + </li> + + <li> + <p>memory bus: 128 bit with ECC</p> + </li> + + <li> + <p>embedded floppy controller</p> + </li> + + <li> + <p>2 serial ports</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>PS/2 style keyboard & mouse port</p> + </li> + </ul> + + <p>Rawhide can be equipped with a variety of CPU + modules. CPU modules exist in versions with and without + external cache. In all cases the CPU modules installed + always must be of the same speed. A mix of NT-only and + full-blown Tru64/VMS CPUs works fine. It will however + result in the system reporting itself to the operating + system as a Digital Server 730x (so the NT-only + variant). FreeBSD does not care, but such a system will + not allow Tru64 or VMS to run.</p> + + <p>Rawhide uses a maximum of 8 RAM modules. These + modules are used in pairs and supply 72 bits to the bus + (this includes ECC bits). Memory can be EDO RAM or + synchronous DRAM. A fully populated AS4100 has 4 pairs + of memory modules. The AS4000 model is limited to 2 + pairs of memory modules. Given the choice use SDRAM for + best performance. The highest capacity memory boards + must be in the memory slots marked MEM0L and MEM0H. A + mix of memory board sizes is allowed. A mix of EDO and + SDRAM works as well (assuming you don't try to mix EDO + and SDRAM in a single module pair). A mix of EDO and + SDRAM results in the <span class="emphasis"><i + class="EMPHASIS">entire</i></span> memory subsystem + running at the slower EDO timing.</p> + + <p>Rawhide has an embedded Symbios 810 chip that gives + you a narrow fast-SCSI bus. Generally only the SCSI + CDROM is driven by this interface.</p> + + <p>Rawhides are available with a 8 64-bit PCI / 3 EISA + slot expansion backplanes (called ``Saddle'' modules). + There are 2 separate PCI buses, PCI0 and PCI1. PCI0 has + 1 dedicated PCI slot and (shared) 3 PCI/EISA slots. + PCI0 also has a PCI/EISA bridge that drives things like + the serial and parallel ports, keyboard/mouse etc. PCI1 + has 4 PCI slots and a Symbios 810 SCSI chip. VGA + console cards must be installed in a slot connected to + PCI0.</p> + + <p>The current FreeBSD implementation has problems in + handling PCI bridges. There is currently a limited fix + in place which allows for single level, single device + PCI bridges. The fix allows the use of the Digital + supplied Qlogic SCSI card which sits behind a 21054 PCI + bridge chip.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> EISA slots are currently + unsupported, but the Compaq Qvision EISA VGA + adapter is treated as an ISA device. It therefore + works as a console. In case you use EISA options in + your machine you must run the EISA Configuration + Utility (ECU) from floppy. Do yourself a favor and + use the Tru64/OpenVMS ECU, and not the WindowsNT + ECU.</p> + </blockquote> + </div> + + <p>Rawhide employs an I2C based power controller + system. If you want to be sure all power is removed + from the system remove all mains cables from the + system.</p> + + <p>Rawhide comes with RCM functionality, which means + you can power it on/off remotely, reset it etc. See + also the description for RMC in the DS10 section of + this document. RCM versus RMC is not a typo, the + various documentation I consulted used both acronyms + interchangably.</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_KN300 +cpu EV5 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN1113" name="AEN1113">2.3.14 + AlphaServer 1200 (``Tincup'') and AlphaStation 1200 + (``DaVinci'')</a></h3> + + <p>The AlphaServer 1200 machine is the successor to the + AlphaServer 1000A. It uses the same enclosure the 1000A + uses, but the logic is based on the AlphaServer 4000 + design. These are multi-CPU machines, up to 2 CPUs can + be in a single machine. Basic disk storage is housed in + a StorageWorks shelves The AS1200 intended for the NT + market were designated DIGITAL Server 5300 (5/400 CPU) + and DIGITAL Server 5305 (5/533 CPU).</p> + + <p>Features:</p> + + <ul> + <li> + <p>21164A EV56 CPUs at 400 or 533 Mhz</p> + </li> + + <li> + <p>cache: 4 Mbytes per CPU</p> + </li> + + <li> + <p>memory bus: 128 bit with ECC, DIMM memory on two + memory daughter boards</p> + </li> + + <li> + <p>embedded floppy controller</p> + </li> + + <li> + <p>2 serial ports</p> + </li> + + <li> + <p>1 parallel port</p> + </li> + + <li> + <p>PS/2 style keyboard & mouse port</p> + </li> + </ul> + + <p>AS1200 uses 2 memory daughter cards. On each of + these cards are 8 DIMM slots. DIMMs must be installed + in pairs. The maximum memory size is 4 GBytes. Slots + must be filled in order and slot 0 must contain the + largest size DIMM if different sized DIMMs are used. + AS1200 employs fixed starting addresses for DIMMs, each + DIMM pair starts at a 512 Mbyte boundary. This means + that if DIMMs smaller than 256 Mbyte are used the + system's physical memory map will contain ``holes''. + Supported DIMM sizes are 64 Mbytes and 256 Mbytes. The + DIMMs are 72 bit SDRAM based, as the system employs + ECC.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> FreeBSD currently supports up to + 2GBytes</p> + </blockquote> + </div> + + <p>AS1200 has an embedded Symbios 810 drive Fast SCSI + bus.</p> + + <p>Tincup has 5 64-bit PCI slots, one 1 32-bit PCI slot + and one EISA slot (which is physically shared with one + of the 64-bit PCI slots). There are 2 separate PCI + buses, PCI0 and PCI1. PCI0 has the 32-bit PCI slot and + the 2 top-most 64-bit PCI slots. PCI0 also has an Intel + 82375EB PCI/EISA bridge that drives things like the + serial and parallel ports, keyboard/mouse etc. PCI1 has + 4 64-bit PCI slots and a Symbios 810 SCSI chip. VGA + console cards must be installed in a slot connected to + PCI0.</p> + + <p>The system employs an I2C based power controller + system. If you want to be sure all power is removed + from the system remove the mains cables from the + system. Tincup uses dual power supplies in load-sharing + mode and not as a redundancy pair.</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_KN300 +cpu EV5 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN1143" name="AEN1143">2.3.15 + AlphaServer 8200 and 8400 (``TurboLaser'')</a></h3> + + <p>The AlphaServer 8200 and 8400 machines are + enterprise servers. Expect a tall 19" cabinet + (8200) or fat (8400) 19" rack. This is big iron, + not a hobbyist system. TurboLasers are multi-CPU + machines, up to 12 CPUs can be in a single machine. The + TurboLaser System Bus (TLSB) allows 9 nodes on the + AS8400 and 5 nodes on the AS8200. TLSB is 256 bit data, + 40 bit address allowing 2.1 GBytes/sec. Nodes on the + TLSB can be CPUs, memory or I/O. A maximum of 3 I/O + ports are supported on a TLSB.</p> + + <p>Basic disk storage is housed in a StorageWorks + shelf. AS8400 uses 3 phase power, AS8200 uses single + phase power.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21164 EV5/EV56 CPUs at up to 467 MHz or 21264 + EV67 CPUs at up to 625 MHz</p> + </li> + + <li> + <p>one or two CPUs per CPU module</p> + </li> + + <li> + <p>cache: 4Mbytes B-cache per CPU</p> + </li> + + <li> + <p>memory bus: 256 bit with ECC</p> + </li> + + <li> + <p>memory: big memory modules that plug into the + TLSB, which in turn hold special SIMM modules. + Memory modules come in varying sizes, up to 4 + GBytes a piece. Uses ECC (8 bits per 64 bits of + data) 7 memory modules max for AS8400, 3 modules + max for AS8200. Maximum memory is 28 GBytes.</p> + </li> + + <li> + <p>expansion: 3 system ``I/O ports'' that allow up + to 12 I/O channels each I/O channel can connect to + XMI, Futurebus+ or PCI boxes</p> + </li> + </ul> + + <p>FreeBSD supports (and has been tested with) up to 2 + GBytes of memory on TurboLaser. There is a trade-off to + be made between TLSB slots occupied by memory modules + and TLSB slots occupied by CPU modules. For example you + can have 28GBytes of memory but only 2 CPUs (1 module) + at the same time.</p> + + <p>Only PCI expansion is supported on FreeBSD. XMI or + Futurebus+ (which are AS8400 only) are both + unsupported.</p> + + <p>The I/O port modules are designated KFTIA or KFTHA. + The I/O port modules supply so called ``hoses'' that + connect to up to 4 (KFTHA) PCI buses or 1 PCI bus + (KFTIA). KFTIA has embedded dual 10baseT Ethernet, + single FDDI, 3 SCSI Fast Wide Differential SCSI buses + and a single Fast Wide Single Ended SCSI bus. The FWSE + SCSI is intended for the CDROM.</p> + + <p>KFTHA can drive via each of its 4 hoses a DWLPA or + DWLPB box. The DWLPx house a 12 slots 32 bit PCI + backplane. Physically the 12 slots are 3 4-slot buses + but to the software it appears as a single 12 slots PCI + bus. A fully expanded AS8x00 can have 3 (I/O ports) + times 4 (hoses) times 12 (PCI slots/DWLPx) = 144 PCI + slots. The maximum bandwidth per KFTHA is 500 + Mbytes/second. DWLPA can also house 8 EISA cards, 2 + slots are PCI-only, 2 slots are EISA only. Of the 12 + slots 2 are always occupied by an I/O and connector + module. DWLPB are the prefered I/O boxes.</p> + + <p>For best performance distribute high bandwidth + (FibreChannel, Gigabit Ethernet) over multiple hoses + and/or multiple KFTHA/KFTIA.</p> + + <p>Currently PCI expansion cards containing PCI bridges + are not usable with FreeBSD. Don't use them at this + time.</p> + + <p>The single ended narrow SCSI bus on the KFTIA will + turn up as the <span class="emphasis"><i + class="EMPHASIS">fourth</i></span> SCSI bus. The 3 + fast-wide differential SCSI buses of the KFTIA precede + it.</p> + + <p>AS8x00 are generally run with serial consoles. Some + newer machines might have a graphical console of some + sorts but FreeBSD has only been tested on a serial + console.</p> + + <p>For serial console usage either change <tt + class="FILENAME">/etc/ttys</tt> to have:</p> +<pre class="PROGRAMLISTING"> +console "/usr/libexec/getty std.9600" unknown on secure +</pre> + + <p>as the console entry, or add</p> +<pre class="PROGRAMLISTING"> +zs0 "/usr/libexec/getty std.9600" unknown on secure +</pre> + + <p>For the AlphaServer 8x00 machines the kernel config + file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_KN8AE # Alpha 8200/8400 (Turbolaser) +cpu EV5 +</pre> + + <p>Contrary to expectation there is no <tt + class="LITERAL">cpu EV6</tt> defined for inclusion in + the kernel config file. The <tt class="LITERAL">cpu + EV5</tt> is mandatory to keep <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> + happy.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN1186" name="AEN1186">2.3.16 + Alpha Processor Inc. UP1000</a></h3> + + <p>The UP1000 is an ATX mainboard based on the 21264a + CPU which itself lives in a Slot B module. It is + normally housed in an ATX tower enclosure.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21264a Alpha CPU at 600 or 700 MHz in a Slot B + module (includes cooling fans)</p> + </li> + + <li> + <p>memory bus: 128 bits to the L2 cache, 64 bits + from Slot B to the AMD-751</p> + </li> + + <li> + <p>on-board Bcache / L2 cache: 2MB (600Mhz) or 4MB + (700Mhz)</p> + </li> + + <li> + <p>AMD AMD-751 (``Irongate'') system controller + chip</p> + </li> + + <li> + <p>Acer Labs M1543C PCI-ISA bridge controller / + super-IO chip</p> + </li> + + <li> + <p>PS/2 mouse & keyboard port</p> + </li> + + <li> + <p>memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 + DIMM slots DIMM sizes supported are 64, 128 or 256 + Mb in size</p> + </li> + + <li> + <p>2 16550A serial port</p> + </li> + + <li> + <p>1 ECP/EPP parallel port</p> + </li> + + <li> + <p>floppy interface</p> + </li> + + <li> + <p>2 embedded Ultra DMA33 IDE interface</p> + </li> + + <li> + <p>2 USB ports</p> + </li> + + <li> + <p>expansion:</p> + + <ul> + <li> + <p>4 32 bit PCI slots</p> + </li> + + <li> + <p>2 ISA slots</p> + </li> + + <li> + <p>1 AGP slot</p> + </li> + </ul> + </li> + </ul> + + <p>Slot B is a box-like enclosure that houses a + daughter-board for the CPU and cache. It has 2 small + fans for cooling. Loud fans..</p> + + <p>The machine needs ECC capable DIMMs, so 72 bit ones. + This does not appear to be documented in the UP1000 + docs. The system accesses the serial EEPROM on the + DIMMs via the SM bus. Note that if only a single DIMM + is used it must be installed in slot <span + class="emphasis"><i class="EMPHASIS">2</i></span>. This + is a bit counter-intuitive.</p> + + <p>The UP1000 needs a 400Watt ATX power supply + according to the manufacturer. This might be a bit + overly conservative/pessimistic judging from the power + consumption of the board & cpu. But as always you + will have to take your expansion cards and peripherals + into account. The M1543C chip contains power management + functionality & temperature monitoring (via I2C / + SM bus).</p> + + <p>Chances are that your UP1000 comes by default with + AlphaBios only. The SRM console firmware is available + from the Alpha Processor Inc. web site. It is currently + available in a beta version which was successfully used + during the port of FreeBSD to the UP1000.</p> + + <p>The embedded Ultra DMA EIDE ports are bootable by + the SRM console.</p> + + <p>UP1000 SRM can boot off an Adaptec 294x adapter. + Under high I/O load conditions machine lockups have + been observed using the Adaptec 294x. A Symbios 875 + based card works just fine, using the sym driver. Most + likely other cards based on the Symbios chips that the + sym driver supports will work as well.</p> + + <p>The USB interfaces are disabled by the SRM console + and have not (yet) been tested with FreeBSD.</p> + + <p>For the UP1000 the kernel config file must + contain:</p> +<pre class="PROGRAMLISTING"> +options API_UP1000 # UP1000, UP1100 (Nautilus) +cpu EV5 +</pre> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN1235" name="AEN1235">2.3.17 + Alpha Processor Inc. UP1100</a></h3> + + <p>The UP1100 is an ATX mainboard based on the 21264a + CPU running at 600 MHz. It is normally housed in an ATX + tower enclosure.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21264a Alpha EV6 CPU at 600 or 700 MHz</p> + </li> + + <li> + <p>memory bus: 100MHz 64-bit (PC-100 SDRAM), 800 + MB/s memory bandwidth</p> + </li> + + <li> + <p>on-board Bcache / L2 cache: 2Mb</p> + </li> + + <li> + <p>AMD AMD-751 (``Irongate'') system controller + chip</p> + </li> + + <li> + <p>Acer Labs M1535D PCI-ISA bridge controller / + super-IO chip</p> + </li> + + <li> + <p>PS/2 mouse & keyboard port</p> + </li> + + <li> + <p>memory: 168-pin PC100 unbuffered SDRAM DIMMS, 3 + DIMM slots DIMM sizes supported are 64, 128 or 256 + Mb in size</p> + </li> + + <li> + <p>2 16550A serial port</p> + </li> + + <li> + <p>1 ECP/EPP parallel port</p> + </li> + + <li> + <p>floppy interface</p> + </li> + + <li> + <p>2 embedded Ultra DMA66 IDE interface</p> + </li> + + <li> + <p>2 USB port</p> + </li> + + <li> + <p>expansion: 3 32 bit PCI slots and 1 AGP2x + slot</p> + </li> + </ul> + + <p>SRM console code comes standard with the UP1100. The + SRM lives in 2Mbytes of flash ROM.</p> + + <p>The machine needs ECC capable DIMMs, so 72 bit ones. + This does not appear to be documented in the UP1100 + docs. The system accesses the serial EEPROM on the + DIMMs via the SM bus. Note that if only a single DIMM + is used it must be installed in slot <span + class="emphasis"><i class="EMPHASIS">2</i></span>. This + is a bit counter-intuitive.</p> + + <p>The UP1100 needs a 400Watt ATX power supply + according to the manufacturer. This might be a bit + overly conservative/pessimistic judging from the power + consumption of the board & cpu. But as always you + will have to take your expansion cards and peripherals + into account. The M1535D chip contains power management + functionality & temperature monitoring (via I2C / + SM bus using a LM75 thermal sensor).</p> + + <p>The UP1100 has an on-board 21143 10/100Mbit Ethernet + interface.</p> + + <p>The UP1100 is equipped with a SoundBlaster + compatible audio interface. Whether it works with + FreeBSD is as of yet unknown.</p> + + <p>The embedded Ultra DMA EIDE ports are bootable by + the SRM console.</p> + + <p>The UP1100 has 3 USB ports, 2 going external and one + connected to the AGP port.</p> + + <p>For the UP1100 the kernel config file must + contain:</p> +<pre class="PROGRAMLISTING"> +options API_UP1000 # UP1000, UP1100 (Nautilus) +cpu EV5 +</pre> + + <p>Contrary to expectation there is no <tt + class="LITERAL">cpu EV6</tt> defined for inclusion in + the kernel config file. The <tt class="LITERAL">cpu + EV5</tt> is mandatory to keep <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> + happy.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN1283" name="AEN1283">2.3.18 + Alpha Processor Inc. CS20, Compaq DS20L</a></h3> + + <p>The CS20 is a 19", 1U high rackmount server + based on the 21264[ab] CPU. It can have a maximum of 2 + CPUs. Compaq sells the CS20 rebranded as the + AlphaServer DS20L. DS20L has 833MHz CPUs.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21264a Alpha CPU at 667 MHz or 21264b 833 MHz + (max. 2 CPUs)</p> + </li> + + <li> + <p>memory bus: 100MHz 256-bit wide</p> + </li> + + <li> + <p>21271 Core Logic chipset (``Tsunami'')</p> + </li> + + <li> + <p>Acer Labs M1533 PCI-ISA bridge controller / + super-IO chip</p> + </li> + + <li> + <p>PS/2 mouse & keyboard port</p> + </li> + + <li> + <p>memory: 168-pin PC100 PLL buffered/registered + SDRAM DIMMS, 8 DIMM slots, uses ECC memory, min 256 + Mbytes / max 2 GBytes of memory</p> + </li> + + <li> + <p>2 16550A serial port</p> + </li> + + <li> + <p>1 ECP/EPP parallel port</p> + </li> + + <li> + <p>ALI M1543C Ultra DMA66 IDE interface</p> + </li> + + <li> + <p>embedded dual Intel 82559 10/100Mbit + Ethernet</p> + </li> + + <li> + <p>embedded Symbios 53C1000 Ultra160 SCSI + controller</p> + </li> + + <li> + <p>expansion: 2 64 bit PCI slots (2/3 length)</p> + </li> + </ul> + + <p>SRM console code comes standard with the CS20. The + SRM lives in 2Mbytes of flash ROM.</p> + + <p>The CS20 needs ECC capable DIMMs. Note that it uses + <span class="emphasis"><i + class="EMPHASIS">buffered</i></span> DIMMs.</p> + + <p>The CS20 has an I2C based internal monitoring system + for things like temperature, fans, voltages etc. The + I2C also supports ``wake on LAN''.</p> + + <p>Each PCI slot is connected to its own independent + PCI bus on the Tsunami.</p> + + <p>The embedded Ultra DMA EIDE ports are bootable by + the SRM console.</p> + + <p>The CS20 has an embedded slim-line IDE CD drive. + There is a front-accessible bay for a 1" high + 3.5" SCSI hard-disk drive with SCA connector.</p> + + <p>Note that there is no floppy disk drive (or a + connector to add one).</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_ST6600 +cpu EV5 +</pre> + + <p>Contrary to expectation there is no <tt + class="LITERAL">cpu EV6</tt> defined for inclusion in + the kernel config file. The <tt class="LITERAL">cpu + EV5</tt> is mandatory to keep <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> + happy.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN1330" name="AEN1330">2.3.19 + Compaq AlphaServer ES40 (``Clipper'')</a></h3> + + <p>The ES40 is a SMP system that can have 1 - 4 21264 + Alpha CPUs. With the maximum configuration of 32GB of + memory these systems are often deployed as heavy + database servers and are also found in HPTC compute + farm environments.</p> + + <p>Features:</p> + + <ul> + <li> + <p>21264 Alpha CPU at 500 (EV6), 667 (EV67) or 833 + MHz (EV68) (max. 4 CPUs)</p> + </li> + + <li> + <p>memory bus: 256-bit wide</p> + </li> + + <li> + <p>21272 Core Logic chipset</p> + </li> + + <li> + <p>PS/2 mouse & keyboard port</p> + </li> + + <li> + <p>memory: 200-pin JEDEC standard SDRAM DIMMS, max + 32 GBytes of memory</p> + </li> + + <li> + <p>2 16550A serial port</p> + </li> + + <li> + <p>1 ECP/EPP parallel port</p> + </li> + + <li> + <p>ALI M1543C Ultra DMA66 IDE interface</p> + </li> + + <li> + <p>expansion: 2 64 bit PCI buses</p> + </li> + </ul> + + <p>SRM console code comes standard with the ES40.</p> + + <p>ES40 comes with an ATA CDROM drive, but uses SCSI + harddisks.</p> + + <p>Memory is divided in 4 memory arrays which each + contain a set of 4 SDRAM DIMMs. Each DIMM is 72 bit + wide and of the 100MHz speed variant. An array can + contain 2 sets, so 8 DIMMs max per array. The DIMMs + live on Memory Mother Boards (MMBs). There are 2 MMB + models, with 4 and 8 DIMM sockets respectively. Each + MMB provides half of the 256 bit memory bus width to + the CPUs. Given the myriad options for the memory + configuration it is advisable to check the system + documentation for the optimum memory configuration.</p> + + <p>Dependent on the model variation the ES40 has 6 or + 10 64 bit PCI slots. This is basically just means the + same backplane with less connectors mounted.</p> + + <p>ES40 has the same RMC remote power control as DS10 + and DS20. See the description of the RMC in the DS10 + section of this document. Most variations of ES40 have + multiple power supplies, allowing for N+1 redundancy. + When installing CPU cards you must unplug all power + cords, the CPU cards receive standby power from the + power supplies. Maximum memory configurations need more + than the default number of powersupplies.</p> + + <p>The kernel config file must contain:</p> +<pre class="PROGRAMLISTING"> +options DEC_ST6600 +cpu EV5 +</pre> + + <p>Contrary to expectation there is no <tt + class="LITERAL">cpu EV6</tt> defined for inclusion in + the kernel config file. The <tt class="LITERAL">cpu + EV5</tt> is mandatory to keep <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> + happy.</p> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1367" name="AEN1367">2.4 + Supported Hardware Overview</a></h2> + + <p>A word of caution: the installed base for FreeBSD 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 alpha + 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 Alpha only.</p> + + <p>The PCI and ISA expansion busses are fully supported. + Turbo Channel is not in <tt class="FILENAME">GENERIC</tt> + and has limited support (see the relevant machine model + info). The MCA bus is not supported. The EISA bus is not + supported for use with EISA expansion cards as the EISA + support code is lacking. ISA cards in EISA slots are + reported to work. The Compaq Qvision EISA VGA card is + driven in ISA mode and works OK as a console.</p> + + <p>1.44 Mbyte and 1.2 Mbyte floppy drives are supported. + 2.88 Mbyte drives sometimes found in Alpha machines are + supported up to 1.44Mbyte.</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.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + framework. As most people run their Alphas with SCSI + disks it is not as well tested as SCSI. Be aware of + boot-ability restrictions for IDE disks. See the machine + specific information.</p> + + <p>There is full SCSI support via the CAM layer for + Adaptec 2940x (AIC7xxx chip-based), Qlogic family and + Symbios. Be aware of the machine-specific boot-ability + issues for the various adapter types.</p> + + <p>The Qlogic QL2x00 FibreChannel host adapters are fully + supported.</p> + + <p>If you want to boot your Alpha over the Ethernet you + will obviously need an Ethernet card that the SRM console + recognizes. This generally means you need a board with an + 21x4x Ethernet chip as that is what Digital used. These + chips are driven by the FreeBSD <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">de</span>(4)</span></a> (older + driver) or <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> (newer + driver). Some new SRM versions are known to recognize the + Intel 8255x Ethernet chips as driven by the FreeBSD <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span></a> driver. + But beware: the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span></a> driver is + reported not to work correctly with FreeBSD (although it + works excellently on FreeBSD/x86).</p> + + <p>DEC DEFPA PCI FDDI network adapters are supported on + alpha.</p> + + <p>In general the SRM console emulates a + VGA-compatibility mode on PCI VGA cards. This is, + however, not guaranteed to work by Compaq/DEC for each + and every card type out there. When the SRM thinks the + VGA is acceptable FreeBSD will be able to use it. The + console driver works just like on a FreeBSD/intel + machine. Please note that VESA modes are not supported on + Alpha, so that leaves you with 80x25 consoles.</p> + + <p>In some Alpha machines you will find video adapters + based on TGA chips. The plain TGA adapter does not + emulate VGA and is therefore not usable for a FreeBSD + console. TGA2 cards have a basic VGA compatibility mode + and work fine as FreeBSD consoles.</p> + + <p>The ``PC standard'' serial ports found on most Alphas + are supported.</p> + + <p>ISDN (i4b) is not supported on FreeBSD/alpha.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1399" name="AEN1399">2.5 + Acknowledgments</a></h2> + + <p>In compiling this file I used multiple information + sources, but <a href="http://www.netbsd.org/" + target="_top">the NetBSD Web site</a> proved to be an + invaluable source of information. If it wasn't for + NetBSD/alpha there probably would not be a FreeBSD/alpha + in the first place.</p> + + <p>People who kindly helped me create this section:</p> + + <ul> + <li> + <p>Andrew Gallatin <tt class="EMAIL"><<a + href="mailto:gallatin@FreeBSD.org">gallatin@FreeBSD.org</a>></tt></p> + </li> + + <li> + <p>Chuck Robey <tt class="EMAIL"><<a + href="mailto:chuckr@FreeBSD.org">chuckr@FreeBSD.org</a>></tt></p> + </li> + + <li> + <p>Matthew Jacob <tt class="EMAIL"><<a + href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>></tt></p> + </li> + + <li> + <p>Michael Smith <tt class="EMAIL"><<a + href="mailto:msmith@FreeBSD.org">msmith@FreeBSD.org</a>></tt></p> + </li> + + <li> + <p>David O'Brien <tt class="EMAIL"><<a + href="mailto:obrien@FreeBSD.org">obrien@FreeBSD.org</a>></tt></p> + </li> + + <li> + <p>Christian Weisgerber</p> + </li> + + <li> + <p>Kazutaka YOKOTA</p> + </li> + + <li> + <p>Nick Maniscalco</p> + </li> + + <li> + <p>Eric Schnoebelen</p> + </li> + + <li> + <p>Peter van Dijk</p> + </li> + + <li> + <p>Peter Jeremy</p> + </li> + + <li> + <p>Dolf de Waal</p> + </li> + + <li> + <p>Wim Lemmers, ex-Compaq</p> + </li> + + <li> + <p>Wouter Brackman, Compaq</p> + </li> + + <li> + <p>Lodewijk van den Berg, Compaq</p> + </li> + </ul> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 + Supported Devices</a></h1> + $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.157 2003/05/30 11:24:00 nyan Exp $ + + <p>This section describes the devices currently known to be + supported by with FreeBSD on the Alpha/AXP 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 id="AEN1446" name="AEN1446">3.1 Disk + Controllers</a></h2> + + <p>IDE/ATA controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6</p> + </li> + + <li> + <p>AMD 756 ATA66, 766 ATA100, 768 ATA100</p> + </li> + + <li> + <p>Cenatek Rocket Drive</p> + </li> + + <li> + <p>CMD 646, 648 ATA66, and 649 ATA100</p> + </li> + + <li> + <p>Cypress 82C693</p> + </li> + + <li> + <p>Cyrix 5530 ATA33</p> + </li> + + <li> + <p>HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 + ATA133, HPT374 ATA133</p> + </li> + + <li> + <p>Intel PIIX, PIIX3, PIIX4</p> + </li> + + <li> + <p>Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 + ATA100</p> + </li> + + <li> + <p>nVidia nForce ATA100, nForce2 ATA133</p> + </li> + + <li> + <p>Promise ATA100 OEM chip (pdc20265)</p> + </li> + + <li> + <p>Promise ATA133 OEM chip (pdc20269)</p> + </li> + + <li> + <p>Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 + TX2/TX2000</p> + </li> + + <li> + <p>Promise SATA150 TX2/TX4 Serial ATA/150</p> + </li> + + <li> + <p>Promise Ultra-33, -66, -100, -133 + TX2/TX2000/TX4000</p> + </li> + + <li> + <p>ServerWorks ROSB4 ATA33</p> + </li> + + <li> + <p>ServerWorks CSB5 and CSB6 ATA66/ATA100</p> + </li> + + <li> + <p>Sil 0680 UDMA6</p> + </li> + + <li> + <p>SiS 530, 540, 550, 620</p> + </li> + + <li> + <p>SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, + 650, 651, 652, 655, 658, 730, 733, 735, 740, 745, + 746, 748, 750, 751, 752, 755</p> + </li> + + <li> + <p>SiS 5591 ATA100</p> + </li> + + <li> + <p>VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, + 82C686b ATA100</p> + </li> + + <li> + <p>VIA 8233, 8235 ATA133</p> + </li> + </ul> + <br /> + <br /> + + <p>Adaptec SCSI Controllers</p> + + <ul> + <li> + <p>Adaptec + 19160/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x + series PCI SCSI controllers, including + Narrow/Wide/Twin/Ultra/Ultra2 variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahc</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec AIC7770, AIC7850, AIC7860, AIC7870, + AIC7880, and AIC789x on-board SCSI controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahc</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>AMI MegaRAID Express and Enterprise family RAID + controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amr</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>MegaRAID Series 418</p> + </li> + + <li> + <p>MegaRAID Enterprise 1200 (Series 428)</p> + </li> + + <li> + <p>MegaRAID Enterprise 1300 (Series 434)</p> + </li> + + <li> + <p>MegaRAID Enterprise 1400 (Series 438)</p> + </li> + + <li> + <p>MegaRAID Enterprise 1500 (Series 467)</p> + </li> + + <li> + <p>MegaRAID Enterprise 1600 (Series 471)</p> + </li> + + <li> + <p>MegaRAID Elite 1500 (Series 467)</p> + </li> + + <li> + <p>MegaRAID Elite 1600 (Series 493)</p> + </li> + + <li> + <p>MegaRAID Express 100 (Series 466WS)</p> + </li> + + <li> + <p>MegaRAID Express 200 (Series 466)</p> + </li> + + <li> + <p>MegaRAID Express 300 (Series 490)</p> + </li> + + <li> + <p>MegaRAID Express 500 (Series 475)</p> + </li> + + <li> + <p>Dell PERC</p> + </li> + + <li> + <p>Dell PERC 2/SC</p> + </li> + + <li> + <p>Dell PERC 2/DC</p> + </li> + + <li> + <p>Dell PERC 3/DCL</p> + </li> + + <li> + <p>HP NetRaid-1si</p> + </li> + + <li> + <p>HP NetRaid-3si</p> + </li> + + <li> + <p>HP Embedded NetRaid</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p>Booting from these controllers is not supported + due to SRM limitations.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Mylex DAC960 and DAC1100 RAID controllers with 2.x, + 3.x, 4.x and 5.x firmware (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mlx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mlx</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>DAC960P</p> + </li> + + <li> + <p>DAC960PD</p> + </li> + + <li> + <p>DAC960PDU</p> + </li> + + <li> + <p>DAC960PL</p> + </li> + + <li> + <p>DAC960PJ</p> + </li> + + <li> + <p>DAC960PG</p> + </li> + + <li> + <p>AcceleRAID 150</p> + </li> + + <li> + <p>AcceleRAID 250</p> + </li> + + <li> + <p>eXtremeRAID 1100</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p>Booting from these controllers is not supported + due to SRM limitations. This list includes + controllers sold by Digital/Compaq in Alpha systems + in the StorageWorks family, e.g. KZPSC or KZPAC.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, + 53C825, 53C825a, 53C860, 53C875, 53C875a, 53C876, 53C885, + 53C895, 53C895a, 53C896, 53C1010-33, 53C1010-66, 53C1000, + 53C1000R PCI SCSI controllers, either embedded on + motherboard or on add-on boards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ncr</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sym</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>ASUS SC-200, SC-896</p> + </li> + + <li> + <p>Data Technology DTC3130 (all variants)</p> + </li> + + <li> + <p>DawiControl DC2976UW</p> + </li> + + <li> + <p>Diamond FirePort (all)</p> + </li> + + <li> + <p>NCR cards (all)</p> + </li> + + <li> + <p>Symbios cards (all)</p> + </li> + + <li> + <p>Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, + and 390U3W</p> + </li> + + <li> + <p>Tyan S1365</p> + </li> + </ul> + <br /> + <br /> + + <p>Qlogic controllers and variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">isp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Qlogic 1020, 1040 SCSI and Ultra SCSI host + adapters</p> + </li> + + <li> + <p>Qlogic 1240 dual Ultra SCSI controllers</p> + </li> + + <li> + <p>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD + controllers</p> + </li> + + <li> + <p>Qlogic 12160 Ultra3 LVD controllers</p> + </li> + + <li> + <p>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI + controllers</p> + </li> + + <li> + <p>Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre + Channel SCSI controllers</p> + </li> + + <li> + <p>Performance Technology SBS440 ISP1000 variants</p> + </li> + + <li> + <p>Performance Technology SBS450 ISP1040 variants</p> + </li> + + <li> + <p>Performance Technology SBS470 ISP2100 variants</p> + </li> + + <li> + <p>Antares Microsystems P-0033 ISP2100 variants</p> + </li> + </ul> + <br /> + <br /> + + <p>LSI Logic Fusion/MP architecture Fiber Channel + controllers (mpt driver)</p> + + <ul> + <li> + <p>LSI FC909, FC929</p> + </li> + + <li> + <p>LSI 53c1020, 53c1030</p> + </li> + </ul> + <br /> + <br /> + + <p>With all supported SCSI controllers, full support is + provided for SCSI-I, SCSI-II, and SCSI-III peripherals, + including hard disks, optical disks, tape drives + (including DAT, 8mm Exabyte, Mammoth, and DLT), medium + changers, processor target devices and CD-ROM drives. + WORM devices that support CD-ROM commands are supported + for read-only access by the CD-ROM drivers (such as <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>). + WORM/CD-R/CD-RW writing support is provided by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&sektion=1&manpath=FreeBSD+Ports"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cdrecord</span>(1)</span></a>, + which is a part of the <a + href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/cdrtools/pkg-descr"> + <tt class="FILENAME">sysutils/cdrtools</tt></a> port in + the Ports Collection.</p> + + <p>The following CD-ROM type systems are supported at + this time:</p> + + <ul> + <li> + <p>SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>)</p> + </li> + + <li> + <p>ATAPI IDE interface (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=acd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">acd</span>(4)</span></a>)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 + Ethernet Interfaces</a></h2> + + <p>Adaptec Duralink PCI Fast Ethernet adapters based on + the Adaptec AIC-6915 Fast Ethernet controller chip (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sf</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>ANA-62011 64-bit single port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62022 64-bit dual port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62044 64-bit quad port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-69011 32-bit single port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62020 64-bit single port 100baseFX adapter</p> + </li> + </ul> + <br /> + <br /> + + <p>AMD PCnet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">lnc</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcn</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>AMD PCnet/PCI (79c970 & 53c974 or 79c974)</p> + </li> + + <li> + <p>AMD PCnet/FAST</p> + </li> + + <li> + <p>Isolan AT 4141-0 (16 bit)</p> + </li> + + <li> + <p>Isolink 4110 (8 bit)</p> + </li> + + <li> + <p>PCnet/FAST+</p> + </li> + + <li> + <p>PCnet/FAST III</p> + </li> + + <li> + <p>PCnet/PRO</p> + </li> + + <li> + <p>PCnet/Home</p> + </li> + + <li> + <p>HomePNA</p> + </li> + </ul> + <br /> + <br /> + + <p>RealTek 8129/8139 Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek + 8139 clone)</p> + </li> + + <li> + <p>Allied Telesyn AT2550</p> + </li> + + <li> + <p>Allied Telesyn AT2500TX</p> + </li> + + <li> + <p>D-Link DFE-530TX+, DFE-538TX</p> + </li> + + <li> + <p>Farallon NetLINE 10/100 PCI</p> + </li> + + <li> + <p>Genius GF100TXR (RTL8139)</p> + </li> + + <li> + <p>KTX-9130TX 10/100 Fast Ethernet</p> + </li> + + <li> + <p>NDC Communications NE100TX-E</p> + </li> + + <li> + <p>Netronix Inc. EA-1210 NetEther 10/100</p> + </li> + + <li> + <p>OvisLink LEF-8129TX</p> + </li> + + <li> + <p>OvisLink LEF-8139TX</p> + </li> + + <li> + <p>SMC EZ Card 10/100 PCI 1211-TX</p> + </li> + </ul> + <br /> + <br /> + + <p>Lite-On 82c168/82c169 PNIC Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Kingston KNE110TX</p> + </li> + + <li> + <p>LinkSys EtherFast LNE100TX</p> + </li> + + <li> + <p>Matrox FastNIC 10/100</p> + </li> + + <li> + <p>NetGear FA310-TX Rev. D1</p> + </li> + </ul> + <br /> + <br /> + + <p>Macronix 98713, 98713A, 98715, 98715A and 98725 Fast + Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Accton EN1217 (98715A)</p> + </li> + + <li> + <p>Adico AE310TX (98715A)</p> + </li> + + <li> + <p>Compex RL100-TX (98713 or 98713A)</p> + </li> + + <li> + <p>CNet Pro120A (98713 or 98713A)</p> + </li> + + <li> + <p>CNet Pro120B (98715)</p> + </li> + + <li> + <p>NDC Communications SFA100A (98713A)</p> + </li> + + <li> + <p>SVEC PN102TX (98713)</p> + </li> + </ul> + <br /> + <br /> + + <p>Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>LinkSys EtherFast LNE100TX Version 2</p> + </li> + </ul> + <br /> + <br /> + + <p>Winbond W89C840F Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wb</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Trendware TE100-PCIE</p> + </li> + </ul> + <br /> + <br /> + + <p>VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine + II'', and VT86C105/VT86C105M ``Rhine III'' Fast Ethernet + NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vr</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>AOpen/Acer ALN-320</p> + </li> + + <li> + <p>D-Link DFE-530TX</p> + </li> + + <li> + <p>Hawking Technologies PN102TX</p> + </li> + </ul> + <br /> + <br /> + + <p>Silicon Integrated Systems SiS 900 and SiS 7016 PCI + Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sis</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>SiS 630, 635 and 735 motherboard chipsets</p> + </li> + </ul> + <br /> + <br /> + + <p>National Semiconductor DP83815 Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sis</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>NetGear FA311-TX</p> + </li> + + <li> + <p>NetGear FA312-TX</p> + </li> + </ul> + <br /> + <br /> + + <p>Sundance Technologies ST201 PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ste</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>D-Link DFE-550TX</p> + </li> + </ul> + <br /> + <br /> + + <p>SysKonnect SK-984x PCI Gigabit Ethernet cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sk</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>SK-9821 1000baseT copper, single port</p> + </li> + + <li> + <p>SK-9822 1000baseT copper, dual port</p> + </li> + + <li> + <p>SK-9841 1000baseLX single mode fiber, single + port</p> + </li> + + <li> + <p>SK-9842 1000baseLX single mode fiber, dual + port</p> + </li> + + <li> + <p>SK-9843 1000baseSX multimode fiber, single + port</p> + </li> + + <li> + <p>SK-9844 1000baseSX multimode fiber, dual port</p> + </li> + </ul> + <br /> + <br /> + + <p>Texas Instruments ThunderLAN PCI NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Compaq Netelligent 10, 10/100, 10/100 + Dual-Port</p> + </li> + + <li> + <p>Compaq Netelligent 10/100 TX Embedded UTP, 10 T + PCI UTP/Coax, 10/100 TX UTP</p> + </li> + + <li> + <p>Compaq NetFlex 3P, 3P Integrated, 3P w/BNC</p> + </li> + + <li> + <p>Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX + UTP</p> + </li> + + <li> + <p>Racore 8165 10/100baseTX</p> + </li> + + <li> + <p>Racore 8148 10baseT/100baseTX/100baseFX + multi-personality</p> + </li> + </ul> + <br /> + <br /> + + <p>ADMtek Inc. AL981-based PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <p>ADMtek Inc. AN985-based PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>LinkSys EtherFast LNE100TX v4.0/4.1</p> + </li> + </ul> + <br /> + <br /> + + <p>ASIX Electronics AX88140A PCI NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Alfa Inc. GFC2204</p> + </li> + + <li> + <p>CNet Pro110B</p> + </li> + </ul> + <br /> + <br /> + + <p>DEC DC21040, DC21041, DC21140, DC21141, DC21142, and + DC21143 based NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">de</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Asante</p> + </li> + + <li> + <p>Cogent EM100FX and EM440TX</p> + </li> + + <li> + <p>DEC DE425, DE435, DE450, and DE500</p> + </li> + + <li> + <p>SMC Etherpower 8432T, 9332, and 9334</p> + </li> + + <li> + <p>ZYNX ZX 3xx</p> + </li> + </ul> + <br /> + <br /> + + <p>DEC/Intel 21143 based Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>DEC DE500</p> + </li> + + <li> + <p>Compaq Presario 7900 series built-in Ethernet</p> + </li> + + <li> + <p>D-Link DFE-570TX</p> + </li> + + <li> + <p>Kingston KNE100TX</p> + </li> + + <li> + <p>LinkSys EtherFast 10/100 Instant GigaDrive + built-in Ethernet</p> + </li> + </ul> + <br /> + <br /> + + <p>Davicom DM9009, DM9100 and DM9102 PCI Fast Ethernet + NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Jaton Corporation XpressNet</p> + </li> + </ul> + <br /> + <br /> + + <p>Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Intel EtherExpress Pro/100B PCI Fast Ethernet</p> + </li> + + <li> + <p>Intel InBusiness 10/100 PCI Network Adapter</p> + </li> + + <li> + <p>Intel PRO/100+ Management Adapter</p> + </li> + + <li> + <p>Intel Pro/100 VE Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 M Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters</p> + </li> + </ul> + <br /> + <br /> + + <p>3Com Etherlink XL-based NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3C900/905/905B/905C PCI</p> + </li> + + <li> + <p>3C555/556/556B MiniPCI</p> + </li> + + <li> + <p>3C450-TX HomeConnect adapter</p> + </li> + + <li> + <p>3c980/3c980B Fast Etherlink XL server adapter</p> + </li> + + <li> + <p>3cSOHO100-TX OfficeConnect adapter</p> + </li> + + <li> + <p>3C575TX/575B/XFE575BT/575C/656/656B/656C + (Cardbus)</p> + </li> + </ul> + <br /> + <br /> + + <p>Ethernet and Fast Ethernet NICs based on the 3Com 3XP + Typhoon/Sidewinder (3CR990) chipset (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">txp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3CR990-TX-95</p> + </li> + + <li> + <p>3Com 3CR990-TX-97</p> + </li> + + <li> + <p>3Com 3CR990B-SRV</p> + </li> + + <li> + <p>3Com 3CR990B-TXM</p> + </li> + + <li> + <p>3Com 3CR990SVR95</p> + </li> + + <li> + <p>3Com 3CR990SVR97</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet NICs based on the Intel 82542 and + 82543 controller chips (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gx</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> drivers), + plus NICs supported by the Intel 82540EM, 82544, 82545EM, + and 82546EB controller chips (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> driver + only)</p> + + <ul> + <li> + <p>Intel PRO/1000 Gigabit Ethernet</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> driver + is officially supported by Intel, but is only + supported on the i386.</p> + </blockquote> + </div> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3012" name="AEN3012">3.3 FDDI + Interfaces</a></h2> + + <p>DEC DEFPA PCI (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fpa</span>(4)</span></a> + driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3022" name="AEN3022">3.4 ATM + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3066" name="AEN3066">3.5 + Wireless Network Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3194" name="AEN3194">3.6 + Miscellaneous Networks</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3225" name="AEN3225">3.7 ISDN + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3289" name="AEN3289">3.8 + Serial Interfaces</a></h2> + + <p>``PC standard'' 8250, 16450, and 16550-based serial + ports (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <p>AST 4 port serial card using shared IRQ</p> + + <p>Comtrol Rocketport card (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rp</span>(4)</span></a> driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3484" name="AEN3484">3.9 + Audio Devices</a></h2> + + <p>ESS</p> + + <ul> + <li> + <p>ES1868, ES1869, ES1879 and ES1888 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbc</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Maestro-1, Maestro-2, and Maestro-2E</p> + </li> + + <li> + <p>Maestro-3/Allegro</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The Maestro-3/Allegro cannot be + compiled into the FreeBSD kernel due to licensing + restrictions. To use this driver, add the + following line to <tt + class="FILENAME">/boot/loader.conf</tt>:</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>snd_maestro3_load="YES"</b></tt> +</pre> + </blockquote> + </div> + </li> + </ul> + <br /> + <br /> + + <p>MSS/WSS Compatible DSPs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a> + driver)</p> + + <p>Creative Technologies SoundBlaster series (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbc</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>SoundBlaster</p> + </li> + + <li> + <p>SoundBlaster Pro</p> + </li> + + <li> + <p>SoundBlaster AWE-32</p> + </li> + + <li> + <p>SoundBlaster AWE-64</p> + </li> + + <li> + <p>SoundBlaster AWE-64 GOLD</p> + </li> + + <li> + <p>SoundBlaster ViBRA-16</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3607" name="AEN3607">3.10 + Camera and Video Capture Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USB" name="USB">3.11 USB + Devices</a></h2> + + <p>A range of USB peripherals are supported; devices + known to work are listed in this section. Owing to the + generic nature of most USB devices, with some exceptions + any device of a given class will be supported, even if + not explicitly listed here.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> USB Ethernet adapters can be found in + the section listing <a href="#ETHERNET">Ethernet + interfaces</a>.</p> + </blockquote> + </div> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> USB Bluetooth adapters can be found + in <a href="#BLUETOOTH">Bluetooth</a> section.</p> + </blockquote> + </div> + + <p>Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ohci</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uhci</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>ALi Aladdin-V</p> + </li> + + <li> + <p>AMD-756</p> + </li> + + <li> + <p>CMD Tech 670 & 673</p> + </li> + + <li> + <p>Intel 82371SB (PIIX3)</p> + </li> + + <li> + <p>Intel 82371AB and EB (PIIX4)</p> + </li> + + <li> + <p>Intel 82801AA (ICH)</p> + </li> + + <li> + <p>Intel 82801AB (ICH0)</p> + </li> + + <li> + <p>Intel 82801BA/BAM (ICH2)</p> + </li> + + <li> + <p>Intel 82443MX</p> + </li> + + <li> + <p>NEC uPD 9210</p> + </li> + + <li> + <p>OPTi 82C861 (FireLink)</p> + </li> + + <li> + <p>SiS 5571</p> + </li> + + <li> + <p>VIA 83C572 USB</p> + </li> + + <li> + <p>UHCI or OHCI compliant motherboard chipsets (no + exceptions known)</p> + </li> + </ul> + <br /> + <br /> + + <p>Hubs</p> + + <ul> + <li> + <p>Andromeda hub</p> + </li> + + <li> + <p>MacAlly self powered hub (4 ports)</p> + </li> + + <li> + <p>NEC hub</p> + </li> + </ul> + <br /> + <br /> + + <p>Keyboards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ukbd</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Apple iMac keyboard</p> + </li> + + <li> + <p>BTC BTC7935 keyboard with PS/2 mouse port</p> + </li> + + <li> + <p>Cherry G81-3504 keyboard</p> + </li> + + <li> + <p>Logitech M2452 keyboard</p> + </li> + + <li> + <p>MacAlly iKey keyboard</p> + </li> + + <li> + <p>Microsoft keyboard</p> + </li> + + <li> + <p>Sun Microsystems Type 6 USB keyboard</p> + </li> + </ul> + <br /> + <br /> + + <p>Mice (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ums</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Agiler Mouse 29UO</p> + </li> + + <li> + <p>Apple iMac Mouse</p> + </li> + + <li> + <p>Belkin Mouse</p> + </li> + + <li> + <p>Chic mouse</p> + </li> + + <li> + <p>Cypress mouse</p> + </li> + + <li> + <p>Genius Niche mouse</p> + </li> + + <li> + <p>Kensington Mouse-in-a-Box</p> + </li> + + <li> + <p>Logitech wheel mouse (3 buttons)</p> + </li> + + <li> + <p>Logitech PS/2 / USB mouse (3 buttons)</p> + </li> + + <li> + <p>MacAlly mouse (3 buttons)</p> + </li> + + <li> + <p>Microsoft IntelliMouse (3 buttons)</p> + </li> + + <li> + <p>Sun Microsystems Type 6 USB Mouse</p> + </li> + + <li> + <p>Trust Ami Mouse (3 buttons)</p> + </li> + </ul> + <br /> + <br /> + + <p>Printers and parallel printer conversion cables (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ulpt</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>ATen parallel printer adapter</p> + </li> + + <li> + <p>Belkin F5U002 parallel printer adapter</p> + </li> + + <li> + <p>Entrega USB-to-parallel printer adapter</p> + </li> + </ul> + <br /> + <br /> + + <p>Storage (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umass</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M</p> + </li> + + <li> + <p>Denno FireWire/USB2 Removable 2.5-inch HDD Case + MIFU-25CB20</p> + </li> + + <li> + <p>FujiFilm Zip USB Drive ZDR100 USB A</p> + </li> + + <li> + <p>GREEN HOUSE USB Flash Memory ``PicoDrive'' + GH-UFD32M, 64M, 128M</p> + </li> + + <li> + <p>IBM 32MB USB Memory Key (P/N 22P5296)</p> + </li> + + <li> + <p>IBM ThinkPad USB Portable CD-ROM Drive (P/N + 33L5151)</p> + </li> + + <li> + <p>I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM + only)</p> + </li> + + <li> + <p>I-O DATA USB + CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive + DVR-iUH2 (CDROM, DVD-RAM only)</p> + </li> + + <li> + <p>Iomega Zip750 USB2.0 Drive</p> + </li> + + <li> + <p>Keian USB1.1/2.0 3.5-inch HDD Case KU350A</p> + </li> + + <li> + <p>Kurouto Shikou USB 2.5-inch HDD Case + GAWAP2.5PS-USB2.0</p> + </li> + + <li> + <p>Logitec USB1.1/2.0 HDD Unit SHD-E60U2</p> + </li> + + <li> + <p>Logitec Mobile USB Memory LMC-256UD</p> + </li> + + <li> + <p>Logitec USB Double-Speed Floppy Drive LFD-31U2</p> + </li> + + <li> + <p>Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 + (CDROM only)</p> + </li> + + <li> + <p>Matshita CF-VFDU03 floppy drive</p> + </li> + + <li> + <p>MELCO USB2.0 MO Drive MO-CH640U2</p> + </li> + + <li> + <p>I-O DATA USB/IEEE1394 Portable HD Drive + HDP-i30P/CI, HDP-i40P/CI</p> + </li> + + <li> + <p>MELCO USB Flash Disk ``PetitDrive'', RUF-32M, + -64M, -128M, -256M</p> + </li> + + <li> + <p>MELCO USB2.0 Flash Disk ``PetitDrive2'', + RUF-256M/U2, -512M/U2</p> + </li> + + <li> + <p>MELCO USB Flash Disk ``ClipDrive'', RUF-C32M, + -C64M, -C128M, -C256M, -C512M</p> + </li> + + <li> + <p>Microtech USB-SCSI-HD 50 USB to SCSI cable</p> + </li> + + <li> + <p>NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U</p> + </li> + + <li> + <p>Panasonic floppy drive</p> + </li> + + <li> + <p>Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN + (CDROM only)</p> + </li> + + <li> + <p>RATOC Systems USB2.0 Removable HDD Case U2-MDK1, + U2-MDK1B</p> + </li> + + <li> + <p>Sony Portable CD-R/RW Drive CRX10U (CDROM + only)</p> + </li> + + <li> + <p>TEAC Portable USB CD-ROM Unit CD-110PU/210PU</p> + </li> + + <li> + <p>Y-E Data floppy drive (720/1.44/2.88Mb)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 + IEEE 1394 (Firewire) Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.13 + Bluetooth Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN3987" name="AEN3987">3.14 + Cryptographic Accelerators</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN4012" name="AEN4012">3.15 + Miscellaneous</a></h2> + + <p>Floppy drives (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fdc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fdc</span>(4)</span></a> + driver)</p> + + <p>VGA-compatible video cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vga&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vga</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Information regarding specific video + cards and compatibility with <b + class="APPLICATION">XFree86</b> can be found at <a + href="http://www.xfree86.org/" + target="_top">http://www.xfree86.org/</a>.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Keyboards including:</p> + + <ul> + <li> + <p>AT-style keyboards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">atkbd</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>PS/2 keyboards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">atkbd</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>USB keyboards (specific instances are listed in + the section describing <a href="#USB">USB + devices</a>)</p> + </li> + </ul> + <br /> + <br /> + + <p>Pointing devices including:</p> + + <ul> + <li> + <p>PS/2 mice and compatible devices, including many + laptop pointing devices (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">psm</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Serial mice and compatible devices</p> + </li> + + <li> + <p>USB mice (specific instances are listed in the + section describing <a href="#USB">USB + devices</a>)</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">moused</span>(8)</span></a> has + more information on using pointing devices with + FreeBSD. Information on using pointing devices with + <b class="APPLICATION">XFree86</b> can be found at <a + href="http://www.xfree86.org/" + target="_top">http://www.xfree86.org/</a>.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>``PC standard'' parallel ports (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ppc</span>(4)</span></a> + driver)</p> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-i386.html b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-i386.html new file mode 100644 index 0000000000..d228215b5a --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-i386.html @@ -0,0 +1,5036 @@ +<!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/i386 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/i386 + 5.1-RELEASE Hardware Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Documentation + Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#PROC">Supported Processors and + Motherboards</a></dt> + + <dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + + <dd> + <dl> + <dt>3.1 <a href="#AEN63">Disk Controllers</a></dt> + + <dt>3.2 <a href="#ETHERNET">Ethernet + Interfaces</a></dt> + + <dt>3.3 <a href="#AEN1629">FDDI Interfaces</a></dt> + + <dt>3.4 <a href="#AEN1639">ATM Interfaces</a></dt> + + <dt>3.5 <a href="#AEN1683">Wireless Network + Interfaces</a></dt> + + <dt>3.6 <a href="#AEN1811">Miscellaneous + Networks</a></dt> + + <dt>3.7 <a href="#AEN1842">ISDN Interfaces</a></dt> + + <dt>3.8 <a href="#AEN1906">Serial Interfaces</a></dt> + + <dt>3.9 <a href="#AEN2101">Audio Devices</a></dt> + + <dt>3.10 <a href="#AEN2224">Camera and Video Capture + Devices</a></dt> + + <dt>3.11 <a href="#USB">USB Devices</a></dt> + + <dt>3.12 <a href="#FIREWIRE">IEEE 1394 (Firewire) + Devices</a></dt> + + <dt>3.13 <a href="#BLUETOOTH">Bluetooth + Devices</a></dt> + + <dt>3.14 <a href="#AEN2604">Cryptographic + Accelerators</a></dt> + + <dt>3.15 <a href="#AEN2629">Miscellaneous</a></dt> + </dl> + </dd> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the hardware compatibility notes + for FreeBSD 5.1-RELEASE on the i386 hardware platform (also + referred to as FreeBSD/i386 5.1-RELEASE). It lists devices + known to work on this platform, as well as some notes on + boot-time kernel customization that may be useful when + attempting to configure support for new devices.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> This document includes information + specific to the i386 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 id="PROC" name="PROC">2 Supported + Processors and Motherboards</a></h1> + + <p>FreeBSD/i386 runs on a wide variety of ``IBM PC + compatible'' machines. Due to the wide range of hardware + available for this architecture, it is impossible to + exhaustively list all combinations of equipment supported + by FreeBSD. Nevertheless, some general guidelines are + presented here.</p> + + <p>Almost all i386-compatible processors are supported. All + Intel processors beginning with the 80386 are supported, + including the 80386, 80486, Pentium, Pentium Pro, Pentium + II, Pentium III, Pentium 4, and variants thereof, such as + the Xeon and Celeron processors. (While technically + supported, the use of the 80386SX is specifically not + recommended.) All i386-compatible AMD processors are also + supported, including the Am486, Am5x86, K5, K6 (and + variants), Athlon (including Athlon-MP, Athlon-XP, + Athlon-4, and Athlon Thunderbird), and Duron processors. + The AMD Élan SC520 embedded processor is supported. + The Transmeta Crusoe is recognized and supported, as are + i386-compatible processors from Cyrix and NexGen.</p> + + <p>There is a wide variety of motherboards available for + this architecture. Motherboards using the ISA, VLB, EISA, + AGP, and PCI expansion busses are well-supported. There is + some limited support for the MCA (``MicroChannel'') + expansion bus used in the IBM PS/2 line of PCs.</p> + + <p>Symmetric multi-processor (SMP) systems are generally + supported by FreeBSD, although in some cases, BIOS or + motherboard bugs may generate some problems. Perusal of the + archives of the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-smp" + target="_top">FreeBSD symmetric multiprocessing mailing + list</a> may yield some clues.</p> + + <p>FreeBSD will take advantage of HyperThreading (HTT) + support on Intel CPUs that support this feature. A kernel + with the <tt class="LITERAL">options SMP</tt> feature + enabled will automatically detect the additional logical + processors. The default FreeBSD scheduler treats the + logical processors the same as additional physical + processors; in other words, no attempt is made to optimize + scheduling decisions given the shared resources between + logical processors within the same CPU. Because this naive + scheduling can result in suboptimal performance, the + logical CPUs are halted by default at startup. They can be + enabled with the <tt + class="VARNAME">machdep.hlt_logical_cpus</tt> sysctl + variable. It is also possible to halt any CPU in the idle + loop with the <tt class="VARNAME">machdep.hlt_cpus</tt> + sysctl variable. The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=smp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">smp</span>(4)</span></a> manual page + has more details.</p> + + <p>FreeBSD will take advantage of Physical Address + Extensions (PAE) support on CPUs that support this feature. + A kernel with the <tt class="LITERAL">PAE</tt> feature + enabled will detect memory above 4 gigabytes and allow it + to be used by the system. This feature places constraints + on the device drivers and other features of FreeBSD which + may be used; consult the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pae&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pae</span>(4)</span></a> manpage for + more details.</p> + + <p>FreeBSD will generally run on i386-based laptops, albeit + with varying levels of support for certain hardware + features such as sound, graphics, power management, and + PCCARD expansion slots. These features tend to vary in + idiosyncratic ways between machines, and frequently require + special-case support in FreeBSD to work around hardware + bugs or other oddities. When in doubt, a search of the + archives of the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-mobile" + target="_top">FreeBSD laptop computer mailing list</a> may + be useful.</p> + + <p>Most modern laptops (as well as many desktops) use the + Advanced Configuration and Power Management (ACPI) + standard. FreeBSD supports ACPI via the ACPI Component + Architecture reference implementation from Intel, as + described in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">acpi</span>(4)</span></a> manual + page. The use of ACPI causes instabilities on some machines + and it may be necessary to disable the ACPI driver, which + is normally loaded via a kernel module. This may be + accomplished by adding the following line to <tt + class="FILENAME">/boot/device.hints</tt>:</p> +<pre class="PROGRAMLISTING"> +hint.acpi.0.disabled="1" +</pre> + + <p>Users debugging ACPI-related problems may find it useful + to disable portions of the ACPI functionality. The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">acpi</span>(4)</span></a> manual page + has more information on how to do this via loader + tunables.</p> + + <p>ACPI depends on a Differentiated System Descriptor Table + (DSDT) provided by each machine's BIOS. Some machines have + bad or incomplete DSDTs, which prevents ACPI from + functioning correctly. Replacement DSDTs for some machines + can be found at the <a + href="http://acpi.sourceforge.net/dsdt/index.php" + target="_top">DSDT</a> section of the <a + href="http://acpi.sourceforge.net/" + target="_top">ACPI4Linux</a> project Web site. FreeBSD can + use these DSDTs to override the DSDT provided by the BIOS; + see the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=acpi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">acpi</span>(4)</span></a> manual page + for more information.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 + Supported Devices</a></h1> + $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.157 2003/05/30 11:24:00 nyan Exp $ + + <p>This section describes the devices currently known to be + supported by with FreeBSD on the i386 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 id="AEN63" name="AEN63">3.1 Disk + Controllers</a></h2> + + <p>IDE/ATA controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6</p> + </li> + + <li> + <p>AMD 756 ATA66, 766 ATA100, 768 ATA100</p> + </li> + + <li> + <p>Cenatek Rocket Drive</p> + </li> + + <li> + <p>CMD 646, 648 ATA66, and 649 ATA100</p> + </li> + + <li> + <p>Cypress 82C693</p> + </li> + + <li> + <p>Cyrix 5530 ATA33</p> + </li> + + <li> + <p>HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 + ATA133, HPT374 ATA133</p> + </li> + + <li> + <p>Intel PIIX, PIIX3, PIIX4</p> + </li> + + <li> + <p>Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 + ATA100</p> + </li> + + <li> + <p>nVidia nForce ATA100, nForce2 ATA133</p> + </li> + + <li> + <p>Promise ATA100 OEM chip (pdc20265)</p> + </li> + + <li> + <p>Promise ATA133 OEM chip (pdc20269)</p> + </li> + + <li> + <p>Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 + TX2/TX2000</p> + </li> + + <li> + <p>Promise SATA150 TX2/TX4 Serial ATA/150</p> + </li> + + <li> + <p>Promise Ultra-33, -66, -100, -133 + TX2/TX2000/TX4000</p> + </li> + + <li> + <p>ServerWorks ROSB4 ATA33</p> + </li> + + <li> + <p>ServerWorks CSB5 and CSB6 ATA66/ATA100</p> + </li> + + <li> + <p>Sil 0680 UDMA6</p> + </li> + + <li> + <p>SiS 530, 540, 550, 620</p> + </li> + + <li> + <p>SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, + 650, 651, 652, 655, 658, 730, 733, 735, 740, 745, + 746, 748, 750, 751, 752, 755</p> + </li> + + <li> + <p>SiS 5591 ATA100</p> + </li> + + <li> + <p>VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, + 82C686b ATA100</p> + </li> + + <li> + <p>VIA 8233, 8235 ATA133</p> + </li> + </ul> + <br /> + <br /> + + <p>Adaptec SCSI Controllers</p> + + <ul> + <li> + <p>Adaptec 1535 ISA SCSI controllers</p> + </li> + + <li> + <p>Adaptec 154x series ISA SCSI controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aha</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec 164x series MCA SCSI controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aha</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec 174x series EISA SCSI controller in + standard and enhanced mode (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aha</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahb&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahb</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec 274x series EISA SCSI controllers, + including narrow and wide variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahc</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec 284x series VLB SCSI controllers, + including narrow and wide variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahc</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec + 19160/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x + series PCI SCSI controllers, including + Narrow/Wide/Twin/Ultra/Ultra2 variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahc</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec AIC7770, AIC7850, AIC7860, AIC7870, + AIC7880, and AIC789x on-board SCSI controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahc</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec 1510 series ISA SCSI controllers (not for + bootable devices)</p> + </li> + + <li> + <p>Adaptec 152x series ISA SCSI controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aha&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aha</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Adaptec AIC-6260 and AIC-6360 based boards, which + includes the AHA-152x and SoundBlaster SCSI cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aic&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aic</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Ultra-320 SCSI controllers based on the Adaptec + AIC7901, AIC7901A, and AIC7902 Ultra320 controller chips + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahd</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Adaptec 29320, 29320A, 29320B, 29320LP</p> + </li> + + <li> + <p>Adaptec 39320, 39320D</p> + </li> + </ul> + <br /> + <br /> + + <p>Adaptec 21x0S/32x0S/34x0S SCSI RAID controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">asr</span>(4)</span></a> + driver)</p> + + <p>Adaptec 2000S/2005S Zero-Channel RAID controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">asr</span>(4)</span></a> + driver)</p> + + <p>Adaptec 2400A ATA-100 RAID controller (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">asr</span>(4)</span></a> + driver)</p> + + <p>Adaptec FSA family RAID controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aac</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Adaptec AAC-2622</p> + </li> + + <li> + <p>Adaptec AAC-364</p> + </li> + + <li> + <p>Adaptec SCSI RAID 2120S</p> + </li> + + <li> + <p>Adaptec SCSI RAID 2200S</p> + </li> + + <li> + <p>Adaptec SCSI RAID 5400S</p> + </li> + + <li> + <p>Dell PERC 2/QC</p> + </li> + + <li> + <p>Dell PERC 2/Si</p> + </li> + + <li> + <p>Dell PERC 3/Di</p> + </li> + + <li> + <p>Dell PERC 3/QC</p> + </li> + + <li> + <p>Dell PERC 3/Si</p> + </li> + + <li> + <p>HP NetRAID-4M</p> + </li> + </ul> + <br /> + <br /> + + <p>AdvanSys SCSI controllers (all models, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adv&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adv</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adw</span>(4)</span></a> + drivers)</p> + <br /> + <br /> + + <p>BusLogic MultiMaster ``W'' Series Host Adapters (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bt</span>(4)</span></a> + driver):</p> + + <ul> + <li> + <p>BT-948</p> + </li> + + <li> + <p>BT-958</p> + </li> + + <li> + <p>BT-958D</p> + </li> + </ul> + <br /> + <br /> + + <p>BusLogic MultiMaster ``C'' Series Host Adapters (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bt</span>(4)</span></a> + driver):</p> + + <ul> + <li> + <p>BT-946C</p> + </li> + + <li> + <p>BT-956C</p> + </li> + + <li> + <p>BT-956CD</p> + </li> + + <li> + <p>BT-445C</p> + </li> + + <li> + <p>BT-747C</p> + </li> + + <li> + <p>BT-757C</p> + </li> + + <li> + <p>BT-757CD</p> + </li> + + <li> + <p>BT-545C</p> + </li> + + <li> + <p>BT-540CF</p> + </li> + </ul> + <br /> + <br /> + + <p>BusLogic MultiMaster ``S'' Series Host Adapters (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bt</span>(4)</span></a> + driver):</p> + + <ul> + <li> + <p>BT-445S</p> + </li> + + <li> + <p>BT-747S</p> + </li> + + <li> + <p>BT-747D</p> + </li> + + <li> + <p>BT-757S</p> + </li> + + <li> + <p>BT-757D</p> + </li> + + <li> + <p>BT-545S</p> + </li> + + <li> + <p>BT-542D</p> + </li> + + <li> + <p>BT-742A</p> + </li> + + <li> + <p>BT-542B</p> + </li> + </ul> + <br /> + <br /> + + <p>BusLogic MultiMaster ``A'' Series Host Adapters (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bt</span>(4)</span></a> + driver):</p> + + <ul> + <li> + <p>BT-742A</p> + </li> + + <li> + <p>BT-542B</p> + </li> + </ul> + <br /> + <br /> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> BusLogic/Mylex ``Flashpoint'' + adapters are not yet supported.</p> + </blockquote> + </div> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> AMI FastDisk controllers that are + true BusLogic MultiMaster clones are also + supported.</p> + </blockquote> + </div> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The Buslogic/Bustek BT-640 and + Storage Dimensions SDC3211B and SDC3211F Microchannel + (MCA) bus adapters are also supported.</p> + </blockquote> + </div> + + <p>DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, + SmartCACHE IV and SmartRAID IV SCSI/RAID controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dpt</span>(4)</span></a> + driver)</p> + + <p>DPT SmartRAID V and VI SCSI RAID controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=asr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">asr</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>PM1554</p> + </li> + + <li> + <p>PM2554</p> + </li> + + <li> + <p>PM2654</p> + </li> + + <li> + <p>PM2865</p> + </li> + + <li> + <p>PM2754</p> + </li> + + <li> + <p>PM3755</p> + </li> + + <li> + <p>PM3757</p> + </li> + </ul> + <br /> + <br /> + + <p>AMI MegaRAID Express and Enterprise family RAID + controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amr</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>MegaRAID Series 418</p> + </li> + + <li> + <p>MegaRAID Enterprise 1200 (Series 428)</p> + </li> + + <li> + <p>MegaRAID Enterprise 1300 (Series 434)</p> + </li> + + <li> + <p>MegaRAID Enterprise 1400 (Series 438)</p> + </li> + + <li> + <p>MegaRAID Enterprise 1500 (Series 467)</p> + </li> + + <li> + <p>MegaRAID Enterprise 1600 (Series 471)</p> + </li> + + <li> + <p>MegaRAID Elite 1500 (Series 467)</p> + </li> + + <li> + <p>MegaRAID Elite 1600 (Series 493)</p> + </li> + + <li> + <p>MegaRAID Express 100 (Series 466WS)</p> + </li> + + <li> + <p>MegaRAID Express 200 (Series 466)</p> + </li> + + <li> + <p>MegaRAID Express 300 (Series 490)</p> + </li> + + <li> + <p>MegaRAID Express 500 (Series 475)</p> + </li> + + <li> + <p>Dell PERC</p> + </li> + + <li> + <p>Dell PERC 2/SC</p> + </li> + + <li> + <p>Dell PERC 2/DC</p> + </li> + + <li> + <p>Dell PERC 3/DCL</p> + </li> + + <li> + <p>HP NetRaid-1si</p> + </li> + + <li> + <p>HP NetRaid-3si</p> + </li> + + <li> + <p>HP Embedded NetRaid</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Booting from these controllers is + supported. EISA adapters are not supported.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Mylex DAC960 and DAC1100 RAID controllers with 2.x, + 3.x, 4.x and 5.x firmware (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mlx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mlx</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>DAC960P</p> + </li> + + <li> + <p>DAC960PD</p> + </li> + + <li> + <p>DAC960PDU</p> + </li> + + <li> + <p>DAC960PL</p> + </li> + + <li> + <p>DAC960PJ</p> + </li> + + <li> + <p>DAC960PG</p> + </li> + + <li> + <p>AcceleRAID 150</p> + </li> + + <li> + <p>AcceleRAID 250</p> + </li> + + <li> + <p>eXtremeRAID 1100</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Booting from these controllers is + supported. EISA adapters are not supported.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Mylex PCI to SCSI RAID controllers with 6.x firmware + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mly</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>AcceleRAID 160</p> + </li> + + <li> + <p>AcceleRAID 170</p> + </li> + + <li> + <p>AcceleRAID 352</p> + </li> + + <li> + <p>eXtremeRAID 2000</p> + </li> + + <li> + <p>eXtremeRAID 3000</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Compatible Mylex controllers not + listed should work, but have not been verified.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>3ware Escalade ATA RAID controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=twe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">twe</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>5000 series</p> + </li> + + <li> + <p>6000 series</p> + </li> + + <li> + <p>7000 series</p> + </li> + </ul> + <br /> + <br /> + + <p>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, + 53C825, 53C825a, 53C860, 53C875, 53C875a, 53C876, 53C885, + 53C895, 53C895a, 53C896, 53C1010-33, 53C1010-66, 53C1000, + 53C1000R PCI SCSI controllers, either embedded on + motherboard or on add-on boards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ncr</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sym</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>ASUS SC-200, SC-896</p> + </li> + + <li> + <p>Data Technology DTC3130 (all variants)</p> + </li> + + <li> + <p>DawiControl DC2976UW</p> + </li> + + <li> + <p>Diamond FirePort (all)</p> + </li> + + <li> + <p>NCR cards (all)</p> + </li> + + <li> + <p>Symbios cards (all)</p> + </li> + + <li> + <p>Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, + and 390U3W</p> + </li> + + <li> + <p>Tyan S1365</p> + </li> + </ul> + <br /> + <br /> + + <p>NCR 53C500 based PC-Card SCSI host adapters (ncv + driver)</p> + + <ul> + <li> + <p>IO DATA PCSC-DV</p> + </li> + + <li> + <p>KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004</p> + </li> + + <li> + <p>Macnica Miracle SCSI-II mPS110</p> + </li> + + <li> + <p>Media Intelligent MSC-110, MSC-200</p> + </li> + + <li> + <p>NEC PC-9801N-J03R</p> + </li> + + <li> + <p>New Media Corporation BASICS SCSI</p> + </li> + + <li> + <p>Qlogic Fast SCSI</p> + </li> + + <li> + <p>RATOC REX-9530, REX-5572 (as SCSI only)</p> + </li> + </ul> + <br /> + <br /> + + <p>TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters + (stg driver)</p> + + <ul> + <li> + <p>Future Domain SCSI2GO</p> + </li> + + <li> + <p>IBM SCSI PCMCIA Card</p> + </li> + + <li> + <p>ICM PSC-2401 SCSI</p> + </li> + + <li> + <p>MELCO IFC-SC</p> + </li> + + <li> + <p>RATOC REX-5536, REX-5536AM, REX-5536M, + REX-9836A</p> + </li> + </ul> + <br /> + <br /> + + <p>Qlogic controllers and variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">isp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Qlogic 1020, 1040 SCSI and Ultra SCSI host + adapters</p> + </li> + + <li> + <p>Qlogic 1240 dual Ultra SCSI controllers</p> + </li> + + <li> + <p>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD + controllers</p> + </li> + + <li> + <p>Qlogic 12160 Ultra3 LVD controllers</p> + </li> + + <li> + <p>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI + controllers</p> + </li> + + <li> + <p>Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre + Channel SCSI controllers</p> + </li> + + <li> + <p>Performance Technology SBS440 ISP1000 variants</p> + </li> + + <li> + <p>Performance Technology SBS450 ISP1040 variants</p> + </li> + + <li> + <p>Performance Technology SBS470 ISP2100 variants</p> + </li> + + <li> + <p>Antares Microsystems P-0033 ISP2100 variants</p> + </li> + </ul> + <br /> + <br /> + + <p>DTC 3290 EISA SCSI controller in 1542 emulation + mode.</p> + + <p>Tekram DC390 and DC390T controllers, maybe other cards + based on the AMD 53c974 as well (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amd</span>(4)</span></a> + driver)</p> + + <p>Workbit Ninja SCSI-3 based PC-Card SCSI host adapters + (nsp driver)</p> + + <ul> + <li> + <p>Alpha-Data AD-PCS201</p> + </li> + + <li> + <p>IO DATA CBSC16</p> + </li> + </ul> + <br /> + <br /> + + <p>Parallel to SCSI interfaces (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vpo&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vpo</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>AIC 7110 SCSI controller (built-in to Iomega ZIP + drive)</p> + </li> + + <li> + <p>Iomega Jaz Traveller interface</p> + </li> + + <li> + <p>Iomega MatchMaker SCSI interface (built-in to + Iomega ZIP+ drive)</p> + </li> + </ul> + <br /> + <br /> + + <p>Compaq Intelligent Drive Array Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ida&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ida</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Compaq SMART Array 221</p> + </li> + + <li> + <p>Compaq Integrated SMART Array Controller</p> + </li> + + <li> + <p>Compaq SMART Array 4200, 4250ES Controllers</p> + </li> + + <li> + <p>Compaq SMART Array 3200, 3100ES Controller</p> + </li> + + <li> + <p>Compaq SMART-2/DH, SMART-2/SL, SMART-2/P, + SMART-2E, and SMART Controllers</p> + </li> + </ul> + <br /> + <br /> + + <p>SCSI adapters utilizing the Command Interface for + SCSI-3 Support (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ciss&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ciss</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Compaq Smart Array 5* series (5300, 5i, 532)</p> + </li> + </ul> + <br /> + <br /> + + <p>Intel Integrated RAID Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">iir</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Intel RAID Controller SRCMR</p> + </li> + + <li> + <p>ICP Vortex SCSI RAID controllers (all + Wide/Ultra160, 32-bit/64-bit PCI models)</p> + </li> + </ul> + <br /> + <br /> + + <p>Promise SuperTrak ATA RAID controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pst&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pst</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Promise SuperTrak SX6000 ATA RAID controller</p> + </li> + </ul> + <br /> + <br /> + + <p>IBM / Adaptec ServeRAID series (ips driver)</p> + + <p>LSI Logic Fusion/MP architecture Fiber Channel + controllers (mpt driver)</p> + + <ul> + <li> + <p>LSI FC909, FC929</p> + </li> + + <li> + <p>LSI 53c1020, 53c1030</p> + </li> + </ul> + <br /> + <br /> + + <p>PCI SCSI host adapters using the Tekram TRM-S1040 SCSI + chipset (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=trm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">trm</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Tekram DC395U/UW/U2W/F</p> + </li> + + <li> + <p>Tekram DC315U</p> + </li> + </ul> + <br /> + <br /> + + <p>With all supported SCSI controllers, full support is + provided for SCSI-I, SCSI-II, and SCSI-III peripherals, + including hard disks, optical disks, tape drives + (including DAT, 8mm Exabyte, Mammoth, and DLT), medium + changers, processor target devices and CD-ROM drives. + WORM devices that support CD-ROM commands are supported + for read-only access by the CD-ROM drivers (such as <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>). + WORM/CD-R/CD-RW writing support is provided by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&sektion=1&manpath=FreeBSD+Ports"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cdrecord</span>(1)</span></a>, + which is a part of the <a + href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/cdrtools/pkg-descr"> + <tt class="FILENAME">sysutils/cdrtools</tt></a> port in + the Ports Collection.</p> + + <p>The following CD-ROM type systems are supported at + this time:</p> + + <ul> + <li> + <p>SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>)</p> + </li> + + <li> + <p>Sony proprietary interface (all models) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=scd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">scd</span>(4)</span></a>)</p> + </li> + + <li> + <p>ATAPI IDE interface (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=acd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">acd</span>(4)</span></a>)</p> + </li> + </ul> + <br /> + <br /> + + <p>The following drivers were supported under the old + SCSI subsystem, but are not yet supported under the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cam&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cam</span>(4)</span></a> SCSI + subsystem:</p> + + <ul> + <li> + <p>NCR5380/NCR53400 (``ProAudio Spectrum'') SCSI + controller</p> + </li> + + <li> + <p>UltraStor 14F, 24F and 34F SCSI controllers.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> There is work-in-progress to port + the UltraStor driver to the new CAM SCSI + framework, but no estimates on when or if it will + be completed.</p> + </blockquote> + </div> + <br /> + <br /> + </li> + + <li> + <p>Seagate ST01/02 SCSI controllers</p> + </li> + + <li> + <p>Future Domain 8xx/950 series SCSI controllers</p> + </li> + + <li> + <p>WD7000 SCSI controller</p> + </li> + </ul> + <br /> + <br /> + + <p>The following device is unmaintained:</p> + + <ul> + <li> + <p>Mitsumi proprietary CD-ROM interface (all models) + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mcd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mcd</span>(4)</span></a>)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 + Ethernet Interfaces</a></h2> + + <p>Adaptec Duralink PCI Fast Ethernet adapters based on + the Adaptec AIC-6915 Fast Ethernet controller chip (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sf</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>ANA-62011 64-bit single port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62022 64-bit dual port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62044 64-bit quad port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-69011 32-bit single port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62020 64-bit single port 100baseFX adapter</p> + </li> + </ul> + <br /> + <br /> + + <p>Allied-Telesis AT1700 and RE2000 cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fe</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>CONTEC C-NET(PC)C PCMCIA Ethernet</p> + </li> + + <li> + <p>Fujitsu MBH10303, MBH10302 Ethernet PCMCIA</p> + </li> + + <li> + <p>Fujitsu Towa LA501 Ethernet</p> + </li> + + <li> + <p>Fujitsu FMV-J182, FMV-J182A</p> + </li> + + <li> + <p>RATOC REX-5588, REX-9822, REX-4886, and + REX-R280</p> + </li> + + <li> + <p>Eiger Labs EPX-10BT</p> + </li> + + <li> + <p>HITACHI HT-4840-11</p> + </li> + + <li> + <p>NextCom J Link NC5310</p> + </li> + + <li> + <p>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</p> + </li> + </ul> + <br /> + <br /> + + <p>Alteon Networks PCI Gigabit Ethernet NICs based on the + Tigon 1 and Tigon 2 chipsets (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ti</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3Com 3c985-SX (Tigon 1 and 2)</p> + </li> + + <li> + <p>Alteon AceNIC (Tigon 1 and 2)</p> + </li> + + <li> + <p>Alteon AceNIC 1000baseT (Tigon 2)</p> + </li> + + <li> + <p>Asante PCI 1000BASE-SX Gigabit Ethernet + Adapter</p> + </li> + + <li> + <p>Asante GigaNIX1000T Gigabit Ethernet Adapter</p> + </li> + + <li> + <p>DEC/Compaq EtherWORKS 1000</p> + </li> + + <li> + <p>Farallon PN9000SX</p> + </li> + + <li> + <p>NEC Gigabit Ethernet</p> + </li> + + <li> + <p>Netgear GA620 (Tigon 2)</p> + </li> + + <li> + <p>Netgear GA620T (Tigon 2, 1000baseT)</p> + </li> + + <li> + <p>Silicon Graphics Gigabit Ethernet</p> + </li> + </ul> + <br /> + <br /> + + <p>AMD PCnet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">lnc</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcn</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>AMD PCnet/PCI (79c970 & 53c974 or 79c974)</p> + </li> + + <li> + <p>AMD PCnet/FAST</p> + </li> + + <li> + <p>Isolan AT 4141-0 (16 bit)</p> + </li> + + <li> + <p>Isolink 4110 (8 bit)</p> + </li> + + <li> + <p>PCnet/FAST+</p> + </li> + + <li> + <p>PCnet/FAST III</p> + </li> + + <li> + <p>PCnet/PRO</p> + </li> + + <li> + <p>PCnet/Home</p> + </li> + + <li> + <p>HomePNA</p> + </li> + </ul> + <br /> + <br /> + + <p>SMC 83c17x (EPIC)-based Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tx</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>SMC EtherPower II 9432 series</p> + </li> + </ul> + <br /> + <br /> + + <p>National Semiconductor DS8390-based Ethernet NICs, + including Novell NE2000 and clones (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ed</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3C503 Etherlink II (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ed</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>DEC Etherworks DE305</p> + </li> + + <li> + <p>Hewlett-Packard PC Lan+ 27247B and 27252A</p> + </li> + + <li> + <p>NetVin 5000</p> + </li> + + <li> + <p>Novell NE1000, NE2000, and NE2100</p> + </li> + + <li> + <p>RealTek 8029</p> + </li> + + <li> + <p>SMC Elite 16 WD8013 Ethernet interface</p> + </li> + + <li> + <p>SMC Elite Ultra</p> + </li> + + <li> + <p>SMC WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, + WD8003SBT and WD8013EBT and clones</p> + </li> + + <li> + <p>Surecom NE-34</p> + </li> + + <li> + <p>VIA VT86C926</p> + </li> + + <li> + <p>Winbond W89C940</p> + </li> + </ul> + <br /> + <br /> + + <p>NE2000 compatible PC-Card (PCMCIA) Ethernet and + FastEthernet cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ed</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>AR-P500 Ethernet</p> + </li> + + <li> + <p>Accton EN2212/EN2216/UE2216</p> + </li> + + <li> + <p>Allied Telesis CentreCOM LA100-PCM_V2</p> + </li> + + <li> + <p>AmbiCom 10BaseT card</p> + </li> + + <li> + <p>BayNetworks NETGEAR FA410TXC Fast Ethernet</p> + </li> + + <li> + <p>CNet BC40 adapter</p> + </li> + + <li> + <p>COREGA Ether PCC-T/EtherII PCC-T/FEther + PCC-TXF/PCC-TXD</p> + </li> + + <li> + <p>Compex Net-A adapter</p> + </li> + + <li> + <p>CyQ've ELA-010</p> + </li> + + <li> + <p>D-Link DE-650/660</p> + </li> + + <li> + <p>Danpex EN-6200P2</p> + </li> + + <li> + <p>Elecom Laneed LD-CDL/TX, LD-CDF, LD-CDS, + LD-10/100CD, LD-CDWA (DP83902A), MACNICA Ethernet ME1 + for JEIDA</p> + </li> + + <li> + <p>IO DATA PCLATE</p> + </li> + + <li> + <p>IBM Creditcard Ethernet I/II</p> + </li> + + <li> + <p>IC-CARD Ethernet/IC-CARD+ Ethernet</p> + </li> + + <li> + <p>Kingston KNE-PC2, KNE-PCM/x Ethernet</p> + </li> + + <li> + <p>Linksys EC2T/PCMPC100/PCM100, PCMLM56, EtherFast + 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 + V2)</p> + </li> + + <li> + <p>MELCO + LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX</p> + </li> + + <li> + <p>NDC Ethernet Instant-Link</p> + </li> + + <li> + <p>National Semiconductor InfoMover NE4100</p> + </li> + + <li> + <p>NetGear FA-410TX</p> + </li> + + <li> + <p>Network Everywhere Ethernet 10BaseT PC Card</p> + </li> + + <li> + <p>Planex FNW-3600-T</p> + </li> + + <li> + <p>Socket LP-E</p> + </li> + + <li> + <p>Surecom EtherPerfect EP-427</p> + </li> + + <li> + <p>TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card</p> + </li> + + <li> + <p>Telecom Device SuperSocket RE450T</p> + </li> + </ul> + <br /> + <br /> + + <p>RealTek RTL 8002 Pocket Ethernet (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rdp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rdp</span>(4)</span></a> + driver)</p> + + <p>RealTek 8129/8139 Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek + 8139 clone)</p> + </li> + + <li> + <p>Allied Telesyn AT2550</p> + </li> + + <li> + <p>Allied Telesyn AT2500TX</p> + </li> + + <li> + <p>D-Link DFE-530TX+, DFE-538TX</p> + </li> + + <li> + <p>Farallon NetLINE 10/100 PCI</p> + </li> + + <li> + <p>Genius GF100TXR (RTL8139)</p> + </li> + + <li> + <p>KTX-9130TX 10/100 Fast Ethernet</p> + </li> + + <li> + <p>NDC Communications NE100TX-E</p> + </li> + + <li> + <p>Netronix Inc. EA-1210 NetEther 10/100</p> + </li> + + <li> + <p>OvisLink LEF-8129TX</p> + </li> + + <li> + <p>OvisLink LEF-8139TX</p> + </li> + + <li> + <p>SMC EZ Card 10/100 PCI 1211-TX</p> + </li> + </ul> + <br /> + <br /> + + <p>Lite-On 82c168/82c169 PNIC Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Kingston KNE110TX</p> + </li> + + <li> + <p>LinkSys EtherFast LNE100TX</p> + </li> + + <li> + <p>Matrox FastNIC 10/100</p> + </li> + + <li> + <p>NetGear FA310-TX Rev. D1</p> + </li> + </ul> + <br /> + <br /> + + <p>Macronix 98713, 98713A, 98715, 98715A and 98725 Fast + Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Accton EN1217 (98715A)</p> + </li> + + <li> + <p>Adico AE310TX (98715A)</p> + </li> + + <li> + <p>Compex RL100-TX (98713 or 98713A)</p> + </li> + + <li> + <p>CNet Pro120A (98713 or 98713A)</p> + </li> + + <li> + <p>CNet Pro120B (98715)</p> + </li> + + <li> + <p>NDC Communications SFA100A (98713A)</p> + </li> + + <li> + <p>SVEC PN102TX (98713)</p> + </li> + </ul> + <br /> + <br /> + + <p>Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>LinkSys EtherFast LNE100TX Version 2</p> + </li> + </ul> + <br /> + <br /> + + <p>Winbond W89C840F Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wb</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Trendware TE100-PCIE</p> + </li> + </ul> + <br /> + <br /> + + <p>VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine + II'', and VT86C105/VT86C105M ``Rhine III'' Fast Ethernet + NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vr</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>AOpen/Acer ALN-320</p> + </li> + + <li> + <p>D-Link DFE-530TX</p> + </li> + + <li> + <p>Hawking Technologies PN102TX</p> + </li> + </ul> + <br /> + <br /> + + <p>Silicon Integrated Systems SiS 900 and SiS 7016 PCI + Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sis</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>SiS 630, 635 and 735 motherboard chipsets</p> + </li> + </ul> + <br /> + <br /> + + <p>National Semiconductor DP83815 Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sis</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>NetGear FA311-TX</p> + </li> + + <li> + <p>NetGear FA312-TX</p> + </li> + </ul> + <br /> + <br /> + + <p>National Semiconductor DP83820 and DP83821 Gigabit + Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nge&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nge</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Addtron AEG320T</p> + </li> + + <li> + <p>Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T + (64-bit PCI)</p> + </li> + + <li> + <p>Asante FriendlyNet GigaNIC 1000TA and 1000TPC</p> + </li> + + <li> + <p>D-Link DGE-500T</p> + </li> + + <li> + <p>LinkSys EG1032 (32-bit PCI) and EG1064 (64-bit + PCI)</p> + </li> + + <li> + <p>Netgear GA621 and GA622T</p> + </li> + + <li> + <p>SMC EZ Card 1000 (SMC9462TX)</p> + </li> + + <li> + <p>Surecom Technology EP-320G-TX</p> + </li> + + <li> + <p>Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 + (64-bit PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>Sundance Technologies ST201 PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ste</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>D-Link DFE-550TX</p> + </li> + </ul> + <br /> + <br /> + + <p>SysKonnect SK-984x PCI Gigabit Ethernet cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sk</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>SK-9821 1000baseT copper, single port</p> + </li> + + <li> + <p>SK-9822 1000baseT copper, dual port</p> + </li> + + <li> + <p>SK-9841 1000baseLX single mode fiber, single + port</p> + </li> + + <li> + <p>SK-9842 1000baseLX single mode fiber, dual + port</p> + </li> + + <li> + <p>SK-9843 1000baseSX multimode fiber, single + port</p> + </li> + + <li> + <p>SK-9844 1000baseSX multimode fiber, dual port</p> + </li> + </ul> + <br /> + <br /> + + <p>Texas Instruments ThunderLAN PCI NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Compaq Netelligent 10, 10/100, 10/100 + Dual-Port</p> + </li> + + <li> + <p>Compaq Netelligent 10/100 Proliant</p> + </li> + + <li> + <p>Compaq Netelligent 10/100 TX Embedded UTP, 10 T + PCI UTP/Coax, 10/100 TX UTP</p> + </li> + + <li> + <p>Compaq NetFlex 3P, 3P Integrated, 3P w/BNC</p> + </li> + + <li> + <p>Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX + UTP</p> + </li> + + <li> + <p>Racore 8165 10/100baseTX</p> + </li> + + <li> + <p>Racore 8148 10baseT/100baseTX/100baseFX + multi-personality</p> + </li> + </ul> + <br /> + <br /> + + <p>ADMtek Inc. AL981-based PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <p>ADMtek Inc. AN985-based PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>LinkSys EtherFast LNE100TX v4.0/4.1</p> + </li> + </ul> + <br /> + <br /> + + <p>ADMtek Inc. AN986-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aue</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Abocom UFE1000, DSB650TX_NA</p> + </li> + + <li> + <p>Accton USB320-EC, SpeedStream</p> + </li> + + <li> + <p>ADMtek AN986, AN8511</p> + </li> + + <li> + <p>Billionton USB100, USB100LP, USB100EL, USBE100</p> + </li> + + <li> + <p>Corega Ether FEther USB-T, FEther USB-TX, FEther + USB-TXS</p> + </li> + + <li> + <p>D-Link DSB-650, DSB-650TX, DSB-650TX-PNA</p> + </li> + + <li> + <p>Elecom LD-USBL/TX</p> + </li> + + <li> + <p>Elsa Microlink USB2Ethernet</p> + </li> + + <li> + <p>I-O Data USB ETTX</p> + </li> + + <li> + <p>Kingston KNU101TX</p> + </li> + + <li> + <p>LinkSys USB10T, USB10TA, USB10TX, USB100TX, + USB100H1</p> + </li> + + <li> + <p>MELCO LUA-TX, LUA2-TX</p> + </li> + + <li> + <p>Planex UE-200TX</p> + </li> + + <li> + <p>Siemens Speedstream</p> + </li> + + <li> + <p>SmartBridges smartNIC</p> + </li> + + <li> + <p>SMC 2202USB</p> + </li> + + <li> + <p>SOHOware NUB100</p> + </li> + </ul> + <br /> + <br /> + + <p>CATC USB-EL1210A-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cue</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Belkin F5U011, F5U111</p> + </li> + + <li> + <p>CATC Netmate, Netmate II</p> + </li> + + <li> + <p>SmartBridges SmartLink</p> + </li> + </ul> + <br /> + <br /> + + <p>Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kue</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3c19250</p> + </li> + + <li> + <p>AOX USB101</p> + </li> + + <li> + <p>Abocom URE 450</p> + </li> + + <li> + <p>ADS Technologies USB-10BT</p> + </li> + + <li> + <p>ATen UC10T</p> + </li> + + <li> + <p>Corega USB-T</p> + </li> + + <li> + <p>D-Link DSB-650C</p> + </li> + + <li> + <p>Entrega NET-USB-E45</p> + </li> + + <li> + <p>I/O Data USB ETT</p> + </li> + + <li> + <p>Kawasaki DU-H3E</p> + </li> + + <li> + <p>LinkSys USB10T</p> + </li> + + <li> + <p>Netgear EA101</p> + </li> + + <li> + <p>Peracom USB Ethernet Adapter</p> + </li> + + <li> + <p>SMC 2102USB, 2104USB</p> + </li> + </ul> + <br /> + <br /> + + <p>ASIX Electronics AX88172-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">axe</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>D-Link DUBE100</p> + </li> + + <li> + <p>Linksys USB200M</p> + </li> + + <li> + <p>Netgear FA120</p> + </li> + </ul> + <br /> + <br /> + + <p>RealTek RTL8150-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rue</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>GREEN HOUSE GH-USB100B</p> + </li> + + <li> + <p>MELCO LUA-KTX</p> + </li> + </ul> + <br /> + <br /> + + <p>ASIX Electronics AX88140A PCI NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Alfa Inc. GFC2204</p> + </li> + + <li> + <p>CNet Pro110B</p> + </li> + </ul> + <br /> + <br /> + + <p>DEC EtherWORKS II and III NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=le&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">le</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>DE200, DE201, DE202, DE422</p> + </li> + + <li> + <p>DE203, DE204, DE205</p> + </li> + </ul> + <br /> + <br /> + + <p>DEC DC21040, DC21041, DC21140, DC21141, DC21142, and + DC21143 based NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">de</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Asante</p> + </li> + + <li> + <p>Cogent EM100FX and EM440TX</p> + </li> + + <li> + <p>DEC DE425, DE435, DE450, and DE500</p> + </li> + + <li> + <p>SMC Etherpower 8432T, 9332, and 9334</p> + </li> + + <li> + <p>ZYNX ZX 3xx</p> + </li> + </ul> + <br /> + <br /> + + <p>DEC/Intel 21143 based Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>DEC DE500</p> + </li> + + <li> + <p>Compaq Presario 7900 series built-in Ethernet</p> + </li> + + <li> + <p>D-Link DFE-570TX</p> + </li> + + <li> + <p>Kingston KNE100TX</p> + </li> + + <li> + <p>LinkSys EtherFast 10/100 Instant GigaDrive + built-in Ethernet</p> + </li> + </ul> + <br /> + <br /> + + <p>Davicom DM9009, DM9100 and DM9102 PCI Fast Ethernet + NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Jaton Corporation XpressNet</p> + </li> + </ul> + <br /> + <br /> + + <p>Xircom 3201 (Cardbus) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <p>Conexant LANfinity RS7112 (MiniPCI) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <p>Fujitsu MB86960A/MB86965A based Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fe</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>CONTEC C-NET(PC)C Ethernet</p> + </li> + + <li> + <p>Eiger Labs EPX-10BT</p> + </li> + + <li> + <p>Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 + Ethernet PCMCIA</p> + </li> + + <li> + <p>Fujitsu Towa LA501 Ethernet</p> + </li> + + <li> + <p>HITACHI HT-4840-11</p> + </li> + + <li> + <p>NextCom J Link NC5310</p> + </li> + + <li> + <p>RATOC REX-5588, REX-9822, REX-4886, REX-R280</p> + </li> + + <li> + <p>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</p> + </li> + </ul> + <br /> + <br /> + + <p>Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Intel EtherExpress Pro/100B PCI Fast Ethernet</p> + </li> + + <li> + <p>Intel InBusiness 10/100 PCI Network Adapter</p> + </li> + + <li> + <p>Intel PRO/100+ Management Adapter</p> + </li> + + <li> + <p>Intel Pro/100 VE Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 M Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters</p> + </li> + + <li> + <p>On-board Ethernet NICs on many Intel + motherboards.</p> + </li> + </ul> + <br /> + <br /> + + <p>Intel 82595-based Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ex&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ex</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Intel EtherExpress Pro/10 and Pro/10+ Ethernet</p> + </li> + + <li> + <p>Olicom OC2220</p> + </li> + </ul> + <br /> + <br /> + + <p>Intel 82586-based Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ie&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ie</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3Com 3C507 Etherlink 16/TP</p> + </li> + + <li> + <p>AT&T Starlan 10 and Starlan Fiber</p> + </li> + + <li> + <p>EN100</p> + </li> + + <li> + <p>Intel EtherExpress 16</p> + </li> + + <li> + <p>RACAL Interlan NI5210</p> + </li> + </ul> + <br /> + <br /> + + <p>3Com 3C5x9 Etherlink III NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ep&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ep</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3C509</p> + </li> + + <li> + <p>3C529 MCA</p> + </li> + + <li> + <p>3C579 EISA</p> + </li> + + <li> + <p>3CXE589EC, 3CXE589ET PCMCIA</p> + </li> + + <li> + <p>3C589/589B/589C/589D/589E/574TX/574B + PC-card/PCMCIA</p> + </li> + + <li> + <p>Megahertz 3CCFEM556BI, 3CXEM556, 3CCFEM556B</p> + </li> + + <li> + <p>OfficeConnect 3CXSH572BT</p> + </li> + + <li> + <p>Farallon EtherMac</p> + </li> + </ul> + <br /> + <br /> + + <p>3Com 3C501 8-bit ISA Ethernet NIC (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=el&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">el</span>(4)</span></a> driver)</p> + + <p>3Com Etherlink XL-based NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3C900/905/905B/905C PCI</p> + </li> + + <li> + <p>3C555/556/556B MiniPCI</p> + </li> + + <li> + <p>3C450-TX HomeConnect adapter</p> + </li> + + <li> + <p>3c980/3c980B Fast Etherlink XL server adapter</p> + </li> + + <li> + <p>3cSOHO100-TX OfficeConnect adapter</p> + </li> + + <li> + <p>3C575TX/575B/XFE575BT/575C/656/656B/656C + (Cardbus)</p> + </li> + + <li> + <p>Dell Optiplex GX1 on-board 3C918</p> + </li> + + <li> + <p>Dell On-board 3C920</p> + </li> + + <li> + <p>Dell Precision on-board 3C905B</p> + </li> + + <li> + <p>Dell Latitude laptop docking station embedded + 3C905-TX</p> + </li> + </ul> + <br /> + <br /> + + <p>3Com 3C59X series NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vx</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3C590 Etherlink III (PCI)</p> + </li> + + <li> + <p>3C595 Fast Etherlink III (PCI)</p> + </li> + + <li> + <p>3C592/3C597 (EISA)</p> + </li> + </ul> + <br /> + <br /> + + <p>Crystal Semiconductor CS89x0-based NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cs&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cs</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>IBM Etherjet ISA</p> + </li> + </ul> + <br /> + <br /> + + <p>Megahertz X-Jack Ethernet PC-Card CC-10BT (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sn&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sn</span>(4)</span></a> driver)</p> + + <p>Xircom X3201 (Cardbus) based Ethernet cards, including + the following:</p> + + <ul> + <li> + <p>IBM EtherJet Cardbus Adapter</p> + </li> + + <li> + <p>Intel PRO/100 Mobile Cardbus (versions that use + the X3201 chipset)</p> + </li> + + <li> + <p>Xircom Cardbus Realport</p> + </li> + + <li> + <p>Xircom Cardbus Ethernet 10/100</p> + </li> + + <li> + <p>Xircom Cardbus Ethernet II 10/100</p> + </li> + </ul> + <br /> + <br /> + + <p>Xircom CreditCard adapters (16 bit) and workalikes (xe + driver)</p> + + <ul> + <li> + <p>Accton EN2226/Fast EtherCard (16-bit version)</p> + </li> + + <li> + <p>Compaq Netelligent 10/100 PC Card</p> + </li> + + <li> + <p>Intel EtherExpress PRO/100 Mobile Adapter (16-bit + version)</p> + </li> + + <li> + <p>Xircom 10/100 Network PC Card adapter</p> + </li> + + <li> + <p>Xircom Realport card + modem(Ethernet part)</p> + </li> + + <li> + <p>Xircom CreditCard Ethernet 10/100</p> + </li> + + <li> + <p>Xircom CreditCard 10Base-T ``CreditCard Ethernet + Adapter IIps'' (PS-CE2-10)</p> + </li> + + <li> + <p>Xircom CreditCard Ethernet 10/100 + modem + (Ethernet part)</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet cards based on the Level 1 LXT1001 + NetCellerator controller (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">lge</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>D-Link DGE-500SX</p> + </li> + + <li> + <p>SMC TigerCard 1000 (SMC9462SX)</p> + </li> + </ul> + <br /> + <br /> + + <p>Ethernet and Fast Ethernet NICs based on the 3Com 3XP + Typhoon/Sidewinder (3CR990) chipset (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">txp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3CR990-TX-95</p> + </li> + + <li> + <p>3Com 3CR990-TX-97</p> + </li> + + <li> + <p>3Com 3CR990B-SRV</p> + </li> + + <li> + <p>3Com 3CR990B-TXM</p> + </li> + + <li> + <p>3Com 3CR990SVR95</p> + </li> + + <li> + <p>3Com 3CR990SVR97</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet NICs based on the Broadcom BCM570x + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bge</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3c996-SX, 3c996-T</p> + </li> + + <li> + <p>Netgear GA302T</p> + </li> + + <li> + <p>SysKonnect SK-9D21 and 9D41</p> + </li> + + <li> + <p>Integrated Gigabit Ethernet NICs on DELL PowerEdge + 2550 servers</p> + </li> + + <li> + <p>Integrated Gigabit Ethernet NICs on IBM x235 + servers</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet NICs based on the Intel 82542 and + 82543 controller chips (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gx</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> drivers), + plus NICs supported by the Intel 82540EM, 82544, 82545EM, + and 82546EB controller chips (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> driver + only)</p> + + <ul> + <li> + <p>Intel PRO/1000 Gigabit Ethernet</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> driver + is officially supported by Intel, but is only + supported on the i386.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Myson Ethernet NICs (my driver)</p> + + <ul> + <li> + <p>Myson MTD80X Based Fast Ethernet Card</p> + </li> + + <li> + <p>Myson MTD89X Based Gigabit Ethernet Card</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1629" name="AEN1629">3.3 FDDI + Interfaces</a></h2> + + <p>DEC DEFPA PCI (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fpa</span>(4)</span></a> + driver)</p> + + <p>DEC DEFEA EISA (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fpa</span>(4)</span></a> + driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1639" name="AEN1639">3.4 ATM + Interfaces</a></h2> + + <p>Efficient Networks, Inc. ENI-155p ATM PCI Adapters + (hea driver)</p> + + <p>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa + driver)</p> + + <p>IDT 77201/211 NICStAR ATM Adapters (idt driver)</p> + + <p>FORE Systems, Inc. LE155 ATM Adapter (idt driver)</p> + + <p>The ATM support in FreeBSD supports the following + signaling protocols:</p> + + <ul> + <li> + <p>The ATM Forum UNI 3.1 signaling protocol</p> + </li> + + <li> + <p>The ATM Forum UNI 3.0 signaling protocol</p> + </li> + + <li> + <p>The ATM Forum ILMI address registration</p> + </li> + + <li> + <p>FORE Systems' proprietary SPANS signaling + protocol</p> + </li> + + <li> + <p>Permanent Virtual Channels (PVCs)</p> + </li> + </ul> + <br /> + <br /> + + <p>Support for the IETF ``Classical IP and ARP over ATM'' + model is provided, compliant with the following RFCs and + Internet Drafts:</p> + + <ul> + <li> + <p>RFC 1483, ``Multiprotocol Encapsulation over ATM + Adaptation Layer 5''</p> + </li> + + <li> + <p>RFC 1577, ``Classical IP and ARP over ATM''</p> + </li> + + <li> + <p>RFC 1626, ``Default IP MTU for use over ATM + AAL5''</p> + </li> + + <li> + <p>RFC 1755, ``ATM Signaling Support for IP over + ATM''</p> + </li> + + <li> + <p>RFC 2225, ``Classical IP and ARP over ATM''</p> + </li> + + <li> + <p>RFC 2334, ``Server Cache Synchronization Protocol + (SCSP)''</p> + </li> + + <li> + <p>Internet Draft <tt + class="FILENAME">draft-ietf-ion-scsp-atmarp-00.txt</tt>, + ``A Distributed ATMARP Service Using SCSP''</p> + </li> + </ul> + <br /> + <br /> + + <p>Support for an ATM sockets interface is also + provided.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1683" name="AEN1683">3.5 + Wireless Network Interfaces</a></h2> + + <p>NCR / AT&T / Lucent Technologies WaveLan T1-speed + ISA/radio LAN cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wl</span>(4)</span></a> driver)</p> + + <p>Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA + standard speed (2Mbps) and turbo speed (6Mbps) wireless + network adapters and workalikes (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wi</span>(4)</span></a> driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The ISA versions of these adapters + are actually PCMCIA cards combined with an ISA to + PCMCIA bridge card, so both kinds of devices work + with the same driver.</p> + </blockquote> + </div> + + <ul> + <li> + <p>3COM 3crwe737A AirConnect Wireless LAN PC Card</p> + </li> + + <li> + <p>Accton airDirect WN3301</p> + </li> + + <li> + <p>Addtron AWA100</p> + </li> + + <li> + <p>Adtec ADLINK340APC</p> + </li> + + <li> + <p>Airway 802.11 Adapter</p> + </li> + + <li> + <p>Avaya Wireless PC Card</p> + </li> + + <li> + <p>Blue Concentric Circle CF Wireless LAN Model + WL-379F</p> + </li> + + <li> + <p>BreezeNET PC-DS.11</p> + </li> + + <li> + <p>Buffalo WLI-CF-S11G</p> + </li> + + <li> + <p>Cabletron RoamAbout 802.11 DS</p> + </li> + + <li> + <p>Compaq WL100, WL110</p> + </li> + + <li> + <p>Corega KK Wireless LAN PCC-11, PCCA-11, + PCCB-11</p> + </li> + + <li> + <p>D-Link DWL-650</p> + </li> + + <li> + <p>Dell TrueMobile 1150 Series</p> + </li> + + <li> + <p>ELECOM Air@Hawk/LD-WL11/PCC</p> + </li> + + <li> + <p>ELSA AirLancer MC-11</p> + </li> + + <li> + <p>Farallon Skyline 11Mbps Wireless</p> + </li> + + <li> + <p>ICOM SL-1100</p> + </li> + + <li> + <p>IBM High Rate Wireless LAN PC Card</p> + </li> + + <li> + <p>Intel PRO/Wireless 2011 LAN PC Card</p> + </li> + + <li> + <p>IO Data WN-B11/PCM</p> + </li> + + <li> + <p>Laneed Wireless card</p> + </li> + + <li> + <p>Linksys Instant Wireless WPC11</p> + </li> + + <li> + <p>Lucent WaveLAN/IEEE 802.11</p> + </li> + + <li> + <p>MELCO Airconnect WLI-PCM-S11, WLI-PCM-L11</p> + </li> + + <li> + <p>NCR WaveLAN/IEEE 802.11</p> + </li> + + <li> + <p>NEC Wireless Card CMZ-RT-WP</p> + </li> + + <li> + <p>NEC Aterm WL11C (PC-WL/11C)</p> + </li> + + <li> + <p>NEC PK-WL001</p> + </li> + + <li> + <p>Netgear MA401</p> + </li> + + <li> + <p>PLANEX GeoWave/GW-NS110</p> + </li> + + <li> + <p>Proxim Harmony, RangeLAN-DS</p> + </li> + + <li> + <p>SMC 2632W, 2602W</p> + </li> + + <li> + <p>Sony PCWA-C100</p> + </li> + + <li> + <p>TDK LAK-CD011WL</p> + </li> + + <li> + <p>Toshiba Wireless LAN Card</p> + </li> + + <li> + <p>US Robotics Wireless Card 2410</p> + </li> + </ul> + <br /> + <br /> + + <p>Aironet 802.11 wireless adapters (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">an</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Aironet 4500/4800 series (PCMCIA, PCI, and ISA + adapters are all supported)</p> + </li> + + <li> + <p>Cisco Systems Aironet 340 and 350 series (PCMCIA, + PCI, Mini-PCI, and ISA adapters are all + supported)</p> + </li> + + <li> + <p>Xircom Wireless Ethernet adapter (rebadged + Aironet)</p> + </li> + </ul> + <br /> + <br /> + + <p>Raytheon Raylink 2.4GHz wireless adapters (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ray&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ray</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Webgear Aviator</p> + </li> + + <li> + <p>Webgear Aviator Pro</p> + </li> + + <li> + <p>Raytheon Raylink PC Card</p> + </li> + </ul> + <br /> + <br /> + + <p>AMD Am79C930 and Harris (Intersil) based 802.11 cards + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=awi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">awi</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>BayStack 650 and 660</p> + </li> + + <li> + <p>Farallon SkyLINE Wireless</p> + </li> + + <li> + <p>Icom SL-200</p> + </li> + + <li> + <p>MELCO WLI-PCM</p> + </li> + + <li> + <p>NEL SSMagic</p> + </li> + + <li> + <p>Netwave AirSurfer Plus and AirSurfer Pro</p> + </li> + + <li> + <p>ZoomAir 4000</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1811" name="AEN1811">3.6 + Miscellaneous Networks</a></h2> + + <p>Granch SBNI12 point-to-point communications adapters + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbni&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbni</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>SBNI12-XX and SBNI12D-XX ISA and PCI</p> + </li> + </ul> + <br /> + <br /> + + <p>Granch SBNI16 SHDSL modems (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbsh&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbsh</span>(4)</span></a> + driver)</p> + + <p>SMC COM90cx6 ARCNET network adapters (cm driver)</p> + + <ul> + <li> + <p>SMC 90c26, 90c56, and 90c66 in 90c56 compatability + mode</p> + </li> + </ul> + <br /> + <br /> + + <p>LAN Media Corp WAN adapters based on the DEC ``Tulip'' + Fast Ethernet controller (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=lmc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">lmc</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>LMC1000 Synchronous Serial Interface adapter</p> + </li> + + <li> + <p>LMC1200 T1/E1 WAN adapter</p> + </li> + + <li> + <p>LMC5200 High Speed Synchronous Interface (HSSI) + adapter</p> + </li> + + <li> + <p>LMC5245 DS3 WAN adapter</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1842" name="AEN1842">3.7 ISDN + Interfaces</a></h2> + + <p>AcerISDN P10 ISA PnP (experimental)</p> + + <p>Asuscom ISDNlink 128K ISA</p> + + <p>ASUSCOM P-IN100-ST-D (and other Winbond W6692-based + cards)</p> + + <p>AVM</p> + + <ul> + <li> + <p>A1</p> + </li> + + <li> + <p>B1 ISA (tested with V2.0)</p> + </li> + + <li> + <p>B1 PCI (tested with V4.0)</p> + </li> + + <li> + <p>Fritz!Card classic</p> + </li> + + <li> + <p>Fritz!Card PnP</p> + </li> + + <li> + <p>Fritz!Card PCI</p> + </li> + + <li> + <p>Fritz!Card PCI, Version 2</p> + </li> + + <li> + <p>T1</p> + </li> + </ul> + <br /> + <br /> + + <p>Creatix</p> + + <ul> + <li> + <p>ISDN-S0</p> + </li> + + <li> + <p>ISDN-S0 P&P</p> + </li> + </ul> + <br /> + <br /> + + <p>Compaq Microcom 610 ISDN (Compaq series PSB2222I) ISA + PnP</p> + + <p>Dr. Neuhaus Niccy Go@ and compatibles</p> + + <p>Dynalink IS64PPH and IS64PPH+</p> + + <p>Eicon Diehl DIVA 2.0 and 2.02</p> + + <p>ELSA</p> + + <ul> + <li> + <p>ELSA PCC-16</p> + </li> + + <li> + <p>QuickStep 1000pro ISA</p> + </li> + + <li> + <p>MicroLink ISDN/PCI</p> + </li> + + <li> + <p>QuickStep 1000pro PCI</p> + </li> + </ul> + <br /> + <br /> + + <p>ITK ix1 Micro ( < V.3, non-PnP version )</p> + + <p>Sedlbauer Win Speed</p> + + <p>Siemens I-Surf 2.0</p> + + <p>TELEINT ISDN SPEED No.1 (experimental)</p> + + <p>Teles</p> + + <ul> + <li> + <p>S0/8</p> + </li> + + <li> + <p>S0/16</p> + </li> + + <li> + <p>S0/16.3</p> + </li> + + <li> + <p>S0/16.3 PnP</p> + </li> + + <li> + <p>16.3c ISA PnP (experimental)</p> + </li> + + <li> + <p>Teles PCI-TJ</p> + </li> + </ul> + <br /> + <br /> + + <p>Traverse Technologies NETjet-S PCI</p> + + <p>USRobotics Sportster ISDN TA intern</p> + + <p>Winbond W6692 based PCI cards</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1906" name="AEN1906">3.8 + Serial Interfaces</a></h2> + + <p>``PC standard'' 8250, 16450, and 16550-based serial + ports (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <p>AST 4 port serial card using shared IRQ</p> + + <p>ARNET serial cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ar&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ar</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>ARNET 8 port serial card using shared IRQ</p> + </li> + + <li> + <p>ARNET (now Digiboard) Sync 570/i high-speed + serial</p> + </li> + </ul> + <br /> + <br /> + + <p>Boca multi-port serial cards</p> + + <ul> + <li> + <p>Boca BB1004 4-Port serial card (Modems <span + class="emphasis"><i class="EMPHASIS">not</i></span> + supported)</p> + </li> + + <li> + <p>Boca IOAT66 6-Port serial card (Modems + supported)</p> + </li> + + <li> + <p>Boca BB1008 8-Port serial card (Modems <span + class="emphasis"><i class="EMPHASIS">not</i></span> + supported)</p> + </li> + + <li> + <p>Boca BB2016 16-Port serial card (Modems + supported)</p> + </li> + </ul> + <br /> + <br /> + + <p>Comtrol Rocketport card (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rp</span>(4)</span></a> driver)</p> + + <p>Cyclades Cyclom-Y serial board (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cy&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cy</span>(4)</span></a> driver)</p> + + <p>STB 4 port card using shared IRQ</p> + + <p>DigiBoard intelligent serial cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dgb&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dgb</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>DigiBoard PC/Xe series</p> + </li> + + <li> + <p>DigiBoard PC/Xi series</p> + </li> + </ul> + <br /> + <br /> + + <p>PCI-Based multi-port serial boards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=puc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">puc</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Actiontech 56K PCI</p> + </li> + + <li> + <p>Avlab Technology, PCI IO 2S and PCI IO 4S</p> + </li> + + <li> + <p>Comtrol RocketPort 550</p> + </li> + + <li> + <p>Decision Computers PCCOM 4-port serial and dual + port RS232/422/485</p> + </li> + + <li> + <p>Dolphin Peripherals 4025/4035/4036</p> + </li> + + <li> + <p>IC Book Labs Dreadnought 16x Lite and Pro</p> + </li> + + <li> + <p>Lava Computers + 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550</p> + </li> + + <li> + <p>Middle Digital, Weasle serial port</p> + </li> + + <li> + <p>Moxa Industio CP-114, Smartio C104H-PCI and + C168H/PCI</p> + </li> + + <li> + <p>NEC PK-UG-X001 and PK-UG-X008</p> + </li> + + <li> + <p>Netmos NM9835 PCI-2S-550</p> + </li> + + <li> + <p>Oxford Semiconductor OX16PCI954 PCI UART</p> + </li> + + <li> + <p>Syba Tech SD-LAB PCI-4S2P-550-ECP</p> + </li> + + <li> + <p>SIIG Cyber I/O PCI 16C550/16C650/16C850</p> + </li> + + <li> + <p>SIIG Cyber 2P1S PCI 16C550/16C650/16C850</p> + </li> + + <li> + <p>SIIG Cyber 2S1P PCI 16C550/16C650/16C850</p> + </li> + + <li> + <p>SIIG Cyber 4S PCI 16C550/16C650/16C850</p> + </li> + + <li> + <p>SIIG Cyber Serial (Single and Dual) PCI + 16C550/16C650/16C850</p> + </li> + + <li> + <p>Syba Tech Ltd. PCI-4S2P-550-ECP</p> + </li> + + <li> + <p>Titan PCI-200H and PCI-800H</p> + </li> + + <li> + <p>US Robotics (3Com) 3CP5609 modem</p> + </li> + + <li> + <p>VScom PCI-400 and PCI-800</p> + </li> + </ul> + <br /> + <br /> + + <p>SDL Communication serial boards</p> + + <ul> + <li> + <p>SDL Communications Riscom/8 Serial Board (rc + driver)</p> + </li> + + <li> + <p>SDL Communications RISCom/N2 and N2pci high-speed + sync serial boards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sr</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Stallion Technologies multiport serial boards</p> + + <ul> + <li> + <p>EasyIO (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=stl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">stl</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>EasyConnection 8/32 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=stl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">stl</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>EasyConnection 8/64 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=stli&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">stli</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>ONboard 4/16 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=stli&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">stli</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Brumby (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=stli&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">stli</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Specialix SI/XIO/SX multiport serial cards, with both + the older SIHOST2.x and the new ``enhanced'' (transputer + based, aka JET) host cards (ISA, EISA and PCI are + supported) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=si&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">si</span>(4)</span></a> driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2101" name="AEN2101">3.9 + Audio Devices</a></h2> + + <p>Advance (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbc</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Asound 100 and 110</p> + </li> + + <li> + <p>Logic ALS120 and ALS4000</p> + </li> + </ul> + <br /> + <br /> + + <p>CMedia sound chips</p> + + <ul> + <li> + <p>CMI8338/CMI8738</p> + </li> + </ul> + <br /> + <br /> + + <p>Crystal Semiconductor (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=csa&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">csa</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>CS461x/462x Audio Accelerator</p> + </li> + + <li> + <p>CS428x Audio Controller</p> + </li> + </ul> + <br /> + <br /> + + <p>ENSONIQ (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>AudioPCI ES1370/1371</p> + </li> + </ul> + <br /> + <br /> + + <p>ESS</p> + + <ul> + <li> + <p>ES1868, ES1869, ES1879 and ES1888 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbc</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Maestro-1, Maestro-2, and Maestro-2E</p> + </li> + + <li> + <p>Maestro-3/Allegro</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The Maestro-3/Allegro cannot be + compiled into the FreeBSD kernel due to licensing + restrictions. To use this driver, add the + following line to <tt + class="FILENAME">/boot/loader.conf</tt>:</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>snd_maestro3_load="YES"</b></tt> +</pre> + </blockquote> + </div> + </li> + </ul> + <br /> + <br /> + + <p>ForteMedia fm801</p> + + <p>Gravis (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gusc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gusc</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>UltraSound MAX</p> + </li> + + <li> + <p>UltraSound PnP</p> + </li> + </ul> + <br /> + <br /> + + <p>Intel 443MX, 810, 815, and 815E integrated sound + devices (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a> + driver)</p> + + <p>MSS/WSS Compatible DSPs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a> + driver)</p> + + <p>NeoMagic 256AV/ZX (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a> + driver)</p> + + <p>OPTi 931/82C931 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a> + driver)</p> + + <p>S3 Sonicvibes</p> + + <p>Creative Technologies SoundBlaster series (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbc</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>SoundBlaster</p> + </li> + + <li> + <p>SoundBlaster Pro</p> + </li> + + <li> + <p>SoundBlaster AWE-32</p> + </li> + + <li> + <p>SoundBlaster AWE-64</p> + </li> + + <li> + <p>SoundBlaster AWE-64 GOLD</p> + </li> + + <li> + <p>SoundBlaster ViBRA-16</p> + </li> + </ul> + <br /> + <br /> + + <p>Creative Technologies Sound Blaster Live! series + (emu10k1 driver)</p> + + <p>Trident 4DWave DX/NX (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a> + driver)</p> + + <p>VIA Technologies VT82C686A</p> + + <p>Yamaha</p> + + <ul> + <li> + <p>DS1</p> + </li> + + <li> + <p>DS1e</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2224" name="AEN2224">3.10 + Camera and Video Capture Devices</a></h2> + + <p>Brooktree Bt848/849/878/879-based frame grabbers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bktr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bktr</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>AverMedia cards</p> + </li> + + <li> + <p>Hauppauge Wincast TV and WinTV boards (PCI)</p> + </li> + + <li> + <p>Intel Smart Video Recorder III</p> + </li> + + <li> + <p>Miro PC TV</p> + </li> + + <li> + <p>STB TV PCI</p> + </li> + + <li> + <p>Video Highway XTreme</p> + </li> + + <li> + <p>VideoLogic Captivator PCI</p> + </li> + </ul> + <br /> + <br /> + + <p>Connectix QuickCam</p> + + <p>Cortex1 frame grabber (ctx driver)</p> + + <p>Creative Labs Video Spigot frame grabber (spigot + driver)</p> + + <p>Matrox Meteor Video frame grabber (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=meteor&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">meteor</span>(4)</span></a> + driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USB" name="USB">3.11 USB + Devices</a></h2> + + <p>A range of USB peripherals are supported; devices + known to work are listed in this section. Owing to the + generic nature of most USB devices, with some exceptions + any device of a given class will be supported, even if + not explicitly listed here.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> USB Ethernet adapters can be found in + the section listing <a href="#ETHERNET">Ethernet + interfaces</a>.</p> + </blockquote> + </div> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> USB Bluetooth adapters can be found + in <a href="#BLUETOOTH">Bluetooth</a> section.</p> + </blockquote> + </div> + + <p>Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ohci</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uhci</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>ALi Aladdin-V</p> + </li> + + <li> + <p>AMD-756</p> + </li> + + <li> + <p>CMD Tech 670 & 673</p> + </li> + + <li> + <p>Intel 82371SB (PIIX3)</p> + </li> + + <li> + <p>Intel 82371AB and EB (PIIX4)</p> + </li> + + <li> + <p>Intel 82801AA (ICH)</p> + </li> + + <li> + <p>Intel 82801AB (ICH0)</p> + </li> + + <li> + <p>Intel 82801BA/BAM (ICH2)</p> + </li> + + <li> + <p>Intel 82443MX</p> + </li> + + <li> + <p>NEC uPD 9210</p> + </li> + + <li> + <p>OPTi 82C861 (FireLink)</p> + </li> + + <li> + <p>SiS 5571</p> + </li> + + <li> + <p>VIA 83C572 USB</p> + </li> + + <li> + <p>UHCI or OHCI compliant motherboard chipsets (no + exceptions known)</p> + </li> + </ul> + <br /> + <br /> + + <p>USB host controllers (PCI)</p> + + <ul> + <li> + <p>ADS Electronics PCI plug-in card (2 ports)</p> + </li> + + <li> + <p>Entrega PCI plug-in card (4 ports)</p> + </li> + </ul> + <br /> + <br /> + + <p>USB 2.0 controllers using the EHCI interface (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ehci</span>(4)</span></a> + driver)</p> + + <p>Hubs</p> + + <ul> + <li> + <p>Andromeda hub</p> + </li> + + <li> + <p>MacAlly self powered hub (4 ports)</p> + </li> + + <li> + <p>NEC hub</p> + </li> + </ul> + <br /> + <br /> + + <p>Keyboards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ukbd</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Apple iMac keyboard</p> + </li> + + <li> + <p>BTC BTC7935 keyboard with PS/2 mouse port</p> + </li> + + <li> + <p>Cherry G81-3504 keyboard</p> + </li> + + <li> + <p>Logitech M2452 keyboard</p> + </li> + + <li> + <p>MacAlly iKey keyboard</p> + </li> + + <li> + <p>Microsoft keyboard</p> + </li> + + <li> + <p>Sun Microsystems Type 6 USB keyboard</p> + </li> + </ul> + <br /> + <br /> + + <p>Miscellaneous</p> + + <ul> + <li> + <p>ActiveWire I/O Board</p> + </li> + + <li> + <p>Diamond Rio 500, 600, and 800 MP3 players (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=urio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">urio</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>D-Link DSB-R100 USB Radio (ufm driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Modems (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umodem&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umodem</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 5605</p> + </li> + + <li> + <p>Metricom Ricochet GS USB wireless modem</p> + </li> + + <li> + <p>Yamaha Broadband Wireless Router RTW65b</p> + </li> + </ul> + <br /> + <br /> + + <p>Mice (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ums</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Agiler Mouse 29UO</p> + </li> + + <li> + <p>Apple iMac Mouse</p> + </li> + + <li> + <p>Belkin Mouse</p> + </li> + + <li> + <p>Chic mouse</p> + </li> + + <li> + <p>Cypress mouse</p> + </li> + + <li> + <p>Genius Niche mouse</p> + </li> + + <li> + <p>Kensington Mouse-in-a-Box</p> + </li> + + <li> + <p>Logitech wheel mouse (3 buttons)</p> + </li> + + <li> + <p>Logitech PS/2 / USB mouse (3 buttons)</p> + </li> + + <li> + <p>MacAlly mouse (3 buttons)</p> + </li> + + <li> + <p>Microsoft IntelliMouse (3 buttons)</p> + </li> + + <li> + <p>Sun Microsystems Type 6 USB Mouse</p> + </li> + + <li> + <p>Trust Ami Mouse (3 buttons)</p> + </li> + </ul> + <br /> + <br /> + + <p>Printers and parallel printer conversion cables (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ulpt</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>ATen parallel printer adapter</p> + </li> + + <li> + <p>Belkin F5U002 parallel printer adapter</p> + </li> + + <li> + <p>Entrega USB-to-parallel printer adapter</p> + </li> + </ul> + <br /> + <br /> + + <p>Serial devices</p> + + <ul> + <li> + <p>Belkin F5U103 and F5U120 (ubsa driver)</p> + </li> + + <li> + <p>e-Tek Labs Kwik232 (ubsa driver)</p> + </li> + + <li> + <p>GoHubs GoCOM232 (ubsa driver)</p> + </li> + + <li> + <p>HP USB-Serial adapter (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uftdi</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Inland UAS111 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uftdi</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Peracom single port serial adapter (ubsa + driver)</p> + </li> + + <li> + <p>Prolific PL-2303 serial adapter (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uplcom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uplcom</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>QVS USC-1000 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uftdi</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>SUNTAC Slipper U VS-10U (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uvscom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uvscom</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Scanners (through <b class="APPLICATION">SANE</b>) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uscanner&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uscanner</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Perfection 636U</p> + </li> + + <li> + <p>HP ScanJet 4100C, 5200C, 6300C</p> + </li> + </ul> + <br /> + <br /> + + <p>Storage (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umass</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M</p> + </li> + + <li> + <p>Denno FireWire/USB2 Removable 2.5-inch HDD Case + MIFU-25CB20</p> + </li> + + <li> + <p>FujiFilm Zip USB Drive ZDR100 USB A</p> + </li> + + <li> + <p>GREEN HOUSE USB Flash Memory ``PicoDrive'' + GH-UFD32M, 64M, 128M</p> + </li> + + <li> + <p>IBM 32MB USB Memory Key (P/N 22P5296)</p> + </li> + + <li> + <p>IBM ThinkPad USB Portable CD-ROM Drive (P/N + 33L5151)</p> + </li> + + <li> + <p>I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM + only)</p> + </li> + + <li> + <p>I-O DATA USB + CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive + DVR-iUH2 (CDROM, DVD-RAM only)</p> + </li> + + <li> + <p>Iomega USB Zip 100Mb (primitive support still)</p> + </li> + + <li> + <p>Iomega Zip750 USB2.0 Drive</p> + </li> + + <li> + <p>Keian USB1.1/2.0 3.5-inch HDD Case KU350A</p> + </li> + + <li> + <p>Kurouto Shikou USB 2.5-inch HDD Case + GAWAP2.5PS-USB2.0</p> + </li> + + <li> + <p>Logitec USB1.1/2.0 HDD Unit SHD-E60U2</p> + </li> + + <li> + <p>Logitec Mobile USB Memory LMC-256UD</p> + </li> + + <li> + <p>Logitec USB Double-Speed Floppy Drive LFD-31U2</p> + </li> + + <li> + <p>Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 + (CDROM only)</p> + </li> + + <li> + <p>Matshita CF-VFDU03 floppy drive</p> + </li> + + <li> + <p>MELCO USB2.0 MO Drive MO-CH640U2</p> + </li> + + <li> + <p>I-O DATA USB/IEEE1394 Portable HD Drive + HDP-i30P/CI, HDP-i40P/CI</p> + </li> + + <li> + <p>MELCO USB Flash Disk ``PetitDrive'', RUF-32M, + -64M, -128M, -256M</p> + </li> + + <li> + <p>MELCO USB2.0 Flash Disk ``PetitDrive2'', + RUF-256M/U2, -512M/U2</p> + </li> + + <li> + <p>MELCO USB Flash Disk ``ClipDrive'', RUF-C32M, + -C64M, -C128M, -C256M, -C512M</p> + </li> + + <li> + <p>Microtech USB-SCSI-HD 50 USB to SCSI cable</p> + </li> + + <li> + <p>NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U</p> + </li> + + <li> + <p>Panasonic floppy drive</p> + </li> + + <li> + <p>Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN + (CDROM only)</p> + </li> + + <li> + <p>RATOC Systems USB2.0 Removable HDD Case U2-MDK1, + U2-MDK1B</p> + </li> + + <li> + <p>Sony Portable CD-R/RW Drive CRX10U (CDROM + only)</p> + </li> + + <li> + <p>TEAC Portable USB CD-ROM Unit CD-110PU/210PU</p> + </li> + + <li> + <p>Y-E Data floppy drive (720/1.44/2.88Mb)</p> + </li> + </ul> + <br /> + <br /> + + <p>Audio Devices (uaudio driver)</p> + + <ul> + <li> + <p>Audio-Technica USB Digital Headphone + ATC-HA4USB</p> + </li> + + <li> + <p>Ergo Systems AUDIOTRAK OPTOPlay USB</p> + </li> + + <li> + <p>KENWOOD MD Personal Stereo System MDX-G7</p> + </li> + + <li> + <p>KENWOOD/SOTEC VH-7PC</p> + </li> + + <li> + <p>I-O DATA Analog to Digital USB Audio Adapter + DAVOX</p> + </li> + + <li> + <p>ONKYO PC Speaker GX-R5U(W)</p> + </li> + + <li> + <p>ONKYO USB Digital Audio Processor SE-U55X(S)</p> + </li> + + <li> + <p>Roland UA-5 USB Audio Interface ``Audio + Capture''</p> + </li> + + <li> + <p>Sony PC Active Speaker System SRS-T100PC</p> + </li> + </ul> + <br /> + <br /> + + <p>Handspring Visor and other PalmOS devices (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uvisor&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uvisor</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Handspring Visor</p> + </li> + + <li> + <p>Palm M125, M500, M505</p> + </li> + + <li> + <p>Sony Clie 4.0 and 4.1</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 + IEEE 1394 (Firewire) Devices</a></h2> + + <p>Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fwohci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fwohci</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Ricoh R5C552 chipset</p> + </li> + + <li> + <p>Sony CX3022 chipset</p> + </li> + + <li> + <p>TI TSB12LV22, LV23, 26 and TSB43AA22 chipsets</p> + </li> + + <li> + <p>uPD72861 chipset</p> + </li> + + <li> + <p>VIA VT6306 chipset</p> + </li> + </ul> + <br /> + <br /> + + <p>Storage (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Apple iPod</p> + </li> + + <li> + <p>Apple Macintosh G4 (target mode)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.13 + Bluetooth Devices</a></h2> + + <p>PCCARD Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_bt3c&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ng_bt3c</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com/HP 3CRWB6096-A PCCARD adapter</p> + </li> + </ul> + <br /> + <br /> + + <p>USB Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_ubt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ng_ubt</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3CREB96</p> + </li> + + <li> + <p>EPoX BT-DG02</p> + </li> + + <li> + <p>Mitsumi USB Bluetooth adapter</p> + </li> + + <li> + <p>MSI MS-6967</p> + </li> + + <li> + <p>TDK Bluetooth USB adapter</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2604" name="AEN2604">3.14 + Cryptographic Accelerators</a></h2> + + <p>Accelerators based on the Hifn 7751, 7811, or 7951 + chipsets (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=hifn&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">hifn</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Invertex AEON</p> + </li> + + <li> + <p>Hifn 7751 reference board</p> + </li> + + <li> + <p>Global Technologies Group PowerCrypt and + XL-Crypt</p> + </li> + + <li> + <p>NetSec 7751</p> + </li> + + <li> + <p>Soekris Engineering vpn1201 and vpn1211</p> + </li> + </ul> + <br /> + <br /> + + <p>Accelerators based on the Bluesteel 5501 or 5601 + chipsets (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ubsec</span>(4)</span></a> + driver)</p> + + <p>Accelerators based on the Broadcom BCM5801, BCM5802, + BCM5805, BCM5820, BCM 5821, BCM5822 chipsets (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ubsec</span>(4)</span></a> + driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2629" name="AEN2629">3.15 + Miscellaneous</a></h2> + + <p>FAX-Modem/PCCARD</p> + + <ul> + <li> + <p>MELCO IGM-PCM56K/IGM-PCM56KH</p> + </li> + + <li> + <p>Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD + terminal)</p> + </li> + </ul> + <br /> + <br /> + + <p>Floppy drives (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fdc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fdc</span>(4)</span></a> + driver)</p> + + <p>Genius and Mustek hand scanners</p> + + <p>GPB and Transputer drivers</p> + + <p>VGA-compatible video cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vga&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vga</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Information regarding specific video + cards and compatibility with <b + class="APPLICATION">XFree86</b> can be found at <a + href="http://www.xfree86.org/" + target="_top">http://www.xfree86.org/</a>.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Keyboards including:</p> + + <ul> + <li> + <p>AT-style keyboards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">atkbd</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>PS/2 keyboards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">atkbd</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>USB keyboards (specific instances are listed in + the section describing <a href="#USB">USB + devices</a>)</p> + </li> + </ul> + <br /> + <br /> + + <p>Loran-C receiver (Dave Mills experimental hardware, + loran driver).</p> + + <p>Pointing devices including:</p> + + <ul> + <li> + <p>Bus mice and compatible devices (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mse&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mse</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>PS/2 mice and compatible devices, including many + laptop pointing devices (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">psm</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Serial mice and compatible devices</p> + </li> + + <li> + <p>USB mice (specific instances are listed in the + section describing <a href="#USB">USB + devices</a>)</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">moused</span>(8)</span></a> has + more information on using pointing devices with + FreeBSD. Information on using pointing devices with + <b class="APPLICATION">XFree86</b> can be found at <a + href="http://www.xfree86.org/" + target="_top">http://www.xfree86.org/</a>.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>``PC standard'' parallel ports (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ppc</span>(4)</span></a> + driver)</p> + + <p>PC-compatible joysticks (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=joy&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">joy</span>(4)</span></a> + driver)</p> + + <p>PHS Data Communication Card/PCCARD</p> + + <ul> + <li> + <p>NTT DoCoMo P-in Comp@ct</p> + </li> + + <li> + <p>Panasonic KX-PH405</p> + </li> + + <li> + <p>SII MC-P200</p> + </li> + </ul> + <br /> + <br /> + + <p>Xilinx XC6200-based reconfigurable hardware cards + compatible with the HOT1 from <a + href="http://www.vcc.com/" target="_top">Virtual + Computers</a> (xrpu driver).</p> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-ia64.html b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-ia64.html new file mode 100644 index 0000000000..76cdacfabb --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-ia64.html @@ -0,0 +1,835 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/ia64 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/ia64 + 5.1-RELEASE Hardware Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Documentation + Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#PROC-IA64">Supported Processors and + Motherboards</a></dt> + + <dd> + <dl> + <dt>2.1 <a href="#AEN38">Supported Devices + Overview</a></dt> + </dl> + </dd> + + <dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + + <dd> + <dl> + <dt>3.1 <a href="#AEN92">Disk Controllers</a></dt> + + <dt>3.2 <a href="#ETHERNET">Ethernet + Interfaces</a></dt> + + <dt>3.3 <a href="#AEN1658">FDDI Interfaces</a></dt> + + <dt>3.4 <a href="#AEN1668">ATM Interfaces</a></dt> + + <dt>3.5 <a href="#AEN1712">Wireless Network + Interfaces</a></dt> + + <dt>3.6 <a href="#AEN1840">Miscellaneous + Networks</a></dt> + + <dt>3.7 <a href="#AEN1871">ISDN Interfaces</a></dt> + + <dt>3.8 <a href="#AEN1935">Serial Interfaces</a></dt> + + <dt>3.9 <a href="#AEN2130">Audio Devices</a></dt> + + <dt>3.10 <a href="#AEN2253">Camera and Video Capture + Devices</a></dt> + + <dt>3.11 <a href="#USB">USB Devices</a></dt> + + <dt>3.12 <a href="#FIREWIRE">IEEE 1394 (Firewire) + Devices</a></dt> + + <dt>3.13 <a href="#BLUETOOTH">Bluetooth + Devices</a></dt> + + <dt>3.14 <a href="#AEN2633">Cryptographic + Accelerators</a></dt> + + <dt>3.15 <a href="#AEN2658">Miscellaneous</a></dt> + </dl> + </dd> + </dl> + </div> + + <blockquote class="ABSTRACT"> + <div class="ABSTRACT"> + <a id="AEN11" name="AEN11"></a> + + <p>This is a preliminary document. It is incomplete, and + in need of additional content. Please send additional + information on IA-64 processors, motherboards, and + various devices working on FreeBSD to the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ia64" + target="_top">FreeBSD IA64 porting mailing list</a>.</p> + </div> + </blockquote> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the hardware compatibility notes + for FreeBSD 5.1-RELEASE on the IA-64 hardware platform + (also referred to as FreeBSD/ia64 5.1-RELEASE). It lists + devices known to work on this platform, as well as some + notes on boot-time kernel customization that may be useful + when attempting to configure support for new devices.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> This document includes information + specific to the IA-64 hardware platform. Versions of + the hardware compatibility notes for other + architectures will differ in some details.</p> + </blockquote> + </div> + + <p>More information on FreeBSD/ia64 is contained on the <a + href="http://www.FreeBSD.org/platforms/ia64/index.html" + target="_top">FreeBSD/ia64 Project</a> page.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="PROC-IA64" name="PROC-IA64">2 + Supported Processors and Motherboards</a></h1> + + <p>Currently supported processors are the <a + href="http://www.intel.com/design/itanium/itanium/index.htm" + target="_top">Itanium</a> and the <a + href="http://www.intel.com/design/itanium2/index.htm" + target="_top">Itanium 2</a>.</p> + + <p>Supported chipsets include:</p> + + <ul> + <li> + <p>HP zx1 (only on development branch, see the <a + href="http://perforce.FreeBSD.org/" + target="_top">Perforce repository</a>)</p> + </li> + + <li> + <p>HP i2000</p> + </li> + + <li> + <p>Intel 460GX</p> + </li> + + <li> + <p>Intel E8870</p> + </li> + </ul> + + <p>Both Uniprocessor (UP) and Symmetric Multi-processor + (SMP) configurations are under active development. At this + time, SMP-enabled systems are considered less stable. The + current priorities are UP fixes to improve stability.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN38" name="AEN38">2.1 + Supported Devices Overview</a></h2> + + <p>This section contains additional information about + what devices may or may not be supported by + FreeBSD/ia64.</p> + + <p>Except for the PC chipset embedded <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> + controllers, most should work out of the box. Eventually, + all ia64-compatible ATA controllers are expected to be + fully supported. Refer to the following sections for + various disk controllers and their current status.</p> + + <p>In general, ``PC standard'' serial ports supported by + the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> driver are + expected to work on Intel legacy machines, but not PA + legacy machines. The reason is that all devices on HP + machines are memory-mapped and there is <span + class="emphasis"><i class="EMPHASIS">no</i></span> ISA + device support other than the PCI dictated VGA + legacy.</p> + + <p>In addition to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> devices, + the following devices fail on non-Intel legacy machines + (but should work on boxes with an Intel legacy) because + their drivers make ISA-specific assumptions that do not + hold:</p> + + <div class="INFORMALTABLE"> + <a id="AEN55" name="AEN55"></a> + + <table border="0" class="CALSTABLE"> + <tbody> + <tr> + <td align="LEFT" valign="TOP"><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a></td> + + <td align="LEFT" valign="TOP">No support for + memory-mapped I/O</td> + </tr> + + <tr> + <td align="LEFT" valign="TOP"><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syscons&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syscons</span>(4)</span></a></td> + + <td align="LEFT" valign="TOP">Expect BIOS, VGA + probes, etc.</td> + </tr> + + <tr> + <td align="LEFT" valign="TOP"><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcm</span>(4)</span></a></td> + + <td align="LEFT" valign="TOP">Probes MSS ISA + ports <span class="emphasis"><i + class="EMPHASIS">ad nauseum</i></span></td> + </tr> + + <tr> + <td align="LEFT" valign="TOP"><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">atkbd</span>(4)</span></a>, + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">psm</span>(4)</span></a></td> + + <td align="LEFT" valign="TOP">Fixed ISA port + locations</td> + </tr> + </tbody> + </table> + </div> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 + Supported Devices</a></h1> + $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.157 2003/05/30 11:24:00 nyan Exp $ + + <p>This section describes the devices currently known to be + supported by with FreeBSD on the IA-64 platform. Other + configurations may also work, but simply have not been + tested yet. Feedback, updates, and corrections to this list + are encouraged.</p> + + <p>Where possible, the drivers applicable to each device or + class of devices is listed. If the driver in question has a + manual page in the FreeBSD base distribution (most should), + it is referenced here.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN92" name="AEN92">3.1 Disk + Controllers</a></h2> + + <p>IDE/ATA controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6</p> + </li> + + <li> + <p>AMD 756 ATA66, 766 ATA100, 768 ATA100</p> + </li> + + <li> + <p>Cenatek Rocket Drive</p> + </li> + + <li> + <p>CMD 646, 648 ATA66, and 649 ATA100</p> + </li> + + <li> + <p>Cypress 82C693</p> + </li> + + <li> + <p>Cyrix 5530 ATA33</p> + </li> + + <li> + <p>HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 + ATA133, HPT374 ATA133</p> + </li> + + <li> + <p>Intel PIIX, PIIX3, PIIX4</p> + </li> + + <li> + <p>Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 + ATA100</p> + </li> + + <li> + <p>nVidia nForce ATA100, nForce2 ATA133</p> + </li> + + <li> + <p>Promise ATA100 OEM chip (pdc20265)</p> + </li> + + <li> + <p>Promise ATA133 OEM chip (pdc20269)</p> + </li> + + <li> + <p>Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 + TX2/TX2000</p> + </li> + + <li> + <p>Promise SATA150 TX2/TX4 Serial ATA/150</p> + </li> + + <li> + <p>Promise Ultra-33, -66, -100, -133 + TX2/TX2000/TX4000</p> + </li> + + <li> + <p>ServerWorks ROSB4 ATA33</p> + </li> + + <li> + <p>ServerWorks CSB5 and CSB6 ATA66/ATA100</p> + </li> + + <li> + <p>Sil 0680 UDMA6</p> + </li> + + <li> + <p>SiS 530, 540, 550, 620</p> + </li> + + <li> + <p>SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, + 650, 651, 652, 655, 658, 730, 733, 735, 740, 745, + 746, 748, 750, 751, 752, 755</p> + </li> + + <li> + <p>SiS 5591 ATA100</p> + </li> + + <li> + <p>VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, + 82C686b ATA100</p> + </li> + + <li> + <p>VIA 8233, 8235 ATA133</p> + </li> + </ul> + <br /> + <br /> + + <p>Qlogic controllers and variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">isp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Qlogic 1020, 1040 SCSI and Ultra SCSI host + adapters</p> + </li> + + <li> + <p>Qlogic 1240 dual Ultra SCSI controllers</p> + </li> + + <li> + <p>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD + controllers</p> + </li> + + <li> + <p>Qlogic 12160 Ultra3 LVD controllers</p> + </li> + + <li> + <p>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI + controllers</p> + </li> + + <li> + <p>Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre + Channel SCSI controllers</p> + </li> + + <li> + <p>Performance Technology SBS440 ISP1000 variants</p> + </li> + + <li> + <p>Performance Technology SBS450 ISP1040 variants</p> + </li> + + <li> + <p>Performance Technology SBS470 ISP2100 variants</p> + </li> + + <li> + <p>Antares Microsystems P-0033 ISP2100 variants</p> + </li> + </ul> + <br /> + <br /> + + <p>LSI Logic Fusion/MP architecture Fiber Channel + controllers (mpt driver)</p> + + <ul> + <li> + <p>LSI 53c1020, 53c1030</p> + </li> + </ul> + <br /> + <br /> + + <p>With all supported SCSI controllers, full support is + provided for SCSI-I, SCSI-II, and SCSI-III peripherals, + including hard disks, optical disks, tape drives + (including DAT, 8mm Exabyte, Mammoth, and DLT), medium + changers, processor target devices and CD-ROM drives. + WORM devices that support CD-ROM commands are supported + for read-only access by the CD-ROM drivers (such as <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>). + WORM/CD-R/CD-RW writing support is provided by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&sektion=1&manpath=FreeBSD+Ports"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cdrecord</span>(1)</span></a>, + which is a part of the <a + href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/cdrtools/pkg-descr"> + <tt class="FILENAME">sysutils/cdrtools</tt></a> port in + the Ports Collection.</p> + + <p>The following CD-ROM type systems are supported at + this time:</p> + + <ul> + <li> + <p>SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>)</p> + </li> + + <li> + <p>ATAPI IDE interface (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=acd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">acd</span>(4)</span></a>)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 + Ethernet Interfaces</a></h2> + + <p>Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Intel EtherExpress Pro/100B PCI Fast Ethernet</p> + </li> + + <li> + <p>Intel InBusiness 10/100 PCI Network Adapter</p> + </li> + + <li> + <p>Intel PRO/100+ Management Adapter</p> + </li> + + <li> + <p>Intel Pro/100 VE Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 M Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters</p> + </li> + + <li> + <p>On-board Ethernet NICs on many Intel + motherboards.</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet NICs based on the Broadcom BCM570x + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bge</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3c996-SX, 3c996-T</p> + </li> + + <li> + <p>Netgear GA302T</p> + </li> + + <li> + <p>SysKonnect SK-9D21 and 9D41</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet NICs based on the Intel 82542 and + 82543 controller chips (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gx</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> drivers), + plus NICs supported by the Intel 82540EM, 82544, 82545EM, + and 82546EB controller chips (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> driver + only)</p> + + <ul> + <li> + <p>Intel PRO/1000 Gigabit Ethernet</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> driver + is officially supported by Intel, but is only + supported on the i386.</p> + </blockquote> + </div> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1658" name="AEN1658">3.3 FDDI + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1668" name="AEN1668">3.4 ATM + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1712" name="AEN1712">3.5 + Wireless Network Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1840" name="AEN1840">3.6 + Miscellaneous Networks</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1871" name="AEN1871">3.7 ISDN + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1935" name="AEN1935">3.8 + Serial Interfaces</a></h2> + + <p>``PC standard'' 8250, 16450, and 16550-based serial + ports (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <p>PCI-Based multi-port serial boards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=puc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">puc</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Diva Serial (GSP) Multiport UART (development + branch only)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2130" name="AEN2130">3.9 + Audio Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2253" name="AEN2253">3.10 + Camera and Video Capture Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USB" name="USB">3.11 USB + Devices</a></h2> + + <p>Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ohci</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uhci</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>UHCI or OHCI compliant motherboard chipsets (no + exceptions known)</p> + </li> + </ul> + <br /> + <br /> + + <p>USB 2.0 controllers using the EHCI interface (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ehci</span>(4)</span></a> + driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 + IEEE 1394 (Firewire) Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.13 + Bluetooth Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2633" name="AEN2633">3.14 + Cryptographic Accelerators</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2658" name="AEN2658">3.15 + Miscellaneous</a></h2> + + <p>VGA-compatible video cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vga&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vga</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Information regarding specific video + cards and compatibility with <b + class="APPLICATION">XFree86</b> can be found at <a + href="http://www.xfree86.org/" + target="_top">http://www.xfree86.org/</a>.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Keyboards including:</p> + + <ul> + <li> + <p>PS/2 keyboards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=atkbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">atkbd</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Pointing devices including:</p> + + <ul> + <li> + <p>PS/2 mice and compatible devices, including many + laptop pointing devices (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=psm&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">psm</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Serial mice and compatible devices</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">moused</span>(8)</span></a> has + more information on using pointing devices with + FreeBSD. Information on using pointing devices with + <b class="APPLICATION">XFree86</b> can be found at <a + href="http://www.xfree86.org/" + target="_top">http://www.xfree86.org/</a>.</p> + </blockquote> + </div> + <br /> + <br /> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-pc98.html b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-pc98.html new file mode 100644 index 0000000000..0ba8f39cf3 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-pc98.html @@ -0,0 +1,3431 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/pc98 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/pc98 + 5.1-RELEASE Hardware Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Documentation + Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#SUPPORT-SYS">Supported Systems</a></dt> + + <dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + + <dd> + <dl> + <dt>3.1 <a href="#AEN32">Disk Controllers</a></dt> + + <dt>3.2 <a href="#ETHERNET">Ethernet + Interfaces</a></dt> + + <dt>3.3 <a href="#AEN1598">FDDI Interfaces</a></dt> + + <dt>3.4 <a href="#AEN1608">ATM Interfaces</a></dt> + + <dt>3.5 <a href="#AEN1652">Wireless Network + Interfaces</a></dt> + + <dt>3.6 <a href="#AEN1780">Miscellaneous + Networks</a></dt> + + <dt>3.7 <a href="#AEN1811">ISDN Interfaces</a></dt> + + <dt>3.8 <a href="#AEN1875">Serial Interfaces</a></dt> + + <dt>3.9 <a href="#AEN2070">Audio Devices</a></dt> + + <dt>3.10 <a href="#AEN2193">Camera and Video Capture + Devices</a></dt> + + <dt>3.11 <a href="#USB">USB Devices</a></dt> + + <dt>3.12 <a href="#FIREWIRE">IEEE 1394 (Firewire) + Devices</a></dt> + + <dt>3.13 <a href="#BLUETOOTH">Bluetooth + Devices</a></dt> + + <dt>3.14 <a href="#AEN2573">Cryptographic + Accelerators</a></dt> + + <dt>3.15 <a href="#AEN2598">Miscellaneous</a></dt> + </dl> + </dd> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the hardware compatibility notes + for FreeBSD 5.1-RELEASE on the NEC PC-98x1 hardware + platform (also referred to as FreeBSD/pc98 5.1-RELEASE). It + lists devices known to work on this platform, as well as + some notes on boot-time kernel customization that may be + useful when attempting to configure support for new + devices.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> This document includes information + specific to the NEC PC-98x1 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 id="SUPPORT-SYS" name="SUPPORT-SYS">2 + Supported Systems</a></h1> + + <p>NEC PC-9801/9821 series with almost all i386-compatible + processors, including 80386, 80486, Pentium, Pentium Pro, + Pentium II, and variants. All i386-compatible processors by + AMD, Cyrix, IBM, and IDT are also supported.</p> + + <p>NEC FC-9801/9821 series, and NEC SV-98 series (both of + them are compatible with PC-9801/9821 series) should be + supported.</p> + + <p>EPSON PC-386/486/586 series, which are compatible with + NEC PC-9801 series are supported.</p> + + <p>High-resolution mode is not supported. NEC + PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in + normal (PC-9801 compatible) mode only.</p> + + <p>Although there are some multi-processor systems (such as + Rs20/B20), SMP-related features of FreeBSD are not + supported yet.</p> + + <p>PC-9801/9821 standard bus (called C-Bus), PC-9801NOTE + expansion bus (110pin), and PCI bus are supported. New + Extend Standard Architecture (NESA) bus (used in PC-H98, + SV-H98, and FC-H98 series) is not supported.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 + Supported Devices</a></h1> + $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.157 2003/05/30 11:24:00 nyan Exp $ + + <p>This section describes the devices currently known to be + supported by with FreeBSD on the NEC PC-98x1 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 id="AEN32" name="AEN32">3.1 Disk + Controllers</a></h2> + + <p>IDE/ATA controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6</p> + </li> + + <li> + <p>AMD 756 ATA66, 766 ATA100, 768 ATA100</p> + </li> + + <li> + <p>Cenatek Rocket Drive</p> + </li> + + <li> + <p>CMD 646, 648 ATA66, and 649 ATA100</p> + </li> + + <li> + <p>Cypress 82C693</p> + </li> + + <li> + <p>Cyrix 5530 ATA33</p> + </li> + + <li> + <p>HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 + ATA133, HPT374 ATA133</p> + </li> + + <li> + <p>Intel PIIX, PIIX3, PIIX4</p> + </li> + + <li> + <p>Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 + ATA100</p> + </li> + + <li> + <p>nVidia nForce ATA100, nForce2 ATA133</p> + </li> + + <li> + <p>Promise ATA100 OEM chip (pdc20265)</p> + </li> + + <li> + <p>Promise ATA133 OEM chip (pdc20269)</p> + </li> + + <li> + <p>Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 + TX2/TX2000</p> + </li> + + <li> + <p>Promise SATA150 TX2/TX4 Serial ATA/150</p> + </li> + + <li> + <p>Promise Ultra-33, -66, -100, -133 + TX2/TX2000/TX4000</p> + </li> + + <li> + <p>ServerWorks ROSB4 ATA33</p> + </li> + + <li> + <p>ServerWorks CSB5 and CSB6 ATA66/ATA100</p> + </li> + + <li> + <p>Sil 0680 UDMA6</p> + </li> + + <li> + <p>SiS 530, 540, 550, 620</p> + </li> + + <li> + <p>SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, + 650, 651, 652, 655, 658, 730, 733, 735, 740, 745, + 746, 748, 750, 751, 752, 755</p> + </li> + + <li> + <p>SiS 5591 ATA100</p> + </li> + + <li> + <p>VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, + 82C686b ATA100</p> + </li> + + <li> + <p>VIA 8233, 8235 ATA133</p> + </li> + </ul> + <br /> + <br /> + + <p>IDE/ATA controllers (wdc driver)</p> + + <ul> + <li> + <p>On-board IDE controller</p> + </li> + </ul> + <br /> + <br /> + + <p>Adaptec SCSI Controllers</p> + + <ul> + <li> + <p>NEC PC-9801-100 and Adaptec AHA-1030P, 1030B(<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aic&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aic</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>NEC PC-9821Xt13 and RvII26 internal, NEC + PC-9821X-B02L/B09, NEC SV-98/2-B03, Adaptec + AHA-2940J, AHA-2940AU and AHA-2940N (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahc</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>NEC PC-9801-55, 92 and their compatible C-Bus SCSI + interfaces (ct driver)</p> + + <ul> + <li> + <p>NEC PC-9801-55, 92 and their compatibles</p> + + <p>ICM IF-2660</p> + + <p>Midori-Denshi MDC-554NA</p> + + <p>Logitec LHA-N151</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <tt class="LITERAL">flags + 0x00000</tt> is necessary in kernel configuration + for DMA transfer mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>I-O DATA SC-98II</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <tt class="LITERAL">flags + 0x10000</tt> is necessary in kernel configuration + for DMA transfer mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>TEXA HA-55BS2 and later</p> + + <p>Midori-Denshi MDC-926Rs</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <tt class="LITERAL">flags + 0x20000</tt> is necessary in kernel configuration + for Bus-master transfer mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>ELECOM Bus-master SCSI interfaces</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <tt class="LITERAL">flags + 0x30000</tt> is necessary in kernel configuration + for Bus-master transfer mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>All SMIT transfer type SCSI interfaces</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <tt class="LITERAL">flags + 0x40000</tt> is necessary in kernel configuration + for SMIT transfer mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>Logitec LHA-20x series</p> + + <p>ICM IF-2766, IF-2766ET, IF-2767 and IF-2769</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <tt class="LITERAL">flags + 0x50000</tt> is necessary in kernel configuration + for Bus-master transfer mode.</p> + </blockquote> + </div> + </li> + </ul> + <br /> + <br /> + + <p>NEC PC-9801-55, 92 and their compatible C-Bus SCSI + interfaces (bs driver)</p> + + <ul> + <li> + <p>NEC PC-9801-55, 92 and their compatibles</p> + + <p>ICM IF-2660</p> + + <p>Midori-Denshi MDC-554NA</p> + + <p>Logitec LHA-N151</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x00000" is necessary in + kernel configuration for DMA transfer mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>I-O DATA SC-98II</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x10000" is necessary in + kernel configuration for DMA transfer mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>TEXA HA-55BS2 and later</p> + + <p>Midori-Denshi MDC-926Rs</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x20000" is necessary in + kernel configuration for Bus-master transfer + mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>ELECOM Bus-master SCSI interfaces</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x30000" is necessary in + kernel configuration for Bus-master transfer + mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>All SMIT transfer type SCSI interfaces</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x40000" is necessary in + kernel configuration for SMIT transfer mode.</p> + </blockquote> + </div> + </li> + + <li> + <p>Logitec LHA-20x series</p> + + <p>ICM IF-2766, IF-2766ET, IF-2767 and IF-2769</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x50000" is necessary in + kernel configuration for Bus-master transfer + mode.</p> + </blockquote> + </div> + </li> + </ul> + <br /> + <br /> + + <p>AdvanSys SCSI controllers (all models, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adv&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adv</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adw</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>MELCO IFC-USP, RATOC REX-PCI30 and @Nifty FNECHARD + IFC-USUP-TX (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adv&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adv</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, + 53C825, 53C825a, 53C860, 53C875, 53C875a, 53C876, 53C885, + 53C895, 53C895a, 53C896, 53C1010-33, 53C1010-66, 53C1000, + 53C1000R PCI SCSI controllers, either embedded on + motherboard or on add-on boards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ncr</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sym</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>I-O DATA SC-98/PCI and SC-PCI (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ncr</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>I-O DATA SC-UPCI and Logitec LHA-521UA (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sym</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>NCR 53C500 based PC-Card SCSI host adapters (ncv + driver)</p> + + <ul> + <li> + <p>IO DATA PCSC-DV</p> + </li> + + <li> + <p>KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004</p> + </li> + + <li> + <p>Macnica Miracle SCSI-II mPS110</p> + </li> + + <li> + <p>Media Intelligent MSC-110, MSC-200</p> + </li> + + <li> + <p>NEC PC-9801N-J03R</p> + </li> + + <li> + <p>New Media Corporation BASICS SCSI</p> + </li> + + <li> + <p>Qlogic Fast SCSI</p> + </li> + + <li> + <p>RATOC REX-9530, REX-5572 (as SCSI only)</p> + </li> + </ul> + <br /> + <br /> + + <p>TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters + (stg driver)</p> + + <ul> + <li> + <p>Future Domain SCSI2GO</p> + </li> + + <li> + <p>IBM SCSI PCMCIA Card</p> + </li> + + <li> + <p>ICM PSC-2401 SCSI</p> + </li> + + <li> + <p>MELCO IFC-SC</p> + </li> + + <li> + <p>RATOC REX-5536, REX-5536AM, REX-5536M, + REX-9836A</p> + </li> + </ul> + <br /> + <br /> + + <p>Qlogic controllers and variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">isp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Qlogic SCSI interface</p> + </li> + </ul> + <br /> + <br /> + + <p>Tekram DC390 and DC390T controllers, maybe other cards + based on the AMD 53c974 as well (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amd</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>MELCO IFC-DP</p> + </li> + </ul> + <br /> + <br /> + + <p>Workbit Ninja SCSI-3 based PC-Card SCSI host adapters + (nsp driver)</p> + + <ul> + <li> + <p>Alpha-Data AD-PCS201</p> + </li> + + <li> + <p>IO DATA CBSC16</p> + </li> + </ul> + <br /> + <br /> + + <p>LSI Logic Fusion/MP architecture Fiber Channel + controllers (mpt driver)</p> + + <ul> + <li> + <p>LSI FC909, FC929</p> + </li> + + <li> + <p>LSI 53c1020, 53c1030</p> + </li> + </ul> + <br /> + <br /> + + <p>With all supported SCSI controllers, full support is + provided for SCSI-I, SCSI-II, and SCSI-III peripherals, + including hard disks, optical disks, tape drives + (including DAT, 8mm Exabyte, Mammoth, and DLT), medium + changers, processor target devices and CD-ROM drives. + WORM devices that support CD-ROM commands are supported + for read-only access by the CD-ROM drivers (such as <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>). + WORM/CD-R/CD-RW writing support is provided by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&sektion=1&manpath=FreeBSD+Ports"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cdrecord</span>(1)</span></a>, + which is a part of the <a + href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/cdrtools/pkg-descr"> + <tt class="FILENAME">sysutils/cdrtools</tt></a> port in + the Ports Collection.</p> + + <p>The following CD-ROM type systems are supported at + this time:</p> + + <ul> + <li> + <p>SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>)</p> + </li> + + <li> + <p>ATAPI IDE interface (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=acd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">acd</span>(4)</span></a>)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 + Ethernet Interfaces</a></h2> + + <p>Adaptec Duralink PCI Fast Ethernet adapters based on + the Adaptec AIC-6915 Fast Ethernet controller chip (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sf&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sf</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>ANA-62011 64-bit single port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62022 64-bit dual port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62044 64-bit quad port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-69011 32-bit single port 10/100baseTX + adapter</p> + </li> + + <li> + <p>ANA-62020 64-bit single port 100baseFX adapter</p> + </li> + </ul> + <br /> + <br /> + + <p>Allied-Telesis AT1700 and RE2000 cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fe</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>CONTEC C-NET(PC)C PCMCIA Ethernet</p> + </li> + + <li> + <p>Fujitsu MBH10303, MBH10302 Ethernet PCMCIA</p> + </li> + + <li> + <p>Fujitsu Towa LA501 Ethernet</p> + </li> + + <li> + <p>Fujitsu FMV-J182, FMV-J182A</p> + </li> + + <li> + <p>RATOC REX-5588, REX-9822, REX-4886, and + REX-R280</p> + </li> + + <li> + <p>Eiger Labs EPX-10BT</p> + </li> + + <li> + <p>HITACHI HT-4840-11</p> + </li> + + <li> + <p>NextCom J Link NC5310</p> + </li> + + <li> + <p>TDK LAK-CD021, LAK-CD021A, LAK-CD021BX</p> + </li> + </ul> + <br /> + <br /> + + <p>Alteon Networks PCI Gigabit Ethernet NICs based on the + Tigon 1 and Tigon 2 chipsets (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ti&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ti</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3Com 3c985-SX (Tigon 1 and 2)</p> + </li> + + <li> + <p>Alteon AceNIC (Tigon 1 and 2)</p> + </li> + + <li> + <p>Alteon AceNIC 1000baseT (Tigon 2)</p> + </li> + + <li> + <p>Asante PCI 1000BASE-SX Gigabit Ethernet + Adapter</p> + </li> + + <li> + <p>Asante GigaNIX1000T Gigabit Ethernet Adapter</p> + </li> + + <li> + <p>DEC/Compaq EtherWORKS 1000</p> + </li> + + <li> + <p>Farallon PN9000SX</p> + </li> + + <li> + <p>NEC Gigabit Ethernet</p> + </li> + + <li> + <p>Netgear GA620 (Tigon 2)</p> + </li> + + <li> + <p>Netgear GA620T (Tigon 2, 1000baseT)</p> + </li> + + <li> + <p>Silicon Graphics Gigabit Ethernet</p> + </li> + </ul> + <br /> + <br /> + + <p>AMD PCnet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">lnc</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pcn&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pcn</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>Contec C-NET(98)S</p> + </li> + + <li> + <p>PCI NIC using AMD AM79C97x (PCnet-PCI/Fast)</p> + </li> + + <li> + <p>NEC SV-98/2-B05, B06 (PCI)</p> + </li> + + <li> + <p>Allied-Telesis LA-PCI (PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>SMC 83c17x (EPIC)-based Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tx</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>SMC EtherPower II 9432 series</p> + </li> + </ul> + <br /> + <br /> + + <p>National Semiconductor DS8390-based Ethernet NICs, + including Novell NE2000 and clones (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ed</span>(4)</span></a> driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> In kernel configuration, you need to + set flag for non-PCI device.</p> + </blockquote> + </div> + + <ul> + <li> + <p>Novell NE1000, NE2000, and NE2100</p> + </li> + + <li> + <p>RealTek 8029</p> + </li> + + <li> + <p>I-O DATA ET2/T-PCI</p> + </li> + + <li> + <p>MELCO LGY-PCI-TR</p> + </li> + + <li> + <p>PLANEX ENW-8300-T</p> + </li> + + <li> + <p>Allied Telesis LA-98 (flags 0x000000)</p> + </li> + + <li> + <p>Corega Ether98-T (flags 0x000000)</p> + </li> + + <li> + <p>SMC EtherEZ98 (flags 0x000000)</p> + </li> + + <li> + <p>ELECOM LD-BDN, LD-NW801G (flags 0x200000)</p> + </li> + + <li> + <p>PLANEX EN-2298-C (flags 0x200000)</p> + </li> + + <li> + <p>MELCO EGY-98 (flags 0x300000)</p> + </li> + + <li> + <p>Contec C-NET(98)E-A, C-NET(98)L-A, C-NET(98)P + (flags 0x300000)</p> + </li> + + <li> + <p>MELCO LGY-98, LGH-98, IND-SP, IND-SS, LGY-98-N + (110pin) (flags 0x400000)</p> + </li> + + <li> + <p>MACNICA NE2098 (flags 0x400000)</p> + </li> + + <li> + <p>ICM IF-2766ET, IF-2771ET, AD-ET2-T, DT-ET-25, + DT-ET-T5, NB-ET-T (110pin) (flags 0x500000)</p> + </li> + + <li> + <p>D-Link DE-298, DE-298P (flags 0x500000)</p> + </li> + + <li> + <p>ELECOM LD-98P (flags 0x500000)</p> + </li> + + <li> + <p>PLANEX EN-2298-T, EN-2298P-T (flags 0x500000)</p> + </li> + + <li> + <p>Allied Telesis SIC-98, SIU-98, SIC-98NOTE (110pin) + (flags 0x600000)</p> + </li> + + <li> + <p>Allied Telesis SIU-98-D (flags 0x610000)</p> + </li> + + <li> + <p>NEC PC-9801-107, 108 (flags 0x800000)</p> + </li> + + <li> + <p>I-O DATA LA/T-98, LA/T-98SB, LA2/T-98, ET/T-98 + (flags 0x900000)</p> + </li> + + <li> + <p>MACNICA ME98 (flags 0x900000)</p> + </li> + + <li> + <p>Kansai KLA-98C/T (flags 0x900000)</p> + </li> + + <li> + <p>NEC PC-9801-77, 78 (flags 0x910000)</p> + </li> + + <li> + <p>Contec C-NET(98), RT-1007(98), C-NET(9N) (110pin) + (flags 0xa00000)</p> + </li> + + <li> + <p>Contec C-NET(98)E, C-NET(98)L, C-NET(9N)L (110pin) + (flags 0xb00000)</p> + </li> + + <li> + <p>Logitec LAN-98T (flags 0xb00000)</p> + </li> + + <li> + <p>Networld 98X3 (flags 0xd00000)</p> + </li> + + <li> + <p>Accton EN1644(old model), EN1646(old model), + EN2203(old model) (110pin) (flags 0xd00000)</p> + </li> + + <li> + <p>Networld EC-98X, EP-98X (flags 0xd10000)</p> + </li> + </ul> + <br /> + <br /> + + <p>NE2000 compatible PC-Card (PCMCIA) Ethernet and + FastEthernet cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ed&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ed</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>AR-P500 Ethernet</p> + </li> + + <li> + <p>Accton EN2212/EN2216/UE2216</p> + </li> + + <li> + <p>Allied Telesis CentreCOM LA100-PCM_V2</p> + </li> + + <li> + <p>AmbiCom 10BaseT card</p> + </li> + + <li> + <p>BayNetworks NETGEAR FA410TXC Fast Ethernet</p> + </li> + + <li> + <p>CNet BC40 adapter</p> + </li> + + <li> + <p>COREGA Ether PCC-T/EtherII PCC-T/FEther + PCC-TXF/PCC-TXD</p> + </li> + + <li> + <p>Compex Net-A adapter</p> + </li> + + <li> + <p>CyQ've ELA-010</p> + </li> + + <li> + <p>D-Link DE-650/660</p> + </li> + + <li> + <p>Danpex EN-6200P2</p> + </li> + + <li> + <p>Elecom Laneed LD-CDL/TX, LD-CDF, LD-CDS, + LD-10/100CD, LD-CDWA (DP83902A), MACNICA Ethernet ME1 + for JEIDA</p> + </li> + + <li> + <p>IO DATA PCLATE</p> + </li> + + <li> + <p>IBM Creditcard Ethernet I/II</p> + </li> + + <li> + <p>IC-CARD Ethernet/IC-CARD+ Ethernet</p> + </li> + + <li> + <p>Kingston KNE-PC2, KNE-PCM/x Ethernet</p> + </li> + + <li> + <p>Linksys EC2T/PCMPC100/PCM100, PCMLM56, EtherFast + 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 + V2)</p> + </li> + + <li> + <p>MELCO + LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX</p> + </li> + + <li> + <p>NDC Ethernet Instant-Link</p> + </li> + + <li> + <p>National Semiconductor InfoMover NE4100</p> + </li> + + <li> + <p>NetGear FA-410TX</p> + </li> + + <li> + <p>Network Everywhere Ethernet 10BaseT PC Card</p> + </li> + + <li> + <p>Planex FNW-3600-T</p> + </li> + + <li> + <p>Socket LP-E</p> + </li> + + <li> + <p>Surecom EtherPerfect EP-427</p> + </li> + + <li> + <p>TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card</p> + </li> + + <li> + <p>Telecom Device SuperSocket RE450T</p> + </li> + </ul> + <br /> + <br /> + + <p>RealTek 8129/8139 Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek + 8139 clone)</p> + </li> + + <li> + <p>SOHO(PRAGMATIC) UE-1211C (PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>Macronix 98713, 98713A, 98715, 98715A and 98725 Fast + Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Accton EN1217 (98715A)</p> + </li> + + <li> + <p>Adico AE310TX (98715A)</p> + </li> + + <li> + <p>Compex RL100-TX (98713 or 98713A)</p> + </li> + + <li> + <p>CNet Pro120A (98713 or 98713A)</p> + </li> + + <li> + <p>CNet Pro120B (98715)</p> + </li> + + <li> + <p>NDC Communications SFA100A (98713A)</p> + </li> + + <li> + <p>SVEC PN102TX (98713)</p> + </li> + </ul> + <br /> + <br /> + + <p>Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>LinkSys EtherFast LNE100TX Version 2</p> + </li> + </ul> + <br /> + <br /> + + <p>Winbond W89C840F Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wb&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wb</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Trendware TE100-PCIE</p> + </li> + </ul> + <br /> + <br /> + + <p>VIA Technologies VT3043 ``Rhine I'', VT86C100A ``Rhine + II'', and VT86C105/VT86C105M ``Rhine III'' Fast Ethernet + NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vr</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>MELCO LGY-PCI-TXR (PCI)</p> + </li> + + <li> + <p>CO-100MV (PCI)</p> + </li> + + <li> + <p>Corega FastEtherII PCI-TX (PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>Silicon Integrated Systems SiS 900 and SiS 7016 PCI + Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sis</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>@Nifty FNECHARD IFC-USUP-TX (PCI)</p> + </li> + + <li> + <p>MELCO LGY-PCI-TXC (PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>National Semiconductor DP83815 Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sis&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sis</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>NetGear FA311-TX</p> + </li> + + <li> + <p>NetGear FA312-TX</p> + </li> + </ul> + <br /> + <br /> + + <p>National Semiconductor DP83820 and DP83821 Gigabit + Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nge&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nge</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Addtron AEG320T</p> + </li> + + <li> + <p>Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T + (64-bit PCI)</p> + </li> + + <li> + <p>Asante FriendlyNet GigaNIC 1000TA and 1000TPC</p> + </li> + + <li> + <p>D-Link DGE-500T</p> + </li> + + <li> + <p>LinkSys EG1032 (32-bit PCI) and EG1064 (64-bit + PCI)</p> + </li> + + <li> + <p>Netgear GA621 and GA622T</p> + </li> + + <li> + <p>SMC EZ Card 1000 (SMC9462TX)</p> + </li> + + <li> + <p>Surecom Technology EP-320G-TX</p> + </li> + + <li> + <p>Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 + (64-bit PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>Sundance Technologies ST201 PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ste&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ste</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>D-Link DFE-550TX</p> + </li> + </ul> + <br /> + <br /> + + <p>SysKonnect SK-984x PCI Gigabit Ethernet cards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sk&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sk</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>SK-9821 1000baseT copper, single port</p> + </li> + + <li> + <p>SK-9822 1000baseT copper, dual port</p> + </li> + + <li> + <p>SK-9841 1000baseLX single mode fiber, single + port</p> + </li> + + <li> + <p>SK-9842 1000baseLX single mode fiber, dual + port</p> + </li> + + <li> + <p>SK-9843 1000baseSX multimode fiber, single + port</p> + </li> + + <li> + <p>SK-9844 1000baseSX multimode fiber, dual port</p> + </li> + </ul> + <br /> + <br /> + + <p>Texas Instruments ThunderLAN PCI NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Compaq Netelligent 10, 10/100, 10/100 + Dual-Port</p> + </li> + + <li> + <p>Compaq Netelligent 10/100 TX Embedded UTP, 10 T + PCI UTP/Coax, 10/100 TX UTP</p> + </li> + + <li> + <p>Compaq NetFlex 3P, 3P Integrated, 3P w/BNC</p> + </li> + + <li> + <p>Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX + UTP</p> + </li> + + <li> + <p>Racore 8165 10/100baseTX</p> + </li> + + <li> + <p>Racore 8148 10baseT/100baseTX/100baseFX + multi-personality</p> + </li> + </ul> + <br /> + <br /> + + <p>ADMtek Inc. AL981-based PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <p>ADMtek Inc. AN985-based PCI Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>LinkSys EtherFast LNE100TX v4.0/4.1</p> + </li> + </ul> + <br /> + <br /> + + <p>ADMtek Inc. AN986-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aue</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Abocom UFE1000, DSB650TX_NA</p> + </li> + + <li> + <p>Accton USB320-EC, SpeedStream</p> + </li> + + <li> + <p>ADMtek AN986, AN8511</p> + </li> + + <li> + <p>Billionton USB100, USB100LP, USB100EL, USBE100</p> + </li> + + <li> + <p>Corega Ether FEther USB-T, FEther USB-TX, FEther + USB-TXS</p> + </li> + + <li> + <p>D-Link DSB-650, DSB-650TX, DSB-650TX-PNA</p> + </li> + + <li> + <p>Elecom LD-USBL/TX</p> + </li> + + <li> + <p>Elsa Microlink USB2Ethernet</p> + </li> + + <li> + <p>I-O Data USB ETTX</p> + </li> + + <li> + <p>Kingston KNU101TX</p> + </li> + + <li> + <p>LinkSys USB10T, USB10TA, USB10TX, USB100TX, + USB100H1</p> + </li> + + <li> + <p>MELCO LUA-TX, LUA2-TX</p> + </li> + + <li> + <p>Planex UE-200TX</p> + </li> + + <li> + <p>Siemens Speedstream</p> + </li> + + <li> + <p>SmartBridges smartNIC</p> + </li> + + <li> + <p>SMC 2202USB</p> + </li> + + <li> + <p>SOHOware NUB100</p> + </li> + </ul> + <br /> + <br /> + + <p>CATC USB-EL1210A-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cue</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Belkin F5U011, F5U111</p> + </li> + + <li> + <p>CATC Netmate, Netmate II</p> + </li> + + <li> + <p>SmartBridges SmartLink</p> + </li> + </ul> + <br /> + <br /> + + <p>Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kue</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3c19250</p> + </li> + + <li> + <p>AOX USB101</p> + </li> + + <li> + <p>Abocom URE 450</p> + </li> + + <li> + <p>ADS Technologies USB-10BT</p> + </li> + + <li> + <p>ATen UC10T</p> + </li> + + <li> + <p>Corega USB-T</p> + </li> + + <li> + <p>D-Link DSB-650C</p> + </li> + + <li> + <p>Entrega NET-USB-E45</p> + </li> + + <li> + <p>I/O Data USB ETT</p> + </li> + + <li> + <p>Kawasaki DU-H3E</p> + </li> + + <li> + <p>LinkSys USB10T</p> + </li> + + <li> + <p>Netgear EA101</p> + </li> + + <li> + <p>Peracom USB Ethernet Adapter</p> + </li> + + <li> + <p>SMC 2102USB, 2104USB</p> + </li> + </ul> + <br /> + <br /> + + <p>ASIX Electronics AX88172-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">axe</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>D-Link DUBE100</p> + </li> + + <li> + <p>Linksys USB200M</p> + </li> + + <li> + <p>Netgear FA120</p> + </li> + </ul> + <br /> + <br /> + + <p>RealTek RTL8150-based USB Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rue</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>GREEN HOUSE GH-USB100B</p> + </li> + + <li> + <p>MELCO LUA-KTX</p> + </li> + </ul> + <br /> + <br /> + + <p>ASIX Electronics AX88140A PCI NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Alfa Inc. GFC2204</p> + </li> + + <li> + <p>CNet Pro110B</p> + </li> + </ul> + <br /> + <br /> + + <p>DEC DC21040, DC21041, DC21140, DC21141, DC21142, and + DC21143 based NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=de&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">de</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Asante</p> + </li> + + <li> + <p>Cogent EM100FX and EM440TX</p> + </li> + + <li> + <p>DEC DE425, DE435, DE450, and DE500</p> + </li> + + <li> + <p>SMC Etherpower 8432T, 9332, and 9334</p> + </li> + + <li> + <p>ZYNX ZX 3xx</p> + </li> + + <li> + <p>I-O DATA LA2/T-PCI (PCI)</p> + </li> + + <li> + <p>ELECOM LD-PCI2T, LD-PCITS (PCI)</p> + </li> + + <li> + <p>Corega FastEther PCI-TX (PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>DEC/Intel 21143 based Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>DEC DE500</p> + </li> + + <li> + <p>Compaq Presario 7900 series built-in Ethernet</p> + </li> + + <li> + <p>D-Link DFE-570TX</p> + </li> + + <li> + <p>Kingston KNE100TX</p> + </li> + + <li> + <p>LinkSys EtherFast 10/100 Instant GigaDrive + built-in Ethernet</p> + </li> + </ul> + <br /> + <br /> + + <p>Davicom DM9009, DM9100 and DM9102 PCI Fast Ethernet + NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Jaton Corporation XpressNet</p> + </li> + </ul> + <br /> + <br /> + + <p>Cnet Pro120A (PCI) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <p>MELCO LGY-PCI-TXL (PCI) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dc</span>(4)</span></a> driver)</p> + + <p>Fujitsu MB86960A/MB86965A based Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fe</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Allied Telesis RE1000, RE1000Plus, ME1500 + (110pin)</p> + </li> + + <li> + <p>Contec C-NET(98)P2, C-NET(9N)E (110pin), + C-NET(9N)C(ExtCard)</p> + </li> + + <li> + <p>Ungermann-Bass Access/PC N98C+(PC85152,PC85142), + Access/NOTE N98 (PC86132) (110pin)</p> + </li> + + <li> + <p>TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 + (110pin)</p> + </li> + + <li> + <p>Ratoc REX-9880/9881/9882/9883</p> + </li> + </ul> + <br /> + <br /> + + <p>Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Intel EtherExpress Pro/100B PCI Fast Ethernet</p> + </li> + + <li> + <p>Intel PRO/100+ Management Adapter</p> + </li> + + <li> + <p>Intel Pro/100 VE Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 M Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters</p> + </li> + + <li> + <p>NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal + 100Base-TX (PCI)</p> + </li> + + <li> + <p>NEC PC-9821X-B06 (PCI)</p> + </li> + + <li> + <p>Contec C-NET(PI)-100TX (PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>3Com 3C5x9 Etherlink III NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ep&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ep</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3Com 3C569, 3C569-TPO, 3C569B, 3C569B-COMBO</p> + </li> + </ul> + <br /> + <br /> + + <p>3Com Etherlink XL-based NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3C900/905/905B/905C PCI</p> + </li> + </ul> + <br /> + <br /> + + <p>3Com 3C59X series NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vx</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3C590 Etherlink III (PCI)</p> + </li> + + <li> + <p>3C595 Fast Etherlink III (PCI)</p> + </li> + </ul> + <br /> + <br /> + + <p>National Semiconductor DP8393X (SONIC) Ethernet cards + (snc driver)</p> + + <ul> + <li> + <p>NEC PC-9801-83, -84, -103, and -104</p> + </li> + + <li> + <p>NEC PC-9801N-25 and -J02R</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet cards based on the Level 1 LXT1001 + NetCellerator controller (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=lge&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">lge</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>D-Link DGE-500SX</p> + </li> + + <li> + <p>SMC TigerCard 1000 (SMC9462SX)</p> + </li> + </ul> + <br /> + <br /> + + <p>Ethernet and Fast Ethernet NICs based on the 3Com 3XP + Typhoon/Sidewinder (3CR990) chipset (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=txp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">txp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3CR990-TX-95</p> + </li> + + <li> + <p>3Com 3CR990-TX-97</p> + </li> + + <li> + <p>3Com 3CR990B-SRV</p> + </li> + + <li> + <p>3Com 3CR990B-TXM</p> + </li> + + <li> + <p>3Com 3CR990SVR95</p> + </li> + + <li> + <p>3Com 3CR990SVR97</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet NICs based on the Broadcom BCM570x + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bge&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bge</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3c996-SX, 3c996-T</p> + </li> + + <li> + <p>Netgear GA302T</p> + </li> + + <li> + <p>SysKonnect SK-9D21 and 9D41</p> + </li> + </ul> + <br /> + <br /> + + <p>Gigabit Ethernet NICs based on the Intel 82542 and + 82543 controller chips (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gx&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gx</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> drivers), + plus NICs supported by the Intel 82540EM, 82544, 82545EM, + and 82546EB controller chips (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> driver + only)</p> + + <ul> + <li> + <p>Intel PRO/1000 Gigabit Ethernet</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=em&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">em</span>(4)</span></a> driver + is officially supported by Intel, but is only + supported on the i386.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Myson Ethernet NICs (my driver)</p> + + <ul> + <li> + <p>Myson MTD80X Based Fast Ethernet Card</p> + </li> + + <li> + <p>Myson MTD89X Based Gigabit Ethernet Card</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1598" name="AEN1598">3.3 FDDI + Interfaces</a></h2> + + <p>DEC DEFPA PCI (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fpa&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fpa</span>(4)</span></a> + driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1608" name="AEN1608">3.4 ATM + Interfaces</a></h2> + + <p>Efficient Networks, Inc. ENI-155p ATM PCI Adapters + (hea driver)</p> + + <p>FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa + driver)</p> + + <p>IDT 77201/211 NICStAR ATM Adapters (idt driver)</p> + + <p>FORE Systems, Inc. LE155 ATM Adapter (idt driver)</p> + + <p>The ATM support in FreeBSD supports the following + signaling protocols:</p> + + <ul> + <li> + <p>The ATM Forum UNI 3.1 signaling protocol</p> + </li> + + <li> + <p>The ATM Forum UNI 3.0 signaling protocol</p> + </li> + + <li> + <p>The ATM Forum ILMI address registration</p> + </li> + + <li> + <p>FORE Systems' proprietary SPANS signaling + protocol</p> + </li> + + <li> + <p>Permanent Virtual Channels (PVCs)</p> + </li> + </ul> + <br /> + <br /> + + <p>Support for the IETF ``Classical IP and ARP over ATM'' + model is provided, compliant with the following RFCs and + Internet Drafts:</p> + + <ul> + <li> + <p>RFC 1483, ``Multiprotocol Encapsulation over ATM + Adaptation Layer 5''</p> + </li> + + <li> + <p>RFC 1577, ``Classical IP and ARP over ATM''</p> + </li> + + <li> + <p>RFC 1626, ``Default IP MTU for use over ATM + AAL5''</p> + </li> + + <li> + <p>RFC 1755, ``ATM Signaling Support for IP over + ATM''</p> + </li> + + <li> + <p>RFC 2225, ``Classical IP and ARP over ATM''</p> + </li> + + <li> + <p>RFC 2334, ``Server Cache Synchronization Protocol + (SCSP)''</p> + </li> + + <li> + <p>Internet Draft <tt + class="FILENAME">draft-ietf-ion-scsp-atmarp-00.txt</tt>, + ``A Distributed ATMARP Service Using SCSP''</p> + </li> + </ul> + <br /> + <br /> + + <p>Support for an ATM sockets interface is also + provided.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1652" name="AEN1652">3.5 + Wireless Network Interfaces</a></h2> + + <p>Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA + standard speed (2Mbps) and turbo speed (6Mbps) wireless + network adapters and workalikes (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wi</span>(4)</span></a> driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The ISA versions of these adapters + are actually PCMCIA cards combined with an ISA to + PCMCIA bridge card, so both kinds of devices work + with the same driver.</p> + </blockquote> + </div> + + <ul> + <li> + <p>3COM 3crwe737A AirConnect Wireless LAN PC Card</p> + </li> + + <li> + <p>Accton airDirect WN3301</p> + </li> + + <li> + <p>Addtron AWA100</p> + </li> + + <li> + <p>Adtec ADLINK340APC</p> + </li> + + <li> + <p>Airway 802.11 Adapter</p> + </li> + + <li> + <p>Avaya Wireless PC Card</p> + </li> + + <li> + <p>Blue Concentric Circle CF Wireless LAN Model + WL-379F</p> + </li> + + <li> + <p>BreezeNET PC-DS.11</p> + </li> + + <li> + <p>Buffalo WLI-CF-S11G</p> + </li> + + <li> + <p>Cabletron RoamAbout 802.11 DS</p> + </li> + + <li> + <p>Compaq WL100, WL110</p> + </li> + + <li> + <p>Corega KK Wireless LAN PCC-11, PCCA-11, + PCCB-11</p> + </li> + + <li> + <p>D-Link DWL-650</p> + </li> + + <li> + <p>Dell TrueMobile 1150 Series</p> + </li> + + <li> + <p>ELECOM Air@Hawk/LD-WL11/PCC</p> + </li> + + <li> + <p>ELSA AirLancer MC-11</p> + </li> + + <li> + <p>Farallon Skyline 11Mbps Wireless</p> + </li> + + <li> + <p>ICOM SL-1100</p> + </li> + + <li> + <p>IBM High Rate Wireless LAN PC Card</p> + </li> + + <li> + <p>Intel PRO/Wireless 2011 LAN PC Card</p> + </li> + + <li> + <p>IO Data WN-B11/PCM</p> + </li> + + <li> + <p>Laneed Wireless card</p> + </li> + + <li> + <p>Linksys Instant Wireless WPC11</p> + </li> + + <li> + <p>Lucent WaveLAN/IEEE 802.11</p> + </li> + + <li> + <p>MELCO Airconnect WLI-PCM-S11, WLI-PCM-L11</p> + </li> + + <li> + <p>NCR WaveLAN/IEEE 802.11</p> + </li> + + <li> + <p>NEC Wireless Card CMZ-RT-WP</p> + </li> + + <li> + <p>NEC Aterm WL11C (PC-WL/11C)</p> + </li> + + <li> + <p>NEC PK-WL001</p> + </li> + + <li> + <p>Netgear MA401</p> + </li> + + <li> + <p>PLANEX GeoWave/GW-NS110</p> + </li> + + <li> + <p>Proxim Harmony, RangeLAN-DS</p> + </li> + + <li> + <p>SMC 2632W, 2602W</p> + </li> + + <li> + <p>Sony PCWA-C100</p> + </li> + + <li> + <p>TDK LAK-CD011WL</p> + </li> + + <li> + <p>Toshiba Wireless LAN Card</p> + </li> + + <li> + <p>US Robotics Wireless Card 2410</p> + </li> + </ul> + <br /> + <br /> + + <p>Aironet 802.11 wireless adapters (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">an</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Aironet 4500/4800 series (PCMCIA, PCI, and ISA + adapters are all supported)</p> + </li> + + <li> + <p>Cisco Systems Aironet 340 and 350 series (PCMCIA, + PCI, Mini-PCI, and ISA adapters are all + supported)</p> + </li> + + <li> + <p>Xircom Wireless Ethernet adapter (rebadged + Aironet)</p> + </li> + </ul> + <br /> + <br /> + + <p>Raytheon Raylink 2.4GHz wireless adapters (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ray&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ray</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Webgear Aviator</p> + </li> + + <li> + <p>Webgear Aviator Pro</p> + </li> + + <li> + <p>Raytheon Raylink PC Card</p> + </li> + </ul> + <br /> + <br /> + + <p>AMD Am79C930 and Harris (Intersil) based 802.11 cards + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=awi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">awi</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>BayStack 650 and 660</p> + </li> + + <li> + <p>Farallon SkyLINE Wireless</p> + </li> + + <li> + <p>Icom SL-200</p> + </li> + + <li> + <p>MELCO WLI-PCM</p> + </li> + + <li> + <p>NEL SSMagic</p> + </li> + + <li> + <p>Netwave AirSurfer Plus and AirSurfer Pro</p> + </li> + + <li> + <p>ZoomAir 4000</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1780" name="AEN1780">3.6 + Miscellaneous Networks</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1811" name="AEN1811">3.7 ISDN + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1875" name="AEN1875">3.8 + Serial Interfaces</a></h2> + + <p>Internel serial interfaces (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>PC-9801 on-board</p> + </li> + + <li> + <p>PC-9821 2'nd CCU (flags 0x12000000)</p> + </li> + </ul> + <br /> + <br /> + + <p>NEC PC-9861K, PC-9801-101 and Midori-Denshi MDC-926Rs + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>COM2 (flags 0x01000000)</p> + </li> + + <li> + <p>COM3 (flags 0x02000000)</p> + </li> + </ul> + <br /> + <br /> + + <p>NEC PC-9801-120 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x11000000" is necessary in + kernel configuration.</p> + </blockquote> + </div> + + <p>Microcore MC-16550, MC-16550II, MC-RS98 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x14000?01" is necessary in + kernel configuration.</p> + </blockquote> + </div> + + <p>Media Intelligent RSB-2000, RSB-3000 and AIWA B98-02 + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x15000?01" is necessary in + kernel configuration.</p> + </blockquote> + </div> + + <p>Media Intelligent RSB-384 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x16000001" is necessary in + kernel configuration.</p> + </blockquote> + </div> + + <p>I-O DATA RSA-98III (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "flags 0x18000?01" is necessary in + kernel configuration.</p> + </blockquote> + </div> + + <p>Hayes ESP98 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sio</span>(4)</span></a> + driver)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> "options COM_ESP" and "flags + 0x19000000" are necessary in kernel + configuration.</p> + </blockquote> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2070" name="AEN2070">3.9 + Audio Devices</a></h2> + + <p>NEC PC-9801-73, 86 and compatibles (nss driver)</p> + + <ul> + <li> + <p>NEC A-MATE internal sound</p> + </li> + + <li> + <p>Q-Vision WaveStar, WaveMaster</p> + </li> + </ul> + <br /> + <br /> + + <p>NEC X-MATE, CanBe, ValueStar internal (mss driver)</p> + + <p>Creative Technologies SoundBlaster(98) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sb&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sb</span>(4)</span></a> driver)</p> + + <p>I-O DATA CD-BOX (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sb&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sb</span>(4)</span></a> driver)</p> + + <p>Software PCM using beep (pca driver)</p> + + <p>MPU-401 and compatible interfaces (mpu driver)</p> + + <ul> + <li> + <p>Q-Vision WaveStar</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2193" name="AEN2193">3.10 + Camera and Video Capture Devices</a></h2> + + <p>Brooktree Bt848/849/878/879-based frame grabbers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bktr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bktr</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>AverMedia cards</p> + </li> + + <li> + <p>Hauppauge Wincast TV and WinTV boards (PCI)</p> + </li> + + <li> + <p>Intel Smart Video Recorder III</p> + </li> + + <li> + <p>Miro PC TV</p> + </li> + + <li> + <p>STB TV PCI</p> + </li> + + <li> + <p>Video Highway XTreme</p> + </li> + + <li> + <p>VideoLogic Captivator PCI</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USB" name="USB">3.11 USB + Devices</a></h2> + + <p>A range of USB peripherals are supported; devices + known to work are listed in this section. Owing to the + generic nature of most USB devices, with some exceptions + any device of a given class will be supported, even if + not explicitly listed here.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> USB Ethernet adapters can be found in + the section listing <a href="#ETHERNET">Ethernet + interfaces</a>.</p> + </blockquote> + </div> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> USB Bluetooth adapters can be found + in <a href="#BLUETOOTH">Bluetooth</a> section.</p> + </blockquote> + </div> + + <p>Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ohci</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uhci</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>NEC PC-9821V200 etc (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ohci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ohci</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>USB host controllers (PCI)</p> + + <ul> + <li> + <p>TRY CORPORATION JUS-02 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uhci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uhci</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>USB 2.0 controllers using the EHCI interface (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ehci</span>(4)</span></a> + driver)</p> + + <p>Hubs</p> + + <ul> + <li> + <p>Andromeda hub</p> + </li> + + <li> + <p>MacAlly self powered hub (4 ports)</p> + </li> + + <li> + <p>NEC hub</p> + </li> + </ul> + <br /> + <br /> + + <p>Keyboards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ukbd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ukbd</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Apple iMac keyboard</p> + </li> + + <li> + <p>BTC BTC7935 keyboard with PS/2 mouse port</p> + </li> + + <li> + <p>Cherry G81-3504 keyboard</p> + </li> + + <li> + <p>Logitech M2452 keyboard</p> + </li> + + <li> + <p>MacAlly iKey keyboard</p> + </li> + + <li> + <p>Microsoft keyboard</p> + </li> + + <li> + <p>Sun Microsystems Type 6 USB keyboard</p> + </li> + </ul> + <br /> + <br /> + + <p>Miscellaneous</p> + + <ul> + <li> + <p>ActiveWire I/O Board</p> + </li> + + <li> + <p>Diamond Rio 500, 600, and 800 MP3 players (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=urio&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">urio</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>D-Link DSB-R100 USB Radio (ufm driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Modems (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umodem&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umodem</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 5605</p> + </li> + + <li> + <p>Metricom Ricochet GS USB wireless modem</p> + </li> + + <li> + <p>Yamaha Broadband Wireless Router RTW65b</p> + </li> + </ul> + <br /> + <br /> + + <p>Mice (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ums&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ums</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Agiler Mouse 29UO</p> + </li> + + <li> + <p>Apple iMac Mouse</p> + </li> + + <li> + <p>Belkin Mouse</p> + </li> + + <li> + <p>Chic mouse</p> + </li> + + <li> + <p>Cypress mouse</p> + </li> + + <li> + <p>Genius Niche mouse</p> + </li> + + <li> + <p>Kensington Mouse-in-a-Box</p> + </li> + + <li> + <p>Logitech wheel mouse (3 buttons)</p> + </li> + + <li> + <p>Logitech PS/2 / USB mouse (3 buttons)</p> + </li> + + <li> + <p>MacAlly mouse (3 buttons)</p> + </li> + + <li> + <p>Microsoft IntelliMouse (3 buttons)</p> + </li> + + <li> + <p>Sun Microsystems Type 6 USB Mouse</p> + </li> + + <li> + <p>Trust Ami Mouse (3 buttons)</p> + </li> + </ul> + <br /> + <br /> + + <p>Printers and parallel printer conversion cables (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ulpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ulpt</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>ATen parallel printer adapter</p> + </li> + + <li> + <p>Belkin F5U002 parallel printer adapter</p> + </li> + + <li> + <p>Entrega USB-to-parallel printer adapter</p> + </li> + </ul> + <br /> + <br /> + + <p>Serial devices</p> + + <ul> + <li> + <p>Belkin F5U103 and F5U120 (ubsa driver)</p> + </li> + + <li> + <p>e-Tek Labs Kwik232 (ubsa driver)</p> + </li> + + <li> + <p>GoHubs GoCOM232 (ubsa driver)</p> + </li> + + <li> + <p>HP USB-Serial adapter (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uftdi</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Inland UAS111 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uftdi</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Peracom single port serial adapter (ubsa + driver)</p> + </li> + + <li> + <p>Prolific PL-2303 serial adapter (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uplcom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uplcom</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>QVS USC-1000 (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uftdi</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>SUNTAC Slipper U VS-10U (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uvscom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uvscom</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Scanners (through <b class="APPLICATION">SANE</b>) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uscanner&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uscanner</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Perfection 636U</p> + </li> + + <li> + <p>HP ScanJet 4100C, 5200C, 6300C</p> + </li> + </ul> + <br /> + <br /> + + <p>Storage (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umass&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umass</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M</p> + </li> + + <li> + <p>Denno FireWire/USB2 Removable 2.5-inch HDD Case + MIFU-25CB20</p> + </li> + + <li> + <p>FujiFilm Zip USB Drive ZDR100 USB A</p> + </li> + + <li> + <p>GREEN HOUSE USB Flash Memory ``PicoDrive'' + GH-UFD32M, 64M, 128M</p> + </li> + + <li> + <p>IBM 32MB USB Memory Key (P/N 22P5296)</p> + </li> + + <li> + <p>IBM ThinkPad USB Portable CD-ROM Drive (P/N + 33L5151)</p> + </li> + + <li> + <p>I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM + only)</p> + </li> + + <li> + <p>I-O DATA USB + CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive + DVR-iUH2 (CDROM, DVD-RAM only)</p> + </li> + + <li> + <p>Iomega USB Zip 100Mb (primitive support still)</p> + </li> + + <li> + <p>Iomega Zip750 USB2.0 Drive</p> + </li> + + <li> + <p>Keian USB1.1/2.0 3.5-inch HDD Case KU350A</p> + </li> + + <li> + <p>Kurouto Shikou USB 2.5-inch HDD Case + GAWAP2.5PS-USB2.0</p> + </li> + + <li> + <p>Logitec USB1.1/2.0 HDD Unit SHD-E60U2</p> + </li> + + <li> + <p>Logitec Mobile USB Memory LMC-256UD</p> + </li> + + <li> + <p>Logitec USB Double-Speed Floppy Drive LFD-31U2</p> + </li> + + <li> + <p>Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 + (CDROM only)</p> + </li> + + <li> + <p>Matshita CF-VFDU03 floppy drive</p> + </li> + + <li> + <p>MELCO USB2.0 MO Drive MO-CH640U2</p> + </li> + + <li> + <p>I-O DATA USB/IEEE1394 Portable HD Drive + HDP-i30P/CI, HDP-i40P/CI</p> + </li> + + <li> + <p>MELCO USB Flash Disk ``PetitDrive'', RUF-32M, + -64M, -128M, -256M</p> + </li> + + <li> + <p>MELCO USB2.0 Flash Disk ``PetitDrive2'', + RUF-256M/U2, -512M/U2</p> + </li> + + <li> + <p>MELCO USB Flash Disk ``ClipDrive'', RUF-C32M, + -C64M, -C128M, -C256M, -C512M</p> + </li> + + <li> + <p>Microtech USB-SCSI-HD 50 USB to SCSI cable</p> + </li> + + <li> + <p>NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U</p> + </li> + + <li> + <p>Panasonic floppy drive</p> + </li> + + <li> + <p>Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN + (CDROM only)</p> + </li> + + <li> + <p>RATOC Systems USB2.0 Removable HDD Case U2-MDK1, + U2-MDK1B</p> + </li> + + <li> + <p>Sony Portable CD-R/RW Drive CRX10U (CDROM + only)</p> + </li> + + <li> + <p>TEAC Portable USB CD-ROM Unit CD-110PU/210PU</p> + </li> + + <li> + <p>Y-E Data floppy drive (720/1.44/2.88Mb)</p> + </li> + </ul> + <br /> + <br /> + + <p>Audio Devices (uaudio driver)</p> + + <ul> + <li> + <p>Audio-Technica USB Digital Headphone + ATC-HA4USB</p> + </li> + + <li> + <p>Ergo Systems AUDIOTRAK OPTOPlay USB</p> + </li> + + <li> + <p>KENWOOD MD Personal Stereo System MDX-G7</p> + </li> + + <li> + <p>KENWOOD/SOTEC VH-7PC</p> + </li> + + <li> + <p>I-O DATA Analog to Digital USB Audio Adapter + DAVOX</p> + </li> + + <li> + <p>ONKYO PC Speaker GX-R5U(W)</p> + </li> + + <li> + <p>ONKYO USB Digital Audio Processor SE-U55X(S)</p> + </li> + + <li> + <p>Roland UA-5 USB Audio Interface ``Audio + Capture''</p> + </li> + + <li> + <p>Sony PC Active Speaker System SRS-T100PC</p> + </li> + </ul> + <br /> + <br /> + + <p>Handspring Visor and other PalmOS devices (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uvisor&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uvisor</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Handspring Visor</p> + </li> + + <li> + <p>Palm M125, M500, M505</p> + </li> + + <li> + <p>Sony Clie 4.0 and 4.1</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 + IEEE 1394 (Firewire) Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.13 + Bluetooth Devices</a></h2> + + <p>PCCARD Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_bt3c&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ng_bt3c</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com/HP 3CRWB6096-A PCCARD adapter</p> + </li> + </ul> + <br /> + <br /> + + <p>USB Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ng_ubt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ng_ubt</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>3Com 3CREB96</p> + </li> + + <li> + <p>EPoX BT-DG02</p> + </li> + + <li> + <p>Mitsumi USB Bluetooth adapter</p> + </li> + + <li> + <p>MSI MS-6967</p> + </li> + + <li> + <p>TDK Bluetooth USB adapter</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2573" name="AEN2573">3.14 + Cryptographic Accelerators</a></h2> + + <p>Accelerators based on the Hifn 7751, 7811, or 7951 + chipsets (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=hifn&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">hifn</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Invertex AEON</p> + </li> + + <li> + <p>Hifn 7751 reference board</p> + </li> + + <li> + <p>Global Technologies Group PowerCrypt and + XL-Crypt</p> + </li> + + <li> + <p>NetSec 7751</p> + </li> + + <li> + <p>Soekris Engineering vpn1201 and vpn1211</p> + </li> + </ul> + <br /> + <br /> + + <p>Accelerators based on the Bluesteel 5501 or 5601 + chipsets (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ubsec</span>(4)</span></a> + driver)</p> + + <p>Accelerators based on the Broadcom BCM5801, BCM5802, + BCM5805, BCM5820, BCM 5821, BCM5822 chipsets (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ubsec&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ubsec</span>(4)</span></a> + driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2598" name="AEN2598">3.15 + Miscellaneous</a></h2> + + <p>FAX-Modem/PCCARD</p> + + <ul> + <li> + <p>MELCO IGM-PCM56K/IGM-PCM56KH</p> + </li> + + <li> + <p>Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD + terminal)</p> + </li> + </ul> + <br /> + <br /> + + <p>Floppy drives (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fdc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fdc</span>(4)</span></a> + driver)</p> + + <p>Keyboards including:</p> + + <ul> + <li> + <p>Standard keyboards</p> + </li> + + <li> + <p>USB keyboards (specific instances are listed in + the section describing <a href="#USB">USB + devices</a>)</p> + </li> + </ul> + <br /> + <br /> + + <p>Pointing devices including:</p> + + <ul> + <li> + <p>Bus mice and compatible devices (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mse&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mse</span>(4)</span></a> + driver)</p> + </li> + + <li> + <p>Serial mice and compatible devices</p> + </li> + + <li> + <p>USB mice (specific instances are listed in the + section describing <a href="#USB">USB + devices</a>)</p> + </li> + </ul> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=moused&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">moused</span>(8)</span></a> has + more information on using pointing devices with + FreeBSD. Information on using pointing devices with + <b class="APPLICATION">XFree86</b> can be found at <a + href="http://www.xfree86.org/" + target="_top">http://www.xfree86.org/</a>.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>``PC-9821 standard'' parallel ports (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ppc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ppc</span>(4)</span></a> + driver)</p> + + <p>Joystick port of SoundBlaster(98) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=joy&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">joy</span>(4)</span></a> + driver)</p> + + <p>PHS Data Communication Card/PCCARD</p> + + <ul> + <li> + <p>NTT DoCoMo P-in Comp@ct</p> + </li> + + <li> + <p>Panasonic KX-PH405</p> + </li> + + <li> + <p>SII MC-P200</p> + </li> + </ul> + <br /> + <br /> + + <p>Power Management Controller of NEC PC-98 Note (pmc + driver)</p> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-sparc64.html b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-sparc64.html new file mode 100644 index 0000000000..cec0d3dd07 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware-sparc64.html @@ -0,0 +1,916 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/sparc64 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/sparc64 + 5.1-RELEASE Hardware Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Documentation + Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#SUPPORT-SYS">Supported Systems</a></dt> + + <dd> + <dl> + <dt>2.1 <a href="#AEN25">Fully Supported + Systems</a></dt> + + <dt>2.2 <a href="#AEN75">Partially Supported + Systems</a></dt> + + <dt>2.3 <a href="#AEN87">Unsupported Systems</a></dt> + </dl> + </dd> + + <dt>3 <a href="#SUPPORT">Supported Devices</a></dt> + + <dd> + <dl> + <dt>3.1 <a href="#AEN101">Disk Controllers</a></dt> + + <dt>3.2 <a href="#ETHERNET">Ethernet + Interfaces</a></dt> + + <dt>3.3 <a href="#AEN1667">FDDI Interfaces</a></dt> + + <dt>3.4 <a href="#AEN1677">ATM Interfaces</a></dt> + + <dt>3.5 <a href="#AEN1721">Wireless Network + Interfaces</a></dt> + + <dt>3.6 <a href="#AEN1849">Miscellaneous + Networks</a></dt> + + <dt>3.7 <a href="#AEN1880">ISDN Interfaces</a></dt> + + <dt>3.8 <a href="#AEN1944">Serial Interfaces</a></dt> + + <dt>3.9 <a href="#AEN2139">Audio Devices</a></dt> + + <dt>3.10 <a href="#AEN2262">Camera and Video Capture + Devices</a></dt> + + <dt>3.11 <a href="#USB">USB Devices</a></dt> + + <dt>3.12 <a href="#FIREWIRE">IEEE 1394 (Firewire) + Devices</a></dt> + + <dt>3.13 <a href="#BLUETOOTH">Bluetooth + Devices</a></dt> + + <dt>3.14 <a href="#AEN2642">Cryptographic + Accelerators</a></dt> + + <dt>3.15 <a href="#AEN2667">Miscellaneous</a></dt> + </dl> + </dd> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the hardware compatibility notes + for FreeBSD 5.1-RELEASE on the UltraSPARC hardware platform + (also referred to as FreeBSD/sparc64 5.1-RELEASE). It lists + devices known to work on this platform, as well as some + notes on boot-time kernel customization that may be useful + when attempting to configure support for new devices.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> This document includes information + specific to the UltraSPARC hardware platform. Versions + of the hardware compatibility notes for other + architectures will differ in some details.</p> + </blockquote> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="SUPPORT-SYS" name="SUPPORT-SYS">2 + Supported Systems</a></h1> + + <p>This section describes the systems currently known to be + supported by FreeBSD on the UltraSPARC platform. For + background information on the various hardware designs see + the <a href="http://sunsolve.sun.com/handbook_pub/" + target="_top">Sun System Handbook</a>.</p> + + <p>SMP is supported on all systems with more than 1 + processor.</p> + + <p>If you have a system that is not listed here, it may not + have been tested with FreeBSD 5.1-RELEASE. We encourage you + to try it and send a note to the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-sparc64" + target="_top">FreeBSD SPARC porting mailing list</a> with + your results, including which devices work and which do + not.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN25" name="AEN25">2.1 Fully + Supported Systems</a></h2> + + <p>The following systems are fully supported by + FreeBSD.</p> + + <ul> + <li> + <p>Blade 100</p> + </li> + + <li> + <p>Blade 150</p> + </li> + + <li> + <p>Enterprise 220R</p> + </li> + + <li> + <p>Enterprise 250</p> + </li> + + <li> + <p>Enterprise 420R</p> + </li> + + <li> + <p>Enterprise 450</p> + </li> + + <li> + <p>Fire V100</p> + </li> + + <li> + <p>Fire V120</p> + </li> + + <li> + <p>Netra t1 105</p> + </li> + + <li> + <p>Netra T1 AC200/DC200</p> + </li> + + <li> + <p>Netra t 1100</p> + </li> + + <li> + <p>Netra t 1120</p> + </li> + + <li> + <p>Netra t 1125</p> + </li> + + <li> + <p>Netra t 1400/1405</p> + </li> + + <li> + <p>Netra 120</p> + </li> + + <li> + <p>Netra X1</p> + </li> + + <li> + <p>SPARCEngine Ultra AXi</p> + </li> + + <li> + <p>SPARCEngine Ultra AXmp</p> + </li> + + <li> + <p>Ultra 5</p> + </li> + + <li> + <p>Ultra 10</p> + </li> + + <li> + <p>Ultra 30</p> + </li> + + <li> + <p>Ultra 60</p> + </li> + + <li> + <p>Ultra 80</p> + </li> + </ul> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN75" name="AEN75">2.2 + Partially Supported Systems</a></h2> + + <p>The following systems are partially supported by + FreeBSD. In particular the onboard scsi controller in + sbus systems is not supported.</p> + + <ul> + <li> + <p>Enterprise 3500</p> + </li> + + <li> + <p>Enterprise 4500</p> + </li> + + <li> + <p>Ultra 1 Enterprise (1E for short)</p> + </li> + + <li> + <p>Ultra 2</p> + </li> + </ul> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN87" name="AEN87">2.3 + Unsupported Systems</a></h2> + + <p>The following systems are not supported by FreeBSD. + This may be due to lack of processor support (UltraSPARC + III), due to a quirk in the system design that makes + FreeBSD unstable, or due to lack of support for + sufficient onboard devices to make FreeBSD generally + useful.</p> + + <ul> + <li> + <p>All systems containing UltraSPARC III + processor(s).</p> + </li> + + <li> + <p>Ultra 1</p> + </li> + </ul> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="SUPPORT" name="SUPPORT">3 + Supported Devices</a></h1> + $FreeBSD: + src/release/doc/en_US.ISO8859-1/hardware/common/dev.sgml,v + 1.157 2003/05/30 11:24:00 nyan 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 id="AEN101" name="AEN101">3.1 Disk + Controllers</a></h2> + + <p>IDE/ATA controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Acard ATP850 UDMA2, ATP860 UDMA4, ATP865 UDMA6</p> + </li> + + <li> + <p>AMD 756 ATA66, 766 ATA100, 768 ATA100</p> + </li> + + <li> + <p>Cenatek Rocket Drive</p> + </li> + + <li> + <p>CMD 646, 648 ATA66, and 649 ATA100</p> + </li> + + <li> + <p>Cypress 82C693</p> + </li> + + <li> + <p>Cyrix 5530 ATA33</p> + </li> + + <li> + <p>HighPoint HPT366 ATA66, HPT370 ATA100, HPT372 + ATA133, HPT374 ATA133</p> + </li> + + <li> + <p>Intel PIIX, PIIX3, PIIX4</p> + </li> + + <li> + <p>Intel ICH ATA66, ICH2 ATA100, ICH3 ATA100, ICH4 + ATA100</p> + </li> + + <li> + <p>nVidia nForce ATA100, nForce2 ATA133</p> + </li> + + <li> + <p>Promise ATA100 OEM chip (pdc20265)</p> + </li> + + <li> + <p>Promise ATA133 OEM chip (pdc20269)</p> + </li> + + <li> + <p>Promise Fasttrak-33, -66, -100, -100 TX2/TX4, -133 + TX2/TX2000</p> + </li> + + <li> + <p>Promise SATA150 TX2/TX4 Serial ATA/150</p> + </li> + + <li> + <p>Promise Ultra-33, -66, -100, -133 + TX2/TX2000/TX4000</p> + </li> + + <li> + <p>ServerWorks ROSB4 ATA33</p> + </li> + + <li> + <p>ServerWorks CSB5 and CSB6 ATA66/ATA100</p> + </li> + + <li> + <p>Sil 0680 UDMA6</p> + </li> + + <li> + <p>SiS 530, 540, 550, 620</p> + </li> + + <li> + <p>SiS 630, 630S, 633, 635, 640, 645, 645DX, 648, + 650, 651, 652, 655, 658, 730, 733, 735, 740, 745, + 746, 748, 750, 751, 752, 755</p> + </li> + + <li> + <p>SiS 5591 ATA100</p> + </li> + + <li> + <p>VIA 82C586 ATA33, 82C596 ATA66, 82C686a ATA66, + 82C686b ATA100</p> + </li> + + <li> + <p>VIA 8233, 8235 ATA133</p> + </li> + </ul> + <br /> + <br /> + + <p>Adaptec SCSI Controllers</p> + + <ul> + <li> + <p>Adaptec + 19160/291x/2920/2930/2940/2950/29160/3940/3950/3960/39160/398x/494x + series PCI SCSI controllers, including + Narrow/Wide/Twin/Ultra/Ultra2 variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahc&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahc</span>(4)</span></a> + driver)</p> + </li> + </ul> + <br /> + <br /> + + <p>Ultra-320 SCSI controllers based on the Adaptec + AIC7901, AIC7901A, and AIC7902 Ultra320 controller chips + (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ahd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ahd</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Adaptec 29320, 29320A, 29320B, 29320LP</p> + </li> + + <li> + <p>Adaptec 39320, 39320D</p> + </li> + </ul> + <br /> + <br /> + + <p>LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, + 53C825, 53C825a, 53C860, 53C875, 53C875a, 53C876, 53C885, + 53C895, 53C895a, 53C896, 53C1010-33, 53C1010-66, 53C1000, + 53C1000R PCI SCSI controllers, either embedded on + motherboard or on add-on boards (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ncr&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ncr</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sym&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sym</span>(4)</span></a> + drivers)</p> + + <ul> + <li> + <p>ASUS SC-200, SC-896</p> + </li> + + <li> + <p>Data Technology DTC3130 (all variants)</p> + </li> + + <li> + <p>DawiControl DC2976UW</p> + </li> + + <li> + <p>Diamond FirePort (all)</p> + </li> + + <li> + <p>NCR cards (all)</p> + </li> + + <li> + <p>Symbios cards (all)</p> + </li> + + <li> + <p>Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, + and 390U3W</p> + </li> + + <li> + <p>Tyan S1365</p> + </li> + </ul> + <br /> + <br /> + + <p>Qlogic controllers and variants (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=isp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">isp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Qlogic 1020, 1040 SCSI and Ultra SCSI host + adapters</p> + </li> + + <li> + <p>Qlogic 1240 dual Ultra SCSI controllers</p> + </li> + + <li> + <p>Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD + controllers</p> + </li> + + <li> + <p>Qlogic 12160 Ultra3 LVD controllers</p> + </li> + + <li> + <p>Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI + controllers</p> + </li> + + <li> + <p>Qlogic 2300 and Qlogic 2312 2-Gigabit Fibre + Channel SCSI controllers</p> + </li> + + <li> + <p>Performance Technology SBS440 ISP1000 variants</p> + </li> + + <li> + <p>Performance Technology SBS450 ISP1040 variants</p> + </li> + + <li> + <p>Performance Technology SBS470 ISP2100 variants</p> + </li> + + <li> + <p>Antares Microsystems P-0033 ISP2100 variants</p> + </li> + </ul> + <br /> + <br /> + + <p>LSI Logic Fusion/MP architecture Fiber Channel + controllers (mpt driver)</p> + + <ul> + <li> + <p>LSI FC909, FC929</p> + </li> + + <li> + <p>LSI 53c1020, 53c1030</p> + </li> + </ul> + <br /> + <br /> + + <p>With all supported SCSI controllers, full support is + provided for SCSI-I, SCSI-II, and SCSI-III peripherals, + including hard disks, optical disks, tape drives + (including DAT, 8mm Exabyte, Mammoth, and DLT), medium + changers, processor target devices and CD-ROM drives. + WORM devices that support CD-ROM commands are supported + for read-only access by the CD-ROM drivers (such as <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>). + WORM/CD-R/CD-RW writing support is provided by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cdrecord&sektion=1&manpath=FreeBSD+Ports"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cdrecord</span>(1)</span></a>, + which is a part of the <a + href="http://www.FreeBSD.org/cgi/url.cgi?ports/sysutils/cdrtools/pkg-descr"> + <tt class="FILENAME">sysutils/cdrtools</tt></a> port in + the Ports Collection.</p> + + <p>The following CD-ROM type systems are supported at + this time:</p> + + <ul> + <li> + <p>SCSI interface (also includes ProAudio Spectrum + and SoundBlaster SCSI) (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a>)</p> + </li> + + <li> + <p>ATAPI IDE interface (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=acd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">acd</span>(4)</span></a>)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="ETHERNET" name="ETHERNET">3.2 + Ethernet Interfaces</a></h2> + + <p>RealTek 8129/8139 Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>Accton ``Cheetah'' EN1207D (MPX 5030/5038; RealTek + 8139 clone)</p> + </li> + + <li> + <p>Allied Telesyn AT2550</p> + </li> + + <li> + <p>Allied Telesyn AT2500TX</p> + </li> + + <li> + <p>D-Link DFE-530TX+, DFE-538TX</p> + </li> + + <li> + <p>Farallon NetLINE 10/100 PCI</p> + </li> + + <li> + <p>Genius GF100TXR (RTL8139)</p> + </li> + + <li> + <p>KTX-9130TX 10/100 Fast Ethernet</p> + </li> + + <li> + <p>NDC Communications NE100TX-E</p> + </li> + + <li> + <p>Netronix Inc. EA-1210 NetEther 10/100</p> + </li> + + <li> + <p>OvisLink LEF-8129TX</p> + </li> + + <li> + <p>OvisLink LEF-8139TX</p> + </li> + + <li> + <p>SMC EZ Card 10/100 PCI 1211-TX</p> + </li> + </ul> + <br /> + <br /> + + <p>Intel 82557-, 82258-, 82559-, 82550- or 82562-based + Fast Ethernet NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fxp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Intel EtherExpress Pro/100B PCI Fast Ethernet</p> + </li> + + <li> + <p>Intel PRO/100+ Management Adapter</p> + </li> + + <li> + <p>Intel Pro/100 VE Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 M Desktop Adapter</p> + </li> + + <li> + <p>Intel Pro/100 S Desktop, Server and Dual-Port + Server Adapters</p> + </li> + </ul> + <br /> + <br /> + + <p>3Com Etherlink XL-based NICs (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xl</span>(4)</span></a> driver)</p> + + <ul> + <li> + <p>3C900/905/905B/905C PCI</p> + </li> + </ul> + <br /> + <br /> + + <p>Sun HME and QFE Ethernet NICs (hme driver)</p> + + <p>Sun GEM (Gigabit Ethernet) and ERI (Fast Ethernet) + NICs (gem driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1667" name="AEN1667">3.3 FDDI + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1677" name="AEN1677">3.4 ATM + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1721" name="AEN1721">3.5 + Wireless Network Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1849" name="AEN1849">3.6 + Miscellaneous Networks</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1880" name="AEN1880">3.7 ISDN + Interfaces</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN1944" name="AEN1944">3.8 + Serial Interfaces</a></h2> + + <p>Serial ports based on the SAB82532 serial chip, + console only (sab driver)</p> + + <p>Serial ports based on the Zilog 8530 dual uart, + console only (zs driver)</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2139" name="AEN2139">3.9 + Audio Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2262" name="AEN2262">3.10 + Camera and Video Capture Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USB" name="USB">3.11 USB + Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="FIREWIRE" name="FIREWIRE">3.12 + IEEE 1394 (Firewire) Devices</a></h2> + + <p>Host Controllers (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fwohci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fwohci</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Ricoh R5C552 chipset</p> + </li> + + <li> + <p>Sony CX3022 chipset</p> + </li> + + <li> + <p>TI TSB12LV22, LV23, 26 and TSB43AA22 chipsets</p> + </li> + + <li> + <p>uPD72861 chipset</p> + </li> + + <li> + <p>VIA VT6306 chipset</p> + </li> + </ul> + <br /> + <br /> + + <p>Storage (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbp</span>(4)</span></a> + driver)</p> + + <ul> + <li> + <p>Apple iPod</p> + </li> + + <li> + <p>Apple Macintosh G4 (target mode)</p> + </li> + </ul> + <br /> + <br /> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="BLUETOOTH" name="BLUETOOTH">3.13 + Bluetooth Devices</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2642" name="AEN2642">3.14 + Cryptographic Accelerators</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN2667" name="AEN2667">3.15 + Miscellaneous</a></h2> + + <p>OpenFirmware console (ofwcons driver)</p> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/hardware.sgml b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware.sgml new file mode 100644 index 0000000000..6903a96811 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/hardware.sgml @@ -0,0 +1,33 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/releases/5.1R/hardware.sgml,v 1.3 2005/10/04 06:52:23 murray Exp $"> +<!ENTITY title "FreeBSD 5.1-RELEASE Hardware Notes"> +<!ENTITY % navinclude.download "INCLUDE"> +]> +<html> + &header; + + <p>The hardware notes for FreeBSD are customized for different + platforms, as many devices are only supported on (or are + only relevant for) + specific processors or architectures.</p> + + <p>Hardware notes for FreeBSD 5.1-RELEASE are available for the following + platforms:</p> + + <ul> + <li><a href="hardware-alpha.html">alpha</a></li> + <li><a href="hardware-i386.html">i386</a></li> + <li><a href="hardware-ia64.html">ia64</a></li> + <li><a href="hardware-pc98.html">pc98</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> + + &footer; + +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/installation-alpha.html b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-alpha.html new file mode 100644 index 0000000000..8abc9dd7c4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-alpha.html @@ -0,0 +1,1544 @@ +<!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/alpha 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/alpha + 5.1-RELEASE Installation Instructions</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <blockquote class="ABSTRACT"> + <div class="ABSTRACT"> + <a id="AEN11" name="AEN11"></a> + + <p>This article gives some brief instructions on + installing FreeBSD/alpha 5.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 /> + + <h1 class="SECT1"><a id="INSTALL" name="INSTALL">1 + Installing FreeBSD</a></h1> + + <p>This section documents the process of installing a new + distribution of FreeBSD. These instructions pay particular + emphasis to the process of obtaining the FreeBSD + 5.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 /> + + <h2 class="SECT2"><a id="GETTING-STARTED" + name="GETTING-STARTED">1.1 Getting Started</a></h2> + + <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 /> + + <h2 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware + Requirements</a></h2> + + <p>FreeBSD for the Alpha/AXP supports the platforms + described in <tt class="FILENAME">HARDWARE.TXT</tt>.</p> + + <p>You will need a dedicated disk for FreeBSD/alpha. It + is not possible to share a disk with another operating + system at this time. This disk will need to be attached + to a SCSI controller which is supported by the SRM + firmware or an IDE disk assuming the SRM in your machine + supports booting from IDE disks.</p> + + <p>Your root filesystem MUST be the first partition + (partition <tt class="LITERAL">a</tt>) on the disk to be + bootable.</p> + + <p>You will need the SRM console firmware for your + platform. In some cases, it is possible to switch between + AlphaBIOS (or ARC) firmware and SRM. In others it will be + necessary to download new firmware from the vendor's Web + site.</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 /> + + <h2 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 + Floppy Disk Image Instructions</a></h2> + + <p>Depending on how you choose to install FreeBSD, you + may need to create a set of floppy disks (usually two) to + begin the installation process. This section briefly + describes how to create these disks, either from a CDROM + installation or from the Internet. Note that in the + common case of installing FreeBSD from CDROM, on a + machine that supports bootable CDROMs, the steps outlined + in this section will not be needed and can be + skipped.</p> + + <p>For most CDROM or network installations, all you need + to copy onto actual floppies from the <tt + class="FILENAME">floppies/</tt> directory are the <tt + class="FILENAME">kern.flp</tt> and <tt + class="FILENAME">mfsroot.flp</tt> images (for 1.44MB + floppies). Depending on your hardware, you may also need + to make the third <tt class="FILENAME">drivers.flp</tt> + image to provide necessary device drivers.</p> + + <p>Getting these images over the network is easy. Simply + fetch the <tt class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/kern.flp</tt>, <tt + class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/mfsroot.flp</tt>, and <tt + class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/drivers.flp</tt> files from <a + href="ftp://ftp.FreeBSD.org/" + target="_top">ftp://ftp.FreeBSD.org/</a> or one of the + many mirrors listed at <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html" + target="_top">FTP Sites</a> section of the Handbook, or + on the <a href="http://mirrorlist.FreeBSD.org/" + target="_top">http://mirrorlist.FreeBSD.org/</a> Web + pages.</p> + + <p>Get two blank, freshly formatted floppies and image + copy <tt class="FILENAME">kern.flp</tt> onto one and <tt + class="FILENAME">mfsroot.flp</tt> onto the other. These + images are <span class="emphasis"><i + class="EMPHASIS">not</i></span> DOS files. You cannot + simply copy them to a DOS or UFS floppy as regular files, + you need to ``image'' copy them to the floppy with <tt + class="FILENAME">fdimage.exe</tt> under DOS (see the <tt + class="FILENAME">tools</tt> directory on your CDROM or + FreeBSD FTP mirror) or the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dd&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dd</span>(1)</span></a> command in + UNIX.</p> + + <p>For example, to create the kernel floppy image from + DOS, you'd do something like this:</p> +<pre class="SCREEN"> +<tt class="PROMPT">C></tt> <tt +class="USERINPUT"><b>fdimage kern.flp a:</b></tt> +</pre> + + <p>Assuming that you'd copied <tt + class="FILENAME">fdimage.exe</tt> and <tt + class="FILENAME">kern.flp</tt> into a directory + somewhere. You would do the same for <tt + class="FILENAME">mfsroot.flp</tt>, of course.</p> + + <p>If you're creating the boot floppy from a UNIX + machine, you may find that:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>dd if=floppies/kern.flp of=/dev/rfd0</b></tt> +</pre> + + <p>or</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>dd if=floppies/kern.flp of=/dev/floppy</b></tt> +</pre> + + <p>work well, depending on your hardware and operating + system environment (different versions of UNIX have + different names for the floppy drive).</p> + + <p>If you're on an alpha machine that can network-boot + its floppy images or you have a 2.88MB or LS-120 floppy + capable of taking a 2.88MB image on an x86 machine, you + may wish to use the single (but twice as large) <tt + class="FILENAME">boot.flp</tt> image. It contains the + contents of <tt class="FILENAME">kern.flp</tt> and <tt + class="FILENAME">mfsroot.flp</tt> on a single floppy. + This file should also be used as the boot file for those + mastering ``El Torito'' bootable CD images. See the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mkisofs&sektion=8&manpath=FreeBSD+Ports"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mkisofs</span>(8)</span></a> + command for more information.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="START-INSTALLATION" + name="START-INSTALLATION">1.4 Installing FreeBSD from + CDROM or the Internet</a></h2> + + <p>The easiest type of installation is from CDROM. If you + have a supported CDROM drive and a FreeBSD installation + CDROM, you can boot FreeBSD directly from the CDROM. + Insert the CDROM into the drive and type the following + command to start the installation (substituting the name + of the appropriate CDROM drive if necessary):</p> +<pre class="SCREEN"> +>>><tt class="USERINPUT"><b>boot dka0</b></tt> +</pre> + + <p>Alternatively you can boot the installation from + floppy disk. You should start the installation by + building a set of FreeBSD boot floppies from the files + <tt class="FILENAME">floppies/kern.flp</tt> and <tt + class="FILENAME">floppies/mfsroot.flp</tt> using the + instructions found in <a href="#FLOPPIES">Section + 1.3</a>. From the SRM console prompt (<tt + class="LITERAL">>>></tt>), just insert the <tt + class="FILENAME">kern.flp</tt> floppy and type the + following command to start the installation:</p> +<pre class="SCREEN"> +>>><tt class="USERINPUT"><b>boot dva0</b></tt> +</pre> + + <p>Insert the <tt class="FILENAME">mfsroot.flp</tt> + floppy when prompted and you will end up at the first + screen of the install program.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN209" name="AEN209">1.5 Detail + on various installation types</a></h2> + + <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> + + <p>Once the install procedure has finished, you will be + able to start FreeBSD/alpha by typing something like this + to the SRM prompt:</p> +<pre class="SCREEN"> +>>><tt class="USERINPUT"><b>boot dkc0</b></tt> +</pre> + + <p>This instructs the firmware to boot the specified + disk. To find the SRM names of disks in your machine, use + the <tt class="LITERAL">show device</tt> command:</p> +<pre class="SCREEN"> +>>><tt class="USERINPUT"><b>show device</b></tt> +dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476 +dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658 +dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015 +dva0.0.0.0.1 DVA0 +ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01 +pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27 +pqa0.0.0.4.0 PQA0 PCI EIDE +pqb0.0.1.4.0 PQB0 PCI EIDE +</pre> + + <p>This example is from a Digital Personal Workstation + 433au and shows three disks attached to the machine. The + first is a CDROM called <tt class="DEVICENAME">dka0</tt> + and the other two are disks and are called <tt + class="DEVICENAME">dkc0</tt> and <tt + class="DEVICENAME">dkc100</tt> respectively.</p> + + <p>You can specify which kernel file to load and what + boot options to use with the <tt + class="OPTION">-file</tt> and <tt + class="OPTION">-flags</tt> options, for example:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>boot -file kernel.old -flags s</b></tt> +</pre> + + <p>To make FreeBSD/alpha boot automatically, use these + commands:</p> +<pre class="SCREEN"> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>set boot_osflags a</b></tt> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>set bootdef_dev dkc0</b></tt> +<tt class="PROMPT">>>></tt> <tt +class="USERINPUT"><b>set auto_action BOOT</b></tt> +</pre> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN248" name="AEN248">1.5.1 + Installing from a Network CDROM</a></h3> + + <p>If you simply wish to install from a local CDROM + drive then see <a href="#START-INSTALLATION">Section + 1.4</a>. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:</p> + + <ul> + <li> + <p>If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+5.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+5.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 /> + + <h3 class="SECT3"><a id="AEN280" name="AEN280">1.5.2 + Installing from Floppies</a></h3> + + <p>If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.</p> + + <p>First, make your boot floppies as described in <a + href="#FLOPPIES">Section 1.3</a>.</p> + + <p>Second, peruse <a href="#LAYOUT">Section 2</a> and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.</p> + + <p>Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the <tt + class="FILENAME">bin</tt> (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies <span class="emphasis"><i + class="EMPHASIS">must</i></span> be formatted using the + MS-DOS <tt class="FILENAME">FORMAT</tt> command. If + you're using Windows, use the Windows File Manager + format command.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Frequently, floppy disks come + ``factory preformatted''. While convenient, many + problems reported by users in the past have + resulted from the use of improperly formatted + media. Re-format them yourself, just to make + sure.</p> + </blockquote> + </div> + + <p>If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+5.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+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>fdformat -f 1440 fd0.1440</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>disklabel -w -r fd0.1440 floppy3</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</b></tt> +</pre> + + <p>After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: <tt + class="FILENAME">a:\bin\bin.inf</tt>, <tt + class="FILENAME">a:\bin\bin.aa</tt>, <tt + class="FILENAME">a:\bin\bin.ab</tt>, ...</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> The <tt + class="FILENAME">bin.inf</tt> file also needs to go + on the first floppy of the <tt + class="FILENAME">bin</tt> set since it is read by + the installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">distname.inf</tt> file <span + class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first + floppy of each distribution set. This is also + covered in <tt + class="FILENAME">README.TXT</tt>.</p> + </blockquote> + </div> + + <p>Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN350" name="AEN350">1.5.4 + Installing from QIC/SCSI Tape</a></h3> + + <p>When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt class="USERINPUT"><b>cd <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>tar cvf /dev/rsa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt +class="REPLACEABLE"><i>dist2</i></tt></b></tt> +</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 /> + + <h3 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 + Installing over a Network using FTP or NFS</a></h3> + + <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 /> + + <h4 class="SECT4"><a id="AEN375" + name="AEN375">1.5.5.1 Serial Port</a></h4> + + <p>SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.</p> + + <p>If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.</p> + + <p>You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.</p> + </div> + + <div class="SECT4"> + <hr /> + + <h4 class="SECT4"><a id="AEN381" + name="AEN381">1.5.5.2 Parallel Port</a></h4> + + <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 <tt + class="OPTION">link0</tt> 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 /> + + <h4 class="SECT4"><a id="AEN392" + name="AEN392">1.5.5.3 Ethernet</a></h4> + + <p>FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see <tt + class="FILENAME">HARDWARE.TXT</tt> in the + Documentation menu on the boot floppy or the top + level directory of the CDROM). If you are using one + of the supported PCMCIA Ethernet cards, also be sure + that it's plugged in <span class="emphasis"><i + class="EMPHASIS">before</i></span> the laptop is + powered on. FreeBSD does not, unfortunately, + currently support ``hot insertion'' of PCMCIA cards + during installation.</p> + + <p>You will also need to know your IP address on the + network, the <tt class="OPTION">netmask</tt> 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 /> + + <h4 class="SECT4"><a id="AEN403" + name="AEN403">1.5.5.4 NFS installation tips</a></h4> + + <p>NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.</p> + + <p>If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.</p> + + <p>If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.</p> + + <p>In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on <tt + class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, + then <tt class="HOSTID">wiggy</tt> will have to allow + the direct mounting of <tt + class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not + just <tt class="FILENAME">/usr</tt> or <tt + class="FILENAME">/usr/archive/stuff</tt>.</p> + + <p>In FreeBSD's <tt + class="FILENAME">/etc/exports</tt> file this is + controlled by the <tt class="OPTION">-alldirs</tt> + 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 /> + + <h4 class="SECT4"><a id="AEN420" + name="AEN420">1.5.5.5 FTP Installation tips</a></h4> + + <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/alpha/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"> +<tt class="USERINPUT"><b>ftp://foo.bar.com:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</b></tt> +</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 class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN441" name="AEN441">1.5.6 + Tips for Serial Console Users</a></h3> + + <p>If you'd like to install FreeBSD on a machine using + just a serial port (e.g. you don't have or wish to use + a VGA card), please follow these steps:</p> + + <div class="PROCEDURE"> + <ol type="1"> + <li> + <p>Connect some sort of ANSI (vt100) compatible + terminal or terminal emulation program to the <tt + class="DEVICENAME">COM1</tt> port of the PC you + are installing FreeBSD onto.</p> + </li> + + <li> + <p>Unplug the keyboard (yes, that's correct!) and + then try to boot from floppy or the installation + CDROM, depending on the type of installation + media you have, with the keyboard unplugged.</p> + </li> + + <li> + <p>If you don't get any output on your serial + console, plug the keyboard in again and wait for + some beeps. If you are booting from the CDROM, + proceed to <a href="#HITSPACE">step 5</a> as soon + as you hear the beep.</p> + </li> + + <li> + <p>For a floppy boot, the first beep means to + remove the <tt class="FILENAME">kern.flp</tt> + floppy and insert the <tt + class="FILENAME">mfsroot.flp</tt> floppy, after + which you should press <b + class="KEYCAP">Enter</b> and wait for another + beep.</p> + </li> + + <li> + <a id="HITSPACE" name="HITSPACE"></a> + + <p>Hit the space bar, then enter</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>boot -h</b></tt> +</pre> + + <p>and you should now definitely be seeing + everything on the serial port. If that still + doesn't work, check your serial cabling as well + as the settings on your terminal emulation + program or actual terminal device. It should be + set for 9600 baud, 8 bits, no parity.</p> + </li> + </ol> + </div> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN463" name="AEN463">1.6 + Question and Answer Section for Alpha/AXP Architecture + Users</a></h2> + + <div class="QANDASET"> + <dl> + <dt>1.6.1. <a href="#Q1.6.1.">Can I boot from the ARC + or Alpha BIOS Console?</a></dt> + + <dt>1.6.2. <a href="#Q1.6.2.">Help! I have no space! + Do I need to delete everything first?</a></dt> + + <dt>1.6.3. <a href="#Q1.6.3.">Can I mount my Compaq + Tru64 or VMS extended partitions?</a></dt> + + <dt>1.6.4. <a href="#Q1.6.4.">What about support for + Compaq Tru64 (OSF/1) binaries?</a></dt> + + <dt>1.6.5. <a href="#Q1.6.5.">What about support for + Linux binaries?</a></dt> + + <dt>1.6.6. <a href="#Q1.6.6.">What about support for + NT Alpha binaries?</a></dt> + </dl> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.1." name="Q1.6.1."></a><b>1.6.1.</b> + Can I boot from the ARC or Alpha BIOS Console?</p> + </div> + + <div class="ANSWER"> + <p><b></b>No. FreeBSD, like Compaq Tru64 and VMS, + will only boot from the SRM console.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.2." name="Q1.6.2."></a><b>1.6.2.</b> + Help! I have no space! Do I need to delete + everything first?</p> + </div> + + <div class="ANSWER"> + <p><b></b>Unfortunately, yes.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.3." name="Q1.6.3."></a><b>1.6.3.</b> + Can I mount my Compaq Tru64 or VMS extended + partitions?</p> + </div> + + <div class="ANSWER"> + <p><b></b>No, not at this time.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.4." name="Q1.6.4."></a><b>1.6.4.</b> + What about support for Compaq Tru64 (OSF/1) + binaries?</p> + </div> + + <div class="ANSWER"> + <p><b></b>FreeBSD can run Tru64 applications very + well using the <a + href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/osf1_base/pkg-descr"> + <tt class="FILENAME">emulators/osf1_base</tt></a> + port/package.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.5." name="Q1.6.5."></a><b>1.6.5.</b> + What about support for Linux binaries?</p> + </div> + + <div class="ANSWER"> + <p><b></b>FreeBSD can run AlphaLinux binaries with + the assistance of the <a + href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/linux_base/pkg-descr"> + <tt class="FILENAME">emulators/linux_base</tt></a> + port/package.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.6." name="Q1.6.6."></a><b>1.6.6.</b> + What about support for NT Alpha binaries?</p> + </div> + + <div class="ANSWER"> + <p><b></b>FreeBSD is not able to run NT + applications natively, although it has the ability + to mount NT partitions.</p> + </div> + </div> + </div> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 + Distribution Format</a></h1> + + <p>A typical FreeBSD distribution directory looks something + like this (exact details may vary depending on version, + architecture, and other factors):</p> +<pre class="SCREEN"> +ERRATA.HTM README.TXT compat1x dict kernel +ERRATA.TXT RELNOTES.HTM compat20 doc manpages +HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages +HARDWARE.TXT base compat22 filename.txt ports +INSTALL.HTM boot compat3x floppies proflibs +INSTALL.TXT catpages compat4x games src +README.HTM cdrom.inf crypto info tools +</pre> + + <p>If you want to do a CDROM, FTP or NFS installation from + this distribution directory, all you need to do is make the + 1.44MB boot floppies from the floppies directory (see <a + href="#FLOPPIES">Section 1.3</a> for instructions on how to + do this), boot them and follow the instructions. The rest + of the data needed during the installation will be obtained + automatically based on your selections. If you've never + installed FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.</p> + + <p>If you're trying to do some other type of installation + or are merely curious about how a distribution is + organized, what follows is a more thorough description of + some of these items in more detail:</p> + + <ol type="1"> + <li> + <p>The <tt class="FILENAME">*.TXT</tt> and <tt + class="FILENAME">*.HTM</tt> files contain documentation + (for example, this document is contained in both <tt + class="FILENAME">INSTALL.TXT</tt> and <tt + class="FILENAME">INSTALL.HTM</tt>) and should be read + before starting an installation. The <tt + class="FILENAME">*.TXT</tt> files are plain text, while + the <tt class="FILENAME">*.HTM</tt> files are HTML + files that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.</p> + </li> + + <li> + <p><tt class="FILENAME">docbook.css</tt> is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.</p> + </li> + + <li> + <p>The <tt class="FILENAME">base</tt>, <tt + class="FILENAME">catpages</tt>, <tt + class="FILENAME">crypto</tt>, <tt + class="FILENAME">dict</tt>, <tt + class="FILENAME">doc</tt>, <tt + class="FILENAME">games</tt>, <tt + class="FILENAME">info</tt>, <tt + class="FILENAME">manpages</tt>, <tt + class="FILENAME">proflibs</tt>, and <tt + class="FILENAME">src</tt> directories contain the + primary distribution components of FreeBSD itself and + are split into smaller files for easy packing onto + floppies (should that be necessary).</p> + </li> + + <li> + <p>The <tt class="FILENAME">compat1x</tt>, <tt + class="FILENAME">compat20</tt>, <tt + class="FILENAME">compat21</tt>, <tt + class="FILENAME">compat22</tt>, <tt + class="FILENAME">compat3x</tt>, and <tt + class="FILENAME">compat4x</tt> directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their <tt class="FILENAME">install.sh</tt> scripts.</p> + </li> + + <li> + <p>The <tt class="FILENAME">floppies/</tt> subdirectory + contains the floppy installation images; further + information on using them can be found in <a + href="#FLOPPIES">Section 1.3</a>.</p> + </li> + + <li> + <p>The <tt class="FILENAME">packages</tt> and <tt + class="FILENAME">ports</tt> directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt><tt +class="USERINPUT"><b>/stand/sysinstall configPackages</b></tt> +</pre> + + <p>Packages can also be installed by feeding individual + filenames in <tt class="FILENAME">packages</tt>/ to the + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.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 100MB unpacked. More + information on the ports collection may be obtained + from <a href="http://www.FreeBSD.org/ports/" + target="_top">http://www.FreeBSD.org/ports/</a> or + locally from <tt + class="FILENAME">/usr/share/doc/handbook</tt> if you've + installed the <tt class="FILENAME">doc</tt> + distribution.</p> + </li> + + <li> + <p>Last of all, the <tt class="FILENAME">tools</tt> + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.</p> + </li> + </ol> + <br /> + <br /> + + <p>A typical distribution directory (for example, the <tt + class="FILENAME">info</tt> distribution) looks like this + internally:</p> +<pre class="SCREEN"> +CHECKSUM.MD5 info.ab info.ad info.inf install.sh +info.aa info.ac info.ae info.mtree +</pre> + + <p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains + MD5 signatures for each file, should data corruption be + suspected, and is purely for reference. It is not used by + the actual installation and does not need to be copied with + the rest of the distribution files. The <tt + class="FILENAME">info.a*</tt> files are split, gzip'd tar + files, the contents of which can be viewed by doing:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cat info.a* | tar tvzf -</b></tt> +</pre> + + <p>During installation, they are automatically concatenated + and extracted by the installation procedure.</p> + + <p>The <tt class="FILENAME">info.inf</tt> file is also + necessary since it is read by the installation program in + order to figure out how many pieces to look for when + fetching and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">.inf</tt> file <span class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first floppy of + each distribution set!</p> + + <p>The <tt class="FILENAME">info.mtree</tt> file is another + non-essential file which is provided for user reference. It + contains the MD5 signatures of the <span + class="emphasis"><i class="EMPHASIS">unpacked</i></span> + distribution files and can be later used with the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&sektion=8&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cd /cdrom/info</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>sh install.sh</b></tt> +</pre> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 + Upgrading FreeBSD</a></h1> + + <p>These instructions describe a procedure for doing a + binary upgrade from an older version of FreeBSD.</p> + + <div class="WARNING"> + <blockquote class="WARNING"> + <p><b>Warning:</b> While the FreeBSD upgrade procedure + does its best to safeguard against accidental loss of + data, it is still more than possible to <span + class="emphasis"><i class="EMPHASIS">wipe out your + entire disk</i></span> with this installation! Please + do not accept the final confirmation request unless you + have adequately backed up any important data files.</p> + </blockquote> + </div> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> These notes assume that you are + using the version of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.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+5.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+5.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 + 5.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></p> + + <p>These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.</p> + </blockquote> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN664" name="AEN664">3.1 + Introduction</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN668" name="AEN668">3.1.1 + Upgrade Overview</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN742" name="AEN742">3.2 + Procedure</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN745" name="AEN745">3.2.1 + Backup</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN748" name="AEN748">3.2.2 + Mount Filesystems</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN753" name="AEN753">3.2.3 + Select Distributions</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 + After Installation</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN763" name="AEN763">3.3 + Upgrading from Source Code</a></h2> + + <p>Those interested in an upgrade method that allows more + flexibility and sophistication should take a look at <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html" + target="_top">The Cutting Edge</a> in the FreeBSD + Handbook. This procedure involves rebuilding all of + FreeBSD from source code. It requires reliable network + connectivity, extra disk space, and time, but has + advantages for networks and other more complex + installations. This is roughly the same procedure as is + used for track the -STABLE or -CURRENT development + branches.</p> + + <p><tt class="FILENAME">/usr/src/UPDATING</tt> contains + important information on updating a FreeBSD system from + source code. It lists various issues resulting from + changes in FreeBSD that may affect an upgrade.</p> + + <p></p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 + Troubleshooting</a></h1> + + <div class="SECT2"> + <h2 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 + Repairing an Existing FreeBSD Installation</a></h2> + + <p>FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + <tt class="FILENAME">fixit.flp</tt> image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.</p> + + <p>To invoke fixit, simply boot the <tt + class="FILENAME">kern.flp</tt> floppy, choose the + ``Fixit'' item and insert the fixit floppy or CDROM when + asked. You will then be placed into a shell with a wide + variety of commands available (in the <tt + class="FILENAME">/stand</tt> and <tt + class="FILENAME">/mnt2/stand</tt> directories) for + checking, repairing and examining filesystems and their + contents. Some UNIX administration experience <span + class="emphasis"><i class="EMPHASIS">is</i></span> + required to use the fixit option.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN784" name="AEN784">4.2 Common + Installation Problems for Alpha/AXP Architecture + Users</a></h2> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/installation-i386.html b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-i386.html new file mode 100644 index 0000000000..cc1be5cc45 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-i386.html @@ -0,0 +1,2091 @@ +<!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/i386 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/i386 + 5.1-RELEASE Installation Instructions</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <blockquote class="ABSTRACT"> + <div class="ABSTRACT"> + <a id="AEN11" name="AEN11"></a> + + <p>This article gives some brief instructions on + installing FreeBSD/i386 5.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 /> + + <h1 class="SECT1"><a id="INSTALL" name="INSTALL">1 + Installing FreeBSD</a></h1> + + <p>This section documents the process of installing a new + distribution of FreeBSD. These instructions pay particular + emphasis to the process of obtaining the FreeBSD + 5.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 /> + + <h2 class="SECT2"><a id="GETTING-STARTED" + name="GETTING-STARTED">1.1 Getting Started</a></h2> + + <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 /> + + <h2 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware + Requirements</a></h2> + + <p>FreeBSD for the i386 requires a 386 or better + processor to run (sorry, there is no support for 286 + processors) and at least 5 megs of RAM to install and 4 + megs of RAM to run. You will need at least 100MB of free + hard drive space for the most minimal installation. See + below for ways of shrinking existing DOS partitions in + order to install FreeBSD.</p> + + <p>If you are not familiar with configuring hardware for + FreeBSD, you should be sure to read the <tt + class="FILENAME">HARDWARE.TXT</tt> file; it contains + important information on what hardware is supported by + FreeBSD.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 + Floppy Disk Image Instructions</a></h2> + + <p>Depending on how you choose to install FreeBSD, you + may need to create a set of floppy disks (usually two) to + begin the installation process. This section briefly + describes how to create these disks, either from a CDROM + installation or from the Internet. Note that in the + common case of installing FreeBSD from CDROM, on a + machine that supports bootable CDROMs, the steps outlined + in this section will not be needed and can be + skipped.</p> + + <p>For most CDROM or network installations, all you need + to copy onto actual floppies from the <tt + class="FILENAME">floppies/</tt> directory are the <tt + class="FILENAME">kern.flp</tt> and <tt + class="FILENAME">mfsroot.flp</tt> images (for 1.44MB + floppies). Depending on your hardware, you may also need + to make the third <tt class="FILENAME">drivers.flp</tt> + image to provide necessary device drivers.</p> + + <p>Getting these images over the network is easy. Simply + fetch the <tt class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/kern.flp</tt>, <tt + class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/mfsroot.flp</tt>, and <tt + class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/drivers.flp</tt> files from <a + href="ftp://ftp.FreeBSD.org/" + target="_top">ftp://ftp.FreeBSD.org/</a> or one of the + many mirrors listed at <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html" + target="_top">FTP Sites</a> section of the Handbook, or + on the <a href="http://mirrorlist.FreeBSD.org/" + target="_top">http://mirrorlist.FreeBSD.org/</a> Web + pages.</p> + + <p>Get two blank, freshly formatted floppies and image + copy <tt class="FILENAME">kern.flp</tt> onto one and <tt + class="FILENAME">mfsroot.flp</tt> onto the other. These + images are <span class="emphasis"><i + class="EMPHASIS">not</i></span> DOS files. You cannot + simply copy them to a DOS or UFS floppy as regular files, + you need to ``image'' copy them to the floppy with <tt + class="FILENAME">fdimage.exe</tt> under DOS (see the <tt + class="FILENAME">tools</tt> directory on your CDROM or + FreeBSD FTP mirror) or the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dd&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dd</span>(1)</span></a> command in + UNIX.</p> + + <p>For example, to create the kernel floppy image from + DOS, you'd do something like this:</p> +<pre class="SCREEN"> +<tt class="PROMPT">C></tt> <tt +class="USERINPUT"><b>fdimage kern.flp a:</b></tt> +</pre> + + <p>Assuming that you'd copied <tt + class="FILENAME">fdimage.exe</tt> and <tt + class="FILENAME">kern.flp</tt> into a directory + somewhere. You would do the same for <tt + class="FILENAME">mfsroot.flp</tt>, of course.</p> + + <p>If you're creating the boot floppy from a UNIX + machine, you may find that:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>dd if=floppies/kern.flp of=/dev/rfd0</b></tt> +</pre> + + <p>or</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>dd if=floppies/kern.flp of=/dev/floppy</b></tt> +</pre> + + <p>work well, depending on your hardware and operating + system environment (different versions of UNIX have + different names for the floppy drive).</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="START-INSTALLATION" + name="START-INSTALLATION">1.4 Installing FreeBSD from + CDROM or the Internet</a></h2> + + <p>The easiest type of installation is from CDROM. If you + have a supported CDROM drive and a FreeBSD installation + CDROM, there are 2 ways of starting the installation from + it:</p> + + <ul> + <li> + <p>If your system supports bootable CDROM media + (usually an option which can be selectively enabled + in the controller's setup menu or in the PC BIOS for + some systems) and you have it enabled, FreeBSD + supports the ``El Torito'' bootable CD standard. + Simply put the installation CD in your CDROM drive + and boot the system to begin installation.</p> + </li> + + <li> + <p>Build a set of FreeBSD boot floppies from the <tt + class="FILENAME">floppies/</tt> directory in every + FreeBSD distribution. Either simply use the <tt + class="FILENAME">makeflp.bat</tt> script from DOS or + read <a href="#FLOPPIES">Section 1.3</a> for more + information on creating the bootable floppies under + different operating systems. Then you simply boot + from the first floppy and you should soon be in the + FreeBSD installation.</p> + </li> + </ul> + <br /> + <br /> + + <p>If you don't have a CDROM (or your computer does not + support booting from CDROM) and would like to simply + install over the net using PPP, SLIP or a dedicated + connection. You should start the installation by building + a set of FreeBSD boot floppies from the files <tt + class="FILENAME">floppies/kern.flp</tt> and <tt + class="FILENAME">floppies/mfsroot.flp</tt> using the + instructions found in <a href="#FLOPPIES">Section + 1.3</a>. Restart your computer using the <tt + class="FILENAME">kern.flp</tt> disk; when prompted, + insert the <tt class="FILENAME">mfsroot.flp</tt> disk. + Then, please go to <a href="#FTPNFS">Section 1.5.5</a> + for additional tips on installing via FTP or NFS.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN209" name="AEN209">1.5 Detail + on various installation types</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN248" name="AEN248">1.5.1 + Installing from a Network CDROM</a></h3> + + <p>If you simply wish to install from a local CDROM + drive then see <a href="#START-INSTALLATION">Section + 1.4</a>. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:</p> + + <ul> + <li> + <p>If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+5.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+5.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 /> + + <h3 class="SECT3"><a id="AEN280" name="AEN280">1.5.2 + Installing from Floppies</a></h3> + + <p>If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.</p> + + <p>First, make your boot floppies as described in <a + href="#FLOPPIES">Section 1.3</a>.</p> + + <p>Second, peruse <a href="#LAYOUT">Section 2</a> and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.</p> + + <p>Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the <tt + class="FILENAME">bin</tt> (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies <span class="emphasis"><i + class="EMPHASIS">must</i></span> be formatted using the + MS-DOS <tt class="FILENAME">FORMAT</tt> command. If + you're using Windows, use the Windows File Manager + format command.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Frequently, floppy disks come + ``factory preformatted''. While convenient, many + problems reported by users in the past have + resulted from the use of improperly formatted + media. Re-format them yourself, just to make + sure.</p> + </blockquote> + </div> + + <p>If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+5.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+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>fdformat -f 1440 fd0.1440</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>disklabel -w -r fd0.1440 floppy3</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</b></tt> +</pre> + + <p>After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: <tt + class="FILENAME">a:\bin\bin.inf</tt>, <tt + class="FILENAME">a:\bin\bin.aa</tt>, <tt + class="FILENAME">a:\bin\bin.ab</tt>, ...</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> The <tt + class="FILENAME">bin.inf</tt> file also needs to go + on the first floppy of the <tt + class="FILENAME">bin</tt> set since it is read by + the installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">distname.inf</tt> file <span + class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first + floppy of each distribution set. This is also + covered in <tt + class="FILENAME">README.TXT</tt>.</p> + </blockquote> + </div> + + <p>Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN322" name="AEN322">1.5.3 + Installing from a DOS partition</a></h3> + + <p>To prepare for installation from an MS-DOS partition + you should simply copy the files from the distribution + into a directory called <tt + class="FILENAME">FREEBSD</tt> on the Primary DOS + partition (<tt class="DEVICENAME">C:</tt>). For + example, to do a minimal installation of FreeBSD from + DOS using files copied from the CDROM, you might do + something like this:</p> +<pre class="SCREEN"> +<tt class="PROMPT">C:\></tt> <tt +class="USERINPUT"><b>MD C:\FREEBSD</b></tt> +<tt class="PROMPT">C:\></tt> <tt +class="USERINPUT"><b>XCOPY /S E:\BASE C:\FREEBSD\BASE</b></tt> +</pre> + + <p>Assuming that <tt class="DEVICENAME">E:</tt> was + where your CD was mounted.</p> + + <p>For as many distributions as you wish to install + from DOS (and you have free space for), install each + one in a directory under <tt + class="FILENAME">C:\FREEBSD</tt> - the <tt + class="FILENAME">BIN</tt> dist is only the minimal + requirement.</p> + + <p>Once you've copied the directories, you can simply + launch the installation from floppies as normal and + select ``DOS'' as your media type when the time + comes.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN350" name="AEN350">1.5.4 + Installing from QIC/SCSI Tape</a></h3> + + <p>When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt class="USERINPUT"><b>cd <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>tar cvf /dev/rsa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt +class="REPLACEABLE"><i>dist2</i></tt></b></tt> +</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 /> + + <h3 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 + Installing over a Network using FTP or NFS</a></h3> + + <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 /> + + <h4 class="SECT4"><a id="AEN375" + name="AEN375">1.5.5.1 Serial Port</a></h4> + + <p>SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.</p> + + <p>If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.</p> + + <p>You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.</p> + </div> + + <div class="SECT4"> + <hr /> + + <h4 class="SECT4"><a id="AEN381" + name="AEN381">1.5.5.2 Parallel Port</a></h4> + + <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 <tt + class="OPTION">link0</tt> 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 /> + + <h4 class="SECT4"><a id="AEN392" + name="AEN392">1.5.5.3 Ethernet</a></h4> + + <p>FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see <tt + class="FILENAME">HARDWARE.TXT</tt> in the + Documentation menu on the boot floppy or the top + level directory of the CDROM). If you are using one + of the supported PCMCIA Ethernet cards, also be sure + that it's plugged in <span class="emphasis"><i + class="EMPHASIS">before</i></span> the laptop is + powered on. FreeBSD does not, unfortunately, + currently support ``hot insertion'' of PCMCIA cards + during installation.</p> + + <p>You will also need to know your IP address on the + network, the <tt class="OPTION">netmask</tt> 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 /> + + <h4 class="SECT4"><a id="AEN403" + name="AEN403">1.5.5.4 NFS installation tips</a></h4> + + <p>NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.</p> + + <p>If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.</p> + + <p>If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.</p> + + <p>In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on <tt + class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, + then <tt class="HOSTID">wiggy</tt> will have to allow + the direct mounting of <tt + class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not + just <tt class="FILENAME">/usr</tt> or <tt + class="FILENAME">/usr/archive/stuff</tt>.</p> + + <p>In FreeBSD's <tt + class="FILENAME">/etc/exports</tt> file this is + controlled by the <tt class="OPTION">-alldirs</tt> + 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 /> + + <h4 class="SECT4"><a id="AEN420" + name="AEN420">1.5.5.5 FTP Installation tips</a></h4> + + <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/i386/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"> +<tt class="USERINPUT"><b>ftp://foo.bar.com:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</b></tt> +</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 class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN441" name="AEN441">1.5.6 + Tips for Serial Console Users</a></h3> + + <p>If you'd like to install FreeBSD on a machine using + just a serial port (e.g. you don't have or wish to use + a VGA card), please follow these steps:</p> + + <div class="PROCEDURE"> + <ol type="1"> + <li> + <p>Connect some sort of ANSI (vt100) compatible + terminal or terminal emulation program to the <tt + class="DEVICENAME">COM1</tt> port of the PC you + are installing FreeBSD onto.</p> + </li> + + <li> + <p>Unplug the keyboard (yes, that's correct!) and + then try to boot from floppy or the installation + CDROM, depending on the type of installation + media you have, with the keyboard unplugged.</p> + </li> + + <li> + <p>If you don't get any output on your serial + console, plug the keyboard in again and wait for + some beeps. If you are booting from the CDROM, + proceed to <a href="#HITSPACE">step 5</a> as soon + as you hear the beep.</p> + </li> + + <li> + <p>For a floppy boot, the first beep means to + remove the <tt class="FILENAME">kern.flp</tt> + floppy and insert the <tt + class="FILENAME">mfsroot.flp</tt> floppy, after + which you should press <b + class="KEYCAP">Enter</b> and wait for another + beep.</p> + </li> + + <li> + <a id="HITSPACE" name="HITSPACE"></a> + + <p>Hit the space bar, then enter</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>boot -h</b></tt> +</pre> + + <p>and you should now definitely be seeing + everything on the serial port. If that still + doesn't work, check your serial cabling as well + as the settings on your terminal emulation + program or actual terminal device. It should be + set for 9600 baud, 8 bits, no parity.</p> + </li> + </ol> + </div> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN463" name="AEN463">1.6 + Question and Answer Section for i386 Architecture + Users</a></h2> + + <div class="QANDASET"> + <dl> + <dt>1.6.1. <a href="#Q1.6.1.">Help! I have no space! + Do I need to delete everything first?</a></dt> + + <dt>1.6.2. <a href="#Q1.6.2.">Can I use compressed + DOS filesystems from FreeBSD?</a></dt> + + <dt>1.6.3. <a href="#Q1.6.3.">Can I mount my DOS + extended partitions?</a></dt> + + <dt>1.6.4. <a href="#Q1.6.4.">Can I run DOS binaries + under FreeBSD?</a></dt> + </dl> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.1." name="Q1.6.1."></a><b>1.6.1.</b> + Help! I have no space! Do I need to delete + everything first?</p> + </div> + + <div class="ANSWER"> + <p><b></b>If your machine is already running DOS + and has little or no free space available for + FreeBSD's installation, all is not lost! You may + find the <b class="APPLICATION">FIPS</b> utility, + provided in the <tt class="FILENAME">tools/</tt> + subdirectory on the FreeBSD CDROM or on the various + FreeBSD ftp sites, to be quite useful.</p> + + <p><b class="APPLICATION">FIPS</b> allows you to + split an existing DOS partition into two pieces, + preserving the original partition and allowing you + to install onto the second free piece. You first + ``defrag'' your DOS partition, using the DOS 6.xx + <tt class="FILENAME">DEFRAG</tt> utility or the <b + class="APPLICATION">Norton Disk Tools</b>, then run + FIPS. It will prompt you for the rest of the + information it needs. Afterwards, you can reboot + and install FreeBSD on the new partition. Also note + that FIPS will create the second partition as a + ``clone'' of the first, so you'll actually see that + you now have two DOS Primary partitions where you + formerly had one. Don't be alarmed! You can simply + delete the extra DOS Primary partition (making sure + it's the right one by examining its size).</p> + + <p><b class="APPLICATION">FIPS</b> does NOT + currently work with NTFS style partitions. To split + up such a partition, you will need a commercial + product such as <b class="APPLICATION">Partition + Magic</b>. Sorry, but this is just the breaks if + you've got a Windows partition hogging your whole + disk and you don't want to reinstall from + scratch.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.2." name="Q1.6.2."></a><b>1.6.2.</b> + Can I use compressed DOS filesystems from + FreeBSD?</p> + </div> + + <div class="ANSWER"> + <p><b></b>No. If you are using a utility such as <b + class="APPLICATION">Stacker</b>(tm) or <b + class="APPLICATION">DoubleSpace</b>(tm), FreeBSD + will only be able to use whatever portion of the + filesystem you leave uncompressed. The rest of the + filesystem will show up as one large file (the + stacked/dblspaced file!). <span class="emphasis"><i + class="EMPHASIS">Do not remove that file</i></span> + as you will probably regret it greatly!</p> + + <p>It is probably better to create another + uncompressed DOS extended partition and use this + for communications between DOS and FreeBSD if such + is your desire.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.3." name="Q1.6.3."></a><b>1.6.3.</b> + Can I mount my DOS extended partitions?</p> + </div> + + <div class="ANSWER"> + <p><b></b>Yes. DOS extended partitions are mapped + in at the end of the other ``slices'' in FreeBSD, + e.g. your <tt class="DEVICENAME">D:</tt> drive + might be <tt class="FILENAME">/dev/da0s5</tt>, your + <tt class="DEVICENAME">E:</tt> drive <tt + class="FILENAME">/dev/da0s6</tt>, and so on. This + example assumes, of course, that your extended + partition is on SCSI drive 0. For IDE drives, + substitute <tt class="LITERAL">ad</tt> for <tt + class="LITERAL">da</tt> appropriately. You + otherwise mount extended partitions exactly like + you would mount any other DOS drive, e.g.:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>mount -t msdos /dev/da0s5 /dos_d</b></tt> +</pre> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q1.6.4." name="Q1.6.4."></a><b>1.6.4.</b> + Can I run DOS binaries under FreeBSD?</p> + </div> + + <div class="ANSWER"> + <p><b></b>Ongoing work with BSDI's <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=doscmd&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">doscmd</span>(1)</span></a> + utility will suffice in many cases, though it still + has some rough edges. If you're interested in + working on this, please send mail to the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-emulation" + target="_top">FreeBSD-emulation mailing list</a> + and indicate that you're interested in joining this + ongoing effort!</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/pcemu/pkg-descr"> + <tt class="FILENAME">emulators/pcemu</tt></a> + port/package in the FreeBSD Ports Collection which + emulates an 8088 and enough BIOS services to run + DOS text mode applications. It requires the X + Window System (XFree86) to operate.</p> + </div> + </div> + </div> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 + Distribution Format</a></h1> + + <p>A typical FreeBSD distribution directory looks something + like this (exact details may vary depending on version, + architecture, and other factors):</p> +<pre class="SCREEN"> +ERRATA.HTM README.TXT compat1x dict kernel +ERRATA.TXT RELNOTES.HTM compat20 doc manpages +HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages +HARDWARE.TXT base compat22 filename.txt ports +INSTALL.HTM boot compat3x floppies proflibs +INSTALL.TXT catpages compat4x games src +README.HTM cdrom.inf crypto info tools +</pre> + + <p>If you want to do a CDROM, FTP or NFS installation from + this distribution directory, all you need to do is make the + 1.44MB boot floppies from the floppies directory (see <a + href="#FLOPPIES">Section 1.3</a> for instructions on how to + do this), boot them and follow the instructions. The rest + of the data needed during the installation will be obtained + automatically based on your selections. If you've never + installed FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.</p> + + <p>If you're trying to do some other type of installation + or are merely curious about how a distribution is + organized, what follows is a more thorough description of + some of these items in more detail:</p> + + <ol type="1"> + <li> + <p>The <tt class="FILENAME">*.TXT</tt> and <tt + class="FILENAME">*.HTM</tt> files contain documentation + (for example, this document is contained in both <tt + class="FILENAME">INSTALL.TXT</tt> and <tt + class="FILENAME">INSTALL.HTM</tt>) and should be read + before starting an installation. The <tt + class="FILENAME">*.TXT</tt> files are plain text, while + the <tt class="FILENAME">*.HTM</tt> files are HTML + files that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.</p> + </li> + + <li> + <p><tt class="FILENAME">docbook.css</tt> is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.</p> + </li> + + <li> + <p>The <tt class="FILENAME">base</tt>, <tt + class="FILENAME">catpages</tt>, <tt + class="FILENAME">crypto</tt>, <tt + class="FILENAME">dict</tt>, <tt + class="FILENAME">doc</tt>, <tt + class="FILENAME">games</tt>, <tt + class="FILENAME">info</tt>, <tt + class="FILENAME">manpages</tt>, <tt + class="FILENAME">proflibs</tt>, and <tt + class="FILENAME">src</tt> directories contain the + primary distribution components of FreeBSD itself and + are split into smaller files for easy packing onto + floppies (should that be necessary).</p> + </li> + + <li> + <p>The <tt class="FILENAME">compat1x</tt>, <tt + class="FILENAME">compat20</tt>, <tt + class="FILENAME">compat21</tt>, <tt + class="FILENAME">compat22</tt>, <tt + class="FILENAME">compat3x</tt>, and <tt + class="FILENAME">compat4x</tt> directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their <tt class="FILENAME">install.sh</tt> scripts.</p> + </li> + + <li> + <p>The <tt class="FILENAME">floppies/</tt> subdirectory + contains the floppy installation images; further + information on using them can be found in <a + href="#FLOPPIES">Section 1.3</a>.</p> + </li> + + <li> + <p>The <tt class="FILENAME">packages</tt> and <tt + class="FILENAME">ports</tt> directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt><tt +class="USERINPUT"><b>/stand/sysinstall configPackages</b></tt> +</pre> + + <p>Packages can also be installed by feeding individual + filenames in <tt class="FILENAME">packages</tt>/ to the + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.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 100MB unpacked. More + information on the ports collection may be obtained + from <a href="http://www.FreeBSD.org/ports/" + target="_top">http://www.FreeBSD.org/ports/</a> or + locally from <tt + class="FILENAME">/usr/share/doc/handbook</tt> if you've + installed the <tt class="FILENAME">doc</tt> + distribution.</p> + </li> + + <li> + <p>Last of all, the <tt class="FILENAME">tools</tt> + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.</p> + </li> + </ol> + <br /> + <br /> + + <p>A typical distribution directory (for example, the <tt + class="FILENAME">info</tt> distribution) looks like this + internally:</p> +<pre class="SCREEN"> +CHECKSUM.MD5 info.ab info.ad info.inf install.sh +info.aa info.ac info.ae info.mtree +</pre> + + <p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains + MD5 signatures for each file, should data corruption be + suspected, and is purely for reference. It is not used by + the actual installation and does not need to be copied with + the rest of the distribution files. The <tt + class="FILENAME">info.a*</tt> files are split, gzip'd tar + files, the contents of which can be viewed by doing:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cat info.a* | tar tvzf -</b></tt> +</pre> + + <p>During installation, they are automatically concatenated + and extracted by the installation procedure.</p> + + <p>The <tt class="FILENAME">info.inf</tt> file is also + necessary since it is read by the installation program in + order to figure out how many pieces to look for when + fetching and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">.inf</tt> file <span class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first floppy of + each distribution set!</p> + + <p>The <tt class="FILENAME">info.mtree</tt> file is another + non-essential file which is provided for user reference. It + contains the MD5 signatures of the <span + class="emphasis"><i class="EMPHASIS">unpacked</i></span> + distribution files and can be later used with the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&sektion=8&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cd /cdrom/info</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>sh install.sh</b></tt> +</pre> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 + Upgrading FreeBSD</a></h1> + + <p>These instructions describe a procedure for doing a + binary upgrade from an older version of FreeBSD.</p> + + <div class="WARNING"> + <blockquote class="WARNING"> + <p><b>Warning:</b> While the FreeBSD upgrade procedure + does its best to safeguard against accidental loss of + data, it is still more than possible to <span + class="emphasis"><i class="EMPHASIS">wipe out your + entire disk</i></span> with this installation! Please + do not accept the final confirmation request unless you + have adequately backed up any important data files.</p> + </blockquote> + </div> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> These notes assume that you are + using the version of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.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+5.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+5.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 + 5.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></p> + + <p>These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.</p> + </blockquote> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN664" name="AEN664">3.1 + Introduction</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN668" name="AEN668">3.1.1 + Upgrade Overview</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN742" name="AEN742">3.2 + Procedure</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN745" name="AEN745">3.2.1 + Backup</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN748" name="AEN748">3.2.2 + Mount Filesystems</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN753" name="AEN753">3.2.3 + Select Distributions</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 + After Installation</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN763" name="AEN763">3.3 + Upgrading from Source Code</a></h2> + + <p>Those interested in an upgrade method that allows more + flexibility and sophistication should take a look at <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html" + target="_top">The Cutting Edge</a> in the FreeBSD + Handbook. This procedure involves rebuilding all of + FreeBSD from source code. It requires reliable network + connectivity, extra disk space, and time, but has + advantages for networks and other more complex + installations. This is roughly the same procedure as is + used for track the -STABLE or -CURRENT development + branches.</p> + + <p><tt class="FILENAME">/usr/src/UPDATING</tt> contains + important information on updating a FreeBSD system from + source code. It lists various issues resulting from + changes in FreeBSD that may affect an upgrade.</p> + + <p></p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 + Troubleshooting</a></h1> + + <div class="SECT2"> + <h2 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 + Repairing an Existing FreeBSD Installation</a></h2> + + <p>FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + <tt class="FILENAME">fixit.flp</tt> image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.</p> + + <p>To invoke fixit, simply boot the <tt + class="FILENAME">kern.flp</tt> floppy, choose the + ``Fixit'' item and insert the fixit floppy or CDROM when + asked. You will then be placed into a shell with a wide + variety of commands available (in the <tt + class="FILENAME">/stand</tt> and <tt + class="FILENAME">/mnt2/stand</tt> directories) for + checking, repairing and examining filesystems and their + contents. Some UNIX administration experience <span + class="emphasis"><i class="EMPHASIS">is</i></span> + required to use the fixit option.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN784" name="AEN784">4.2 Common + Installation Problems for i386 Architecture + Users</a></h2> + + <div class="QANDASET"> + <dl> + <dt>4.2.1. <a href="#Q4.2.1.">My system hangs while + probing hardware during boot, or it behaves strangely + during install, or the floppy drive isn't + probed.</a></dt> + + <dt>4.2.2. <a href="#Q4.2.2.">My legacy ISA device + used to be recognized in previous versions of + FreeBSD, but now it's not. What happened?</a></dt> + + <dt>4.2.3. <a href="#Q4.2.3.">I go to boot from the + hard disk for the first time after installing + FreeBSD, the kernel loads and probes my hardware, but + stops with messages like:</a></dt> + + <dt>4.2.4. <a href="#Q4.2.4.">I go to boot from the + hard disk for the first time after installing + FreeBSD, but the Boot Manager prompt just prints <tt + class="LITERAL">F?</tt> at the boot menu each time + but the boot won't go any further.</a></dt> + + <dt>4.2.5. <a href="#Q4.2.5.">The <span + class="CITEREFENTRY"><span + class="REFENTRYTITLE">mcd</span>(4)</span> driver + keeps thinking that it has found a device and this + stops my Intel EtherExpress card from + working.</a></dt> + + <dt>4.2.6. <a href="#Q4.2.6.">The system finds my + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ed</span>(4)</span> network + card, but I keep getting device timeout + errors.</a></dt> + + <dt>4.2.7. <a href="#Q4.2.7.">I booted the install + floppy on my IBM ThinkPad (tm) laptop, and the + keyboard is all messed up.</a></dt> + + <dt>4.2.8. <a href="#Q4.2.8.">My system can not find + my Intel EtherExpress 16 card.</a></dt> + + <dt>4.2.9. <a href="#Q4.2.9.">When installing on an + EISA HP Netserver, my on-board AIC-7xxx SCSI + controller isn't detected.</a></dt> + + <dt>4.2.10. <a href="#Q4.2.10.">I have a Panasonic + AL-N1 or Rios Chandler Pentium machine and I find + that the system hangs before ever getting into the + installation now.</a></dt> + + <dt>4.2.11. <a href="#Q4.2.11.">I have this CMD640 + IDE controller that is said to be broken.</a></dt> + + <dt>4.2.12. <a href="#Q4.2.12.">On a Compaq Aero + notebook, I get the message ``No floppy devices + found! Please check ...'' when trying to install from + floppy.</a></dt> + + <dt>4.2.13. <a href="#Q4.2.13.">When installing on a + Dell Poweredge XE, Dell proprietary RAID controller + DSA (Dell SCSI Array) isn't recognized.</a></dt> + + <dt>4.2.14. <a href="#Q4.2.14.">I have an IBM + EtherJet PCI card, it is detected by the <span + class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span> driver + correctly, but the lights on the card don't come on + and it doesn't connect to the network.</a></dt> + + <dt>4.2.15. <a href="#Q4.2.15.">When I configure the + network during installation on an IBM Netfinity 3500, + the system freezes.</a></dt> + + <dt>4.2.16. <a href="#Q4.2.16.">When I install onto a + drive managed by a Mylex PCI RAID controller, the + system fails to boot (eg. with a <tt + class="LITERAL">read error</tt> message).</a></dt> + </dl> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.1." name="Q4.2.1."></a><b>4.2.1.</b> + My system hangs while probing hardware during boot, + or it behaves strangely during install, or the + floppy drive isn't probed.</p> + </div> + + <div class="ANSWER"> + <p><b></b>FreeBSD 5.0 and above makes extensive use + of the system ACPI service on the i386 platform to + aid in system configuration if it's detected during + boot. Unfortunately, some bugs still exist in both + the ACPI driver and within system motherboards and + BIOS. The use of ACPI can be disabled by setting + the ``hint.acpi.0.disabled'' hint in the third + stage boot loader:</p> +<pre class="SCREEN"> +set hint.acpi.0.disabled="1" +</pre> + + <p>This is reset each time the system is booted, so + it is necessary to add <tt + class="LITERAL">hint.acpi.0.disabled="1"</tt> to + the file <tt + class="FILENAME">/boot/loader.conf</tt>. More + information about the boot loader can be found in + the FreeBSD Handbook.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.2." name="Q4.2.2."></a><b>4.2.2.</b> + My legacy ISA device used to be recognized in + previous versions of FreeBSD, but now it's not. + What happened?</p> + </div> + + <div class="ANSWER"> + <p><b></b>Some device drivers, like matcd, were + removed over time due to lack of maintainership or + other reasons. Others still exist but are disabled + because of their intrusive hardware probe routines. + The following ISA device drivers fall into this + category and can re-enabled from the third stage + boot loader: aha, ahv, aic, bt, ed, cs, sn, ie, fe, + le, and lnc. To do this, stop the loader during + it's 10 second countdown and enter the following at + the prompt:</p> +<pre class="SCREEN"> +unset hint.foo.0.disabled +</pre> + + <p>where <tt class="REPLACEABLE"><i>foo</i></tt> is + the name of the driver to re-enable. This can be + set permanently by editing the file <tt + class="FILENAME">/boot/device.hints</tt> and + removing the appropriate ``disabled'' entry.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.3." name="Q4.2.3."></a><b>4.2.3.</b> + I go to boot from the hard disk for the first time + after installing FreeBSD, the kernel loads and + probes my hardware, but stops with messages + like:</p> +<pre class="SCREEN"> +changing root device to ad1s1a panic: cannot mount root +</pre> + + <p>What is wrong? What can I do?</p> + + <p>What is this <tt + class="LITERAL">bios_drive:interface(unit,partition)kernel_name</tt> + thing that is displayed with the boot help?</p> + </div> + + <div class="ANSWER"> + <p><b></b>There is a longstanding problem in the + case where the boot disk is not the first disk in + the system. The BIOS uses a different numbering + scheme to FreeBSD, and working out which numbers + correspond to which is difficult to get right.</p> + + <p>In the case where the boot disk is not the first + disk in the system, FreeBSD can need some help + finding it. There are two common situations here, + and in both of these cases, you need to tell + FreeBSD where the root filesystem is. You do this + by specifying the BIOS disk number, the disk type + and the FreeBSD disk number for that type.</p> + + <p>The first situation is where you have two IDE + disks, each configured as the master on their + respective IDE busses, and wish to boot FreeBSD + from the second disk. The BIOS sees these as disk 0 + and disk 1, while FreeBSD sees them as <tt + class="DEVICENAME">ad0</tt> and <tt + class="DEVICENAME">ad2</tt>.</p> + + <p>FreeBSD is on BIOS disk 1, of type <tt + class="LITERAL">ad</tt> and the FreeBSD disk number + is 2, so you would say:</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>1:ad(2,a)kernel</b></tt> +</pre> + + <p>Note that if you have a slave on the primary + bus, the above is not necessary (and is effectively + wrong).</p> + + <p>The second situation involves booting from a + SCSI disk when you have one or more IDE disks in + the system. In this case, the FreeBSD disk number + is lower than the BIOS disk number. If you have two + IDE disks as well as the SCSI disk, the SCSI disk + is BIOS disk 2, type <tt class="LITERAL">da</tt> + and FreeBSD disk number 0, so you would say:</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>2:da(0,a)kernel</b></tt> +</pre> + + <p>To tell FreeBSD that you want to boot from BIOS + disk 2, which is the first SCSI disk in the system. + If you only had one IDE disk, you would use '1:' + instead.</p> + + <p>Once you have determined the correct values to + use, you can put the command exactly as you would + have typed it in the <tt + class="FILENAME">/boot.config</tt> file using a + standard text editor. Unless instructed otherwise, + FreeBSD will use the contents of this file as the + default response to the <tt + class="LITERAL">boot:</tt> prompt.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.4." name="Q4.2.4."></a><b>4.2.4.</b> + I go to boot from the hard disk for the first time + after installing FreeBSD, but the Boot Manager + prompt just prints <tt class="LITERAL">F?</tt> at + the boot menu each time but the boot won't go any + further.</p> + </div> + + <div class="ANSWER"> + <p><b></b>The hard disk geometry was set + incorrectly in the Partition editor when you + installed FreeBSD. Go back into the partition + editor and specify the actual geometry of your hard + disk. You must reinstall FreeBSD again from the + beginning with the correct geometry.</p> + + <p>If you are failing entirely in figuring out the + correct geometry for your machine, here's a tip: + Install a small DOS partition at the beginning of + the disk and install FreeBSD after that. The + install program will see the DOS partition and try + to infer the correct geometry from it, which + usually works.</p> + + <p>The following tip is no longer recommended, but + is left here for reference:</p> + <a id="AEN841" name="AEN841"></a> + + <blockquote class="BLOCKQUOTE"> + <p>If you are setting up a truly dedicated + FreeBSD server or workstation where you don't + care for (future) compatibility with DOS, Linux + or another operating system, you've also got the + option to use the entire disk (`A' in the + partition editor), selecting the non-standard + option where FreeBSD occupies the entire disk + from the very first to the very last sector. This + will leave all geometry considerations aside, but + is somewhat limiting unless you're never going to + run anything other than FreeBSD on a disk.</p> + </blockquote> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.5." name="Q4.2.5."></a><b>4.2.5.</b> + The <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mcd</span>(4)</span> driver + keeps thinking that it has found a device and this + stops my Intel EtherExpress card from working.</p> + </div> + + <div class="ANSWER"> + <p><b></b>Use the UserConfig utility (see <tt + class="FILENAME">HARDWARE.TXT</tt>) and disable the + probing of the <tt class="DEVICENAME">mcd0</tt> and + <tt class="DEVICENAME">mcd1</tt> devices. Generally + speaking, you should only leave the devices that + you will be using enabled in your kernel.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.6." name="Q4.2.6."></a><b>4.2.6.</b> + The system finds my <span + class="CITEREFENTRY"><span + class="REFENTRYTITLE">ed</span>(4)</span> network + card, but I keep getting device timeout errors.</p> + </div> + + <div class="ANSWER"> + <p><b></b>Your card is probably on a different IRQ + from what is specified in the kernel configuration. + The ed driver does not use the `soft' configuration + by default (values entered using EZSETUP in DOS), + but it will use the software configuration if you + specify <tt class="LITERAL">?</tt> in the IRQ field + of your kernel config file.</p> + + <p>Either move the jumper on the card to a hard + configuration setting (altering the kernel settings + if necessary), or specify the IRQ as <tt + class="LITERAL">-1</tt> in UserConfig or <tt + class="LITERAL">?</tt> in your kernel config file. + This will tell the kernel to use the soft + configuration.</p> + + <p>Another possibility is that your card is at IRQ + 9, which is shared by IRQ 2 and frequently a cause + of problems (especially when you have a VGA card + using IRQ 2!). You should not use IRQ 2 or 9 if at + all possible.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.7." name="Q4.2.7."></a><b>4.2.7.</b> + I booted the install floppy on my IBM ThinkPad (tm) + laptop, and the keyboard is all messed up.</p> + </div> + + <div class="ANSWER"> + <p><b></b>Older IBM laptops use a non-standard + keyboard controller, so you must tell the keyboard + driver (atkbd0) to go into a special mode which + works on the ThinkPads. Change the atkbd0 'Flags' + to 0x4 in UserConfig and it should work fine. (Look + in the Input Menu for 'Keyboard'.)</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.8." name="Q4.2.8."></a><b>4.2.8.</b> + My system can not find my Intel EtherExpress 16 + card.</p> + </div> + + <div class="ANSWER"> + <p><b></b>You must set your Intel EtherExpress 16 + card to be memory mapped at address 0xD0000, and + set the amount of mapped memory to 32K using the + Intel supplied <tt + class="FILENAME">softset.exe</tt> program.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.9." name="Q4.2.9."></a><b>4.2.9.</b> + When installing on an EISA HP Netserver, my + on-board AIC-7xxx SCSI controller isn't + detected.</p> + </div> + + <div class="ANSWER"> + <p><b></b>This is a known problem, and will + hopefully be fixed in the future. In order to get + your system installed at all, boot with the <tt + class="OPTION">-c</tt> option into UserConfig, but + <span class="emphasis"><i + class="EMPHASIS">don't</i></span> use the pretty + visual mode but the plain old CLI mode. Type:</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>eisa 12</b></tt> +<tt class="USERINPUT"><b>quit</b></tt> +</pre> + + <p>at the prompt. (Instead of `quit', you might + also type `visual', and continue the rest of the + configuration session in visual mode.) While it's + recommended to compile a custom kernel, dset now + also understands to save this value.</p> + + <p>Refer to the FAQ topic 3.16 for an explanation + of the problem, and for how to continue. Remember + that you can find the FAQ on your local system in + /usr/share/doc/FAQ, provided you have installed the + `doc' distribution.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.10." + name="Q4.2.10."></a><b>4.2.10.</b> I have a + Panasonic AL-N1 or Rios Chandler Pentium machine + and I find that the system hangs before ever + getting into the installation now.</p> + </div> + + <div class="ANSWER"> + <p><b></b>Your machine doesn't like the new <tt + class="LITERAL">i586_copyout</tt> and <tt + class="LITERAL">i586_copyin</tt> code for some + reason. To disable this, boot the installation boot + floppy and when it comes to the very first menu + (the choice to drop into kernel UserConfig mode or + not) choose the command-line interface (``expert + mode'') version and type the following at it:</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>flags npx0 1</b></tt> +</pre> + + <p>Then proceed normally to boot. This will be + saved into your kernel, so you only need to do it + once.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.11." + name="Q4.2.11."></a><b>4.2.11.</b> I have this + CMD640 IDE controller that is said to be + broken.</p> + </div> + + <div class="ANSWER"> + <p><b></b>FreeBSD does not support this + controller.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.12." + name="Q4.2.12."></a><b>4.2.12.</b> On a Compaq Aero + notebook, I get the message ``No floppy devices + found! Please check ...'' when trying to install + from floppy.</p> + </div> + + <div class="ANSWER"> + <p><b></b>With Compaq being always a little + different from other systems, they do not announce + their floppy drive in the CMOS RAM of an Aero + notebook. Therefore, the floppy disk driver assumes + there is no drive configured. Go to the UserConfig + screen, and set the Flags value of the fdc0 device + to 0x1. This pretends the existence of the first + floppy drive (as a 1.44 MB drive) to the driver + without asking the CMOS at all.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.13." + name="Q4.2.13."></a><b>4.2.13.</b> When installing + on a Dell Poweredge XE, Dell proprietary RAID + controller DSA (Dell SCSI Array) isn't + recognized.</p> + </div> + + <div class="ANSWER"> + <p><b></b>Configure the DSA to use AHA-1540 + emulation using EISA configuration utility. After + that FreeBSD detects the DSA as an Adaptec AHA-1540 + SCSI controller, with irq 11 and port 340. Under + emulation mode system will use DSA RAID disks, but + you cannot use DSA-specific features such as + watching RAID health.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.14." + name="Q4.2.14."></a><b>4.2.14.</b> I have an IBM + EtherJet PCI card, it is detected by the <span + class="CITEREFENTRY"><span + class="REFENTRYTITLE">fxp</span>(4)</span> driver + correctly, but the lights on the card don't come on + and it doesn't connect to the network.</p> + </div> + + <div class="ANSWER"> + <p><b></b>We don't understand why this happens. + Neither do IBM (we asked them). The card is a + standard Intel EtherExpress Pro/100 with an IBM + label on it, and these cards normally work just + fine. You may see these symptoms only in some IBM + Netfinity servers. The only solution is to install + a different Ethernet adapter.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.15." + name="Q4.2.15."></a><b>4.2.15.</b> When I configure + the network during installation on an IBM Netfinity + 3500, the system freezes.</p> + </div> + + <div class="ANSWER"> + <p><b></b>There is a problem with the onboard + Ethernet in the Netfinity 3500 which we have not + been able to identify at this time. It may be + related to the SMP features of the system being + misconfigured. You will have to install another + Ethernet adapter and avoid attempting to configure + the onboard adapter at any time.</p> + </div> + </div> + + <div class="QANDAENTRY"> + <div class="QUESTION"> + <p><a id="Q4.2.16." + name="Q4.2.16."></a><b>4.2.16.</b> When I install + onto a drive managed by a Mylex PCI RAID + controller, the system fails to boot (eg. with a + <tt class="LITERAL">read error</tt> message).</p> + </div> + + <div class="ANSWER"> + <p><b></b>There is a bug in the Mylex driver which + results in it ignoring the ``8GB'' geometry mode + setting in the BIOS. Use the 2GB mode instead.</p> + </div> + </div> + </div> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/installation-ia64.html b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-ia64.html new file mode 100644 index 0000000000..0d2db03136 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-ia64.html @@ -0,0 +1,1188 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/ia64 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/ia64 + 5.1-RELEASE Installation Instructions</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <blockquote class="ABSTRACT"> + <div class="ABSTRACT"> + <a id="AEN11" name="AEN11"></a> + + <p>This article gives some brief instructions on + installing FreeBSD/ia64 5.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 /> + + <h1 class="SECT1"><a id="INSTALL" name="INSTALL">1 + Installing FreeBSD</a></h1> + + <p>This section documents the process of installing a new + distribution of FreeBSD. These instructions pay particular + emphasis to the process of obtaining the FreeBSD + 5.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 /> + + <h2 class="SECT2"><a id="GETTING-STARTED" + name="GETTING-STARTED">1.1 Getting Started</a></h2> + + <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 /> + + <h2 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware + Requirements</a></h2> + + <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 /> + + <h2 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 + Floppy Disk Image Instructions</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="START-INSTALLATION" + name="START-INSTALLATION">1.4 Installing FreeBSD from + CDROM or the Internet</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN209" name="AEN209">1.5 Detail + on various installation types</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN248" name="AEN248">1.5.1 + Installing from a Network CDROM</a></h3> + + <p>If you simply wish to install from a local CDROM + drive then see <a href="#START-INSTALLATION">Section + 1.4</a>. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:</p> + + <ul> + <li> + <p>If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+5.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+5.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 /> + + <h3 class="SECT3"><a id="AEN280" name="AEN280">1.5.2 + Installing from Floppies</a></h3> + + <p>If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.</p> + + <p>First, make your boot floppies as described in <a + href="#FLOPPIES">Section 1.3</a>.</p> + + <p>Second, peruse <a href="#LAYOUT">Section 2</a> and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.</p> + + <p>Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the <tt + class="FILENAME">bin</tt> (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies <span class="emphasis"><i + class="EMPHASIS">must</i></span> be formatted using the + MS-DOS <tt class="FILENAME">FORMAT</tt> command. If + you're using Windows, use the Windows File Manager + format command.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Frequently, floppy disks come + ``factory preformatted''. While convenient, many + problems reported by users in the past have + resulted from the use of improperly formatted + media. Re-format them yourself, just to make + sure.</p> + </blockquote> + </div> + + <p>If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+5.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+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>fdformat -f 1440 fd0.1440</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>disklabel -w -r fd0.1440 floppy3</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</b></tt> +</pre> + + <p>After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: <tt + class="FILENAME">a:\bin\bin.inf</tt>, <tt + class="FILENAME">a:\bin\bin.aa</tt>, <tt + class="FILENAME">a:\bin\bin.ab</tt>, ...</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> The <tt + class="FILENAME">bin.inf</tt> file also needs to go + on the first floppy of the <tt + class="FILENAME">bin</tt> set since it is read by + the installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">distname.inf</tt> file <span + class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first + floppy of each distribution set. This is also + covered in <tt + class="FILENAME">README.TXT</tt>.</p> + </blockquote> + </div> + + <p>Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN350" name="AEN350">1.5.4 + Installing from QIC/SCSI Tape</a></h3> + + <p>When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt class="USERINPUT"><b>cd <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>tar cvf /dev/rsa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt +class="REPLACEABLE"><i>dist2</i></tt></b></tt> +</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 /> + + <h3 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 + Installing over a Network using FTP or NFS</a></h3> + + <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 /> + + <h4 class="SECT4"><a id="AEN375" + name="AEN375">1.5.5.1 Serial Port</a></h4> + + <p>SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.</p> + + <p>If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.</p> + + <p>You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.</p> + </div> + + <div class="SECT4"> + <hr /> + + <h4 class="SECT4"><a id="AEN381" + name="AEN381">1.5.5.2 Parallel Port</a></h4> + + <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 <tt + class="OPTION">link0</tt> 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 /> + + <h4 class="SECT4"><a id="AEN392" + name="AEN392">1.5.5.3 Ethernet</a></h4> + + <p>FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see <tt + class="FILENAME">HARDWARE.TXT</tt> in the + Documentation menu on the boot floppy or the top + level directory of the CDROM). If you are using one + of the supported PCMCIA Ethernet cards, also be sure + that it's plugged in <span class="emphasis"><i + class="EMPHASIS">before</i></span> the laptop is + powered on. FreeBSD does not, unfortunately, + currently support ``hot insertion'' of PCMCIA cards + during installation.</p> + + <p>You will also need to know your IP address on the + network, the <tt class="OPTION">netmask</tt> 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 /> + + <h4 class="SECT4"><a id="AEN403" + name="AEN403">1.5.5.4 NFS installation tips</a></h4> + + <p>NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.</p> + + <p>If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.</p> + + <p>If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.</p> + + <p>In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on <tt + class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, + then <tt class="HOSTID">wiggy</tt> will have to allow + the direct mounting of <tt + class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not + just <tt class="FILENAME">/usr</tt> or <tt + class="FILENAME">/usr/archive/stuff</tt>.</p> + + <p>In FreeBSD's <tt + class="FILENAME">/etc/exports</tt> file this is + controlled by the <tt class="OPTION">-alldirs</tt> + 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 /> + + <h4 class="SECT4"><a id="AEN420" + name="AEN420">1.5.5.5 FTP Installation tips</a></h4> + + <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"> +<tt class="USERINPUT"><b>ftp://foo.bar.com:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</b></tt> +</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 /> + + <h2 class="SECT2"><a id="AEN463" name="AEN463">1.6 + Question and Answer Section for IA-64 Architecture + Users</a></h2> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 + Distribution Format</a></h1> + + <p>A typical FreeBSD distribution directory looks something + like this (exact details may vary depending on version, + architecture, and other factors):</p> +<pre class="SCREEN"> +ERRATA.HTM README.TXT compat1x dict kernel +ERRATA.TXT RELNOTES.HTM compat20 doc manpages +HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages +HARDWARE.TXT base compat22 filename.txt ports +INSTALL.HTM boot compat3x floppies proflibs +INSTALL.TXT catpages compat4x games src +README.HTM cdrom.inf crypto info tools +</pre> + + <p>If you want to do a CDROM, FTP or NFS installation from + this distribution directory, all you need to do is make the + 1.44MB boot floppies from the floppies directory (see <a + href="#FLOPPIES">Section 1.3</a> for instructions on how to + do this), boot them and follow the instructions. The rest + of the data needed during the installation will be obtained + automatically based on your selections. If you've never + installed FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.</p> + + <p>If you're trying to do some other type of installation + or are merely curious about how a distribution is + organized, what follows is a more thorough description of + some of these items in more detail:</p> + + <ol type="1"> + <li> + <p>The <tt class="FILENAME">*.TXT</tt> and <tt + class="FILENAME">*.HTM</tt> files contain documentation + (for example, this document is contained in both <tt + class="FILENAME">INSTALL.TXT</tt> and <tt + class="FILENAME">INSTALL.HTM</tt>) and should be read + before starting an installation. The <tt + class="FILENAME">*.TXT</tt> files are plain text, while + the <tt class="FILENAME">*.HTM</tt> files are HTML + files that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.</p> + </li> + + <li> + <p><tt class="FILENAME">docbook.css</tt> is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.</p> + </li> + + <li> + <p>The <tt class="FILENAME">base</tt>, <tt + class="FILENAME">catpages</tt>, <tt + class="FILENAME">crypto</tt>, <tt + class="FILENAME">dict</tt>, <tt + class="FILENAME">doc</tt>, <tt + class="FILENAME">games</tt>, <tt + class="FILENAME">info</tt>, <tt + class="FILENAME">manpages</tt>, <tt + class="FILENAME">proflibs</tt>, and <tt + class="FILENAME">src</tt> directories contain the + primary distribution components of FreeBSD itself and + are split into smaller files for easy packing onto + floppies (should that be necessary).</p> + </li> + + <li> + <p>The <tt class="FILENAME">compat1x</tt>, <tt + class="FILENAME">compat20</tt>, <tt + class="FILENAME">compat21</tt>, <tt + class="FILENAME">compat22</tt>, <tt + class="FILENAME">compat3x</tt>, and <tt + class="FILENAME">compat4x</tt> directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their <tt class="FILENAME">install.sh</tt> scripts.</p> + </li> + + <li> + <p>The <tt class="FILENAME">floppies/</tt> subdirectory + contains the floppy installation images; further + information on using them can be found in <a + href="#FLOPPIES">Section 1.3</a>.</p> + </li> + + <li> + <p>The <tt class="FILENAME">packages</tt> and <tt + class="FILENAME">ports</tt> directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt><tt +class="USERINPUT"><b>/stand/sysinstall configPackages</b></tt> +</pre> + + <p>Packages can also be installed by feeding individual + filenames in <tt class="FILENAME">packages</tt>/ to the + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.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 100MB unpacked. More + information on the ports collection may be obtained + from <a href="http://www.FreeBSD.org/ports/" + target="_top">http://www.FreeBSD.org/ports/</a> or + locally from <tt + class="FILENAME">/usr/share/doc/handbook</tt> if you've + installed the <tt class="FILENAME">doc</tt> + distribution.</p> + </li> + + <li> + <p>Last of all, the <tt class="FILENAME">tools</tt> + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.</p> + </li> + </ol> + <br /> + <br /> + + <p>A typical distribution directory (for example, the <tt + class="FILENAME">info</tt> distribution) looks like this + internally:</p> +<pre class="SCREEN"> +CHECKSUM.MD5 info.ab info.ad info.inf install.sh +info.aa info.ac info.ae info.mtree +</pre> + + <p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains + MD5 signatures for each file, should data corruption be + suspected, and is purely for reference. It is not used by + the actual installation and does not need to be copied with + the rest of the distribution files. The <tt + class="FILENAME">info.a*</tt> files are split, gzip'd tar + files, the contents of which can be viewed by doing:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cat info.a* | tar tvzf -</b></tt> +</pre> + + <p>During installation, they are automatically concatenated + and extracted by the installation procedure.</p> + + <p>The <tt class="FILENAME">info.inf</tt> file is also + necessary since it is read by the installation program in + order to figure out how many pieces to look for when + fetching and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">.inf</tt> file <span class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first floppy of + each distribution set!</p> + + <p>The <tt class="FILENAME">info.mtree</tt> file is another + non-essential file which is provided for user reference. It + contains the MD5 signatures of the <span + class="emphasis"><i class="EMPHASIS">unpacked</i></span> + distribution files and can be later used with the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&sektion=8&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cd /cdrom/info</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>sh install.sh</b></tt> +</pre> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 + Upgrading FreeBSD</a></h1> + + <p>These instructions describe a procedure for doing a + binary upgrade from an older version of FreeBSD.</p> + + <div class="WARNING"> + <blockquote class="WARNING"> + <p><b>Warning:</b> While the FreeBSD upgrade procedure + does its best to safeguard against accidental loss of + data, it is still more than possible to <span + class="emphasis"><i class="EMPHASIS">wipe out your + entire disk</i></span> with this installation! Please + do not accept the final confirmation request unless you + have adequately backed up any important data files.</p> + </blockquote> + </div> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> These notes assume that you are + using the version of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.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+5.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+5.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 + 5.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></p> + + <p>These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.</p> + </blockquote> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN664" name="AEN664">3.1 + Introduction</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN668" name="AEN668">3.1.1 + Upgrade Overview</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN742" name="AEN742">3.2 + Procedure</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN745" name="AEN745">3.2.1 + Backup</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN748" name="AEN748">3.2.2 + Mount Filesystems</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN753" name="AEN753">3.2.3 + Select Distributions</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 + After Installation</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN763" name="AEN763">3.3 + Upgrading from Source Code</a></h2> + + <p>Those interested in an upgrade method that allows more + flexibility and sophistication should take a look at <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html" + target="_top">The Cutting Edge</a> in the FreeBSD + Handbook. This procedure involves rebuilding all of + FreeBSD from source code. It requires reliable network + connectivity, extra disk space, and time, but has + advantages for networks and other more complex + installations. This is roughly the same procedure as is + used for track the -STABLE or -CURRENT development + branches.</p> + + <p><tt class="FILENAME">/usr/src/UPDATING</tt> contains + important information on updating a FreeBSD system from + source code. It lists various issues resulting from + changes in FreeBSD that may affect an upgrade.</p> + + <p></p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 + Troubleshooting</a></h1> + + <div class="SECT2"> + <h2 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 + Repairing an Existing FreeBSD Installation</a></h2> + + <p>FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + <tt class="FILENAME">fixit.flp</tt> image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.</p> + + <p>To invoke fixit, simply boot the <tt + class="FILENAME">kern.flp</tt> floppy, choose the + ``Fixit'' item and insert the fixit floppy or CDROM when + asked. You will then be placed into a shell with a wide + variety of commands available (in the <tt + class="FILENAME">/stand</tt> and <tt + class="FILENAME">/mnt2/stand</tt> directories) for + checking, repairing and examining filesystems and their + contents. Some UNIX administration experience <span + class="emphasis"><i class="EMPHASIS">is</i></span> + required to use the fixit option.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN784" name="AEN784">4.2 Common + Installation Problems for IA-64 Architecture + Users</a></h2> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/installation-pc98.html b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-pc98.html new file mode 100644 index 0000000000..eb765c5f91 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-pc98.html @@ -0,0 +1,1346 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/pc98 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/pc98 + 5.1-RELEASE Installation Instructions</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <blockquote class="ABSTRACT"> + <div class="ABSTRACT"> + <a id="AEN11" name="AEN11"></a> + + <p>This article gives some brief instructions on + installing FreeBSD/pc98 5.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 /> + + <h1 class="SECT1"><a id="INSTALL" name="INSTALL">1 + Installing FreeBSD</a></h1> + + <p>This section documents the process of installing a new + distribution of FreeBSD. These instructions pay particular + emphasis to the process of obtaining the FreeBSD + 5.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 /> + + <h2 class="SECT2"><a id="GETTING-STARTED" + name="GETTING-STARTED">1.1 Getting Started</a></h2> + + <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 /> + + <h2 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware + Requirements</a></h2> + + <p>FreeBSD for the NEC PC-98x1 requires a 386 or better + processor to run (sorry, there is no support for 286 + processors) and at least 5 megs of RAM to install and 4 + megs of RAM to run. You will need at least 100MB of free + hard drive space for the most minimal installation. See + below for ways of shrinking existing DOS partitions in + order to install FreeBSD.</p> + + <p>If you are not familiar with configuring hardware for + FreeBSD, you should be sure to read the <tt + class="FILENAME">HARDWARE.TXT</tt> file; it contains + important information on what hardware is supported by + FreeBSD.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 + Floppy Disk Image Instructions</a></h2> + + <p>Depending on how you choose to install FreeBSD, you + may need to create a set of floppy disks (usually two) to + begin the installation process. This section briefly + describes how to create these disks, either from a CDROM + installation or from the Internet. Note that in the + common case of installing FreeBSD from CDROM, on a + machine that supports bootable CDROMs, the steps outlined + in this section will not be needed and can be + skipped.</p> + + <p>For a normal CDROM or network installation, all you + need to copy onto actual floppies from the <tt + class="FILENAME">floppies/</tt> directory are the <tt + class="FILENAME">kern.flp</tt> and <tt + class="FILENAME">mfsroot.flp</tt> images (for 1.44MB + floppies) or <tt class="FILENAME">kern-small.flp</tt> and + <tt class="FILENAME">mfsroot-small.flp</tt> images (for + 1.2MB floppies).</p> + + <p>Getting these images over the network is easy. Simply + fetch the <tt class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/kern.flp</tt>, <tt + class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/mfsroot.flp</tt>, and <tt + class="REPLACEABLE"><i>release</i></tt><tt + class="FILENAME">/floppies/drivers.flp</tt> files from <a + href="ftp://ftp.FreeBSD.org/" + target="_top">ftp://ftp.FreeBSD.org/</a> or one of the + many mirrors listed at <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html" + target="_top">FTP Sites</a> section of the Handbook, or + on the <a href="http://mirrorlist.FreeBSD.org/" + target="_top">http://mirrorlist.FreeBSD.org/</a> Web + pages.</p> + + <p>Get two blank, freshly formatted floppies and image + copy <tt class="FILENAME">kern.flp</tt> onto one and <tt + class="FILENAME">mfsroot.flp</tt> onto the other. These + images are <span class="emphasis"><i + class="EMPHASIS">not</i></span> DOS files. You cannot + simply copy them to a DOS or UFS floppy as regular files, + you need to ``image'' copy them to the floppy with <tt + class="FILENAME">rawrite.exe</tt> under DOS (see the <tt + class="FILENAME">tools</tt> directory on your CDROM or + FreeBSD FTP mirror) or the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dd&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dd</span>(1)</span></a> command in + UNIX.</p> + + <p>For example, to create the kernel floppy image from + DOS, you'd do something like this:</p> +<pre class="SCREEN"> +<tt class="PROMPT">A></tt> <tt +class="USERINPUT"><b>rawrite</b></tt> +</pre> + + <p>Assuming that you'd copied <tt + class="FILENAME">rawrite.exe</tt> and <tt + class="FILENAME">kern.flp</tt> into a directory + somewhere. You would do the same for <tt + class="FILENAME">mfsroot.flp</tt>, of course.</p> + + <p>If you're creating the boot floppy from a UNIX + machine, you may find that:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>dd if=floppies/kern.flp of=/dev/rfd0.1440</b></tt> +</pre> + + <p>or</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>dd if=floppies/kern-small.flp of=/dev/rfd0.1200</b></tt> +</pre> + + <p>work well, depending on your hardware and operating + system environment (different versions of UNIX have + different names for the floppy drive).</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="START-INSTALLATION" + name="START-INSTALLATION">1.4 Installing FreeBSD from + CDROM or the Internet</a></h2> + + <p>The easiest type of installation is from CDROM. If you + have a supported CDROM drive and a FreeBSD installation + CDROM, there is a next way of starting the installation + from it:</p> + + <ul> + <li> + <p>Build a set of FreeBSD boot floppies from the <tt + class="FILENAME">floppies/</tt> directory in every + FreeBSD distribution. Read <a + href="#FLOPPIES">Section 1.3</a> for more information + on creating the bootable floppies under different + operating systems. Then you simply boot from the + first floppy and you should soon be in the FreeBSD + installation.</p> + </li> + </ul> + <br /> + <br /> + + <p>If you don't have a CDROM and would like to simply + install over the net using PPP, SLIP or a dedicated + connection. You should start the installation by building + a set of FreeBSD boot floppies from the files <tt + class="FILENAME">floppies/kern.flp</tt> and <tt + class="FILENAME">floppies/mfsroot.flp</tt> using the + instructions found in <a href="#FLOPPIES">Section + 1.3</a>. Restart your computer using the <tt + class="FILENAME">kern.flp</tt> disk; when prompted, + insert the <tt class="FILENAME">mfsroot.flp</tt> disk. + Then, please go to <a href="#FTPNFS">Section 1.5.5</a> + for additional tips on installing via FTP or NFS.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN209" name="AEN209">1.5 Detail + on various installation types</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN248" name="AEN248">1.5.1 + Installing from a Network CDROM</a></h3> + + <p>If you simply wish to install from a local CDROM + drive then see <a href="#START-INSTALLATION">Section + 1.4</a>. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:</p> + + <ul> + <li> + <p>If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+5.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+5.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 /> + + <h3 class="SECT3"><a id="AEN280" name="AEN280">1.5.2 + Installing from Floppies</a></h3> + + <p>If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.</p> + + <p>First, make your boot floppies as described in <a + href="#FLOPPIES">Section 1.3</a>.</p> + + <p>Second, peruse <a href="#LAYOUT">Section 2</a> and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.</p> + + <p>Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the <tt + class="FILENAME">bin</tt> (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies <span class="emphasis"><i + class="EMPHASIS">must</i></span> be formatted using the + MS-DOS <tt class="FILENAME">FORMAT</tt> command. If + you're using Windows, use the Windows File Manager + format command.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Frequently, floppy disks come + ``factory preformatted''. While convenient, many + problems reported by users in the past have + resulted from the use of improperly formatted + media. Re-format them yourself, just to make + sure.</p> + </blockquote> + </div> + + <p>If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+5.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+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>fdformat -f 1440 fd0.1440</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>disklabel -w -r fd0.1440 floppy3</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</b></tt> +</pre> + + <p>After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: <tt + class="FILENAME">a:\bin\bin.inf</tt>, <tt + class="FILENAME">a:\bin\bin.aa</tt>, <tt + class="FILENAME">a:\bin\bin.ab</tt>, ...</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> The <tt + class="FILENAME">bin.inf</tt> file also needs to go + on the first floppy of the <tt + class="FILENAME">bin</tt> set since it is read by + the installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">distname.inf</tt> file <span + class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first + floppy of each distribution set. This is also + covered in <tt + class="FILENAME">README.TXT</tt>.</p> + </blockquote> + </div> + + <p>Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN322" name="AEN322">1.5.3 + Installing from a DOS partition</a></h3> + + <p>To prepare for installation from an MS-DOS partition + you should simply copy the files from the distribution + into a directory called <tt + class="FILENAME">FREEBSD</tt> on the Primary DOS + partition (<tt class="DEVICENAME">A:</tt>). For + example, to do a minimal installation of FreeBSD from + DOS using files copied from the CDROM, you might do + something like this:</p> +<pre class="SCREEN"> +<tt class="PROMPT">A:\></tt> <tt +class="USERINPUT"><b>MD A:\FREEBSD</b></tt> +<tt class="PROMPT">A:\></tt> <tt +class="USERINPUT"><b>XCOPY /S E:\BASE A:\FREEBSD\BASE</b></tt> +</pre> + + <p>Assuming that <tt class="DEVICENAME">E:</tt> was + where your CD was mounted.</p> + + <p>For as many distributions as you wish to install + from DOS (and you have free space for), install each + one in a directory under <tt + class="FILENAME">A:\FREEBSD</tt> - the <tt + class="FILENAME">BIN</tt> dist is only the minimal + requirement.</p> + + <p>Once you've copied the directories, you can simply + launch the installation from floppies as normal and + select ``DOS'' as your media type when the time + comes.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN350" name="AEN350">1.5.4 + Installing from QIC/SCSI Tape</a></h3> + + <p>When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt class="USERINPUT"><b>cd <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>tar cvf /dev/rsa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt +class="REPLACEABLE"><i>dist2</i></tt></b></tt> +</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 /> + + <h3 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 + Installing over a Network using FTP or NFS</a></h3> + + <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 /> + + <h4 class="SECT4"><a id="AEN375" + name="AEN375">1.5.5.1 Serial Port</a></h4> + + <p>SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.</p> + + <p>If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.</p> + + <p>You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.</p> + </div> + + <div class="SECT4"> + <hr /> + + <h4 class="SECT4"><a id="AEN381" + name="AEN381">1.5.5.2 Parallel Port</a></h4> + + <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 <tt + class="OPTION">link0</tt> 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 /> + + <h4 class="SECT4"><a id="AEN392" + name="AEN392">1.5.5.3 Ethernet</a></h4> + + <p>FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see <tt + class="FILENAME">HARDWARE.TXT</tt> in the + Documentation menu on the boot floppy or the top + level directory of the CDROM). If you are using one + of the supported PCMCIA Ethernet cards, also be sure + that it's plugged in <span class="emphasis"><i + class="EMPHASIS">before</i></span> the laptop is + powered on. FreeBSD does not, unfortunately, + currently support ``hot insertion'' of PCMCIA cards + during installation.</p> + + <p>You will also need to know your IP address on the + network, the <tt class="OPTION">netmask</tt> 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 /> + + <h4 class="SECT4"><a id="AEN403" + name="AEN403">1.5.5.4 NFS installation tips</a></h4> + + <p>NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.</p> + + <p>If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.</p> + + <p>If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.</p> + + <p>In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on <tt + class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, + then <tt class="HOSTID">wiggy</tt> will have to allow + the direct mounting of <tt + class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not + just <tt class="FILENAME">/usr</tt> or <tt + class="FILENAME">/usr/archive/stuff</tt>.</p> + + <p>In FreeBSD's <tt + class="FILENAME">/etc/exports</tt> file this is + controlled by the <tt class="OPTION">-alldirs</tt> + 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 /> + + <h4 class="SECT4"><a id="AEN420" + name="AEN420">1.5.5.5 FTP Installation tips</a></h4> + + <p>FTP installation may be done from any mirror site + containing a reasonably up-to-date version of + FreeBSD. A full menu of reasonable choices for almost + any location in the world is provided in the FTP site + menu during installation.</p> + + <p>If you are installing from some other FTP site not + listed in this menu, or you are having troubles + getting your name server configured properly, you can + also specify your own URL by selecting the ``URL'' + choice in that menu. A URL can contain a hostname or + an IP address, so something like the following would + work in the absence of a name server:</p> +<pre class="SCREEN"> +ftp://216.66.64.162/pub/FreeBSD/releases/pc98/4.2-RELEASE +</pre> + + <p>There are three FTP installation modes you can + use:</p> + + <ul> + <li> + <p>FTP: This method uses the standard ``Active'' + mode for transfers, in which the server initiates + a connection to the client. This will not work + through most firewalls but will often work best + with older FTP servers that do not support + passive mode. If your connection hangs with + passive mode, try this one.</p> + </li> + + <li> + <p>FTP Passive: This sets the FTP "Passive" mode + which prevents the server from opening + connections to the client. This option is best + for users to pass through firewalls that do not + allow incoming connections on random port + addresses.</p> + </li> + + <li> + <p>FTP via an HTTP proxy: This option instructs + FreeBSD to use HTTP to connect to a proxy for all + FTP operations. The proxy will translate the + requests and send them to the FTP server. This + allows the user to pass through firewalls that do + not allow FTP at all, but offer an HTTP proxy. + You must specify the hostname of the proxy in + addition to the FTP server.</p> + + <p>In the rare case that you have an FTP proxy + that does not go through HTTP, you can specify + the URL as something like:</p> +<pre class="SCREEN"> +<tt class="USERINPUT"><b>ftp://foo.bar.com:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</b></tt> +</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 /> + + <h2 class="SECT2"><a id="AEN463" name="AEN463">1.6 + Question and Answer Section for NEC PC-98x1 Architecture + Users</a></h2> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 + Distribution Format</a></h1> + + <p>A typical FreeBSD distribution directory looks something + like this (exact details may vary depending on version, + architecture, and other factors):</p> +<pre class="SCREEN"> +ERRATA.HTM README.TXT compat1x dict kernel +ERRATA.TXT RELNOTES.HTM compat20 doc manpages +HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages +HARDWARE.TXT base compat22 filename.txt ports +INSTALL.HTM boot compat3x floppies proflibs +INSTALL.TXT catpages compat4x games src +README.HTM cdrom.inf crypto info tools +</pre> + + <p>If you want to do a CDROM, FTP or NFS installation from + this distribution directory, all you need to do is make the + 1.44MB boot floppies from the floppies directory (see <a + href="#FLOPPIES">Section 1.3</a> for instructions on how to + do this), boot them and follow the instructions. The rest + of the data needed during the installation will be obtained + automatically based on your selections. If you've never + installed FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.</p> + + <p>If you're trying to do some other type of installation + or are merely curious about how a distribution is + organized, what follows is a more thorough description of + some of these items in more detail:</p> + + <ol type="1"> + <li> + <p>The <tt class="FILENAME">*.TXT</tt> and <tt + class="FILENAME">*.HTM</tt> files contain documentation + (for example, this document is contained in both <tt + class="FILENAME">INSTALL.TXT</tt> and <tt + class="FILENAME">INSTALL.HTM</tt>) and should be read + before starting an installation. The <tt + class="FILENAME">*.TXT</tt> files are plain text, while + the <tt class="FILENAME">*.HTM</tt> files are HTML + files that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.</p> + </li> + + <li> + <p><tt class="FILENAME">docbook.css</tt> is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.</p> + </li> + + <li> + <p>The <tt class="FILENAME">base</tt>, <tt + class="FILENAME">catpages</tt>, <tt + class="FILENAME">crypto</tt>, <tt + class="FILENAME">dict</tt>, <tt + class="FILENAME">doc</tt>, <tt + class="FILENAME">games</tt>, <tt + class="FILENAME">info</tt>, <tt + class="FILENAME">manpages</tt>, <tt + class="FILENAME">proflibs</tt>, and <tt + class="FILENAME">src</tt> directories contain the + primary distribution components of FreeBSD itself and + are split into smaller files for easy packing onto + floppies (should that be necessary).</p> + </li> + + <li> + <p>The <tt class="FILENAME">compat1x</tt>, <tt + class="FILENAME">compat20</tt>, <tt + class="FILENAME">compat21</tt>, <tt + class="FILENAME">compat22</tt>, <tt + class="FILENAME">compat3x</tt>, and <tt + class="FILENAME">compat4x</tt> directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their <tt class="FILENAME">install.sh</tt> scripts.</p> + </li> + + <li> + <p>The <tt class="FILENAME">floppies/</tt> subdirectory + contains the floppy installation images; further + information on using them can be found in <a + href="#FLOPPIES">Section 1.3</a>.</p> + </li> + + <li> + <p>The <tt class="FILENAME">packages</tt> and <tt + class="FILENAME">ports</tt> directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt><tt +class="USERINPUT"><b>/stand/sysinstall configPackages</b></tt> +</pre> + + <p>Packages can also be installed by feeding individual + filenames in <tt class="FILENAME">packages</tt>/ to the + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.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 100MB unpacked. More + information on the ports collection may be obtained + from <a href="http://www.FreeBSD.org/ports/" + target="_top">http://www.FreeBSD.org/ports/</a> or + locally from <tt + class="FILENAME">/usr/share/doc/handbook</tt> if you've + installed the <tt class="FILENAME">doc</tt> + distribution.</p> + </li> + + <li> + <p>Last of all, the <tt class="FILENAME">tools</tt> + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.</p> + </li> + </ol> + <br /> + <br /> + + <p>A typical distribution directory (for example, the <tt + class="FILENAME">info</tt> distribution) looks like this + internally:</p> +<pre class="SCREEN"> +CHECKSUM.MD5 info.ab info.ad info.inf install.sh +info.aa info.ac info.ae info.mtree +</pre> + + <p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains + MD5 signatures for each file, should data corruption be + suspected, and is purely for reference. It is not used by + the actual installation and does not need to be copied with + the rest of the distribution files. The <tt + class="FILENAME">info.a*</tt> files are split, gzip'd tar + files, the contents of which can be viewed by doing:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cat info.a* | tar tvzf -</b></tt> +</pre> + + <p>During installation, they are automatically concatenated + and extracted by the installation procedure.</p> + + <p>The <tt class="FILENAME">info.inf</tt> file is also + necessary since it is read by the installation program in + order to figure out how many pieces to look for when + fetching and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">.inf</tt> file <span class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first floppy of + each distribution set!</p> + + <p>The <tt class="FILENAME">info.mtree</tt> file is another + non-essential file which is provided for user reference. It + contains the MD5 signatures of the <span + class="emphasis"><i class="EMPHASIS">unpacked</i></span> + distribution files and can be later used with the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&sektion=8&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cd /cdrom/info</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>sh install.sh</b></tt> +</pre> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 + Upgrading FreeBSD</a></h1> + + <p>These instructions describe a procedure for doing a + binary upgrade from an older version of FreeBSD.</p> + + <div class="WARNING"> + <blockquote class="WARNING"> + <p><b>Warning:</b> While the FreeBSD upgrade procedure + does its best to safeguard against accidental loss of + data, it is still more than possible to <span + class="emphasis"><i class="EMPHASIS">wipe out your + entire disk</i></span> with this installation! Please + do not accept the final confirmation request unless you + have adequately backed up any important data files.</p> + </blockquote> + </div> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> These notes assume that you are + using the version of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.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+5.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+5.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 + 5.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></p> + + <p>These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.</p> + </blockquote> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN664" name="AEN664">3.1 + Introduction</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN668" name="AEN668">3.1.1 + Upgrade Overview</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN742" name="AEN742">3.2 + Procedure</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN745" name="AEN745">3.2.1 + Backup</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN748" name="AEN748">3.2.2 + Mount Filesystems</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN753" name="AEN753">3.2.3 + Select Distributions</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 + After Installation</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN763" name="AEN763">3.3 + Upgrading from Source Code</a></h2> + + <p>Those interested in an upgrade method that allows more + flexibility and sophistication should take a look at <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html" + target="_top">The Cutting Edge</a> in the FreeBSD + Handbook. This procedure involves rebuilding all of + FreeBSD from source code. It requires reliable network + connectivity, extra disk space, and time, but has + advantages for networks and other more complex + installations. This is roughly the same procedure as is + used for track the -STABLE or -CURRENT development + branches.</p> + + <p><tt class="FILENAME">/usr/src/UPDATING</tt> contains + important information on updating a FreeBSD system from + source code. It lists various issues resulting from + changes in FreeBSD that may affect an upgrade.</p> + + <p></p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 + Troubleshooting</a></h1> + + <div class="SECT2"> + <h2 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 + Repairing an Existing FreeBSD Installation</a></h2> + + <p>FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + <tt class="FILENAME">fixit.flp</tt> image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.</p> + + <p>To invoke fixit, simply boot the <tt + class="FILENAME">kern.flp</tt> floppy, choose the + ``Fixit'' item and insert the fixit floppy or CDROM when + asked. You will then be placed into a shell with a wide + variety of commands available (in the <tt + class="FILENAME">/stand</tt> and <tt + class="FILENAME">/mnt2/stand</tt> directories) for + checking, repairing and examining filesystems and their + contents. Some UNIX administration experience <span + class="emphasis"><i class="EMPHASIS">is</i></span> + required to use the fixit option.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN784" name="AEN784">4.2 Common + Installation Problems for NEC PC-98x1 Architecture + Users</a></h2> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/installation-sparc64.html b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-sparc64.html new file mode 100644 index 0000000000..0b72295699 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/installation-sparc64.html @@ -0,0 +1,1248 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/sparc64 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD/sparc64 + 5.1-RELEASE Installation Instructions</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + <hr /> + </div> + + <blockquote class="ABSTRACT"> + <div class="ABSTRACT"> + <a id="AEN11" name="AEN11"></a> + + <p>This article gives some brief instructions on + installing FreeBSD/sparc64 5.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 /> + + <h1 class="SECT1"><a id="INSTALL" name="INSTALL">1 + Installing FreeBSD</a></h1> + + <p>This section documents the process of installing a new + distribution of FreeBSD. These instructions pay particular + emphasis to the process of obtaining the FreeBSD + 5.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 /> + + <h2 class="SECT2"><a id="GETTING-STARTED" + name="GETTING-STARTED">1.1 Getting Started</a></h2> + + <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 /> + + <h2 class="SECT2"><a id="AEN36" name="AEN36">1.2 Hardware + Requirements</a></h2> + + <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 /> + + <h2 class="SECT2"><a id="FLOPPIES" name="FLOPPIES">1.3 + Floppy Disk Image Instructions</a></h2> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="START-INSTALLATION" + name="START-INSTALLATION">1.4 Installing FreeBSD from + CDROM or the Internet</a></h2> + + <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.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+5.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"> +<tt class="PROMPT">ok </tt> <a id="PROMPT-SINGLE" +name="PROMPT-SINGLE"><b>(1)</b></a> +<tt class="PROMPT">ok {0}</tt> <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 /> + + <h2 class="SECT2"><a id="AEN209" name="AEN209">1.5 Detail + on various installation types</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN248" name="AEN248">1.5.1 + Installing from a Network CDROM</a></h3> + + <p>If you simply wish to install from a local CDROM + drive then see <a href="#START-INSTALLATION">Section + 1.4</a>. If you don't have a CDROM drive on your system + and wish to use a FreeBSD distribution CD in the CDROM + drive of another system to which you have network + connectivity, there are also several ways of going + about it:</p> + + <ul> + <li> + <p>If you would be able to FTP install FreeBSD + directly from the CDROM drive in some FreeBSD + machine, it's quite easy: You simply add the + following line to the password file (using the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+5.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+5.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 /> + + <h3 class="SECT3"><a id="AEN280" name="AEN280">1.5.2 + Installing from Floppies</a></h3> + + <p>If you must install from floppy disks, either due to + unsupported hardware or just because you enjoy doing + things the hard way, you must first prepare some + floppies for the install.</p> + + <p>First, make your boot floppies as described in <a + href="#FLOPPIES">Section 1.3</a>.</p> + + <p>Second, peruse <a href="#LAYOUT">Section 2</a> and + pay special attention to the ``Distribution Format'' + section since it describes which files you're going to + need to put onto floppy and which you can safely + skip.</p> + + <p>Next you will need, at minimum, as many 1.44MB + floppies as it takes to hold all files in the <tt + class="FILENAME">bin</tt> (binary distribution) + directory. If you're preparing these floppies under + DOS, then these floppies <span class="emphasis"><i + class="EMPHASIS">must</i></span> be formatted using the + MS-DOS <tt class="FILENAME">FORMAT</tt> command. If + you're using Windows, use the Windows File Manager + format command.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Frequently, floppy disks come + ``factory preformatted''. While convenient, many + problems reported by users in the past have + resulted from the use of improperly formatted + media. Re-format them yourself, just to make + sure.</p> + </blockquote> + </div> + + <p>If you're creating the floppies from another FreeBSD + machine, a format is still not a bad idea though you + don't need to put a DOS filesystem on each floppy. You + can use the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+5.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+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>fdformat -f 1440 fd0.1440</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>disklabel -w -r fd0.1440 floppy3</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</b></tt> +</pre> + + <p>After you've formatted the floppies for DOS or UFS, + you'll need to copy the files onto them. The + distribution files are split into chunks conveniently + sized so that 5 of them will fit on a conventional + 1.44MB floppy. Go through all your floppies, packing as + many files as will fit on each one, until you've got + all the distributions you want packed up in this + fashion. Each distribution should go into its own + subdirectory on the floppy, e.g.: <tt + class="FILENAME">a:\bin\bin.inf</tt>, <tt + class="FILENAME">a:\bin\bin.aa</tt>, <tt + class="FILENAME">a:\bin\bin.ab</tt>, ...</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> The <tt + class="FILENAME">bin.inf</tt> file also needs to go + on the first floppy of the <tt + class="FILENAME">bin</tt> set since it is read by + the installation program in order to figure out how + many additional pieces to look for when fetching + and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">distname.inf</tt> file <span + class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first + floppy of each distribution set. This is also + covered in <tt + class="FILENAME">README.TXT</tt>.</p> + </blockquote> + </div> + + <p>Once you come to the Media screen of the install, + select ``Floppy'' and you'll be prompted for the + rest.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="AEN350" name="AEN350">1.5.4 + Installing from QIC/SCSI Tape</a></h3> + + <p>When installing from tape, the installation program + expects the files to be simply tar'ed onto it, so after + fetching all of the files for the distributions you're + interested in, simply use <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt class="USERINPUT"><b>cd <tt +class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>tar cvf /dev/rsa0 <tt +class="REPLACEABLE"><i>dist1</i></tt> .. <tt +class="REPLACEABLE"><i>dist2</i></tt></b></tt> +</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 /> + + <h3 class="SECT3"><a id="FTPNFS" name="FTPNFS">1.5.5 + Installing over a Network using FTP or NFS</a></h3> + + <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 /> + + <h4 class="SECT4"><a id="AEN375" + name="AEN375">1.5.5.1 Serial Port</a></h4> + + <p>SLIP support is rather primitive, and is limited + primarily to hard-wired links, such as a serial cable + running between two computers. The link must be + hard-wired because the SLIP installation doesn't + currently offer a dialing capability. If you need to + dial out with a modem or otherwise dialog with the + link before connecting to it, then I recommend that + the PPP utility be used instead.</p> + + <p>If you're using PPP, make sure that you have your + Internet Service Provider's IP address and DNS + information handy as you'll need to know it fairly + early in the installation process. You may also need + to know your own IP address, though PPP supports + dynamic address negotiation and may be able to pick + up this information directly from your ISP if they + support it.</p> + + <p>You will also need to know how to use the various + ``AT commands'' for dialing out with your particular + brand of modem as the PPP dialer provides only a very + simple terminal emulator.</p> + </div> + + <div class="SECT4"> + <hr /> + + <h4 class="SECT4"><a id="AEN381" + name="AEN381">1.5.5.2 Parallel Port</a></h4> + + <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 <tt + class="OPTION">link0</tt> 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 /> + + <h4 class="SECT4"><a id="AEN392" + name="AEN392">1.5.5.3 Ethernet</a></h4> + + <p>FreeBSD supports many common Ethernet cards; a + table of supported cards is provided as part of the + FreeBSD Hardware Notes (see <tt + class="FILENAME">HARDWARE.TXT</tt> in the + Documentation menu on the boot floppy or the top + level directory of the CDROM). If you are using one + of the supported PCMCIA Ethernet cards, also be sure + that it's plugged in <span class="emphasis"><i + class="EMPHASIS">before</i></span> the laptop is + powered on. FreeBSD does not, unfortunately, + currently support ``hot insertion'' of PCMCIA cards + during installation.</p> + + <p>You will also need to know your IP address on the + network, the <tt class="OPTION">netmask</tt> 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 /> + + <h4 class="SECT4"><a id="AEN403" + name="AEN403">1.5.5.4 NFS installation tips</a></h4> + + <p>NFS installation is fairly straight-forward: + Simply copy the FreeBSD distribution files you want + onto a server somewhere and then point the NFS media + selection at it.</p> + + <p>If this server supports only ``privileged port'' + access (this is generally the default for Sun and + Linux workstations), you will need to set this option + in the Options menu before installation can + proceed.</p> + + <p>If you have a poor quality Ethernet card which + suffers from very slow transfer rates, you may also + wish to toggle the appropriate Options flag.</p> + + <p>In order for NFS installation to work, the server + must also support ``subdir mounts'', e.g. if your + FreeBSD distribution directory lives on <tt + class="FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>, + then <tt class="HOSTID">wiggy</tt> will have to allow + the direct mounting of <tt + class="FILENAME">/usr/archive/stuff/FreeBSD</tt>, not + just <tt class="FILENAME">/usr</tt> or <tt + class="FILENAME">/usr/archive/stuff</tt>.</p> + + <p>In FreeBSD's <tt + class="FILENAME">/etc/exports</tt> file this is + controlled by the <tt class="OPTION">-alldirs</tt> + 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 /> + + <h4 class="SECT4"><a id="AEN420" + name="AEN420">1.5.5.5 FTP Installation tips</a></h4> + + <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"> +<tt class="USERINPUT"><b>ftp://foo.bar.com:<tt +class="REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</b></tt> +</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 /> + + <h2 class="SECT2"><a id="AEN463" name="AEN463">1.6 + Question and Answer Section for UltraSPARC Architecture + Users</a></h2> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="LAYOUT" name="LAYOUT">2 + Distribution Format</a></h1> + + <p>A typical FreeBSD distribution directory looks something + like this (exact details may vary depending on version, + architecture, and other factors):</p> +<pre class="SCREEN"> +ERRATA.HTM README.TXT compat1x dict kernel +ERRATA.TXT RELNOTES.HTM compat20 doc manpages +HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages +HARDWARE.TXT base compat22 filename.txt ports +INSTALL.HTM boot compat3x floppies proflibs +INSTALL.TXT catpages compat4x games src +README.HTM cdrom.inf crypto info tools +</pre> + + <p>If you want to do a CDROM, FTP or NFS installation from + this distribution directory, all you need to do is make the + 1.44MB boot floppies from the floppies directory (see <a + href="#FLOPPIES">Section 1.3</a> for instructions on how to + do this), boot them and follow the instructions. The rest + of the data needed during the installation will be obtained + automatically based on your selections. If you've never + installed FreeBSD before, you also want to read the + entirety of this document (the installation instructions) + file.</p> + + <p>If you're trying to do some other type of installation + or are merely curious about how a distribution is + organized, what follows is a more thorough description of + some of these items in more detail:</p> + + <ol type="1"> + <li> + <p>The <tt class="FILENAME">*.TXT</tt> and <tt + class="FILENAME">*.HTM</tt> files contain documentation + (for example, this document is contained in both <tt + class="FILENAME">INSTALL.TXT</tt> and <tt + class="FILENAME">INSTALL.HTM</tt>) and should be read + before starting an installation. The <tt + class="FILENAME">*.TXT</tt> files are plain text, while + the <tt class="FILENAME">*.HTM</tt> files are HTML + files that can be read by almost any Web browser. Some + distributions may contain documentation in other + formats as well, such as PDF or PostScript.</p> + </li> + + <li> + <p><tt class="FILENAME">docbook.css</tt> is a Cascading + Style Sheet (CSS) file used by some Web browsers for + formatting the HTML documentation.</p> + </li> + + <li> + <p>The <tt class="FILENAME">base</tt>, <tt + class="FILENAME">catpages</tt>, <tt + class="FILENAME">crypto</tt>, <tt + class="FILENAME">dict</tt>, <tt + class="FILENAME">doc</tt>, <tt + class="FILENAME">games</tt>, <tt + class="FILENAME">info</tt>, <tt + class="FILENAME">manpages</tt>, <tt + class="FILENAME">proflibs</tt>, and <tt + class="FILENAME">src</tt> directories contain the + primary distribution components of FreeBSD itself and + are split into smaller files for easy packing onto + floppies (should that be necessary).</p> + </li> + + <li> + <p>The <tt class="FILENAME">compat1x</tt>, <tt + class="FILENAME">compat20</tt>, <tt + class="FILENAME">compat21</tt>, <tt + class="FILENAME">compat22</tt>, <tt + class="FILENAME">compat3x</tt>, and <tt + class="FILENAME">compat4x</tt> directories contain + distributions for compatibility with older releases and + are distributed as single gzip'd tar files - they can + be installed during release time or later by running + their <tt class="FILENAME">install.sh</tt> scripts.</p> + </li> + + <li> + <p>The <tt class="FILENAME">floppies/</tt> subdirectory + contains the floppy installation images; further + information on using them can be found in <a + href="#FLOPPIES">Section 1.3</a>.</p> + </li> + + <li> + <p>The <tt class="FILENAME">packages</tt> and <tt + class="FILENAME">ports</tt> directories contain the + FreeBSD Packages and Ports Collections. Packages may be + installed from the packages directory by running the + command:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt><tt +class="USERINPUT"><b>/stand/sysinstall configPackages</b></tt> +</pre> + + <p>Packages can also be installed by feeding individual + filenames in <tt class="FILENAME">packages</tt>/ to the + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.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 100MB unpacked. More + information on the ports collection may be obtained + from <a href="http://www.FreeBSD.org/ports/" + target="_top">http://www.FreeBSD.org/ports/</a> or + locally from <tt + class="FILENAME">/usr/share/doc/handbook</tt> if you've + installed the <tt class="FILENAME">doc</tt> + distribution.</p> + </li> + + <li> + <p>Last of all, the <tt class="FILENAME">tools</tt> + directory contains various DOS tools for discovering + disk geometries, installing boot managers and the like. + It is purely optional and provided only for user + convenience.</p> + </li> + </ol> + <br /> + <br /> + + <p>A typical distribution directory (for example, the <tt + class="FILENAME">info</tt> distribution) looks like this + internally:</p> +<pre class="SCREEN"> +CHECKSUM.MD5 info.ab info.ad info.inf install.sh +info.aa info.ac info.ae info.mtree +</pre> + + <p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains + MD5 signatures for each file, should data corruption be + suspected, and is purely for reference. It is not used by + the actual installation and does not need to be copied with + the rest of the distribution files. The <tt + class="FILENAME">info.a*</tt> files are split, gzip'd tar + files, the contents of which can be viewed by doing:</p> +<pre class="SCREEN"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cat info.a* | tar tvzf -</b></tt> +</pre> + + <p>During installation, they are automatically concatenated + and extracted by the installation procedure.</p> + + <p>The <tt class="FILENAME">info.inf</tt> file is also + necessary since it is read by the installation program in + order to figure out how many pieces to look for when + fetching and concatenating the distribution. When putting + distributions onto floppies, the <tt + class="FILENAME">.inf</tt> file <span class="emphasis"><i + class="EMPHASIS">must</i></span> occupy the first floppy of + each distribution set!</p> + + <p>The <tt class="FILENAME">info.mtree</tt> file is another + non-essential file which is provided for user reference. It + contains the MD5 signatures of the <span + class="emphasis"><i class="EMPHASIS">unpacked</i></span> + distribution files and can be later used with the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mtree&sektion=8&manpath=FreeBSD+5.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"> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>cd /cdrom/info</b></tt> +<tt class="PROMPT">#</tt> <tt +class="USERINPUT"><b>sh install.sh</b></tt> +</pre> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADING" name="UPGRADING">3 + Upgrading FreeBSD</a></h1> + + <p>These instructions describe a procedure for doing a + binary upgrade from an older version of FreeBSD.</p> + + <div class="WARNING"> + <blockquote class="WARNING"> + <p><b>Warning:</b> While the FreeBSD upgrade procedure + does its best to safeguard against accidental loss of + data, it is still more than possible to <span + class="emphasis"><i class="EMPHASIS">wipe out your + entire disk</i></span> with this installation! Please + do not accept the final confirmation request unless you + have adequately backed up any important data files.</p> + </blockquote> + </div> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> These notes assume that you are + using the version of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.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+5.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+5.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 + 5.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></p> + + <p>These upgrade instructions are provided for the use + of users upgrading from relatively recent FreeBSD + 5-CURRENT snapshots.</p> + </blockquote> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN664" name="AEN664">3.1 + Introduction</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN668" name="AEN668">3.1.1 + Upgrade Overview</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN742" name="AEN742">3.2 + Procedure</a></h2> + + <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 /> + + <h3 class="SECT3"><a id="AEN745" name="AEN745">3.2.1 + Backup</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN748" name="AEN748">3.2.2 + Mount Filesystems</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="AEN753" name="AEN753">3.2.3 + Select Distributions</a></h3> + + <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 /> + + <h3 class="SECT3"><a id="FSTAB" name="FSTAB">3.2.4 + After Installation</a></h3> + + <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 /> + + <h2 class="SECT2"><a id="AEN763" name="AEN763">3.3 + Upgrading from Source Code</a></h2> + + <p>Those interested in an upgrade method that allows more + flexibility and sophistication should take a look at <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html" + target="_top">The Cutting Edge</a> in the FreeBSD + Handbook. This procedure involves rebuilding all of + FreeBSD from source code. It requires reliable network + connectivity, extra disk space, and time, but has + advantages for networks and other more complex + installations. This is roughly the same procedure as is + used for track the -STABLE or -CURRENT development + branches.</p> + + <p><tt class="FILENAME">/usr/src/UPDATING</tt> contains + important information on updating a FreeBSD system from + source code. It lists various issues resulting from + changes in FreeBSD that may affect an upgrade.</p> + + <p></p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="TROUBLE" name="TROUBLE">4 + Troubleshooting</a></h1> + + <div class="SECT2"> + <h2 class="SECT2"><a id="REPAIRING" name="REPAIRING">4.1 + Repairing an Existing FreeBSD Installation</a></h2> + + <p>FreeBSD features a ``Fixit'' option in the top menu of + the boot floppy. To use it, you will also need either a + <tt class="FILENAME">fixit.flp</tt> image floppy, + generated in the same fashion as the boot floppy, or the + ``live filesystem'' CDROM; typically the second CDROM in + a multi-disc FreeBSD distribution.</p> + + <p>To invoke fixit, simply boot the <tt + class="FILENAME">kern.flp</tt> floppy, choose the + ``Fixit'' item and insert the fixit floppy or CDROM when + asked. You will then be placed into a shell with a wide + variety of commands available (in the <tt + class="FILENAME">/stand</tt> and <tt + class="FILENAME">/mnt2/stand</tt> directories) for + checking, repairing and examining filesystems and their + contents. Some UNIX administration experience <span + class="emphasis"><i class="EMPHASIS">is</i></span> + required to use the fixit option.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN784" name="AEN784">4.2 Common + Installation Problems for UltraSPARC Architecture + Users</a></h2> + </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 <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/installation.sgml b/en_US.ISO8859-1/htdocs/releases/5.1R/installation.sgml new file mode 100644 index 0000000000..5718dc32ac --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/installation.sgml @@ -0,0 +1,32 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/releases/5.1R/installation.sgml,v 1.3 2005/10/04 06:52:23 murray Exp $"> +<!ENTITY title "FreeBSD 5.1-RELEASE Installation Notes"> +<!ENTITY % navinclude.download "INCLUDE"> +]> +<html> + &header; + + <p>The installation notes for FreeBSD are customized for different + platforms, as the procedures for installing FreeBSD are highly + dependent on the hardware platform.</p> + + <p>Installation notes for FreeBSD 5.1-RELEASE are available for the following + platforms:</p> + + <ul> + <li><a href="installation-alpha.html">alpha</a></li> + <li><a href="installation-i386.html">i386</a></li> + <li><a href="installation-ia64.html">ia64</a></li> + <li><a href="installation-pc98.html">pc98</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> + + &footer; + +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/readme.html b/en_US.ISO8859-1/htdocs/releases/5.1R/readme.html new file mode 100644 index 0000000000..c81a3a3ec7 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/readme.html @@ -0,0 +1,540 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD 5.1-RELEASE 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 id="AEN2" name="AEN2">FreeBSD + 5.1-RELEASE README</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + + <p class="PUBDATE">$FreeBSD: + src/release/doc/en_US.ISO8859-1/readme/article.sgml,v 1.26 + 2003/05/06 20:01:07 bmah Exp $<br /> + </p> + <hr /> + </div> + + <blockquote class="ABSTRACT"> + <div class="ABSTRACT"> + <a id="AEN12" name="AEN12"></a> + + <p>This document gives a brief introduction to FreeBSD + 5.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 /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This distribution is a release of FreeBSD 5.1-RELEASE, + the latest point along the 5-CURRENT branch.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN17" name="AEN17">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 + (i386), NEC PC-9801/9821 series PCs and compatibles + (pc98), DEC/Compaq/HP Alpha computers (alpha), and + UltraSPARC machines (sparc64). Versions for the IA64 + (ia64), PowerPC (powerpc), and AMD ``Hammer'' (amd64) + architectures are currently under development as well. + FreeBSD works with a wide variety of peripherals and + configurations and can be used for everything from + software development to games to Internet Service + Provision.</p> + + <p>This release of FreeBSD contains everything you need + to run such a system, including full source code for the + kernel and all utilities in the base distribution. With + the source distribution installed, you can literally + recompile the entire system from scratch with one + command, making it ideal for students, researchers, or + users who simply want to see how it all works.</p> + + <p>A large collection of third-party ported software (the + ``Ports Collection'') is also provided to make it easy to + obtain and install all your favorite traditional <span + class="TRADEMARK">UNIX</span>® 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 8,500 ports, from editors to + programming languages to graphical applications, make + FreeBSD a powerful and comprehensive operating + environment that extends far beyond what's provided by + many commercial versions of <span + class="TRADEMARK">UNIX</span>®. Most ports are also + available as pre-compiled ``packages'', which can be + quickly installed from the installation program.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN29" name="AEN29">1.2 Target + Audience</a></h2> + + <p>This release of FreeBSD is suitable for all users. It + has undergone a period of testing and quality assurance + checking to ensure the highest reliability and + dependability.</p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="OBTAIN" name="OBTAIN">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 id="AEN35" name="AEN35">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 id="AEN42" name="AEN42">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://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 + <tt class="EMAIL"><<a + href="mailto:freebsd-admin@FreeBSD.org">freebsd-admin@FreeBSD.org</a>></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 id="CONTACTING" name="CONTACTING">3 + Contacting the FreeBSD Project</a></h1> + + <div class="SECT2"> + <h2 class="SECT2"><a id="AEN56" name="AEN56">3.1 Email + and Mailing Lists</a></h2> + + <p>For any questions or general technical support issues, + please send mail to the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-questions" + target="_top">FreeBSD general questions mailing + list</a>.</p> + + <p>If you're tracking the 5-CURRENT development efforts, + you <span class="emphasis"><i + class="EMPHASIS">must</i></span> join the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-current" + target="_top">FreeBSD-CURRENT mailing list</a>, in order + to keep abreast of recent developments and changes that + may affect the way you use and maintain the system.</p> + + <p>Being a largely-volunteer effort, the FreeBSD Project + is always happy to have extra hands willing to + help--there are already far more desired enhancements + than there is time to implement them. To contact the + developers on technical matters, or with offers of help, + please send mail to the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hackers" + target="_top">FreeBSD technical discussions mailing + list</a>.</p> + + <p>Please note that these mailing lists can experience + <span class="emphasis"><i + class="EMPHASIS">significant</i></span> amounts of + traffic. If you have slow or expensive mail access, or + are only interested in keeping up with major FreeBSD + events, you may find it preferable to subscribe instead + to the <a + href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-announce" + target="_top">FreeBSD announcements mailing + list</a>.</p> + + <p>All of the mailing lists can be freely joined by + anyone wishing to do so. Visit the <a + href="http://www.FreeBSD.org/mailman/listinfo" + target="_top">FreeBSD Mailman Info Page</a>. This will + give you more information on joining the various lists, + accessing archives, etc. There are a number of mailing + lists targeted at special interest groups not mentioned + here; more information can be obtained either from the + Mailman pages or the <a + href="http://www.FreeBSD.org/support.html#mailing-list" + target="_top">mailing lists section</a> of the FreeBSD + Web site.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Do <span class="emphasis"><i + class="EMPHASIS">not</i></span> send email to the + lists asking to be subscribed. Use the Mailman + interface instead.</p> + </blockquote> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="AEN74" name="AEN74">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.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+5.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+5.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 /> + + <h1 class="SECT1"><a id="SEEALSO" name="SEEALSO">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 id="RELEASE-DOCS" + name="RELEASE-DOCS">4.1 Release Documentation</a></h2> + + <p>A number of other files provide more specific + information about this release distribution. These files + are provided in various formats. Most distributions will + include both ASCII text (<tt class="FILENAME">.TXT</tt>) + and HTML (<tt class="FILENAME">.HTM</tt>) renditions. + Some distributions may also include other formats such as + PostScript (<tt class="FILENAME">.PS</tt>) or Portable + Document Format (<tt class="FILENAME">.PDF</tt>).</p> + + <ul> + <li> + <p><tt class="FILENAME">README.TXT</tt>: This file, + which gives some general information about FreeBSD as + well as some cursory notes about obtaining a + distribution.</p> + </li> + + <li> + <p><tt class="FILENAME">EARLY.TXT</tt>: A guide for + early adopters of FreeBSD 5.1-RELEASE. Highly + recommended reading for users new to FreeBSD + 5-CURRENT and/or the 5.<tt + class="REPLACEABLE"><i>X</i></tt> series of + releases.</p> + </li> + + <li> + <p><tt class="FILENAME">RELNOTES.TXT</tt>: The + release notes, showing what's new and different in + FreeBSD 5.1-RELEASE compared to the previous release + (FreeBSD 5.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 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.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + (currently alpha, i386, ia64, pc98, and sparc64), 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.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 /> + + <h2 class="SECT2"><a id="AEN141" name="AEN141">4.2 Manual + Pages</a></h2> + + <p>As with almost all <span + class="TRADEMARK">UNIX</span>®-like operating + systems, FreeBSD comes with a set of on-line manual + pages, accessed through the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=man&sektion=1&manpath=FreeBSD+5.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+5.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+5.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+5.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 /> + + <h2 class="SECT2"><a id="AEN159" name="AEN159">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 <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 /> + + <h1 class="SECT1"><a id="ACKNOWLEDGEMENTS" + name="ACKNOWLEDGEMENTS">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 release. + For a complete list of FreeBSD developers and contributors, + please see <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/" + target="_top">``Contributors to FreeBSD''</a> on the + FreeBSD Web site or any of its mirrors.</p> + + <p>Special thanks also go to the many thousands of FreeBSD + users and testers all over the world, without whom this + release simply would not have been possible.</p> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-alpha.html b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-alpha.html new file mode 100644 index 0000000000..cd45c619e4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-alpha.html @@ -0,0 +1,1563 @@ +<!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/alpha 5.1-RELEASE Release 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 id="AEN2" name="AEN2">FreeBSD/alpha + 5.1-RELEASE Release Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + + <p class="PUBDATE">$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.573 2003/05/28 21:01:22 hrs Exp $<br /> + </p> + + <div> + <div class="ABSTRACT"> + <a id="AEN12" name="AEN12"></a> + + <p>The release notes for FreeBSD 5.1-RELEASE contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. This + document lists applicable security advisories that were + issued since the last release, as well as significant + changes to the FreeBSD kernel and userland. Some brief + remarks on upgrading are also presented.</p> + </div> + </div> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#NEW">What's New</a></dt> + + <dd> + <dl> + <dt>2.1 <a href="#SECURITY">Security + Advisories</a></dt> + + <dt>2.2 <a href="#KERNEL">Kernel Changes</a></dt> + + <dd> + <dl> + <dt>2.2.1 <a href="#PROC">Processor/Motherboard + Support</a></dt> + + <dt>2.2.2 <a href="#BOOT">Boot Loader + Changes</a></dt> + + <dt>2.2.3 <a href="#NET-IF">Network Interface + Support</a></dt> + + <dt>2.2.4 <a href="#NET-PROTO">Network + Protocols</a></dt> + + <dt>2.2.5 <a href="#DISKS">Disks and + Storage</a></dt> + + <dt>2.2.6 <a href="#FS">File Systems</a></dt> + + <dt>2.2.7 <a href="#PCCARD">PCCARD + Support</a></dt> + + <dt>2.2.8 <a href="#MM">Multimedia + Support</a></dt> + </dl> + </dd> + + <dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + + <dt>2.4 <a href="#CONTRIB">Contributed + Software</a></dt> + + <dt>2.5 <a href="#PORTS">Ports/Packages Collection + Infrastructure</a></dt> + + <dt>2.6 <a href="#RELENG">Release Engineering and + Integration</a></dt> + + <dt>2.7 <a href="#DOC">Documentation</a></dt> + </dl> + </dd> + + <dt>3 <a href="#UPGRADE">Upgrading from previous releases + of FreeBSD</a></dt> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the release notes for FreeBSD + 5.1-RELEASE on the Alpha/AXP hardware platform. It + describes recently added, changed, or deleted features of + FreeBSD. It also provides some notes on upgrading from + previous versions of FreeBSD.</p> + + <p>This distribution of FreeBSD 5.1-RELEASE is a release + distribution. It can be found at <a + href="ftp://ftp.FreeBSD.org/" + target="_top">ftp://ftp.FreeBSD.org/</a> or any of its + mirrors. More information on obtaining this (or other) + release distributions of FreeBSD can be found in the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html" + target="_top">``Obtaining FreeBSD'' appendix</a> to the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" + target="_top">FreeBSD Handbook</a>.</p> + + <p>Users who are new to the 5-CURRENT series of FreeBSD + releases should also read the ``Early Adopters Guide to + FreeBSD 5.1-RELEASE''. This document can generally be found + in the same location as the release notes (either as a part + of a FreeBSD distribution or on the FreeBSD Web site). It + contains important information regarding the advantages and + disadvantages of using FreeBSD 5.1-RELEASE, as opposed to + releases based on the FreeBSD 4-STABLE development + branch.</p> + + <p>All users are encouraged to consult the release errata + before installing FreeBSD. The errata document is updated + with ``late-breaking'' information discovered late in the + release cycle or after the release. Typically, it contains + information on known bugs, security advisories, and + corrections to documentation. An up-to-date copy of the + errata for FreeBSD 5.1-RELEASE can be found on the FreeBSD + Web site.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="NEW" name="NEW">2 What's + New</a></h1> + + <p>This section describes many of the user-visible new or + changed features in FreeBSD since 5.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 5.0-RELEASE). The latter items are + marked as [MERGED].</p> + + <p>Typical release note items document recent security + advisories issued after 5.0-RELEASE, new drivers or + hardware support, new commands or options, major bug fixes, + or contributed software upgrades. They may also list + changes to major ports/packages or release engineering + practices. Clearly the release notes cannot list every + single change made to FreeBSD between releases; this + document focuses primarily on security advisories, + user-visible changes, and major architectural + improvements.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 + Security Advisories</a></h2> + + <p>A remotely exploitable vulnerability in <b + class="APPLICATION">CVS</b> has been corrected with the + import of version 1.11.5. More details can be found in + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:01.cvs.asc" + target="_top">FreeBSD-SA-03:01</a>. [MERGED]</p> + + <p>A timing-based attack on <b + class="APPLICATION">OpenSSL</b>, which could allow a very + powerful attacker access to plaintext under certain + circumstances, has been prevented via an upgrade to <b + class="APPLICATION">OpenSSL</b> 0.9.7. See security + advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:02.openssl.asc" + target="_top">FreeBSD-SA-03:02</a> for more details. + [MERGED]</p> + + <p>The security and performance of the ``syncookies'' + feature has been improved to decrease the chance of an + attacker being able to spoof connections. More details + are given in security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:03.syncookies.asc" + target="_top">FreeBSD-SA-03:03</a>. [MERGED]</p> + + <p>Remotely-exploitable buffer overflow vulnerabilities + in <b class="APPLICATION">sendmail</b> have been fixed by + updating <b class="APPLICATION">sendmail</b>. For more + details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:04.sendmail.asc" + target="_top">FreeBSD-SA-03:04</a> and <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:07.sendmail.asc" + target="_top">FreeBSD-SA-03:07</a>. [MERGED]</p> + + <p>A bounds-checking bug in the XDR implementation, which + could allow a remote attacker to cause a + denial-of-service, has been fixed. For more details see + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:05.xdr.asc" + target="_top">FreeBSD-SA-03:05</a>. [MERGED]</p> + + <p>Two recently-publicized flaws in <b + class="APPLICATION">OpenSSL</b> have been corrected. For + more details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:06.openssl.asc" + target="_top">FreeBSD-SA-03:06</a>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel + Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a> is now + mandatory; the <tt class="LITERAL">NODEVFS</tt> option + has been removed from the set of possible kernel + configuration options.</p> + + <p>A minor bug in the permissions handling of <tt + class="FILENAME">/dev/tty</tt> has been fixed. As a + result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh</span>(1)</span></a> can now be + used after <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=su&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">su</span>(1)</span></a>.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstat</span>(2)</span></a> to + return <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kqueue&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kqueue</span>(2)</span></a> to + report <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed. The + <tt class="LITERAL">NOTE_LOWAT</tt> flag for <tt + class="LITERAL">EVFILT_READ</tt> has been fixed.</p> + + <p>Linux emulation mode now supports IPv6.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=madvise&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">madvise</span>(2)</span></a> now + supports a <tt class="LITERAL">MADV_PROTECT</tt> + behavior, which informs the virtual memory system that a + process is critical and should not be killed when swap + space has been exhausted. The process must be owned by + the superuser.</p> + + <p>A second process scheduler, designed to be a general + purpose scheduler with many SMP benefits, has been added + to the scheduler framework. Exactly one scheduler must be + specified in a kernel configuration. The original + scheduler may be selected using <tt + class="LITERAL">options SCHED_4BSD</tt>. The newer + (experimental) scheduler can be selected by using <tt + class="LITERAL">options SCHED_ULE</tt>.</p> + + <p>Device major numbers are now allocated dynamically by + default. This change greatly decreases the need for a + static, centralized table of major number assignments to + device drivers (a few drivers retain their old static + major numbers for compatibility), and also reduces the + possibility of running out of device major numbers.</p> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PROC" name="PROC">2.2.1 + Processor/Motherboard Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="BOOT" name="BOOT">2.2.2 Boot + Loader Changes</a></h3> + + <p>The alpha boot loader (<tt + class="FILENAME">boot1</tt>) can now be called <tt + class="FILENAME">boot</tt> for consistency with other + platforms.</p> + + <p>The <tt class="FILENAME">/modules</tt> directory + (once the default location for modules on FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>) is no longer a part + of the default <tt + class="VARNAME">kern.module_path</tt>. Third-party + modules should be placed in <tt + class="FILENAME">/boot/modules</tt>.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Modules designed for use with + FreeBSD 4.<tt class="REPLACEABLE"><i>X</i></tt> are + likely to panic when loaded into a FreeBSD + 5.1-RELEASE kernel and should be used with extreme + caution.</p> + </blockquote> + </div> + <br /> + <br /> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-IF" name="NET-IF">2.2.3 + Network Interface Support</a></h3> + + <p>The cm driver now supports IPX. [MERGED]</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wlan&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wlan</span>(4)</span></a> module + provides 802.11 link-layer support. The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wi</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">an</span>(4)</span></a> drivers + now use this facility.</p> + + <p>A timing bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xl</span>(4)</span></a> driver, + which could cause a kernel panic (or other problems) + when configuring an interface, has been fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-PROTO" + name="NET-PROTO">2.2.4 Network Protocols</a></h3> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">skipto</tt> rules can once again be + used with the <tt class="LITERAL">log</tt> keyword. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">uid</tt> rules are once again + working.</p> + + <p>It is now possible to build the <tt + class="LITERAL">FAST_IPSEC</tt> and <tt + class="LITERAL">INET6</tt> options into the same + kernel. (They still cannot be used together, + however.)</p> + + <p>A bug in TCP NewReno, which caused premature exit + from fast recovery when NewReno was enabled, has been + fixed. [MERGED]</p> + + <p>TCP now has support for the ``Limited Transmit'' + mechanism proposed by RFC 3042. This feature is + intended to improve the effectiveness of TCP loss + recovery in certain circumstances. It is off by default + but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3042</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>TCP now has support for increased initial congestion + window sizes as described in RFC 3390. This feature can + improve the throughput of short transfers, as well as + high-bandwidth, large propagation-delay connections. It + is off by default but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3390</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>The IP fragment reassembly code behaves more + gracefully when receiving a large number of packet + fragments (it is designed to be more resistant to + fragment-based denial of service attacks). [MERGED]</p> + + <p>TCP connections in the <tt + class="LITERAL">TIME_WAIT</tt> state now use a special + protocol control block that uses less space than a + full-blown TCP PCB. This allows some of the data + structures and resources used by such a connection to + be freed earlier.</p> + + <p>It is now possible to specify the range of + ``privileged ports'' (TCP and UDP ports that require + superuser access to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bind&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bind</span>(2)</span></a> to). + The range is now specified with the <tt + class="VARNAME">net.inet.ip.portrange.reservedlow</tt> + and <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl variables, defaulting to the traditional UNIX + behavior. This feature is intended to help network + servers bind to traditionally privileged ports without + requiring superuser access. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ip&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ip</span>(4)</span></a> has more + details.</p> + + <p>Some bugs in the non-blocking RPC code has been + fixed. As a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amd</span>(8)</span></a> users + are now able to mount volumes from a 5.1-RELEASE + server.</p> + + <p>Support for XNS networking, which has not worked + correctly for almost seven years, has been removed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="DISKS" name="DISKS">2.2.5 + Disks and Storage</a></h3> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aac</span>(4)</span></a> driver + now runs free of the Giant kernel lock. This change has + given a nearly 20% performance speedup on an SMP system + running multiple I/O intensive loads.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports all known SiS chipsets. (More details can + be found in the Hardware Notes.)</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports the Promise SATA150 TX2 and TX4 Serial + ATA/150 controllers.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now flushes devices on shutdown. This change may result + in failure messages being printed on the console for + devices that do not support flushing.</p> + + <p>The CAM layer now has support for devices with more + than 2<sup>32</sup> blocks. (Assuming 512-byte blocks, + this means support for devices larger than 2TB.)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> For users upgrading across this + change, note that all userland applications that + talk to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pass&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pass</span>(4)</span></a> or + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xpt</span>(4)</span></a> + devices must be recompiled. Examples of such + programs are <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=camcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">camcontrol</span>(8)</span></a> + in the base system, the <tt + class="FILENAME">sysutils/cdrtools</tt> port, and + the <tt class="FILENAME">multimedia/xmms</tt> + port.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>A number of changes have been made to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a> driver. + The primary user-visible change is improved + compatibility with ATAPI/USB/Firewire CDROM drives.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> is now + mandatory; the <tt class="LITERAL">NO_GEOM</tt> has + been removed from the set of kernel configuration + options.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">iir</span>(4)</span></a> driver + has been updated; this update is believed to fix + problems detecting attached disks during + installation.</p> + + <p>A bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mly</span>(4)</span></a> driver + that caused hangs has been corrected.</p> + + <p>Support has been added for volume labels on UFS and + UFS2 file systems. These labels are strings that can be + used to identify a volume, regardless of what device it + appears on. Labels can be set with the <tt + class="OPTION">-L</tt> options to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> or <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tunefs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tunefs</span>(8)</span></a>. With + the <tt class="LITERAL">GEOM_VOL</tt> module, volumes + can be accessed using their labels under <tt + class="FILENAME">/dev/vol</tt>.</p> + + <p>The root file system can now be located on a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> + volume. More information can be found in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> manual + page.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="FS" name="FS">2.2.6 File + Systems</a></h3> + + <p>A new <tt class="LITERAL">DIRECTIO</tt> kernel + option enables support for read operations that bypass + the buffer cache and put data directly into a userland + buffer. This feature requires that the <tt + class="LITERAL">O_DIRECT</tt> flag is set on the file + descriptor and that both the offset and length for the + read operation are multiples of the physical media + sector size. [MERGED]</p> + + <p>NETNCP and Netware File System Support (nwfs) are + once again working.</p> + + <p>Bugs that could cause the unmounting of a smbfs + share to fail or cause a kernel panic have been + fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PCCARD" name="PCCARD">2.2.7 + PCCARD Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="MM" name="MM">2.2.8 Multimedia + Support</a></h3> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 + Userland Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + correctly handles setting user passwords containing + special shell characters.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + supports a <tt class="OPTION">-g</tt> option to set a + user's default login group.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> + utility is a replacement for the older disklabel utility. + Like its predecessor, it installs, examines, or modifies + the BSD label on a disk partition, and can install + bootstrap code. Compared to disklabel, a number of + obsolete options and parameters have been retired. A new + <tt class="OPTION">-m</tt> option instructs <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> to + use the layout suitable for a specific machine.</p> + + <p>The <tt class="FILENAME">compat4x</tt> distribution + now includes the <tt + class="FILENAME">libcrypto.so.2</tt>, <tt + class="FILENAME">libgmp.so.3</tt>, and <tt + class="FILENAME">libssl.so.2</tt> libraries from FreeBSD + 4.7-RELEASE.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chgrp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chgrp</span>(1)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chown&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chown</span>(8)</span></a> now, + when the owner/group is modified, print the old and new + uid/gid if the <tt class="OPTION">-v</tt> option is + specified more than once.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> now + implements a <tt class="LITERAL">nodevice</tt> kernel + configuration file directive that cancels the effect of a + <tt class="LITERAL">device</tt> directive. The new <tt + class="LITERAL">nooption</tt> and <tt + class="LITERAL">nomakeoption</tt> directives cancel prior + <tt class="LITERAL">options</tt> and <tt + class="LITERAL">makeoptions</tt> directives, + respectively.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=diskinfo&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">diskinfo</span>(8)</span></a> + utility has been added to show information about a disk + device and optionally to run a naive performance + test.</p> + + <p>The disklabel utility has been replaced by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>. On + the alpha, i386, and pc98 platforms, disklabel is a link + to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dump</span>(8)</span></a> now + supports caching of disk blocks with the <tt + class="OPTION">-C</tt> option. This can improve dump + performance at the cost of possibly missing file system + updates that occur between passes.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dumpfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dumpfs</span>(8)</span></a> now + supports a <tt class="OPTION">-m</tt> flag to print file + system parameters in the form of a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> + command.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elfdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elfdump</span>(1)</span></a>, a + utility to display information about <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elf</span>(5)</span></a> format + executable files, has been added.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(1)</span></a> uses the + <tt class="FILENAME">.netrc</tt> support in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> and also + supports a <tt class="OPTION">-N</tt> to specify an + alternate <tt class="FILENAME">.netrc</tt> file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> now has + support for <tt class="FILENAME">.netrc</tt> files (see + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftp</span>(1)</span></a> for more + details).</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-h</tt> option to disable + printing any host-specific information, such as the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> version + or hostname, in server messages. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-P</tt> option to specify a + port on which to listen in daemon mode. The default data + port number is now set to be one less than the control + port number, rather than being hard-coded. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports an extended format of the <tt + class="FILENAME">/etc/ftpchroot</tt> file. Please refer + to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> + manpage, which is now available, for details. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports login directory pathnames that specify + simultaneously a directory for <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> and + that to change to in the chrooted environment. The <tt + class="LITERAL">/./</tt> separator is used for this + purpose, like in other FTP daemons having this feature. + It may be used in both <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=passwd&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">passwd</span>(5)</span></a>. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fwcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fwcontrol</span>(8)</span></a> now + supports <tt class="OPTION">-R</tt> and <tt + class="OPTION">-S</tt> options for receiving and sending + DV streams. [MERGED]</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gstat</span>(8)</span></a> utility + has been added to show the disk activity inside the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(8)</span></a> now + supports <tt class="LITERAL">enable</tt> and <tt + class="LITERAL">disable</tt> commands to control various + aspects of the operation of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> + (including enabling and disabling the firewall itself). + These provide a more convenient and visible interface + than the existing sysctl variables. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jail</span>(8)</span></a> now + supports a <tt class="OPTION">-i</tt> flag to output an + identifier for a newly-created jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jexec&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jexec</span>(8)</span></a> utility + has been added to execute a command inside an existing + jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jls&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jls</span>(8)</span></a> utility + has been added to list existing jails.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kenv&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kenv</span>(1)</span></a> has been + moved from <tt class="FILENAME">/usr/bin</tt> to <tt + class="FILENAME">/bin</tt> to make it available at times + during system startup when only the root file system is + mounted.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=killall&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">killall</span>(1)</span></a> now + supports a <tt class="OPTION">-j</tt> option to kill all + processes inside a jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libgeom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libgeom</span>(3)</span></a> + library has been added to allow some userland access to + the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p>The mac_portacl MAC policy module has been added. It + provides a simple ACL mechanism to permit users and + groups to bind ports for TCP or UDP, and is intended to + be used in conjunction with the recently-added <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl.</p> + + <p>The <tt class="FILENAME">MAKEDEV</tt> script is now + unnecessary, due to the mandatory presence of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a>, and has + been removed.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a> + now supports a <tt class="OPTION">-P</tt> option to + preserve the contents of files being replaced.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mixer&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mixer</span>(8)</span></a> can now + implement relative volume adjustments.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mksnap_ffs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mksnap_ffs</span>(8)</span></a> + program has been added to allow easier creation of FFS + snapshots. It is a SUID-<tt class="USERNAME">root</tt> + executable designed for use by members of the <tt + class="GROUPNAME">operator</tt> group.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umount</span>(8)</span></a> now + accept a <tt class="OPTION">-F</tt> option to specify an + alternate <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstab&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstab</span>(5)</span></a> + file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports a <tt class="OPTION">-c</tt> flag to avoid doing + a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=connect&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">connect</span>(2)</span></a> for + UDP mount points. This option must be used if the server + does not reply to requests from the standard NFS port + number 2049 or if it replies to requests using a + different IP address (which can occur if the server is + multi-homed). Setting the <tt + class="VARNAME">vfs.nfs.nfs_ip_paranoia</tt> sysctl to + <tt class="LITERAL">0</tt> will make this option the + default. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports the <tt class="OPTION">noinet4</tt> and <tt + class="OPTION">noinet6</tt> mount options to prevent NFS + mounts from using IPv4 or IPv6 respectively.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> will now + create UFS2 file systems by default, unless UFS1 is + specifically requested with the <tt + class="OPTION">-O1</tt> option.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newsyslog&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newsyslog</span>(8)</span></a> has + a number of new features. Among them:</p> + + <ul> + <li> + <p>A <tt class="LITERAL">W</tt> flag forces + previously-started compression jobs for an entry (or + group of entries specified with the <tt + class="LITERAL">G</tt> flag) to finish before + beginning a new one. This feature is designed to + prevent system overloads caused by starting several + compression jobs on big files simultaneously. + [MERGED]</p> + </li> + + <li> + <p>A ``default rotate action'', to be used for files + specified for rotation but not specified in the + configuration file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="OPTION">-s</tt> command-line flag to + disable sending signals to processes when rotating + files. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">N</tt> configuration file + flag to indicate that no process needs to be signaled + when rotating a file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">U</tt> configuration file + flag to specify that a process group (rather than a + single process) should be signaled when rotating + files. [MERGED]</p> + </li> + </ul> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + now thread-safe and implements support for Name Service + Switch (NSS) modules. NSS modules may be statically built + into <tt class="FILENAME">libc</tt> or dynamically loaded + via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dlopen&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dlopen</span>(3)</span></a>. They + are loaded/initialized at configuration time (i.e. when + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + called and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsswitch.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsswitch.conf</span>(5)</span></a> + is read or re-read).</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_chroot&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_chroot</span>(8)</span></a> + module has been added, which does a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> + operation for users into either a predetermined directory + or one derived from their home directory.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_ssh&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_ssh</span>(8)</span></a> has + been rewritten. One side effect of the rewrite is that it + now starts a separate instance of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh-agent&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh-agent</span>(1)</span></a> for + each session instead of trying to connect each session to + the agent started by the first session.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-D</tt> flag to set the + ``Don't Fragment'' bit on outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-M</tt> option to use ICMP + mask request or timestamp request messages instead of + ICMP echo requests.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-z</tt> flag to set the + Type of Service bits in outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pw</span>(8)</span></a> can now add + a user whose name ends with a <tt class="LITERAL">$</tt> + character; this change is intended to help administration + of <b class="APPLICATION">Samba</b> services. + [MERGED]</p> + + <p>The format of the <tt + class="FILENAME">/etc/pwd.db</tt> and <tt + class="FILENAME">/etc/spwd.db</tt> password databases + created by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pwd_mkdb&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pwd_mkdb</span>(8)</span></a> is + now byte-order independent. The pre-processed password + databases can now be moved between machines of different + architectures. The format includes version numbers on + entries to ensure compatibility with old binaries.</p> + + <p>A bug in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> that + could cause a sequence to remain stuck at <tt + class="LITERAL">0</tt> has been fixed. (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> remains + unsuitable for all but trivial uses.)</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rtld&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rtld</span>(1)</span></a> now has + support for the dynamic mapping of shared object + dependencies. This optional feature is especially useful + when experimenting with different threading libraries. It + is not, however, built by default. More information on + enabling and using this feature can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libmap.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libmap.conf</span>(5)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_open&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_open</span>(3)</span></a> now + correctly handles multiple opens of the same semaphore; + as a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_close&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_close</span>(3)</span></a> no + longer crashes calling programs.</p> + + <p>The seeding algorithm used by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=srandom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">srandom</span>(3)</span></a> has + been strengthened.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + will now select UFS2 as the default layout for new file + systems unless specifically requested in the disk + labeler.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + command has been added to disable paging and swapping on + a device. A related <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapctl&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapctl</span>(8)</span></a> + command has been added to provide an interface to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapon&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapon</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + similar to other BSDs.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + feature should be considered experimental.</p> + </blockquote> + </div> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslogd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslogd</span>(8)</span></a> now + allows multiple hosts or programs to be named in host or + program specifications in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslog.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslog.conf</span>(5)</span></a> + files.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=systat&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">systat</span>(1)</span></a> now + includes an <tt class="OPTION">-ifstat</tt> display mode + that displays the network traffic going through active + interfaces on the system.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=usbhidaction&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">usbhidaction</span>(1)</span></a> + command has been added; it performs actions according to + its configuration in response to USB HID controls.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uudecode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uudecode</span>(1)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=b64decode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">b64decode</span>(1)</span></a> now + support a <tt class="OPTION">-r</tt> flag for decoding + raw (or broken) files that may be missing the initial and + possibly final framing lines. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vmstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vmstat</span>(8)</span></a> has + re-implemented the <tt class="OPTION">-f</tt> flag, which + displays statistics on fork operations.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-P</tt> option to execute + multiple copies of the same utility in parallel.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-o</tt> flag to reopen <tt + class="FILENAME">/dev/tty</tt> for the child process + before executing the command. This is useful when the + child process is an interactive application.</p> + + <p>The historic BSD boot scripts in <tt + class="FILENAME">/etc</tt> have been removed, in favor of + the <tt class="FILENAME">rc.d</tt> system imported from + <b class="APPLICATION">NetBSD</b> (sometimes referred to + as ``rcNG''). All functionality of the historic system + has been preserved. In particular, files such as <tt + class="FILENAME">/etc/rc.conf</tt> continue to be the + recommended means of configuring the system startup. The + <tt class="FILENAME">rc.d</tt> system has been the + default since FreeBSD 5.0-RELEASE, so this change should + be largely transparent for the vast majority of users. + Users who have customized their historic-style startup + scripts should be aware that the following files have + been removed from <tt class="FILENAME">/etc</tt>: <tt + class="FILENAME">rc.atm</tt>, <tt + class="FILENAME">rc.devfs</tt>, <tt + class="FILENAME">rc.diskless1</tt>, <tt + class="FILENAME">rc.diskless2</tt>, <tt + class="FILENAME">rc.i386</tt>, <tt + class="FILENAME">rc.alpha</tt>, <tt + class="FILENAME">rc.amd64</tt>, <tt + class="FILENAME">rc.ia64</tt>, <tt + class="FILENAME">rc.sparc64</tt>, <tt + class="FILENAME">rc.isdn</tt>, <tt + class="FILENAME">rc.network</tt>, <tt + class="FILENAME">rc.network6</tt>, <tt + class="FILENAME">rc.pccard</tt>, <tt + class="FILENAME">rc.serial</tt>, <tt + class="FILENAME">rc.syscons</tt>, <tt + class="FILENAME">rc.sysctl</tt>. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a>, + when run, will offer to move these files out of the way + for convenience. More details can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.subr&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rc.subr</span>(8)</span></a>.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="CONTRIB" name="CONTRIB">2.4 + Contributed Software</a></h2> + + <p>The <b class="APPLICATION">ACPI-CA</b> code has been + updated from the 20021118 snapshot to the 20030228 + snapshot.</p> + + <p><b class="APPLICATION">awk</b> from Bell Labs has been + updated to a 14 March 2003 snapshot.</p> + + <p><b class="APPLICATION">BIND</b> has been updated to + version 8.3.4. [MERGED]</p> + + <p>All of the <b class="APPLICATION">bzip2</b> suite of + applications is now installed in the base system (in + particular, <tt class="COMMAND">bzip2recover</tt> is now + built and installed). [MERGED]</p> + + <p><b class="APPLICATION">CVS</b> has been updated to + 1.11.5. [MERGED]</p> + + <p><b class="APPLICATION">FILE</b> has been updated to + 3.41. [MERGED]</p> + + <p><b class="APPLICATION">GCC</b> has been updated to + 3.2.2 (release version).</p> + + <p>The <b class="APPLICATION">gdtoa</b> library, for + conversions between strings and floating point, has been + imported. These sources were dated 24 March 2003.</p> + + <p><b class="APPLICATION">groff</b> (and related + utilities) have been updated from 1.18.1 to 1.19.</p> + + <p><b class="APPLICATION">IPFilter</b> has been updated + to 3.4.31. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client has + been updated to 3.0.1RC11. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client now + includes the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=omshell&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">omshell</span>(1)</span></a> + utility and the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dhcpctl&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dhcpctl</span>(3)</span></a> + library for run-time control of the client.</p> + + <p><b class="APPLICATION">Kerberos IV</b> support (in the + form of <b class="APPLICATION">KTH eBones</b>) has been + removed. Users requiring this functionality can still get + it from the <tt class="FILENAME">security/krb4</tt> port + (or package). Kerberos IV compatibility mode for Kerberos + 5 has been removed, and the <tt class="LITERAL">k5<tt + class="REPLACEABLE"><i>program</i></tt></tt> userland + utilities have been renamed to <tt class="LITERAL">k<tt + class="REPLACEABLE"><i>program</i></tt></tt>.</p> + + <p><b class="APPLICATION">Kerberos 5</b> is now built by + default in <tt class="LITERAL">buildworld</tt> + operations. Setting <tt + class="VARNAME">MAKE_KERBEROS5</tt> no longer has any + effect. Disabling the base system Kerberos 5 now requires + the <tt class="VARNAME">NO_KERBEROS</tt> Makefile + variable to be set.</p> + + <p><b class="APPLICATION">libpcap</b> now has support for + selecting among multiple data link types on an + interface.</p> + + <p><b class="APPLICATION">lukemftpd</b> (not built or + installed by default) has been updated to a snapshot from + 22 January 2003.</p> + + <p><b class="APPLICATION">OpenPAM</b> has been updated + from the ``Citronella'' release to the ``Dianthus'' + release.</p> + + <p><b class="APPLICATION">OpenSSH</b> has been updated to + 3.6.1p1.</p> + + <p><b class="APPLICATION">OpenSSL</b> has been updated to + release 0.9.7a. Among other features, this release + includes support for AES and takes advantage of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=crypto&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">crypto</span>(4)</span></a> + devices. [MERGED]</p> + + <p><b class="APPLICATION">sendmail</b> has been updated + to version 8.12.9. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcpdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcpdump</span>(1)</span></a> has + been updated to version 3.7.2. [MERGED] It also now + supports a <tt class="OPTION">-L</tt> flag to list the + data link types available on an interface and a <tt + class="OPTION">-y</tt> option to specify the data link + type to use while capturing packets.</p> + + <p><b class="APPLICATION">texinfo</b> has been updated + from 4.2 to 4.5.</p> + + <p>The timezone database has been updated from <tt + class="FILENAME">tzdata2002d</tt> to <tt + class="FILENAME">tzdata2003a</tt>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="PORTS" name="PORTS">2.5 + Ports/Packages Collection Infrastructure</a></h2> + + <p>The one-line <tt class="FILENAME">pkg-comment</tt> + files have been eliminated from each port skeleton; their + contents have been moved into each port's <tt + class="FILENAME">Makefile</tt>. This change reduces the + disk space and inodes used by the ports tree. + [MERGED]</p> + + <p>When fetching distfiles for building a port, the <tt + class="VARNAME">FETCH_REGET</tt> <tt + class="FILENAME">Makefile</tt> variable can be used to + specify the number of times to try continuing to fetch a + distfile if it fails its MD5 checksum. The port + infrastructure also supports re-fetching interrupted + distfiles.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_create</span>(1)</span></a> now + supports a <tt class="OPTION">-C</tt> option, which + allows packages to register a list of other packages with + which they conflict. They will refuse to install (via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a>) if + one of the listed packages is already present. The <tt + class="OPTION">-f</tt> flag to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a> + overrides this conflict-checking.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + honors the <tt class="VARNAME">BLOCKSIZE</tt> environment + variable in its output when the <tt + class="OPTION">-b</tt> flag is given.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + implements a <tt class="OPTION">-Q</tt> option, which is + similar to the <tt class="OPTION">-q</tt> ``quiet'' + option except that it prefixes the output with the + package name.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="RELENG" name="RELENG">2.6 + Release Engineering and Integration</a></h2> + + <p>The supported release of <b + class="APPLICATION">GNOME</b> has been updated to 2.2.1. + [MERGED]</p> + + <p>The supported release of <b + class="APPLICATION">KDE</b> has been updated to 3.1.2. + [MERGED]</p> + + <p>There is no longer a separate <tt + class="FILENAME">krb5</tt> distribution. The Kerberos 5 + libraries and utilities have been incorporated into the + <tt class="FILENAME">crypto</tt> distribution.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + once again supports installing individual components of + <b class="APPLICATION">XFree86</b>. Supporting changes + (not user-visible) generalize the concept of installing + parts of distributions as packages.</p> + + <p>The supported release of <b + class="APPLICATION">XFree86</b> has been updated to + 4.3.0. [MERGED]</p> + + <p>Several upgrade mechanisms designed to permit major + version upgrades from FreeBSD 2.<tt + class="REPLACEABLE"><i>X</i></tt> to 3.<tt + class="REPLACEABLE"><i>X</i></tt> and from FreeBSD 3.<tt + class="REPLACEABLE"><i>X</i></tt> to 4.<tt + class="REPLACEABLE"><i>X</i></tt> have been removed.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="DOC" name="DOC">2.7 + Documentation</a></h2> + + <p>The following new articles have been added to the + documentation set: ``FreeBSD From Scratch'', ``The + Roadmap for 5-STABLE''.</p> + + <p>A new Danish (<tt + class="FILENAME">da_DK.ISO8859-1</tt>) translation + project has been started.</p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 + Upgrading from previous releases of FreeBSD</a></h1> + + <p>Users with existing FreeBSD systems are <span + class="emphasis"><i class="EMPHASIS">highly</i></span> + encouraged to read the ``Early Adopter's Guide to FreeBSD + 5.1-RELEASE''. This document generally has the filename <tt + class="FILENAME">EARLY.TXT</tt> on the distribution media, + or any other place that the release notes can be found. It + offers some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> versus + running FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Upgrading FreeBSD should, of + course, only be attempted after backing up <span + class="emphasis"><i class="EMPHASIS">all</i></span> + data and configuration files.</p> + </blockquote> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-i386.html b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-i386.html new file mode 100644 index 0000000000..4cb9c05fef --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-i386.html @@ -0,0 +1,1740 @@ +<!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/i386 5.1-RELEASE Release 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 id="AEN2" name="AEN2">FreeBSD/i386 + 5.1-RELEASE Release Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + + <p class="PUBDATE">$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.573 2003/05/28 21:01:22 hrs Exp $<br /> + </p> + + <div> + <div class="ABSTRACT"> + <a id="AEN12" name="AEN12"></a> + + <p>The release notes for FreeBSD 5.1-RELEASE contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. This + document lists applicable security advisories that were + issued since the last release, as well as significant + changes to the FreeBSD kernel and userland. Some brief + remarks on upgrading are also presented.</p> + </div> + </div> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#NEW">What's New</a></dt> + + <dd> + <dl> + <dt>2.1 <a href="#SECURITY">Security + Advisories</a></dt> + + <dt>2.2 <a href="#KERNEL">Kernel Changes</a></dt> + + <dd> + <dl> + <dt>2.2.1 <a href="#PROC">Processor/Motherboard + Support</a></dt> + + <dt>2.2.2 <a href="#BOOT">Boot Loader + Changes</a></dt> + + <dt>2.2.3 <a href="#NET-IF">Network Interface + Support</a></dt> + + <dt>2.2.4 <a href="#NET-PROTO">Network + Protocols</a></dt> + + <dt>2.2.5 <a href="#DISKS">Disks and + Storage</a></dt> + + <dt>2.2.6 <a href="#FS">File Systems</a></dt> + + <dt>2.2.7 <a href="#PCCARD">PCCARD + Support</a></dt> + + <dt>2.2.8 <a href="#MM">Multimedia + Support</a></dt> + </dl> + </dd> + + <dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + + <dt>2.4 <a href="#CONTRIB">Contributed + Software</a></dt> + + <dt>2.5 <a href="#PORTS">Ports/Packages Collection + Infrastructure</a></dt> + + <dt>2.6 <a href="#RELENG">Release Engineering and + Integration</a></dt> + + <dt>2.7 <a href="#DOC">Documentation</a></dt> + </dl> + </dd> + + <dt>3 <a href="#UPGRADE">Upgrading from previous releases + of FreeBSD</a></dt> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the release notes for FreeBSD + 5.1-RELEASE on the i386 hardware platform. It describes + recently added, changed, or deleted features of FreeBSD. It + also provides some notes on upgrading from previous + versions of FreeBSD.</p> + + <p>This distribution of FreeBSD 5.1-RELEASE is a release + distribution. It can be found at <a + href="ftp://ftp.FreeBSD.org/" + target="_top">ftp://ftp.FreeBSD.org/</a> or any of its + mirrors. More information on obtaining this (or other) + release distributions of FreeBSD can be found in the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html" + target="_top">``Obtaining FreeBSD'' appendix</a> to the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" + target="_top">FreeBSD Handbook</a>.</p> + + <p>Users who are new to the 5-CURRENT series of FreeBSD + releases should also read the ``Early Adopters Guide to + FreeBSD 5.1-RELEASE''. This document can generally be found + in the same location as the release notes (either as a part + of a FreeBSD distribution or on the FreeBSD Web site). It + contains important information regarding the advantages and + disadvantages of using FreeBSD 5.1-RELEASE, as opposed to + releases based on the FreeBSD 4-STABLE development + branch.</p> + + <p>All users are encouraged to consult the release errata + before installing FreeBSD. The errata document is updated + with ``late-breaking'' information discovered late in the + release cycle or after the release. Typically, it contains + information on known bugs, security advisories, and + corrections to documentation. An up-to-date copy of the + errata for FreeBSD 5.1-RELEASE can be found on the FreeBSD + Web site.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="NEW" name="NEW">2 What's + New</a></h1> + + <p>This section describes many of the user-visible new or + changed features in FreeBSD since 5.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 5.0-RELEASE). The latter items are + marked as [MERGED].</p> + + <p>Typical release note items document recent security + advisories issued after 5.0-RELEASE, new drivers or + hardware support, new commands or options, major bug fixes, + or contributed software upgrades. They may also list + changes to major ports/packages or release engineering + practices. Clearly the release notes cannot list every + single change made to FreeBSD between releases; this + document focuses primarily on security advisories, + user-visible changes, and major architectural + improvements.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 + Security Advisories</a></h2> + + <p>A remotely exploitable vulnerability in <b + class="APPLICATION">CVS</b> has been corrected with the + import of version 1.11.5. More details can be found in + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:01.cvs.asc" + target="_top">FreeBSD-SA-03:01</a>. [MERGED]</p> + + <p>A timing-based attack on <b + class="APPLICATION">OpenSSL</b>, which could allow a very + powerful attacker access to plaintext under certain + circumstances, has been prevented via an upgrade to <b + class="APPLICATION">OpenSSL</b> 0.9.7. See security + advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:02.openssl.asc" + target="_top">FreeBSD-SA-03:02</a> for more details. + [MERGED]</p> + + <p>The security and performance of the ``syncookies'' + feature has been improved to decrease the chance of an + attacker being able to spoof connections. More details + are given in security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:03.syncookies.asc" + target="_top">FreeBSD-SA-03:03</a>. [MERGED]</p> + + <p>Remotely-exploitable buffer overflow vulnerabilities + in <b class="APPLICATION">sendmail</b> have been fixed by + updating <b class="APPLICATION">sendmail</b>. For more + details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:04.sendmail.asc" + target="_top">FreeBSD-SA-03:04</a> and <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:07.sendmail.asc" + target="_top">FreeBSD-SA-03:07</a>. [MERGED]</p> + + <p>A bounds-checking bug in the XDR implementation, which + could allow a remote attacker to cause a + denial-of-service, has been fixed. For more details see + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:05.xdr.asc" + target="_top">FreeBSD-SA-03:05</a>. [MERGED]</p> + + <p>Two recently-publicized flaws in <b + class="APPLICATION">OpenSSL</b> have been corrected. For + more details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:06.openssl.asc" + target="_top">FreeBSD-SA-03:06</a>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel + Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a> is now + mandatory; the <tt class="LITERAL">NODEVFS</tt> option + has been removed from the set of possible kernel + configuration options.</p> + + <p>An <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ehci</span>(4)</span></a> driver + has been added; it supports the USB Enhanced Host + Controller Interface used by USB 2.0 controllers.</p> + + <p>A minor bug in the permissions handling of <tt + class="FILENAME">/dev/tty</tt> has been fixed. As a + result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh</span>(1)</span></a> can now be + used after <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=su&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">su</span>(1)</span></a>.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstat</span>(2)</span></a> to + return <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kqueue&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kqueue</span>(2)</span></a> to + report <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed. The + <tt class="LITERAL">NOTE_LOWAT</tt> flag for <tt + class="LITERAL">EVFILT_READ</tt> has been fixed.</p> + + <p>Linux emulation mode now supports IPv6.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=madvise&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">madvise</span>(2)</span></a> now + supports a <tt class="LITERAL">MADV_PROTECT</tt> + behavior, which informs the virtual memory system that a + process is critical and should not be killed when swap + space has been exhausted. The process must be owned by + the superuser.</p> + + <p>The tw driver for TW-523 power line interfaces (used + by X-10 home control products) has been removed. It is + currently non-functional, and would require a + considerable amount of work to make it work under + 5-CURRENT. The xten and xtend userland control programs + have also been removed.</p> + + <p>A second process scheduler, designed to be a general + purpose scheduler with many SMP benefits, has been added + to the scheduler framework. Exactly one scheduler must be + specified in a kernel configuration. The original + scheduler may be selected using <tt + class="LITERAL">options SCHED_4BSD</tt>. The newer + (experimental) scheduler can be selected by using <tt + class="LITERAL">options SCHED_ULE</tt>.</p> + + <p>Device major numbers are now allocated dynamically by + default. This change greatly decreases the need for a + static, centralized table of major number assignments to + device drivers (a few drivers retain their old static + major numbers for compatibility), and also reduces the + possibility of running out of device major numbers.</p> + + <p>A partial lazy switch mechanism for in-kernel threads + has been implemented; it is designed to reduce the + overhead of short context switches (such as for interrupt + handlers) that do not involve another process. This + feature can be enabled with <tt + class="LITERAL">options LAZY_SWITCH</tt>.</p> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PROC" name="PROC">2.2.1 + Processor/Motherboard Support</a></h3> + + <p><tt class="LITERAL">SMP</tt> kernels now have + rudimentary support for HyperThreading (HTT). The + scheduler treats the logical CPUs as if they were + additional physical CPUs. This can actually cause + suboptimal performance in some cases due to contention + for resources. Therefore, logical CPUs are halted by + default at startup. They can be enabled with the <tt + class="VARNAME">machdep.hlt_logical_cpus</tt> sysctl + variable. It is also possible to halt any CPU in the + idle loop with the <tt + class="VARNAME">machdep.hlt_cpus</tt> sysctl variable. + The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=smp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">smp</span>(4)</span></a> manual + page has more details.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Some other versions of FreeBSD, + including early 5.0-CURRENT snapshots and + 4.8-RELEASE, used <tt + class="LITERAL">options HTT</tt> to enable + HyperThreading support at kernel configuration + time. This option is no longer necessary.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Support for the Physical Address Extensions (PAE) + capability on Intel Pentium Pro and higher processors + has been added. This allows the use of up to 64GB of + RAM in a machine, although the amount of memory usable + by any single process (or the FreeBSD kernel) is + unchanged. For more information, see the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pae&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pae</span>(4)</span></a> manual + page. Work on this feature was sponsored by DARPA and + Network Associates Laboratories.</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vpd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vpd</span>(4)</span></a> driver + has been added to read hardware information from the + Vital Product Data structure on IBM ThinkPad + machines.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="BOOT" name="BOOT">2.2.2 Boot + Loader Changes</a></h3> + + <p>The two parts of the boot loader (<tt + class="FILENAME">boot1</tt> and <tt + class="FILENAME">boot2</tt>) have been combined into a + single <tt class="FILENAME">boot</tt> file, to simplify + programs that need to write or otherwise manipulate the + boot loader.</p> + + <p>The <tt class="FILENAME">/modules</tt> directory + (once the default location for modules on FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>) is no longer a part + of the default <tt + class="VARNAME">kern.module_path</tt>. Third-party + modules should be placed in <tt + class="FILENAME">/boot/modules</tt>.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Modules designed for use with + FreeBSD 4.<tt class="REPLACEABLE"><i>X</i></tt> are + likely to panic when loaded into a FreeBSD + 5.1-RELEASE kernel and should be used with extreme + caution.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>Due to code size limitations, the i386 boot loader + can only load kernels from root file systems that are + 1.5TB or smaller in size.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-IF" name="NET-IF">2.2.3 + Network Interface Support</a></h3> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">axe</span>(4)</span></a> network + driver has been added. It provides support for USB + Ethernet adapters based on the ASIX Electronics AX88172 + USB 2.0 chipset.</p> + + <p>The cm driver now supports IPX. [MERGED]</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rue</span>(4)</span></a> network + driver has been added, providing support for Ethernet + adapters based on the RealTek RTL8150 USB to Fast + Ethernet controller chip.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sbsh&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sbsh</span>(4)</span></a> driver + for the Granch SBNI16 SHDSL modem has been added. + [MERGED]</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wlan&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wlan</span>(4)</span></a> module + provides 802.11 link-layer support. The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wi</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">an</span>(4)</span></a> drivers + now use this facility.</p> + + <p>A timing bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xl</span>(4)</span></a> driver, + which could cause a kernel panic (or other problems) + when configuring an interface, has been fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-PROTO" + name="NET-PROTO">2.2.4 Network Protocols</a></h3> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">skipto</tt> rules can once again be + used with the <tt class="LITERAL">log</tt> keyword. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">uid</tt> rules are once again + working.</p> + + <p>It is now possible to build the <tt + class="LITERAL">FAST_IPSEC</tt> and <tt + class="LITERAL">INET6</tt> options into the same + kernel. (They still cannot be used together, + however.)</p> + + <p>A bug in TCP NewReno, which caused premature exit + from fast recovery when NewReno was enabled, has been + fixed. [MERGED]</p> + + <p>TCP now has support for the ``Limited Transmit'' + mechanism proposed by RFC 3042. This feature is + intended to improve the effectiveness of TCP loss + recovery in certain circumstances. It is off by default + but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3042</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>TCP now has support for increased initial congestion + window sizes as described in RFC 3390. This feature can + improve the throughput of short transfers, as well as + high-bandwidth, large propagation-delay connections. It + is off by default but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3390</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>The IP fragment reassembly code behaves more + gracefully when receiving a large number of packet + fragments (it is designed to be more resistant to + fragment-based denial of service attacks). [MERGED]</p> + + <p>TCP connections in the <tt + class="LITERAL">TIME_WAIT</tt> state now use a special + protocol control block that uses less space than a + full-blown TCP PCB. This allows some of the data + structures and resources used by such a connection to + be freed earlier.</p> + + <p>It is now possible to specify the range of + ``privileged ports'' (TCP and UDP ports that require + superuser access to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bind&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bind</span>(2)</span></a> to). + The range is now specified with the <tt + class="VARNAME">net.inet.ip.portrange.reservedlow</tt> + and <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl variables, defaulting to the traditional UNIX + behavior. This feature is intended to help network + servers bind to traditionally privileged ports without + requiring superuser access. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ip&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ip</span>(4)</span></a> has more + details.</p> + + <p>Some bugs in the non-blocking RPC code has been + fixed. As a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amd</span>(8)</span></a> users + are now able to mount volumes from a 5.1-RELEASE + server.</p> + + <p>Support for XNS networking, which has not worked + correctly for almost seven years, has been removed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="DISKS" name="DISKS">2.2.5 + Disks and Storage</a></h3> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aac</span>(4)</span></a> driver + now runs free of the Giant kernel lock. This change has + given a nearly 20% performance speedup on an SMP system + running multiple I/O intensive loads.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports all known SiS chipsets. (More details can + be found in the Hardware Notes.)</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports the Promise SATA150 TX2 and TX4 Serial + ATA/150 controllers.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now flushes devices on shutdown. This change may result + in failure messages being printed on the console for + devices that do not support flushing.</p> + + <p>The CAM layer now has support for devices with more + than 2<sup>32</sup> blocks. (Assuming 512-byte blocks, + this means support for devices larger than 2TB.)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> For users upgrading across this + change, note that all userland applications that + talk to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pass&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pass</span>(4)</span></a> or + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xpt</span>(4)</span></a> + devices must be recompiled. Examples of such + programs are <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=camcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">camcontrol</span>(8)</span></a> + in the base system, the <tt + class="FILENAME">sysutils/cdrtools</tt> port, and + the <tt class="FILENAME">multimedia/xmms</tt> + port.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>A number of changes have been made to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a> driver. + The primary user-visible change is improved + compatibility with ATAPI/USB/Firewire CDROM drives.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> is now + mandatory; the <tt class="LITERAL">NO_GEOM</tt> has + been removed from the set of kernel configuration + options.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">iir</span>(4)</span></a> driver + has been updated; this update is believed to fix + problems detecting attached disks during + installation.</p> + + <p>The ips driver, which supports the IBM (now Adaptec) + ServeRAID series, has been added.</p> + + <p>A bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mly</span>(4)</span></a> driver + that caused hangs has been corrected.</p> + + <p>Support has been added for volume labels on UFS and + UFS2 file systems. These labels are strings that can be + used to identify a volume, regardless of what device it + appears on. Labels can be set with the <tt + class="OPTION">-L</tt> options to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> or <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tunefs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tunefs</span>(8)</span></a>. With + the <tt class="LITERAL">GEOM_VOL</tt> module, volumes + can be accessed using their labels under <tt + class="FILENAME">/dev/vol</tt>.</p> + + <p>The root file system can now be located on a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> + volume. More information can be found in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> manual + page.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="FS" name="FS">2.2.6 File + Systems</a></h3> + + <p>A new <tt class="LITERAL">DIRECTIO</tt> kernel + option enables support for read operations that bypass + the buffer cache and put data directly into a userland + buffer. This feature requires that the <tt + class="LITERAL">O_DIRECT</tt> flag is set on the file + descriptor and that both the offset and length for the + read operation are multiples of the physical media + sector size. [MERGED]</p> + + <p>NETNCP and Netware File System Support (nwfs) are + once again working.</p> + + <p>Bugs that could cause the unmounting of a smbfs + share to fail or cause a kernel panic have been + fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PCCARD" name="PCCARD">2.2.7 + PCCARD Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="MM" name="MM">2.2.8 Multimedia + Support</a></h3> + + <p>The <tt class="FILENAME">atspeaker.ko</tt> and <tt + class="FILENAME">pcspeaker.ko</tt> modules for the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=speaker&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">speaker</span>(4)</span></a> + device have been renamed <tt + class="FILENAME">speaker.ko</tt>.</p> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 + Userland Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + correctly handles setting user passwords containing + special shell characters.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + supports a <tt class="OPTION">-g</tt> option to set a + user's default login group.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> + utility is a replacement for the older disklabel utility. + Like its predecessor, it installs, examines, or modifies + the BSD label on a disk partition, and can install + bootstrap code. Compared to disklabel, a number of + obsolete options and parameters have been retired. A new + <tt class="OPTION">-m</tt> option instructs <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> to + use the layout suitable for a specific machine.</p> + + <p>The <tt class="FILENAME">compat4x</tt> distribution + now includes the <tt + class="FILENAME">libcrypto.so.2</tt>, <tt + class="FILENAME">libgmp.so.3</tt>, and <tt + class="FILENAME">libssl.so.2</tt> libraries from FreeBSD + 4.7-RELEASE.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chgrp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chgrp</span>(1)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chown&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chown</span>(8)</span></a> now, + when the owner/group is modified, print the old and new + uid/gid if the <tt class="OPTION">-v</tt> option is + specified more than once.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> now + implements a <tt class="LITERAL">nodevice</tt> kernel + configuration file directive that cancels the effect of a + <tt class="LITERAL">device</tt> directive. The new <tt + class="LITERAL">nooption</tt> and <tt + class="LITERAL">nomakeoption</tt> directives cancel prior + <tt class="LITERAL">options</tt> and <tt + class="LITERAL">makeoptions</tt> directives, + respectively.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=diskinfo&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">diskinfo</span>(8)</span></a> + utility has been added to show information about a disk + device and optionally to run a naive performance + test.</p> + + <p>The disklabel utility has been replaced by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>. On + the alpha, i386, and pc98 platforms, disklabel is a link + to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dump</span>(8)</span></a> now + supports caching of disk blocks with the <tt + class="OPTION">-C</tt> option. This can improve dump + performance at the cost of possibly missing file system + updates that occur between passes.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dumpfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dumpfs</span>(8)</span></a> now + supports a <tt class="OPTION">-m</tt> flag to print file + system parameters in the form of a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> + command.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elfdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elfdump</span>(1)</span></a>, a + utility to display information about <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elf</span>(5)</span></a> format + executable files, has been added.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(1)</span></a> uses the + <tt class="FILENAME">.netrc</tt> support in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> and also + supports a <tt class="OPTION">-N</tt> to specify an + alternate <tt class="FILENAME">.netrc</tt> file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> now has + support for <tt class="FILENAME">.netrc</tt> files (see + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftp</span>(1)</span></a> for more + details).</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-h</tt> option to disable + printing any host-specific information, such as the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> version + or hostname, in server messages. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-P</tt> option to specify a + port on which to listen in daemon mode. The default data + port number is now set to be one less than the control + port number, rather than being hard-coded. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports an extended format of the <tt + class="FILENAME">/etc/ftpchroot</tt> file. Please refer + to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> + manpage, which is now available, for details. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports login directory pathnames that specify + simultaneously a directory for <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> and + that to change to in the chrooted environment. The <tt + class="LITERAL">/./</tt> separator is used for this + purpose, like in other FTP daemons having this feature. + It may be used in both <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=passwd&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">passwd</span>(5)</span></a>. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fwcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fwcontrol</span>(8)</span></a> now + supports <tt class="OPTION">-R</tt> and <tt + class="OPTION">-S</tt> options for receiving and sending + DV streams. [MERGED]</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gstat</span>(8)</span></a> utility + has been added to show the disk activity inside the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(8)</span></a> now + supports <tt class="LITERAL">enable</tt> and <tt + class="LITERAL">disable</tt> commands to control various + aspects of the operation of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> + (including enabling and disabling the firewall itself). + These provide a more convenient and visible interface + than the existing sysctl variables. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jail</span>(8)</span></a> now + supports a <tt class="OPTION">-i</tt> flag to output an + identifier for a newly-created jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jexec&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jexec</span>(8)</span></a> utility + has been added to execute a command inside an existing + jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jls&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jls</span>(8)</span></a> utility + has been added to list existing jails.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kenv&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kenv</span>(1)</span></a> has been + moved from <tt class="FILENAME">/usr/bin</tt> to <tt + class="FILENAME">/bin</tt> to make it available at times + during system startup when only the root file system is + mounted.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=killall&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">killall</span>(1)</span></a> now + supports a <tt class="OPTION">-j</tt> option to kill all + processes inside a jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libgeom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libgeom</span>(3)</span></a> + library has been added to allow some userland access to + the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p>The mac_portacl MAC policy module has been added. It + provides a simple ACL mechanism to permit users and + groups to bind ports for TCP or UDP, and is intended to + be used in conjunction with the recently-added <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl.</p> + + <p>The <tt class="FILENAME">MAKEDEV</tt> script is now + unnecessary, due to the mandatory presence of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a>, and has + been removed.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a> + now supports a <tt class="OPTION">-P</tt> option to + preserve the contents of files being replaced.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mixer&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mixer</span>(8)</span></a> can now + implement relative volume adjustments.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mksnap_ffs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mksnap_ffs</span>(8)</span></a> + program has been added to allow easier creation of FFS + snapshots. It is a SUID-<tt class="USERNAME">root</tt> + executable designed for use by members of the <tt + class="GROUPNAME">operator</tt> group.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umount</span>(8)</span></a> now + accept a <tt class="OPTION">-F</tt> option to specify an + alternate <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstab&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstab</span>(5)</span></a> + file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports a <tt class="OPTION">-c</tt> flag to avoid doing + a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=connect&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">connect</span>(2)</span></a> for + UDP mount points. This option must be used if the server + does not reply to requests from the standard NFS port + number 2049 or if it replies to requests using a + different IP address (which can occur if the server is + multi-homed). Setting the <tt + class="VARNAME">vfs.nfs.nfs_ip_paranoia</tt> sysctl to + <tt class="LITERAL">0</tt> will make this option the + default. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports the <tt class="OPTION">noinet4</tt> and <tt + class="OPTION">noinet6</tt> mount options to prevent NFS + mounts from using IPv4 or IPv6 respectively.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> will now + create UFS2 file systems by default, unless UFS1 is + specifically requested with the <tt + class="OPTION">-O1</tt> option.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newsyslog&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newsyslog</span>(8)</span></a> has + a number of new features. Among them:</p> + + <ul> + <li> + <p>A <tt class="LITERAL">W</tt> flag forces + previously-started compression jobs for an entry (or + group of entries specified with the <tt + class="LITERAL">G</tt> flag) to finish before + beginning a new one. This feature is designed to + prevent system overloads caused by starting several + compression jobs on big files simultaneously. + [MERGED]</p> + </li> + + <li> + <p>A ``default rotate action'', to be used for files + specified for rotation but not specified in the + configuration file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="OPTION">-s</tt> command-line flag to + disable sending signals to processes when rotating + files. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">N</tt> configuration file + flag to indicate that no process needs to be signaled + when rotating a file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">U</tt> configuration file + flag to specify that a process group (rather than a + single process) should be signaled when rotating + files. [MERGED]</p> + </li> + </ul> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + now thread-safe and implements support for Name Service + Switch (NSS) modules. NSS modules may be statically built + into <tt class="FILENAME">libc</tt> or dynamically loaded + via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dlopen&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dlopen</span>(3)</span></a>. They + are loaded/initialized at configuration time (i.e. when + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + called and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsswitch.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsswitch.conf</span>(5)</span></a> + is read or re-read).</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_chroot&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_chroot</span>(8)</span></a> + module has been added, which does a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> + operation for users into either a predetermined directory + or one derived from their home directory.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_ssh&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_ssh</span>(8)</span></a> has + been rewritten. One side effect of the rewrite is that it + now starts a separate instance of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh-agent&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh-agent</span>(1)</span></a> for + each session instead of trying to connect each session to + the agent started by the first session.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-D</tt> flag to set the + ``Don't Fragment'' bit on outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-M</tt> option to use ICMP + mask request or timestamp request messages instead of + ICMP echo requests.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-z</tt> flag to set the + Type of Service bits in outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pw</span>(8)</span></a> can now add + a user whose name ends with a <tt class="LITERAL">$</tt> + character; this change is intended to help administration + of <b class="APPLICATION">Samba</b> services. + [MERGED]</p> + + <p>The format of the <tt + class="FILENAME">/etc/pwd.db</tt> and <tt + class="FILENAME">/etc/spwd.db</tt> password databases + created by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pwd_mkdb&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pwd_mkdb</span>(8)</span></a> is + now byte-order independent. The pre-processed password + databases can now be moved between machines of different + architectures. The format includes version numbers on + entries to ensure compatibility with old binaries.</p> + + <p>A bug in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> that + could cause a sequence to remain stuck at <tt + class="LITERAL">0</tt> has been fixed. (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> remains + unsuitable for all but trivial uses.)</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rtld&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rtld</span>(1)</span></a> now has + support for the dynamic mapping of shared object + dependencies. This optional feature is especially useful + when experimenting with different threading libraries. It + is not, however, built by default. More information on + enabling and using this feature can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libmap.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libmap.conf</span>(5)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_open&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_open</span>(3)</span></a> now + correctly handles multiple opens of the same semaphore; + as a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_close&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_close</span>(3)</span></a> no + longer crashes calling programs.</p> + + <p>The seeding algorithm used by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=srandom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">srandom</span>(3)</span></a> has + been strengthened.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + will now select UFS2 as the default layout for new file + systems unless specifically requested in the disk + labeler.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Due to i386 boot loader limitations, + the root file system must be 1.5TB or smaller in + size.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + command has been added to disable paging and swapping on + a device. A related <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapctl&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapctl</span>(8)</span></a> + command has been added to provide an interface to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapon&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapon</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + similar to other BSDs.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + feature should be considered experimental.</p> + </blockquote> + </div> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslogd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslogd</span>(8)</span></a> now + allows multiple hosts or programs to be named in host or + program specifications in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslog.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslog.conf</span>(5)</span></a> + files.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=systat&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">systat</span>(1)</span></a> now + includes an <tt class="OPTION">-ifstat</tt> display mode + that displays the network traffic going through active + interfaces on the system.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=usbhidaction&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">usbhidaction</span>(1)</span></a> + command has been added; it performs actions according to + its configuration in response to USB HID controls.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uudecode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uudecode</span>(1)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=b64decode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">b64decode</span>(1)</span></a> now + support a <tt class="OPTION">-r</tt> flag for decoding + raw (or broken) files that may be missing the initial and + possibly final framing lines. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vmstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vmstat</span>(8)</span></a> has + re-implemented the <tt class="OPTION">-f</tt> flag, which + displays statistics on fork operations.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-P</tt> option to execute + multiple copies of the same utility in parallel.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-o</tt> flag to reopen <tt + class="FILENAME">/dev/tty</tt> for the child process + before executing the command. This is useful when the + child process is an interactive application.</p> + + <p>The <tt class="FILENAME">libkse</tt> library, + providing POSIX threading support using KSE, is now + enabled and installed by default. This library currently + supports M:N threading. Both process and system scope + threads are supported, as well as getting/setting the + concurrency level. By default, the library sets the + concurrency level to the number of CPUs in the system. + Each concurrency level correlates to a KSE, and all + process scope threads run in these KSEs. Each system + scope thread gets its own KSE in addition to those + corresponding to concurrency levels. <tt + class="FILENAME">libkse</tt> is still considered a + work-in-progress, and is not used by default. However, it + can be used as a replacement for the <tt + class="FILENAME">libc_r</tt> thread library, by + substituting <tt class="OPTION">-lkse</tt> instead of <tt + class="OPTION">-pthread</tt> when linking programs.</p> + + <p>A 1:1 threading package (where for every pthread in an + application there is one KSE and thread) has been + implemented. Under this model, the kernel handles all + thread scheduling decisions and all signal delivery. This + uses some of the common KSE code, and is a restricted + case of the M:N threading work still in progress. The <tt + class="FILENAME">libthr</tt> library implementing the + userland portion of this functionality is a drop-in + replacement for the <tt class="FILENAME">libc_r</tt> + library. Note that <tt class="FILENAME">libthr</tt> is + not (at this time) built by default.</p> + + <p>The historic BSD boot scripts in <tt + class="FILENAME">/etc</tt> have been removed, in favor of + the <tt class="FILENAME">rc.d</tt> system imported from + <b class="APPLICATION">NetBSD</b> (sometimes referred to + as ``rcNG''). All functionality of the historic system + has been preserved. In particular, files such as <tt + class="FILENAME">/etc/rc.conf</tt> continue to be the + recommended means of configuring the system startup. The + <tt class="FILENAME">rc.d</tt> system has been the + default since FreeBSD 5.0-RELEASE, so this change should + be largely transparent for the vast majority of users. + Users who have customized their historic-style startup + scripts should be aware that the following files have + been removed from <tt class="FILENAME">/etc</tt>: <tt + class="FILENAME">rc.atm</tt>, <tt + class="FILENAME">rc.devfs</tt>, <tt + class="FILENAME">rc.diskless1</tt>, <tt + class="FILENAME">rc.diskless2</tt>, <tt + class="FILENAME">rc.i386</tt>, <tt + class="FILENAME">rc.alpha</tt>, <tt + class="FILENAME">rc.amd64</tt>, <tt + class="FILENAME">rc.ia64</tt>, <tt + class="FILENAME">rc.sparc64</tt>, <tt + class="FILENAME">rc.isdn</tt>, <tt + class="FILENAME">rc.network</tt>, <tt + class="FILENAME">rc.network6</tt>, <tt + class="FILENAME">rc.pccard</tt>, <tt + class="FILENAME">rc.serial</tt>, <tt + class="FILENAME">rc.syscons</tt>, <tt + class="FILENAME">rc.sysctl</tt>. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a>, + when run, will offer to move these files out of the way + for convenience. More details can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.subr&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rc.subr</span>(8)</span></a>.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="CONTRIB" name="CONTRIB">2.4 + Contributed Software</a></h2> + + <p>The <b class="APPLICATION">ACPI-CA</b> code has been + updated from the 20021118 snapshot to the 20030228 + snapshot.</p> + + <p><b class="APPLICATION">awk</b> from Bell Labs has been + updated to a 14 March 2003 snapshot.</p> + + <p><b class="APPLICATION">BIND</b> has been updated to + version 8.3.4. [MERGED]</p> + + <p>All of the <b class="APPLICATION">bzip2</b> suite of + applications is now installed in the base system (in + particular, <tt class="COMMAND">bzip2recover</tt> is now + built and installed). [MERGED]</p> + + <p><b class="APPLICATION">CVS</b> has been updated to + 1.11.5. [MERGED]</p> + + <p>The <b class="APPLICATION">DRM</b> kernel modules have + been updated to a snapshot from the DRI CVS repository, + as of 24 April 2003. The <tt + class="LITERAL">DRM_LINUX</tt> kernel option hsa been + removed because the handler is now provided by the Linux + compatibility code.</p> + + <p><b class="APPLICATION">FILE</b> has been updated to + 3.41. [MERGED]</p> + + <p><b class="APPLICATION">GCC</b> has been updated to + 3.2.2 (release version).</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> <b class="APPLICATION">GCC</b> is + known to produce broken code with the <tt + class="OPTION">-march=pentium4</tt> option set. As a + workaround to avoid this problem, setting the <tt + class="VARNAME">CPUTYPE=p4</tt> Makefile variable + (for example, in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=make.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">make.conf</span>(5)</span></a>) + enables GCC's <tt class="OPTION">-march=pentium3</tt> + option instead. This situation is expected to be + resolved when GCC 3.3 is imported.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>The <b class="APPLICATION">gdtoa</b> library, for + conversions between strings and floating point, has been + imported. These sources were dated 24 March 2003.</p> + + <p><b class="APPLICATION">groff</b> (and related + utilities) have been updated from 1.18.1 to 1.19.</p> + + <p><b class="APPLICATION">IPFilter</b> has been updated + to 3.4.31. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client has + been updated to 3.0.1RC11. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client now + includes the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=omshell&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">omshell</span>(1)</span></a> + utility and the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dhcpctl&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dhcpctl</span>(3)</span></a> + library for run-time control of the client.</p> + + <p><b class="APPLICATION">Kerberos IV</b> support (in the + form of <b class="APPLICATION">KTH eBones</b>) has been + removed. Users requiring this functionality can still get + it from the <tt class="FILENAME">security/krb4</tt> port + (or package). Kerberos IV compatibility mode for Kerberos + 5 has been removed, and the <tt class="LITERAL">k5<tt + class="REPLACEABLE"><i>program</i></tt></tt> userland + utilities have been renamed to <tt class="LITERAL">k<tt + class="REPLACEABLE"><i>program</i></tt></tt>.</p> + + <p><b class="APPLICATION">Kerberos 5</b> is now built by + default in <tt class="LITERAL">buildworld</tt> + operations. Setting <tt + class="VARNAME">MAKE_KERBEROS5</tt> no longer has any + effect. Disabling the base system Kerberos 5 now requires + the <tt class="VARNAME">NO_KERBEROS</tt> Makefile + variable to be set.</p> + + <p><b class="APPLICATION">libpcap</b> now has support for + selecting among multiple data link types on an + interface.</p> + + <p><b class="APPLICATION">lukemftpd</b> (not built or + installed by default) has been updated to a snapshot from + 22 January 2003.</p> + + <p><b class="APPLICATION">OpenPAM</b> has been updated + from the ``Citronella'' release to the ``Dianthus'' + release.</p> + + <p><b class="APPLICATION">OpenSSH</b> has been updated to + 3.6.1p1.</p> + + <p><b class="APPLICATION">OpenSSL</b> has been updated to + release 0.9.7a. Among other features, this release + includes support for AES and takes advantage of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=crypto&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">crypto</span>(4)</span></a> + devices. [MERGED]</p> + + <p><b class="APPLICATION">sendmail</b> has been updated + to version 8.12.9. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcpdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcpdump</span>(1)</span></a> has + been updated to version 3.7.2. [MERGED] It also now + supports a <tt class="OPTION">-L</tt> flag to list the + data link types available on an interface and a <tt + class="OPTION">-y</tt> option to specify the data link + type to use while capturing packets.</p> + + <p><b class="APPLICATION">texinfo</b> has been updated + from 4.2 to 4.5.</p> + + <p>The timezone database has been updated from <tt + class="FILENAME">tzdata2002d</tt> to <tt + class="FILENAME">tzdata2003a</tt>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="PORTS" name="PORTS">2.5 + Ports/Packages Collection Infrastructure</a></h2> + + <p>The one-line <tt class="FILENAME">pkg-comment</tt> + files have been eliminated from each port skeleton; their + contents have been moved into each port's <tt + class="FILENAME">Makefile</tt>. This change reduces the + disk space and inodes used by the ports tree. + [MERGED]</p> + + <p>When fetching distfiles for building a port, the <tt + class="VARNAME">FETCH_REGET</tt> <tt + class="FILENAME">Makefile</tt> variable can be used to + specify the number of times to try continuing to fetch a + distfile if it fails its MD5 checksum. The port + infrastructure also supports re-fetching interrupted + distfiles.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_create</span>(1)</span></a> now + supports a <tt class="OPTION">-C</tt> option, which + allows packages to register a list of other packages with + which they conflict. They will refuse to install (via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a>) if + one of the listed packages is already present. The <tt + class="OPTION">-f</tt> flag to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a> + overrides this conflict-checking.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + honors the <tt class="VARNAME">BLOCKSIZE</tt> environment + variable in its output when the <tt + class="OPTION">-b</tt> flag is given.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + implements a <tt class="OPTION">-Q</tt> option, which is + similar to the <tt class="OPTION">-q</tt> ``quiet'' + option except that it prefixes the output with the + package name.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="RELENG" name="RELENG">2.6 + Release Engineering and Integration</a></h2> + + <p>The supported release of <b + class="APPLICATION">GNOME</b> has been updated to 2.2.1. + [MERGED]</p> + + <p>The supported release of <b + class="APPLICATION">KDE</b> has been updated to 3.1.2. + [MERGED]</p> + + <p>There is no longer a separate <tt + class="FILENAME">krb5</tt> distribution. The Kerberos 5 + libraries and utilities have been incorporated into the + <tt class="FILENAME">crypto</tt> distribution.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + once again supports installing individual components of + <b class="APPLICATION">XFree86</b>. Supporting changes + (not user-visible) generalize the concept of installing + parts of distributions as packages.</p> + + <p>The supported release of <b + class="APPLICATION">XFree86</b> has been updated to + 4.3.0. [MERGED]</p> + + <p>Several upgrade mechanisms designed to permit major + version upgrades from FreeBSD 2.<tt + class="REPLACEABLE"><i>X</i></tt> to 3.<tt + class="REPLACEABLE"><i>X</i></tt> and from FreeBSD 3.<tt + class="REPLACEABLE"><i>X</i></tt> to 4.<tt + class="REPLACEABLE"><i>X</i></tt> have been removed.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="DOC" name="DOC">2.7 + Documentation</a></h2> + + <p>The following new articles have been added to the + documentation set: ``FreeBSD From Scratch'', ``The + Roadmap for 5-STABLE''.</p> + + <p>A new Danish (<tt + class="FILENAME">da_DK.ISO8859-1</tt>) translation + project has been started.</p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 + Upgrading from previous releases of FreeBSD</a></h1> + + <p>Users with existing FreeBSD systems are <span + class="emphasis"><i class="EMPHASIS">highly</i></span> + encouraged to read the ``Early Adopter's Guide to FreeBSD + 5.1-RELEASE''. This document generally has the filename <tt + class="FILENAME">EARLY.TXT</tt> on the distribution media, + or any other place that the release notes can be found. It + offers some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> versus + running FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Upgrading FreeBSD should, of + course, only be attempted after backing up <span + class="emphasis"><i class="EMPHASIS">all</i></span> + data and configuration files.</p> + </blockquote> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-ia64.html b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-ia64.html new file mode 100644 index 0000000000..62162ededa --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-ia64.html @@ -0,0 +1,1563 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/ia64 5.1-RELEASE Release 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 id="AEN2" name="AEN2">FreeBSD/ia64 + 5.1-RELEASE Release Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + + <p class="PUBDATE">$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.573 2003/05/28 21:01:22 hrs Exp $<br /> + </p> + + <div> + <div class="ABSTRACT"> + <a id="AEN12" name="AEN12"></a> + + <p>The release notes for FreeBSD 5.1-RELEASE contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. This + document lists applicable security advisories that were + issued since the last release, as well as significant + changes to the FreeBSD kernel and userland. Some brief + remarks on upgrading are also presented.</p> + </div> + </div> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#NEW">What's New</a></dt> + + <dd> + <dl> + <dt>2.1 <a href="#SECURITY">Security + Advisories</a></dt> + + <dt>2.2 <a href="#KERNEL">Kernel Changes</a></dt> + + <dd> + <dl> + <dt>2.2.1 <a href="#PROC">Processor/Motherboard + Support</a></dt> + + <dt>2.2.2 <a href="#BOOT">Boot Loader + Changes</a></dt> + + <dt>2.2.3 <a href="#NET-IF">Network Interface + Support</a></dt> + + <dt>2.2.4 <a href="#NET-PROTO">Network + Protocols</a></dt> + + <dt>2.2.5 <a href="#DISKS">Disks and + Storage</a></dt> + + <dt>2.2.6 <a href="#FS">File Systems</a></dt> + + <dt>2.2.7 <a href="#PCCARD">PCCARD + Support</a></dt> + + <dt>2.2.8 <a href="#MM">Multimedia + Support</a></dt> + </dl> + </dd> + + <dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + + <dt>2.4 <a href="#CONTRIB">Contributed + Software</a></dt> + + <dt>2.5 <a href="#PORTS">Ports/Packages Collection + Infrastructure</a></dt> + + <dt>2.6 <a href="#RELENG">Release Engineering and + Integration</a></dt> + + <dt>2.7 <a href="#DOC">Documentation</a></dt> + </dl> + </dd> + + <dt>3 <a href="#UPGRADE">Upgrading from previous releases + of FreeBSD</a></dt> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the release notes for FreeBSD + 5.1-RELEASE on the IA-64 hardware platform. It describes + recently added, changed, or deleted features of FreeBSD. It + also provides some notes on upgrading from previous + versions of FreeBSD.</p> + + <p>This distribution of FreeBSD 5.1-RELEASE is a release + distribution. It can be found at <a + href="ftp://ftp.FreeBSD.org/" + target="_top">ftp://ftp.FreeBSD.org/</a> or any of its + mirrors. More information on obtaining this (or other) + release distributions of FreeBSD can be found in the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html" + target="_top">``Obtaining FreeBSD'' appendix</a> to the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" + target="_top">FreeBSD Handbook</a>.</p> + + <p>Users who are new to the 5-CURRENT series of FreeBSD + releases should also read the ``Early Adopters Guide to + FreeBSD 5.1-RELEASE''. This document can generally be found + in the same location as the release notes (either as a part + of a FreeBSD distribution or on the FreeBSD Web site). It + contains important information regarding the advantages and + disadvantages of using FreeBSD 5.1-RELEASE, as opposed to + releases based on the FreeBSD 4-STABLE development + branch.</p> + + <p>All users are encouraged to consult the release errata + before installing FreeBSD. The errata document is updated + with ``late-breaking'' information discovered late in the + release cycle or after the release. Typically, it contains + information on known bugs, security advisories, and + corrections to documentation. An up-to-date copy of the + errata for FreeBSD 5.1-RELEASE can be found on the FreeBSD + Web site.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="NEW" name="NEW">2 What's + New</a></h1> + + <p>This section describes many of the user-visible new or + changed features in FreeBSD since 5.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 5.0-RELEASE). The latter items are + marked as [MERGED].</p> + + <p>Typical release note items document recent security + advisories issued after 5.0-RELEASE, new drivers or + hardware support, new commands or options, major bug fixes, + or contributed software upgrades. They may also list + changes to major ports/packages or release engineering + practices. Clearly the release notes cannot list every + single change made to FreeBSD between releases; this + document focuses primarily on security advisories, + user-visible changes, and major architectural + improvements.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 + Security Advisories</a></h2> + + <p>A remotely exploitable vulnerability in <b + class="APPLICATION">CVS</b> has been corrected with the + import of version 1.11.5. More details can be found in + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:01.cvs.asc" + target="_top">FreeBSD-SA-03:01</a>. [MERGED]</p> + + <p>A timing-based attack on <b + class="APPLICATION">OpenSSL</b>, which could allow a very + powerful attacker access to plaintext under certain + circumstances, has been prevented via an upgrade to <b + class="APPLICATION">OpenSSL</b> 0.9.7. See security + advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:02.openssl.asc" + target="_top">FreeBSD-SA-03:02</a> for more details. + [MERGED]</p> + + <p>The security and performance of the ``syncookies'' + feature has been improved to decrease the chance of an + attacker being able to spoof connections. More details + are given in security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:03.syncookies.asc" + target="_top">FreeBSD-SA-03:03</a>. [MERGED]</p> + + <p>Remotely-exploitable buffer overflow vulnerabilities + in <b class="APPLICATION">sendmail</b> have been fixed by + updating <b class="APPLICATION">sendmail</b>. For more + details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:04.sendmail.asc" + target="_top">FreeBSD-SA-03:04</a> and <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:07.sendmail.asc" + target="_top">FreeBSD-SA-03:07</a>. [MERGED]</p> + + <p>A bounds-checking bug in the XDR implementation, which + could allow a remote attacker to cause a + denial-of-service, has been fixed. For more details see + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:05.xdr.asc" + target="_top">FreeBSD-SA-03:05</a>. [MERGED]</p> + + <p>Two recently-publicized flaws in <b + class="APPLICATION">OpenSSL</b> have been corrected. For + more details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:06.openssl.asc" + target="_top">FreeBSD-SA-03:06</a>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel + Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a> is now + mandatory; the <tt class="LITERAL">NODEVFS</tt> option + has been removed from the set of possible kernel + configuration options.</p> + + <p>An <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ehci</span>(4)</span></a> driver + has been added; it supports the USB Enhanced Host + Controller Interface used by USB 2.0 controllers.</p> + + <p>A minor bug in the permissions handling of <tt + class="FILENAME">/dev/tty</tt> has been fixed. As a + result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh</span>(1)</span></a> can now be + used after <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=su&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">su</span>(1)</span></a>.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstat</span>(2)</span></a> to + return <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kqueue&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kqueue</span>(2)</span></a> to + report <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed. The + <tt class="LITERAL">NOTE_LOWAT</tt> flag for <tt + class="LITERAL">EVFILT_READ</tt> has been fixed.</p> + + <p>Linux emulation mode now supports IPv6.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=madvise&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">madvise</span>(2)</span></a> now + supports a <tt class="LITERAL">MADV_PROTECT</tt> + behavior, which informs the virtual memory system that a + process is critical and should not be killed when swap + space has been exhausted. The process must be owned by + the superuser.</p> + + <p>A second process scheduler, designed to be a general + purpose scheduler with many SMP benefits, has been added + to the scheduler framework. Exactly one scheduler must be + specified in a kernel configuration. The original + scheduler may be selected using <tt + class="LITERAL">options SCHED_4BSD</tt>. The newer + (experimental) scheduler can be selected by using <tt + class="LITERAL">options SCHED_ULE</tt>.</p> + + <p>Device major numbers are now allocated dynamically by + default. This change greatly decreases the need for a + static, centralized table of major number assignments to + device drivers (a few drivers retain their old static + major numbers for compatibility), and also reduces the + possibility of running out of device major numbers.</p> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PROC" name="PROC">2.2.1 + Processor/Motherboard Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="BOOT" name="BOOT">2.2.2 Boot + Loader Changes</a></h3> + + <p>The <tt class="FILENAME">/modules</tt> directory + (once the default location for modules on FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>) is no longer a part + of the default <tt + class="VARNAME">kern.module_path</tt>. Third-party + modules should be placed in <tt + class="FILENAME">/boot/modules</tt>.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Modules designed for use with + FreeBSD 4.<tt class="REPLACEABLE"><i>X</i></tt> are + likely to panic when loaded into a FreeBSD + 5.1-RELEASE kernel and should be used with extreme + caution.</p> + </blockquote> + </div> + <br /> + <br /> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-IF" name="NET-IF">2.2.3 + Network Interface Support</a></h3> + + <p>The cm driver now supports IPX. [MERGED]</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wlan&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wlan</span>(4)</span></a> module + provides 802.11 link-layer support. The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wi</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">an</span>(4)</span></a> drivers + now use this facility.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-PROTO" + name="NET-PROTO">2.2.4 Network Protocols</a></h3> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">skipto</tt> rules can once again be + used with the <tt class="LITERAL">log</tt> keyword. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">uid</tt> rules are once again + working.</p> + + <p>It is now possible to build the <tt + class="LITERAL">FAST_IPSEC</tt> and <tt + class="LITERAL">INET6</tt> options into the same + kernel. (They still cannot be used together, + however.)</p> + + <p>A bug in TCP NewReno, which caused premature exit + from fast recovery when NewReno was enabled, has been + fixed. [MERGED]</p> + + <p>TCP now has support for the ``Limited Transmit'' + mechanism proposed by RFC 3042. This feature is + intended to improve the effectiveness of TCP loss + recovery in certain circumstances. It is off by default + but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3042</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>TCP now has support for increased initial congestion + window sizes as described in RFC 3390. This feature can + improve the throughput of short transfers, as well as + high-bandwidth, large propagation-delay connections. It + is off by default but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3390</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>The IP fragment reassembly code behaves more + gracefully when receiving a large number of packet + fragments (it is designed to be more resistant to + fragment-based denial of service attacks). [MERGED]</p> + + <p>TCP connections in the <tt + class="LITERAL">TIME_WAIT</tt> state now use a special + protocol control block that uses less space than a + full-blown TCP PCB. This allows some of the data + structures and resources used by such a connection to + be freed earlier.</p> + + <p>It is now possible to specify the range of + ``privileged ports'' (TCP and UDP ports that require + superuser access to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bind&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bind</span>(2)</span></a> to). + The range is now specified with the <tt + class="VARNAME">net.inet.ip.portrange.reservedlow</tt> + and <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl variables, defaulting to the traditional UNIX + behavior. This feature is intended to help network + servers bind to traditionally privileged ports without + requiring superuser access. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ip&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ip</span>(4)</span></a> has more + details.</p> + + <p>Some bugs in the non-blocking RPC code has been + fixed. As a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amd</span>(8)</span></a> users + are now able to mount volumes from a 5.1-RELEASE + server.</p> + + <p>Support for XNS networking, which has not worked + correctly for almost seven years, has been removed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="DISKS" name="DISKS">2.2.5 + Disks and Storage</a></h3> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aac</span>(4)</span></a> driver + now runs free of the Giant kernel lock. This change has + given a nearly 20% performance speedup on an SMP system + running multiple I/O intensive loads.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports all known SiS chipsets. (More details can + be found in the Hardware Notes.)</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports the Promise SATA150 TX2 and TX4 Serial + ATA/150 controllers.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now flushes devices on shutdown. This change may result + in failure messages being printed on the console for + devices that do not support flushing.</p> + + <p>The CAM layer now has support for devices with more + than 2<sup>32</sup> blocks. (Assuming 512-byte blocks, + this means support for devices larger than 2TB.)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> For users upgrading across this + change, note that all userland applications that + talk to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pass&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pass</span>(4)</span></a> or + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xpt</span>(4)</span></a> + devices must be recompiled. Examples of such + programs are <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=camcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">camcontrol</span>(8)</span></a> + in the base system, the <tt + class="FILENAME">sysutils/cdrtools</tt> port, and + the <tt class="FILENAME">multimedia/xmms</tt> + port.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>A number of changes have been made to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a> driver. + The primary user-visible change is improved + compatibility with ATAPI/USB/Firewire CDROM drives.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> is now + mandatory; the <tt class="LITERAL">NO_GEOM</tt> has + been removed from the set of kernel configuration + options.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">iir</span>(4)</span></a> driver + has been updated; this update is believed to fix + problems detecting attached disks during + installation.</p> + + <p>A bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mly</span>(4)</span></a> driver + that caused hangs has been corrected.</p> + + <p>Support has been added for volume labels on UFS and + UFS2 file systems. These labels are strings that can be + used to identify a volume, regardless of what device it + appears on. Labels can be set with the <tt + class="OPTION">-L</tt> options to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> or <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tunefs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tunefs</span>(8)</span></a>. With + the <tt class="LITERAL">GEOM_VOL</tt> module, volumes + can be accessed using their labels under <tt + class="FILENAME">/dev/vol</tt>.</p> + + <p>The root file system can now be located on a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> + volume. More information can be found in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> manual + page.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="FS" name="FS">2.2.6 File + Systems</a></h3> + + <p>A new <tt class="LITERAL">DIRECTIO</tt> kernel + option enables support for read operations that bypass + the buffer cache and put data directly into a userland + buffer. This feature requires that the <tt + class="LITERAL">O_DIRECT</tt> flag is set on the file + descriptor and that both the offset and length for the + read operation are multiples of the physical media + sector size. [MERGED]</p> + + <p>NETNCP and Netware File System Support (nwfs) are + once again working.</p> + + <p>Bugs that could cause the unmounting of a smbfs + share to fail or cause a kernel panic have been + fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PCCARD" name="PCCARD">2.2.7 + PCCARD Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="MM" name="MM">2.2.8 Multimedia + Support</a></h3> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 + Userland Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + correctly handles setting user passwords containing + special shell characters.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + supports a <tt class="OPTION">-g</tt> option to set a + user's default login group.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> + utility is a replacement for the older disklabel utility. + Like its predecessor, it installs, examines, or modifies + the BSD label on a disk partition, and can install + bootstrap code. Compared to disklabel, a number of + obsolete options and parameters have been retired. A new + <tt class="OPTION">-m</tt> option instructs <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> to + use the layout suitable for a specific machine.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chgrp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chgrp</span>(1)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chown&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chown</span>(8)</span></a> now, + when the owner/group is modified, print the old and new + uid/gid if the <tt class="OPTION">-v</tt> option is + specified more than once.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> now + implements a <tt class="LITERAL">nodevice</tt> kernel + configuration file directive that cancels the effect of a + <tt class="LITERAL">device</tt> directive. The new <tt + class="LITERAL">nooption</tt> and <tt + class="LITERAL">nomakeoption</tt> directives cancel prior + <tt class="LITERAL">options</tt> and <tt + class="LITERAL">makeoptions</tt> directives, + respectively.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=diskinfo&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">diskinfo</span>(8)</span></a> + utility has been added to show information about a disk + device and optionally to run a naive performance + test.</p> + + <p>The disklabel utility has been replaced by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>. On + the alpha, i386, and pc98 platforms, disklabel is a link + to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dump</span>(8)</span></a> now + supports caching of disk blocks with the <tt + class="OPTION">-C</tt> option. This can improve dump + performance at the cost of possibly missing file system + updates that occur between passes.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dumpfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dumpfs</span>(8)</span></a> now + supports a <tt class="OPTION">-m</tt> flag to print file + system parameters in the form of a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> + command.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elfdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elfdump</span>(1)</span></a>, a + utility to display information about <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elf</span>(5)</span></a> format + executable files, has been added.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(1)</span></a> uses the + <tt class="FILENAME">.netrc</tt> support in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> and also + supports a <tt class="OPTION">-N</tt> to specify an + alternate <tt class="FILENAME">.netrc</tt> file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> now has + support for <tt class="FILENAME">.netrc</tt> files (see + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftp</span>(1)</span></a> for more + details).</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-h</tt> option to disable + printing any host-specific information, such as the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> version + or hostname, in server messages. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-P</tt> option to specify a + port on which to listen in daemon mode. The default data + port number is now set to be one less than the control + port number, rather than being hard-coded. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports an extended format of the <tt + class="FILENAME">/etc/ftpchroot</tt> file. Please refer + to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> + manpage, which is now available, for details. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports login directory pathnames that specify + simultaneously a directory for <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> and + that to change to in the chrooted environment. The <tt + class="LITERAL">/./</tt> separator is used for this + purpose, like in other FTP daemons having this feature. + It may be used in both <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=passwd&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">passwd</span>(5)</span></a>. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fwcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fwcontrol</span>(8)</span></a> now + supports <tt class="OPTION">-R</tt> and <tt + class="OPTION">-S</tt> options for receiving and sending + DV streams. [MERGED]</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gstat</span>(8)</span></a> utility + has been added to show the disk activity inside the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(8)</span></a> now + supports <tt class="LITERAL">enable</tt> and <tt + class="LITERAL">disable</tt> commands to control various + aspects of the operation of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> + (including enabling and disabling the firewall itself). + These provide a more convenient and visible interface + than the existing sysctl variables. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jail</span>(8)</span></a> now + supports a <tt class="OPTION">-i</tt> flag to output an + identifier for a newly-created jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jexec&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jexec</span>(8)</span></a> utility + has been added to execute a command inside an existing + jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jls&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jls</span>(8)</span></a> utility + has been added to list existing jails.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kenv&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kenv</span>(1)</span></a> has been + moved from <tt class="FILENAME">/usr/bin</tt> to <tt + class="FILENAME">/bin</tt> to make it available at times + during system startup when only the root file system is + mounted.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=killall&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">killall</span>(1)</span></a> now + supports a <tt class="OPTION">-j</tt> option to kill all + processes inside a jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libgeom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libgeom</span>(3)</span></a> + library has been added to allow some userland access to + the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p>The mac_portacl MAC policy module has been added. It + provides a simple ACL mechanism to permit users and + groups to bind ports for TCP or UDP, and is intended to + be used in conjunction with the recently-added <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl.</p> + + <p>The <tt class="FILENAME">MAKEDEV</tt> script is now + unnecessary, due to the mandatory presence of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a>, and has + been removed.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a> + now supports a <tt class="OPTION">-P</tt> option to + preserve the contents of files being replaced.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mixer&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mixer</span>(8)</span></a> can now + implement relative volume adjustments.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mksnap_ffs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mksnap_ffs</span>(8)</span></a> + program has been added to allow easier creation of FFS + snapshots. It is a SUID-<tt class="USERNAME">root</tt> + executable designed for use by members of the <tt + class="GROUPNAME">operator</tt> group.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umount</span>(8)</span></a> now + accept a <tt class="OPTION">-F</tt> option to specify an + alternate <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstab&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstab</span>(5)</span></a> + file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports a <tt class="OPTION">-c</tt> flag to avoid doing + a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=connect&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">connect</span>(2)</span></a> for + UDP mount points. This option must be used if the server + does not reply to requests from the standard NFS port + number 2049 or if it replies to requests using a + different IP address (which can occur if the server is + multi-homed). Setting the <tt + class="VARNAME">vfs.nfs.nfs_ip_paranoia</tt> sysctl to + <tt class="LITERAL">0</tt> will make this option the + default. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports the <tt class="OPTION">noinet4</tt> and <tt + class="OPTION">noinet6</tt> mount options to prevent NFS + mounts from using IPv4 or IPv6 respectively.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> will now + create UFS2 file systems by default, unless UFS1 is + specifically requested with the <tt + class="OPTION">-O1</tt> option.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newsyslog&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newsyslog</span>(8)</span></a> has + a number of new features. Among them:</p> + + <ul> + <li> + <p>A <tt class="LITERAL">W</tt> flag forces + previously-started compression jobs for an entry (or + group of entries specified with the <tt + class="LITERAL">G</tt> flag) to finish before + beginning a new one. This feature is designed to + prevent system overloads caused by starting several + compression jobs on big files simultaneously. + [MERGED]</p> + </li> + + <li> + <p>A ``default rotate action'', to be used for files + specified for rotation but not specified in the + configuration file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="OPTION">-s</tt> command-line flag to + disable sending signals to processes when rotating + files. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">N</tt> configuration file + flag to indicate that no process needs to be signaled + when rotating a file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">U</tt> configuration file + flag to specify that a process group (rather than a + single process) should be signaled when rotating + files. [MERGED]</p> + </li> + </ul> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + now thread-safe and implements support for Name Service + Switch (NSS) modules. NSS modules may be statically built + into <tt class="FILENAME">libc</tt> or dynamically loaded + via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dlopen&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dlopen</span>(3)</span></a>. They + are loaded/initialized at configuration time (i.e. when + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + called and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsswitch.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsswitch.conf</span>(5)</span></a> + is read or re-read).</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_chroot&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_chroot</span>(8)</span></a> + module has been added, which does a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> + operation for users into either a predetermined directory + or one derived from their home directory.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_ssh&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_ssh</span>(8)</span></a> has + been rewritten. One side effect of the rewrite is that it + now starts a separate instance of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh-agent&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh-agent</span>(1)</span></a> for + each session instead of trying to connect each session to + the agent started by the first session.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-D</tt> flag to set the + ``Don't Fragment'' bit on outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-M</tt> option to use ICMP + mask request or timestamp request messages instead of + ICMP echo requests.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-z</tt> flag to set the + Type of Service bits in outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pw</span>(8)</span></a> can now add + a user whose name ends with a <tt class="LITERAL">$</tt> + character; this change is intended to help administration + of <b class="APPLICATION">Samba</b> services. + [MERGED]</p> + + <p>The format of the <tt + class="FILENAME">/etc/pwd.db</tt> and <tt + class="FILENAME">/etc/spwd.db</tt> password databases + created by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pwd_mkdb&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pwd_mkdb</span>(8)</span></a> is + now byte-order independent. The pre-processed password + databases can now be moved between machines of different + architectures. The format includes version numbers on + entries to ensure compatibility with old binaries.</p> + + <p>A bug in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> that + could cause a sequence to remain stuck at <tt + class="LITERAL">0</tt> has been fixed. (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> remains + unsuitable for all but trivial uses.)</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rtld&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rtld</span>(1)</span></a> now has + support for the dynamic mapping of shared object + dependencies. This optional feature is especially useful + when experimenting with different threading libraries. It + is not, however, built by default. More information on + enabling and using this feature can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libmap.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libmap.conf</span>(5)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_open&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_open</span>(3)</span></a> now + correctly handles multiple opens of the same semaphore; + as a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_close&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_close</span>(3)</span></a> no + longer crashes calling programs.</p> + + <p>The seeding algorithm used by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=srandom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">srandom</span>(3)</span></a> has + been strengthened.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + will now select UFS2 as the default layout for new file + systems unless specifically requested in the disk + labeler.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + command has been added to disable paging and swapping on + a device. A related <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapctl&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapctl</span>(8)</span></a> + command has been added to provide an interface to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapon&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapon</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + similar to other BSDs.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + feature should be considered experimental.</p> + </blockquote> + </div> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslogd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslogd</span>(8)</span></a> now + allows multiple hosts or programs to be named in host or + program specifications in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslog.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslog.conf</span>(5)</span></a> + files.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=systat&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">systat</span>(1)</span></a> now + includes an <tt class="OPTION">-ifstat</tt> display mode + that displays the network traffic going through active + interfaces on the system.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=usbhidaction&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">usbhidaction</span>(1)</span></a> + command has been added; it performs actions according to + its configuration in response to USB HID controls.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uudecode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uudecode</span>(1)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=b64decode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">b64decode</span>(1)</span></a> now + support a <tt class="OPTION">-r</tt> flag for decoding + raw (or broken) files that may be missing the initial and + possibly final framing lines. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vmstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vmstat</span>(8)</span></a> has + re-implemented the <tt class="OPTION">-f</tt> flag, which + displays statistics on fork operations.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-P</tt> option to execute + multiple copies of the same utility in parallel.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-o</tt> flag to reopen <tt + class="FILENAME">/dev/tty</tt> for the child process + before executing the command. This is useful when the + child process is an interactive application.</p> + + <p>A 1:1 threading package (where for every pthread in an + application there is one KSE and thread) has been + implemented. Under this model, the kernel handles all + thread scheduling decisions and all signal delivery. This + uses some of the common KSE code, and is a restricted + case of the M:N threading work still in progress. The <tt + class="FILENAME">libthr</tt> library implementing the + userland portion of this functionality is a drop-in + replacement for the <tt class="FILENAME">libc_r</tt> + library. Note that <tt class="FILENAME">libthr</tt> is + not (at this time) built by default.</p> + + <p>The historic BSD boot scripts in <tt + class="FILENAME">/etc</tt> have been removed, in favor of + the <tt class="FILENAME">rc.d</tt> system imported from + <b class="APPLICATION">NetBSD</b> (sometimes referred to + as ``rcNG''). All functionality of the historic system + has been preserved. In particular, files such as <tt + class="FILENAME">/etc/rc.conf</tt> continue to be the + recommended means of configuring the system startup. The + <tt class="FILENAME">rc.d</tt> system has been the + default since FreeBSD 5.0-RELEASE, so this change should + be largely transparent for the vast majority of users. + Users who have customized their historic-style startup + scripts should be aware that the following files have + been removed from <tt class="FILENAME">/etc</tt>: <tt + class="FILENAME">rc.atm</tt>, <tt + class="FILENAME">rc.devfs</tt>, <tt + class="FILENAME">rc.diskless1</tt>, <tt + class="FILENAME">rc.diskless2</tt>, <tt + class="FILENAME">rc.i386</tt>, <tt + class="FILENAME">rc.alpha</tt>, <tt + class="FILENAME">rc.amd64</tt>, <tt + class="FILENAME">rc.ia64</tt>, <tt + class="FILENAME">rc.sparc64</tt>, <tt + class="FILENAME">rc.isdn</tt>, <tt + class="FILENAME">rc.network</tt>, <tt + class="FILENAME">rc.network6</tt>, <tt + class="FILENAME">rc.pccard</tt>, <tt + class="FILENAME">rc.serial</tt>, <tt + class="FILENAME">rc.syscons</tt>, <tt + class="FILENAME">rc.sysctl</tt>. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a>, + when run, will offer to move these files out of the way + for convenience. More details can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.subr&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rc.subr</span>(8)</span></a>.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="CONTRIB" name="CONTRIB">2.4 + Contributed Software</a></h2> + + <p>The <b class="APPLICATION">ACPI-CA</b> code has been + updated from the 20021118 snapshot to the 20030228 + snapshot.</p> + + <p><b class="APPLICATION">awk</b> from Bell Labs has been + updated to a 14 March 2003 snapshot.</p> + + <p><b class="APPLICATION">BIND</b> has been updated to + version 8.3.4. [MERGED]</p> + + <p>All of the <b class="APPLICATION">bzip2</b> suite of + applications is now installed in the base system (in + particular, <tt class="COMMAND">bzip2recover</tt> is now + built and installed). [MERGED]</p> + + <p><b class="APPLICATION">CVS</b> has been updated to + 1.11.5. [MERGED]</p> + + <p><b class="APPLICATION">FILE</b> has been updated to + 3.41. [MERGED]</p> + + <p><b class="APPLICATION">GCC</b> has been updated to + 3.2.2 (release version).</p> + + <p>The <b class="APPLICATION">gdtoa</b> library, for + conversions between strings and floating point, has been + imported. These sources were dated 24 March 2003.</p> + + <p><b class="APPLICATION">groff</b> (and related + utilities) have been updated from 1.18.1 to 1.19.</p> + + <p><b class="APPLICATION">IPFilter</b> has been updated + to 3.4.31. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client has + been updated to 3.0.1RC11. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client now + includes the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=omshell&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">omshell</span>(1)</span></a> + utility and the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dhcpctl&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dhcpctl</span>(3)</span></a> + library for run-time control of the client.</p> + + <p><b class="APPLICATION">Kerberos IV</b> support (in the + form of <b class="APPLICATION">KTH eBones</b>) has been + removed. Users requiring this functionality can still get + it from the <tt class="FILENAME">security/krb4</tt> port + (or package). Kerberos IV compatibility mode for Kerberos + 5 has been removed, and the <tt class="LITERAL">k5<tt + class="REPLACEABLE"><i>program</i></tt></tt> userland + utilities have been renamed to <tt class="LITERAL">k<tt + class="REPLACEABLE"><i>program</i></tt></tt>.</p> + + <p><b class="APPLICATION">Kerberos 5</b> is now built by + default in <tt class="LITERAL">buildworld</tt> + operations. Setting <tt + class="VARNAME">MAKE_KERBEROS5</tt> no longer has any + effect. Disabling the base system Kerberos 5 now requires + the <tt class="VARNAME">NO_KERBEROS</tt> Makefile + variable to be set.</p> + + <p><b class="APPLICATION">libpcap</b> now has support for + selecting among multiple data link types on an + interface.</p> + + <p><b class="APPLICATION">lukemftpd</b> (not built or + installed by default) has been updated to a snapshot from + 22 January 2003.</p> + + <p><b class="APPLICATION">OpenPAM</b> has been updated + from the ``Citronella'' release to the ``Dianthus'' + release.</p> + + <p><b class="APPLICATION">OpenSSH</b> has been updated to + 3.6.1p1.</p> + + <p><b class="APPLICATION">OpenSSL</b> has been updated to + release 0.9.7a. Among other features, this release + includes support for AES and takes advantage of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=crypto&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">crypto</span>(4)</span></a> + devices. [MERGED]</p> + + <p><b class="APPLICATION">sendmail</b> has been updated + to version 8.12.9. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcpdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcpdump</span>(1)</span></a> has + been updated to version 3.7.2. [MERGED] It also now + supports a <tt class="OPTION">-L</tt> flag to list the + data link types available on an interface and a <tt + class="OPTION">-y</tt> option to specify the data link + type to use while capturing packets.</p> + + <p><b class="APPLICATION">texinfo</b> has been updated + from 4.2 to 4.5.</p> + + <p>The timezone database has been updated from <tt + class="FILENAME">tzdata2002d</tt> to <tt + class="FILENAME">tzdata2003a</tt>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="PORTS" name="PORTS">2.5 + Ports/Packages Collection Infrastructure</a></h2> + + <p>The one-line <tt class="FILENAME">pkg-comment</tt> + files have been eliminated from each port skeleton; their + contents have been moved into each port's <tt + class="FILENAME">Makefile</tt>. This change reduces the + disk space and inodes used by the ports tree. + [MERGED]</p> + + <p>When fetching distfiles for building a port, the <tt + class="VARNAME">FETCH_REGET</tt> <tt + class="FILENAME">Makefile</tt> variable can be used to + specify the number of times to try continuing to fetch a + distfile if it fails its MD5 checksum. The port + infrastructure also supports re-fetching interrupted + distfiles.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_create</span>(1)</span></a> now + supports a <tt class="OPTION">-C</tt> option, which + allows packages to register a list of other packages with + which they conflict. They will refuse to install (via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a>) if + one of the listed packages is already present. The <tt + class="OPTION">-f</tt> flag to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a> + overrides this conflict-checking.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + honors the <tt class="VARNAME">BLOCKSIZE</tt> environment + variable in its output when the <tt + class="OPTION">-b</tt> flag is given.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + implements a <tt class="OPTION">-Q</tt> option, which is + similar to the <tt class="OPTION">-q</tt> ``quiet'' + option except that it prefixes the output with the + package name.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="RELENG" name="RELENG">2.6 + Release Engineering and Integration</a></h2> + + <p>The supported release of <b + class="APPLICATION">GNOME</b> has been updated to 2.2.1. + [MERGED]</p> + + <p>The supported release of <b + class="APPLICATION">KDE</b> has been updated to 3.1.2. + [MERGED]</p> + + <p>There is no longer a separate <tt + class="FILENAME">krb5</tt> distribution. The Kerberos 5 + libraries and utilities have been incorporated into the + <tt class="FILENAME">crypto</tt> distribution.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + once again supports installing individual components of + <b class="APPLICATION">XFree86</b>. Supporting changes + (not user-visible) generalize the concept of installing + parts of distributions as packages.</p> + + <p>The supported release of <b + class="APPLICATION">XFree86</b> has been updated to + 4.3.0. [MERGED]</p> + + <p>Several upgrade mechanisms designed to permit major + version upgrades from FreeBSD 2.<tt + class="REPLACEABLE"><i>X</i></tt> to 3.<tt + class="REPLACEABLE"><i>X</i></tt> and from FreeBSD 3.<tt + class="REPLACEABLE"><i>X</i></tt> to 4.<tt + class="REPLACEABLE"><i>X</i></tt> have been removed.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="DOC" name="DOC">2.7 + Documentation</a></h2> + + <p>The following new articles have been added to the + documentation set: ``FreeBSD From Scratch'', ``The + Roadmap for 5-STABLE''.</p> + + <p>A new Danish (<tt + class="FILENAME">da_DK.ISO8859-1</tt>) translation + project has been started.</p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 + Upgrading from previous releases of FreeBSD</a></h1> + + <p>Users with existing FreeBSD systems are <span + class="emphasis"><i class="EMPHASIS">highly</i></span> + encouraged to read the ``Early Adopter's Guide to FreeBSD + 5.1-RELEASE''. This document generally has the filename <tt + class="FILENAME">EARLY.TXT</tt> on the distribution media, + or any other place that the release notes can be found. It + offers some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> versus + running FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Upgrading FreeBSD should, of + course, only be attempted after backing up <span + class="emphasis"><i class="EMPHASIS">all</i></span> + data and configuration files.</p> + </blockquote> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-pc98.html b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-pc98.html new file mode 100644 index 0000000000..a8ac8c9413 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-pc98.html @@ -0,0 +1,1641 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/pc98 5.1-RELEASE Release 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 id="AEN2" name="AEN2">FreeBSD/pc98 + 5.1-RELEASE Release Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + + <p class="PUBDATE">$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.573 2003/05/28 21:01:22 hrs Exp $<br /> + </p> + + <div> + <div class="ABSTRACT"> + <a id="AEN12" name="AEN12"></a> + + <p>The release notes for FreeBSD 5.1-RELEASE contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. This + document lists applicable security advisories that were + issued since the last release, as well as significant + changes to the FreeBSD kernel and userland. Some brief + remarks on upgrading are also presented.</p> + </div> + </div> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#NEW">What's New</a></dt> + + <dd> + <dl> + <dt>2.1 <a href="#SECURITY">Security + Advisories</a></dt> + + <dt>2.2 <a href="#KERNEL">Kernel Changes</a></dt> + + <dd> + <dl> + <dt>2.2.1 <a href="#PROC">Processor/Motherboard + Support</a></dt> + + <dt>2.2.2 <a href="#BOOT">Boot Loader + Changes</a></dt> + + <dt>2.2.3 <a href="#NET-IF">Network Interface + Support</a></dt> + + <dt>2.2.4 <a href="#NET-PROTO">Network + Protocols</a></dt> + + <dt>2.2.5 <a href="#DISKS">Disks and + Storage</a></dt> + + <dt>2.2.6 <a href="#FS">File Systems</a></dt> + + <dt>2.2.7 <a href="#PCCARD">PCCARD + Support</a></dt> + + <dt>2.2.8 <a href="#MM">Multimedia + Support</a></dt> + </dl> + </dd> + + <dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + + <dt>2.4 <a href="#CONTRIB">Contributed + Software</a></dt> + + <dt>2.5 <a href="#PORTS">Ports/Packages Collection + Infrastructure</a></dt> + + <dt>2.6 <a href="#RELENG">Release Engineering and + Integration</a></dt> + + <dt>2.7 <a href="#DOC">Documentation</a></dt> + </dl> + </dd> + + <dt>3 <a href="#UPGRADE">Upgrading from previous releases + of FreeBSD</a></dt> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the release notes for FreeBSD + 5.1-RELEASE on the NEC PC-98x1 hardware platform. It + describes recently added, changed, or deleted features of + FreeBSD. It also provides some notes on upgrading from + previous versions of FreeBSD.</p> + + <p>This distribution of FreeBSD 5.1-RELEASE is a release + distribution. It can be found at <a + href="ftp://ftp.FreeBSD.org/" + target="_top">ftp://ftp.FreeBSD.org/</a> or any of its + mirrors. More information on obtaining this (or other) + release distributions of FreeBSD can be found in the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html" + target="_top">``Obtaining FreeBSD'' appendix</a> to the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" + target="_top">FreeBSD Handbook</a>.</p> + + <p>Users who are new to the 5-CURRENT series of FreeBSD + releases should also read the ``Early Adopters Guide to + FreeBSD 5.1-RELEASE''. This document can generally be found + in the same location as the release notes (either as a part + of a FreeBSD distribution or on the FreeBSD Web site). It + contains important information regarding the advantages and + disadvantages of using FreeBSD 5.1-RELEASE, as opposed to + releases based on the FreeBSD 4-STABLE development + branch.</p> + + <p>All users are encouraged to consult the release errata + before installing FreeBSD. The errata document is updated + with ``late-breaking'' information discovered late in the + release cycle or after the release. Typically, it contains + information on known bugs, security advisories, and + corrections to documentation. An up-to-date copy of the + errata for FreeBSD 5.1-RELEASE can be found on the FreeBSD + Web site.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="NEW" name="NEW">2 What's + New</a></h1> + + <p>This section describes many of the user-visible new or + changed features in FreeBSD since 5.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 5.0-RELEASE). The latter items are + marked as [MERGED].</p> + + <p>Typical release note items document recent security + advisories issued after 5.0-RELEASE, new drivers or + hardware support, new commands or options, major bug fixes, + or contributed software upgrades. They may also list + changes to major ports/packages or release engineering + practices. Clearly the release notes cannot list every + single change made to FreeBSD between releases; this + document focuses primarily on security advisories, + user-visible changes, and major architectural + improvements.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 + Security Advisories</a></h2> + + <p>A remotely exploitable vulnerability in <b + class="APPLICATION">CVS</b> has been corrected with the + import of version 1.11.5. More details can be found in + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:01.cvs.asc" + target="_top">FreeBSD-SA-03:01</a>. [MERGED]</p> + + <p>A timing-based attack on <b + class="APPLICATION">OpenSSL</b>, which could allow a very + powerful attacker access to plaintext under certain + circumstances, has been prevented via an upgrade to <b + class="APPLICATION">OpenSSL</b> 0.9.7. See security + advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:02.openssl.asc" + target="_top">FreeBSD-SA-03:02</a> for more details. + [MERGED]</p> + + <p>The security and performance of the ``syncookies'' + feature has been improved to decrease the chance of an + attacker being able to spoof connections. More details + are given in security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:03.syncookies.asc" + target="_top">FreeBSD-SA-03:03</a>. [MERGED]</p> + + <p>Remotely-exploitable buffer overflow vulnerabilities + in <b class="APPLICATION">sendmail</b> have been fixed by + updating <b class="APPLICATION">sendmail</b>. For more + details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:04.sendmail.asc" + target="_top">FreeBSD-SA-03:04</a> and <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:07.sendmail.asc" + target="_top">FreeBSD-SA-03:07</a>. [MERGED]</p> + + <p>A bounds-checking bug in the XDR implementation, which + could allow a remote attacker to cause a + denial-of-service, has been fixed. For more details see + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:05.xdr.asc" + target="_top">FreeBSD-SA-03:05</a>. [MERGED]</p> + + <p>Two recently-publicized flaws in <b + class="APPLICATION">OpenSSL</b> have been corrected. For + more details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:06.openssl.asc" + target="_top">FreeBSD-SA-03:06</a>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel + Changes</a></h2> + + <p>Support for the CanBe power management controller has + been added. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a> is now + mandatory; the <tt class="LITERAL">NODEVFS</tt> option + has been removed from the set of possible kernel + configuration options.</p> + + <p>An <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ehci&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ehci</span>(4)</span></a> driver + has been added; it supports the USB Enhanced Host + Controller Interface used by USB 2.0 controllers.</p> + + <p>A minor bug in the permissions handling of <tt + class="FILENAME">/dev/tty</tt> has been fixed. As a + result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh</span>(1)</span></a> can now be + used after <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=su&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">su</span>(1)</span></a>.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstat</span>(2)</span></a> to + return <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kqueue&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kqueue</span>(2)</span></a> to + report <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed. The + <tt class="LITERAL">NOTE_LOWAT</tt> flag for <tt + class="LITERAL">EVFILT_READ</tt> has been fixed.</p> + + <p>Linux emulation mode now supports IPv6.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=madvise&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">madvise</span>(2)</span></a> now + supports a <tt class="LITERAL">MADV_PROTECT</tt> + behavior, which informs the virtual memory system that a + process is critical and should not be killed when swap + space has been exhausted. The process must be owned by + the superuser.</p> + + <p>The tw driver for TW-523 power line interfaces (used + by X-10 home control products) has been removed. It is + currently non-functional, and would require a + considerable amount of work to make it work under + 5-CURRENT. The xten and xtend userland control programs + have also been removed.</p> + + <p>A second process scheduler, designed to be a general + purpose scheduler with many SMP benefits, has been added + to the scheduler framework. Exactly one scheduler must be + specified in a kernel configuration. The original + scheduler may be selected using <tt + class="LITERAL">options SCHED_4BSD</tt>. The newer + (experimental) scheduler can be selected by using <tt + class="LITERAL">options SCHED_ULE</tt>.</p> + + <p>Device major numbers are now allocated dynamically by + default. This change greatly decreases the need for a + static, centralized table of major number assignments to + device drivers (a few drivers retain their old static + major numbers for compatibility), and also reduces the + possibility of running out of device major numbers.</p> + + <p>A partial lazy switch mechanism for in-kernel threads + has been implemented; it is designed to reduce the + overhead of short context switches (such as for interrupt + handlers) that do not involve another process. This + feature can be enabled with <tt + class="LITERAL">options LAZY_SWITCH</tt>.</p> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PROC" name="PROC">2.2.1 + Processor/Motherboard Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="BOOT" name="BOOT">2.2.2 Boot + Loader Changes</a></h3> + + <p>The two parts of the boot loader (<tt + class="FILENAME">boot1</tt> and <tt + class="FILENAME">boot2</tt>) have been combined into a + single <tt class="FILENAME">boot</tt> file, to simplify + programs that need to write or otherwise manipulate the + boot loader.</p> + + <p>The PC98 boot loader now has support for booting + from SCSI MO media. [MERGED]</p> + + <p>The <tt class="FILENAME">/modules</tt> directory + (once the default location for modules on FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>) is no longer a part + of the default <tt + class="VARNAME">kern.module_path</tt>. Third-party + modules should be placed in <tt + class="FILENAME">/boot/modules</tt>.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Modules designed for use with + FreeBSD 4.<tt class="REPLACEABLE"><i>X</i></tt> are + likely to panic when loaded into a FreeBSD + 5.1-RELEASE kernel and should be used with extreme + caution.</p> + </blockquote> + </div> + <br /> + <br /> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-IF" name="NET-IF">2.2.3 + Network Interface Support</a></h3> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=axe&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">axe</span>(4)</span></a> network + driver has been added. It provides support for USB + Ethernet adapters based on the ASIX Electronics AX88172 + USB 2.0 chipset.</p> + + <p>The cm driver now supports IPX. [MERGED]</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rue&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rue</span>(4)</span></a> network + driver has been added, providing support for Ethernet + adapters based on the RealTek RTL8150 USB to Fast + Ethernet controller chip.</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wlan&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wlan</span>(4)</span></a> module + provides 802.11 link-layer support. The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wi</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">an</span>(4)</span></a> drivers + now use this facility.</p> + + <p>A timing bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xl</span>(4)</span></a> driver, + which could cause a kernel panic (or other problems) + when configuring an interface, has been fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-PROTO" + name="NET-PROTO">2.2.4 Network Protocols</a></h3> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">skipto</tt> rules can once again be + used with the <tt class="LITERAL">log</tt> keyword. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">uid</tt> rules are once again + working.</p> + + <p>It is now possible to build the <tt + class="LITERAL">FAST_IPSEC</tt> and <tt + class="LITERAL">INET6</tt> options into the same + kernel. (They still cannot be used together, + however.)</p> + + <p>A bug in TCP NewReno, which caused premature exit + from fast recovery when NewReno was enabled, has been + fixed. [MERGED]</p> + + <p>TCP now has support for the ``Limited Transmit'' + mechanism proposed by RFC 3042. This feature is + intended to improve the effectiveness of TCP loss + recovery in certain circumstances. It is off by default + but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3042</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>TCP now has support for increased initial congestion + window sizes as described in RFC 3390. This feature can + improve the throughput of short transfers, as well as + high-bandwidth, large propagation-delay connections. It + is off by default but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3390</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>The IP fragment reassembly code behaves more + gracefully when receiving a large number of packet + fragments (it is designed to be more resistant to + fragment-based denial of service attacks). [MERGED]</p> + + <p>TCP connections in the <tt + class="LITERAL">TIME_WAIT</tt> state now use a special + protocol control block that uses less space than a + full-blown TCP PCB. This allows some of the data + structures and resources used by such a connection to + be freed earlier.</p> + + <p>It is now possible to specify the range of + ``privileged ports'' (TCP and UDP ports that require + superuser access to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bind&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bind</span>(2)</span></a> to). + The range is now specified with the <tt + class="VARNAME">net.inet.ip.portrange.reservedlow</tt> + and <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl variables, defaulting to the traditional UNIX + behavior. This feature is intended to help network + servers bind to traditionally privileged ports without + requiring superuser access. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ip&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ip</span>(4)</span></a> has more + details.</p> + + <p>Some bugs in the non-blocking RPC code has been + fixed. As a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amd</span>(8)</span></a> users + are now able to mount volumes from a 5.1-RELEASE + server.</p> + + <p>Support for XNS networking, which has not worked + correctly for almost seven years, has been removed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="DISKS" name="DISKS">2.2.5 + Disks and Storage</a></h3> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aac</span>(4)</span></a> driver + now runs free of the Giant kernel lock. This change has + given a nearly 20% performance speedup on an SMP system + running multiple I/O intensive loads.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports all known SiS chipsets. (More details can + be found in the Hardware Notes.)</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports the Promise SATA150 TX2 and TX4 Serial + ATA/150 controllers.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now flushes devices on shutdown. This change may result + in failure messages being printed on the console for + devices that do not support flushing.</p> + + <p>The CAM layer now has support for devices with more + than 2<sup>32</sup> blocks. (Assuming 512-byte blocks, + this means support for devices larger than 2TB.)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> For users upgrading across this + change, note that all userland applications that + talk to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pass&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pass</span>(4)</span></a> or + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xpt</span>(4)</span></a> + devices must be recompiled. Examples of such + programs are <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=camcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">camcontrol</span>(8)</span></a> + in the base system, the <tt + class="FILENAME">sysutils/cdrtools</tt> port, and + the <tt class="FILENAME">multimedia/xmms</tt> + port.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>A number of changes have been made to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a> driver. + The primary user-visible change is improved + compatibility with ATAPI/USB/Firewire CDROM drives.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> is now + mandatory; the <tt class="LITERAL">NO_GEOM</tt> has + been removed from the set of kernel configuration + options.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">iir</span>(4)</span></a> driver + has been updated; this update is believed to fix + problems detecting attached disks during + installation.</p> + + <p>A bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mly</span>(4)</span></a> driver + that caused hangs has been corrected.</p> + + <p>Support has been added for volume labels on UFS and + UFS2 file systems. These labels are strings that can be + used to identify a volume, regardless of what device it + appears on. Labels can be set with the <tt + class="OPTION">-L</tt> options to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> or <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tunefs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tunefs</span>(8)</span></a>. With + the <tt class="LITERAL">GEOM_VOL</tt> module, volumes + can be accessed using their labels under <tt + class="FILENAME">/dev/vol</tt>.</p> + + <p>The root file system can now be located on a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> + volume. More information can be found in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> manual + page.</p> + + <p>The wfd and wst drivers, which have been broken for + some time, have been removed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="FS" name="FS">2.2.6 File + Systems</a></h3> + + <p>A new <tt class="LITERAL">DIRECTIO</tt> kernel + option enables support for read operations that bypass + the buffer cache and put data directly into a userland + buffer. This feature requires that the <tt + class="LITERAL">O_DIRECT</tt> flag is set on the file + descriptor and that both the offset and length for the + read operation are multiples of the physical media + sector size. [MERGED]</p> + + <p>NETNCP and Netware File System Support (nwfs) are + once again working.</p> + + <p>Bugs that could cause the unmounting of a smbfs + share to fail or cause a kernel panic have been + fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PCCARD" name="PCCARD">2.2.7 + PCCARD Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="MM" name="MM">2.2.8 Multimedia + Support</a></h3> + + <p>The <tt class="FILENAME">atspeaker.ko</tt> and <tt + class="FILENAME">pcspeaker.ko</tt> modules for the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=speaker&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">speaker</span>(4)</span></a> + device have been renamed <tt + class="FILENAME">speaker.ko</tt>.</p> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 + Userland Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + correctly handles setting user passwords containing + special shell characters.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + supports a <tt class="OPTION">-g</tt> option to set a + user's default login group.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> + utility is a replacement for the older disklabel utility. + Like its predecessor, it installs, examines, or modifies + the BSD label on a disk partition, and can install + bootstrap code. Compared to disklabel, a number of + obsolete options and parameters have been retired. A new + <tt class="OPTION">-m</tt> option instructs <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> to + use the layout suitable for a specific machine.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chgrp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chgrp</span>(1)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chown&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chown</span>(8)</span></a> now, + when the owner/group is modified, print the old and new + uid/gid if the <tt class="OPTION">-v</tt> option is + specified more than once.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> now + implements a <tt class="LITERAL">nodevice</tt> kernel + configuration file directive that cancels the effect of a + <tt class="LITERAL">device</tt> directive. The new <tt + class="LITERAL">nooption</tt> and <tt + class="LITERAL">nomakeoption</tt> directives cancel prior + <tt class="LITERAL">options</tt> and <tt + class="LITERAL">makeoptions</tt> directives, + respectively.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=diskinfo&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">diskinfo</span>(8)</span></a> + utility has been added to show information about a disk + device and optionally to run a naive performance + test.</p> + + <p>The disklabel utility has been replaced by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>. On + the alpha, i386, and pc98 platforms, disklabel is a link + to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dump</span>(8)</span></a> now + supports caching of disk blocks with the <tt + class="OPTION">-C</tt> option. This can improve dump + performance at the cost of possibly missing file system + updates that occur between passes.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dumpfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dumpfs</span>(8)</span></a> now + supports a <tt class="OPTION">-m</tt> flag to print file + system parameters in the form of a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> + command.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elfdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elfdump</span>(1)</span></a>, a + utility to display information about <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elf</span>(5)</span></a> format + executable files, has been added.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(1)</span></a> uses the + <tt class="FILENAME">.netrc</tt> support in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> and also + supports a <tt class="OPTION">-N</tt> to specify an + alternate <tt class="FILENAME">.netrc</tt> file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> now has + support for <tt class="FILENAME">.netrc</tt> files (see + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftp</span>(1)</span></a> for more + details).</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-h</tt> option to disable + printing any host-specific information, such as the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> version + or hostname, in server messages. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-P</tt> option to specify a + port on which to listen in daemon mode. The default data + port number is now set to be one less than the control + port number, rather than being hard-coded. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports an extended format of the <tt + class="FILENAME">/etc/ftpchroot</tt> file. Please refer + to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> + manpage, which is now available, for details. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports login directory pathnames that specify + simultaneously a directory for <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> and + that to change to in the chrooted environment. The <tt + class="LITERAL">/./</tt> separator is used for this + purpose, like in other FTP daemons having this feature. + It may be used in both <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=passwd&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">passwd</span>(5)</span></a>. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fwcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fwcontrol</span>(8)</span></a> now + supports <tt class="OPTION">-R</tt> and <tt + class="OPTION">-S</tt> options for receiving and sending + DV streams. [MERGED]</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gstat</span>(8)</span></a> utility + has been added to show the disk activity inside the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(8)</span></a> now + supports <tt class="LITERAL">enable</tt> and <tt + class="LITERAL">disable</tt> commands to control various + aspects of the operation of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> + (including enabling and disabling the firewall itself). + These provide a more convenient and visible interface + than the existing sysctl variables. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jail</span>(8)</span></a> now + supports a <tt class="OPTION">-i</tt> flag to output an + identifier for a newly-created jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jexec&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jexec</span>(8)</span></a> utility + has been added to execute a command inside an existing + jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jls&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jls</span>(8)</span></a> utility + has been added to list existing jails.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kenv&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kenv</span>(1)</span></a> has been + moved from <tt class="FILENAME">/usr/bin</tt> to <tt + class="FILENAME">/bin</tt> to make it available at times + during system startup when only the root file system is + mounted.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=killall&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">killall</span>(1)</span></a> now + supports a <tt class="OPTION">-j</tt> option to kill all + processes inside a jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libgeom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libgeom</span>(3)</span></a> + library has been added to allow some userland access to + the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p>The mac_portacl MAC policy module has been added. It + provides a simple ACL mechanism to permit users and + groups to bind ports for TCP or UDP, and is intended to + be used in conjunction with the recently-added <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl.</p> + + <p>The <tt class="FILENAME">MAKEDEV</tt> script is now + unnecessary, due to the mandatory presence of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a>, and has + been removed.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a> + now supports a <tt class="OPTION">-P</tt> option to + preserve the contents of files being replaced.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mixer&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mixer</span>(8)</span></a> can now + implement relative volume adjustments.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mksnap_ffs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mksnap_ffs</span>(8)</span></a> + program has been added to allow easier creation of FFS + snapshots. It is a SUID-<tt class="USERNAME">root</tt> + executable designed for use by members of the <tt + class="GROUPNAME">operator</tt> group.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umount</span>(8)</span></a> now + accept a <tt class="OPTION">-F</tt> option to specify an + alternate <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstab&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstab</span>(5)</span></a> + file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports a <tt class="OPTION">-c</tt> flag to avoid doing + a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=connect&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">connect</span>(2)</span></a> for + UDP mount points. This option must be used if the server + does not reply to requests from the standard NFS port + number 2049 or if it replies to requests using a + different IP address (which can occur if the server is + multi-homed). Setting the <tt + class="VARNAME">vfs.nfs.nfs_ip_paranoia</tt> sysctl to + <tt class="LITERAL">0</tt> will make this option the + default. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports the <tt class="OPTION">noinet4</tt> and <tt + class="OPTION">noinet6</tt> mount options to prevent NFS + mounts from using IPv4 or IPv6 respectively.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> will now + create UFS2 file systems by default, unless UFS1 is + specifically requested with the <tt + class="OPTION">-O1</tt> option.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newsyslog&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newsyslog</span>(8)</span></a> has + a number of new features. Among them:</p> + + <ul> + <li> + <p>A <tt class="LITERAL">W</tt> flag forces + previously-started compression jobs for an entry (or + group of entries specified with the <tt + class="LITERAL">G</tt> flag) to finish before + beginning a new one. This feature is designed to + prevent system overloads caused by starting several + compression jobs on big files simultaneously. + [MERGED]</p> + </li> + + <li> + <p>A ``default rotate action'', to be used for files + specified for rotation but not specified in the + configuration file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="OPTION">-s</tt> command-line flag to + disable sending signals to processes when rotating + files. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">N</tt> configuration file + flag to indicate that no process needs to be signaled + when rotating a file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">U</tt> configuration file + flag to specify that a process group (rather than a + single process) should be signaled when rotating + files. [MERGED]</p> + </li> + </ul> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + now thread-safe and implements support for Name Service + Switch (NSS) modules. NSS modules may be statically built + into <tt class="FILENAME">libc</tt> or dynamically loaded + via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dlopen&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dlopen</span>(3)</span></a>. They + are loaded/initialized at configuration time (i.e. when + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + called and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsswitch.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsswitch.conf</span>(5)</span></a> + is read or re-read).</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_chroot&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_chroot</span>(8)</span></a> + module has been added, which does a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> + operation for users into either a predetermined directory + or one derived from their home directory.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_ssh&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_ssh</span>(8)</span></a> has + been rewritten. One side effect of the rewrite is that it + now starts a separate instance of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh-agent&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh-agent</span>(1)</span></a> for + each session instead of trying to connect each session to + the agent started by the first session.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-D</tt> flag to set the + ``Don't Fragment'' bit on outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-M</tt> option to use ICMP + mask request or timestamp request messages instead of + ICMP echo requests.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-z</tt> flag to set the + Type of Service bits in outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pw</span>(8)</span></a> can now add + a user whose name ends with a <tt class="LITERAL">$</tt> + character; this change is intended to help administration + of <b class="APPLICATION">Samba</b> services. + [MERGED]</p> + + <p>The format of the <tt + class="FILENAME">/etc/pwd.db</tt> and <tt + class="FILENAME">/etc/spwd.db</tt> password databases + created by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pwd_mkdb&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pwd_mkdb</span>(8)</span></a> is + now byte-order independent. The pre-processed password + databases can now be moved between machines of different + architectures. The format includes version numbers on + entries to ensure compatibility with old binaries.</p> + + <p>A bug in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> that + could cause a sequence to remain stuck at <tt + class="LITERAL">0</tt> has been fixed. (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> remains + unsuitable for all but trivial uses.)</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rtld&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rtld</span>(1)</span></a> now has + support for the dynamic mapping of shared object + dependencies. This optional feature is especially useful + when experimenting with different threading libraries. It + is not, however, built by default. More information on + enabling and using this feature can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libmap.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libmap.conf</span>(5)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_open&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_open</span>(3)</span></a> now + correctly handles multiple opens of the same semaphore; + as a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_close&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_close</span>(3)</span></a> no + longer crashes calling programs.</p> + + <p>The seeding algorithm used by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=srandom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">srandom</span>(3)</span></a> has + been strengthened.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + command has been added to disable paging and swapping on + a device. A related <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapctl&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapctl</span>(8)</span></a> + command has been added to provide an interface to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapon&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapon</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + similar to other BSDs.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + feature should be considered experimental.</p> + </blockquote> + </div> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslogd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslogd</span>(8)</span></a> now + allows multiple hosts or programs to be named in host or + program specifications in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslog.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslog.conf</span>(5)</span></a> + files.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=systat&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">systat</span>(1)</span></a> now + includes an <tt class="OPTION">-ifstat</tt> display mode + that displays the network traffic going through active + interfaces on the system.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=usbhidaction&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">usbhidaction</span>(1)</span></a> + command has been added; it performs actions according to + its configuration in response to USB HID controls.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uudecode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uudecode</span>(1)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=b64decode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">b64decode</span>(1)</span></a> now + support a <tt class="OPTION">-r</tt> flag for decoding + raw (or broken) files that may be missing the initial and + possibly final framing lines. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vmstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vmstat</span>(8)</span></a> has + re-implemented the <tt class="OPTION">-f</tt> flag, which + displays statistics on fork operations.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-P</tt> option to execute + multiple copies of the same utility in parallel.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-o</tt> flag to reopen <tt + class="FILENAME">/dev/tty</tt> for the child process + before executing the command. This is useful when the + child process is an interactive application.</p> + + <p>The <tt class="FILENAME">libkse</tt> library, + providing POSIX threading support using KSE, is now + enabled and installed by default. This library currently + supports M:N threading. Both process and system scope + threads are supported, as well as getting/setting the + concurrency level. By default, the library sets the + concurrency level to the number of CPUs in the system. + Each concurrency level correlates to a KSE, and all + process scope threads run in these KSEs. Each system + scope thread gets its own KSE in addition to those + corresponding to concurrency levels. <tt + class="FILENAME">libkse</tt> is still considered a + work-in-progress, and is not used by default. However, it + can be used as a replacement for the <tt + class="FILENAME">libc_r</tt> thread library, by + substituting <tt class="OPTION">-lkse</tt> instead of <tt + class="OPTION">-pthread</tt> when linking programs.</p> + + <p>A 1:1 threading package (where for every pthread in an + application there is one KSE and thread) has been + implemented. Under this model, the kernel handles all + thread scheduling decisions and all signal delivery. This + uses some of the common KSE code, and is a restricted + case of the M:N threading work still in progress. The <tt + class="FILENAME">libthr</tt> library implementing the + userland portion of this functionality is a drop-in + replacement for the <tt class="FILENAME">libc_r</tt> + library. Note that <tt class="FILENAME">libthr</tt> is + not (at this time) built by default.</p> + + <p>The historic BSD boot scripts in <tt + class="FILENAME">/etc</tt> have been removed, in favor of + the <tt class="FILENAME">rc.d</tt> system imported from + <b class="APPLICATION">NetBSD</b> (sometimes referred to + as ``rcNG''). All functionality of the historic system + has been preserved. In particular, files such as <tt + class="FILENAME">/etc/rc.conf</tt> continue to be the + recommended means of configuring the system startup. The + <tt class="FILENAME">rc.d</tt> system has been the + default since FreeBSD 5.0-RELEASE, so this change should + be largely transparent for the vast majority of users. + Users who have customized their historic-style startup + scripts should be aware that the following files have + been removed from <tt class="FILENAME">/etc</tt>: <tt + class="FILENAME">rc.atm</tt>, <tt + class="FILENAME">rc.devfs</tt>, <tt + class="FILENAME">rc.diskless1</tt>, <tt + class="FILENAME">rc.diskless2</tt>, <tt + class="FILENAME">rc.i386</tt>, <tt + class="FILENAME">rc.alpha</tt>, <tt + class="FILENAME">rc.amd64</tt>, <tt + class="FILENAME">rc.ia64</tt>, <tt + class="FILENAME">rc.sparc64</tt>, <tt + class="FILENAME">rc.isdn</tt>, <tt + class="FILENAME">rc.network</tt>, <tt + class="FILENAME">rc.network6</tt>, <tt + class="FILENAME">rc.pccard</tt>, <tt + class="FILENAME">rc.serial</tt>, <tt + class="FILENAME">rc.syscons</tt>, <tt + class="FILENAME">rc.sysctl</tt>. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a>, + when run, will offer to move these files out of the way + for convenience. More details can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.subr&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rc.subr</span>(8)</span></a>.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="CONTRIB" name="CONTRIB">2.4 + Contributed Software</a></h2> + + <p>The <b class="APPLICATION">ACPI-CA</b> code has been + updated from the 20021118 snapshot to the 20030228 + snapshot.</p> + + <p><b class="APPLICATION">awk</b> from Bell Labs has been + updated to a 14 March 2003 snapshot.</p> + + <p><b class="APPLICATION">BIND</b> has been updated to + version 8.3.4. [MERGED]</p> + + <p>All of the <b class="APPLICATION">bzip2</b> suite of + applications is now installed in the base system (in + particular, <tt class="COMMAND">bzip2recover</tt> is now + built and installed). [MERGED]</p> + + <p><b class="APPLICATION">CVS</b> has been updated to + 1.11.5. [MERGED]</p> + + <p>The <b class="APPLICATION">DRM</b> kernel modules have + been updated to a snapshot from the DRI CVS repository, + as of 24 April 2003. The <tt + class="LITERAL">DRM_LINUX</tt> kernel option hsa been + removed because the handler is now provided by the Linux + compatibility code.</p> + + <p><b class="APPLICATION">FILE</b> has been updated to + 3.41. [MERGED]</p> + + <p><b class="APPLICATION">GCC</b> has been updated to + 3.2.2 (release version).</p> + + <p>The <b class="APPLICATION">gdtoa</b> library, for + conversions between strings and floating point, has been + imported. These sources were dated 24 March 2003.</p> + + <p><b class="APPLICATION">groff</b> (and related + utilities) have been updated from 1.18.1 to 1.19.</p> + + <p><b class="APPLICATION">IPFilter</b> has been updated + to 3.4.31. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client has + been updated to 3.0.1RC11. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client now + includes the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=omshell&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">omshell</span>(1)</span></a> + utility and the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dhcpctl&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dhcpctl</span>(3)</span></a> + library for run-time control of the client.</p> + + <p><b class="APPLICATION">Kerberos IV</b> support (in the + form of <b class="APPLICATION">KTH eBones</b>) has been + removed. Users requiring this functionality can still get + it from the <tt class="FILENAME">security/krb4</tt> port + (or package). Kerberos IV compatibility mode for Kerberos + 5 has been removed, and the <tt class="LITERAL">k5<tt + class="REPLACEABLE"><i>program</i></tt></tt> userland + utilities have been renamed to <tt class="LITERAL">k<tt + class="REPLACEABLE"><i>program</i></tt></tt>.</p> + + <p><b class="APPLICATION">Kerberos 5</b> is now built by + default in <tt class="LITERAL">buildworld</tt> + operations. Setting <tt + class="VARNAME">MAKE_KERBEROS5</tt> no longer has any + effect. Disabling the base system Kerberos 5 now requires + the <tt class="VARNAME">NO_KERBEROS</tt> Makefile + variable to be set.</p> + + <p><b class="APPLICATION">libpcap</b> now has support for + selecting among multiple data link types on an + interface.</p> + + <p><b class="APPLICATION">lukemftpd</b> (not built or + installed by default) has been updated to a snapshot from + 22 January 2003.</p> + + <p><b class="APPLICATION">OpenPAM</b> has been updated + from the ``Citronella'' release to the ``Dianthus'' + release.</p> + + <p><b class="APPLICATION">OpenSSH</b> has been updated to + 3.6.1p1.</p> + + <p><b class="APPLICATION">OpenSSL</b> has been updated to + release 0.9.7a. Among other features, this release + includes support for AES and takes advantage of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=crypto&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">crypto</span>(4)</span></a> + devices. [MERGED]</p> + + <p><b class="APPLICATION">sendmail</b> has been updated + to version 8.12.9. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcpdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcpdump</span>(1)</span></a> has + been updated to version 3.7.2. [MERGED] It also now + supports a <tt class="OPTION">-L</tt> flag to list the + data link types available on an interface and a <tt + class="OPTION">-y</tt> option to specify the data link + type to use while capturing packets.</p> + + <p><b class="APPLICATION">texinfo</b> has been updated + from 4.2 to 4.5.</p> + + <p>The timezone database has been updated from <tt + class="FILENAME">tzdata2002d</tt> to <tt + class="FILENAME">tzdata2003a</tt>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="PORTS" name="PORTS">2.5 + Ports/Packages Collection Infrastructure</a></h2> + + <p>The one-line <tt class="FILENAME">pkg-comment</tt> + files have been eliminated from each port skeleton; their + contents have been moved into each port's <tt + class="FILENAME">Makefile</tt>. This change reduces the + disk space and inodes used by the ports tree. + [MERGED]</p> + + <p>When fetching distfiles for building a port, the <tt + class="VARNAME">FETCH_REGET</tt> <tt + class="FILENAME">Makefile</tt> variable can be used to + specify the number of times to try continuing to fetch a + distfile if it fails its MD5 checksum. The port + infrastructure also supports re-fetching interrupted + distfiles.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_create</span>(1)</span></a> now + supports a <tt class="OPTION">-C</tt> option, which + allows packages to register a list of other packages with + which they conflict. They will refuse to install (via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a>) if + one of the listed packages is already present. The <tt + class="OPTION">-f</tt> flag to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a> + overrides this conflict-checking.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + honors the <tt class="VARNAME">BLOCKSIZE</tt> environment + variable in its output when the <tt + class="OPTION">-b</tt> flag is given.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + implements a <tt class="OPTION">-Q</tt> option, which is + similar to the <tt class="OPTION">-q</tt> ``quiet'' + option except that it prefixes the output with the + package name.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="RELENG" name="RELENG">2.6 + Release Engineering and Integration</a></h2> + + <p>The supported release of <b + class="APPLICATION">GNOME</b> has been updated to 2.2.1. + [MERGED]</p> + + <p>The supported release of <b + class="APPLICATION">KDE</b> has been updated to 3.1.2. + [MERGED]</p> + + <p>There is no longer a separate <tt + class="FILENAME">krb5</tt> distribution. The Kerberos 5 + libraries and utilities have been incorporated into the + <tt class="FILENAME">crypto</tt> distribution.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + once again supports installing individual components of + <b class="APPLICATION">XFree86</b>. Supporting changes + (not user-visible) generalize the concept of installing + parts of distributions as packages.</p> + + <p>The supported release of <b + class="APPLICATION">XFree86</b> has been updated to + 4.3.0. [MERGED]</p> + + <p>Several upgrade mechanisms designed to permit major + version upgrades from FreeBSD 2.<tt + class="REPLACEABLE"><i>X</i></tt> to 3.<tt + class="REPLACEABLE"><i>X</i></tt> and from FreeBSD 3.<tt + class="REPLACEABLE"><i>X</i></tt> to 4.<tt + class="REPLACEABLE"><i>X</i></tt> have been removed.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="DOC" name="DOC">2.7 + Documentation</a></h2> + + <p>The following new articles have been added to the + documentation set: ``FreeBSD From Scratch'', ``The + Roadmap for 5-STABLE''.</p> + + <p>A new Danish (<tt + class="FILENAME">da_DK.ISO8859-1</tt>) translation + project has been started.</p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 + Upgrading from previous releases of FreeBSD</a></h1> + + <p>Users with existing FreeBSD systems are <span + class="emphasis"><i class="EMPHASIS">highly</i></span> + encouraged to read the ``Early Adopter's Guide to FreeBSD + 5.1-RELEASE''. This document generally has the filename <tt + class="FILENAME">EARLY.TXT</tt> on the distribution media, + or any other place that the release notes can be found. It + offers some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> versus + running FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Upgrading FreeBSD should, of + course, only be attempted after backing up <span + class="emphasis"><i class="EMPHASIS">all</i></span> + data and configuration files.</p> + </blockquote> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p> + + <p align="center"><small>For questions about FreeBSD, read the + <a href="http://www.FreeBSD.org/docs.html">documentation</a> + before contacting <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-sparc64.html b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-sparc64.html new file mode 100644 index 0000000000..1565c115d2 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes-sparc64.html @@ -0,0 +1,1570 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + <title>FreeBSD/sparc64 5.1-RELEASE Release 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 id="AEN2" name="AEN2">FreeBSD/sparc64 + 5.1-RELEASE Release Notes</a></h1> + + <h3 class="CORPAUTHOR">The FreeBSD Project</h3> + + <p class="COPYRIGHT">Copyright © 2000, 2001, 2002, + 2003 by The FreeBSD Documentation Project</p> + + <p class="PUBDATE">$FreeBSD: + src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v + 1.573 2003/05/28 21:01:22 hrs Exp $<br /> + </p> + + <div> + <div class="ABSTRACT"> + <a id="AEN12" name="AEN12"></a> + + <p>The release notes for FreeBSD 5.1-RELEASE contain a + summary of recent changes made to the FreeBSD base + system on the 5-CURRENT development branch. This + document lists applicable security advisories that were + issued since the last release, as well as significant + changes to the FreeBSD kernel and userland. Some brief + remarks on upgrading are also presented.</p> + </div> + </div> + <hr /> + </div> + + <div class="TOC"> + <dl> + <dt><b>Table of Contents</b></dt> + + <dt>1 <a href="#INTRO">Introduction</a></dt> + + <dt>2 <a href="#NEW">What's New</a></dt> + + <dd> + <dl> + <dt>2.1 <a href="#SECURITY">Security + Advisories</a></dt> + + <dt>2.2 <a href="#KERNEL">Kernel Changes</a></dt> + + <dd> + <dl> + <dt>2.2.1 <a href="#PROC">Processor/Motherboard + Support</a></dt> + + <dt>2.2.2 <a href="#BOOT">Boot Loader + Changes</a></dt> + + <dt>2.2.3 <a href="#NET-IF">Network Interface + Support</a></dt> + + <dt>2.2.4 <a href="#NET-PROTO">Network + Protocols</a></dt> + + <dt>2.2.5 <a href="#DISKS">Disks and + Storage</a></dt> + + <dt>2.2.6 <a href="#FS">File Systems</a></dt> + + <dt>2.2.7 <a href="#PCCARD">PCCARD + Support</a></dt> + + <dt>2.2.8 <a href="#MM">Multimedia + Support</a></dt> + </dl> + </dd> + + <dt>2.3 <a href="#USERLAND">Userland Changes</a></dt> + + <dt>2.4 <a href="#CONTRIB">Contributed + Software</a></dt> + + <dt>2.5 <a href="#PORTS">Ports/Packages Collection + Infrastructure</a></dt> + + <dt>2.6 <a href="#RELENG">Release Engineering and + Integration</a></dt> + + <dt>2.7 <a href="#DOC">Documentation</a></dt> + </dl> + </dd> + + <dt>3 <a href="#UPGRADE">Upgrading from previous releases + of FreeBSD</a></dt> + </dl> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="INTRO" name="INTRO">1 + Introduction</a></h1> + + <p>This document contains the release notes for FreeBSD + 5.1-RELEASE on the UltraSPARC hardware platform. It + describes recently added, changed, or deleted features of + FreeBSD. It also provides some notes on upgrading from + previous versions of FreeBSD.</p> + + <p>This distribution of FreeBSD 5.1-RELEASE is a release + distribution. It 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> + or any of its mirrors. More information on obtaining this + (or other) release distributions of FreeBSD can be found in + the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html" + target="_top">``Obtaining FreeBSD'' appendix</a> to the <a + href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/" + target="_top">FreeBSD Handbook</a>.</p> + + <p>Users who are new to the 5-CURRENT series of FreeBSD + releases should also read the ``Early Adopters Guide to + FreeBSD 5.1-RELEASE''. This document can generally be found + in the same location as the release notes (either as a part + of a FreeBSD distribution or on the FreeBSD Web site). It + contains important information regarding the advantages and + disadvantages of using FreeBSD 5.1-RELEASE, as opposed to + releases based on the FreeBSD 4-STABLE development + branch.</p> + + <p>All users are encouraged to consult the release errata + before installing FreeBSD. The errata document is updated + with ``late-breaking'' information discovered late in the + release cycle or after the release. Typically, it contains + information on known bugs, security advisories, and + corrections to documentation. An up-to-date copy of the + errata for FreeBSD 5.1-RELEASE can be found on the FreeBSD + Web site.</p> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="NEW" name="NEW">2 What's + New</a></h1> + + <p>This section describes many of the user-visible new or + changed features in FreeBSD since 5.0-RELEASE. It includes + items that are unique to the 5-CURRENT branch, as well as + some features that may have been recently merged to other + branches (after FreeBSD 5.0-RELEASE). The latter items are + marked as [MERGED].</p> + + <p>Typical release note items document recent security + advisories issued after 5.0-RELEASE, new drivers or + hardware support, new commands or options, major bug fixes, + or contributed software upgrades. They may also list + changes to major ports/packages or release engineering + practices. Clearly the release notes cannot list every + single change made to FreeBSD between releases; this + document focuses primarily on security advisories, + user-visible changes, and major architectural + improvements.</p> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="SECURITY" name="SECURITY">2.1 + Security Advisories</a></h2> + + <p>A remotely exploitable vulnerability in <b + class="APPLICATION">CVS</b> has been corrected with the + import of version 1.11.5. More details can be found in + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:01.cvs.asc" + target="_top">FreeBSD-SA-03:01</a>. [MERGED]</p> + + <p>A timing-based attack on <b + class="APPLICATION">OpenSSL</b>, which could allow a very + powerful attacker access to plaintext under certain + circumstances, has been prevented via an upgrade to <b + class="APPLICATION">OpenSSL</b> 0.9.7. See security + advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:02.openssl.asc" + target="_top">FreeBSD-SA-03:02</a> for more details. + [MERGED]</p> + + <p>The security and performance of the ``syncookies'' + feature has been improved to decrease the chance of an + attacker being able to spoof connections. More details + are given in security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:03.syncookies.asc" + target="_top">FreeBSD-SA-03:03</a>. [MERGED]</p> + + <p>Remotely-exploitable buffer overflow vulnerabilities + in <b class="APPLICATION">sendmail</b> have been fixed by + updating <b class="APPLICATION">sendmail</b>. For more + details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:04.sendmail.asc" + target="_top">FreeBSD-SA-03:04</a> and <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:07.sendmail.asc" + target="_top">FreeBSD-SA-03:07</a>. [MERGED]</p> + + <p>A bounds-checking bug in the XDR implementation, which + could allow a remote attacker to cause a + denial-of-service, has been fixed. For more details see + security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:05.xdr.asc" + target="_top">FreeBSD-SA-03:05</a>. [MERGED]</p> + + <p>Two recently-publicized flaws in <b + class="APPLICATION">OpenSSL</b> have been corrected. For + more details, see security advisory <a + href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:06.openssl.asc" + target="_top">FreeBSD-SA-03:06</a>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="KERNEL" name="KERNEL">2.2 Kernel + Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a> is now + mandatory; the <tt class="LITERAL">NODEVFS</tt> option + has been removed from the set of possible kernel + configuration options.</p> + + <p>A minor bug in the permissions handling of <tt + class="FILENAME">/dev/tty</tt> has been fixed. As a + result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh</span>(1)</span></a> can now be + used after <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=su&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">su</span>(1)</span></a>.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstat&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstat</span>(2)</span></a> to + return <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed.</p> + + <p>A bug that caused <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kqueue&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kqueue</span>(2)</span></a> to + report <tt class="LITERAL">0</tt> as the number of bytes + available to read from a TCP socket has been fixed. The + <tt class="LITERAL">NOTE_LOWAT</tt> flag for <tt + class="LITERAL">EVFILT_READ</tt> has been fixed.</p> + + <p>Linux emulation mode now supports IPv6.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=madvise&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">madvise</span>(2)</span></a> now + supports a <tt class="LITERAL">MADV_PROTECT</tt> + behavior, which informs the virtual memory system that a + process is critical and should not be killed when swap + space has been exhausted. The process must be owned by + the superuser.</p> + + <p>A second process scheduler, designed to be a general + purpose scheduler with many SMP benefits, has been added + to the scheduler framework. Exactly one scheduler must be + specified in a kernel configuration. The original + scheduler may be selected using <tt + class="LITERAL">options SCHED_4BSD</tt>. The newer + (experimental) scheduler can be selected by using <tt + class="LITERAL">options SCHED_ULE</tt>.</p> + + <p>Device major numbers are now allocated dynamically by + default. This change greatly decreases the need for a + static, centralized table of major number assignments to + device drivers (a few drivers retain their old static + major numbers for compatibility), and also reduces the + possibility of running out of device major numbers.</p> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PROC" name="PROC">2.2.1 + Processor/Motherboard Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="BOOT" name="BOOT">2.2.2 Boot + Loader Changes</a></h3> + + <p>The <tt class="FILENAME">/modules</tt> directory + (once the default location for modules on FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>) is no longer a part + of the default <tt + class="VARNAME">kern.module_path</tt>. Third-party + modules should be placed in <tt + class="FILENAME">/boot/modules</tt>.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> Modules designed for use with + FreeBSD 4.<tt class="REPLACEABLE"><i>X</i></tt> are + likely to panic when loaded into a FreeBSD + 5.1-RELEASE kernel and should be used with extreme + caution.</p> + </blockquote> + </div> + <br /> + <br /> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-IF" name="NET-IF">2.2.3 + Network Interface Support</a></h3> + + <p>The cm driver now supports IPX. [MERGED]</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wlan&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wlan</span>(4)</span></a> module + provides 802.11 link-layer support. The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">wi</span>(4)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=an&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">an</span>(4)</span></a> drivers + now use this facility.</p> + + <p>A timing bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xl&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xl</span>(4)</span></a> driver, + which could cause a kernel panic (or other problems) + when configuring an interface, has been fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="NET-PROTO" + name="NET-PROTO">2.2.4 Network Protocols</a></h3> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">skipto</tt> rules can once again be + used with the <tt class="LITERAL">log</tt> keyword. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> <tt + class="LITERAL">uid</tt> rules are once again + working.</p> + + <p>It is now possible to build the <tt + class="LITERAL">FAST_IPSEC</tt> and <tt + class="LITERAL">INET6</tt> options into the same + kernel. (They still cannot be used together, + however.)</p> + + <p>A bug in TCP NewReno, which caused premature exit + from fast recovery when NewReno was enabled, has been + fixed. [MERGED]</p> + + <p>TCP now has support for the ``Limited Transmit'' + mechanism proposed by RFC 3042. This feature is + intended to improve the effectiveness of TCP loss + recovery in certain circumstances. It is off by default + but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3042</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>TCP now has support for increased initial congestion + window sizes as described in RFC 3390. This feature can + improve the throughput of short transfers, as well as + high-bandwidth, large propagation-delay connections. It + is off by default but can be enabled with the <tt + class="VARNAME">net.inet.tcp.rfc3390</tt> sysctl + variable. More information can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcp&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcp</span>(4)</span></a>.</p> + + <p>The IP fragment reassembly code behaves more + gracefully when receiving a large number of packet + fragments (it is designed to be more resistant to + fragment-based denial of service attacks). [MERGED]</p> + + <p>TCP connections in the <tt + class="LITERAL">TIME_WAIT</tt> state now use a special + protocol control block that uses less space than a + full-blown TCP PCB. This allows some of the data + structures and resources used by such a connection to + be freed earlier.</p> + + <p>It is now possible to specify the range of + ``privileged ports'' (TCP and UDP ports that require + superuser access to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bind&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bind</span>(2)</span></a> to). + The range is now specified with the <tt + class="VARNAME">net.inet.ip.portrange.reservedlow</tt> + and <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl variables, defaulting to the traditional UNIX + behavior. This feature is intended to help network + servers bind to traditionally privileged ports without + requiring superuser access. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ip&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ip</span>(4)</span></a> has more + details.</p> + + <p>Some bugs in the non-blocking RPC code has been + fixed. As a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=amd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">amd</span>(8)</span></a> users + are now able to mount volumes from a 5.1-RELEASE + server.</p> + + <p>Support for XNS networking, which has not worked + correctly for almost seven years, has been removed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="DISKS" name="DISKS">2.2.5 + Disks and Storage</a></h3> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=aac&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">aac</span>(4)</span></a> driver + now runs free of the Giant kernel lock. This change has + given a nearly 20% performance speedup on an SMP system + running multiple I/O intensive loads.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports all known SiS chipsets. (More details can + be found in the Hardware Notes.)</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now supports the Promise SATA150 TX2 and TX4 Serial + ATA/150 controllers.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ata</span>(4)</span></a> driver + now flushes devices on shutdown. This change may result + in failure messages being printed on the console for + devices that do not support flushing.</p> + + <p>The CAM layer now has support for devices with more + than 2<sup>32</sup> blocks. (Assuming 512-byte blocks, + this means support for devices larger than 2TB.)</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> For users upgrading across this + change, note that all userland applications that + talk to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pass&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pass</span>(4)</span></a> or + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xpt&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xpt</span>(4)</span></a> + devices must be recompiled. Examples of such + programs are <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=camcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">camcontrol</span>(8)</span></a> + in the base system, the <tt + class="FILENAME">sysutils/cdrtools</tt> port, and + the <tt class="FILENAME">multimedia/xmms</tt> + port.</p> + </blockquote> + </div> + <br /> + <br /> + + <p>A number of changes have been made to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=cd&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">cd</span>(4)</span></a> driver. + The primary user-visible change is improved + compatibility with ATAPI/USB/Firewire CDROM drives.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> is now + mandatory; the <tt class="LITERAL">NO_GEOM</tt> has + been removed from the set of kernel configuration + options.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=iir&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">iir</span>(4)</span></a> driver + has been updated; this update is believed to fix + problems detecting attached disks during + installation.</p> + + <p>A bug in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mly&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mly</span>(4)</span></a> driver + that caused hangs has been corrected.</p> + + <p>Support has been added for volume labels on UFS and + UFS2 file systems. These labels are strings that can be + used to identify a volume, regardless of what device it + appears on. Labels can be set with the <tt + class="OPTION">-L</tt> options to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> or <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tunefs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tunefs</span>(8)</span></a>. With + the <tt class="LITERAL">GEOM_VOL</tt> module, volumes + can be accessed using their labels under <tt + class="FILENAME">/dev/vol</tt>.</p> + + <p>The root file system can now be located on a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> + volume. More information can be found in the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vinum&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vinum</span>(4)</span></a> manual + page.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="FS" name="FS">2.2.6 File + Systems</a></h3> + + <p>A new <tt class="LITERAL">DIRECTIO</tt> kernel + option enables support for read operations that bypass + the buffer cache and put data directly into a userland + buffer. This feature requires that the <tt + class="LITERAL">O_DIRECT</tt> flag is set on the file + descriptor and that both the offset and length for the + read operation are multiples of the physical media + sector size. [MERGED]</p> + + <p>NETNCP and Netware File System Support (nwfs) are + once again working.</p> + + <p>Bugs that could cause the unmounting of a smbfs + share to fail or cause a kernel panic have been + fixed.</p> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="PCCARD" name="PCCARD">2.2.7 + PCCARD Support</a></h3> + </div> + + <div class="SECT3"> + <hr /> + + <h3 class="SECT3"><a id="MM" name="MM">2.2.8 Multimedia + Support</a></h3> + </div> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="USERLAND" name="USERLAND">2.3 + Userland Changes</a></h2> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + correctly handles setting user passwords containing + special shell characters.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=adduser&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">adduser</span>(8)</span></a> now + supports a <tt class="OPTION">-g</tt> option to set a + user's default login group.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> + utility is a replacement for the older disklabel utility. + Like its predecessor, it installs, examines, or modifies + the BSD label on a disk partition, and can install + bootstrap code. Compared to disklabel, a number of + obsolete options and parameters have been retired. A new + <tt class="OPTION">-m</tt> option instructs <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> to + use the layout suitable for a specific machine.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chgrp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chgrp</span>(1)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chown&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chown</span>(8)</span></a> now, + when the owner/group is modified, print the old and new + uid/gid if the <tt class="OPTION">-v</tt> option is + specified more than once.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=config&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">config</span>(8)</span></a> now + implements a <tt class="LITERAL">nodevice</tt> kernel + configuration file directive that cancels the effect of a + <tt class="LITERAL">device</tt> directive. The new <tt + class="LITERAL">nooption</tt> and <tt + class="LITERAL">nomakeoption</tt> directives cancel prior + <tt class="LITERAL">options</tt> and <tt + class="LITERAL">makeoptions</tt> directives, + respectively.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=diskinfo&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">diskinfo</span>(8)</span></a> + utility has been added to show information about a disk + device and optionally to run a naive performance + test.</p> + + <p>The disklabel utility has been replaced by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>. On + the alpha, i386, and pc98 platforms, disklabel is a link + to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dump</span>(8)</span></a> now + supports caching of disk blocks with the <tt + class="OPTION">-C</tt> option. This can improve dump + performance at the cost of possibly missing file system + updates that occur between passes.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dumpfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dumpfs</span>(8)</span></a> now + supports a <tt class="OPTION">-m</tt> flag to print file + system parameters in the form of a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> + command.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elfdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elfdump</span>(1)</span></a>, a + utility to display information about <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=elf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">elf</span>(5)</span></a> format + executable files, has been added.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(1)</span></a> uses the + <tt class="FILENAME">.netrc</tt> support in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> and also + supports a <tt class="OPTION">-N</tt> to specify an + alternate <tt class="FILENAME">.netrc</tt> file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fetch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fetch</span>(3)</span></a> now has + support for <tt class="FILENAME">.netrc</tt> files (see + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftp&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftp</span>(1)</span></a> for more + details).</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-h</tt> option to disable + printing any host-specific information, such as the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> version + or hostname, in server messages. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports a <tt class="OPTION">-P</tt> option to specify a + port on which to listen in daemon mode. The default data + port number is now set to be one less than the control + port number, rather than being hard-coded. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports an extended format of the <tt + class="FILENAME">/etc/ftpchroot</tt> file. Please refer + to the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> + manpage, which is now available, for details. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpd</span>(8)</span></a> now + supports login directory pathnames that specify + simultaneously a directory for <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> and + that to change to in the chrooted environment. The <tt + class="LITERAL">/./</tt> separator is used for this + purpose, like in other FTP daemons having this feature. + It may be used in both <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ftpchroot&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ftpchroot</span>(5)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=passwd&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">passwd</span>(5)</span></a>. + [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fwcontrol&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fwcontrol</span>(8)</span></a> now + supports <tt class="OPTION">-R</tt> and <tt + class="OPTION">-S</tt> options for receiving and sending + DV streams. [MERGED]</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=gstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">gstat</span>(8)</span></a> utility + has been added to show the disk activity inside the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(8)</span></a> now + supports <tt class="LITERAL">enable</tt> and <tt + class="LITERAL">disable</tt> commands to control various + aspects of the operation of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ipfw</span>(4)</span></a> + (including enabling and disabling the firewall itself). + These provide a more convenient and visible interface + than the existing sysctl variables. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jail</span>(8)</span></a> now + supports a <tt class="OPTION">-i</tt> flag to output an + identifier for a newly-created jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jexec&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jexec</span>(8)</span></a> utility + has been added to execute a command inside an existing + jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=jls&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">jls</span>(8)</span></a> utility + has been added to list existing jails.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=kenv&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">kenv</span>(1)</span></a> has been + moved from <tt class="FILENAME">/usr/bin</tt> to <tt + class="FILENAME">/bin</tt> to make it available at times + during system startup when only the root file system is + mounted.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=killall&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">killall</span>(1)</span></a> now + supports a <tt class="OPTION">-j</tt> option to kill all + processes inside a jail.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libgeom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libgeom</span>(3)</span></a> + library has been added to allow some userland access to + the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=geom&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">geom</span>(4)</span></a> + subsystem.</p> + + <p>The mac_portacl MAC policy module has been added. It + provides a simple ACL mechanism to permit users and + groups to bind ports for TCP or UDP, and is intended to + be used in conjunction with the recently-added <tt + class="VARNAME">net.inet.ip.portrange.reservedhigh</tt> + sysctl.</p> + + <p>The <tt class="FILENAME">MAKEDEV</tt> script is now + unnecessary, due to the mandatory presence of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=devfs&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">devfs</span>(5)</span></a>, and has + been removed.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a> + now supports a <tt class="OPTION">-P</tt> option to + preserve the contents of files being replaced.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mixer&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mixer</span>(8)</span></a> can now + implement relative volume adjustments.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mksnap_ffs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mksnap_ffs</span>(8)</span></a> + program has been added to allow easier creation of FFS + snapshots. It is a SUID-<tt class="USERNAME">root</tt> + executable designed for use by members of the <tt + class="GROUPNAME">operator</tt> group.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=umount&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">umount</span>(8)</span></a> now + accept a <tt class="OPTION">-F</tt> option to specify an + alternate <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=fstab&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">fstab</span>(5)</span></a> + file.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports a <tt class="OPTION">-c</tt> flag to avoid doing + a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=connect&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">connect</span>(2)</span></a> for + UDP mount points. This option must be used if the server + does not reply to requests from the standard NFS port + number 2049 or if it replies to requests using a + different IP address (which can occur if the server is + multi-homed). Setting the <tt + class="VARNAME">vfs.nfs.nfs_ip_paranoia</tt> sysctl to + <tt class="LITERAL">0</tt> will make this option the + default. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mount_nfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mount_nfs</span>(8)</span></a> now + supports the <tt class="OPTION">noinet4</tt> and <tt + class="OPTION">noinet6</tt> mount options to prevent NFS + mounts from using IPv4 or IPv6 respectively.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newfs</span>(8)</span></a> will now + create UFS2 file systems by default, unless UFS1 is + specifically requested with the <tt + class="OPTION">-O1</tt> option.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=newsyslog&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">newsyslog</span>(8)</span></a> has + a number of new features. Among them:</p> + + <ul> + <li> + <p>A <tt class="LITERAL">W</tt> flag forces + previously-started compression jobs for an entry (or + group of entries specified with the <tt + class="LITERAL">G</tt> flag) to finish before + beginning a new one. This feature is designed to + prevent system overloads caused by starting several + compression jobs on big files simultaneously. + [MERGED]</p> + </li> + + <li> + <p>A ``default rotate action'', to be used for files + specified for rotation but not specified in the + configuration file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="OPTION">-s</tt> command-line flag to + disable sending signals to processes when rotating + files. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">N</tt> configuration file + flag to indicate that no process needs to be signaled + when rotating a file. [MERGED]</p> + </li> + + <li> + <p>A <tt class="LITERAL">U</tt> configuration file + flag to specify that a process group (rather than a + single process) should be signaled when rotating + files. [MERGED]</p> + </li> + </ul> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + now thread-safe and implements support for Name Service + Switch (NSS) modules. NSS modules may be statically built + into <tt class="FILENAME">libc</tt> or dynamically loaded + via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dlopen&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dlopen</span>(3)</span></a>. They + are loaded/initialized at configuration time (i.e. when + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsdispatch&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsdispatch</span>(3)</span></a> is + called and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=nsswitch.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">nsswitch.conf</span>(5)</span></a> + is read or re-read).</p> + + <p>A new <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_chroot&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_chroot</span>(8)</span></a> + module has been added, which does a <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=chroot&sektion=2&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">chroot</span>(2)</span></a> + operation for users into either a predetermined directory + or one derived from their home directory.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pam_ssh&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pam_ssh</span>(8)</span></a> has + been rewritten. One side effect of the rewrite is that it + now starts a separate instance of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ssh-agent&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ssh-agent</span>(1)</span></a> for + each session instead of trying to connect each session to + the agent started by the first session.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-D</tt> flag to set the + ``Don't Fragment'' bit on outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-M</tt> option to use ICMP + mask request or timestamp request messages instead of + ICMP echo requests.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=ping&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">ping</span>(8)</span></a> now + supports a <tt class="OPTION">-z</tt> flag to set the + Type of Service bits in outgoing packets.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pw&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pw</span>(8)</span></a> can now add + a user whose name ends with a <tt class="LITERAL">$</tt> + character; this change is intended to help administration + of <b class="APPLICATION">Samba</b> services. + [MERGED]</p> + + <p>The format of the <tt + class="FILENAME">/etc/pwd.db</tt> and <tt + class="FILENAME">/etc/spwd.db</tt> password databases + created by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pwd_mkdb&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pwd_mkdb</span>(8)</span></a> is + now byte-order independent. The pre-processed password + databases can now be moved between machines of different + architectures. The format includes version numbers on + entries to ensure compatibility with old binaries.</p> + + <p>A bug in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> that + could cause a sequence to remain stuck at <tt + class="LITERAL">0</tt> has been fixed. (<a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rand&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rand</span>(3)</span></a> remains + unsuitable for all but trivial uses.)</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rtld&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rtld</span>(1)</span></a> now has + support for the dynamic mapping of shared object + dependencies. This optional feature is especially useful + when experimenting with different threading libraries. It + is not, however, built by default. More information on + enabling and using this feature can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=libmap.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">libmap.conf</span>(5)</span></a>.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_open&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_open</span>(3)</span></a> now + correctly handles multiple opens of the same semaphore; + as a result, <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sem_close&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sem_close</span>(3)</span></a> no + longer crashes calling programs.</p> + + <p>The seeding algorithm used by <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=srandom&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">srandom</span>(3)</span></a> has + been strengthened.</p> + + <p>The sunlabel utility, a program analogous to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=bsdlabel&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">bsdlabel</span>(8)</span></a> that + works on Sun disk labels, has been added.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + will now select UFS2 as the default layout for new file + systems unless specifically requested in the disk + labeler.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + command has been added to disable paging and swapping on + a device. A related <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapctl&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapctl</span>(8)</span></a> + command has been added to provide an interface to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapon&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapon</span>(8)</span></a> and <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + similar to other BSDs.</p> + + <div class="NOTE"> + <blockquote class="NOTE"> + <p><b>Note:</b> The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=swapoff&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">swapoff</span>(8)</span></a> + feature should be considered experimental.</p> + </blockquote> + </div> + <br /> + <br /> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslogd&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslogd</span>(8)</span></a> now + allows multiple hosts or programs to be named in host or + program specifications in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=syslog.conf&sektion=5&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">syslog.conf</span>(5)</span></a> + files.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=systat&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">systat</span>(1)</span></a> now + includes an <tt class="OPTION">-ifstat</tt> display mode + that displays the network traffic going through active + interfaces on the system.</p> + + <p>The <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=usbhidaction&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">usbhidaction</span>(1)</span></a> + command has been added; it performs actions according to + its configuration in response to USB HID controls.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=uudecode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">uudecode</span>(1)</span></a> and + <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=b64decode&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">b64decode</span>(1)</span></a> now + support a <tt class="OPTION">-r</tt> flag for decoding + raw (or broken) files that may be missing the initial and + possibly final framing lines. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=vmstat&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">vmstat</span>(8)</span></a> has + re-implemented the <tt class="OPTION">-f</tt> flag, which + displays statistics on fork operations.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-P</tt> option to execute + multiple copies of the same utility in parallel.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=xargs&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">xargs</span>(1)</span></a> now + supports a <tt class="OPTION">-o</tt> flag to reopen <tt + class="FILENAME">/dev/tty</tt> for the child process + before executing the command. This is useful when the + child process is an interactive application.</p> + + <p>A 1:1 threading package (where for every pthread in an + application there is one KSE and thread) has been + implemented. Under this model, the kernel handles all + thread scheduling decisions and all signal delivery. This + uses some of the common KSE code, and is a restricted + case of the M:N threading work still in progress. The <tt + class="FILENAME">libthr</tt> library implementing the + userland portion of this functionality is a drop-in + replacement for the <tt class="FILENAME">libc_r</tt> + library. Note that <tt class="FILENAME">libthr</tt> is + not (at this time) built by default.</p> + + <p>The historic BSD boot scripts in <tt + class="FILENAME">/etc</tt> have been removed, in favor of + the <tt class="FILENAME">rc.d</tt> system imported from + <b class="APPLICATION">NetBSD</b> (sometimes referred to + as ``rcNG''). All functionality of the historic system + has been preserved. In particular, files such as <tt + class="FILENAME">/etc/rc.conf</tt> continue to be the + recommended means of configuring the system startup. The + <tt class="FILENAME">rc.d</tt> system has been the + default since FreeBSD 5.0-RELEASE, so this change should + be largely transparent for the vast majority of users. + Users who have customized their historic-style startup + scripts should be aware that the following files have + been removed from <tt class="FILENAME">/etc</tt>: <tt + class="FILENAME">rc.atm</tt>, <tt + class="FILENAME">rc.devfs</tt>, <tt + class="FILENAME">rc.diskless1</tt>, <tt + class="FILENAME">rc.diskless2</tt>, <tt + class="FILENAME">rc.i386</tt>, <tt + class="FILENAME">rc.alpha</tt>, <tt + class="FILENAME">rc.amd64</tt>, <tt + class="FILENAME">rc.ia64</tt>, <tt + class="FILENAME">rc.sparc64</tt>, <tt + class="FILENAME">rc.isdn</tt>, <tt + class="FILENAME">rc.network</tt>, <tt + class="FILENAME">rc.network6</tt>, <tt + class="FILENAME">rc.pccard</tt>, <tt + class="FILENAME">rc.serial</tt>, <tt + class="FILENAME">rc.syscons</tt>, <tt + class="FILENAME">rc.sysctl</tt>. <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=mergemaster&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">mergemaster</span>(8)</span></a>, + when run, will offer to move these files out of the way + for convenience. More details can be found in <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=rc.subr&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">rc.subr</span>(8)</span></a>.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="CONTRIB" name="CONTRIB">2.4 + Contributed Software</a></h2> + + <p>The <b class="APPLICATION">ACPI-CA</b> code has been + updated from the 20021118 snapshot to the 20030228 + snapshot.</p> + + <p><b class="APPLICATION">awk</b> from Bell Labs has been + updated to a 14 March 2003 snapshot.</p> + + <p><b class="APPLICATION">BIND</b> has been updated to + version 8.3.4. [MERGED]</p> + + <p>All of the <b class="APPLICATION">bzip2</b> suite of + applications is now installed in the base system (in + particular, <tt class="COMMAND">bzip2recover</tt> is now + built and installed). [MERGED]</p> + + <p><b class="APPLICATION">CVS</b> has been updated to + 1.11.5. [MERGED]</p> + + <p><b class="APPLICATION">FILE</b> has been updated to + 3.41. [MERGED]</p> + + <p><b class="APPLICATION">GCC</b> has been updated to + 3.2.2 (release version).</p> + + <p>The <b class="APPLICATION">gdtoa</b> library, for + conversions between strings and floating point, has been + imported. These sources were dated 24 March 2003.</p> + + <p><b class="APPLICATION">groff</b> (and related + utilities) have been updated from 1.18.1 to 1.19.</p> + + <p><b class="APPLICATION">IPFilter</b> has been updated + to 3.4.31. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client has + been updated to 3.0.1RC11. [MERGED]</p> + + <p>The <b class="APPLICATION">ISC DHCP</b> client now + includes the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=omshell&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">omshell</span>(1)</span></a> + utility and the <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=dhcpctl&sektion=3&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">dhcpctl</span>(3)</span></a> + library for run-time control of the client.</p> + + <p><b class="APPLICATION">Kerberos IV</b> support (in the + form of <b class="APPLICATION">KTH eBones</b>) has been + removed. Users requiring this functionality can still get + it from the <tt class="FILENAME">security/krb4</tt> port + (or package). Kerberos IV compatibility mode for Kerberos + 5 has been removed, and the <tt class="LITERAL">k5<tt + class="REPLACEABLE"><i>program</i></tt></tt> userland + utilities have been renamed to <tt class="LITERAL">k<tt + class="REPLACEABLE"><i>program</i></tt></tt>.</p> + + <p><b class="APPLICATION">Kerberos 5</b> is now built by + default in <tt class="LITERAL">buildworld</tt> + operations. Setting <tt + class="VARNAME">MAKE_KERBEROS5</tt> no longer has any + effect. Disabling the base system Kerberos 5 now requires + the <tt class="VARNAME">NO_KERBEROS</tt> Makefile + variable to be set.</p> + + <p><b class="APPLICATION">libpcap</b> now has support for + selecting among multiple data link types on an + interface.</p> + + <p><b class="APPLICATION">lukemftpd</b> (not built or + installed by default) has been updated to a snapshot from + 22 January 2003.</p> + + <p><b class="APPLICATION">OpenPAM</b> has been updated + from the ``Citronella'' release to the ``Dianthus'' + release.</p> + + <p><b class="APPLICATION">OpenSSH</b> has been updated to + 3.6.1p1.</p> + + <p><b class="APPLICATION">OpenSSL</b> has been updated to + release 0.9.7a. Among other features, this release + includes support for AES and takes advantage of <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=crypto&sektion=4&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">crypto</span>(4)</span></a> + devices. [MERGED]</p> + + <p><b class="APPLICATION">sendmail</b> has been updated + to version 8.12.9. [MERGED]</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=tcpdump&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">tcpdump</span>(1)</span></a> has + been updated to version 3.7.2. [MERGED] It also now + supports a <tt class="OPTION">-L</tt> flag to list the + data link types available on an interface and a <tt + class="OPTION">-y</tt> option to specify the data link + type to use while capturing packets.</p> + + <p><b class="APPLICATION">texinfo</b> has been updated + from 4.2 to 4.5.</p> + + <p>The timezone database has been updated from <tt + class="FILENAME">tzdata2002d</tt> to <tt + class="FILENAME">tzdata2003a</tt>. [MERGED]</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="PORTS" name="PORTS">2.5 + Ports/Packages Collection Infrastructure</a></h2> + + <p>The one-line <tt class="FILENAME">pkg-comment</tt> + files have been eliminated from each port skeleton; their + contents have been moved into each port's <tt + class="FILENAME">Makefile</tt>. This change reduces the + disk space and inodes used by the ports tree. + [MERGED]</p> + + <p>When fetching distfiles for building a port, the <tt + class="VARNAME">FETCH_REGET</tt> <tt + class="FILENAME">Makefile</tt> variable can be used to + specify the number of times to try continuing to fetch a + distfile if it fails its MD5 checksum. The port + infrastructure also supports re-fetching interrupted + distfiles.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_create&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_create</span>(1)</span></a> now + supports a <tt class="OPTION">-C</tt> option, which + allows packages to register a list of other packages with + which they conflict. They will refuse to install (via <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a>) if + one of the listed packages is already present. The <tt + class="OPTION">-f</tt> flag to <a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_add</span>(1)</span></a> + overrides this conflict-checking.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + honors the <tt class="VARNAME">BLOCKSIZE</tt> environment + variable in its output when the <tt + class="OPTION">-b</tt> flag is given.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=pkg_info&sektion=1&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">pkg_info</span>(1)</span></a> now + implements a <tt class="OPTION">-Q</tt> option, which is + similar to the <tt class="OPTION">-q</tt> ``quiet'' + option except that it prefixes the output with the + package name.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="RELENG" name="RELENG">2.6 + Release Engineering and Integration</a></h2> + + <p>The supported release of <b + class="APPLICATION">GNOME</b> has been updated to 2.2.1. + [MERGED]</p> + + <p>The supported release of <b + class="APPLICATION">KDE</b> has been updated to 3.1.2. + [MERGED]</p> + + <p>There is no longer a separate <tt + class="FILENAME">krb5</tt> distribution. The Kerberos 5 + libraries and utilities have been incorporated into the + <tt class="FILENAME">crypto</tt> distribution.</p> + + <p><a + href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.1-release"> + <span class="CITEREFENTRY"><span + class="REFENTRYTITLE">sysinstall</span>(8)</span></a> + once again supports installing individual components of + <b class="APPLICATION">XFree86</b>. Supporting changes + (not user-visible) generalize the concept of installing + parts of distributions as packages.</p> + + <p>The supported release of <b + class="APPLICATION">XFree86</b> has been updated to + 4.3.0. [MERGED]</p> + + <p>Several upgrade mechanisms designed to permit major + version upgrades from FreeBSD 2.<tt + class="REPLACEABLE"><i>X</i></tt> to 3.<tt + class="REPLACEABLE"><i>X</i></tt> and from FreeBSD 3.<tt + class="REPLACEABLE"><i>X</i></tt> to 4.<tt + class="REPLACEABLE"><i>X</i></tt> have been removed.</p> + </div> + + <div class="SECT2"> + <hr /> + + <h2 class="SECT2"><a id="DOC" name="DOC">2.7 + Documentation</a></h2> + + <p>The following new articles have been added to the + documentation set: ``FreeBSD From Scratch'', ``The + Roadmap for 5-STABLE''.</p> + + <p>A new Danish (<tt + class="FILENAME">da_DK.ISO8859-1</tt>) translation + project has been started.</p> + </div> + </div> + + <div class="SECT1"> + <hr /> + + <h1 class="SECT1"><a id="UPGRADE" name="UPGRADE">3 + Upgrading from previous releases of FreeBSD</a></h1> + + <p>Users with existing FreeBSD systems are <span + class="emphasis"><i class="EMPHASIS">highly</i></span> + encouraged to read the ``Early Adopter's Guide to FreeBSD + 5.1-RELEASE''. This document generally has the filename <tt + class="FILENAME">EARLY.TXT</tt> on the distribution media, + or any other place that the release notes can be found. It + offers some notes on upgrading, but more importantly, also + discusses some of the relative merits of upgrading to + FreeBSD 5.<tt class="REPLACEABLE"><i>X</i></tt> versus + running FreeBSD 4.<tt + class="REPLACEABLE"><i>X</i></tt>.</p> + + <div class="IMPORTANT"> + <blockquote class="IMPORTANT"> + <p><b>Important:</b> Upgrading FreeBSD should, of + course, only be attempted after backing up <span + class="emphasis"><i class="EMPHASIS">all</i></span> + data and configuration files.</p> + </blockquote> + </div> + </div> + </div> + <hr /> + + <p align="center"><small>This file, and other release-related + documents, can be downloaded from <a + href="ftp://ftp.FreeBSD.org/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 <<a + href="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p> + + <p align="center"><small><small>All users of FreeBSD 5-CURRENT + should subscribe to the <<a + href="mailto:current@FreeBSD.org">current@FreeBSD.org</a>> + mailing list.</small></small></p> + + <p align="center">For questions about this documentation, + e-mail <<a + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</p> + <br /> + <br /> + </body> +</html> + diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes.sgml b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes.sgml new file mode 100644 index 0000000000..db213a49af --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes.sgml @@ -0,0 +1,32 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$FreeBSD: www/en/releases/5.1R/relnotes.sgml,v 1.3 2005/10/04 06:52:23 murray Exp $"> +<!ENTITY title "FreeBSD 5.1-RELEASE Release Notes"> +<!ENTITY % navinclude.download "INCLUDE"> +]> +<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.1-RELEASE are available for the following + platforms:</p> + + <ul> + <li><a href="relnotes-alpha.html">alpha</a></li> + <li><a href="relnotes-i386.html">i386</a></li> + <li><a href="relnotes-ia64.html">ia64</a></li> + <li><a href="relnotes-pc98.html">pc98</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> + + &footer; + +</body> +</html> diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/schedule.sgml b/en_US.ISO8859-1/htdocs/releases/5.1R/schedule.sgml new file mode 100644 index 0000000000..207fb362bd --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/schedule.sgml @@ -0,0 +1,181 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY email 'freebsd-qa'> +<!ENTITY date "$FreeBSD: www/en/releases/5.1R/schedule.sgml,v 1.15 2005/10/04 06:52:23 murray Exp $"> +<!ENTITY title "FreeBSD 5.1 Release Process"> +<!ENTITY % navinclude.download "INCLUDE"> +]> + +<html> +&header; + +<h1>Introduction</h1> + +<p>This is a specific schedule for the release of FreeBSD 5.1. For + more general information about the release engineering process, + please see the <a href="&base;/releng/index.html">Release + Engineering</a> section of the web site.</p> + +<p>General discussions about the release engineering process or + quality assurance issues should be sent to the public <a + href="mailto:FreeBSD-qa@FreeBSD.org">FreeBSD-qa</a> mailing list. + <a + href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a> + requests should be sent to <a + href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>.</p> + +<p>One of the major features of FreeBSD 5.1 will be further refinement of + the re-worked SMP support introduced in FreeBSD 5.0. For specific + information about the progress towards 5.1-RELEASE in this area, please + see the <a href="&base;/smp/index.html">SMP Project</a> page.</p> + +<p>FreeBSD 5.1 will continue to be released from the 5-CURRENT development + stream. For more details about the milestones for reaching + 5-STABLE, see the <a href="&base;/doc/en/articles/5-roadmap">5-STABLE + Roadmap</a> page.</p> + +<p>The current release engineering <a + href="&base;/releases/5.1R/todo.html">TODO list</a> is also available. + This list is updated periodically through the release cycle.</p> + +<h1>Schedule</h1> + +<table class="tblbasic"> + <tr> + <td>Action</td> + <td>Expected</td> + <td>Actual</td> + <td>Description</td> + </tr> + + <tr> + <td><tt>-CURRENT</tt> code freeze</td> + <td>5 May 2003</td> + <td>5 May 2003</td> + <td>The <tt>src/</tt> code freeze for 5.1. Commits to + <tt>HEAD</tt> require <tt>re@FreeBSD.org</tt> approval.</td> + </tr> + + <tr> + <td><tt>5.1-BETA</tt></td> + <td>5 May 2003</td> + <td>15 May 2003</td> + <td><tt>5.1-BETA</tt> release of x86, alpha, sparc64, and ia64.</td> + </tr> + + <tr> + <td><tt>5.1-BETA2</tt></td> + <td>19 May 2003</td> + <td>22 May 2003</td> + <td>Second <tt>5.1-BETA</tt> release of x86, alpha, sparc64, and ia64.</td> + </tr> + + <tr> + <td><tt>RELENG_5_1</tt> branched</td> + <td>30 May 2003</td> + <td>31 May 2003</td> + <td>Branch of <tt>src/</tt> from <tt>HEAD</tt> for the release. + Note: no branch for <tt>RELENG_5</tt> will happen at this time.</td> + </tr> + + <tr> + <td>Turn off debugging for <tt>RELENG_5_1</tt></td> + <td>30 May 2003</td> + <td>31 May 2003</td> + <td>Turn off WITNESS, INVARIANTS, and malloc debugging options similar to + what was done for 5.0.</td> + </tr> + + <tr> + <td>First release candidate</td> + <td>30 May 2003</td> + <td>1 June 2003</td> + <td>x86, alpha, sparc64, and ia64 images released and uploaded to + <tt>ftp-master.FreeBSD.org</tt>.</td> + </tr> + + <tr> + <td><tt>src/</tt> unfrozen</td> + <td>30 May 2003</td> + <td>31 May 2003</td> + <td>Unfreeze <tt>HEAD</tt> src. Continue to coordinate significant + check-ins with <tt>re@FreeBSD.org</tt> in order to work towards + <tt>5-STABLE</tt>.</td> + </tr> + + <tr> + <td>Ports tree tagged</td> + <td>30 May 2003</td> + <td>27 May 2003</td> + <td>Tentative date of <tt>RELEASE_5_1_0</tt> tag for ports.</td> + </tr> + + <tr> + <td>Version numbers bumped</td> + <td>2 June 2003</td> + <td>3 June 2003</td> + <td>The files listed <a + href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP">here</a> + are updated to reflect FreeBSD 5.1.</td> + </tr> + + <tr> + <td><tt>src/</tt> tree tagged</td> + <td>2 June 2003</td> + <td>4 June 2003</td> + <td>Tag the <tt>RELENG_5_1</tt> branch with <tt>RELENG_5_1_0_RELEASE</tt>.</td> + </tr> + + <tr> + <td><tt>doc/</tt> tree tagged</td> + <td>2 June 2003</td> + <td>30 May 2003</td> + <td>Tag the <tt>doc/</tt> tree with <tt>RELEASE_5_1_0</tt>.</td> + </tr> + + <tr> + <td>Final builds</td> + <td>2 June 2003</td> + <td>4 June 2003</td> + <td>Start x86, alpha, sparc64, ia64, and pc98 builds.</td> + </tr> + + <tr> + <td>Warn <tt>hubs@FreeBSD.org</tt></td> + <td>5 June 2003</td> + <td>5 June 2003</td> + <td>Heads up email to <tt>hubs@FreeBSD.org</tt> to give admins + time to prepare for the load spike to come. The site + administrators have frequently requested advance notice + for new ISOs.</td> + </tr> + + <tr> + <td>Upload to <tt>ftp-master</tt></td> + <td>5 June 2003</td> + <td>8 June 2003</td> + <td>Release and packages uploaded to <tt>ftp-master.FreeBSD.org.</tt></td> + </tr> + + <tr> + <td>FreeBSD 5.1 Released</td> + <td>9 June 2003</td> + <td>9 June 2003</td> + <td>FreeBSD 5.1 is announced to the mailing lists.</td> + </tr> + + <tr> + <td>FreeBSD 5.1 Press Release</td> + <td>9 June 2003</td> + <td>9 June 2003</td> + <td>A formal press release statement is in the works and should be + released at this time to the <tt>www.FreeBSD.org</tt> website and various + tech publications.</td> + </tr> + +</table> + + &footer; + + </body> +</html> diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/todo.sgml b/en_US.ISO8859-1/htdocs/releases/5.1R/todo.sgml new file mode 100644 index 0000000000..cd961082f6 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.1R/todo.sgml @@ -0,0 +1,111 @@ +<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY email 'freebsd-qa'> +<!ENTITY date "$FreeBSD: www/en/releases/5.1R/todo.sgml,v 1.61 2005/10/04 06:52:23 murray Exp $"> +<!ENTITY title "FreeBSD 5.1 Open Issues"> +<!ENTITY % navinclude.download "INCLUDE"> +<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers; +]> + +<html> +&header; + +<h1>Open Issues</h1> + +<p>This is a list of open issues that need to be resolved for FreeBSD + 5.1. If you have any updates for this list, please e-mail + re@FreeBSD.org.</p> + +<h3>Must Resolve Issues for 5.1-RELEASE</h3> + +<table class="tblbasic"> + <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th> + </tr> + +</table> + +<h3>Desired Features for 5.1-RELEASE</h3> + +<table class="tblbasic"> + <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th> + </tr> + +</table> + +<h3>Documentation items that must be resolved for 5.1</h3> + +<table class="tblbasic"> + <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th> + </tr> + +</table> + +<h3>Areas requiring immediate testing</h3> + +<table class="tblbasic"> + <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th> + </tr> + + <tr> + <td>Fresh ACPI-CA import</td> + <td>--</td> + <td>--</td> + <td>The 20030228 vendor sources have been imported. Further testing is + appreciated.</td> + </tr> + + <tr> + <td>PAE support for i386</td> + <td>--</td> + <td>--</td> + <td>PAE support allows the use of up to 64GB of RAM on Pentium Pro and above + systems. Virtual addresses are still constrained to 32-bits.</td> + </tr> + + <tr> + <td>if_wi problems on Lucent hardware</td> + <td>--</td> + <td>--</td> + <td>The recently upgraded if_wi driver is more tuned to Prism hardware + than to Lucent hardware, resulting in system lockups and poor performance + when using Lucent hardware. These problems are believed to be fixed + but more testing is welcome.</td> + </tr> + + <tr> + <td>UFS2 as installation, newfs default</td> + <td>--</td> + <td>&a.rwatson;</td> + <td>For 5.1-RELEASE, the default file system type for newly created + file systems is UFS2 rather than UFS1. newfs(8) and sysinstall(8) + have been updated to use this new default. Testing to make sure all + goes well after the change (committed on April 20, 2003) is + vital.</td> + </tr> + + <tr> + <td>NSSwitch support</td> + <td>--</td> + <td>&a.nectar;</td> + <td>Support for pluggable directory services using NSS, including + adaptations of current directory services (local databases, NIS), + and support for new services (LDAP, Active Directory, etc). + This change has been committed, and requires broader testing.</td> + </tr> + + <tr> + <td>Spurious alpha panics</td> + <td>--</td> + <td>--</td> + <td>&a.kris; reports that he has seen several unique panics on the + alpha machines, but since gdb -k doesn't work on alpha I haven't + been able to get more than a DDB traceback. No-one has looked + into them.</td> + </tr> + +</table> + + &footer; + + </body> +</html> |