d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

First commit of RELNOTESng, the rewrite of the *.TXT documentation

Browse Source 
files.

src/release/doc/README has additional information.

Reviewed by:	-current, -doc
This commit is contained in:
Bruce A. Mah 2001-04-27 21:28:02 +00:00
parent 1af6a10849
commit 8ed3802bb0
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=76082
101 changed files with 22926 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
release/Makefile
View File

@ -59,8 +59,16 @@ OBJFORMAT?= elf
# Uncomment this to disable the doc.1 target. It is also an ERROR
# to set NOPORTS and not set NODOC since docs depend on ports.
# Setting this also disables doc.2 (RELNOTESng).
#NODOC= YES
#NOPORTS= YES
# RELNOTESng can be enabled be uncommenting the following variable
# definition. It depends on having ports and docs enabled for this
# release build.
#RELNOTESNG= YES
#RELNOTESNG_LANG= en_US.ISO_8859-1
# Set ALLLANG=no if you want the release documentation to be
# in English only.
ALLLANG?= yes
@ -71,9 +79,13 @@ DOCDISTFILES?= ${.CURDIR}/../../ports/distfiles
# on the boot floppy. WARNING: Breaks on some Athlon (K7) motherboards.
AUTO_KEYBOARD_DETECT?= 0
.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES"
DIST_DOCS_ARCH_INDEP= readme errata
DIST_DOCS_ARCH_DEP= installation relnotes hardware
.else
DIST_DOCS= ABOUT.TXT ERRATA.TXT LAYOUT.TXT README.TXT HARDWARE.TXT \
RELNOTES.TXT TROUBLE.TXT UPGRADE.TXT INSTALL.TXT
.endif
# Things which without too much trouble can be considered variables
# BIN_DISTS are special in that they get full /etc installation sets.
@ -181,6 +193,9 @@ EXTRAS= cdrom.1 ftp.1
.if !defined(NODOC)
DOCREL= doc.1
.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES"
DOCREL+= doc.2
.endif
.endif
.if !defined(NOPORTREADMES)
@ -198,6 +213,11 @@ rerelease release:
@echo "unset NOPORTS!"
@exit 1
.endif
.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES" && defined(NODOC)
@echo "Ports and docs are required for building RELNOTESng. Either"
@echo "unset RELNOTESNG or unset both NOPORTS and NODOC!"
@exit 1
.endif
.if make(release)
.if exists(${CHROOTDIR})
# The first command will fail on a handful of files that have their schg
@ -296,6 +316,14 @@ rerelease release:
.if defined(NOSRC)
echo "export NOSRC=${NOSRC}" >> ${CHROOTDIR}/mk
.endif
.if defined(RELNOTESNG)
echo "export RELNOTESNG=${RELNOTESNG}" >> ${CHROOTDIR}/mk
.endif
.if defined(RELNOTESNG_LANG)
echo "export RELNOTESNG_LANG=${RELNOTESNG_LANG}" >> ${CHROOTDIR}/mk
.else
echo "export RELNOTESNG_LANG=en_US.ISO_8859-1" >> ${CHROOTDIR}/mk
.endif
.if defined(NOSHARED)
echo "export NOSHARED=${NOSHARED}" >> ${CHROOTDIR}/mk
.endif
@ -548,6 +576,15 @@ release.8: write_mfs_in_kernel
ln ${RD}/mfsfd/stand/etc/services ${RD}/mfsfd/etc/services
ln ${RD}/mfsfd/stand/etc/netconfig ${RD}/mfsfd/etc/netconfig
gzip -9c ${.CURDIR}/../COPYRIGHT > ${RD}/mfsfd/stand/help/COPYRIGHT.hlp.gz
.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES"
@for i in ${DIST_DOCS_ARCH_INDEP}; do \
gzip -9c ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.txt > ${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \
done
@for i in ${DIST_DOCS_ARCH_DEP}; do \
gzip -9c ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.txt > ${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \
done
@mv ${RD}/mfsfd/stand/help/INSTALLATION.TXT.gz ${RD}/mfsfd/stand/help/INSTALL.TXT.gz
.else
@for i in README.TXT RELNOTES.TXT INSTALL.TXT UPGRADE.TXT HARDWARE.TXT; do \
if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \
gzip -9c ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} > ${RD}/mfsfd/stand/help/$${i}.gz; \
@ -555,6 +592,7 @@ release.8: write_mfs_in_kernel
gzip -9c ${.CURDIR}/texts/$${i} > ${RD}/mfsfd/stand/help/$${i}.gz; \
fi; \
done
.endif
-test -f ${.CURDIR}/install.cfg && cp ${.CURDIR}/install.cfg ${RD}/mfsfd
@mkdir -p ${RD}/mfsfd/boot
@cp /boot/boot* ${RD}/mfsfd/boot
@ -636,6 +674,18 @@ ftp.1:
-@ln -s . ${FD}/${BUILDNAME}
@cd ${RD} && find floppies -print | cpio -dumpl ${FD}
@cd ${RD}/dists && find . -print | cpio -dumpl ${FD}
.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES"
@for i in ${DIST_DOCS_ARCH_INDEP}; do \
cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.txt ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \
cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.html ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \
done
@for i in ${DIST_DOCS_ARCH_DEP}; do \
cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.txt ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \
cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.html ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \
done
@mv ${FD}/INSTALLATION.TXT ${FD}/INSTALL.TXT
@mv ${FD}/INSTALLATION.HTM ${FD}/INSTALL.HTM
.else
@for i in ${DIST_DOCS}; do \
if [ -f ${.CURDIR}/texts/$${i} ]; then \
cp ${.CURDIR}/texts/$${i} ${FD}; \
@ -645,6 +695,7 @@ ftp.1:
cat ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} >> ${FD}/$${i}; \
fi; \
done
.endif
@echo "CD_VERSION = ${BUILDNAME}" > ${FD}/cdrom.inf
.if !defined(NOPORTS)
@tar --exclude CVS -cBf - -C ${CD_DISC1} ports | tar -xBf - -C ${FD}
@ -672,6 +723,18 @@ cdrom.1:
@cp ${.CURDIR}/fixit.profile ${CD_DISC2}/.profile
@echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC1}/cdrom.inf
@echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC2}/cdrom.inf
.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES"
@for i in ${DIST_DOCS_ARCH_INDEP}; do \
cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.txt ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \
cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.html ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \
done
@for i in ${DIST_DOCS_ARCH_DEP}; do \
cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.txt ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \
cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.html ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \
done
@mv ${CD_DISC1}/INSTALLATION.TXT ${CD_DISC1}/INSTALL.TXT
@mv ${CD_DISC1}/INSTALLATION.HTM ${CD_DISC1}/INSTALL.HTM
.else
@for i in ${DIST_DOCS}; do \
if [ -f ${.CURDIR}/texts/$${i} ]; then \
cp ${.CURDIR}/texts/$${i} ${CD_DISC1}; \
@ -681,6 +744,7 @@ cdrom.1:
cat ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} >> ${CD_DISC1}/$${i}; \
fi; \
done
.endif
.if ${MACHINE_ARCH} == "alpha"
@echo "Setting up Alpha CD disc1 for booting"
@cp -Rp ${RD}/image.boot/boot ${CD_DISC1}
@ -697,6 +761,9 @@ cdrom.1:
.endif
touch cdrom.1
#
# --==## Documentation Project files such as the Handbook and FAQ ##==--
#
doc.1:
@echo "Making docs..."
@for i in ${DOCPORTS}; do \
@ -705,6 +772,14 @@ doc.1:
@cd /usr/doc && make all install 'FORMATS=html html-split txt' INSTALL_COMPRESSED='' DOCDIR=${RD}/trees/bin/usr/share/doc
touch doc.1
#
# --==## RELNOTESng: Next-generation replacements for *.TXT files ##==--
#
doc.2:
@echo "Making release documentation..."
@cd ${.CURDIR}/doc && make all 'FORMATS=html txt'
touch doc.2
# Various "subroutine" and other supporting targets.
# RD=

36
release/doc/Makefile Normal file
View File

@ -0,0 +1,36 @@
# $FreeBSD$
#
# The user can override the default list of languages to build and install
# with the DOC_LANG variable.
#
.if defined(DOC_LANG) && !empty(DOC_LANG)
SUBDIR = ${DOC_LANG}
.else
SUBDIR = en_US.ISO_8859-1
.endif
DOC_PREFIX?= /usr/doc
.if defined(SUPHOST)
SUPFLAGS+= -h ${SUPHOST}
.endif
update:
.if defined(SUP_UPDATE)
.if !defined(DOCSUPFILE)
@echo "Error: Please define DOCSUPFILE before doing make update."
@exit 1
.endif
@echo "--------------------------------------------------------------"
@echo ">>> Running ${SUP}"
@echo "--------------------------------------------------------------"
@${SUP} ${SUPFLAGS} ${DOCSUPFILE}
.elif defined(CVS_UPDATE)
@echo "--------------------------------------------------------------"
@echo ">>> Updating ${.CURDIR} from cvs repository" ${CVSROOT}
@echo "--------------------------------------------------------------"
cd ${.CURDIR}; cvs -q update -P -d
.else
@echo "Error: Please define either SUP_UPDATE or CVS_UPDATE first."
.endif
.include "${DOC_PREFIX}/share/mk/doc.subdir.mk"

88
release/doc/README Normal file
View File

@ -0,0 +1,88 @@
-*- text -*-
RELNOTESng README
Bruce A. Mah <bmah@freebsd.org>
$FreeBSD$
This is the top-level directory for RELNOTESng, a re-write of
FreeBSD's *.TXT documentation files. They have been converted to
DocBook, and versions of the documents can be now be built for various
supported architectures. The output files can be rendered in any
format supported by the FreeBSD Documentation Project (for example,
ASCII text, PDF, PS, HTML).
RELNOTESng requires that the FreeBSD doc/ sources are installed; it
leverages off of much of the DocProj build infrastructure, including
DocBook extensions and stylesheets. If the doc/ sources are not
installed in /usr/src, their location should be specified with the
DOC_PREFIX Makefile variable. RELNOTESng also requires the DocProj
build tools, which can easily be installed with the textproc/docproj
port in the Ports Collection.
share/sgml/*.dsl
Architecture-dependent stylesheets. These stylesheets support
the arch= attribute on (all?) DocBook elements. Currently-
supported values are: i386, alpha.
share/sgml/release.ent
Release information. Need to update the entry definitions in
this file when rolling new revisions; these should take effect
in all documents.
*/relnotes/common/
Directory for multi-architecture release notes files.
*/relnotes/*/
Directories for architecture-specific release notes files.
*/hardware/common/
Directory for multi-architecture hardware notes files.
*/hardware/*/
Directories for architecture-specific hardware notes files.
*/installation/common/
Directory for multi-architecture installation notes files.
Note that the FreeBSD DocProj build infrastructure does
not handle documents (or subdirectories) named "install"
well, so we call our document "installation" and do
a hack when it gets installed into a distribution to fix
this up.
*/installation/*/
Directories for architecture-specific release notes files.
*/errata/
Directory for errata document.
*/readme/
Directory for (introductory) document.
All definition of the "current" version of FreeBSD is contained in the
share/sgml/release.ent file; release engineers should peruse the
contents of this file carefully when doing version number bumps.
When creating content for the architecture-dependent files, authors
should use the arch= attribute to elements that are specific to a
particular machine architecture. The value of this attribute should
be a single word that indicates for which architecture the current
element will be included. For example:
<para arch="alpha">Alpha-specific text</para>
The currently-supported architectures are i386 and alpha. As of this
writing there is no mechanism for supporting multiple architectures
(i.e. arch="alpha,ia64"), but with some work in the stylesheets this
should be possible.
When creating a translation, make a new directory under this
directory with a language code (paralleling the DocProj directory
structure).
RELNOTESng is supported in the FreeBSD release-build process. For
now, the building of RELNOTESng is enabled by RELNOTESNG=YES when
building a release. Note that setting RELNOTESng requires that both
NODOC and NOPORTS *not* be set, as RELNOTESng require parts of
both. Eventually, RELNOTESNG will be made the default.
Release builders can set which language gets built with the
RELNOTESNG_LANG variable; note that this is different from the
DOC_LANG variable because (at least intially) most languages
will have localized DocProj files but not localized release notes.
The default language, if none is specified, is en_US.ISO_8859-1.

12
release/doc/en_US.ISO8859-1/Makefile Normal file
View File

@ -0,0 +1,12 @@
# $FreeBSD$
SUBDIR = relnotes
SUBDIR+= hardware
SUBDIR+= readme
SUBDIR+= errata
SUBDIR+= installation
COMPAT_SYMLINK = en
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

13
release/doc/en_US.ISO8859-1/errata/Makefile Normal file
View File

@ -0,0 +1,13 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

84
release/doc/en_US.ISO8859-1/errata/article.sgml Normal file
View File

@ -0,0 +1,84 @@
<!--
$FreeBSD$
FreeBSD errata document. Unlike some of the other RELNOTESng
files, this file should remain as a single SGML file, so that
the dollar FreeBSD dollar header has a meaningful modification
time. This file is all but useless without a datestamp on it,
so we'll take some extra care to make sure it has one.
(If we didn't do this, then the file with the datestamp might
not be the one that received the last change in the document.)
-->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
]>
<article>
<articleinfo>
<title>&os; &release.current; Errata</title>
<corpauthor>
The &os; Project
</corpauthor>
<pubdate>$FreeBSD$</pubdate>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>
<sect1>
<title>Introduction</title>
<para>If you read no other documentation before installing this
version of &os;, you should at least by all means <emphasis>read
the errata</emphasis> for this release so that you don't stumble
over problems which have already been found and fixed. This
<filename>ERRATA.TXT</filename> file is obviously already out of
date by definition, but other copies are kept updated on the net and
should be consulted as the <quote>current errata</quote> for your
release. These other copies of the errata are located at:
<orderedlist>
<listitem>
<para><ulink url="http://www.freebsd.org/releases/">http://www.freebsd.org/releases/</ulink></para>
</listitem>
<listitem>
<para><userinput>ftp://ftp.freebsd.org/pub/FreeBSD/releases/<replaceable>architecture</replaceable>/<replaceable>release</replaceable>/ERRATA.TXT</userinput></para>
<para>(and any sites which keep up-to-date mirrors of this
location)</para>
</listitem>
</orderedlist>
</para>
<para>Any changes to this file are also automatically emailed to the
&a.current;.</para>
<para>For all CERT security advisories, see <ulink
url="ftp://ftp.freebsd.org/pub/FreeBSD/CERT/">ftp://ftp.freebsd.org/pub/FreeBSD/CERT/</ulink>.</para>
</sect1>
<sect1>
<title>Security Advisories</title>
<para>Current active security advisories: None.</para>
</sect1>
<sect1>
<title>System Update Information</title>
<para>Current active errata items: None.</para>
</sect1>
</article>

7
release/doc/en_US.ISO8859-1/hardware/Makefile Normal file
View File

@ -0,0 +1,7 @@
# $FreeBSD$
SUBDIR = alpha
SUBDIR+= i386
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

22
release/doc/en_US.ISO8859-1/hardware/alpha/Makefile Normal file
View File

@ -0,0 +1,22 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= proc-alpha.sgml
SRCS+= ../common/hw.ent
SRCS+= ../common/artheader.sgml
SRCS+= ../common/dev.sgml
SRCS+= ../common/config.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

26
release/doc/en_US.ISO8859-1/hardware/alpha/article.sgml Normal file
View File

@ -0,0 +1,26 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/hw.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "alpha">
]>
<article>
&artheader;
&sect.intro;
&sect.proc.alpha;
&sect.dev;
&sect.config;
</article>

2370
release/doc/en_US.ISO8859-1/hardware/alpha/proc-alpha.sgml Normal file
View File

File diff suppressed because it is too large Load Diff

2104
release/doc/en_US.ISO8859-1/hardware/article.sgml Normal file
View File

File diff suppressed because it is too large Load Diff

13
release/doc/en_US.ISO8859-1/hardware/common/artheader.sgml Normal file
View File

@ -0,0 +1,13 @@
<!-- $FreeBSD$ -->
<articleinfo>
<title>&os; &release.current; &arch; Hardware Notes</title>
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>

776
release/doc/en_US.ISO8859-1/hardware/common/config.sgml Normal file
View File

@ -0,0 +1,776 @@
<!-- $FreeBSD$ -->
<sect1>
<title>Boot-time Kernel Configuration</title>
<para>This section describes the boot-time configuration of the
&os; kernel.</para>
<note>
<para>How architecture-dependent is this?</para>
</note>
<sect2>
<title>Default Configuration</title>
<para>The following table contains a list of all of the devices
that are present in the <filename>GENERIC</filename> kernel. This
is the essential part of the operating system that is placed in
your root partition during the installation process. A compressed
version of the <filename>GENERIC</filename> kernel is also used on
the installation floppy diskette and DOS boot image.</para>
<para>The table describes the various parameters used by the
driver to communicate with the hardware in your system. There are
four parameters in the table, though not all are used by each and
every device:
<informaltable frame=none>
<tgroup cols=2 align=left>
<colspec colwidth="*">
<colspec colwidth="5*">
<tbody>
<row>
<entry>Port</entry>
<entry>The starting I/O port used by the device, shown in hexadecimal.</entry>
</row>
<row>
<entry>IRQ</entry>
<entry>The interrupt the device uses to alert the driver to an event,
given in decimal.</entry>
</row>
<row>
<entry>DRQ</entry>
<entry>The DMA (direct memory access) channel the device uses to move
data to and from main memory, also given in decimal.</entry>
</row>
<row>
<entry>IOMem</entry>
<entry>The lowest (or starting) memory address used by the device,
also shown in hexadecimal.</entry>
</row>
</tbody>
</tgroup>
</informaltable>
If an entry in the table has `n/a' for a value then it means that
the parameter in question does not apply to that device. A value
of `dyn' means that the correct value should be determined
automatically by the kernel when the system boots and that you
don't need to worry about it.</para>
<para>If an entry is marked with an *, it means that support is
currently not available for it but should be back as soon as
someone converts the driver to work within the new (post-4.0)
framework.</para>
<para>
<informaltable frame=none>
<tgroup cols=6 align=left>
<colspec colwidth="*">
<colspec colwidth="*">
<colspec colwidth="*">
<colspec colwidth="*">
<colspec colwidth="*">
<colspec colwidth="5*">
<thead>
<row>
<entry>Device</entry>
<entry>Port</entry>
<entry>IRQ</entry>
<entry>DRQ</entry>
<entry>IOMem</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>fdc0</entry>
<entry>3f0</entry>
<entry>6</entry>
<entry>2</entry>
<entry>n/a</entry>
<entry>Floppy disk controller</entry>
</row>
<row>
<entry>ata0</entry>
<entry>170</entry>
<entry>14</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATA/ATAPI controller</entry>
</row>
<row>
<entry>ata1</entry>
<entry>170</entry>
<entry>15</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATA/ATAPI controller</entry>
</row>
<row>
<entry>atadisk0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATA disk drives</entry>
</row>
<row>
<entry>atapicd0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATAPI CDROM drives</entry>
</row>
<row>
<entry>atapifd0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATAPI floppy drives</entry>
</row>
<row>
<entry>atapist0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATAPI tape drives</entry>
</row>
<row>
<entry>adv0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>AdvanSys Narrow SCSI controllers</entry>
</row>
<row>
<entry>adw0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>AdvanSys Wide SCSI controllers</entry>
</row>
<row>
<entry>amd0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>AMD 53C974 (Tekram DC390(T))</entry>
</row>
<row>
<entry>ncr0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>NCR PCI SCSI controller</entry>
</row>
<row>
<entry>bt0</entry>
<entry>330</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Buslogic SCSI controller</entry>
</row>
<row>
<entry>aha0</entry>
<entry>330</entry>
<entry>dyn</entry>
<entry>5</entry>
<entry>dyn</entry>
<entry>Adaptec 154x/1535 SCSI controller</entry>
</row>
<row>
<entry>ahb0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Adaptec 174x SCSI controller</entry>
</row>
<row>
<entry>ahc0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Adaptec 274x/284x/294x SCSI controller</entry>
</row>
<row>
<entry>aic0</entry>
<entry>340</entry>
<entry>11</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Adaptec 152x/AIC-6360/AIC-6260 SCSI controller</entry>
</row>
<row>
<entry>isp0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>QLogic 10X0, 1240 Ultra SCSI, 1080/1280 Ultra2 SCSI, 12160 Ultra3 SCSI, 2X00 Fibre Channel SCSI controller</entry>
</row>
<row>
<entry>dpt0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>DPT RAID SCSI controllers</entry>
</row>
<row>
<entry>amr0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>AMI MegaRAID controllers</entry>
</row>
<row>
<entry>mlx0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Mylex DAC960 RAID controllers</entry>
</row>
<row>
<entry>twe0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>3ware Escalade RAID controllers</entry>
</row>
<row>
<entry>asr0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>DPT SmartRaid V, VI, and Adaptec SCSI RAID</entry>
</row>
<row>
<entry>mly0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Mylex AcceleRAID/eXtremeRAID</entry>
</row>
<row>
<entry>aac</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Adaptec FSA family PCI SCSI RAID</entry>
</row>
<row>
<entry>ncv</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>NCR 53C500 based PC-Card SCSI</entry>
</row>
<row>
<entry>nsp</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Workbit Ninja SCSI-3 based PC-Card SCSI</entry>
</row>
<row>
<entry>stg</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>TMC 18C30/50 based ISA/PC-Card SCSI</entry>
</row>
<row>
<entry>wt0</entry>
<entry>300</entry>
<entry>5</entry>
<entry>1</entry>
<entry>dyn</entry>
<entry>Wangtek and Archive QIC-02/QIC-36</entry>
</row>
<row>
<entry>psm0</entry>
<entry>60</entry>
<entry>12</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>PS/2 Mouse</entry>
</row>
<row>
<entry>mcd0</entry>
<entry>300</entry>
<entry>10</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Mitsumi CD-ROM</entry>
</row>
<row>
<entry>matcd0</entry>
<entry>230</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Matsushita/Panasonic CD-ROM</entry>
</row>
<row>
<entry>scd0</entry>
<entry>230</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Sony CD-ROM</entry>
</row>
<row>
<entry>sio0</entry>
<entry>3f8</entry>
<entry>4</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Serial Port 0 (COM1)</entry>
</row>
<row>
<entry>sio1</entry>
<entry>2f8</entry>
<entry>3</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Serial Port 1 (COM2)</entry>
</row>
<row>
<entry>ppc0</entry>
<entry>dyn</entry>
<entry>7</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Printer ports</entry>
</row>
<row>
<entry>dc0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>DEC/Intel 21143 cards and workalikes</entry>
</row>
<row>
<entry>de0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>DEC DC21x40 PCI based cards (including 21140 100bT cards)</entry>
</row>
<row>
<entry>ed0</entry>
<entry>280</entry>
<entry>10</entry>
<entry>dyn</entry>
<entry>d8000</entry>
<entry>WD & SMC 80xx; Novell NE1000 & NE2000; 3Com 3C503; HP PC Lan+</entry>
</row>
<row>
<entry>ep0</entry>
<entry>300</entry>
<entry>10</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>3Com 3C509, 3C529, 3C556, 3C562D, 3C563D, 3C572, 3C574X, 3C579, 3C589</entry>
</row>
<row>
<entry>ex0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>Intel EtherExpress Pro/10 cards</entry>
</row>
<row>
<entry>fe0</entry>
<entry>300</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Allied-Telesyn AT1700, RE2000 and Fujitsu FMV-180 series cards.</entry>
</row>
<row>
<entry>fxp0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Intel EtherExpress Pro/100B and Intel PRO/100+ Management Adapter</entry>
</row>
<row>
<entry>ie0</entry>
<entry>300</entry>
<entry>10</entry>
<entry>dyn</entry>
<entry>d0000</entry>
<entry>AT&amp;T StarLAN 10 and EN100; 3Com 3C507; NI5210; Intel EtherExpress (8/16,16[TP]) cards</entry>
</row>
<row>
<entry>le0</entry>
<entry>300</entry>
<entry>5</entry>
<entry>dyn</entry>
<entry>d0000</entry>
<entry>Digital Equipment EtherWorks 2 and EtherWorks 3</entry>
</row>
<row>
<entry>lnc0</entry>
<entry>280</entry>
<entry>10</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Lance/PCnet cards (Isolan, Novell NE2100, NE32-VL, some PCnet-PCI cards)</entry>
</row>
<row>
<entry>pcn0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA cards</entry>
</row>
<row>
<entry>rl0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>RealTek 8129/8139 fast ethernet</entry>
</row>
<row>
<entry>sf0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Adaptec AIC-6915 fast ethernet</entry>
</row>
<row>
<entry>sis0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>SiS 900/SiS 7016 fast ethernet</entry>
</row>
<row>
<entry>sn0</entry>
<entry>0x300</entry>
<entry>10</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>SMC 91xx ethernet</entry>
</row>
<row>
<entry>ste0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Sundance ST201 fast ethernet</entry>
</row>
<row>
<entry>tl0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>TI TNET100 'ThunderLAN' cards.</entry>
</row>
<row>
<entry>tx0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>SMC 9432 'Epic' fast ethernet</entry>
</row>
<row>
<entry>wb0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Winbond W89C840F PCI based cards.</entry>
</row>
<row>
<entry>vr0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>VIA VT3043/VT86C100A PCI based cards.</entry>
</row>
<row>
<entry>vx0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>3Com 3c59x ((Fast) Etherlink III)</entry>
</row>
<row>
<entry>xe0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Xircom CreditCard adapters (16 bit)</entry>
</row>
<row>
<entry>xl0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>3Com 3c900, 3c905, 3c905B, 3c905C, 3c980, 3cSOHO100 ((Fast) Etherlink XL)</entry>
</row>
<row>
<entry>cs0</entry>
<entry>0x300</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Crystal Semiconductor CS89x0-based cards.</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
<para>If the hardware in your computer is not set to the same
settings as those shown in the table and the item in conflict is
not marked 'dyn', you will have to either reconfigure your
hardware or use UserConfig to reconfigure the kernel to match the
way your hardware is currently set (see the next section).</para>
<para>If the settings do not match, the kernel may be unable to
locate or reliably access the devices in your system.</para>
</sect2>
<sect2>
<title>Using UserConfig to change FreeBSD kernel settings</title>
<note>
<para>The markup for this section leaves a lot to be desired.</para>
</note>
<para>The FreeBSD kernel on the install floppy contains drivers
for every piece of hardware that could conceivably be used to
install the rest of the system with. Unfortunately, PC hardware
being what it is, some of these devices can be difficult to detect
accurately, and for some, the process of detecting another can
cause irreversible confusion.</para>
<para>To make this process easier, FreeBSD provides UserConfig.
With this tool the user can configure and disable device drivers
before the kernel is loaded, avoiding potential conflicts, and
eliminating the need to reconfigure hardware to suit the default
driver settings.</para>
<para>Once FreeBSD is installed, it will remember the changes made using
UserConfig, so that they only need be made once.</para>
<para>It is important to disable drivers that are not relevant to
a system in order to minimize the possibility of interference,
which can cause problems that are difficult to track down.</para>
<para>UserConfig features a command line interface for users with
serial consoles or a need to type commands, and a full screen
<quote>visual</quote> interface, which provides point-and-shoot
configuration functionality.</para>
<para>Here is a sample UserConfig screen shot in
<quote>visual</quote> mode:</para>
<screen>---Active Drivers---------------------------10 Conflicts------Dev---IRQ--Port--
Storage : (Collapsed)
Network :
NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed0 5 0x280
NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed1 5 0x300
Communications : (Collapsed)
Input : (Collapsed)
Multimedia :
---Inactive Drivers-------------------------------------------Dev--------------
Storage :
Network : (Collapsed)
Communications :
Input :
Multimedia :
---Parameters-for-device-ed0---------------------------------------------------
Port address : 0x280 Memory address : 0xd8000
IRQ number : 5 Memory size : 0x2000
Flags : 0x0000
-------------------------------------------------------------------------------
IO Port address (Hexadecimal, 0x1-0x2000)
[TAB] Change fields [Q] Save device parameters</screen>
<para>The screen is divided into four sections:
<itemizedlist>
<listitem>
<para>Active Drivers. Listed here are the device drivers
that are currently enabled, and their basic
parameters.</para>
</listitem>
<listitem>
<para>Inactive Drivers. These drivers are present, but are
disabled.</para>
</listitem>
<listitem>
<para>Parameter edit field. This area is used for editing
driver parameters.</para>
</listitem>
<listitem>
<para>Help area. Keystroke help is displayed here.</para>
</listitem>
</itemizedlist>
</para>
<para>One of the Active and Inactive lists is always in use, and
the current entry in the list will be shown with a highlight bar.
If there are more entries in a list than can be shown, it will
scroll. The bar can be moved up and down using the cursor keys,
and moved between lists with the TAB key.</para>
<para>Drivers in the Active list may be marked
<literal>CONF</literal>. This indicates that one or more of their
parameters conflicts with another device, and indicates a
potential for problems. The total number of conflicts is
displayed at the top of the screen.</para>
<para>As a general rule, conflicts should be avoided, either by
disabling conflicting devices that are not present in the system,
or by altering their configuration so that they match the
installed hardware.</para>
<para>In the list areas, drivers are grouped by their basic
function. Groups can be <literal>Collapsed</literal> to simplify
the display (this is the default state for all groups). If a
group is collapsed, it will be shown with
<literal>Collapsed</literal> in the list, as above. To Expand a
Collapsed group, position the highlight bar over the group heading
and press Enter. To Collapse it again, repeat the process.</para>
<para>When a device driver in the Active list is highlighted, its
full parameters are displayed in the Parameter edit area. Note
that not all drivers use all possible parameters, and some
hardware supported by drivers may not use all the parameters the
driver supports.</para>
<para>To disable a driver, go to the Active list, Expand the group
it is in, highlight the driver and press Del. The driver will
move to its group in the Inactive list. (If the group is
collapsed or off the screen, you may not see the driver in its new
location.)</para>
<para>To enable a driver, go to the Inactive list, Expand the
group it is in, highlight the driver and press Enter. The
highlight will move to the Active list, and the driver you have
just enabled will be highlighted, ready to be configured.</para>
<para>To configure a driver, go to the Active list, Expand the
group it is in, highlight the driver and press Enter. The cursor
will move to the Parameter edit area, and the device's parameters
may be edited.</para>
<para>While editing parameters, the TAB and cursor keys can be
used to move between fields. Most numeric values (except IRQ) are
entered in hexadecimal, as indicated by the '0x' at the beginning
of the field. The allowable values for a given field are show in
the Key Help area when the field is active.</para>
<para>To finish configuring a driver, press 'Q'.</para>
<para>Note that PCI, Microchannel and EISA devices can be probed
reliably, therefore they are not shown in the table above nor can
their settings be changed using UserConfig.</para>
</sect2>
</sect1>

