diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml
index 546decb6c6..11ebe38646 100644
--- a/en_US.ISO8859-1/books/faq/book.xml
+++ b/en_US.ISO8859-1/books/faq/book.xml
@@ -1,6431 +1,6431 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
 	"http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd" [
 <!ENTITY bibliography SYSTEM "../../../share/xml/bibliography.xml">
 <!ENTITY rel.numbranch "3">  <!-- number of branches that follow in this list -->
 <!ENTITY rel.head "<emphasis xmlns='http://docbook.org/ns/docbook'>13-CURRENT</emphasis>">
 <!ENTITY rel.head.relx "13.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">
 <!ENTITY rel.head.releng "<symbol xmlns='http://docbook.org/ns/docbook'>head/</symbol>">
 <!ENTITY rel.relx "12.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">
 <!ENTITY rel.stable "<emphasis xmlns='http://docbook.org/ns/docbook'>12-STABLE</emphasis>">
 <!ENTITY rel.releng "<symbol xmlns='http://docbook.org/ns/docbook'>stable/12/</symbol>">
 <!ENTITY rel.relengdate "December 2018">
 <!ENTITY rel2.relx "11.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">
 <!ENTITY rel2.stable "<emphasis xmlns='http://docbook.org/ns/docbook'>11-STABLE</emphasis>">
 <!ENTITY rel2.releng "<symbol xmlns='http://docbook.org/ns/docbook'>stable/11/</symbol>">
 <!ENTITY rel2.relengdate "October 2016">
 ]>
 <book xmlns="http://docbook.org/ns/docbook"
   xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
   xml:lang="en">
   <info>
     <title>Frequently Asked Questions for &os;
       &rel2.relx; and &rel.relx;</title>
 
     <author><orgname>The &os; Documentation Project</orgname></author>
 
     <copyright>
       <year>1995</year>
       <year>1996</year>
       <year>1997</year>
       <year>1998</year>
       <year>1999</year>
       <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>
       <year>2020</year>
 
       <holder>The &os; Documentation Project</holder>
     </copyright>
 
     &legalnotice;
 
     <legalnotice xml:id="trademarks" role="trademarks">
       &tm-attrib.freebsd;
       &tm-attrib.adobe;
       &tm-attrib.ibm;
       &tm-attrib.ieee;
       &tm-attrib.intel;
       &tm-attrib.linux;
       &tm-attrib.microsoft;
       &tm-attrib.netbsd;
       &tm-attrib.opengroup;
       &tm-attrib.sgi;
       &tm-attrib.sun;
       &tm-attrib.general;
     </legalnotice>
 
     <releaseinfo>$FreeBSD$</releaseinfo>
 
     <abstract>
       <para>This is the Frequently Asked Questions
 	<acronym>(FAQ)</acronym> for &os; versions
 	&rel.relx; and &rel2.relx;.  Every effort has been made to
 	make this <acronym>FAQ</acronym> as informative as possible;
 	if you have any suggestions as to how it may be improved, send
 	them to the &a.doc;.</para>
 
       <para>The latest version of this document is always available
 	from the <link
 	  xlink:href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">&os;
 	  website</link>.  It may also be downloaded as one large
 	<link xlink:href="book.html">HTML</link> file with HTTP or as
 	a variety of other formats from the <link
 	  xlink:href="https://download.freebsd.org/ftp/doc/">&os; FTP
 	  server</link>.</para>
     </abstract>
   </info>
 
   <chapter xml:id="introduction">
     <title>Introduction</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="what-is-FreeBSD">
 	  <para>What is &os;?</para>
 	</question>
 
 	<answer>
 	  <para>&os; is a modern operating system for desktops,
 	    laptops, servers, and embedded systems with support for a
 	    large number of  <link
 	      xlink:href="https://www.FreeBSD.org/platforms/">platforms</link>.</para>
 
 	  <para>It is based on U.C. Berkeley's
 	    <quote>4.4BSD-Lite</quote> release, with some
 	    <quote>4.4BSD-Lite2</quote> enhancements.  It is also
 	    based indirectly on William Jolitz's port of U.C.
 	    Berkeley's <quote>Net/2</quote> to the &i386;, known as
 	    <quote>386BSD</quote>, though very little of the 386BSD
 	    code remains.</para>
 
 	  <para>&os; is used by companies, Internet Service Providers,
 	    researchers, computer professionals, students and home
 	    users all over the world in their work, education and
 	    recreation.</para>
 
 	  <para>For more detailed information on &os;, refer to the
 	    <link xlink:href="&url.books.handbook;/index.html">&os;
 	      Handbook</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="FreeBSD-goals">
 	  <para>What is the goal of the &os; Project?</para>
 	</question>
 
 	<answer>
 	  <para>The goal of the &os; Project is to provide a stable
 	    and fast general purpose operating system that may be used
 	    for any purpose without strings attached.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="bsd-license-restrictions">
 	  <para>Does the &os; license have any restrictions?</para>
 	</question>
 
 	<answer>
 	  <para>Yes.  Those restrictions do not control how the code
 	    is used, but how to treat the &os; Project itself.
 	    The license itself is available at
 	    <link
 	      xlink:href="https://www.FreeBSD.org/copyright/freebsd-license.html">license</link>
 	    and can be summarized like this:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Do not claim that you wrote this.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Do not sue us if it breaks.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Do not remove or modify the license.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>Many of us have a significant investment in the
 	    project and would certainly not mind a little financial
 	    compensation now and then, but we definitely do not insist
 	    on it.  We believe that our first and foremost
 	    <quote>mission</quote> is to provide code to any and all
 	    comers, and for whatever purpose, so that the code gets
 	    the widest possible use and provides the widest possible
 	    benefit.  This, we believe, is one of the most fundamental
 	    goals of Free Software and one that we enthusiastically
 	    support.</para>
 
 	  <para>Code in our source tree which falls under the <link
 	      xlink:href="https://www.FreeBSD.org/copyright/COPYING">GNU
 	      General Public License (GPL)</link> or <link
 	      xlink:href="https://www.FreeBSD.org/copyright/COPYING.LIB">GNU
 	      Library General Public License (LGPL)</link> comes with
 	    slightly more strings attached, though at least on the
 	    side of enforced access rather than the usual opposite.
 	    Due to the additional complexities that can evolve in the
 	    commercial use of GPL software, we do, however, endeavor
 	    to replace such software with submissions under the more
 	    relaxed <link
 	      xlink:href="https://www.FreeBSD.org/copyright/freebsd-license.html">&os;
 	      license</link> whenever possible.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="replace-current-OS">
 	  <para>Can &os; replace my current operating system?</para>
 	</question>
 
 	<answer>
 	  <para>For most people, yes.  But this question is not quite
 	    that cut-and-dried.</para>
 
 	  <para>Most people do not actually use an operating system.
 	    They use applications.  The applications are what really
 	    use the operating system.  &os; is designed to provide a
 	    robust and full-featured environment for applications.  It
 	    supports a wide variety of web browsers, office suites,
 	    email readers, graphics programs, programming
 	    environments, network servers, and much more.
 	    Most of these applications can be
 	    managed through the <link
 	      xlink:href="https://www.FreeBSD.org/ports/">Ports
 	      Collection</link>.</para>
 
 	  <para>If an application is only available on one operating
 	    system, that operating system cannot just be replaced.
 	    Chances are, there is a very similar application on &os;,
 	    however.  As a solid office or Internet server or a
 	    reliable workstation, &os; will almost certainly do
 	    everything you need.  Many computer users across the
 	    world, including both novices and experienced &unix;
 	    administrators, use &os; as their only desktop operating
 	    system.</para>
 
 	  <para>Users migrating to &os; from another &unix;-like
             environment will find &os; to be similar.
             &windows; and &macos; users may be interested in instead
             using <link
-              xlink:href="https://www.furybsd.org/">FuryBSD</link>,
+              xlink:href="https://ghostbsd.org/">GhostBSD</link>,
             <link
-              xlink:href="https://ghostbsd.org/">GhostBSD</link>
-            or <link
               xlink:href="https://www.midnightbsd.org/">MidnightBSD</link>
+	    or <link
+              xlink:href="https://nomadbsd.org/">NomadBSD</link>
             three &os;-based desktop distributions.  Non-&unix; users
             should expect to invest some additional time learning the
             &unix; way of doing things.  This <acronym>FAQ</acronym>
             and the <link
               xlink:href="&url.books.handbook;/index.html">&os;
             Handbook</link> are excellent places to start.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="why-called-FreeBSD">
 	  <para>Why is it called &os;?</para>
 	</question>
 
 	<answer>
 	  <itemizedlist>
 	    <listitem>
 	      <para>It may be used free of charge, even by commercial
 		users.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Full source for the operating system is freely
 		available, and the minimum possible restrictions have
 		been placed upon its use, distribution and
 		incorporation into other work (commercial or
 		non-commercial).</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Anyone who has an improvement or bug fix is free
 		to submit their code and have it added to the source
 		tree (subject to one or two obvious
 		provisions).</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>It is worth pointing out that the word
 	    <quote>free</quote> is being used in two ways here: one
 	    meaning <quote>at no cost</quote> and the other meaning
 	    <quote>do whatever you like</quote>.  Apart from
 	    one or two things you <emphasis>cannot</emphasis> do with
 	    the &os; code, for example pretending you wrote it, you
 	    can really do whatever you like with it.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="differences-to-other-bsds">
 	  <para>What are the differences between &os; and NetBSD,
 	    OpenBSD, and other open source BSD operating
 	    systems?</para>
 	</question>
 
 	<answer>
 	  <para>James Howard wrote a good explanation of the history
 	    and differences between the various projects, called <link
 	      xlink:href="https://jameshoward.us/archive/the-bsd-family-tree/">The
 	      BSD Family Tree</link> which goes a fair way to
 	    answering this question.  Some of the information is out
 	    of date, but the history portion in particular remains
 	    accurate.</para>
 
 	  <para>Most of the BSDs share patches and code, even today.
 	    All of the BSDs have common ancestry.</para>
 
 	  <para>The design goals of &os; are described in <xref
 	      linkend="FreeBSD-goals"/>, above.  The design goals of
 	    the other most popular BSDs may be summarized as
 	    follows:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>OpenBSD aims for operating system security above
 		all else.  The OpenBSD team wrote &man.ssh.1; and
 		&man.pf.4;, which have both been ported to
 		&os;.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>NetBSD aims to be easily ported to other hardware
 		platforms.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>DragonFly&nbsp;BSD is a fork of &os;&nbsp;4.8 that
 		has since developed many interesting features of its
 		own, including the HAMMER file system and support for
 		user-mode <quote>vkernels</quote>.</para>
 	    </listitem>
 	  </itemizedlist>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="latest-version">
 	  <para>What is the latest version of &os;?</para>
 	</question>
 
 	<answer>
 	  <para>At any point in the development of &os;, there can be
 	    multiple parallel branches.  &rel.relx; releases are made
 	    from the &rel.stable; branch, and &rel2.relx; releases are
 	    made from the &rel2.stable; branch.</para>
 
 	  <para>Up until the release of 12.0, the &rel2.relx; series
 	    was the one known as <emphasis>-STABLE</emphasis>.
 	    However, as of &rel.head.relx;, the &rel2.relx; branch
 	    will be designated for an <quote>extended support</quote>
 	    status and receive only fixes for major problems, such as
 	    security-related fixes.
 	    <!--There will be no more releases made from the
 	    &rel2.stable; branch, and it is considered a
 	    <quote>legacy</quote> branch and most current work will only
 	    become a part of &rel.stable; and &rel2.stable;.--></para>
 
 	  <para>Releases are made <link linkend="release-freq">every
 	      few months</link>.  While many people stay more
 	    up-to-date with the &os; sources (see the questions on
 	    <link linkend="current">&os.current;</link> and <link
 	      linkend="stable">&os.stable;</link>) than that, doing so
 	    is more of a commitment, as the sources are a moving
 	    target.</para>
 
 	  <para>More information on &os; releases can be found on the
 	    <link
 	      xlink:href="https://www.FreeBSD.org/releng/index.html#release-build">Release
 	      Engineering page</link> and in &man.release.7;.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="current">
 	  <para>What is <emphasis>&os;-CURRENT</emphasis>?</para>
 	</question>
 
 	<answer>
 	  <para><link
 	      xlink:href="&url.books.handbook;/current-stable.html#current">&os.current;</link>
 	    is the development version of the operating system, which
 	    will in due course become the new &os.stable; branch.  As
 	    such, it is really only of interest to developers working
 	    on the system and die-hard hobbyists.  See the <link
 	      xlink:href="&url.books.handbook;/current-stable.html#current">relevant
 	      section</link> in the <link
 	      xlink:href="&url.books.handbook;/index.html">Handbook</link>
 	    for details on running
 	    <emphasis>-CURRENT</emphasis>.</para>
 
 	  <para>Users not familiar with &os; should not use
 	    &os.current;.  This branch sometimes evolves quite quickly
 	    and due to mistake can be un-buildable at times.  People
 	    that use &os.current; are expected to be able to analyze,
 	    debug, and report problems.</para>
 
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="stable">
 	  <para>What is the <emphasis>&os;-STABLE</emphasis>
 	    concept?</para>
 	</question>
 
 	<answer>
 	  <para>
 	    <emphasis>&os;-STABLE</emphasis> is the development branch
 	    from which major releases are made.  Changes go into this
 	    branch at a slower pace and with the general assumption
 	    that they have first been tested in &os;-CURRENT.
 	    However, at any given time, the sources for &os;-STABLE
 	    may or may not be suitable for general use, as it may
 	    uncover bugs and corner cases that were not yet found in
 	    &os;-CURRENT.  Users who do not have the resources to
 	    perform testing should instead run the most recent release
 	    of &os;.
 	    <emphasis>&os;-CURRENT</emphasis>, on the other hand, has
 	    been one unbroken line since 2.0 was released.</para>
 
 	  <para>For more
 	    detailed information on branches see <quote><link
 	      xlink:href="&url.articles.releng;/release-proc.html#rel-branch">&os;
 	      Release Engineering: Creating the Release
 	      Branch</link></quote>, the status of the branches and
 	      the upcoming release schedule can be found on the <link
 	      xlink:href="https://www.FreeBSD.org/releng">Release
 	      Engineering Information</link> page.</para>
 
 	  <para>Version <link
 	      xlink:href="https://download.FreeBSD.org/ftp/releases/amd64/amd64/&rel121.current;-RELEASE/">&rel121.current;</link>
 	    is the latest release from the &rel.stable; branch; it was
 	    released in &rel121.current.date;.  Version <link
 	      xlink:href="https://download.FreeBSD.org/ftp/releases/amd64/amd64/&rel1.current;-RELEASE/">&rel1.current;</link>
 	    is the latest release from the &rel2.stable; branch; it
 	    was released in &rel1.current.date;.</para>
 
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="release-freq">
 	  <para>When are &os; releases made?</para>
 	</question>
 
 	<answer>
 	  <para>The &a.re; releases a new major version of &os; about
 	    every 18 months and a new minor version about every 8
 	    months, on average.  Release dates are announced well in
 	    advance, so that the people working on the system know
 	    when their projects need to be finished and tested.  A
 	    testing period precedes each release, to ensure that the
 	    addition of new features does not compromise the stability
 	    of the release.  Many users regard this caution as one of
 	    the best things about &os;, even though waiting for all
 	    the latest goodies to reach <emphasis>-STABLE</emphasis>
 	    can be a little frustrating.</para>
 
 	  <para>More information on the release engineering process
 	    (including a schedule of upcoming releases) can be found
 	    on the <link
 	      xlink:href="https://www.FreeBSD.org/releng/index.html">release
 	      engineering</link> pages on the &os; Web site.</para>
 
 	  <para>For people who need or want a little more excitement,
 	    binary snapshots are made weekly as discussed
 	    above.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="snapshot-freq">
 	  <para>When are &os; snapshots made?</para>
 	</question>
 
 	<answer>
 	  <para>&os; <link
 	      xlink:href="&url.base;/snapshots/">snapshot</link>
 	    releases are made based on the current state of the
 	    <emphasis>-CURRENT</emphasis> and
 	    <emphasis>-STABLE</emphasis> branches.  The goals behind
 	    each snapshot release are:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>To test the latest version of the installation
 		software.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>To give people who would like to run
 		<emphasis>-CURRENT</emphasis> or
 		<emphasis>-STABLE</emphasis> but who do not have the
 		time or bandwidth to follow it on a day-to-day basis
 		an easy way of bootstrapping it onto their
 		systems.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>To preserve a fixed reference point for the code
 		in question, just in case we break something really
 		badly later.  (Although Subversion normally prevents
 		anything horrible like this happening.)</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>To ensure that all new features and fixes in need
 		of testing have the greatest possible number of
 		potential testers.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>No claims are made that any
 	    <emphasis>-CURRENT</emphasis> snapshot can be considered
 	    <quote>production quality</quote> for any purpose.
 	    If a stable and fully tested system is needed,
 	    stick to full releases.</para>
 
 	  <para>Snapshot releases are directly available from <link
 	      xlink:href="&url.base;/snapshots/">snapshot</link>.</para>
 
 	  <para>Official snapshots are generated on a regular
 	    basis for all actively developed branches.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="responsible">
 	  <para>Who is responsible for &os;?</para>
 	</question>
 
 	<answer>
 	  <para>The key decisions concerning the &os; project, such as
 	    the overall direction of the project and who is allowed to
 	    add code to the source tree, are made by a <link
 	      xlink:href="&url.base;/administration.html#t-core">core
 	      team</link> of 9 people.  There is a much larger team of
 	    more than 350 <link
 	      xlink:href="&url.articles.contributors;/article.html#staff-committers">committers</link>
 	    who are authorized to make changes directly to the &os;
 	    source tree.</para>
 
 	  <para>However, most non-trivial changes are discussed in
 	    advance in the <link linkend="mailing">mailing
 	      lists</link>, and there are no restrictions on who may
 	    take part in the discussion.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="where-get">
 	  <para>Where can I get &os;?</para>
 	</question>
 
 	<answer>
 	  <para>Every significant release of &os; is available via
 	    anonymous FTP from the <link
 	      xlink:href="https://download.FreeBSD.org/ftp/releases/">&os;
 	      FTP site</link>:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>The latest &rel.stable; release,
 		&rel121.current;-RELEASE can be found in the <link
 		  xlink:href="https://download.FreeBSD.org/ftp/releases/amd64/amd64/&rel121.current;-RELEASE/">&rel121.current;-RELEASE
 		  directory</link>.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><link
 		  xlink:href="&url.base;/snapshots/">Snapshot</link>
 		releases are made monthly for the <link
 		  linkend="current">-CURRENT</link> and <link
 		  linkend="stable">-STABLE</link> branch, these being
 		of service purely to bleeding-edge testers and
 		developers.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>The latest &rel2.stable; release,
 		&rel1.current;-RELEASE can be found in the <link
 		  xlink:href="https://download.FreeBSD.org/ftp/releases/amd64/amd64/&rel1.current;-RELEASE/">&rel1.current;-RELEASE
 		  directory</link>.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>Information about obtaining &os; on CD, DVD, and other
 	    media can be found in <link
 	      xlink:href="&url.books.handbook;/mirrors.html">the
 	      Handbook</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="access-pr">
 	  <para>How do I access the Problem Report database?</para>
 	</question>
 
 	<answer>
 	  <para>The Problem Report database of all user change
 	    requests may be queried by using our web-based PR <link
 	      xlink:href="https://bugs.FreeBSD.org/search/">query</link>
 	    interface.</para>
 
 	  <para>The <link
 	      xlink:href="&url.base;/support/bugreports.html">web-based
 	      problem report submission interface</link> can be used
 	    to submit problem reports through a web browser.</para>
 
 	  <para>Before submitting a problem report, read <link
 	      xlink:href="&url.articles.problem-reports;/article.html">Writing
 	      &os; Problem Reports</link>, an article on how to write
 	    good problem reports.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="support">
     <title>Documentation and Support</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="books">
 	  <para>What good books are there about &os;?</para>
 	</question>
 
 	<answer>
 	  <para>The project produces a wide range of documentation,
 	    available online from this link: <uri
 	      xlink:href="https://www.FreeBSD.org/docs.html">https://www.FreeBSD.org/docs.html</uri>.
 <!-- TODO suppress this until some future time that the bibliography is updated
 	    In addition, the <link
 	      xlink:href="&url.books.handbook;/bibliography.html">the
 	      bibliography in the Handbook</link> reference other
 	    recommended books.
 -->
 	  </para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="doc-formats">
 	  <para>Is the documentation available in other formats, such
 	    as plain text (ASCII), or PDF?</para>
 	</question>
 
 	<answer>
 	  <para>Yes.  The documentation is available in a number of
 	    different formats and compression schemes on the &os; FTP
 	    site, in the <link
 	      xlink:href="https://download.freebsd.org/ftp/doc/">/ftp/doc/</link>
 	    directory.</para>
 
 	  <para>The documentation is categorized in a number of
 	    different ways.  These include:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>The document's name, such as
 		<literal>faq</literal>, or
 		<literal>handbook</literal>.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>The document's language and encoding.  These are
 		based on the locale names found under
 		<filename>/usr/share/locale</filename> on a &os;
 		system.  The current languages and encodings
 		are as follows:</para>
 
 	      <informaltable frame="none" pgwide="1">
 		<tgroup cols="2">
 		  <thead>
 		    <row>
 		      <entry>Name</entry>
 
 		      <entry>Meaning</entry>
 		    </row>
 		  </thead>
 
 		  <tbody>
 		    <row>
 		      <entry><literal>en_US.ISO8859-1</literal></entry>
 
 		      <entry>English (United States)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>bn_BD.ISO10646-1</literal></entry>
 
 		      <entry>Bengali or Bangla (Bangladesh)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>da_DK.ISO8859-1</literal></entry>
 
 		      <entry>Danish (Denmark)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>de_DE.ISO8859-1</literal></entry>
 
 		      <entry>German (Germany)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>el_GR.ISO8859-7</literal></entry>
 
 		      <entry>Greek (Greece)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>es_ES.ISO8859-1</literal></entry>
 
 		      <entry>Spanish (Spain)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>fr_FR.ISO8859-1</literal></entry>
 
 		      <entry>French (France)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>hu_HU.ISO8859-2</literal></entry>
 
 		      <entry>Hungarian (Hungary)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>it_IT.ISO8859-15</literal></entry>
 
 		      <entry>Italian (Italy)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>ja_JP.eucJP</literal></entry>
 
 		      <entry>Japanese (Japan, EUC encoding)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>ko_KR.UTF-8</literal></entry>
 
 		      <entry>Korean (Korea, UTF-8 encoding)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>mn_MN.UTF-8</literal></entry>
 
 		      <entry>Mongolian (Mongolia, UTF-8
 			encoding)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>nl_NL.ISO8859-1</literal></entry>
 
 		      <entry>Dutch (Netherlands)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>pl_PL.ISO8859-2</literal></entry>
 
 		      <entry>Polish (Poland)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>pt_BR.ISO8859-1</literal></entry>
 
 		      <entry>Portuguese (Brazil)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>ru_RU.KOI8-R</literal></entry>
 
 		      <entry>Russian (Russia, KOI8-R encoding)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>tr_TR.ISO8859-9</literal></entry>
 
 		      <entry>Turkish (Turkey)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>zh_CN.UTF-8</literal></entry>
 
 		      <entry>Simplified Chinese (China, UTF-8
 			encoding)</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>zh_TW.UTF-8</literal></entry>
 
 		      <entry>Traditional Chinese (Taiwan, UTF-8
 			encoding)</entry>
 		    </row>
 		  </tbody>
 		</tgroup>
 	      </informaltable>
 
 	      <note>
 		<para>Some documents may not be available in all
 		  languages.</para>
 	      </note>
 	    </listitem>
 
 	    <listitem>
 	      <para>The document's format.  We produce the
 		documentation in a number of different output formats.
 		Each format has its own advantages and disadvantages.
 		Some formats are better suited for online reading,
 		while others are meant to be aesthetically pleasing
 		when printed on paper.  Having the documentation
 		available in any of these formats ensures that our
 		readers will be able to read the parts they are
 		interested in, either on their monitor, or on paper
 		after printing the documents.  The currently available
 		formats are:</para>
 
 	      <informaltable frame="none" pgwide="1">
 		<tgroup cols="2">
 		  <thead>
 		    <row>
 		      <entry>Format</entry>
 
 		      <entry>Meaning</entry>
 		    </row>
 		  </thead>
 
 		  <tbody>
 		    <row>
 		      <entry><literal>html-split</literal></entry>
 
 		      <entry>A collection of small, linked, HTML
 			files.</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>html</literal></entry>
 
 		      <entry>One large HTML file containing the entire
 			document</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>pdf</literal></entry>
 
 		      <entry>Adobe's Portable Document Format</entry>
 		    </row>
 
 		    <row>
 		      <entry><literal>txt</literal></entry>
 
 		      <entry>Plain text</entry>
 		    </row>
 		  </tbody>
 		</tgroup>
 	      </informaltable>
 	    </listitem>
 
 	    <listitem>
 	      <para>The compression and packaging scheme.</para>
 
 	      <orderedlist>
 		<listitem>
 		  <para>Where the format is
 		    <literal>html-split</literal>, the files are
 		    bundled up using &man.tar.1;.  The resulting
 		    <filename>.tar</filename> is then compressed
 		    using the compression schemes detailed in the next
 		    point.</para>
 		</listitem>
 
 		<listitem>
 		  <para>All the other formats generate one file.  For
 		    example,
 		    <filename>article.pdf</filename>,
 		    <filename>book.html</filename>, and so on.</para>
 
 		  <para>These files are then compressed using either
 		    the <literal>zip</literal> or
 		    <literal>bz2</literal> compression schemes.
 		    &man.tar.1; can be used to uncompress these
 		    files.</para>
 
 		  <para>So the PDF version of the Handbook,
 		    compressed using <literal>bzip2</literal> will be
 		    stored in a file called
 		    <filename>book.pdf.bz2</filename> in the
 		    <filename>handbook/</filename> directory.</para>
 		</listitem>
 	      </orderedlist>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>After choosing the format and compression mechanism,
 	    download the
 	    compressed files, uncompress them, and then copy
 	    the appropriate documents into place.</para>
 
 	  <para>For example, the split HTML version of the
 	    <acronym>FAQ</acronym>, compressed using &man.bzip2.1;,
 	    can be found in
 	    <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</filename>
 	    To download and uncompress that file, type:</para>
 
 	  <screen>&prompt.root; <userinput>fetch https://download.freebsd.org/ftp/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</userinput>
 &prompt.root; <userinput>tar xvf book.html-split.tar.bz2</userinput></screen>
 
 	  <para>If the file is compressed,
 	    <application>tar</application> will automatically
 	    detect the appropriate format and decompress it correctly,
 	    resulting in a collection of
 	    <filename>.html</filename> files.  The main one is called
 	    <filename>index.html</filename>, which will contain the
 	    table of contents, introductory material, and links to the
 	    other parts of the document.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="mailing">
 	  <para>Where do I find info on the &os; mailing lists?  What
 	    &os; news groups are available?</para>
 	</question>
 
 	<answer>
 	  <para>Refer to the <link
 	      xlink:href="&url.books.handbook;/eresources.html#eresources-mail">Handbook
 	      entry on mailing-lists</link> and the <link
 	      xlink:href="&url.books.handbook;/eresources-news.html">Handbook
 	      entry on newsgroups</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="irc">
 	  <para>Are there &os; IRC (Internet Relay Chat)
 	    channels?</para>
 	</question>
 
 	<answer>
 	  <para>Yes, most major IRC networks host a &os; chat
 	    channel:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Channel <literal>#FreeBSDhelp</literal> on <link
 		  xlink:href="http://www.efnet.org/index.php">EFNet</link>
 		is a channel dedicated to helping &os; users.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Channel <literal>#FreeBSD</literal> on <link
 		  xlink:href="http://freenode.net/">Freenode</link> is
 		a general help channel with many users at any time.
 		The conversations have been known to run off-topic for
 		a while, but priority is given to users with &os;
 		questions.  Other users can help with
 		the basics, referring to the Handbook whenever
 		possible and providing links for learning more about
 		a particular topic.  This is primarily an English
 		speaking channel, though it does have users from all
 		over the world.  Non-native English speakers should
 		try to ask the question in English first and then
 		relocate to <literal>##freebsd-lang</literal> as
 		appropriate.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Channel <literal>#FreeBSD</literal> on <link
 		  xlink:href="http://www.dal.net/">DALNET</link> is
 		available at <systemitem>irc.dal.net</systemitem> in
 		the US and <systemitem>irc.eu.dal.net</systemitem> in
 		Europe.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Channel <literal>#FreeBSD</literal> on <link
 		  xlink:href="http://www.undernet.org/">UNDERNET</link>
 		is available at
 		<systemitem>us.undernet.org</systemitem> in the US and
 		<systemitem>eu.undernet.org</systemitem> in Europe.
 		Since it is a help channel, be prepared to read the
 		documents you are referred to.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Channel <literal>#FreeBSD</literal> on <link
 		  xlink:href="http://www.rusnet.org.ru/">RUSNET</link>
 		is a Russian language channel dedicated to
 		helping &os; users.  This is also a good place for
 		non-technical discussions.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Channel <literal>#bsdchat</literal> on <link
 		  xlink:href="http://freenode.net/">Freenode</link> is
 		a Traditional Chinese (UTF-8 encoding) language
 		channel dedicated to helping &os; users.
 		This is also a good place for non-technical
 		discussions.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>The &os; wiki has a <link
 	      xlink:href="https://wiki.freebsd.org/IRC/Channels">good
 	      list</link> of IRC channels.</para>
 
 	  <para>Each of these channels are distinct and are not
 	    connected to each other.  Since their chat styles differ,
 	    try each to find one suited to your
 	    chat style.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="forums">
 	  <para>Are there any web based forums to discuss &os;?</para>
 	</question>
 	<answer>
 	  <para>The official &os; forums are located at <link
 	      xlink:href="https://forums.FreeBSD.org/">https://forums.FreeBSD.org/</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="training">
 	  <para>Where can I get commercial &os; training and
 	    support?</para>
 	</question>
 
 	<answer>
 	  <para><link xlink:href="http://www.ixsystems.com">iXsystems,
 	      Inc.</link>, parent company of the <link
 	      xlink:href="http://www.freebsdmall.com/">&os;
 	      Mall</link>, provides commercial &os; and TrueOS
 	    software <link
 	      xlink:href="http://www.ixsystems.com/support">support</link>,
 	    in addition to &os; development and tuning
 	    solutions.</para>
 
 	  <para>BSD Certification Group, Inc. provides system
 	    administration certifications for DragonFly&nbsp;BSD,
 	    &os;, NetBSD, and OpenBSD.  Refer to <link
 	      xlink:href="http://www.BSDCertification.org">their
 	      site</link> for more information.</para>
 
 	  <para>Any other organizations providing training and support
 	    should contact the Project to be listed here.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="install">
     <info>
       <title>Installation</title>
 
       <author>
 	<personname>
 	  <firstname>Nik</firstname>
 	  <surname>Clayton</surname>
 	</personname>
 	<affiliation>
 	  <address>
 	    <email>nik@FreeBSD.org</email>
 	  </address>
 	</affiliation>
       </author>
     </info>
 
     <qandaset>
 
       <qandaentry>
 	<question xml:id="which-architecture">
 	  <para>Which platform should I download? I have a 64
 	    bit capable &intel; CPU,
 	    but I only see <literal>amd64</literal>.</para>
 	</question>
 
 	<answer>
 	  <para>&arch.amd64; is the term &os; uses for 64-bit
 	    compatible x86 architectures (also known as "x86-64" or
 	    "x64").  Most modern computers should use &arch.amd64;.
 	    Older hardware should use &arch.i386;.  When installing
 	    on a non-x86-compatible architecture, select the
 	    platform which best matches the hardware.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="floppy-download">
 	  <para>Which file do I download to get &os;?</para>
 	</question>
 
 	<answer>
 	  <para>On the <link
 	      xlink:href="https://www.freebsd.org/where.html">Getting
 	      &os;</link> page, select <literal>[iso]</literal> next
 	    to the architecture that matches the hardware.</para>
 
 	  <para>Any of the following can be used:</para>
 
 	  <informaltable frame="none" pgwide="1">
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>file</entry>
 		  <entry>description</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><filename>disc1.iso</filename></entry>
 		  <entry>Contains enough to install &os; and
 		    a minimal set of packages.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>dvd1.iso</filename></entry>
 		  <entry>Similar to <filename>disc1.iso</filename>
 		    but with additional packages.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>memstick.img</filename></entry>
 		  <entry>A bootable image sufficient for writing to a
 		    USB stick.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>bootonly.iso</filename></entry>
 		  <entry>A minimal image that requires network access
 		    during installation to completely install
 		    &os;.</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </informaltable>
 
 	  <para>Full instructions on this procedure and a little bit
 	    more about installation issues in general can be found in
 	    the <link
 	      xlink:href="&url.books.handbook;/bsdinstall.html">Handbook
 	      entry on installing &os;</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="floppy-image-too-large">
 	  <para>What do I do if the install image does not
 	    boot?</para>
 	</question>
 
 	<answer>
 	  <para>This can be caused by not downloading the image in
 	    <emphasis>binary</emphasis> mode when using
 	    <acronym>FTP</acronym>.</para>
 
 	  <para>Some FTP clients default their transfer mode to
 	    <emphasis>ascii</emphasis> and attempt to change any
 	    end-of-line characters received to match the
 	    conventions used by the client's system.  This will
 	    almost invariably corrupt the boot image.  Check the
 	    SHA-256 checksum of the downloaded boot image: if it
 	    is not <emphasis>exactly</emphasis> that on the
 	    server, then the download process is suspect.</para>
 
 	  <para>When using a command line FTP client, type
 	    <emphasis>binary</emphasis> at the FTP command prompt
 	    after getting connected to the server and before
 	    starting the download of the image.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="install-instructions-location">
 	  <para>Where are the instructions for installing &os;?</para>
 	</question>
 
 	<answer>
 	  <para>Installation instructions
 	    can be found at <link
 	      xlink:href="&url.books.handbook;/bsdinstall.html">Handbook
 	      entry on installing &os;</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="custom-boot-floppy">
 	  <para>How can I make my own custom release or install
 	    disk?</para>
 	</question>
 
 	<answer>
 	  <para>Customized &os; installation media can be created by
 	    building a custom release.  Follow the instructions in the
 	    <link
 	      xlink:href="&url.articles.releng;/article.html">Release
 	      Engineering</link> article.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="windows-coexist">
 	  <para>Can &windows; co-exist with &os;? (x86-specific)</para>
 	</question>
 
 	<answer>
 	  <para>If &windows; is installed first, then yes.  &os;'s
 	    boot manager will then manage to boot &windows; and &os;.
 	    If &windows; is installed afterwards, it will
 	    overwrite the boot manager.  If that
 	    happens, see the next section.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="bootmanager-restore">
 	  <para>Another operating system destroyed my Boot Manager.
 	    How do I get it back? (x86-specific)</para>
 	</question>
 
 	<answer>
 	  <para>This depends upon the boot manager.
 	    The &os; boot selection menu can be reinstalled using
 	    &man.boot0cfg.8;.  For example, to restore the boot menu
 	    onto the disk <replaceable>ada0</replaceable>:</para>
 
 	  <screen>&prompt.root; <userinput>boot0cfg -B ada0</userinput></screen>
 
 	  <para>The non-interactive MBR bootloader can be installed
 	    using &man.gpart.8;:</para>
 
 	  <screen>&prompt.root; <userinput>gpart bootcode -b /boot/mbr ada0</userinput></screen>
 
 	  <para>For more complex situations, including GPT disks, see
 	    &man.gpart.8;.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="need-complete-sources">
 	  <para>Do I need to install the source?</para>
 	</question>
 
 	<answer>
 	  <para>In general, no.  There is nothing in the base system
 	    which requires the presence of the source to operate.
 	    Some ports, like <package>sysutils/lsof</package>, will
 	    not build unless the source is installed.  In particular,
 	    if the port builds a kernel module or directly operates on
 	    kernel structures, the source must be installed.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="need-kernel">
 	  <para>Do I need to build a kernel?</para>
 	</question>
 
 	<answer>
 	  <para>Usually not.  The supplied <literal>GENERIC</literal>
 	    kernel contains the drivers an ordinary computer will
 	    need.  &man.freebsd-update.8;, the &os; binary upgrade
 	    tool, cannot upgrade custom kernels, another reason to
 	    stick with the <literal>GENERIC</literal> kernel when
 	    possible.  For computers with very limited RAM, such as
 	    embedded systems, it may be worthwhile to build a smaller
 	    custom kernel containing just the required drivers.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="password-encryption">
 	  <para>Should I use DES, Blowfish, or MD5 passwords and how
 	    do I specify which form my users receive?</para>
 	</question>
 
 	<answer>
 	  <para>&os; uses
 	    <emphasis>SHA512</emphasis> by
 	    default.  DES
 	    passwords are still available for backwards compatibility
 	    with operating systems that still
 	    use the less secure password format.  &os; also supports
 	    the Blowfish and MD5 password formats.  Which
 	    password format to use for new passwords is controlled by
 	    the <literal>passwd_format</literal> login capability in
 	    <filename>/etc/login.conf</filename>, which takes values
 	    of <literal>des</literal>, <literal>blf</literal> (if
 	    these are available) or <literal>md5</literal>.  See the
 	    &man.login.conf.5; manual page for more information about
 	    login capabilities.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ffs-limits">
 	  <para>What are the limits for FFS file systems?</para>
 	</question>
 
 	<answer>
 	  <para>For FFS file systems, the largest file system is
 	    practically limited by the amount of memory required to
 	    &man.fsck.8; the file system.  &man.fsck.8; requires one
 	    bit per fragment, which with the default fragment size of
 	    4&nbsp;KB equates to 32&nbsp;MB of memory per TB of disk.
 	    This does mean that on architectures which limit userland
 	    processes to 2&nbsp;GB (e.g., &i386;), the maximum
 	    &man.fsck.8;'able filesystem is ~60&nbsp;TB.</para>
 
 	  <para>If there was not a &man.fsck.8; memory limit the
 	    maximum filesystem size would be 2&nbsp;^&nbsp;64 (blocks)
 	    * 32&nbsp;KB => 16 Exa * 32&nbsp;KB => 512
 	    ZettaBytes.</para>
 
 	  <para>The maximum size of a single FFS file is approximately
 	    2&nbsp;PB with the default block size of 32&nbsp;KB.  Each
 	    32&nbsp;KB block can point to 4096 blocks.  With triple
 	    indirect blocks, the calculation is 32&nbsp;KB * 12 +
 	    32&nbsp;KB * 4096 + 32&nbsp;KB * 4096^2 + 32&nbsp;KB *
 	    4096^3.  Increasing the block size to 64&nbsp;KB will
 	    increase the max file size by a factor of 16.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="archsw-readin-failed-error">
 	  <para>Why do I get an error message, <errorname>readin
 	      failed</errorname> after compiling and booting a new
 	    kernel?</para>
 	</question>
 
 	<answer>
 	  <para>The world and kernel are out of sync.  This
 	    is not supported.  Be sure to use <command>make
 	      buildworld</command> and <command>make
 	      buildkernel</command> to update the kernel.</para>
 
 	  <para>Boot the system by specifying the kernel directly at
 	    the second stage, pressing any key when the
 	    <literal>|</literal> shows up before loader is
 	    started.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="general-configuration-tool">
 	  <para>Is there a tool to perform post-installation
 	    configuration tasks?</para>
 	</question>
 
 	<answer>
 	  <para>Yes.  <application>bsdconfig</application> provides a
 	    nice interface to configure &os; post-installation.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="hardware">
     <title>Hardware Compatibility</title>
 
     <sect1 xml:id="compatibility-general">
       <title>General</title>
 
       <qandaset>
 	<qandaentry>
 	  <question xml:id="which-hardware-to-get">
 	    <para>I want to get a piece of hardware for my &os;
 	      system.  Which model/brand/type is best?</para>
 	  </question>
 
 	  <answer>
 	    <para>This is discussed continually on the &os; mailing
 	      lists but is to be expected since hardware changes so
 	      quickly.  Read through the Hardware&nbsp;Notes
 	      for &os; <link
 		xlink:href="&rel121.current.hardware;">&rel121.current;</link>
 	      or <link
 		xlink:href="&rel1.current.hardware;">&rel1.current;</link>
 	      and search the mailing list <link
 		xlink:href="https://www.FreeBSD.org/search/#mailinglists">archives</link>
 	      before asking about the latest and greatest hardware.
 	      Chances are a discussion about that type of hardware
 	      took place just last week.</para>
 
 	    <para>Before purchasing a laptop, check the archives for
 	      &a.questions;, or possibly a specific
 	      mailing list for a particular hardware type.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question xml:id="memory-upper-limitation">
 	    <para>What are the limits for memory?</para>
 	  </question>
 
 	  <answer>
 	    <para>&os; as an operating system generally supports
 	      as much physical memory (RAM) as the platform it is
 	      running on does.  Keep in mind that different platforms
 	      have different limits for memory; for example &i386;
 	      without <acronym>PAE</acronym> supports at most
 	      4&nbsp;GB of memory (and usually less than that because
 	      of PCI address space) and &i386; with PAE supports at
 	      most 64&nbsp;GB memory.  As of &os;&nbsp;10, AMD64
 	      platforms support up to 4&nbsp;TB of physical
 	      memory.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question xml:id="memory-i386-over-4gb">
 	    <para>Why does &os; report less than 4&nbsp;GB memory when
 	      installed on an &i386; machine?</para>
 	  </question>
 
 	  <answer>
 	    <para>The total address space on &i386; machines is
 	      32-bit, meaning that at most 4&nbsp;GB of memory is
 	      addressable (can be accessed).  Furthermore, some
 	      addresses in this range are reserved by hardware for
 	      different purposes, for example for using and
 	      controlling PCI devices, for accessing video memory, and
 	      so on.  Therefore, the total amount of memory usable by
 	      the operating system for its kernel and applications is
 	      limited to significantly less than 4&nbsp;GB.  Usually,
 	      3.2&nbsp;GB to 3.7&nbsp;GB is the maximum usable
 	      physical memory in this configuration.</para>
 
 	    <para>To access more than 3.2&nbsp;GB to 3.7&nbsp;GB of
 	      installed memory (meaning up to 4&nbsp;GB but also more
 	      than 4&nbsp;GB), a special tweak called
 	      <acronym>PAE</acronym> must be used.  PAE stands for
 	      Physical Address Extension and is a way for 32-bit x86
 	      CPUs to address more than 4&nbsp;GB of memory.  It
 	      remaps the memory that would otherwise be overlaid by
 	      address reservations for hardware devices above the
 	      4&nbsp;GB range and uses it as additional physical
 	      memory (see &man.pae.4;).  Using PAE has some drawbacks;
 	      this mode of memory access is a little bit slower than
 	      the normal (without PAE) mode and loadable modules (see
 	      &man.kld.4;) are not supported.  This means all drivers
 	      must be compiled into the kernel.</para>
 
 	    <para>The most common way to enable PAE is to build a new
 	      kernel with the special ready-provided kernel
 	      configuration file called <filename>PAE</filename>,
 	      which is already configured to build a safe kernel.
 	      Note that some entries in this kernel configuration file
 	      are too conservative and some drivers marked as unready
 	      to be used with PAE are actually usable.  A rule of
 	      thumb is that if the driver is usable on 64-bit
 	      architectures (like AMD64), it is also usable with PAE.
 	      When creating a custom kernel configuration
 	      file, PAE can be enabled by adding the following
 	      line:</para>
 
 	    <programlisting>options       PAE</programlisting>
 
 	    <para>PAE is not much used nowadays because most new x86
 	      hardware also supports running in 64-bit mode, known as
 	      AMD64 or &intel;&nbsp;64.  It has a much larger address
 	      space and does not need such tweaks.  &os; supports
 	      AMD64 and it is recommended that this version of &os; be
 	      used instead of the &i386; version if 4&nbsp;GB or more
 	      memory is required.</para>
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect1>
 
     <sect1 xml:id="compatibility-processors">
       <title>Architectures and Processors</title>
 
       <qandaset>
 	<qandaentry>
 	  <question xml:id="architectures">
 	    <para>Does &os; support architectures other than the
 	      x86?</para>
 	  </question>
 
 	  <answer>
 	    <para>Yes.  &os; divides support into multiple tiers.
 	      Tier 1 architectures, such as i386 or amd64; are fully
 	      supported.  Tiers 2 and 3 are supported on a
 	      best-effort basis.  A full explanation of the tier
 	      system is available in the <link
 		xlink:href="&url.articles.committers-guide;/archs.html">Committer's
 		Guide.</link></para>
 
 	    <para>A complete  list of supported architectures can be
 	      found on the <link
 		xlink:href="https://www.FreeBSD.org/platforms/">platforms
 		page.</link></para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question xml:id="smp-support">
 	    <para>Does &os; support Symmetric Multiprocessing
 	      (SMP)?</para>
 	  </question>
 
 	  <answer>
 	    <para>&os; supports symmetric multi-processor (SMP) on all
 	      non-embedded platforms (e.g, &arch.i386;, &arch.amd64;,
 	      etc.).  SMP is also supported in arm and MIPS kernels,
 	      although some CPUs may not support this.  &os;'s SMP
 	      implementation uses fine-grained locking, and
 	      performance scales nearly linearly with number of
 	      CPUs.</para>
 
 	    <para>&man.smp.4; has more details.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question xml:id="microcode">
 	    <para>What is microcode?
 	      How do I install &intel; CPU microcode updates?</para>
 	  </question>
 
 	  <answer>
 	    <para>Microcode is a method of programmatically
 	      implementing hardware level instructions.  This allows
 	      for CPU bugs to be fixed without replacing the on board
 	      chip.</para>
 
 	    <para>Install <package>sysutils/devcpu-data</package>,
 	      then add:</para>
 
 	    <programlisting>microcode_update_enable="YES"</programlisting>
 
 	    <para>to <filename>/etc/rc.conf</filename></para>
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect1>
 
     <sect1 xml:id="compatibility-peripherals">
       <title>Peripherals</title>
 
       <qandaset>
 	<qandaentry>
 	  <question xml:id="supported-peripherals">
 	    <para>What kind of peripherals does &os; support?</para>
 	  </question>
 
 	  <answer>
 	    <para>See the complete list in the Hardware Notes for &os;
 	      <link
 		xlink:href="&rel121.current.hardware;">&rel121.current;</link>
 	      or <link
 		xlink:href="&rel1.current.hardware;">&rel1.current;</link>.</para>
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect1>
 
     <sect1 xml:id="compatibility-kbd-mice">
       <title>Keyboards and Mice</title>
 
       <qandaset>
 	<qandaentry>
 	  <question xml:id="moused">
 	    <para>Is it possible to use a mouse outside the
 	      X Window system?</para>
 	  </question>
 
 	  <answer>
 	    <para>The default console driver,
 	      &man.vt.4;, provides the ability to use a mouse
 	      pointer in text consoles to cut &amp; paste text.  Run
 	      the mouse daemon, &man.moused.8;, and turn on the mouse
 	      pointer in the virtual console:</para>
 
 	    <screen>&prompt.root; <userinput>moused -p /dev/xxxx -t yyyy</userinput>
 &prompt.root; <userinput>vidcontrol -m on</userinput></screen>
 
 	    <para>Where <replaceable>xxxx</replaceable> is the mouse
 	      device name and <replaceable>yyyy</replaceable> is a
 	      protocol type for the mouse.  The mouse daemon can
 	      automatically determine the protocol type of most mice,
 	      except old serial mice.  Specify the
 	      <literal>auto</literal> protocol to invoke automatic
 	      detection.  If automatic detection does not work, see
 	      the &man.moused.8; manual page for a list of supported
 	      protocol types.</para>
 
 	    <para>For a PS/2 mouse, add
 	      <literal>moused_enable="YES"</literal> to
 	      <filename>/etc/rc.conf</filename> to start the mouse
 	      daemon at boot time.  Additionally, to
 	      use the mouse daemon on all virtual terminals instead of
 	      just the console, add <literal>allscreens_flags="-m
 		on"</literal> to
 	      <filename>/etc/rc.conf</filename>.</para>
 
 	    <para>When the mouse daemon is running, access to the
 	      mouse must be coordinated between the mouse daemon and
 	      other programs such as X Windows.  Refer to the
 	      <acronym>FAQ</acronym>
 	      <link linkend="x-and-moused">Why does my mouse not work
 		with X?</link> for more details on this issue.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question xml:id="text-mode-cut-paste">
 	    <para>How do I cut and paste text with a mouse in the text
 	      console?</para>
 	  </question>
 
 	  <answer>
 	    <para>It is not possible to remove data using the mouse.
 	      However, it is possible to copy and paste.  Once the
 	      mouse daemon is running as described in the <link
 		linkend="moused">previous question</link>, hold down
 	      button 1 (left button) and move the mouse to select a
 	      region of text.  Then, press button 2 (middle button) to
 	      paste it at the text cursor.  Pressing button 3 (right
 	      button) will <quote>extend</quote> the selected region
 	      of text.</para>
 
 	    <para>If the mouse does not have a middle button, it is
 	      possible to emulate one or remap buttons using mouse
 	      daemon options.  See the &man.moused.8; manual page for
 	      details.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question xml:id="mouse-wheel-buttons">
 	    <para>My mouse has a fancy wheel and buttons.  Can I use
 	      them in &os;?</para>
 	  </question>
 
 	  <answer>
 	    <para>The answer is, unfortunately, <quote>It
 		depends</quote>.  These mice with additional features
 	      require specialized driver in most cases.  Unless the
 	      mouse device driver or the user program has specific
 	      support for the mouse, it will act just like a standard
 	      two, or three button mouse.</para>
 
 	    <para>For the possible usage of wheels in the X Window
 	      environment, refer to <link
 		linkend="x-and-wheel">that section</link>.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question xml:id="keyboard-delete-key">
 	    <para>How do I use my delete key in <command>sh</command>
 	      and <command>csh</command>?</para>
 	  </question>
 
 	  <answer>
 	    <para>For the <application>Bourne Shell</application>, add
 	      the following lines to <filename>~/.shrc</filename>.
 	      See &man.sh.1; and &man.editrc.5;.</para>
 
             <programlisting>bind ^[[3~ ed-delete-next-char # for xterm</programlisting>
 
 	    <para>For the <application>C Shell</application>, add the
 	      following lines to <filename>~/.cshrc</filename>.
 	      See &man.csh.1;.</para>
 
             <programlisting>bindkey ^[[3~ delete-char # for xterm</programlisting>
 
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect1>
 
     <sect1 xml:id="compatibility-other">
       <title>Other Hardware</title>
 
       <qandaset>
 	<qandaentry>
 	  <question xml:id="es1370-silent-pcm">
 	    <para>Workarounds for no sound from my &man.pcm.4; sound
 	      card?</para>
 	  </question>
 
 	  <answer>
 	    <para>Some sound cards set their output volume to 0 at
 	      every boot.  Run the following command every time the
 	      machine boots:</para>
 
 	    <screen>&prompt.root; <userinput>mixer pcm 100 vol 100 cd 100</userinput></screen>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question xml:id="power-management-support">
 	    <para>Does &os; support power management on my
 	      laptop?</para>
 	  </question>
 
 	  <answer>
 	    <para>&os; supports the <acronym>ACPI</acronym> features
 	      found in modern hardware.  Further information can be
 	      found in &man.acpi.4;.</para>
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect1>
   </chapter>
 
   <chapter xml:id="troubleshoot">
     <title>Troubleshooting</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="pae">
 	  <para>Why is &os; finding the wrong amount of memory on
 	    &i386; hardware?</para>
 	</question>
 
 	<answer>
 	  <para>The most likely reason is the difference between
 	    physical memory addresses and virtual addresses.</para>
 
 	  <para>The convention for most PC hardware is to use the
 	    memory area between 3.5&nbsp;GB and 4&nbsp;GB for a
 	    special purpose (usually for PCI).  This address space is
 	    used to access PCI hardware.  As a result real, physical
 	    memory cannot be accessed by that address space.</para>
 
 	  <para>What happens to the memory that should appear in that
 	    location is hardware dependent.  Unfortunately,
 	    some hardware does nothing and the ability to use that
 	    last 500&nbsp;MB of RAM is entirely lost.</para>
 
 	  <para>Luckily, most hardware remaps the memory to a higher
 	    location so that it can still be used.  However, this can
 	    cause some confusion when watching the boot
 	    messages.</para>
 
 	  <para>On a 32-bit version of &os;, the memory appears lost,
 	    since it will be remapped above 4&nbsp;GB, which a 32-bit
 	    kernel is unable to access.  In this case, the solution is
 	    to build a PAE enabled kernel.  See the entry on memory
 	    limits for more information.</para>
 
 	  <para>On a 64-bit version of &os;, or when running a
 	    PAE-enabled kernel, &os; will correctly detect and remap
 	    the memory so it is usable.  During boot, however, it may
 	    seem as if &os; is detecting more memory than the system
 	    really has, due to the described remapping.  This is
 	    normal and the available memory will be corrected as the
 	    boot process completes.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="signal11">
 	  <para>Why do my programs occasionally die with
 	    <errorname>Signal 11</errorname> errors?</para>
 	</question>
 
 	<answer>
 	  <para>Signal 11 errors are caused when a process has
 	    attempted to access memory which the operating system has
 	    not granted it access to.  If something like this is
 	    happening at seemingly random intervals,
 	    start investigating the cause.</para>
 
 	  <para>These problems can usually be attributed to
 	    either:</para>
 
 	  <orderedlist>
 	    <listitem>
 	      <para>If the problem is occurring only in a specific
 		custom application, it is
 		probably a bug in the code.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>If it is a problem with part of the base &os;
 		system, it may also be buggy code, but more often than
 		not these problems are found and fixed long before us
 		general <acronym>FAQ</acronym> readers get to use
 		these bits of code (that is what -CURRENT is
 		for).</para>
 	    </listitem>
 	  </orderedlist>
 
 	  <para>It is probably
 	    not a &os; bug if the
 	    problem occurs compiling a program, but the activity
 	    that the compiler is carrying out changes each
 	    time.</para>
 
 	  <para>For example, if <command>make
 	      buildworld</command> fails while trying
 	    to compile <filename>ls.c</filename> into
 	    <filename>ls.o</filename> and, when run again, it fails
 	    in the same place, this is a broken build.  Try
 	    updating source and try again.  If the compile fails
 	    elsewhere, it is almost certainly due to hardware.</para>
 
 	  <para>In the first case, use a debugger such as
 	    &man.gdb.1; to find the point in the program which is
 	    attempting to access a bogus address and fix
 	    it.</para>
 
 	  <para>In the second case, verify which piece of
 	    hardware is at fault.</para>
 
 	  <para>Common causes of this include:</para>
 
 	  <orderedlist>
 	    <listitem>
 	      <para>The hard disks might be overheating: Check that
 		the fans are still working, as the disk and
 		other hardware might be overheating.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>The processor running is overheating: This might
 		be because the processor has been overclocked, or the
 		fan on the processor might have died.  In either case,
 		ensure that the hardware is running at
 		what it is specified to run at, at least while trying
 		to solve this problem.  If it is not, clock it back
 		to the default settings.)</para>
 
 	      <para>Regarding overclocking, it is far
 		cheaper to have a slow system than a fried system that
 		needs replacing!  Also the community is not
 		sympathetic to problems on overclocked systems.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Dodgy memory: if multiple memory
 		SIMMS/DIMMS are installed, pull them all out and try
 		running the machine with each SIMM or DIMM
 		individually to narrow the problem down to either the
 		problematic DIMM/SIMM or perhaps even a
 		combination.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Over-optimistic motherboard settings: the BIOS
 		settings, and some motherboard jumpers, provide
 		options to set various timings.  The defaults
 		are often sufficient, but sometimes setting the wait
 		states on RAM too low, or setting the <quote>RAM
 		  Speed: Turbo</quote> option
 		will cause strange behavior.  A possible idea is to
 		set to BIOS defaults, after noting
 		the current settings first.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Unclean or insufficient power to the motherboard.
 		Remove any unused I/O boards, hard disks, or
 		CD-ROMs,
 		or disconnect the power cable from them, to see if
 		the power supply can manage a smaller load.  Or try
 		another power supply, preferably one with a little
 		more power.  For instance, if the current power supply
 		is rated at 250&nbsp;Watts, try one rated at
 		300&nbsp;Watts.</para>
 	    </listitem>
 	  </orderedlist>
 
 	  <para>Read the section on
 	    <link linkend="signal11">Signal 11</link> for a further
 	    explanation and a discussion on how memory testing
 	    software or hardware can still pass faulty memory.  There
 	    is an extensive <acronym>FAQ</acronym> on this at <link
 	      xlink:href="http://www.bitwizard.nl/sig11/">the SIG11
 	      problem <acronym>FAQ</acronym></link>.</para>
 
 	  <para>Finally, if none of this has helped, it is possibly
 	    a bug in &os;.
 	    Follow <link linkend="access-pr">these instructions</link>
 	    to send a problem report.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="trap-12-panic">
 	  <para>My system crashes with either <errorname>Fatal trap
 	      12: page fault in kernel mode</errorname>, or
 	    <errorname>panic:</errorname>, and spits out a bunch of
 	    information.  What should I do?</para>
 	</question>
 
 	<answer>
 	  <para>The &os; developers are interested in these
 	    errors, but need more information than just the error
 	    message.  Copy the full crash message.  Then consult the
 	    <acronym>FAQ</acronym> section on <link
 	      linkend="kernel-panic-troubleshooting">kernel
 	      panics</link>, build a debugging kernel, and get a
 	    backtrace.  This might sound difficult, but does not
 	    require any programming skills.  Just follow the
 	    instructions.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="proc-table-full">
 	  <para>What is the meaning of the error <errorname>maxproc
 	      limit exceeded by uid %i, please see tuning(7) and
 	      login.conf(5)</errorname>?</para>
 	</question>
 
 	<answer>
 	  <para>The &os; kernel will only allow a certain number of
 	    processes to exist at one time.  The number is based on
 	    the <varname>kern.maxusers</varname> &man.sysctl.8;
 	    variable.  <varname>kern.maxusers</varname> also affects
 	    various other in-kernel limits, such as network buffers.
 	    If the machine is heavily loaded,
 	    increase <varname>kern.maxusers</varname>.  This will
 	    increase these other system limits in addition to the
 	    maximum number of processes.</para>
 
 	  <para>To adjust the <varname>kern.maxusers</varname> value,
 	    see the <link
 	      xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">File/Process
 	      Limits</link> section of the Handbook.  While that
 	    section refers to open files, the same limits apply to
 	    processes.</para>
 
 	  <para>If the machine is lightly loaded but running a very
 	    large number of processes, adjust the
 	    <varname>kern.maxproc</varname> tunable by defining it in
 	    <filename>/boot/loader.conf</filename>.  The tunable will
 	    not get adjusted until the system is rebooted.  For more
 	    information about tuning tunables, see
 	    &man.loader.conf.5;.  If these processes are being run by
 	    a single user, adjust
 	    <varname>kern.maxprocperuid</varname> to be one less than
 	    the new <varname>kern.maxproc</varname> value.  It must
 	    be at least one less because one system program,
 	    &man.init.8;, must always be running.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="remote-fullscreen">
 	  <para>Why do full screen applications on remote machines
 	    misbehave?</para>
 	</question>
 
 	<answer>
 	  <para>The remote machine may be setting the terminal type to
 	    something other than <literal>xterm</literal> which is
 	    required by the &os; console.  Alternatively the kernel
 	    may have the wrong values for the width and height of the
 	    terminal.</para>
 
 	  <para>Check the value of the <envar>TERM</envar>
 	    environment variable is <literal>xterm</literal>.  If the
 	    remote machine does not support that try
 	    <literal>vt100</literal>.</para>
 
 	  <para>Run <command>stty -a</command> to check what the
 	    kernel thinks the terminal dimensions are.  If they are
 	    incorrect, they can be changed by running
 	    <command>stty rows <replaceable>RR</replaceable> cols
 	    <replaceable>CC</replaceable></command>.</para>
 
 	  <para>Alternatively, if the client machine has
 	    <package>x11/xterm</package> installed, then running
 	    <command>resize</command> will query the terminal for the
 	    correct dimensions and set them.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="connection-delay">
 	  <para>Why does it take so long to connect to my computer via
 	    <command>ssh</command> or
 	    <command>telnet</command>?</para>
 	</question>
 
 	<answer>
 	  <para>The symptom: there is a long delay between the time
 	    the TCP connection is established and the time when the
 	    client software asks for a password (or, in
 	    &man.telnet.1;'s case, when a login prompt
 	    appears).</para>
 
 	  <para>The problem: more likely than not, the delay is caused
 	    by the server software trying to resolve the client's IP
 	    address into a hostname.  Many servers, including the
 	    <application>Telnet</application> and
 	    <application>SSH</application> servers that come with
 	    &os;, do this to store the hostname in a log file for
 	    future reference by the administrator.</para>
 
 	  <para>The remedy: if the problem occurs whenever connecting
 	    the client computer to any server, the problem
 	    is with the client.  If the problem only occurs
 	    when someone connects to the server computer, the
 	    problem is with the server.</para>
 
 	  <para>If the problem is with the client, the only remedy is
 	    to fix the DNS so the server can resolve it.  If this is
 	    on a local network, consider it a server problem and keep
 	    reading.  If this is on the Internet,
 	    contact your ISP.</para>
 
 	  <para>If the problem is with the server on a
 	    local network, configure the server
 	    to resolve address-to-hostname queries for the local
 	    address range.  See &man.hosts.5; and &man.named.8;
 	    for more information.  If this is on the
 	    Internet, the problem may be that the local server's
 	    resolver is not functioning correctly.  To check, try to
 	    look up another host such as
 	    <systemitem>www.yahoo.com</systemitem>.  If it does not
 	    work, that is the problem.</para>
 
 	  <para>Following a fresh install of &os;, it is also possible
 	    that domain and name server information is missing from
 	    <filename>/etc/resolv.conf</filename>.  This will often
 	    cause a delay in <application>SSH</application>, as the
 	    option <literal>UseDNS</literal> is set to
 	    <literal>yes</literal> by default in
 	    <filename>/etc/ssh/sshd_config</filename>.  If this is
 	    causing the problem, either fill in the
 	    missing information in
 	    <filename>/etc/resolv.conf</filename> or set
 	    <literal>UseDNS</literal> to <literal>no</literal> in
 	    <filename>sshd_config</filename> as a temporary
 	    workaround.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="file-table-full">
 	  <para>Why does <errorname>file: table is full</errorname>
 	    show up repeatedly in &man.dmesg.8;?</para>
 	</question>
 
 	<answer>
 	  <para>This error message indicates that the number of
 	    available file descriptors have been exhausted on the
 	    system.  Refer to the <link
 	      xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">kern.maxfiles</link>
 	    section of the <link
 	      xlink:href="&url.books.handbook;/configtuning-kernel-limits.html">Tuning
 	      Kernel Limits</link> section of the Handbook for a
 	    discussion and solution.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="computer-clock-skew">
 	  <para>Why does the clock on my computer keep incorrect
 	    time?</para>
 	</question>
 
 	<answer>
 	  <para>The computer has two or more clocks, and &os; has
 	    chosen to use the wrong one.</para>
 
 	  <para>Run &man.dmesg.8;, and check for lines that contain
 	    <literal>Timecounter</literal>.  The one with the highest
 	    quality value that &os; chose.</para>
 
 	  <screen>&prompt.root; <userinput>dmesg | grep Timecounter</userinput>
 Timecounter "i8254" frequency 1193182 Hz quality 0
 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
 Timecounter "TSC" frequency 2998570050 Hz quality 800
 Timecounters tick every 1.000 msec</screen>
 
 	  <para>Confirm this by checking the
 	    <varname>kern.timecounter.hardware</varname>
 	    &man.sysctl.3;.</para>
 
 	  <screen>&prompt.root; <userinput>sysctl kern.timecounter.hardware</userinput>
 kern.timecounter.hardware: ACPI-fast</screen>
 
 	  <para>It may be a broken ACPI timer.  The simplest solution
 	    is to disable the ACPI timer in
 	    <filename>/boot/loader.conf</filename>:</para>
 
 	  <programlisting>debug.acpi.disabled="timer"</programlisting>
 
 	  <para>Or the BIOS may modify the TSC clock&mdash;perhaps to
 	    change the speed of the processor when running from
 	    batteries, or going into a power saving mode, but &os; is
 	    unaware of these adjustments, and appears to gain or lose
 	    time.</para>
 
 	  <para>In this example, the <literal>i8254</literal> clock is
 	    also available, and can be selected by writing its name to
 	    the <varname>kern.timecounter.hardware</varname>
 	    &man.sysctl.3;.</para>
 
 	  <screen>&prompt.root; <userinput>sysctl kern.timecounter.hardware=i8254</userinput>
 kern.timecounter.hardware: TSC -&gt; i8254</screen>
 
 	  <para>The computer should now start keeping more accurate
 	    time.</para>
 
 	  <para>To have this change automatically run at boot time,
 	    add the following line to
 	    <filename>/etc/sysctl.conf</filename>:</para>
 
 	  <programlisting>kern.timecounter.hardware=i8254</programlisting>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="indefinite-wait-buffer">
 	  <para>What does the error <errorname>swap_pager: indefinite
 	      wait buffer:</errorname> mean?</para>
 	</question>
 
 	<answer>
 	  <para>This means that a process is trying to page memory
 	    from
 	    disk, and the page attempt has hung trying to access the
 	    disk for more than 20 seconds.  It might be caused by bad
 	    blocks on the disk drive, disk wiring, cables, or any
 	    other disk I/O-related hardware.  If the drive itself is
 	    bad, disk errors will appear in
 	    <filename>/var/log/messages</filename> and in the output
 	    of <command>dmesg</command>.  Otherwise, check the cables
 	    and connections.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="lock-order-reversal">
 	  <para>What is a <errorname>lock order
 	      reversal</errorname>?</para>
 	</question>
 
 	<answer>
 	  <para>The &os; kernel uses a number of resource locks to
 	    arbitrate contention for certain resources.  When multiple
 	    kernel threads try to obtain multiple resource locks,
 	    there's always the potential for a deadlock, where two
 	    threads have each obtained one of the locks and blocks
 	    forever waiting for the other thread to release one of the
 	    other locks.  This sort of locking problem can be avoided
 	    if all threads obtain the locks in the same order.</para>
 
 	  <para>A run-time lock diagnostic system called
 	    &man.witness.4;, enabled in &os.current; and disabled by
 	    default for stable branches and releases, detects the
 	    potential for deadlocks due to locking errors, including
 	    errors caused by obtaining multiple resource locks with a
 	    different order from different parts of the kernel.  The
 	    &man.witness.4; framework tries to detect this problem as
 	    it happens, and reports it by printing a message to the
 	    system console about a <errorname>lock order
 	      reversal</errorname> (often referred to also as
 	    <acronym>LOR</acronym>).</para>
 
 	  <para>It is possible to get false positives, as
 	    &man.witness.4; is conservative.  A true positive report
 	    <emphasis>does not</emphasis> mean that a system is
 	    dead-locked; instead it should be understood as a warning
 	    that a deadlock could have happened here.</para>
 
 	  <note>
 	    <para>Problematic <acronym>LOR</acronym>s tend to get
 	      fixed quickly, so check the &a.current; before posting
 	      to it.</para>
 	  </note>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="called-with-non-sleepable-locks-held">
 	  <para>What does <errorname>Called ...  with the following
 	      non-sleepable locks held</errorname> mean?</para>
 	</question>
 
 	<answer>
 	  <para>This means that a function that may sleep was called
 	    while a mutex (or other unsleepable) lock was held.</para>
 
 	  <para>The reason this is an error is because mutexes are not
 	    intended to be held for long periods of time; they are
 	    supposed to only be held to maintain short periods of
 	    synchronization.  This programming contract allows device
 	    drivers to use mutexes to synchronize with the rest of the
 	    kernel during interrupts.  Interrupts (under &os;) may not
 	    sleep.  Hence it is imperative that no subsystem in the
 	    kernel block for an extended period while holding a
 	    mutex.</para>
 
 	  <para>To catch such errors, assertions may be added to the
 	    kernel that interact with the &man.witness.4; subsystem to
 	    emit a warning or fatal error (depending on the system
 	    configuration) when a potentially blocking call is made
 	    while holding a mutex.</para>
 
 	  <para>In summary, such warnings are non-fatal, however with
 	    unfortunate timing they could cause undesirable effects
 	    ranging from a minor blip in the system's responsiveness
 	    to a complete system lockup.</para>
 
 	  <para>For additional information about locking in &os; see
 	    &man.locking.9;.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="touch-not-found">
 	  <para>Why does
 	    <buildtarget>buildworld</buildtarget>/<buildtarget>installworld</buildtarget>
 	    die with the message <errorname>touch: not
 	      found</errorname>?</para>
 	</question>
 
 	<answer>
 	  <para>This error does not mean that the &man.touch.1;
 	    utility is missing.  The error is instead probably due to
 	    the dates of the files being set sometime in the future.
 	    If the CMOS clock is set to local time, run
 	    <command>adjkerntz&nbsp;-i</command> to adjust
 	    the kernel clock when booting into single-user
 	    mode.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="applications">
     <title>User Applications</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="user-apps">
 	  <para>Where are all the user applications?</para>
 	</question>
 
 	<answer>
 	  <para>Refer to <link
 	      xlink:href="&url.base;/ports/index.html">the ports
 	      page</link> for info on software packages ported to
 	    &os;.</para>
 
 	  <para>Most ports should work on all supported versions of
 	    &os;.  Those that do not are specifically marked as such.
 	    Each time a &os; release is made, a snapshot of the ports
 	    tree at the time of release is also included in the
 	    <filename>ports/</filename> directory.</para>
 
 	  <para>&os; supports compressed binary packages to easily
 	    install and uninstall ports.  Use &man.pkg.7; to control
 	    the installation of packages.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="how-do-download-ports-tree">
 	  <para>How do I download the Ports tree? Should I be using
 	    Subversion?</para>
 	</question>
 
 	<answer>
 	  <para>Any of the methods listed here work:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Use portsnap for most use cases.  Refer to <link
 		  xlink:href="&url.books.handbook;/ports-using.html">Using
 		the Ports Collection</link> for instructions on how to
 		use this tool.</para>
 	    </listitem>
 	    <listitem>
 	      <para>Use Subversion if custom patches to the
 		ports tree are needed or if running &os.current;.
 		Refer to <link
 		  xlink:href="&url.books.handbook;/svn.html">Using
 		  Subversion</link> for details.</para>
 	    </listitem>
 	  </itemizedlist>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ports-4x">
 	  <para>Why can I not build this port on my
 	    &rel2.relx;&nbsp;-, or
 	    &rel.relx;&nbsp;-STABLE machine?</para>
 	</question>
 
 	<answer>
 	  <para>If the installed &os; version lags significantly
 	    behind <emphasis>-CURRENT</emphasis> or
 	    <emphasis>-STABLE</emphasis>, update the Ports Collection
 	    using the instructions in <link
 	      xlink:href="&url.books.handbook;/ports-using.html">Using
 	      the Ports Collection</link>.  If the system is
 	    up-to-date, someone might have committed a change to the
 	    port which works for <emphasis>-CURRENT</emphasis> but
 	    which broke the port for <emphasis>-STABLE</emphasis>.
 	    <link
 	      xlink:href="https://bugs.FreeBSD.org/submit/">Submit</link>
 	    a bug report, since the Ports Collection is supposed to
 	    work for both the <emphasis>-CURRENT</emphasis> and
 	    <emphasis>-STABLE</emphasis> branches.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="make-index">
 	  <para>I just tried to build <filename>INDEX</filename> using
 	    <command>make index</command>, and it failed.  Why?</para>
 	</question>
 
 	<answer>
 	  <para>First, make sure that the Ports Collection is
 	    up-to-date.  Errors that affect building
 	    <filename>INDEX</filename> from an up-to-date copy of the
 	    Ports Collection are high-visibility and are thus almost
 	    always fixed immediately.</para>
 
 	  <para>There are rare cases where <filename>INDEX</filename>
 	    will not build due to odd cases involving
 	    <varname>OPTIONS_SET</varname>
 	    being set in <filename>make.conf</filename>.  If
 	    you suspect that this is the case, try to make
 	    <filename>INDEX</filename> with those variables
 	    turned off before reporting it to &a.ports;.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ports-update">
 	  <para>I updated the sources, now how do I update my
 	    installed ports?</para>
 	</question>
 
 	<answer>
 	  <para>&os; does not include a port upgrading tool, but it
 	    does have some tools to make the upgrade process somewhat
 	    easier.  Additional tools are available to simplify
 	    port handling and are described the <link
 	      xlink:href="&url.books.handbook;/ports-using.html">Upgrading
 	      Ports</link> section in the &os; Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ports-major-upgrade">
 	  <para>Do I need to recompile every port each time I perform
 	    a major version update?</para>
 	</question>
 
 	<answer>
 	  <para>Yes!  While a recent system will run with
 	    software compiled under an older release,
 	    things will randomly crash and fail to work once
 	    other ports are installed or updated.</para>
 
 	  <para>When the system is upgraded, various shared libraries,
 	    loadable modules, and other parts of the system will be
 	    replaced with newer versions.  Applications linked against
 	    the older versions may fail to start or, in other cases,
 	    fail to function properly.</para>
 
 	  <para>For more information, see <link
 	      xlink:href="&url.books.handbook;/updating-upgrading-freebsdupdate.html#freebsdupdate-upgrade">the
 	      section on upgrades</link> in the &os; Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ports-minor-upgrade">
 	  <para>Do I need to recompile every port each time I perform
 	    a minor version update?</para>
 	</question>
 
 	<answer>
 	  <para>In general, no.  &os; developers do their utmost to
 	    guarantee binary compatibility across all releases with
 	    the same major version number.  Any exceptions will be
 	    documented in the Release Notes, and advice given there
 	    should be followed.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="minimal-sh">
 	  <para>Why is <command>/bin/sh</command> so minimal?  Why
 	    does &os; not use <command>bash</command> or another
 	    shell?</para>
 	</question>
 
 	<answer>
 	  <para>Many people need to write shell scripts which will be
 	    portable across many systems.  That is why &posix;
 	    specifies the shell and utility commands in great detail.
 	    Most scripts are written in Bourne shell (&man.sh.1;), and
 	    because several important programming interfaces
 	    (&man.make.1;, &man.system.3;, &man.popen.3;, and
 	    analogues in higher-level scripting languages like Perl
 	    and Tcl) are specified to use the Bourne shell to
 	    interpret commands.  Because the Bourne shell is so often
 	    and widely used, it is important for it to be quick to
 	    start, be deterministic in its behavior, and have a small
 	    memory footprint.</para>
 
 	  <para>The existing implementation is our best effort at
 	    meeting as many of these requirements simultaneously as we
 	    can.  To keep <command>/bin/sh</command> small, we have
 	    not provided many of the convenience features that other
 	    shells have.  That is why other more featureful shells
 	    like <command>bash</command>, <command>scsh</command>,
 	    &man.tcsh.1;, and <command>zsh</command> are available.
 	    Compare the memory utilization of
 	    these shells by looking at the <quote>VSZ</quote> and
 	    <quote>RSS</quote> columns in a <command>ps -u</command>
 	    listing.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="kernelconfig">
     <title>Kernel Configuration</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="make-kernel">
 	  <para>I would like to customize my kernel.  Is it
 	    difficult?</para>
 	</question>
 
 	<answer>
 	  <para>Not at all!  Check out the <link
 	      xlink:href="&url.books.handbook;/kernelconfig.html">kernel
 	      config section of the Handbook</link>.</para>
 
 	  <note>
 	    <para>The new <filename>kernel</filename> will be
 	      installed to the <filename>/boot/kernel</filename>
 	      directory along with its modules, while the old kernel
 	      and its modules will be moved to the
 	      <filename>/boot/kernel.old</filename> directory.  If
 	      a mistake is made in the
 	      configuration, simply boot the previous version of the
 	      kernel.</para>
 	  </note>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="why-kernel-big">
 	  <para>Why is my kernel so big?</para>
 	</question>
 
 	<answer>
 	  <para><literal>GENERIC</literal> kernels shipped with &os;
 	    are compiled in <emphasis>debug mode</emphasis>.
 	    Kernels built in debug mode contain debug data in
 	    separate files that are used for debugging.
 	    &os; releases prior to 11.0 store these debug files in
 	    the same directory as the kernel itself,
 	    <filename>/boot/kernel/</filename>.
 	    In &os; 11.0 and later the debug files are stored in
 	    <filename>/usr/lib/debug/boot/kernel/</filename>.
 	    Note that there will be little or no performance loss from
 	    running a debug kernel, and it is useful to keep one
 	    around in case of a system panic.</para>
 
 	  <para>When running low on disk space, there
 	    are different options to reduce the size of
 	    <filename>/boot/kernel/</filename> and
 	    <filename>/usr/lib/debug/</filename>.</para>
 
 	  <para>To not install the symbol files,
 	    make sure the following line exists in
 	    <filename>/etc/src.conf</filename>:</para>
 
 	  <programlisting>WITHOUT_KERNEL_SYMBOLS=yes</programlisting>
 
 	  <para>For more information see &man.src.conf.5;.</para>
 
 	  <para>If you want to avoid building debug files altogether,
 	    make sure that both of the following are true:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>This line does not exist in the kernel
 		configuration file:</para>
 
 	      <programlisting>makeoptions DEBUG=-g</programlisting>
 	    </listitem>
 
 	    <listitem>
 	      <para>Do not run &man.config.8; with
 		<option>-g</option>.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>Either of the above settings will cause the kernel to
 	    be built in debug mode.</para>
 
 	  <para>To build and install only the specified modules, list
 	    them in
 	    <filename>/etc/make.conf</filename>:</para>
 
 	  <programlisting>MODULES_OVERRIDE= <replaceable>accf_http ipfw</replaceable></programlisting>
 
 	  <para>Replace <emphasis>accf_httpd ipfw</emphasis> with a
 	    list of needed modules.  Only the listed modules will be
 	    built.  This reduces the size of the kernel
 	    directory and decreases the amount of time needed to
 	    build the kernel.  For more information, read
 	    <filename>/usr/share/examples/etc/make.conf</filename>.</para>
 
 	  <para>Unneeded devices can be removed from the kernel
 	    to further reduce the size.  See <xref
 	      linkend="make-kernel"/> for more information.</para>
 
 	  <para>To put any of these options into effect, follow the
 	    instructions to <link
 	      xlink:href="&url.books.handbook;/kernelconfig-building.html">build
 	      and install</link> the new kernel.</para>
 
 	  <para>For reference, the &os; 11 &arch.amd64; kernel
 	    (<filename>/boot/kernel/kernel</filename>) is
 	    approximately 25&nbsp;MB.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="generic-kernel-build-failure">
 	  <para>Why does every kernel I try to build fail to compile,
 	    even <filename>GENERIC</filename>?</para>
 	</question>
 
 	<answer>
 	  <para>There are a number of possible causes for this
 	    problem:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>The source
 		tree is different from the one used to build the
 		currently running system.  When attempting an upgrade,
 		read <filename>/usr/src/UPDATING</filename>, paying
 		particular attention to the <quote>COMMON
 		  ITEMS</quote> section at the end.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>The <command>make buildkernel</command> did not
 		complete successfully.  The <command>make
 		  buildkernel</command> target relies on files
 		generated by the <command>make buildworld</command>
 		target to complete its job correctly.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Even when building <link
 		  linkend="stable">&os;-STABLE</link>, it is possible
 		that the source tree was fetched at a time when it was
 		either being modified or it was broken.
 		Only releases are guaranteed to be
 		buildable, although <link
 		  linkend="stable">&os;-STABLE</link> builds fine the
 		majority of the time.  Try re-fetching the source tree
 		and see if the problem goes away.  Try using a
 		different mirror in case the previous one is having
 		problems.</para>
 	    </listitem>
 	  </itemizedlist>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="scheduler-in-use">
 	  <para>Which scheduler is in use on a
 	    running system?</para>
 	</question>
 
 	<answer>
 	  <para>The name of the scheduler currently being used is
 	    directly available as the value of the
 	    <varname>kern.sched.name</varname> sysctl:</para>
 
 	  <screen>&prompt.user; sysctl <replaceable>kern.sched.name</replaceable>
 kern.sched.name: ULE</screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="scheduler-kern-quantum">
 	  <para>What is <varname>kern.sched.quantum</varname>?</para>
 	</question>
 
 	<answer>
 	  <para><varname>kern.sched.quantum</varname> is the maximum
 	    number of ticks a process can run without being preempted
 	    in the 4BSD scheduler.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="disks">
     <title>Disks, File Systems, and Boot Loaders</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="adding-disks">
 	  <para>How can I add my new hard disk to my &os;
 	    system?</para>
 	</question>
 
 	<answer>
 	  <para>See the <link
 	      xlink:href="&url.books.handbook;/disks-adding.html">Adding
 	      Disks</link> section in the &os; Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="new-huge-disk">
 	  <para>How do I move my system over to my huge new
 	    disk?</para>
 	</question>
 
 	<answer>
 	  <para>The best way is to reinstall the operating system on
 	    the new disk, then move the user data over.  This is
 	    highly recommended when tracking
 	    <emphasis>-STABLE</emphasis> for more than one release or
 	    when updating a release instead of installing a new one.
 	    Install booteasy on both disks with &man.boot0cfg.8; and
 	    dual boot until you are happy with the new configuration.
 	    Skip the next paragraph to find out how to move the data
 	    after doing this.</para>
 
 	  <para>Alternatively, partition and label the new disk with
 	    either &man.sade.8; or &man.gpart.8;.  If the disks are
 	    MBR-formatted, booteasy can be installed on both disks
 	    with &man.boot0cfg.8; so that the computer can dual boot
 	    to the old or new system after the copying is done.</para>
 
 	  <para>Once the new disk set up,
 	    the data cannot just be copied.  Instead, use tools that
 	    understand device files and system flags, such as
 	    &man.dump.8;.  Although it is recommended
 	    to move the data while in single-user mode, it
 	    is not required.</para>
 
 	  <para>When the disks are formatted with
 	    <acronym>UFS</acronym>, never use anything but
 	    &man.dump.8; and &man.restore.8; to move the root file
 	    system.  These commands should also be used when moving a
 	    single partition to another empty partition.  The sequence
 	    of steps to use <command>dump</command> to move the data
 	    from one <acronym>UFS</acronym> partitions to a new
 	    partition is:</para>
 
 	  <procedure>
 	    <step>
 	      <para><command>newfs</command> the new partition.</para>
 	    </step>
 
 	    <step>
 	      <para><command>mount</command> it on a temporary mount
 		point.</para>
 	    </step>
 
 	    <step>
 	      <para><command>cd</command> to that directory.</para>
 	    </step>
 
 	    <step>
 	      <para><command>dump</command> the old partition, piping
 		output to the new one.</para>
 	    </step>
 	  </procedure>
 
 	  <para>For example, to move
 	    <filename>/dev/ada1s1a</filename> with
 	    <filename>/mnt</filename> as the temporary mount point,
 	    type:</para>
 
 	  <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput>
 &prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput>
 &prompt.root; <userinput>cd /mnt</userinput>
 &prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen>
 
 	  <para>Rearranging partitions with
 	    <command>dump</command> takes a bit more work.  To merge a
 	    partition like <filename>/var</filename> into its parent,
 	    create the new partition large enough for both, move the
 	    parent partition as described above, then move the child
 	    partition into the empty directory that the first move
 	    created:</para>
 
 	  <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput>
 &prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput>
 &prompt.root; <userinput>cd /mnt</userinput>
 &prompt.root; <userinput>dump 0af - / | restore rf -</userinput>
 &prompt.root; <userinput>cd var</userinput>
 &prompt.root; <userinput>dump 0af - /var | restore rf -</userinput></screen>
 
 	  <para>To split a directory from its parent, say putting
 	    <filename>/var</filename> on its own partition when it was
 	    not before, create both partitions, then mount the child
 	    partition on the appropriate directory in the temporary
 	    mount point, then move the old single partition:</para>
 
 	  <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput>
 &prompt.root; <userinput>newfs /dev/ada1s1d</userinput>
 &prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput>
 &prompt.root; <userinput>mkdir /mnt/var</userinput>
 &prompt.root; <userinput>mount /dev/ada1s1d /mnt/var</userinput>
 &prompt.root; <userinput>cd /mnt</userinput>
 &prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen>
 
 	  <para>The &man.cpio.1; and &man.pax.1; utilities are also
 	    available for moving user data.  These are known to lose
 	    file flag information, so use them with caution.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="safe-softupdates">
 	  <para>Which partitions can safely use Soft Updates?  I have
 	    heard that Soft Updates on <filename>/</filename> can
 	    cause problems.  What about Journaled Soft Updates?</para>
 	</question>
 
 	<answer>
 	  <para>Short answer: Soft Updates can usually be safely used
 	    on all partitions.</para>
 
 	  <para>Long answer:  Soft Updates has two characteristics
 	    that may be undesirable on certain partitions.  First, a
 	    Soft Updates partition has a small chance of losing data
 	    during a system crash.  The partition will not be
 	    corrupted as the data will simply be lost.  Second, Soft
 	    Updates can cause temporary space shortages.</para>
 
 	  <para>When using Soft Updates, the kernel can take up to
 	    thirty seconds to write changes to the physical disk.
 	    When a large file is deleted the file still resides on
 	    disk until the kernel actually performs the deletion.
 	    This can cause a very simple race condition.  Suppose
 	    one large file is deleted and another large file is
 	    immediately created.  The first large file is not yet
 	    actually removed from the physical disk, so the disk might
 	    not have enough room for the second large file.  This will
 	    produce an error that the partition does not have enough
 	    space, even though a large chunk of space has just been
 	    released.  A few seconds later, the file creation works as
 	    expected.</para>
 
 	  <para>If a system should crash after the kernel accepts a
 	    chunk of data for writing to disk, but before that data is
 	    actually written out, data could be lost.  This risk is
 	    extremely small, but generally manageable.</para>
 
 	  <para>These issues affect all partitions using Soft Updates.
 	    So, what does this mean for the root partition?</para>
 
 	  <para>Vital information on the root partition changes very
 	    rarely.  If the system crashed during the thirty-second
 	    window after such a change is made, it is possible that
 	    data could be lost.  This risk is negligible for most
 	    applications, but be aware that it exists.  If
 	    the system cannot tolerate this much risk, do not use
 	    Soft Updates on the root file system!</para>
 
 	  <para><filename>/</filename> is traditionally one of the
 	    smallest partitions.  If
 	    <filename>/tmp</filename> is on
 	    <filename>/</filename>, there may be intermittent
 	    space problems.  Symlinking <filename>/tmp</filename> to
 	    <filename>/var/tmp</filename> will solve this
 	    problem.</para>
 
 	  <para>Finally, &man.dump.8; does not work in live mode (-L)
 	    on a filesystem, with Journaled Soft Updates
 	    (<acronym>SU+J</acronym>).</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="mount-foreign-fs">
 	  <para>Can I mount other foreign file systems under
 	    &os;?</para>
 	</question>
 
 	<answer>
 	  <para>&os; supports a variety of other file systems.</para>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>UFS</term>
 
 	      <listitem>
 		<para>UFS CD-ROMs can be mounted directly on &os;.
 		  Mounting disk partitions from Digital UNIX and other
 		  systems that support UFS may be more complex,
 		  depending on the details of the disk partitioning
 		  for the operating system in question.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>ext2/ext3</term>
 
 	      <listitem>
 		<para>&os; supports <literal>ext2fs</literal> and
 		  <literal>ext3fs</literal> partitions.  See
 		  &man.ext2fs.5; for more information.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>NTFS</term>
 
 	      <listitem>
 		<para>FUSE based NTFS support is available as a port
 		  (<package>sysutils/fusefs-ntfs</package>).  For more
 		  information see <link
 		    xlink:href="http://www.tuxera.com/community/ntfs-3g-manual/"><application>ntfs-3g</application></link>.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>FAT</term>
 
 	      <listitem>
 		<para>&os; includes a read-write FAT driver.  For more
 		  information, see &man.mount.msdosfs.8;.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>ZFS</term>
 
 	      <listitem>
 		<para>&os; includes a port of &sun;'s ZFS driver.  The
 		  current recommendation is to use it only on
 		  &arch.amd64; platforms with sufficient memory.  For
 		  more information, see &man.zfs.8;.</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>&os; includes the Network File System
 	    <acronym>NFS</acronym> and the &os; Ports Collection
 	    provides several FUSE applications to support many other
 	    file systems.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="mount-dos">
 	  <para>How do I mount a secondary DOS partition?</para>
 	</question>
 
 	<answer>
 	  <para>The secondary DOS partitions are found after
 	    <emphasis>all</emphasis> the primary partitions.  For
 	    example, if <literal>E</literal> is the
 	    second DOS partition on the second SCSI drive, there will
 	    be a device file for <quote>slice 5</quote> in
 	    <filename>/dev</filename>.  To mount it:</para>
 
 	  <screen>&prompt.root; <userinput>mount -t msdosfs /dev/da1s5 /dos/e</userinput></screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="crypto-file-system">
 	  <para>Is there a cryptographic file system for &os;?</para>
 	</question>
 
 	<answer>
 	  <para>Yes, &man.gbde.8; and &man.geli.8;.
 	    See the <link
 	      xlink:href="&url.books.handbook;/disks-encrypting.html">Encrypting
 	      Disk Partitions</link> section of the &os;
 	    Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="grub-loader">
 	  <para>How do I boot &os; and &linux; using
 	    <application>GRUB</application>?</para>
 	</question>
 
 	<answer>
 	  <para>To boot &os; using <application>GRUB</application>,
 	    add the following to either
 	    <filename>/boot/grub/menu.lst</filename> or
 	    <filename>/boot/grub/grub.conf</filename>, depending upon
 	    which is used by the &linux; distribution.</para>
 
 	  <programlisting>title &os; 9.1
 	root <replaceable>(hd0,a)</replaceable>
 	kernel /boot/loader</programlisting>
 
 	  <para>Where <replaceable>hd0,a</replaceable> points to the
 	    root partition on the first disk.  To specify
 	    the slice number, use something like this
 	    <replaceable>(hd0,2,a)</replaceable>.  By default, if the
 	    slice number is omitted, <application>GRUB</application>
 	    searches the first slice
 	    which has the <literal>a</literal> partition.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="booteasy-loader">
 	  <para>How do I boot &os; and &linux; using
 	    <application>BootEasy?</application></para>
 	</question>
 
 	<answer>
 	  <para>Install LILO at the start of the &linux; boot
 	    partition instead of in the Master Boot Record.  Then boot
 	    LILO from <application>BootEasy</application>.</para>
 
 	  <para>This is recommended when running &windows; and &linux;
 	    as it makes it simpler to get &linux; booting again if
 	    &windows; is reinstalled.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="changing-bootprompt">
 	  <para>How do I change the boot prompt from
 	    <literal>???</literal> to something more
 	    meaningful?</para>
 	</question>
 
 	<answer>
 	  <para>This cannot be accomplished with the standard boot
 	    manager without rewriting it.  There are a number of other
 	    boot managers in the <filename>sysutils</filename>
 	    category of the Ports Collection.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="removable-drives">
 	  <para>How do I use a new removable drive?</para>
 	</question>
 
 	<answer>
 	  <para>If the drive already has a file system on it,
 	    use a command like this:</para>
 
 	  <screen>&prompt.root; <userinput>mount -t msdosfs /dev/da0s1 /mnt</userinput></screen>
 
 	  <para>If the drive will only be used with &os; systems,
 	    partition it with <acronym>UFS</acronym> or
 	    <acronym>ZFS</acronym>.  This will provide long filename
 	    support, improvement in performance, and stability.  If
 	    the drive will be used by other operating systems, a more
 	    portable choice, such as msdosfs, is better.</para>
 
 	  <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da0 count=2</userinput>
 &prompt.root; <userinput>gpart create -s GPT /dev/da0</userinput>
 &prompt.root; <userinput>gpart add -t freebsd-ufs /dev/da0</userinput></screen>
 
 	  <para>Finally, create a new file system:</para>
 
 	  <screen>&prompt.root; <userinput>newfs /dev/da0p1</userinput></screen>
 
 	  <para>and mount it:</para>
 
 	  <screen>&prompt.root; <userinput>mount /dev/da0s1 /mnt</userinput></screen>
 
 	  <para>It is a good idea to add a line to
 	    <filename>/etc/fstab</filename> (see &man.fstab.5;) so you
 	    can just type <command>mount /mnt</command> in the
 	    future:</para>
 
 	  <programlisting>/dev/da0p1 /mnt ufs rw,noauto 0 0</programlisting>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="mount-cd-superblock">
 	  <para>Why do I get <errorname>Incorrect super
 	      block</errorname> when mounting a CD?</para>
 	</question>
 
 	<answer>
 	  <para>The type of device to mount must be specified.  This
 	    is described in the Handbook section on <link
 	      xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using
 	      Data CDs</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="cdrom-not-configured">
 	  <para>Why do I get <errorname>Device not
 	      configured</errorname> when mounting a CD?</para>
 	</question>
 
 	<answer>
 	  <para>This generally means that there is no CD in the
 	    drive, or the drive is not visible on the bus.
 	    Refer to the <link
 	      xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using
 	      Data CDs</link> section of the Handbook for a detailed
 	    discussion of this issue.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="cdrom-unicode-filenames">
 	  <para>Why do all non-English characters in filenames show up
 	    as <quote>?</quote> on my CDs when mounted in &os;?</para>
 	</question>
 
 	<answer>
 	  <para>The CD probably uses the <quote>Joliet</quote>
 	    extension for storing information about files and
 	    directories.  This is discussed in the Handbook section on
 	   <link
 	      xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using
 	      Data CD-ROMs</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="burncd-isofs">
 	  <para>A CD burned under &os; cannot be read
 	    under any other operating system.  Why?</para>
 	</question>
 
 	<answer>
 	  <para>This means a raw file was burned to the CD, rather
 	    than creating an ISO&nbsp;9660 file system.  Take a look
 	    at the Handbook section on <link
 	      xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using
 	      Data <acronym>CD</acronym>s</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="copy-cd">
 	  <para>How can I create an image of a data CD?</para>
 	</question>
 
 	<answer>
 	  <para>This is discussed in the Handbook section on <link
 	      xlink:href="&url.books.handbook;/creating-cds.html#mkisofs">Writing
 	      Data to an <acronym>ISO</acronym> File System</link>.
 	    For more on working with CD-ROMs, see the <link
 	      xlink:href="&url.books.handbook;/creating-cds.html">Creating
 	      CDs Section</link> in the Storage chapter in the
 	    Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="mount-audio-CD">
 	  <para>Why can I not <command>mount</command> an audio
 	    CD?</para>
 	</question>
 
 	<answer>
 	  <para>Trying to mount an audio CD will produce an error
 	    like <errorname>cd9660: /dev/cd0: Invalid
 	      argument</errorname>.  This is because
 	    <command>mount</command> only works on file systems.
 	    Audio CDs do not have file systems; they just have data.
 	    Instead, use a program that reads audio CDs, such as the
 	    <package>audio/xmcd</package> package or port.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="multi-session-CD">
 	  <para>How do I <command>mount</command> a multi-session
 	    CD?</para>
 	</question>
 
 	<answer>
 	  <para>By default, &man.mount.8; will attempt to mount the
 	    last data track (session) of a CD.  To
 	    load an earlier session, use the
 	    <option>-s</option> command line argument.  Refer to
 	    &man.mount.cd9660.8; for specific examples.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="user-floppymount">
 	  <para>How do I let ordinary users mount CD-ROMs, DVDs,
 	    USB drives, and other removable media?</para>
 	</question>
 
 	<answer>
 	  <para>As <systemitem class="username">root</systemitem> set
 	    the sysctl variable <varname>vfs.usermount</varname> to
 	    <literal>1</literal>.</para>
 
 	  <screen>&prompt.root; <userinput>sysctl vfs.usermount=1</userinput></screen>
 
 	  <para>To make this persist across reboots, add the line
 	    <literal>vfs.usermount=1</literal> to
 	    <filename>/etc/sysctl.conf</filename> so that it is reset
 	    at system boot time.</para>
 
 	  <para>Users can only mount devices they have read
 	    permissions to.  To allow users to mount a device
 	    permissions must be set in
 	    <filename>/etc/devfs.conf</filename>.</para>
 
 	  <para>For example, to allow users to mount the first USB
 	    drive add:</para>
 
 	  <programlisting># Allow all users to mount a USB drive.
 	    own       /dev/da0       root:operator
 	    perm      /dev/da0       0666</programlisting>
 
 	  <para>All users can now mount devices they could read onto a
 	    directory that they own:</para>
 
 	  <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
 &prompt.user; <userinput>mount -t msdosfs /dev/da0 ~/my-mount-point</userinput></screen>
 
 	  <para>Unmounting the device is simple:</para>
 
 	  <screen>&prompt.user; <userinput>umount ~/my-mount-point</userinput></screen>
 
 	  <para>Enabling <varname>vfs.usermount</varname>, however,
 	    has negative security implications.  A better way to
 	    access &ms-dos; formatted media is to use the
 	    <package>emulators/mtools</package> package in the Ports
 	    Collection.</para>
 
 	  <note>
 	    <para>The device name used in the previous examples must
 	      be changed according to the configuration.</para>
 	  </note>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="du-vs-df">
 	  <para>The <command>du</command> and <command>df</command>
 	    commands show different amounts of disk space available.
 	    What is going on?</para>
 	</question>
 
 	<answer>
 	  <para>This is due to how these commands actually work.
 	    <command>du</command> goes through the directory tree,
 	    measures how large each file is, and presents the totals.
 	    <command>df</command> just asks the file system how much
 	    space it has left.  They seem to be the same thing, but a
 	    file without a directory entry will affect
 	    <command>df</command> but not
 	    <command>du</command>.</para>
 
 	  <para>When a program is using a file, and the file is
 	    deleted, the file is not really removed from the file
 	    system until the program stops using it.  The file is
 	    immediately deleted from the directory listing, however.
 	    As an example, consider a file large enough
 	    to affect the output of
 	    <command>du</command> and <command>df</command>.  A
 	    file being viewed with <command>more</command> can be
 	    deleted wihout causing an error.
 	    The entry is
 	    removed from the directory so no other program or user can
 	    access it.  However, <command>du</command> shows that it
 	    is gone as it has walked the directory tree and the
 	    file is not listed.  <command>df</command> shows that it
 	    is still there, as the file system knows that
 	    <command>more</command> is still using that space.  Once
 	    the <command>more</command> session ends,
 	    <command>du</command> and <command>df</command> will
 	    agree.</para>
 
 	  <para>This situation is common on web servers.  Many people
 	    set up a &os; web server and forget to rotate the log
 	    files.  The access log fills up <filename>/var</filename>.
 	    The new administrator deletes the file, but the system
 	    still complains that the partition is full.  Stopping and
 	    restarting the web server program would free the file,
 	    allowing the system to release the disk space.  To prevent
 	    this from happening, set up &man.newsyslog.8;.</para>
 
 	  <para>Note that Soft Updates can delay the freeing of disk
 	    space and it can take up to 30 seconds for the
 	    change to be visible.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="add-swap-space">
 	  <para>How can I add more swap space?</para>
 	</question>
 
 	<answer>
 	  <para>This section <link
 	      xlink:href="&url.books.handbook;/adding-swap-space.html">of
 	      the Handbook</link> describes how to do this.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="manufacturer-disk-size">
 	  <para>Why does &os; see my disk as smaller than the
 	    manufacturer says it is?</para>
 	</question>
 
 	<answer>
 	  <para>Disk manufacturers calculate gigabytes as a billion
 	    bytes each, whereas &os; calculates them as
 	    1,073,741,824&nbsp;bytes each.  This explains why, for
 	    example, &os;'s boot messages will report a disk that
 	    supposedly has 80&nbsp;GB as holding
 	    76,319&nbsp;MB.</para>
 
 	  <para>Also note that &os; will (by default) <link
 	      linkend="disk-more-than-full">reserve</link> 8% of the
 	    disk space.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="disk-more-than-full">
 	  <para>How is it possible for a partition to be more than
 	    100% full?</para>
 	</question>
 
 	<answer>
 	  <para>A portion of each UFS partition (8%, by default) is
 	    reserved for use by the operating system and the
 	    <systemitem class="username">root</systemitem> user.
 	    &man.df.1; does not count that space when calculating the
 	    <literal>Capacity</literal> column, so it can exceed 100%.
 	    Notice that the <literal>Blocks</literal>
 	    column is always greater than the sum of the
 	    <literal>Used</literal> and <literal>Avail</literal>
 	    columns, usually by a factor of 8%.</para>
 
 	  <para>For more details, look up <option>-m</option> in
 	    &man.tunefs.8;.</para>
 	</answer>
       </qandaentry>
 
     </qandaset>
   </chapter>
 
   <chapter xml:id="all-about-zfs">
     <title>ZFS</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="how-much-ram-for-zfs">
 	  <para>What is the minimum amount of RAM one should have to
 	    run ZFS?</para>
 	</question>
 
 	<answer>
 	  <para>A minimum of 4GB of RAM is required for comfortable
 	    usage, but individual workloads can vary widely.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="what-is-zil">
 	  <para>What is the ZIL and when does it get used?</para>
 	</question>
 
 	<answer>
 	  <para>The <acronym>ZIL</acronym> (<acronym>ZFS</acronym>
 	    intent log) is a write log used to implement posix write
 	    commitment semantics across crashes.  Normally writes are
 	    bundled up into transaction groups and written to disk
 	    when filled (<quote>Transaction Group Commit</quote>).
 	    However syscalls like &man.fsync.2; require a commitment
 	    that the data is written to stable storage before
 	    returning.  The ZIL is needed for writes that have been
 	    acknowledged as written but which are not yet on disk as
 	    part of a transaction.  The transaction groups are
 	    timestamped.  In the event of a crash the last valid
 	    timestamp is found and missing data is merged in from the
 	    ZIL.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="need-ssd-for-zil">
 	  <para>Do I need a SSD for ZIL?</para>
 	</question>
 
 	<answer>
 	  <para>By default, ZFS stores the ZIL in the pool with all
 	    the data.  If an application has a heavy write load,
 	    storing the ZIL in a separate device that has very fast
 	    synchronous, sequential write performance can improve
 	    overall system performance.  For other workloads, a SSD
 	    is unlikely to make much of an improvement.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="what-is-l2arc">
 	  <para>What is the L2ARC?</para>
 	</question>
 
 	<answer>
 	  <para>The <acronym>L2ARC</acronym> is a read cache stored on
 	    a fast device such as an <acronym>SSD</acronym>.  This
 	    cache is not persistent across reboots.  Note that RAM is
 	    used as the first layer of cache and the L2ARC is only
 	    needed if there is insufficient RAM.</para>
 
 	  <para>L2ARC needs space in the ARC to index it.  So,
 	    perversely, a working set that fits perfectly in the ARC
 	    will not fit perfectly any more if a L2ARC is used because
 	    part of the ARC is holding the L2ARC index, pushing part
 	    of the working set into the L2ARC which is slower than
 	    RAM.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="should-enable-dedup">
 	  <para>Is enabling deduplication advisable?</para>
 	</question>
 
 	<answer>
 	  <para>Generally speaking, no.</para>
 
 	  <para>Deduplication takes up a significant amount of RAM and
 	    may slow down read and write disk access times.  Unless
 	    one is storing data that is very heavily duplicated, such
 	    as virtual machine images or user backups, it is possible
 	    that deduplication will do more harm than good.  Another
 	    consideration is the inability to revert deduplication
 	    status.  If data is written when deduplication is enabled,
 	    disabling dedup will not cause those blocks which were
 	    deduplicated to be replicated until they are next
 	    modified.</para>
 
 	  <para>Deduplication can also lead to some unexpected
 	    situations.  In particular, deleting files may become much
 	    slower.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="zpool-fully-full">
 	  <para>I cannot delete or create files on my ZFS pool.  How
 	    can I fix this?</para>
 	</question>
 
 	<answer>
 	  <para>This could happen because the pool is 100% full.  ZFS
 	    requires space on the disk to write transaction metadata.
 	    To restore the pool to a usable state, truncate the file
 	    to delete:</para>
 
 	  <screen>&prompt.user; <userinput>truncate -s 0 unimportant-file</userinput></screen>
 
 	  <para>File truncation works because a new transaction is not
 	    started, new spare blocks are created instead.</para>
 
 	  <note>
 	    <para>On systems with additional ZFS dataset tuning, such
 	      as deduplication, the space may not be immediately
 	      available</para>
 	  </note>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="zfs-ssd-trim">
 	  <para>Does ZFS support TRIM for Solid State Drives?</para>
 	</question>
 
 	<answer>
 	  <para>ZFS TRIM support was added to &os;&nbsp;10-CURRENT
 	    with revision r<revnumber>240868</revnumber>.  ZFS TRIM
 	    support was added to all &os;-STABLE branches in
 	    r<revnumber>252162</revnumber> and
 	    r<revnumber>251419</revnumber>, respectively.</para>
 
 	  <para>ZFS TRIM is enabled by default, and can be turned off
 	    by adding this line to
 	    <filename>/etc/sysctl.conf</filename>:</para>
 
 	  <programlisting>vfs.zfs.trim.enabled=0</programlisting>
 
 	  <note>
 	    <para>ZFS TRIM support was added to GELI as of
 	      r<revnumber>286444</revnumber>.  Please see
 	      &man.geli.8; and the <option>-T</option> switch.</para>
 	  </note>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="admin">
     <title>System Administration</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="startup-config-files">
 	  <para>Where are the system start-up configuration
 	    files?</para>
 	</question>
 
 	<answer>
 	  <para>The primary configuration file is
 	    <filename>/etc/defaults/rc.conf</filename> which is
 	    described in &man.rc.conf.5;.  System startup scripts
 	    such as <filename>/etc/rc</filename> and
 	    <filename>/etc/rc.d</filename>, which are described in
 	    &man.rc.8;, include this file.  <emphasis>Do not edit this
 	      file!</emphasis>  Instead, to edit an entry in
 	    <filename>/etc/defaults/rc.conf</filename>, copy the line
 	    into <filename>/etc/rc.conf</filename> and change it
 	    there.</para>
 
 	  <para>For example, if to start &man.named.8;, the
 	    included DNS server:</para>
 
 	  <screen>&prompt.root; <userinput>echo 'named_enable="YES"' &gt;&gt; /etc/rc.conf</userinput></screen>
 
 	  <para>To start up local services, place shell scripts in the
 	    <filename>/usr/local/etc/rc.d</filename> directory.  These
 	    shell scripts should be set executable, the default file
 	    mode is <literal>555</literal>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="adding-users">
 	  <para>How do I add a user easily?</para>
 	</question>
 
 	<answer>
 	  <para>Use the &man.adduser.8; command, or the &man.pw.8;
 	    command for more complicated situations.</para>
 
 	  <para>To remove the user, use the &man.rmuser.8; command or,
 	    if necessary, &man.pw.8;.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="root-not-found-cron-errors">
 	  <para>Why do I keep getting messages like <errorname>root:
 	      not found</errorname> after editing
 	    <filename>/etc/crontab</filename>?</para>
 	</question>
 
 	<answer>
 	  <para>This is normally caused by editing the system crontab.
 	    This is not the correct way to do things as the system
 	    crontab has a different format to the per-user crontabs.
 	    The system
 	    crontab has an extra field, specifying which user to run
 	    the command as.  &man.cron.8; assumes this user is the
 	    first word of the command to execute.  Since no such
 	    command exists, this error message is displayed.</para>
 
 	  <para>To delete the extra, incorrect crontab:</para>
 
 	  <screen>&prompt.root; <userinput>crontab -r</userinput></screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="su-wheel-group">
 	  <para>Why do I get the error, <errorname>you are not in the
 	      correct group to su root</errorname> when I try to
 	    <command>su</command> to <systemitem
 	      class="username">root</systemitem>?</para>
 	</question>
 
 	<answer>
 	  <para>This is a security feature.  In order to
 	    <command>su</command> to
 	    <systemitem class="username">root</systemitem>, or any
 	    other account with superuser privileges, the user account
 	    must be a member of the
 	    <systemitem class="groupname">wheel</systemitem> group.
 	    If this feature were not there, anybody with an
 	    account on a system who also found out <systemitem
 	      class="username">root</systemitem>'s password would be
 	    able to gain superuser level access to the system.</para>
 
 	  <para>To allow someone to <command>su</command> to
 	    <systemitem class="username">root</systemitem>, put
 	    them in the <systemitem
 	      class="groupname">wheel</systemitem> group using
 	    <command>pw</command>:</para>
 
 	  <screen>&prompt.root; <userinput>pw groupmod wheel -m lisa</userinput></screen>
 
 	  <para>The above example will add user <systemitem
 	      class="username">lisa</systemitem> to the group
 	    <systemitem class="groupname">wheel</systemitem>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="rcconf-readonly">
 	  <para>I made a mistake in <filename>rc.conf</filename>, or
 	    another startup file, and now I cannot edit it because the
 	    file system is read-only.  What should I do?</para>
 	</question>
 
 	<answer>
 	  <para>Restart the system using <userinput>boot
 	      -s</userinput> at the loader prompt to enter single-user
 	    mode.  When prompted for a shell pathname, press
 	    <keycap>Enter</keycap> and run <command>mount -urw
 	      /</command> to re-mount the root file system in
 	    read/write mode.  You may also need to run <command>mount
 	      -a -t ufs</command> to mount the file system where your
 	    favorite editor is defined.  If that editor is on a
 	    network file system, either configure the network manually
 	    before mounting the network file systems, or use an editor
 	    which resides on a local file system, such as
 	    &man.ed.1;.</para>
 
 	  <para>In order to use a full screen editor such as
 	    &man.vi.1; or &man.emacs.1;, run
 	    <command>export TERM=xterm</command>
 	    so that these editors can load the correct data from the
 	    &man.termcap.5; database.</para>
 
 	  <para>After performing these steps, edit
 	    <filename>/etc/rc.conf</filename> to
 	    fix the syntax error.  The error message displayed
 	    immediately after the kernel boot messages should indicate
 	    the number of the line in the file which is at
 	    fault.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="printer-setup">
 	  <para>Why am I having trouble setting up my printer?</para>
 	</question>
 
 	<answer>
 	  <para>See the <link
 	      xlink:href="&url.books.handbook;/printing.html">Handbook
 	      entry on printing</link> for troubleshooting
 	    tips.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="keyboard-mappings">
 	  <para>How can I correct the keyboard mappings for my
 	    system?</para>
 	</question>
 
 	<answer>
 	  <para>Refer to the Handbook section on <link
 	      xlink:href="&url.books.handbook;/using-localization.html">using
 	      localization</link>, specifically the section on <link
 	      xlink:href="&url.books.handbook;/using-localization.html#setting-console">console
 	      setup</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="user-quotas">
 	  <para>Why can I not get user quotas to work properly?</para>
 	</question>
 
 	<answer>
 	  <orderedlist>
 	    <listitem>
 	      <para>It is possible that the kernel is not configured
 		to use quotas.  In this case,
 		add the following line to the kernel configuration
 		file and recompile the kernel:</para>
 
 	      <programlisting>options QUOTA</programlisting>
 
 	      <para>Refer to the <link
 		  xlink:href="&url.books.handbook;/quotas.html">Handbook
 		  entry on quotas</link> for full details.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Do not turn on quotas on
 		<filename>/</filename>.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Put the quota file on the file system that the
 		quotas are to be enforced on:</para>
 
 	      <informaltable frame="none" pgwide="1">
 		<tgroup cols="2">
 		  <thead>
 		    <row>
 		      <entry>File System</entry>
 
 		      <entry>Quota file</entry>
 		    </row>
 		  </thead>
 
 		  <tbody>
 		    <row>
 		      <entry><filename>/usr</filename></entry>
 
 		      <entry><filename>/usr/admin/quotas</filename></entry>
 		    </row>
 
 		    <row>
 		      <entry><filename>/home</filename></entry>
 
 		      <entry><filename>/home/admin/quotas</filename></entry>
 		    </row>
 
 		    <row>
 		      <entry>&hellip;</entry>
 
 		      <entry>&hellip;</entry>
 		    </row>
 		  </tbody>
 		</tgroup>
 	      </informaltable>
 	    </listitem>
 	  </orderedlist>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="sysv-ipc">
 	  <para>Does &os; support System V IPC primitives?</para>
 	</question>
 
 	<answer>
 	  <para>Yes, &os; supports System V-style IPC, including
 	    shared memory, messages and semaphores, in the
 	    <filename>GENERIC</filename> kernel.  With a custom
 	    kernel, support may be loaded with the
 	    <filename>sysvshm.ko</filename>,
 	    <filename>sysvsem.ko</filename> and
 	    <filename>sysvmsg.ko</filename> kernel modules, or
 	    enabled in the custom kernel by adding the following lines
 	    to the kernel configuration file:</para>
 
 	  <programlisting>options    SYSVSHM          # enable shared memory
 options    SYSVSEM          # enable for semaphores
 options    SYSVMSG          # enable for messaging</programlisting>
 
 	  <para>Recompile and install the kernel.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="sendmail-alternative">
 	  <para>What other mail-server software can I use instead of
 	    <application>Sendmail</application>?</para>
 	</question>
 
 	<answer>
 	  <para>The <link
 	      xlink:href="http://www.sendmail.org/"><application>Sendmail</application></link>
 	    server is the default mail-server software for &os;, but
 	    it can be replaced with another
 	    MTA installed from the Ports Collection.  Available ports
 	    include <package>mail/exim</package>,
 	    <package>mail/postfix</package>, and
 	    <package>mail/qmail</package>.  Search the mailing lists
 	    for discussions regarding the advantages and disadvantages
 	    of the available MTAs.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="forgot-root-pw">
 	  <para>I have forgotten the <systemitem
 	      class="username">root</systemitem> password!  What do I
 	    do?</para>
 	</question>
 
 	<answer>
 	  <para>Do not panic!  Restart the system, type
 	    <userinput>boot -s</userinput> at the
 	    <literal>Boot:</literal> prompt to enter single-user mode.
 	    At the question about the shell to use, hit
 	    <keycap>Enter</keycap> which will display a
 	    &prompt.root; prompt.  Enter <command>mount
 	      -urw /</command> to remount the root file system
 	    read/write, then run <command>mount -a</command> to
 	    remount all the file systems.  Run <command>passwd
 	      root</command> to change the <systemitem
 	      class="username">root</systemitem> password then run
 	    &man.exit.1; to continue booting.</para>
 
 	  <note>
 	    <para>If you are still prompted to give the <systemitem
 		class="username">root</systemitem> password when
 	      entering the single-user mode, it means that the console
 	      has been marked as <literal>insecure</literal> in
 	      <filename>/etc/ttys</filename>.  In this case, it will
 	      be required to boot from a &os; installation disk,
 	      choose the <guimenuitem>Live CD</guimenuitem> or
 	      <guimenuitem>Shell</guimenuitem> at the beginning of the
 	      install process and issue the commands mentioned above.
 	      Mount the specific partition in this
 	      case and then chroot to it.  For example, replace
 	      <command>mount -urw /</command> with
 	      <command>mount /dev/ada0p1 /mnt; chroot /mnt</command>
 	      for a system on
 	      <replaceable>ada0p1</replaceable>.</para>
 	  </note>
 
 	  <note>
 	    <para>If the root partition cannot be mounted from
 	      single-user mode, it is possible that the partitions are
 	      encrypted and it is impossible to mount them without the
 	      access keys.  For more information see the section
 	      about encrypted disks in the &os; <link
 		xlink:href="&url.books.handbook;/disks-encrypting.html">Handbook</link>.</para>
 	  </note>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="CAD-reboot">
 	  <para>How do I keep <keycombo
 	      action="simul"><keycap>Control</keycap><keycap>Alt</keycap><keycap>Delete</keycap></keycombo>
 	    from rebooting the system?</para>
 	</question>
 
 	<answer>
 	  <para>When using &man.vt.4;, the default console
 	    driver, this can be done by setting the following
 	    &man.sysctl.8;:</para>
 
 	  <screen>&prompt.root; <userinput>sysctl kern.vt.kbd_reboot=0</userinput></screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="dos-to-unix-txt">
 	  <para>How do I reformat DOS text files to &unix;
 	    ones?</para>
 	</question>
 
 	<answer>
 	  <para>Use this &man.perl.1; command:</para>
 
 	  <screen>&prompt.user; <userinput>perl -i.bak -npe 's/\r\n/\n/g' file(s)</userinput></screen>
 
 	  <para>where <replaceable>file(s)</replaceable> is one or
 	    more files to process.  The modification is done in-place,
 	    with the original file stored with a
 	    <filename>.bak</filename> extension.</para>
 
 	  <para>Alternatively, use &man.tr.1;:</para>
 
 	  <screen>&prompt.user; <userinput>tr -d '\r' &lt; dos-text-file &gt; unix-file</userinput></screen>
 
 	  <para><replaceable>dos-text-file</replaceable> is the file
 	    containing DOS text while
 	    <replaceable>unix-file</replaceable> will contain the
 	    converted output.  This can be quite a bit faster than
 	    using <command>perl</command>.</para>
 
 	  <para>Yet another way to reformat DOS text files is to use
 	    the <package>converters/dosunix</package> port from the
 	    Ports Collection.  Consult its documentation about the
 	    details.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="reread-rc">
 	  <para>How do I re-read <filename>/etc/rc.conf</filename> and
 	    re-start <filename>/etc/rc</filename> without a
 	    reboot?</para>
 	</question>
 
 	<answer>
 	  <para>Go into single-user mode and then back to multi-user
 	    mode:</para>
 
 	  <screen>&prompt.root; <userinput>shutdown now</userinput>
 &prompt.root; <userinput>return</userinput>
 &prompt.root; <userinput>exit</userinput></screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="release-candidate">
 	  <para>I tried to update my system to the latest
 	    <emphasis>-STABLE</emphasis>, but got
 	    <emphasis>-BETA<replaceable>x</replaceable></emphasis>,
 	    <emphasis>-RC</emphasis> or
 	    <emphasis>-PRERELEASE</emphasis>!  What is going
 	    on?</para>
 	</question>
 
 	<answer>
 	  <para>Short answer: it is just a name.
 	    <emphasis>RC</emphasis> stands for <quote>Release
 	      Candidate</quote>.  It signifies that a release is
 	    imminent.  In &os;, <emphasis>-PRERELEASE</emphasis> is
 	    typically synonymous with the code freeze before a
 	    release.  (For some releases, the
 	    <emphasis>-BETA</emphasis> label was used in the same way
 	    as <emphasis>-PRERELEASE</emphasis>.)</para>
 
 	  <para>Long answer: &os; derives its releases from one of two
 	    places.  Major, dot-zero, releases, such as 9.0-RELEASE
 	    are branched from the head of the development stream,
 	    commonly referred to as <link
 	      linkend="current">-CURRENT</link>.  Minor releases, such
 	    as 6.3-RELEASE or 5.2-RELEASE, have been snapshots of the
 	    active <link linkend="stable">-STABLE</link> branch.
 	    Starting with 4.3-RELEASE, each release also now has its
 	    own branch which can be tracked by people requiring an
 	    extremely conservative rate of development (typically only
 	    security advisories).</para>
 
 	  <para>When a release is about to be made, the branch from
 	    which it will be derived from has to undergo a certain
 	    process.  Part of this process is a code freeze.  When a
 	    code freeze is initiated, the name of the branch is
 	    changed to reflect that it is about to become a release.
 	    For example, if the branch used to be called 6.2-STABLE,
 	    its name will be changed to 6.3-PRERELEASE to signify the
 	    code freeze and signify that extra pre-release testing
 	    should be happening.  Bug fixes can still be committed to
 	    be part of the release.  When the source code is in shape
 	    for the release the name will be changed to 6.3-RC to
 	    signify that a release is about to be made from it.  Once
 	    in the RC stage, only the most critical bugs found can be
 	    fixed.  Once the release (6.3-RELEASE in this example) and
 	    release branch have been made, the branch will be renamed
 	    to 6.3-STABLE.</para>
 
 	  <para>For more information on version numbers and the
 	    various Subversion branches, refer to the <link
 	      xlink:href="&url.articles.releng;/article.html">Release
 	      Engineering</link> article.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="kernel-chflag-failure">
 	  <para>I tried to install a new kernel, and the
 	    &man.chflags.1; failed.  How do I get around this?</para>
 	</question>
 
 	<answer>
 	  <para>Short answer: the security level is
 	    greater than 0.  Reboot directly to single-user mode to
 	    install the kernel.</para>
 
 	  <para>Long answer: &os; disallows changing system flags at
 	    security levels greater than 0.  To check the current
 	    security level:</para>
 
 	  <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
 
 	  <para>The security level cannot be lowered in multi-user
 	    mode, so boot to single-user mode to install the kernel,
 	    or change the security level in
 	    <filename>/etc/rc.conf</filename> then reboot.  See the
 	    &man.init.8; manual page for details on
 	    <literal>securelevel</literal>, and see
 	    <filename>/etc/defaults/rc.conf</filename> and the
 	    &man.rc.conf.5; manual page for more information on
 	    <filename>rc.conf</filename>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="kernel-securelevel-time">
 	  <para>I cannot change the time on my system by more than one
 	    second!  How do I get around this?</para>
 	</question>
 
 	<answer>
 	  <para>Short answer: the system is at a security level
 	    greater than 1.  Reboot directly to single-user mode to
 	    change the date.</para>
 
 	  <para>Long answer: &os; disallows changing the time by more
 	    that one second at security levels greater than 1.  To
 	    check the security level:</para>
 
 	  <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
 
 	  <para>The security level cannot be lowered in multi-user
 	    mode.  Either boot to single-user mode to change the date
 	    or change the security level in
 	    <filename>/etc/rc.conf</filename> and reboot.  See the
 	    &man.init.8; manual page for details on
 	    <literal>securelevel</literal>, and see
 	    <filename>/etc/defaults/rc.conf</filename> and the
 	    &man.rc.conf.5; manual page for more information on
 	    <filename>rc.conf</filename>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="statd-mem-leak">
 	  <para>Why is <command>rpc.statd</command> using 256&nbsp;MB
 	    of memory?</para>
 	</question>
 
 	<answer>
 	  <para>No, there is no memory leak, and it is not using
 	    256&nbsp;MB of memory.  For convenience,
 	    <command>rpc.statd</command> maps an obscene amount of
 	    memory into its address space.  There is nothing terribly
 	    wrong with this from a technical standpoint; it just
 	    throws off things like &man.top.1; and &man.ps.1;.</para>
 
 	  <para>&man.rpc.statd.8; maps its status file (resident on
 	    <filename>/var</filename>) into its address space; to save
 	    worrying about remapping the status file later when it
 	    needs to grow, it maps the status file with a generous
 	    size.  This is very evident from the source code, where
 	    one can see that the length argument to &man.mmap.2; is
 	    <literal>0x10000000</literal>, or one sixteenth of the
 	    address space on an IA32, or exactly 256&nbsp;MB.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="unsetting-schg">
 	  <para>Why can I not unset the <literal>schg</literal> file
 	    flag?</para>
 	</question>
 
 	<answer>
 	  <para>The system is running at securelevel greater than 0.
 	    Lower the securelevel and try again.  For more
 	    information, see <link linkend="securelevel">the
 	      <acronym>FAQ</acronym> entry on securelevel</link> and
 	    the &man.init.8; manual page.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="vnlru">
 	  <para>What is <literal>vnlru</literal>?</para>
 	</question>
 
 	<answer>
 	  <para><literal>vnlru</literal> flushes and frees vnodes when
 	    the system hits the <varname>kern.maxvnodes</varname>
 	    limit.  This kernel thread sits mostly idle, and only
 	    activates when there is a huge amount of RAM and users are
 	    accessing tens of thousands of tiny files.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="top-memory-states">
 	  <para>What do the various memory states displayed by
 	    <command>top</command> mean?</para>
 	</question>
 
 	<!-- Provided by John Dyson via Usenet, and later amended -->
 	<answer>
 	  <itemizedlist>
 	    <listitem>
 	      <para><literal>Active</literal>: pages recently
 		statistically used.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><literal>Inactive</literal>: pages recently
 		statistically unused.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><literal>Laundry</literal>: pages recently
 		statistically unused but known to be dirty, that is,
                 whose contents needs to be paged out before they can
 		be reused.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><literal>Free</literal>: pages without data
 		content, which can be immediately reused.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><literal>Wired</literal>: pages that are fixed
 		into memory, usually for kernel purposes, but also
 		sometimes for special use in processes.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>Pages are most often written to disk (sort of a VM
 	    sync) when they are in the laundry state, but active or
 	    inactive pages can also be synced.  This depends upon the
 	    CPU tracking of the modified bit being available, and in
 	    certain situations there can be an advantage for a block
 	    of VM pages to be synced, regardless of the queue they
 	    belong to.  In most common cases, it is best to think of
 	    the laundry queue as a queue of relatively unused
 	    pages that might or might not be in the process of being
 	    written to disk.  The inactive queue contains a mix of
 	    clean and dirty pages; clean pages near the head of the
 	    queue are reclaimed immediately to alleviate a free page
 	    shortage, and dirty pages are moved to the laundry queue
 	    for deferred processing.</para>
 
 	  <para>There are some other flags (e.g., busy flag or busy
 	    count) that might modify some of the described
 	    rules.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="free-memory-amount">
 	  <para>How much free memory is available?</para>
 	</question>
 
 	<!-- Provided by John Dyson via Usenet, and later amended -->
 	<answer>
 	  <para>There are a couple of kinds of <quote>free
 	    memory</quote>.  The most common is the amount of memory
 	    immediately available without reclaiming memory already
 	    in use.  That is the size of the free pages queue plus
 	    some other reserved pages.  This amount is exported by the
 	    <literal>vm.stats.vm.v_free_count</literal>
 	    &man.sysctl.8;, shown, for instance, by &man.top.1;.
 	    Another kind of <quote>free memory</quote> is
 	    the total amount of virtual memory available to userland
 	    processes, which depends on the sum of swap space and
 	    usable memory.  Other kinds of <quote>free memory</quote>
 	    descriptions are also possible, but it is relatively
 	    useless to define these, but rather it is important to
 	    make sure that the paging rate is kept low, and to avoid
 	    running out of swap space.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="var-empty">
 	  <para>What is <filename>/var/empty</filename>?</para>
 	</question>
 
 	<answer>
 	  <para><filename>/var/empty</filename> is a directory that
 	    the &man.sshd.8; program uses when performing privilege
 	    separation.  The <filename>/var/empty</filename>
 	    directory is empty, owned by <systemitem
 	      class="username">root</systemitem> and has the
 	    <literal>schg</literal> flag set.  This directory should
 	    not be deleted.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="newsyslog-expectations">
 	  <para>I just changed
 	    <filename>/etc/newsyslog.conf</filename>.  How can I check
 	    if it does what I expect?</para>
 	</question>
 
 	<answer>
 	  <para>To see what &man.newsyslog.8; will do, use the
 	    following:</para>
 
 	  <screen>&prompt.user; <userinput>newsyslog -nrvv</userinput></screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="timezone">
 	  <para>My time is wrong, how can I change the
 	    timezone?</para>
 	</question>
 
 	<answer>
 	  <para>Use &man.tzsetup.8;.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="x">
     <title>The X Window System and Virtual Consoles</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="whatis-X">
 	  <para>What is the X Window System?</para>
 	</question>
 
 	<answer>
 	  <para>The X Window System (commonly <literal>X11</literal>)
 	    is the most widely available windowing system capable of
 	    running on &unix; or &unix;&nbsp;like systems, including
 	    &os;.  <link xlink:href="http://www.x.org/wiki/">The X.Org
 	      Foundation</link> administers the <link
 	      xlink:href="http://en.wikipedia.org/wiki/X_Window_System_core_protocol">X
 	      protocol standards</link>, with the current reference
 	    implementation, version 11 release &xorg.version;, so
 	    references are often shortened to
 	    <literal>X11</literal>.</para>
 
 	  <para>Many implementations are available for different
 	    architectures and operating systems.  An implementation of
 	    the server-side code is properly known as an <literal>X
 	      server</literal>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="running-X">
 	  <para>I want to run &xorg;, how do I go about it?</para>
 	</question>
 
 	<answer>
 	  <para>To install &xorg; do one of the following:</para>
 
 	  <para>Use the <package>x11/xorg</package>
 	    meta-port, which builds and installs every &xorg;
 	    component.</para>
 
 	  <para>Use <package>x11/xorg-minimal</package>, which builds
 	    and installs only the necessary &xorg; components.</para>
 
 	  <para>Install &xorg; from &os; packages:</para>
 
 	  <screen><userinput>&prompt.root; pkg install xorg</userinput></screen>
 
 	  <para>After the installation of &xorg;, follow the
 	    instructions from the <link
 	      xlink:href="&url.books.handbook;/x-config.html">X11
 	      Configuration</link> section of the &os;
 	    Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="running-X-securelevels">
 	  <para>I <emphasis>tried</emphasis> to run X, but I get a
 	    <errorname>No devices detected.</errorname> error when I
 	    type <command>startx</command>.  What do I do now?</para>
 	</question>
 
 	<answer>
 	  <para>The system is probably running at a raised
 	    <literal>securelevel</literal>.  It is not possible to
 	    start X at a raised <literal>securelevel</literal> because
 	    X requires write access to &man.io.4;.  For more
 	    information, see at the &man.init.8; manual page.</para>
 
 	  <para>There are two solutions to the problem: set the
 	    <literal>securelevel</literal> back down to zero or run
 	    &man.xdm.1; (or an alternative display manager) at boot
 	    time before the <literal>securelevel</literal> is
 	    raised.</para>
 
 	  <para>See <xref linkend="xdm-boot"/> for more information
 	    about running &man.xdm.1; at boot time.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="x-and-moused">
 	  <para>Why does my mouse not work with X?</para>
 	</question>
 
 	<answer>
 	  <para>When using &man.vt.4;, the default console
 	    driver, &os; can be configured to support a mouse pointer
 	    on each virtual screen.  To avoid conflicting with X,
 	    &man.vt.4; supports a virtual device called
 	    <filename>/dev/sysmouse</filename>.  All mouse events
 	    received from the real mouse device are written to the
 	    &man.sysmouse.4; device via &man.moused.8;.  To use the
 	    mouse on one or more virtual consoles,
 	    <emphasis>and</emphasis> use X, see <xref
 	      linkend="moused" remap="another section"/> and set up
 	    &man.moused.8;.</para>
 
 	  <para>Then edit <filename>/etc/X11/xorg.conf</filename> and
 	    make sure the following lines exist:</para>
 
 	  <programlisting>Section "InputDevice"
    Option          "Protocol" "SysMouse"
    Option          "Device" "/dev/sysmouse"
 .....</programlisting>
 
 	  <para>Starting with &xorg; version 7.4, the
 	    <literal>InputDevice</literal> sections in
 	    <filename>xorg.conf</filename> are ignored in favor of
 	    autodetected devices.  To restore the old behavior, add
 	    the following line to the <literal>ServerLayout</literal>
 	    or <literal>ServerFlags</literal> section:</para>
 
 	  <programlisting>Option "AutoAddDevices" "false"</programlisting>
 
 	  <para>Some people prefer to use
 	    <filename>/dev/mouse</filename> under X.  To make this
 	    work, <filename>/dev/mouse</filename> should be linked
 	    to <filename>/dev/sysmouse</filename> (see
 	    &man.sysmouse.4;) by adding the following line to
 	    <filename>/etc/devfs.conf</filename> (see
 	    &man.devfs.conf.5;):</para>
 
 	  <programlisting>link    sysmouse    mouse</programlisting>
 
 	  <para>This link can be created by restarting &man.devfs.5;
 	    with the following command (as <systemitem
 	      class="username">root</systemitem>):</para>
 
 	  <screen>&prompt.root; <userinput>service devfs restart</userinput></screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="x-and-wheel">
 	  <para>My mouse has a fancy wheel.  Can I use it in X?</para>
 	</question>
 
 	<answer>
 	  <para>Yes, if X is configured for a 5 button mouse.  To
 	    do this, add the lines <literal>Buttons 5</literal>
 	    and <literal>ZAxisMapping 4 5</literal> to the
 	    <quote>InputDevice</quote> section of
 	    <filename>/etc/X11/xorg.conf</filename>, as seen in this
 	    example:</para>
 
 	  <programlisting>Section "InputDevice"
    Identifier      "Mouse1"
    Driver          "mouse"
    Option          "Protocol" "auto"
    Option          "Device" "/dev/sysmouse"
    Option          "Buttons" "5"
    Option          "ZAxisMapping" "4 5"
 EndSection</programlisting>
 
 	    <para>The mouse can be enabled in
 	      <application>Emacs</application> by adding these
 	      lines to <filename>~/.emacs</filename>:</para>
 
 	    <programlisting>;; wheel mouse
 (global-set-key [mouse-4] 'scroll-down)
 (global-set-key [mouse-5] 'scroll-up)</programlisting>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="x-and-synaptic">
 	  <para>My laptop has a Synaptics touchpad.  Can I use it in
 	    X?</para>
 	</question>
 
 	<answer>
 	  <para>Yes, after configuring a few things to make
 	    it work.</para>
 
 	  <para>In order to use the Xorg synaptics driver,
 	    first remove <literal>moused_enable</literal> from
 	    <filename>rc.conf</filename>.</para>
 
 	  <para>To enable synaptics, add the following line to
 	    <filename>/boot/loader.conf</filename>:</para>
 
 	  <programlisting>hw.psm.synaptics_support="1"</programlisting>
 
 	  <para>Add the following to
 	    <filename>/etc/X11/xorg.conf</filename>:</para>
 
 	  <programlisting>Section "InputDevice"
 Identifier  "Touchpad0"
 Driver      "synaptics"
 Option      "Protocol" "psm"
 Option      "Device" "/dev/psm0"
 EndSection</programlisting>
 
 	  <para>And be sure to add the following into the
 	    <quote>ServerLayout</quote> section:</para>
 
 	  <programlisting>InputDevice    "Touchpad0" "SendCoreEvents"</programlisting>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="no-remote-x11">
 	  <para>How do I use remote X displays?</para>
 	</question>
 
 	<answer>
 	  <para>For security reasons, the default setting is to not
 	    allow a machine to remotely open a window.</para>
 
 	  <para>To enable this feature, start
 	    <application>X</application> with the optional
 	    <option>-listen_tcp</option> argument:</para>
 
 	  <screen>&prompt.user; <userinput>startx -listen_tcp</userinput></screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="virtual-console">
 	  <para>What is a virtual console and how do I make
 	    more?</para>
 	</question>
 
 	<answer>
 	  <para>Virtual consoles provide
 	    several simultaneous sessions on the same machine without
 	    doing anything complicated like setting up a network or
 	    running X.</para>
 
 	  <para>When the system starts, it will display a login prompt
 	    on the monitor after displaying all the boot messages.
 	    Type in your login name and password to
 	    start working on the first virtual
 	    console.</para>
 
 	  <para>To start another
 	    session, perhaps to look at documentation for a program
 	    or to read mail while waiting for an
 	    FTP transfer to finish,
 	    hold down <keycap>Alt</keycap> and press
 	    <keycap>F2</keycap>.  This will display the login prompt
 	    for the second virtual
 	      console.  To go back to the
 	    original session, press <keycombo
 	      action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.</para>
 
 	  <para>The default &os; installation has eight virtual
 	    consoles enabled.  <keycombo
 	      action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>,
 	    <keycombo
 	      action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>,
 	    <keycombo
 	      action="simul"><keycap>Alt</keycap><keycap>F3</keycap></keycombo>,
 	    and so on will switch between these virtual
 	    consoles.</para>
 
 	  <para>To enable more of virtual consoles, edit
 	    <filename>/etc/ttys</filename> (see &man.ttys.5;) and add
 	    entries for <filename>ttyv8</filename> to
 	    <filename>ttyvc</filename>, after the comment on
 	    <quote>Virtual terminals</quote>:</para>
 
 	  <programlisting># Edit the existing entry for ttyv8 in /etc/ttys and change
 # "off" to "on".
 ttyv8   "/usr/libexec/getty Pc"         xterm  on secure
 ttyv9   "/usr/libexec/getty Pc"         xterm  on secure
 ttyva   "/usr/libexec/getty Pc"         xterm  on secure
 ttyvb   "/usr/libexec/getty Pc"         xterm  on secure</programlisting>
 
 	  <para>The more virtual
 	    terminals, the more resources that are used.  This can be
 	    problematic on systems with 8&nbsp;MB RAM or less.
 	    Consider changing <literal>secure</literal> to
 	    <literal>insecure</literal>.</para>
 
 	  <important>
 	    <para>In order to run an X server, at least one virtual
 	      terminal must be left to <literal>off</literal> for it
 	      to use.  This means that only eleven of the Alt-function
 	      keys can be used as virtual consoles so that one is left
 	      for the X server.</para>
 	  </important>
 
 	  <para>For example, to run X and eleven virtual consoles, the
 	    setting for virtual terminal 12 should be:</para>
 
 	  <programlisting>ttyvb   "/usr/libexec/getty Pc"         xterm  off secure</programlisting>
 
 	  <para>The easiest way to activate the
 	    virtual consoles is to reboot.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="vty-from-x">
 	  <para>How do I access the virtual consoles from X?</para>
 	</question>
 
 	<answer>
 	  <para>Use <keycombo
 	      action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo>
 	    to switch back to a virtual console.  Press <keycombo
 	      action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo>
 	    to return to the first virtual console.</para>
 
 	  <para>Once at a text console, use
 	    <keycombo
 	      action="simul"><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo>
 	    to move between them.</para>
 
 	  <para>To return to the X session, switch to the
 	    virtual console running X.  If X was started from the
 	    command line using <command>startx</command>,
 	    the X session will attach to the next unused virtual
 	    console, not the text console from which it was invoked.
 	    For eight active virtual terminals, X will
 	    run on the ninth, so use <keycombo
 	      action="simul"><keycap>Alt</keycap><keycap>F9</keycap></keycombo>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="xdm-boot">
 	  <para>How do I start <application>XDM</application> on
 	    boot?</para>
 	</question>
 
 	<answer>
 	  <para>There are two schools of thought on how to start
 	    &man.xdm.1;.  One school starts <command>xdm</command>
 	    from <filename>/etc/ttys</filename> (see &man.ttys.5;)
 	    using the supplied example, while the other runs
 	    <command>xdm</command> from
 	    <filename>rc.local</filename> (see &man.rc.8;) or from an
 	    <filename>X</filename> script in
 	    <filename>/usr/local/etc/rc.d</filename>.  Both are
 	    equally valid, and one may work in situations where the
 	    other does not.  In both cases the result is the same: X
 	    will pop up a graphical login prompt.</para>
 
 	  <para>The &man.ttys.5; method has the advantage of
 	    documenting which vty X will start on and passing the
 	    responsibility of restarting the X server on logout to
 	    &man.init.8;.  The &man.rc.8; method makes it easy to
 	    <command>kill</command> <command>xdm</command> if there is
 	    a problem starting the X server.</para>
 
 	  <para>If loaded from &man.rc.8;, <command>xdm</command>
 	    should be started without any arguments.
 	    <command>xdm</command> must start
 	    <emphasis>after</emphasis> &man.getty.8; runs, or else
 	    <command>getty</command> and <command>xdm</command> will
 	    conflict, locking out the console.  The best way around
 	    this is to have the script sleep 10 seconds or so then
 	    launch <command>xdm</command>.</para>
 
 	  <para>When starting <command>xdm</command> from
 	    <filename>/etc/ttys</filename>, there still is a chance of
 	    conflict between <command>xdm</command> and &man.getty.8;.
 	    One way to avoid this is to add the <literal>vt</literal>
 	    number in
 	    <filename>/usr/local/lib/X11/xdm/Xservers</filename>:</para>
 
 	  <programlisting>:0 local /usr/local/bin/X vt4</programlisting>
 
 	  <para>The above example will direct the X server to run in
 	    <filename>/dev/ttyv3</filename>.  Note the number is
 	    offset by one.  The X server counts the vty from one,
 	    whereas the &os; kernel numbers the vty from zero.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="xconsole-failure">
 	  <para>Why do I get <errorname>Couldn't open
 	      console</errorname> when I run
 	    <command>xconsole</command>?</para>
 	</question>
 
 	<answer>
 	  <para>When <application>X</application> is started with
 	    <command>startx</command>, the permissions on
 	    <filename>/dev/console</filename> will
 	    <emphasis>not</emphasis> get changed, resulting in things
 	    like <command>xterm -C</command> and
 	    <command>xconsole</command> not working.</para>
 
 	  <para>This is because of the way console permissions are set
 	    by default.  On a multi-user system, one does not
 	    necessarily want just any user to be able to write on the
 	    system console.  For users who are logging directly onto a
 	    machine with a VTY, the &man.fbtab.5; file exists to solve
 	    such problems.</para>
 
 	  <para>In a nutshell, make sure an uncommented line of the
 	    form is in <filename>/etc/fbtab</filename> (see
 	    &man.fbtab.5;):</para>
 
 	  <programlisting>/dev/ttyv0 0600 /dev/console</programlisting>
 
 	  <para>It will ensure that whomever logs in on
 	    <filename>/dev/ttyv0</filename> will own the
 	    console.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ps2-x">
 	  <para>Why does my PS/2 mouse misbehave under X?</para>
 	</question>
 
 	<answer>
 	  <para>The mouse and the mouse driver may have become out of
 	    synchronization.  In rare cases, the driver may also
 	    erroneously report synchronization errors:</para>
 
 	  <programlisting>psmintr: out of sync (xxxx != yyyy)</programlisting>
 
 	  <para>If this happens, disable the synchronization check
 	    code by setting the driver flags for the PS/2 mouse driver
 	    to <literal>0x100</literal>.  This can be easiest achieved
 	    by adding <literal>hint.psm.0.flags="0x100"</literal> to
 	    <filename>/boot/loader.conf</filename> and
 	    rebooting.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="mouse-button-reverse">
 	  <para>How do I reverse the mouse buttons?</para>
 	</question>
 
 	<answer>
 	  <para>Type
 	    <command>xmodmap -e "pointer = 3 2 1"</command>.  Add this
 	    command to <filename>~/.xinitrc</filename> or
 	    <filename>~/.xsession</filename> to make it happen
 	    automatically.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="install-splash">
 	  <para>How do I install a splash screen and where do I find
 	    them?</para>
 	</question>
 
 	<answer>
 	  <para>The detailed answer for this question can be found in
 	    the <link
 	      xlink:href="&url.books.handbook;/boot-splash.html">Boot
 	    Time Splash Screens</link> section of the &os;
 	    Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="windows-keys">
 	  <para>Can I use the <keycap>Windows</keycap> keys on my
 	    keyboard in X?</para>
 	</question>
 
 	<answer>
 	  <para>Yes.  Use &man.xmodmap.1; to
 	    define which functions the keys should perform.</para>
 
 	  <para>Assuming all Windows keyboards are
 	    standard, the keycodes for these three keys are the
 	    following:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para><keycode>115</keycode> &mdash;
 		<keycap>Windows</keycap> key, between the left-hand
 		<keycap>Ctrl</keycap> and <keycap>Alt</keycap>
 		keys</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><keycode>116</keycode> &mdash;
 		<keycap>Windows</keycap> key, to the right of
 		<keycap>AltGr</keycap></para>
 	    </listitem>
 
 	    <listitem>
 	      <para><keycode>117</keycode> &mdash;
 		<keycap>Menu</keycap>, to the left of the right-hand
 		<keycap>Ctrl</keycap></para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>To have the left <keycap>Windows</keycap> key print a
 	    comma, try this.</para>
 
 	  <screen>&prompt.root; <userinput>xmodmap -e "keycode 115 = comma"</userinput></screen>
 
 	  <para>To have the <keycap>Windows</keycap> key-mappings
 	    enabled automatically every time X is started, either put
 	    the <command>xmodmap</command> commands in
 	    <filename>~/.xinitrc</filename> or, preferably, create
 	    a <filename>~/.xmodmaprc</filename> and include the
 	    <command>xmodmap</command> options, one per line, then add
 	    the following line to
 	    <filename>~/.xinitrc</filename>:</para>
 
 	  <programlisting>xmodmap $HOME/.xmodmaprc</programlisting>
 
 	  <para>For example, to map the 3 keys to be
 	    <keycap>F13</keycap>, <keycap>F14</keycap>, and
 	    <keycap>F15</keycap>, respectively.  This would make it
 	    easy to map them to useful functions within applications
 	    or the window manager.</para>
 
 	  <para>To do this, put the following in
 	    <filename>~/.xmodmaprc</filename>.</para>
 
 	  <programlisting>keycode 115 = F13
 keycode 116 = F14
 keycode 117 = F15</programlisting>
 
 	  <para>For the <package>x11-wm/fvwm2</package> desktop
 	    manager, one could map the keys so that
 	    <keycap>F13</keycap> iconifies or de-iconifies the
 	    window the cursor is in, <keycap>F14</keycap> brings the
 	    window the cursor is in to the front or, if it is already
 	    at the front, pushes it to the back, and
 	    <keycap>F15</keycap> pops up the main Workplace
 	    menu even if the cursor is not on the
 	    desktop, which is useful when no part of
 	    the desktop is visible.</para>
 
 	  <para>The following entries in
 	    <filename>~/.fvwmrc</filename> implement the
 	    aforementioned setup:</para>
 
 	  <programlisting>Key F13        FTIWS    A        Iconify
 Key F14        FTIWS    A        RaiseLower
 Key F15        A        A        Menu Workplace Nop</programlisting>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="x-3d-acceleration">
 	  <para>How can I get 3D hardware acceleration for
 	    &opengl;?</para>
 	</question>
 
 	<answer>
 	  <para>The availability of 3D acceleration depends on the
 	    version of &xorg; and the type of video
 	    chip.  For an nVidia chip, use
 	    the binary drivers provided for &os; by installing one of
 	    the following ports:</para>
 
 	  <para>The latest versions of nVidia cards are supported
 	    by the <package>x11/nvidia-driver</package>
 	    port.</para>
 
 	  <para>Older drivers are available as
 	    <package>x11/nvidia-driver-<replaceable>###</replaceable></package></para>
 
 	  <para>nVidia provides detailed information on which
 	    card is supported by which driver on their web site: <uri
 	      xlink:href="http://www.nvidia.com/object/IO_32667.html">http://www.nvidia.com/object/IO_32667.html</uri>.</para>
 
 	  <para>For Matrox&nbsp;G200/G400, check the
 	    <package>x11-drivers/xf86-video-mga</package>
 	    port.</para>
 
 	  <para>For ATI&nbsp;Rage&nbsp;128 and Radeon see
 	    &man.ati.4x;, &man.r128.4x; and &man.radeon.4x;.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="networking">
     <title>Networking</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="diskless-booting">
 	  <para>Where can I get information on <quote>diskless
 	      booting</quote>?</para>
 	</question>
 
 	<answer>
 	  <para><quote>Diskless booting</quote> means that the &os;
 	    box is booted over a network, and reads the necessary
 	    files from a server instead of its hard disk.  For full
 	    details, see <link
 	      xlink:href="&url.books.handbook;/network-diskless.html">the
 	      Handbook entry on diskless booting</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="router">
 	  <para>Can a &os; box be used as a dedicated network
 	    router?</para>
 	</question>
 
 	<answer>
 	  <para>Yes.  Refer to the Handbook entry on <link
 	      xlink:href="&url.books.handbook;/advanced-networking.html">advanced
 	      networking</link>, specifically the section on <link
 	      xlink:href="&url.books.handbook;/network-routing.html">routing
 	      and gateways</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="natd">
 	  <para>Does &os; support NAT or Masquerading?</para>
 	</question>
 
 	<answer>
 	  <para>Yes.  For instructions on how to use NAT over a PPP
 	    connection, see the <link
 	      xlink:href="&url.books.handbook;/userppp.html">Handbook
 	      entry on PPP</link>.  To use NAT over
 	    some other sort of network connection, look at the
 	    <link
 	      xlink:href="&url.books.handbook;/firewalls-ipfw.html#network-natd">natd</link>
 	    section of the Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ethernet-aliases">
 	  <para>How can I set up Ethernet aliases?</para>
 	</question>
 
 	<answer>
 	  <para>If the alias is on the same subnet as an address
 	    already configured on the interface, add
 	    <literal>netmask 0xffffffff</literal> to this
 	    command:</para>
 
 	  <screen>&prompt.root; <userinput>ifconfig <replaceable>ed0</replaceable> alias <replaceable>192.0.2.2 </replaceable>netmask 0xffffffff</userinput></screen>
 
 	  <para>Otherwise, specify the network address and
 	    netmask as usual:</para>
 
 	  <screen>&prompt.root; <userinput>ifconfig <replaceable>ed0</replaceable> alias <replaceable>172.16.141.5</replaceable> netmask 0xffffff00</userinput></screen>
 
 	  <para>More information can be found in the &os; <link
 	      xlink:href="&url.books.handbook;/configtuning-virtual-hosts.html">Handbook</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="nfs-linux">
 	  <para>Why can I not NFS-mount from a &linux; box?</para>
 	</question>
 
 	<answer>
 	  <para>Some versions of the &linux; NFS code only accept
 	    mount requests from a privileged port; try to issue the
 	    following command:</para>
 
 	  <screen>&prompt.root; <userinput>mount -o -P linuxbox:/blah /mnt</userinput></screen>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="exports-errors">
 	  <para>Why does <command>mountd</command> keep telling me it
 	    <errorname>can't change attributes</errorname> and that I
 	    have a <errorname>bad exports list</errorname> on my &os;
 	    NFS server?</para>
 	</question>
 
 	<answer>
 	  <para>The most frequent problem is not understanding the
 	    correct format of <filename>/etc/exports</filename>.
 	    Review &man.exports.5; and the <link
 	      xlink:href="&url.books.handbook;/network-nfs.html">NFS</link>
 	    entry in the Handbook, especially the section on <link
 	      xlink:href="&url.books.handbook;/network-nfs.html#configuring-nfs">configuring
 	      NFS</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ip-multicast">
 	  <para>How do I enable IP multicast support?</para>
 	</question>
 
 	<answer>
 	  <para>Install the <package>net/mrouted</package> package
 	    or port and add
 	    <literal>mrouted_enable="YES"</literal> to
 	    <filename>/etc/rc.conf</filename> start this service at
 	    boot time.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="fqdn-hosts">
 	  <para>Why do I have to use the FQDN for hosts on my
 	    site?</para>
 	</question>
 
 	<answer>
 	  <para>See the answer in the &os; <link
 	      xlink:href="&url.books.handbook;/mail-trouble.html">Handbook</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="network-permission-denied">
 	  <para>Why do I get an error, <errorname>Permission
 	      denied</errorname>, for all networking
 	    operations?</para>
 	</question>
 
 	<answer>
 	  <para>If the kernel is compiled with the
 	    <literal>IPFIREWALL</literal> option, be aware
 	    that the default policy is to deny all packets that are
 	    not explicitly allowed.</para>
 
 	  <para>If the firewall is unintentionally misconfigured,
 	    restore network operability by
 	    typing the following as <systemitem
 	      class="username">root</systemitem>:</para>
 
 	  <screen>&prompt.root; <userinput>ipfw add 65534 allow all from any to any</userinput></screen>
 
 	  <para>Consider setting
 	    <literal>firewall_type="open"</literal> in
 	    <filename>/etc/rc.conf</filename>.</para>
 
 	  <para>For further information on configuring this
 	    firewall, see the <link
 	      xlink:href="&url.books.handbook;/firewalls-ipfw.html">Handbook
 	      chapter</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ipfw-fwd">
 	  <para>Why is my <command>ipfw</command> <quote>fwd</quote>
 	    rule to redirect a service to another machine not
 	    working?</para>
 	</question>
 
 	<answer>
 	  <para>Possibly because network address translation (NAT) is
 	    needed instead of just forwarding packets.  A
 	    <quote>fwd</quote> rule only forwards packets, it does not
 	    actually change the data inside the packet.  Consider this
 	    rule:</para>
 
 	  <screen>01000 fwd <replaceable>10.0.0.1</replaceable> from any to <replaceable>foo 21</replaceable></screen>
 
 	  <para>When a packet with a destination address of
 	    <replaceable>foo</replaceable> arrives at the machine with
 	    this rule, the packet is forwarded to
 	    <replaceable>10.0.0.1</replaceable>, but it still has the
 	    destination address of <replaceable>foo</replaceable>.
 	    The destination address of the packet is
 	    not changed to
 	    <replaceable>10.0.0.1</replaceable>.  Most machines would
 	    probably drop a packet that they receive with a
 	    destination address that is not their own.  Therefore,
 	    using a <quote>fwd</quote> rule does not often work the
 	    way the user expects.  This behavior is a feature and not
 	    a bug.</para>
 
 	  <para>See the <link
 	      linkend="service-redirect"><acronym>FAQ</acronym> about
 	      redirecting services</link>, the &man.natd.8; manual, or
 	    one of the several port redirecting utilities in the <link
 	      xlink:href="&url.base;/ports/index.html">Ports
 	      Collection</link> for a correct way to do this.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="service-redirect">
 	  <para>How can I redirect service requests from one machine
 	    to another?</para>
 	</question>
 
 	<answer>
 	  <para>FTP and other service requests can be redirected with
 	    the <package>sysutils/socket</package> package or port.
 	    Replace the entry for the service in
 	    <filename>/etc/inetd.conf</filename> to call
 	    <command>socket</command>, as seen in this example for
 	    <application>ftpd</application>:</para>
 
 	  <programlisting>ftp stream tcp nowait nobody /usr/local/bin/socket socket <replaceable>ftp.example.com</replaceable> <replaceable>ftp</replaceable></programlisting>
 
 	  <para>where <replaceable>ftp.example.com</replaceable> and
 	    <replaceable>ftp</replaceable> are the host and port to
 	    redirect to, respectively.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="bandwidth-mgr-tool">
 	  <para>Where can I get a bandwidth management tool?</para>
 	</question>
 
 	<answer>
 	  <para>There are three bandwidth management tools available
 	    for &os;.  &man.dummynet.4; is integrated into &os; as
 	    part of &man.ipfw.4;.  <link
 	      xlink:href="http://www.sonycsl.co.jp/person/kjc/programs.html">ALTQ</link>
 	    has been integrated into &os; as part of &man.pf.4;.
 	    Bandwidth Manager from <link
 	      xlink:href="http://www.etinc.com/">Emerging
 	      Technologies</link> is a commercial product.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="bpf-not-configured">
 	  <para>Why do I get <errorname>/dev/bpf0: device not
 	      configured</errorname>?</para>
 	</question>
 
 	<answer>
 	  <para>The running application requires the Berkeley
 	    Packet Filter (&man.bpf.4;), but it was removed from a
 	    custom kernel.  Add this to the kernel config file and
 	    build a new kernel:</para>
 
 	  <programlisting>device bpf        # Berkeley Packet Filter</programlisting>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="mount-smb-share">
 	  <para>How do I mount a disk from a &windows; machine that is
 	    on my network, like smbmount in &linux;?</para>
 	</question>
 
 	<answer>
 	  <para>Use the <application>SMBFS</application> toolset.  It
 	    includes a set of kernel modifications and a set of
 	    userland programs.  The programs and information are
 	    available as &man.mount.smbfs.8; in the base
 	    system.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="icmp-response-bw-limit">
 	  <para>What are these messages about: <errorname>Limiting
 	      icmp/open port/closed port response</errorname> in my
 	    log files?</para>
 	</question>
 
 	<answer>
 	  <para>This kernel message indicates that some activity is
 	    provoking it to send a large amount of ICMP or TCP reset
 	    (RST) responses.  ICMP responses are
 	    often generated as a result of attempted connections to
 	    unused UDP ports.  TCP resets are generated as a result of
 	    attempted connections to unopened TCP ports.  Among
 	    others, these are the kinds of activities which may cause
 	    these messages:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Brute-force denial of service (DoS) attacks (as
 		opposed to single-packet attacks which exploit a
 		specific vulnerability).</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Port scans which attempt to connect to a large
 		number of ports (as opposed to only trying a few
 		well-known ports).</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>The first number in the message indicates how many
 	    packets the kernel would have sent if the limit was not in
 	    place, and the second indicates the limit.  This limit
 	    is controlled using
 	    <varname>net.inet.icmp.icmplim</varname>.  This example
 	    sets the limit to <literal>300</literal>
 	    packets per second:</para>
 
 	  <screen>&prompt.root; <userinput>sysctl net.inet.icmp.icmplim=300</userinput></screen>
 
 	  <para>To disable these messages
 	    without disabling response
 	    limiting, use
 	    <varname>net.inet.icmp.icmplim_output</varname>
 	    to disable the output:</para>
 
 	  <screen>&prompt.root; <userinput>sysctl net.inet.icmp.icmplim_output=0</userinput></screen>
 
 	  <para>Finally, to disable response limiting completely,
 	    set <varname>net.inet.icmp.icmplim</varname> to
 	    <literal>0</literal>.  Disabling response limiting is
 	    discouraged for the reasons listed above.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="unknown-hw-addr-format">
 	  <para>What are these <errorname>arp: unknown hardware
 	      address format</errorname> error messages?</para>
 	</question>
 
 	<answer>
 	  <para>This means that some device on the local Ethernet is
 	    using a MAC address in a format that &os; does not
 	    recognize.  This is probably caused by someone
 	    experimenting with an Ethernet card somewhere else on the
 	    network.  This is most commonly seen on cable modem
 	    networks.  It is harmless, and should not affect the
 	    performance of the &os; system.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="arp-wrong-iface">
 	  <para>Why do I keep seeing messages like:
 	    <errorname>192.168.0.10 is on
 	      fxp1 but got reply from 00:15:17:67:cf:82 on
 	      rl0</errorname>, and how do I disable it?</para>
 	</question>
 
 	<answer>
 	  <para>Because a packet is coming from outside the network
 	    unexpectedly.  To disable them, set
 	    <varname>net.link.ether.inet.log_arp_wrong_iface</varname>
 	    to <literal>0</literal>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="ipv6-only">
 	  <para>How do I compile an IPv6 only kernel?</para>
 	</question>
 
 	<answer>
 	  <para>Configure your kernel with these settings:
 
 	    <screen>include GENERIC
 ident GENERIC-IPV6ONLY
 makeoptions MKMODULESENV+="WITHOUT_INET_SUPPORT="
 nooptions INET
 nodevice gre</screen></para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="security">
     <title>Security</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="sandbox">
 	  <para>What is a sandbox?</para>
 	</question>
 	<answer>
 	  <para><quote>Sandbox</quote> is a security term.  It can
 	    mean two things:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>A process which is placed inside a set of virtual
 		walls that are designed to prevent someone who breaks
 		into the process from being able to break into the
 		wider system.</para>
 
 	      <para>The process is only able to run inside the walls.
 		Since nothing the process does in regards to executing
 		code is supposed to be able to breach the walls, a
 		detailed audit of its code is not needed in order to
 		be able to say certain things about its
 		security.</para>
 
 	      <para>The walls might be a user ID, for example.
 		This is the definition used in the &man.security.7;
 		and &man.named.8; man pages.</para>
 
 	      <para>Take the <literal>ntalk</literal> service, for
 		example (see &man.inetd.8;).  This service used to run
 		as user&nbsp;ID <systemitem
 		  class="username">root</systemitem>.  Now it runs as
 		user&nbsp;ID <systemitem
 		  class="username">tty</systemitem>.  The <systemitem
 		  class="username">tty</systemitem> user is a sandbox
 		designed to make it more difficult for someone who has
 		successfully hacked into the system via
 		<literal>ntalk</literal> from being able to hack
 		beyond that user&nbsp;ID.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>A process which is placed inside a simulation of
 		the machine.  It means that someone who is able to
 		break into the process may believe that he can break
 		into the wider machine but is, in fact, only breaking
 		into a simulation of that machine and not modifying
 		any real data.</para>
 
 	      <para>The most common way to accomplish this is to build
 		a simulated environment in a subdirectory and then run
 		the processes in that directory chrooted so that
 		<filename>/</filename> for that process is this
 		directory, not the real <filename>/</filename> of the
 		system).</para>
 
 	      <para>Another common use is to mount an underlying file
 		system read-only and then create a file system layer
 		on top of it that gives a process a seemingly
 		writeable view into that file system.  The process may
 		believe it is able to write to those files, but only
 		the process sees the effects &mdash; other processes
 		in the system do not, necessarily.</para>
 
 	      <para>An attempt is made to make this sort of sandbox so
 		transparent that the user (or hacker) does not realize
 		that he is sitting in it.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>&unix; implements two core sandboxes.  One is at the
 	    process level, and one is at the userid level.</para>
 
 	  <para>Every &unix; process is completely firewalled off from
 	    every other &unix; process.  One process cannot modify the
 	    address space of another.</para>
 
 	  <para>A &unix; process is owned by a particular userid.  If
 	    the user&nbsp;ID is not the <systemitem
 	      class="username">root</systemitem> user, it serves to
 	    firewall the process off from processes owned by other
 	    users.  The user&nbsp;ID is also used to firewall off
 	    on-disk data.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="securelevel">
 	  <para>What is securelevel?</para>
 	</question>
 
 	<answer>
 	  <para><literal>securelevel</literal> is a security
 	    mechanism implemented in the kernel.  When the securelevel
 	    is positive, the kernel restricts certain tasks; not even
 	    the superuser (<systemitem
 	      class="username">root</systemitem>) is allowed to do
 	    them.  The securelevel mechanism limits the ability
 	    to:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Unset certain file flags, such as
 		<literal>schg</literal> (the system immutable
 		flag).</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Write to kernel memory via
 		<filename>/dev/mem</filename> and
 		<filename>/dev/kmem</filename>.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Load kernel modules.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Alter firewall rules.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>To check the status of the securelevel on a running
 	    system:</para>
 
 	  <screen>&prompt.root; <userinput>sysctl -n kern.securelevel</userinput></screen>
 
 	  <para>The output contains the current value of the
 	    securelevel.  If it is greater than 0, at
 	    least some of the securelevel's protections are
 	    enabled.</para>
 
 	  <para>The securelevel of a running system cannot be lowered
 	    as this would defeat its purpose.  If a task requires that
 	    the securelevel be non-positive, change the
 	    <varname>kern_securelevel</varname> and
 	    <varname>kern_securelevel_enable</varname> variables in
 	    <filename>/etc/rc.conf</filename> and reboot.</para>
 
 	  <para>For more information on securelevel and the specific
 	    things all the levels do, consult &man.init.8;.</para>
 
 	  <warning>
 	    <para>Securelevel is not a silver bullet; it has many
 	      known deficiencies.  More often than not, it provides a
 	      false sense of security.</para>
 
 	    <para>One of its biggest problems is that in order for it
 	      to be at all effective, all files used in the boot
 	      process up until the securelevel is set must be
 	      protected.  If an attacker can get the system to execute
 	      their code prior to the securelevel being set (which
 	      happens quite late in the boot process since some things
 	      the system must do at start-up cannot be done at an
 	      elevated securelevel), its protections are invalidated.
 	      While this task of protecting all files used in the boot
 	      process is not technically impossible, if it is
 	      achieved, system maintenance will become a nightmare
 	      since one would have to take the system down, at least
 	      to single-user mode, to modify a configuration
 	      file.</para>
 
 	    <para>This point and others are often discussed on the
 	      mailing lists, particularly the &a.security;.
 	      Search the archives <link
 		xlink:href="&url.base;/search/index.html">here</link>
 	      for an extensive discussion.  A more fine-grained
 	      mechanism is preferred.</para>
 	  </warning>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="toor-account">
 	  <para>What is this UID 0 <systemitem
 	      class="username">toor</systemitem> account?  Have I been
 	    compromised?</para>
 	</question>
 
 	<answer>
 	  <para>Do not worry.  <systemitem
 	      class="username">toor</systemitem> is an
 	    <quote>alternative</quote> superuser account, where toor
 	    is root spelled backwards.  It is intended to be used with
 	    a non-standard shell so the default shell for <systemitem
 	      class="username">root</systemitem> does not need to
 	    change.  This is important as shells which are not part of
 	    the base distribution, but are instead installed from
 	    ports or packages, are installed in
 	    <filename>/usr/local/bin</filename> which, by default,
 	    resides on a different file system.  If <systemitem
 	      class="username">root</systemitem>'s shell is located in
 	    <filename>/usr/local/bin</filename> and the
 	    file system
 	    containing <filename>/usr/local/bin</filename>) is not
 	    mounted, <systemitem
 	      class="username">root</systemitem> will not be able to
 	    log in to fix a problem and will have to reboot into
 	    single-user mode in order to enter the path to a
 	    shell.</para>
 
 	  <para>Some people use <systemitem
 	      class="username">toor</systemitem> for day-to-day
 	    <systemitem class="username">root</systemitem> tasks with
 	    a non-standard shell, leaving <systemitem
 	      class="username">root</systemitem>, with a standard
 	    shell, for single-user mode or emergencies.  By default, a
 	    user cannot log in using <systemitem
 	      class="username">toor</systemitem> as it does not have a
 	    password, so log in as <systemitem
 	      class="username">root</systemitem> and set a password
 	    for <systemitem class="username">toor</systemitem> before
 	    using it to login.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="serial">
     <title>Serial Communications</title>
 
     <para>This section answers common questions about serial
       communications with &os;.</para>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="serial-console-prompt">
 	  <para>How do I get the boot: prompt to show on the serial
 	    console?</para>
 	</question>
 
 	<answer>
 	  <para>See <link
 	      xlink:href="&url.books.handbook;/serialconsole-setup.html">this
 	      section of the Handbook</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="found-serial">
 	  <para>How do I tell if &os; found my serial ports or modem
 	    cards?</para>
 	</question>
 
 	<answer>
 	  <para>As the &os; kernel boots, it will probe for the serial
 	    ports for which the kernel is configured.
 	    Either watch the boot messages closely
 	    or run this command after the system is up and
 	    running:</para>
 
 	  <screen>&prompt.user; <userinput>grep -E '^(sio|uart)[0-9]' &lt; /var/run/dmesg.boot</userinput>
 sio0: &lt;16550A-compatible COM port&gt; port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
 sio0: type 16550A
 sio1: &lt;16550A-compatible COM port&gt; port 0x2f8-0x2ff irq 3 on acpi0
 sio1: type 16550A</screen>
 
 	  <para>This example shows two serial ports.  The first is on
 	    IRQ4, port address
 	    <literal>0x3f8</literal>, and has a 16550A-type UART chip.
 	    The second uses the same kind of chip but is on
 	    IRQ3 and is at port address
 	    <literal>0x2f8</literal>.  Internal modem cards are
 	    treated just like serial ports, except that they
 	    always have a modem attached to the
 	    port.</para>
 
 	  <para>The <filename>GENERIC</filename> kernel includes
 	    support for two serial ports using the same IRQ and port
 	    address settings in the above example.  If these settings
 	    are not right for the system, or if there are more modem
 	    cards or serial ports than the kernel is
 	    configured for, reconfigure using the instructions in
 	    <link linkend="make-kernel">building a kernel</link>
 	    for more details.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="access-serial-ports">
 	  <para>How do I access the serial ports on &os;? (x86-specific)</para>
 	</question>
 
 	<answer>
 	  <para>The third serial port, <filename>sio2</filename>,
 	    or <filename>COM3</filename>,
 	    is on <filename>/dev/cuad2</filename> for dial-out
 	    devices, and on <filename>/dev/ttyd2</filename> for
 	    dial-in devices.  What is the difference between these two
 	    classes of devices?</para>
 
 	  <para>When
 	    opening <filename>/dev/ttydX</filename> in blocking mode,
 	    a process will wait for the corresponding
 	    <filename>cuadX</filename> device to become inactive, and
 	    then wait for the carrier detect line to go active.  When
 	    the <filename>cuadX</filename> device is opened, it makes
 	    sure the serial port is not already in use by the
 	    <filename>ttydX</filename> device.  If the port is
 	    available, it steals it from the
 	    <filename>ttydX</filename> device.  Also, the
 	    <filename>cuadX</filename> device does not care about
 	    carrier detect.  With this scheme and an auto-answer
 	    modem, remote users can log in and local users can still
 	    dial out with the same modem and the system will take care
 	    of all the conflicts.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="enable-multiport-serial">
 	  <para>How do I enable support for a multi-port serial
 	    card?</para>
 	</question>
 
 	<answer>
 	  <para>The section on kernel configuration provides
 	    information about configuring the kernel.  For a
 	    multi-port serial card, place an &man.sio.4; line for each
 	    serial port on the card in the &man.device.hints.5; file.
 	    But place the IRQ specifiers on only one of the entries.
 	    All of the ports on the card should share one IRQ.  For
 	    consistency, use the last serial port to specify the IRQ.
 	    Also, specify the following option in the kernel
 	    configuration file:</para>
 
 	  <programlisting>options COM_MULTIPORT</programlisting>
 
 	  <para>The following <filename>/boot/device.hints</filename>
 	    example is for an AST 4-port serial card on
 	    IRQ&nbsp;12:</para>
 
 	  <programlisting>hint.sio.4.at="isa"
 hint.sio.4.port="0x2a0"
 hint.sio.4.flags="0x701"
 hint.sio.5.at="isa"
 hint.sio.5.port="0x2a8"
 hint.sio.5.flags="0x701"
 hint.sio.6.at="isa"
 hint.sio.6.port="0x2b0"
 hint.sio.6.flags="0x701"
 hint.sio.7.at="isa"
 hint.sio.7.port="0x2b8"
 hint.sio.7.flags="0x701"
 hint.sio.7.irq="12"</programlisting>
 
 	  <para>The flags indicate that the master port has minor
 	    number <literal>7</literal> (<literal>0x700</literal>),
 	    and all the ports share an IRQ
 	    (<literal>0x001</literal>).</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="default-serial-params">
 	  <para>Can I set the default serial parameters for a
 	    port?</para>
 	</question>
 
 	<answer>
 	  <para>See the <link
 	      xlink:href="&url.books.handbook;/serial.html#serial-hw-config">Serial
 	      Communications</link> section in the &os;
 	    Handbook.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="cannot-tip">
 	  <para>Why can I not run <command>tip</command> or
 	    <command>cu</command>?</para>
 	</question>
 
 	<answer>
 	  <para>The built-in &man.tip.1; and
 	    &man.cu.1; utilities can only access the
 	    <filename>/var/spool/lock</filename> directory via user
 	    <systemitem class="username">uucp</systemitem> and group
 	    <systemitem class="groupname">dialer</systemitem>.
 	    Use the <systemitem
 	      class="groupname">dialer</systemitem> group to control
 	    who has access to the modem or remote systems by adding
 	    user accounts to <systemitem
 	      class="groupname">dialer</systemitem>.</para>
 
 	  <para>Alternatively, everyone can be configured to run
 	    &man.tip.1; and &man.cu.1; by typing:</para>
 
 	  <screen>&prompt.root; <userinput>chmod 4511 /usr/bin/cu</userinput>
 &prompt.root; <userinput>chmod 4511 /usr/bin/tip</userinput></screen>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="misc">
     <title>Miscellaneous Questions</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="more-swap">
 	  <para>&os; uses a lot of swap space even when the computer
 	    has free memory left.  Why?</para>
 	</question>
 
 	<answer>
 	  <para>&os; will proactively move entirely idle, unused pages
 	    of main memory into swap in order to make more main memory
 	    available for active use.  This heavy use of swap is
 	    balanced by using the extra free memory for
 	    caching.</para>
 
 	  <para>Note that while &os; is proactive in this regard, it
 	    does not arbitrarily decide to swap pages when the system
 	    is truly idle.  Thus, the system will not be all
 	    paged out after leaving it
 	    idle overnight.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="top-freemem">
 	  <para>Why does <command>top</command> show very little free
 	    memory even when I have very few programs running?</para>
 	</question>
 
 	<answer>
 	  <para>The simple answer is that free memory is wasted
 	    memory.  Any memory that programs do not actively
 	    allocate is used within the &os; kernel as disk cache.
 	    The values shown by &man.top.1; labeled as
 	    <literal>Inact</literal> and <literal>Laundry</literal>
 	    are cached data at different
 	    aging levels.  This cached data means the system does not
 	    have to access a slow disk again for data it has accessed
 	    recently, thus increasing overall performance.  In
 	    general, a low value shown for <literal>Free</literal>
 	    memory in &man.top.1; is good, provided it is not
 	    <emphasis>very</emphasis> low.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="chmod-symlinks">
 	  <para>Why will <command>chmod</command> not change the
 	    permissions on symlinks?</para>
 	</question>
 
 	<answer>
 	  <para>Symlinks do not have permissions, and by default,
 	    &man.chmod.1; will follow symlinks to change the
 	    permissions on the source file, if possible.  For
 	    the file, <filename>foo</filename> with a symlink named
 	    <filename>bar</filename>, this command
 	    will always succeed.</para>
 
 	  <screen>&prompt.user; <userinput>chmod g-w bar</userinput></screen>
 
 	  <para>However, the permissions on <filename>bar</filename>
 	    will not have changed.</para>
 
 	  <para>When changing modes of the file hierarchies rooted in
 	    the files instead of the files themselves, use
 	    either <option>-H</option> or <option>-L</option> together
 	    with <option>-R</option> to make this work.  See
 	    &man.chmod.1; and &man.symlink.7; for more
 	    information.</para>
 
 	  <warning>
 	    <para><option>-R</option> does a
 	      <emphasis>recursive</emphasis> &man.chmod.1;.  Be
 	      careful about specifying directories or symlinks to
 	      directories to &man.chmod.1;.  To change the
 	      permissions of a directory referenced by a symlink, use
 	      &man.chmod.1; without any options and follow the symlink
 	      with a trailing slash (<filename>/</filename>).  For
 	      example, if <filename>foo</filename> is a symlink to
 	      directory <filename>bar</filename>, to
 	      change the permissions of <filename>foo</filename>
 	      (actually <filename>bar</filename>), do
 	      something like:</para>
 
 	    <screen>&prompt.user; <userinput>chmod 555 foo/</userinput></screen>
 
 	    <para>With the trailing slash, &man.chmod.1; will follow
 	      the symlink, <filename>foo</filename>, to change the
 	      permissions of the directory,
 	      <filename>bar</filename>.</para>
 	  </warning>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="dos-binaries">
 	  <para>Can I run DOS binaries under &os;?</para>
 	</question>
 
 	<answer>
 	  <para>Yes.  A DOS emulation program,
 	    <package>emulators/doscmd</package>, is available in the
 	    &os; Ports Collection.</para>
 
 	  <para>If <application>doscmd</application> will not suffice,
 	    <package>emulators/pcemu</package>
 	    emulates an 8088 and enough BIOS services to run many DOS
 	    text-mode applications.  It requires the X Window
 	    System.</para>
 
 	  <para>The Ports Collection also has
 	    <package>emulators/dosbox</package>.  The main focus of
 	    this application is emulating old DOS games using the
 	    local file system for files.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="translation">
 	  <para>What do I need to do to translate a &os; document into
 	    my native language?</para>
 	</question>
 
 	<answer>
 	  <para>See the <link
 	      xlink:href="&url.books.fdp-primer;/translations.html">Translation
 	      <acronym>FAQ</acronym></link> in the &os; Documentation
 	    Project Primer.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="freebsd-mail-bounces">
 	  <para>Why does my email to any address at <systemitem
 	      class="fqdomainname">FreeBSD.org</systemitem>
 	    bounce?</para>
 	</question>
 
 	<answer>
 	  <para>The <systemitem
 	      class="fqdomainname">FreeBSD.org</systemitem> mail
 	    system implements some <application>Postfix</application>
 	    checks on incoming mail and rejects mail that is either
 	    from misconfigured relays or otherwise appears likely to
 	    be spam.  Some of the specific requirements are:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>The IP address of the SMTP client must
 		"reverse-resolve" to a forward confirmed
 		hostname.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>The fully-qualified hostname given in the
 		SMTP conversation (either HELO or EHLO) must resolve
 		to the IP address of the client.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>Other advice to help mail reach its destination
 	    include:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Mail should be sent in plain text, and messages
 		sent to mailing lists should generally be no more than
 		200KB in length.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Avoid excessive cross posting.  Choose
 		<emphasis>one</emphasis> mailing list which seems most
 		relevant and send it there.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>If you still have trouble with email infrastructure at
 	    <systemitem class="fqdomainname">FreeBSD.org</systemitem>,
 	    send a note with the details to
 	    <email>postmaster@freebsd.org</email>;  Include a
 	    date/time interval so that logs may be reviewed &mdash;
 	    and note that we only keep one week's worth of mail logs.
 	    (Be sure to specify the time zone or offset from
 	    UTC.)</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="free-account">
 	  <para>Where can I find a free &os; account?</para>
 	</question>
 
 	<answer>
 	  <para>While &os; does not provide open access to any of
 	    their servers, others do provide open access &unix;
 	    systems.  The charge varies and limited services may be
 	    available.</para>
 
 	  <para><link xlink:href="http://www.arbornet.org/">Arbornet,
 	      Inc</link>, also known as <emphasis>M-Net</emphasis>,
 	    has been providing open access to &unix; systems since
 	    1983.  Starting on an Altos running System III, the site
 	    switched to BSD/OS in 1991.  In June of 2000, the site
 	    switched again to &os;.  <emphasis>M-Net</emphasis> can be
 	    accessed via <application>telnet</application> and
 	    <application>SSH</application> and provides basic access
 	    to the entire &os; software suite.  However, network
 	    access is limited to members and patrons who donate to the
 	    system, which is run as a non-profit organization.
 	    <emphasis>M-Net</emphasis> also provides an bulletin board
 	    system and interactive chat.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="daemon-name">
 	  <para>What is the cute little red guy's name?</para>
 	</question>
 
 	<answer>
 	  <para>He does not have one, and is just called <quote>the
 	      BSD daemon</quote>.  If you insist upon using a name,
 	    call him <quote>beastie</quote>.  Note that
 	    <quote>beastie</quote> is pronounced
 	    <quote>BSD</quote>.</para>
 
 	  <para>More about the BSD daemon is available on his <link
 	      xlink:href="http://www.mckusick.com/beastie/index.html">home
 	      page</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="use-beastie">
 	  <para>Can I use the BSD daemon image?</para>
 	</question>
 
 	<answer>
 	  <para>Perhaps.  The BSD daemon is copyrighted by Marshall
 	    Kirk McKusick.  Check his <link
 	      xlink:href="http://www.mckusick.com/beastie/mainpage/copyright.html">Statement
 	      on the Use of the BSD Daemon Figure</link> for detailed
 	    usage terms.</para>
 
 	  <para>In summary, the image can be used in a tasteful
 	    manner, for personal use, so long as appropriate credit
 	    is given.  Before using the logo commercially, contact
 	    &a.mckusick.email; for permission.  More details are
 	    available on the <link
 	      xlink:href="http://www.mckusick.com/beastie/index.html">BSD
 	      Daemon's home page</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="daemon-images">
 	  <para>Do you have any BSD daemon images I could use?</para>
 	</question>
 
 	<answer>
 	  <para>Xfig and eps drawings are available under
 	    <filename>/usr/share/examples/BSD_daemon/</filename>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="glossary">
 	  <para>I have seen an acronym or other term on the mailing
 	    lists and I do not understand what it means.  Where should
 	    I look?</para>
 	</question>
 
 	<answer>
 	  <para>Refer to the <link
 	      xlink:href="&url.books.handbook;/freebsd-glossary.html">&os;
 	      Glossary</link>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="bikeshed-painting">
 	  <para>Why should I care what color the bikeshed is?</para>
 	</question>
 
 	<answer>
 	  <para>The really, really short answer is that you should
 	    not.  The somewhat longer answer is that just because you
 	    are capable of building a bikeshed does not mean you
 	    should stop others from building one just because you do
 	    not like the color they plan to paint it.  This is a
 	    metaphor indicating that you need not argue about every
 	    little feature just because you know enough to do so.
 	    Some people have commented that the amount of noise
 	    generated by a change is inversely proportional to the
 	    complexity of the change.</para>
 
 	  <para>The longer and more complete answer is that after a
 	    very long argument about whether &man.sleep.1; should take
 	    fractional second arguments, &a.phk.email; posted a long
 	    message entitled <quote><link
 	      xlink:href="http://www.bikeshed.com">A
 	      bike shed (any color will do) on greener
 	      grass...</link></quote>.  The appropriate portions of
 	    that message are quoted below.</para>
 
 	  <blockquote>
 	    <attribution>&a.phk.email; on &a.hackers.name;, October 2,
 	      1999</attribution>
 
 	    <para><quote>What is it about this bike shed?</quote>
 	      Some of you have asked me.</para>
 
 	    <para>It is a long story, or rather it is an old story,
 	      but it is quite short actually.  C. Northcote Parkinson
 	      wrote a book in the early 1960s, called
 	      <quote>Parkinson's Law</quote>, which contains a lot of
 	      insight into the dynamics of management.</para>
 
 	    <para><emphasis>[snip a bit of commentary on the
 		book]</emphasis></para>
 
 	    <para>In the specific example involving the bike shed, the
 	      other vital component is an atomic power-plant, I guess
 	      that illustrates the age of the book.</para>
 
 	    <para>Parkinson shows how you can go into the board of
 	      directors and get approval for building a multi-million
 	      or even billion dollar atomic power plant, but if you
 	      want to build a bike shed you will be tangled up in
 	      endless discussions.</para>
 
 	    <para>Parkinson explains that this is because an atomic
 	      plant is so vast, so expensive and so complicated that
 	      people cannot grasp it, and rather than try, they fall
 	      back on the assumption that somebody else checked all
 	      the details before it got this far.  Richard P. Feynmann
 	      gives a couple of interesting, and very much to the
 	      point, examples relating to Los Alamos in his
 	      books.</para>
 
 	    <para>A bike shed on the other hand.  Anyone can build one
 	      of those over a weekend, and still have time to watch
 	      the game on TV.  So no matter how well prepared, no
 	      matter how reasonable you are with your proposal,
 	      somebody will seize the chance to show that he is doing
 	      his job, that he is paying attention, that he is
 	      <emphasis>here</emphasis>.</para>
 
 	    <para>In Denmark we call it <quote>setting your
 		fingerprint</quote>.  It is about personal pride and
 	      prestige, it is about being able to point somewhere and
 	      say <quote>There!  <emphasis>I</emphasis> did
 		that.</quote> It is a strong trait in politicians, but
 	      present in most people given the chance.  Just think
 	      about footsteps in wet cement.</para>
 	  </blockquote>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="funnies">
     <title>The &os; Funnies</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="very-very-cool">
 	  <para>How cool is &os;?</para>
 	</question>
 
 	<answer>
 	  <para>Q.  Has anyone done any temperature testing while
 	    running &os;?  I know &linux; runs cooler than DOS, but
 	    have never seen a mention of &os;.  It seems to run really
 	    hot.</para>
 
 	  <para>A.  No, but we have done numerous taste tests on
 	    blindfolded volunteers who have also had 250 micrograms of
 	    LSD-25 administered beforehand.  35% of the volunteers
 	    said that &os; tasted sort of orange, whereas &linux;
 	    tasted like purple haze.  Neither group mentioned any
 	    significant variances in temperature.  We eventually had
 	    to throw the results of this survey out entirely anyway
 	    when we found that too many volunteers were wandering out
 	    of the room during the tests, thus skewing the results.
 	    We think most of the volunteers are at Apple now, working
 	    on their new <quote>scratch and sniff</quote> GUI.  It is
 	    a funny old business we are in!</para>
 
 	  <para>Seriously, &os; uses the <acronym>HLT</acronym> (halt)
 	    instruction when the system is idle thus lowering its
 	    energy consumption and therefore the heat it generates.
 	    Also if you have <acronym>ACPI</acronym> (Advanced
 	    Configuration and Power Interface) configured, then &os;
 	    can also put the CPU into a low power mode.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="letmeoutofhere">
 	  <para>Who is scratching in my memory banks??</para>
 	</question>
 
 	<answer>
 	  <para>Q.  Is there anything <quote>odd</quote> that &os;
 	    does when compiling the kernel which would cause the
 	    memory to make a scratchy sound?  When compiling (and for
 	    a brief moment after recognizing the floppy drive upon
 	    startup, as well), a strange scratchy sound emanates from
 	    what appears to be the memory banks.</para>
 
 	  <para>A.  Yes!  You will see frequent references to
 	    <quote>daemons</quote> in the BSD documentation, and what
 	    most people do not know is that this refers to genuine,
 	    non-corporeal entities that now possess your computer.
 	    The scratchy sound coming from your memory is actually
 	    high-pitched whispering exchanged among the daemons as
 	    they best decide how to deal with various system
 	    administration tasks.</para>
 
 	  <para>If the noise gets to you, a good <command>fdisk
 	      /mbr</command> from DOS will get rid of them, but do not
 	    be surprised if they react adversely and try to stop you.
 	    In fact, if at any point during the exercise you hear the
 	    satanic voice of Bill Gates coming from the built-in
 	    speaker, take off running and do not ever look back!
 	    Freed from the counterbalancing influence of the BSD
 	    daemons, the twin demons of DOS and &windows; are often
 	    able to re-assert total control over your machine to the
 	    eternal damnation of your soul.  Now that you know, given
 	    a choice you would probably prefer to get used to the
 	    scratchy noises, no?</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="changing-lightbulbs">
 	  <para>How many &os; hackers does it take to change a
 	    lightbulb?</para>
 	</question>
 
 	<answer>
 	  <para>One thousand, one hundred and sixty-nine:</para>
 
 	  <para>Twenty-three to complain to -CURRENT about the lights
 	    being out;</para>
 
 	  <para>Four to claim that it is a configuration problem, and
 	    that such matters really belong on -questions;</para>
 
 	  <para>Three to submit PRs about it, one of which is misfiled
 	    under doc and consists only of <quote>it's
 	      dark</quote>;</para>
 
 	  <para>One to commit an untested lightbulb which breaks
 	    buildworld, then back it out five minutes later;</para>
 
 	  <para>Eight to flame the PR originators for not including
 	    patches in their PRs;</para>
 
 	  <para>Five to complain about buildworld being broken;</para>
 
 	  <para>Thirty-one to answer that it works for them, and they
 	    must have updated at a bad time;</para>
 
 	  <para>One to post a patch for a new lightbulb to
 	    -hackers;</para>
 
 	  <para>One to complain that he had patches for this three
 	    years ago, but when he sent them to -CURRENT they were
 	    just ignored, and he has had bad experiences with the PR
 	    system; besides, the proposed new lightbulb is
 	    non-reflexive;</para>
 
 	  <para>Thirty-seven to scream that lightbulbs do not belong
 	    in the base system, that committers have no right to do
 	    things like this without consulting the Community, and
 	    WHAT IS -CORE DOING ABOUT IT!?</para>
 
 	  <para>Two hundred to complain about the color of the bicycle
 	    shed;</para>
 
 	  <para>Three to point out that the patch breaks
 	    &man.style.9;;</para>
 
 	  <para>Seventeen to complain that the proposed new lightbulb
 	    is under GPL;</para>
 
 	  <para>Five hundred and eighty-six to engage in a flame war
 	    about the comparative advantages of the GPL, the BSD
 	    license, the MIT license, the NPL, and the personal
 	    hygiene of unnamed FSF founders;</para>
 
 	  <para>Seven to move various portions of the thread to -chat
 	    and -advocacy;</para>
 
 	  <para>One to commit the suggested lightbulb, even though it
 	    shines dimmer than the old one;</para>
 
 	  <para>Two to back it out with a furious flame of a commit
 	    message, arguing that &os; is better off in the dark than
 	    with a dim lightbulb;</para>
 
 	  <para>Forty-six to argue vociferously about the backing out
 	    of the dim lightbulb and demanding a statement from
 	    -core;</para>
 
 	  <para>Eleven to request a smaller lightbulb so it will fit
 	    their Tamagotchi if we ever decide to port &os; to that
 	    platform;</para>
 
 	  <para>Seventy-three to complain about the SNR on -hackers
 	    and -chat and unsubscribe in protest;</para>
 
 	  <para>Thirteen to post <quote>unsubscribe</quote>,
 	    <quote>How do I unsubscribe?</quote>, or <quote>Please
 	      remove me from the list</quote>, followed by the usual
 	    footer;</para>
 
 	  <para>One to commit a working lightbulb while everybody is
 	    too busy flaming everybody else to notice;</para>
 
 	  <para>Thirty-one to point out that the new lightbulb would
 	    shine 0.364% brighter if compiled with TenDRA (although it
 	    will have to be reshaped into a cube), and that &os;
 	    should therefore switch to TenDRA instead of GCC;</para>
 
 	  <para>One to complain that the new lightbulb lacks
 	    fairings;</para>
 
 	  <para>Nine (including the PR originators) to ask <quote>what
 	      is MFC?</quote>;</para>
 
 	  <para>Fifty-seven to complain about the lights being out two
 	    weeks after the bulb has been changed.</para>
 
 	  <para><emphasis>&a.nik.email; adds:</emphasis></para>
 
 	  <para><emphasis>I was laughing quite hard at
 	      this.</emphasis></para>
 
 	  <para><emphasis>And then I thought, <quote>Hang on,
 	      shouldn't there be '1 to document it.' in that list
 	      somewhere?</quote></emphasis></para>
 
 	  <para><emphasis>And then I was enlightened
 	      :-)</emphasis></para>
 
 	  <para><emphasis>&a.tabthorpe.email;</emphasis> says:
 	    <quote>None, <emphasis>real</emphasis> &os; hackers are
 	      not afraid of the dark!</quote></para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="dev-null">
 	  <para>Where does data written to
 	    <filename>/dev/null</filename> go?</para>
 	</question>
 
 	<answer>
 	  <para>It goes into a special data sink in the CPU where it
 	    is converted to heat which is vented through the heatsink
 	    / fan assembly.  This is why CPU cooling is increasingly
 	    important; as people get used to faster processors, they
 	    become careless with their data and more and more of it
 	    ends up in <filename>/dev/null</filename>, overheating
 	    their CPUs.  If you delete <filename>/dev/null</filename>
 	    (which effectively disables the CPU data sink) your CPU
 	    may run cooler but your system will quickly become
 	    constipated with all that excess data and start to behave
 	    erratically.  If you have a fast network connection you
 	    can cool down your CPU by reading data out of
 	    <filename>/dev/random</filename> and sending it off
 	    somewhere; however you run the risk of overheating your
 	    network connection and <filename>/</filename> or angering
 	    your ISP, as most of the data will end up getting
 	    converted to heat by their equipment, but they generally
 	    have good cooling, so if you do not overdo it you should
 	    be OK.</para>
 
 	  <para><emphasis>Paul Robinson adds:</emphasis></para>
 
 	  <para>There are other methods.  As every good sysadmin
 	    knows, it is part of standard practice to send data to the
 	    screen of interesting variety to keep all the pixies that
 	    make up your picture happy.  Screen pixies (commonly
 	    mis-typed or re-named as <quote>pixels</quote>) are
 	    categorized by the type of hat they wear (red, green or
 	    blue) and will hide or appear (thereby showing the color
 	    of their hat) whenever they receive a little piece of
 	    food.  Video cards turn data into pixie-food, and then
 	    send them to the pixies &mdash; the more expensive the
 	    card, the better the food, so the better behaved the
 	    pixies are.  They also need constant stimulation &mdash;
 	    this is why screen savers exist.</para>
 
 	  <para>To take your suggestions further, you could just throw
 	    the random data to console, thereby letting the pixies
 	    consume it.  This causes no heat to be produced at all,
 	    keeps the pixies happy and gets rid of your data quite
 	    quickly, even if it does make things look a bit messy on
 	    your screen.</para>
 
 	  <para>Incidentally, as an ex-admin of a large ISP who
 	    experienced many problems attempting to maintain a stable
 	    temperature in a server room, I would strongly discourage
 	    people sending the data they do not want out to the
 	    network.  The fairies who do the packet switching and
 	    routing get annoyed by it as well.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="punk-my-friend">
 	  <para>My colleague sits at the computer too much, how
 	    can I prank her?</para>
 	</question>
 
 	<answer>
 	  <para>Install <package role="port">games/sl</package> and
 	    wait for her to mistype <userinput>sl</userinput> for
 	    <command>ls</command>.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="advanced">
     <title>Advanced Topics</title>
 
     <qandaset>
       <qandaentry>
 	<question xml:id="learn-advanced">
 	  <para>How can I learn more about &os;'s internals?</para>
 	</question>
 
 	<answer>
 	  <para>See the <link
 	      xlink:href="&url.books.arch-handbook;">&os;
 	      Architecture Handbook</link>.</para>
 
 	  <para>Additionally, much general &unix; knowledge is
 	    directly applicable to &os;.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="how-to-contribute">
 	  <para>How can I contribute to &os;?  What can I do to
 	    help?</para>
 	</question>
 
 	<answer>
 	  <para>We accept all types of contributions: documentation,
 	    code, and even art.  See the article on <link
 	      xlink:href="&url.articles.contributing;/article.html">Contributing
 	      to &os;</link> for specific advice on how to do
 	    this.</para>
 
 	  <para>And thanks for the thought!</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="define-snap-release">
 	  <para>What are snapshots and releases?</para>
 	</question>
 
 	<answer>
 	  <para>There are currently &rel.numbranch; active/semi-active
 	    branches in the &os; <link
 	      xlink:href="http://svnweb.FreeBSD.org/base/">Subversion
 	      Repository</link>.  (Earlier branches are only changed
 	    very rarely, which is why there are only &rel.numbranch;
 	    active branches of development):</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>&rel2.releng; AKA
 		&rel2.stable;</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>&rel.releng; AKA
 		&rel.stable;</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>&rel.head.releng; AKA
 		<emphasis>-CURRENT</emphasis> AKA
 		&rel.head;</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para><literal>HEAD</literal> is not an actual branch tag.
 	    It is a symbolic constant for
 	    the current, non-branched development
 		stream known as
 	    <emphasis>-CURRENT</emphasis>.</para>
 
 	  <para>Right now, <emphasis>-CURRENT</emphasis> is the
 	    &rel.head.relx; development stream; the &rel.stable;
 	    branch, &rel.releng;, forked off from
 	    <emphasis>-CURRENT</emphasis> in &rel.relengdate; and the
 	    &rel2.stable; branch, &rel2.releng;, forked off from
 	    <emphasis>-CURRENT</emphasis> in &rel2.relengdate;.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="kernel-panic-troubleshooting">
 	  <para>How can I make the most of the data I see when my
 	    kernel panics?</para>
 	</question>
 
 	<answer>
 	  <para>Here is typical kernel panic:</para>
 
 	  <programlisting>Fatal trap 12: page fault while in kernel mode
 fault virtual address   = 0x40
 fault code              = supervisor read, page not present
 instruction pointer     = 0x8:0xf014a7e5
 stack pointer           = 0x10:0xf4ed6f24
 frame pointer           = 0x10:0xf4ed6f28
 code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, def32 1, gran 1
 processor eflags        = interrupt enabled, resume, IOPL = 0
 current process         = 80 (mount)
 interrupt mask          =
 trap number             = 12
 panic: page fault</programlisting>
 
 	  <para>This message is not enough.  While the instruction
 	    pointer value is important, it is also configuration
 	    dependent as it varies depending on the kernel image.
 	    If it is a <filename>GENERIC</filename> kernel
 	    image from one of the snapshots, it is possible for
 	    somebody else to track down the offending function, but
 	    for a custom kernel, only you can tell us where the fault
 	    occurred.</para>
 
 	  <para>To proceed:</para>
 
 	  <procedure>
 	    <step>
 	      <para>Write down the instruction pointer value.  Note
 		that the <literal>0x8:</literal> part at the beginning
 		is not significant in this case: it is the
 		<literal>0xf0xxxxxx</literal> part that we
 		want.</para>
 	    </step>
 
 	    <step>
 	      <para>When the system reboots, do the following:</para>
 
 	      <screen>&prompt.user; <userinput>nm -n kernel.that.caused.the.panic | grep f0xxxxxx</userinput></screen>
 
 	      <para>where <literal>f0xxxxxx</literal> is the
 		instruction pointer value.  The odds are you will not
 		get an exact match since the symbols in the kernel
 		symbol table are for the entry points of functions and
 		the instruction pointer address will be somewhere
 		inside a function, not at the start.  If you do not
 		get an exact match, omit the last digit from the
 		instruction pointer value and try again:</para>
 
 	      <screen>&prompt.user; <userinput>nm -n kernel.that.caused.the.panic | grep f0xxxxx</userinput></screen>
 
 	      <para>If that does not yield any results, chop off
 		another digit.  Repeat until there is some sort of
 		output.  The result will be a possible list of
 		functions which caused the panic.  This is a less than
 		exact mechanism for tracking down the point of
 		failure, but it is better than nothing.</para>
 	    </step>
 	  </procedure>
 
 	  <para>However, the best way to track down the cause of a
 	    panic is by capturing a crash dump, then using
 	    &man.kgdb.1; to generate a stack trace on the crash
 	    dump.</para>
 
 	  <para>In any case, the method is this:</para>
 
 	  <procedure>
 	    <step>
 	      <para>Make sure that the following line is included in
 		the kernel configuration file:</para>
 
 	      <programlisting>makeoptions     DEBUG=-g          # Build kernel with gdb(1) debug symbols</programlisting>
 	    </step>
 
 	    <step>
 	      <para>Change to the <filename>/usr/src</filename>
 		directory:</para>
 
 	      <screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
 	    </step>
 
 	    <step>
 	      <para>Compile the kernel:</para>
 
 	      <screen>&prompt.root; <userinput>make buildkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput></screen>
 	    </step>
 
 	    <step>
 	      <para>Wait for &man.make.1; to finish compiling.</para>
 	    </step>
 
 	    <step>
 	      <screen>&prompt.root; <userinput>make installkernel KERNCONF=MYKERNEL</userinput></screen>
 	    </step>
 
 	    <step>
 	      <para>Reboot.</para>
 	    </step>
 	  </procedure>
 
 	  <note>
 	    <para>If <varname>KERNCONF</varname> is not included,
 	      the <filename>GENERIC</filename> kernel will instead
 	      be built and installed.</para>
 	  </note>
 
 	  <para>The &man.make.1; process will have built two kernels.
 	    <filename>/usr/obj/usr/src/sys/MYKERNEL/kernel</filename>
 	    and
 	    <filename>/usr/obj/usr/src/sys/MYKERNEL/kernel.debug</filename>.
 	    <filename>kernel</filename> was installed as
 	    <filename>/boot/kernel/kernel</filename>, while
 	    <filename>kernel.debug</filename> can be used as the
 	    source of debugging symbols for &man.kgdb.1;.</para>
 
 	  <para>To capture a crash dump, edit
 	    <filename>/etc/rc.conf</filename> and set
 	    <literal>dumpdev</literal> to point to either the swap
 	    partition or <literal>AUTO</literal>.  This will cause the
 	    &man.rc.8; scripts to use the &man.dumpon.8; command to
 	    enable crash dumps.  This command can also be run
 	    manually.  After a panic, the crash dump can be recovered
 	    using &man.savecore.8;; if <literal>dumpdev</literal> is
 	    set in <filename>/etc/rc.conf</filename>, the &man.rc.8;
 	    scripts will run &man.savecore.8; automatically and put
 	    the crash dump in <filename>/var/crash</filename>.</para>
 
 	  <note>
 	    <para>&os; crash dumps are usually the same size as
 	      physical RAM.  Therefore, make sure there is enough
 	      space in <filename>/var/crash</filename> to hold the
 	      dump.  Alternatively, run &man.savecore.8; manually
 	      and have it recover the crash dump to another directory
 	      with more room.  It is possible to limit the
 	      size of the crash dump by using <literal>options
 		MAXMEM=N</literal> where
 	      <replaceable>N</replaceable> is the size of kernel's
 	      memory usage in KBs.  For example, for 1&nbsp;GB
 	      of RAM, limit the kernel's memory usage to
 	      128&nbsp;MB, so that the crash dump size
 	      will be 128&nbsp;MB instead of 1&nbsp;GB.</para>
 	  </note>
 
 	  <para>Once the crash dump has been recovered , get a
 	    stack trace as follows:</para>
 
 	  <screen>&prompt.user; <userinput>kgdb /usr/obj/usr/src/sys/MYKERNEL/kernel.debug /var/crash/vmcore.0</userinput>
 <prompt>(kgdb)</prompt> <userinput>backtrace</userinput></screen>
 
 	  <para>Note that there may be several screens worth of
 	    information.  Ideally, use &man.script.1; to
 	    capture all of them.  Using the unstripped kernel image
 	    with all the debug symbols should show the exact line of
 	    kernel source code where the panic occurred.  The stack
 	    trace is usually read from the bottom up to trace
 	    the exact sequence of events that lead to the crash.
 	    &man.kgdb.1; can also be used to print out the contents of
 	    various variables or structures to examine the system
 	    state at the time of the crash.</para>
 
 	  <tip>
 	    <para>If a second computer is available, &man.kgdb.1; can
 	      be configured to do remote debugging, including setting
 	      breakpoints and single-stepping through the kernel
 	      code.</para>
 	  </tip>
 
 	  <note>
 	    <para>If <literal>DDB</literal> is enabled and the
 	      kernel drops into the debugger, a panic
 	      and a crash dump can be forced by typing
 	      <literal>panic</literal> at the <literal>ddb</literal>
 	      prompt.  It may stop in the debugger again during the
 	      panic phase.  If it does, type
 	      <literal>continue</literal> and it will finish the crash
 	      dump.</para>
 	  </note>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="dlsym-failure">
 	  <para>Why has <function>dlsym()</function> stopped working
 	    for ELF executables?</para>
 	</question>
 
 	<answer>
 	  <para>The ELF toolchain does not, by default, make the
 	    symbols defined in an executable visible to the dynamic
 	    linker.  Consequently <function>dlsym()</function>
 	    searches on handles obtained from calls to
 	    <function>dlopen(NULL, flags)</function> will fail to find
 	    such symbols.</para>
 
 	  <para>To search, using
 	    <function>dlsym()</function>, for symbols present in the
 	    main executable of a process, link the
 	    executable using the <option>--export-dynamic</option>
 	    option to the ELF linker (&man.ld.1;).</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question xml:id="change-kernel-address-space">
 	  <para>How can I increase or reduce the kernel address space
 	    on i386?</para>
 	</question>
 
 	<answer>
 	  <para>By default, the kernel address space is 1&nbsp;GB
 	    (2&nbsp;GB for PAE) for i386.  When running a
 	    network-intensive server or using
 	    ZFS, this will probably not be
 	    enough.</para>
 
 	  <para>Add the following line to the kernel configuration
 	    file to increase available space and rebuild the
 	    kernel:</para>
 
 	  <programlisting>options KVA_PAGES=<replaceable>N</replaceable></programlisting>
 
 	  <para>To find the correct value of
 	    <replaceable>N</replaceable>, divide the desired address
 	    space size (in megabytes) by four.  (For example, it is
 	    <literal>512</literal> for 2&nbsp;GB.)</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter xml:id="acknowledgments">
     <title>Acknowledgments</title>
 
     <para>This innocent little Frequently Asked Questions document has
       been written, rewritten, edited, folded, spindled, mutilated,
       eviscerated, contemplated, discombobulated, cogitated,
       regurgitated, rebuilt, castigated, and reinvigorated over the
       last decade, by a cast of hundreds if not thousands.
       Repeatedly.</para>
 
     <para>We wish to thank every one of the people responsible, and we
       encourage you to <link
 	xlink:href="&url.articles.contributing;/article.html">join
 	them</link> in making this <acronym>FAQ</acronym> even
       better.</para>
   </chapter>
 </book>
diff --git a/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml b/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
index 3a40f23413..c20e796c67 100644
--- a/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
@@ -1,3018 +1,3018 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter xmlns="http://docbook.org/ns/docbook"
   xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
   xml:id="bsdinstall">
 
   <info>
     <title>Installing &os;</title>
 
     <authorgroup>
       <author>
 	<personname>
 	  <firstname>Jim</firstname>
 	  <surname>Mock</surname>
 	</personname>
 
 	<contrib>Restructured, reorganized, and parts rewritten
 	  by </contrib>
       </author>
     </authorgroup>
 
     <!---
       <authorgroup>
 	<author>
 	  <personname>
 	    <firstname>Randy</firstname>
 	    <surname>Pratt</surname>
 	  </personname>
 	  <contrib>The sysinstall walkthrough, screenshots, and
 	    general copy by </contrib>
 	</author>
       </authorgroup>
     -->
 
     <authorgroup>
       <author>
 	<personname>
 	  <firstname>Gavin</firstname>
 	  <surname>Atkinson</surname>
 	</personname>
 
 	<contrib>Updated for bsdinstall by </contrib>
       </author>
 
       <author>
 	<personname>
 	  <firstname>Warren</firstname>
 	  <surname>Block</surname>
 	</personname>
       </author>
     </authorgroup>
 
     <authorgroup>
       <author>
 	<personname>
 	  <firstname>Allan</firstname>
 	  <surname>Jude</surname>
 	</personname>
 
 	<contrib>Updated for root-on-ZFS by </contrib>
       </author>
     </authorgroup>
   </info>
 
   <sect1 xml:id="bsdinstall-synopsis">
     <title>Synopsis</title>
 
     <indexterm><primary>installation</primary></indexterm>
 
     <para>There are several different ways of getting &os; to run,
       depending on the environment.  Those are:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Virtual Machine images, to download and import on a
 	  virtual environment of choice.  These can be downloaded from
 	  the <link
 	    xlink:href="https://www.freebsd.org/where.html">Download
 	    FreeBSD</link> page.  There are images for KVM
 	  (<quote>qcow2</quote>), VMWare (<quote>vmdk</quote>),
 	  Hyper-V (<quote>vhd</quote>), and raw device images that are
 	  universally supported.  These are not installation images,
 	  but rather the preconfigured (<quote>already
 	    installed</quote>) instances, ready to run and perform
 	  post-installation tasks.</para>
       </listitem>
 
       <listitem>
 	<para>Virtual Machine images available at Amazon's <link
 	    xlink:href="https://aws.amazon.com/marketplace/pp/B07L6QV354">AWS
 	    Marketplace</link>, <link
 	    xlink:href="https://azuremarketplace.microsoft.com/en-us/marketplace/apps?search=freebsd&amp;page=1">Microsoft
 	    Azure Marketplace</link>, and <link
 	    xlink:href="https://console.cloud.google.com/marketplace/details/freebsd-cloud/freebsd-12">Google
 	    Cloud Platform</link>, to run on their respective hosting
 	  services.  For more information on deploying &os; on Azure
 	  please consult the relevant chapter in the <link
 	    xlink:href="https://docs.microsoft.com/en-us/azure/virtual-machines/linux/freebsd-intro-on-azure">Azure
 	    Documentation</link>.</para>
       </listitem>
 
       <listitem>
 	<para>SD card images, for embedded systems such as Raspberry
 	  Pi or BeagleBone Black.  These can be downloaded from the
 	  <link
 	    xlink:href="https://www.freebsd.org/where.html">Download
 	    FreeBSD</link> page.  These files must be uncompressed and
 	  written as a raw image to an SD card, from which the board
 	  will then boot.</para>
       </listitem>
 
       <listitem>
 	<para>Installation images, to install &os; on
 	  a hard drive for the usual desktop, laptop, or server
 	  systems.</para>
       </listitem>
     </itemizedlist>
 
     <para>The rest of this chapter describes the fourth case,
       explaining how to install &os; using the text-based
       installation program named
       <application>bsdinstall</application>.</para>
 
     <para>In general, the installation instructions in this chapter
       are written for the &i386; and <acronym>AMD64</acronym>
       architectures.  Where applicable, instructions specific to other
       platforms will be listed.  There may be minor differences
       between the installer and what is shown here, so use this
       chapter as a general guide rather than as a set of literal
       instructions.</para>
 
     <note><para>Users who prefer to install &os; using a graphical
       installer may be interested in
-      <link xlink:href="https://www.furybsd.org">FuryBSD</link>,
-      <link xlink:href="https://ghostbsd.org">GhostBSD</link> or
+      <link xlink:href="https://ghostbsd.org">GhostBSD</link>,
       <link
-	xlink:href="https://www.midnightbsd.org">MidnightBSD</link>.</para>
+	xlink:href="https://www.midnightbsd.org">MidnightBSD</link> or
+      <link xlink:href="https://nomadbsd.org/">NomadBSD</link>.</para>
     </note>
 
     <para>After reading this chapter, you will know:</para>
 
     <itemizedlist>
       <listitem>
 	<para>The minimum hardware requirements and &os; supported
 	  architectures.</para>
       </listitem>
 
       <listitem>
 	<para>How to create the &os; installation media.</para>
       </listitem>
 
       <listitem>
 	<para>How to start
 	  <application>bsdinstall</application>.</para>
       </listitem>
 
       <listitem>
 	<para>The questions <application>bsdinstall</application> will
 	  ask, what they mean, and how to answer them.</para>
       </listitem>
 
       <listitem>
 	<para>How to troubleshoot a failed installation.</para>
       </listitem>
 
       <listitem>
 	<para>How to access a live version of &os; before committing
 	  to an installation.</para>
       </listitem>
     </itemizedlist>
 
     <para>Before reading this chapter, you should:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Read the supported hardware list that shipped with the
 	  version of &os; to be installed and verify that the system's
 	  hardware is supported.</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 xml:id="bsdinstall-hardware">
     <title>Minimum Hardware Requirements</title>
 
     <para>The hardware requirements to install &os; vary by
       architecture.  Hardware architectures and devices supported by a
       &os; release are listed on the <link
 	xlink:href="&url.base;/releases/index.html">&os; Release
       Information</link> page.  The <link
 	xlink:href="&url.base;/where.html">&os; download page</link>
       also has recommendations for choosing the correct image for
       different architectures.</para>
 
     <para>A &os; installation requires a minimum of 96&nbsp;MB of
       <acronym>RAM</acronym> and 1.5&nbsp;GB of free hard drive space.
       However, such small amounts of memory and disk space are really
       only suitable for custom applications like embedded appliances.
       General-purpose desktop systems need more resources.
       2-4&nbsp;GB RAM and at least 8&nbsp;GB hard drive space is a
       good starting point.</para>
 
     <para>These are the processor requirements for each
       architecture:</para>
 
     <variablelist>
       <varlistentry>
 	<term>&arch.amd64;</term>
 	<listitem>
 	  <para>This is the most common desktop and laptop processor
 	    type, used in most modern systems.  &intel; calls it
 	    <acronym>Intel64</acronym>.  Other manufacturers sometimes
 	    call it <acronym>x86-64</acronym>.</para>
 
 	  <para>Examples of &arch.amd64; compatible processors
 	    include: &amd.athlon;64, &amd.opteron;,
 	    multi-core &intel;&nbsp;&xeon;, and
 	    &intel;&nbsp;&core;&nbsp;2 and later processors.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>&arch.i386;</term>
 	<listitem>
 	  <para>Older desktops and laptops often use this 32-bit, x86
 	    architecture.</para>
 
 	  <para>Almost all i386-compatible processors with a floating
 	    point unit are supported.  All &intel; processors 486 or
 	    higher are supported.</para>
 
 	  <para>&os; will take advantage of Physical Address
 	    Extensions (<acronym>PAE</acronym>) support on
 	    <acronym>CPU</acronym>s with this feature.  A kernel with
 	    the <acronym>PAE</acronym> feature enabled will detect
 	    memory above 4&nbsp;GB and allow it to be used by the
 	    system.  However, using <acronym>PAE</acronym> places
 	    constraints on device drivers and other features of
 	    &os;.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>&arch.powerpc;</term>
 	<listitem>
 	  <para>All New World <acronym>ROM</acronym> &apple;
 	    &mac; systems with built-in <acronym>USB</acronym>
 	    are supported.  <acronym>SMP</acronym> is supported on
 	    machines with multiple <acronym>CPU</acronym>s.</para>
 
 	  <para>A 32-bit kernel can only use the first 2&nbsp;GB of
 	    <acronym>RAM</acronym>.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>&arch.sparc64;</term>
 	<listitem>
 	  <para>Systems supported by &os;/&arch.sparc64; are listed at
 	    the <link
 	      xlink:href="&url.base;/platforms/sparc.html">FreeBSD/sparc64
 	      Project</link>.</para>
 
 	  <para><acronym>SMP</acronym> is supported on all systems
 	    with more than 1 processor.  A dedicated disk is required
 	    as it is not possible to share a disk with another
 	    operating system at this time.</para>
 	</listitem>
       </varlistentry>
     </variablelist>
   </sect1>
 
   <sect1 xml:id="bsdinstall-pre">
     <title>Pre-Installation Tasks</title>
 
     <para>Once it has been determined that the system meets the
       minimum hardware requirements for installing &os;, the
       installation file should be downloaded and the installation
       media prepared.  Before doing this, check that the system is
       ready for an installation by verifying the items in this
       checklist:</para>
 
     <procedure>
       <step>
 	<title>Back Up Important Data</title>
 
 	<para>Before installing any operating system,
 	  <emphasis>always</emphasis> backup all important data first.
 	  Do not store the backup on the system being installed.
 	  Instead, save the data to a removable disk such as a
 	  <acronym>USB</acronym> drive, another system on the network,
 	  or an online backup service.  Test the backup before
 	  starting the installation to make sure it contains all of
 	  the needed files.  Once the installer formats the system's
 	  disk, all data stored on that disk will be lost.</para>
       </step>
 
       <step>
 	<title>Decide Where to Install &os;</title>
 
 	<para>If &os; will be the only operating system installed,
 	  this step can be skipped.  But if &os; will share the disk
 	  with another operating system, decide which disk or
 	  partition will be used for &os;.</para>
 
 	<para>In the &arch.i386; and &arch.amd64; architectures, disks
 	  can be divided into multiple partitions using one of two
 	  partitioning schemes.  A traditional <firstterm>Master Boot
 	    Record</firstterm> (<acronym>MBR</acronym>) holds a
 	  partition table defining up to four <firstterm>primary
 	    partitions</firstterm>.  For historical reasons, &os;
 	  calls these primary partition
 	  <firstterm>slices</firstterm>.  One of these primary
 	  partitions can be made into an <firstterm>extended
 	    partition</firstterm> containing multiple
 	  <firstterm>logical partitions</firstterm>.  The
 	  <firstterm>GUID Partition Table</firstterm>
 	  (<acronym>GPT</acronym>) is a newer and simpler method of
 	  partitioning a disk.  Common <acronym>GPT</acronym>
 	  implementations allow up to 128 partitions per disk,
 	  eliminating the need for logical partitions.</para>
 
 	<para>The &os; boot loader requires either a primary or
 	  <acronym>GPT</acronym> partition.  If all of the primary or
 	  <acronym>GPT</acronym> partitions are already in use, one
 	  must be freed for &os;.  To create a partition without
 	  deleting existing data, use a partition resizing tool to
 	  shrink an existing partition and create a new partition
 	  using the freed space.</para>
 
 	<para>A variety of free and commercial partition resizing
 	  tools are listed at <link
 	    xlink:href="http://en.wikipedia.org/wiki/List_of_disk_partitioning_software">http://en.wikipedia.org/wiki/List_of_disk_partitioning_software</link>.
 	  <application>GParted Live</application> (<link
 	    xlink:href="http://gparted.sourceforge.net/livecd.php">http://gparted.sourceforge.net/livecd.php</link>)
 	  is a free live <acronym>CD</acronym> which includes the
 	  <application>GParted</application> partition editor.
 	  <application>GParted</application> is also included with
 	  many other Linux live <acronym>CD</acronym>
 	  distributions.</para>
 
 	<warning>
 	  <para>When used properly, disk shrinking utilities can
 	    safely create space for creating a new partition.  Since
 	    the possibility of selecting the wrong partition exists,
 	    always backup any important data and verify the integrity
 	    of the backup before modifying disk partitions.</para>
 	</warning>
 
 	<para>Disk partitions containing different operating systems
 	  make it possible to install multiple operating systems on
 	  one computer.  An alternative is to use virtualization
 	  (<xref linkend="virtualization"/>) which allows multiple
 	  operating systems to run at the same time without modifying
 	  any disk partitions.</para>
       </step>
 
       <step>
 	<title>Collect Network Information</title>
 
 	<para>Some &os; installation methods require a network
 	  connection in order to download the installation files.
 	  After any installation, the installer will offer to setup
 	  the system's network interfaces.</para>
 
 	<para>If the network has a <acronym>DHCP</acronym> server, it
 	  can be used to provide automatic network configuration.  If
 	  <acronym>DHCP</acronym> is not available, the following
 	  network information for the system must be obtained from the
 	  local network administrator or Internet service
 	  provider:</para>
 
 	<orderedlist xml:id="bsdinstall-collect-network-information">
 	  <title>Required Network Information</title>
 
 	  <listitem>
 	    <para><acronym>IP</acronym> address</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Subnet mask</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><acronym>IP</acronym> address of default
 	      gateway</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Domain name of the network</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><acronym>IP</acronym> addresses of the network's
 	      <acronym>DNS</acronym> servers</para>
 	  </listitem>
 	</orderedlist>
       </step>
 
       <step>
 	<title>Check for &os; Errata</title>
 
 	<para>Although the &os;&nbsp;Project strives to ensure that
 	  each release of &os; is as stable as possible, bugs
 	  occasionally creep into the process.  On very rare occasions
 	  those bugs affect the installation process.  As these
 	  problems are discovered and fixed, they are noted in the
 	  &os; Errata (<link
 	    xlink:href="&url.base;/releases/&rel121.current;R/errata.html">https://www.freebsd.org/releases/&rel121.current;R/errata.html</link>)
 	  on the &os; web site.  Check the errata before installing to
 	  make sure that there are no problems that might affect the
 	  installation.</para>
 
 	<para>Information and errata for all the releases can be found
 	  on the release information section of the &os; web site
 	  (<link
 	    xlink:href="&url.base;/releases/index.html">https://www.freebsd.org/releases/index.html</link>).</para>
       </step>
     </procedure>
 
     <sect2 xml:id="bsdinstall-installation-media">
       <title>Prepare the Installation Media</title>
 
       <para>The &os; installer is not an application that can be run
 	from within another operating system.  Instead, download a
 	&os; installation file, burn it to the media associated with
 	its file type and size (<acronym>CD</acronym>,
 	<acronym>DVD</acronym>, or <acronym>USB</acronym>), and boot
 	the system to install from the inserted media.</para>
 
       <para>&os; installation files are available at <link
 	  xlink:href="&url.base;/where.html#download">www.freebsd.org/where.html#download</link>.
 	Each installation file's name includes the release version of
 	&os;, the architecture, and the type of file.  For example, to
 	install &os; 12.1 on an &arch.amd64; system from a
 	<acronym>DVD</acronym>, download
 	<filename>FreeBSD-12.1-RELEASE-amd64-dvd1.iso</filename>, burn
 	this file to a <acronym>DVD</acronym>, and boot the system
 	with the <acronym>DVD</acronym> inserted.</para>
 
       <para>Installation files are available in several formats.
 	The formats vary depending on computer architecture and media
 	type.</para>
 
       <para xml:id="bsdinstall-installation-media-uefi">Additional
 	installation files are included for computers that boot with
 	<acronym>UEFI</acronym> (Unified Extensible Firmware
 	Interface).  The names of these files include the string
 	<filename>uefi</filename>.</para>
 
       <para>File types:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>-bootonly.iso</literal>: This is the smallest
 	    installation file as it only contains the installer.  A
 	    working Internet connection is required during
 	    installation as the installer will download the files it
 	    needs to complete the &os; installation.  This file should
 	    be burned to a <acronym>CD</acronym> using a
 	    <acronym>CD</acronym> burning application.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>-disc1.iso</literal>: This file contains all
 	    of the files needed to install &os;, its source, and the
 	    Ports Collection.  It should be burned to a
 	    <acronym>CD</acronym> using a <acronym>CD</acronym>
 	    burning application.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>-dvd1.iso</literal>: This file contains all
 	    of the files needed to install &os;, its source, and the
 	    Ports Collection.  It also contains a set of popular
 	    binary packages for installing a window manager and some
 	    applications so that a complete system can be installed
 	    from media without requiring a connection to the Internet.
 	    This file should be burned to a <acronym>DVD</acronym>
 	    using a <acronym>DVD</acronym> burning application.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>-memstick.img</literal>: This file contains
 	    all of the files needed to install &os;, its source, and
 	    the Ports Collection.  It should be burned to a
 	    <acronym>USB</acronym> stick using the instructions
 	    below.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>-mini-memstick.img</literal>: Like
 	    <literal>-bootonly.iso</literal>, does not include
 	    installation files, but downloads them as needed.  A
 	    working internet connection is required during
 	    installation.  Write this file to a <acronym>USB</acronym>
 	    stick as shown in <xref linkend="bsdinstall-usb"/>.</para>
 	</listitem>
       </itemizedlist>
 
       <para>After downloading the image file, download
 	<filename>CHECKSUM.SHA256</filename> from
 	the same directory.  Calculate a
 	<firstterm>checksum</firstterm> for the image file.
 	&os; provides &man.sha256.1; for this, used as <command>sha256
 	  <replaceable>imagefilename</replaceable></command>.
 	Other operating systems have similar programs.</para>
 
       <para>Compare the calculated checksum with the one shown in
 	<filename>CHECKSUM.SHA256</filename>.  The checksums must
 	match exactly.  If the checksums do not match, the image file
 	is corrupt and must be downloaded again.</para>
 
       <sect3 xml:id="bsdinstall-usb">
 	<title>Writing an Image File to <acronym>USB</acronym></title>
 
 	<para>The <filename>*.img</filename> file is an
 	  <emphasis>image</emphasis> of the complete contents of a
 	  memory stick.  It <emphasis>cannot</emphasis> be copied to
 	  the target device as a file.  Several applications are
 	  available for writing the <filename>*.img</filename> to a
 	  <acronym>USB</acronym> stick.  This section describes two of
 	  these utilities.</para>
 
 	<important>
 	  <para>Before proceeding, back up any important data on the
 	    <acronym>USB</acronym> stick.  This procedure will erase
 	    the existing data on the stick.</para>
 	</important>
 
 	<procedure xml:id="bsdinstall-usb-dd">
 	  <title>Using <command>dd</command> to Write the
 	    Image</title>
 
 	  <warning>
 	    <para>This example uses <filename>/dev/da0</filename> as
 	      the target device where the image will be written.  Be
 	      <emphasis>very careful</emphasis> that the correct
 	      device is used as this command will destroy the existing
 	      data on the specified target device.</para>
 	  </warning>
 
 	  <step>
 	    <para>The &man.dd.1; command-line utility is
 	      available on BSD, &linux;, and &macos; systems.  To burn
 	      the image using <command>dd</command>, insert the
 	      <acronym>USB</acronym> stick and determine its device
 	      name.  Then, specify the name of the downloaded
 	      installation file and the device name for the
 	      <acronym>USB</acronym> stick.  This example burns the
 	      &arch.amd64; installation image to the first
 	      <acronym>USB</acronym> device on an existing &os;
 	      system.</para>
 
 	    <screen>&prompt.root; <userinput>dd if=<replaceable>FreeBSD-12.1-RELEASE-amd64-memstick.img</replaceable> of=/dev/<replaceable>da0</replaceable> bs=1M conv=sync</userinput></screen>
 
 	    <para>If this command fails, verify that the
 	      <acronym>USB</acronym> stick is not mounted and that the
 	      device name is for the disk, not a partition.  Some
 	      operating systems might require this command to be run
 	      with &man.sudo.8;.  The &man.dd.1; syntax varies slightly
 	      across different platforms; for example, &macos; requires
 	      a lower-case <option>bs=1m</option>.
 	      Systems like &linux; might buffer
 	      writes.  To force all writes to complete, use
 	      &man.sync.8;.</para>
 	  </step>
 	</procedure>
 
 	<procedure>
 	  <title>Using &windows; to Write the Image</title>
 
 	  <warning>
 	    <para>Be sure to give the correct drive letter as the
 	      existing data on the specified drive will be overwritten
 	      and destroyed.</para>
 	  </warning>
 
 	  <step>
 	    <title>Obtaining <application>Image Writer for
 		&windows;</application></title>
 
 	    <para><application>Image Writer for
 		&windows;</application> is a free application that can
 	      correctly write an image file to a memory stick.
 	      Download it from <uri
 		xlink:href="https://sourceforge.net/projects/win32diskimager/">https://sourceforge.net/projects/win32diskimager/</uri>
 	      and extract it into a folder.</para>
 	  </step>
 
 	  <step>
 	    <title>Writing the Image with Image Writer</title>
 
 	    <para>Double-click the
 	      <application>Win32DiskImager</application> icon to start
 	      the program.  Verify that the drive letter shown under
 	      <computeroutput>Device</computeroutput> is the drive
 	      with the memory stick.  Click the folder icon and select
 	      the image to be written to the memory stick.  Click
 	      <guibutton>[&nbsp;Save&nbsp;]</guibutton> to accept the
 	      image file name.  Verify that everything is correct, and
 	      that no folders on the memory stick are open in other
 	      windows.  When everything is ready, click
 	      <guibutton>[&nbsp;Write&nbsp;]</guibutton> to write the
 	      image file to the memory stick.</para>
 	  </step>
 	</procedure>
 
 	<para>You are now ready to start installing &os;.</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 xml:id="bsdinstall-start">
     <title>Starting the Installation</title>
 
     <important>
       <para>By default, the installation will not make any changes to
 	the disk(s) before the following message:</para>
 
       <programlisting>Your changes will now be written to disk. If you
 have chosen to overwrite existing data, it will
 be PERMANENTLY ERASED. Are you sure you want to
 commit your changes?</programlisting>
 
       <para>The install can be exited at any time prior to this
 	warning.  If
 	there is a concern that something is incorrectly configured,
 	just turn the computer off before this point and no changes
 	will be made to the system's disks.</para>
     </important>
 
     <para>This section describes how to boot the system from the
       installation media which was prepared using the instructions in
       <xref linkend="bsdinstall-installation-media"/>.  When using a
       bootable USB stick, plug in the <acronym>USB</acronym> stick
       before turning on the computer.  When booting from
       <acronym>CD</acronym> or <acronym>DVD</acronym>, turn on the
       computer and insert the media at the first opportunity.  How to
       configure the system to boot from the inserted media depends
       upon the architecture.</para>
 
     <sect2 xml:id="bsdinstall-starting-i386">
       <title>Booting on &i386; and &arch.amd64;</title>
 
       <para>These architectures provide a <acronym>BIOS</acronym>
 	menu for selecting the boot device.  Depending upon the
 	installation media being used, select the
 	<acronym>CD</acronym>/<acronym>DVD</acronym> or
 	<acronym>USB</acronym> device as the first boot device.  Most
 	systems also provide a key for selecting the boot device
 	during startup without having to enter the
 	<acronym>BIOS</acronym>.  Typically, the key is either
 	<keycap>F10</keycap>, <keycap>F11</keycap>,
 	<keycap>F12</keycap>, or <keycap>Escape</keycap>.</para>
 
       <para>If the computer loads the existing operating system
 	instead of the &os; installer, then either:</para>
 
       <orderedlist>
 	<listitem>
 	  <para>The installation media was not inserted early enough
 	    in the boot process.  Leave the media inserted and try
 	    restarting the computer.</para>
 	</listitem>
 
 	<listitem>
 	  <para>The <acronym>BIOS</acronym> changes were incorrect or
 	    not saved.  Double-check that the right boot device is
 	    selected as the first boot device.</para>
 	</listitem>
 
 	<listitem>
 	  <para>This system is too old to support booting from the
 	    chosen media.  In this case, the <application>Plop Boot
 	      Manager</application> (<link
 	      xlink:href="http://www.plop.at/en/bootmanagers.html" />)
 	    can be used to boot the system from the selected
 	    media.</para>
 	</listitem>
       </orderedlist>
     </sect2>
 
     <sect2>
       <title>Booting on &powerpc;</title>
 
       <para>On most machines, holding <keycap>C</keycap> on the
 	keyboard during boot will boot from the <acronym>CD</acronym>.
 	Otherwise, hold <keycombo action="simul">
 	  <keycap>Command</keycap>
 	  <keycap>Option</keycap>
 	  <keycap>O</keycap>
 	  <keycap>F</keycap>
 	</keycombo>, or
 	<keycombo action="simul">
 	  <keycap>Windows</keycap>
 	  <keycap>Alt</keycap>
 	  <keycap>O</keycap>
 	  <keycap>F</keycap>
 	</keycombo> on non-&apple; keyboards.  At the
 	<prompt>0 &gt;</prompt> prompt, enter</para>
 
       <screen><userinput>boot cd:,\ppc\loader cd:0</userinput></screen>
     </sect2>
 
     <sect2 xml:id="bsdinstall-view-probe">
       <title>&os; Boot Menu</title>
 
       <para>Once the system boots from the installation media, a menu
 	similar to the following will be displayed:</para>
 
       <figure xml:id="bsdinstall-newboot-loader-menu">
 	<title>&os; Boot Loader Menu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-newboot-loader-menu"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>By default, the menu will wait ten seconds for user input
 	before booting into the &os; installer or, if &os; is already
 	installed, before booting into &os;.  To pause the boot timer
 	in order to review the selections, press
 	<keycap>Space</keycap>.  To select an option, press its
 	highlighted number, character, or key.  The following options
 	are available.</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>Boot Multi User</literal>: This will
 	    continue the &os; boot process.  If the boot timer has
 	    been paused, press <keycap>1</keycap>, upper- or
 	    lower-case <keycap>B</keycap>, or
 	    <keycap>Enter</keycap>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Boot Single User</literal>: This mode can be
 	    used to fix an existing &os; installation as described in
 	    <xref linkend="boot-singleuser"/>.  Press
 	    <keycap>2</keycap> or the upper- or lower-case
 	    <keycap>S</keycap> to enter this mode.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Escape to loader prompt</literal>: This will
 	    boot the system into a repair prompt that contains a
 	    limited number of low-level commands.  This prompt is
 	    described in <xref linkend="boot-loader"/>.  Press
 	    <keycap>3</keycap> or <keycap>Esc</keycap> to boot into
 	    this prompt.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Reboot</literal>: Reboots the system.</para>
 	</listitem>
 
         <listitem>
           <para><literal>Kernel</literal>: Loads a different
             kernel.</para>
         </listitem>
 
 	<listitem>
 	  <para><literal>Configure Boot Options</literal>: Opens the
 	    menu shown in, and described under, <xref
 	      linkend="bsdinstall-boot-options-menu"/>.</para>
 	</listitem>
       </itemizedlist>
 
       <figure xml:id="bsdinstall-boot-options-menu">
 	<title>&os; Boot Options Menu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-boot-options-menu"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The boot options menu is divided into two sections.  The
 	first section can be used to either return to the main boot
 	menu or to reset any toggled options back to their
 	defaults.</para>
 
       <para>The next section is used to toggle the available options
 	to <literal>On</literal> or <literal>Off</literal> by pressing
 	the option's highlighted number or character.  The system will
 	always boot using the settings for these options until they
 	are modified.  Several options can be toggled using this
 	menu:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>ACPI Support</literal>: If the system hangs
 	    during boot, try toggling this option to
 	    <literal>Off</literal>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Safe Mode</literal>: If the system still
 	    hangs during boot even with <literal>ACPI
 	      Support</literal> set to <literal>Off</literal>, try
 	    setting this option to <literal>On</literal>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Single User</literal>: Toggle this option to
 	    <literal>On</literal> to fix an existing &os; installation
 	    as described in <xref linkend="boot-singleuser"/>.  Once
 	    the problem is fixed, set it back to
 	    <literal>Off</literal>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Verbose</literal>: Toggle this option to
 	    <literal>On</literal> to see more detailed messages during
 	    the boot process.  This can be useful when troubleshooting
 	    a piece of hardware.</para>
 	</listitem>
       </itemizedlist>
 
       <para>After making the needed selections, press
 	<keycap>1</keycap> or <keycap>Backspace</keycap> to return to
 	the main boot menu, then press <keycap>Enter</keycap> to
 	continue booting into &os;.  A series of boot messages will
 	appear as &os; carries out its hardware device probes and
 	loads the installation program.  Once the boot is complete,
 	the welcome menu shown in <xref
 	  linkend="bsdinstall-choose-mode"/> will be displayed.</para>
 
       <figure xml:id="bsdinstall-choose-mode">
 	<title>Welcome Menu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-choose-mode"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Press <keycap>Enter</keycap> to select the default of
 	<guibutton>[&nbsp;Install&nbsp;]</guibutton> to enter the
 	installer.  The rest of this chapter describes how to use this
 	installer.  Otherwise, use the right or left arrows or the
 	colorized letter to select the desired menu item.  The
 	<guibutton>[&nbsp;Shell&nbsp;]</guibutton> can be used to
 	access a &os; shell in order to use command line utilities to
 	prepare the disks before installation.  The
 	<guibutton>[&nbsp;Live CD&nbsp;]</guibutton> option can be
 	used to try out &os; before installing it.  The live version
 	is described in <xref linkend="using-live-cd"/>.</para>
 
       <tip>
 	<para>To review the boot messages, including the hardware
 	  device probe, press the upper- or lower-case
 	  <keycap>S</keycap> and then <keycap>Enter</keycap> to access
 	  a shell.  At the shell prompt, type <command>more
 	    /var/run/dmesg.boot</command> and use the space bar to
 	  scroll through the messages.  When finished, type
 	  <command>exit</command> to return to the welcome
 	  menu.</para>
       </tip>
     </sect2>
   </sect1>
 
   <sect1 xml:id="using-bsdinstall">
     <title>Using <application>bsdinstall</application></title>
 
     <para>This section shows the order of the
       <application>bsdinstall</application> menus and the type of
       information that will be asked before the system is installed.
       Use the arrow keys to highlight a menu option, then
       <keycap>Space</keycap> to select or deselect that menu item.
       When finished, press <keycap>Enter</keycap> to save the
       selection and move onto the next screen.</para>
 
     <sect2 xml:id="bsdinstall-keymap">
       <title>Selecting the Keymap Menu</title>
 
       <para>Before starting the process,
 	<application>bsdinstall</application> will load the keymap
 	files as show in <xref
 	  linkend="bsdinstall-keymap-loading"/>.</para>
 
       <figure xml:id="bsdinstall-keymap-loading">
 	<title>Keymap Loading</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-keymap-loading"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>After the keymaps have been loaded
 	<application>bsdinstall</application> displays the
 	menu shown in <xref linkend="bsdinstall-keymap-10"/>.  Use the
 	up and down arrows to select the keymap that most closely
 	represents the mapping of the keyboard attached to the system.
 	Press <keycap>Enter</keycap> to save the selection.</para>
 
       <figure xml:id="bsdinstall-keymap-10">
 	<title>Keymap Selection Menu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-keymap-10"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <note><para>Pressing <keycap>Esc</keycap> will exit this menu
 	and use the default keymap.  If the choice of keymap is not
 	clear, <guimenuitem>United States of America
 	ISO-8859-1</guimenuitem> is also a safe option.</para></note>
 
       <para>In addition, when selecting a different keymap, the user
 	can try the keymap and ensure it is correct before proceeding
 	as shown in <xref linkend="bsdinstall-keymap-testing"/>.</para>
 
       <figure xml:id="bsdinstall-keymap-testing">
 	<title>Keymap Testing Menu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-keymap-testing"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
     </sect2>
 
     <sect2 xml:id="bsdinstall-hostname">
       <title>Setting the Hostname</title>
 
       <para>The next <application>bsdinstall</application> menu is
 	used to set the hostname for the newly installed
 	system.</para>
 
       <figure xml:id="bsdinstall-config-hostname">
 	<title>Setting the Hostname</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-config-hostname"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Type in a hostname that is unique for the network.  It
 	should be a fully-qualified hostname, such as <systemitem
 	  class="fqdomainname">machine3.example.com</systemitem>.</para>
     </sect2>
 
     <sect2 xml:id="bsdinstall-components">
       <title>Selecting Components to Install</title>
 
       <para>Next, <application>bsdinstall</application> will prompt to
 	select optional components to install.</para>
 
       <figure xml:id="bsdinstall-config-components">
 	<title>Selecting Components to Install</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-config-components"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Deciding which components to install will depend largely
 	on the intended use of the system and the amount of disk space
 	available.  The &os; kernel and userland, collectively known
 	as the <firstterm>base system</firstterm>, are always
 	installed.  Depending on the architecture, some of these
 	components may not appear:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>base-dbg</literal> - Base tools like
 	    <application>cat</application>,
 	    <application>ls</application> among many others with
 	    debug symbols activated.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>kernel-dbg</literal> - Kernel and modules with
 	    debug symbols activated.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>lib32-dbg</literal> - Compatibility libraries
 	    for running 32-bit applications on a 64-bit version of
 	    &os; with debug symbols activated.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>lib32</literal> - Compatibility libraries for
 	    running 32-bit applications on a 64-bit version of
 	    &os;.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>ports</literal> - The &os; Ports Collection
 	    is a collection of files which automates the downloading,
 	    compiling and installation of third-party software
 	    packages.  <xref linkend="ports"/> discusses how to use
 	    the Ports Collection.</para>
 
 	  <warning>
 	    <para>The installation program does not check for
 	      adequate disk space.  Select this option only if
 	      sufficient hard disk space is available.  The &os; Ports
 	      Collection takes up about &ports.size; of disk
 	      space.</para>
 	  </warning>
 	</listitem>
 
 	<listitem>
 	  <para><literal>src</literal> - The complete &os; source code
 	    for both the kernel and the userland.  Although not
 	    required for the majority of applications, it may be
 	    required to build device drivers, kernel modules, or some
 	    applications from the Ports Collection.  It is also used
 	    for developing &os; itself.  The full source tree requires
 	    1&nbsp;GB of disk space and recompiling the entire &os;
 	    system requires an additional 5&nbsp;GB of space.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>tests</literal> - &os; Test Suite.</para>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2 xml:id="bsdinstall-netinstall">
       <title>Installing from the Network</title>
 
       <para>The menu shown in
 	<xref linkend="bsdinstall-netinstall-notify"/> only appears
 	when installing from a <filename>-bootonly.iso</filename> or
 	<filename>-mini-memstick.img</filename> as this installation
 	media does not hold copies of the installation files.
 	Since the installation files must be retrieved over a network
 	connection, this menu indicates that the network interface must
 	be configured first.  If this menu is shown in any step of the
 	process remember to follow the instructions in
 	<xref linkend="bsdinstall-config-network-dev"/>.</para>
 
       <figure xml:id="bsdinstall-netinstall-notify">
 	<title>Installing from the Network</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-netinstall-files"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 xml:id="bsdinstall-partitioning">
     <title>Allocating Disk Space</title>
 
     <para>The next menu is used to determine the method for
       allocating disk space.</para>
 
     <figure xml:id="bsdinstall-zfs-partmenu">
       <title>Partitioning Choices</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="bsdinstall/bsdinstall-zfs-partmenu"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
     <para><application>bsdinstall</application> gives the user four
       methods for allocating disk space:</para>
 
     <itemizedlist>
       <listitem>
 	<para><literal>Auto (UFS)</literal> partitioning
 	  automatically sets up the disk partitions using the
 	  <literal>UFS</literal> file system.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Manual</literal> partitioning allows
 	  advanced users to create customized partitions from menu
 	  options.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Shell</literal> opens a shell prompt where
 	  advanced users can create customized partitions using
 	  command-line utilities like &man.gpart.8;, &man.fdisk.8;,
 	  and &man.bsdlabel.8;.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Auto (ZFS)</literal> partitioning creates a
 	  root-on-ZFS system with optional GELI encryption support for
 	  <firstterm>boot environments</firstterm>.</para>
       </listitem>
     </itemizedlist>
 
     <para>This section describes what to consider when laying out the
       disk partitions.  It then demonstrates how to use the different
       partitioning methods.</para>
 
     <sect2 xml:id="configtuning-initial">
       <title>Designing the Partition Layout</title>
 
       <indexterm><primary>partition layout</primary></indexterm>
       <indexterm>
 	<primary><filename>/etc</filename></primary>
       </indexterm>
       <indexterm>
 	<primary><filename>/var</filename></primary>
       </indexterm>
       <indexterm>
 	<primary><filename>/usr</filename></primary>
       </indexterm>
 
       <para>When laying out file systems, remember that hard drives
 	transfer data faster from the outer tracks to the inner.
 	Thus, smaller and heavier-accessed file systems should be
 	closer to the outside of the drive, while larger partitions
 	like <filename>/usr</filename> should be placed toward the
 	inner parts of the disk.  It is a good idea to create
 	partitions in an order similar to: <filename>/</filename>,
 	swap, <filename>/var</filename>, and
 	<filename>/usr</filename>.</para>
 
       <para>The size of the <filename>/var</filename> partition
 	reflects the intended machine's usage.  This partition is
 	used to hold mailboxes, log files, and printer spools.
 	Mailboxes and log files can grow to unexpected sizes
 	depending on the number of users and how long log files are
 	kept.  On average, most users rarely need more than about a
 	gigabyte of free disk space in
 	<filename>/var</filename>.</para>
 
       <note>
 	<para>Sometimes, a lot of disk space is required in
 	  <filename>/var/tmp</filename>.  When new software is
 	  installed, the packaging tools extract a temporary copy of
 	  the packages under <filename>/var/tmp</filename>.  Large
 	  software packages, like <application>Firefox</application>
 	  or <application>LibreOffice</application> may be tricky to
 	  install if there is not enough disk space under
 	  <filename>/var/tmp</filename>.</para>
       </note>
 
       <para>The <filename>/usr</filename> partition holds many of the
 	files which support the system, including the &os; Ports
 	Collection and system source code.  At least 2 gigabytes of
 	space is recommended for this partition.</para>
 
       <para>When selecting partition sizes, keep the space
 	requirements in mind.  Running out of space in one partition
 	while barely using another can be a hassle.</para>
 
       <indexterm>
 	<primary>swap sizing</primary>
       </indexterm>
       <indexterm>
 	<primary>swap partition</primary>
       </indexterm>
 
       <para>As a rule of thumb, the swap partition should be about
 	double the size of physical memory (<acronym>RAM</acronym>).
 	Systems with minimal <acronym>RAM</acronym> may perform
 	better with more swap.  Configuring too little swap can lead
 	to inefficiencies in the <acronym>VM</acronym> page scanning
 	code and might create issues later if more memory is
 	added.</para>
 
       <para>On larger systems with multiple <acronym>SCSI</acronym>
 	disks or multiple <acronym>IDE</acronym> disks operating on
 	different controllers, it is recommended that swap be
 	configured on each drive, up to four drives.  The swap
 	partitions should be approximately the same size.  The
 	kernel can handle arbitrary sizes but internal data structures
 	scale to 4 times the largest swap partition.  Keeping the swap
 	partitions near the same size will allow the kernel to
 	optimally stripe swap space across disks.  Large swap sizes
 	are fine, even if swap is not used much.  It might be easier
 	to recover from a runaway program before being forced to
 	reboot.</para>
 
       <para>By properly partitioning a system, fragmentation
 	introduced in the smaller write heavy partitions will not
 	bleed over into the mostly read partitions.  Keeping the
 	write loaded partitions closer to the disk's edge will
 	increase <acronym>I/O</acronym> performance in the
 	partitions where it occurs the most.  While
 	<acronym>I/O</acronym> performance in the larger partitions
 	may be needed, shifting them more toward the edge of the disk
 	will not lead to a significant performance improvement over
 	moving <filename>/var</filename> to the edge.</para>
     </sect2>
 
     <sect2 xml:id="bsdinstall-part-guided">
       <title>Guided Partitioning Using UFS</title>
 
       <para>When this method is selected, a menu will display the
 	available disk(s).  If multiple disks are connected, choose
 	the one where &os; is to be installed.</para>
 
       <figure xml:id="bsdinstall-part-guided-disk">
 	<title>Selecting from Multiple Disks</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-part-guided-disk"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Once the disk is selected, the next menu prompts to
 	install to either the entire disk or to create a partition
 	using free space.  If
 	<guibutton>[&nbsp;Entire&nbsp;Disk&nbsp;]</guibutton> is
 	chosen, a general partition layout filling the whole disk is
 	automatically created.  Selecting
 	<guibutton>[&nbsp;Partition&nbsp;]</guibutton> creates a
 	partition layout from the unused space on the disk.</para>
 
       <figure xml:id="bsdinstall-part-entire-part">
 	<title>Selecting Entire Disk or Partition</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-part-entire-part"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>After
 	<guibutton>[&nbsp;Entire&nbsp;Disk&nbsp;]</guibutton> is
 	chosen <application>bsdinstall</application> displays a
 	dialog indicating that the disk will be erased.</para>
 
       <figure xml:id="bsdinstall-ufs-warning">
 	<title>Confirmation</title>
 
         <mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-ufs-warning"/>
 	  </imageobject>
         </mediaobject>
       </figure>
 
       <para>The next menu shows a list with the partition schemes
 	types.  GPT is usually the most appropriate choice for amd64
 	computers.  Older computers that are not compatible with GPT
 	should use MBR.  The other partition schemes are generally
 	used for uncommon or older computers.  More information is
 	available in <xref linkend="partition-schemes"/>.</para>
 
       <figure xml:id="bsdinstall-ufs-scheme">
 	<title>Select Partition Scheme</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-part-manual-partscheme"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>After the partition layout has been created, review it to
 	ensure it meets the needs of the installation.  Selecting
 	<guibutton>[&nbsp;Revert&nbsp;]</guibutton> will reset the
 	partitions to their original values and pressing
 	<guibutton>[&nbsp;Auto&nbsp;]</guibutton> will recreate the
 	automatic &os; partitions.  Partitions can also be manually
 	created, modified, or deleted.  When the partitioning is
 	correct, select <guibutton>[&nbsp;Finish&nbsp;]</guibutton> to
 	continue with the installation.</para>
 
       <figure xml:id="bsdinstall-part-review">
 	<title>Review Created Partitions</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-part-review"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Once the disks are configured, the next menu provides the
 	last chance to make changes before the selected drives are
 	formatted.  If changes need to be made, select
 	<guibutton>[&nbsp;Back&nbsp;]</guibutton> to return to the
 	main partitioning menu.
       	<guibutton>[&nbsp;Revert&nbsp;&amp;&nbsp;Exit&nbsp;]</guibutton>
 	exits the installer without making any changes to the drive.
 	Select <guibutton>[&nbsp;Commit&nbsp;]</guibutton> to start
 	the installation process.</para>
 
       <figure xml:id="bsdinstall-ufs-final-confirmation">
 	<title>Final Confirmation</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-final-confirmation"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
     <para>To continue with the installation process go to
       <xref linkend="bsdinstall-fetching-distribution"/>.</para>
     </sect2>
 
     <sect2 xml:id="bsdinstall-part-manual">
       <title>Manual Partitioning</title>
 
       <para>Selecting this method opens the partition editor:</para>
 
       <figure xml:id="bsdinstall-part-manual-create">
 	<title>Manually Create Partitions</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-part-manual-create"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Highlight the installation drive
 	(<filename>ada0</filename> in this example) and select
 	<guibutton>[&nbsp;Create&nbsp;]</guibutton> to display a menu
 	of available partition schemes:</para>
 
       <figure xml:id="bsdinstall-part-manual-partscheme">
 	<title>Manually Create Partitions</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-part-manual-partscheme"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para><acronym>GPT</acronym> is usually the most appropriate
 	choice for &arch.amd64; computers.  Older computers that are
 	not compatible with <acronym>GPT</acronym> should use
 	<acronym>MBR</acronym>.  The other partition schemes are
 	generally used for uncommon or older computers.</para>
 
       <table xml:id="partition-schemes" frame="none" rowsep="1" pgwide="1">
 	<title>Partitioning Schemes</title>
 
 	<tgroup cols="2" align="left">
 	  <thead>
 	    <row>
 	      <entry align="left">Abbreviation</entry>
 	      <entry align="left">Description</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>APM</entry>
 	      <entry>Apple Partition Map, used by &powerpc;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>BSD</entry>
 	      <entry><acronym>BSD</acronym> label without an
 		<acronym>MBR</acronym>, sometimes called
 		<firstterm>dangerously dedicated mode</firstterm> as
 		non-<acronym>BSD</acronym> disk utilities may not
 		recognize it.</entry>
 	    </row>
 
 	    <row>
 	      <entry>GPT</entry>
 	      <entry>GUID Partition Table (<link
 		  xlink:href="http://en.wikipedia.org/wiki/GUID_Partition_Table">http://en.wikipedia.org/wiki/GUID_Partition_Table</link>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>MBR</entry>
 	      <entry>Master Boot Record (<link
 		  xlink:href="http://en.wikipedia.org/wiki/Master_boot_record">http://en.wikipedia.org/wiki/Master_boot_record</link>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>VTOC8</entry>
 	      <entry>Volume Table Of Contents used by Sun SPARC64 and
 		UltraSPARC computers.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>After the partitioning scheme has been selected and
 	created, select <guibutton>[&nbsp;Create&nbsp;]</guibutton>
 	again to create the partitions.  The <keycap>Tab</keycap>
 	key is used to move the cursor between fields.</para>
 
       <figure xml:id="bsdinstall-part-manual-addpart">
 	<title>Manually Create Partitions</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-part-manual-addpart"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A standard &os; <acronym>GPT</acronym> installation uses
 	at least three partitions:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>freebsd-boot</literal> - Holds the &os; boot
 	    code.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>freebsd-ufs</literal> - A &os;
 	    <acronym>UFS</acronym> file system.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>freebsd-zfs</literal> - A &os;
 	    <acronym>ZFS</acronym> file system.  More information about
 	    ZFS is available in <xref linkend="zfs"/>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>freebsd-swap</literal> - &os; swap
 	    space.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Refer to &man.gpart.8; for descriptions of the available
 	<acronym>GPT</acronym> partition types.</para>
 
       <para>Multiple file system partitions can be created and some
 	people prefer a traditional layout with separate partitions
 	for <filename>/</filename>, <filename>/var</filename>,
 	<filename>/tmp</filename>, and <filename>/usr</filename>.  See
 	<xref linkend="bsdinstall-part-manual-splitfs"/> for an
 	example.</para>
 
       <para>The <literal>Size</literal> may be entered with common
 	abbreviations: <emphasis>K</emphasis> for kilobytes,
 	<emphasis>M</emphasis> for megabytes, or
 	<emphasis>G</emphasis> for gigabytes.</para>
 
       <tip>
 	<para>Proper sector alignment provides the best performance,
 	  and making partition sizes even multiples of 4K bytes helps
 	  to ensure alignment on drives with either 512-byte or
 	  4K-byte sectors.  Generally, using partition sizes that are
 	  even multiples of 1M or 1G is the easiest way to make sure
 	  every partition starts at an even multiple of 4K.  There is
 	  one exception: the <emphasis>freebsd-boot</emphasis>
 	  partition should be no larger than 512K due to current boot
 	  code limitations.</para>
       </tip>
 
       <para>A <literal>Mountpoint</literal> is needed if the partition
 	will contain a file system.  If only a single
 	<acronym>UFS</acronym> partition will be created, the
 	mountpoint should be <filename>/</filename>.</para>
 
       <para>The <literal>Label</literal> is a name by which the
 	partition will be known.  Drive names or numbers can change if
 	the drive is connected to a different controller or port, but
 	the partition label does not change.  Referring to labels
 	instead of drive names and partition numbers in files like
 	<filename>/etc/fstab</filename> makes the system more tolerant
 	to hardware changes.  <acronym>GPT</acronym> labels appear in
 	<filename>/dev/gpt/</filename> when a disk is attached.  Other
 	partitioning schemes have different label capabilities and
 	their labels appear in different directories in
 	<filename>/dev/</filename>.</para>
 
       <tip>
 	<para>Use a unique label on every partition to avoid
 	  conflicts from identical labels.  A few letters from the
 	  computer's name, use, or location can be added to the label.
 	  For instance, use <literal>labroot</literal> or
 	  <literal>rootfslab</literal> for the <acronym>UFS</acronym>
 	  root partition on the computer named
 	  <literal>lab</literal>.</para>
       </tip>
 
       <example xml:id="bsdinstall-part-manual-splitfs">
 	<title>Creating Traditional Split File System
 	  Partitions</title>
 
 	<para>For a traditional partition layout where the
 	  <filename>/</filename>, <filename>/var</filename>,
 	  <filename>/tmp</filename>, and <filename>/usr</filename>
 	  directories are separate file systems on their own
 	  partitions, create a <acronym>GPT</acronym> partitioning
 	  scheme, then create the partitions as shown.  Partition
 	  sizes shown are typical for a 20G target disk.  If more
 	  space is available on the target disk, larger swap or
 	  <filename>/var</filename> partitions may be useful.  Labels
 	  shown here are prefixed with <literal>ex</literal> for
 	  <quote>example</quote>, but readers should use other unique
 	  label values as described above.</para>
 
 	<para>By default, &os;'s <filename>gptboot</filename> expects
 	  the first <acronym>UFS</acronym> partition to be the
 	  <filename>/</filename> partition.</para>
 
 	<informaltable frame="none">
 	  <tgroup cols="4">
 	    <thead>
 	      <row>
 		<entry>Partition Type</entry>
 		<entry>Size</entry>
 		<entry>Mountpoint</entry>
 		<entry>Label</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>freebsd-boot</literal></entry>
 		<entry><literal>512K</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>freebsd-ufs</literal></entry>
 		<entry><literal>2G</literal></entry>
 		<entry><filename>/</filename></entry>
 		<entry><literal>exrootfs</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>freebsd-swap</literal></entry>
 		<entry><literal>4G</literal></entry>
 		<entry></entry>
 		<entry><literal>exswap</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>freebsd-ufs</literal></entry>
 		<entry><literal>2G</literal></entry>
 		<entry><filename>/var</filename></entry>
 		<entry><literal>exvarfs</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>freebsd-ufs</literal></entry>
 		<entry><literal>1G</literal></entry>
 		<entry><filename>/tmp</filename></entry>
 		<entry><literal>extmpfs</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>freebsd-ufs</literal></entry>
 		<entry>accept the default (remainder of the
 		  disk)</entry>
 		<entry><filename>/usr</filename></entry>
 		<entry><literal>exusrfs</literal></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
       </example>
 
       <para>After the custom partitions have been created, select
 	<guibutton>[&nbsp;Finish&nbsp;]</guibutton> to continue with
 	the installation and go to
 	<xref linkend="bsdinstall-fetching-distribution"/>.</para>
     </sect2>
 
     <sect2 xml:id="bsdinstall-part-zfs">
       <title>Guided Partitioning Using Root-on-ZFS</title>
 
       <para>This partitioning mode only works with whole disks and
 	will erase the contents of the entire disk.  The main
 	<acronym>ZFS</acronym> configuration menu offers a number of
 	options to control the creation of the pool.</para>
 
       <figure xml:id="bsdinstall-zfs-menu">
 	<title><acronym>ZFS</acronym> Partitioning Menu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-zfs-menu"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Here is a summary of the options which can be used in
 	this menu:</para>
 
     <itemizedlist>
       <listitem>
 	<para><literal>Install</literal> - Proceed with the
 	  installation with the selected options.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Pool Type/Disks</literal> - Allow to configure
 	  the <literal>Pool Type</literal> and the disk(s) that will
 	  constitute the pool.  The automatic <acronym>ZFS</acronym>
 	  installer currently only supports the creation of a single top
 	  level vdev, except in stripe mode.  To create more complex
 	  pools, use the instructions in <xref linkend="bsdinstall-part-shell"/>
 	  to create the pool.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Rescan Devices</literal> - Repopulate the list
 	  of available disks.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Disk Info</literal> - Disk Info menu can be
 	  used to inspect each disk, including its partition table and
 	  various other information such as the device model number
 	  and serial number, if available.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Pool Name</literal> - Establish the name of the
 	  pool.  The default name is
 	  <emphasis>zroot</emphasis>.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Force 4K Sectors?</literal> - Force the use of
 	  4K sectors.  By default, the installer will automatically
 	  create partitions aligned to 4K boundaries and force ZFS to
 	  use 4K sectors.  This is safe even with 512 byte sector
 	  disks, and has the added benefit of ensuring that pools
 	  created on 512 byte disks will be able to have 4K sector
 	  disks added in the future, either as additional storage
 	  space or as replacements for failed disks.  Press the
 	  <keycap>Enter</keycap> key to chose to activate it or
 	  not.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Encrypt Disks?</literal> - Encrypting the disks
 	  allows the user to encrypt the disks using
 	  <acronym>GELI</acronym>.  More information about disk
 	  encryption is available in <xref linkend="disks-encrypting-geli"/>.
 	  Press the <keycap>Enter</keycap> key to chose activate it or
 	  not.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Partition Scheme</literal> - Allow to choose
 	  the partition scheme.  GPT is the recommended option in
 	  most cases.  Press the <keycap>Enter</keycap> key to chose
 	  between the different options.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Swap Size</literal> - Establish the amount of
 	  swap space.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Mirror Swap?</literal> - Allows the user to
 	  mirror the swap between the disks.  Be aware, enabling
 	  mirror swap will break crash dumps.  Press the
 	  <keycap>Enter</keycap> key to activate it or not.</para>
       </listitem>
 
       <listitem>
 	<para><literal>Encrypt Swap?</literal> - Allow the user the
 	  possibility to encrypt the swap.  Encrypts the swap with a
 	  temporary key each time that the system boots and discards
 	  it on reboot.  Press the <keycap>Enter</keycap> key to chose
 	  activate it or not.  More information about swap encryption
 	  in <xref linkend="swap-encrypting"/>.</para>
       </listitem>
     </itemizedlist>
 
       <para>Select <keycap>T</keycap> to configure the <literal>Pool
 	Type</literal> and the disk(s) that will constitute the
 	pool.</para>
 
       <figure xml:id="bsdinstall-zfs-vdev_type">
 	<title><acronym>ZFS</acronym> Pool Type</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-zfs-vdev_type"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Here is a summary of the <literal>Pool Type</literal>
 	which can be selected in this menu:</para>
 
     <itemizedlist>
       <listitem>
 	<para><literal>stripe</literal> - Striping provides maximum
 	  storage of all connected devices, but no redundancy.  If
 	  just one disk fails the data on the pool is lost
 	  irrevocably.</para>
       </listitem>
       <listitem>
 	<para><literal>mirror</literal> - Mirroring stores a complete
 	  copy of all data on every disk.  Mirroring provides a good
 	  read perfomance because data is read from all disks in
 	  parallel.  Write performance is slower as the data must be
 	  written to all disks in the pool.  Allows all but one disk
 	  to fail.  This option requires at least two disks.</para>
       </listitem>
       <listitem>
 	<para><literal>raid10</literal> - Striped mirrors.  Provides
 	  the best performance, but the least storage.  This option
 	  needs at least an even number of disks and a minimum of four
 	  disks.</para>
       </listitem>
       <listitem>
 	<para><literal>raidz1</literal> - Single Redundant RAID.
 	  Allow one disk to fail concurrently.  This option needs at
 	  least three disks.</para>
       </listitem>
       <listitem>
 	<para><literal>raidz2</literal> - Double Redundant RAID.
 	  Allows two disks to fail concurrently.  This option needs
 	  at least four disks.</para>
       </listitem>
       <listitem>
 	<para><literal>raidz3</literal> - Triple Redundant RAID.
 	  Allows three disks to fail concurrently.  This option needs
 	  at least five disks.</para>
       </listitem>
     </itemizedlist>
 
       <para>Once a <literal>Pool Type</literal> has been selected, a
 	list of available disks is displayed, and the user is prompted
 	to select one or more disks to make up the pool.  The
 	configuration is then validated, to ensure enough disks are
 	selected.  If not, select <guibutton>&lt;Change
 	Selection&gt;</guibutton> to return to the list of disks, or
 	<guibutton>&lt;Back&gt;</guibutton> to change the
 	<literal>Pool Type</literal>.</para>
 
       <figure xml:id="bsdinstall-zfs-disk_select">
 	<title>Disk Selection</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-zfs-disk_select"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <figure xml:id="bsdinstall-zfs-vdev_invalid">
 	<title>Invalid Selection</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-zfs-vdev_invalid"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If one or more disks are missing from the list, or if
 	disks were attached after the installer was started, select
 	<guibutton>- Rescan Devices</guibutton> to repopulate the list
 	of available disks.</para>
 
       <figure xml:id="bsdinstall-zfs-rescan-devices">
 	<title>Rescan Devices</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-zfs-rescan-devices"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>To avoid accidentally erasing the wrong disk, the
 	<guibutton>- Disk Info</guibutton> menu can be used to inspect
 	each disk, including its partition table and various other
 	information such as the device model number and serial number,
 	if available.</para>
 
       <figure xml:id="bsdinstall-zfs-disk_info">
 	<title>Analyzing a Disk</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-zfs-disk_info"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Select <keycap>N</keycap> to configure the
 	<literal>Pool Name</literal>.  Enter the desired name then
 	select <guibutton>&lt;OK&gt;</guibutton> to establish it or
 	<guibutton>&lt;Cancel&gt;</guibutton> to return to the
 	main menu and leave the default name.</para>
 
       <figure xml:id="bsdinstall-zfs-pool-name">
 	<title>Pool Name</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-zfs-pool-name"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Select <keycap>S</keycap> to set the amount of
 	swap.  Enter the desired amount of swap and then select
 	<guibutton>&lt;OK&gt;</guibutton> to establish it or
 	<guibutton>&lt;Cancel&gt;</guibutton> to return to the
 	main menu and let the default amount.</para>
 
       <figure xml:id="bsdinstall-zfs-swap-amount">
 	<title>Swap Amount</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-zfs-swap-amount"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Once all options have been set to the desired values,
 	select the <guibutton>&gt;&gt;&gt;&nbsp;Install</guibutton>
 	option at the top of the menu.  The installer then offers a
 	last chance to cancel before the contents of the selected
 	drives are destroyed to create the <acronym>ZFS</acronym>
 	pool.</para>
 
       <figure xml:id="bsdinstall-zfs-warning">
 	<title>Last Chance</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-zfs-warning"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If <acronym>GELI</acronym> disk encryption was enabled,
 	the installer will prompt twice for the passphrase to be used
 	to encrypt the disks.  And after that the initializing of the
 	encryption begins.</para>
 
       <figure xml:id="bsdinstall-zfs-geli_password">
 	<title>Disk Encryption Password</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-zfs-geli_password"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <figure xml:id="bsdinstall-zfs-init-encription">
 	<title>Initializing Encryption</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-zfs-init-encription"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The installation then proceeds normally.  To continue
 	with the installation go to
 	<xref linkend="bsdinstall-fetching-distribution"/>.</para>
 
     </sect2>
 
     <sect2 xml:id="bsdinstall-part-shell">
       <title>Shell Mode Partitioning</title>
 
       <para>When creating advanced installations, the
 	<application>bsdinstall</application> partitioning menus may
 	not provide the level of flexibility required.  Advanced users
 	can select the <guibutton>Shell</guibutton> option from the
 	partitioning menu in order to manually partition the drives,
 	create the file system(s), populate
 	<filename>/tmp/bsdinstall_etc/fstab</filename>, and mount the
 	file systems under <filename>/mnt</filename>.  Once this is
 	done, type <command>exit</command> to return to
 	<application>bsdinstall</application> and continue the
 	installation.</para>
     </sect2>
   </sect1>
 
   <sect1 xml:id="bsdinstall-fetching-distribution">
     <title>Fetching Distribution Files</title>
 
     <para>Installation time will vary depending on the distributions
       chosen, installation media, and speed of the computer.  A series
       of messages will indicate the progress.</para>
 
     <para>First, the installer formats the selected disk(s) and
       initializes the partitions.  Next, in the case of a
       <literal>bootonly media</literal> or
       <literal>mini memstick</literal>, it downloads the selected
       components:</para>
 
     <figure xml:id="bsdinstall-distfile-fetching">
       <title>Fetching Distribution Files</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata
 	    fileref="bsdinstall/bsdinstall-distfile-fetching"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
     <para>Next, the integrity of the distribution files is verified
       to ensure they have not been corrupted during download or
       misread from the installation media:</para>
 
     <figure xml:id="bsdinstall-distfile-verify">
       <title>Verifying Distribution Files</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata
 	    fileref="bsdinstall/bsdinstall-distfile-verifying"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
     <para>Finally, the verified distribution files are extracted to
       the disk:</para>
 
     <figure xml:id="bsdinstall-distfile-extract">
       <title>Extracting Distribution Files</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata
 	    fileref="bsdinstall/bsdinstall-distfile-extracting"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
     <para>Once all requested distribution files have been extracted,
       <application>bsdinstall</application> displays the first
       post-installation configuration screen.  The available
       post-configuration options are described in the next
       section.</para>
   </sect1>
 
   <sect1 xml:id="bsdinstall-post">
     <title>Accounts, Time Zone, Services and Hardening</title>
 
     <sect2 xml:id="bsdinstall-post-root">
       <title>Setting the
 	<systemitem class="username">root</systemitem>
 	Password</title>
 
       <para>First, the <systemitem class="username">root</systemitem>
 	password must be set.  While entering the password, the
 	characters being typed are not displayed on the screen.  After
 	the password has been entered, it must be entered again.  This
 	helps prevent typing errors.</para>
 
       <figure xml:id="bsdinstall-post-set-root-passwd">
 	<title>Setting the <systemitem
 	    class="username">root</systemitem> Password</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-post-root-passwd"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
 
     <sect2 xml:id="bsdinstall-timezone">
       <title>Setting the Time Zone</title>
 
       <para>The next series of menus are used to determine the correct
 	local time by selecting the geographic region, country, and
 	time zone.  Setting the time zone allows the system to
 	automatically correct for regional time changes, such as
 	daylight savings time, and perform other time zone related
 	functions properly.</para>
 
       <para>The example shown here is for a machine located in the
 	mainland time zone of Spain, Europe.  The selections will
 	vary according to the geographical location.</para>
 
       <figure xml:id="bsdinstall-timezone-region">
 	<title>Select a Region</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-timezone-region"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The appropriate region is selected using the arrow keys
 	and then pressing <keycap>Enter</keycap>.</para>
 
       <figure xml:id="bsdinstall-timezone-country">
 	<title>Select a Country</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-timezone-country"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Select the appropriate country using the arrow keys and
 	press <keycap>Enter</keycap>.</para>
 
       <figure xml:id="bsdinstall-timezone-zone">
 	<title>Select a Time Zone</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-timezone-zone"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The appropriate time zone is selected using the arrow keys
 	and pressing <keycap>Enter</keycap>.</para>
 
       <figure xml:id="bsdinstall-timezone-confirmation">
 	<title>Confirm Time Zone</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-timezone-confirm"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Confirm the abbreviation for the time zone is
 	correct.</para>
 
       <figure xml:id="bsdinstall-timezone-date">
 	<title>Select Date</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-timezone-date"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The appropriate date is selected using the arrow keys
 	and then pressing
 	<guibutton>[&nbsp;Set&nbsp;Date&nbsp;]</guibutton>.
 	Otherwise, the date selection can be skipped by pressing
 	<guibutton>[&nbsp;Skip&nbsp;]</guibutton>.</para>
 
       <figure xml:id="bsdinstall-timezone-time">
 	<title>Select Time</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-timezone-time"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The appropriate time is selected using the arrow keys
 	and then pressing
 	<guibutton>[&nbsp;Set&nbsp;Time&nbsp;]</guibutton>.
 	Otherwise, the time selection can be skipped by pressing
 	<guibutton>[&nbsp;Skip&nbsp;]</guibutton>.</para>
     </sect2>
 
     <sect2 xml:id="bsdinstall-sysconf">
       <title>Enabling Services</title>
 
       <para>The next menu is used to configure which system services
 	will be started whenever the system boots.  All of these
 	services are optional.  Only start the services that are
 	needed for the system to function.</para>
 
       <figure xml:id="bsdinstall-config-serv">
 	<title>Selecting Additional Services to Enable</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-config-services"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Here is a summary of the services which can be enabled in
 	this menu:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>local_unbound</literal> - Enable the DNS
 	    local unbound.  It is necessary to keep in mind that this
 	    is the unbound of the base system and is only meant for
 	    use as a local caching forwarding resolver.  If the
 	    objective is to set up a resolver for the entire network
 	    install <package>dns/unbound</package>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>sshd</literal> - The Secure Shell
 	    (<acronym>SSH</acronym>) daemon is used to remotely access
 	    a system over an encrypted connection.  Only enable this
 	    service if the system should be available for remote
 	    logins.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>moused</literal> - Enable this service if the
 	    mouse will be used from the command-line system
 	    console.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>ntpdate</literal> - Enable the automatic
 	    clock synchronization at boot time.  The functionality of
 	    this program is now available in the &man.ntpd.8; daemon.
 	    After a suitable period of mourning, the &man.ntpdate.8;
 	    utility will be retired.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>ntpd</literal> - The Network Time Protocol
 	    (<acronym>NTP</acronym>) daemon for automatic clock
 	    synchronization.  Enable this service if there is a
 	    &windows;, Kerberos, or <acronym>LDAP</acronym> server on
 	    the network.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>powerd</literal> - System power control
 	    utility for power control and energy saving.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>dumpdev</literal> - Enabling crash dumps is
 	    useful in debugging issues with the system, so users are
 	    encouraged to enable crash dumps.</para>
 	</listitem>
 	</itemizedlist>
     </sect2>
 
     <sect2 xml:id="bsdinstall-hardening">
       <title>Enabling Hardening Security Options</title>
 
       <para>The next menu is used to configure which security
 	options will be enabled.  All of these options are optional.
 	But their use is encouraged.</para>
 
       <figure xml:id="bsdinstall-hardening-options">
 	<title>Selecting Hardening Security Options</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-hardening"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Here is a summary of the options which can be enabled in
 	this menu:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>hide_uids</literal> - Hide processes running
 	    as other users to prevent the unprivileged users to see
 	    other running processes in execution by other users (UID)
 	    preventing information leakage.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>hide_gids</literal> - Hide processes running
 	    as other groups to prevent the unprivileged users to see
 	    other running processes in execution by other groups (GID)
 	    preventing information leakage.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>hide_jail</literal> - Hide processes running
 	    in jails to prevent the unprivileged users to see
 	    processes running inside the jails.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>read_msgbuf</literal> - Disabling reading
 	    kernel message buffer for unprivileged users prevent from
 	    using &man.dmesg.8; to view messages from the kernel's log
 	    buffer.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>proc_debug</literal> - Disabling process
 	    debugging facilities for unprivileged users disables
 	    a variety of unprivileged inter-process debugging
 	    services, including some procfs functionality, ptrace(),
 	    and ktrace().  Please note that this will also prevent
 	    debugging tools, for instance &man.lldb.1;, &man.truss.1;,
 	    &man.procstat.1;, as well as some built-in debugging
 	    facilities in certain scripting language like PHP, etc.,
 	    from working for unprivileged users.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>random_pid</literal> - Randomize the PID of
 	    newly created processes.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>clear_tmp</literal> - Clean
 	    <filename>/tmp</filename> when the system starts
 	    up.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>disable_syslogd</literal> - Disable opening
 	    <application>syslogd</application> network socket.  By
 	    default &os; runs <application>syslogd</application> in a
 	    secure way with <command>-s</command>.  That prevents the
 	    daemon from listening for incoming UDP requests
 	    at port 514.  With this option enabled
 	    <application>syslogd</application> will run with the flag
 	    <command>-ss</command> which prevents
 	    <application>syslogd</application> from opening any port.
 	    To get more information consult &man.syslogd.8;.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>disable_sendmail</literal> - Disable the
 	    sendmail mail transport agent.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>secure_console</literal> - When this option
 	    is enabled, the prompt requests the <systemitem class="username">root</systemitem> password when
 	    entering single-user mode.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>disable_ddtrace</literal> - &dtrace; can run
 	    in a mode that will actually affect the running kernel.
 	    Destructive actions may not be used unless they have
 	    been explicitly enabled.  To enable this option when using
 	    &dtrace; use <command>-w</command>.  To get more
 	    information consult &man.dtrace.1;.</para>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2 xml:id="bsdinstall-addusers">
       <title>Add Users</title>
 
       <para>The next menu prompts to create at least one user account.
 	It is recommended to login to the system using a user account
 	rather than as <systemitem class="username">root</systemitem>.
 	When logged in as <systemitem
 	  class="username">root</systemitem>, there are essentially no
 	limits or protection on what can be done.  Logging in as a
 	normal user is safer and more secure.</para>
 
       <para>Select <guibutton>[&nbsp;Yes&nbsp;]</guibutton> to add new
 	users.</para>
 
       <figure xml:id="bsdinstall-add-user1">
 	<title>Add User Accounts</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-adduser1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Follow the prompts and input the requested information for
 	the user account.  The example shown in <xref
 	  linkend="bsdinstall-add-user2"/> creates the <systemitem
 	  class="username">asample</systemitem> user account.</para>
 
       <figure xml:id="bsdinstall-add-user2">
 	<title>Enter User Information</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-adduser2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Here is a summary of the information to input:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>Username</literal> - The name the user will
 	    enter to log in.  A common convention is to use the first
 	    letter of the first name combined with the last name, as
 	    long as each username is unique for the system.  The
 	    username is case sensitive and should not contain any
 	    spaces.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Full name</literal> - The user's full name.
 	    This can contain spaces and is used as a description for
 	    the user account.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Uid</literal> - User <acronym>ID</acronym>.
 	    Typically, this is left blank so the system will assign a
 	    value.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Login group</literal> - The user's group.
 	    Typically this is left blank to accept the default.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Invite <replaceable>user</replaceable> into
 	      other groups?</literal> - Additional groups to which the
 	    user will be added as a member.  If the user needs
 	    administrative access, type <literal>wheel</literal>
 	    here.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Login class</literal> - Typically left blank
 	    for the default.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Shell</literal> - Type in one of the listed
 	    values to set the interactive shell for the user.  Refer
 	    to <xref linkend="shells"/> for more information about
 	    shells.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Home directory</literal> - The user's home
 	    directory.  The default is usually correct.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Home directory permissions</literal> -
 	    Permissions on the user's home directory.  The default is
 	    usually correct.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Use password-based authentication?</literal>
 	    - Typically <literal>yes</literal> so that the user is
 	    prompted to input their password at login.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Use an empty password?</literal> -
 	    Typically <literal>no</literal> as it is insecure to have
 	    a blank password.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Use a random password?</literal> - Typically
 	    <literal>no</literal> so that the user can set their own
 	    password in the next prompt.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Enter password</literal> - The password for
 	    this user.  Characters typed will not show on the
 	    screen.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Enter password again</literal> - The password
 	    must be typed again for verification.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Lock out the account after
 	      creation?</literal> - Typically <literal>no</literal> so
 	    that the user can login.</para>
 	</listitem>
       </itemizedlist>
 
       <para>After entering everything, a summary is shown for review.
 	If a mistake was made, enter <literal>no</literal> and try
 	again.  If everything is correct, enter <literal>yes</literal>
 	to create the new user.</para>
 
       <figure xml:id="bsdinstall-add-user3">
 	<title>Exit User and Group Management</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-adduser3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If there are more users to add, answer the <literal>Add
 	  another user?</literal> question with
 	<literal>yes</literal>.  Enter <literal>no</literal> to finish
 	adding users and continue the installation.</para>
 
       <para>For more information on adding users and user management,
 	see <xref linkend="users-synopsis"/>.</para>
     </sect2>
 
     <sect2 xml:id="bsdinstall-final-conf">
       <title>Final Configuration</title>
 
       <para>After everything has been installed and configured, a
 	final chance is provided to modify settings.</para>
 
       <figure xml:id="bsdinstall-final-config">
 	<title>Final Configuration</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-finalconfiguration"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Use this menu to make any changes or do any additional
 	configuration before completing the installation.</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>Add User</literal> - Described in <xref
 	      linkend="bsdinstall-addusers"/>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Root Password</literal> - Described in <xref
 	      linkend="bsdinstall-post-root"/>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Hostname</literal> - Described in <xref
 	      linkend="bsdinstall-hostname"/>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Network</literal> - Described in <xref
 	      linkend="bsdinstall-config-network-dev"/>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Services</literal> - Described in <xref
 	      linkend="bsdinstall-sysconf"/>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>System Hardening</literal> - Described in
 	      <xref linkend="bsdinstall-hardening"/>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Time Zone</literal> - Described in <xref
 	      linkend="bsdinstall-timezone"/>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Handbook</literal> - Download and install the
 	    &os; Handbook.</para>
 	</listitem>
       </itemizedlist>
 
       <para>After any final configuration is complete, select
 	<guibutton>Exit</guibutton>.</para>
 
       <figure xml:id="bsdinstall-final-modification-shell">
 	<title>Manual Configuration</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-final-modification-shell"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para><application>bsdinstall</application> will prompt if there
 	are any additional configuration that needs to be done before
 	rebooting into the new system.  Select
 	<guibutton>[&nbsp;Yes&nbsp;]</guibutton> to exit to a shell
 	within the new system or
 	<guibutton>[&nbsp;No&nbsp;]</guibutton> to proceed to the last
 	step of the installation.</para>
 
       <figure xml:id="bsdinstall-final-main">
 	<title>Complete the Installation</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="bsdinstall/bsdinstall-mainexit"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If further configuration or special setup is needed,
 	select <guibutton>[&nbsp;Live&nbsp;CD&nbsp;]</guibutton> to
 	boot the install media into Live <acronym>CD</acronym>
 	mode.</para>
 
       <para>If the installation is complete, select
 	<guibutton>[&nbsp;Reboot&nbsp;]</guibutton> to reboot the
 	computer and start the new &os; system.  Do not forget to
 	remove the &os; install media or the computer may boot from it
 	again.</para>
 
       <para>As &os; boots, informational messages are displayed.
 	After the system finishes booting, a login prompt is
 	displayed.  At the <prompt>login:</prompt> prompt, enter the
 	username added during the installation.  Avoid logging in as
 	<systemitem class="username">root</systemitem>.  Refer to
 	<xref linkend="users-superuser"/> for instructions on how to
 	become the superuser when administrative access is
 	needed.</para>
 
       <para>The messages that appeared during boot can be reviewed by
 	pressing <keycap>Scroll-Lock</keycap> to turn on the
 	scroll-back buffer.  The <keycap>PgUp</keycap>,
 	<keycap>PgDn</keycap>, and arrow keys can be used to scroll
 	back through the messages.  When finished, press
 	<keycap>Scroll-Lock</keycap> again to unlock the display and
 	return to the console.  To review these messages once the
 	system has been up for some time, type <command>less
 	  /var/run/dmesg.boot</command> from a command prompt.  Press
 	<keycap>q</keycap> to return to the command line after
 	viewing.</para>
 
       <para>If <application>sshd</application> was enabled in <xref
 	  linkend="bsdinstall-config-serv"/>, the first boot may be
 	a bit slower as the system will generate the
 	<acronym>RSA</acronym> and <acronym>DSA</acronym> keys.
 	Subsequent boots will be faster.  The fingerprints of the keys
 	will be displayed, as seen in this example:</para>
 
       <screen>Generating public/private rsa1 key pair.
 Your identification has been saved in /etc/ssh/ssh_host_key.
 Your public key has been saved in /etc/ssh/ssh_host_key.pub.
 The key fingerprint is:
 10:a0:f5:af:93:ae:a3:1a:b2:bb:3c:35:d9:5a:b3:f3 root@machine3.example.com
 The key's randomart image is:
 +--[RSA1 1024]----+
 |    o..          |
 |   o . .         |
 |  .   o          |
 |       o         |
 |    o   S        |
 |   + + o         |
 |o . + *          |
 |o+ ..+ .         |
 |==o..o+E         |
 +-----------------+
 Generating public/private dsa key pair.
 Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
 Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
 The key fingerprint is:
 7e:1c:ce:dc:8a:3a:18:13:5b:34:b5:cf:d9:d1:47:b2 root@machine3.example.com
 The key's randomart image is:
 +--[ DSA 1024]----+
 |       ..     . .|
 |      o  .   . + |
 |     . ..   . E .|
 |    . .  o o . . |
 |     +  S = .    |
 |    +  . = o     |
 |     +  . * .    |
 |    . .  o .     |
 |      .o. .      |
 +-----------------+
 Starting sshd.</screen>
 
       <para>Refer to <xref linkend="openssh"/> for more information
 	about fingerprints and <acronym>SSH</acronym>.</para>
 
       <para>&os; does not install a graphical environment by default.
 	Refer to <xref linkend="x11"/> for more information about
 	installing and configuring a graphical window manager.</para>
 
       <para>Proper shutdown of a &os; computer helps protect data and
 	hardware from damage.  <emphasis>Do not turn off the power
 	before the system has been properly shut down!</emphasis>  If
 	the user is a member of the <systemitem
 	  class="groupname">wheel</systemitem> group, become the
 	superuser by typing <command>su</command> at the command line
 	and entering the <systemitem
 	  class="username">root</systemitem> password.  Then, type
 	<command>shutdown -p now</command> and the system will shut
 	down cleanly, and if the hardware supports it, turn itself
 	off.</para>
     </sect2>
   </sect1>
 
   <sect1 xml:id="bsdinstall-network">
     <title>Network Interfaces</title>
 
     <sect2 xml:id="bsdinstall-config-network-dev">
       <title>Configuring Network Interfaces</title>
 
       <para>Next, a list of the network interfaces found on the
 	computer is shown.  Select the interface to configure.</para>
 
       <figure xml:id="bsdinstall-configure-net-interface">
 	<title>Choose a Network Interface</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-network-interface"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If an Ethernet interface is selected, the installer will
 	skip ahead to the menu shown in <xref
 	  linkend="bsdinstall-configure-net-ipv4"/>.  If a wireless
 	network interface is chosen, the system will instead scan for
 	wireless access points:</para>
 
       <figure xml:id="bsdinstall-wireless-scan">
 	<title>Scanning for Wireless Access Points</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-wireless-scan"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Wireless networks are identified by a Service Set
 	Identifier (<acronym>SSID</acronym>), a short, unique name
 	given to each network.  <acronym>SSIDs</acronym> found during
 	the scan are listed, followed by a description of the
 	encryption types available for that network.  If the desired
 	<acronym>SSID</acronym> does not appear in the list, select
 	<guibutton>[&nbsp;Rescan&nbsp;]</guibutton> to scan again.  If
 	the desired network still does not appear, check for problems
 	with antenna connections or try moving the computer closer to
 	the access point.  Rescan after each change is made.</para>
 
       <figure xml:id="bsdinstall-wireless-accesspoints">
 	<title>Choosing a Wireless Network</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-wireless-accesspoints"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Next, enter the encryption information for connecting to
 	the selected wireless network.  <acronym>WPA2</acronym>
 	encryption is strongly recommended as older encryption types,
 	like <acronym>WEP</acronym>, offer little security.  If the
 	network uses <acronym>WPA2</acronym>, input the password, also
 	known as the Pre-Shared Key (<acronym>PSK</acronym>).  For
 	security reasons, the characters typed into the input box are
 	displayed as asterisks.</para>
 
       <figure xml:id="bsdinstall-wireless-wpa2">
 	<title>WPA2 Setup</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-wireless-wpa2setup"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Next, choose whether or not an <acronym>IPv4</acronym>
 	address should be configured on the Ethernet or wireless
 	interface:</para>
 
       <figure xml:id="bsdinstall-configure-net-ipv4">
 	<title>Choose <acronym>IPv4</acronym> Networking</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-network-interface-ipv4"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>There are two methods of <acronym>IPv4</acronym>
 	configuration.  <acronym>DHCP</acronym> will automatically
 	configure the network interface correctly and should be used
 	if the network provides a <acronym>DHCP</acronym> server.
 	Otherwise, the addressing information needs to be input
 	manually as a static configuration.</para>
 
       <note>
 	<para>Do not enter random network information as it will not
 	  work.  If a <acronym>DHCP</acronym> server is not available,
 	  obtain the information listed in <xref
 	    linkend="bsdinstall-collect-network-information"/> from
 	  the network administrator or Internet service
 	  provider.</para>
       </note>
 
       <para>If a <acronym>DHCP</acronym> server is available, select
 	<guibutton>[&nbsp;Yes&nbsp;]</guibutton> in the next menu to
 	automatically configure the network interface.  The installer
 	will appear to pause for a minute or so as it finds the
 	<acronym>DHCP</acronym> server and obtains the addressing
 	information for the system.</para>
 
       <figure xml:id="bsdinstall-net-ipv4-dhcp">
 	<title>Choose <acronym>IPv4</acronym> <acronym>DHCP</acronym>
 	  Configuration</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If a <acronym>DHCP</acronym> server is not available,
 	select <guibutton>[&nbsp;No&nbsp;]</guibutton> and input the
 	following addressing information in this menu:</para>
 
       <figure xml:id="bsdinstall-net-ipv4-static">
 	<title><acronym>IPv4</acronym> Static Configuration</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-network-interface-ipv4-static"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>IP Address</literal> - The
 	    <acronym>IPv4</acronym> address assigned to this computer.
 	    The address must be unique and not already in use by
 	    another piece of equipment on the local network.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Subnet Mask</literal> - The subnet mask for
 	    the network.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Default Router</literal> - The
 	    <acronym>IP</acronym> address of the network's default
 	    gateway.</para>
 	</listitem>
       </itemizedlist>
 
       <para>The next screen will ask if the interface should be
 	configured for <acronym>IPv6</acronym>.  If
 	<acronym>IPv6</acronym> is available and desired, choose
 	<guibutton>[&nbsp;Yes&nbsp;]</guibutton> to select it.</para>
 
       <figure xml:id="bsdinstall-net-ipv6">
 	<title>Choose IPv6 Networking</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-network-interface-ipv6"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para><acronym>IPv6</acronym> also has two methods of
 	configuration.    StateLess Address AutoConfiguration
 	(<acronym>SLAAC</acronym>) will automatically request the
 	correct configuration information from a local router.  Refer
 	to <link
 	  xlink:href="http://tools.ietf.org/html/rfc4862">rfc4862</link>
 	for more information.  Static configuration requires manual
 	entry of network information.</para>
 
       <para>If an <acronym>IPv6</acronym> router is available, select
 	<guibutton>[&nbsp;Yes&nbsp;]</guibutton> in the next menu to
 	automatically configure the network interface.  The installer
 	will appear to pause for a minute or so as it finds the router
 	and obtains the addressing information for the system.</para>
 
       <figure xml:id="bsdinstall-net-ipv6-slaac">
 	<title>Choose IPv6 SLAAC Configuration</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-network-interface-slaac"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If an <acronym>IPv6</acronym> router is not available,
 	select <guibutton>[&nbsp;No&nbsp;]</guibutton> and input the
 	following addressing information in this menu:</para>
 
       <figure xml:id="bsdinstall-net-ipv6-static">
 	<title>IPv6 Static Configuration</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-network-interface-ipv6-static"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>IPv6 Address</literal> - The
 	    <acronym>IPv6</acronym> address assigned to this computer.
 	    The address must be unique and not already in use by
 	    another piece of equipment on the local network.</para>
 	</listitem>
 
 	<listitem>
 	  <para><literal>Default Router</literal> - The
 	    <acronym>IPv6</acronym> address of the network's default
 	    gateway.</para>
 	</listitem>
       </itemizedlist>
 
       <para>The last network configuration menu is used to configure
 	the Domain Name System (<acronym>DNS</acronym>) resolver,
 	which converts hostnames to and from network addresses.  If
 	<acronym>DHCP</acronym> or <acronym>SLAAC</acronym> was used
 	to autoconfigure the network interface, the <literal>Resolver
 	  Configuration</literal> values may already be filled in.
 	Otherwise, enter the local network's domain name in the
 	<literal>Search</literal> field.  <literal>DNS #1</literal>
 	and <literal>DNS #2</literal> are the <acronym>IPv4</acronym>
 	and/or <acronym>IPv6</acronym> addresses of the
 	<acronym>DNS</acronym> servers.  At least one
 	<acronym>DNS</acronym> server is required.</para>
 
       <figure xml:id="bsdinstall-net-dns-config">
 	<title>DNS Configuration</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-configure-network-ipv4-dns"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Once the interface is configured, select a mirror site
 	that is located in the same region of the world as the
 	computer on which &os; is being installed.  Files can be
 	retrieved more quickly when the mirror is close to the
 	target computer, reducing installation time.</para>
 
       <figure xml:id="bsdinstall-netinstall-mirror">
 	<title>Choosing a Mirror</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata
 	      fileref="bsdinstall/bsdinstall-netinstall-mirrorselect"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 xml:id="bsdinstall-install-trouble">
     <title>Troubleshooting</title>
 
     <indexterm>
       <primary>installation</primary>
       <secondary>troubleshooting</secondary>
     </indexterm>
     <para>This section covers basic installation
       troubleshooting, such as common problems people have
       reported.</para>
 
     <para>Check the Hardware Notes (<link
 	xlink:href="&url.base;/releases/index.html">https://www.freebsd.org/releases/index.html</link>)
       document for the version of &os; to make sure the hardware is
       supported.  If the hardware is supported and lock-ups or other
       problems occur, build a custom kernel using the instructions in
       <xref linkend="kernelconfig"/> to add support for devices which
       are not present in the <filename>GENERIC</filename> kernel.  The
       default kernel assumes that most hardware devices are in their
       factory default configuration in terms of
       <acronym>IRQ</acronym>s, <acronym>I/O</acronym> addresses, and
       <acronym>DMA</acronym> channels.  If the hardware has been
       reconfigured, a custom kernel configuration file can tell &os;
       where to find things.</para>
 
     <note>
       <para>Some installation problems can be avoided or alleviated by
 	updating the firmware on various hardware components, most
 	notably the motherboard.  Motherboard firmware is usually
 	referred to as the <acronym>BIOS</acronym>.  Most motherboard
 	and computer manufacturers have a website for upgrades and
 	upgrade information.</para>
 
       <para>Manufacturers generally advise against upgrading the
 	motherboard <acronym>BIOS</acronym> unless there is a good
 	reason for doing so, like a critical update.  The upgrade
 	process <emphasis>can</emphasis> go wrong, leaving the
 	<acronym>BIOS</acronym> incomplete and the computer
 	inoperative.</para>
     </note>
 
     <para>If the system hangs while probing hardware during boot, or
       it behaves strangely during install, <acronym>ACPI</acronym> may
       be the culprit.  &os; makes extensive use of the system
       <acronym>ACPI</acronym> service on the &arch.i386; and
       &arch.amd64; platforms to aid in system configuration
       if it is detected during boot.  Unfortunately, some bugs still
       exist in both the <acronym>ACPI</acronym> driver and within
       system motherboards and <acronym>BIOS</acronym> firmware.
       <acronym>ACPI</acronym> can be disabled by setting the
       <literal>hint.acpi.0.disabled</literal> hint in the third stage
       boot loader:</para>
 
     <screen><userinput>set hint.acpi.0.disabled="1"</userinput></screen>
 
     <para>This is reset each time the system is booted, so it is
       necessary to add <literal>hint.acpi.0.disabled="1"</literal> to
       the file <filename>/boot/loader.conf</filename>.  More
       information about the boot loader can be found in <xref
 	linkend="boot-synopsis"/>.</para>
   </sect1>
 
   <sect1 xml:id="using-live-cd">
     <title>Using the Live <acronym>CD</acronym></title>
 
     <para>The welcome menu of <application>bsdinstall</application>,
       shown in <xref linkend="bsdinstall-choose-mode"/>, provides a
       <guibutton>[&nbsp;Live&nbsp;CD&nbsp;]</guibutton> option.  This
       is useful for those who are still wondering whether &os; is the
       right operating system for them and want to test some of the
       features before installing.</para>
 
     <para>The following points should be noted before using the
       <guibutton>[&nbsp;Live&nbsp;CD&nbsp;]</guibutton>:</para>
 
     <itemizedlist>
       <listitem>
 	<para>To gain access to the system, authentication is
 	  required.  The username is <systemitem
 	    class="username">root</systemitem> and the password is
 	  blank.</para>
       </listitem>
 
       <listitem>
 	<para>As the system runs directly from the installation media,
 	  performance will be significantly slower than that of a
 	  system installed on a hard disk.</para>
       </listitem>
 
       <listitem>
 	<para>This option only provides a command prompt and not a
 	  graphical interface.</para>
       </listitem>
     </itemizedlist>
   </sect1>
 </chapter>
diff --git a/en_US.ISO8859-1/books/handbook/desktop/chapter.xml b/en_US.ISO8859-1/books/handbook/desktop/chapter.xml
index 9daff7a2f3..9fbd69a5dc 100644
--- a/en_US.ISO8859-1/books/handbook/desktop/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/desktop/chapter.xml
@@ -1,919 +1,920 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!--
      The FreeBSD Documentation Project
      $FreeBSD$
 -->
 <chapter xmlns="http://docbook.org/ns/docbook"
   xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
   xml:id="desktop">
   <!--
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Christophe</firstname>
 	<surname>Juniet</surname>
 	<contrib>Contributed by </contrib>
       </author>
     </authorgroup>
   </chapterinfo>
   -->
 
   <title>Desktop Applications</title>
 
   <sect1 xml:id="desktop-synopsis">
     <title>Synopsis</title>
 
     <para>While &os; is popular as a server for its performance and
       stability, it is also suited for day-to-day use as a desktop.
       With over &os.numports; applications available as &os; packages
       or ports, it is easy to build a customized desktop that runs
       a wide variety of desktop applications.  This chapter
       demonstrates how to install numerous desktop applications,
       including web browsers, productivity software, document viewers,
       and financial software.</para>
 
     <note>
       <para>Users who prefer to install a pre-built desktop version
 	of FreeBSD rather than configuring one from scratch should
 	refer to <link
-	  xlink:href="https://www.furybsd.org">FuryBSD</link>,
-	<link xlink:href="https://ghostbsd.org">GhostBSD</link> or
+	  xlink:href="https://ghostbsd.org">GhostBSD</link>,
 	<link
-	  xlink:href="https://www.midnightbsd.org">MidnightBSD</link>.</para>
+	  xlink:href="https://www.midnightbsd.org">MidnightBSD</link>
+	 or <link
+	 xlink:href="https://nomadbsd.org/">NomadBSD</link>.</para>
     </note>
 
     <para>Readers of this chapter should know how to:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Install additional software using packages or
 	  ports as described in <xref linkend="ports"/>.</para>
       </listitem>
 
       <listitem>
 	<para>Install X and a window manager as described in
 	  <xref linkend="x11"/>.</para>
       </listitem>
     </itemizedlist>
 
     <para>For information on how to configure a multimedia
       environment, refer to <xref linkend="multimedia"/>.</para>
   </sect1>
 
   <sect1 xml:id="desktop-browsers">
     <title>Browsers</title>
 
     <indexterm>
       <primary>browsers</primary>
       <secondary>web</secondary>
     </indexterm>
 
     <para>&os; does not come with a pre-installed web browser.
       Instead, the <link
 	xlink:href="https://www.FreeBSD.org/ports/www.html">www</link>
       category of the Ports Collection contains many browsers which
       can be installed as a package or compiled from the Ports
       Collection.</para>
 
     <para>The <application>KDE</application> and
       <application>GNOME</application> desktop environments include
       their own HTML browser.  Refer to <xref linkend="x11-wm"/>
       for more information on how to set up these complete
       desktops.</para>
 
     <para>Some lightweight browsers include
       <package>www/dillo2</package>, <package>www/links</package>, and
       <package>www/w3m</package>.</para>
 
     <para>This section demonstrates how to install the following
       popular web browsers and indicates if the application is
       resource-heavy, takes time to compile from ports, or has any
       major dependencies.</para>
 
     <informaltable frame="none" pgwide="1">
       <tgroup cols="4">
 	<thead>
 	  <row>
 	    <entry>Application Name</entry>
 	    <entry>Resources Needed</entry>
 	    <entry>Installation from Ports</entry>
 	    <entry>Notes</entry>
 	  </row>
 	</thead>
 
 	<tbody>
 	  <row>
 	    <entry><application>Firefox</application></entry>
 	    <entry>medium</entry>
 	    <entry>heavy</entry>
 	    <entry>&os;, &linux;, and localized versions are
 	      available</entry>
 	  </row>
 
 	  <row>
 	    <entry><application>Konqueror</application></entry>
 	    <entry>medium</entry>
 	    <entry>heavy</entry>
 	    <entry>Requires <application>KDE</application>
 	      libraries</entry>
 	  </row>
 
 	  <row>
 	    <entry><application>Chromium</application></entry>
 	    <entry>medium</entry>
 	    <entry>heavy</entry>
 	    <entry>Requires <application>Gtk+</application></entry>
 	  </row>
 	</tbody>
       </tgroup>
     </informaltable>
 
     <sect2>
       <title>Firefox</title>
 
       <indexterm>
 	<primary><application>Firefox</application></primary>
       </indexterm>
 
       <para><application>Firefox</application> is an open source
 	browser that features a
 	standards-compliant HTML display engine, tabbed browsing,
 	popup blocking, extensions, improved security, and more.
 	<application>Firefox</application> is based on the
 	<application>Mozilla</application> codebase.</para>
 
       <para>To install the package of the latest release version of
 	<application>Firefox</application>, type:</para>
 
       <screen>&prompt.root; <userinput>pkg install firefox</userinput></screen>
 
       <para>To instead install <application>Firefox</application>
 	Extended Support Release (ESR) version, use:</para>
 
       <screen>&prompt.root; <userinput>pkg install firefox-esr</userinput></screen>
 
       <para>The Ports Collection can instead be used to compile the
 	desired version of <application>Firefox</application> from
 	source code.  This example builds
 	<package>www/firefox</package>, where
 	<literal>firefox</literal> can be replaced with the ESR or
 	localized version to install.</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/www/firefox</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Konqueror</title>
 
       <indexterm>
 	<primary><application>Konqueror</application></primary>
       </indexterm>
 
       <para><application>Konqueror</application> is more than a web
 	browser as it is also a file manager and a multimedia
 	viewer.  Supports WebKit as well as its own KHTML.  WebKit is
 	a rendering engine used by many modern browsers including
 	Chromium.</para>
 
       <para><application>Konqueror</application> can be installed as
 	a package by typing:</para>
 
       <screen>&prompt.root; <userinput>pkg install konqueror</userinput></screen>
 
       <para>To install from the Ports Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/x11-fm/konqueror/</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Chromium</title>
 
       <indexterm>
 	<primary><application>Chromium</application></primary>
       </indexterm>
 
       <para><application>Chromium</application> is an open source
 	browser project that aims to build a safer, faster, and more
 	stable web browsing experience.
 	<application>Chromium</application> features tabbed browsing,
 	popup blocking, extensions, and much more.
 	<application>Chromium</application> is the open source project
 	upon which the Google Chrome web browser is based.</para>
 
       <para><application>Chromium</application> can be installed as a
 	package by typing:</para>
 
       <screen>&prompt.root; <userinput>pkg install chromium</userinput></screen>
 
       <para>Alternatively, <application>Chromium</application> can be
 	compiled from source using the Ports Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/www/chromium</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <note>
 	<para>The executable for <application>Chromium</application>
 	  is <filename>/usr/local/bin/chrome</filename>, not
 	  <filename>/usr/local/bin/chromium</filename>.</para>
       </note>
     </sect2>
   </sect1>
 
   <sect1 xml:id="desktop-productivity">
     <title>Productivity</title>
 
     <para>When it comes to productivity, users often look for an
       office suite or an easy-to-use word processor.  While some
       <link linkend="x11-wm">desktop environments</link> like
       <application>KDE</application> provide an office suite, there
       is no default productivity package.  Several office suites and
       graphical word processors are available for &os;, regardless
       of the installed window manager.</para>
 
     <para>This section demonstrates how to install the following
       popular productivity software and indicates if the application
       is resource-heavy, takes time to compile from ports, or has any
       major dependencies.</para>
 
     <informaltable frame="none" pgwide="1">
       <tgroup cols="4">
 	<thead>
 	  <row>
 	    <entry>Application Name</entry>
 	    <entry>Resources Needed</entry>
 	    <entry>Installation from Ports</entry>
 	    <entry>Major Dependencies</entry>
 	  </row>
 	</thead>
 
 	<tbody>
 	  <row>
 	    <entry><application>Calligra</application></entry>
 	    <entry>light</entry>
 	    <entry>heavy</entry>
 	    <entry><application>KDE</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>AbiWord</application></entry>
 	    <entry>light</entry>
 	    <entry>light</entry>
 	    <entry><application>Gtk+</application> or
 	      <application>GNOME</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>The Gimp</application></entry>
 	    <entry>light</entry>
 	    <entry>heavy</entry>
 	    <entry><application>Gtk+</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>Apache
 		OpenOffice</application></entry>
 	    <entry>heavy</entry>
 	    <entry>huge</entry>
 	    <entry><application>&jdk;</application> and
 	      <application>Mozilla</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>LibreOffice</application></entry>
 	    <entry>somewhat heavy</entry>
 	    <entry>huge</entry>
 	    <entry><application>Gtk+</application>, or
 	      <application>KDE</application>/
 	      <application>GNOME</application>, or
 	      <application>&jdk;</application></entry>
 	  </row>
 	</tbody>
       </tgroup>
     </informaltable>
 
     <sect2>
       <title>Calligra</title>
 
       <indexterm>
 	<primary><application>Calligra</application></primary>
       </indexterm>
       <indexterm>
 	<primary>office suite</primary>
 	<secondary><application>Calligra</application></secondary>
       </indexterm>
 
       <para>The KDE desktop environment includes
 	an office suite which can be installed separately from
 	<application>KDE</application>.
 	<application>Calligra</application> includes standard
 	components that can be found in other office suites.
 	<application>Words</application> is the word processor,
 	<application>Sheets</application> is the spreadsheet program,
 	<application>Stage</application> manages slide presentations,
 	and <application>Karbon</application> is used to draw
 	graphical documents.</para>
 
       <para>In &os;, <package>editors/calligra</package> can be
 	installed as a package or a port.  To install the
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install calligra</userinput></screen>
 
       <para>If the package is not available, use the Ports Collection
 	instead:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/editors/calligra</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>AbiWord</title>
 
       <indexterm>
 	<primary><application>AbiWord</application></primary>
       </indexterm>
 
       <para><application>AbiWord</application> is a free word
 	processing program similar in look and feel to
 	<application>&microsoft; Word</application>.  It is fast,
 	contains many features, and is user-friendly.</para>
 
       <para><application>AbiWord</application> can import or export
 	many file formats, including some proprietary ones like
 	&microsoft; <filename>.rtf</filename>.</para>
 
       <para>To install the <application>AbiWord</application>
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install abiword</userinput></screen>
 
       <para>If the package is not available, it can be compiled from
 	the Ports Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/editors/abiword</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>The GIMP</title>
 
       <indexterm>
 	<primary><application>The GIMP</application></primary>
       </indexterm>
 
       <para>For image authoring or picture retouching,
 	<application>The GIMP</application> provides a sophisticated
 	image manipulation program.  It can be used as a simple paint
 	program or as a quality photo retouching suite.  It supports a
 	large number of plugins and features a scripting interface.
 	<application>The GIMP</application> can read and write a wide
 	range of file formats and supports interfaces with scanners
 	and tablets.</para>
 
       <para>To install the package:</para>
 
       <screen>&prompt.root; <userinput>pkg install gimp</userinput></screen>
 
       <para>Alternately, use the Ports Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/graphics/gimp</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <para>The graphics category (<link
 	  xlink:href="https://www.FreeBSD.org/ports/graphics.html">freebsd.org/ports/graphics.html</link>)
 	of the Ports Collection contains several
 	<application>GIMP</application>-related plugins, help files,
 	and user manuals.</para>
 
     </sect2>
 
     <sect2>
       <title>Apache OpenOffice</title>
 
       <indexterm>
 	<primary>
 	  <application>Apache OpenOffice</application>
 	</primary>
       </indexterm>
       <indexterm>
 	<primary>office suite</primary>
 	<secondary>
 	  <application>Apache OpenOffice</application>
 	</secondary>
       </indexterm>
 
       <para><application>Apache OpenOffice</application> is an open
 	source office suite which is developed under the wing of the
 	Apache Software Foundation's Incubator.  It includes all of
 	the applications found in a complete office productivity
 	suite: a word processor, spreadsheet, presentation manager,
 	and drawing program.  Its user interface is similar to other
 	office suites, and it can import and export in various popular
 	file formats.  It is available in a number of different
 	languages and internationalization has been extended to
 	interfaces, spell checkers, and dictionaries.</para>
 
       <para>The word processor of <application>Apache
 	  OpenOffice</application> uses a native XML file format for
 	increased portability and flexibility.  The spreadsheet
 	program features a macro language which can be interfaced
 	with external databases.  <application>Apache
 	  OpenOffice</application> is stable and runs natively on
 	&windows;, &solaris;, &linux;, &os;, and &macos;&nbsp;X.
 	More information about <application>Apache
 	  OpenOffice</application> can be found at <link
 	  xlink:href="http://openoffice.org/">openoffice.org</link>.
 	For &os; specific information refer to <link
 	  xlink:href="http://porting.openoffice.org/freebsd/">porting.openoffice.org/freebsd/</link>.</para>
 
       <para>To install the <application>Apache
 	  OpenOffice</application> package:</para>
 
       <screen>&prompt.root; <userinput>pkg install apache-openoffice</userinput></screen>
 
       <para>Once the package is installed, type the following command
 	to launch <application>Apache OpenOffice</application>:</para>
 
       <screen>&prompt.user; <userinput>openoffice-<replaceable>X.Y.Z</replaceable></userinput></screen>
 
       <para>where <replaceable>X.Y.Z</replaceable> is the version
 	number of the installed version of <application>Apache
 	  OpenOffice</application>.  The first time
 	<application>Apache OpenOffice</application> launches, some
 	questions will be asked and a
 	<filename>.openoffice.org</filename> folder will be created in
 	the user's home directory.</para>
 
       <para>If the desired <application>Apache
 	  OpenOffice</application> package is not available, compiling
 	the port is still an option.  However, this requires a lot of
 	disk space and a fairly long time to compile:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/editors/openoffice-4</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <note>
 	<para>To build a localized version, replace the previous
 	  command with:</para>
 
 	<screen>&prompt.root; <userinput>make LOCALIZED_LANG=<replaceable>your_language</replaceable> install clean</userinput></screen>
 
 	<para>Replace
 	  <replaceable>your_language</replaceable> with the correct
 	  language ISO-code.  A list of supported language codes is
 	  available in
 	  <filename>files/Makefile.localized</filename>, located in
 	  the port's directory.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>LibreOffice</title>
 
       <indexterm>
 	<primary><application>LibreOffice</application></primary>
       </indexterm>
       <indexterm>
 	<primary>office suite</primary>
 	<secondary><application>LibreOffice</application></secondary>
       </indexterm>
 
       <para><application>LibreOffice</application> is a free software
 	office suite developed by <link
 	  xlink:href="http://www.documentfoundation.org/">documentfoundation.org</link>.
 	It is compatible with other major office suites and available
 	on a variety of platforms.  It is a rebranded fork of
 	<application>Apache OpenOffice</application> and includes
 	applications found in a complete office productivity suite:
 	a word processor, spreadsheet, presentation manager, drawing
 	program, database management program, and a tool for creating
 	and editing mathematical formul&aelig;.  It is available in
 	a number of different languages and internationalization has
 	been extended to interfaces, spell checkers, and
 	dictionaries.</para>
 
       <para>The word processor of
 	<application>LibreOffice</application> uses a native XML file
 	format for increased portability and flexibility.  The
 	spreadsheet program features a macro language which can be
 	interfaced with external databases.
 	<application>LibreOffice</application> is stable and runs
 	natively on &windows;, &linux;, &os;, and &macos;&nbsp;X.
 	More information about <application>LibreOffice</application>
 	can be found at <link
 	  xlink:href="http://www.libreoffice.org/">libreoffice.org</link>.</para>
 
       <para>To install the English version of the
 	<application>LibreOffice</application> package:</para>
 
       <screen>&prompt.root; <userinput>pkg install libreoffice</userinput></screen>
 
       <para>The editors category (<link
 	  xlink:href="https://www.FreeBSD.org/ports/editors.html">freebsd.org/ports/editors.html</link>)
 	of the Ports Collection contains several localizations for
 	<application>LibreOffice</application>.  When installing a
 	localized package, replace <literal>libreoffice</literal>
 	with the name of the localized package.</para>
 
       <para>Once the package is installed, type the following command
 	to run <application>LibreOffice</application>:</para>
 
       <screen>&prompt.user; <userinput>libreoffice</userinput></screen>
 
       <para>During the first launch, some questions will be asked
 	and a <filename>.libreoffice</filename> folder will be created
 	in the user's home directory.</para>
 
       <para>If the desired <application>LibreOffice</application>
 	package is not available, compiling the port is still an
 	option.  However, this requires a lot of disk space and a
 	fairly long time to compile.  This example compiles the
 	English version:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/editors/libreoffice</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <note>
 	<para>To build a localized version,
 	  <command>cd</command> into the port directory of
 	  the desired language.  Supported languages can be found
 	  in the editors category (<link
 	    xlink:href="https://www.FreeBSD.org/ports/editors.html">freebsd.org/ports/editors.html</link>)
 	  of the Ports Collection.</para>
       </note>
     </sect2>
   </sect1>
 
   <sect1 xml:id="desktop-viewers">
     <title>Document Viewers</title>
 
     <para>Some new document formats have gained popularity since
       the advent of &unix; and the viewers they require may not be
       available in the base system.  This section demonstrates how to
       install the following document viewers:</para>
 
     <informaltable frame="none" pgwide="1">
       <tgroup cols="4">
 	<thead>
 	  <row>
 	    <entry>Application Name</entry>
 	    <entry>Resources Needed</entry>
 	    <entry>Installation from Ports</entry>
 	    <entry>Major Dependencies</entry>
 	  </row>
 	</thead>
 
 	<tbody>
 	  <row>
 	    <entry><application>Xpdf</application></entry>
 	    <entry>light</entry>
 	    <entry>light</entry>
 	    <entry><application>FreeType</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>gv</application></entry>
 	    <entry>light</entry>
 	    <entry>light</entry>
 	    <entry><application>Xaw3d</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>Geeqie</application></entry>
 	    <entry>light</entry>
 	    <entry>light</entry>
 	    <entry><application>Gtk+</application> or
 	      <application>GNOME</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>ePDFView</application></entry>
 	    <entry>light</entry>
 	    <entry>light</entry>
 	    <entry><application>Gtk+</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>Okular</application></entry>
 	    <entry>light</entry>
 	    <entry>heavy</entry>
 	    <entry><application>KDE</application></entry>
 	  </row>
 	</tbody>
       </tgroup>
     </informaltable>
 
     <sect2>
       <title>Xpdf</title>
 
       <indexterm>
 	<primary><application>Xpdf</application></primary>
       </indexterm>
       <indexterm>
 	<primary>PDF</primary>
 	<secondary>viewing</secondary>
       </indexterm>
 
       <para>For users that prefer a small &os; PDF viewer,
 	<application>Xpdf</application> provides a light-weight and
 	efficient viewer which requires few resources.  It uses the
 	standard X fonts and does not require any additional
 	toolkits.</para>
 
       <para>To install the <application>Xpdf</application>
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install xpdf</userinput></screen>
 
       <para>If the package is not available, use the Ports
 	Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/graphics/xpdf</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <para>Once the installation is complete, launch
 	<command>xpdf</command> and use the right mouse button to
 	activate the menu.</para>
     </sect2>
 
     <sect2>
       <title><application>gv</application></title>
 
       <indexterm>
 	<primary><application>gv</application></primary>
       </indexterm>
       <indexterm>
 	<primary>PDF</primary>
 	<secondary>viewing</secondary>
       </indexterm>
       <indexterm>
 	<primary>PostScript</primary>
 	<secondary>viewing</secondary>
       </indexterm>
 
       <para><application>gv</application> is a &postscript; and PDF
 	viewer.  It is based on <application>ghostview</application>,
 	but has a nicer look as it is based on the
 	<application>Xaw3d</application> widget toolkit.
 	<application>gv</application> has many configurable features,
 	such as orientation, paper size, scale, and anti-aliasing.
 	Almost any operation can be performed with either the
 	keyboard or the mouse.</para>
 
       <para>To install <application>gv</application> as a
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install gv</userinput></screen>
 
       <para>If a package is unavailable, use the Ports
 	Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/print/gv</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Geeqie</title>
 
       <indexterm>
 	<primary><application>Geeqie</application></primary>
       </indexterm>
 
       <para><application>Geeqie</application> is a fork from the
 	unmaintained <application>GQView</application> project, in an
 	effort to move development forward and integrate the existing
 	patches.  <application>Geeqie</application> is an image
 	manager which supports viewing a file with a single click,
 	launching an external editor, and thumbnail previews.  It also
 	features a slideshow mode and some basic file operations,
 	making it easy to manage image collections and to find
 	duplicate files.  <application>Geeqie</application> supports
 	full screen viewing and internationalization.</para>
 
       <para>To install the <application>Geeqie</application>
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install geeqie</userinput></screen>
 
       <para>If the package is not available, use the Ports
 	Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/graphics/geeqie</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>ePDFView</title>
 
       <indexterm>
 	<primary><application>ePDFView</application></primary>
       </indexterm>
       <indexterm>
 	<primary>PDF</primary>
 	<secondary>viewing</secondary>
       </indexterm>
 
       <para><application>ePDFView</application> is a lightweight
 	<acronym>PDF</acronym> document viewer that only uses the
 	<application>Gtk+</application> and
 	<application>Poppler</application> libraries.  It is currently
 	under development, but already opens most
 	<acronym>PDF</acronym> files (even encrypted), save copies of
 	documents, and has support for printing using
 	<application>CUPS</application>.</para>
 
       <para>To install <application>ePDFView</application> as a
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install epdfview</userinput></screen>
 
       <para>If a package is unavailable, use the Ports
 	Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/graphics/epdfview</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Okular</title>
 
       <indexterm>
 	<primary><application>Okular</application></primary>
       </indexterm>
       <indexterm>
 	<primary><acronym>PDF</acronym></primary>
 	<secondary>viewing</secondary>
       </indexterm>
 
       <para><application>Okular</application> is a universal document
 	viewer based on <application>KPDF</application> for
 	<application>KDE</application>.  It can open many document
 	formats, including <acronym>PDF</acronym>, &postscript;, DjVu,
 	<acronym>CHM</acronym>, <acronym>XPS</acronym>, and
 	ePub.</para>
 
       <para>To install <application>Okular</application> as a
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install okular</userinput></screen>
 
       <para>If a package is unavailable, use the Ports
 	Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/graphics/okular</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
   </sect1>
 
   <sect1 xml:id="desktop-finance">
     <title>Finance</title>
 
     <para>For managing personal finances on a &os; desktop, some
       powerful and easy-to-use applications can be installed.  Some
       are compatible with widespread file formats, such as the formats
       used by <application>Quicken</application> and
       <application>Excel</application>.</para>
 
     <para>This section covers these programs:</para>
 
     <informaltable frame="none" pgwide="1">
       <tgroup cols="4">
 	<thead>
 	  <row>
 	    <entry>Application Name</entry>
 	    <entry>Resources Needed</entry>
 	    <entry>Installation from Ports</entry>
 	    <entry>Major Dependencies</entry>
 	  </row>
 	</thead>
 
 	<tbody>
 	  <row>
 	    <entry><application>GnuCash</application></entry>
 	    <entry>light</entry>
 	    <entry>heavy</entry>
 	    <entry><application>GNOME</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>Gnumeric</application></entry>
 	    <entry>light</entry>
 	    <entry>heavy</entry>
 	    <entry><application>GNOME</application></entry>
 	  </row>
 
 	  <row>
 	    <entry><application>KMyMoney</application></entry>
 	    <entry>light</entry>
 	    <entry>heavy</entry>
 	    <entry><application>KDE</application></entry>
 	  </row>
 	</tbody>
       </tgroup>
     </informaltable>
 
     <sect2>
       <title>GnuCash</title>
 
       <indexterm>
 	<primary><application>GnuCash</application></primary>
       </indexterm>
 
       <para><application>GnuCash</application> is part of the
 	<application>GNOME</application> effort to provide
 	user-friendly, yet powerful, applications to end-users.
 	<application>GnuCash</application> can be used to keep track
 	of income and expenses, bank accounts, and stocks.  It
 	features an intuitive interface while remaining
 	professional.</para>
 
       <para><application>GnuCash</application> provides a smart
 	register, a hierarchical system of accounts, and many keyboard
 	accelerators and auto-completion methods.  It can split a
 	single transaction into several more detailed pieces.
 	<application>GnuCash</application> can import and merge
 	<application>Quicken</application> QIF files.  It also handles
 	most international date and currency formats.</para>
 
       <para>To install the <application>GnuCash</application>
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install gnucash</userinput></screen>
 
       <para>If the package is not available, use the Ports
 	Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/finance/gnucash</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Gnumeric</title>
 
       <indexterm>
 	<primary><application>Gnumeric</application></primary>
       </indexterm>
       <indexterm>
 	<primary>spreadsheet</primary>
 	<secondary><application>Gnumeric</application></secondary>
       </indexterm>
 
       <para><application>Gnumeric</application> is a spreadsheet
 	program developed by the <application>GNOME</application>
 	community.  It features convenient automatic guessing of user
 	input according to the cell format with an autofill system
 	for many sequences.  It can import files in a number of
 	popular formats, including <application>Excel</application>,
 	<application>Lotus 1-2-3</application>, and
 	<application>Quattro Pro</application>.  It has a large number
 	of built-in functions and allows all of the usual cell formats
 	such as number, currency, date, time, and much more.</para>
 
       <para>To install <application>Gnumeric</application> as a
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install gnumeric</userinput></screen>
 
       <para>If the package is not available, use the Ports
 	Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/math/gnumeric</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
 
     <sect2>
       <title>KMyMoney</title>
 
       <indexterm><primary><application>KMyMoney</application></primary></indexterm>
 
       <indexterm>
 	<primary>spreadsheet</primary>
 	<secondary><application>KMyMoney</application></secondary>
       </indexterm>
 
       <para><application>KMyMoney</application> is a personal finance
 	application created by the <application>KDE</application>
 	community.  <application>KMyMoney</application> aims to
 	provide the important features found in commercial personal
 	finance manager applications.  It also highlights ease-of-use
 	and proper double-entry accounting among its features.
 	<application>KMyMoney</application> imports from standard
 	<application>Quicken</application> QIF files, tracks
 	investments, handles multiple currencies, and provides a
 	wealth of reports.</para>
 
       <para>To install <application>KMyMoney</application> as a
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install kmymoney-kde4</userinput></screen>
 
       <para>If the package is not available, use the Ports
 	Collection:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/finance/kmymoney-kde4</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
     </sect2>
   </sect1>
 </chapter>
diff --git a/en_US.ISO8859-1/books/handbook/introduction/chapter.xml b/en_US.ISO8859-1/books/handbook/introduction/chapter.xml
index 34fec5a301..0df8e1f8ec 100644
--- a/en_US.ISO8859-1/books/handbook/introduction/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/introduction/chapter.xml
@@ -1,1162 +1,1162 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 <chapter xmlns="http://docbook.org/ns/docbook"
   xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
   xml:id="introduction">
 
   <info>
     <title>Introduction</title>
 
     <authorgroup>
       <author>
 	<personname>
 	  <firstname>Jim</firstname>
 	  <surname>Mock</surname>
 	</personname>
 	<contrib>Restructured, reorganized, and parts rewritten
 	  by </contrib>
       </author>
     </authorgroup>
   </info>
 
   <sect1 xml:id="introduction-synopsis">
     <title>Synopsis</title>
 
     <para>Thank you for your interest in &os;!  The following chapter
       covers various aspects of the &os;&nbsp;Project, such as its
       history, goals, development model, and so on.</para>
 
     <para>After reading this chapter you will know:</para>
 
     <itemizedlist>
       <listitem>
 	<para>How &os; relates to other computer operating
 	  systems.</para>
       </listitem>
 
       <listitem>
 	<para>The history of the &os;&nbsp;Project.</para>
       </listitem>
 
       <listitem>
 	<para>The goals of the &os;&nbsp;Project.</para>
       </listitem>
 
       <listitem>
 	<para>The basics of the &os; open-source development
 	  model.</para>
       </listitem>
 
       <listitem>
 	<para>And of course: where the name <quote>&os;</quote> comes
 	  from.</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 xml:id="nutshell">
     <title>Welcome to &os;!</title>
 
     <indexterm><primary>4.4BSD-Lite</primary></indexterm>
 
     <para>&os; is an Open Source, standards-compliant Unix-like
       operating system for x86 (both 32 and 64 bit), &arm;, AArch64,
       &risc-v;, &mips;, &power;, &powerpc;, and Sun &ultrasparc;
       computers.  It provides all the features that are
       nowadays taken for granted, such as preemptive multitasking,
       memory protection, virtual memory, multi-user facilities, SMP
       support, all the Open Source development tools for different
       languages and frameworks, and desktop features centered around
       X Window System, KDE, or GNOME.  Its particular strengths
       are:</para>
 
     <itemizedlist>
       <listitem>
 	<para><emphasis>Liberal Open Source license</emphasis>,
 	  which grants you rights to freely modify and extend
 	  its source code and incorporate it in both Open Source
 	  projects and closed products without imposing
 	  restrictions typical to copyleft licenses, as well
 	  as avoiding potential license incompatibility
 	  problems.</para>
       </listitem>
 
       <listitem>
 	<para><emphasis>Strong TCP/IP networking</emphasis>
 	  <indexterm> <primary>TCP/IP
 	      networking</primary></indexterm> - &os;
 	  implements industry standard protocols with ever
 	  increasing performance and scalability.  This makes
 	  it a good match in both server, and routing/firewalling
 	  roles - and indeed many companies and vendors use it
 	  precisely for that purpose.</para>
       </listitem>
 
       <listitem>
 	<para><emphasis>Fully integrated OpenZFS support</emphasis>,
 	  including root-on-ZFS, ZFS Boot Environments, fault
 	  management, administrative delegation, support for jails,
 	  &os; specific documentation, and system installer
 	  support.</para>
       </listitem>
 
       <listitem>
 	<para><emphasis>Extensive security features</emphasis>,
 	  from the Mandatory Access Control framework to Capsicum
 	  capability and sandbox mechanisms.</para>
       </listitem>
 
       <listitem>
 	<para><emphasis>Over 30 thousand prebuilt
 	    packages</emphasis> for all supported architectures,
 	  and the Ports Collection which makes it easy to build your
 	  own, customized ones.</para>
       </listitem>
 
       <listitem>
 	<para><emphasis>Documentation</emphasis> - in addition
 	  to Handbook and books from different authors that cover
 	  topics ranging from system administration to kernel
 	  internals, there are also the &man.man.1; pages, not only
 	  for userspace daemons, utilities, and configuration files,
 	  but also for kernel driver APIs (section 9) and individual
 	  drivers (section 4).</para>
       </listitem>
 
       <listitem>
 	<para><emphasis>Simple and consistent repository structure
 	    and build system</emphasis> - &os; uses a single
 	  repository for all of its components, both kernel and
 	  userspace.  This, along with an unified and easy to
 	  customize build system and a well thought out development
 	  process makes it easy to integrate &os; with build
 	  infrastructure for your own product.</para>
       </listitem>
 
       <listitem>
 	<para><emphasis>Staying true to Unix philosophy</emphasis>,
 	  preferring composability instead of monolithic <quote>all
 	    in one</quote> daemons with hardcoded behavior.</para>
       </listitem>
 
       <listitem>
 	<para><indexterm> <primary>binary compatibility</primary>
 	    <secondary>Linux</secondary></indexterm>
 	  <emphasis>Binary compatibility</emphasis> with Linux,
 	  which makes it possible to run many Linux binaries without
 	  the need for virtualisation.</para>
       </listitem>
     </itemizedlist>
 
     <para>&os; is based on the 4.4BSD-Lite<indexterm>
 	<primary>4.4BSD-Lite</primary>
       </indexterm> release from Computer
       Systems Research Group (CSRG)<indexterm>
 	<primary>Computer Systems Research Group (CSRG)</primary>
       </indexterm> at the University of California at Berkeley, and
       carries on the distinguished tradition of BSD systems
       development.  In addition to the fine work provided by CSRG,
       the &os;&nbsp;Project has put in many thousands of man-hours
       into extending the functionality and fine-tuning the system
       for maximum performance and reliability
       in real-life load situations.  &os; offers performance and
       reliability on par with other Open Source and commercial
       offerings, combined with cutting-edge features not available
       anywhere else.</para>
 
     <sect2 xml:id="os-overview">
       <title>What Can &os; Do?</title>
 
       <para>The applications to which &os; can be put are truly
 	limited only by your own imagination.  From software
 	development to factory automation, inventory control to
 	azimuth correction of remote satellite antennae; if it can be
 	done with a commercial &unix; product then it is more than
 	likely that you can do it with &os; too!  &os; also benefits
 	significantly from literally thousands of high quality
 	applications developed by research centers and universities
 	around the world, often available at little to no cost.</para>
 
       <para>Because the source code for &os; itself is freely
 	available, the system can also be customized to an almost
 	unheard of degree for special applications or projects, and in
 	ways not generally possible with operating systems from most
 	major commercial vendors.  Here is just a sampling of some of
 	the applications in which people are currently using
 	&os;:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><emphasis>Internet Services:</emphasis> The robust
 	    TCP/IP networking built into &os; makes it an ideal
 	    platform for a variety of Internet services such
 	    as:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Web servers</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>IPv4 and IPv6 routing</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Firewalls<indexterm>
 		  <primary>firewall</primary>
 		</indexterm>
 		and NAT<indexterm>
 		  <primary>NAT</primary>
 		</indexterm>
 		(<quote>IP masquerading</quote>) gateways</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>FTP servers<indexterm>
 		  <primary>FTP servers</primary>
 		</indexterm></para>
 	    </listitem>
 
 	    <listitem>
 	      <para>
 		<indexterm>
 		  <primary>electronic mail</primary>
 		  <see>email</see>
 		</indexterm>
 		<indexterm>
 		  <primary>email</primary>
 		</indexterm>
 		Email servers</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>And more...</para>
 	    </listitem>
 	  </itemizedlist>
 	</listitem>
 
 	<listitem>
 	  <para><emphasis>Education:</emphasis>  Are you a student of
 	    computer science or a related engineering field?  There
 	    is no better way of learning about operating systems,
 	    computer architecture and networking than the hands on,
 	    under the hood experience that &os; can provide.  A number
 	    of freely available CAD, mathematical and graphic design
 	    packages also make it highly useful to those whose primary
 	    interest in a computer is to get
 	    <emphasis>other</emphasis> work done!</para>
 	</listitem>
 
 	<listitem>
 	  <para><emphasis>Research:</emphasis>  With source code for
 	    the entire system available, &os; is an excellent platform
 	    for research in operating systems as well as other
 	    branches of computer science.  &os;'s freely available
 	    nature also makes it possible for remote groups to
 	    collaborate on ideas or shared development without having
 	    to worry about special licensing agreements or limitations
 	    on what may be discussed in open forums.</para>
 	</listitem>
 
 	<listitem>
 	  <para><emphasis>Networking:</emphasis> Need a new
 	    router?<indexterm>
 	      <primary>router</primary>
 	    </indexterm>  A name server (DNS)?<indexterm>
 	      <primary>DNS Server</primary>
 	    </indexterm>  A firewall to keep people out of your
 	    internal network?  &os; can easily turn that unused
 	    PC sitting in the corner into an advanced router with
 	    sophisticated packet-filtering capabilities.</para>
 	</listitem>
 
 	<listitem>
 	  <para><emphasis>Embedded:</emphasis> &os; makes an
 	    excellent platform to build embedded systems upon.
 	    <indexterm>
 	      <primary>embedded</primary>
 	    </indexterm>
 	    With support for the &arm;, &mips; and &powerpc;
 	    platforms, coupled with a robust network stack, cutting
 	    edge features and the permissive <link
 	      xlink:href="&url.books.faq;/introduction.html#bsd-license-restrictions">BSD
 	      license</link> &os; makes an excellent foundation for
 	    building embedded routers, firewalls, and other
 	    devices.</para>
 	</listitem>
 
 	<listitem>
 	  <para>
 	    <indexterm>
 	      <primary>X Window System</primary>
 	    </indexterm>
 	    <indexterm>
 	      <primary>GNOME</primary>
 	    </indexterm>
 	    <indexterm>
 	      <primary>KDE</primary>
 	    </indexterm>
 	    <emphasis>Desktop:</emphasis> &os; makes a
 	    fine choice for an inexpensive desktop solution
 	    using the freely available X11 server.
 	    &os; offers a choice from many open-source desktop
 	    environments, including the standard
 	    <application>GNOME</application> and
 	    <application>KDE</application> graphical user interfaces.
 	    &os; can even boot <quote>diskless</quote> from
 	    a central server, making individual workstations
 	    even cheaper and easier to administer.</para>
 	</listitem>
 
 	<listitem>
 	  <para><emphasis>Software Development:</emphasis>  The basic
 	    &os; system comes with a full suite of development
 	    tools including a full
 	    C/C++<indexterm>
 	      <primary>Compiler</primary>
 	    </indexterm>
 	    compiler and debugger suite.
 	    Support for many other languages are also available
 	    through the ports and packages collection.</para>
 	</listitem>
       </itemizedlist>
 
       <para>&os; is available to download free of charge, or can be
 	obtained on either CD-ROM or DVD.  Please see
 	<xref linkend="mirrors"/> for more information about obtaining
 	&os;.</para>
     </sect2>
 
     <sect2 xml:id="introduction-nutshell-users">
       <title>Who Uses &os;?</title>
 
       <indexterm>
 	<primary>users</primary>
 	<secondary>large sites running &os;</secondary>
       </indexterm>
 
       <para>&os; has been known for its web serving capabilities -
 	sites that run on &os; include
 	<link xlink:href="https://news.ycombinator.com/">Hacker News</link>,
 	<link xlink:href="http://www.netcraft.com/">Netcraft</link>,
 	<link xlink:href="http://www.163.com/">NetEase</link>,
 	<link xlink:href="https://signup.netflix.com/openconnect">Netflix</link>,
 	<link xlink:href="http://www.sina.com/">Sina</link>,
 	<link xlink:href="http://www.sony.co.jp/">Sony Japan</link>,
 	<link xlink:href="http://www.rambler.ru/">Rambler</link>,
 	<link xlink:href="http://www.yahoo.com/">Yahoo!</link>, and
 	<link xlink:href="http://www.yandex.ru/">Yandex</link>.
       </para>
 
       <para>&os;'s advanced features, proven security, predictable
 	release cycle, and permissive license have led to its use as a
 	platform for building many commercial and open source
 	appliances, devices, and products.  Many of the world's
 	largest IT companies use &os;:</para>
 
       <itemizedlist>
 	<listitem>
 
 	  <para><link
 	      xlink:href="http://www.apache.org/">Apache</link>
 	    <indexterm>
 	      <primary>Apache</primary>
 	    </indexterm> - The Apache Software Foundation runs most of
 	    its public facing infrastructure, including possibly one
 	    of the largest SVN repositories in the world with over 1.4
 	    million commits, on &os;.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.apple.com/">Apple</link>
 	    <indexterm>
 	      <primary>Apple</primary>
 	    </indexterm> - OS X borrows heavily from &os; for the
 	    network stack, virtual file system, and many userland
 	    components.  Apple iOS also contains elements borrowed
 	    from &os;.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.cisco.com/">Cisco</link>
 	    <indexterm>
 	      <primary>Cisco</primary>
 	    </indexterm> - IronPort network security and anti-spam
 	    appliances run a modified &os; kernel.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.citrix.com/">Citrix</link>
 	    <indexterm>
 	      <primary>Citrix</primary>
 	    </indexterm> - The NetScaler line of security appliances
 	    provide layer 4-7 load balancing, content caching,
 	    application firewall, secure VPN, and mobile cloud network
 	    access, along with the power of a &os; shell.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="https://www.emc.com/isilon">Dell EMC Isilon</link>
 	    <indexterm>
 	      <primary>Isilon</primary>
 	    </indexterm> - Isilon's enterprise storage appliances
 	    are based on &os;.  The extremely liberal &os; license
 	    allowed Isilon to integrate their intellectual property
 	    throughout the kernel and focus on building their product
 	    instead of an operating system.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link xlink:href="http://www.quest.com/KACE">Quest
 	      KACE</link>
 	    <indexterm>
 	      <primary>Quest KACE</primary>
 	    </indexterm> - The KACE system management appliances run
 	    &os; because of its reliability, scalability, and the
 	    community that supports its continued development.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.ixsystems.com/">iXsystems</link>
 	    <indexterm>
 	      <primary>iXsystems</primary>
 	    </indexterm> - The TrueNAS line of unified storage
 	    appliances is based on &os;.  In addition to their
 	    commercial products, iXsystems also manages development of
 	    the open source projects TrueOS and FreeNAS.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.juniper.net/">Juniper</link>
 	    <indexterm>
 	      <primary>Juniper</primary>
 	    </indexterm> - The JunOS operating system that powers all
 	    Juniper networking gear (including routers, switches,
 	    security, and networking appliances) is based on &os;.
 	    Juniper is one of many vendors that showcases the
 	    symbiotic relationship between the project and vendors of
 	    commercial products.  Improvements generated at Juniper
 	    are upstreamed into &os; to reduce the complexity of
 	    integrating new features from &os; back into JunOS in the
 	    future.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.mcafee.com/">McAfee</link>
 	    <indexterm>
 	      <primary>McAfee</primary>
 	    </indexterm> - SecurOS, the basis of McAfee enterprise
 	    firewall products including Sidewinder is based on
 	    &os;.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.netapp.com/">NetApp</link>
 	    <indexterm>
 	      <primary>NetApp</primary>
 	    </indexterm> - The Data ONTAP GX line of storage
 	    appliances are based on &os;.  In addition, NetApp has
 	    contributed back many features, including the new BSD
 	    licensed hypervisor, bhyve.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.netflix.com/">Netflix</link>
 	    <indexterm>
 	      <primary>Netflix</primary>
 	    </indexterm> - The OpenConnect appliance that Netflix
 	    uses to stream movies to its customers is based on &os;.
 	    Netflix has made extensive contributions to the codebase
 	    and works to maintain a zero delta from mainline &os;.
 	    Netflix OpenConnect appliances are responsible for
 	    delivering more than 32% of all Internet traffic in North
 	    America.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.sandvine.com/">Sandvine</link>
 	    <indexterm>
 	      <primary>Sandvine</primary>
 	    </indexterm> - Sandvine uses &os; as the basis of their
 	    high performance real-time network processing platforms
 	    that make up their intelligent network policy control
 	    products.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link xlink:href="http://www.sony.com/">Sony</link>
 	    <indexterm>
 	      <primary>Sony</primary>
 	    </indexterm> - The PlayStation 4 gaming console runs a
 	    modified version of &os;.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.sophos.com/">Sophos</link>
 	    <indexterm>
 	      <primary>Sophos</primary>
 	    </indexterm> - The Sophos Email Appliance product is based
 	    on a hardened &os; and scans inbound mail for spam and
 	    viruses, while also monitoring outbound mail for malware
 	    as well as the accidental loss of sensitive
 	    information.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.spectralogic.com/">Spectra
 	      Logic</link>
 	    <indexterm>
 	      <primary>Spectra Logic</primary>
 	    </indexterm> - The nTier line of archive grade storage
 	    appliances run &os; and OpenZFS.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="https://www.stormshield.eu">Stormshield</link>
 	    <indexterm>
 	      <primary>Stormshield</primary>
 
 	    </indexterm> - Stormshield Network Security appliances
 	    are based on a hardened version of &os;.  The BSD license
 	    allows them to integrate their own intellectual property with
 	    the system while returning a great deal of interesting
 	    development to the community.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link xlink:href="http://www.weather.com/">The Weather
 	      Channel</link>
 	    <indexterm>
 	      <primary>The Weather Channel</primary>
 
 	    </indexterm> - The IntelliStar appliance that is installed
 	    at each local cable provider's headend and is responsible
 	    for injecting local weather forecasts into the cable TV
 	    network's programming runs &os;.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.verisign.com/">Verisign</link>
 	    <indexterm>
 	      <primary>Verisign</primary>
 
 	    </indexterm> - Verisign is responsible for operating the
 	    .com and .net root domain registries as well as the
 	    accompanying DNS infrastructure.  They rely on a number of
 	    different network operating systems including &os; to
 	    ensure there is no common point of failure in their
 	    infrastructure.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.voxer.com/">Voxer</link>
 	    <indexterm>
 	      <primary>Voxer</primary>
 
 	    </indexterm> - Voxer powers their mobile voice messaging
 	    platform with ZFS on &os;.  Voxer switched from a Solaris
 	    derivative to &os; because of its superior documentation,
 	    larger and more active community, and more developer
 	    friendly environment.  In addition to critical features
 	    like <acronym>ZFS</acronym> and DTrace, &os; also offers
 	    TRIM support for <acronym>ZFS</acronym>.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link xlink:href="https://fudosecurity.com/en/">Fudo
 	      Security</link>
 	    <indexterm>
 	      <primary>Fudo Security</primary>
 
 	    </indexterm> - The FUDO security appliance allows
 	    enterprises to monitor, control, record, and audit
 	    contractors and administrators who work on their systems.
 	    Based on all of the best security features of &os;
 	    including ZFS, GELI, Capsicum, HAST, and
 	    auditdistd.</para>
 	</listitem>
       </itemizedlist>
 
       <para>&os; has also spawned a number of related open source
 	projects:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><link xlink:href="http://bsdrp.net/">BSD
 	      Router</link>
 	    <indexterm>
 	      <primary>BSD Router</primary>
 	    </indexterm> - A &os; based replacement for large
 	    enterprise routers designed to run on standard PC
 	    hardware.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.freenas.org/">FreeNAS</link>
 	    <indexterm>
 	      <primary>FreeNAS</primary>
 	    </indexterm> - A customized &os; designed to be used as a
 	    network file server appliance.  Provides a python based
 	    web interface to simplify the management of both the UFS
 	    and ZFS file systems.  Includes support for NFS, SMB/CIFS,
 	    AFP, FTP, and iSCSI.  Includes an extensible plugin system
 	    based on &os; jails.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="https://ghostbsd.org/">GhostBSD</link>
 	    <indexterm>
 	      <primary>GhostBSD</primary>
 	    </indexterm> - is derived from &os;, uses the GTK
 	    environment to provide a beautiful looks and comfortable
 	    experience on the modern BSD platform offering a natural
 	    and native &unix; work environment.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://mfsbsd.vx.sk/">mfsBSD</link>
 	    <indexterm>
 	      <primary>mfsBSD</primary>
 	    </indexterm> - A toolkit for building a &os; system image
 	    that runs entirely from memory.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.nas4free.org/">NAS4Free</link>
 	    <indexterm>
 	      <primary>NAS4Free</primary>
 	    </indexterm> - A file server distribution based on &os;
 	    with a PHP powered web interface.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.opnsense.org/">OPNSense</link>
 	    <indexterm>
 	      <primary>OPNsense</primary>
 	    </indexterm> - OPNsense is an open source, easy-to-use and
 	    easy-to-build FreeBSD based firewall and routing platform.
 	    OPNsense includes most of the features available in
 	    expensive commercial firewalls, and more in many cases.
 	    It brings the rich feature set of commercial offerings
 	    with the benefits of open and verifiable sources.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link
 	      xlink:href="https://www.trueos.org">TrueOS</link>
 	    <indexterm>
 	      <primary>TrueOS</primary>
 	    </indexterm> - TrueOS is based on the legendary security
 	    and stability of &os;.  TrueOS follows &os;-CURRENT, with
 	    the latest drivers, security updates, and packages
 	    available.</para>
 	</listitem>
 
-	<listitem>
-	  <para><link
-	      xlink:href="https://www.furybsd.org">FuryBSD</link>
-	    <indexterm>
-	      <primary>FuryBSD</primary>
-	    </indexterm> - is a brand new, open source &os; desktop.
-	    FuryBSD pays homage to desktop BSD projects of the past
-	    like PC-BSD and TrueOS with its graphical interface and
-	    adds additional tools like a live, hybrid USB/DVD image.
-	    FuryBSD is completely free to use and distributed under
-	    the BSD license.</para>
-	</listitem>
-
 	<listitem>
 	  <para><link
 	      xlink:href="https://www.midnightbsd.org">MidnightBSD</link>
 	    <indexterm>
 	      <primary>MidnightBSD</primary>
 	    </indexterm> - is a &os; derived operating system
 	    developed with desktop users in mind.  It includes all the
 	    software you'd expect for your daily tasks: mail,
 	    web browsing, word processing, gaming, and much
 	    more.</para>
 	</listitem>
 
+	<listitem>
+	  <para><link
+	      xlink:href="https://nomadbsd.org/">NomadBSD</link>
+	    <indexterm>
+	      <primary>NomadBSD</primary>
+	    </indexterm> - is a persistent live system for USB flash
+	    drives, based on &os;. Together with automatic hardware
+	    detection and setup, it is configured to be used as a
+	    desktop system that works out of the box, but can also be
+	    used for data recovery, for educational purposes, or to
+	    test &os;'s hardware compatibility.</para>
+	</listitem>
+
 	<listitem>
 	  <para><link
 	      xlink:href="http://www.pfsense.org/">pfSense</link>
 	    <indexterm>
 	      <primary>pfSense</primary>
 	    </indexterm> - A firewall distribution based on &os; with
 	    a huge array of features and extensive IPv6
 	    support.</para>
 	</listitem>
 
 	<listitem>
 	  <para><link xlink:href="http://zrouter.org/">ZRouter</link>
 	    <indexterm>
 	      <primary>ZRouter</primary>
 	    </indexterm> - An open source alternative firmware for
 	    embedded devices based on &os;.  Designed to replace the
 	    proprietary firmware on off-the-shelf routers.</para>
 	</listitem>
       </itemizedlist>
 
       <para>A list of <link
 	  xlink:href="https://www.freebsdfoundation.org/about/testimonials/">
 	  testimonials from companies basing their products and
 	  services on &os;</link> can be found at the FreeBSD
 	  Foundation website.  Wikipedia also maintains a <link
 	  xlink:href="https://en.wikipedia.org/wiki/List_of_products_based_on_FreeBSD">list
 	  of products based on &os;</link>.</para>
 
     </sect2>
   </sect1>
 
   <sect1 xml:id="history">
     <title>About the &os;&nbsp;Project</title>
 
     <para>The following section provides some background information
       on the project, including a brief history, project goals, and
       the development model of the project.</para>
 
     <sect2 xml:id="intro-history">
       <title>A Brief History of &os;</title>
 
       <indexterm><primary>386BSD Patchkit</primary></indexterm>
       <indexterm><primary>Hubbard, Jordan</primary></indexterm>
       <indexterm><primary>Williams, Nate</primary></indexterm>
       <indexterm><primary>Grimes, Rod</primary></indexterm>
       <indexterm>
 	<primary>FreeBSD Project</primary>
 	<secondary>history</secondary>
       </indexterm>
 
       <para>The &os;&nbsp;Project had its genesis in the early part
 	of 1993, partially as the brainchild of the Unofficial
 	386BSDPatchkit's last 3 coordinators: Nate Williams,
 	Rod Grimes and Jordan Hubbard.</para>
 
       <indexterm><primary>386BSD</primary></indexterm>
       <para>The original goal was to produce an intermediate snapshot
 	of 386BSD in order to fix a number of problems that
 	the patchkit mechanism was just not capable of solving.  The
 	early working title for the project was 386BSD 0.5 or 386BSD
 	Interim in reference of that fact.</para>
 
       <indexterm><primary>Jolitz, Bill</primary></indexterm>
       <para>386BSD was Bill Jolitz's operating system, which had been
 	up to that point suffering rather severely from almost a
 	year's worth of neglect.  As the patchkit swelled ever more
 	uncomfortably with each passing day, they decided to assist
 	Bill by providing this interim <quote>cleanup</quote>
 	snapshot.  Those plans came to a rude halt when Bill Jolitz
 	suddenly decided to withdraw his sanction from the project
 	without any clear indication of what would be done
 	instead.</para>
 
       <indexterm><primary>Greenman, David</primary></indexterm>
       <indexterm><primary>Walnut Creek CDROM</primary></indexterm>
 
       <para>The trio thought that the goal remained worthwhile, even
 	without Bill's support, and so they adopted the name "&os;"
 	coined by David Greenman.  The initial objectives were set
 	after consulting with the system's current users and, once it
 	became clear that the project was on the road to perhaps even
 	becoming a reality, Jordan contacted Walnut Creek CDROM with
 	an eye toward improving &os;'s distribution channels for those
 	many unfortunates without easy access to the Internet.  Walnut
 	Creek CDROM not only supported the idea of distributing &os;
 	on CD but also went so far as to provide the project with a
 	machine to work on and a fast Internet connection.  Without
 	Walnut Creek CDROM's almost unprecedented degree of faith in
 	what was, at the time, a completely unknown project, it is
 	quite unlikely that &os; would have gotten as far, as fast, as
 	it has today.</para>
 
       <indexterm><primary>4.3BSD-Lite</primary></indexterm>
       <indexterm><primary>Net/2</primary></indexterm>
       <indexterm><primary>U.C. Berkeley</primary></indexterm>
       <indexterm><primary>386BSD</primary></indexterm>
       <indexterm><primary>Free Software
 	  Foundation</primary></indexterm>
       <para>The first CD-ROM (and general net-wide) distribution was
 	&os;&nbsp;1.0, released in December of 1993.  This was based
 	on the 4.3BSD-Lite (<quote>Net/2</quote>) tape from U.C.
 	Berkeley, with many components also provided by 386BSD and the
 	Free Software Foundation.  It was a fairly reasonable success
 	for a first offering, and they followed it with the highly
 	successful &os; 1.1 release in May of 1994.</para>
 
       <indexterm><primary>Novell</primary></indexterm>
       <indexterm><primary>U.C. Berkeley</primary></indexterm>
       <indexterm><primary>Net/2</primary></indexterm>
       <indexterm><primary>AT&amp;T</primary></indexterm>
       <para>Around this time, some rather unexpected storm clouds
 	formed on the horizon as Novell and U.C. Berkeley settled
 	their long-running lawsuit over the legal status of the
 	Berkeley Net/2 tape.  A condition of that settlement was U.C.
 	Berkeley's concession that large parts of Net/2 were
 	<quote>encumbered</quote> code and the property of Novell, who
 	had in turn acquired it from AT&amp;T some time previously.
 	What Berkeley got in return was Novell's
 	<quote>blessing</quote> that the 4.4BSD-Lite release, when
 	it was finally released, would be declared unencumbered and
 	all existing Net/2 users would be strongly encouraged to
 	switch.  This included &os;, and the project was given until
 	the end of July 1994 to stop shipping its own Net/2 based
 	product.  Under the terms of that agreement, the project was
 	allowed one last release before the deadline, that release
 	being &os;&nbsp;1.1.5.1.</para>
 
       <para>&os; then set about the arduous task of literally
 	re-inventing itself from a completely new and rather
 	incomplete set of 4.4BSD-Lite bits.  The <quote>Lite</quote>
 	releases were light in part because Berkeley's CSRG had
 	removed large chunks of code required for actually
 	constructing a bootable running system (due to various legal
 	requirements) and the fact that the Intel port of 4.4 was
 	highly incomplete.  It took the project until November of 1994
 	to make this transition, and in December it released
 	&os;&nbsp;2.0 to the world.  Despite being still more than a
 	little rough around the edges, the release was a significant
 	success and was followed by the more robust and easier to
 	install &os;&nbsp;2.0.5 release in June of 1995.</para>
 
       <para>Since that time, &os; has made a series of releases each
 	time improving the stability, speed, and feature set of the
 	previous version.</para>
 
       <para>For now, long-term development projects continue to take
 	place in the 10.X-CURRENT (trunk) branch, and snapshot
 	releases of 10.X are continually made available from <link
 	  xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/">the
 	  snapshot server</link> as work progresses.</para>
     </sect2>
 
     <sect2 xml:id="goals">
       <info>
 	<title>&os;&nbsp;Project Goals</title>
 
 	<authorgroup>
 	  <author>
 	    <personname>
 	      <firstname>Jordan</firstname>
 	      <surname>Hubbard</surname>
 	    </personname>
 	    <contrib>Contributed by </contrib>
 	  </author>
 	</authorgroup>
       </info>
 
       <indexterm>
 	<primary>FreeBSD Project</primary>
 	<secondary>goals</secondary>
       </indexterm>
       <para>The goals of the &os;&nbsp;Project are to provide software
 	that may be used for any purpose and without strings attached.
 	Many of us have a significant investment in the code (and
 	project) and would certainly not mind a little financial
 	compensation now and then, but we are definitely not prepared
 	to insist on it.  We believe that our first and foremost
 	<quote>mission</quote> is to provide code to any and all
 	comers, and for whatever purpose, so that the code gets the
 	widest possible use and provides the widest possible benefit.
 	This is, I believe, one of the most fundamental goals of Free
 	Software and one that we enthusiastically support.</para>
 
       <indexterm>
 	<primary>GNU General Public License (GPL)</primary>
       </indexterm>
       <indexterm>
 	<primary>GNU Lesser General Public License (LGPL)</primary>
       </indexterm>
       <indexterm><primary>BSD Copyright</primary></indexterm>
       <para>That code in our source tree which falls under the GNU
 	General Public License (GPL) or Library General Public License
 	(LGPL) comes with slightly more strings attached, though at
 	least on the side of enforced access rather than the usual
 	opposite.  Due to the additional complexities that can evolve
 	in the commercial use of GPL software we do, however, prefer
 	software submitted under the more relaxed BSD license when
 	it is a reasonable option to do so.</para>
     </sect2>
 
     <sect2 xml:id="development">
       <info>
 	<title>The &os; Development Model</title>
 
 	<authorgroup>
 	  <author>
 	    <personname>
 	      <firstname>Satoshi</firstname>
 	      <surname>Asami</surname>
 	    </personname>
 	    <contrib>Contributed by </contrib>
 	  </author>
 	</authorgroup>
       </info>
 
       <indexterm>
 	<primary>FreeBSD Project</primary>
 	<secondary>development model</secondary>
       </indexterm>
 
       <para>The development of &os; is a very open and flexible
 	process, being literally built from the contributions of
 	thousands of people around the world, as can be seen from our
 	<link
 	  xlink:href="&url.articles.contributors;/article.html">list
 	  of contributors</link>.  &os;'s development infrastructure
 	allow these thousands of contributors to collaborate over the
 	Internet.  We are constantly on the lookout for new developers
 	and ideas, and those interested in becoming more closely
 	involved with the project need simply contact us at the
 	&a.hackers;.  The &a.announce; is also available to those
 	wishing to make other &os; users aware of major areas of
 	work.</para>
 
       <para>Useful things to know about the &os;&nbsp;Project and its
 	development process, whether working independently or in close
 	cooperation:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>The SVN repositories<anchor
 	    xml:id="development-cvs-repository"/></term>
 
 	  <listitem>
 	    <para>
 	      <indexterm>
 		<primary>CVS</primary>
 	      </indexterm>
 
 	      <indexterm>
 		<primary>CVS Repository</primary>
 	      </indexterm>
 
 	      <indexterm>
 		<primary>Concurrent Versions System</primary>
 		<see>CVS</see>
 	      </indexterm>
 
 	      <indexterm>
 		<primary>Subversion</primary>
 	      </indexterm>
 
 	      <indexterm>
 		<primary>Subversion Repository</primary>
 	      </indexterm>
 
 	      <indexterm>
 		<primary>SVN</primary>
 		<see>Subversion</see>
 	      </indexterm>
 	      For several years, the central source tree for &os;
 	      was maintained by
 	      <link xlink:href="http://www.nongnu.org/cvs/">CVS</link>
 	      (Concurrent Versions System), a freely available source
 	      code control tool.  In June 2008, the Project switched
 	      to using <link
 		xlink:href="http://subversion.tigris.org">SVN</link>
 	      (Subversion).  The switch was deemed necessary, as the
 	      technical limitations imposed by
 	      <application>CVS</application> were becoming obvious due
 	      to the rapid expansion of the source tree and the amount
 	      of history already stored.  The Documentation Project
 	      and Ports Collection repositories also moved from
 	      <application>CVS</application> to
 	      <application>SVN</application> in May 2012 and July
 	        2012, respectively.  Please refer to the <link
 		linkend="synching">Obtaining the Source</link>
 		section for more information on obtaining the
 		&os; <literal>src/</literal> repository and <link
 		linkend="ports-using">Using the Ports
 		Collection</link> for details on obtaining the &os;
 	      Ports Collection.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>The committers list<anchor
 	    xml:id="development-committers"/></term>
 
 	  <listitem>
 	    <para>The <firstterm>committers</firstterm>
 	      <indexterm>
 		<primary>committers</primary>
 	      </indexterm> are the people who have
 	      <emphasis>write</emphasis> access to the Subversion
 	      tree, and are authorized to make modifications to the
 	      &os; source (the term <quote>committer</quote> comes
 	      from <command>commit</command>, the source control
 	      command which is used to bring new changes into the
 	      repository).  Anyone can submit a bug to the <link
 		xlink:href="https://bugs.FreeBSD.org/submit/">Bug
 	      Database</link>.  Before submitting a bug report, the
 	    &os; mailing lists, IRC channels, or forums can be used to
 	    help verify that an issue is actually a bug.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>The FreeBSD core team<anchor
 	    xml:id="development-core"/></term>
 
 	  <listitem>
 	    <para>The <firstterm>&os; core team</firstterm>
 	      <indexterm>
 		<primary>core team</primary>
 	      </indexterm> would be equivalent to the board of
 	      directors if the &os;&nbsp;Project were a company.  The
 	      primary task of the core team is to make sure the
 	      project, as a whole, is in good shape and is heading in
 	      the right directions.  Inviting dedicated and
 	      responsible developers to join our group of committers
 	      is one of the functions of the core team, as is the
 	      recruitment of new core team members as others move on.
 	      The current core team was elected from a pool of
 	      committer candidates in June 2020.  Elections are held
 	      every 2 years.</para>
 
 	    <note>
 	      <para>Like most developers, most members of the
 		core team are also volunteers when
 		it comes to &os; development and do not benefit from
 		the project financially, so <quote>commitment</quote>
 		should also not be misconstrued as meaning
 		<quote>guaranteed support.</quote>  The
 		<quote>board of directors</quote> analogy above is not
 		very accurate, and it may be more suitable to say that
 		these are the people who gave up their lives in favor
 		of &os; against their better judgement!</para>
 	    </note>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Outside contributors</term>
 
 	  <listitem>
 	    <para>Last, but definitely not least, the largest group of
 	      developers are the users themselves who provide feedback
 	      and bug fixes to us on an almost constant basis.  The
 	      primary way of keeping in touch with &os;'s more
 	      non-centralized development is to subscribe to the
 	      &a.hackers; where such things are discussed.  See
 	      <xref linkend="eresources"/> for more information about
 	      the various &os; mailing lists.</para>
 
 	    <para><citetitle><link
 		  xlink:href="&url.articles.contributors;/article.html">The
 		  &os; Contributors List</link></citetitle>
 	      <indexterm>
 		<primary>contributors</primary>
 	      </indexterm> is a long and growing one, so why not join
 	      it by contributing something back to &os; today?</para>
 
 	    <para>Providing code is not the only way of contributing
 	      to the project; for a more complete list of things that
 	      need doing, please refer to the <link
 		xlink:href="&url.base;/index.html">&os;&nbsp;Project
 		web site</link>.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>In summary, our development model is organized as a loose
 	set of concentric circles.  The centralized model is designed
 	for the convenience of the <emphasis>users</emphasis> of &os;,
 	who are provided with an easy way of tracking one central code
 	base, not to keep potential contributors out! Our desire is to
 	present a stable operating system with a large set of coherent
 	<link linkend="ports">application programs</link> that the
 	users can easily install and use &mdash; this model works very
 	well in accomplishing that.</para>
 
       <para>All we ask of those who would join us as &os; developers
 	is some of the same dedication its current people have to its
 	continued success!</para>
     </sect2>
 
     <sect2 xml:id="third-party-programs">
       <title>Third Party Programs</title>
 
       <para>In addition to the base distributions, &os; offers a
 	ported software collection with thousands of commonly
 	sought-after programs.  At the time of this writing, there
 	were over &os.numports; ports!  The list of ports ranges from
 	http servers, to games, languages, editors, and almost
 	everything in between.  The entire Ports Collection requires
 	approximately &ports.size;.  To compile a port, you simply
 	change to the directory of the program you wish to install,
 	type <command>make install</command>, and let the system do
 	the rest.  The full original distribution for each port you
 	build is retrieved dynamically so you need only enough disk
 	space to build the ports you want.  Almost every port is also
 	provided as a pre-compiled <quote>package</quote>, which can
 	be installed with a simple command
 	(<command>pkg install</command>) by those who do not wish to
 	compile their own ports from source.  More information on
 	packages and ports can be found in
 	<xref linkend="ports"/>.</para>
     </sect2>
 
     <sect2>
       <title>Additional Documentation</title>
 
       <para>All supported &os; versions provide an option in the
 	installer to
 	install additional documentation under
 	<filename>/usr/local/share/doc/freebsd</filename> during the
 	initial system setup.  Documentation may also be installed at
 	any later time using packages as described in
 	<xref linkend="doc-ports-install-package"/>.  You may view the
 	locally installed manuals with any HTML capable browser using
 	the following URLs:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>The FreeBSD Handbook</term>
 
 	  <listitem>
 	    <para><link
 		xlink:href="file://localhost/usr/local/share/doc/freebsd/handbook/index.html"><filename>/usr/local/share/doc/freebsd/handbook/index.html</filename></link></para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>The FreeBSD FAQ</term>
 
 	  <listitem>
 	    <para><link
 		xlink:href="file://localhost/usr/local/share/doc/freebsd/faq/index.html"><filename>/usr/local/share/doc/freebsd/faq/index.html</filename></link></para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>You can also view the master (and most frequently updated)
 	copies at <uri
 	  xlink:href="https://www.FreeBSD.org/">https://www.FreeBSD.org/</uri>.</para>
     </sect2>
   </sect1>
 </chapter>
diff --git a/en_US.ISO8859-1/books/handbook/x11/chapter.xml b/en_US.ISO8859-1/books/handbook/x11/chapter.xml
index 0ebd1bb20f..41c753186e 100644
--- a/en_US.ISO8859-1/books/handbook/x11/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/x11/chapter.xml
@@ -1,2226 +1,2228 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 <chapter xmlns="http://docbook.org/ns/docbook"
   xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
   xml:id="x11">
   <!--
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Ken</firstname>
 	<surname>Tom</surname>
 	<contrib>Updated for X.Org's X11 server by </contrib>
       </author>
       <author>
 	<firstname>Marc</firstname>
 	<surname>Fonvieille</surname>
       </author>
     </authorgroup>
   </chapterinfo>
   -->
 
   <title>The X Window System</title>
 
   <sect1 xml:id="x11-synopsis">
     <title>Synopsis</title>
 
     <para>An installation of &os; using
       <application>bsdinstall</application> does not automatically
       install a graphical user interface.  This chapter describes how
       to install and configure <application>&xorg;</application>,
       which provides the open source X Window System used to provide a
       graphical environment.  It then describes how to find and
       install a desktop environment or window manager.</para>
 
     <note>
       <para>Users who prefer an installation method that automatically
 	configures the <application>&xorg;</application> should refer
-	to <link xlink:href="https://www.furybsd.org">FuryBSD</link>,
-	<link xlink:href="https://ghostbsd.org">GhostBSD</link> or
+	to <link xlink:href="https://ghostbsd.org">GhostBSD</link>,
 	<link
-	  xlink:href="https://www.midnightbsd.org">MidnightBSD</link>.</para>
+	  xlink:href="https://www.midnightbsd.org">MidnightBSD</link>
+	  or
+	<link
+	  xlink:href="https://nomadbsd.org/">NomadBSD</link>.</para>
     </note>
 
     <para>For more information on the video hardware that
       <application>&xorg;</application> supports, refer to the <link
 	xlink:href="http://www.x.org/">x.org</link> website.</para>
 
     <para>After reading this chapter, you will know:</para>
 
     <itemizedlist>
       <listitem>
 	<para>The various components of the X Window System, and how
 	  they interoperate.</para>
       </listitem>
 
       <listitem>
 	<para>How to install and configure
 	  <application>&xorg;</application>.</para>
       </listitem>
 
       <listitem>
 	<para>How to install and configure several window managers
 	  and desktop environments.</para>
       </listitem>
 
       <listitem>
 	<para>How to use &truetype; fonts in
 	  <application>&xorg;</application>.</para>
       </listitem>
 
       <listitem>
 	<para>How to set up your system for graphical logins
 	  (<application>XDM</application>).</para>
       </listitem>
     </itemizedlist>
 
     <para>Before reading this chapter, you should:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Know how to install additional third-party
 	  software as described in <xref linkend="ports"/>.</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 xml:id="x-understanding">
     <title>Terminology</title>
 
     <para>While it is not necessary to understand all of the details
       of the various components in the X Window System and how they
       interact, some basic knowledge of these components can be
       useful.</para>
 
     <variablelist>
       <varlistentry>
 	<term>X server</term>
 
 	<listitem>
 	  <para>X was designed from the beginning to be
 	    network-centric, and adopts a <quote>client-server</quote>
 	    model.  In this model, the <quote>X server</quote> runs on
 	    the computer that has the keyboard, monitor, and mouse
 	    attached.  The server's responsibility includes tasks such
 	    as managing the display, handling input from the keyboard
 	    and mouse, and handling input or output from other devices
 	    such as a tablet or a video projector.  This confuses some
 	    people, because the X terminology is exactly backward to
 	    what they expect.  They expect the <quote>X server</quote>
 	    to be the big powerful machine down the hall, and the
 	    <quote>X client</quote> to be the machine on their
 	    desk.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>X client</term>
 
 	<listitem>
 	  <para>Each X application, such as
 	    <application>XTerm</application> or
 	    <application>Firefox</application>, is a
 	    <quote>client</quote>.  A client sends messages to the
 	    server such as <quote>Please draw a window at these
 	      coordinates</quote>, and the server sends back messages
 	    such as <quote>The user just clicked on the OK
 	      button</quote>.</para>
 
 	  <para>In a home or small office environment, the X server
 	    and the X clients commonly run on the same computer.  It
 	    is also possible to run the X server on a less powerful
 	    computer and to run the X applications on a more powerful
 	    system.  In this scenario, the communication between the X
 	    client and server takes place over the network.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>window manager</term>
 
 	<listitem>
 	  <para>X does not dictate what windows should look like
 	    on-screen, how to move them around with the mouse, which
 	    keystrokes should be used to move between windows, what
 	    the title bars on each window should look like, whether or
 	    not they have close buttons on them, and so on.  Instead,
 	    X delegates this responsibility to a separate window
 	    manager application.  There are <link
 	      xlink:href="http://www.xwinman.org/">dozens of window
 	      managers</link> available.  Each window manager provides
 	    a different look and feel: some support virtual desktops,
 	    some allow customized keystrokes to manage the desktop,
 	    some have a <quote>Start</quote> button, and some are
 	    themeable, allowing a complete change of the desktop's
 	    look-and-feel.  Window managers are available in the
 	    <filename>x11-wm</filename> category of the Ports
 	    Collection.</para>
 
 	  <para>Each window manager uses a different configuration
 	    mechanism.  Some expect configuration file written by hand
 	    while others provide graphical tools for most
 	    configuration tasks.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>desktop environment</term>
 
 	<listitem>
 	  <para><application>KDE</application> and
 	    <application>GNOME</application> are considered to be
 	    desktop environments as they include an entire suite of
 	    applications for performing common desktop tasks.  These
 	    may include office suites, web browsers, and games.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>focus policy</term>
 
 	<listitem>
 	  <para>The window manager is responsible for the mouse focus
 	    policy.  This policy provides some means for choosing
 	    which window is actively receiving keystrokes and it
 	    should also visibly indicate which window is currently
 	    active.</para>
 
 	  <para>One focus policy is called
 	    <quote>click-to-focus</quote>.  In this model, a window
 	    becomes active upon receiving a mouse click.  In the
 	    <quote>focus-follows-mouse</quote> policy, the window that
 	    is under the mouse pointer has focus and the focus is
 	    changed by pointing at another window.  If the mouse is
 	    over the root window, then this window is focused.  In the
 	    <quote>sloppy-focus</quote> model, if the mouse is moved
 	    over the root window, the most recently used window still
 	    has the focus.  With sloppy-focus, focus is only changed
 	    when the cursor enters a new window, and not when exiting
 	    the current window.  In the <quote>click-to-focus</quote>
 	    policy, the active window is selected by mouse click.  The
 	    window may then be raised and appear in front of all other
 	    windows.  All keystrokes will now be directed to this
 	    window, even if the cursor is moved to another
 	    window.</para>
 
 	  <para>Different window managers support different focus
 	    models.  All of them support click-to-focus, and the
 	    majority of them also support other policies.  Consult the
 	    documentation for the window manager to determine which
 	    focus models are available.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>widgets</term>
 
 	<listitem>
 	  <para>Widget is a term for all of the items in the user
 	    interface that can be clicked or manipulated in some way.
 	    This includes buttons, check boxes, radio buttons, icons,
 	    and lists.  A widget toolkit is a set of widgets used to
 	    create graphical applications.  There are several popular
 	    widget toolkits, including Qt, used by
 	    <application>KDE</application>, and GTK+, used by
 	    <application>GNOME</application>.  As a result,
 	    applications will have a different look and feel,
 	    depending upon which widget toolkit was used to create the
 	    application.</para>
 	</listitem>
       </varlistentry>
     </variablelist>
   </sect1>
 
   <sect1 xml:id="x-install">
     <title>Installing <application>&xorg;</application></title>
 
     <para>On &os;, <application>&xorg;</application> can be installed
       as a package or port.</para>
 
     <para>The binary package can be installed quickly but with
       fewer options for customization:</para>
 
     <screen>&prompt.root; <userinput>pkg install xorg</userinput></screen>
 
     <para>To build and install from the Ports Collection:</para>
 
     <screen>&prompt.root; <userinput>cd /usr/ports/x11/xorg</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
     <para>Either of these installations results in the complete
       <application>&xorg;</application> system being installed.
       Binary packages are the best option for most users.</para>
 
     <para>A smaller version of the X system suitable for experienced
       users is available in <package>x11/xorg-minimal</package>.  Most
       of the documents, libraries, and applications will not be
       installed.  Some applications require these additional
       components to function.</para>
   </sect1>
 
   <sect1 xml:id="x-config">
     <title><application>&xorg;</application> Configuration</title>
 
     <info>
       <authorgroup>
 	<author>
 	  <personname>
 	    <firstname>Warren</firstname>
 	    <surname>Block</surname>
 	  </personname>
 	  <contrib>Originally contributed by </contrib>
 	</author>
       </authorgroup>
     </info>
 
     <indexterm><primary>&xorg;</primary></indexterm>
     <indexterm><primary><application>&xorg;</application></primary></indexterm>
 
     <sect2 xml:id="x-config-quick-start">
       <title>Quick Start</title>
 
       <para><application>&xorg;</application> supports most common
 	video cards, keyboards, and pointing devices.</para>
 
       <tip>
 	<para>Video cards, monitors, and input devices are
 	  automatically detected and do not require any manual
 	  configuration.  Do not create <filename>xorg.conf</filename>
 	  or run a <option>-configure</option> step unless automatic
 	  configuration fails.</para>
       </tip>
 
       <procedure>
 	<step>
 	  <para>If <application>&xorg;</application> has been used on
 	    this computer before, move or remove any existing
 	    configuration files:</para>
 
 	  <screen>&prompt.root; <userinput>mv /etc/X11/xorg.conf ~/xorg.conf.etc</userinput>
 &prompt.root; <userinput>mv /usr/local/etc/X11/xorg.conf ~/xorg.conf.localetc</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Add the user who will run
 	    <application>&xorg;</application> to the
 	    <systemitem class="groupname">video</systemitem> or
 	    <systemitem class="groupname">wheel</systemitem> group to
 	    enable 3D acceleration when available.  To add user
 	    <replaceable>jru</replaceable> to whichever group is
 	    available:</para>
 
 	  <screen>&prompt.root; <userinput>pw groupmod video -m <replaceable>jru</replaceable> || pw groupmod wheel -m <replaceable>jru</replaceable></userinput></screen>
 	</step>
 
 	<step>
 	  <para>The <application>twm</application> window manager is
 	    included by default.  It is started when
 	    <application>&xorg;</application> starts:</para>
 
 	  <screen>&prompt.user; <userinput>startx</userinput></screen>
 	</step>
 
 	<step>
 	  <para>On some older versions of &os;, the system console
 	    must be set to &man.vt.4; before switching back to the
 	    text console will work properly.  See
 	    <xref linkend="x-config-kms"/>.</para>
 	</step>
       </procedure>
     </sect2>
 
     <sect2 xml:id="x-config-user-group">
       <title>User Group for Accelerated Video</title>
 
       <para>Access to <filename>/dev/dri</filename> is needed to allow
 	3D acceleration on video cards.  It is usually simplest to add
 	the user who will be running X to either the <systemitem
 	  class="groupname">video</systemitem> or <systemitem
 	  class="groupname">wheel</systemitem> group.  Here,
 	&man.pw.8; is used to add user
 	<replaceable>slurms</replaceable> to the
 	<systemitem class="groupname">video</systemitem> group, or to
 	the <systemitem class="groupname">wheel</systemitem> group if
 	there is no <systemitem class="groupname">video</systemitem>
 	group:</para>
 
       <screen>&prompt.root; <userinput>pw groupmod video -m <replaceable>slurms</replaceable> || pw groupmod wheel -m <replaceable>slurms</replaceable></userinput></screen>
     </sect2>
 
     <sect2 xml:id="x-config-kms">
       <title>Kernel Mode Setting (<acronym>KMS</acronym>)</title>
 
       <para>When the computer switches from displaying the console to
 	a higher screen resolution for X, it must set the video
 	output <emphasis>mode</emphasis>.  Recent versions of
 	<acronym>&xorg;</acronym> use a system inside the kernel to do
 	these mode changes more efficiently.  Older versions of &os;
 	use &man.sc.4;, which is not aware of the
 	<acronym>KMS</acronym> system.  The end result is that after
 	closing X, the system console is blank, even though it is
 	still working.  The newer &man.vt.4; console avoids this
 	problem.</para>
 
       <para>Add this line to <filename>/boot/loader.conf</filename>
 	to enable &man.vt.4;:</para>
 
       <programlisting>kern.vty=vt</programlisting>
     </sect2>
 
     <sect2 xml:id="x-config-files">
       <title>Configuration Files</title>
 
       <para>Manual configuration is usually not necessary.  Please do
 	not manually create configuration files unless
 	autoconfiguration does not work.</para>
 
       <sect3 xml:id="x-config-files-directory">
 	<title>Directory</title>
 
 	<para><application>&xorg;</application> looks in several
 	  directories for configuration files.
 	  <filename>/usr/local/etc/X11/</filename> is the recommended
 	  directory for these files on &os;.  Using this directory
 	  helps keep application files separate from operating system
 	  files.</para>
 
 	<para>Storing configuration files in the legacy
 	  <filename>/etc/X11/</filename> still works.  However, this
 	  mixes application files with the base &os; files and is not
 	  recommended.</para>
       </sect3>
 
       <sect3 xml:id="x-config-files-single-or-multi">
 	<title>Single or Multiple Files</title>
 
 	<para>It is easier to use multiple files that each configure a
 	  specific setting than the traditional single
 	  <filename>xorg.conf</filename>.  These files are stored in
 	  the <filename>xorg.conf.d/</filename> subdirectory of the
 	  main configuration file directory.  The full path is
 	  typically
 	  <filename>/usr/local/etc/X11/xorg.conf.d/</filename>.</para>
 
 	<para>Examples of these files are shown later in this
 	  section.</para>
 
 	<para>The traditional single <filename>xorg.conf</filename>
 	  still works, but is neither as clear nor as flexible as
 	  multiple files in the <filename>xorg.conf.d/</filename>
 	  subdirectory.</para>
       </sect3>
     </sect2>
 
     <sect2 xml:id="x-config-video-cards">
       <title>Video Cards</title>
 
       <para>Because of changes made in recent versions of &os;, it
 	is now possible to use graphics drivers provided by the Ports
 	framework or as packages.  As such, users can use one of the
 	following drivers available from
 	<package>graphics/drm-kmod</package>.</para>
 
       <variablelist>
 	<varlistentry xml:id="x-config-video-cards-ports">
 	  <term>&i915kms;</term>
 	  <term>&radeonkms;</term>
 	  <term>&amdgpu;</term>
 
 	  <listitem>
 	    <para>2D and 3D acceleration is supported on most
 	      &i915kms; graphics cards provided by &intel;.</para>
 
 	    <para>Driver name: <literal>i915kms</literal></para>
 
 	    <para>2D and 3D acceleration is supported on most older
 	      &radeonkms; graphics cards provided by &amd;.</para>
 
 	    <para>Driver name: <literal>radeonkms</literal></para>
 
 	    <para>2D and 3D acceleration is supported on most newer
 	      &amdgpu; graphics cards provided by &amd;..</para>
 
 	    <para>Driver name: <literal>amdgpu</literal></para>
 
 	    <para>For reference, please see <link
 		xlink:href="https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units"/>
 	      or <link
 		xlink:href="https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units"/>
 	      for a list of supported GPUs.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry xml:id="x-config-video-cards-intel">
 	  <term>&intel;</term>
 
 	  <listitem>
 	    <para>3D acceleration is supported on most &intel;
 	      graphics up to Ivy Bridge (HD Graphics 2500, 4000, and
 	      P4000), including Iron Lake (HD Graphics) and
 	      Sandy Bridge (HD Graphics 2000).</para>
 
 	    <para>Driver name: <literal>intel</literal></para>
 
 	    <para>For reference, see <link
 	      xlink:href="https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units"/>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry xml:id="x-config-video-cards-radeon">
 	  <term>&amd; Radeon</term>
 
 	  <listitem>
 	    <para>2D and 3D acceleration is supported on Radeon
 	      cards up to and including the HD6000 series.</para>
 
 	    <para>Driver name: <literal>radeon</literal></para>
 
 	    <para>For reference, see <link
 		xlink:href="https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units"/>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry xml:id="x-config-video-cards-nvidia">
 	  <term>NVIDIA</term>
 
 	  <listitem>
 	    <para>Several NVIDIA drivers are available in the
 	      <filename>x11</filename> category of the Ports
 	      Collection.  Install the driver that matches the video
 	      card.</para>
 
 	    <para>For reference, see <link
 		xlink:href="https://en.wikipedia.org/wiki/List_of_Nvidia_graphics_processing_units"/>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry xml:id="x-config-video-cards-hybrid">
 	  <term>Hybrid Combination Graphics</term>
 
 	  <listitem>
 	    <para>Some notebook computers add additional graphics
 	      processing units to those built into the chipset or
 	      processor.  <emphasis>Optimus</emphasis> combines
 	      &intel; and NVIDIA hardware.
 	      <emphasis>Switchable Graphics</emphasis> or
 	      <emphasis>Hybrid Graphics</emphasis> are a combination
 	      of an &intel; or &amd; processor and an &amd; Radeon
 	      <acronym>GPU</acronym>.</para>
 
 	    <para>Implementations of these hybrid graphics systems
 	      vary, and <application>&xorg;</application> on &os; is
 	      not able to drive all versions of them.</para>
 
 	    <para>Some computers provide a <acronym>BIOS</acronym>
 	      option to disable one of the graphics adapters or select
 	      a <emphasis>discrete</emphasis> mode which can be used
 	      with one of the standard video card drivers.  For
 	      example, it is sometimes possible to disable the NVIDIA
 	      <acronym>GPU</acronym> in an Optimus system.  The
 	      &intel; video can then be used with an &intel;
 	      driver.</para>
 
 	    <para><acronym>BIOS</acronym> settings depend on the model
 	      of computer.  In some situations, both
 	      <acronym>GPU</acronym>s can be left enabled, but
 	      creating a configuration file that only uses the main
 	      <acronym>GPU</acronym> in the <literal>Device</literal>
 	      section is enough to make such a system
 	      functional.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry xml:id="x-config-video-cards-other">
 	  <term>Other Video Cards</term>
 
 	  <listitem>
 	    <para>Drivers for some less-common video cards can be
 	      found in the <filename>x11-drivers</filename> directory
 	      of the Ports Collection.</para>
 
 	    <para>Cards that are not supported by a specific driver
 	      might still be usable with the
 	      <package>x11-drivers/xf86-video-vesa</package> driver.
 	      This driver is installed by <package>x11/xorg</package>.
 	      It can also be installed manually as
 	      <package>x11-drivers/xf86-video-vesa</package>.
 	      <application>&xorg;</application> attempts to use this
 	      driver when a specific driver is not found for the video
 	      card.</para>
 
 	    <para><package>x11-drivers/xf86-video-scfb</package> is a
 	      similar nonspecialized video driver that works on many
 	      <acronym>UEFI</acronym> and &arm; computers.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry xml:id="x-config-video-cards-file">
 	  <term>Setting the Video Driver in a File</term>
 
 	  <listitem>
 	    <para>To set the &intel; driver in a configuration
 	      file:</para>
 
 	    <example xml:id="x-config-video-cards-file-intel">
 	      <title>Select &intel; Video Driver in a File</title>
 
 	      <para><filename>/usr/local/etc/X11/xorg.conf.d/driver-intel.conf</filename></para>
 
 	      <programlisting>Section "Device"
 	Identifier "Card0"
 	Driver     "intel"
 	# BusID    "PCI:1:0:0"
 EndSection</programlisting>
 
 	      <para>If more than one video card is present, the
 		<literal>BusID</literal> identifier can be uncommented
 		and set to select the desired card.  A list of video
 		card bus <acronym>ID</acronym>s can be displayed with
 		<command>pciconf -lv | grep -B3
 		  display</command>.</para>
 	    </example>
 
 	    <para>To set the Radeon driver in a configuration
 	      file:</para>
 
 	    <example xml:id="x-config-video-cards-file-radeon">
 	      <title>Select Radeon Video Driver in a File</title>
 
 	      <para><filename>/usr/local/etc/X11/xorg.conf.d/driver-radeon.conf</filename></para>
 
 	      <programlisting>Section "Device"
 	Identifier "Card0"
 	Driver     "radeon"
 EndSection</programlisting>
 	    </example>
 
 	    <para>To set the <acronym>VESA</acronym> driver in a
 	      configuration file:</para>
 
 	    <example xml:id="x-config-video-cards-file-vesa">
 	      <title>Select <acronym>VESA</acronym> Video Driver in a
 		File</title>
 
 	      <para><filename>/usr/local/etc/X11/xorg.conf.d/driver-vesa.conf</filename></para>
 
 	      <programlisting>Section "Device"
 	Identifier "Card0"
 	Driver     "vesa"
 EndSection</programlisting>
 	    </example>
 
 	    <para>To set the <literal>scfb</literal> driver for use
 	      with a <acronym>UEFI</acronym> or &arm; computer:</para>
 
 	    <example xml:id="x-config-video-cards-file-scfb">
 	      <title>Select <literal>scfb</literal> Video Driver in a
 		File</title>
 
 	      <para><filename>/usr/local/etc/X11/xorg.conf.d/driver-scfb.conf</filename></para>
 
 	      <programlisting>Section "Device"
 	Identifier "Card0"
 	Driver     "scfb"
 EndSection</programlisting>
 	    </example>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2 xml:id="x-config-monitors">
       <title>Monitors</title>
 
       <para>Almost all monitors support the Extended Display
 	Identification Data standard (<acronym>EDID</acronym>).
 	<application>&xorg;</application> uses <acronym>EDID</acronym>
 	to communicate with the monitor and detect the supported
 	resolutions and refresh rates.  Then it selects the most
 	appropriate combination of settings to use with that
 	monitor.</para>
 
       <para>Other resolutions supported by the monitor can be
 	chosen by setting the desired resolution in configuration
 	files, or after the X server has been started with
 	&man.xrandr.1;.</para>
 
       <variablelist>
 	<varlistentry xml:id="x-config-monitors-xrandr">
 	  <term>Using &man.xrandr.1;</term>
 
 	  <listitem>
 	    <para>Run &man.xrandr.1; without any parameters to see a
 	      list of video outputs and detected monitor modes:</para>
 
 	    <screen>&prompt.user; <userinput>xrandr</userinput>
 Screen 0: minimum 320 x 200, current 3000 x 1920, maximum 8192 x 8192
 DVI-0 connected primary 1920x1200+1080+0 (normal left inverted right x axis y axis) 495mm x 310mm
    1920x1200     59.95*+
    1600x1200     60.00
    1280x1024     85.02    75.02    60.02
    1280x960      60.00
    1152x864      75.00
    1024x768      85.00    75.08    70.07    60.00
    832x624       74.55
    800x600       75.00    60.32
    640x480       75.00    60.00
    720x400       70.08
 DisplayPort-0 disconnected (normal left inverted right x axis y axis)
 HDMI-0 disconnected (normal left inverted right x axis y axis)</screen>
 
 	    <para>This shows that the <literal>DVI-0</literal> output
 	      is being used to display a screen resolution of
 	      1920x1200 pixels at a refresh rate of about 60 Hz.
 	      Monitors are not attached to the
 	      <literal>DisplayPort-0</literal> and
 	      <literal>HDMI-0</literal> connectors.</para>
 
 	    <para>Any of the other display modes can be selected with
 	      &man.xrandr.1;.  For example, to switch to 1280x1024 at
 	      60 Hz:</para>
 
 	    <screen>&prompt.user; <userinput>xrandr --mode 1280x1024 --rate 60</userinput></screen>
 
 	    <para>A common task is using the external video output on
 	      a notebook computer for a video projector.</para>
 
 	    <para>The type and quantity of output connectors varies
 	      between devices, and the name given to each output
 	      varies from driver to driver.  What one driver calls
 	      <literal>HDMI-1</literal>, another might call
 	      <literal>HDMI1</literal>.  So the first step is to run
 	      &man.xrandr.1; to list all the available
 	      outputs:</para>
 
 	    <screen>&prompt.user; <userinput>xrandr</userinput>
 Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
 LVDS1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
    1366x768      60.04*+
    1024x768      60.00
    800x600       60.32    56.25
    640x480       59.94
 VGA1 connected (normal left inverted right x axis y axis)
    1280x1024     60.02 +  75.02
    1280x960      60.00
    1152x864      75.00
    1024x768      75.08    70.07    60.00
    832x624       74.55
    800x600       72.19    75.00    60.32    56.25
    640x480       75.00    72.81    66.67    60.00
    720x400       70.08
 HDMI1 disconnected (normal left inverted right x axis y axis)
 DP1 disconnected (normal left inverted right x axis y axis)</screen>
 
 	    <para>Four outputs were found: the built-in panel
 	      <literal>LVDS1</literal>, and external
 	      <literal>VGA1</literal>, <literal>HDMI1</literal>, and
 	      <literal>DP1</literal> connectors.</para>
 
 	    <para>The projector has been connected to the
 	      <literal>VGA1</literal> output.  &man.xrandr.1; is now
 	      used to set that output to the native resolution of the
 	      projector and add the additional space to the right side
 	      of the desktop:</para>
 
 	    <screen>&prompt.user; <userinput>xrandr --output VGA1 --auto --right-of LVDS1</userinput></screen>
 
 	    <para><literal>--auto</literal> chooses the resolution and
 	      refresh rate detected by <acronym>EDID</acronym>.  If
 	      the resolution is not correctly detected, a fixed value
 	      can be given with <literal>--mode</literal> instead of
 	      the <literal>--auto</literal> statement.  For example,
 	      most projectors can be used with a 1024x768 resolution,
 	      which is set with
 	      <literal>--mode 1024x768</literal>.</para>
 
 	    <para>&man.xrandr.1; is often run from
 	      <filename>.xinitrc</filename> to set the appropriate
 	      mode when X starts.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry xml:id="x-config-monitors-files">
 	  <term>Setting Monitor Resolution in a File</term>
 
 	  <listitem>
 	    <para>To set a screen resolution of 1024x768 in a
 	      configuration file:</para>
 
 	    <example>
 	      <title>Set Screen Resolution in a File</title>
 
 	      <para><filename>/usr/local/etc/X11/xorg.conf.d/screen-resolution.conf</filename></para>
 
 	      <programlisting>Section "Screen"
 	Identifier "Screen0"
 	Device     "Card0"
 	SubSection "Display"
 	Modes      "1024x768"
 	EndSubSection
 EndSection</programlisting>
 	    </example>
 
 	    <para>The few monitors that do not have
 	      <acronym>EDID</acronym> can be configured by setting
 	      <literal>HorizSync</literal> and
 	      <literal>VertRefresh</literal> to the range of
 	      frequencies supported by the monitor.</para>
 
 	    <example>
 	      <title>Manually Setting Monitor Frequencies</title>
 
 	      <para><filename>/usr/local/etc/X11/xorg.conf.d/monitor0-freq.conf</filename></para>
 
 	      <programlisting>Section "Monitor"
 	Identifier   "Monitor0"
 	HorizSync    30-83   # kHz
 	VertRefresh  50-76   # Hz
 EndSection</programlisting>
 	    </example>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2 xml:id="x-config-input">
       <title>Input Devices</title>
 
       <sect3 xml:id="x-config-input-keyboard">
 	<title>Keyboards</title>
 
 	<variablelist>
 	  <varlistentry xml:id="x-config-input-keyboard-layout">
 	    <term>Keyboard Layout</term>
 
 	    <listitem>
 	      <para>The standardized location of keys on a keyboard
 		is called a <emphasis>layout</emphasis>.  Layouts and
 		other adjustable parameters are listed in
 		&man.xkeyboard-config.7;.</para>
 
 	      <para>A United States layout is the default.  To select
 		an alternate layout, set the
 		<literal>XkbLayout</literal> and
 		<literal>XkbVariant</literal> options in an
 		<literal>InputClass</literal>.  This will be applied
 		to all input devices that match the class.</para>
 
 	      <para>This example selects a French keyboard
 		layout.</para>
 
 	      <example>
 		<title>Setting a Keyboard Layout</title>
 
 		<para><filename>/usr/local/etc/X11/xorg.conf.d/keyboard-fr.conf</filename></para>
 
 		<programlisting>Section	"InputClass"
 	Identifier	"KeyboardDefaults"
 	MatchIsKeyboard	"on"
 	Option		"XkbLayout" "fr"
 EndSection</programlisting>
 	      </example>
 
 	      <example>
 		<title>Setting Multiple Keyboard Layouts</title>
 
 		<para>Set United States, Spanish, and Ukrainian
 		  keyboard layouts.  Cycle through these layouts by
 		  pressing
 		  <keycombo action="simul">
 		    <keycap>Alt</keycap>
 		    <keycap>Shift</keycap>
 		  </keycombo>.  <package>x11/xxkb</package> or
 		  <package>x11/sbxkb</package> can be used for
 		  improved layout switching control and
 		  current layout indicators.</para>
 
 		<para><filename>/usr/local/etc/X11/xorg.conf.d/kbd-layout-multi.conf</filename></para>
 
 		<programlisting>Section	"InputClass"
 	Identifier	"All Keyboards"
 	MatchIsKeyboard	"yes"
 	Option		"XkbLayout" "us, es, ua"
 EndSection</programlisting>
 	      </example>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry xml:id="x-config-input-keyboard-zap">
 	    <term>Closing <application>&xorg;</application> From the
 	    Keyboard</term>
 
 	    <listitem>
 	      <para>X can be closed with a combination of keys.
 		By default, that key combination is not set because it
 		conflicts with keyboard commands for some
 		applications.  Enabling this option requires changes
 		to the keyboard <literal>InputDevice</literal>
 		section:</para>
 
 	      <example>
 		<title>Enabling Keyboard Exit from X</title>
 
 		<para><filename>/usr/local/etc/X11/xorg.conf.d/keyboard-zap.conf</filename></para>
 
 		<programlisting>Section	"InputClass"
 	Identifier	"KeyboardDefaults"
 	MatchIsKeyboard	"on"
 	Option		"XkbOptions" "terminate:ctrl_alt_bksp"
 EndSection</programlisting>
 	      </example>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
       </sect3>
 
       <sect3 xml:id="x11-input-mice">
 	<title>Mice and Pointing Devices</title>
 
 	<important>
 	  <para>If using <package>xorg-server</package>&nbsp;1.20.8 or
 	    later under &os;&nbsp;&rel121.current; and not
 	    using &man.moused.8;, add
 	    <userinput>kern.evdev.rcpt_mask=12</userinput> to
 	    <filename>/etc/sysctl.conf</filename>.</para>
 	</important>
 
 	<para>Many mouse parameters can be adjusted with configuration
 	  options.  See &man.mousedrv.4x; for a full list.</para>
 
 	<variablelist>
 	  <varlistentry xml:id="x11-input-mice-buttons">
 	    <term>Mouse Buttons</term>
 
 	    <listitem>
 	      <para>The number of buttons on a mouse can be set in the
 		mouse <literal>InputDevice</literal> section of
 		<filename>xorg.conf</filename>.  To set the number of
 		buttons to 7:</para>
 
 	      <example>
 		<title>Setting the Number of Mouse Buttons</title>
 
 		<para><filename>/usr/local/etc/X11/xorg.conf.d/mouse0-buttons.conf</filename></para>
 
 		<programlisting>Section "InputDevice"
 	Identifier  "Mouse0"
 	Option      "Buttons" "7"
 EndSection</programlisting>
 	      </example>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
       </sect3>
     </sect2>
 
     <sect2 xml:id="x-config-manual-configuration">
       <title>Manual Configuration</title>
 
       <para>In some cases, <application>&xorg;</application>
 	autoconfiguration does not work with particular hardware, or a
 	different configuration is desired.  For these cases, a custom
 	configuration file can be created.</para>
 
       <warning>
 	<para>Do not create manual configuration files unless
 	  required.  Unnecessary manual configuration can prevent
 	  proper operation.</para>
       </warning>
 
       <para>A configuration file can be generated by
 	<application>&xorg;</application> based on the detected
 	hardware.  This file is often a useful starting point for
 	custom configurations.</para>
 
       <para>Generating an <filename>xorg.conf</filename>:</para>
 
       <screen>&prompt.root; <userinput>Xorg -configure</userinput></screen>
 
       <para>The configuration file is saved to
 	<filename>/root/xorg.conf.new</filename>.  Make any changes
 	desired, then test that file (using <option>-retro</option>
 	so there is a visible background) with:</para>
 
       <screen>&prompt.root; <userinput>Xorg -retro -config /root/xorg.conf.new</userinput></screen>
 
       <para>After the new configuration has been adjusted and tested,
 	it can be split into smaller files in the normal location,
 	<filename>/usr/local/etc/X11/xorg.conf.d/</filename>.</para>
     </sect2>
   </sect1>
 
   <sect1 xml:id="x-fonts">
     <!--
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Murray</firstname>
 	  <surname>Stokely</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     -->
     <title>Using Fonts in <application>&xorg;</application></title>
 
     <sect2 xml:id="type1">
       <title>Type1 Fonts</title>
 
       <para>The default fonts that ship with
 	<application>&xorg;</application> are less than ideal for
 	typical desktop publishing applications.  Large presentation
 	fonts show up jagged and unprofessional looking, and small
 	fonts are almost completely unintelligible.  However, there
 	are several free, high quality Type1 (&postscript;) fonts
 	available which can be readily used with
 	<application>&xorg;</application>.  For instance, the URW font
 	collection (<package>x11-fonts/urwfonts</package>) includes
 	high quality versions of standard type1 fonts (<trademark
 	  class="registered">Times Roman</trademark>, <trademark
 	  class="registered">Helvetica</trademark>, <trademark
 	  class="registered">Palatino</trademark> and others).  The
 	Freefonts collection (<package>x11-fonts/freefonts</package>)
 	includes many more fonts, but most of them are intended for
 	use in graphics software such as the
 	<application>Gimp</application>, and are not complete enough
 	to serve as screen fonts.  In addition,
 	<application>&xorg;</application> can be configured to use
 	&truetype; fonts with a minimum of effort.  For more details
 	on this, see the &man.X.7; manual page or <xref
 	  linkend="truetype"/>.</para>
 
       <para>To install the above Type1 font collections from binary
 	packages, run the following commands:</para>
 
       <screen>&prompt.root; <userinput>pkg install urwfonts</userinput></screen>
 
       <para>Alternatively, to build from the Ports Collection, run the
 	following commands:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/x11-fonts/urwfonts</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <para>And likewise with the freefont or other collections.  To
 	have the X server detect these fonts, add an appropriate line
 	to the X server configuration file
 	(<filename>/etc/X11/xorg.conf</filename>), which reads:</para>
 
       <programlisting>FontPath "/usr/local/share/fonts/urwfonts/"</programlisting>
 
       <para>Alternatively, at the command line in the X session
 	run:</para>
 
       <screen>&prompt.user; <userinput>xset fp+ /usr/local/share/fonts/urwfonts</userinput>
 &prompt.user; <userinput>xset fp rehash</userinput></screen>
 
       <para>This will work but will be lost when the X session is
 	closed, unless it is added to the startup file
 	(<filename>~/.xinitrc</filename> for a normal
 	<command>startx</command> session, or
 	<filename>~/.xsession</filename> when logging in through a
 	graphical login manager like <application>XDM</application>).
 	A third way is to use the new
 	<filename>/usr/local/etc/fonts/local.conf</filename> as
 	demonstrated in <xref linkend="antialias"/>.</para>
     </sect2>
 
     <sect2 xml:id="truetype">
       <title>&truetype; Fonts</title>
 
       <indexterm>
 	<primary>TrueType Fonts</primary>
       </indexterm>
       <indexterm>
 	<primary>fonts</primary>
 	<secondary>TrueType</secondary>
       </indexterm>
 
       <para><application>&xorg;</application> has built in support for
 	rendering &truetype; fonts.  There are two different modules
 	that can enable this functionality.  The freetype module is
 	used in this example because it is more consistent with the
 	other font rendering back-ends.  To enable the freetype module
 	just add the following line to the <literal>"Module"</literal>
 	section of <filename>/etc/X11/xorg.conf</filename>.</para>
 
       <programlisting>Load  "freetype"</programlisting>
 
       <para>Now make a directory for the &truetype; fonts (for
 	example, <filename>/usr/local/share/fonts/TrueType</filename>)
 	and copy all of the &truetype; fonts into this directory.
 	Keep in mind that &truetype; fonts cannot be directly taken
 	from an &apple; &mac;; they must be in
 	&unix;/&ms-dos;/&windows; format for use by
 	<application>&xorg;</application>.  Once the files have been
 	copied into this directory, use
 	<application>mkfontscale</application> to create a
 	<filename>fonts.dir</filename>, so that the X font renderer
 	knows that these new files have been installed.
 	<command>mkfontscale</command> can be installed as a
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install mkfontscale</userinput></screen>
 
       <para>Then create an index of X font files in a
 	directory:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/local/share/fonts/TrueType</userinput>
 &prompt.root; <userinput>mkfontscale</userinput></screen>
 
       <para>Now add the &truetype; directory to the font path.  This
 	is just the same as described in <xref
 	  linkend="type1"/>:</para>
 
       <screen>&prompt.user; <userinput>xset fp+ /usr/local/share/fonts/TrueType</userinput>
 &prompt.user; <userinput>xset fp rehash</userinput></screen>
 
       <para>or add a <literal>FontPath</literal> line to
 	<filename>xorg.conf</filename>.</para>
 
       <para>Now <application>Gimp</application>,
 	<application>LibreOffice</application>, and all of the
 	other X applications should now recognize the installed
 	&truetype; fonts.  Extremely small fonts (as with text in a
 	high resolution display on a web page) and extremely large
 	fonts (within <application>LibreOffice</application>) will
 	look much better now.</para>
     </sect2>
 
     <sect2 xml:id="antialias">
       <!--
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Joe Marcus</firstname>
 	    <surname>Clarke</surname>
 	    <contrib>Updated in May 2003 by</contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
       -->
       <title>Anti-Aliased Fonts</title>
 
       <indexterm>
 	<primary>anti-aliased fonts</primary>
       </indexterm>
       <indexterm>
 	<primary>fonts</primary>
 	<secondary>anti-aliased</secondary>
       </indexterm>
 
       <para>All fonts in <application>&xorg;</application> that are
 	found in <filename>/usr/local/share/fonts/</filename> and
 	<filename>~/.fonts/</filename> are automatically made
 	available for anti-aliasing to Xft-aware applications.  Most
 	recent applications are Xft-aware, including
 	<application>KDE</application>,
 	<application>GNOME</application>, and
 	<application>Firefox</application>.</para>
 
       <para>To control which fonts are anti-aliased, or to
 	configure anti-aliasing properties, create (or edit, if it
 	already exists) the file
 	<filename>/usr/local/etc/fonts/local.conf</filename>.  Several
 	advanced features of the Xft font system can be tuned using
 	this file; this section describes only some simple
 	possibilities.  For more details, please see
 	&man.fonts-conf.5;.</para>
 
       <indexterm><primary>XML</primary></indexterm>
 
       <para>This file must be in XML format.  Pay careful attention to
 	case, and make sure all tags are properly closed.  The file
 	begins with the usual XML header followed by a DOCTYPE
 	definition, and then the <literal>&lt;fontconfig&gt;</literal>
 	tag:</para>
 
       <programlisting>&lt;?xml version="1.0"?&gt;
       &lt;!DOCTYPE fontconfig SYSTEM "fonts.dtd"&gt;
       &lt;fontconfig&gt;</programlisting>
 
       <para>As previously stated, all fonts in
 	<filename>/usr/local/share/fonts/</filename> as well as
 	<filename>~/.fonts/</filename> are already made available to
 	Xft-aware applications.  To add another directory
 	outside of these two directory trees, add a line like
 	this to
 	<filename>/usr/local/etc/fonts/local.conf</filename>:</para>
 
       <programlisting>&lt;dir&gt;/path/to/my/fonts&lt;/dir&gt;</programlisting>
 
       <para>After adding new fonts, and especially new font
 	directories, rebuild
 	the font caches:</para>
 
       <screen>&prompt.root; <userinput>fc-cache -f</userinput></screen>
 
       <para>Anti-aliasing makes borders slightly fuzzy, which makes
 	very small text more readable and removes
 	<quote>staircases</quote> from large text, but can cause
 	eyestrain if applied to normal text.  To exclude font sizes
 	smaller than 14 point from anti-aliasing, include these
 	lines:</para>
 
       <programlisting>        &lt;match target="font"&gt;
 	    &lt;test name="size" compare="less"&gt;
 		&lt;double&gt;14&lt;/double&gt;
 	    &lt;/test&gt;
 	    &lt;edit name="antialias" mode="assign"&gt;
 		&lt;bool&gt;false&lt;/bool&gt;
 	    &lt;/edit&gt;
 	&lt;/match&gt;
 	&lt;match target="font"&gt;
 	    &lt;test name="pixelsize" compare="less" qual="any"&gt;
 		&lt;double&gt;14&lt;/double&gt;
 	    &lt;/test&gt;
 	    &lt;edit mode="assign" name="antialias"&gt;
 		&lt;bool&gt;false&lt;/bool&gt;
 	    &lt;/edit&gt;
 	&lt;/match&gt;</programlisting>
 
       <indexterm>
 	<primary>fonts</primary>
 	<secondary>spacing</secondary>
       </indexterm>
 
       <para>Spacing for some monospaced fonts might also be
 	inappropriate with anti-aliasing.  This seems to be an issue
 	with <application>KDE</application>, in particular.  One
 	possible fix is to force the spacing for such fonts
 	to be 100. Add these lines:</para>
 
       <programlisting>	&lt;match target="pattern" name="family"&gt;
 	   &lt;test qual="any" name="family"&gt;
 	       &lt;string&gt;fixed&lt;/string&gt;
 	   &lt;/test&gt;
 	   &lt;edit name="family" mode="assign"&gt;
 	       &lt;string&gt;mono&lt;/string&gt;
 	   &lt;/edit&gt;
 	&lt;/match&gt;
 	&lt;match target="pattern" name="family"&gt;
 	    &lt;test qual="any" name="family"&gt;
 		&lt;string&gt;console&lt;/string&gt;
 	    &lt;/test&gt;
 	    &lt;edit name="family" mode="assign"&gt;
 		&lt;string&gt;mono&lt;/string&gt;
 	    &lt;/edit&gt;
 	&lt;/match&gt;</programlisting>
 
       <para>(this aliases the other common names for fixed fonts as
 	<literal>"mono"</literal>), and then add:</para>
 
       <programlisting>         &lt;match target="pattern" name="family"&gt;
 	     &lt;test qual="any" name="family"&gt;
 		 &lt;string&gt;mono&lt;/string&gt;
 	     &lt;/test&gt;
 	     &lt;edit name="spacing" mode="assign"&gt;
 		 &lt;int&gt;100&lt;/int&gt;
 	     &lt;/edit&gt;
 	 &lt;/match&gt;      </programlisting>
 
       <para>Certain fonts, such as Helvetica, may have a problem when
 	anti-aliased.  Usually this manifests itself as a font that
 	seems cut in half vertically.  At worst, it may cause
 	applications to crash.  To avoid this, consider adding the
 	following to <filename>local.conf</filename>:</para>
 
       <programlisting>         &lt;match target="pattern" name="family"&gt;
 	     &lt;test qual="any" name="family"&gt;
 		 &lt;string&gt;Helvetica&lt;/string&gt;
 	     &lt;/test&gt;
 	     &lt;edit name="family" mode="assign"&gt;
 		 &lt;string&gt;sans-serif&lt;/string&gt;
 	     &lt;/edit&gt;
 	 &lt;/match&gt;        </programlisting>
 
       <para>After editing
 	<filename>local.conf</filename>, make certain to end the file
 	with the <literal>&lt;/fontconfig&gt;</literal> tag.  Not
 	doing this will cause changes to be ignored.</para>
 
       <para>Users can add personalized settings by creating their own
 	<filename>~/.config/fontconfig/fonts.conf</filename>.  This
 	file uses the same <acronym>XML</acronym> format described
 	above.</para>
 
       <indexterm><primary>LCD screen</primary></indexterm>
       <indexterm><primary>Fonts</primary>
 	<secondary>LCD screen</secondary></indexterm>
 
       <para>One last point: with an LCD screen, sub-pixel sampling may
 	be desired.  This basically treats the (horizontally
 	separated) red, green and blue components separately to
 	improve the horizontal resolution; the results can be
 	dramatic.  To enable this, add the line somewhere in
 	<filename>local.conf</filename>:</para>
 
       <programlisting>	 &lt;match target="font"&gt;
 	     &lt;test qual="all" name="rgba"&gt;
 		 &lt;const&gt;unknown&lt;/const&gt;
 	     &lt;/test&gt;
 	     &lt;edit name="rgba" mode="assign"&gt;
 		 &lt;const&gt;rgb&lt;/const&gt;
 	     &lt;/edit&gt;
 	 &lt;/match&gt;</programlisting>
 
       <note>
 	<para>Depending on the sort of display,
 	  <literal>rgb</literal> may need to be changed to
 	  <literal>bgr</literal>, <literal>vrgb</literal> or
 	  <literal>vbgr</literal>: experiment and see which works
 	  best.</para>
       </note>
     </sect2>
   </sect1>
 
   <sect1 xml:id="x-xdm">
     <info>
       <title>The X Display Manager</title>
 
       <authorgroup>
 	<author>
 	  <personname>
 	    <firstname>Seth</firstname>
 	    <surname>Kingsley</surname>
 	  </personname>
 	  <contrib>Originally contributed by </contrib>
 	</author>
       </authorgroup>
     </info>
 
     <indexterm><primary>X Display Manager</primary></indexterm>
     <para><application>&xorg;</application> provides an X Display
       Manager, <application>XDM</application>, which can be used for
       login session management.  <application>XDM</application>
       provides a graphical interface for choosing which display server
       to connect to and for entering authorization information such as
       a login and password combination.</para>
 
     <para>This section demonstrates how to configure the X Display
       Manager on &os;.  Some desktop environments provide their own
       graphical login manager.  Refer to <xref
 	linkend="x11-wm-gnome"/> for instructions on how to configure
       the GNOME Display Manager and <xref linkend="x11-wm-kde"/> for
       instructions on how to configure the KDE Display Manager.</para>
 
     <sect2>
       <title>Configuring <application>XDM</application></title>
 
       <para>To install <application>XDM</application>, use the
 	<package>x11/xdm</package> package or port.  Once installed,
 	<application>XDM</application> can be configured to run when
 	the  machine boots up by editing this entry in
 	<filename>/etc/ttys</filename>:</para>
 
       <screen>ttyv8   "/usr/local/bin/xdm -nodaemon"  xterm   off secure</screen>
 
       <para>Change the <literal>off</literal> to <literal>on</literal>
 	and save the edit.  The <literal>ttyv8</literal> in this entry
 	indicates that <application>XDM</application> will run on the
 	ninth virtual terminal.</para>
 
       <para>The <application>XDM</application> configuration directory
 	is located in <filename>/usr/local/etc/X11/xdm</filename>.
 	This directory contains several files used to change the
 	behavior and appearance of <application>XDM</application>, as
 	well as a few scripts and programs used to set up the desktop
 	when <application>XDM</application> is running.  <xref
 	  linkend="xdm-config-files"/> summarizes the function of each
 	of these files.  The exact syntax and usage of these files is
 	described in &man.xdm.1;.</para>
 
       <table frame="none" pgwide="1" xml:id="xdm-config-files">
 	<title>XDM Configuration Files</title>
 
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>File</entry>
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><filename>Xaccess</filename></entry>
 	      <entry>The protocol for connecting to
 		<application>XDM</application> is called the X Display
 		Manager Connection Protocol
 		(<acronym>XDMCP</acronym>).  This file is a client
 		authorization ruleset for controlling
 		<acronym>XDMCP</acronym> connections from remote
 		machines.  By default, this file does not allow any
 		remote clients to connect.</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>Xresources</filename></entry>
 	      <entry>This file controls the look and feel of the
 		<application>XDM</application> display chooser and
 		login screens.  The default configuration is a simple
 		rectangular login window with the hostname of the
 		machine displayed at the top in a large font and
 		<quote>Login:</quote> and <quote>Password:</quote>
 		prompts below.  The format of this file is identical
 		to the app-defaults file described in the
 		<application>&xorg;</application>
 		documentation.</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>Xservers</filename></entry>
 	      <entry>The list of local and remote displays the chooser
 		should provide as login choices.</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>Xsession</filename></entry>
 	      <entry>Default session script for logins which is run by
 		<application>XDM</application> after a user has logged
 		in.  This points to a customized session
 		script in <filename>~/.xsession</filename>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>Xsetup_</filename>*</entry>
 	      <entry>Script to automatically launch applications
 		before displaying the chooser or login interfaces.
 		There is a script for each display being used, named
 		<filename>Xsetup_*</filename>, where
 		<literal>*</literal> is the local display number.
 		Typically these scripts run one or two programs in the
 		background such as
 		<command>xconsole</command>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>xdm-config</filename></entry>
 	      <entry>Global configuration for all displays running
 		on this machine.</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>xdm-errors</filename></entry>
 	      <entry>Contains errors generated by the server program.
 		If a display that <application>XDM</application> is
 		trying to start hangs, look at this file for error
 		messages.  These messages are also written to the
 		user's <filename>~/.xsession-errors</filename> on a
 		per-session basis.</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>xdm-pid</filename></entry>
 	      <entry>The running process <acronym>ID</acronym> of
 		<application>XDM</application>.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
     </sect2>
 
     <sect2>
       <title>Configuring Remote Access</title>
 
       <para>By default, only users on the same system can login using
 	<application>XDM</application>.  To enable users on other
 	systems to connect to the display server, edit the access
 	control rules and enable the connection listener.</para>
 
       <para>To configure <application>XDM</application> to listen for
 	any remote connection, comment out the
 	<literal>DisplayManager.requestPort</literal> line in
 	<filename>/usr/local/etc/X11/xdm/xdm-config</filename> by
 	putting a <literal>!</literal> in front of it:</para>
 
       <screen>! SECURITY: do not listen for XDMCP or Chooser requests
 ! Comment out this line if you want to manage X terminals with xdm
 DisplayManager.requestPort:     0</screen>
 
       <para>Save the edits and restart <application>XDM</application>.
 	To restrict remote access, look at the example entries in
 	<filename>/usr/local/etc/X11/xdm/Xaccess</filename> and refer
 	to &man.xdm.1; for further information.</para>
     </sect2>
   </sect1>
 
   <sect1 xml:id="x11-wm">
     <info>
       <title>Desktop Environments</title>
 
       <authorgroup>
 	<author>
 	  <personname>
 	    <firstname>Valentino</firstname>
 	    <surname>Vaschetto</surname>
 	  </personname>
 	  <contrib>Contributed by </contrib>
 	   <!-- in June 2001 -->
 	</author>
       </authorgroup>
     </info>
 
     <para>This section describes how to install three popular desktop
       environments on a &os; system.  A desktop environment can range
       from a simple window manager to a complete suite of desktop
       applications.  Over a hundred desktop environments are available
       in the <filename>x11-wm</filename> category of the Ports
       Collection.</para>
 
     <sect2 xml:id="x11-wm-gnome">
       <title>GNOME</title>
 
       <indexterm><primary>GNOME</primary></indexterm>
       <para><application>GNOME</application> is a user-friendly
 	desktop environment.  It includes a panel for starting
 	applications and displaying status, a desktop, a set of tools
 	and applications, and a set of conventions that make it easy
 	for applications to cooperate and be consistent with each
 	other.  More information regarding
 	<application>GNOME</application> on &os; can be found at <link
 	  xlink:href="https://www.FreeBSD.org/gnome">https://www.FreeBSD.org/gnome</link>.
 	That web site contains additional documentation about
 	installing, configuring, and managing
 	<application>GNOME</application> on &os;.</para>
 
       <para>This desktop environment can be installed from a
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install gnome3</userinput></screen>
 
       <para>To instead build <application>GNOME</application> from
 	ports, use the following command.
 	<application>GNOME</application> is a large application and
 	will take some time to compile, even on a fast
 	computer.</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/x11/gnome3</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <para><application>GNOME</application>
 	requires <filename>/proc</filename> to be mounted.  Add this
 	line to <filename>/etc/fstab</filename> to mount this file
 	system automatically during system startup:</para>
 
       <programlisting>proc           /proc       procfs  rw  0   0</programlisting>
 
       <para><application>GNOME</application> uses
 	<application>D-Bus</application> and
 	<application>HAL</application> for a message bus and hardware
 	abstraction.  These applications are automatically installed
 	as dependencies of <application>GNOME</application>.  Enable
 	them in <filename>/etc/rc.conf</filename> so they will be
 	started when the system boots:</para>
 
       <programlisting>dbus_enable="YES"
 hald_enable="YES"</programlisting>
 
       <para>After installation,
 	configure <application>&xorg;</application> to start
 	<application>GNOME</application>.  The easiest way to do this
 	is to enable the GNOME Display Manager,
 	<application>GDM</application>, which is installed as part of
 	the <application>GNOME</application> package or port.  It can
 	be enabled by adding this line to
 	<filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>gdm_enable="YES"</programlisting>
 
       <para>It is often desirable to also start all
 	<application>GNOME</application> services.  To achieve this,
 	add a second line to <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>gnome_enable="YES"</programlisting>
 
       <para><application>GDM</application> will start
 	automatically when the system boots.</para>
 
       <para>A second method for starting
 	<application>GNOME</application> is to type
 	<command>startx</command> from the command-line after
 	configuring <filename>~/.xinitrc</filename>.  If this file
 	already exists, replace the line that starts the current
 	window manager with one that starts
 	<filename>/usr/local/bin/gnome-session</filename>.  If this
 	file does not exist, create it with this command:</para>
 
       <screen>&prompt.user; <userinput>echo "exec /usr/local/bin/gnome-session" &gt; ~/.xinitrc</userinput></screen>
 
       <para>A third method is to use <application>XDM</application> as
 	the display manager.  In this case, create an executable
 	<filename>~/.xsession</filename>:</para>
 
       <screen>&prompt.user; <userinput>echo "exec /usr/local/bin/gnome-session" &gt; ~/.xsession</userinput></screen>
     </sect2>
 
     <sect2 xml:id="x11-wm-kde">
       <title>KDE</title>
 
       <indexterm><primary>KDE</primary></indexterm>
 
       <para><application>KDE</application> is another easy-to-use
 	desktop environment.  This desktop provides a suite of
 	applications with a consistent look and feel, a standardized
 	menu and toolbars, keybindings, color-schemes,
 	internationalization, and a centralized, dialog-driven desktop
 	configuration.  More information on
 	<application>KDE</application> can be found at <link
 	  xlink:href="http://www.kde.org/">http://www.kde.org/</link>.
 	For &os;-specific information, consult <link
 	  xlink:href="http://freebsd.kde.org/">http://freebsd.kde.org</link>.</para>
 
       <para>To install the <application>KDE</application> package,
 	type:</para>
 
       <screen>&prompt.root; <userinput>pkg install x11/kde5</userinput></screen>
 
       <para>To instead build the <application>KDE</application> port,
 	use the following command.  Installing the port will provide a
 	menu for selecting which components to install.
 	<application>KDE</application> is a large application and will
 	take some time to compile, even on a fast computer.</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/x11/kde5</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <para><application>KDE</application> requires
 	<filename>/proc</filename> to be mounted.  Add this line to
 	<filename>/etc/fstab</filename> to mount this file system
 	automatically during system startup:</para>
 
       <programlisting>proc           /proc       procfs  rw  0   0</programlisting>
 
       <para><application>KDE</application> uses
 	<application>D-Bus</application> and
 	<application>HAL</application> for a message bus and hardware
 	abstraction.  These applications are automatically installed
 	as dependencies of <application>KDE</application>.  Enable
 	them in <filename>/etc/rc.conf</filename> so they will be
 	started when the system boots:</para>
 
       <programlisting>dbus_enable="YES"
 hald_enable="YES"</programlisting>
 
       <indexterm>
 	<primary>KDE</primary>
 	<secondary>display manager</secondary>
       </indexterm>
 
       <para>Since KDE Plasma 5, the KDE Display Manager,
 	<application>KDM</application> is no longer developed.
 	A possible replacement is <application>SDDM</application>.
 	To install it, type:</para>
 
       <screen>&prompt.root; <userinput>pkg install x11/sddm</userinput></screen>
 
       <para>Add this line to
 	<filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>sddm_enable="YES"</programlisting>
 
       <para>A second method for launching
 	<application>KDE Plasma</application> is to type
 	<command>startx</command> from the command line.  For this to
 	work, the following line is needed in
 	<filename>~/.xinitrc</filename>:</para>
 
       <programlisting>exec ck-launch-session startplasma-x11</programlisting>
 
       <para>A third method for starting <application>KDE
 	  Plasma</application> is through
 	<application>XDM</application>.  To do so, create
 	an executable <filename>~/.xsession</filename> as
 	follows:</para>
 
       <screen>&prompt.user; <userinput>echo "exec ck-launch-session startplasma-x11" &gt; ~/.xsession</userinput></screen>
 
       <para>Once <application>KDE Plasma</application> is started,
 	refer to its built-in help system for more information on how
 	to use its various menus and applications.</para>
     </sect2>
 
     <sect2 xml:id="x11-wm-xfce">
       <title>Xfce</title>
 
       <para><application>Xfce</application> is a desktop environment
 	based on the GTK+ toolkit used by
 	<application>GNOME</application>.  However, it is more
 	lightweight and provides a simple, efficient, easy-to-use
 	desktop.  It is fully configurable, has a main panel with
 	menus, applets, and application launchers, provides a file
 	manager and sound manager, and is themeable.  Since it is
 	fast, light, and efficient, it is ideal for older or slower
 	machines with memory limitations.  More information on
 	<application>Xfce</application> can be found at <link
 	  xlink:href="http://www.xfce.org/">http://www.xfce.org</link>.</para>
 
       <para>To install the <application>Xfce</application>
 	package:</para>
 
       <screen>&prompt.root; <userinput>pkg install xfce</userinput></screen>
 
       <para>Alternatively, to build the port:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/x11-wm/xfce4</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <para><application>Xfce</application> uses
 	<application>D-Bus</application> for a message bus.  This
 	application is automatically installed as dependency of
 	<application>Xfce</application>.  Enable it in
 	<filename>/etc/rc.conf</filename> so it will be started when
 	the system boots:</para>
 
       <programlisting>dbus_enable="YES"</programlisting>
 
       <para>Unlike <application>GNOME</application> or
 	<application>KDE</application>,
 	<application>Xfce</application> does not provide its own login
 	manager.  In order to start <application>Xfce</application>
 	from the command line by typing <command>startx</command>,
 	first create <filename>~/.xinitrc</filename> with this
 	command:</para>
 
       <screen>&prompt.user; <userinput>echo ". /usr/local/etc/xdg/xfce4/xinitrc" &gt; ~/.xinitrc</userinput></screen>
 
       <para>An alternate method is to use
 	<application>XDM</application>.  To configure this method,
 	create an executable <filename>~/.xsession</filename>:</para>
 
       <screen>&prompt.user; <userinput>echo ". /usr/local/etc/xdg/xfce4/xinitrc" &gt; ~/.xsession</userinput></screen>
     </sect2>
   </sect1>
 
   <sect1 xml:id="x-compiz-fusion">
     <title>Installing Compiz Fusion</title>
 
     <para>One way to make using a desktop
       computer more pleasant is with nice 3D effects.</para>
 
     <para>Installing the <application>Compiz&nbsp;Fusion</application>
       package is easy, but configuring it requires a few steps that
       are not described in the port's documentation.</para>
 
     <sect2 xml:id="x-compiz-video-card">
       <title>Setting up the &os; nVidia Driver</title>
 
       <para>Desktop effects can cause quite a load on the graphics
 	card.  For an nVidia-based graphics card, the proprietary
 	driver is required for good performance.  Users of other
 	graphics cards can skip this section and continue with the
 	<filename>xorg.conf</filename> configuration.</para>
 
       <para>To determine which nVidia driver is needed see the <link
 	  xlink:href="&url.books.faq;/x.html#idp59950544">FAQ question
 	  on the subject</link>.</para>
 
       <para>Having determined the correct driver to use for your card,
 	installation is as simple as installing any other
 	package.</para>
 
       <para>For example, to install the latest driver:</para>
 
       <screen>&prompt.root; <userinput>pkg install x11/nvidia-driver</userinput></screen>
 
       <para>The driver will create a kernel module, which needs to be
 	loaded at system startup.  Add the following line to
 	<filename>/boot/loader.conf</filename>:</para>
 
       <programlisting>nvidia_load="YES"</programlisting>
 
       <note>
 	<para>To immediately load the kernel module into the running
 	  kernel issue a command like <command>kldload
 	    nvidia</command>.  However, it has been noted that some
 	  versions of <application>&xorg;</application> will not
 	  function properly if the driver is not loaded at boot time.
 	  After editing <filename>/boot/loader.conf</filename>, a
 	  reboot is recommended.</para>
       </note>
 
       <para>With the kernel module loaded, you normally only need to
 	change a single line in <filename>xorg.conf</filename>
 	to enable the proprietary driver:</para>
 
       <para>Find the following line in
 	<filename>/etc/X11/xorg.conf</filename>:</para>
 
       <programlisting>Driver      "nv"</programlisting>
 
       <para>and change it to:</para>
 
       <programlisting>Driver      "nvidia"</programlisting>
 
       <para>Start the GUI as usual, and you should be greeted by the
 	nVidia splash.  Everything should work as usual.</para>
     </sect2>
 
     <sect2 xml:id="xorg-configuration">
       <title>Configuring <literal>xorg.conf</literal> for Desktop
 	Effects</title>
 
       <para>To enable <application>Compiz&nbsp;Fusion</application>,
 	<filename>/etc/X11/xorg.conf</filename> needs to be
 	modified:</para>
 
       <para>Add the following section to enable composite
 	effects:</para>
 
       <programlisting>Section "Extensions"
     Option         "Composite" "Enable"
 EndSection</programlisting>
 
       <para>Locate the <quote>Screen</quote> section which should look
 	similar to the one below:</para>
 
       <programlisting>Section "Screen"
     Identifier     "Screen0"
     Device         "Card0"
     Monitor        "Monitor0"
     ...</programlisting>
 
       <para>and add the following two lines (after
 	<quote>Monitor</quote> will do):</para>
 
       <programlisting>DefaultDepth    24
 Option         "AddARGBGLXVisuals" "True"</programlisting>
 
       <para>Locate the <quote>Subsection</quote> that refers to the
 	screen resolution that you wish to use.  For example, if you
 	wish to use 1280x1024, locate the section that follows.  If
 	the desired resolution does not appear in any subsection, you
 	may add the relevant entry by hand:</para>
 
       <programlisting>SubSection     "Display"
     Viewport    0 0
     Modes      "1280x1024"
 EndSubSection</programlisting>
 
       <para>A color depth of 24&nbsp;bits is needed for desktop
 	composition, change the above subsection to:</para>
 
       <programlisting>SubSection     "Display"
     Viewport    0 0
     Depth       24
     Modes      "1280x1024"
 EndSubSection</programlisting>
 
       <para>Finally, confirm that the <quote>glx</quote> and
 	<quote>extmod</quote> modules are loaded in the
 	<quote>Module</quote> section:</para>
 
       <programlisting>Section "Module"
     Load           "extmod"
     Load           "glx"
     ...</programlisting>
 
       <para>The preceding can be done automatically with
 	<package>x11/nvidia-xconfig</package> by running (as
 	 <systemitem class="username">root</systemitem>):</para>
 
        <screen>&prompt.root; <userinput>nvidia-xconfig --add-argb-glx-visuals</userinput>
 &prompt.root; <userinput>nvidia-xconfig --composite</userinput>
 &prompt.root; <userinput>nvidia-xconfig --depth=24</userinput></screen>
     </sect2>
 
     <sect2 xml:id="compiz-fusion">
       <title>Installing and Configuring Compiz&nbsp;Fusion</title>
 
       <para>Installing <application>Compiz&nbsp;Fusion</application>
 	is as simple as any other package:</para>
 
       <screen>&prompt.root; <userinput>pkg install x11-wm/compiz-fusion</userinput></screen>
 
       <para>When the installation is finished, start your graphic
 	desktop and at a terminal, enter the following commands (as a
 	normal user):</para>
 
       <screen>&prompt.user; <userinput>compiz --replace --sm-disable --ignore-desktop-hints ccp &amp;</userinput>
 &prompt.user; <userinput>emerald --replace &amp;</userinput></screen>
 
       <para>Your screen will flicker for a few seconds, as your window
 	manager (e.g., <application>Metacity</application> if you are
 	using <application>GNOME</application>) is replaced by
 	<application>Compiz&nbsp;Fusion</application>.
 	<application>Emerald</application> takes care of the window
 	decorations (i.e., close, minimize, maximize buttons, title
 	bars and so on).</para>
 
       <para>You may convert this to a trivial script and have it run
 	at startup automatically (e.g., by adding to
 	<quote>Sessions</quote> in a <application>GNOME</application>
 	desktop):</para>
 
       <programlisting>#! /bin/sh
 compiz --replace --sm-disable --ignore-desktop-hints ccp &amp;
 emerald --replace &amp;</programlisting>
 
       <para>Save this in your home directory as, for example,
 	<filename>start-compiz</filename> and make it
 	executable:</para>
 
       <screen>&prompt.user; <userinput>chmod +x ~/start-compiz</userinput></screen>
 
       <para>Then use the GUI to add it to <guimenuitem>Startup
 	  Programs</guimenuitem> (located in
 	<guimenuitem>System</guimenuitem>,
 	<guimenuitem>Preferences</guimenuitem>,
 	<guimenuitem>Sessions</guimenuitem> on a
 	<application>GNOME</application> desktop).</para>
 
       <para>To actually select all the desired effects and their
 	settings, execute (again as a normal user) the
 	<application>Compiz&nbsp;Config&nbsp;Settings&nbsp;Manager</application>:</para>
 
       <screen>&prompt.user; <userinput>ccsm</userinput></screen>
 
       <note>
 	<para>In <application>GNOME</application>, this can also be
 	  found in the <guimenuitem>System</guimenuitem>,
 	  <guimenuitem>Preferences</guimenuitem> menu.</para>
       </note>
 
       <para>If you have selected <quote>gconf support</quote> during
 	the build, you will also be able to view these settings using
 	<command>gconf-editor</command> under
 	<literal>apps/compiz</literal>.</para>
     </sect2>
   </sect1>
 
   <sect1 xml:id="x11-troubleshooting">
 
     <title>Troubleshooting</title>
 
     <para>If the mouse does not work, you will need to first configure
       it before proceeding.
       In recent <application>Xorg</application>
       versions, the <literal>InputDevice</literal> sections in
       <filename>xorg.conf</filename> are ignored in favor of the
       autodetected devices.  To restore the old behavior, add the
       following line to the <literal>ServerLayout</literal> or
       <literal>ServerFlags</literal> section of this file:</para>
 
       <programlisting>Option "AutoAddDevices" "false"</programlisting>
 
       <para>Input devices may then be configured as in previous
 	versions, along with any other options needed (e.g., keyboard
 	layout switching).</para>
 
       <note>
 	<para>As previously explained the
 	  <application>hald</application> daemon will, by default,
 	  automatically detect your keyboard.  There are chances that
 	  your keyboard layout or model will not be correct, desktop
 	  environments like <application>GNOME</application>,
 	  <application>KDE</application> or
 	  <application>Xfce</application> provide tools to configure
 	  the keyboard.  However, it is possible to set the keyboard
 	  properties directly either with the help of the
 	  &man.setxkbmap.1; utility or with a
 	  <application>hald</application>'s configuration rule.</para>
 
 	<para>For example if, one wants to use a PC 102 keys keyboard
 	  coming with a french layout, we have to create a keyboard
 	  configuration file for <application>hald</application>
 	  called <filename>x11-input.fdi</filename> and saved in the
 	  <filename>/usr/local/etc/hal/fdi/policy</filename>
 	  directory.  This file should contain the following
 	  lines:</para>
 
 	<programlisting>&lt;?xml version="1.0" encoding="iso-8859-1"?&gt;
 &lt;deviceinfo version="0.2"&gt;
   &lt;device&gt;
     &lt;match key="info.capabilities" contains="input.keyboard"&gt;
 	  &lt;merge key="input.x11_options.XkbModel" type="string"&gt;pc102&lt;/merge&gt;
 	  &lt;merge key="input.x11_options.XkbLayout" type="string"&gt;fr&lt;/merge&gt;
     &lt;/match&gt;
   &lt;/device&gt;
 &lt;/deviceinfo&gt;</programlisting>
 
 	<para>If this file already exists, just copy and add to your
 	  file the lines regarding the keyboard configuration.</para>
 
 	<para>You will have to reboot your machine to force
 	  <application>hald</application> to read this file.</para>
 
 	<para>It is possible to do the same configuration from an X
 	  terminal or a script with this command line:</para>
 
 	<screen>&prompt.user; <userinput>setxkbmap -model pc102 -layout fr</userinput></screen>
 
 	<para><filename>/usr/local/share/X11/xkb/rules/base.lst</filename>
 	  lists the various keyboard, layouts and options
 	  available.</para>
       </note>
 
       <indexterm><primary><application>&xorg;</application>
 	  tuning</primary></indexterm>
 
       <para>The <filename>xorg.conf.new</filename> configuration file
 	may now be tuned to taste.  Open the file in a text editor
 	such as &man.emacs.1; or &man.ee.1;.  If the monitor is an
 	older or unusual model that does not support autodetection of
 	sync frequencies, those settings can be added to
 	<filename>xorg.conf.new</filename> under the
 	<literal>"Monitor"</literal> section:</para>
 
       <programlisting>Section "Monitor"
 	Identifier   "Monitor0"
 	VendorName   "Monitor Vendor"
 	ModelName    "Monitor Model"
 	HorizSync    30-107
 	VertRefresh  48-120
 EndSection</programlisting>
 
       <para>Most monitors support sync frequency autodetection, making
 	manual entry of these values unnecessary.  For the few
 	monitors that do not support autodetection, avoid potential
 	damage by only entering values provided by the
 	manufacturer.</para>
 
       <para>X allows DPMS (Energy Star) features to be used with
 	capable monitors.  The &man.xset.1; program controls the
 	time-outs and can force standby, suspend, or off modes.  If
 	you wish to enable DPMS features for your monitor, you must
 	add the following line to the monitor section:</para>
 
       <programlisting>Option       "DPMS"</programlisting>
 
       <indexterm>
 	<primary><filename>xorg.conf</filename></primary>
       </indexterm>
 
       <para>While the <filename>xorg.conf.new</filename> configuration
 	file is still open in an editor, select the default resolution
 	and color depth desired.  This is defined in the
 	<literal>"Screen"</literal> section:</para>
 
       <programlisting>Section "Screen"
 	Identifier "Screen0"
 	Device     "Card0"
 	Monitor    "Monitor0"
 	DefaultDepth 24
 	SubSection "Display"
 		Viewport  0 0
 		Depth     24
 		Modes     "1024x768"
 	EndSubSection
 EndSection</programlisting>
 
       <para>The <literal>DefaultDepth</literal> keyword describes the
 	color depth to run at by default.  This can be overridden with
 	the <option>-depth</option> command line switch to
 	&man.Xorg.1;.  The <literal>Modes</literal> keyword describes
 	the resolution to run at for the given color depth.  Note that
 	only VESA standard modes are supported as defined by the
 	target system's graphics hardware.  In the example above, the
 	default color depth is twenty-four bits per pixel.  At this
 	color depth, the accepted resolution is 1024 by 768
 	pixels.</para>
 
       <para>Finally, write the configuration file and test it using
 	the test mode given above.</para>
 
       <note>
 	<para>One of the tools available to assist you during
 	  troubleshooting process are the
 	  <application>&xorg;</application> log files, which contain
 	  information on each device that the
 	  <application>&xorg;</application> server attaches to.
 	  <application>&xorg;</application> log file names are in the
 	  format of <filename>/var/log/Xorg.0.log</filename>.  The
 	  exact name of the log can vary from
 	  <filename>Xorg.0.log</filename> to
 	  <filename>Xorg.8.log</filename> and so forth.</para>
       </note>
 
       <para>If all is well, the configuration file needs to be
 	installed in a common location where &man.Xorg.1; can find it.
 	This is typically <filename>/etc/X11/xorg.conf</filename> or
 	<filename>/usr/local/etc/X11/xorg.conf</filename>.</para>
 
       <screen>&prompt.root; <userinput>cp xorg.conf.new /etc/X11/xorg.conf</userinput></screen>
 
       <para>The <application>&xorg;</application> configuration
 	process is now complete.  <application>&xorg;</application>
 	may be now started with the &man.startx.1; utility.  The
 	<application>&xorg;</application> server may also be started
 	with the use of &man.xdm.1;.</para>
 
       <sect2>
 	<title>Configuration with &intel; <literal>i810</literal>
 	  Graphics Chipsets</title>
 
 	<indexterm>
 	  <primary>&intel; i810 graphic chipset</primary>
 	</indexterm>
 
 	<para>Configuration with &intel; i810 integrated chipsets
 	  requires the <filename>agpgart</filename> AGP programming
 	  interface for <application>&xorg;</application> to drive the
 	  card.  See the &man.agp.4; driver manual page for more
 	  information.</para>
 
 	<para>This will allow configuration of the hardware as any
 	  other graphics board.  Note on systems without the
 	  &man.agp.4; driver compiled in the kernel, trying to load
 	  the module with &man.kldload.8; will not work.  This driver
 	  has to be in the kernel at boot time through being compiled
 	  in or using <filename>/boot/loader.conf</filename>.</para>
       </sect2>
 
       <sect2>
 	<title>Adding a Widescreen Flatpanel to the Mix</title>
 
 	<indexterm>
 	  <primary>widescreen flatpanel configuration</primary>
 	</indexterm>
 
 	<para>This section assumes a bit of advanced configuration
 	  knowledge.  If attempts to use the standard configuration
 	  tools above have not resulted in a working configuration,
 	  there is information enough in the log files to be of use in
 	  getting the setup working.  Use of a text editor will be
 	  necessary.</para>
 
 	<para>Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA, WXGA+,
 	  et.al.) formats support 16:10 and 10:9 formats or aspect
 	  ratios that can be problematic.  Examples of some common
 	  screen resolutions for 16:10 aspect ratios are:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>2560x1600</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>1920x1200</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>1680x1050</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>1440x900</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>1280x800</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>At some point, it will be as easy as adding one of these
 	  resolutions as a possible <literal>Mode</literal> in the
 	  <literal>Section "Screen"</literal> as such:</para>
 
 	<programlisting>Section "Screen"
 Identifier "Screen0"
 Device     "Card0"
 Monitor    "Monitor0"
 DefaultDepth 24
 SubSection "Display"
 	Viewport  0 0
 	Depth     24
 	Modes     "1680x1050"
 EndSubSection
 EndSection</programlisting>
 
 	<para><application>&xorg;</application> is smart enough to
 	  pull the resolution information from the widescreen via
 	  I2C/DDC information so it knows what the monitor can handle
 	  as far as frequencies and resolutions.</para>
 
 	<para>If those <literal>ModeLines</literal> do not exist in
 	  the drivers, one might need to give
 	  <application>&xorg;</application> a little hint.  Using
 	  <filename>/var/log/Xorg.0.log</filename> one can extract
 	  enough information to manually create a
 	  <literal>ModeLine</literal> that will work.  Simply look for
 	  information resembling this:</para>
 
 	<programlisting>(II) MGA(0): Supported additional Video Mode:
 (II) MGA(0): clock: 146.2 MHz   Image Size:  433 x 271 mm
 (II) MGA(0): h_active: 1680  h_sync: 1784  h_sync_end 1960 h_blank_end 2240 h_border: 0
 (II) MGA(0): v_active: 1050  v_sync: 1053  v_sync_end 1059 v_blanking: 1089 v_border: 0
 (II) MGA(0): Ranges: V min: 48  V max: 85 Hz, H min: 30  H max: 94 kHz, PixClock max 170 MHz</programlisting>
 
 	<para>This information is called EDID information.  Creating a
 	  <literal>ModeLine</literal> from this is just a matter of
 	  putting the numbers in the correct order:</para>
 
 	<programlisting>ModeLine &lt;name&gt; &lt;clock&gt; &lt;4 horiz. timings&gt; &lt;4 vert. timings&gt;</programlisting>
 
 	<para>So that the <literal>ModeLine</literal> in
 	  <literal>Section "Monitor"</literal> for this example would
 	  look like this:</para>
 
 	<programlisting>Section "Monitor"
 Identifier      "Monitor1"
 VendorName      "Bigname"
 ModelName       "BestModel"
 ModeLine        "1680x1050" 146.2 1680 1784 1960 2240 1050 1053 1059 1089
 Option          "DPMS"
 EndSection</programlisting>
 
 	<para>Now having completed these simple editing steps, X
 	  should start on your new widescreen monitor.</para>
       </sect2>
 
       <sect2 xml:id="compiz-troubleshooting">
 	<title>Troubleshooting Compiz&nbsp;Fusion</title>
 
 	<qandaset>
 	  <qandaentry>
 	    <question xml:id="no-decorations">
 	      <para>I have installed
 		<application>Compiz&nbsp;Fusion</application>, and
 		after running the commands you mention, my windows are
 		left without title bars and buttons.  What is
 		wrong?</para>
 	    </question>
 
 	    <answer>
 	      <para>You are probably missing a setting in
 		<filename>/etc/X11/xorg.conf</filename>.  Review this
 		file carefully and check especially the
 		<literal>DefaultDepth</literal> and
 		<literal>AddARGBGLXVisuals</literal>
 		directives.</para>
 	    </answer>
 	  </qandaentry>
 
 	  <qandaentry>
 	    <question xml:id="xorg-crash">
 	      <para>When I run the command to start
 		<application>Compiz&nbsp;Fusion</application>, the X
 		server crashes and I am back at the console.  What is
 		wrong?</para>
 	    </question>
 
 	    <answer>
 	      <para>If you check
 		<filename>/var/log/Xorg.0.log</filename>, you
 		will probably find error messages during the X
 		startup.  The most common would be:</para>
 
 	      <screen>(EE) NVIDIA(0):     Failed to initialize the GLX module; please check in your X
 (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
 (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
 (EE) NVIDIA(0):     you continue to encounter problems, Please try
 (EE) NVIDIA(0):     reinstalling the NVIDIA driver.</screen>
 
 	    <para>This is usually the case when you upgrade
 	      <application>&xorg;</application>.  You will need to
 	      reinstall the <package>x11/nvidia-driver</package>
 	      package so glx is built again.</para>
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect2>
   </sect1>
 </chapter>
diff --git a/en_US.ISO8859-1/htdocs/advocacy/myths.xml b/en_US.ISO8859-1/htdocs/advocacy/myths.xml
index 753e6ca507..731f633fe8 100644
--- a/en_US.ISO8859-1/htdocs/advocacy/myths.xml
+++ b/en_US.ISO8859-1/htdocs/advocacy/myths.xml
@@ -1,398 +1,399 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
 "http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [
 <!ENTITY title "FreeBSD Advocacy Project">
 <!ENTITY url.articles "../doc/en_US.ISO8859-1/articles">
 ]>
 
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
       <title>&title;</title>
 
       <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
     </head>
 
     <body class="navinclude.about">
 
     <p>As the BSD projects (including DragonFlyBSD, &os;, NetBSD, and
       OpenBSD) have grown in size, a number of persistent myths have
       grown up around them.  Some of these are perpetuated by well
       meaning but misguided individuals, others by people pursuing
       their own agendas.</p>
 
     <p>This page aims to dispel those myths while remaining as
       dispassionate as possible.</p>
 
     <blockquote><b>Note:</b> Throughout this page, ''*BSD'' refers to
       all of the BSD Projects.  Where a myth or response is specific
       to a particular project it is indicated as such.</blockquote>
 
     <blockquote>If you are aware of an omission or error on this page,
       please let the <a href="mailto:doc@freebsd.org">&os;
       Documentation Project mailing list</a> know.</blockquote>
 
     <h2>Myths</h2>
 
     <h2>Index</h2>
 
     <ul>
 	<li><a href="#closed-model">*BSD has a closed development
 	  model, it's more ''Cathedral'' than ''Bazaar''</a></li>
 
         <li><a href="#own-distro">You can't make your own distributions or
 	  derivative works of *BSD</a></li>
 
         <li><a href="#server">*BSD makes a great server, but a poor
 	  desktop</a></li>
 
         <li><a href="#old-codebase">The *BSD codebase is old, outdated, and
 	  dying</a></li>
 
         <li><a href="#bsd-war">The *BSD projects are at war with one
 	  another, splinter groups form each week</a></li>
 
         <li><a href="#clustering">You can't cluster *BSD systems (parallel
 	  computing)</a></li>
 
         <li><a href="#support">There's no commercial support for
 	  *BSD</a></li>
 
         <li><a href="#applications">There are no applications for
 	  *BSD</a></li>
 
         <li><a href="#beats">*BSD is better than (some other system)</a></li>
 
         <li><a href="#beaten">(some other system) is better than *BSD</a></li>
 </ul>
 
     <h3>Myth: <a name="closed-model">*BSD</a> has a closed development
       model, it's more ''Cathedral'' than ''Bazaar''</h3>
 
     <p>Eric Raymond wrote an influential paper,
       ''<a
 	  href="http://www.catb.org/~esr/writings/cathedral-bazaar/"
 	  target="_blank"
 	  rel="noopener">The
 	  Cathedral and the Bazaar</a>'' in which the Linux
       development model (and the model Eric used for
       <tt>fetchmail</tt>) is held up as an example of how to do
       ''open'' development.  By contrast, the model employed by *BSD
       is often characterized as closed.</p>
 
     <p>The implicit value judgment is that ''bazaar'' (open) is good,
       and ''cathedral'' (closed) is bad.</p>
 
     <p>If anything, *BSD's development model is probably
       <strong>more</strong> akin to the ''bazaar'' that Eric describes
       than either Linux or <tt>fetchmail</tt>.</p>
 
     <p>Consider the following;</p>
 
     <ul>
         <li><p><b>All the *BSD projects:</b> The current, bleeding edge source
           code for FreeBSD, NetBSD, and OpenBSD is available for anyone to download
           from the Internet, 24 hours a day. You don't need to wait for
           someone else to roll a release.</p>
 
 	<p><b>FreeBSD:</b> An installable snapshot of the current
 	  progress is made weekly. These snapshots can be installed
 	  exactly like an ordinary release, and do not require installation
 	  over an existing system.</p>
 
 	<p><b>OpenBSD:</b> Installable snapshots are generated daily and if
 	  Theo thinks they are good enough, he uploads them to the mirrors.</p>
 
 	<p>Contrast this with Linux, where new kernel distributions are
 	  made available on an ad-hoc basis, and where the frequency of
 	  each Linux distribution release is at the whim of the individual
 	  vendor.</p>
 
 	<p>There's none of the Linux fanfare every time a new kernel is
 	  released, simply because for most *BSD users it is an every day
 	  event.</p></li>
 
         <li><p>Anyone can submit patches, bug reports, documentation, and
 	  other contributions. They can do this
 	  by using a web based
 	  interface.</p>
 
 	<p>Pointers to this system litter the documentation.</p></li>
 
 	<li><p>Not everyone can commit code changes to the *BSD code.
 	  You need to be a <em>committer</em> first.  Typically,
 	  people are offered ''commit privs'' after they have made a
 	  few well-thought out submissions to the project using
 	  Bugzilla or similar.</p>
 
 	<p>This is identical to the Linux mechanism. Only one person is
 	  (notionally) allowed to change the Kernel, Linus. But specific areas
 	  (such as the networking code) are delegated to other people.</p>
 
 	<p><i>Aside: Nik (nik@FreeBSD.org) is a case in point.  After
 	    making several submissions to the &os; Documentation
 	    Project and web pages, he was offered ''commit privs'' so
 	    that he did not have to keep bothering other committers to
 	    commit the changes.  He never had to ask for them, they
 	    were freely given.</i></p></li>
 </ul>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="own-distro">You</a> cannot make your own distributions
       or derivative works of *BSD</h3>
 
     <p>You can. You just need to say in the documentation and source
       files where the code is derived from. Multiple derivative
       projects exist:</p>
 
     <ul>
 	<li><p><a href="http://www.dragonflybsd.org/">DragonflyBSD</a>
 	  started as a code fork from
 	  FreeBSD 4.X, but it has since its own user community and
 	  development goals.</p></li>
 
 	<li><p><a href="https://wiki.gentoo.org/wiki/Gentoo_FreeBSD">Gentoo/FreeBSD</a>
 	  is an effort by the Gentoo Project to port their complete
 	  administration facilities to take advantage of the reliable
 	  FreeBSD kernel and userland.  This project is purely
 	  incomplete and experimental.</p></li>
 
 	<li><p><a href="&url.articles;/nanobsd/index.html">NanoBSD</a> is another
 	  project to produce reduced versions
 	  of FreeBSD to put it on a Compact Flash card or other mass
 	  storage.  It is also a part of the FreeBSD source tree, see
 	  /usr/src/tools/tools/nanobsd.</p></li>
 
-	<li><p><a href="https://www.furybsd.org">FuryBSD</a> is a
-	  brand new, open source &os; desktop.  FuryBSD pays homage to
-	  desktop BSD projects of the past PC-BSD and TrueOS with its
-	  graphical interface and adds additional tools like a live,
-	  hybrid USB/DVD image.  FuryBSD is completely free to use and
-	  distributed under the BSD license.</p></li>
+	<li><p><a href="https://nomadbsd.org/">NomadBSD</a> is a
+	persistent live system for USB flash drives, based on &os;.
+	Together with automatic hardware detection and setup, it is
+	configured to be used as a desktop system that works out of
+	the box, but can also be used for data recovery, for
+	educational purposes, or to test &os;'s hardware
+	compatibility.</p></li>
 
 	<li><p><a href="https://ghostbsd.org">GhostBSD</a> is derived
 	  from &os;, uses the GTK environment to provide a beautiful
 	  looks and comfortable experience on the modern BSD platform
 	  offering a natural and native &unix; work
 	  environment.</p></li>
 
 	<li><p><a href="https://www.midnightbsd.org">MidnightBSD</a>
 	  is a &os; derived operating system developed with desktop
 	  users in mind.  It includes all the software you'd expect
 	  for your daily tasks: mail, web browsing, word processing,
 	  gaming, and much more.</p></li>
 
 	<li><p><a href="http://www.pfsense.com">pfSense</a> is an open source
 	  firewall derived from the m0n0wall firewall system with several
 	  different goals and features, such as OpenBSD's Packet Filter (PF),
 	  FreeBSD 6.1, ALTQ support for excellent packet queuing and
 	  finally an integrated package management system for extending the
 	  environment with new features.</p></li>
 
 	<li><p><a href="https://hardenedbsd.org">HardenedBSD</a> was
 	  Founded in 2014 by Oliver Pinter and Shawn Webb, HardenedBSD
 	  is a security-enhanced fork of &os;.  The HardenedBSD
 	  Project is implementing many exploit mitigation and security
 	  technologies on top of &os;.</p></li>
 
 	<li><p><a href="https://opnsense.org">OPNsense</a> started as
 	  a fork of pfSense&copy; and m0n0wall in 2014, with its first
 	  official release in January 2015.  The project has evolved
 	  very quickly while still retaining familiar aspects of both
 	  m0n0wall and pfSense.  A strong focus on security and code
 	  quality drives the development of the project.</p></li>
 
 	<li><p><a href="https://www.freenas.org/">FreeNAS</a> is an
 	  operating system that can be installed on virtually any
 	  hardware platform to share data over a network.  FreeNAS is
 	  the simplest way to create a centralized and easily
 	  accessible place for your data.  Use FreeNAS with ZFS to
 	  protect, store, and back up all of your data.  FreeNAS is
 	  used everywhere, for the home, small business, and the
 	  enterprise.</p></li>
 
 	<li><p><a href="https://www.xigmanas.com/">XigmaNAS</a> is an
 	  embedded Open Source NAS (Network-Attached Storage)
 	  distribution based on &os;.</p></li>
 </ul>
 
     <p>Similarly to DragonflyBSD, OpenBSD was not a standalone project,
       it started as a spinoff from the NetBSD project, and has since evolved
       its own distinctive approach.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="server">*BSD</a> makes a great server, but a poor
       (&unix;) desktop</h3>
 
     <p>*BSD makes a great server. It also makes a great desktop. Many of
       the requirements for a server (responsiveness under load, stability,
       effective use of system resources) are the same requirements as for a
       desktop machine.</p>
 
     <p>*BSD has access to the same desktop tools (KDE, GNOME, Firefox,
       windowmanagers) as Linux.  And ''office'' applications such as
       LibreOffice suite work under *BSD too.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="old-codebase">The</a> BSD codebase is old, outdated, and
       dying</h3>
 
     <p>While the BSD codebase may be more than 20 years old, it is neither
       outdated nor dying.  Many professional users like the stability that years
       of testing has provided FreeBSD.</p>
 
     <p><a href="../features.html">Technological
       enhancements</a> continue to be added to *BSD.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="bsd-war">The</a> *BSD projects are at war with one another,
       splinter groups form each week</h3>
 
     <p>No. While occasional advocacy may get a touch heated, the *BSD flavors
       continue to work with one another. FreeBSD's Alpha port was initially
       heavily based on the work done by the NetBSD team. Both NetBSD and
       OpenBSD used the FreeBSD ports collection to bootstrap their own port
       sets. FreeBSD and NetBSD both integrate security fixes first discovered
       by the OpenBSD team.</p>
 
     <p>The FreeBSD and NetBSD projects separated more than twenty years
       ago. OpenBSD and DragonflyBSD are the only new BSD projects to
       split off in the last twenty years.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="clustering">You</a> can't cluster *BSD systems (parallel
       computing)</h3>
 
     <p>The following URLs should disprove this;</p>
 
     <ul>
 	<li><a href="https://people.FreeBSD.org/~brooks/papers/bsdcon2003/fbsdcluster/">
 	  https://people.FreeBSD.org/~brooks/papers/bsdcon2003/fbsdcluster/</a>
 	  Brooks Davis's paper about the implementation of a FreeBSD
 	  cluster with more than 300 CPU's</li>
 
 	<li><a href="http://www.openbsd.org/faq/pf/carp.html">
 	  http://www.openbsd.org/faq/pf/carp.html</a>
 	  OpenBSD's Common Address Redundancy Protocol (CARP) to
 	  build redundant clusters at the level of the firewall</li>
 
 	<li><a href="http://pf4freebsd.love2party.net/carp.html">
 	  http://pf4freebsd.love2party.net/carp.html</a>
 	  OpenBSD's CARP ported to FreeBSD</li>
 
     </ul>
 
     <p>Note, that
       <a href="mailto:freebsd-cluster@FreeBSD.org">freebsd-cluster</a>
       mailing list is available for further discussion about
       clustering of FreeBSD.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="support">There's no commercial support for *BSD</a></h3>
 
     <p><b>FreeBSD:</b> The <a href="../commercial/consult_bycat.html">FreeBSD
 	Commercial Vendors Page</a> lists companies that offer commercial
         support for FreeBSD.</p>
 
         <p>The <a href="http://www.freebsdmall.com">FreeBSD
 	  Mall</a> also offer commercial support, along with shirts,
 	  hats, books, software, and promotional items.</p>
 
     <p><b>OpenBSD:</b> The <a href="http://www.openbsd.org/support.html">OpenBSD Commercial
 	Consulting Page</a> lists companies that offer commercial support for
         OpenBSD.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="applications">There</a> are no applications for *BSD</h3>
 
     <p>The free software community started running on predominantly BSD
       systems (SunOS and similar). *BSD users can generally compile software
       written for these systems without needing to make any changes.</p>
 
     <p>In addition, each *BSD project uses a ''ports'' system to make
       the building of ported software much easier.</p>
 
     <p><b>FreeBSD:</b> There are currently more than 30,000
       applications ready to download and install in the FreeBSD ports
       collection. On i386 and AMD64, the Linux emulation layer will
       also run the vast majority of Linux applications. On the AMD64
       architectures there is a compatibility layer to run 32-bit FreeBSD binaries.</p>
 
     <p><b>NetBSD:</b> The Linux emulation layer will run the vast majority of
       i386 Linux applications, and the majority of SunOS4 applications can be
       run on a SPARCStation.</p>
 
     <p><b>OpenBSD:</b> There are currently more than 8000 applications
       ready to download and install in the OpenBSD ports collection. The Linux
       emulation layer will also run the vast majority of i386 Linux
       applications, and the majority of SunOS4 applications can be run on a
       SPARCStation.</p>
 
     <p>Both NetBSD and OpenBSD are able to use applications in FreeBSD's ports
       collection with minimal effort. Their lower number of ported
       applications reflects this.</p>
 
     <p>It is true that most companies when porting to PC Unix will choose Linux
       first. Fortunately, *BSD's Linux emulation layer will run these
       programs (Acrobat, StarOffice, Mathematica, WordPerfect, Quake, Intel
       ICC compiler, Compaq's Alpha compiler ...)
       with few, if any, problems.</p>
 
     <p>As a historical note, the first version of Netscape Navigator that ran
       on FreeBSD with Java support was the Linux version. These day you can
       also use a native FreeBSD version of Mozilla with a native Java
       plugin, all compiled conveniently from ports.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="beats">*BSD</a> is better than (insert other system)</h3>
 
     <p>This is user opinion only.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h3>Myth: <a name="beaten">(insert some other system)</a> is better than *BSD</h3>
 
     <p>This is user opinion only.</p>
 
     <hr noshade="noshade" size="1"/>
 
     <h2>Contributors</h2>
 
     <p>Members of the FreeBSD, NetBSD, and OpenBSD projects have contributed
       to this page;</p>
 
     <table width="100%">
 <tbody>
 <tr>
 <td>Nik Clayton
 	    &lt;<a href="mailto:nik@FreeBSD.org">nik@FreeBSD.org</a>&gt;</td>
 </tr>
 <tr>
 <td>Jordan Hubbard
 	    &lt;<a href="mailto:jkh@FreeBSD.org">jkh@FreeBSD.org</a>&gt;</td>
 </tr>
 <tr>
 <td>Ian F. Darwin
 	    &lt;<a href="mailto:ian@DarwinSys.com">ian@DarwinSys.com</a>&gt;</td>
 </tr>
 <tr>
 <td>Adrian Filipi-Martin
 	    &lt;<a href="mailto:adrian@ubergeeks.com">adrian@ubergeeks.com</a>&gt;</td>
 </tr>
 <tr>
 <td>Tom Rhodes
 		&lt;<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>&gt;</td>
 </tr>
 </tbody>
 </table>
 
 
   </body>
 </html>
diff --git a/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml b/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml
index 62e007c332..16942c4a9d 100644
--- a/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml
+++ b/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml
@@ -1,209 +1,209 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
 "http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [
 <!ENTITY title "FreeBSD Advocacy Project">
 ]>
 
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
       <title>&title;</title>
 
       <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
     </head>
 
     <body class="navinclude.about">
 
   <h1>Why Choose &os;?</h1>
 
     <p>Why would you consider using &os;?  We think that there are
       lots of reasons.  Here is a selection of reasons that some of
       our existing users gave for their choice of operating system.</p>
 
     <h2>The Community</h2>
 
       <p>&os; is a community-driven operating system despite it being
 	to a partial degree sponsored corporately.  &os; has active mailing lists,
 	forums, and IRC channels where experienced users and
 	developers are always willing to help the less
 	experienced.</p>
 
       <p>The community is largely driven by technology, not ideology,
 	and is focused on building the best possible system and making
 	&os; as widely used as possible, not on pushing any other
 	agendas.</p>
 
       <p>There is no dictator&mdash;benevolent or
 	otherwise&mdash;for the project.  The Core Team is elected and
 	is nominally responsible for overseeing the goals of the project,
 	but this is a very light touch.  Core mediates disputes between
 	developers, but rarely needs to take an active role in
 	development, beyond their separate contributions as individual
 	developers.</p>
 
     <h2>Stability</h2>
 
       <p>Stability means many different things.  &os; very rarely
 	crashes (and when it does it is usually due to hardware
 	faults), but while that was a great boast a decade ago, now it
 	is an expected feature for any operating system.</p>
 
       <p>Stability in &os; means much more than that.  It means that
 	upgrading the system does not require upgrading the user.
 	Configuration interfaces do change over time, but only when
 	there is a good reason.  If you learned how to use &os; in
 	2000, most of your knowledge would still be relevant.</p>
 
       <p>Backwards compatibility is very important to the &os; team,
 	and any release in a major release series is expected to
 	be able to run any code&mdash;including kernel
 	modules&mdash;that ran on an earlier version.  The entire base
 	system is developed together, including the kernel, the core
 	utilities, and the configuration system, so upgrades are
 	usually painless.  Included tools like mergemaster help update
 	configuration files with little or no manual intervention.</p>
 
     <h2>Early Adoption and Collaboration With Other Projects</h2>
 
       <p>&os; has been one of the first adopters of the LLVM
 	infrastructure, including the clang compiler and the libc++
 	stack.  The entire &os; system, including kernel and
 	userspace, can build with clang, and from &os; both clang
 	and the permissively-licensed libc++ are included, giving a
 	modern, BSD-licensed C++ stack.  Several &os; developers are
 	also active contributors to LLVM, ensuring that both projects
 	thrive together.</p>
 
       <p>This same collaboration works downstream, with projects like
-	FuryBSD, GhostBSD, MidnightBSD and pfSense building on top of
+	GhostBSD, MidnightBSD, NomadBSD and pfSense building on top of
 	the &os; base to provide desktop and firewall oriented
 	distributions, respectively.  These projects are not forks,
 	they base their work on the latest version of &os; and
 	customize the system for specific uses.</p>
 
     <h2>Simple Configuration</h2>
 
       <p>&os; service initialization is very simple.  Each service,
 	whether part of the base system or installed from a port, comes
 	with a script that is responsible for starting and stopping it
 	(and often some other options).  The /etc/rc.conf file
 	contains a list of variables for enabling and configuring
 	services.  Want to enable ssh?  Just add sshd_enable="YES" to
 	your rc.conf file.  This system makes it easy to see at a
 	glance everything that will be started when your system
 	boots.</p>
 
       <p>The rc system that reads this file understands dependencies
 	between services and so can automatically launch them in
 	parallel, or wait until one is finished before starting the
 	things that it needs.  You get all of the benefits of a modern
 	configuration system, without a complex interface.</p>
 
     <h2>Ports</h2>
 
       <p>The ports tree contains a large collection of third-party
 	software, including older versions of some things where the
 	userbase is divided about the benefits of upgrading, and a lot
 	of niche programs.  The chances are that anything you want to
 	run which works on &os; will be there.</p>
 
       <p>Unlike some other systems, &os; maintains a clean division
 	between the base system and third-party ports and packages.
 	All third-party software goes in /usr/local, so if you want to
 	repurpose a machine, it is trivial to simply delete all
 	installed packages and then start installing the ones that you
 	want.</p>
 
       <p>The pkg(8) tool makes working with binary packages
 	even easier, although source installs are still supported for
 	people who want the level of configurability that this
 	implies.</p>
 
     <h2>Security</h2>
 
       <p>Security is vital in any network-connected machine.  &os;
 	provides a number of tools for ensuring that you can maintain a
 	secure system, such as:</p>
 
       <ul>
 	<li>Jails, allowing you to run applications or entire systems
 	  in a sandbox that cannot access the rest of the system.  With
 	  tools like ezjail and ZFS you can instantly create a new
 	  jail with a clone of an existing system, using a tiny amount
 	  of disk space, and run untrusted code inside it.</li>
 	<li>Mandatory Access Control, from the TrustedBSD project,
 	  allowing you to configure access control policies for all
 	  operating system resources.</li>
 	<li>Capsicum, from &os; 9 onwards, allows developers to easily
 	  implement privilege separation, reducing the impact of
 	  compromised code.</li>
 	<li>The VuXML system for publishing vulnerabilities in ports,
 	  which integrates with tools such as pkg, so that your
 	  daily security email tells you about any known
 	  vulnerabilities in ported software.</li>
 	<li>Security event auditing, using the BSM standard.</li>
       </ul>
 
       <p>And, of course, all of the standard features that are
 	expected from a modern &unix; system including IPSec, SSH, and so
 	on.</p>
 
     <h2>ZFS</h2>
 
       <p>Cheap snapshots, clones, end-to-end checksums, deduplication,
 	compression, and no need to decide partition sizes on install.
 	Using ZFS for a few days makes going back to a more
 	traditional volume manager painful.  If you want to test
 	something with ZFS, it is trivial to just create a
 	snapshot and roll back if it didn't work.</p>
 
       <p>ZFS lets you clone an existing
 	jail in under a second, no matter how big the jail
 	itself is.</p>
 
     <h2>GEOM</h2>
 
       <p>Even without ZFS, &os; comes with a rich storage system.
 	GEOM layers providers and consumers in arbitrary ways,
 	allowing you to use two networked machines for
 	high-availability storage, use your choice of RAID level, or
 	add features like compression or encryption.</p>
 
     <h2>Working Sound</h2>
 
       <p>&os; 4.x introduced in-kernel sound mixing, so that multiple
 	applications could play sound at the same time even with cheap
 	sound cards with no hardware mixing support.  &os; 5.x
 	automatically allocated new channels to applications, without
 	any configuration.</p>
 
       <p>Now, &os; has low-latency sound mixing with per-application
 	volume controls and full support for the OSS 4 APIs out of the
 	box.  There is no need to configure a userspace sound daemon.
 	The same audio APIs that were used a decade ago still work on
 	&os;,  including some compatibility modes to allow
 	applications that try to manipulate the global volume to only
 	change their own.  If you want to watch DVDs with 5.1 surround
 	sound, just install your favourite media player and press
 	play.</p>
 
     <h2>My System, How I Want It</h2>
 
       <p>&os; gives you an easy-to-use, working, &unix;-like system.
 	This base system can then be extended easily.  If you want to
 	run KDE or GNOME, then just install the metapackage for the
 	version that you prefer.  If you want a headless server, then
 	it is equally easy to install the server tools that you want.</p>
 
       <p>It is easy to run the &os; installer via a serial port and to
 	configure the entire system from the terminal.  It is also easy
 	to install and use an existing desktop environment.  The
 	decisions about the kind of system you want to use are left to
 	you.</p>
 
       <p>If you are deploying &os; in a corporate environment, then
 	it is very easy to customise both the base system and the set
 	of installed packages for your specific requirements.  The
 	build system provides numerous tuneable variables allowing you
 	to build exactly the base system that meets your needs.</p>
   </body>
 </html>
diff --git a/en_US.ISO8859-1/htdocs/projects/newbies.xml b/en_US.ISO8859-1/htdocs/projects/newbies.xml
index db704b409a..5a889a8392 100644
--- a/en_US.ISO8859-1/htdocs/projects/newbies.xml
+++ b/en_US.ISO8859-1/htdocs/projects/newbies.xml
@@ -1,137 +1,138 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
 "http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [
 <!ENTITY title 'Resources for Newbies'>
 <!ENTITY url.articles "&base;/doc/en_US.ISO8859-1/articles">
 <!ENTITY url.books "&base;/doc/en_US.ISO8859-1/books">
 ]>
 
 <html xmlns="http://www.w3.org/1999/xhtml">
     <head>
       <title>&title;</title>
 
       <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
     </head>
 
     <body class="navinclude.docs">
 
     <h2><a>Getting &os;</a></h2>
 
     <p>The latest &os; releases are available <a
 	href="&enbase;/where.html">here</a>.  Before you begin,
 	please carefully read the <a
 	href="&url.books;/handbook/bsdinstall.html">installation
 	instructions</a>.</p>
 
     <h2><a>Learning about &os;</a></h2>
 
     <ul>
       <li><p>The <a href="&url.books;/handbook/index.html">&os;
 	Handbook</a> and <a
 	href="&url.books;/faq/index.html">Frequently Asked Questions
 	(FAQ)</a> are the main documents for &os;. Essential reading,
 	they contain a lot of material for newbies as well as advanced
 	users.  For users interested in installing a GUI, see the <a
 	href="&url.books;/handbook/x11.html">X Windows</a> chapter.
 	</p></li>
 
       <li><p><a href="&cgibase;/man.cgi">Manual pages</a> are good for
 	reference but not always the best introduction for a novice.
 	They generally provide information on a specific command,
 	driver or service.</p></li>
 
     </ul>
 
     <h2><a>Questions and Support</a></h2>
 
     <ul>
       <li><p>Join the &os;-Questions mailing list to see the questions
 	you were too afraid to ask, and their answers. Subscribe by
 	filling out the following form: <a
 	href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-questions">http://lists.FreeBSD.org/mailman/listinfo/freebsd-questions</a>.
 	You can look up old questions and answers via the <a
 	href="&base;/search/search.html#mailinglists">search</a>
 	page.</p></li>
 
       <li><p>The &os; <a href="https://forums.freebsd.org">Forums</a>
 	offer another support channel.  Many users have written various
 	tutorials and lots of new users receive help there.</p></li>
 
       <li><p>You can <a href="&base;/search/search.html">search</a> the
 	Handbook and FAQ, the whole web site, or the &os; mailing list
 	archives.</p></li>
 
       <li><p>The <a href="&base;/support.html">Support</a> page
 	contains a wealth of information about &os;, including mailing
 	lists, user groups, web and FTP sites, release information,
 	and links to some sources of &unix; information.</p></li>
     </ul>
 
     <h2><a>Learning about &os;-derived projects</a></h2>
 
     <p>&os; is widely used as a building block for other commercial
       and open-source operating systems.  Some of the most widely used
       and publicly available systems are listed below.</p>
 
     <ul>
       <li><p><a href="http://www.freenas.org">FreeNAS</a> is a storage
 	solution that can be installed on virtually any hardware
 	platform to share data over a network.  It uses ZFS to protect,
 	store, backup, all of your data.</p></li>
 
-      <li><p><a href="https://www.furybsd.org">FuryBSD</a> is a brand
-	new, open source &os; desktop.  FuryBSD pays homage to desktop
-	BSD projects of the past PC-BSD and TrueOS with its graphical
-	interface and adds additional tools like a live, hybrid
-	USB/DVD image.  FuryBSD is completely free to use and
-	distributed under the BSD license.</p></li>
-
       <li><p><a href="https://ghostbsd.org">GhostBSD</a> is derived
 	from &os;, GhostBSD uses the GTK environment to provide a
 	beautiful looks and comfortable experience on the modern BSD
 	platform offering a natural and native &unix; work
 	environment.</p></li>
 
       <li><p><a href="https://www.midnightbsd.org">MidnightBSD</a> is
 	a BSD-derived operating system developed with desktop users
 	in mind.  It includes all the software you'd expect for your
 	daily tasks: mail, web browsing, word processing, gaming,
 	and much more.</p></li>
 
+      <li><p><a href="https://nomadbsd.org/">NomadBSD</a> is a
+      persistent live system for USB flash drives, based on &os;.
+      Together with automatic hardware detection and setup, it is
+      configured to be used as a desktop system that works out
+      of the box, but can also be used for data recovery, for
+      educational purposes, or to test &os;'s hardware
+      compatibility.</p></li>
+
       <li><p><a href="http://www.pfsense.org">pfSense</a> is a &os;
 	based network security solution.  pfSense
 	software, with the help of the package system, is able to
 	provide the same functionality or more of common commercial
 	firewalls, without any of the artificial limitations.  It has
 	successfully replaced every big name commercial firewall you can
 	imagine in numerous installations around the world.</p></li>
     </ul>
 
     <h2><a>How to Contribute</a></h2>
 
     <p>Everyone has something to contribute to the &os; community,
       even newbies! Some are busy working with the new advocacy group
       and some have become involved with the <a
 	href="&base;/docproj/docproj.html">Documentation Project</a> as
       reviewers.  Other &os; newbies might have particular skills and
       experiences to share, either computer related or not, or just
       want to meet new newbies and make them feel welcome. There are
       always people around who help others simply because they like
       to.</p>
 
     <p>Friends who run &os; are a great resource. No book can replace
       chatting on the phone or across a pizza with someone who has the
       same interests, enjoys similar accomplishments, and faces the
       same challenges. If you do not have many friends who use &os;,
       consider using your old &os; CDs to create some more.</p>
 
     <p><a href="&base;/usergroups.html">User groups</a> are good
       places to meet other &os; users. If there is no one nearby, you
       might consider starting one!</p>
 
     <p>For more information on getting involved in the community, see
       the <a
 	href="&enbase;/doc/en_US.ISO8859-1/articles/contributing/index.html">Contributing
 	to &os;</a> article.</p>
   </body>
 </html>
diff --git a/en_US.ISO8859-1/htdocs/where.xml b/en_US.ISO8859-1/htdocs/where.xml
index 1b91724cda..66bdc6ef5f 100644
--- a/en_US.ISO8859-1/htdocs/where.xml
+++ b/en_US.ISO8859-1/htdocs/where.xml
@@ -1,560 +1,562 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
 "http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [
 <!ENTITY title "Download FreeBSD">
 <!ENTITY url.rel "https://download.FreeBSD.org/ftp/releases">
 <!ENTITY url.snapshot "https://download.FreeBSD.org/ftp/snapshots">
 ]>
 
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
       <title>&title;</title>
 
       <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
     </head>
 
     <body class="navinclude.download">
 
     <a name="choose-version"></a>
 
     <a name="choose-arch"></a>
 
     <h2>Choosing an Architecture</h2>
 
     <p>Most users of &os; will have hardware for either the amd64,
       i386, or armv6 architectures.</p>
 
     <p>Modern PCs use the amd64 architecture, including those with
       Intel&reg; branded processors.  Computers with more than
       3&nbsp;GB of memory should use amd64.  If the computer is an
       older, 32-bit only model, use i386.  For embedded devices and
       single-board computers (SBC) such as the Raspberry Pi, Beagle
       Bone Black, Panda Board, and Zed Board, use the armv6 SD card
       image which supports ARMv6 and ARMv7 processors.</p>
 
     <p>All other users should reference the
       <a href="&base;/platforms/index.html">complete list</a>
       of supported &os; platforms.</p>
 
     <a name="choose-image"></a>
 
     <h2>Choosing an Image</h2>
 
     <p>The &os; installer can be downloaded in a number of different
       formats including CD (disc1), DVD (dvd1), and Network Install
       (bootonly) sized ISO
       Disc Images, as well as regular and mini USB memory stick
       images.  Recent versions of &os; are also offered as prebuilt
       expandable Virtual Machine images, and as SD Card images for embedded
       platforms.</p>
 
     <a name="help-statistics"></a>
 
     <h2>&os;&nbsp;Deployment Statistics</h2>
 
     <p>While &os; does not gather deployment statistics, having
       statistical information available is essential.  Please consider
       installing the <a
 	href="https://www.freshports.org/sysutils/bsdstats/">sysutils/bsdstats</a>
       package, which collects hardware and software statistics,
       helping developers understand how to best focus their
       efforts.  The information collected is available at the
       <a href="http://bsdstats.org">bsdstats.org</a> website.</p>
 
     <a name="download"></a>
 
     <a name="download-rel122"></a>
 
     <h1>&os; &rel122.current;-RELEASE</h1>
 
     <table class="tblbasic tblwide tbldownload">
       <tbody>
 	<tr>
 	  <th>Installer Images</th>
 	  <th>Virtual Machine Images</th>
 	  <th>SD Card Images</th>
 	  <th>Documentation</th>
 	</tr>
 	<tr>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/amd64/amd64/ISO-IMAGES/&rel122.current;/">amd64</a></li>
 	      <li><a href="&url.rel;/i386/i386/ISO-IMAGES/&rel122.current;/">i386</a></li>
 	      <li><a href="&url.rel;/powerpc/powerpc/ISO-IMAGES/&rel122.current;/">powerpc</a></li>
 	      <li><a href="&url.rel;/powerpc/powerpc64/ISO-IMAGES/&rel122.current;/">powerpc64</a></li>
 	      <li><a href="&url.rel;/powerpc/powerpcspe/ISO-IMAGES/&rel122.current;/">powerpcspe</a></li>
 	      <li><a href="&url.rel;/sparc64/sparc64/ISO-IMAGES/&rel122.current;/">sparc64</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel122.current;/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/VM-IMAGES/README.txt">README</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel122.current;-RELEASE/amd64/Latest/">amd64</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel122.current;-RELEASE/i386/Latest/">i386</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel122.current;-RELEASE/aarch64/Latest/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv6-RPI-B.img.xz">RPI-B</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv7-BANANAPI.img.xz">BANANAPI</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv7-CUBIEBOARD.img.xz">CUBIEBOARD</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv7-CUBIEBOARD2.img.xz">CUBIEBOARD2</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv7-CUBOX-HUMMINGBOARD.img.xz">CUBOX-HUMMINGBOARD</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv7-GENERICSD.img.xz">GENERICSD</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv7-RPI2.img.xz">RPI2</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv7-PANDABOARD.img.xz">PANDABOARD</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm-armv7-WANDBOARD.img.xz">WANDBOARD</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm64-aarch64-PINE64.img.xz">PINE64</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm64-aarch64-PINE64-LTS.img.xz">PINE64-LTS</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel122.current;/&os;-&rel122.current;-RELEASE-arm64-aarch64-RPI3.img.xz">RPI3</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdocslist">
 	      <li><a href="&base;/releases/index.html#current">Released</a>: &rel122.current.date;</li>
 	      <li><a href="&u.rel122.notes;">Release Notes</a></li>
 	      <li><a href="&u.rel122.readme;">Readme</a></li>
 	      <li><a href="&u.rel122.hardware;">Hardware Compatibility List</a></li>
 	      <li><a href="&u.rel122.installation;">Installation Instructions</a></li>
 	      <li><a href="&u.rel122.errata;">Errata</a></li>
 	      <li><a href="&u.rel122.signatures;">Signed Checksums</a></li>
 	    </ul>
 	  </td>
 	</tr>
       </tbody>
     </table>
     <br />
 
     <a name="download-rel121"></a>
 
     <h1>&os; &rel121.current;-RELEASE</h1>
 
     <table class="tblbasic tblwide tbldownload">
       <tbody>
 	<tr>
 	  <th>Installer Images</th>
 	  <th>Virtual Machine Images</th>
 	  <th>SD Card Images</th>
 	  <th>Documentation</th>
 	</tr>
 	<tr>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/amd64/amd64/ISO-IMAGES/&rel121.current;/">amd64</a></li>
 	      <li><a href="&url.rel;/i386/i386/ISO-IMAGES/&rel121.current;/">i386</a></li>
 	      <li><a href="&url.rel;/powerpc/powerpc/ISO-IMAGES/&rel121.current;/">powerpc</a></li>
 	      <li><a href="&url.rel;/powerpc/powerpc64/ISO-IMAGES/&rel121.current;/">powerpc64</a></li>
 	      <li><a href="&url.rel;/powerpc/powerpcspe/ISO-IMAGES/&rel121.current;/">powerpcspe</a></li>
 	      <li><a href="&url.rel;/sparc64/sparc64/ISO-IMAGES/&rel121.current;/">sparc64</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel121.current;/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/VM-IMAGES/README.txt">README</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel121.current;-RELEASE/amd64/Latest/">amd64</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel121.current;-RELEASE/i386/Latest/">i386</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel121.current;-RELEASE/aarch64/Latest/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv6-RPI-B.img.xz">RPI-B</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-BANANAPI.img.xz">BANANAPI</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-BEAGLEBONE.img.xz">BEAGLEBONE</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-CUBIEBOARD.img.xz">CUBIEBOARD</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-CUBIEBOARD2.img.xz">CUBIEBOARD2</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-CUBOX-HUMMINGBOARD.img.xz">CUBOX-HUMMINGBOARD</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-GENERICSD.img.xz">GENERICSD</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-RPI2.img.xz">RPI2</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-PANDABOARD.img.xz">PANDABOARD</a></li>
 	      <li><a href="&url.rel;/arm/armv7/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm-armv7-WANDBOARD.img.xz">WANDBOARD</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm64-aarch64-PINE64.img.xz">PINE64</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm64-aarch64-PINE64-LTS.img.xz">PINE64-LTS</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel121.current;/&os;-&rel121.current;-RELEASE-arm64-aarch64-RPI3.img.xz">RPI3</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdocslist">
 	      <li><a href="&base;/releases/index.html#current">Released</a>: &rel121.current.date;</li>
 	      <li><a href="&u.rel121.notes;">Release Notes</a></li>
 	      <li><a href="&u.rel121.readme;">Readme</a></li>
 	      <li><a href="&u.rel121.hardware;">Hardware Compatibility List</a></li>
 	      <li><a href="&u.rel121.installation;">Installation Instructions</a></li>
 	      <li><a href="&u.rel121.errata;">Errata</a></li>
 	      <li><a href="&u.rel121.signatures;">Signed Checksums</a></li>
 	    </ul>
 	  </td>
 	</tr>
       </tbody>
     </table>
     <br />
 
     <a name="download-rel114"></a>
 
     <h1>&os; &rel114.current;-RELEASE</h1>
 
     <table class="tblbasic tblwide tbldownload">
       <tbody>
 	<tr>
 	  <th>Installer Images</th>
 	  <th>Virtual Machine Images</th>
 	  <th>SD Card Images</th>
 	  <th>Documentation</th>
 	</tr>
 	<tr>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/amd64/amd64/ISO-IMAGES/&rel114.current;/">amd64</a></li>
 	      <li><a href="&url.rel;/i386/i386/ISO-IMAGES/&rel114.current;/">i386</a></li>
 	      <li><a href="&url.rel;/powerpc/powerpc/ISO-IMAGES/&rel114.current;/">powerpc</a></li>
 	      <li><a href="&url.rel;/powerpc/powerpc64/ISO-IMAGES/&rel114.current;/">powerpc64</a></li>
 	      <li><a href="&url.rel;/sparc64/sparc64/ISO-IMAGES/&rel114.current;/">sparc64</a></li>
 	      <li><a href="&url.rel;/arm64/aarch64/ISO-IMAGES/&rel114.current;/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/VM-IMAGES/README.txt">README</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel114.current;-RELEASE/amd64/Latest/">amd64</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel114.current;-RELEASE/i386/Latest/">i386</a></li>
 	      <li><a href="&url.rel;/VM-IMAGES/&rel114.current;-RELEASE/aarch64/Latest/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel114.current;/&os;-&rel114.current;-RELEASE-arm-armv6-BANANAPI.img.xz">BANANAPI</a></li>
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel114.current;/&os;-&rel114.current;-RELEASE-arm-armv6-BEAGLEBONE.img.xz">BEAGLEBONE</a></li>
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel114.current;/&os;-&rel114.current;-RELEASE-arm-armv6-CUBIEBOARD.img.xz">CUBIEBOARD</a></li>
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel114.current;/&os;-&rel114.current;-RELEASE-arm-armv6-CUBIEBOARD2.img.xz">CUBIEBOARD2</a></li>
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel114.current;/&os;-&rel114.current;-RELEASE-arm-armv6-CUBOX-HUMMINGBOARD.img.xz">CUBOX-HUMMINGBOARD</a></li>
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel114.current;/&os;-&rel114.current;-RELEASE-arm-armv6-RPI-B.img.xz">RPI-B</a></li>
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel114.current;/&os;-&rel114.current;-RELEASE-arm-armv6-RPI2.img.xz">RPI2</a></li>
 	      <li><a href="&url.rel;/arm/armv6/ISO-IMAGES/&rel114.current;/&os;-&rel114.current;-RELEASE-arm-armv6-WANDBOARD.img.xz">WANDBOARD</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdocslist">
 	      <li><a href="&base;/releases/index.html#current">Released</a>: &rel114.current.date;</li>
 	      <li><a href="&u.rel114.notes;">Release Notes</a></li>
 	      <li><a href="&u.rel114.readme;">Readme</a></li>
 	      <li><a href="&u.rel114.hardware;">Hardware Compatibility List</a></li>
 	      <li><a href="&u.rel114.installation;">Installation Instructions</a></li>
 	      <li><a href="&u.rel114.errata;">Errata</a></li>
 	      <li><a href="&u.rel114.signatures;">Signed Checksums</a></li>
 	    </ul>
 	  </td>
 	</tr>
       </tbody>
     </table>
     <br />
 
     &beta.desc;
     &beta.second;
 
     <a name="download-snapshots"></a>
 
     <h1>Development Snapshots</h1>
 
     <p>If you are interested in a purely experimental
       <strong>snapshot</strong> release of &os;-CURRENT (AKA
       &rel.head;-CURRENT), aimed at developers and bleeding-edge
       testers only, then please see the <a
 	href="&base;/snapshots/">&os; Snapshot Releases</a> page.  For
       more information about past, present and future releases in
       general, please visit the <a
 	href="&base;/releases/index.html">release information
 	page</a>.</p>
 
     <h1>&os; &rel.head;-CURRENT</h1>
 
     <table class="tblbasic tblwide tbldownload">
       <tbody>
 	<tr>
 	  <th>Installer Images</th>
 	  <th>Virtual Machine Images</th>
 	  <th>SD Card Images</th>
 	  <th>Documentation</th>
 	</tr>
 	<tr>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.snapshot;/amd64/amd64/ISO-IMAGES/&rel.head;/">amd64</a></li>
 	      <li><a href="&url.snapshot;/i386/i386/ISO-IMAGES/&rel.head;/">i386</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpc/ISO-IMAGES/&rel.head;/">powerpc</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpc64/ISO-IMAGES/&rel.head;/">powerpc64</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpc64le/ISO-IMAGES/&rel.head;/">powerpc64le</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpcspe/ISO-IMAGES/&rel.head;/">powerpcspe</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel.head;/">armv6</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel.head;/">armv7</a></li>
 	      <li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel.head;/">aarch64</a></li>
 	      <li><a href="&url.snapshot;/riscv/riscv64/ISO-IMAGES/&rel.head;/">riscv64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel.head;-CURRENT/amd64/Latest/">amd64</a></li>
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel.head;-CURRENT/i386/Latest/">i386</a></li>
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel.head;-CURRENT/aarch64/Latest/">aarch64</a></li>
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel.head;-CURRENT/riscv64/Latest/">riscv64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li>aarch64</li>
 	      <li><ul class="txtdownloadlist">
 		<li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel.head;/">PINE64</a></li>
 		<li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel.head;/">PINE64-LTS</a></li>
 		<li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel.head;/">RPI3</a></li>
 	      </ul></li>
 	      <li>armv6/armv7</li>
 	      <li><ul class="txtdownloadlist">
 		<li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel.head;/">GENERICSD</a></li>
 		<li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel.head;/">RPI-B</a></li>
 	      </ul></li>
 	      <li>riscv64</li>
 	      <li><ul class="txtdownloadlist">
 		<li><a href="&url.snapshot;/riscv/riscv64/ISO-IMAGES/&rel.head;/">GENERICSD</a></li>
 	      </ul></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdocslist">
 	    <?ignore
 	      <li><a href="&base;/releases/13.0R/relnotes.html">Release Notes</a></li>
 	      ?>
 	    <li>&nbsp;</li>
 	    </ul>
 	  </td>
 	</tr>
       </tbody>
     </table>
 
     <p>&nbsp;</p>
 
     <h1>&os; &rel122.current;-STABLE</h1>
 
     <table class="tblbasic tblwide tbldownload">
       <tbody>
 	<tr>
 	  <th>Installer Images</th>
 	  <th>Virtual Machine Images</th>
 	  <th>SD Card Images</th>
 	  <th>Documentation</th>
 	</tr>
 	<tr>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.snapshot;/amd64/amd64/ISO-IMAGES/&rel122.current;/">amd64</a></li>
 	      <li><a href="&url.snapshot;/i386/i386/ISO-IMAGES/&rel122.current;/">i386</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpc/ISO-IMAGES/&rel122.current;/">powerpc</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpc64/ISO-IMAGES/&rel122.current;/">powerpc64</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpcspe/ISO-IMAGES/&rel122.current;/">powerpcspe</a></li>
 	      <li><a href="&url.snapshot;/sparc64/sparc64/ISO-IMAGES/&rel122.current;/">sparc64</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel122.current;/">armv6</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">armv7</a></li>
 	      <li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel122.current;/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel122.current;-STABLE/amd64/Latest/">amd64</a></li>
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel122.current;-STABLE/i386/Latest/">i386</a></li>
 	      <?ignore
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel122.current;-STABLE/aarch64/Latest/">aarch64</a></li>
 	      ?>
 	      <li>&nbsp;</li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">BANANAPI</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">BEAGLEBONE</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">CUBIEBOARD</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">CUBIEBOARD2</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">CUBOX/HUMMINGBOARD</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">GENERICSD</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">PANDABOARD</a></li>
 	      <li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel122.current;/">PINE64</a></li>
 	      <li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel122.current;/">PINE64-LTS</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel122.current;/">RPI-B</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">RPI2</a></li>
 	      <li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel122.current;/">RPI3</a></li>
 	      <li><a href="&url.snapshot;/arm/armv7/ISO-IMAGES/&rel122.current;/">WANDBOARD</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdocslist">
 	      <?ignore
 	      <li><a href="&base;/relnotes/&rel122.current.major;-STABLE/relnotes/article.html">Release Notes</a></li>
 	      ?>
 	      <li>&nbsp;</li>
 	    </ul>
 	  </td>
 	</tr>
       </tbody>
     </table>
 
     <p>&nbsp;</p>
 
     <h1>&os; &rel114.current;-STABLE</h1>
 
     <table class="tblbasic tblwide tbldownload">
       <tbody>
 	<tr>
 	  <th>Installer Images</th>
 	  <th>Virtual Machine Images</th>
 	  <th>SD Card Images</th>
 	  <th>Documentation</th>
 	</tr>
 	<tr>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.snapshot;/amd64/amd64/ISO-IMAGES/&rel114.current;/">amd64</a></li>
 	      <li><a href="&url.snapshot;/i386/i386/ISO-IMAGES/&rel114.current;/">i386</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpc/ISO-IMAGES/&rel114.current;/">powerpc</a></li>
 	      <li><a href="&url.snapshot;/powerpc/powerpc64/ISO-IMAGES/&rel114.current;/">powerpc64</a></li>
 	      <li><a href="&url.snapshot;/sparc64/sparc64/ISO-IMAGES/&rel114.current;/">sparc64</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">armv6</a></li>
 	      <li><a href="&url.snapshot;/arm64/aarch64/ISO-IMAGES/&rel114.current;/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel114.current;-STABLE/amd64/Latest/">amd64</a></li>
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel114.current;-STABLE/i386/Latest/">i386</a></li>
 	      <li><a href="&url.snapshot;/VM-IMAGES/&rel114.current;-STABLE/aarch64/Latest/">aarch64</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdownloadlist">
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">BANANAPI</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">BEAGLEBONE</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">CUBIEBOARD</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">CUBIEBOARD2</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">CUBOX/HUMMINGBOARD</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">RPI2</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">RPI-B</a></li>
 	      <li><a href="&url.snapshot;/arm/armv6/ISO-IMAGES/&rel114.current;/">WANDBOARD</a></li>
 	    </ul>
 	  </td>
 	  <td>
 	    <ul class="txtdocslist">
 	      <?ignore
 	      <li><a href="&base;/relnotes/&rel114.current.major;-STABLE/relnotes/article.html">Release Notes</a></li>
 	      ?>
 	      <li>&nbsp;</li>
 	    </ul>
 	  </td>
 	</tr>
       </tbody>
     </table>
 
     <p>If you plan on getting &os; via HTTP or FTP, please check
       the listing of <a
 	href="&base;/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"><strong>mirror
 	  sites</strong></a> in the Handbook to see if there is a site
       closer to you.</p>
 
     <a name="install"></a>
 
     <h2>Install &os;</h2>
 
     <p>There are many options for installing &os;, including
       installation from CD-ROM, DVD, USB Memory Stick or even directly
       using anonymous FTP, HTTP, or NFS.  Please read through the <a
       href="&base;/doc/en_US.ISO8859-1/books/handbook/bsdinstall.html">&os;
       installation guide</a> before downloading the entire &os;
       distribution.</p>
 
     <a name="distribution"></a>
 
     <h2>Purchase &os; Media</h2>
 
     <p>&os; can be acquired on CD-ROM or DVD from <a
 	href="http://www.freebsdmall.com/">FreeBSD Mall</a>, or
       one of the other <a
 	href="&base;/doc/en_US.ISO8859-1/books/handbook/mirrors.html">CD-ROM
 	and DVD Publishers</a>.</p>
 
     <a name="past"></a>
 
     <h2>Past Releases</h2>
 
     <p>For downloading past releases, please visit the <a
 	href="http://ftp-archive.FreeBSD.org/pub/FreeBSD-Archive/old-releases/">FTP
 	archive</a>.</p>
 
     <a name="derived"></a>
 
     <h2>&os;-derived Operating System Distributions</h2>
 
     <p>&os; is widely used as a building block for other commercial
       and open-source operating systems.  The projects below are
       widely used and of particular interest to &os; users.</p>
 
     <ul class="txtdownloadlist">
       <li><p><a href="https://www.freenas.org">FreeNAS</a> is an open
 	source storage platform based on &os; and supports sharing
 	across Windows, Apple, and UNIX-like systems.</p></li>
 
-      <li><p><a href="https://www.furybsd.org">FuryBSD</a> is a brand
-	new, open source &os; desktop.  FuryBSD pays homage to desktop
-	BSD projects of the past PC-BSD and TrueOS with its graphical
-	interface and adds additional tools like a live, hybrid
-	USB/DVD image.  FuryBSD is completely free to use and
-	distributed under the BSD license.</p></li>
-
       <li><p><a href="https://ghostbsd.org">GhostBSD</a> is derived
 	from &os;, GhostBSD uses the GTK environment to provide a
 	beautiful looks and comfortable experience on the modern BSD
 	platform offering a natural and native &unix; work
 	environment.</p></li>
 
       <li><p><a href="https://www.midnightbsd.org">MidnightBSD</a> is
 	a BSD-derived operating system developed with desktop users in
 	mind.  It includes all the software you'd expect for your
 	daily tasks: mail, web browsing, word processing, gaming,
 	and much more.</p></li>
 
+      <li><p><a href="https://nomadbsd.org/">NomadBSD</a> is
+      a persistent live system for USB flash drives, based on &os;.
+      Together with automatic hardware detection and setup,
+      it is configured to be used as a desktop system that works out
+      of the box, but can also be used for data recovery, for
+      educational purposes, or to test &os;'s hardware
+      compatibility.</p></li>
+
+
       <li><p><a href="http://www.pfsense.org">pfSense</a> is a
 	&os; based customized distribution tailored for
 	use as a firewall and router.</p></li>
     </ul>
 
     <a name="apps"></a>
 
     <h2>Applications and Utility Software</h2>
 
     <h3>The Ports Collection</h3>
 
     <p>The &os; Ports Collection is a diverse collection of utility
       and application software that has been ported to &os;.</p>
 
     <p>See <a href="&base;/doc/en_US.ISO8859-1/books/handbook/ports.html">
       <strong>Installing Applications: Packages and Ports</strong></a>
       in the Handbook.</p>
 
     <ul class="txtdownloadlist">
       <li><a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/">Download the &os;
 	  Ports Collection framework</a></li>
 
       <li><a href="&base;/ports/index.html">Web interface to the Ports
 	  Collection</a></li>
 
       <li><a href="http://www.freshports.org/">FreshPorts - a more
 	  advanced web interface to the Ports Collection</a></li>
     </ul>
 
     <p>For information about how <em>you</em> can contribute
       <em>your</em> favorite piece of software to the Ports Collection,
       have a look at <em><a
 	  href="&base;/doc/en_US.ISO8859-1/books/porters-handbook/index.html">The
 	  Porter's Handbook</a></em> and the article <em><a
 	  href="&base;/doc/en_US.ISO8859-1/articles/contributing/index.html">Contributing
 	  to &os;</a></em>.</p>
 
   </body>
 </html>