Add the 12.1-RELEASE errata, hardware, installation, and readme

pages.  These are not yet connected to the build.

Prune errata page entries from 12.0-RELEASE, and bump the copyright
years as appropriate.

Sponsored by:	Rubicon Communications, LLC (Netgate)

8 files changed, 2231 insertions, 0 deletions

diff --git a/en_US.ISO8859-1/htdocs/releases/12.1R/errata/Makefile b/en_US.ISO8859-1/htdocs/releases/12.1R/errata/Makefile
new file mode 100644
index 0000000000..476c4e0cc6
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/releases/12.1R/errata/Makefile
@@ -0,0 +1,15 @@
+# $FreeBSD$
+
+.if exists(../Makefile.inc)
+.include "../Makefile.inc"
+.endif
+
+DOC?=			errata
+FORMATS?=		html txt
+INSTALL_COMPRESSED?=	gz
+INSTALL_ONLY_COMPRESSED=
+
+.PHONY:			${DOC}.parsed.xml
+.PHONY:			${DOC}.html
+
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/htdocs/releases/12.1R/errata/errata.xml b/en_US.ISO8859-1/htdocs/releases/12.1R/errata/errata.xml
new file mode 100644
index 0000000000..df7e07ed5a
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/releases/12.1R/errata/errata.xml
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+"../../../../../share/xml/freebsd50.dtd" [
+<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "../share/xml/release.ent">
+ %release;
+<!ENTITY % sponsor PUBLIC "-//FreeBSD//ENTITIES Sponsor Specification//EN" "../share/xml/sponsor.ent">
+ %sponsor;
+<!ENTITY % vendor PUBLIC "-//FreeBSD//ENTITIES Vendor Specification//EN" "../share/xml/vendor.ent">
+ %vendor;
+<!ENTITY security SYSTEM "../share/xml/security.xml">
+<!ENTITY errata SYSTEM "../share/xml/errata.xml">
+]>
+
+<article xmlns="http://docbook.org/ns/docbook"
+	xmlns:xlink="http://www.w3.org/1999/xlink"
+	version="5.0">
+  <info>
+    <title>&os; &release; Errata</title>
+
+    <author>
+      <orgname>The &os; Project</orgname>
+    </author>
+
+    <pubdate>$FreeBSD$</pubdate>
+
+    <copyright>
+      <year>2019</year>
+      <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
+	Project</holder>
+    </copyright>
+
+    <legalnotice xml:id="trademarks" role="trademarks">
+      &tm-attrib.freebsd;
+      &tm-attrib.intel;
+      &tm-attrib.sparc;
+      &tm-attrib.general;
+    </legalnotice>
+
+    <abstract>
+      <para>This document lists errata items for &os; &release;,
+	containing significant information discovered after the
+	release or too late in the release cycle to be otherwise
+	included in the release documentation.  This information
+	includes security advisories, as well as news relating to the
+	software or documentation that could affect its operation or
+	usability.  An up-to-date version of this document should
+	always be consulted before installing this version of
+	&os;.</para>
+
+      <para>This errata document for &os; &release; will be maintained
+	until the release of &os; &release.next;.</para>
+    </abstract>
+  </info>
+
+  <sect1 xml:id="intro">
+    <title>Introduction</title>
+
+    <para>This errata document contains <quote>late-breaking
+	news</quote> about &os; &release; Before installing this
+      version, it is important to consult this document to learn about
+      any post-release discoveries or problems that may already have
+      been found and fixed.</para>
+
+    <para>Any version of this errata document actually distributed
+      with the release (for example, on a CDROM distribution) will be
+      out of date by definition, but other copies are kept updated on
+      the Internet and should be consulted as the <quote>current
+	errata</quote> for this release.  These other copies of the
+      errata are located at <link
+	xlink:href="https://www.FreeBSD.org/releases/" />, plus any
+      sites which keep up-to-date mirrors of this location.</para>
+
+    <para>Source and binary snapshots of &os; &release.branch; also
+      contain up-to-date copies of this document (as of the time of
+      the snapshot).</para>
+
+    <para>For a list of all &os; CERT security advisories, see
+      <link xlink:href="https://www.FreeBSD.org/security/"/>.</para>
+  </sect1>
+
+  <sect1 xml:id="security">
+    <title>Security Advisories</title>
+
+    &security;
+  </sect1>
+
+  <sect1 xml:id="errata">
+    <title>Errata Notices</title>
+
+    &errata;
+  </sect1>
+
+  <sect1 xml:id="open-issues">
+    <title>Open Issues</title>
+
+    <itemizedlist>
+      <listitem>
+	<para>No open issues.</para>
+      </listitem>
+    </itemizedlist>
+  </sect1>
+
+  <sect1 xml:id="late-news">
+    <title>Late-Breaking News</title>
+
+    <para>No news.</para>
+  </sect1>
+</article>
diff --git a/en_US.ISO8859-1/htdocs/releases/12.1R/hardware/Makefile b/en_US.ISO8859-1/htdocs/releases/12.1R/hardware/Makefile
new file mode 100644
index 0000000000..5c5e8fdbbd
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/releases/12.1R/hardware/Makefile
@@ -0,0 +1,49 @@
+# $FreeBSD$
+
+.if exists(../Makefile.inc)
+.include "../Makefile.inc"
+.endif
+.if exists(../Makefile.hardware)
+.include "../Makefile.hardware"
+.endif
+
+ARCHLIST?=	${DOC_PREFIX}/share/misc/dev.archlist.txt
+
+MAN2HWNOTES_CMD=${DOC_PREFIX}/share/misc/man2hwnotes.pl
+.if defined(HWNOTES_MI)
+MAN2HWNOTES_FLAGS=
+.else
+MAN2HWNOTES_FLAGS=	-c
+.endif
+
+DOC?=			hardware
+FORMATS?=		html txt
+INSTALL_COMPRESSED?=	gz
+INSTALL_ONLY_COMPRESSED=
+
+.if ${.TARGET:M${DOC}.html}
+MAN4TMP!=	${MKTEMP} -d ${.CURDIR}/svn.XXXXXXXX
+MAN4DIR=	${MAN4TMP}
+.if exists(${MAN4DIR})
+	rm -rf ${MAN4DIR}
+.endif
+
+MAN4PAGES?=	${MAN4DIR}/*.4 ${MAN4DIR}/man4.*/*.4
+hardware.parsed.xml:	dev-auto.ent man4-rmsrc
+dev-auto.ent:	man4-src-checkout
+	${PERL} ${MAN2HWNOTES_CMD} ${MAN2HWNOTES_FLAGS} -a ${ARCHLIST} -o ${.TARGET} ${MAN4PAGES} || (rm -f ${.TARGET})
+CLEANFILES+=	dev-auto.ent
+CLEANDIRS+=	${.CURDIR}/svn.*
+
+.ORDER:			man4-rmsrc man4-src-checkout
+man4-src-checkout:
+	mkdir -p ${MAN4TMP}
+	${SVN} co svn://svn.freebsd.org/base/${SRCBRANCH}/share/man/man4 \
+		${MAN4TMP}
+
+man4-rmsrc:
+	@# Just in case.
+	rm -rf ${MAN4DIR} || true
+.endif
+
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/htdocs/releases/12.1R/hardware/hardware.xml b/en_US.ISO8859-1/htdocs/releases/12.1R/hardware/hardware.xml
new file mode 100644
index 0000000000..182ff8f032
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/releases/12.1R/hardware/hardware.xml
@@ -0,0 +1,1476 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+    "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd" [
+<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"
+    "../share/xml/release.ent">
+ %release;
+<!ENTITY % sponsor PUBLIC "-//FreeBSD//ENTITIES Sponsor Specification//EN"
+    "../share/xml/sponsor.ent">
+ %sponsor;
+<!ENTITY % vendor PUBLIC "-//FreeBSD//ENTITIES Vendor Specification//EN"
+    "../share/xml/vendor.ent">
+ %vendor;
+<!ENTITY security SYSTEM "../share/xml/security.xml">
+<!ENTITY errata SYSTEM "../share/xml/errata.xml">
+<!ENTITY % devauto PUBLIC "-//FreeBSD//ENTITIES Auto Generated Device Lists//EN"
+    "http://www.FreeBSD.org/XML/cwd/dev-auto.ent">
+%devauto;
+]>
+<article xmlns="http://docbook.org/ns/docbook"
+  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
+
+  <info>
+    <title>&os; &release.current; Hardware Notes</title>
+
+    <author>
+      <orgname>The &os; Documentation Project</orgname>
+    </author>
+
+    <pubdate>$FreeBSD$</pubdate>
+    <copyright>
+      <year>2000</year>
+      <year>2001</year>
+      <year>2002</year>
+      <year>2003</year>
+      <year>2004</year>
+      <year>2005</year>
+      <year>2006</year>
+      <year>2007</year>
+      <year>2008</year>
+      <year>2009</year>
+      <year>2010</year>
+      <year>2011</year>
+      <year>2012</year>
+      <year>2013</year>
+      <year>2014</year>
+      <year>2015</year>
+      <year>2016</year>
+      <year>2017</year>
+      <year>2018</year>
+      <year>2019</year>
+      <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
+	Project</holder>
+    </copyright>
+
+    <legalnotice xml:id="trademarks" role="trademarks">
+      &tm-attrib.freebsd;
+      &tm-attrib.amd;
+      &tm-attrib.fujitsu;
+      &tm-attrib.ibm;
+      &tm-attrib.intel;
+      &tm-attrib.sparc;
+      &tm-attrib.sun;
+      &tm-attrib.general;
+    </legalnotice>
+
+  </info>
+
+  <sect1 xml:id="intro">
+    <title>Introduction</title>
+
+    <para>This document contains the hardware compatibility notes for
+      &os; &release.current;.  It lists the hardware platforms
+      supported by &os;, as well as the various types of hardware
+      devices (storage controllers, network interfaces, and so on),
+      along with known working instances of these devices.</para>
+  </sect1>
+
+  <sect1 xml:id="proc">
+    <title>Supported Processors and System Boards</title>
+
+    <para>This section provides some architecture-specific information
+      about the specific processors and systems that are supported by
+      each architecture.</para>
+
+    <sect2 xml:id="proc-amd64">
+      <title>amd64</title>
+
+      <para>Since mid-2003 &os;/&arch.amd64; has supported the AMD64
+	(<quote>Hammer</quote>) and &intel; EM64T architecture, and is
+	now one of the Tier-1 platforms (fully supported
+	architecture), which are expected to be Production Quality
+	with respects to all aspects of the &os; operating system,
+	including installation and development environments.</para>
+
+      <para>Note that there are two names for this architecture, AMD64
+	(AMD) and Intel EM64T (Extended Memory 64-bit Technology).
+	64-bit mode of the two architectures are almost compatible
+	with each other, and &os;/&arch.amd64; supports them
+	both.</para>
+
+      <para>As of this writing, the following processors are
+	supported:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>&amd.athlon;64 (<quote>Clawhammer</quote>).</para>
+	</listitem>
+
+	<listitem>
+	  <para>&amd.opteron; (<quote>Sledgehammer</quote>).</para>
+	</listitem>
+
+	<listitem>
+	  <para>&amd.sempron;.</para>
+	</listitem>
+
+	<listitem>
+	  <para>&amd.turion;.</para>
+	</listitem>
+
+	<listitem>
+	  <para>&amd.phenom;.</para>
+	</listitem>
+
+	<listitem>
+	  <para>All multi-core &intel; &xeon; processors except
+	    Sossaman have EM64T support.</para>
+	</listitem>
+
+	<listitem>
+	  <para>The single-core &intel; &xeon; processors
+	    <quote>Nocona</quote>, <quote>Irwindale</quote>,
+	    <quote>Potomac</quote>, and <quote>Cranford</quote> have
+	    EM64T support.</para>
+	</listitem>
+
+	<listitem>
+	  <para>All &intel; &core; 2 (not &core; Duo) and later
+	    processors</para>
+	</listitem>
+
+	<listitem>
+	  <para>All &intel; &core; i range of processors</para>
+	</listitem>
+
+	<listitem>
+	  <para>All &intel; &pentium; D processors</para>
+	</listitem>
+
+	<listitem>
+	  <para>All &intel; &centrino; Duo and &centrino; Pro
+	    platforms</para>
+	</listitem>
+
+	<listitem>
+	  <para>&intel; &pentium; 4s and &celeron; Ds using
+	    the <quote>Cedar Mill</quote> core have EM64T
+	    support.</para>
+	</listitem>
+
+	<listitem>
+	  <para>Some &intel; &pentium; 4s and &celeron; Ds using the
+	    <quote>Prescott</quote> core have EM64T support.  See the
+	    <link xlink:href="http://processorfinder.intel.com">Intel
+	      Processor Spec Finder</link> for the definitive answer
+	    about EM64T support in Intel processors.</para>
+	</listitem>
+
+      </itemizedlist>
+
+      <para>&intel; EM64T is an extended version of IA-32 (x86) and
+	different from &intel; IA-64 (Itanium) architecture.  Some of
+	&intel;'s old documentation refers to &intel; EM64T as
+	<quote>64-bit extension technology</quote> or
+	<quote>IA-32e</quote>.</para>
+
+      <para>Both Uniprocessor (UP) and Symmetric Multi-processor (SMP)
+	configurations are supported.</para>
+
+      <para>In many respects, &os;/&arch.amd64; is similar to
+	&os;/&arch.i386;, in terms of drivers supported.  Generally,
+	drivers that already function correctly on other 64-bit
+	platforms should work.</para>
+    </sect2>
+
+    <sect2 xml:id="proc-i386">
+      <title>i386</title>
+
+      <para>&os;/&arch.i386; runs on a wide variety of <quote>IBM PC
+	  compatible</quote> machines.  Due to the wide range of
+	hardware available for this architecture, it is impossible
+	to exhaustively list all combinations of equipment supported
+	by &os;.  Nevertheless, some general guidelines are
+	presented here.</para>
+
+      <para>Almost all &i386;-compatible processors with a floating
+	point unit are supported.  All &intel; processors beginning
+	with the 80486 are supported, including the 80486, &pentium;,
+	&pentium; Pro, &pentium; II, &pentium; III, &pentium; 4, and
+	variants thereof, such as the &xeon; and &celeron; processors.
+	All &i386;-compatible AMD processors are also supported,
+	including the &am486;, &am5x86;, K5, &amd.k6; (and variants),
+	&amd.athlon; (including Athlon-MP, Athlon-XP, Athlon-4, and
+	Athlon Thunderbird), and &amd.duron; processors.  The AMD
+	&Eacute;lan SC520 embedded processor is supported.  The
+	Transmeta Crusoe is recognized and supported, as are
+	&i386;-compatible processors from Cyrix and NexGen.</para>
+
+      <para>There is a wide variety of motherboards available for this
+	architecture.  Motherboards using the ISA, VLB, EISA, AGP, and
+	PCI expansion buses are well-supported.  There is some
+	limited support for the MCA (<quote>MicroChannel</quote>)
+	expansion bus used in the IBM PS/2 line of PCs.</para>
+
+      <para>Symmetric multi-processor (SMP) systems are generally
+	supported by &os;, although in some cases, BIOS or motherboard
+	bugs may generate some problems.  Perusal of the archives of
+	the &a.smp; may yield some clues.</para>
+
+      <para>&os; will take advantage of SMT (Symmetric MultiThreading,
+	also known as HyperThreading on &intel; CPUs) on the supported
+	CPUs.  The <filename>GENERIC</filename> kernel which is
+	installed by default will automatically detect the additional
+	logical processors.  The default &os; scheduler recognizes
+	processor topology on the system and selects logical and
+	physical processors to obtain optimal performance.
+	The &man.smp.4; manual page has more details.</para>
+
+      <para>&os; will take advantage of Physical Address Extensions
+	(PAE) support on CPUs that support this feature.  A kernel
+	with the <literal>PAE</literal> feature enabled will detect
+	memory above 4 gigabytes and allow it to be used by the
+	system.  This feature places constraints on the device drivers
+	and other features of &os; which may be used; consult the
+	&man.pae.4; manual page for more details.</para>
+
+      <para>&os; will generally run on i386-based laptops, albeit with
+	varying levels of support for certain hardware features such
+	as sound, graphics, power management, and PCCARD expansion
+	slots.  These features tend to vary in idiosyncratic ways
+	between machines, and frequently require special-case support
+	in &os; to work around hardware bugs or other oddities.  When
+	in doubt, a search of the archives of the &a.mobile; may be
+	useful.</para>
+
+      <para>Most modern laptops (as well as many desktops) use the
+	Advanced Configuration and Power Management (ACPI) standard.
+	&os; supports ACPI via the ACPI Component Architecture
+	reference implementation from &intel;, as described in the
+	&man.acpi.4; manual page.  The use of ACPI causes
+	instabilities on some machines and it may be necessary to
+	disable the ACPI driver, which is normally loaded via a kernel
+	module.  This may be accomplished by adding the following line
+	to <filename>/boot/device.hints</filename>:</para>
+
+      <programlisting>hint.acpi.0.disabled="1"</programlisting>
+
+      <para>Users debugging ACPI-related problems may find it useful
+	to disable portions of the ACPI functionality.  The
+	&man.acpi.4; manual page has more information on how to do
+	this via loader tunables.</para>
+
+      <para>ACPI depends on a Differentiated System Descriptor Table
+	(DSDT) provided by each machine's BIOS.  Some machines have
+	bad or incomplete DSDTs, which prevents ACPI from functioning
+	correctly.  Replacement DSDTs for some machines can be found
+	at the <link
+	  xlink:href="http://acpi.sourceforge.net/dsdt/index.php">DSDT</link>
+	section of the <link
+	  xlink:href="http://acpi.sourceforge.net/">ACPI4Linux</link>
+	project Web site.  &os; can use these DSDTs to override the
+	DSDT provided by the BIOS; see the &man.acpi.4; manual page
+	for more information.</para>
+    </sect2>
+
+    <sect2 xml:id="proc-powerpc">
+      <title>powerpc</title>
+
+      <para>All Apple PowerPC machines with built-in USB are
+	supported, as well a limited selection of non-Apple machines,
+	including KVM on POWER7</para>
+
+      <para>SMP is supported on all systems with more than
+	1 processor.</para>
+    </sect2>
+
+    <sect2 xml:id="proc-sparc64">
+      <title>sparc64</title>
+
+      <para>This section describes the systems currently known to be
+	supported by &os; on the Fujitsu &sparc64; and Sun
+	&ultrasparc; platforms.</para>
+
+      <para>SMP is supported on all systems with more than 1
+	processor.</para>
+
+      <para>When using the <filename>GENERIC</filename> kernel,
+	&os;/&arch.sparc64; systems not equipped with a framebuffer
+	supported by the &man.creator.4; (Sun Creator, Sun Creator3D
+	and Sun Elite3D) or &man.machfb.4; (Sun PGX and Sun PGX64 as
+	well as the ATI Mach64 chips found onboard in for example
+	&sun.blade; 100, &sun.blade; 150, &sun.ultra; 5 and
+	&sun.ultra; 10) driver must use the serial console.</para>
+
+      <para>If you have a system that is not listed here, it may not
+	have been tested with &os; &release.current;.  We encourage
+	you to try it and send a note to the &a.sparc; with your
+	results, including which devices work and which do not.</para>
+
+      <para>The following systems are fully supported by &os;:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>Naturetech GENIALstation 777S</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.blade; 100</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.blade; 150</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.enterprise; 150</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.enterprise; 220R</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.enterprise; 250</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.enterprise; 420R</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.enterprise; 450</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; B100s (support for the on-board NICs first
+	    appeared in 8.1-RELEASE)</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V100</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V120</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &netra; t1 100/105</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &netra; T1 AC200/DC200</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &netra; t 1100</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &netra; t 1120</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &netra; t 1125</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &netra; t 1400/1405</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &netra; 120</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &netra; X1</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &sparcengine; Ultra AX1105</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &sparcengine; Ultra AXe</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &sparcengine; Ultra AXi</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &sparcengine; Ultra AXmp</para>
+	</listitem>
+
+	<listitem>
+	  <para>Sun &sparcengine; CP1500</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 1</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 1E</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 2</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 5</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 10</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 30</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 60</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 80</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.ultra; 450</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>The following systems are partially supported by &os;.  In
+	particular the fiber channel controllers in SBus-based systems
+	are not supported.  However, it is possible to use these with
+	a SCSI controller supported by the &man.esp.4; driver (Sun ESP
+	SCSI, Sun FAS Fast-SCSI and Sun FAS366 Fast-Wide SCSI
+	controllers).</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>&sun.enterprise; 3500</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.enterprise; 4500</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>Starting with 7.2-RELEASE, &arch.sparc64; systems based on
+	Sun &ultrasparc; III and beyond are also supported by &os;,
+	which includes the following known working systems:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>&sun.blade; 1000</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.blade; 1500</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.blade; 2000</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.blade; 2500</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; 280R</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V210</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V215 (support first appeared in 7.3-RELEASE
+	    and 8.1-RELEASE)</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V240</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V245 (support first appeared in 7.3-RELEASE
+	    and 8.1-RELEASE)</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V250</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V440 (support for the on-board NICs first
+	    appeared in 7.3-RELEASE and 8.0-RELEASE)</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V480 (501-6780 and 501-6790 centerplanes
+	    only, for which support first appeared in 7.3-RELEASE and
+	    8.1-RELEASE, other centerplanes might work beginning with
+	    8.3-RELEASE and 9.0-RELEASE)</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V880</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V890 (support first appeared in 7.4-RELEASE
+	    and 8.1-RELEASE, non-mixed &ultrasparc; IV/IV+
+	    CPU-configurations only)</para>
+	</listitem>
+
+	<listitem>
+	  <para>&netra; 20/&netra; T4</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>The following Sun &ultrasparc; systems are not tested but
+	believed to be also supported by &os;:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>&sun.fire; V125</para>
+	</listitem>
+
+	<listitem>
+	  <para>&sun.fire; V490 (support first appeared in 7.4-RELEASE
+	    and 8.1-RELEASE, non-mixed &ultrasparc; IV/IV+
+	    CPU-configurations only)</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>Starting with 7.4-RELEASE and 8.1-RELEASE, &arch.sparc64;
+	systems based on Fujitsu &sparc64; V are also supported by
+	&os;, which includes the following known working
+	systems:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>Fujitsu &primepower; 250</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>The following Fujitsu &primepower; systems are not tested
+	but believed to be also supported by &os;:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>Fujitsu &primepower; 450</para>
+	</listitem>
+
+	<listitem>
+	  <para>Fujitsu &primepower; 650</para>
+	</listitem>
+
+	<listitem>
+	  <para>Fujitsu &primepower; 850</para>
+	</listitem>
+      </itemizedlist>
+
+    </sect2>
+  </sect1>
+
+  <!--
+
+  The "Supported Devices" section of the release notes.
+  Generally processor-independent, with conditional text
+  inclusion handling any architecture-dependent text.
+
+  Within each subsection describing a class of hardware
+  (i.e. Ethernet interfaces), list broad groups of devices
+  alphabetically as paragraphs sorted alphabetically (frequently
+  these groups will be arranged by manufacturer, i.e. 3Com
+  Ethernet interfaces).
+
+  Where applicable, a "Miscellaneous" section may follow all
+  other named sections.
+
+  These guidelines are not hard-and-fast rules, and exceptions
+  will occur.  Following these guidelines (vague as they may be)
+  is highly recommended to try to keep the formatting of
+  this section consistent.
+
+  We give manpage references using the &man entities where
+  possible.  If a driver has no manpage (and consequently no
+  &man entity, we simply give the name of the driver).
+  Please avoid doing &man entity conversions unless you
+  know for sure that an entity and manpage exist; sweeps through
+  this file to fix "missed" conversions are likely to break the
+  build.
+  -->
+
+  <sect1 xml:id="support">
+    <title>Supported Devices</title>
+
+    <para>This section describes the devices currently known to be
+      supported by &os;.  Other configurations may also work, but
+      simply have not been tested yet.  Feedback, updates, and
+      corrections to this list are encouraged.</para>
+
+    <para>Where possible, the drivers applicable to each device or
+      class of devices is listed.  If the driver in question has a
+      manual page in the &os; base distribution (most should), it is
+      referenced here.  Information on specific models of supported
+      devices, controllers, etc. can be found in the manual
+      pages.</para>
+
+    <note>
+      <para>The device lists in this document are being generated
+	automatically from &os; manual pages.  This means that some
+	devices, which are supported by multiple drivers, may appear
+	multiple times.</para>
+    </note>
+
+    <sect2 xml:id="disk">
+      <title>Disk Controllers</title>
+
+      <para>[&arch.amd64;, &arch.i386;, &arch.sparc64;]
+	IDE/ATA controllers (&man.ata.4; driver)</para>
+
+      &hwlist.aac;
+
+      &hwlist.adv;
+
+      &hwlist.adw;
+
+      &hwlist.aha;
+
+      &hwlist.ahc;
+
+      &hwlist.ahci;
+
+      &hwlist.ahd;
+
+      &hwlist.aic;
+
+      &hwlist.amr;
+
+      &hwlist.arcmsr;
+
+      &hwlist.bt;
+
+      &hwlist.ciss;
+
+      &hwlist.dpt;
+
+      <note>
+	<para>[&arch.amd64;, &arch.i386;] Booting from these
+	  controllers is supported.  EISA adapters are not
+	  supported.</para>
+      </note>
+
+      &hwlist.esp;
+
+      &hwlist.hpt27xx;
+
+      &hwlist.hptiop;
+
+      &hwlist.hptmv;
+
+      &hwlist.hptrr;
+
+      &hwlist.ida;
+
+      &hwlist.iir;
+
+      &hwlist.ips;
+
+      &hwlist.isci;
+
+      &hwlist.isp;
+
+      &hwlist.mfi;
+
+      &hwlist.mlx;
+
+      <note>
+	<para>[&arch.amd64;, &arch.i386;] Booting from these
+	  controllers is supported.  EISA adapters are not
+	  supported.</para>
+      </note>
+
+      &hwlist.mly;
+
+      &hwlist.mpr;
+
+      &hwlist.mps;
+
+      &hwlist.mpt;
+
+      &hwlist.mrsas;
+
+      &hwlist.mvs;
+
+      &hwlist.ncr;
+
+      &hwlist.ncv;
+
+      &hwlist.nsp;
+
+      &hwlist.pms;
+
+      &hwlist.pst;
+
+      &hwlist.siis;
+
+      &hwlist.stg;
+
+      &hwlist.sym;
+
+      &hwlist.trm;
+
+      &hwlist.twa;
+
+      &hwlist.twe;
+
+      &hwlist.tws;
+
+      &hwlist.vpo;
+
+      <para>With all supported SCSI controllers, full support is
+	provided for SCSI-I, SCSI-II, and SCSI-III peripherals,
+	including hard disks, optical disks, tape drives (including
+	DAT, 8mm Exabyte, Mammoth, and DLT), medium changers,
+	processor target devices and CD-ROM drives.  WORM devices that
+	support CD-ROM commands are supported for read-only access by
+	the CD-ROM drivers (such as &man.cd.4;).  WORM/CD-R/CD-RW
+	writing support is provided by &man.cdrecord.1;, which is
+	a part of the <package>sysutils/cdrtools</package> port in the
+	Ports Collection.</para>
+
+      <para>The following CD-ROM type systems are supported at this
+	time:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>SCSI interface (also includes ProAudio Spectrum and
+	    SoundBlaster SCSI) (&man.cd.4;)</para>
+	</listitem>
+
+	<listitem>
+	  <para>ATAPI IDE interface (&man.acd.4;)</para>
+	</listitem>
+      </itemizedlist>
+    </sect2>
+
+    <sect2 xml:id="ethernet">
+      <title>Ethernet Interfaces</title>
+
+      &hwlist.ae;
+
+      &hwlist.age;
+
+      &hwlist.ale;
+
+      &hwlist.aue;
+
+      &hwlist.axe;
+
+      <para>ASIX Electronics AX88178A/AX88179 USB Gigabit Ethernet
+	adapters (&man.axge.4; driver)</para>
+
+      &hwlist.bce;
+
+      <para>[&arch.amd64;, &arch.i386;] Broadcom BCM4401 based Fast
+	Ethernet adapters (&man.bfe.4; driver)</para>
+
+      &hwlist.bge;
+
+      &hwlist.bnxt;
+
+      &hwlist.bxe;
+
+      &hwlist.cas;
+
+      &hwlist.cdce;
+
+      <para>[&arch.amd64;, &arch.i386;] Crystal Semiconductor
+	CS89x0-based NICs (&man.cs.4; driver)</para>
+
+      &hwlist.cue;
+
+      &hwlist.cxgb;
+
+      &hwlist.cxgbe;
+
+      &hwlist.dc;
+
+      &hwlist.de;
+
+      &hwlist.ed;
+
+      &hwlist.em;
+
+      &hwlist.ep;
+
+      <para>Agere ET1310 Gigabit Ethernet adapters
+	(&man.et.4; driver)</para>
+
+      &hwlist.ex;
+
+      &hwlist.fe;
+
+      &hwlist.fxp;
+
+      &hwlist.gem;
+
+      &hwlist.hme;
+
+      &hwlist.ipheth;
+
+      &hwlist.ixgbe;
+
+      &hwlist.ixl;
+
+      &hwlist.jme;
+
+      &hwlist.kue;
+
+      &hwlist.lge;
+
+      &hwlist.mlx4en;
+
+      &hwlist.mlx5en;
+
+      &hwlist.msk;
+
+      &hwlist.mxge;
+
+      &hwlist.my;
+
+      &hwlist.nfe;
+
+      &hwlist.nge;
+
+      &hwlist.oce;
+
+      &hwlist.pcn;
+
+      &hwlist.qlxgb;
+
+      &hwlist.qlxgbe;
+
+      &hwlist.qlxge;
+
+      &hwlist.re;
+
+      &hwlist.rl;
+
+      &hwlist.rue;
+
+      &hwlist.sf;
+
+      &hwlist.sfxge;
+
+      &hwlist.sge;
+
+      &hwlist.sis;
+
+      &hwlist.sk;
+
+      &hwlist.smsc;
+
+      &hwlist.sn;
+
+      &hwlist.ste;
+
+      &hwlist.stge;
+
+      &hwlist.ti;
+
+      &hwlist.tl;
+
+      <para>[&arch.amd64;, &arch.i386;] SMC 83c17x
+	(EPIC)-based Ethernet NICs (&man.tx.4; driver)</para>
+
+      &hwlist.txp;
+
+      &hwlist.udav;
+
+      &hwlist.urndis;
+
+      &hwlist.vge;
+
+      &hwlist.vr;
+
+      &hwlist.vte;
+
+      &hwlist.vx;
+
+      &hwlist.wb;
+
+      &hwlist.xe;
+
+      &hwlist.xl;
+
+    </sect2>
+
+    <sect2 xml:id="fddi">
+      <title>FDDI Interfaces</title>
+
+      <para>[&arch.i386;] DEC DEFPA PCI (&man.fpa.4; driver)</para>
+
+      <para>[&arch.i386;] DEC DEFEA EISA (&man.fpa.4; driver)</para>
+    </sect2>
+
+    <sect2 xml:id="wlan">
+      <title>Wireless Network Interfaces</title>
+
+      <para>[&arch.amd64;, &arch.i386;] Cisco/Aironet
+	802.11b wireless adapters (&man.an.4; driver)</para>
+
+      &hwlist.ath;
+
+      &hwlist.bwi;
+
+      &hwlist.bwn;
+
+      <para>[&arch.i386;, &arch.amd64;] Intel PRO/Wireless 2100
+	MiniPCI network adapter (&man.ipw.4; driver)</para>
+
+      <para>[&arch.i386;, &arch.amd64;] Intel PRO/Wireless
+	2200BG/2915ABG MiniPCI and 2225BG PCI network adapters
+	(&man.iwi.4; driver)</para>
+
+      <para>[&arch.i386;, &arch.amd64;] Intel Dual Band Wireless AC
+	3160/7260/7265 IEEE 802.11ac network adapters (&man.iwm.4;
+	driver)</para>
+
+      <para>[&arch.i386;, &arch.amd64;] Intel Wireless WiFi Link
+	4965AGN IEEE 802.11n PCI network adapters
+	(&man.iwn.4; driver)</para>
+
+      <para>[&arch.i386;, &arch.amd64;] Marvell Libertas IEEE
+	802.11b/g PCI network adapters (&man.malo.4; driver)</para>
+
+      <para>Marvell 88W8363 IEEE 802.11n wireless network
+	adapters (&man.mwl.4; driver)</para>
+
+      &hwlist.otus;
+
+      &hwlist.ral;
+
+      &hwlist.rsu;
+
+      <para>Realtek RTL8192C, RTL8188E, RTL8812A and RTL8821A based
+	PCIe IEEE 802.11b/g/n wireless network adapters (&man.rtwn.4;
+	driver)</para>
+
+      &hwlist.rum;
+
+      &hwlist.run;
+
+      &hwlist.uath;
+
+      &hwlist.upgt;
+
+      &hwlist.ural;
+
+      &hwlist.urtw;
+
+      <para>[&arch.amd64;, &arch.i386;] Lucent
+	Technologies WaveLAN/IEEE 802.11b wireless network adapters
+	and workalikes using the Lucent Hermes, Intersil PRISM-II,
+	Intersil PRISM-2.5, Intersil Prism-3, and Symbol Spectrum24
+	chipsets (&man.wi.4; driver)</para>
+
+      <para>[&arch.i386;, &arch.amd64;] Intel PRO/Wireless 3945ABG
+	MiniPCI network adapters (&man.wpi.4; driver)</para>
+
+      &hwlist.zyd;
+    </sect2>
+
+    <sect2 xml:id="misc-network">
+      <title>Miscellaneous Networks</title>
+
+      &hwlist.ce;
+
+      &hwlist.cx;
+
+      &hwlist.cp;
+
+      &hwlist.ctau;
+    </sect2>
+
+    <sect2 xml:id="serial">
+      <title>Serial Interfaces</title>
+
+      <para>[&arch.amd64;, &arch.i386;] <quote>PC standard</quote>
+	8250, 16450, and 16550-based serial ports (&man.sio.4;
+	driver)</para>
+
+      &hwlist.uart;
+
+      &hwlist.scc;
+
+      <para>[&arch.amd64;, &arch.i386;] AST 4 port serial card using
+	shared IRQ</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>ARNET 8 port serial card using shared IRQ</para>
+	</listitem>
+
+	<listitem>
+	  <para>ARNET (now Digiboard) Sync 570/i high-speed
+	    serial</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>[&arch.i386;] Boca multi-port serial cards</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>Boca BB1004 4-Port serial card (Modems
+	    <emphasis>not</emphasis> supported)</para>
+	</listitem>
+
+	<listitem>
+	  <para>Boca IOAT66 6-Port serial card (Modems
+	    supported)</para>
+	</listitem>
+
+	<listitem>
+	  <para>Boca BB1008 8-Port serial card (Modems
+	    <emphasis>not</emphasis> supported)</para>
+	</listitem>
+
+	<listitem>
+	  <para>Boca BB2016 16-Port serial card (Modems
+	    supported)</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>[&arch.i386;] Comtrol Rocketport card (&man.rp.4;
+	driver)</para>
+
+      <para>[&arch.i386;] Cyclades Cyclom-Y serial board (&man.cy.4;
+	driver)</para>
+
+      <para>[&arch.i386;] STB 4 port card using shared IRQ</para>
+
+      <para>[&arch.amd64;, &arch.i386;] PCI-Based multi-port serial
+	boards (&man.puc.4; driver)</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Actiontech 56K PCI</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Avlab Technology, PCI IO
+	    2S and PCI IO 4S</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Comtrol RocketPort
+	    550</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Decision Computers PCCOM
+	    4-port serial and dual port RS232/422/485</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Dolphin Peripherals
+	    4025/4035/4036</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] IC Book Labs Dreadnought
+	    16x Lite and Pro</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Lava Computers
+	    2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Middle Digital, Weasle
+	    serial port</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Moxa Industio CP-114,
+	    Smartio C104H-PCI and C168H/PCI</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] NEC PK-UG-X001 and
+	    PK-UG-X008</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Netmos NM9835
+	    PCI-2S-550</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Oxford Semiconductor
+	    OX16PCI954 PCI UART</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Syba Tech SD-LAB
+	    PCI-4S2P-550-ECP</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] SIIG Cyber I/O PCI
+	    16C550/16C650/16C850</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] SIIG Cyber 2P1S PCI
+	    16C550/16C650/16C850</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] SIIG Cyber 2S1P PCI
+	    16C550/16C650/16C850</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] SIIG Cyber 4S PCI
+	    16C550/16C650/16C850</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] SIIG Cyber Serial (Single
+	    and Dual) PCI 16C550/16C650/16C850</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Syba Tech
+	    Ltd. PCI-4S2P-550-ECP</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Titan PCI-200H and
+	    PCI-800H</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] US Robotics (3Com) 3CP5609
+	    modem</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] VScom PCI-400 and
+	    PCI-800</para>
+	</listitem>
+      </itemizedlist>
+
+      &hwlist.rc;
+
+    </sect2>
+
+    <sect2 xml:id="sound">
+      <title>Sound Devices</title>
+
+      &hwlist.snd.ad1816;
+
+      &hwlist.snd.als4000;
+
+      &hwlist.snd.atiixp;
+
+      &hwlist.snd.audiocs;
+
+      &hwlist.snd.cmi;
+
+      &hwlist.snd.cs4281;
+
+      &hwlist.snd.csa;
+
+      &hwlist.snd.ds1;
+
+      &hwlist.snd.emu10k1;
+
+      &hwlist.snd.emu10kx;
+
+      &hwlist.snd.envy24;
+
+      &hwlist.snd.envy24ht;
+
+      &hwlist.snd.es137x;
+
+      &hwlist.snd.ess;
+
+      &hwlist.snd.fm801;
+
+      &hwlist.snd.gusc;
+
+      &hwlist.snd.hda;
+
+      &hwlist.snd.hdspe;
+
+      &hwlist.snd.ich;
+
+      &hwlist.snd.maestro;
+
+      &hwlist.snd.maestro3;
+
+      &hwlist.snd.mss;
+
+      &hwlist.snd.neomagic;
+
+      &hwlist.snd.sbc;
+
+      &hwlist.snd.solo;
+
+      &hwlist.snd.spicds;
+
+      &hwlist.snd.t4dwave;
+
+      &hwlist.snd.via8233;
+
+      &hwlist.snd.via82c686;
+
+      &hwlist.snd.vibes;
+
+    </sect2>
+
+    <sect2 xml:id="camera">
+      <title>Camera and Video Capture Devices</title>
+
+      &hwlist.bktr;
+
+      <para>[&arch.i386;] Connectix QuickCam</para>
+    </sect2>
+
+    <sect2 xml:id="usb">
+      <title>USB Devices</title>
+
+      <para>[&arch.amd64;, &arch.i386;] A
+	range of USB peripherals are supported; devices known to work
+	are listed in this section.  Owing to the generic nature of
+	most USB devices, with some exceptions any device of a given
+	class will be supported, even if not explicitly listed
+	here.</para>
+
+      <note>
+	<para>[&arch.amd64;, &arch.i386;]
+	  USB Ethernet adapters can be found in the section listing
+	  <link linkend="ethernet">Ethernet
+	    interfaces</link>.</para>
+      </note>
+
+      <note>
+	<para>[&arch.amd64;, &arch.i386;] USB Bluetooth adapters can
+	  be found in <link linkend="bluetooth">Bluetooth</link>
+	  section.</para>
+      </note>
+
+      &hwlist.ohci;
+
+      &hwlist.uhci;
+
+      <para>[&arch.amd64;, &arch.i386;] USB
+	2.0 controllers using the EHCI interface (&man.ehci.4;
+	driver)</para>
+
+      <para>[&arch.amd64;, &arch.i386;] Hubs</para>
+
+      <para>[&arch.amd64;, &arch.i386;] Keyboards (&man.ukbd.4;
+	driver)</para>
+
+      <para>[&arch.amd64;, &arch.i386;] Miscellaneous</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>Assist Computer Systems PC Camera C-M1</para>
+	</listitem>
+
+	<listitem>
+	  <para>ActiveWire I/O Board</para>
+	</listitem>
+
+	<listitem>
+	  <para>Creative Technology Video Blaster WebCam Plus</para>
+	</listitem>
+
+	<listitem>
+	  <para>D-Link DSB-R100 USB Radio (&man.ufm.4; driver)</para>
+	</listitem>
+
+	<listitem>
+	  <para>Mirunet AlphaCam Plus</para>
+	</listitem>
+      </itemizedlist>
+
+      &hwlist.urio;
+
+      &hwlist.umodem;
+
+      <para>[&arch.amd64;, &arch.i386;] Mice (&man.ums.4;
+	driver)</para>
+
+      &hwlist.ulpt;
+
+      &hwlist.ubsa;
+
+      &hwlist.ubser;
+
+      &hwlist.uftdi;
+
+      &hwlist.uplcom;
+
+      &hwlist.umct;
+
+      &hwlist.umass;
+
+      <para>[&arch.amd64;, &arch.i386;] Audio Devices
+	(&man.uaudio.4; driver)</para>
+
+      &hwlist.uvisor;
+    </sect2>
+
+    <sect2 xml:id="firewire">
+      <title>IEEE 1394 (Firewire) Devices</title>
+
+      &hwlist.fwohci;
+
+      <para>[&arch.amd64;, &arch.i386;, &arch.sparc64;] Serial Bus
+	Protocol 2 (SBP-2) storage devices (&man.sbp.4; driver)</para>
+    </sect2>
+
+    <sect2 xml:id="bluetooth">
+      <title>Bluetooth Devices</title>
+
+      &hwlist.ng.bt3c;
+
+      &hwlist.ng.ubt;
+    </sect2>
+
+    <sect2 xml:id="crypto-accel">
+      <title>Cryptographic Accelerators</title>
+
+      &hwlist.hifn;
+
+      &hwlist.safe;
+
+      &hwlist.ubsec;
+    </sect2>
+
+    <sect2 xml:id="misc">
+      <title>Miscellaneous</title>
+
+      <para>[&arch.amd64;, &arch.i386;] FAX-Modem/PCCARD</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>MELCO IGM-PCM56K/IGM-PCM56KH</para>
+	</listitem>
+
+	<listitem>
+	  <para>Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD
+	    terminal)</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>[&arch.amd64;, &arch.i386;] Floppy drives
+	(&man.fdc.4; driver)</para>
+
+      <para>[&arch.amd64;, &arch.i386;] VGA-compatible video cards
+	(&man.vga.4; driver)</para>
+
+      <note>
+	<para>Information regarding specific video cards and
+	  compatibility with <application>Xorg</application> can be
+	  found at <uri
+	    xlink:href="http://www.x.org/">http://www.x.org/</uri>.</para>
+      </note>
+
+      <para>[&arch.amd64;, &arch.i386;] Keyboards including:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>[&arch.i386;] AT-style keyboards (&man.atkbd.4;
+	    driver)</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] PS/2 keyboards
+	    (&man.atkbd.4; driver)</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;]
+	    USB keyboards (&man.ukbd.4; driver)</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>[&arch.amd64;, &arch.i386;]
+	Pointing devices including:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] Bus mice and
+	    compatible devices (&man.mse.4; driver)</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;] PS/2 mice and compatible
+	    devices, including many laptop pointing devices
+	    (&man.psm.4; driver)</para>
+	</listitem>
+
+	<listitem>
+	  <para>Serial mice and compatible devices</para>
+	</listitem>
+
+	<listitem>
+	  <para>[&arch.amd64;, &arch.i386;]
+	    USB mice (&man.ums.4; driver)</para>
+	</listitem>
+      </itemizedlist>
+
+      <note>
+	<para>&man.moused.8; has more information on using pointing
+	  devices with &os;.  Information on using pointing devices
+	  with <application>Xorg</application> can be found at <uri
+	    xlink:href="http://www.x.org/">http://www.x.org/</uri>.</para>
+      </note>
+
+      <para>[&arch.amd64;, &arch.i386;] <quote>PC standard</quote>
+	parallel ports (&man.ppc.4; driver)</para>
+
+      <para>[&arch.i386;, &arch.amd64;] PC-compatible joysticks
+	(&man.joy.4; driver)</para>
+
+      <para>[&arch.i386;] PHS Data Communication Card/PCCARD</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>NTT DoCoMo P-in Comp@ct</para>
+	</listitem>
+
+	<listitem>
+	  <para>Panasonic KX-PH405</para>
+	</listitem>
+
+	<listitem>
+	  <para>SII MC-P200</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>[&arch.i386;] Xilinx XC6200-based reconfigurable hardware
+	cards compatible with the HOT1 from <link
+	  xlink:href="http://www.vcc.com/">Virtual Computers</link>
+	(xrpu driver).</para>
+    </sect2>
+  </sect1>
+</article>
diff --git a/en_US.ISO8859-1/htdocs/releases/12.1R/installation/Makefile b/en_US.ISO8859-1/htdocs/releases/12.1R/installation/Makefile
new file mode 100644
index 0000000000..5d7fbee29d
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/releases/12.1R/installation/Makefile
@@ -0,0 +1,12 @@
+# $FreeBSD$
+
+.if exists(../Makefile.inc)
+.include "../Makefile.inc"
+.endif
+
+DOC=			installation
+FORMATS?=		html txt
+INSTALL_COMPRESSED?=	gz
+INSTALL_ONLY_COMPRESSED=
+
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/htdocs/releases/12.1R/installation/installation.xml b/en_US.ISO8859-1/htdocs/releases/12.1R/installation/installation.xml
new file mode 100644
index 0000000000..ee3e451a2f
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/releases/12.1R/installation/installation.xml
@@ -0,0 +1,125 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+"../../../../../share/xml/freebsd50.dtd" [
+<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "../share/xml/release.ent">
+ %release;
+<!ENTITY local.rel "12.1">
+]>
+<article xmlns="http://docbook.org/ns/docbook"
+  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
+  xml:id="top">
+
+  <info>
+    <title>&os; &release.current; Installation
+      Instructions</title>
+
+    <author>
+      <orgname>The &os; Project</orgname>
+    </author>
+
+    <pubdate>$FreeBSD$</pubdate>
+
+    <copyright>
+      <year>2019</year>
+      <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
+	Project</holder>
+    </copyright>
+
+    <legalnotice xml:id="trademarks" role="trademarks">
+      &tm-attrib.freebsd;
+      &tm-attrib.intel;
+      &tm-attrib.sparc;
+      &tm-attrib.general;
+    </legalnotice>
+
+    <abstract>
+      <para>This article gives some brief instructions on installing
+	&os; &release.current; and upgrading the systems running
+	earlier releases.</para>
+    </abstract>
+  </info>
+
+  <sect1 xml:id="install">
+    <title>Installing &os;</title>
+
+    <para>The <uri
+	xlink:href="&url.books.handbook;/bsdinstall.html">Installing
+	&os;</uri> chapter of the <uri
+	xlink:href="&url.books.handbook;/">&os; Handbook</uri>
+      provides more in-depth information about the installation
+      program itself, including a guided walk-through with
+      screenshots.</para>
+  </sect1>
+
+  <sect1 xml:id="upgrade">
+    <title>Upgrading &os;</title>
+
+    <para>If you are upgrading from a previous release of &os;, please
+      read <uri
+      xlink:href="http://www.FreeBSD.org/releases/&local.rel;R/relnotes.html#upgrade">upgrading
+      section in the Release Notes</uri> for notable
+      incompatibilities carefully.</para>
+
+    <sect2 xml:id="upgrade-source">
+      <title>Upgrading from Source</title>
+
+      <para>The procedure for doing a source code based update is
+	described in <uri
+	  xlink:href="&url.books.handbook;/makeworld.html">Updating
+	  &os; from Source</uri>.</para>
+
+      <para>For SVN use the <filename>releng/&local.rel;</filename>
+	branch which will be where any upcoming Security Advisories or
+	Errata Notices will be applied.</para>
+    </sect2>
+
+    <sect2 xml:id="upgrade-binary">
+      <title>Upgrading Using <quote>&os; Update</quote></title>
+
+      <para>The &man.freebsd-update.8; utility supports binary
+	upgrades of &arch.i386; and &arch.amd64; systems running
+	earlier FreeBSD releases.  Systems running
+	<literal>11.2-RELEASE</literal> can upgrade as follows:</para>
+
+      <screen>&prompt.root; freebsd-update fetch
+&prompt.root; freebsd-update install</screen>
+
+      <para>Now the &man.freebsd-update.8; utility can fetch bits
+	belonging to &release.current;.  During this process
+	&man.freebsd-update.8; will ask for help in merging
+	configuration files.</para>
+
+      <screen>&prompt.root; freebsd-update upgrade -r &local.rel;-RELEASE</screen>
+
+      <screen>&prompt.root; freebsd-update install</screen>
+
+      <para>The system must now be rebooted with the newly installed
+	kernel before the non-kernel components are updated.</para>
+
+      <screen>&prompt.root; shutdown -r now</screen>
+
+      <para>After rebooting, &man.freebsd-update.8; needs to be run
+	again to install the new userland components:</para>
+
+      <screen>&prompt.root; freebsd-update install</screen>
+
+      <para>At this point, users of systems being upgraded from
+	earlier &os; releases will be prompted by
+	&man.freebsd-update.8; to rebuild all third-party applications
+	(e.g., ports installed from the ports tree) due to updates in
+	system libraries.</para>
+
+      <para>After updating installed third-party applications (and
+	again, only if &man.freebsd-update.8; printed a message
+	indicating that this was necessary), run
+	&man.freebsd-update.8; again so that it can delete the old (no
+	longer used) system libraries:</para>
+
+      <screen>&prompt.root; freebsd-update install</screen>
+
+      <para>Finally, reboot into &release.current;</para>
+
+      <screen>&prompt.root; shutdown -r now</screen>
+    </sect2>
+  </sect1>
+</article>
diff --git a/en_US.ISO8859-1/htdocs/releases/12.1R/readme/Makefile b/en_US.ISO8859-1/htdocs/releases/12.1R/readme/Makefile
new file mode 100644
index 0000000000..3683dfea47
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/releases/12.1R/readme/Makefile
@@ -0,0 +1,12 @@
+# $FreeBSD$
+
+.if exists(../Makefile.inc)
+.include "../Makefile.inc"
+.endif
+
+DOC=			readme
+FORMATS?=		html txt
+INSTALL_COMPRESSED?=	gz
+INSTALL_ONLY_COMPRESSED=
+
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/htdocs/releases/12.1R/readme/readme.xml b/en_US.ISO8859-1/htdocs/releases/12.1R/readme/readme.xml
new file mode 100644
index 0000000000..d39a537e8f
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/releases/12.1R/readme/readme.xml
@@ -0,0 +1,434 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+"../../../../../share/xml/freebsd50.dtd" [
+<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "../share/xml/release.ent">
+ %release;
+]>
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     End:
+-->
+<article xmlns="http://docbook.org/ns/docbook"
+  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
+
+  <info>
+    <title>&os; &release.current; README</title>
+
+    <author>
+      <orgname>The &os; Project</orgname>
+    </author>
+
+    <pubdate>$FreeBSD$</pubdate>
+
+    <copyright>
+      <year>2000</year>
+      <year>2001</year>
+      <year>2002</year>
+      <year>2003</year>
+      <year>2004</year>
+      <year>2005</year>
+      <year>2006</year>
+      <year>2007</year>
+      <year>2008</year>
+      <year>2009</year>
+      <year>2010</year>
+      <year>2011</year>
+      <year>2012</year>
+      <year>2013</year>
+      <year>2014</year>
+      <year>2015</year>
+      <year>2016</year>
+      <year>2017</year>
+      <year>2018</year>
+      <year>2019</year>
+      <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
+	Project</holder>
+    </copyright>
+
+    <legalnotice xml:id="trademarks" role="trademarks">
+      &tm-attrib.freebsd;
+      &tm-attrib.intel;
+      &tm-attrib.opengroup;
+      &tm-attrib.sparc;
+      &tm-attrib.general;
+    </legalnotice>
+
+    <abstract>
+      <para>This document gives a brief introduction to &os;
+	&release.current;.  It includes some information on how to
+	obtain &os;, a listing of various ways to contact the &os;
+	Project, and pointers to some other sources of
+	information.</para>
+    </abstract>
+  </info>
+
+  <sect1 xml:id="intro">
+    <title>Introduction</title>
+
+    <para>This distribution is a &release.type; of &os;
+      &release.current;, the latest point along the &release.branch;
+      branch.</para>
+
+    <sect2>
+      <title>About &os;</title>
+
+      <para>&os; is an operating system based on 4.4 BSD Lite for
+	AMD64 and Intel EM64T based PC hardware (&arch.amd64;), Intel,
+	AMD, Cyrix or NexGen <quote>x86</quote> based PC hardware
+	(&arch.i386;), and &ultrasparc; machines (&arch.sparc64;).
+	Versions for the &arm; (&arch.arm;), &mips; (&arch.mips;), and
+	&powerpc; (&arch.powerpc;) architectures are currently under
+	development as well.  &os; works with a wide variety of
+	peripherals and configurations and can be used for everything
+	from software development to games to Internet Service
+	Provision.</para>
+
+      <para>This release of &os; contains everything you need to run
+	such a system, including full source code for the kernel and
+	all utilities in the base distribution.  With the source
+	distribution installed, you can literally recompile the entire
+	system from scratch with one command, making it ideal for
+	students, researchers, or users who simply want to see how it
+	all works.</para>
+
+      <para>A large collection of third-party ported software (the
+	<quote>Ports Collection</quote>) is also provided to make it
+	easy to obtain and install all your favorite traditional
+	&unix; utilities for &os;.  Each <quote>port</quote> consists
+	of a set of scripts to retrieve, configure, build, and install
+	a piece of software, with a single command.  Over
+	&os.numports; 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;.  Most ports are also
+	available as pre-compiled <quote>packages</quote>, which can
+	be quickly installed from the installation program.</para>
+    </sect2>
+
+    <sect2>
+      <title>Target Audience</title>
+
+      <para releasetype="current">This &release.type; is aimed
+	primarily at early adopters and various other users who want
+	to get involved with the ongoing development of &os;.  While
+	the &os; development team tries its best to ensure that each
+	&release.type; works as advertised, &release.branch; is very
+	much a work-in-progress.</para>
+
+      <para releasetype="current">The basic requirements for using
+	this &release.type; are technical proficiency with &os; and an
+	understanding of the ongoing development process of &os;
+	&release.branch; (as discussed on the &a.current;).</para>
+
+      <para releasetype="current">For those more interested in doing
+	business with &os; than in experimenting with new &os;
+	technology, formal releases (such as &release.prev.stable;)
+	are frequently more appropriate.  Releases undergo a period of
+	testing and quality assurance checking to ensure high
+	reliability and dependability.</para>
+
+      <para releasetype="snapshot">This &release.type; is aimed
+	primarily at early adopters and various other users who want
+	to get involved with the ongoing development of &os;.  While
+	the &os; development team tries its best to ensure that each
+	&release.type; works as advertised, &release.branch; is very
+	much a work-in-progress.</para>
+
+      <para releasetype="snapshot">The basic requirements for using
+	this &release.type; are technical proficiency with &os; and an
+	understanding of the ongoing development process of &os;
+	&release.branch; (as discussed on the &a.current;).</para>
+
+      <para releasetype="snapshot">For those more interested in doing
+	business with &os; than in experimenting with new &os;
+	technology, formal releases (such as &release.prev.stable;)
+	are frequently more appropriate.  Releases undergo a period of
+	testing and quality assurance checking to ensure high
+	reliability and dependability.</para>
+
+      <para releasetype="release">This &release.type; of &os; is
+	suitable for all users.  It has undergone a period of testing
+	and quality assurance checking to ensure the highest
+	reliability and dependability.</para>
+    </sect2>
+  </sect1>
+
+  <sect1 xml:id="obtain">
+    <title>Obtaining &os;</title>
+
+    <para>&os; may be obtained in a variety of ways.  This section
+      focuses on those ways that are primarily useful for obtaining a
+      complete &os; distribution, rather than updating an existing
+      installation.</para>
+
+    <sect2>
+      <title>CDROM and DVD</title>
+
+      <para>&os; -RELEASE distributions may be ordered on CDROM or DVD
+	from several publishers.  This is frequently the most
+	convenient way to obtain &os; for new installations, as it
+	provides a convenient way to quickly reinstall the system if
+	necessary.  Some distributions include some of the optional,
+	precompiled <quote>packages</quote> from the &os; Ports
+	Collection, or other extra material.</para>
+
+      <para>A list of the CDROM and DVD publishers known to the
+	project are listed in the <link
+	  xlink:href="&url.books.handbook;/mirrors.html"><quote>Obtaining
+	    &os;</quote></link> appendix to the Handbook.</para>
+    </sect2>
+
+    <sect2>
+      <title>FTP</title>
+
+      <para>You can use FTP to retrieve &os; and any or all of its
+	optional packages from <uri
+	  xlink:href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</uri>,
+	which is the official &os; release site, or any of its
+	<quote>mirrors</quote>.</para>
+
+      <para>Lists of locations that mirror &os; can be found in the
+	<link xlink:href="&url.books.handbook;/mirrors-ftp.html">FTP
+	Sites</link> section of the Handbook.
+	Finding a close (in networking terms) mirror from which to
+	download the distribution is highly recommended.</para>
+
+      <para>Additional mirror sites are always welcome.  Contact
+	<email>freebsd-admin@FreeBSD.org</email> for more details on
+	becoming an official mirror site.  You can also find useful
+	information for mirror sites at the <link
+	  xlink:href="&url.articles.hubs;/">Mirroring &os;</link>
+	article.</para>
+
+      <para>Mirrors generally contain the ISO images generally used to
+	create a CDROM of a &os; release.  They usually also contain
+	floppy disk images (for applicable platforms), as well as the
+	files necessary to do an installation over the network.
+	Finally mirrors sites usually contain a set of packages for
+	the most current release.</para>
+    </sect2>
+  </sect1>
+
+  <sect1 xml:id="contacting">
+    <title>Contacting the &os; Project</title>
+
+    <sect2>
+      <title>Email and Mailing Lists</title>
+
+      <para>For any questions or general technical support issues,
+	please send mail to the &a.questions;.</para>
+
+      <para>If you're tracking the &release.branch; 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>
+
+      <para>Being a largely-volunteer effort, the &os; Project is
+	always happy to have extra hands willing to help&mdash;there
+	are already far more desired enhancements than there is time
+	to implement them.  To contact the developers on technical
+	matters, or with offers of help, please send mail to the
+	&a.hackers;.</para>
+
+      <para>Please note that these mailing lists can experience
+	<emphasis>significant</emphasis> amounts of traffic.  If you
+	have slow or expensive mail access, or are only interested in
+	keeping up with major &os; 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.  Visit the <link
+	  xlink:href="&url.base;/mailman/listinfo">&os; Mailman Info
+	  Page</link>.  This will give you more information on joining
+	the various lists, accessing archives, etc.  There are
+	a number of mailing lists targeted at special interest groups
+	not mentioned here; more information can be obtained either
+	from the Mailman pages or the <link
+	  xlink:href="&url.base;/support.html#mailing-list">mailing
+	  lists section</link> of the &os; Web site.</para>
+
+      <important>
+	<para>Do <emphasis>not</emphasis> send email to the lists
+	  asking to be subscribed.  Use the Mailman interface
+	  instead.</para>
+      </important>
+    </sect2>
+
+    <sect2>
+      <title>Submitting Problem Reports</title>
+
+      <para>Suggestions, bug reports and contributions of code are
+	always valued&mdash;please do not hesitate to report any
+	problems you may find.  Bug reports with attached fixes are of
+	course even more welcome.</para>
+
+      <para>The preferred method to submit bug reports from a machine
+	with Internet connectivity is to use the
+	<application>Bugzilla</application> bug tracker.
+	<quote>Problem Reports</quote> (PRs) submitted in this way
+	will be filed and their progress tracked; the &os; developers
+	will do their best to respond to all reported bugs as soon as
+	possible.  <link
+	  xlink:href="https://bugs.FreeBSD.org/search/">A list of all
+	  active PRs</link> is available on the &os; Web site; this
+	list is useful to see what potential problems other users have
+	encountered.</para>
+
+      <para>Note that &man.send-pr.1; is deprecated.</para>
+
+      <para>For more information, <link
+	  xlink:href="&url.articles.problem-reports;/"><quote>Writing
+	    &os; Problem Reports</quote></link>, available on the &os;
+	Web site, has a number of helpful hints on writing and
+	submitting effective problem reports.</para>
+    </sect2>
+  </sect1>
+
+  <sect1 xml:id="seealso">
+    <title>Further Reading</title>
+
+    <para>There are many sources of information about &os;; some are
+      included with this distribution, while others are available
+      on-line or in print versions.</para>
+
+    <sect2 xml:id="release-docs">
+      <title>Release Documentation</title>
+
+      <para>A number of other files provide more specific information
+	about this &release.type; distribution.  These files are
+	provided in various formats.  Most distributions will include
+	both ASCII text (<filename>.TXT</filename>) and HTML
+	(<filename>.HTM</filename>) renditions.  Some distributions
+	may also include other formats such as Portable Document
+	Format (<filename>.PDF</filename>).</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para><filename>README.TXT</filename>: This file, which
+	    gives some general information about &os; as well as some
+	    cursory notes about obtaining a distribution.</para>
+	</listitem>
+
+	<listitem>
+	  <para><filename>RELNOTES.TXT</filename>: The release notes,
+	    showing what's new and different in &os; &release.current;
+	    compared to the previous release (&os;
+	    &release.prev;).</para>
+	</listitem>
+
+	<listitem>
+	  <para><filename>HARDWARE.TXT</filename>: The hardware
+	    compatibility 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, which is principally applicable to releases (as
+	    opposed to snapshots).  It is important to consult this
+	    file before installing a release of &os;, as it contains
+	    the latest information on problems which have been found
+	    and fixed since the release was created.</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>On platforms that support &man.bsdinstall.8; (currently
+	&arch.amd64;, &arch.i386;, and &arch.sparc64;), these
+	documents are generally available via the Documentation menu
+	during installation.  Once the system is installed, you can
+	revisit this menu by re-running the &man.bsdinstall.8;
+	utility.</para>
+
+      <note>
+	<para>It is extremely important to read the errata for any
+	  given release before installing it, to learn about any
+	  <quote>late-breaking news</quote> or post-release problems.
+	  The errata file accompanying each release (most likely right
+	  next to this file) is already out of date by definition, but
+	  other copies are kept updated on the Internet and should be
+	  consulted as the <quote>current errata</quote> for this
+	  release.  These other copies of the errata are located at
+	  <uri
+	    xlink:href="&url.base;/releases/">&url.base;/releases/</uri>
+	  (as well as any sites which keep up-to-date mirrors of this
+	  location).</para>
+      </note>
+    </sect2>
+
+    <sect2>
+      <title>Manual Pages</title>
+
+      <para>As with almost all &unix; like operating systems, &os;
+	comes with a set of on-line manual pages, accessed through the
+	&man.man.1; command or through the <link
+	  xlink:href="http://www.FreeBSD.org/cgi/man.cgi">hypertext
+	  manual pages gateway</link> on the &os; Web site.  In
+	general, the manual pages provide information on the different
+	commands and APIs available to the &os; user.</para>
+
+      <para>In some cases, manual pages are written to give
+	information on particular topics.  Notable examples of such
+	manual pages are &man.tuning.7; (a guide to performance
+	tuning), &man.security.7; (an introduction to &os; security),
+	and &man.style.9; (a style guide to kernel coding).</para>
+    </sect2>
+
+    <sect2>
+      <title>Books and Articles</title>
+
+      <para>Two highly-useful collections of &os;-related information,
+	maintained by the &os; Project, are the &os; Handbook and &os;
+	FAQ (Frequently Asked Questions document).  On-line versions
+	of the <link
+	  xlink:href="&url.books.handbook;/">Handbook</link> and <link
+	  xlink:href="&url.books.faq;/">FAQ</link> are always
+	available from the <link
+	  xlink:href="&url.base;/docs.html">&os; Documentation
+	  page</link> or its mirrors.  If you install the
+	<filename>doc</filename> distribution set, you can use a Web
+	browser to read the Handbook and FAQ locally.  In particular,
+	note that the Handbook contains a step-by-step guide to
+	installing &os;.</para>
+
+      <para>A number of on-line books and articles, also maintained by
+	the &os; Project, cover more-specialized, &os;-related topics.
+	This material spans a wide range of topics, from effective use
+	of the mailing lists, to dual-booting &os; with other
+	operating systems, to guidelines for new committers.  Like the
+	Handbook and FAQ, these documents are available from the &os;
+	Documentation Page or in the <filename>doc</filename>
+	distribution set.</para>
+
+      <para>A listing of other books and documents about &os; can be
+	found in the <link
+	  xlink:href="&url.books.handbook;/bibliography.html">bibliography</link>
+	of the &os; Handbook.  Because of &os;'s strong &unix;
+	heritage, many other articles and books written for &unix;
+	systems are applicable as well, some of which are also listed
+	in the bibliography.</para>
+    </sect2>
+  </sect1>
+
+  <sect1 xml:id="acknowledgements">
+    <title>Acknowledgments</title>
+
+    <para>&os; represents the cumulative work of many hundreds, if not
+      thousands, of individuals from around the world who have worked
+      countless hours to bring about this &release.type;.  For
+      a complete list of &os; developers and contributors, please see
+      <link
+	xlink:href="&url.articles.contributors;/"><quote>Contributors
+	  to &os;</quote></link> on the &os; Web site or any of its
+      mirrors.</para>
+
+    <para>Special thanks also go to the many thousands of &os; users
+      and testers all over the world, without whom this &release.type;
+      simply would not have been possible.</para>
+  </sect1>
+</article>