2104
release/doc/en_US.ISO8859-1/hardware/common/dev.sgml Normal file
View File

File diff suppressed because it is too large Load Diff

15
release/doc/en_US.ISO8859-1/hardware/common/hw.ent Normal file
View File

@ -0,0 +1,15 @@
<!-- -*- sgml -*- -->
<!-- $FreeBSD$ -->
<!-- Text constants which probably don't need to be changed.-->
<!-- Files to be included -->
<!ENTITY artheader SYSTEM "../common/artheader.sgml">
<!ENTITY sect.intro SYSTEM "../common/intro.sgml">
<!ENTITY sect.proc.alpha SYSTEM "../alpha/proc-alpha.sgml">
<!ENTITY sect.proc.i386 SYSTEM "../i386/proc-i386.sgml">
<!ENTITY sect.proc.ia64 SYSTEM "../ia64/proc-ia64.sgml">
<!ENTITY sect.dev SYSTEM "../common/dev.sgml">
<!ENTITY sect.config SYSTEM "../common/config.sgml">

17
release/doc/en_US.ISO8859-1/hardware/common/intro.sgml Normal file
View File

@ -0,0 +1,17 @@
<!-- $FreeBSD$ -->
<sect1>
<title>Introduction</title>
<para>This document contains the hardware compatability notes for
&os; &release.current; on the &arch; hardware platform. 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.</para>
<note>
<para>This document includes information specific to the &arch;
hardware platform. Versions of the hardware compatability notes
for other architectures will differ in some details.</para>
</note>
</sect1>

22
release/doc/en_US.ISO8859-1/hardware/i386/Makefile Normal file
View File

@ -0,0 +1,22 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= proc-i386.sgml
SRCS+= ../common/hw.ent
SRCS+= ../common/artheader.sgml
SRCS+= ../common/dev.sgml
SRCS+= ../common/config.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

26
release/doc/en_US.ISO8859-1/hardware/i386/article.sgml Normal file
View File

@ -0,0 +1,26 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/hw.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "i386">
]>
<article>
&artheader;
&sect.intro;
&sect.proc.i386;
&sect.dev;
&sect.config;
</article>

11
release/doc/en_US.ISO8859-1/hardware/i386/proc-i386.sgml Normal file
View File

@ -0,0 +1,11 @@
<!--
$FreeBSD$
-->
<sect1>
<title>Supported Processors and Motherboards</title>
<para>&os; for the i386 currently runs on a wide variety of ISA,
VLB, EISA, MCA and PCI bus based PC's, ranging from 386sx to
Pentium 4 class machines (though the 386sx is not
recommended).</para>
</sect1>

7
release/doc/en_US.ISO8859-1/installation/Makefile Normal file
View File

@ -0,0 +1,7 @@
# $FreeBSD$
SUBDIR = alpha
SUBDIR+= i386
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

23
release/doc/en_US.ISO8859-1/installation/alpha/Makefile Normal file
View File

@ -0,0 +1,23 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= ../common/artheader.sgml
SRCS+= ../common/install.sgml
SRCS+= ../common/floppies.sgml
SRCS+= ../common/layout.sgml
SRCS+= ../common/trouble.sgml
SRCS+= ../common/upgrade.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

27
release/doc/en_US.ISO8859-1/installation/alpha/article.sgml Normal file
View File

@ -0,0 +1,27 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/install.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "alpha">
]>
<article>
&artheader;
&sect.install;
&sect.layout;
&sect.floppies;
&sect.upgrade;
&sect.trouble;
</article>

15
release/doc/en_US.ISO8859-1/installation/common/artheader.sgml Normal file
View File

@ -0,0 +1,15 @@
<!-- $FreeBSD$ -->
<articleinfo>
<title>&os; &release.current; &arch; Installation Instructions</title>
<corpauthor>
The &os; Project
</corpauthor>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>

83
release/doc/en_US.ISO8859-1/installation/common/floppies.sgml Normal file
View File

@ -0,0 +1,83 @@
<!-- $FreeBSD$ -->
<sect1 id="floppies">
<title>Floppy Disk Image Instructions</title>
<para>For a normal CDROM or network installation, all you need to
copy onto actual floppies from the <filename>floppies/</filename> directory are the
<filename>kern.flp</filename> and <filename>mfsroot.flp</filename>
images (for 1.44MB floppies).</para>
<para>Getting these images over the network is easy. simply fetch
the
<replaceable>release</replaceable><filename>/floppies/kern.flp</filename>
and
<replaceable>release</replaceable><filename>/floppies/mfsroot.flp</filename>
files from <ulink
url="ftp://ftp.freebsd.org/pub/FreeBSD">ftp://ftp.freebsd.org/pub/FreeBSD</ulink>
or one of the many mirrors listed at <ulink
url="http://www.freebsd.org/handbook/mirrors.html">http://www.freebsd.org/handbook/mirrors.html</ulink>.
</para>
<para>Get two blank, freshly formatted floppies and image copy
<filename>kern.flp</filename> onto one and <filename>mfsroot.flp</filename> onto the other. These images are
<emphasis>not</emphasis> DOS files! You cannot simply copy them to a DOS or UFS floppy
as regular files, you need to <quote>image</quote> copy them to the floppy with
<filename>fdimage.exe</filename> under DOS (see the
<filename>tools</filename> directory on your CDROM or &os; FTP
mirror) or the &man.dd.1; command in UNIX.</para>
<para>For example, to create the kernel floppy image from DOS, you'd
do something like this:</para>
<screen><userinput>C> fdimage kern.flp a:</userinput></screen>
<para>Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>kern.flp</filename> into a directory
somewhere. You would do the same for <filename>mfsroot.flp</filename>, of course.</para>
<para>If you're creating the boot floppy from a UNIX machine, you
may find that:</para>
<screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/rfd0</userinput></screen>
<para>or</para>
<screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/floppy</userinput></screen>
<para>work well, depending on your hardware and operating system
environment (different versions of UNIX have totally different names
for the floppy drive).</para>
<para arch="alpha">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 older (but now twice as large) <filename>boot.flp</filename> image which we also
provide. That contains the contents of <filename>kern.flp</filename> and <filename>mfsroot.flp</filename> on
a single floppy, essentially. This file should also be used as the
boot file for those mastering <quote>El Torito</quote> bootable CD images. See
the &man.mkisofs.8; command for more information.</para>
<para>Going to two installation boot floppies is a step we
definitely would have rather avoided but we simply no longer could
due to general code bloat and &os;'s many new device drivers in
<filename>GENERIC</filename>.</para>
<para>One positive side-effect of this new organizational scheme,
however, is that it also allows one to easily make one's own
<filename>kern.flp</filename> or <filename>mfsroot.flp</filename> floppies
should a need to customize some aspect of the installation process
or use a custom kernel for an otherwise unsupported piece of
hardware arise. As long as the kernel is compiled with
<literal>options MFS</literal> and <literal>options
MFS_ROOT</literal>, it will properly look for and boot an
<filename>mfsroot.flp</filename> image in memory when run (see how
<filename>/boot/loader.rc</filename> in
<filename>kern.flp</filename> does its thing). The
<filename>mfsroot.flp</filename> image is also just a gzip'd
filesystem image which is used as root, something which can be made
rather easily using &man.vnconfig.8;. If none of that makes any
sense to you then don't worry about it - just use the
<filename>kern.flp</filename> and <filename>mfsroot.flp</filename>
images as described above.</para>
</sect1>

15
release/doc/en_US.ISO8859-1/installation/common/install.ent Normal file
View File

@ -0,0 +1,15 @@
<!-- -*- sgml -*- -->
<!-- $FreeBSD$ -->
<!-- Text constants which probably don't need to be changed.-->
<!-- Files to be included -->
<!ENTITY artheader SYSTEM "artheader.sgml">
<!ENTITY sect.install SYSTEM "install.sgml">
<!ENTITY sect.layout SYSTEM "layout.sgml">
<!ENTITY sect.floppies SYSTEM "floppies.sgml">
<!ENTITY sect.upgrade SYSTEM "upgrade.sgml">
<!ENTITY sect.trouble SYSTEM "trouble.sgml">

734
release/doc/en_US.ISO8859-1/installation/common/install.sgml Normal file
View File

@ -0,0 +1,734 @@
<!--
$FreeBSD$
install.sgml
This file has architecture-dependent installation instructions, culled
from {alpha,i386}/INSTALL.TXT.
-->
<sect1>
<title>Installing &os;</title>
<sect2 id="quickstart">
<title>Quick Start</title>
<para>This manual documents the process of making a new
installation of &os; on your machine. If you are upgrading
from a previous release of &os;, please see <xref
linkend="upgrading">
for important information on upgrading. If you are
not familiar with configuring hardware for &os;, you should
also read the <filename>HARDWARE.TXT</filename> file - it contains important
information which may save you a lot of grief.</para>
<para>If you're new to &os; then you should also read
<emphasis>everything</emphasis> listed in the Documentation menu
of the installer. It may seem like a lot to read, but the time
you spend now reading the documents will be made up many times
over because you were adequately prepared. Also, you will know the
types of information available should you get stuck later. Once
the system is installed, you can also revisit this menu and use a
Web browser to read the installed FAQ (Frequently Asked Questions)
and Handbook HTML documentation sets for &os;. Note that on-line
versions of the <ulink
url="http://www.freebsd.org/faq/">FAQ</ulink> and <ulink
url="http://www.freebsd.org/handbook/">Handbook</ulink> are also
available from the <ulink
url="http://www.freebsd.org/">FreeBSD Project Web
site</ulink>, if you have an Internet connection. See
<filename>README.TXT</filename> for more information on the
resources available to you.</para>
<para>The best laid plans sometimes go awry, so if you run into
trouble take a look at <xref linkend="trouble">, which contains
valuable troubleshooting information. You should also read
<filename>ERRATA.TXT</filename> before installing and follow the
pointers there carefully since this will stop you from falling
over any problems which have reported in the interim for your
particular release.</para>
<important>
<para>While &os; does its best to safeguard against
accidental loss of data, it's still more than possible to
<emphasis>wipe out your entire disk</emphasis>
with this installation if you make a
mistake! Please do not proceed to the final &os;
installation menu unless you've adequately backed up any
important data first! We really mean it!</para>
</important>
<para arch="i386">&os; for the &arch; 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 &os;.</para>
<para arch="alpha">&os; for the &arch; supports the alpha platforms
described in <filename>HARDWARE.TXT</filename>.</para>
<para arch="alpha">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.</para>
<para arch="alpha">Your root filesystem MUST be the first
partition (partition <literal>a</literal>) on the disk to be
bootable.</para>
<para arch="alpha">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.</para>
<sect3>
<title>Installing &os; from CDROM or the Internet</title>
<para arch="i386">The easiest type of installation is from
CDROM. If you have a supported CDROM drive and a &os;
installation CDROM, there are 2 ways of starting the
installation from it:
<itemizedlist>
<listitem>
<para>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, &os; supports the
<quote>El Torrito</quote> bootable CD standard. Simply
put the installation CD in your CDROM drive and boot the
system to begin installation.</para>
</listitem>
<listitem>
<para>Build a set of &os; boot floppies from the
<filename>floppies/</filename> directory in every &os;
distribution. Either simply use the
<filename>makeflp.bat</filename> script from DOS or read
<xref linkend="floppies"> 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 &os; installation.</para>
</listitem>
</itemizedlist>
</para>
<para arch="alpha">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):
<screen>&gt;&gt;&gt;<userinput>boot dka0</userinput></screen>
</para>
<para arch="alpha">Alternatively you can boot the installation
from floppy disk. You should start the installation by building
a set of FreeBSD boot floppy from the files
<filename>floppies/kern.flp</filename> and
<filename>floppies/mfsroot.flp</filename> using the instructions
found in <xref linkend="floppies">. From the SRM console prompt
(<literal>&gt;&gt;&gt;</literal>), just insert the
<filename>kern.flp</filename> floppy and type the following
command to start the installation:
<screen>&gt;&gt;&gt;<userinput>boot dva0</userinput></screen>
</para>
<para arch="alpha">Insert the <filename>mfsroot.flp</filename>
floppy when prompted and you will end up at the first screen of
the install program.</para>
<para>If you don't have a CDROM and would like to simply install
over the net using PPP, SLIP or a dedicated connection, see
<xref linkend="floppies"> for instructions on
making boot floppies. Then please go to
<xref linkend="ftpnfs"> for additional tips on installing
via FTP or NFS.</para>
</sect3>
</sect2>
<sect2>
<title>Detail on various installation types</title>
<para>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 &os;
installation before, you are also encouraged to read some of the
documentation in the the Documentation submenu as well as the
general <quote>Usage</quote> instructions on the first menu.</para>
<note>
<para>If you get stuck at a screen, hit the <keycap>F1</keycap> key for online
documentation relevant to that specific section.</para>
</note>
<para>If you've never installed &os; before, or even if you
have, the <quote>Standard</quote> 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 &os; installation process and know <emphasis>exactly</emphasis> what you
want to do, use the <quote>Express</quote> or <quote>Custom</quote> installation options. If
you're upgrading an existing system, use the <quote>Upgrade</quote> option.</para>
<para>The &os; 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.</para>
<para arch="alpha">Once the install procedure has finished, you will be able
to start &os;/&arch; by typing something like this to the SRM
prompt:
<screen>&gt;&gt;&gt;<userinput>boot dkc0</userinput></screen>
</para>
<para arch="alpha">This instructs the firmware to boot the specified disk. To
find the SRM names of disks in your machine, use the <literal>show
device</literal> command:
<screen>&gt;&gt;&gt;<userinput>show device</userinput>
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</screen>
</para>
<para arch="alpha">This example is from a Digital Personal Workstation 433au
and shows three disks attached to the machine. The first is a
CDROM called <devicename>dka0</devicename> and the other two are
disks and are called <devicename>dkc0</devicename> and
<devicename>dkc100</devicename> repectively.</para>
<para arch="alpha">You can specify which kernel file to load and what boot
options to use with the <option>-file</option> and
<option>-flags</option> options, for example:
<screen><prompt>&gt;&gt;&gt;</prompt> <userinput>boot -file kernel.old -flags s</userinput></screen>
</para>
<para arch="alpha">To make &os;/&arch; boot automatically, use these commands:
<screen><prompt>&gt;&gt;&gt;</prompt> <userinput>set boot_osflags a</userinput>
<prompt>&gt;&gt;&gt;</prompt> <userinput>set bootdef_dev dkc0</userinput>
<prompt>&gt;&gt;&gt;</prompt> <userinput>set auto_action BOOT</userinput></screen>
</para>
<sect3>
<title>Installing from a Network CDROM</title>
<para>If you simply wish to install from a local CDROM drive
then see <xref linkend="quickstart">. If you don't have a CDROM
drive on your system and wish to use a &os; distribution CD
in the CDROM drive of another system to which you have network
connectivity, there are also several ways of going about it:</para>
<itemizedlist>
<listitem>
<para>If you would be able to FTP install &os; directly
from the CDROM drive in some &os; machine, it's quite
easy: You simply add the following line to the password file
(using the &man.vipw.8; command):</para>
<screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen>
<para>On the machine on which you are running the install,
go to the Options menu and set Release Name to
<literal>any</literal>. You may then choose a Media type of
<literal>FTP</literal> and type in
<filename>ftp://<replaceable>machine</replaceable></filename>
after picking <quote>URL</quote> in the ftp sites
menu.</para>
<warning>
<para>This may allow anyone on the local network (or Internet) to
make <quote>anonymous FTP</quote> connections to this
machine, which may not be desirable.</para>
</warning>
</listitem>
<listitem>
<para>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
<filename>/etc/exports</filename> file (on the machine with
the CDROM drive). The example below allows the machine
<hostid role="hostname">ziggy.foo.com</hostid> to mount the
CDROM directly via NFS during installation:</para>
<screen>/cdrom -ro ziggy.foo.com</screen>
<para>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 &man.rc.conf.5; and configure things
appropriately. Assuming that this part goes smoothly, you
should be able to enter: <filename><replaceable>cdrom-host</replaceable>:/cdrom</filename> as the path for
an NFS installation when the target machine is installed,
e.g. <filename>wiggy:/cdrom</filename>.</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Installing from Floppies</title>
<para>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.</para>
<para>First, make your boot floppies as described in
<xref linkend="floppies">.</para>
<para>Second, peruse <xref linkend="layout"> and pay special attention
to the <quote>Distribution Format</quote> section since it describes which
files you're going to need to put onto floppy and which you can
safely skip.</para>
<para>Next you will need, at minimum, as many 1.44MB floppies as
it takes to hold all files in the <filename>bin</filename>
(binary distribution) directory. If you're preparing these
floppies under DOS, then these floppies
<emphasis>must</emphasis> be formatted using the MS-DOS
<filename>FORMAT</filename> command. If you're using Windows,
use the Windows File Manager format command.</para>
<important>
<para>Don't trust <quote>factory preformatted</quote>
floppies! Format them again yourself, just to make sure.
Many problems reported by users in the past have resulted
from the use of improperly formatted media.</para>
</important>
<para>If you're creating the floppies from another &os;
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
&man.disklabel.8; and &man.newfs.8; commands to put a UFS filesystem on a
floppy, as the following sequence of commands illustrates:
<screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
&prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput>
&prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
</para>
<para>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.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para>
<important>
<para>The <filename>bin.inf</filename> file also needs to go on the first floppy of
the <filename>bin</filename> 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
<filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first
floppy of each distribution set! This is also covered in
<filename>README.TXT</filename>.</para>
</important>
<para>Once you come to the Media screen of the install, select
<quote>Floppy</quote> and you'll be prompted for the rest.</para>
</sect3>
<sect3 arch="i386">
<title>Installing from a DOS partition</title>
<para>To prepare for installation from an MS-DOS partition you
should simply copy the files from the distribution into a
directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>C:</devicename>). For example, to do a minimal installation of &os; from
DOS using files copied from the CDROM, you might do something
like this:</para>
<screen><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput>
<prompt>C:\></prompt <userinput>XCOPY /S E:\BIN C:\FREEBSD\BIN</userinput></screen>
<para>Assuming that <devicename>E:</devicename> was where your CD was mounted.</para>
<para>For as many distributions as you wish to install from DOS (and
you have free space for), install each one in a directory under
<filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para>
<para>Once you've copied the directories, you can simply launch
the installation from floppies as normal and select <quote>DOS</quote> as
your media type when the time comes.</para>
</sect3>
<sect3>
<title>Installing from QIC/SCSI Tape</title>
<para>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 &man.tar.1; to get them onto the tape with a command something like
this:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput>
&prompt.root; <userinput>tar cvf /dev/rsa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen>
<para>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 <emphasis>full</emphasis>
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.</para>
<note>
<para>When going to do the installation, the tape must be in
the drive <emphasis>before</emphasis> booting from the boot floppies. The
installation <quote>probe</quote> may otherwise fail to find it.</para>
</note>
<para>Now create a boot floppy as described in <xref linkend="quickstart"> and
proceed with the installation.</para>
</sect3>
<sect3 id="ftpnfs">
<title>Installing over a Network using FTP or NFS</title>
<para>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.</para>
<sect4>
<title>Serial Port</title>
<para>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.</para>
<para>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.</para>
<para>You will also need to know how to use the various <quote>AT
commands</quote> for dialing out with your particular brand of modem
as the PPP dialer provides only a very simple terminal
emulator.</para>
</sect4>
<sect4>
<title>Parallel Port</title>
<para>If a hard-wired connection to another &os; or Linux
machine is available, you might also consider installing over
a <quote>laplink</quote> 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
<quote>real</quote> 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. <hostid
role="ipaddr">10.0.0.1</hostid>, <hostid role="ipaddr">10.0.0.2</hostid>,
etc).</para>
<important>
<para>If you use a Linux machine rather than a &os;
machine as your PLIP peer, you will also have to specify
<option>link0</option> in the TCP/IP setup screen's <quote>extra options for
ifconfig</quote> field in order to be compatible with Linux's
slightly different PLIP protocol.</para>
</important>
</sect4>
<sect4>
<title>Ethernet</title>
<para>&os; supports most common PC Ethernet cards, a table
of supported cards (and their required settings) being
provided as part of the &os; Hardware Guide (see 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 <emphasis>before</emphasis> the laptop is powered on! &os; does
not, unfortunately, currently support <quote>hot insertion</quote> of
PCMCIA cards during installation.</para>
<para>You will also need to know your IP address on the
network, the <option>netmask</option> 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.</para>
<para>If you do not know the answers to these questions then
you should really probably talk to your system administrator
<emphasis>first</emphasis> before trying this type of
installation! Using a randomly chosen IP address or netmask
on a live network will almost certainly get you shot at
dawn.</para>
<para>Once you have a network connection of some sort working, the
installation can continue over NFS or FTP.</para>
</sect4>
<sect4>
<title>NFS installation tips</title>
<para>NFS installation is fairly straight-forward: Simply copy
the &os; distribution files you want onto a server
somewhere and then point the NFS media selection at it.</para>
<para>If this server supports only <quote>privileged port</quote> 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.</para>
<para>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.</para>
<para>In order for NFS installation to work, the server must
also support <quote>subdir mounts</quote>, e.g. if your &os;
distribution directory lives on
<filename>wiggy:/usr/archive/stuff/FreeBSD</filename>, then
<hostid role="hostname">wiggy</hostid> will have to allow
the direct mounting of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
<filename>/usr</filename> or <filename>/usr/archive/stuff</filename>.</para>
<para>In FreeBSD's <filename>/etc/exports</filename> file this is controlled by the
<option>-alldirs</option> option. Other NFS servers may have different
conventions. If you are getting <literal>Permission Denied</literal> messages
from the server then it's likely that you don't have this
properly enabled!</para>
</sect4>
<sect4>
<title>FTP Installation tips</title>
<para>FTP installation may be done from any mirror site containing a
reasonably up-to-date version of &os;. A full menu of
reasonable choices for almost any location in the world is
provided in the FTP site menu during installation.</para>
<para>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 <quote>URL</quote> 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:</para>
<screen>ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE</screen>
<para>There are three FTP installation modes you can use:
<itemizedlist>
<listitem>
<para>FTP: This method uses the standard
<quote>Active</quote> 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!</para>
</listitem>
<listitem>
<para>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.</para>
</listitem>
<listitem>
<para>FTP via an HTTP proxy: This option instructs &os;
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.</para>
<para>In the rare case that you have an FTP proxy that
does not go through HTTP, you can specify the URL as
something like:</para>
<screen><userinput>ftp://foo.bar.com:<replaceable>port</replaceable>/pub/FreeBSD</userinput></screen>
<para>In the URL above, <replaceable>port</replaceable>
is the port number of the proxy FTP server.</para>
</listitem>
</itemizedlist>
</sect4>
</sect3>
<sect3>
<title>Tips for Serial Console Users</title>
<para>If you'd like to install &os; 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:</para>
<procedure>
<step>
<para>Connect some sort of ANSI (vt100) compatible terminal
or terminal emulation program to the <devicename>COM1</devicename> port of the PC you
are installing &os; onto.</para>
</step>
<step>
<para>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.</para>
</step>
<step>
<para>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 <xref
linkend="hitspace"> as soon as you
hear the beep.</para>
</step>
<step>
<para>For a floppy boot, the first beep means to remove the
<filename>kern.flp</filename> floppy and insert the
<filename>mfsroot.flp</filename> floppy, after
which you should press <keycap>Enter</keycap> and wait for another beep.</para>
</step>
<step id="hitspace">
<para>Hit the space bar, then enter</para>
<screen><userinput>boot -h</userinput></screen>
<para>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.</para>
</step>
</procedure>
</sect3>
</sect2>
<sect2 arch="i386">
<title>DOS User's Question and Answer Section</title>
<qandaset>
<qandaentry>
<question>
<para>Help! I have no space! Do I need to delete
everything first?</para>
</question>
<answer>
<para>If your machine is already running DOS and has little
or no free space available for &os;'s installation, all is
not lost! You may find the <application>FIPS</application>
utility, provided in the <filename>tools/</filename>
subdirectory on the &os; CDROM or on the various &os; ftp
sites, to be quite useful.</para>
<para><application>FIPS</application> 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 <quote>defrag</quote> your DOS
partition, using the DOS 6.xx <filename>DEFRAG</filename>
utility or the <application>Norton Disk Tools</application>,
then run FIPS. It will
prompt you for the rest of the information it needs.
Afterwards, you can reboot and install &os; on the new
partition. Also note that FIPS will create the second
partition as a <quote>clone</quote> 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! :)</para>
<para><application>FIPS</application> does NOT currently
work with FAT32 or VFAT style partitions as used by newer
versions of Windows 95. To split up such a partition, you
will need a commercial product such as
<application>Partition Magic</application>. 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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Can I use compressed DOS filesystems from
&os;?</para>
</question>
<answer>
<para>No. If you are using a utility such as
<application>Stacker</application>(tm) or
<application>DoubleSpace</application>(tm), &os; 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!). <emphasis>Do
not remove that file</emphasis> as you will probably regret
it greatly!</para>
<para>It is probably better to create another uncompressed DOS
extended partition and use this for communications between
DOS and &os; if such is your desire.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Can I mount my DOS extended partitions?</para>
</question>
<answer>
<para>Yes. DOS extended partitions are mapped in at the end
of the other <quote>slices</quote> in &os;, e.g. your <devicename>D:</devicename> drive might
be <filename>/dev/da0s5</filename>, your <devicename>E:</devicename> drive <filename>/dev/da0s6</filename>, and so on. This
example assumes, of course, that your extended partition is
on SCSI drive 0. For IDE drives, substitute <literal>ad</literal> for
<literal>da</literal> appropriately. You otherwise mount extended
partitions exactly like you would mount any other DOS drive,
e.g.:</para>
<screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Can I run DOS binaries under &os;?</para>
</question>
<answer>
<para>Ongoing work with BSDI's &man.doscmd.1; 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.emulation
and indicate that you're interested in joining this ongoing
effort!</para>
<para>There is also a neat utility called <filename>pcemu</filename> in the
&os; 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.</para>
</answer>
</qandaentry>
</qandaset>
</sect2>
</sect1>

133
release/doc/en_US.ISO8859-1/installation/common/layout.sgml Normal file
View File

@ -0,0 +1,133 @@
<!--
$FreeBSD$
This section contains the contents of the old LAYOUT.TXT file.
-->
<sect1 id="layout">
<title>Distribution Format</title>
<para>A typical &os; distribution directory looks something like this:</para>
<screen>
ABOUT.TXT bin compat3x games proflibs
HARDWARE.TXT compat1x info src tools
INSTALL.TXT compat20 dict manpages packages
README.TXT compat21 crypto doc
RELNOTES.TXT compat22 floppies ports
XF86336</screen>
<para>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
<xref linkend="floppies"> 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 &os; before,
you also want to read the entirety of this document (the
installation instructions) file.</para>
<para>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 each item in more detail:
<orderedlist>
<listitem>
<para>The <filename>*.TXT</filename> files obviously contain
documentation (this file is <filename>INSTALL.TXT</filename>) and should be read
before starting an installation.</para>
</listitem>
<listitem>
<para>The <filename>XF86336</filename> directory contains the
XFree86 project's 3.3.6 release and consists of a series of
gzip'd tar files which contain each component of the XFree86
distribution.</para>
</listitem>
<listitem>
<para>The <filename>bin</filename>, <filename>dict</filename>, <filename>crypto</filename>, <filename>doc</filename>, <filename>games</filename>, <filename>info</filename>, <filename>manpages</filename>,
<filename>proflibs</filename>, and <filename>src</filename> directories contain the primary distribution
components of &os; itself and are split into smaller files
for easy packing onto floppies (should that be
necessary).</para>
</listitem>
<listitem>
<para>The <filename>compat1x</filename>, <filename>compat20</filename>, <filename>compat21</filename>, <filename>compat22</filename>, and <filename>compat3x</filename>
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
<filename>install.sh</filename> scripts.</para>
</listitem>
<listitem>
<para>The <filename>floppies/</filename> subdirectory contains the floppy
installation images; further information on using them can be
found in <xref linkend="floppies">.</para>
</listitem>
<listitem>
<para>The <filename>packages</filename> and <filename>ports</filename> directories contain the &os;
packages and ports collections. Packages may be installed from
the packages directory by running the command:</para>
<screen>&prompt.root;<userinput>/stand/sysinstall configPackages</userinput></screen>
<para>Packages can also be installed by feeding individual
filenames in <filename>packages</filename>/ to the &man.pkg.add.1; command.</para>
<para>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
<ulink url="http://www.freebsd.org/ports/">http://www.freebsd.org/ports/</ulink> or locally from
<filename>/usr/share/doc/handbook</filename> if you've installed the <filename>doc</filename>
distribution.</para>
</listitem>
<listitem>
<para>Last of all, the <filename>tools</filename> 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.</para>
</listitem>
</orderedlist>
</para>
<para>A typical distribution (we'll use the <filename>info</filename> distribution as an
example) looks like this internally:</para>
<screen>CHECKSUM.MD5 info.ab info.ad info.inf install.sh
info.aa info.ac info.ae info.mtree</screen>
<para>The <filename>CHECKSUM.MD5</filename> 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 <filename>info.a*</filename> files
are split, gzip'd tar files, the contents of which can be viewed by
doing:</para>
<screen>&prompt.root; <userinput>cat info.a* | tar tvzf -</userinput></screen>
<para>During installation, they are automatically concatenated and
extracted by the installation procedure.</para>
<para>The <filename>info.inf</filename> 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 <filename>.inf</filename> file <emphasis>must</emphasis> occupy the first
floppy of each distribution set!</para>
<para>The <filename>info.mtree</filename> file is another non-essential file which is
provided for user reference. It contains the MD5 signatures of the
<emphasis>unpacked</emphasis> distribution files and can be later
used with the &man.mtree.8; program to verify the installation
permissions and checksums against any possible modifications to the
file. When used with the <filename>bin</filename> distribution,
this can be an excellent way of detecting trojan horse attacks on
your system.</para>
<para>Finally, the <filename>install.sh</filename> 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:</para>
<screen>&prompt.root; <userinput>cd /cdrom/info</userinput>
&prompt.root; <userinput>sh install.sh</userinput></screen>
<para>And that's all there is to it! Each distribution contains its
own <filename>install.sh</filename> file for this.</para>
</sect1>

529
release/doc/en_US.ISO8859-1/installation/common/trouble.sgml Normal file
View File

@ -0,0 +1,529 @@
<!--
$FreeBSD$
This file contains the comments of the old TROUBLE.TXT file.
-->
<sect1 id="trouble">
<title>Troubleshooting</title>
<sect2 id="repairing">
<title>Repairing an Existing &os; Installation</title>
<para>&os; releases 2.2.1 and later feature a
<quote>Fixit</quote> option in the top menu of the boot floppy.
To use it, you will also need either a
<filename>fixit.flp</filename> image floppy, generated in the same
fashion as the boot floppy, or the 2nd CDROM from Walnut Creek
CDROM's &os; distribution.</para>
<para>To invoke fixit, simply boot the
<filename>kern.flp</filename> floppy, choose the
<quote>Fixit</quote> 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 <filename>/stand</filename>
and <filename>/mnt2/stand</filename> directories) for checking,
repairing and examining file systems and their contents. Some
UNIX administration experience <emphasis>is</emphasis> required to
use the fixit option!</para>
</sect2>
<sect2>
<title>Common Installation Problems, Q&amp;A</title>
<qandaset>
<qandaentry>
<question>
<para>I go to boot from the hard disk for the first time
after installing &os;, the kernel loads and probes my
hardware, but stops with messages like:</para>
<screen>changing root device to wd1s1a panic: cannot mount root</screen>
<para>What is wrong? What can I do?</para>
<para>What is this
<literal>bios_drive:interface(unit,partition)kernel_name</literal>
thing that is displayed with the boot help?</para>
</question>
<answer>
<para>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 &os;, and working
out which numbers correspond to which is difficult to get
right.</para>
<para>In the case where the boot disk is not the first disk
in the system, &os; can need some help finding it. There
are two common situations here, and in both of these cases,
you need to tell &os; where the root filesystem is. You
do this by specifying the BIOS disk number, the disk type
and the &os; disk number for that type.</para>
<para>The first situation is where you have two IDE disks,
each configured as the master on their respective IDE
busses, and wish to boot &os; from the second disk. The
BIOS sees these as disk 0 and disk 1, while &os; sees
them as <devicename>wd0</devicename> and
<devicename>wd2</devicename>.</para>
<para>&os; is on BIOS disk 1, of type
<literal>wd</literal> and the &os; disk number is 2, so
you would say:</para>
<screen><userinput>1:wd(2,a)kernel</userinput></screen>
<para>Note that if you have a slave on the primary bus, the
above is not necessary (and is effectively wrong).</para>
<para>The second situation involves booting from a SCSI disk
when you have one or more IDE disks in the system. In this
case, the &os; 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 <literal>da</literal> and
&os; disk number 0, so you would say:</para>
<screen><userinput>2:da(0,a)kernel</userinput></screen>
<para>To tell &os; 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.</para>
<para>Once you have determined the correct values to use,
you can put the command exactly as you would have typed it
in the <filename>/boot.config</filename> file using a
standard text editor. Unless instructed otherwise, &os;
will use the contents of this file as the default response
to the <literal>boot:</literal> prompt.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I go to boot from the hard disk for the first time
after installing &os;, but the Boot Manager prompt just
prints <literal>F?</literal> at the boot menu each time but
the boot won't go any further.</para>
</question>
<answer>
<para>The hard disk geometry was set incorrectly in the
Partition editor when you installed &os;. Go back into
the partition editor and specify the actual geometry of your
hard disk. You must reinstall &os; again from the
beginning with the correct geometry.</para>
<para>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
&os; after that. The install program will see the DOS
partition and try to infer the correct geometry from it,
which usually works.</para>
<para>The following tip is no longer recommended, but is left here
for reference:</para>
<blockquote>
<para>If you are setting up a truly dedicated &os;
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 &os; 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 &os; on a
disk.</para>
</blockquote>
</answer>
</qandaentry>
</qandaset>
</sect2>
<sect2>
<title>Known Hardware Problems, Q&amp;A</title>
<note>
<para>Please send hardware tips for this section to &a.jkh;.</para>
</note>
<qandaset>
<qandaentry>
<question>
<para>The &man.mcd.4; driver keeps thinking that it has
found a device and this stops my Intel EtherExpress card
from working.</para>
</question>
<answer>
<para>Use the UserConfig utility (see
<filename>HARDWARE.TXT</filename>) and disable the probing
of the <devicename>mcd0</devicename> and
<devicename>mcd1</devicename> devices. Generally speaking,
you should only leave the devices that you will be using
enabled in your kernel.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>&os; claims to support the 3Com PCMCIA card, but my
card isn't recognized when it's plugged into my
laptop.</para>
</question>
<answer>
<para>There are a couple of possible problems. First of
all, &os; does not support multi-function cards, so if
you have a combo Ethernet/modem card (such as the 3C562), it
won't work. The default driver for the 3C589 card was
written just like all of the other drivers in &os;, and
depend on the card's own configuration data stored in NVRAM
to work. You must correctly configure &os;'s driver to
match the IRQ, port, and IOMEM stored in NVRAM.</para>
<para>Unfortunately, the only program capable of reading
them is the 3COM supplied DOS program. This program must be
run on a absolutely clean system (no other drivers must be
running), and the program will whine about CARD-Services not
being found, but it will continue. This is necessary to
read the NVRAM values. You want to know the IRQ, port, and
IOMEM values (the latter is called the CIS tuple by 3COM).
The first two can be set in the program, the third is
un-settable, and can only be read. Once you have these
values, set them in UserConfig and your card will be
recognized.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>&os; finds my PCMCIA network card, but no packets
appear to be sent even though it claims to be working.</para>
</question>
<answer>
<para>Many PCMCIA cards have the ability to use either the
10-Base2 (BNC) or 10-BaseT connectors for connecting to the
network. The driver is unable to <quote>auto-select</quote>
the correct connector, so you must tell it which connector
to use. In order to switch between the two connectors, the
link flags must be set. Depending on the model of the card,
<option>-link0 link1</option> or <option>-link0
-link1</option> will choose the correct network connector.
You can set these in &man.sysinstall.8; by using the
<literal>Extra options to ifconfig:</literal> field in the
network setup screen.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>The system finds my &man.ed.4; network card, but I
keep getting device timeout errors.</para>
</question>
<answer>
<para>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 <literal>?</literal> in the IRQ field of your
kernel config file.</para>
<para>Either move the jumper on the card to a hard
configuration setting (altering the kernel settings if
necessary), or specify the IRQ as <literal>-1</literal> in UserConfig or <literal>?</literal>
in your kernel config file. This will tell the kernel to
use the soft configuration.</para>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I have a Matsushita/Panasonic drive but it isn't
recognized by the system.</para>
</question>
<answer>
<para>Make certain that the I/O port that the &man.matcd.4; driver
is set to is correct for the host interface card you have.
(Some SoundBlaster DOS drivers report a hardware I/O port
address for the CD-ROM interface that is 0x10 lower than it
really is.)</para>
<para>If you are unable to determine the settings for the
card by examining the board or documentation, you can use
UserConfig to change the 'port' address (I/O port) to -1 and
start the system. This setting causes the driver to look at
a number of I/O ports that various manufacturers use for
their Matsushita/Panasonic/Creative CD-ROM interfaces. Once
the driver locates the address, you should run UserConfig
again and specify the correct address. Leaving the 'port'
parameter set to -1 increases the amount of time that it
takes the system to boot, and this could interfere with
other devices.</para>
<para>The double-speed Matsushita CR-562 and CR-563 are the
only drives that are supported.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I booted the install floppy on my IBM ThinkPad (tm)
laptop, and the keyboard is all messed up.</para>
</question>
<answer>
<para>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'.)</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I try to boot the install floppy, I see the
following message and nothing seems to be happening. I
cannot enter anything from the keyboard either.</para>
<screen>Keyboard: no</screen>
</question>
<answer>
<para>Due to lack of space, full support for old XT/AT
(84-key) keyboards is no longer available in the bootblocks.
Some notebook computers may also have this type of keyboard.
If you are still using this kind of hardware, you will see
the above message appears when you boot from the CD-ROM or
an install floppy.</para>
<para>As soon as you see this message, hit the space bar,
and you will see the prompt:</para>
<screen>>> FreeBSD/i386 BOOT
Default: x:xx(x,x)/boot/loader
boot:</screen>
<para>Then enter <userinput>-Dh</userinput>, and things
should proceed normally.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I have a Matsushita/Panasonic CR-522, a
Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is
not recognized even when the correct I/O port is set.</para>
</question>
<answer>
<para>These CD-ROM drives are currently not supported by
&os;. The command sets for these drives are not compatible
with the double-speed CR-562 and CR-563 drives.</para>
<para>The single-speed CR-522 and CR-523 drives can be
identified by their use of a CD-caddy. </para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I'm trying to install from a tape drive but all I get
is something like this on the screen:</para>
<screen>sa0(aha0:1:0) NOT READY csi 40,0,0,0</screen>
</question>
<answer>
<para>There's a limitation in the current &man.sysinstall.8;
that the tape <emphasis>must</emphasis> be in the drive
while &man.sysinstall.8; is started or it won't be detected.
Try again with the tape in the drive the whole time.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I've installed &os; onto my system, but it hangs
when booting from the hard drive with the message:</para>
<screen>Changing root to /dev/da0a</screen>
</question>
<answer>
<para>his problem may occur in a system with a 3com 3c509
Ethernet adapter. The &man.ep.4; device driver appears to
be sensitive to probes for other devices that also use
address 0x300. Boot your &os; system by power cycling
the machine (turn off and on). At the
<literal>Boot:</literal> prompt specify the
<option>-c</option>. This will invoke UserConfig (see
<xref linkend="repairing"> above).
Use the <literal>disable</literal>
command to disable the device probes for all devices at
address 0x300 except the ep0 driver. On exit, your machine
should successfully boot &os;.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>My system can not find my Intel EtherExpress 16 card.</para>
</question>
<answer>
<para>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
<filename>softset.exe</filename> program.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When installing on an EISA HP Netserver, my on-board
AIC-7xxx SCSI controller isn't detected.</para>
</question>
<answer>
<para>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 <option>-c</option> option into
UserConfig, but <emphasis>don't</emphasis> use the pretty
visual mode but the plain old CLI mode. Type:
<screen><userinput>eisa 12</userinput>
<userinput>quit</userinput></screen>
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.</para>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>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.</para>
</question>
<answer>
<para>Your machine doesn't like the new
<literal>i586_copyout</literal> and
<literal>i586_copyin</literal> 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
(<quote>expert mode</quote>) version and type the following
at it:
<screen><userinput>flags npx0 1</userinput></screen>
Then proceed normally to boot. This will be saved
into your kernel, so you only need to do it once.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I have this CMD640 IDE controller that is said to be
broken.</para>
</question>
<answer>
<para>Yes, it is. &os; does not support this controller
except through the legacy wdc driver.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>On a Compaq Aero notebook, I get the message <quote>No
floppy devices found! Please check ...</quote> when trying to
install from floppy.</para>
</question>
<answer>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I go to boot my Intel AL440LX
(<quote>Atlanta</quote>) -based system from the hard disk the
first time, it stops with a <literal>Read Error</literal>
message.</para>
</question>
<answer>
<para>There appears to be a bug in the BIOS on at least some
of these boards, this bug results in the &os; bootloader
thinking that it is booting from a floppy disk. This is
only a problem if you are not using the BootEasy boot
manager. Slice the disk in <quote>compatible</quote>mode
and install BootEasy during the &os; installation to
avoid the bug, or upgrade the BIOS (see Intel's website for
details).</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When installing on an Dell Poweredge XE, Dell
proprietary RAID controller DSA (Dell SCSI Array) isn't
recognized.</para>
</question>
<answer>
<para>Configure the DSA to use AHA-1540 emulation using EISA
configuration utility. After that &os; 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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>My Ethernet adapter is detected as an AMD PCnet-FAST
(or similar) but it doesn't work. (Eg. onboard Ethernet on
IBM Netfinity 5xxx or 7xxx)</para>
</question>
<answer>
<para>The &man.lnc.4; driver is currently faulty, and will
often not work correctly with the PCnet-FAST and
PCnet-FAST+. You need to install a different Ethernet
adapter.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I have an IBM EtherJet PCI card, it is detected by the
&man.fxp.4; driver correctly, but the lights on the card don't
come on and it doesn't connect to the network.</para>
</question>
<answer>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I configure the network during installation on an
IBM Netfinity 3500, the system freezes.</para>
</question>
<answer>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I install onto a drive managed by a Mylex PCI
RAID controller, the system fails to boot (eg. with a
<literal>read error</literal> message).</para>
</question>
<answer>
<para>There is a bug in the Mylex driver which results in it
ignoring the <quote>8GB</quote> geometry mode setting in the
BIOS. Use the 2GB mode instead.</para>
</answer>
</qandaentry>
</qandaset>
</sect2>
</sect1>

255
release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml Normal file
View File

@ -0,0 +1,255 @@
<!--
$FreeBSD$
This section contains the contents of the old UPGRADE.TXT
file.
-->
<sect1 id="upgrading">
<title>Upgrading &os;</title>
<para>These instructions describe a procedure for doing a binary
upgrade from an older version of &os;.</para>
<warning>
<para>While the &os; upgrade procedure does its best to
safeguard against accidental loss of data, it is still more than
possible to <emphasis>wipe out your entire disk</emphasis> with
this installation! Please do not accept the final confirmation
request unless you have adequately backed up any important data
files.</para>
</warning>
<important>
<para>These notes assume that you are using the version of
&man.sysinstall.8; supplied with the version of &os; to which you
intend to upgrade. Using a mismatched version of &man.sysinstall.8; 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 &man.sysinstall.8; from
an existing installation to upgrade to a newer version of
&os;. This is <emphasis>not</emphasis> recommended.</para>
<para>Furthermore, if you are upgrading from &os; 2.2.5 or
earlier, see <xref linkend="fstab"> for important details regarding changes
to the <filename>/etc/fstab</filename> file required during the upgrade procedure.</para>
</important>
<sect2>
<title>Introduction</title>
<para>The upgrade procedure replaces distributions selected by the
user with those corresponding to the new &os; release. It
preserves standard system configuration data, as well as user
data, installed packages and other software.</para>
<para>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.</para>
<sect3>
<title>Upgrade Overview</title>
<para>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.</para>
<para>System configuration is preserved by retaining and
restoring the previous version of the following files:</para>
<para><filename>Xaccel.ini</filename>,
<filename>adduser.conf</filename>,
<filename>aliases</filename>,
<filename>aliases.db</filename>,
<filename>amd.map</filename>,
<filename>crontab</filename>,
<filename>csh.cshrc</filename>,
<filename>csh.login</filename>,
<filename>csh.logout</filename>,
<filename>daily</filename>,
<filename>disktab</filename>,
<filename>dm.conf</filename>,
<filename>exports</filename>,
<filename>fbtab</filename>,
<filename>fstab</filename>,
<filename>ftpusers</filename>,
<filename>gettytab</filename>,
<filename>gnats</filename>,
<filename>group</filename>,
<filename>hosts</filename>,
<filename>hosts.equiv</filename>,
<filename>hosts.lpd</filename>,
<filename>inetd.conf</filename>,
<filename>kerberosIV</filename>,
<filename>localtime</filename>,
<filename>login.access</filename>,
<filename>mail.rc</filename>,
<filename>make.conf</filename>,
<filename>manpath.config</filename>,
<filename>master.passwd</filename>,
<filename>mib.txt</filename>,
<filename>modems</filename>,
<filename>monthly</filename>,
<filename>motd</filename>,
<filename>namedb</filename>,
<filename>networks</filename>,
<filename>nsswitch.conf</filename>,
<filename>passwd</filename>,
<filename>phones</filename>,
<filename>ppp</filename>,
<filename>printcap</filename>,
<filename>profile</filename>,
<filename>protocols</filename>,
<filename>pwd.db</filename>,
<filename>rc</filename>,
<filename>rc.firewall</filename>,
<filename>rc.i386</filename>,
<filename>rc.local</filename>,
<filename>rc.network</filename>,
<filename>rc.conf</filename>,
<filename>remote</filename>,
<filename>resolv.conf</filename>,
<filename>rmt</filename>,
<filename>security</filename>,
<filename>sendmail.cf</filename>,
<filename>services</filename>,
<filename>shells</filename>,
<filename>skeykeys</filename>,
<filename>spwd.db</filename>,
<filename>supfile,</filename>
<filename>syslog.conf</filename>,
<filename>termcap</filename>,
<filename>ttys</filename>,
<filename>uucp</filename>,
<filename>weekly</filename></para>
<para>The versions of these files which correspond to the new
version are moved to <filename>/etc/upgrade/</filename>. 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.</para>
<para>During the upgrade procedure, the administrator is
prompted for a location into which all files from
<filename>/etc/</filename> are saved. In the event that local
modifications have been made to other files, they may be
subsequently retrieved from this location.</para>
</sect3>
</sect2>
<sect2>
<title>Procedure</title>
<para>This section details the upgrade procedure. Particular
attention is given to items which substantially differ from a
normal installation.</para>
<sect3>
<title>Backup</title>
<para>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.</para>
</sect3>
<sect3>
<title>Mount Filesystems</title>
<para>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. <emphasis>Do not</emphasis>set the <quote>newfs
flag</quote> for any filesystems, as this will cause data
loss.</para>
</sect3>
<sect3>
<title>Select Distributions</title>
<para>When selecting distributions, there are no constraints
on which must be selected. As a general rule, the <literal>bin</literal>
distribution should be selected for an update, and the <literal>man</literal>
distribution if manpages are already installed. Other
distributions may be selected beyond those originally
installed if the administrator wishes to add additional
functionality.</para>
</sect3>
<sect3 id="fstab">
<title>After Installation</title>
<para>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
<filename>/etc/rc.conf</filename> and
<filename>/etc/fstab</filename> files should be checked.</para>
<para>Read the following, but <emphasis>do not</emphasis> update
<filename>/etc/fstab</filename> as described below until the new
system has booted correctly. The upgrade procedure replaces the
previous &os; kernel with a <filename>GENERIC</filename> kernel,
and a custom kernel may need to be generated to suit the local
system configuration.</para>
<important>
<para>&os; 2.2.6 introduced a change in the naming of the
device from which the root filesystem is mounted. This
change affects all systems, however user intervention is
only required for systems undergoing an upgrade installation
from a version prior to &os; 2.2.6.</para>
<para>Previously, the root filesystem was always mounted from
the compatibility slice, while other partitions on the same
disk were mounted from their true slice. This might, for
example, have resulted in an <filename>/etc/fstab</filename>
file like:</para>
<screen># Device Mountpoint FStype Options Dump Pass#
/dev/wd0s2b none swap sw 0 0
/dev/wd0a / ufs rw 1 1
/dev/wd0s2f /local0 ufs rw 1 1
/dev/wd0s2e /usr ufs rw 1 1</screen>
<para>For &os; 2.2.6 and later, this format changes so that
the device for <filename>/</filename> is consistent with
others. Also, the driver for the ATA-drives has changed from
&man.wd.4; to &man.ad.4;, so the new file could look something
like:</para>
<screen># Device Mountpoint FStype Options Dump Pass#
/dev/ad0s2b none swap sw 0 0
/dev/ad0s2a / ufs rw 1 1
/dev/ad0s2f /local0 ufs rw 1 1
/dev/ad0s2e /usr ufs rw 1 1</screen>
<para>If <filename>/etc/fstab</filename> is not updated
manually in this case, the system will issue a warning message
whenever <filename>/</filename> is mounted (normally at
startup) indicating the change that must be made. In
addition, trouble may be experienced if the root filesystem is
not correctly unmounted, whereby the root filesystem will not
be marked clean at the next reboot.</para>
<para>This change should be made as soon as the upgraded
system has been successfully rebooted.</para>
</important>
</sect3>
</sect2>
<sect2>
<title>Alternative Upgrade Techniques</title>
<para>Those interested in an upgrade method that allows more
flexibility and sophistication should take a look at the
<quote>Upgrading FreeBSD from source</quote> tutorial found at
http://www.freebsd.org/docs.html. This method requires reliable
network connectivity, extra disk space and spare time, but has
advantages for networks and other more complex
installations.</para>
</sect2>
</sect1>

23
release/doc/en_US.ISO8859-1/installation/i386/Makefile Normal file
View File

@ -0,0 +1,23 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= ../common/artheader.sgml
SRCS+= ../common/install.sgml
SRCS+= ../common/floppies.sgml
SRCS+= ../common/layout.sgml
SRCS+= ../common/trouble.sgml
SRCS+= ../common/upgrade.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

27
release/doc/en_US.ISO8859-1/installation/i386/article.sgml Normal file
View File

@ -0,0 +1,27 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/install.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "i386">
]>
<article>
&artheader;
&sect.install;
&sect.layout;
&sect.floppies;
&sect.upgrade;
&sect.trouble;
</article>

24
release/doc/en_US.ISO8859-1/readme/Makefile Normal file
View File

@ -0,0 +1,24 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../share/sgml/catalog
#
# SRCS lists the individual SGML files that make up the document. Changes
# to any of these files will force a rebuild
#
# SGML content
SRCS+= article.sgml
SRCS+= artheader.sgml
SRCS+= intro.sgml
SRCS+= about.sgml
SRCS+= obtaining.sgml
SRCS+= problems.sgml
SRCS+= ack.sgml
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

102
release/doc/en_US.ISO8859-1/readme/about.sgml Normal file
View File

@ -0,0 +1,102 @@
<!--
$FreeBSD$
about.sgml
General information about FreeBSD. Most contents of this file
come from the old ABOUT.TXT.
-->
<sect1>
<title>About &os;</title>
<para>What is &os;? &os; is an operating system based on 4.4 BSD
Lite for Intel, AMD, Cyrix or NexGen <quote>x86</quote> based PC
hardware and Compaq (formerly DEC) Alpha computers. Versions for
the IA64 and PowerPC architectures are currently under
development as well. &os; works with a
very wide variety of PC peripherals and configurations and can be
used for everything from software development to Internet Service
Provision.</para>
<para>This release of &os; contains everything you need to run
such a system, including full source code for everything. With the
source distribution installed you can literally recompile the entire
system from scratch with one command, making it ideal for students,
researchers or folks who simply want to see how it all works.</para>
<para>A large collection of third party ported software (the
<quote>Ports Collection</quote>) is also provided to make it easier
for you to obtain and install all your favorite traditional UNIX
utilities for &os;. Over 5000 ports, from editors to programming
languages to graphical applications, make &os; a powerful and
comprehensive operating environment that extends far beyond what's
provided by many commercial versions of UNIX.</para>
<para>For more documentation on this system it is recommended that
you purchase The Complete FreeBSD, available from local bookstores
and from The FreeBSD Mall (<ulink
url="http://www.freebsdmall.com">http://www.freebsdmall.com</ulink>),
as well as the 4.4BSD Document Set from O'Reilly Associates and the
USENIX Association, ISBN 1-56592-082-1. We have no connection with
O'Reilly, we're just satisfied customers!</para>
<para>If you're new to &os; then you should also read
<emphasis>everything</emphasis>
listed in the Documentation menu on the boot floppy. It may seem
like a lot to read, but you should at least acquaint yourself with
the types of information available should you later get stuck. Once
the system is installed, you can also revisit this menu and use a
Web browser to read the installed FAQ (Frequently Asked Questions)
and Handbook HTML documentation sets for &os;. Note that on-line
versions of the <ulink
url="http://www.freebsd.org/faq/">FAQ</ulink> and <ulink
url="http://www.freebsd.org/handbook/">Handbook</ulink> are also
available from the <ulink
url="http://www.freebsd.org/">FreeBSD Project Web
site</ulink>, if you have an Internet connection. See
<filename>README.TXT</filename> for more information on the
resources available to you.</para>
<note>
<para>If you read no other documentation before installing a given
version of &os;, you should at least by all means <emphasis>read
the errata</emphasis> for that release so that you don't stumble
over problems which have already been found and fixed. The
<filename>ERRATA.TXT</filename> file accompanying your release (it
should be right next to this file) is obviously already out of
date by definition, but other copies are kept updated on the net
and should be consulted as the <quote>current errata</quote> for
your release (this is also what your
<filename>ERRATA.TXT</filename> file says, by the way). These
other copies of the errata are located at:
<orderedlist>
<listitem>
<para><ulink url="http://www.freebsd.org/releases/">http://www.freebsd.org/releases/</ulink></para>
</listitem>
<listitem>
<para>ftp://ftp.freebsd.org/pub/FreeBSD/releases/your-release/ERRATA.TXT
(and any sites which keep up-to-date mirrors of this
location).</para>
</listitem>
</orderedlist>
</para>
</note>
<warning>
<para>While &os; does its best to safeguard against accidental
loss of data, it's still more than possible to <emphasis>wipe out
your entire disk</emphasis>
with this installation! Please do not proceed to the
final &os; installation menu unless you've adequately backed up
any important data first! We really mean it!</para>
</warning>
</sect1>

29
release/doc/en_US.ISO8859-1/readme/ack.sgml Normal file
View File

@ -0,0 +1,29 @@
<!--
$FreeBSD$
ack.sgml
This file is the Acknowledgments section of the old RELNOTES.TXT.
-->
<sect1>
<title>Acknowledgments</title>
<para>&os; represents the cumulative work of many hundreds, if not
thousands, of individuals from around the world who have worked very
hard to bring you this release. For a complete list of &os;
project staffers, please see:</para>
<para><ulink url="http://www.freebsd.org/handbook/staff.html">http://www.freebsd.org/handbook/staff.html</ulink></para>
<para>or, if you've loaded the doc distribution:</para>
<para><filename>/usr/share/doc/handbook/staff.html</filename></para>
<para>Special thanks also go to the many thousands of &os; users and
testers all over the world, without whom this release simply would
not have been possible.</para>
</sect1>

13
release/doc/en_US.ISO8859-1/readme/artheader.sgml Normal file
View File

@ -0,0 +1,13 @@
<!-- $FreeBSD$ -->
<articleinfo>
<title>&os; &release.current; README</title>
<corpauthor>The &os; Project</corpauthor>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>

22
release/doc/en_US.ISO8859-1/readme/article.sgml Normal file
View File

@ -0,0 +1,22 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "readme.ent"> %sections;
]>
<article>
&artheader;
&sect.intro;
&sect.about;
&sect.obtaining;
&sect.problems;
&sect.ack;
</article>

86
release/doc/en_US.ISO8859-1/readme/intro.sgml Normal file
View File

@ -0,0 +1,86 @@
<!--
$FreeBSD$
intro.sgml
Introduction to the README file. Most text here comes from the
old README.TXT (the file with Chuck in ASCII art).
-->
<sect1>
<title>Introduction</title>
<para>This is a binary snapshot of &os; &release.current;, the
&release.branch; branch that is currently moving towards
&release.next;.</para>
<para>Feedback or offers to help with anything you see in this
release are most welcome and should be sent to one of the
appropriate mailing lists, as listed in <xref linkend="contacting">.</para>
<sect2>
<title>Target Audience</title>
<para>This release is aimed primarily at early-adopters and the
various other folks who want to get involved with the ongoing
development of &os; and are willing to deal with a few bumps in
the road. We do our best to ensure that each snapshot works as
advertised, but tracking -CURRENT is a process which frequently
has its off days.</para>
<para>If you're both technically proficient and know exactly what
you're getting into here (e.g. you've been following -CURRENT)
then this snapshot is probably for you. If you're more interested
in doing business with &os; than in playing with the cutting
edge of technology, however, then 3.x or 4.x is almost certainly
your best bet.</para>
<para>If you're a developer/hobbiest and not interested in QA'd
releases so much as simply keeping up to date on the latest &os;
technology, you can also install one of our
<quote>snapshot</quote> releases.
</para>
</sect2>
<sect2>
<title>For More Information</title>
<para>A number of other files provide more specific information
about this distribution.
<itemizedlist>
<listitem>
<para><filename>README.TXT</filename>: This file, which
gives some general information about &os; as well as some
cursory notes about installation..</para>
</listitem>
<listitem>
<para><filename>RELNOTES.TXT</filename>: The release notes,
showing what's new and different in &os; &release.current;
compared to &os; &release.prev;.</para>
</listitem>
<listitem>
<para><filename>HARDWARE.TXT</filename>: The hardware
compatability list, showing devices with which &os; has been
tested and is known to work.</para>
</listitem>
<listitem>
<para><filename>ERRATA.TXT</filename>: Release errata.
Late-breaking, post-release information can be found in this
file. Read this file! It will tell you where to look for
the latest information on problems which have been found and
fixed since this release was created (and may bite
you).</para>
</listitem>
</itemizedlist>
</para>
<para>Most information is also available from the
Documentation menu during installation.</para>
</sect2>
</sect1>

102
release/doc/en_US.ISO8859-1/readme/obtaining.sgml Normal file
View File

@ -0,0 +1,102 @@
<!--
$FreeBSD$
obtaining.sgml
Information on getting a copy of FreeBSD. This text used to
be the "Obtaining FreeBSD" section of RELNOTES.TXT.
-->
<sect1>
<title>Obtaining &os;</title>
<para>You may obtain &os; in a variety of ways. This section
focuses on those ways that are primarily of use for obtaining a
complete &os; distribution, rather than updating an existing
installation. More information can be found in the <ulink
url="http://www.freebsd.org/handbook/mirrors.html"><quote>Obtaining
FreeBSD</quote></ulink> appendix to the <ulink
url="http://www.freebsd.org/handbook/">FreeBSD
Handbook</ulink>.</para>
<sect2>
<title>CDROM</title>
<para>&os; 4.x-RELEASE and 3.x-RELEASE may be ordered on
CDROM from:
<address>
BSDi
<street>4041 Pike Lane, Suite D</street>
<city>Concord</city> <state>CA</state> <postcode>94520</postcode>
<country>USA</country>
<phone>+1-800-786-9907</phone>
<phone>+1-925-674-0783</phone>
<fax>+1-925-674-0821 (FAX)</fax></address>
</para>
<para>Orders may also be placed via the Internet from
<email>orders@cdrom.com</email> or <ulink
url="http://www.cdrom.com/">http://www.cdrom.com/</ulink>. A
current catalog can be obtained via ftp from <ulink
url="ftp://ftp.cdrom.com/cdrom/catalog">ftp://ftp.cdrom.com/cdrom/catalog</ulink>.</para>
<para>As of this writing, the cost per -RELEASE CDROM set is $39.95
(US Dollars) or $24.95 with a &os;
subscription. &os; SNAPshot CDROM sets, when available, are $39.95 or
$14.95 with a &os;-SNAP subscription (-RELEASE and -SNAP
subscriptions are entirely separate). With a subscription, you
will automatically receive updates as they are released. Your
credit card will be billed when each disk is shipped and you may
cancel your subscription at any time without further
obligation.</para>
<para>Shipping (per order not per disk) is $5.00 in the United
States, Canada or Mexico and $9.00 overseas. BSDi accepts Visa,
Mastercard, Discover, American Express or checks in U.S. Dollars
and ships COD within the United States. California residents
please add 8.25% sales tax.</para>
<para>Should you be dissatisfied for any reason, the CDROM comes with
an unconditional return policy.</para>
</sect2>
<sect2>
<title>FTP</title>
<para>You can use FTP to retrieve &os; and any or all of its
optional packages from <ulink
url="ftp://ftp.freebsd.org/">ftp://ftp.freebsd.org/</ulink>, which
is the
official &os; release site.</para>
<para>For other locations that mirror the &os; software see the
file <filename>MIRROR.SITES</filename>.
Please FTP the distribution from the site
closest (in networking terms) to you. Additional mirror sites are
always welcome!
Contact <email>freebsd-admin@FreeBSD.org</email> for more
details if you'd like to become an official mirror site.</para>
<para>Mirrors generally contain the floppy disk images necessary
to begin an installation, as well as the distribution files needed
for the install process itself. Some mirrors also contain some of
the ISO images necessary to create a CDROM of a &os; release.</para>
</sect2>
<sect2>
<title>Email</title>
<para>If you do not have access to the Internet and electronic
mail is your only recourse, then you may still fetch the files by
sending mail to <email>ftpmail@ftpmail.vix.com</email> - putting
the keyword <literal>help</literal> in your message to get more
information on how to fetch files from a &os; FTP archive using
this mechanism. Please do note, however, that this will end up
sending many <emphasis>tens of megabytes</emphasis> through the
mail and should only be employed as an absolute
<emphasis>last</emphasis> resort!</para>
</sect2>
</sect1>

78
release/doc/en_US.ISO8859-1/readme/problems.sgml Normal file
View File

@ -0,0 +1,78 @@
<!--
$FreeBSD$
problems.sgml
Information on contacting the FreeBSD project, originally from
RELNOTES.TXT.
-->
<sect1 id="contacting">
<title>Reporting Problems, Making Suggestions, and Submitting
Code</title>
<para>Your suggestions, bug reports and contributions of code are
always valued &mdash; please do not hesitate to report any problems you
may find (preferably with a fix attached, if you can!).</para>
<para>The preferred method to submit bug reports from a machine with
Internet mail connectivity is to use the &man.send-pr.1; command or
use the CGI script at <ulink
url="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</ulink>.
Bug reports will be dutifully filed by our faithful bugfiler program
and you can be sure that we'll do our best to respond to all
reported bugs as soon as possible. Bugs filed in this way are also
visible on our Web site in the support section and are therefore
valuable both as bug reports and as <quote>signposts</quote> for
other users concerning potential problems to watch out for.</para>
<para>If, for some reason, you are unable to use &man.send-pr.1; to
submit a bug report, you can try to send it to the &a.bugs;.</para>
<para>Note that &man.send-pr.1; itself is a shell script that should
be easy to move even onto a totally different system. We much
prefer if you could use this interface, since it make it easier to
keep track of the problem reports. However, before submitting,
please try to make sure whether the problem might have already been
fixed since.</para>
<para>Otherwise, for any questions or tech support issues, please send
mail to the &a.questions;.</para>
<para>If you're tracking the -current development efforts, you
<emphasis>must</emphasis> join the &a.current;, in order to keep
abreast of recent developments and changes that may affect the way
you use and maintain the system.
<para>Additionally, being a volunteer effort, we are always happy to
have extra hands willing to help &mdash; there are already far more
desired enhancements than we'll ever be able to manage by ourselves!
To contact us on technical matters, or with offers of help, please
send mail to the &a.hackers;.</para>
<para>Please note that these mailing lists can experience
<emphasis>significant</emphasis> amounts of traffic and if you have
slow or expensive mail access and are only interested in keeping up
with significant FreeBSD events, you may find it preferable to
subscribe instead to the &a.announce;.</para>
<para>All of the mailing lists can be freely joined by anyone
wishing to do so. Send mail to &a.majordomo;
and include the keyword <literal>help</literal> on a line by itself
somewhere in the body of the message. This will give you more
information on joining the various lists, accessing archives, etc.
There are a number of mailing lists targeted at special interest
groups not mentioned here; more information can be obtained either
through majordomo or the <ulink
url="http://www.freebsd.org/support.html#mailing-list">mailing lists
section</ulink> of the FreeBSD Web site.</para>
<important>
<para>Do <emphasis>not</emphasis> send email to the lists asking to
be subscribed. Use the &a.majordomo; address
instead.</para>
</important>
</sect1>

14
release/doc/en_US.ISO8859-1/readme/readme.ent Normal file
View File

@ -0,0 +1,14 @@
<!-- -*- sgml -*- -->
<!-- $FreeBSD$ -->
<!-- Text constants which probably don't need to be changed.-->
<!-- Files to be included -->
<!ENTITY artheader SYSTEM "artheader.sgml">
<!ENTITY sect.intro SYSTEM "intro.sgml">
<!ENTITY sect.about SYSTEM "about.sgml">
<!ENTITY sect.obtaining SYSTEM "obtaining.sgml">
<!ENTITY sect.problems SYSTEM "problems.sgml">
<!ENTITY sect.ack SYSTEM "ack.sgml">

7
release/doc/en_US.ISO8859-1/relnotes/Makefile Normal file
View File

@ -0,0 +1,7 @@
# $FreeBSD$
SUBDIR = alpha
SUBDIR+= i386
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

21
release/doc/en_US.ISO8859-1/relnotes/alpha/Makefile Normal file
View File

@ -0,0 +1,21 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= ../common/relnotes.ent
SRCS+= ../common/artheader.sgml
SRCS+= ../common/new.sgml
SRCS+= ../common/upgrading.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

25
release/doc/en_US.ISO8859-1/relnotes/alpha/article.sgml Normal file
View File

@ -0,0 +1,25 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/relnotes.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "alpha">
]>
<article>
&artheader;
&sect.intro;
&sect.new;
&sect.upgrading;
</article>

1469
release/doc/en_US.ISO8859-1/relnotes/article.sgml Normal file
View File

File diff suppressed because it is too large Load Diff

13
release/doc/en_US.ISO8859-1/relnotes/common/artheader.sgml Normal file
View File

@ -0,0 +1,13 @@
<!-- $FreeBSD$ -->
<articleinfo>
<title>&os; &release.current; &arch; Release Notes</title>
<corpauthor>The FreeBSD Project</corpauthor>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>

26
release/doc/en_US.ISO8859-1/relnotes/common/intro.sgml Normal file
View File

@ -0,0 +1,26 @@
<!--
$FreeBSD$
Introduction to the release notes, adapted from the
introduction to the old RELNOTES.TXT.
-->
<sect1>
<title>Introduction</title>
<para>This document contains the release notes for &os; &release.current; on
the &arch; hardware platform. It describes new features of &os;
that have been added (or changed) since &release.prev;.</para>
<para>For information about &os; and the layout of the
distribution directory (especially if you're installing from
floppies!), see <filename>README.TXT</filename>. For installation
instructions, see the <filename>INSTALL.TXT</filename> and
<filename>HARDWARE.TXT</filename> files.</para>
<para>For the latest of these &release.branch; snapshots, you should always
see:</para>
<para><ulink url="&release.url;">&release.url;</ulink></para>
</sect1>

1469
release/doc/en_US.ISO8859-1/relnotes/common/new.sgml Normal file
View File

File diff suppressed because it is too large Load Diff

16
release/doc/en_US.ISO8859-1/relnotes/common/relnotes.ent Normal file
View File

@ -0,0 +1,16 @@
<!-- -*- sgml -*- -->
<!-- $FreeBSD$ -->
<!-- Text constants which probably don't need to be changed.-->
<!-- The marker for MFCs. -->
<!ENTITY merged "[MERGED]">
<!-- Files to be included -->
<!ENTITY artheader SYSTEM "../common/artheader.sgml">
<!ENTITY sect.intro SYSTEM "../common/intro.sgml">
<!ENTITY sect.new SYSTEM "../common/new.sgml">
<!ENTITY sect.upgrading SYSTEM "../common/upgrading.sgml">

41
release/doc/en_US.ISO8859-1/relnotes/common/upgrading.sgml Normal file
View File

@ -0,0 +1,41 @@
<!--
$FreeBSD$
Summary information on upgrading FreeBSD. This comes from
the similarly-named section of RELNOTES.TXT.
-->
<sect1>
<title>Upgrading from previous releases of &os;</title>
<para>If you're upgrading from a previous release of &os;,
most likely it's 4.X and there may be some issues affecting you,
depending of course on your chosen method of upgrading. There
are two popular ways of upgrading &os; distributions:</para>
<para>
<itemizedlist>
<listitem>
<para>Using sources, via <filename>/usr/src</filename></para>
</listitem>
<listitem>
<para>Using the binary upgrade option of &man.sysinstall.8;.</para>
</listitem>
</itemizedlist>
</para>
<para>Please read the <filename>UPGRADE.TXT</filename> file for more
information, preferably <emphasis>before</emphasis> beginning an
upgrade. If you are upgrading from source, please be sure to read
<filename>/usr/src/UPDATING</filename> as well.</para>
<para>Finally, if you want to use one of various means to track the
-STABLE or -CURRENT branches of &os;, please be sure to consult the
<ulink
url="http://www.freebsd.org/handbook/current-stable.html"><quote>-CURRENT
vs. -STABLE</quote></ulink> section of the <ulink
url="http://www.freebsd.org/handbook/">FreeBSD
Handbook</ulink>.</para>
</sect1>

21
release/doc/en_US.ISO8859-1/relnotes/i386/Makefile Normal file
View File

@ -0,0 +1,21 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= ../common/relnotes.ent
SRCS+= ../common/artheader.sgml
SRCS+= ../common/new.sgml
SRCS+= ../common/upgrading.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

25
release/doc/en_US.ISO8859-1/relnotes/i386/article.sgml Normal file
View File

@ -0,0 +1,25 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/relnotes.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "i386">
]>
<article>
&artheader;
&sect.intro;
&sect.new;
&sect.upgrading;
</article>

12
release/doc/en_US.ISO_8859-1/Makefile Normal file
View File

@ -0,0 +1,12 @@
# $FreeBSD$
SUBDIR = relnotes
SUBDIR+= hardware
SUBDIR+= readme
SUBDIR+= errata
SUBDIR+= installation
COMPAT_SYMLINK = en
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

13
release/doc/en_US.ISO_8859-1/errata/Makefile Normal file
View File

@ -0,0 +1,13 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

84
release/doc/en_US.ISO_8859-1/errata/article.sgml Normal file
View File

@ -0,0 +1,84 @@
<!--
$FreeBSD$
FreeBSD errata document. Unlike some of the other RELNOTESng
files, this file should remain as a single SGML file, so that
the dollar FreeBSD dollar header has a meaningful modification
time. This file is all but useless without a datestamp on it,
so we'll take some extra care to make sure it has one.
(If we didn't do this, then the file with the datestamp might
not be the one that received the last change in the document.)
-->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
]>
<article>
<articleinfo>
<title>&os; &release.current; Errata</title>
<corpauthor>
The &os; Project
</corpauthor>
<pubdate>$FreeBSD$</pubdate>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>
<sect1>
<title>Introduction</title>
<para>If you read no other documentation before installing this
version of &os;, you should at least by all means <emphasis>read
the errata</emphasis> for this release so that you don't stumble
over problems which have already been found and fixed. This
<filename>ERRATA.TXT</filename> file is obviously already out of
date by definition, but other copies are kept updated on the net and
should be consulted as the <quote>current errata</quote> for your
release. These other copies of the errata are located at:
<orderedlist>
<listitem>
<para><ulink url="http://www.freebsd.org/releases/">http://www.freebsd.org/releases/</ulink></para>
</listitem>
<listitem>
<para><userinput>ftp://ftp.freebsd.org/pub/FreeBSD/releases/<replaceable>architecture</replaceable>/<replaceable>release</replaceable>/ERRATA.TXT</userinput></para>
<para>(and any sites which keep up-to-date mirrors of this
location)</para>
</listitem>
</orderedlist>
</para>
<para>Any changes to this file are also automatically emailed to the
&a.current;.</para>
<para>For all CERT security advisories, see <ulink
url="ftp://ftp.freebsd.org/pub/FreeBSD/CERT/">ftp://ftp.freebsd.org/pub/FreeBSD/CERT/</ulink>.</para>
</sect1>
<sect1>
<title>Security Advisories</title>
<para>Current active security advisories: None.</para>
</sect1>
<sect1>
<title>System Update Information</title>
<para>Current active errata items: None.</para>
</sect1>
</article>

7
release/doc/en_US.ISO_8859-1/hardware/Makefile Normal file
View File

@ -0,0 +1,7 @@
# $FreeBSD$
SUBDIR = alpha
SUBDIR+= i386
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

22
release/doc/en_US.ISO_8859-1/hardware/alpha/Makefile Normal file
View File

@ -0,0 +1,22 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= proc-alpha.sgml
SRCS+= ../common/hw.ent
SRCS+= ../common/artheader.sgml
SRCS+= ../common/dev.sgml
SRCS+= ../common/config.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

26
release/doc/en_US.ISO_8859-1/hardware/alpha/article.sgml Normal file
View File

@ -0,0 +1,26 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/hw.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "alpha">
]>
<article>
&artheader;
&sect.intro;
&sect.proc.alpha;
&sect.dev;
&sect.config;
</article>

2370
release/doc/en_US.ISO_8859-1/hardware/alpha/proc-alpha.sgml Normal file
View File

File diff suppressed because it is too large Load Diff

13
release/doc/en_US.ISO_8859-1/hardware/common/artheader.sgml Normal file
View File

@ -0,0 +1,13 @@
<!-- $FreeBSD$ -->
<articleinfo>
<title>&os; &release.current; &arch; Hardware Notes</title>
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>

776
release/doc/en_US.ISO_8859-1/hardware/common/config.sgml Normal file
View File

@ -0,0 +1,776 @@
<!-- $FreeBSD$ -->
<sect1>
<title>Boot-time Kernel Configuration</title>
<para>This section describes the boot-time configuration of the
&os; kernel.</para>
<note>
<para>How architecture-dependent is this?</para>
</note>
<sect2>
<title>Default Configuration</title>
<para>The following table contains a list of all of the devices
that are present in the <filename>GENERIC</filename> kernel. This
is the essential part of the operating system that is placed in
your root partition during the installation process. A compressed
version of the <filename>GENERIC</filename> kernel is also used on
the installation floppy diskette and DOS boot image.</para>
<para>The table describes the various parameters used by the
driver to communicate with the hardware in your system. There are
four parameters in the table, though not all are used by each and
every device:
<informaltable frame=none>
<tgroup cols=2 align=left>
<colspec colwidth="*">
<colspec colwidth="5*">
<tbody>
<row>
<entry>Port</entry>
<entry>The starting I/O port used by the device, shown in hexadecimal.</entry>
</row>
<row>
<entry>IRQ</entry>
<entry>The interrupt the device uses to alert the driver to an event,
given in decimal.</entry>
</row>
<row>
<entry>DRQ</entry>
<entry>The DMA (direct memory access) channel the device uses to move
data to and from main memory, also given in decimal.</entry>
</row>
<row>
<entry>IOMem</entry>
<entry>The lowest (or starting) memory address used by the device,
also shown in hexadecimal.</entry>
</row>
</tbody>
</tgroup>
</informaltable>
If an entry in the table has `n/a' for a value then it means that
the parameter in question does not apply to that device. A value
of `dyn' means that the correct value should be determined
automatically by the kernel when the system boots and that you
don't need to worry about it.</para>
<para>If an entry is marked with an *, it means that support is
currently not available for it but should be back as soon as
someone converts the driver to work within the new (post-4.0)
framework.</para>
<para>
<informaltable frame=none>
<tgroup cols=6 align=left>
<colspec colwidth="*">
<colspec colwidth="*">
<colspec colwidth="*">
<colspec colwidth="*">
<colspec colwidth="*">
<colspec colwidth="5*">
<thead>
<row>
<entry>Device</entry>
<entry>Port</entry>
<entry>IRQ</entry>
<entry>DRQ</entry>
<entry>IOMem</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>fdc0</entry>
<entry>3f0</entry>
<entry>6</entry>
<entry>2</entry>
<entry>n/a</entry>
<entry>Floppy disk controller</entry>
</row>
<row>
<entry>ata0</entry>
<entry>170</entry>
<entry>14</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATA/ATAPI controller</entry>
</row>
<row>
<entry>ata1</entry>
<entry>170</entry>
<entry>15</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATA/ATAPI controller</entry>
</row>
<row>
<entry>atadisk0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATA disk drives</entry>
</row>
<row>
<entry>atapicd0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATAPI CDROM drives</entry>
</row>
<row>
<entry>atapifd0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATAPI floppy drives</entry>
</row>
<row>
<entry>atapist0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>ATAPI tape drives</entry>
</row>
<row>
<entry>adv0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>AdvanSys Narrow SCSI controllers</entry>
</row>
<row>
<entry>adw0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>AdvanSys Wide SCSI controllers</entry>
</row>
<row>
<entry>amd0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>AMD 53C974 (Tekram DC390(T))</entry>
</row>
<row>
<entry>ncr0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>NCR PCI SCSI controller</entry>
</row>
<row>
<entry>bt0</entry>
<entry>330</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Buslogic SCSI controller</entry>
</row>
<row>
<entry>aha0</entry>
<entry>330</entry>
<entry>dyn</entry>
<entry>5</entry>
<entry>dyn</entry>
<entry>Adaptec 154x/1535 SCSI controller</entry>
</row>
<row>
<entry>ahb0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Adaptec 174x SCSI controller</entry>
</row>
<row>
<entry>ahc0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Adaptec 274x/284x/294x SCSI controller</entry>
</row>
<row>
<entry>aic0</entry>
<entry>340</entry>
<entry>11</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Adaptec 152x/AIC-6360/AIC-6260 SCSI controller</entry>
</row>
<row>
<entry>isp0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>QLogic 10X0, 1240 Ultra SCSI, 1080/1280 Ultra2 SCSI, 12160 Ultra3 SCSI, 2X00 Fibre Channel SCSI controller</entry>
</row>
<row>
<entry>dpt0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>DPT RAID SCSI controllers</entry>
</row>
<row>
<entry>amr0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>AMI MegaRAID controllers</entry>
</row>
<row>
<entry>mlx0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Mylex DAC960 RAID controllers</entry>
</row>
<row>
<entry>twe0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>3ware Escalade RAID controllers</entry>
</row>
<row>
<entry>asr0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>DPT SmartRaid V, VI, and Adaptec SCSI RAID</entry>
</row>
<row>
<entry>mly0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Mylex AcceleRAID/eXtremeRAID</entry>
</row>
<row>
<entry>aac</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>Adaptec FSA family PCI SCSI RAID</entry>
</row>
<row>
<entry>ncv</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>NCR 53C500 based PC-Card SCSI</entry>
</row>
<row>
<entry>nsp</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Workbit Ninja SCSI-3 based PC-Card SCSI</entry>
</row>
<row>
<entry>stg</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>TMC 18C30/50 based ISA/PC-Card SCSI</entry>
</row>
<row>
<entry>wt0</entry>
<entry>300</entry>
<entry>5</entry>
<entry>1</entry>
<entry>dyn</entry>
<entry>Wangtek and Archive QIC-02/QIC-36</entry>
</row>
<row>
<entry>psm0</entry>
<entry>60</entry>
<entry>12</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>PS/2 Mouse</entry>
</row>
<row>
<entry>mcd0</entry>
<entry>300</entry>
<entry>10</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Mitsumi CD-ROM</entry>
</row>
<row>
<entry>matcd0</entry>
<entry>230</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Matsushita/Panasonic CD-ROM</entry>
</row>
<row>
<entry>scd0</entry>
<entry>230</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Sony CD-ROM</entry>
</row>
<row>
<entry>sio0</entry>
<entry>3f8</entry>
<entry>4</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Serial Port 0 (COM1)</entry>
</row>
<row>
<entry>sio1</entry>
<entry>2f8</entry>
<entry>3</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Serial Port 1 (COM2)</entry>
</row>
<row>
<entry>ppc0</entry>
<entry>dyn</entry>
<entry>7</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Printer ports</entry>
</row>
<row>
<entry>dc0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>DEC/Intel 21143 cards and workalikes</entry>
</row>
<row>
<entry>de0</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>DEC DC21x40 PCI based cards (including 21140 100bT cards)</entry>
</row>
<row>
<entry>ed0</entry>
<entry>280</entry>
<entry>10</entry>
<entry>dyn</entry>
<entry>d8000</entry>
<entry>WD & SMC 80xx; Novell NE1000 & NE2000; 3Com 3C503; HP PC Lan+</entry>
</row>
<row>
<entry>ep0</entry>
<entry>300</entry>
<entry>10</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>3Com 3C509, 3C529, 3C556, 3C562D, 3C563D, 3C572, 3C574X, 3C579, 3C589</entry>
</row>
<row>
<entry>ex0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>Intel EtherExpress Pro/10 cards</entry>
</row>
<row>
<entry>fe0</entry>
<entry>300</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Allied-Telesyn AT1700, RE2000 and Fujitsu FMV-180 series cards.</entry>
</row>
<row>
<entry>fxp0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Intel EtherExpress Pro/100B and Intel PRO/100+ Management Adapter</entry>
</row>
<row>
<entry>ie0</entry>
<entry>300</entry>
<entry>10</entry>
<entry>dyn</entry>
<entry>d0000</entry>
<entry>AT&amp;T StarLAN 10 and EN100; 3Com 3C507; NI5210; Intel EtherExpress (8/16,16[TP]) cards</entry>
</row>
<row>
<entry>le0</entry>
<entry>300</entry>
<entry>5</entry>
<entry>dyn</entry>
<entry>d0000</entry>
<entry>Digital Equipment EtherWorks 2 and EtherWorks 3</entry>
</row>
<row>
<entry>lnc0</entry>
<entry>280</entry>
<entry>10</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Lance/PCnet cards (Isolan, Novell NE2100, NE32-VL, some PCnet-PCI cards)</entry>
</row>
<row>
<entry>pcn0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA cards</entry>
</row>
<row>
<entry>rl0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>RealTek 8129/8139 fast ethernet</entry>
</row>
<row>
<entry>sf0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Adaptec AIC-6915 fast ethernet</entry>
</row>
<row>
<entry>sis0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>SiS 900/SiS 7016 fast ethernet</entry>
</row>
<row>
<entry>sn0</entry>
<entry>0x300</entry>
<entry>10</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>SMC 91xx ethernet</entry>
</row>
<row>
<entry>ste0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Sundance ST201 fast ethernet</entry>
</row>
<row>
<entry>tl0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>TI TNET100 'ThunderLAN' cards.</entry>
</row>
<row>
<entry>tx0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>SMC 9432 'Epic' fast ethernet</entry>
</row>
<row>
<entry>wb0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Winbond W89C840F PCI based cards.</entry>
</row>
<row>
<entry>vr0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>VIA VT3043/VT86C100A PCI based cards.</entry>
</row>
<row>
<entry>vx0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>3Com 3c59x ((Fast) Etherlink III)</entry>
</row>
<row>
<entry>xe0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>Xircom CreditCard adapters (16 bit)</entry>
</row>
<row>
<entry>xl0</entry>
<entry>dyn</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>dyn</entry>
<entry>3Com 3c900, 3c905, 3c905B, 3c905C, 3c980, 3cSOHO100 ((Fast) Etherlink XL)</entry>
</row>
<row>
<entry>cs0</entry>
<entry>0x300</entry>
<entry>dyn</entry>
<entry>n/a</entry>
<entry>n/a</entry>
<entry>Crystal Semiconductor CS89x0-based cards.</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
<para>If the hardware in your computer is not set to the same
settings as those shown in the table and the item in conflict is
not marked 'dyn', you will have to either reconfigure your
hardware or use UserConfig to reconfigure the kernel to match the
way your hardware is currently set (see the next section).</para>
<para>If the settings do not match, the kernel may be unable to
locate or reliably access the devices in your system.</para>
</sect2>
<sect2>
<title>Using UserConfig to change FreeBSD kernel settings</title>
<note>
<para>The markup for this section leaves a lot to be desired.</para>
</note>
<para>The FreeBSD kernel on the install floppy contains drivers
for every piece of hardware that could conceivably be used to
install the rest of the system with. Unfortunately, PC hardware
being what it is, some of these devices can be difficult to detect
accurately, and for some, the process of detecting another can
cause irreversible confusion.</para>
<para>To make this process easier, FreeBSD provides UserConfig.
With this tool the user can configure and disable device drivers
before the kernel is loaded, avoiding potential conflicts, and
eliminating the need to reconfigure hardware to suit the default
driver settings.</para>
<para>Once FreeBSD is installed, it will remember the changes made using
UserConfig, so that they only need be made once.</para>
<para>It is important to disable drivers that are not relevant to
a system in order to minimize the possibility of interference,
which can cause problems that are difficult to track down.</para>
<para>UserConfig features a command line interface for users with
serial consoles or a need to type commands, and a full screen
<quote>visual</quote> interface, which provides point-and-shoot
configuration functionality.</para>
<para>Here is a sample UserConfig screen shot in
<quote>visual</quote> mode:</para>
<screen>---Active Drivers---------------------------10 Conflicts------Dev---IRQ--Port--
Storage : (Collapsed)
Network :
NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed0 5 0x280
NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed1 5 0x300
Communications : (Collapsed)
Input : (Collapsed)
Multimedia :
---Inactive Drivers-------------------------------------------Dev--------------
Storage :
Network : (Collapsed)
Communications :
Input :
Multimedia :
---Parameters-for-device-ed0---------------------------------------------------
Port address : 0x280 Memory address : 0xd8000
IRQ number : 5 Memory size : 0x2000
Flags : 0x0000
-------------------------------------------------------------------------------
IO Port address (Hexadecimal, 0x1-0x2000)
[TAB] Change fields [Q] Save device parameters</screen>
<para>The screen is divided into four sections:
<itemizedlist>
<listitem>
<para>Active Drivers. Listed here are the device drivers
that are currently enabled, and their basic
parameters.</para>
</listitem>
<listitem>
<para>Inactive Drivers. These drivers are present, but are
disabled.</para>
</listitem>
<listitem>
<para>Parameter edit field. This area is used for editing
driver parameters.</para>
</listitem>
<listitem>
<para>Help area. Keystroke help is displayed here.</para>
</listitem>
</itemizedlist>
</para>
<para>One of the Active and Inactive lists is always in use, and
the current entry in the list will be shown with a highlight bar.
If there are more entries in a list than can be shown, it will
scroll. The bar can be moved up and down using the cursor keys,
and moved between lists with the TAB key.</para>
<para>Drivers in the Active list may be marked
<literal>CONF</literal>. This indicates that one or more of their
parameters conflicts with another device, and indicates a
potential for problems. The total number of conflicts is
displayed at the top of the screen.</para>
<para>As a general rule, conflicts should be avoided, either by
disabling conflicting devices that are not present in the system,
or by altering their configuration so that they match the
installed hardware.</para>
<para>In the list areas, drivers are grouped by their basic
function. Groups can be <literal>Collapsed</literal> to simplify
the display (this is the default state for all groups). If a
group is collapsed, it will be shown with
<literal>Collapsed</literal> in the list, as above. To Expand a
Collapsed group, position the highlight bar over the group heading
and press Enter. To Collapse it again, repeat the process.</para>
<para>When a device driver in the Active list is highlighted, its
full parameters are displayed in the Parameter edit area. Note
that not all drivers use all possible parameters, and some
hardware supported by drivers may not use all the parameters the
driver supports.</para>
<para>To disable a driver, go to the Active list, Expand the group
it is in, highlight the driver and press Del. The driver will
move to its group in the Inactive list. (If the group is
collapsed or off the screen, you may not see the driver in its new
location.)</para>
<para>To enable a driver, go to the Inactive list, Expand the
group it is in, highlight the driver and press Enter. The
highlight will move to the Active list, and the driver you have
just enabled will be highlighted, ready to be configured.</para>
<para>To configure a driver, go to the Active list, Expand the
group it is in, highlight the driver and press Enter. The cursor
will move to the Parameter edit area, and the device's parameters
may be edited.</para>
<para>While editing parameters, the TAB and cursor keys can be
used to move between fields. Most numeric values (except IRQ) are
entered in hexadecimal, as indicated by the '0x' at the beginning
of the field. The allowable values for a given field are show in
the Key Help area when the field is active.</para>
<para>To finish configuring a driver, press 'Q'.</para>
<para>Note that PCI, Microchannel and EISA devices can be probed
reliably, therefore they are not shown in the table above nor can
their settings be changed using UserConfig.</para>
</sect2>
</sect1>

2104
release/doc/en_US.ISO_8859-1/hardware/common/dev.sgml Normal file
View File

File diff suppressed because it is too large Load Diff

15
release/doc/en_US.ISO_8859-1/hardware/common/hw.ent Normal file
View File

@ -0,0 +1,15 @@
<!-- -*- sgml -*- -->
<!-- $FreeBSD$ -->
<!-- Text constants which probably don't need to be changed.-->
<!-- Files to be included -->
<!ENTITY artheader SYSTEM "../common/artheader.sgml">
<!ENTITY sect.intro SYSTEM "../common/intro.sgml">
<!ENTITY sect.proc.alpha SYSTEM "../alpha/proc-alpha.sgml">
<!ENTITY sect.proc.i386 SYSTEM "../i386/proc-i386.sgml">
<!ENTITY sect.proc.ia64 SYSTEM "../ia64/proc-ia64.sgml">
<!ENTITY sect.dev SYSTEM "../common/dev.sgml">
<!ENTITY sect.config SYSTEM "../common/config.sgml">

17
release/doc/en_US.ISO_8859-1/hardware/common/intro.sgml Normal file
View File

@ -0,0 +1,17 @@
<!-- $FreeBSD$ -->
<sect1>
<title>Introduction</title>
<para>This document contains the hardware compatability notes for
&os; &release.current; on the &arch; hardware platform. 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.</para>
<note>
<para>This document includes information specific to the &arch;
hardware platform. Versions of the hardware compatability notes
for other architectures will differ in some details.</para>
</note>
</sect1>

22
release/doc/en_US.ISO_8859-1/hardware/i386/Makefile Normal file
View File

@ -0,0 +1,22 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= proc-i386.sgml
SRCS+= ../common/hw.ent
SRCS+= ../common/artheader.sgml
SRCS+= ../common/dev.sgml
SRCS+= ../common/config.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

26
release/doc/en_US.ISO_8859-1/hardware/i386/article.sgml Normal file
View File

@ -0,0 +1,26 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/hw.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "i386">
]>
<article>
&artheader;
&sect.intro;
&sect.proc.i386;
&sect.dev;
&sect.config;
</article>

11
release/doc/en_US.ISO_8859-1/hardware/i386/proc-i386.sgml Normal file
View File

@ -0,0 +1,11 @@
<!--
$FreeBSD$
-->
<sect1>
<title>Supported Processors and Motherboards</title>
<para>&os; for the i386 currently runs on a wide variety of ISA,
VLB, EISA, MCA and PCI bus based PC's, ranging from 386sx to
Pentium 4 class machines (though the 386sx is not
recommended).</para>
</sect1>

7
release/doc/en_US.ISO_8859-1/installation/Makefile Normal file
View File

@ -0,0 +1,7 @@
# $FreeBSD$
SUBDIR = alpha
SUBDIR+= i386
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

23
release/doc/en_US.ISO_8859-1/installation/alpha/Makefile Normal file
View File

@ -0,0 +1,23 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= ../common/artheader.sgml
SRCS+= ../common/install.sgml
SRCS+= ../common/floppies.sgml
SRCS+= ../common/layout.sgml
SRCS+= ../common/trouble.sgml
SRCS+= ../common/upgrade.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

27
release/doc/en_US.ISO_8859-1/installation/alpha/article.sgml Normal file
View File

@ -0,0 +1,27 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/install.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "alpha">
]>
<article>
&artheader;
&sect.install;
&sect.layout;
&sect.floppies;
&sect.upgrade;
&sect.trouble;
</article>

15
release/doc/en_US.ISO_8859-1/installation/common/artheader.sgml Normal file
View File

@ -0,0 +1,15 @@
<!-- $FreeBSD$ -->
<articleinfo>
<title>&os; &release.current; &arch; Installation Instructions</title>
<corpauthor>
The &os; Project
</corpauthor>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>

83
release/doc/en_US.ISO_8859-1/installation/common/floppies.sgml Normal file
View File

@ -0,0 +1,83 @@
<!-- $FreeBSD$ -->
<sect1 id="floppies">
<title>Floppy Disk Image Instructions</title>
<para>For a normal CDROM or network installation, all you need to
copy onto actual floppies from the <filename>floppies/</filename> directory are the
<filename>kern.flp</filename> and <filename>mfsroot.flp</filename>
images (for 1.44MB floppies).</para>
<para>Getting these images over the network is easy. simply fetch
the
<replaceable>release</replaceable><filename>/floppies/kern.flp</filename>
and
<replaceable>release</replaceable><filename>/floppies/mfsroot.flp</filename>
files from <ulink
url="ftp://ftp.freebsd.org/pub/FreeBSD">ftp://ftp.freebsd.org/pub/FreeBSD</ulink>
or one of the many mirrors listed at <ulink
url="http://www.freebsd.org/handbook/mirrors.html">http://www.freebsd.org/handbook/mirrors.html</ulink>.
</para>
<para>Get two blank, freshly formatted floppies and image copy
<filename>kern.flp</filename> onto one and <filename>mfsroot.flp</filename> onto the other. These images are
<emphasis>not</emphasis> DOS files! You cannot simply copy them to a DOS or UFS floppy
as regular files, you need to <quote>image</quote> copy them to the floppy with
<filename>fdimage.exe</filename> under DOS (see the
<filename>tools</filename> directory on your CDROM or &os; FTP
mirror) or the &man.dd.1; command in UNIX.</para>
<para>For example, to create the kernel floppy image from DOS, you'd
do something like this:</para>
<screen><userinput>C> fdimage kern.flp a:</userinput></screen>
<para>Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>kern.flp</filename> into a directory
somewhere. You would do the same for <filename>mfsroot.flp</filename>, of course.</para>
<para>If you're creating the boot floppy from a UNIX machine, you
may find that:</para>
<screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/rfd0</userinput></screen>
<para>or</para>
<screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/floppy</userinput></screen>
<para>work well, depending on your hardware and operating system
environment (different versions of UNIX have totally different names
for the floppy drive).</para>
<para arch="alpha">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 older (but now twice as large) <filename>boot.flp</filename> image which we also
provide. That contains the contents of <filename>kern.flp</filename> and <filename>mfsroot.flp</filename> on
a single floppy, essentially. This file should also be used as the
boot file for those mastering <quote>El Torito</quote> bootable CD images. See
the &man.mkisofs.8; command for more information.</para>
<para>Going to two installation boot floppies is a step we
definitely would have rather avoided but we simply no longer could
due to general code bloat and &os;'s many new device drivers in
<filename>GENERIC</filename>.</para>
<para>One positive side-effect of this new organizational scheme,
however, is that it also allows one to easily make one's own
<filename>kern.flp</filename> or <filename>mfsroot.flp</filename> floppies
should a need to customize some aspect of the installation process
or use a custom kernel for an otherwise unsupported piece of
hardware arise. As long as the kernel is compiled with
<literal>options MFS</literal> and <literal>options
MFS_ROOT</literal>, it will properly look for and boot an
<filename>mfsroot.flp</filename> image in memory when run (see how
<filename>/boot/loader.rc</filename> in
<filename>kern.flp</filename> does its thing). The
<filename>mfsroot.flp</filename> image is also just a gzip'd
filesystem image which is used as root, something which can be made
rather easily using &man.vnconfig.8;. If none of that makes any
sense to you then don't worry about it - just use the
<filename>kern.flp</filename> and <filename>mfsroot.flp</filename>
images as described above.</para>
</sect1>

15
release/doc/en_US.ISO_8859-1/installation/common/install.ent Normal file
View File

@ -0,0 +1,15 @@
<!-- -*- sgml -*- -->
<!-- $FreeBSD$ -->
<!-- Text constants which probably don't need to be changed.-->
<!-- Files to be included -->
<!ENTITY artheader SYSTEM "artheader.sgml">
<!ENTITY sect.install SYSTEM "install.sgml">
<!ENTITY sect.layout SYSTEM "layout.sgml">
<!ENTITY sect.floppies SYSTEM "floppies.sgml">
<!ENTITY sect.upgrade SYSTEM "upgrade.sgml">
<!ENTITY sect.trouble SYSTEM "trouble.sgml">

734
release/doc/en_US.ISO_8859-1/installation/common/install.sgml Normal file
View File

@ -0,0 +1,734 @@
<!--
$FreeBSD$
install.sgml
This file has architecture-dependent installation instructions, culled
from {alpha,i386}/INSTALL.TXT.
-->
<sect1>
<title>Installing &os;</title>
<sect2 id="quickstart">
<title>Quick Start</title>
<para>This manual documents the process of making a new
installation of &os; on your machine. If you are upgrading
from a previous release of &os;, please see <xref
linkend="upgrading">
for important information on upgrading. If you are
not familiar with configuring hardware for &os;, you should
also read the <filename>HARDWARE.TXT</filename> file - it contains important
information which may save you a lot of grief.</para>
<para>If you're new to &os; then you should also read
<emphasis>everything</emphasis> listed in the Documentation menu
of the installer. It may seem like a lot to read, but the time
you spend now reading the documents will be made up many times
over because you were adequately prepared. Also, you will know the
types of information available should you get stuck later. Once
the system is installed, you can also revisit this menu and use a
Web browser to read the installed FAQ (Frequently Asked Questions)
and Handbook HTML documentation sets for &os;. Note that on-line
versions of the <ulink
url="http://www.freebsd.org/faq/">FAQ</ulink> and <ulink
url="http://www.freebsd.org/handbook/">Handbook</ulink> are also
available from the <ulink
url="http://www.freebsd.org/">FreeBSD Project Web
site</ulink>, if you have an Internet connection. See
<filename>README.TXT</filename> for more information on the
resources available to you.</para>
<para>The best laid plans sometimes go awry, so if you run into
trouble take a look at <xref linkend="trouble">, which contains
valuable troubleshooting information. You should also read
<filename>ERRATA.TXT</filename> before installing and follow the
pointers there carefully since this will stop you from falling
over any problems which have reported in the interim for your
particular release.</para>
<important>
<para>While &os; does its best to safeguard against
accidental loss of data, it's still more than possible to
<emphasis>wipe out your entire disk</emphasis>
with this installation if you make a
mistake! Please do not proceed to the final &os;
installation menu unless you've adequately backed up any
important data first! We really mean it!</para>
</important>
<para arch="i386">&os; for the &arch; 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 &os;.</para>
<para arch="alpha">&os; for the &arch; supports the alpha platforms
described in <filename>HARDWARE.TXT</filename>.</para>
<para arch="alpha">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.</para>
<para arch="alpha">Your root filesystem MUST be the first
partition (partition <literal>a</literal>) on the disk to be
bootable.</para>
<para arch="alpha">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.</para>
<sect3>
<title>Installing &os; from CDROM or the Internet</title>
<para arch="i386">The easiest type of installation is from
CDROM. If you have a supported CDROM drive and a &os;
installation CDROM, there are 2 ways of starting the
installation from it:
<itemizedlist>
<listitem>
<para>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, &os; supports the
<quote>El Torrito</quote> bootable CD standard. Simply
put the installation CD in your CDROM drive and boot the
system to begin installation.</para>
</listitem>
<listitem>
<para>Build a set of &os; boot floppies from the
<filename>floppies/</filename> directory in every &os;
distribution. Either simply use the
<filename>makeflp.bat</filename> script from DOS or read
<xref linkend="floppies"> 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 &os; installation.</para>
</listitem>
</itemizedlist>
</para>
<para arch="alpha">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):
<screen>&gt;&gt;&gt;<userinput>boot dka0</userinput></screen>
</para>
<para arch="alpha">Alternatively you can boot the installation
from floppy disk. You should start the installation by building
a set of FreeBSD boot floppy from the files
<filename>floppies/kern.flp</filename> and
<filename>floppies/mfsroot.flp</filename> using the instructions
found in <xref linkend="floppies">. From the SRM console prompt
(<literal>&gt;&gt;&gt;</literal>), just insert the
<filename>kern.flp</filename> floppy and type the following
command to start the installation:
<screen>&gt;&gt;&gt;<userinput>boot dva0</userinput></screen>
</para>
<para arch="alpha">Insert the <filename>mfsroot.flp</filename>
floppy when prompted and you will end up at the first screen of
the install program.</para>
<para>If you don't have a CDROM and would like to simply install
over the net using PPP, SLIP or a dedicated connection, see
<xref linkend="floppies"> for instructions on
making boot floppies. Then please go to
<xref linkend="ftpnfs"> for additional tips on installing
via FTP or NFS.</para>
</sect3>
</sect2>
<sect2>
<title>Detail on various installation types</title>
<para>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 &os;
installation before, you are also encouraged to read some of the
documentation in the the Documentation submenu as well as the
general <quote>Usage</quote> instructions on the first menu.</para>
<note>
<para>If you get stuck at a screen, hit the <keycap>F1</keycap> key for online
documentation relevant to that specific section.</para>
</note>
<para>If you've never installed &os; before, or even if you
have, the <quote>Standard</quote> 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 &os; installation process and know <emphasis>exactly</emphasis> what you
want to do, use the <quote>Express</quote> or <quote>Custom</quote> installation options. If
you're upgrading an existing system, use the <quote>Upgrade</quote> option.</para>
<para>The &os; 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.</para>
<para arch="alpha">Once the install procedure has finished, you will be able
to start &os;/&arch; by typing something like this to the SRM
prompt:
<screen>&gt;&gt;&gt;<userinput>boot dkc0</userinput></screen>
</para>
<para arch="alpha">This instructs the firmware to boot the specified disk. To
find the SRM names of disks in your machine, use the <literal>show
device</literal> command:
<screen>&gt;&gt;&gt;<userinput>show device</userinput>
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</screen>
</para>
<para arch="alpha">This example is from a Digital Personal Workstation 433au
and shows three disks attached to the machine. The first is a
CDROM called <devicename>dka0</devicename> and the other two are
disks and are called <devicename>dkc0</devicename> and
<devicename>dkc100</devicename> repectively.</para>
<para arch="alpha">You can specify which kernel file to load and what boot
options to use with the <option>-file</option> and
<option>-flags</option> options, for example:
<screen><prompt>&gt;&gt;&gt;</prompt> <userinput>boot -file kernel.old -flags s</userinput></screen>
</para>
<para arch="alpha">To make &os;/&arch; boot automatically, use these commands:
<screen><prompt>&gt;&gt;&gt;</prompt> <userinput>set boot_osflags a</userinput>
<prompt>&gt;&gt;&gt;</prompt> <userinput>set bootdef_dev dkc0</userinput>
<prompt>&gt;&gt;&gt;</prompt> <userinput>set auto_action BOOT</userinput></screen>
</para>
<sect3>
<title>Installing from a Network CDROM</title>
<para>If you simply wish to install from a local CDROM drive
then see <xref linkend="quickstart">. If you don't have a CDROM
drive on your system and wish to use a &os; distribution CD
in the CDROM drive of another system to which you have network
connectivity, there are also several ways of going about it:</para>
<itemizedlist>
<listitem>
<para>If you would be able to FTP install &os; directly
from the CDROM drive in some &os; machine, it's quite
easy: You simply add the following line to the password file
(using the &man.vipw.8; command):</para>
<screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen>
<para>On the machine on which you are running the install,
go to the Options menu and set Release Name to
<literal>any</literal>. You may then choose a Media type of
<literal>FTP</literal> and type in
<filename>ftp://<replaceable>machine</replaceable></filename>
after picking <quote>URL</quote> in the ftp sites
menu.</para>
<warning>
<para>This may allow anyone on the local network (or Internet) to
make <quote>anonymous FTP</quote> connections to this
machine, which may not be desirable.</para>
</warning>
</listitem>
<listitem>
<para>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
<filename>/etc/exports</filename> file (on the machine with
the CDROM drive). The example below allows the machine
<hostid role="hostname">ziggy.foo.com</hostid> to mount the
CDROM directly via NFS during installation:</para>
<screen>/cdrom -ro ziggy.foo.com</screen>
<para>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 &man.rc.conf.5; and configure things
appropriately. Assuming that this part goes smoothly, you
should be able to enter: <filename><replaceable>cdrom-host</replaceable>:/cdrom</filename> as the path for
an NFS installation when the target machine is installed,
e.g. <filename>wiggy:/cdrom</filename>.</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Installing from Floppies</title>
<para>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.</para>
<para>First, make your boot floppies as described in
<xref linkend="floppies">.</para>
<para>Second, peruse <xref linkend="layout"> and pay special attention
to the <quote>Distribution Format</quote> section since it describes which
files you're going to need to put onto floppy and which you can
safely skip.</para>
<para>Next you will need, at minimum, as many 1.44MB floppies as
it takes to hold all files in the <filename>bin</filename>
(binary distribution) directory. If you're preparing these
floppies under DOS, then these floppies
<emphasis>must</emphasis> be formatted using the MS-DOS
<filename>FORMAT</filename> command. If you're using Windows,
use the Windows File Manager format command.</para>
<important>
<para>Don't trust <quote>factory preformatted</quote>
floppies! Format them again yourself, just to make sure.
Many problems reported by users in the past have resulted
from the use of improperly formatted media.</para>
</important>
<para>If you're creating the floppies from another &os;
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
&man.disklabel.8; and &man.newfs.8; commands to put a UFS filesystem on a
floppy, as the following sequence of commands illustrates:
<screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
&prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput>
&prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
</para>
<para>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.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para>
<important>
<para>The <filename>bin.inf</filename> file also needs to go on the first floppy of
the <filename>bin</filename> 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
<filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first
floppy of each distribution set! This is also covered in
<filename>README.TXT</filename>.</para>
</important>
<para>Once you come to the Media screen of the install, select
<quote>Floppy</quote> and you'll be prompted for the rest.</para>
</sect3>
<sect3 arch="i386">
<title>Installing from a DOS partition</title>
<para>To prepare for installation from an MS-DOS partition you
should simply copy the files from the distribution into a
directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>C:</devicename>). For example, to do a minimal installation of &os; from
DOS using files copied from the CDROM, you might do something
like this:</para>
<screen><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput>
<prompt>C:\></prompt <userinput>XCOPY /S E:\BIN C:\FREEBSD\BIN</userinput></screen>
<para>Assuming that <devicename>E:</devicename> was where your CD was mounted.</para>
<para>For as many distributions as you wish to install from DOS (and
you have free space for), install each one in a directory under
<filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para>
<para>Once you've copied the directories, you can simply launch
the installation from floppies as normal and select <quote>DOS</quote> as
your media type when the time comes.</para>
</sect3>
<sect3>
<title>Installing from QIC/SCSI Tape</title>
<para>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 &man.tar.1; to get them onto the tape with a command something like
this:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput>
&prompt.root; <userinput>tar cvf /dev/rsa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen>
<para>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 <emphasis>full</emphasis>
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.</para>
<note>
<para>When going to do the installation, the tape must be in
the drive <emphasis>before</emphasis> booting from the boot floppies. The
installation <quote>probe</quote> may otherwise fail to find it.</para>
</note>
<para>Now create a boot floppy as described in <xref linkend="quickstart"> and
proceed with the installation.</para>
</sect3>
<sect3 id="ftpnfs">
<title>Installing over a Network using FTP or NFS</title>
<para>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.</para>
<sect4>
<title>Serial Port</title>
<para>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.</para>
<para>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.</para>
<para>You will also need to know how to use the various <quote>AT
commands</quote> for dialing out with your particular brand of modem
as the PPP dialer provides only a very simple terminal
emulator.</para>
</sect4>
<sect4>
<title>Parallel Port</title>
<para>If a hard-wired connection to another &os; or Linux
machine is available, you might also consider installing over
a <quote>laplink</quote> 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
<quote>real</quote> 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. <hostid
role="ipaddr">10.0.0.1</hostid>, <hostid role="ipaddr">10.0.0.2</hostid>,
etc).</para>
<important>
<para>If you use a Linux machine rather than a &os;
machine as your PLIP peer, you will also have to specify
<option>link0</option> in the TCP/IP setup screen's <quote>extra options for
ifconfig</quote> field in order to be compatible with Linux's
slightly different PLIP protocol.</para>
</important>
</sect4>
<sect4>
<title>Ethernet</title>
<para>&os; supports most common PC Ethernet cards, a table
of supported cards (and their required settings) being
provided as part of the &os; Hardware Guide (see 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 <emphasis>before</emphasis> the laptop is powered on! &os; does
not, unfortunately, currently support <quote>hot insertion</quote> of
PCMCIA cards during installation.</para>
<para>You will also need to know your IP address on the
network, the <option>netmask</option> 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.</para>
<para>If you do not know the answers to these questions then
you should really probably talk to your system administrator
<emphasis>first</emphasis> before trying this type of
installation! Using a randomly chosen IP address or netmask
on a live network will almost certainly get you shot at
dawn.</para>
<para>Once you have a network connection of some sort working, the
installation can continue over NFS or FTP.</para>
</sect4>
<sect4>
<title>NFS installation tips</title>
<para>NFS installation is fairly straight-forward: Simply copy
the &os; distribution files you want onto a server
somewhere and then point the NFS media selection at it.</para>
<para>If this server supports only <quote>privileged port</quote> 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.</para>
<para>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.</para>
<para>In order for NFS installation to work, the server must
also support <quote>subdir mounts</quote>, e.g. if your &os;
distribution directory lives on
<filename>wiggy:/usr/archive/stuff/FreeBSD</filename>, then
<hostid role="hostname">wiggy</hostid> will have to allow
the direct mounting of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
<filename>/usr</filename> or <filename>/usr/archive/stuff</filename>.</para>
<para>In FreeBSD's <filename>/etc/exports</filename> file this is controlled by the
<option>-alldirs</option> option. Other NFS servers may have different
conventions. If you are getting <literal>Permission Denied</literal> messages
from the server then it's likely that you don't have this
properly enabled!</para>
</sect4>
<sect4>
<title>FTP Installation tips</title>
<para>FTP installation may be done from any mirror site containing a
reasonably up-to-date version of &os;. A full menu of
reasonable choices for almost any location in the world is
provided in the FTP site menu during installation.</para>
<para>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 <quote>URL</quote> 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:</para>
<screen>ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE</screen>
<para>There are three FTP installation modes you can use:
<itemizedlist>
<listitem>
<para>FTP: This method uses the standard
<quote>Active</quote> 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!</para>
</listitem>
<listitem>
<para>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.</para>
</listitem>
<listitem>
<para>FTP via an HTTP proxy: This option instructs &os;
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.</para>
<para>In the rare case that you have an FTP proxy that
does not go through HTTP, you can specify the URL as
something like:</para>
<screen><userinput>ftp://foo.bar.com:<replaceable>port</replaceable>/pub/FreeBSD</userinput></screen>
<para>In the URL above, <replaceable>port</replaceable>
is the port number of the proxy FTP server.</para>
</listitem>
</itemizedlist>
</sect4>
</sect3>
<sect3>
<title>Tips for Serial Console Users</title>
<para>If you'd like to install &os; 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:</para>
<procedure>
<step>
<para>Connect some sort of ANSI (vt100) compatible terminal
or terminal emulation program to the <devicename>COM1</devicename> port of the PC you
are installing &os; onto.</para>
</step>
<step>
<para>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.</para>
</step>
<step>
<para>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 <xref
linkend="hitspace"> as soon as you
hear the beep.</para>
</step>
<step>
<para>For a floppy boot, the first beep means to remove the
<filename>kern.flp</filename> floppy and insert the
<filename>mfsroot.flp</filename> floppy, after
which you should press <keycap>Enter</keycap> and wait for another beep.</para>
</step>
<step id="hitspace">
<para>Hit the space bar, then enter</para>
<screen><userinput>boot -h</userinput></screen>
<para>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.</para>
</step>
</procedure>
</sect3>
</sect2>
<sect2 arch="i386">
<title>DOS User's Question and Answer Section</title>
<qandaset>
<qandaentry>
<question>
<para>Help! I have no space! Do I need to delete
everything first?</para>
</question>
<answer>
<para>If your machine is already running DOS and has little
or no free space available for &os;'s installation, all is
not lost! You may find the <application>FIPS</application>
utility, provided in the <filename>tools/</filename>
subdirectory on the &os; CDROM or on the various &os; ftp
sites, to be quite useful.</para>
<para><application>FIPS</application> 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 <quote>defrag</quote> your DOS
partition, using the DOS 6.xx <filename>DEFRAG</filename>
utility or the <application>Norton Disk Tools</application>,
then run FIPS. It will
prompt you for the rest of the information it needs.
Afterwards, you can reboot and install &os; on the new
partition. Also note that FIPS will create the second
partition as a <quote>clone</quote> 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! :)</para>
<para><application>FIPS</application> does NOT currently
work with FAT32 or VFAT style partitions as used by newer
versions of Windows 95. To split up such a partition, you
will need a commercial product such as
<application>Partition Magic</application>. 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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Can I use compressed DOS filesystems from
&os;?</para>
</question>
<answer>
<para>No. If you are using a utility such as
<application>Stacker</application>(tm) or
<application>DoubleSpace</application>(tm), &os; 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!). <emphasis>Do
not remove that file</emphasis> as you will probably regret
it greatly!</para>
<para>It is probably better to create another uncompressed DOS
extended partition and use this for communications between
DOS and &os; if such is your desire.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Can I mount my DOS extended partitions?</para>
</question>
<answer>
<para>Yes. DOS extended partitions are mapped in at the end
of the other <quote>slices</quote> in &os;, e.g. your <devicename>D:</devicename> drive might
be <filename>/dev/da0s5</filename>, your <devicename>E:</devicename> drive <filename>/dev/da0s6</filename>, and so on. This
example assumes, of course, that your extended partition is
on SCSI drive 0. For IDE drives, substitute <literal>ad</literal> for
<literal>da</literal> appropriately. You otherwise mount extended
partitions exactly like you would mount any other DOS drive,
e.g.:</para>
<screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Can I run DOS binaries under &os;?</para>
</question>
<answer>
<para>Ongoing work with BSDI's &man.doscmd.1; 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.emulation
and indicate that you're interested in joining this ongoing
effort!</para>
<para>There is also a neat utility called <filename>pcemu</filename> in the
&os; 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.</para>
</answer>
</qandaentry>
</qandaset>
</sect2>
</sect1>

133
release/doc/en_US.ISO_8859-1/installation/common/layout.sgml Normal file
View File

@ -0,0 +1,133 @@
<!--
$FreeBSD$
This section contains the contents of the old LAYOUT.TXT file.
-->
<sect1 id="layout">
<title>Distribution Format</title>
<para>A typical &os; distribution directory looks something like this:</para>
<screen>
ABOUT.TXT bin compat3x games proflibs
HARDWARE.TXT compat1x info src tools
INSTALL.TXT compat20 dict manpages packages
README.TXT compat21 crypto doc
RELNOTES.TXT compat22 floppies ports
XF86336</screen>
<para>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
<xref linkend="floppies"> 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 &os; before,
you also want to read the entirety of this document (the
installation instructions) file.</para>
<para>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 each item in more detail:
<orderedlist>
<listitem>
<para>The <filename>*.TXT</filename> files obviously contain
documentation (this file is <filename>INSTALL.TXT</filename>) and should be read
before starting an installation.</para>
</listitem>
<listitem>
<para>The <filename>XF86336</filename> directory contains the
XFree86 project's 3.3.6 release and consists of a series of
gzip'd tar files which contain each component of the XFree86
distribution.</para>
</listitem>
<listitem>
<para>The <filename>bin</filename>, <filename>dict</filename>, <filename>crypto</filename>, <filename>doc</filename>, <filename>games</filename>, <filename>info</filename>, <filename>manpages</filename>,
<filename>proflibs</filename>, and <filename>src</filename> directories contain the primary distribution
components of &os; itself and are split into smaller files
for easy packing onto floppies (should that be
necessary).</para>
</listitem>
<listitem>
<para>The <filename>compat1x</filename>, <filename>compat20</filename>, <filename>compat21</filename>, <filename>compat22</filename>, and <filename>compat3x</filename>
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
<filename>install.sh</filename> scripts.</para>
</listitem>
<listitem>
<para>The <filename>floppies/</filename> subdirectory contains the floppy
installation images; further information on using them can be
found in <xref linkend="floppies">.</para>
</listitem>
<listitem>
<para>The <filename>packages</filename> and <filename>ports</filename> directories contain the &os;
packages and ports collections. Packages may be installed from
the packages directory by running the command:</para>
<screen>&prompt.root;<userinput>/stand/sysinstall configPackages</userinput></screen>
<para>Packages can also be installed by feeding individual
filenames in <filename>packages</filename>/ to the &man.pkg.add.1; command.</para>
<para>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
<ulink url="http://www.freebsd.org/ports/">http://www.freebsd.org/ports/</ulink> or locally from
<filename>/usr/share/doc/handbook</filename> if you've installed the <filename>doc</filename>
distribution.</para>
</listitem>
<listitem>
<para>Last of all, the <filename>tools</filename> 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.</para>
</listitem>
</orderedlist>
</para>
<para>A typical distribution (we'll use the <filename>info</filename> distribution as an
example) looks like this internally:</para>
<screen>CHECKSUM.MD5 info.ab info.ad info.inf install.sh
info.aa info.ac info.ae info.mtree</screen>
<para>The <filename>CHECKSUM.MD5</filename> 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 <filename>info.a*</filename> files
are split, gzip'd tar files, the contents of which can be viewed by
doing:</para>
<screen>&prompt.root; <userinput>cat info.a* | tar tvzf -</userinput></screen>
<para>During installation, they are automatically concatenated and
extracted by the installation procedure.</para>
<para>The <filename>info.inf</filename> 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 <filename>.inf</filename> file <emphasis>must</emphasis> occupy the first
floppy of each distribution set!</para>
<para>The <filename>info.mtree</filename> file is another non-essential file which is
provided for user reference. It contains the MD5 signatures of the
<emphasis>unpacked</emphasis> distribution files and can be later
used with the &man.mtree.8; program to verify the installation
permissions and checksums against any possible modifications to the
file. When used with the <filename>bin</filename> distribution,
this can be an excellent way of detecting trojan horse attacks on
your system.</para>
<para>Finally, the <filename>install.sh</filename> 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:</para>
<screen>&prompt.root; <userinput>cd /cdrom/info</userinput>
&prompt.root; <userinput>sh install.sh</userinput></screen>
<para>And that's all there is to it! Each distribution contains its
own <filename>install.sh</filename> file for this.</para>
</sect1>

529
release/doc/en_US.ISO_8859-1/installation/common/trouble.sgml Normal file
View File

@ -0,0 +1,529 @@
<!--
$FreeBSD$
This file contains the comments of the old TROUBLE.TXT file.
-->
<sect1 id="trouble">
<title>Troubleshooting</title>
<sect2 id="repairing">
<title>Repairing an Existing &os; Installation</title>
<para>&os; releases 2.2.1 and later feature a
<quote>Fixit</quote> option in the top menu of the boot floppy.
To use it, you will also need either a
<filename>fixit.flp</filename> image floppy, generated in the same
fashion as the boot floppy, or the 2nd CDROM from Walnut Creek
CDROM's &os; distribution.</para>
<para>To invoke fixit, simply boot the
<filename>kern.flp</filename> floppy, choose the
<quote>Fixit</quote> 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 <filename>/stand</filename>
and <filename>/mnt2/stand</filename> directories) for checking,
repairing and examining file systems and their contents. Some
UNIX administration experience <emphasis>is</emphasis> required to
use the fixit option!</para>
</sect2>
<sect2>
<title>Common Installation Problems, Q&amp;A</title>
<qandaset>
<qandaentry>
<question>
<para>I go to boot from the hard disk for the first time
after installing &os;, the kernel loads and probes my
hardware, but stops with messages like:</para>
<screen>changing root device to wd1s1a panic: cannot mount root</screen>
<para>What is wrong? What can I do?</para>
<para>What is this
<literal>bios_drive:interface(unit,partition)kernel_name</literal>
thing that is displayed with the boot help?</para>
</question>
<answer>
<para>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 &os;, and working
out which numbers correspond to which is difficult to get
right.</para>
<para>In the case where the boot disk is not the first disk
in the system, &os; can need some help finding it. There
are two common situations here, and in both of these cases,
you need to tell &os; where the root filesystem is. You
do this by specifying the BIOS disk number, the disk type
and the &os; disk number for that type.</para>
<para>The first situation is where you have two IDE disks,
each configured as the master on their respective IDE
busses, and wish to boot &os; from the second disk. The
BIOS sees these as disk 0 and disk 1, while &os; sees
them as <devicename>wd0</devicename> and
<devicename>wd2</devicename>.</para>
<para>&os; is on BIOS disk 1, of type
<literal>wd</literal> and the &os; disk number is 2, so
you would say:</para>
<screen><userinput>1:wd(2,a)kernel</userinput></screen>
<para>Note that if you have a slave on the primary bus, the
above is not necessary (and is effectively wrong).</para>
<para>The second situation involves booting from a SCSI disk
when you have one or more IDE disks in the system. In this
case, the &os; 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 <literal>da</literal> and
&os; disk number 0, so you would say:</para>
<screen><userinput>2:da(0,a)kernel</userinput></screen>
<para>To tell &os; 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.</para>
<para>Once you have determined the correct values to use,
you can put the command exactly as you would have typed it
in the <filename>/boot.config</filename> file using a
standard text editor. Unless instructed otherwise, &os;
will use the contents of this file as the default response
to the <literal>boot:</literal> prompt.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I go to boot from the hard disk for the first time
after installing &os;, but the Boot Manager prompt just
prints <literal>F?</literal> at the boot menu each time but
the boot won't go any further.</para>
</question>
<answer>
<para>The hard disk geometry was set incorrectly in the
Partition editor when you installed &os;. Go back into
the partition editor and specify the actual geometry of your
hard disk. You must reinstall &os; again from the
beginning with the correct geometry.</para>
<para>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
&os; after that. The install program will see the DOS
partition and try to infer the correct geometry from it,
which usually works.</para>
<para>The following tip is no longer recommended, but is left here
for reference:</para>
<blockquote>
<para>If you are setting up a truly dedicated &os;
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 &os; 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 &os; on a
disk.</para>
</blockquote>
</answer>
</qandaentry>
</qandaset>
</sect2>
<sect2>
<title>Known Hardware Problems, Q&amp;A</title>
<note>
<para>Please send hardware tips for this section to &a.jkh;.</para>
</note>
<qandaset>
<qandaentry>
<question>
<para>The &man.mcd.4; driver keeps thinking that it has
found a device and this stops my Intel EtherExpress card
from working.</para>
</question>
<answer>
<para>Use the UserConfig utility (see
<filename>HARDWARE.TXT</filename>) and disable the probing
of the <devicename>mcd0</devicename> and
<devicename>mcd1</devicename> devices. Generally speaking,
you should only leave the devices that you will be using
enabled in your kernel.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>&os; claims to support the 3Com PCMCIA card, but my
card isn't recognized when it's plugged into my
laptop.</para>
</question>
<answer>
<para>There are a couple of possible problems. First of
all, &os; does not support multi-function cards, so if
you have a combo Ethernet/modem card (such as the 3C562), it
won't work. The default driver for the 3C589 card was
written just like all of the other drivers in &os;, and
depend on the card's own configuration data stored in NVRAM
to work. You must correctly configure &os;'s driver to
match the IRQ, port, and IOMEM stored in NVRAM.</para>
<para>Unfortunately, the only program capable of reading
them is the 3COM supplied DOS program. This program must be
run on a absolutely clean system (no other drivers must be
running), and the program will whine about CARD-Services not
being found, but it will continue. This is necessary to
read the NVRAM values. You want to know the IRQ, port, and
IOMEM values (the latter is called the CIS tuple by 3COM).
The first two can be set in the program, the third is
un-settable, and can only be read. Once you have these
values, set them in UserConfig and your card will be
recognized.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>&os; finds my PCMCIA network card, but no packets
appear to be sent even though it claims to be working.</para>
</question>
<answer>
<para>Many PCMCIA cards have the ability to use either the
10-Base2 (BNC) or 10-BaseT connectors for connecting to the
network. The driver is unable to <quote>auto-select</quote>
the correct connector, so you must tell it which connector
to use. In order to switch between the two connectors, the
link flags must be set. Depending on the model of the card,
<option>-link0 link1</option> or <option>-link0
-link1</option> will choose the correct network connector.
You can set these in &man.sysinstall.8; by using the
<literal>Extra options to ifconfig:</literal> field in the
network setup screen.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>The system finds my &man.ed.4; network card, but I
keep getting device timeout errors.</para>
</question>
<answer>
<para>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 <literal>?</literal> in the IRQ field of your
kernel config file.</para>
<para>Either move the jumper on the card to a hard
configuration setting (altering the kernel settings if
necessary), or specify the IRQ as <literal>-1</literal> in UserConfig or <literal>?</literal>
in your kernel config file. This will tell the kernel to
use the soft configuration.</para>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I have a Matsushita/Panasonic drive but it isn't
recognized by the system.</para>
</question>
<answer>
<para>Make certain that the I/O port that the &man.matcd.4; driver
is set to is correct for the host interface card you have.
(Some SoundBlaster DOS drivers report a hardware I/O port
address for the CD-ROM interface that is 0x10 lower than it
really is.)</para>
<para>If you are unable to determine the settings for the
card by examining the board or documentation, you can use
UserConfig to change the 'port' address (I/O port) to -1 and
start the system. This setting causes the driver to look at
a number of I/O ports that various manufacturers use for
their Matsushita/Panasonic/Creative CD-ROM interfaces. Once
the driver locates the address, you should run UserConfig
again and specify the correct address. Leaving the 'port'
parameter set to -1 increases the amount of time that it
takes the system to boot, and this could interfere with
other devices.</para>
<para>The double-speed Matsushita CR-562 and CR-563 are the
only drives that are supported.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I booted the install floppy on my IBM ThinkPad (tm)
laptop, and the keyboard is all messed up.</para>
</question>
<answer>
<para>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'.)</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I try to boot the install floppy, I see the
following message and nothing seems to be happening. I
cannot enter anything from the keyboard either.</para>
<screen>Keyboard: no</screen>
</question>
<answer>
<para>Due to lack of space, full support for old XT/AT
(84-key) keyboards is no longer available in the bootblocks.
Some notebook computers may also have this type of keyboard.
If you are still using this kind of hardware, you will see
the above message appears when you boot from the CD-ROM or
an install floppy.</para>
<para>As soon as you see this message, hit the space bar,
and you will see the prompt:</para>
<screen>>> FreeBSD/i386 BOOT
Default: x:xx(x,x)/boot/loader
boot:</screen>
<para>Then enter <userinput>-Dh</userinput>, and things
should proceed normally.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I have a Matsushita/Panasonic CR-522, a
Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is
not recognized even when the correct I/O port is set.</para>
</question>
<answer>
<para>These CD-ROM drives are currently not supported by
&os;. The command sets for these drives are not compatible
with the double-speed CR-562 and CR-563 drives.</para>
<para>The single-speed CR-522 and CR-523 drives can be
identified by their use of a CD-caddy. </para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I'm trying to install from a tape drive but all I get
is something like this on the screen:</para>
<screen>sa0(aha0:1:0) NOT READY csi 40,0,0,0</screen>
</question>
<answer>
<para>There's a limitation in the current &man.sysinstall.8;
that the tape <emphasis>must</emphasis> be in the drive
while &man.sysinstall.8; is started or it won't be detected.
Try again with the tape in the drive the whole time.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I've installed &os; onto my system, but it hangs
when booting from the hard drive with the message:</para>
<screen>Changing root to /dev/da0a</screen>
</question>
<answer>
<para>his problem may occur in a system with a 3com 3c509
Ethernet adapter. The &man.ep.4; device driver appears to
be sensitive to probes for other devices that also use
address 0x300. Boot your &os; system by power cycling
the machine (turn off and on). At the
<literal>Boot:</literal> prompt specify the
<option>-c</option>. This will invoke UserConfig (see
<xref linkend="repairing"> above).
Use the <literal>disable</literal>
command to disable the device probes for all devices at
address 0x300 except the ep0 driver. On exit, your machine
should successfully boot &os;.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>My system can not find my Intel EtherExpress 16 card.</para>
</question>
<answer>
<para>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
<filename>softset.exe</filename> program.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When installing on an EISA HP Netserver, my on-board
AIC-7xxx SCSI controller isn't detected.</para>
</question>
<answer>
<para>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 <option>-c</option> option into
UserConfig, but <emphasis>don't</emphasis> use the pretty
visual mode but the plain old CLI mode. Type:
<screen><userinput>eisa 12</userinput>
<userinput>quit</userinput></screen>
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.</para>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>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.</para>
</question>
<answer>
<para>Your machine doesn't like the new
<literal>i586_copyout</literal> and
<literal>i586_copyin</literal> 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
(<quote>expert mode</quote>) version and type the following
at it:
<screen><userinput>flags npx0 1</userinput></screen>
Then proceed normally to boot. This will be saved
into your kernel, so you only need to do it once.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I have this CMD640 IDE controller that is said to be
broken.</para>
</question>
<answer>
<para>Yes, it is. &os; does not support this controller
except through the legacy wdc driver.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>On a Compaq Aero notebook, I get the message <quote>No
floppy devices found! Please check ...</quote> when trying to
install from floppy.</para>
</question>
<answer>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I go to boot my Intel AL440LX
(<quote>Atlanta</quote>) -based system from the hard disk the
first time, it stops with a <literal>Read Error</literal>
message.</para>
</question>
<answer>
<para>There appears to be a bug in the BIOS on at least some
of these boards, this bug results in the &os; bootloader
thinking that it is booting from a floppy disk. This is
only a problem if you are not using the BootEasy boot
manager. Slice the disk in <quote>compatible</quote>mode
and install BootEasy during the &os; installation to
avoid the bug, or upgrade the BIOS (see Intel's website for
details).</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When installing on an Dell Poweredge XE, Dell
proprietary RAID controller DSA (Dell SCSI Array) isn't
recognized.</para>
</question>
<answer>
<para>Configure the DSA to use AHA-1540 emulation using EISA
configuration utility. After that &os; 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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>My Ethernet adapter is detected as an AMD PCnet-FAST
(or similar) but it doesn't work. (Eg. onboard Ethernet on
IBM Netfinity 5xxx or 7xxx)</para>
</question>
<answer>
<para>The &man.lnc.4; driver is currently faulty, and will
often not work correctly with the PCnet-FAST and
PCnet-FAST+. You need to install a different Ethernet
adapter.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I have an IBM EtherJet PCI card, it is detected by the
&man.fxp.4; driver correctly, but the lights on the card don't
come on and it doesn't connect to the network.</para>
</question>
<answer>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I configure the network during installation on an
IBM Netfinity 3500, the system freezes.</para>
</question>
<answer>
<para>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.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I install onto a drive managed by a Mylex PCI
RAID controller, the system fails to boot (eg. with a
<literal>read error</literal> message).</para>
</question>
<answer>
<para>There is a bug in the Mylex driver which results in it
ignoring the <quote>8GB</quote> geometry mode setting in the
BIOS. Use the 2GB mode instead.</para>
</answer>
</qandaentry>
</qandaset>
</sect2>
</sect1>

255
release/doc/en_US.ISO_8859-1/installation/common/upgrade.sgml Normal file
View File

@ -0,0 +1,255 @@
<!--
$FreeBSD$
This section contains the contents of the old UPGRADE.TXT
file.
-->
<sect1 id="upgrading">
<title>Upgrading &os;</title>
<para>These instructions describe a procedure for doing a binary
upgrade from an older version of &os;.</para>
<warning>
<para>While the &os; upgrade procedure does its best to
safeguard against accidental loss of data, it is still more than
possible to <emphasis>wipe out your entire disk</emphasis> with
this installation! Please do not accept the final confirmation
request unless you have adequately backed up any important data
files.</para>
</warning>
<important>
<para>These notes assume that you are using the version of
&man.sysinstall.8; supplied with the version of &os; to which you
intend to upgrade. Using a mismatched version of &man.sysinstall.8; 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 &man.sysinstall.8; from
an existing installation to upgrade to a newer version of
&os;. This is <emphasis>not</emphasis> recommended.</para>
<para>Furthermore, if you are upgrading from &os; 2.2.5 or
earlier, see <xref linkend="fstab"> for important details regarding changes
to the <filename>/etc/fstab</filename> file required during the upgrade procedure.</para>
</important>
<sect2>
<title>Introduction</title>
<para>The upgrade procedure replaces distributions selected by the
user with those corresponding to the new &os; release. It
preserves standard system configuration data, as well as user
data, installed packages and other software.</para>
<para>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.</para>
<sect3>
<title>Upgrade Overview</title>
<para>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.</para>
<para>System configuration is preserved by retaining and
restoring the previous version of the following files:</para>
<para><filename>Xaccel.ini</filename>,
<filename>adduser.conf</filename>,
<filename>aliases</filename>,
<filename>aliases.db</filename>,
<filename>amd.map</filename>,
<filename>crontab</filename>,
<filename>csh.cshrc</filename>,
<filename>csh.login</filename>,
<filename>csh.logout</filename>,
<filename>daily</filename>,
<filename>disktab</filename>,
<filename>dm.conf</filename>,
<filename>exports</filename>,
<filename>fbtab</filename>,
<filename>fstab</filename>,
<filename>ftpusers</filename>,
<filename>gettytab</filename>,
<filename>gnats</filename>,
<filename>group</filename>,
<filename>hosts</filename>,
<filename>hosts.equiv</filename>,
<filename>hosts.lpd</filename>,
<filename>inetd.conf</filename>,
<filename>kerberosIV</filename>,
<filename>localtime</filename>,
<filename>login.access</filename>,
<filename>mail.rc</filename>,
<filename>make.conf</filename>,
<filename>manpath.config</filename>,
<filename>master.passwd</filename>,
<filename>mib.txt</filename>,
<filename>modems</filename>,
<filename>monthly</filename>,
<filename>motd</filename>,
<filename>namedb</filename>,
<filename>networks</filename>,
<filename>nsswitch.conf</filename>,
<filename>passwd</filename>,
<filename>phones</filename>,
<filename>ppp</filename>,
<filename>printcap</filename>,
<filename>profile</filename>,
<filename>protocols</filename>,
<filename>pwd.db</filename>,
<filename>rc</filename>,
<filename>rc.firewall</filename>,
<filename>rc.i386</filename>,
<filename>rc.local</filename>,
<filename>rc.network</filename>,
<filename>rc.conf</filename>,
<filename>remote</filename>,
<filename>resolv.conf</filename>,
<filename>rmt</filename>,
<filename>security</filename>,
<filename>sendmail.cf</filename>,
<filename>services</filename>,
<filename>shells</filename>,
<filename>skeykeys</filename>,
<filename>spwd.db</filename>,
<filename>supfile,</filename>
<filename>syslog.conf</filename>,
<filename>termcap</filename>,
<filename>ttys</filename>,
<filename>uucp</filename>,
<filename>weekly</filename></para>
<para>The versions of these files which correspond to the new
version are moved to <filename>/etc/upgrade/</filename>. 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.</para>
<para>During the upgrade procedure, the administrator is
prompted for a location into which all files from
<filename>/etc/</filename> are saved. In the event that local
modifications have been made to other files, they may be
subsequently retrieved from this location.</para>
</sect3>
</sect2>
<sect2>
<title>Procedure</title>
<para>This section details the upgrade procedure. Particular
attention is given to items which substantially differ from a
normal installation.</para>
<sect3>
<title>Backup</title>
<para>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.</para>
</sect3>
<sect3>
<title>Mount Filesystems</title>
<para>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. <emphasis>Do not</emphasis>set the <quote>newfs
flag</quote> for any filesystems, as this will cause data
loss.</para>
</sect3>
<sect3>
<title>Select Distributions</title>
<para>When selecting distributions, there are no constraints
on which must be selected. As a general rule, the <literal>bin</literal>
distribution should be selected for an update, and the <literal>man</literal>
distribution if manpages are already installed. Other
distributions may be selected beyond those originally
installed if the administrator wishes to add additional
functionality.</para>
</sect3>
<sect3 id="fstab">
<title>After Installation</title>
<para>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
<filename>/etc/rc.conf</filename> and
<filename>/etc/fstab</filename> files should be checked.</para>
<para>Read the following, but <emphasis>do not</emphasis> update
<filename>/etc/fstab</filename> as described below until the new
system has booted correctly. The upgrade procedure replaces the
previous &os; kernel with a <filename>GENERIC</filename> kernel,
and a custom kernel may need to be generated to suit the local
system configuration.</para>
<important>
<para>&os; 2.2.6 introduced a change in the naming of the
device from which the root filesystem is mounted. This
change affects all systems, however user intervention is
only required for systems undergoing an upgrade installation
from a version prior to &os; 2.2.6.</para>
<para>Previously, the root filesystem was always mounted from
the compatibility slice, while other partitions on the same
disk were mounted from their true slice. This might, for
example, have resulted in an <filename>/etc/fstab</filename>
file like:</para>
<screen># Device Mountpoint FStype Options Dump Pass#
/dev/wd0s2b none swap sw 0 0
/dev/wd0a / ufs rw 1 1
/dev/wd0s2f /local0 ufs rw 1 1
/dev/wd0s2e /usr ufs rw 1 1</screen>
<para>For &os; 2.2.6 and later, this format changes so that
the device for <filename>/</filename> is consistent with
others. Also, the driver for the ATA-drives has changed from
&man.wd.4; to &man.ad.4;, so the new file could look something
like:</para>
<screen># Device Mountpoint FStype Options Dump Pass#
/dev/ad0s2b none swap sw 0 0
/dev/ad0s2a / ufs rw 1 1
/dev/ad0s2f /local0 ufs rw 1 1
/dev/ad0s2e /usr ufs rw 1 1</screen>
<para>If <filename>/etc/fstab</filename> is not updated
manually in this case, the system will issue a warning message
whenever <filename>/</filename> is mounted (normally at
startup) indicating the change that must be made. In
addition, trouble may be experienced if the root filesystem is
not correctly unmounted, whereby the root filesystem will not
be marked clean at the next reboot.</para>
<para>This change should be made as soon as the upgraded
system has been successfully rebooted.</para>
</important>
</sect3>
</sect2>
<sect2>
<title>Alternative Upgrade Techniques</title>
<para>Those interested in an upgrade method that allows more
flexibility and sophistication should take a look at the
<quote>Upgrading FreeBSD from source</quote> tutorial found at
http://www.freebsd.org/docs.html. This method requires reliable
network connectivity, extra disk space and spare time, but has
advantages for networks and other more complex
installations.</para>
</sect2>
</sect1>

23
release/doc/en_US.ISO_8859-1/installation/i386/Makefile Normal file
View File

@ -0,0 +1,23 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= ../common/artheader.sgml
SRCS+= ../common/install.sgml
SRCS+= ../common/floppies.sgml
SRCS+= ../common/layout.sgml
SRCS+= ../common/trouble.sgml
SRCS+= ../common/upgrade.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

27
release/doc/en_US.ISO_8859-1/installation/i386/article.sgml Normal file
View File

@ -0,0 +1,27 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/install.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "i386">
]>
<article>
&artheader;
&sect.install;
&sect.layout;
&sect.floppies;
&sect.upgrade;
&sect.trouble;
</article>

24
release/doc/en_US.ISO_8859-1/readme/Makefile Normal file
View File

@ -0,0 +1,24 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../share/sgml/catalog
#
# SRCS lists the individual SGML files that make up the document. Changes
# to any of these files will force a rebuild
#
# SGML content
SRCS+= article.sgml
SRCS+= artheader.sgml
SRCS+= intro.sgml
SRCS+= about.sgml
SRCS+= obtaining.sgml
SRCS+= problems.sgml
SRCS+= ack.sgml
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

102
release/doc/en_US.ISO_8859-1/readme/about.sgml Normal file
View File

@ -0,0 +1,102 @@
<!--
$FreeBSD$
about.sgml
General information about FreeBSD. Most contents of this file
come from the old ABOUT.TXT.
-->
<sect1>
<title>About &os;</title>
<para>What is &os;? &os; is an operating system based on 4.4 BSD
Lite for Intel, AMD, Cyrix or NexGen <quote>x86</quote> based PC
hardware and Compaq (formerly DEC) Alpha computers. Versions for
the IA64 and PowerPC architectures are currently under
development as well. &os; works with a
very wide variety of PC peripherals and configurations and can be
used for everything from software development to Internet Service
Provision.</para>
<para>This release of &os; contains everything you need to run
such a system, including full source code for everything. With the
source distribution installed you can literally recompile the entire
system from scratch with one command, making it ideal for students,
researchers or folks who simply want to see how it all works.</para>
<para>A large collection of third party ported software (the
<quote>Ports Collection</quote>) is also provided to make it easier
for you to obtain and install all your favorite traditional UNIX
utilities for &os;. Over 5000 ports, from editors to programming
languages to graphical applications, make &os; a powerful and
comprehensive operating environment that extends far beyond what's
provided by many commercial versions of UNIX.</para>
<para>For more documentation on this system it is recommended that
you purchase The Complete FreeBSD, available from local bookstores
and from The FreeBSD Mall (<ulink
url="http://www.freebsdmall.com">http://www.freebsdmall.com</ulink>),
as well as the 4.4BSD Document Set from O'Reilly Associates and the
USENIX Association, ISBN 1-56592-082-1. We have no connection with
O'Reilly, we're just satisfied customers!</para>
<para>If you're new to &os; then you should also read
<emphasis>everything</emphasis>
listed in the Documentation menu on the boot floppy. It may seem
like a lot to read, but you should at least acquaint yourself with
the types of information available should you later get stuck. Once
the system is installed, you can also revisit this menu and use a
Web browser to read the installed FAQ (Frequently Asked Questions)
and Handbook HTML documentation sets for &os;. Note that on-line
versions of the <ulink
url="http://www.freebsd.org/faq/">FAQ</ulink> and <ulink
url="http://www.freebsd.org/handbook/">Handbook</ulink> are also
available from the <ulink
url="http://www.freebsd.org/">FreeBSD Project Web
site</ulink>, if you have an Internet connection. See
<filename>README.TXT</filename> for more information on the
resources available to you.</para>
<note>
<para>If you read no other documentation before installing a given
version of &os;, you should at least by all means <emphasis>read
the errata</emphasis> for that release so that you don't stumble
over problems which have already been found and fixed. The
<filename>ERRATA.TXT</filename> file accompanying your release (it
should be right next to this file) is obviously already out of
date by definition, but other copies are kept updated on the net
and should be consulted as the <quote>current errata</quote> for
your release (this is also what your
<filename>ERRATA.TXT</filename> file says, by the way). These
other copies of the errata are located at:
<orderedlist>
<listitem>
<para><ulink url="http://www.freebsd.org/releases/">http://www.freebsd.org/releases/</ulink></para>
</listitem>
<listitem>
<para>ftp://ftp.freebsd.org/pub/FreeBSD/releases/your-release/ERRATA.TXT
(and any sites which keep up-to-date mirrors of this
location).</para>
</listitem>
</orderedlist>
</para>
</note>
<warning>
<para>While &os; does its best to safeguard against accidental
loss of data, it's still more than possible to <emphasis>wipe out
your entire disk</emphasis>
with this installation! Please do not proceed to the
final &os; installation menu unless you've adequately backed up
any important data first! We really mean it!</para>
</warning>
</sect1>

29
release/doc/en_US.ISO_8859-1/readme/ack.sgml Normal file
View File

@ -0,0 +1,29 @@
<!--
$FreeBSD$
ack.sgml
This file is the Acknowledgments section of the old RELNOTES.TXT.
-->
<sect1>
<title>Acknowledgments</title>
<para>&os; represents the cumulative work of many hundreds, if not
thousands, of individuals from around the world who have worked very
hard to bring you this release. For a complete list of &os;
project staffers, please see:</para>
<para><ulink url="http://www.freebsd.org/handbook/staff.html">http://www.freebsd.org/handbook/staff.html</ulink></para>
<para>or, if you've loaded the doc distribution:</para>
<para><filename>/usr/share/doc/handbook/staff.html</filename></para>
<para>Special thanks also go to the many thousands of &os; users and
testers all over the world, without whom this release simply would
not have been possible.</para>
</sect1>

13
release/doc/en_US.ISO_8859-1/readme/artheader.sgml Normal file
View File

@ -0,0 +1,13 @@
<!-- $FreeBSD$ -->
<articleinfo>
<title>&os; &release.current; README</title>
<corpauthor>The &os; Project</corpauthor>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>

22
release/doc/en_US.ISO_8859-1/readme/article.sgml Normal file
View File

@ -0,0 +1,22 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "readme.ent"> %sections;
]>
<article>
&artheader;
&sect.intro;
&sect.about;
&sect.obtaining;
&sect.problems;
&sect.ack;
</article>

86
release/doc/en_US.ISO_8859-1/readme/intro.sgml Normal file
View File

@ -0,0 +1,86 @@
<!--
$FreeBSD$
intro.sgml
Introduction to the README file. Most text here comes from the
old README.TXT (the file with Chuck in ASCII art).
-->
<sect1>
<title>Introduction</title>
<para>This is a binary snapshot of &os; &release.current;, the
&release.branch; branch that is currently moving towards
&release.next;.</para>
<para>Feedback or offers to help with anything you see in this
release are most welcome and should be sent to one of the
appropriate mailing lists, as listed in <xref linkend="contacting">.</para>
<sect2>
<title>Target Audience</title>
<para>This release is aimed primarily at early-adopters and the
various other folks who want to get involved with the ongoing
development of &os; and are willing to deal with a few bumps in
the road. We do our best to ensure that each snapshot works as
advertised, but tracking -CURRENT is a process which frequently
has its off days.</para>
<para>If you're both technically proficient and know exactly what
you're getting into here (e.g. you've been following -CURRENT)
then this snapshot is probably for you. If you're more interested
in doing business with &os; than in playing with the cutting
edge of technology, however, then 3.x or 4.x is almost certainly
your best bet.</para>
<para>If you're a developer/hobbiest and not interested in QA'd
releases so much as simply keeping up to date on the latest &os;
technology, you can also install one of our
<quote>snapshot</quote> releases.
</para>
</sect2>
<sect2>
<title>For More Information</title>
<para>A number of other files provide more specific information
about this distribution.
<itemizedlist>
<listitem>
<para><filename>README.TXT</filename>: This file, which
gives some general information about &os; as well as some
cursory notes about installation..</para>
</listitem>
<listitem>
<para><filename>RELNOTES.TXT</filename>: The release notes,
showing what's new and different in &os; &release.current;
compared to &os; &release.prev;.</para>
</listitem>
<listitem>
<para><filename>HARDWARE.TXT</filename>: The hardware
compatability list, showing devices with which &os; has been
tested and is known to work.</para>
</listitem>
<listitem>
<para><filename>ERRATA.TXT</filename>: Release errata.
Late-breaking, post-release information can be found in this
file. Read this file! It will tell you where to look for
the latest information on problems which have been found and
fixed since this release was created (and may bite
you).</para>
</listitem>
</itemizedlist>
</para>
<para>Most information is also available from the
Documentation menu during installation.</para>
</sect2>
</sect1>

102
release/doc/en_US.ISO_8859-1/readme/obtaining.sgml Normal file
View File

@ -0,0 +1,102 @@
<!--
$FreeBSD$
obtaining.sgml
Information on getting a copy of FreeBSD. This text used to
be the "Obtaining FreeBSD" section of RELNOTES.TXT.
-->
<sect1>
<title>Obtaining &os;</title>
<para>You may obtain &os; in a variety of ways. This section
focuses on those ways that are primarily of use for obtaining a
complete &os; distribution, rather than updating an existing
installation. More information can be found in the <ulink
url="http://www.freebsd.org/handbook/mirrors.html"><quote>Obtaining
FreeBSD</quote></ulink> appendix to the <ulink
url="http://www.freebsd.org/handbook/">FreeBSD
Handbook</ulink>.</para>
<sect2>
<title>CDROM</title>
<para>&os; 4.x-RELEASE and 3.x-RELEASE may be ordered on
CDROM from:
<address>
BSDi
<street>4041 Pike Lane, Suite D</street>
<city>Concord</city> <state>CA</state> <postcode>94520</postcode>
<country>USA</country>
<phone>+1-800-786-9907</phone>
<phone>+1-925-674-0783</phone>
<fax>+1-925-674-0821 (FAX)</fax></address>
</para>
<para>Orders may also be placed via the Internet from
<email>orders@cdrom.com</email> or <ulink
url="http://www.cdrom.com/">http://www.cdrom.com/</ulink>. A
current catalog can be obtained via ftp from <ulink
url="ftp://ftp.cdrom.com/cdrom/catalog">ftp://ftp.cdrom.com/cdrom/catalog</ulink>.</para>
<para>As of this writing, the cost per -RELEASE CDROM set is $39.95
(US Dollars) or $24.95 with a &os;
subscription. &os; SNAPshot CDROM sets, when available, are $39.95 or
$14.95 with a &os;-SNAP subscription (-RELEASE and -SNAP
subscriptions are entirely separate). With a subscription, you
will automatically receive updates as they are released. Your
credit card will be billed when each disk is shipped and you may
cancel your subscription at any time without further
obligation.</para>
<para>Shipping (per order not per disk) is $5.00 in the United
States, Canada or Mexico and $9.00 overseas. BSDi accepts Visa,
Mastercard, Discover, American Express or checks in U.S. Dollars
and ships COD within the United States. California residents
please add 8.25% sales tax.</para>
<para>Should you be dissatisfied for any reason, the CDROM comes with
an unconditional return policy.</para>
</sect2>
<sect2>
<title>FTP</title>
<para>You can use FTP to retrieve &os; and any or all of its
optional packages from <ulink
url="ftp://ftp.freebsd.org/">ftp://ftp.freebsd.org/</ulink>, which
is the
official &os; release site.</para>
<para>For other locations that mirror the &os; software see the
file <filename>MIRROR.SITES</filename>.
Please FTP the distribution from the site
closest (in networking terms) to you. Additional mirror sites are
always welcome!
Contact <email>freebsd-admin@FreeBSD.org</email> for more
details if you'd like to become an official mirror site.</para>
<para>Mirrors generally contain the floppy disk images necessary
to begin an installation, as well as the distribution files needed
for the install process itself. Some mirrors also contain some of
the ISO images necessary to create a CDROM of a &os; release.</para>
</sect2>
<sect2>
<title>Email</title>
<para>If you do not have access to the Internet and electronic
mail is your only recourse, then you may still fetch the files by
sending mail to <email>ftpmail@ftpmail.vix.com</email> - putting
the keyword <literal>help</literal> in your message to get more
information on how to fetch files from a &os; FTP archive using
this mechanism. Please do note, however, that this will end up
sending many <emphasis>tens of megabytes</emphasis> through the
mail and should only be employed as an absolute
<emphasis>last</emphasis> resort!</para>
</sect2>
</sect1>

78
release/doc/en_US.ISO_8859-1/readme/problems.sgml Normal file
View File

@ -0,0 +1,78 @@
<!--
$FreeBSD$
problems.sgml
Information on contacting the FreeBSD project, originally from
RELNOTES.TXT.
-->
<sect1 id="contacting">
<title>Reporting Problems, Making Suggestions, and Submitting
Code</title>
<para>Your suggestions, bug reports and contributions of code are
always valued &mdash; please do not hesitate to report any problems you
may find (preferably with a fix attached, if you can!).</para>
<para>The preferred method to submit bug reports from a machine with
Internet mail connectivity is to use the &man.send-pr.1; command or
use the CGI script at <ulink
url="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</ulink>.
Bug reports will be dutifully filed by our faithful bugfiler program
and you can be sure that we'll do our best to respond to all
reported bugs as soon as possible. Bugs filed in this way are also
visible on our Web site in the support section and are therefore
valuable both as bug reports and as <quote>signposts</quote> for
other users concerning potential problems to watch out for.</para>
<para>If, for some reason, you are unable to use &man.send-pr.1; to
submit a bug report, you can try to send it to the &a.bugs;.</para>
<para>Note that &man.send-pr.1; itself is a shell script that should
be easy to move even onto a totally different system. We much
prefer if you could use this interface, since it make it easier to
keep track of the problem reports. However, before submitting,
please try to make sure whether the problem might have already been
fixed since.</para>
<para>Otherwise, for any questions or tech support issues, please send
mail to the &a.questions;.</para>
<para>If you're tracking the -current development efforts, you
<emphasis>must</emphasis> join the &a.current;, in order to keep
abreast of recent developments and changes that may affect the way
you use and maintain the system.
<para>Additionally, being a volunteer effort, we are always happy to
have extra hands willing to help &mdash; there are already far more
desired enhancements than we'll ever be able to manage by ourselves!
To contact us on technical matters, or with offers of help, please
send mail to the &a.hackers;.</para>
<para>Please note that these mailing lists can experience
<emphasis>significant</emphasis> amounts of traffic and if you have
slow or expensive mail access and are only interested in keeping up
with significant FreeBSD events, you may find it preferable to
subscribe instead to the &a.announce;.</para>
<para>All of the mailing lists can be freely joined by anyone
wishing to do so. Send mail to &a.majordomo;
and include the keyword <literal>help</literal> on a line by itself
somewhere in the body of the message. This will give you more
information on joining the various lists, accessing archives, etc.
There are a number of mailing lists targeted at special interest
groups not mentioned here; more information can be obtained either
through majordomo or the <ulink
url="http://www.freebsd.org/support.html#mailing-list">mailing lists
section</ulink> of the FreeBSD Web site.</para>
<important>
<para>Do <emphasis>not</emphasis> send email to the lists asking to
be subscribed. Use the &a.majordomo; address
instead.</para>
</important>
</sect1>

14
release/doc/en_US.ISO_8859-1/readme/readme.ent Normal file
View File

@ -0,0 +1,14 @@
<!-- -*- sgml -*- -->
<!-- $FreeBSD$ -->
<!-- Text constants which probably don't need to be changed.-->
<!-- Files to be included -->
<!ENTITY artheader SYSTEM "artheader.sgml">
<!ENTITY sect.intro SYSTEM "intro.sgml">
<!ENTITY sect.about SYSTEM "about.sgml">
<!ENTITY sect.obtaining SYSTEM "obtaining.sgml">
<!ENTITY sect.problems SYSTEM "problems.sgml">
<!ENTITY sect.ack SYSTEM "ack.sgml">

7
release/doc/en_US.ISO_8859-1/relnotes/Makefile Normal file
View File

@ -0,0 +1,7 @@
# $FreeBSD$
SUBDIR = alpha
SUBDIR+= i386
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

21
release/doc/en_US.ISO_8859-1/relnotes/alpha/Makefile Normal file
View File

@ -0,0 +1,21 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= ../common/relnotes.ent
SRCS+= ../common/artheader.sgml
SRCS+= ../common/new.sgml
SRCS+= ../common/upgrading.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-alpha.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

25
release/doc/en_US.ISO_8859-1/relnotes/alpha/article.sgml Normal file
View File

@ -0,0 +1,25 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/relnotes.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "alpha">
]>
<article>
&artheader;
&sect.intro;
&sect.new;
&sect.upgrading;
</article>

13
release/doc/en_US.ISO_8859-1/relnotes/common/artheader.sgml Normal file
View File

@ -0,0 +1,13 @@
<!-- $FreeBSD$ -->
<articleinfo>
<title>&os; &release.current; &arch; Release Notes</title>
<corpauthor>The FreeBSD Project</corpauthor>
<copyright>
<year>2000</year>
<year>2001</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder>
</copyright>
</articleinfo>

26
release/doc/en_US.ISO_8859-1/relnotes/common/intro.sgml Normal file
View File

@ -0,0 +1,26 @@
<!--
$FreeBSD$
Introduction to the release notes, adapted from the
introduction to the old RELNOTES.TXT.
-->
<sect1>
<title>Introduction</title>
<para>This document contains the release notes for &os; &release.current; on
the &arch; hardware platform. It describes new features of &os;
that have been added (or changed) since &release.prev;.</para>
<para>For information about &os; and the layout of the
distribution directory (especially if you're installing from
floppies!), see <filename>README.TXT</filename>. For installation
instructions, see the <filename>INSTALL.TXT</filename> and
<filename>HARDWARE.TXT</filename> files.</para>
<para>For the latest of these &release.branch; snapshots, you should always
see:</para>
<para><ulink url="&release.url;">&release.url;</ulink></para>
</sect1>

1469
release/doc/en_US.ISO_8859-1/relnotes/common/new.sgml Normal file
View File

File diff suppressed because it is too large Load Diff

16
release/doc/en_US.ISO_8859-1/relnotes/common/relnotes.ent Normal file
View File

@ -0,0 +1,16 @@
<!-- -*- sgml -*- -->
<!-- $FreeBSD$ -->
<!-- Text constants which probably don't need to be changed.-->
<!-- The marker for MFCs. -->
<!ENTITY merged "[MERGED]">
<!-- Files to be included -->
<!ENTITY artheader SYSTEM "../common/artheader.sgml">
<!ENTITY sect.intro SYSTEM "../common/intro.sgml">
<!ENTITY sect.new SYSTEM "../common/new.sgml">
<!ENTITY sect.upgrading SYSTEM "../common/upgrading.sgml">

41
release/doc/en_US.ISO_8859-1/relnotes/common/upgrading.sgml Normal file
View File

@ -0,0 +1,41 @@
<!--
$FreeBSD$
Summary information on upgrading FreeBSD. This comes from
the similarly-named section of RELNOTES.TXT.
-->
<sect1>
<title>Upgrading from previous releases of &os;</title>
<para>If you're upgrading from a previous release of &os;,
most likely it's 4.X and there may be some issues affecting you,
depending of course on your chosen method of upgrading. There
are two popular ways of upgrading &os; distributions:</para>
<para>
<itemizedlist>
<listitem>
<para>Using sources, via <filename>/usr/src</filename></para>
</listitem>
<listitem>
<para>Using the binary upgrade option of &man.sysinstall.8;.</para>
</listitem>
</itemizedlist>
</para>
<para>Please read the <filename>UPGRADE.TXT</filename> file for more
information, preferably <emphasis>before</emphasis> beginning an
upgrade. If you are upgrading from source, please be sure to read
<filename>/usr/src/UPDATING</filename> as well.</para>
<para>Finally, if you want to use one of various means to track the
-STABLE or -CURRENT branches of &os;, please be sure to consult the
<ulink
url="http://www.freebsd.org/handbook/current-stable.html"><quote>-CURRENT
vs. -STABLE</quote></ulink> section of the <ulink
url="http://www.freebsd.org/handbook/">FreeBSD
Handbook</ulink>.</para>
</sect1>

21
release/doc/en_US.ISO_8859-1/relnotes/i386/Makefile Normal file
View File

@ -0,0 +1,21 @@
# $FreeBSD$
DOC?= article
FORMATS?= html
INSTALL_COMPRESSED?= gz
INSTALL_ONLY_COMPRESSED?=
EXTRA_CATALOGS+= ../../../share/sgml/catalog
# SGML content
SRCS+= article.sgml
SRCS+= ../common/relnotes.ent
SRCS+= ../common/artheader.sgml
SRCS+= ../common/new.sgml
SRCS+= ../common/upgrading.sgml
# Use the appropriate architecture-dependent RELNOTESng stylesheet
DSLHTML?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DSLPRINT?= ${.CURDIR}/../../../share/sgml/release-i386.dsl
DOC_PREFIX?= /usr/doc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"

25
release/doc/en_US.ISO_8859-1/relnotes/i386/article.sgml Normal file
View File

@ -0,0 +1,25 @@
<!-- $FreeBSD$ -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
%authors;
<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mlists;
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
%release;
<!ENTITY % sections SYSTEM "../common/relnotes.ent"> %sections;
<!-- Architecture-specific customization -->
<!ENTITY arch "i386">
]>
<article>
&artheader;
&sect.intro;
&sect.new;
&sect.upgrading;
</article>

8
release/doc/share/sgml/catalog Normal file
View File

@ -0,0 +1,8 @@
-- FreeBSD SGML Public Identifiers --
-- Release-specific --
-- $FreeBSD$ --
PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"
"release.ent"

32
release/doc/share/sgml/release-alpha.dsl Normal file
View File

@ -0,0 +1,32 @@
<!-- $FreeBSD$ -->
<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
<!ENTITY freebsd.dsl PUBLIC "-//FreeBSD//DOCUMENT DocBook Stylesheet//EN" CDATA DSSSL>
]>
<style-sheet>
<style-specification use="docbook">
<style-specification-body>
; The architecture we're building for. We really need to pull this out of a
; entity somewhere, so it can be defined without needing to munge the
; stylesheet. Or do we?
(define for-arch "alpha")
(default
(let* ((arch (attribute-string (normalize "arch"))))
(if (or (equal? arch #f)
(equal? arch ""))
(next-match)
; We can do a lot more flexible things here. Like it'd be nice to
; tokenize the arch= attribute and do comparisons of for-arch against
; different substrings.
(cond ((equal? arch for-arch) (next-match))
(else (empty-sosofo))))))
</style-specification-body>
</style-specification>
<external-specification id="docbook" document="freebsd.dsl">
</style-sheet>

32
release/doc/share/sgml/release-i386.dsl Normal file
View File

@ -0,0 +1,32 @@
<!-- $FreeBSD$ -->
<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
<!ENTITY freebsd.dsl PUBLIC "-//FreeBSD//DOCUMENT DocBook Stylesheet//EN" CDATA DSSSL>
]>
<style-sheet>
<style-specification use="docbook">
<style-specification-body>
; The architecture we're building for. We really need to pull this out of a
; entity somewhere, so it can be defined without needing to munge the
; stylesheet. Or do we?
(define for-arch "i386")
(default
(let* ((arch (attribute-string (normalize "arch"))))
(if (or (equal? arch #f)
(equal? arch ""))
(next-match)
; We can do a lot more flexible things here. Like it'd be nice to
; tokenize the arch= attribute and do comparisons of for-arch against
; different substrings.
(cond ((equal? arch for-arch) (next-match))
(else (empty-sosofo))))))
</style-specification-body>
</style-specification>
<external-specification id="docbook" document="freebsd.dsl">
</style-sheet>

Some files were not shown because too many files have changed in this diff Show More