diff --git a/en_US.ISO8859-1/books/porters-handbook/book.xml b/en_US.ISO8859-1/books/porters-handbook/book.xml
index e606873275..6aa94dfffd 100644
--- a/en_US.ISO8859-1/books/porters-handbook/book.xml
+++ b/en_US.ISO8859-1/books/porters-handbook/book.xml
@@ -1,17041 +1,17039 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
 	"../../../share/xml/freebsd45.dtd" [
 <!ENTITY values.uses SYSTEM "uses.xml">
 ]>
 
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <book lang='en'>
   <bookinfo>
     <title>FreeBSD Porter's Handbook</title>
 
     <authorgroup>
       <corpauthor>The FreeBSD Documentation Project</corpauthor>
     </authorgroup>
 
     <pubdate>$FreeBSD$</pubdate>
 
     <copyright>
       <year>2000</year>
       <year>2001</year>
       <year>2002</year>
       <year>2003</year>
       <year>2004</year>
       <year>2005</year>
       <year>2006</year>
       <year>2007</year>
       <year>2008</year>
       <year>2009</year>
       <year>2010</year>
       <year>2011</year>
       <year>2012</year>
       <year>2013</year>
       <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation
 	Project</holder>
     </copyright>
 
     &trademarks;
 
     &legalnotice;
 
     <releaseinfo>$FreeBSD$</releaseinfo>
   </bookinfo>
 
   <chapter id="why-port">
     <title>Introduction</title>
 
     <para>The FreeBSD ports collection is the way almost everyone
       installs applications ("ports") on FreeBSD.  Like everything
       else about FreeBSD, it is primarily a volunteer effort.
       It is important to keep this in mind when reading this
       document.</para>
 
     <para>In FreeBSD, anyone may submit a new port, or volunteer
       to maintain an existing port if it is unmaintained&mdash;you
       do not need any special commit privileges to do so.</para>
 
   </chapter>
 
   <chapter id="own-port">
     <title>Making a New Port Yourself</title>
 
     <para>So, you are interested in making your own port or
       upgrading an existing one?  Great!</para>
 
     <para>What follows are some guidelines for creating a new port for
       FreeBSD.  If you want to upgrade an existing port, you should
       read this and then read <xref linkend="port-upgrading"/>.</para>
 
     <para>When this document is not sufficiently detailed, you should
       refer to <filename>/usr/ports/Mk/bsd.port.mk</filename>, which
       all port Makefiles include.  Even if you do not hack Makefiles
       daily, it is well commented, and you will still gain much
       knowledge from it.  Additionally, you may send specific
       questions to the &a.ports;.</para>
 
     <note>
       <para>Only a fraction of the variables
 	(<makevar><replaceable>VAR</replaceable></makevar>) that can
 	be overridden are mentioned in this document.  Most (if not
 	all) are documented at the start of
 	<filename>/usr/ports/Mk/bsd.port.mk</filename>; the others
 	probably ought to be.  Note that this file uses a non-standard
 	tab setting: <application>Emacs</application> and
 	<application>Vim</application> should recognize the setting on
 	loading the file.  Both &man.vi.1; and &man.ex.1; can be set
 	to use the correct value by typing <command>:set
 	  tabstop=4</command> once the file has been loaded.</para>
     </note>
 
     <para>
       Looking for something easy to start with? Take a look at the
       <ulink url="http://wiki.freebsd.org/WantedPorts">list of
 	requested ports</ulink> and see if you can work on one (or
       more).</para>
   </chapter>
 
   <chapter id="quick-porting">
     <title>Quick Porting</title>
 
     <para>This section tells you how to quickly create a new port.  In
       many cases, it is not sufficient, so you will have to read
       further on into the document.</para>
 
     <para>First, get the original tarball and put it into
       <makevar>DISTDIR</makevar>, which defaults to
       <filename>/usr/ports/distfiles</filename>.</para>
 
     <note>
       <para>The following assumes that the software compiled
 	out-of-the-box, i.e., there was absolutely no change required
 	for the port to work on your FreeBSD box.  If you needed to
 	change something, you will have to refer to the next section
 	too.</para>
     </note>
 
     <sect1 id="porting-makefile">
       <title>Writing the <filename>Makefile</filename></title>
 
       <para>The minimal <filename>Makefile</filename> would look
 	something like this:</para>
 
       <programlisting># &dollar;FreeBSD&dollar;
 
 PORTNAME=	oneko
 PORTVERSION=	1.1b
 CATEGORIES=	games
 MASTER_SITES=	ftp://ftp.cs.columbia.edu/archives/X11R5/contrib/
 
 MAINTAINER=	asami@FreeBSD.org
 COMMENT=	Cat chasing a mouse all over the screen
 
 MAN1=		oneko.1
 MANCOMPRESSED=	yes
 USE_IMAKE=	yes
 
 .include &lt;bsd.port.mk&gt;</programlisting>
 
       <note>
 	<para>In some cases, the <filename>Makefile</filename> of an
 	  existing port may contain additional lines in the header,
 	  such as the name of the port and the date it was created.
 	  This additional information has been declared obsolete, and
 	  is being phased out.</para>
       </note>
 
       <para>See if you can figure it out.  Do not worry about the
 	contents of the <literal>&dollar;FreeBSD&dollar;</literal>
 	line, it will be filled in automatically by SVN when the port
 	is imported to our main ports tree.  You can find a more
 	detailed example in the <link
 	  linkend="porting-samplem">sample Makefile</link>
 	section.</para>
     </sect1>
 
     <sect1 id="porting-desc">
       <title>Writing the Description Files</title>
 
       <para>There are two description files that are required for
 	any port, whether they actually package or not.  They are
 	<filename>pkg-descr</filename> and
 	<filename>pkg-plist</filename>.  Their
 	<filename>pkg-</filename> prefix distinguishes them from
 	other files.</para>
 
       <sect2>
 	<title><filename>pkg-descr</filename></title>
 
 	<para>This is a longer description of the port.  One to a few
 	  paragraphs concisely explaining what the port does is
 	  sufficient.</para>
 
 	<note>
 	  <para>This is <emphasis>not</emphasis> a manual or an
 	    in-depth description on how to use or compile the port!
 	    <emphasis>Please be careful if you are copying from the
 	    <filename>README</filename> or manpage</emphasis>; too
 	    often they are not a concise description of the port or
 	    are in an awkward format (e.g., manpages have justified
 	    spacing, as it looks particularly bad with monospaced
 	    fonts).</para>
 	</note>
 
 	<para>A well-written <filename>pkg-descr</filename> describes
 	  the port completely enough that users would not have to
 	  consult the documentation or visit the website to understand
 	  what the software does, how it can be useful, or what
 	  particularly nice features it has.  Mentioning certain
 	  requirements like a graphical toolkit, heavy dependencies,
 	  runtime environment, or implementation languages help users
 	  decide whether this port will work for them.</para>
 
 	<para>Include a URL to the official WWW homepage.
 	  Prepend <emphasis>one</emphasis> of
 	  the websites (pick the most common one) with
 	  <literal>WWW:</literal> (followed by single space) so that
 	  automated tools will work correctly.  If the URI is the root
 	  of the website or directory, it should be terminated with a
 	  slash.</para>
 
 	<note>
 	  <para>If the listed webpage for a port is not available, try
 	    to search the Internet first to see if the official site
 	    moved, was renamed, or is hosted elsewhere.</para>
 	</note>
 
 	<para>The following example shows how your
 	  <filename>pkg-descr</filename> should look:</para>
 
 	<programlisting>This is a port of oneko, in which a cat chases a poor mouse all over
 the screen.
  :
 (etc.)
 
 WWW: http://www.oneko.org/</programlisting>
       </sect2>
 
       <sect2>
 	<title><filename>pkg-plist</filename></title>
 
 	<para>This file lists all the files installed by the port.  It
 	  is also called the <quote>packing list</quote> because the
 	  package is generated by packing the files listed here.  The
 	  pathnames are relative to the installation prefix (usually
 	  <filename>/usr/local</filename>.  If you are using the
 	  <makevar>MAN<replaceable>n</replaceable></makevar> variables
 	  (as you should be), do not list any manpages here.  If the
 	  port creates directories during installation, make sure to
 	  add <literal>@dirrm</literal> lines to remove them when the
 	  package is deleted.</para>
 
 	<para>Here is a small example:</para>
 
 	<programlisting>bin/oneko
 lib/X11/app-defaults/Oneko
 lib/X11/oneko/cat1.xpm
 lib/X11/oneko/cat2.xpm
 lib/X11/oneko/mouse.xpm
 @dirrm lib/X11/oneko</programlisting>
 
 	<para>Refer to the &man.pkg.create.1; manual page for details
 	  on the packing list.</para>
 
 	<note>
 	  <para>It is recommended that you keep all the filenames in
 	    this file sorted alphabetically.  It will make verifying
 	    the changes when you upgrade the port much easier.</para>
 	</note>
 
 	<note>
 	  <para>Creating a packing list manually can be a very tedious
 	    task.  If the port installs a large numbers of files,
 	    <link linkend="plist-autoplist">creating the packing list
 	      automatically</link> might save time.</para>
 	</note>
 
 	<para>There is only one case when
 	  <filename>pkg-plist</filename> can be omitted from a port.
 	  If the port installs just a handful of files, and perhaps
 	  directories, the files and directories may be listed in the
 	  variables <makevar>PLIST_FILES</makevar> and
 	  <makevar>PLIST_DIRS</makevar>, respectively, within the
 	  port's <filename>Makefile</filename>.  For instance, we
 	  could get along without <filename>pkg-plist</filename> in
 	  the above <filename>oneko</filename> port by adding the
 	  following lines to the <filename>Makefile</filename>:</para>
 
 	<programlisting>PLIST_FILES=	bin/oneko \
 		lib/X11/app-defaults/Oneko \
 		lib/X11/oneko/cat1.xpm \
 		lib/X11/oneko/cat2.xpm \
 		lib/X11/oneko/mouse.xpm
 PLIST_DIRS=	lib/X11/oneko</programlisting>
 
 	<para>Of course, <makevar>PLIST_DIRS</makevar> should be left
 	  unset if a port installs no directories of its own.</para>
 
 	<para>The price for this way of listing port's files and
 	  directories is that you cannot use command sequences
 	  described in &man.pkg.create.1;.  Therefore, it is suitable
 	  only for simple ports and makes them even simpler.  At the
 	  same time, it has the advantage of reducing the number of
 	  files in the ports collection.  Please consider using this
 	  technique before you resort to
 	  <filename>pkg-plist</filename>.</para>
 
 	<para>Later we will see how <filename>pkg-plist</filename>
 	  and <makevar>PLIST_FILES</makevar> can be used to fulfill
 	  <link linkend="plist">more sophisticated
 	    tasks</link>.</para>
       </sect2>
     </sect1>
 
     <sect1 id="porting-checksum">
       <title>Creating the Checksum File</title>
 
       <para>Just type <command>make makesum</command>.  The ports make
 	rules will automatically generate the file
 	<filename>distinfo</filename>.</para>
 
       <para>If a file fetched has its checksum changed regularly and
 	you are certain the source is trusted (i.e., it comes from
 	manufacturer CDs or documentation generated daily), you should
 	specify these files in the <makevar>IGNOREFILES</makevar>
 	variable.  Then the checksum is not calculated for that file
 	when you run <command>make makesum</command>, but set to
 	<literal>IGNORE</literal>.</para>
     </sect1>
 
     <sect1 id="porting-testing">
       <title>Testing the Port</title>
 
       <para>You should make sure that the port rules do exactly what
 	you want them to do, including packaging up the port.  These
 	are the important points you need to verify.</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><filename>pkg-plist</filename> does not contain
 	    anything not installed by your port</para>
 	</listitem>
 
 	<listitem>
 	  <para><filename>pkg-plist</filename> contains everything
 	    that is installed by your port</para>
 	</listitem>
 
 	<listitem>
 	  <para>Your port can be installed multiple times using the
 	    <maketarget>reinstall</maketarget> target</para>
 	</listitem>
 
 	<listitem>
 	  <para>Your port <link linkend="plist-cleaning">cleans
 	      up</link> after itself upon deinstall</para>
 	</listitem>
       </itemizedlist>
 
       <procedure>
 	<title>Recommended Test Ordering</title>
 
 	<step>
 	  <para><command>make install</command></para>
 	</step>
 
 	<step>
 	  <para><command>make package</command></para>
 	</step>
 
 	<step>
 	  <para><command>make deinstall</command></para>
 	</step>
 
 	<step>
 	  <para><command>pkg_add
 	      <replaceable>package-name</replaceable></command></para>
 	</step>
 
 	<step>
 	  <para><command>make deinstall</command></para>
 	</step>
 
 	<step>
 	  <para><command>make reinstall</command></para>
 	</step>
 
 	<step>
 	  <para><command>make package</command></para>
 	</step>
 
 	<step>
 	  <para><command>make readme</command></para>
 	</step>
       </procedure>
 
       <para>Make sure that there are not any warnings issued in any of
 	the <maketarget>package</maketarget> and
 	<maketarget>deinstall</maketarget> stages.  After step 3,
 	check to see if all the new directories are correctly deleted.
 	Also, try using the software after step 4, to ensure that it
 	works correctly when installed from a package.</para>
 
       <para>The most thorough way to automate these steps is via
 	installing the <application>ports tinderbox</application>.
 	This maintains <literal>jails</literal> in which you can
 	test all of the above steps without changing the state of
 	your running system.  Please see
 	<filename>ports/ports-mgmt/tinderbox</filename> for more
 	information.</para>
     </sect1>
 
     <sect1 id="porting-portlint">
       <title>Checking Your Port with
 	<command>portlint</command></title>
 
       <para>Please use <command>portlint</command> to see if your port
 	conforms to our guidelines.  The <filename
 	  role="package">ports-mgmt/portlint</filename> program is
 	part of the ports collection.  In particular, you may want to
 	check if the <link linkend="porting-samplem">Makefile</link>
 	is in the right shape and the <link
 	  linkend="porting-pkgname">package</link> is named
 	appropriately.</para>
     </sect1>
 
     <sect1 id="porting-submitting">
       <title>Submitting the New Port</title>
 
       <para>Before you submit the new port, make sure you have read
 	the <link
 	  linkend="porting-dads">DOs and DON'Ts</link> section.</para>
 
       <para>Now that you are happy with your port, the only thing
 	remaining is to put it in the main &os; ports tree and make
 	everybody else happy about it too.  We do not need your
 	<filename>work</filename> directory or the
 	<filename>pkgname.tgz</filename> package, so delete them now.
 	Next, assuming your port is called oneko,
 	<command>cd</command> to the directory above where the
 	<literal>oneko</literal> directory is located, and then type
 	the following: <command>shar `find oneko` &gt;
 	  oneko.shar</command></para>
 
       <para>Include your <literal>oneko.shar</literal> file in a bug
 	report and send it with the &man.send-pr.1; program (see
 	<ulink
 	  url="&url.articles.contributing;/contrib-how.html#CONTRIB-GENERAL">Bug
 	  Reports and General Commentary</ulink> for more information
 	about &man.send-pr.1;).  Be sure to classify the bug report
 	as category <literal>ports</literal> and class
 	<literal>change-request</literal> (Do not mark the report
 	<literal>confidential</literal>!).  Also add a short
 	description of the program you ported to the
 	<quote>Description</quote> field of the PR (e.g., perhaps a
 	short version of the <makevar>COMMENT</makevar>), and add
 	the shar file to the <quote>Fix</quote> field.</para>
 
       <note>
 	<para>You can make our work a lot easier, if you use a good
 	  description in the synopsis of the problem report.  We
 	  prefer something like <quote>New port:
 	    &lt;category&gt;/&lt;portname&gt; &lt;short description of
 	    the port&gt;</quote> for new ports.  If you stick to this
 	  scheme, the chance that someone will take a look at your PR
 	  soon is much better.</para>
       </note>
 
       <para>One more time, <emphasis>do not include the original
 	  source distfile, the <filename>work</filename> directory, or
 	  the package you built with <command>make
 	  package</command></emphasis>; and, do use &man.shar.1; for
 	new ports, not &man.diff.1;.</para>
 
       <para>After you have submitted your port, please be patient.
 	Sometimes it can take a few months before a port is included
 	in &os;, although it might only take a few days.  You can
 	view the list of <ulink
 	  url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?category=ports">ports
 	  PRs waiting to be committed to &os;</ulink>.</para>
 
       <para>Once we have looked at your port, we will get back to you
 	if necessary, and put it in the tree.  Your name will also
 	be added to the list of <ulink
 	  url="&url.articles.contributors;/contrib-additional.html">Additional
 	  FreeBSD Contributors</ulink> and other files.</para>
     </sect1>
   </chapter>
 
   <chapter id="slow">
     <title>Slow Porting</title>
 
     <para>Ok, so it was not that simple, and the port required some
       modifications to get it to work.  In this section, we will
       explain, step by step, how to modify it to get it to work with
       the ports paradigm.</para>
 
     <sect1 id="slow-work">
       <title>How Things Work</title>
 
       <para>First, this is the sequence of events which occurs when
 	the user first types <command>make</command> in your port's
 	directory.  You may find that having
 	<filename>bsd.port.mk</filename> in another window while you
 	read this really helps to understand it.</para>
 
       <para>But do not worry if you do not really understand what
 	<filename>bsd.port.mk</filename> is doing, not many people
 	do...  <!-- smiley --><emphasis>:-)</emphasis></para>
 
       <procedure>
 	<step>
 	  <para>The <maketarget>fetch</maketarget> target is run.  The
 	    <maketarget>fetch</maketarget> target is responsible for
 	    making sure that the tarball exists locally in
 	    <makevar>DISTDIR</makevar>.  If
 	    <maketarget>fetch</maketarget> cannot find the required
 	    files in <makevar>DISTDIR</makevar> it will look up the
 	    URL <makevar>MASTER_SITES</makevar>, which is set in the
 	    Makefile, as well as our main FTP site at <ulink
 	      url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/"></ulink>,
 	    where we put sanctioned distfiles as backup.  It will then
 	    attempt to fetch the named distribution file with
 	    <makevar>FETCH</makevar>, assuming that the requesting
 	    site has direct access to the Internet.  If that succeeds,
 	    it will save the file in <makevar>DISTDIR</makevar> for
 	    future use and proceed.</para>
 	</step>
 
 	<step>
 	  <para>The <maketarget>extract</maketarget> target is run.
 	    It looks for your port's distribution file (typically a
 	    <command>gzip</command>ped tarball) in
 	    <makevar>DISTDIR</makevar> and unpacks it into a temporary
 	    subdirectory specified by <makevar>WRKDIR</makevar>
 	    (defaults to <filename>work</filename>).</para>
 	</step>
 
 	<step>
 	  <para>The <maketarget>patch</maketarget> target is run.
 	    First, any patches defined in
 	    <makevar>PATCHFILES</makevar> are applied.  Second, if any
 	    patch files named
 	    <filename>patch-<replaceable>*</replaceable></filename>
 	    are found in <makevar>PATCHDIR</makevar> (defaults to the
 	    <filename>files</filename> subdirectory), they are applied
 	    at this time in alphabetical order.</para>
 	</step>
 
 	<step>
 	  <para>The <maketarget>configure</maketarget> target is run.
 	    This can do any one of many different things.</para>
 
 	  <orderedlist>
 	    <listitem>
 	      <para>If it exists,
 		<filename>scripts/configure</filename> is run.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>If <makevar>HAS_CONFIGURE</makevar> or
 		<makevar>GNU_CONFIGURE</makevar> is set,
 		<filename><makevar>WRKSRC</makevar>/configure</filename>
 		is run.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>If <makevar>USE_IMAKE</makevar> is set,
 		<makevar>XMKMF</makevar> (default: <command>xmkmf
 		  -a</command>) is run.</para>
 	    </listitem>
 	  </orderedlist>
 	</step>
 
 	<step>
 	  <para>The <maketarget>build</maketarget> target is run.
 	    This is responsible for descending into the port's private
 	    working directory (<makevar>WRKSRC</makevar>) and building
 	    it.  If <makevar>USE_GMAKE</makevar> is set, GNU
 	    <command>make</command> will be used, otherwise the system
 	    <command>make</command> will be used.</para>
 	</step>
       </procedure>
 
       <para>The above are the default actions.  In addition, you can
 	define targets
 	<maketarget>pre-<replaceable>something</replaceable></maketarget>
 	or
 	<maketarget>post-<replaceable>something</replaceable></maketarget>,
 	or put scripts with those names, in the
 	<filename>scripts</filename> subdirectory, and they will be
 	run before or after the default actions are done.</para>
 
       <para>For example, if you have a
 	<maketarget>post-extract</maketarget> target defined in your
 	<filename>Makefile</filename>, and a file
 	<filename>pre-build</filename> in the
 	<filename>scripts</filename> subdirectory, the
 	<maketarget>post-extract</maketarget> target will be called
 	after the regular extraction actions, and the
 	<filename>pre-build</filename> script will be executed before
 	the default build rules are done.  It is recommended that you
 	use <filename>Makefile</filename> targets if the actions are
 	simple enough, because it will be easier for someone to figure
 	out what kind of non-default action the port requires.</para>
 
       <para>The default actions are done by the
 	<filename>bsd.port.mk</filename> targets
 	<maketarget>do-<replaceable>something</replaceable></maketarget>.
 	For example, the commands to extract a port are in the target
 	<maketarget>do-extract</maketarget>.  If you are not happy
 	with the default target, you can fix it by redefining the
 	<maketarget>do-<replaceable>something</replaceable></maketarget>
 	target in your <filename>Makefile</filename>.</para>
 
       <note>
 	<para>The <quote>main</quote> targets (e.g.,
 	  <maketarget>extract</maketarget>,
 	  <maketarget>configure</maketarget>, etc.) do nothing more
 	  than make sure all the stages up to that one are completed
 	  and call the real targets or scripts, and they are not
 	  intended to be changed.  If you want to fix the extraction,
 	  fix <maketarget>do-extract</maketarget>, but never ever
 	  change the way <maketarget>extract</maketarget>
 	  operates! Additionally, the target
 	  <maketarget>post-deinstall</maketarget> is invalid and
 	  is not run by the ports infrastructure.</para>
       </note>
 
       <para>Now that you understand what goes on when the user types
 	<command>make</command>, let us go through the recommended
 	steps to create the perfect port.</para>
     </sect1>
 
     <sect1 id="slow-sources">
       <title>Getting the Original Sources</title>
 
       <para>Get the original sources (normally) as a compressed
 	tarball
 	(<filename><replaceable>foo</replaceable>.tar.gz</filename> or
 	<filename><replaceable>foo</replaceable>.tar.bz2</filename>)
 	and copy it into <makevar>DISTDIR</makevar>.  Always use
 	<emphasis>mainstream</emphasis> sources when and where you
 	can.</para>
 
       <para>You will need to set the variable
 	<makevar>MASTER_SITES</makevar> to reflect where the original
 	tarball resides.  You will find convenient shorthand
 	definitions for most mainstream sites in
 	<filename>bsd.sites.mk</filename>.  Please use these
 	sites&mdash;and the associated definitions&mdash;if at all
 	possible, to help avoid the problem of having the same
 	information repeated over again many times in the source base.
 	As these sites tend to change over time, this becomes a
 	maintenance nightmare for everyone involved.</para>
 
       <para>If you cannot find a FTP/HTTP site that is well-connected
 	to the net, or can only find sites that have irritatingly
 	non-standard formats, you might want to put a copy on a
 	reliable FTP or HTTP server that you control (e.g., your home
 	page).</para>
 
       <para>If you cannot find somewhere convenient and reliable to
 	put the distfile we can <quote>house</quote> it ourselves on
 	<hostid>ftp.FreeBSD.org</hostid>; however, this is the
 	least-preferred solution.  The distfile must be placed into
 	<filename>~/public_distfiles/</filename> of someone's
 	<hostid>freefall</hostid> account.  Ask the person who commits
 	your port to do this.  This person will also set
 	<makevar>MASTER_SITES</makevar> to
 	<makevar>MASTER_SITE_LOCAL</makevar> and
 	<makevar>MASTER_SITE_SUBDIR</makevar> to their
 	<hostid>freefall</hostid> username.</para>
 
       <para>If your port's distfile changes all the time without any
 	kind of version update by the author, consider putting the
 	distfile on your home page and listing it as the first
 	<makevar>MASTER_SITES</makevar>.  If you can, try to talk the
 	port author out of doing this; it really does help to
 	establish some kind of source code control.  Hosting your own
 	version will prevent users from getting <errorname>checksum
 	  mismatch</errorname> errors, and also reduce the workload of
 	maintainers of our FTP site.  Also, if there is only one
 	master site for the port, it is recommended that you house a
 	backup at your site and list it as the second
 	<makevar>MASTER_SITES</makevar>.</para>
 
       <para>If your port requires some additional `patches' that are
 	available on the Internet, fetch them too and put them in
 	<makevar>DISTDIR</makevar>.  Do not worry if they come from a
 	site other than where you got the main source tarball, we have
 	a way to handle these situations (see the description of <link
 	  linkend="porting-patchfiles">PATCHFILES</link>
 	below).</para>
     </sect1>
 
     <sect1 id="slow-modifying">
       <title>Modifying the Port</title>
 
       <para>Unpack a copy of the tarball in a private directory and
 	make whatever changes are necessary to get the port to compile
 	properly under the current version of &os;.  Keep
 	<emphasis>careful track</emphasis> of everything you do, as
 	you will be automating the process shortly.  Everything,
 	including the deletion, addition, or modification of files
 	should be doable using an automated script or patch file when
 	your port is finished.</para>
 
       <para>If your port requires significant user
 	interaction/customization to compile or install, you should
 	take a look at one of Larry Wall's classic
 	<application>Configure</application> scripts and perhaps do
 	something similar yourself.  The goal of the new ports
 	collection is to make each port as
 	<quote>plug-and-play</quote> as possible for the end-user
 	while using a minimum of disk space.</para>
 
       <note>
 	<para>Unless explicitly stated, patch files, scripts, and
 	  other files you have created and contributed to the &os;
 	  ports collection are assumed to be covered by the standard
 	  BSD copyright conditions.</para>
       </note>
     </sect1>
 
     <sect1 id="slow-patch">
       <title>Patching</title>
 
       <para>In the preparation of the port, files that have been added
 	or changed can be picked up with a &man.diff.1; for later
 	feeding to &man.patch.1;.  Each patch you wish to apply should
 	be saved into a file named
 	<filename>patch-<replaceable>*</replaceable></filename> where
 	<replaceable>*</replaceable> indicates the pathname of the
 	file that is patched, such as
 	<filename>patch-Imakefile</filename> or
 	<filename>patch-src-config.h</filename>.  These files should
 	be stored in <makevar>PATCHDIR</makevar> (usually
 	<filename>files/</filename>, from where they will be
 	automatically applied.  All patches must be relative to
 	<makevar>WRKSRC</makevar> (generally the directory your port's
 	tarball unpacks itself into, that being where the build is
 	done).  To make fixes and upgrades easier, you should avoid
 	having more than one patch fix the same file (e.g.,
 	<filename>patch-file</filename> and
 	<filename>patch-file2</filename> both changing
 	<filename><makevar>WRKSRC</makevar>/foobar.c</filename>).
 	Note that if the path of a patched file contains an underscore
 	(<literal>_</literal>) character, the patch needs to have two
 	underscores instead in its name.  For example, to patch a file
 	named <filename>src/freeglut_joystick.c</filename>, the
 	corresponding patch should be named
 	<filename>patch-src-freeglut__joystick.c</filename>.</para>
 
       <para>Please only use characters
 	<literal>[-+._a-zA-Z0-9]</literal> for naming your patches.
 	Do not use any other characters besides them.  Do not name
 	your patches like <filename>patch-aa</filename> or
 	<filename>patch-ab</filename> etc, always mention the path and
 	file name in patch names.</para>
 
       <para>Do not put RCS strings in patches.  SVN will mangle them
 	when we put the files into the ports tree, and when we check
 	them out again, they will come out different and the patch
 	will fail.  RCS strings are surrounded by dollar
 	(<literal>&dollar;</literal>) signs, and typically start with
 	<literal>&dollar;Id</literal> or
 	<literal>&dollar;RCS</literal>.</para>
 
       <para>Using the recurse (<option>-r</option>) option to
 	&man.diff.1; to generate patches is fine, but please take a
 	look at the resulting patches to make sure you do not have any
 	unnecessary junk in there.  In particular, diffs between two
 	backup files, <filename>Makefile</filename>s when the port
 	uses <command>Imake</command> or GNU
 	<command>configure</command>, etc., are unnecessary and should
 	be deleted.  If you had to edit
 	<filename>configure.in</filename> and run
 	<command>autoconf</command> to regenerate
 	<command>configure</command>, do not take the diffs of
 	<command>configure</command> (it often grows to a few thousand
 	lines!); define <literal>USE_AUTOTOOLS=autoconf:261</literal>
 	and take the diffs of
 	<filename>configure.in</filename>.</para>
 
       <para>Also, try to minimize the amount of non-functional
 	whitespace changes in your patches.  It is common in the Open
 	Source world for projects to share large amounts of a code
 	base, but obey different style and indenting rules.  If you
 	take a working piece of functionality from one project to fix
 	similar areas in another, please be careful: the resulting
 	line patch may be full of non-functional changes.  It not only
 	increases the size of the SVN repository but makes it hard to
 	find out what exactly caused the problem and what you changed
 	at all.</para>
 
       <para>If you had to delete a file, then you can do it in the
 	<maketarget>post-extract</maketarget> target rather than as
 	part of the patch.</para>
 
       <para>Simple replacements can be performed directly from the
 	port <filename>Makefile</filename> using the in-place mode of
 	&man.sed.1;.  This is very useful when you need to patch in a
 	variable value.  Example:</para>
 
       <programlisting>post-patch:
 	@${REINPLACE_CMD} -e 's|for Linux|for FreeBSD|g' ${WRKSRC}/README</programlisting>
 
       <para>Quite often, there is a situation when the software being
 	ported, especially if it is primarily developed on &windows;,
 	uses the CR/LF convention for most of its source files.  This
 	may cause problems with further patching, compiler warnings,
 	scripts execution (<command>/bin/sh^M</command> not found),
 	etc.  To quickly convert all files from CR/LF to just LF, add
 	<literal>USE_DOS2UNIX=yes</literal> to the port
 	<filename>Makefile</filename>.  A list of files to convert can
 	be specified:</para>
 
       <programlisting>USE_DOS2UNIX=	util.c util.h</programlisting>
 
       <para>If you want to convert a group of files across
 	subdirectories, <makevar>DOS2UNIX_REGEX</makevar> can be used.
 	Its argument is a <command>find</command> compatible regular
 	expression.  More on the format is in &man.re.format.7;.  This
 	option is useful for converting all files of a given
 	extension, for example all source code files leaving binary
 	files intact:</para>
 
       <programlisting>USE_DOS2UNIX=	yes
 DOS2UNIX_REGEX=	.*\.(c|cpp|h)</programlisting>
 
       <para>If you want to create a patch file based off of an
 	existing file, you can copy it with an
 	<filename>.orig</filename> extension, and then modify the
 	original one.  The <maketarget>makepatch</maketarget> target
 	will write out an appropriate patch file to the <filename
 	  class="directory">files</filename> directory of the
 	port.</para>
     </sect1>
 
     <sect1 id="slow-configure">
       <title>Configuring</title>
 
       <para>Include any additional customization commands in your
 	<filename>configure</filename> script and save it in the
 	<filename>scripts</filename> subdirectory.  As mentioned
 	above, you can also do this with <filename>Makefile</filename>
 	targets and/or scripts with the name
 	<filename>pre-configure</filename> or
 	<filename>post-configure</filename>.</para>
     </sect1>
 
     <sect1 id="slow-user-input">
       <title>Handling User Input</title>
 
       <para>If your port requires user input to build, configure, or
 	install, you must set <makevar>IS_INTERACTIVE</makevar> in
 	your <filename>Makefile</filename>.  This will allow
 	<quote>overnight builds</quote> to skip your port if the user
 	sets the variable <envar>BATCH</envar> in his environment (and
 	if the user sets the variable <envar>INTERACTIVE</envar>, then
 	<emphasis>only</emphasis> those ports requiring interaction
 	are built).  This will save a lot of wasted time on the set of
 	machines that continually build ports (see below).</para>
 
       <para>It is also recommended that if there are reasonable
 	default answers to the questions, you check the
 	<makevar>PACKAGE_BUILDING</makevar> variable and turn off the
 	interactive script when it is set.  This will allow us to
 	build the packages for CDROMs and FTP.</para>
     </sect1>
   </chapter>
 
   <chapter id="makefile">
     <title>Configuring the Makefile</title>
 
     <para>Configuring the <filename>Makefile</filename> is pretty
       simple, and again we suggest that you look at existing examples
       before starting.  Also, there is a <link
 	linkend="porting-samplem">sample Makefile</link> in this
       handbook, so take a look and please follow the ordering of
       variables and sections in that template to make your port easier
       for others to read.</para>
 
     <para>Now, consider the following problems in sequence as you
       design your new <filename>Makefile</filename>:</para>
 
     <sect1 id="makefile-source">
       <title>The Original Source</title>
 
       <para>Does it live in <makevar>DISTDIR</makevar> as a standard
 	<command>gzip</command>ped tarball named something like
 	<filename>foozolix-1.2.tar.gz</filename>? If so, you can go on
 	to the next step.  If not, you should look at overriding any
 	of the <makevar>DISTVERSION</makevar>,
 	<makevar>DISTNAME</makevar>, <makevar>EXTRACT_CMD</makevar>,
 	<makevar>EXTRACT_BEFORE_ARGS</makevar>,
 	<makevar>EXTRACT_AFTER_ARGS</makevar>,
 	<makevar>EXTRACT_SUFX</makevar>, or
 	<makevar>DISTFILES</makevar> variables, depending on how alien
 	a format your port's distribution file is.</para>
 
       <para>In the worst case, you can simply create your own
 	<maketarget>do-extract</maketarget> target to override the
 	default, though this should be rarely, if ever,
 	necessary.</para>
     </sect1>
 
     <sect1 id="makefile-naming">
       <title>Naming</title>
 
       <para>The first part of the port's <filename>Makefile</filename>
 	names the port, describes its version number, and lists it
 	in the correct category.</para>
 
       <sect2>
 	<title><makevar>PORTNAME</makevar> and
 	  <makevar>PORTVERSION</makevar></title>
 
 	<para>You should set <makevar>PORTNAME</makevar> to the
 	  base name of your port, and <makevar>PORTVERSION</makevar>
 	  to the version number of the port.</para>
       </sect2>
 
       <sect2 id="makefile-naming-revepoch">
 	<title><makevar>PORTREVISION</makevar> and
 	  <makevar>PORTEPOCH</makevar></title>
 
 	<sect3>
 	  <title><makevar>PORTREVISION</makevar></title>
 
 	  <para>The <makevar>PORTREVISION</makevar> variable is a
 	    monotonically increasing value which is reset to 0 with
 	    every increase of <makevar>PORTVERSION</makevar> (i.e.,
 	    every time a new official vendor release is made), and
 	    appended to the package name if non-zero.  Changes to
 	    <makevar>PORTREVISION</makevar> are used by automated
 	    tools (e.g., &man.pkg.version.1;) to highlight the fact
 	    that a new package is available.</para>
 
 	  <para><makevar>PORTREVISION</makevar> should be increased
 	    each time a change is made to the port which significantly
 	    affects the content or structure of the derived
 	    package.</para>
 
 	  <para>Examples of when <makevar>PORTREVISION</makevar>
 	    should be bumped:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Addition of patches to correct security
 		vulnerabilities, bugs, or to add new functionality to
 		the port.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Changes to the port <filename>Makefile</filename>
 		to enable or disable compile-time options in the
 		package.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Changes in the packing list or the install-time
 		behavior of the package (e.g., change to a script
 		which generates initial data for the package, like ssh
 		host keys).</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Version bump of a port's shared library dependency
 		(in this case, someone trying to install the old
 		package after installing a newer version of the
 		dependency will fail since it will look for the old
 		libfoo.x instead of libfoo.(x+1)).</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Silent changes to the port distfile which have
 		significant functional differences, i.e., changes to
 		the distfile requiring a correction to
 		<filename>distinfo</filename> with no corresponding
 		change to <makevar>PORTVERSION</makevar>, where a
 		<command>diff -ru</command> of the old and new
 		versions shows non-trivial changes to the code.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>Examples of changes which do not require a
 	    <makevar>PORTREVISION</makevar> bump:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Style changes to the port skeleton with no
 		functional change to what appears in the resulting
 		package.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Changes to <makevar>MASTER_SITES</makevar> or
 		other functional changes to the port which do not
 		affect the resulting package.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Trivial patches to the distfile such as correction
 		of typos, which are not important enough that users of
 		the package should go to the trouble of
 		upgrading.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Build fixes which cause a package to become
 		compilable where it was previously failing (as long as
 		the changes do not introduce any functional change on
 		any other platforms on which the port did previously
 		build).  Since <makevar>PORTREVISION</makevar>
 		reflects the content of the package, if the package
 		was not previously buildable then there is no need to
 		increase <makevar>PORTREVISION</makevar> to mark a
 		change.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>A rule of thumb is to ask yourself whether a change
 	    committed to a port is something which everyone would
 	    benefit from having (either because of an enhancement,
 	    fix, or by virtue that the new package will actually work
 	    at all), and weigh that against that fact that it will
 	    cause everyone who regularly updates their ports tree to
 	    be compelled to update.  If yes, the
 	    <makevar>PORTREVISION</makevar> should be bumped.</para>
 	</sect3>
 
 	<sect3>
 	  <title><makevar>PORTEPOCH</makevar></title>
 
 	  <para>From time to time a software vendor or FreeBSD porter
 	    will do something silly and release a version of their
 	    software which is actually numerically less than the
 	    previous version.  An example of this is a port which goes
 	    from foo-20000801 to foo-1.0 (the former will be
 	    incorrectly treated as a newer version since 20000801 is a
 	    numerically greater value than 1).</para>
 
 	  <tip>
 	    <para>The results of version number comparisons are not
 	      always obvious.  &man.pkg.version.1; can be used to test
 	      the comparison of two version number strings.  The
 	      <application>pkgng</application> equivalent is
 	      <command>pkg version -t</command>.  For example:</para>
 
 	    <screen>&prompt.user; <userinput>pkg_version -t 0.031 0.29</userinput>
 ></screen>
 
 	    <para>Or, for <application>pkgng</application>
 	      users:</para>
 
 	    <screen>&prompt.user; <userinput>pkg version -t 0.031 0.29</userinput>
 ></screen>
 
 	    <para>The <literal>&gt;</literal> output indicates that
 	      version 0.031 is considered greater than version 0.29,
 	      which may not have been obvious to the porter.</para>
 	  </tip>
 
 	  <para>In situations such as this, the
 	    <makevar>PORTEPOCH</makevar> version should be increased.
 	    If <makevar>PORTEPOCH</makevar> is nonzero it is appended
 	    to the package name as described in section 0 above.
 	    <makevar>PORTEPOCH</makevar> must never be decreased or
 	    reset to zero, because that would cause comparison to a
 	    package from an earlier epoch to fail (i.e., the package
 	    would not be detected as out of date): the new version
 	    number (e.g., <literal>1.0,1</literal> in the above
 	    example) is still numerically less than the previous
 	    version (20000801), but the <literal>,1</literal> suffix
 	    is treated specially by automated tools and found to be
 	    greater than the implied suffix <literal>,0</literal> on
 	    the earlier package.</para>
 
 	  <para>Dropping or resetting <makevar>PORTEPOCH</makevar>
 	    incorrectly leads to no end of grief; if you do not
 	    understand the above discussion, please keep after it
 	    until you do, or ask questions on the mailing
 	    lists.</para>
 
 	  <para>It is expected that <makevar>PORTEPOCH</makevar> will
 	    not be used for the majority of ports, and that sensible
 	    use of <makevar>PORTVERSION</makevar> can often preempt it
 	    becoming necessary if a future release of the software
 	    should change the version structure.  However, care is
 	    needed by FreeBSD porters when a vendor release is made
 	    without an official version number &mdash; such as a code
 	    <quote>snapshot</quote> release.  The temptation is to
 	    label the release with the release date, which will cause
 	    problems as in the example above when a new
 	    <quote>official</quote> release is made.</para>
 
 	  <para>For example, if a snapshot release is made on the date
 	    20000917, and the previous version of the software was
 	    version 1.2, the snapshot release should be given a
 	    <makevar>PORTVERSION</makevar> of 1.2.20000917 or similar,
 	    not 20000917, so that the succeeding release, say 1.3, is
 	    still a numerically greater value.</para>
 	</sect3>
 
 	<sect3>
 	  <title>Example of <makevar>PORTREVISION</makevar> and
 	    <makevar>PORTEPOCH</makevar> Usage</title>
 
 	  <para>The <literal>gtkmumble</literal> port, version
 	    <literal>0.10</literal>, is committed to the ports
 	    collection:</para>
 
 	  <programlisting>PORTNAME=	gtkmumble
 PORTVERSION=	0.10</programlisting>
 
 	  <para><makevar>PKGNAME</makevar> becomes
 	    <literal>gtkmumble-0.10</literal>.</para>
 
 	  <para>A security hole is discovered which requires a local
 	    FreeBSD patch.  <makevar>PORTREVISION</makevar> is bumped
 	    accordingly.</para>
 
 	  <programlisting>PORTNAME=	gtkmumble
 PORTVERSION=	0.10
 PORTREVISION=	1</programlisting>
 
 	  <para><makevar>PKGNAME</makevar> becomes
 	    <literal>gtkmumble-0.10_1</literal></para>
 
 	  <para>A new version is released by the vendor, numbered
 	    <literal>0.2</literal> (it turns out the author actually
 	    intended <literal>0.10</literal> to actually mean
 	    <literal>0.1.0</literal>, not <quote>what comes after
 	      0.9</quote> - oops, too late now).  Since the new minor
 	    version <literal>2</literal> is numerically less than the
 	    previous version <literal>10</literal>, the
 	    <makevar>PORTEPOCH</makevar> must be bumped to manually
 	    force the new package to be detected as
 	    <quote>newer</quote>.  Since it is a new vendor release of
 	    the code, <makevar>PORTREVISION</makevar> is reset to 0
 	    (or removed from the
 	    <filename>Makefile</filename>).</para>
 
 	  <programlisting>PORTNAME=	gtkmumble
 PORTVERSION=	0.2
 PORTEPOCH=	1</programlisting>
 
 	  <para><makevar>PKGNAME</makevar> becomes
 	    <literal>gtkmumble-0.2,1</literal></para>
 
 	  <para>The next release is 0.3.  Since
 	    <makevar>PORTEPOCH</makevar> never decreases, the version
 	    variables are now:</para>
 
 	  <programlisting>PORTNAME=	gtkmumble
 PORTVERSION=	0.3
 PORTEPOCH=	1</programlisting>
 
 	  <para><makevar>PKGNAME</makevar> becomes
 	    <literal>gtkmumble-0.3,1</literal></para>
 
 	  <note>
 	    <para>If <makevar>PORTEPOCH</makevar> were reset to
 	      <literal>0</literal> with this upgrade, someone who had
 	      installed the <literal>gtkmumble-0.10_1</literal>
 	      package would not detect the
 	      <literal>gtkmumble-0.3</literal> package as newer, since
 	      <literal>3</literal> is still numerically less than
 	      <literal>10</literal>.  Remember, this is the whole
 	      point of <makevar>PORTEPOCH</makevar> in the first
 	      place.</para>
 	  </note>
 	</sect3>
       </sect2>
 
       <sect2>
 	<title><makevar>PKGNAMEPREFIX</makevar> and
 	  <makevar>PKGNAMESUFFIX</makevar></title>
 
 	<para>Two optional variables, <makevar>PKGNAMEPREFIX</makevar>
 	  and <makevar>PKGNAMESUFFIX</makevar>, are combined with
 	  <makevar>PORTNAME</makevar> and
 	  <makevar>PORTVERSION</makevar> to form
 	  <makevar>PKGNAME</makevar> as
 	  <literal>${PKGNAMEPREFIX}${PORTNAME}${PKGNAMESUFFIX}-${PORTVERSION}</literal>.
 	  Make sure this conforms to our <link
 	    linkend="porting-pkgname">guidelines for a good package
 	    name</link>.  In particular, you are
 	  <emphasis>not</emphasis> allowed to use a hyphen
 	  (<literal>-</literal>) in <makevar>PORTVERSION</makevar>.
 	  Also, if the package name has the
 	  <replaceable>language-</replaceable> or the
 	  <replaceable>-compiled.specifics</replaceable> part (see
 	  below), use <makevar>PKGNAMEPREFIX</makevar> and
 	  <makevar>PKGNAMESUFFIX</makevar>, respectively.  Do not make
 	  them part of <makevar>PORTNAME</makevar>.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>LATEST_LINK</makevar></title>
 
 	<para><makevar>LATEST_LINK</makevar> is used during package
 	  building to determine a shortened name to create links that
 	  can be used by <command>pkg_add -r</command>.  This makes it
 	  possible to, for example, install the latest perl version by
 	  running <command>pkg_add -r perl</command> without knowing
 	  the exact version number.  This name needs to be unique and
 	  obvious to users.</para>
 
 	<para>In some cases, several versions of a program may be
 	  present in the ports collection at the same time.  Both the
 	  index build and the package build system need to be able to
 	  see them as different, independent ports, although they may
 	  all have the same <makevar>PORTNAME</makevar>,
 	  <makevar>PKGNAMEPREFIX</makevar>, and even
 	  <makevar>PKGNAMESUFFIX</makevar>.  In those cases, the
 	  optional <makevar>LATEST_LINK</makevar> variable should be
 	  set to a different value for all ports except the
 	  <quote>main</quote> one &mdash; see the
 	  <filename>lang/gcc46</filename> and
 	  <filename>lang/gcc</filename> ports, and the
 	  <filename>www/apache*</filename> family for examples of its
 	  use.  By setting <makevar>NO_LATEST_LINK</makevar>, no link
 	  will be generated, which may be an option for all but the
 	  <quote>main</quote> version.  Note that how to choose a
 	  <quote>main</quote> version &mdash; <quote>most
 	    popular</quote>, <quote>best supported</quote>,
 	  <quote>least patched</quote>, and so on &mdash; is outside
 	  the scope of this handbook's recommendations; we only tell
 	  you how to specify the other ports' versions after you have
 	  picked a <quote>main</quote> one.</para>
       </sect2>
 
       <sect2 id="porting-pkgname">
 	<title>Package Naming Conventions</title>
 
 	<para>The following are the conventions you should follow in
 	  naming your packages.  This is to have our package directory
 	  easy to scan, as there are already thousands of packages and
 	  users are going to turn away if they hurt their eyes!</para>
 
 	<para>The package name should look like
 	  <filename><replaceable><optional>language<optional>_region</optional></optional>-name<optional><optional>-</optional>compiled.specifics</optional>-version.numbers</replaceable></filename>.</para>
 
 	<para>The package name is defined as
 	  <literal>${PKGNAMEPREFIX}${PORTNAME}${PKGNAMESUFFIX}-${PORTVERSION}</literal>.
 	  Make sure to set the variables to conform to that
 	  format.</para>
 
 	<orderedlist>
 	  <listitem>
 	    <para>FreeBSD strives to support the native language of
 	      its users.  The <replaceable>language-</replaceable>
 	      part should be a two letter abbreviation of the natural
 	      language defined by ISO-639 if the port is specific to a
 	      certain language.  Examples are <literal>ja</literal>
 	      for Japanese, <literal>ru</literal> for Russian,
 	      <literal>vi</literal> for Vietnamese,
 	      <literal>zh</literal> for Chinese, <literal>ko</literal>
 	      for Korean and <literal>de</literal> for German.</para>
 
 	    <para>If the port is specific to a certain region within
 	      the language area, add the two letter country code as
 	      well.  Examples are <literal>en_US</literal> for US
 	      English and <literal>fr_CH</literal> for Swiss
 	      French.</para>
 
 	    <para>The <replaceable>language-</replaceable> part should
 	      be set in the <makevar>PKGNAMEPREFIX</makevar>
 	      variable.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>The first letter of the <filename>name</filename>
 	      part should be lowercase.  (The rest of the name may
 	      contain capital letters, so use your own discretion when
 	      you are converting a software name that has some capital
 	      letters in it.) There is a tradition of naming
 	      <literal>Perl 5</literal> modules by prepending
 	      <literal>p5-</literal> and converting the double-colon
 	      separator to a hyphen; for example, the
 	      <literal>Data::Dumper</literal> module becomes
 	      <literal>p5-Data-Dumper</literal>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Make sure that the port's name and version are
 	      clearly separated and placed into the
 	      <makevar>PORTNAME</makevar> and
 	      <makevar>PORTVERSION</makevar> variables.  The only
 	      reason for <makevar>PORTNAME</makevar> to contain a
 	      version part is if the upstream distribution is really
 	      named that way, as in the
 	      <filename>textproc/libxml2</filename> or
 	      <filename>japanese/kinput2-freewnn</filename> ports.
 	      Otherwise, the <makevar>PORTNAME</makevar> should not
 	      contain any version-specific information.  It is quite
 	      normal for several ports to have the same
 	      <makevar>PORTNAME</makevar>, as the
 	      <filename>www/apache*</filename> ports do; in that case,
 	      different versions (and different index entries) are
 	      distinguished by the <makevar>PKGNAMEPREFIX</makevar>,
 	      <makevar>PKGNAMESUFFIX</makevar>, and
 	      <makevar>LATEST_LINK</makevar> values.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>If the port can be built with different <link
 		linkend="makefile-masterdir">hardcoded defaults</link>
 	      (usually part of the directory name in a family of
 	      ports), the
 	      <replaceable>-compiled.specifics</replaceable> part
 	      should state the compiled-in defaults (the hyphen is
 	      optional).  Examples are paper size and font
 	      units.</para>
 
 	    <para>The <replaceable>-compiled.specifics</replaceable>
 	      part should be set in the
 	      <makevar>PKGNAMESUFFIX</makevar> variable.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>The version string should follow a dash
 	      (<literal>-</literal>) and be a period-separated list of
 	      integers and single lowercase alphabetics.  In
 	      particular, it is not permissible to have another dash
 	      inside the version string.  The only exception is the
 	      string <literal>pl</literal> (meaning
 	      <quote>patchlevel</quote>), which can be used
 	      <emphasis>only</emphasis> when there are no major and
 	      minor version numbers in the software.  If the software
 	      version has strings like <quote>alpha</quote>,
 	      <quote>beta</quote>, <quote>rc</quote>, or
 	      <quote>pre</quote>, take the first letter and put it
 	      immediately after a period.  If the version string
 	      continues after those names, the numbers should follow
 	      the single alphabet without an extra period between
 	      them.</para>
 
 	    <para>The idea is to make it easier to sort ports by
 	      looking at the version string.  In particular, make sure
 	      version number components are always delimited by a
 	      period, and if the date is part of the string, use the
 	      <literal>0.0.<replaceable>yyyy</replaceable>.<replaceable>mm</replaceable>.<replaceable>dd</replaceable></literal>
 	      format, not
 	      <literal><replaceable>dd</replaceable>.<replaceable>mm</replaceable>.<replaceable>yyyy</replaceable></literal>
 	      or the non-Y2K compliant
 	      <literal><replaceable>yy</replaceable>.<replaceable>mm</replaceable>.<replaceable>dd</replaceable></literal>
 	      format.  It is important to prefix the version with
 	      <literal>0.0.</literal> in case a release with an actual
 	      version number is made, which would of course be
 	      numerically less than
 	      <literal><replaceable>yyyy</replaceable></literal>.</para>
 	  </listitem>
 	</orderedlist>
 
 	<para>Here are some (real) examples on how to convert the name
 	  as called by the software authors to a suitable package
 	  name:</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="6">
 	    <thead>
 	      <row>
 		<entry>Distribution Name</entry>
 		<entry><makevar>PKGNAMEPREFIX</makevar></entry>
 		<entry><makevar>PORTNAME</makevar></entry>
 		<entry><makevar>PKGNAMESUFFIX</makevar></entry>
 		<entry><makevar>PORTVERSION</makevar></entry>
 		<entry>Reason</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry>mule-2.2.2</entry>
 		<entry>(empty)</entry>
 		<entry>mule</entry>
 		<entry>(empty)</entry>
 		<entry>2.2.2</entry>
 		<entry>No changes required</entry>
 	      </row>
 
 	      <row>
 		<entry>EmiClock-1.0.2</entry>
 		<entry>(empty)</entry>
 		<entry>emiclock</entry>
 		<entry>(empty)</entry>
 		<entry>1.0.2</entry>
 		<entry>No uppercase names for single programs</entry>
 	      </row>
 
 	      <row>
 		<entry>rdist-1.3alpha</entry>
 		<entry>(empty)</entry>
 		<entry>rdist</entry>
 		<entry>(empty)</entry>
 		<entry>1.3.a</entry>
 		<entry>No strings like <literal>alpha</literal>
 		  allowed</entry>
 	      </row>
 
 	      <row>
 		<entry>es-0.9-beta1</entry>
 		<entry>(empty)</entry>
 		<entry>es</entry>
 		<entry>(empty)</entry>
 		<entry>0.9.b1</entry>
 		<entry>No strings like <literal>beta</literal>
 		  allowed</entry>
 	      </row>
 
 	      <row>
 		<entry>mailman-2.0rc3</entry>
 		<entry>(empty)</entry>
 		<entry>mailman</entry>
 		<entry>(empty)</entry>
 		<entry>2.0.r3</entry>
 		<entry>No strings like <literal>rc</literal>
 		  allowed</entry>
 	      </row>
 
 	      <row>
 		<entry>v3.3beta021.src</entry>
 		<entry>(empty)</entry>
 		<entry>tiff</entry>
 		<entry>(empty)</entry>
 		<entry>3.3</entry>
 		<entry>What the heck was that anyway?</entry>
 	      </row>
 
 	      <row>
 		<entry>tvtwm</entry>
 		<entry>(empty)</entry>
 		<entry>tvtwm</entry>
 		<entry>(empty)</entry>
 		<entry>pl11</entry>
 		<entry>Version string always required</entry>
 	      </row>
 
 	      <row>
 		<entry>piewm</entry>
 		<entry>(empty)</entry>
 		<entry>piewm</entry>
 		<entry>(empty)</entry>
 		<entry>1.0</entry>
 		<entry>Version string always required</entry>
 	      </row>
 
 	      <row>
 		<entry>xvgr-2.10pl1</entry>
 		<entry>(empty)</entry>
 		<entry>xvgr</entry>
 		<entry>(empty)</entry>
 		<entry>2.10.1</entry>
 		<entry><literal>pl</literal> allowed only when no
 		  major/minor version numbers</entry>
 	      </row>
 
 	      <row>
 		<entry>gawk-2.15.6</entry>
 		<entry>ja-</entry>
 		<entry>gawk</entry>
 		<entry>(empty)</entry>
 		<entry>2.15.6</entry>
 		<entry>Japanese language version</entry>
 	      </row>
 
 	      <row>
 		<entry>psutils-1.13</entry>
 		<entry>(empty)</entry>
 		<entry>psutils</entry>
 		<entry>-letter</entry>
 		<entry>1.13</entry>
 		<entry>Paper size hardcoded at package build
 		  time</entry>
 	      </row>
 
 	      <row>
 		<entry>pkfonts</entry>
 		<entry>(empty)</entry>
 		<entry>pkfonts</entry>
 		<entry>300</entry>
 		<entry>1.0</entry>
 		<entry>Package for 300dpi fonts</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
 	<para>If there is absolutely no trace of version information
 	  in the original source and it is unlikely that the original
 	  author will ever release another version, just set the
 	  version string to <literal>1.0</literal> (like the
 	  <literal>piewm</literal> example above).  Otherwise, ask the
 	  original author or use the date string
 	  (<literal>0.0.<replaceable>yyyy</replaceable>.<replaceable>mm</replaceable>.<replaceable>dd</replaceable></literal>)
 	  as the version.</para>
       </sect2>
     </sect1>
 
     <sect1 id="makefile-categories">
       <title>Categorization</title>
 
       <sect2>
 	<title><makevar>CATEGORIES</makevar></title>
 
 	<para>When a package is created, it is put under
 	  <filename>/usr/ports/packages/All</filename> and links are
 	  made from one or more subdirectories of
 	  <filename>/usr/ports/packages</filename>.  The names of
 	  these subdirectories are specified by the variable
 	  <makevar>CATEGORIES</makevar>.  It is intended to make life
 	  easier for the user when he is wading through the pile of
 	  packages on the FTP site or the CDROM.  Please take a look
 	  at the <link linkend="porting-categories">current list of
 	    categories</link> and pick the ones that are suitable for
 	  your port.</para>
 
 	<para>This list also determines where in the ports tree the
 	  port is imported.  If you put more than one category here,
 	  it is assumed that the port files will be put in the
 	  subdirectory with the name in the first category.  See <link
 	    linkend="choosing-categories">below</link> for more
 	  discussion about how to pick the right categories.</para>
       </sect2>
 
       <sect2 id="porting-categories">
 	<title>Current List of Categories</title>
 
 	<para>Here is the current list of port categories.  Those
 	  marked with an asterisk (<literal>*</literal>) are
 	  <emphasis>virtual</emphasis> categories&mdash;those that do
 	  not have a corresponding subdirectory in the ports tree.
 	  They are only used as secondary categories, and only for
 	  search purposes.</para>
 
 	<note>
 	  <para>For non-virtual categories, you will find a one-line
 	    description in the <makevar>COMMENT</makevar> in that
 	    subdirectory's <filename>Makefile</filename>.</para>
 	</note>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="3">
 	    <thead>
 	      <row>
 		<entry>Category</entry>
 		<entry>Description</entry>
 		<entry>Notes</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><filename>accessibility</filename></entry>
 		<entry>Ports to help disabled users.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>afterstep*</filename></entry>
 		<entry>Ports to support the <ulink
 		    url="http://www.afterstep.org">AfterStep</ulink>
 		  window manager.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>arabic</filename></entry>
 		<entry>Arabic language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>archivers</filename></entry>
 		<entry>Archiving tools.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>astro</filename></entry>
 		<entry>Astronomical ports.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>audio</filename></entry>
 		<entry>Sound support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>benchmarks</filename></entry>
 		<entry>Benchmarking utilities.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>biology</filename></entry>
 		<entry>Biology-related software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>cad</filename></entry>
 		<entry>Computer aided design tools.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>chinese</filename></entry>
 		<entry>Chinese language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>comms</filename></entry>
 		<entry>Communication software.</entry>
 		<entry>Mostly software to talk to your serial
 		  port.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>converters</filename></entry>
 		<entry>Character code converters.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>databases</filename></entry>
 		<entry>Databases.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>deskutils</filename></entry>
 		<entry>Things that used to be on the desktop before
 		  computers were invented.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>devel</filename></entry>
 		<entry>Development utilities.</entry>
 		<entry>Do not put libraries here just because they are
 		  libraries&mdash;unless they truly do not belong
 		  anywhere else, they should not be in this
 		  category.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>dns</filename></entry>
 		<entry>DNS-related software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>docs*</filename></entry>
 		<entry>Meta-ports for FreeBSD documentation.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>editors</filename></entry>
 		<entry>General editors.</entry>
 		<entry>Specialized editors go in the section for those
 		  tools (e.g., a mathematical-formula editor will go
 		  in <filename>math</filename>).</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>elisp*</filename></entry>
 		<entry>Emacs-lisp ports.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>emulators</filename></entry>
 		<entry>Emulators for other operating systems.</entry>
 		<entry>Terminal emulators do <emphasis>not</emphasis>
 		  belong here&mdash;X-based ones should go to
 		  <filename>x11</filename> and text-based ones to
 		  either <filename>comms</filename> or
 		  <filename>misc</filename>, depending on the exact
 		  functionality.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>finance</filename></entry>
 		<entry>Monetary, financial and related
 		  applications.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>french</filename></entry>
 		<entry>French language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>ftp</filename></entry>
 		<entry>FTP client and server utilities.</entry>
 		<entry>If your port speaks both FTP and HTTP, put it
 		  in <filename>ftp</filename> with a secondary
 		  category of <filename>www</filename>.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>games</filename></entry>
 		<entry>Games.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>geography*</filename></entry>
 		<entry>Geography-related software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>german</filename></entry>
 		<entry>German language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>gnome*</filename></entry>
 		<entry>Ports from the <ulink
 		    url="http://www.gnome.org">GNOME</ulink>
 		  Project.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>gnustep*</filename></entry>
 		<entry>Software related to the GNUstep desktop
 		  environment.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>graphics</filename></entry>
 		<entry>Graphics utilities.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>hamradio*</filename></entry>
 		<entry>Software for amateur radio.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>haskell*</filename></entry>
 		<entry>Software related to the Haskell
 		  language.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>hebrew</filename></entry>
 		<entry>Hebrew language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>hungarian</filename></entry>
 		<entry>Hungarian language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>ipv6*</filename></entry>
 		<entry>IPv6 related software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>irc</filename></entry>
 		<entry>Internet Relay Chat utilities.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>japanese</filename></entry>
 		<entry>Japanese language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>java</filename></entry>
 		<entry>Software related to the Java&trade;
 		  language.</entry>
 		<entry>The <filename>java</filename> category must
 		  not be the only one for a port.  Save for ports
 		  directly related to the Java language, porters are
 		  also encouraged not to use <filename>java</filename>
 		  as the main category of a port.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>kde*</filename></entry>
 		<entry>Ports from the <ulink
 		    url="http://www.kde.org">KDE</ulink>
 		  Project.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>kld*</filename></entry>
 		<entry>Kernel loadable modules.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>korean</filename></entry>
 		<entry>Korean language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>lang</filename></entry>
 		<entry>Programming languages.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>linux*</filename></entry>
 		<entry>Linux applications and support
 		  utilities.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>lisp*</filename></entry>
 		<entry>Software related to the Lisp language.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>mail</filename></entry>
 		<entry>Mail software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>math</filename></entry>
 		<entry>Numerical computation software and other
 		  utilities for mathematics.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>mbone*</filename></entry>
 		<entry>MBone applications.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>misc</filename></entry>
 		<entry>Miscellaneous utilities</entry>
 		<entry>Basically things that do not belong anywhere
 		  else.  If at all possible, try to find a better
 		  category for your port than <literal>misc</literal>,
 		  as ports tend to get overlooked in here.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>multimedia</filename></entry>
 		<entry>Multimedia software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>net</filename></entry>
 		<entry>Miscellaneous networking software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>net-im</filename></entry>
 		<entry>Instant messaging software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>net-mgmt</filename></entry>
 		<entry>Networking management software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>net-p2p</filename></entry>
 		<entry>Peer to peer network applications.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>news</filename></entry>
 		<entry>USENET news software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>palm</filename></entry>
 		<entry>Software support for the <ulink
 		    url="http://www.palm.com/">Palm&trade;</ulink>
 		  series.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>parallel*</filename></entry>
 		<entry>Applications dealing with parallelism in
 		  computing.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>pear*</filename></entry>
 		<entry>Ports related to the Pear PHP
 		  framework.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>perl5*</filename></entry>
 		<entry>Ports that require
 		  <application>Perl</application> version 5 to
 		  run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>plan9*</filename></entry>
 		<entry>Various programs from <ulink
 		    url="http://www.cs.bell-labs.com/plan9dist/">Plan9</ulink>.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>polish</filename></entry>
 		<entry>Polish language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>ports-mgmt</filename></entry>
 		<entry>Ports for managing, installing and developing
 		  FreeBSD ports and packages.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>portuguese</filename></entry>
 		<entry>Portuguese language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>print</filename></entry>
 		<entry>Printing software.</entry>
 		<entry>Desktop publishing tools
 		  (previewers, etc.) belong here too.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>python*</filename></entry>
 		<entry>Software related to the <ulink
 		    url="http://www.python.org/">Python</ulink>
 		  language.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>ruby*</filename></entry>
 		<entry>Software related to the <ulink
 		    url="http://www.ruby-lang.org/">Ruby</ulink>
 		  language.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>rubygems*</filename></entry>
 		<entry>Ports of <ulink
 		    url="http://www.rubygems.org/">RubyGems</ulink>
 		  packages.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>russian</filename></entry>
 		<entry>Russian language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>scheme*</filename></entry>
 		<entry>Software related to the Scheme
 		  language.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>science</filename></entry>
 		<entry>Scientific ports that do not fit into other
 		  categories such as <filename>astro</filename>,
 		  <filename>biology</filename> and
 		  <filename>math</filename>.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>security</filename></entry>
 		<entry>Security utilities.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>shells</filename></entry>
 		<entry>Command line shells.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>spanish*</filename></entry>
 		<entry>Spanish language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>sysutils</filename></entry>
 		<entry>System utilities.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tcl*</filename></entry>
 		<entry>Ports that use Tcl to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>textproc</filename></entry>
 		<entry>Text processing utilities.</entry>
 		<entry>It does not include desktop publishing tools,
 		  which go to <filename>print</filename>.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tk*</filename></entry>
 		<entry>Ports that use Tk to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>ukrainian</filename></entry>
 		<entry>Ukrainian language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>vietnamese</filename></entry>
 		<entry>Vietnamese language support.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>windowmaker*</filename></entry>
 		<entry>Ports to support the WindowMaker window
 		  manager.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>www</filename></entry>
 		<entry>Software related to the World Wide Web.</entry>
 		<entry>HTML language
 		  support belongs here too.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11</filename></entry>
 		<entry>The X Window System and friends.</entry>
 		<entry>This category is only for software that
 		  directly supports the window system.  Do not put
 		  regular X applications here; most of them should go
 		  into other <filename>x11-*</filename> categories
 		  (see below).</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-clocks</filename></entry>
 		<entry>X11 clocks.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-drivers</filename></entry>
 		<entry>X11 drivers.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-fm</filename></entry>
 		<entry>X11 file managers.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-fonts</filename></entry>
 		<entry>X11 fonts and font utilities.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-servers</filename></entry>
 		<entry>X11 servers.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-themes</filename></entry>
 		<entry>X11 themes.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-toolkits</filename></entry>
 		<entry>X11 toolkits.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-wm</filename></entry>
 		<entry>X11 window managers.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>xfce*</filename></entry>
 		<entry>Ports related to the <ulink
 		    url="http://www.xfce.org/">Xfce</ulink> desktop
 		  environment.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>zope*</filename></entry>
 		<entry><ulink url="http://www.zope.org/">Zope</ulink>
 		  support.</entry>
 		<entry></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
       </sect2>
 
       <sect2 id="choosing-categories">
 	<title>Choosing the Right Category</title>
 
 	<para>As many of the categories overlap, you often have to
 	  choose which of the categories should be the primary
 	  category of your port.  There are several rules that govern
 	  this issue.  Here is the list of priorities, in decreasing
 	  order of precedence:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>The first category must be a physical category (see
 	      <link linkend="porting-categories">above</link>).  This
 	      is necessary to make the packaging work.  Virtual
 	      categories and physical categories may be intermixed
 	      after that.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Language specific categories always come first.  For
 	      example, if your port installs Japanese X11 fonts, then
 	      your <makevar>CATEGORIES</makevar> line would read
 	      <filename>japanese x11-fonts</filename>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Specific categories are listed before less-specific
 	      ones.  For instance, an HTML editor should be listed as
 	      <filename>www editors</filename>, not the other way
 	      around.  Also, you should not list
 	      <filename>net</filename> when the port belongs to any of
 	      <filename>irc</filename>, <filename>mail</filename>,
 	      <filename>news</filename>,
 	      <filename>security</filename>, or
 	      <filename>www</filename>, as <filename>net</filename> is
 	      included implicitly.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><filename>x11</filename> is used as a secondary
 	      category only when the primary category is a natural
 	      language.  In particular, you should not put
 	      <filename>x11</filename> in the category line for X
 	      applications.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><application>Emacs</application> modes should be
 	      placed in the same ports category as the application
 	      supported by the mode, not in
 	      <filename>editors</filename>.  For example, an
 	      <application>Emacs</application> mode to edit source
 	      files of some programming language should go into
 	      <filename>lang</filename>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Ports which install loadable kernel modules should
 	      have the virtual category <filename>kld</filename> in
 	      their <makevar>CATEGORIES</makevar> line.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><filename>misc</filename> should not appear with any
 	      other non-virtual category.  If you have
 	      <literal>misc</literal> with something else in your
 	      <makevar>CATEGORIES</makevar> line, that means you can
 	      safely delete <literal>misc</literal> and just put the
 	      port in that other subdirectory!</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>If your port truly does not belong anywhere else,
 	      put it in <filename>misc</filename>.</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>If you are not sure about the category, please put a
 	  comment to that effect in your &man.send-pr.1; submission so
 	  we can discuss it before we import it.  If you are a
 	  committer, send a note to the &a.ports; so we can discuss it
 	  first.  Too often, new ports are imported to the wrong
 	  category only to be moved right away.  This causes
 	  unnecessary and undesirable bloat in the master source
 	  repository.</para>
       </sect2>
 
       <sect2 id="proposing-categories">
 	<title>Proposing a New Category</title>
 
 	<para>As the Ports Collection has grown over time, various new
 	  categories have been introduced.  New categories can either
 	  be <emphasis>virtual</emphasis> categories&mdash;those that
 	  do not have a corresponding subdirectory in the ports
 	  tree&mdash; or <emphasis>physical</emphasis>
 	  categories&mdash;those that do.  The following text
 	  discusses the issues involved in creating a new physical
 	  category so that you can understand them before you propose
 	  one.</para>
 
 	<para>Our existing practice has been to avoid creating a new
 	  physical category unless either a large number of ports
 	  would logically belong to it, or the ports that would belong
 	  to it are a logically distinct group that is of limited
 	  general interest (for instance, categories related to spoken
 	  human languages), or preferably both.</para>
 
 	<para>The rationale for this is that such a change creates a
 	  <ulink url="&url.articles.committers-guide;/#ports"> fair
 	    amount of work</ulink> for both the committers and also
 	  for all users who track changes to the Ports Collection.  In
 	  addition, proposed category changes just naturally seem to
 	  attract controversy.  (Perhaps this is because there is no
 	  clear consensus on when a category is <quote>too
 	    big</quote>, nor whether categories should lend themselves
 	  to browsing (and thus what number of categories would be an
 	  ideal number), and so forth.)</para>
 
 	<para>Here is the procedure:</para>
 
 	<procedure>
 	  <step>
 	    <para>Propose the new category on &a.ports;.  You should
 	      include a detailed rationale for the new category,
 	      including why you feel the existing categories are not
 	      sufficient, and the list of existing ports proposed to
 	      move.  (If there are new ports pending in
 	      <application>GNATS</application> that would fit this
 	      category, list them too.)  If you are the maintainer
 	      and/or submitter, respectively, mention that as it may
 	      help you to make your case.</para>
 	  </step>
 
 	  <step>
 	    <para>Participate in the discussion.</para>
 	  </step>
 
 	  <step>
 	    <para>If it seems that there is support for your idea,
 	      file a PR which includes both the rationale and the list
 	      of existing ports that need to be moved.  Ideally, this
 	      PR should also include patches for the following:</para>
 
 	    <itemizedlist>
 	      <listitem>
 		<para><filename>Makefile</filename>s for the
 		  new ports once they are repocopied</para>
 	      </listitem>
 
 	      <listitem>
 		<para><filename>Makefile</filename> for the
 		  new category</para>
 	      </listitem>
 
 	      <listitem>
 		<para><filename>Makefile</filename> for the
 		  old ports' categories</para>
 	      </listitem>
 
 	      <listitem>
 		<para><filename>Makefile</filename>s for ports
 		  that depend on the old ports</para>
 	      </listitem>
 
 	      <listitem>
 		<para>(for extra credit, you can include the other
 		  files that have to change, as per the procedure
 		  in the Committer's Guide.)</para>
 	      </listitem>
 	    </itemizedlist>
 	  </step>
 
 	  <step>
 	    <para>Since it affects the ports infrastructure and
 	      involves not only performing repo-copies but also
 	      possibly running regression tests on the build cluster,
 	      the PR should be assigned to the &a.portmgr;.</para>
 	  </step>
 
 	  <step>
 	    <para>If that PR is approved, a committer will need to
 	      follow the rest of the procedure that is <ulink
 		url="&url.articles.committers-guide;/article.html#PORTS">
 		outlined in the Committer's Guide</ulink>.</para>
 	  </step>
 	</procedure>
 
 	<para>Proposing a new virtual category should be similar to
 	  the above but much less involved, since no ports will
 	  actually have to move.  In this case, the only patches to
 	  include in the PR would be those to add the new category to
 	  the <makevar>CATEGORIES</makevar> of the affected
 	  ports.</para>
       </sect2>
 
       <sect2 id="proposing-reorg">
 	<title>Proposing Reorganizing All the Categories</title>
 
 	<para>Occasionally someone proposes reorganizing the
 	  categories with either a 2-level structure, or some other
 	  kind of keyword structure.  To date, nothing has come of any
 	  of these proposals because, while they are very easy to
 	  make, the effort involved to retrofit the entire existing
 	  ports collection with any kind of reorganization is daunting
 	  to say the very least.  Please read the history of these
 	  proposals in the mailing list archives before you post this
 	  idea; furthermore, you should be prepared to be challenged
 	  to offer a working prototype.</para>
       </sect2>
     </sect1>
 
     <sect1 id="makefile-distfiles">
       <title>The Distribution Files</title>
 
       <para>The second part of the <filename>Makefile</filename>
 	describes the files that must be downloaded in order to build
 	the port, and where they can be downloaded from.</para>
 
       <sect2>
 	<title><makevar>DISTVERSION/DISTNAME</makevar></title>
 
 	<para><makevar>DISTNAME</makevar> is the name of the port as
 	  called by the authors of the software.
 	  <makevar>DISTNAME</makevar> defaults to
 	  <literal>${PORTNAME}-${PORTVERSION}</literal>, so override
 	  it only if necessary.  <makevar>DISTNAME</makevar> is only
 	  used in two places.  First, the distribution file list
 	  (<makevar>DISTFILES</makevar>) defaults to
 	  <makevar>${DISTNAME}</makevar><makevar>${EXTRACT_SUFX}</makevar>.
 	  Second, the distribution file is expected to extract into a
 	  subdirectory named <makevar>WRKSRC</makevar>, which defaults
 	  to
 	  <filename>work/<makevar>${DISTNAME}</makevar></filename>.</para>
 
 	<para>Some vendor's distribution names which do not fit into
 	  the <literal>${PORTNAME}-${PORTVERSION}</literal>-scheme can
 	  be handled automatically by setting
 	  <makevar>DISTVERSION</makevar>.
 	  <makevar>PORTVERSION</makevar> and
 	  <makevar>DISTNAME</makevar> will be derived automatically,
 	  but can of course be overridden.  The following table lists
 	  some examples:</para>
 
 	<informaltable frame="none" pgwide="0">
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry><makevar>DISTVERSION</makevar></entry>
 		<entry><makevar>PORTVERSION</makevar></entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry>0.7.1d</entry>
 		<entry>0.7.1.d</entry>
 	      </row>
 
 	      <row>
 		<entry>10Alpha3</entry>
 		<entry>10.a3</entry>
 	      </row>
 
 	      <row>
 		<entry>3Beta7-pre2</entry>
 		<entry>3.b7.p2</entry>
 	      </row>
 
 	      <row>
 		<entry>8:f_17</entry>
 		<entry>8f.17</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
 	<note>
 	  <para><makevar>PKGNAMEPREFIX</makevar> and
 	    <makevar>PKGNAMESUFFIX</makevar> do not affect
 	    <makevar>DISTNAME</makevar>.  Also note that if
 	    <makevar>WRKSRC</makevar> is equal to
 	    <filename>work/<makevar>${PORTNAME}-${PORTVERSION}</makevar></filename>
 	    while the original source archive is named something other
 	    than
 	    <makevar>${PORTNAME}-${PORTVERSION}${EXTRACT_SUFX}</makevar>,
 	    you should probably leave <makevar>DISTNAME</makevar>
 	    alone&mdash; you are better off defining
 	    <makevar>DISTFILES</makevar> than having to set both
 	    <makevar>DISTNAME</makevar> and <makevar>WRKSRC</makevar>
 	    (and possibly <makevar>EXTRACT_SUFX</makevar>).</para>
 	</note>
       </sect2>
 
       <sect2>
 	<title><makevar>MASTER_SITES</makevar></title>
 
 	<para>Record the directory part of the FTP/HTTP-URL pointing
 	  at the original tarball in <makevar>MASTER_SITES</makevar>.
 	  Do not forget the trailing slash
 	  (<filename>/</filename>)!</para>
 
 	<para>The <command>make</command> macros will try to use this
 	  specification for grabbing the distribution file with
 	  <makevar>FETCH</makevar> if they cannot find it already on
 	  the system.</para>
 
 	<para>It is recommended that you put multiple sites on this
 	  list, preferably from different continents.  This will
 	  safeguard against wide-area network problems.  We are even
 	  planning to add support for automatically determining the
 	  closest master site and fetching from there; having multiple
 	  sites will go a long way towards helping this effort.</para>
 
 	<para>If the original tarball is part of one of the popular
 	  archives such as SourceForge, GNU, or Perl CPAN, you may be
 	  able refer to those sites in an easy compact form using
 	  <makevar>MASTER_SITE_<replaceable>*</replaceable></makevar>
 	  (e.g., <makevar>MASTER_SITE_SOURCEFORGE</makevar>,
 	  <makevar>MASTER_SITE_GNU</makevar> and
 	  <makevar>MASTER_SITE_PERL_CPAN</makevar>).  Simply set
 	  <makevar>MASTER_SITES</makevar> to one of these variables
 	  and <makevar>MASTER_SITE_SUBDIR</makevar> to the path within
 	  the archive.  Here is an example:</para>
 
 	<programlisting>MASTER_SITES=		${MASTER_SITE_GNU}
 MASTER_SITE_SUBDIR=	make</programlisting>
 
 	<para>Or you can use a condensed format:</para>
 
 	<programlisting>MASTER_SITES=	GNU/make</programlisting>
 
 	<para>These variables are defined in
 	  <filename>/usr/ports/Mk/bsd.sites.mk</filename>.  There are
 	  new entries added all the time, so make sure to check the
 	  latest version of this file before submitting a port.</para>
 
 	<para>Several <emphasis>magic</emphasis> macros exist for
 	  popular sites with a predictable directory structure.  For
 	  these, just use the abbreviation and the system will try to
 	  guess the correct subdirectory for you.</para>
 
 	<programlisting>MASTER_SITES=	SF</programlisting>
 
 	<para>If the guess is incorrect, it can be overridden as
 	  follows.</para>
 
 	<programlisting>MASTER_SITES=	SF/stardict/WyabdcRealPeopleTTS/${PORTVERSION}</programlisting>
 
 	<para>This can be also written as</para>
 	<programlisting>MASTER_SITES=	SF
 MASTER_SITE_SUBDIR=	stardict/WyabdcRealPeopleTTS/${PORTVERSION}</programlisting>
 
 	<table frame="none">
 	  <title>Popular Magic <makevar>MASTER_SITES</makevar>
 	    Macros</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Macro</entry>
 		<entry>Assumed subdirectory</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>APACHE_JAKARTA</makevar></entry>
 		<entry><makevar>/dist/jakarta/${PORTNAME:S,-,,/,}/source</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>BERLIOS</makevar></entry>
 		<entry><makevar>/${PORTNAME:L}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>CHEESESHOP</makevar></entry>
 		<entry><makevar>/packages/source/source/${DISTNAME:C/(.).*/\1/}/${DISTNAME:C/(.*)-[0-9].*/\1/}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>DEBIAN</makevar></entry>
 		<entry><makevar>/debian/pool/main/${PORTNAME:C/^((lib)?.).*$/\1/}/${PORTNAME}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>GCC</makevar></entry>
 		<entry><makevar>/pub/gcc/releases/${DISTNAME}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>GNOME</makevar></entry>
 		<entry><makevar>/pub/GNOME/sources/${PORTNAME}/${PORTVERSION:C/^([0-9]+\.[0-9]+).*/\1/}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>GNU</makevar></entry>
 		<entry><makevar>/gnu/${PORTNAME}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>MOZDEV</makevar></entry>
 		<entry><makevar>/pub/mozdev/${PORTNAME:L}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>PERL_CPAN</makevar></entry>
 		<entry><makevar>/pub/CPAN/modules/by-module/${PORTNAME:C/-.*//}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>PYTHON</makevar></entry>
 		<entry><makevar>/ftp/python/${PYTHON_PORTVERSION:C/rc[0-9]//}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>RUBYFORGE</makevar></entry>
 		<entry><makevar>/${PORTNAME:L}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>SAVANNAH</makevar></entry>
 		<entry><makevar>/${PORTNAME:L}</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>SF</makevar></entry>
 		<entry><makevar>/project/${PORTNAME:L}/${PORTNAME:L}/${PORTVERSION}</makevar></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
       </sect2>
 
       <sect2>
 	<title><makevar>EXTRACT_SUFX</makevar></title>
 
 	<para>If you have one distribution file, and it uses an odd
 	  suffix to indicate the compression mechanism, set
 	  <makevar>EXTRACT_SUFX</makevar>.</para>
 
 	<para>For example, if the distribution file was named
 	  <filename>foo.tgz</filename> instead of the more normal
 	  <filename>foo.tar.gz</filename>, you would write:</para>
 
 	<programlisting>DISTNAME=	foo
 EXTRACT_SUFX=	.tgz</programlisting>
 
 	<para>The <makevar>USE_BZIP2</makevar>,
 	  <makevar>USE_XZ</makevar> and
 	  <makevar>USE_ZIP</makevar> variables automatically set
 	  <makevar>EXTRACT_SUFX</makevar> to
 	  <literal>.tar.bz2</literal>, <literal>.tar.xz</literal>
 	  or <literal>.zip</literal> as necessary.  If neither of
 	  these are set then <makevar>EXTRACT_SUFX</makevar>
 	  defaults to <literal>.tar.gz</literal>.</para>
 
 	<note>
 	  <para>You never need to set both
 	    <makevar>EXTRACT_SUFX</makevar> and
 	    <makevar>DISTFILES</makevar>.</para>
 	</note>
       </sect2>
 
       <sect2>
 	<title><makevar>DISTFILES</makevar></title>
 
 	<para>Sometimes the names of the files to be downloaded have
 	  no resemblance to the name of the port.  For example, it
 	  might be called <filename>source.tar.gz</filename> or
 	  similar.  In other cases the application's source code might
 	  be in several different archives, all of which must be
 	  downloaded.</para>
 
 	<para>If this is the case, set <makevar>DISTFILES</makevar> to
 	  be a space separated list of all the files that must be
 	  downloaded.</para>
 
 	<programlisting>DISTFILES=	source1.tar.gz source2.tar.gz</programlisting>
 
 	<para>If not explicitly set, <makevar>DISTFILES</makevar>
 	  defaults to
 	  <literal>${DISTNAME}${EXTRACT_SUFX}</literal>.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>EXTRACT_ONLY</makevar></title>
 
 	<para>If only some of the <makevar>DISTFILES</makevar> must be
 	  extracted&mdash;for example, one of them is the source code,
 	  while another is an uncompressed document&mdash;list the
 	  filenames that must be extracted in
 	  <makevar>EXTRACT_ONLY</makevar>.</para>
 
 	<programlisting>DISTFILES=	source.tar.gz manual.html
 EXTRACT_ONLY=	source.tar.gz</programlisting>
 
 	<para>If <emphasis>none</emphasis> of the
 	  <makevar>DISTFILES</makevar> should be uncompressed then set
 	  <makevar>EXTRACT_ONLY</makevar> to the empty string.</para>
 
 	<programlisting>EXTRACT_ONLY=</programlisting>
       </sect2>
 
       <sect2 id="porting-patchfiles">
 	<title><makevar>PATCHFILES</makevar></title>
 
 	<para>If your port requires some additional patches that are
 	  available by FTP or HTTP, set <makevar>PATCHFILES</makevar>
 	  to the names of the files and <makevar>PATCH_SITES</makevar>
 	  to the URL of the directory that contains them (the format
 	  is the same as <makevar>MASTER_SITES</makevar>).</para>
 
 	<para>If the patch is not relative to the top of the source
 	  tree (i.e., <makevar>WRKSRC</makevar>) because it contains
 	  some extra pathnames, set
 	  <makevar>PATCH_DIST_STRIP</makevar> accordingly.  For
 	  instance, if all the pathnames in the patch have an extra
 	  <literal>foozolix-1.0/</literal> in front of the filenames,
 	  then set <literal>PATCH_DIST_STRIP=-p1</literal>.</para>
 
 	<para>Do not worry if the patches are compressed; they will be
 	  decompressed automatically if the filenames end with
 	  <filename>.gz</filename> or <filename>.Z</filename>.</para>
 
 	<para>If the patch is distributed with some other files, such
 	  as documentation, in a <command>gzip</command>ped tarball,
 	  you cannot just use <makevar>PATCHFILES</makevar>.  If that
 	  is the case, add the name and the location of the patch
 	  tarball to <makevar>DISTFILES</makevar> and
 	  <makevar>MASTER_SITES</makevar>.  Then, use the
 	  <makevar>EXTRA_PATCHES</makevar> variable to point to those
 	  files and <filename>bsd.port.mk</filename> will
 	  automatically apply them for you.  In particular, do
 	  <emphasis>not</emphasis> copy patch files into the
 	  <makevar>PATCHDIR</makevar> directory&mdash;that directory
 	  may not be writable.</para>
 
 	<note>
 	  <para>The tarball will have been extracted alongside the
 	    regular source by then, so there is no need to explicitly
 	    extract it if it is a regular <command>gzip</command>ped
 	    or <command>compress</command>ed tarball.  If you do the
 	    latter, take extra care not to overwrite something that
 	    already exists in that directory.  Also, do not forget to
 	    add a command to remove the copied patch in the
 	    <maketarget>pre-clean</maketarget> target.</para>
 	</note>
       </sect2>
 
       <sect2 id="porting-master-sites-n">
 	<title>Multiple Distribution Files or Patches from Different
 	  Sites and Subdirectories
 	  (<literal>MASTER_SITES:n</literal>)</title>
 
 	<para>(Consider this to be a somewhat <quote>advanced
 	    topic</quote>; those new to this document may wish to skip
 	  this section at first).</para>
 
 	<para>This section has information on the fetching mechanism
 	  known as both <literal>MASTER_SITES:n</literal> and
 	  <literal>MASTER_SITES_NN</literal>.  We will refer to this
 	  mechanism as <literal>MASTER_SITES:n</literal>.</para>
 
 	<para>A little background first.  OpenBSD has a neat feature
 	  inside the <makevar>DISTFILES</makevar> and
 	  <makevar>PATCHFILES</makevar> variables which allows files
 	  and patches to be postfixed with <literal>:n</literal>
 	  identifiers.  Here, <literal>n</literal> can be both
 	  <literal>[0-9]</literal> and denote a group designation.
 	  For example:</para>
 
 	<programlisting>DISTFILES=	alpha:0 beta:1</programlisting>
 
 	<para>In OpenBSD, distribution file <filename>alpha</filename>
 	  will be associated with variable
 	  <makevar>MASTER_SITES0</makevar> instead of our common
 	  <makevar>MASTER_SITES</makevar> and
 	  <filename>beta</filename> with
 	  <makevar>MASTER_SITES1</makevar>.</para>
 
 	<para>This is a very interesting feature which can decrease
 	  that endless search for the correct download site.</para>
 
 	<para>Just picture 2 files in <makevar>DISTFILES</makevar> and
 	  20 sites in <makevar>MASTER_SITES</makevar>, the sites slow
 	  as hell where <filename>beta</filename> is carried by all
 	  sites in <makevar>MASTER_SITES</makevar>, and
 	  <filename>alpha</filename> can only be found in the 20th
 	  site.  It would be such a waste to check all of them if the
 	  maintainer knew this beforehand, would it not?  Not a good
 	  start for that lovely weekend!</para>
 
 	<para>Now that you have the idea, just imagine more
 	  <makevar>DISTFILES</makevar> and more
 	  <makevar>MASTER_SITES</makevar>.  Surely our
 	  <quote>distfiles survey meister</quote> would appreciate the
 	  relief to network strain that this would bring.</para>
 
 	<para>In the next sections, information will follow on the
 	  FreeBSD implementation of this idea.  We improved a bit on
 	  OpenBSD's concept.</para>
 
 	<sect3>
 	  <title>Simplified Information</title>
 
 	  <para>This section tells you how to quickly prepare fine
 	    grained fetching of multiple distribution files and
 	    patches from different sites and subdirectories.  We
 	    describe here a case of simplified
 	    <literal>MASTER_SITES:n</literal> usage.  This will be
 	    sufficient for most scenarios.  However, if you need
 	    further information, you will have to refer to the next
 	    section.</para>
 
 	  <para>Some applications consist of multiple distribution
 	    files that must be downloaded from a number of different
 	    sites.  For example,
 	    <application>Ghostscript</application> consists of the
 	    core of the program, and then a large number of driver
 	    files that are used depending on the user's printer.  Some
 	    of these driver files are supplied with the core, but many
 	    others must be downloaded from a variety of different
 	    sites.</para>
 
 	  <para>To support this, each entry in
 	    <makevar>DISTFILES</makevar> may be followed by a colon
 	    and a <quote>tag name</quote>.  Each site listed in
 	    <makevar>MASTER_SITES</makevar> is then followed by a
 	    colon, and the tag that indicates which distribution files
 	    should be downloaded from this site.</para>
 
 	  <para>For example, consider an application with the source
 	    split in two parts, <filename>source1.tar.gz</filename>
 	    and <filename>source2.tar.gz</filename>, which must be
 	    downloaded from two different sites.  The port's
 	    <filename>Makefile</filename> would include lines like
 	    <xref
 	      linkend="ports-master-sites-n-example-simple-use-one-file-per-site"/>.</para>
 
 	  <example
 	    id="ports-master-sites-n-example-simple-use-one-file-per-site">
 	    <title>Simplified Use of <literal>MASTER_SITES:n</literal>
 	      with One File Per Site</title>
 
 	    <programlisting>MASTER_SITES=	ftp://ftp.example1.com/:source1 \
 		ftp://ftp.example2.com/:source2
 DISTFILES=	source1.tar.gz:source1 \
 		source2.tar.gz:source2</programlisting>
 	  </example>
 
 	  <para>Multiple distribution files can have the same tag.
 	    Continuing the previous example, suppose that there was a
 	    third distfile, <filename>source3.tar.gz</filename>, that
 	    should be downloaded from
 	    <hostid>ftp.example2.com</hostid>.  The
 	    <filename>Makefile</filename> would then be written like
 	    <xref
 	      linkend="ports-master-sites-n-example-simple-use-more-than-one-file-per-site"/>.</para>
 
 	  <example
 	    id="ports-master-sites-n-example-simple-use-more-than-one-file-per-site">
 	    <title>Simplified Use of <literal>MASTER_SITES:n</literal>
 	      with More Than One File Per Site</title>
 
 	    <programlisting>MASTER_SITES=	ftp://ftp.example1.com/:source1 \
 		ftp://ftp.example2.com/:source2
 DISTFILES=	source1.tar.gz:source1 \
 		source2.tar.gz:source2 \
 		source3.tar.gz:source2</programlisting>
 	  </example>
 	</sect3>
 
 	<sect3>
 	  <title>Detailed Information</title>
 
 	  <para>Okay, so the previous section example did not reflect
 	    your needs?  In this section we will explain in detail
 	    how the fine grained fetching mechanism
 	    <literal>MASTER_SITES:n</literal> works and how you can
 	    modify your ports to use it.</para>
 
 	  <orderedlist>
 	    <listitem>
 	      <para>Elements can be postfixed with
 		<literal>:<replaceable>n</replaceable></literal> where
 		<replaceable>n</replaceable> is
 		<literal>[^:,]+</literal>, i.e.,
 		<replaceable>n</replaceable> could conceptually be any
 		alphanumeric string but we will limit it to
 		<literal>[a-zA-Z_][0-9a-zA-Z_]+</literal> for
 		now.</para>
 
 	      <para>Moreover, string matching is case sensitive;
 		i.e., <literal>n</literal> is different from
 		<literal>N</literal>.</para>
 
 	      <para>However, the following words cannot be used for
 		postfixing purposes since they yield special meaning:
 		<literal>default</literal>, <literal>all</literal> and
 		<literal>ALL</literal> (they are used internally in
 		item <xref
 		  linkend="porting-master-sites-n-what-changes-in-port-targets"/>).
 		Furthermore, <literal>DEFAULT</literal> is a special
 		purpose word (check item <xref
 		  linkend="porting-master-sites-n-DEFAULT-group"/>).</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Elements postfixed with <literal>:n</literal>
 		belong to the group <literal>n</literal>,
 		<literal>:m</literal> belong to group
 		<literal>m</literal> and so forth.</para>
 	    </listitem>
 
 	    <listitem id="porting-master-sites-n-DEFAULT-group">
 	      <para>Elements without a postfix are groupless, i.e.,
 		they all belong to the special group
 		<literal>DEFAULT</literal>.  If you postfix any
 		elements with <literal>DEFAULT</literal>, you are just
 		being redundant unless you want to have an element
 		belonging to both <literal>DEFAULT</literal> and other
 		groups at the same time (check item <xref
 		  linkend="porting-master-sites-n-comma-operator"/>).</para>
 
 	      <para>The following examples are equivalent but the
 		first one is preferred:</para>
 
 	      <programlisting>MASTER_SITES=	alpha</programlisting>
 
 	      <programlisting>MASTER_SITES=	alpha:DEFAULT</programlisting>
 	    </listitem>
 
 	    <listitem>
 	      <para>Groups are not exclusive, an element may belong to
 		several different groups at the same time and a group
 		can either have either several different elements or
 		none at all.  Repeated elements within the same group
 		will be simply that, repeated elements.</para>
 	    </listitem>
 
 	    <listitem id="porting-master-sites-n-comma-operator">
 	      <para>When you want an element to belong to several
 		groups at the same time, you can use the comma
 		operator (<literal>,</literal>).</para>
 
 	      <para>Instead of repeating it several times, each time
 		with a different postfix, we can list several groups
 		at once in a single postfix.  For instance,
 		<literal>:m,n,o</literal> marks an element that
 		belongs to group <literal>m</literal>,
 		<literal>n</literal> and <literal>o</literal>.</para>
 
 	      <para>All the following examples are equivalent but the
 		last one is preferred:</para>
 
 	      <programlisting>MASTER_SITES=	alpha alpha:SOME_SITE</programlisting>
 
 	      <programlisting>MASTER_SITES=	alpha:DEFAULT alpha:SOME_SITE</programlisting>
 
 	      <programlisting>MASTER_SITES=	alpha:SOME_SITE,DEFAULT</programlisting>
 
 	      <programlisting>MASTER_SITES=	alpha:DEFAULT,SOME_SITE</programlisting>
 	    </listitem>
 
 	    <listitem>
 	      <para>All sites within a given group are sorted
 		according to <makevar>MASTER_SORT_AWK</makevar>.  All
 		groups within <makevar>MASTER_SITES</makevar> and
 		<makevar>PATCH_SITES</makevar> are sorted as
 		well.</para>
 	    </listitem>
 
 	    <listitem id="porting-master-sites-n-group-semantics">
 	      <para>Group semantics can be used in any of the
 		following variables <makevar>MASTER_SITES</makevar>,
 		<makevar>PATCH_SITES</makevar>,
 		<makevar>MASTER_SITE_SUBDIR</makevar>,
 		<makevar>PATCH_SITE_SUBDIR</makevar>,
 		<makevar>DISTFILES</makevar>, and
 		<makevar>PATCHFILES</makevar> according to the
 		following syntax:</para>
 
 	      <orderedlist>
 		<listitem>
 		  <para>All <makevar>MASTER_SITES</makevar>,
 		    <makevar>PATCH_SITES</makevar>,
 		    <makevar>MASTER_SITE_SUBDIR</makevar> and
 		    <makevar>PATCH_SITE_SUBDIR</makevar> elements must
 		    be terminated with the forward slash
 		    <literal>/</literal> character.  If any elements
 		    belong to any groups, the group postfix
 		    <literal>:<replaceable>n</replaceable></literal>
 		    must come right after the terminator
 		    <literal>/</literal>.  The
 		    <literal>MASTER_SITES:n</literal> mechanism relies
 		    on the existence of the terminator
 		    <literal>/</literal> to avoid confusing elements
 		    where a <literal>:n</literal> is a valid part of
 		    the element with occurrences where
 		    <literal>:n</literal> denotes group
 		    <literal>n</literal>.  For compatibility purposes,
 		    since the <literal>/</literal> terminator was not
 		    required before in both
 		    <makevar>MASTER_SITE_SUBDIR</makevar> and
 		    <makevar>PATCH_SITE_SUBDIR</makevar> elements, if
 		    the postfix immediate preceding character is not
 		    a <literal>/</literal> then <literal>:n</literal>
 		    will be considered a valid part of the element
 		    instead of a group postfix even if an element is
 		    postfixed with <literal>:n</literal>.  See both
 		    <xref
 		      linkend="ports-master-sites-n-example-detailed-use-master-site-subdir"/>
 		    and <xref
 		      linkend="ports-master-sites-n-example-detailed-use-complete-example-master-sites"/>.</para>
 
 		  <example
 		    id="ports-master-sites-n-example-detailed-use-master-site-subdir">
 
 		    <title>Detailed Use of
 		      <literal>MASTER_SITES:n</literal> in
 		      <makevar>MASTER_SITE_SUBDIR</makevar></title>
 
 		    <programlisting>MASTER_SITE_SUBDIR=	old:n new/:NEW</programlisting>
 
 		    <itemizedlist>
 		      <listitem>
 			<para>Directories within group
 			  <literal>DEFAULT</literal> -&gt;
 			  old:n</para>
 		      </listitem>
 
 		      <listitem>
 			<para>Directories within group
 			  <literal>NEW</literal> -&gt; new</para>
 		      </listitem>
 		    </itemizedlist>
 		  </example>
 
 		  <example
 		    id="ports-master-sites-n-example-detailed-use-complete-example-master-sites">
 		    <title>Detailed Use of
 		      <literal>MASTER_SITES:n</literal> with Comma
 		      Operator, Multiple Files, Multiple Sites and
 		      Multiple Subdirectories</title>
 
 		    <programlisting>MASTER_SITES=	http://site1/%SUBDIR%/ http://site2/:DEFAULT \
 		http://site3/:group3 http://site4/:group4 \
 		http://site5/:group5 http://site6/:group6 \
 		http://site7/:DEFAULT,group6 \
 		http://site8/%SUBDIR%/:group6,group7 \
 		http://site9/:group8
 DISTFILES=	file1 file2:DEFAULT file3:group3 \
 		file4:group4,group5,group6 file5:grouping \
 		file6:group7
 MASTER_SITE_SUBDIR=	directory-trial:1 directory-n/:groupn \
 			directory-one/:group6,DEFAULT \
 			directory</programlisting>
 
 		    <para>The previous example results in the
 		      following fine grained fetching.  Sites are
 		      listed in the exact order they will be
 		      used.</para>
 
 		    <itemizedlist>
 		      <listitem>
 			<para><filename>file1</filename> will be
 			  fetched from</para>
 
 			<itemizedlist>
 			  <listitem>
 			    <para><makevar>MASTER_SITE_OVERRIDE</makevar></para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site1/directory-trial:1/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site1/directory-one/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site1/directory/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site2/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site7/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para><makevar>MASTER_SITE_BACKUP</makevar></para>
 			  </listitem>
 			</itemizedlist>
 		      </listitem>
 
 		      <listitem>
 			<para><filename>file2</filename> will be
 			  fetched exactly as
 			  <filename>file1</filename> since they
 			  both belong to the same group</para>
 
 			<itemizedlist>
 			  <listitem>
 			    <para><makevar>MASTER_SITE_OVERRIDE</makevar></para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site1/directory-trial:1/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site1/directory-one/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site1/directory/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site2/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site7/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para><makevar>MASTER_SITE_BACKUP</makevar></para>
 			  </listitem>
 			</itemizedlist>
 		      </listitem>
 
 		      <listitem>
 			<para><filename>file3</filename> will be
 			  fetched from</para>
 
 			<itemizedlist>
 			  <listitem>
 			    <para><makevar>MASTER_SITE_OVERRIDE</makevar></para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site3/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para><makevar>MASTER_SITE_BACKUP</makevar></para>
 			  </listitem>
 			</itemizedlist>
 		      </listitem>
 
 		      <listitem>
 			<para><filename>file4</filename> will be
 			  fetched from</para>
 
 			<itemizedlist>
 			  <listitem>
 			    <para><makevar>MASTER_SITE_OVERRIDE</makevar></para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site4/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site5/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site6/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site7/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site8/directory-one/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para><makevar>MASTER_SITE_BACKUP</makevar></para>
 			  </listitem>
 			</itemizedlist>
 		      </listitem>
 
 		      <listitem>
 			<para><filename>file5</filename> will be
 			  fetched from</para>
 
 			<itemizedlist>
 			  <listitem>
 			    <para><makevar>MASTER_SITE_OVERRIDE</makevar></para>
 			  </listitem>
 
 			  <listitem>
 			    <para><makevar>MASTER_SITE_BACKUP</makevar></para>
 			  </listitem>
 			</itemizedlist>
 		      </listitem>
 
 		      <listitem>
 			<para><filename>file6</filename> will be
 			  fetched from</para>
 
 			<itemizedlist>
 			  <listitem>
 			    <para><makevar>MASTER_SITE_OVERRIDE</makevar></para>
 			  </listitem>
 
 			  <listitem>
 			    <para>http://site8/</para>
 			  </listitem>
 
 			  <listitem>
 			    <para><makevar>MASTER_SITE_BACKUP</makevar></para>
 			  </listitem>
 			</itemizedlist>
 		      </listitem>
 		    </itemizedlist>
 		  </example>
 		</listitem>
 	      </orderedlist>
 	    </listitem>
 
 	    <listitem>
 	      <para>How do I group one of the special variables from
 		<filename>bsd.sites.mk</filename>, e.g.,
 		<makevar>MASTER_SITE_SOURCEFORGE</makevar>?</para>
 
 	      <para>See <xref
 		  linkend="ports-master-sites-n-example-detailed-use-master-site-sourceforge"/>.</para>
 
 	      <example
 		id="ports-master-sites-n-example-detailed-use-master-site-sourceforge">
 		<title>Detailed Use of
 		  <literal>MASTER_SITES:n</literal> with
 		  <makevar>MASTER_SITE_SOURCEFORGE</makevar></title>
 
 		<programlisting>MASTER_SITES=	http://site1/ ${MASTER_SITE_SOURCEFORGE:S/$/:sourceforge,TEST/}
 DISTFILES=	something.tar.gz:sourceforge</programlisting>
 	      </example>
 
 	      <para><filename>something.tar.gz</filename> will be
 		fetched from all sites within
 		<makevar>MASTER_SITE_SOURCEFORGE</makevar>.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>How do I use this with <makevar>PATCH*</makevar>
 		variables?</para>
 
 	      <para>All examples were done with
 		<makevar>MASTER*</makevar> variables but they work
 		exactly the same for <makevar>PATCH*</makevar> ones as
 		can be seen in <xref
 		  linkend="ports-master-sites-n-example-detailed-use-patch-sites"/>.</para>
 
 	      <example
 		id="ports-master-sites-n-example-detailed-use-patch-sites">
 		<title>Simplified Use of
 		  <literal>MASTER_SITES:n</literal> with
 		  <makevar>PATCH_SITES</makevar></title>
 
 		<programlisting>PATCH_SITES=	http://site1/ http://site2/:test
 PATCHFILES=	patch1:test</programlisting>
 	      </example>
 	    </listitem>
 	  </orderedlist>
 	</sect3>
 
 	<sect3>
 	  <title>What Does Change for Ports?  What Does Not?</title>
 
 	  <orderedlist numeration="lowerroman">
 	    <listitem>
 	      <para>All current ports remain the same.  The
 		<literal>MASTER_SITES:n</literal> feature code is only
 		activated if there are elements postfixed with
 		<literal>:<replaceable>n</replaceable></literal> like
 		elements according to the aforementioned syntax rules,
 		especially as shown in item <xref
 		  linkend="porting-master-sites-n-group-semantics"/>.</para>
 	    </listitem>
 
 	    <listitem
 	      id="porting-master-sites-n-what-changes-in-port-targets">
 	      <para>The port targets remain the same:
 		<maketarget>checksum</maketarget>,
 		<maketarget>makesum</maketarget>,
 		<maketarget>patch</maketarget>,
 		<maketarget>configure</maketarget>,
 		<maketarget>build</maketarget>, etc.  With the obvious
 		exceptions of <maketarget>do-fetch</maketarget>,
 		<maketarget>fetch-list</maketarget>,
 		<maketarget>master-sites</maketarget> and
 		<maketarget>patch-sites</maketarget>.</para>
 
 	      <itemizedlist>
 		<listitem>
 		  <para><maketarget>do-fetch</maketarget>: deploys the
 		    new grouping postfixed
 		    <makevar>DISTFILES</makevar> and
 		    <makevar>PATCHFILES</makevar> with their matching
 		    group elements within both
 		    <makevar>MASTER_SITES</makevar> and
 		    <makevar>PATCH_SITES</makevar> which use matching
 		    group elements within both
 		    <makevar>MASTER_SITE_SUBDIR</makevar> and
 		    <makevar>PATCH_SITE_SUBDIR</makevar>.  Check <xref
 		      linkend="ports-master-sites-n-example-detailed-use-complete-example-master-sites"/>.</para>
 		</listitem>
 
 		<listitem>
 		  <para><maketarget>fetch-list</maketarget>: works
 		    like old <maketarget>fetch-list</maketarget> with
 		    the exception that it groups just like
 		    <maketarget>do-fetch</maketarget>.</para>
 		</listitem>
 
 		<listitem>
 		  <para><maketarget>master-sites</maketarget> and
 		    <maketarget>patch-sites</maketarget>:
 		    (incompatible with older versions) only return the
 		    elements of group <literal>DEFAULT</literal>;  in
 		    fact, they execute targets
 		    <maketarget>master-sites-default</maketarget> and
 		    <maketarget>patch-sites-default</maketarget>
 		    respectively.</para>
 
 		  <para>Furthermore, using target either
 		    <maketarget>master-sites-all</maketarget> or
 		    <maketarget>patch-sites-all</maketarget> is
 		    preferred to directly checking either
 		    <maketarget>MASTER_SITES</maketarget> or
 		    <maketarget>PATCH_SITES</maketarget>.  Also,
 		    directly checking is not guaranteed to work in any
 		    future versions.  Check item <xref
 		      linkend="porting-master-sites-n-new-port-targets-master-sites-all"/>
 		    for more information on these new port
 		    targets.</para>
 		</listitem>
 	      </itemizedlist>
 	    </listitem>
 
 	    <listitem>
 	      <para>New port targets</para>
 
 	      <orderedlist>
 		<listitem>
 		  <para>There are
 		    <maketarget>master-sites-<replaceable>n</replaceable></maketarget>
 		    and
 		    <maketarget>patch-sites-<replaceable>n</replaceable></maketarget>
 		    targets which will list the elements of the
 		    respective group <replaceable>n</replaceable>
 		    within <makevar>MASTER_SITES</makevar> and
 		    <makevar>PATCH_SITES</makevar> respectively.  For
 		    instance, both
 		    <maketarget>master-sites-DEFAULT</maketarget> and
 		    <maketarget>patch-sites-DEFAULT</maketarget> will
 		    return the elements of group
 		    <literal>DEFAULT</literal>,
 		    <maketarget>master-sites-test</maketarget> and
 		    <maketarget>patch-sites-test</maketarget> of group
 		    <literal>test</literal>, and thereon.</para>
 		</listitem>
 
 		<listitem
 		  id="porting-master-sites-n-new-port-targets-master-sites-all">
 		  <para>There are new targets
 		    <maketarget>master-sites-all</maketarget> and
 		    <maketarget>patch-sites-all</maketarget> which do
 		    the work of the old
 		    <maketarget>master-sites</maketarget> and
 		    <maketarget>patch-sites</maketarget> ones.  They
 		    return the elements of all groups as if they all
 		    belonged to the same group with the caveat that it
 		    lists as many
 		    <makevar>MASTER_SITE_BACKUP</makevar> and
 		    <makevar>MASTER_SITE_OVERRIDE</makevar> as there
 		    are groups defined within either
 		    <makevar>DISTFILES</makevar> or
 		    <makevar>PATCHFILES</makevar>;  respectively for
 		    <maketarget>master-sites-all</maketarget> and
 		    <maketarget>patch-sites-all</maketarget>.</para>
 		</listitem>
 	      </orderedlist>
 	    </listitem>
 	  </orderedlist>
 	</sect3>
       </sect2>
 
       <sect2>
 	<title><makevar>DIST_SUBDIR</makevar></title>
 
 	<para>Do not let your port clutter
 	  <filename>/usr/ports/distfiles</filename>.  If your port
 	  requires a lot of files to be fetched, or contains a file
 	  that has a name that might conflict with other ports (e.g.,
 	  <filename>Makefile</filename>), set
 	  <makevar>DIST_SUBDIR</makevar> to the name of the port
 	  (<literal>${PORTNAME}</literal> or
 	  <literal>${PKGNAMEPREFIX}${PORTNAME}</literal> should work
 	  fine).  This will change <makevar>DISTDIR</makevar> from the
 	  default <filename>/usr/ports/distfiles</filename> to
 	  <filename>/usr/ports/distfiles/<makevar>DIST_SUBDIR</makevar></filename>,
 	  and in effect puts everything that is required for your port
 	  into that subdirectory.</para>
 
 	<para>It will also look at the subdirectory with the same name
 	  on the backup master site at
 	  <filename>ftp.FreeBSD.org</filename>.  (Setting
 	  <makevar>DISTDIR</makevar> explicitly in your
 	  <makevar>Makefile</makevar> will not accomplish this, so
 	  please use <makevar>DIST_SUBDIR</makevar>.)</para>
 
 	<note>
 	  <para>This does not affect the
 	    <makevar>MASTER_SITES</makevar> you define in your
 	    <filename>Makefile</filename>.</para>
 	</note>
       </sect2>
 
       <sect2>
 	<title><makevar>ALWAYS_KEEP_DISTFILES</makevar></title>
 
 	<para>If your port uses binary distfiles and has a license
 	  that requires that the source code is provided with packages
 	  distributed in binary form, e.g., GPL,
 	  <makevar>ALWAYS_KEEP_DISTFILES</makevar> will instruct the
 	  &os; build cluster to keep a copy of the files specified in
 	  <makevar>DISTFILES</makevar>.  Users of these ports will
 	  generally not need these files, so it is a good idea to only
 	  add the source distfiles to <makevar>DISTFILES</makevar>
 	  when <makevar>PACKAGE_BUILDING</makevar> is defined.</para>
 
 	<example
 	  id="ports-master-sites-n-example-always-keep-distfiles">
 	  <title>Use of
 	    <makevar>ALWAYS_KEEP_DISTFILES</makevar></title>
 
 	  <programlisting>.if defined(PACKAGE_BUILDING)
 DISTFILES+=		<replaceable>foo.tar.gz</replaceable>
 ALWAYS_KEEP_DISTFILES=	yes
 .endif</programlisting>
 	</example>
 
 	<para>When adding extra files to <makevar>DISTFILES</makevar>,
 	  make sure you also add them to
 	  <filename>distinfo</filename>.  Also, the additional files
 	  will normally be extracted into <makevar>WRKDIR</makevar> as
 	  well, which for some ports may lead to undesirable side
 	  effects and require special handling.</para>
       </sect2>
     </sect1>
 
     <sect1 id="makefile-maintainer">
       <title><makevar>MAINTAINER</makevar></title>
 
       <para>Set your mail-address here.  Please.  <!-- smiley
 	--><emphasis>:-)</emphasis></para>
 
       <para>Note that only a single address without the comment part
 	is allowed as a <makevar>MAINTAINER</makevar> value.  The
 	format used should be <literal>user@hostname.domain</literal>.
 	Please do not include any descriptive text such as your real
 	name in this entry&mdash;that merely confuses
 	<filename>bsd.port.mk</filename>.</para>
 
       <para>The maintainer is responsible for keeping the port up to
 	date, and ensuring the port works correctly.
 	For a detailed description of the responsibilities of a port
 	maintainer, refer to the <ulink
 	  url="&url.articles.contributing-ports;/maintain-port.html">The
 	  challenge for port maintainers</ulink> section.</para>
 
       <para>Changes to the port will be sent to the maintainer of a
 	port for review and approval before being committed.  If the
 	maintainer does not respond to an update request after two
 	weeks (excluding major public holidays), then that is
 	considered a maintainer timeout, and the update may be made
 	without explicit maintainer approval.  If the maintainer does
 	not respond within three months, then that maintainer is
 	considered absent without leave, and can be replaced as the
 	maintainer of the particular port in question.  Exceptions to
 	this are anything maintained by the &a.portmgr;, or the
 	&a.security-officer;.  No unauthorized commits may ever be
 	made to ports maintained by those groups.</para>
 
       <para>We reserve the right to modify the maintainer's submission
 	to better match existing policies and style of the Ports
 	Collection without explicit blessing from the submitter.
 	Also, large infrastructural changes can result in a port being
 	modified without the maintainer's consent.  These kinds of
 	changes will never affect the port's functionality.</para>
 
       <para>The &a.portmgr; reserves the right to revoke or override
 	anyone's maintainership for any reason, and the
 	&a.security-officer; reserves the right to revoke or override
 	maintainership for security reasons.</para>
     </sect1>
 
     <sect1 id="makefile-comment">
       <title><makevar>COMMENT</makevar></title>
 
       <para>This is a one-line description of the port.
 	Please respect the following rules:</para>
 
       <orderedlist>
 	<listitem>
 	  <para>Try to keep the COMMENT value at no longer than 70
 	    characters, as this line will be used by the
 	    &man.pkg.info.1; utility to display a one-line summary
 	    of the port;</para>
 	</listitem>
 
 	<listitem>
 	  <para>Do <emphasis>not</emphasis> include the package
 	    name (or version number of the software);</para>
 	</listitem>
 
 	<listitem>
 	  <para>The comment should begin with a capital and end
 	    without a period;</para>
 	</listitem>
 
 	<listitem>
 	  <para>Do not start with an indefinite article (i.e.,
 	    A or An);</para>
 	</listitem>
 
 	<listitem>
 	  <para>Names are capitalized (for example, Apache,
 	    JavaScript, Perl);</para>
 	</listitem>
 
 	<listitem>
 	  <para>For lists of words, use the Oxford comma (e.g.,
 	    green, red<emphasis>,</emphasis> and blue);</para>
 	</listitem>
 
 	<listitem>
 	  <para>Spell check the text.</para>
 	</listitem>
       </orderedlist>
 
       <para>Here is an example:</para>
 
       <programlisting>COMMENT=	Cat chasing a mouse all over the screen</programlisting>
 
       <para>The COMMENT variable should immediately follow the
 	MAINTAINER variable in the
 	<filename>Makefile</filename>.</para>
     </sect1>
 
     <sect1 id="makefile-portscout">
       <title><makevar>PORTSCOUT</makevar></title>
 
       <para><application>Portscout</application> is an automated
 	distfile check utility for the &os;&nbsp;Ports Collection,
 	described in detail in
 	<xref linkend="distfile-survey"/>.</para>
 
       <para>The <makevar>PORTSCOUT</makevar> variable defines
 	special conditions within which the
 	<application>Portscout</application> distfile
 	scanner should be restricted.</para>
 
       <para>Situations where the <makevar>PORTSCOUT</makevar>
 	variable should be set include:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>When distfiles should be ignored, whether for
 	    specific versions, or specific minor revisions.  For
 	    example, to exclude version
 	    <replaceable>8.2</replaceable> from distfile version
 	    checks because it is known to be broken, add:</para>
 
 	  <programlisting>PORTSCOUT=	ignore:8.2</programlisting>
 
 	</listitem>
 	<listitem>
 	  <para>When specific versions or specific major and minor
 	    revisions of a distfile should be checked.  For
 	    example, if only version
 	    <replaceable>0.6.4</replaceable> should be monitored
 	    because newer versions have compatablity issues with
 	    &os;, add:</para>
 
 	  <programlisting>PORTSCOUT=	limit:^0\.6\.4</programlisting>
 
 	</listitem>
 	<listitem>
 	  <para>When URLs listing the available versions differ
 	    from the download URLs.  For example, to limit
 	    distfile version checks to the download page for the
 	    <filename role="package">databases/pgtune</filename>
 	    port, add:</para>
 
 	  <programlisting>PORTSCOUT=	site:http://pgfoundry.org/frs/?group_id=1000416</programlisting>
 	</listitem>
       </itemizedlist>
     </sect1>
 
     <sect1 id="makefile-depend">
       <title>Dependencies</title>
 
       <para>Many ports depend on other ports.  This is a very
 	convenient feature of most Unix-like operating systems,
 	including &os;.  Multiple ports can share a common dependency,
 	rather than bundling that dependency with every port or
 	package that needs it.  There are seven variables that can be
 	used to ensure that all the required bits will be on the
 	user's machine.  There are also some pre-supported dependency
 	variables for common cases, plus a few more to control the
 	behavior of dependencies.</para>
 
       <sect2>
 	<title><makevar>LIB_DEPENDS</makevar></title>
 
 	<para>This variable specifies the shared libraries this port
 	  depends on.  It is a list of
 	  <replaceable>lib</replaceable>:<replaceable>dir</replaceable><optional><replaceable>:target</replaceable></optional>
 	  tuples where <replaceable>lib</replaceable> is the name of
 	  the shared library, <replaceable>dir</replaceable> is the
 	  directory in which to find it in case it is not available,
 	  and <replaceable>target</replaceable> is the target to call
 	  in that directory.  For example,</para>
 
 	<programlisting>LIB_DEPENDS=   jpeg:${PORTSDIR}/graphics/jpeg</programlisting>
 
 	<para>will check for a shared jpeg library with any version,
 	  and descend into the
 	  <filename>graphics/jpeg</filename> subdirectory of your
 	  ports tree to build and install it if it is not found.  The
 	  <replaceable>target</replaceable> part can be omitted if it
 	  is equal to <makevar>DEPENDS_TARGET</makevar> (which
 	  defaults to <literal>install</literal>).</para>
 
 	<note>
 	  <para>The <replaceable>lib</replaceable> part is a regular
 	    expression which is being looked up in the
 	    <command>ldconfig -r</command> output.  Values such as
 	    <literal>intl.9</literal> and
 	    <literal>intl.[5-7]</literal> are allowed.  The first
 	    pattern, <literal>intl.9</literal>, will match only
 	    version 9 of intl, while <literal>intl.[5-7]</literal>,
 	    will match any of: <literal>intl.5</literal>,
 	    <literal>intl.6</literal> or
 	    <literal>intl.7</literal>.</para>
 	</note>
 
 	<para>The dependency is checked twice, once from within the
 	  <maketarget>extract</maketarget> target and then from within
 	  the <maketarget>install</maketarget> target.  Also, the name
 	  of the dependency is put into the package so that
 	  &man.pkg.add.1; will automatically install it if it is not
 	  on the user's system.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>RUN_DEPENDS</makevar></title>
 
 	<para>This variable specifies executables or files this port
 	  depends on during run-time.  It is a list of
 	  <replaceable>path</replaceable>:<replaceable>dir</replaceable><optional><replaceable>:target</replaceable></optional>
 	  tuples where <replaceable>path</replaceable> is the name of
 	  the executable or file, <replaceable>dir</replaceable> is
 	  the directory in which to find it in case it is not
 	  available, and <replaceable>target</replaceable> is the
 	  target to call in that directory.  If
 	  <replaceable>path</replaceable> starts with a slash
 	  (<literal>/</literal>), it is treated as a file and its
 	  existence is tested with <command>test -e</command>;
 	  otherwise, it is assumed to be an executable, and
 	  <command>which -s</command> is used to determine if the
 	  program exists in the search path.</para>
 
 	<para>For example,</para>
 
 	<programlisting>RUN_DEPENDS=	${LOCALBASE}/news/bin/innd:${PORTSDIR}/news/inn \
 		xmlcatmgr:${PORTSDIR}/textproc/xmlcatmgr</programlisting>
 
 	<para>will check if the file or directory
 	  <filename>/usr/local/news/bin/innd</filename> exists, and
 	  build and install it from the <filename>news/inn</filename>
 	  subdirectory of the ports tree if it is not found.  It will
 	  also see if an executable called
 	  <command>xmlcatmgr</command> is in the search path, and
 	  descend into the <filename>textproc/xmlcatmgr</filename>
 	  subdirectory of your ports tree to build and install it if
 	  it is not found.</para>
 
 	<note>
 	  <para>In this case, <command>innd</command> is actually an
 	    executable; if an executable is in a place that is not
 	    expected to be in the search path, you should use the full
 	    pathname.</para>
 	</note>
 
 	<note>
 	  <para>The official search <envar>PATH</envar> used on the
 	    ports build cluster is</para>
 
 	  <programlisting>/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin</programlisting>
 	</note>
 
 	<para>The dependency is checked from within the
 	  <maketarget>install</maketarget> target.  Also, the name of
 	  the dependency is put into the package so that
 	  &man.pkg.add.1; will automatically install it if it is not
 	  on the user's system.  The <replaceable>target</replaceable>
 	  part can be omitted if it is the same as
 	  <makevar>DEPENDS_TARGET</makevar>.</para>
 
 	<para>A quite common situation is when
 	  <makevar>RUN_DEPENDS</makevar> is literally the same as
 	  <makevar>BUILD_DEPENDS</makevar>, especially if ported
 	  software is written in a scripted language or if it requires
 	  the same build and run-time environment.  In this
 	  case, it is both tempting and intuitive to directly
 	  assign one to the other:</para>
 
 	<programlisting>RUN_DEPENDS=	${BUILD_DEPENDS}</programlisting>
 
 	<para>However, such assignment can pollute run-time
 	  dependencies with entries not defined in the port's original
 	  <makevar>BUILD_DEPENDS</makevar>.  This happens because of
 	  &man.make.1;'s lazy evaluation of variable assignment.
 	  Consider a <filename>Makefile</filename> with
 	  <makevar>USE_<replaceable>*</replaceable></makevar>
 	  variables, which are processed by
 	  <filename>ports/Mk/bsd.*.mk</filename> to augment initial
 	  build dependencies.  For example,
 	  <literal>USE_GMAKE=yes</literal> adds <filename
 	    role="package">devel/gmake</filename> to
 	  <makevar>BUILD_DEPENDS</makevar>.  To prevent such
 	  additional dependencies from polluting
 	  <makevar>RUN_DEPENDS</makevar>, take care to assign with
 	  expansion, i.e., expand the value before assigning it to the
 	  variable:</para>
 
 	<programlisting>RUN_DEPENDS:=	${BUILD_DEPENDS}</programlisting>
       </sect2>
 
       <sect2>
 	<title><makevar>BUILD_DEPENDS</makevar></title>
 
 	<para>This variable specifies executables or files this port
 	  requires to build.  Like <makevar>RUN_DEPENDS</makevar>, it
 	  is a list of
 	  <replaceable>path</replaceable>:<replaceable>dir</replaceable><optional><replaceable>:target</replaceable></optional>
 	  tuples.  For example,</para>
 
 	<programlisting>BUILD_DEPENDS=	unzip:${PORTSDIR}/archivers/unzip</programlisting>
 
 	<para>will check for an executable called
 	  <command>unzip</command>, and descend into the
 	  <filename>archivers/unzip</filename> subdirectory of your
 	  ports tree to build and install it if it is not
 	  found.</para>
 
 	<note>
 	  <para><quote>build</quote> here means everything from
 	    extraction to compilation.  The dependency is checked from
 	    within the <maketarget>extract</maketarget> target.  The
 	    <replaceable>target</replaceable> part can be omitted if
 	    it is the same as <makevar>DEPENDS_TARGET</makevar></para>
 	</note>
       </sect2>
 
       <sect2>
 	<title><makevar>FETCH_DEPENDS</makevar></title>
 
 	<para>This variable specifies executables or files this port
 	  requires to fetch.  Like the previous two, it is a list of
 	  <replaceable>path</replaceable>:<replaceable>dir</replaceable><optional><replaceable>:target</replaceable></optional>
 	  tuples.  For example,</para>
 
 	<programlisting>FETCH_DEPENDS=	ncftp2:${PORTSDIR}/net/ncftp2</programlisting>
 
 	<para>will check for an executable called
 	  <command>ncftp2</command>, and descend into the
 	  <filename>net/ncftp2</filename> subdirectory of your ports
 	  tree to build and install it if it is not found.</para>
 
 	<para>The dependency is checked from within the
 	  <maketarget>fetch</maketarget> target.  The
 	  <replaceable>target</replaceable> part can be omitted if it
 	  is the same as <makevar>DEPENDS_TARGET</makevar>.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>EXTRACT_DEPENDS</makevar></title>
 
 	<para>This variable specifies executables or files this port
 	  requires for extraction.  Like the previous, it is a list of
 	  <replaceable>path</replaceable>:<replaceable>dir</replaceable><optional><replaceable>:target</replaceable></optional>
 	  tuples.  For example,</para>
 
 	<programlisting>EXTRACT_DEPENDS=	unzip:${PORTSDIR}/archivers/unzip</programlisting>
 
 	<para>will check for an executable called
 	  <command>unzip</command>, and descend into the
 	  <filename>archivers/unzip</filename> subdirectory of your
 	  ports tree to build and install it if it is not
 	  found.</para>
 
 	<para>The dependency is checked from within the
 	  <maketarget>extract</maketarget> target.  The
 	  <replaceable>target</replaceable> part can be omitted if it
 	  is the same as <makevar>DEPENDS_TARGET</makevar>.</para>
 
 	<note>
 	  <para>Use this variable only if the extraction does not
 	    already work (the default assumes <command>gzip</command>)
 	    and cannot be made to work using
 	    <makevar>USE_ZIP</makevar> or <makevar>USE_BZIP2</makevar>
 	    described in <xref linkend="use-vars"/>.</para>
 	</note>
       </sect2>
 
       <sect2>
 	<title><makevar>PATCH_DEPENDS</makevar></title>
 
 	<para>This variable specifies executables or files this port
 	  requires to patch.  Like the previous, it is a list of
 	  <replaceable>path</replaceable>:<replaceable>dir</replaceable><optional><replaceable>:target</replaceable></optional>
 	  tuples.  For example,</para>
 
 	<programlisting>PATCH_DEPENDS=	${NONEXISTENT}:${PORTSDIR}/java/jfc:extract</programlisting>
 
 	<para>will descend into the <filename>java/jfc</filename>
 	  subdirectory of your ports tree to extract it.</para>
 
 	<para>The dependency is checked from within the
 	  <maketarget>patch</maketarget> target.  The
 	  <replaceable>target</replaceable> part can be omitted if it
 	  is the same as <makevar>DEPENDS_TARGET</makevar>.</para>
       </sect2>
 
       <sect2 id="uses">
 	<title><makevar>USES</makevar></title>
 
 	<para>There several parameters exist for defining different
 	  kind of features and dependencies that the port in question
 	  uses.  They can be specified by adding the following line to
 	  the <filename>Makefile</filename> of the port:</para>
 
 	<programlisting>USES= feature[:arguments]</programlisting>
 
 	<para>For the complete list of such values, please see <xref
 	    linkend="uses-values"/>.</para>
 
 	<warning>
 	  <para><makevar>USES</makevar> cannot be assigned after
 	    inclusion of <filename>bsd.port.pre.mk</filename>.</para>
 	</warning>
       </sect2>
 
       <sect2 id="use-vars">
 	<title><makevar>USE_<replaceable>*</replaceable></makevar></title>
 
 	<para>Several variables exist to define
 	  common dependencies shared by many ports.  Their
 	  use is optional, but helps to reduce the verbosity of
 	  the port <filename>Makefile</filename>s.  Each of them is
 	  styled as
 	  <makevar>USE_<replaceable>*</replaceable></makevar>.
 	  These variables may be used only in the port
 	  <filename>Makefile</filename>s and
 	  <filename>ports/Mk/bsd.*.mk</filename>.  They are not meant
 	  for user-settable options &mdash; use
 	  <makevar>PORT_OPTIONS</makevar> for that purpose.</para>
 
 	<note>
 	  <para>It is <emphasis>always</emphasis> incorrect to set any
 	    <makevar>USE_<replaceable>*</replaceable></makevar> in
 	    <filename>/etc/make.conf</filename>.  For instance,
 	    setting</para>
 
 	  <programlisting>USE_GCC=3.4</programlisting>
 
 	  <para>would add a dependency on gcc34 for every port,
 	    including gcc34 itself!</para>
 	</note>
 
 	<table frame="none">
 	  <title>The
 	    <makevar>USE_<replaceable>*</replaceable></makevar>
 	    Variables</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Means</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_BZIP2</makevar></entry>
 		<entry>The port's tarballs are compressed with
 		  <command>bzip2</command>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_ZIP</makevar></entry>
 		<entry>The port's tarballs are compressed with
 		  <command>zip</command>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_GCC</makevar></entry>
 		<entry>The port requires a specific version of
 		  <command>gcc</command> to build.  The exact version
 		  can be specified with value such as
 		  <literal>3.4</literal>.  The minimal required
 		  version can be specified as <literal>3.4+</literal>.
 		  The <command>gcc</command> from the base system is
 		  used when it satisfies the requested version,
 		  otherwise an appropriate <command>gcc</command> is
 		  compiled from ports and the <makevar>CC</makevar>
 		  and <makevar>CXX</makevar> variables are
 		  adjusted.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>Variables related to <application>gmake</application>
 	  and the <filename>configure</filename> script are described
 	  in <xref linkend="building"/>, while
 	  <application>autoconf</application>,
 	  <application>automake</application> and
 	  <application>libtool</application> are described in
 	  <xref linkend="using-autotools"/>.
 	  <application>Perl</application> related variables are
 	  described in <xref linkend="using-perl"/>.  X11 variables
 	  are listed in <xref linkend="using-x11"/>.
 	  <xref linkend="using-gnome"/> deals with GNOME and
 	  <xref linkend="using-kde"/> with KDE related variables.
 	  <xref linkend="using-java"/> documents Java variables, while
 	  <xref linkend="using-php"/> contains information on
 	  <application>Apache</application>,
 	  <application>PHP</application> and PEAR modules.
 	  <application>Python</application> is discussed in
 	  <xref linkend="using-python"/>, while
 	  <application>Ruby</application> in
 	  <xref linkend="using-ruby"/>.  <xref linkend="using-sdl"/>
 	  provides variables used for <application>SDL</application>
 	  applications and finally, <xref linkend="using-xfce"/>
 	  contains information on
 	  <application>Xfce</application>.</para>
       </sect2>
 
       <sect2>
 	<title>Minimal Version of a Dependency</title>
 
 	<para>A minimal version of a dependency can be specified in
 	  any <makevar>*_DEPENDS</makevar> variable except
 	  <makevar>LIB_DEPENDS</makevar> using the following
 	  syntax:</para>
 
 	<programlisting>p5-Spiffy>=0.26:${PORTSDIR}/devel/p5-Spiffy</programlisting>
 
 	<para>The first field contains a dependent package name, which
 	  must match the entry in the package database, a comparison
 	  sign, and a package version.  The dependency is satisfied if
 	  p5-Spiffy-0.26 or newer is installed on the machine.</para>
       </sect2>
 
       <sect2>
 	<title>Notes on Dependencies</title>
 
 	<para>As mentioned above, the default target to call when a
 	  dependency is required is
 	  <maketarget>DEPENDS_TARGET</maketarget>.  It defaults to
 	  <literal>install</literal>.  This is a user variable; it is
 	  never defined in a port's <filename>Makefile</filename>.  If
 	  your port needs a special way to handle a dependency, use
 	  the <literal>:target</literal> part of the
 	  <makevar>*_DEPENDS</makevar> variables instead of redefining
 	  <makevar>DEPENDS_TARGET</makevar>.</para>
 
 	<para>When you type <command>make clean</command>, its
 	  dependencies are automatically cleaned too.  If you do not
 	  wish this to happen, define the variable
 	  <makevar>NOCLEANDEPENDS</makevar> in your environment.  This
 	  may be particularly desirable if the port has something that
 	  takes a long time to rebuild in its dependency list, such as
 	  KDE, GNOME or Mozilla.</para>
 
 	<para>To depend on another port unconditionally, use the
 	  variable <makevar>${NONEXISTENT}</makevar> as the first
 	  field of <makevar>BUILD_DEPENDS</makevar> or
 	  <makevar>RUN_DEPENDS</makevar>.  Use this only when you need
 	  to get the source of the other port.  You can often save
 	  compilation time by specifying the target too.  For
 	  instance</para>
 
 	<programlisting>BUILD_DEPENDS=	${NONEXISTENT}:${PORTSDIR}/graphics/jpeg:extract</programlisting>
 
 	<para>will always descend to the <literal>jpeg</literal> port
 	  and extract it.</para>
       </sect2>
 
       <sect2>
 	<title>Circular Dependencies Are Fatal</title>
 
 	<important>
 	  <para>Do not introduce any circular dependencies into the
 	    ports tree!</para>
 	</important>
 
 	<para>The ports building technology does not tolerate circular
 	  dependencies.  If you introduce one, you will have someone,
 	  somewhere in the world, whose FreeBSD installation will
 	  break almost immediately, with many others quickly to
 	  follow.  These can really be hard to detect; if in doubt,
 	  before you make that change, make sure you have done the
 	  following: <command>cd /usr/ports; make index</command>.
 	  That process can be quite slow on older machines, but you
 	  may be able to save a large number of people&mdash;including
 	  yourself&mdash; a lot of grief in the process.</para>
       </sect2>
 
       <sect2>
 	<title>Problems Caused by Automatic Dependencies</title>
 
 	<para>Dependencies must be declared either explicitly or by
 	  using the <link
 	    linkend="makefile-options">OPTIONS framework</link>.
 	  Using other methods like automatic detection complicates
 	  indexing, which causes problems for port and package
 	  management.</para>
 
 	<example>
 	  <title>Wrong Declaration of an Optional Dependency</title>
 
 	  <programlisting>.include &lt;bsd.port.pre.mk&gt;
 
 .if exists(${LOCALBASE}/bin/foo)
 LIB_DEPENDS=	bar:${PORTSDIR}/foo/bar
 .endif</programlisting>
 	</example>
 
 	<para>The problem with trying to automatically add
 	  dependencies is that files and settings outside an
 	  individual port can change at any time.  For example: an
 	  index is built, then a batch of ports are installed.  But
 	  one of the ports installs the tested file.  The index is now
 	  incorrect, because an installed port unexpectedly has a new
 	  dependency.  The index may still be wrong even after
 	  rebuilding if other ports also determine their need for
 	  dependencies based on the existence of other files.</para>
 
 	<example>
 	  <title>Correct Declaration of an Optional Dependency</title>
 
 	  <programlisting>OPTIONS_DEFINE=	BAR
 BAR_DESC=	Bar support
 
 .include &lt;bsd.port.options.mk&gt;
 
 .if ${PORT_OPTIONS:MBAR}
 LIB_DEPENDS=	bar:${PORTSDIR}/foo/bar
 .endif</programlisting>
 	</example>
 
 	<para>Testing option variables is the correct method.  It will
 	  not cause inconsistencies in the index of a batch of ports,
 	  provided the options were defined prior to the index build.
 	  Simple scripts can then be used to automate the building,
 	  installation, and updating of these ports and their
 	  packages.</para>
       </sect2>
 
       <sect2 id="use-want">
 	<title><makevar>USE_</makevar> and
 	  <makevar>WANT_</makevar></title>
 
 	<para><makevar>USE_</makevar> variables are set by the port
 	  maintainer to define software on which this port depends.  A
 	  port that needs Firefox would set</para>
 
 	<programlisting>USE_FIREFOX=	yes</programlisting>
 
 	<para>Some <makevar>USE_</makevar> variables can accept
 	  version numbers or other parameters.  For example, a port
 	  that requires Apache 2.2 would set</para>
 
 	<programlisting>USE_APACHE=	22</programlisting>
 
 	<para>For more control over dependencies in some cases,
 	  <makevar>WANT_</makevar> variables are available to more
 	  precisely specify what is needed.  For example, consider the
 	  <filename role="package">mail/squirrelmail</filename> port.
 	  This port needs some PHP modules, which are listed in the
 	  <makevar>USE_PHP</makevar> variable:</para>
 
 	<programlisting>USE_PHP=	session mhash gettext mbstring pcre openssl xml</programlisting>
 
 	<para>Those modules may be available in CLI or web versions,
 	  so the web version is selected with a
 	  <makevar>WANT_</makevar> variable:</para>
 
 	<programlisting>WANT_PHP_WEB=	yes</programlisting>
 
 	<para>Available <makevar>USE_</makevar> and
 	  <makevar>WANT_</makevar> variables are defined in the files
 	  in <filename>/usr/ports/Mk</filename>.</para>
       </sect2>
     </sect1>
 
     <sect1 id="makefile-masterdir">
       <title><makevar>MASTERDIR</makevar></title>
 
       <para>If your port needs to build slightly different versions of
 	packages by having a variable (for instance, resolution, or
 	paper size) take different values, create one subdirectory per
 	package to make it easier for users to see what to do, but try
 	to share as many files as possible between ports.  Typically
 	you only need a very short <filename>Makefile</filename> in
 	all but one of the directories if you use variables cleverly.
 	In the sole <filename>Makefile</filename>, you can use
 	<makevar>MASTERDIR</makevar> to specify the directory where
 	the rest of the files are.  Also, use a variable as part of
 	<link
 	  linkend="porting-pkgname"><makevar>PKGNAMESUFFIX</makevar></link>
 	so the packages will have different names.</para>
 
       <para>This will be best demonstrated by an example.  This is
 	part of <filename>japanese/xdvi300/Makefile</filename>;</para>
 
       <programlisting>PORTNAME=	xdvi
 PORTVERSION=	17
 PKGNAMEPREFIX=	ja-
 PKGNAMESUFFIX=	${RESOLUTION}
  :
 # default
 RESOLUTION?=	300
 .if ${RESOLUTION} != 118 &amp;&amp; ${RESOLUTION} != 240 &amp;&amp; \
 	${RESOLUTION} != 300 &amp;&amp; ${RESOLUTION} != 400
 	@${ECHO_MSG} "Error: invalid value for RESOLUTION: \"${RESOLUTION}\""
 	@${ECHO_MSG} "Possible values are: 118, 240, 300 (default) and 400."
 	@${FALSE}
 .endif</programlisting>
 
       <para><filename role="package">japanese/xdvi300</filename> also
 	has all the regular patches, package files, etc.  If you type
 	<command>make</command> there, it will take the default value
 	for the resolution (300) and build the port normally.</para>
 
       <para>As for other resolutions, this is the
 	<emphasis>entire</emphasis>
 	<filename>xdvi118/Makefile</filename>:</para>
 
       <programlisting>RESOLUTION=	118
 MASTERDIR=	${.CURDIR}/../xdvi300
 
 .include "${MASTERDIR}/Makefile"</programlisting>
 
       <para>(<filename>xdvi240/Makefile</filename> and
 	<filename>xdvi400/Makefile</filename> are similar).  The
 	<makevar>MASTERDIR</makevar> definition tells
 	<filename>bsd.port.mk</filename> that the regular set of
 	subdirectories like <makevar>FILESDIR</makevar> and
 	<makevar>SCRIPTDIR</makevar> are to be found under
 	<filename>xdvi300</filename>.  The
 	<literal>RESOLUTION=118</literal> line will override the
 	<literal>RESOLUTION=300</literal> line in
 	<filename>xdvi300/Makefile</filename> and the port will be
 	built with resolution set to 118.</para>
     </sect1>
 
     <sect1 id="makefile-manpages">
       <title>Man Pages</title>
 
       <para>The <makevar>MAN[1-9LN]</makevar> variables will
 	automatically add any manpages to
 	<filename>pkg-plist</filename> (this means you must
 	<emphasis>not</emphasis> list manpages in the
 	<filename>pkg-plist</filename>&mdash;see <link
 	  linkend="plist-sub">generating PLIST</link> for more).  It
 	also makes the install stage automatically compress or
 	uncompress manpages depending on the setting of
 	<makevar>NO_MANCOMPRESS</makevar> in
 	<filename>/etc/make.conf</filename>.</para>
 
       <para>If your port tries to install multiple names for manpages
 	using symlinks or hardlinks, you must use the
 	<makevar>MLINKS</makevar> variable to identify these.  The
 	link installed by your port will be destroyed and recreated by
 	<filename>bsd.port.mk</filename> to make sure it points to the
 	correct file.  Any manpages listed in MLINKS must not be
 	listed in the <filename>pkg-plist</filename>.</para>
 
       <para>To specify whether the manpages are compressed upon
 	installation, use the <makevar>MANCOMPRESSED</makevar>
 	variable.  This variable can take three values,
 	<literal>yes</literal>, <literal>no</literal> and
 	<literal>maybe</literal>.  <literal>yes</literal> means
 	manpages are already installed compressed,
 	<literal>no</literal> means they are not, and
 	<literal>maybe</literal> means the software already respects
 	the value of <makevar>NO_MANCOMPRESS</makevar> so
 	<filename>bsd.port.mk</filename> does not have to do anything
 	special.</para>
 
       <para><makevar>MANCOMPRESSED</makevar> is automatically set to
 	<literal>yes</literal> if <makevar>USE_IMAKE</makevar> is set
 	and <makevar>NO_INSTALL_MANPAGES</makevar> is not set, and to
 	<literal>no</literal> otherwise.  You do not have to
 	explicitly define it unless the default is not suitable for
 	your port.</para>
 
       <para>If your port anchors its man tree somewhere other than
 	<makevar>PREFIX</makevar>, you can use the
 	<makevar>MANPREFIX</makevar> to set it.  Also, if only
 	manpages in certain sections go in a non-standard place, such
 	as some <literal>perl</literal> modules ports, you can set
 	individual man paths using
 	<makevar>MAN<replaceable>sect</replaceable>PREFIX</makevar>
 	(where <replaceable>sect</replaceable> is one of
 	<literal>1-9</literal>, <literal>L</literal> or
 	<literal>N</literal>).</para>
 
       <para>If your manpages go to language-specific subdirectories,
 	set the name of the languages to <makevar>MANLANG</makevar>.
 	The value of this variable defaults to <literal>""</literal>
 	(i.e., English only).</para>
 
       <para>Here is an example that puts it all together.</para>
 
       <programlisting>MAN1=		foo.1
 MAN3=		bar.3
 MAN4=		baz.4
 MLINKS=		foo.1 alt-name.8
 MANLANG=	"" ja
 MAN3PREFIX=	${PREFIX}/share/foobar
 MANCOMPRESSED=	yes</programlisting>
 
       <para>This states that six files are installed by this
 	port;</para>
 
       <programlisting>${MANPREFIX}/man/man1/foo.1.gz
 ${MANPREFIX}/man/ja/man1/foo.1.gz
 ${PREFIX}/share/foobar/man/man3/bar.3.gz
 ${PREFIX}/share/foobar/man/ja/man3/bar.3.gz
 ${MANPREFIX}/man/man4/baz.4.gz
 ${MANPREFIX}/man/ja/man4/baz.4.gz</programlisting>
 
       <para>Additionally
 	<filename>${MANPREFIX}/man/man8/alt-name.8.gz</filename> may
 	or may not be installed by your port.  Regardless, a symlink
 	will be made to join the foo(1) manpage and alt-name(8)
 	manpage.</para>
 
       <para>If only some manpages are translated, you can use several
 	variables dynamically created from <makevar>MANLANG</makevar>
 	content:</para>
 
       <programlisting>MANLANG=	"" de ja
 MAN1=		foo.1
 MAN1_EN=	bar.1
 MAN3_DE=	baz.3</programlisting>
 
       <para>This translates into this list of files:</para>
 
       <programlisting>${MANPREFIX}/man/man1/foo.1.gz
 ${MANPREFIX}/man/de/man1/foo.1.gz
 ${MANPREFIX}/man/ja/man1/foo.1.gz
 ${MANPREFIX}/man/man1/bar.1.gz
 ${MANPREFIX}/man/de/man3/baz.3.gz</programlisting>
     </sect1>
 
     <sect1 id="makefile-info">
       <title>Info Files</title>
 
       <para>If your package needs to install GNU info files, they
 	should be listed in the <makevar>INFO</makevar> variable
 	(without the trailing <literal>.info</literal>), one entry per
 	document.  These files are assumed to be installed to
 	<filename><makevar>PREFIX</makevar>/<makevar>INFO_PATH</makevar></filename>.
 	You can change <makevar>INFO_PATH</makevar> if your package
 	uses a different location.  However, this is not recommended.
 	These entries contain just the path relative to
 	<filename><makevar>PREFIX</makevar>/<makevar>INFO_PATH</makevar></filename>.
 	For example, <filename role="package">lang/gcc34</filename>
 	installs info files to
 	<filename><makevar>PREFIX</makevar>/<makevar>INFO_PATH</makevar>/gcc34</filename>,
 	and <makevar>INFO</makevar> will be something like
 	this:</para>
 
       <programlisting>INFO=	gcc34/cpp gcc34/cppinternals gcc34/g77 ...</programlisting>
 
       <para>Appropriate installation/de-installation code will be
 	automatically added to the temporary
 	<filename>pkg-plist</filename> before package
 	registration.</para>
     </sect1>
 
     <sect1 id="makefile-options">
       <title>Makefile Options</title>
 
       <para>Many applications can be built with optional or differing
 	configurations.  Examples include choice of natural (human)
 	language, GUI versus command-line, or type of database to
 	support.  Users may need a different configuration than the
 	default, so the ports system provides hooks the port author
 	can use to control which variant will be built.  Supporting
 	these options properly will make users happy, and effectively
 	provide two or more ports for the price of one.</para>
 
       <sect2>
 	<title>Knobs</title>
 
 	<sect3>
 	  <title><makevar>WITH_<replaceable>*</replaceable></makevar>
 	    and
 	    <makevar>WITHOUT_<replaceable>*</replaceable></makevar></title>
 
 	  <para>These variables are designed to be set by the system
 	    administrator.  There are many that are standardized in
 	    the <ulink
-	      url="http://svn.FreeBSD.org/ports/head/KNOBS?view=markup"><filename>ports/KNOBS</filename></ulink>
+	      url="http://svnweb.FreeBSD.org/ports/head/KNOBS?view=markup"><filename>ports/KNOBS</filename></ulink>
 	    file.</para>
 
 	  <para>When creating a port, do not make knob names specific
 	    to a given application.  For example in Avahi port, use
 	    <makevar>WITHOUT_MDNS</makevar> instead of
 	    <makevar>WITHOUT_AVAHI_MDNS</makevar>.</para>
 
 	  <note>
 	    <para>You should not assume that a
 	      <makevar>WITH_<replaceable>*</replaceable></makevar>
 	      necessarily has a corresponding
 	      <makevar>WITHOUT_<replaceable>*</replaceable></makevar>
 	      variable and vice versa.  In general, the default is
 	      simply assumed.</para>
 	  </note>
 
 	  <note>
 	    <para>Unless otherwise specified, these variables are only
 	      tested for being set or not set, rather than being set
 	      to a specific value such as <literal>YES</literal>
 	      or <literal>NO</literal>.</para>
 	  </note>
 
 	  <table frame="none">
 	    <title>Common
 	      <makevar>WITH_<replaceable>*</replaceable></makevar> and
 	      <makevar>WITHOUT_<replaceable>*</replaceable></makevar>
 	      Variables</title>
 
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>Variable</entry>
 		  <entry>Means</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row id="knobs-without-nls">
 		  <entry><makevar>WITHOUT_NLS</makevar></entry>
 		  <entry>If set, says that internationalization is not
 		    needed, which can save compile time.  By default,
 		    internationalization is used.</entry>
 		</row>
 
 		<row>
 		  <entry><makevar>WITH_OPENSSL_BASE</makevar></entry>
 		  <entry>Use the version of OpenSSL in the base
 		    system.</entry>
 		</row>
 
 		<row>
 		  <entry><makevar>WITH_OPENSSL_PORT</makevar></entry>
 		  <entry>Installs the version of OpenSSL from
 		    <filename
 		      role="package">security/openssl</filename>, even
 		    if the base is up to date.</entry>
 		</row>
 
 		<row>
 		  <entry><makevar>WITHOUT_X11</makevar></entry>
 		  <entry>Ports that can be built both with and
 		    without X support are normally
 		    built with X support.  If this variable is
 		    defined, then the version that does not have X
 		    support will be built instead.</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </table>
 	</sect3>
 
 	<sect3>
 	  <title>Knob Naming</title>
 
 	  <para>Porters should use like-named knobs, both
 	    for the benefit of end-users and to help keep the number
 	    of knob names down.  A list of popular knob names can be
 	    found in the <ulink
-	      url="http://svn.FreeBSD.org/ports/head/KNOBS?view=markup"><filename>KNOBS</filename></ulink>
+	      url="http://svnweb.FreeBSD.org/ports/head/KNOBS?view=markup"><filename>KNOBS</filename></ulink>
 	    file.</para>
 
 	  <para>Knob names should reflect what the knob is and does.
 	    When a port has a lib-prefix in the
 	    <makevar>PORTNAME</makevar> the lib-prefix should be
 	    dropped in knob naming.</para>
 	</sect3>
       </sect2>
 
       <sect2>
 	<title><makevar>OPTIONS</makevar></title>
 
 	<sect3>
 	  <title>Background</title>
 
 	  <para>The <makevar>OPTIONS_*</makevar> variables give the
 	    user installing the port a dialog showing the available
 	    options, and then saves those options to
 	    <filename>/var/db/ports/<makevar>${UNIQUENAME}</makevar>/options</filename>.
 	    The next time the port is built, the options are
 	    reused.</para>
 
 	  <para>When the user runs <command>make config</command> (or
 	    runs <command>make build</command> for the first time),
 	    the framework checks for
 	    <filename>/var/db/ports/<makevar>${UNIQUENAME}</makevar>/options</filename>.
 	    If that file does not exist, the values of
 	    <makevar>OPTIONS_*</makevar> are used, and a dialog box is
 	    displayed where the options can be enabled or disabled.
 	    Then the <filename>options</filename> file is saved and
 	    the configured variables are used when building the
 	    port.</para>
 
 	  <para>If a new version of the port adds new
 	    <makevar>OPTIONS</makevar>, the dialog will be presented
 	    to the user with the saved values of old
 	    <makevar>OPTIONS</makevar> prefilled.</para>
 
 	  <para><command>make showconfig</command> shows the
 	    saved configuration.  Use <command>make rmconfig</command>
 	    to remove the saved configuration.</para>
 	</sect3>
 
 	<sect3>
 	  <title>Syntax</title>
 
 	  <para><makevar>OPTIONS_DEFINE</makevar> contains a list of
 	    <makevar>OPTIONS</makevar> to be used.  These are
 	    independent of each other and are not grouped:</para>
 
 	  <programlisting>OPTIONS_DEFINE=	OPT1 OPT2</programlisting>
 
 	  <para>Once defined, <makevar>OPTIONS</makevar> are
 	    described (optional, but strongly recommended):</para>
 
 	  <programlisting>OPT1_DESC=	Describe OPT1
 OPT2_DESC=	Describe OPT2
 OPT3_DESC=	Describe OPT3
 OPT4_DESC=	Describe OPT4
 OPT5_DESC=	Describe OPT5
 OPT6_DESC=	Describe OPT6</programlisting>
 
 	  <tip>
 	    <para><filename>ports/Mk/bsd.options.desc.mk</filename>
 	      has descriptions for many common
 	      <makevar>OPTIONS</makevar>; there is usually no need
 	      to override these.</para>
 	  </tip>
 
 	  <tip>
 	    <para>When describing options, view it from the
 	      perspective of the user: <quote>What does it do?</quote>
 	      and <quote>Why would I want to enable this?</quote>  Do
 	      not just repeat the name.  For example, describing the
 	      <literal>NLS</literal> option as
 	      <quote>include NLS support</quote> does not help the
 	      user, who can already see the option name but may not
 	      know what it means.  Describing it as <quote>Native
 		Language Support via gettext utilities</quote> is
 	      much more helpful.</para>
 	  </tip>
 
 	  <para><makevar>OPTIONS</makevar> can be grouped as radio
 	    choices, where only one choice from each group is
 	    allowed:</para>
 
 	  <programlisting>OPTIONS_SINGLE=		SG1
 OPTIONS_SINGLE_SG1=	OPT3 OPT4</programlisting>
 
 	  <para><makevar>OPTIONS</makevar> can be grouped as radio
 	    choices, where none or only one choice from each group
 	    is allowed:</para>
 
 	  <programlisting>OPTIONS_RADIO=		RG1
 OPTIONS_RADIO_RG1=	OPT7 OPT8</programlisting>
 
 	  <para><makevar>OPTIONS</makevar> can also be grouped as
 	    <quote>multiple-choice</quote> lists, where
 	    <emphasis>at least one</emphasis> option must be
 	    enabled:</para>
 
 	  <programlisting>OPTIONS_MULTI=		MG1
 OPTIONS_MULTI_MG1=	OPT5 OPT6</programlisting>
 
 	  <para><makevar>OPTIONS</makevar> can also be grouped as
 	    <quote>multiple-choice</quote> lists, where none or any
 	    option can be enabled:</para>
 
 	  <programlisting>OPTIONS_GROUP=		GG1
 OPTIONS_GROUP_GG1=	OPT9 OPT10</programlisting>
 
 	  <para><makevar>OPTIONS</makevar> are unset by default,
 	    unless they are listed in
 	    <makevar>OPTIONS_DEFAULT</makevar>:</para>
 
 	  <programlisting>OPTIONS_DEFAULT=	OPT1 OPT3 OPT6</programlisting>
 
 	  <para><makevar>OPTIONS</makevar> definitions must appear
 	    before the inclusion of
 	    <filename>bsd.port.options.mk</filename>.  The
 	    <makevar>PORT_OPTIONS</makevar> variable can only be
 	    tested after the inclusion of
 	    <filename>bsd.port.options.mk</filename>.  Inclusion of
 	    <filename>bsd.port.pre.mk</filename> can be used instead,
 	    too, and is still widely used in ports written before the
 	    introduction of <filename>bsd.port.options.mk</filename>.
 	    But be aware that some variables will not work as expected
 	    after the inclusion of
 	    <filename>bsd.port.pre.mk</filename>, typically some
 	    <makevar>USE_*</makevar> flags.</para>
 
 	  <example id="ports-options-simple-use">
 	    <title>Simple Use of <makevar>OPTIONS</makevar></title>
 
 	    <programlisting>OPTIONS_DEFINE=	FOO BAR
 FOO_DESC=	Enable option foo
 BAR_DESC=	Support feature bar
 
 OPTIONS_DEFAULT=FOO
 
 .include &lt;bsd.port.options.mk&gt;
 
 .if ${PORT_OPTIONS:MFOO}
 CONFIGURE_ARGS+=--with-foo
 .else
 CONFIGURE_ARGS+=--without-foo
 .endif
 
 .if ${PORT_OPTIONS:MBAR}
 RUN_DEPENDS+=	bar:${PORTSDIR}/bar/bar
 .endif
 
 .include &lt;bsd.port.mk&gt;</programlisting>
 	  </example>
 
 	  <example id ="ports-options-check-unset">
 	    <title>Check for Unset Port
 	      <makevar>OPTIONS</makevar></title>
 
 	    <programlisting>.if ! ${PORT_OPTIONS:MEXAMPLES}
 CONFIGURE_ARGS+=--without-examples
 .endif</programlisting>
 	  </example>
 
 	  <example id="ports-options-practical-use">
 	    <title>Practical Use of <makevar>OPTIONS</makevar></title>
 
 	    <programlisting>OPTIONS_DEFINE=		EXAMPLES
 
 OPTIONS_SINGLE=		BACKEND
 OPTIONS_SINGLE_BACKEND=	MYSQL PGSQL BDB
 
 OPTIONS_MULTI=		AUTH
 OPTIONS_MULTI_AUTH=	LDAP PAM SSL
 
 EXAMPLES_DESC=		Install extra examples
 MYSQL_DESC=		Use MySQL as backend
 PGSQL_DESC=		Use PostgreSQL as backend
 BDB_DESC=		Use Berkeley DB as backend
 LDAP_DESC=		Build with LDAP authentication support
 PAM_DESC=		Build with PAM support
 SSL_DESC=		Build with OpenSSL support
 
 OPTIONS_DEFAULT=	PGSQL LDAP SSL
 
 .include &lt;bsd.port.options.mk&gt;
 
 .if ${PORT_OPTIONS:MPGSQL}
 USE_PGSQL=		yes
 CONFIGURE_ARGS+=	--with-postgres
 .else
 CONFIGURE_ARGS+=	--without-postgres
 .endif
 
 .if ${PORT_OPTIONS:MICU}
 LIB_DEPENDS+=	icuuc:${PORTSDIR}/devel/icu
 .endif
 
 .if ! ${PORT_OPTIONS:MEXAMPLES}
 CONFIGURE_ARGS+=	--without-examples
 .endif
 
 # Check other OPTIONS
 
 .include &lt;bsd.port.mk&gt;</programlisting>
 	  </example>
 
 	</sect3>
 
 	<sect3>
 	  <title>Default Options</title>
 
 	  <para>The following options are always on by default.</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para><literal>DOCS</literal> &mdash; build and install
 		documentation.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><literal>NLS</literal> &mdash; Native Language
 		Support.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><literal>EXAMPLES</literal> &mdash; build and
 		install examples.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><literal>IPV6</literal> &mdash; IPv6 protocol
 		support.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <note>
 	    <para>There is no need to add these to
 	      <makevar>OPTIONS_DEFAULT</makevar>.  To have them show
 	      up in the options selection dialog, however, they must
 	      be added to <makevar>OPTIONS_DEFINE</makevar>.</para>
 	  </note>
 	</sect3>
       </sect2>
 
       <sect2>
 	<title>Feature Auto-Activation</title>
 
 	<para>When using a GNU configure script, keep an eye on which
 	  optional features are activated by auto-detection.
 	  Explicitly disable optional features you do not wish to be
 	  used by passing respective <literal>--without-xxx</literal>
 	  or <literal>--disable-xxx</literal> in
 	  <makevar>CONFIGURE_ARGS</makevar>.</para>
 
 	<example>
 	  <title>Wrong Handling of an Option</title>
 
 	  <programlisting>.if ${PORT_OPTIONS:MFOO}
 LIB_DEPENDS+=		foo:${PORTSDIR}/devel/foo
 CONFIGURE_ARGS+=	--enable-foo
 .endif</programlisting>
 	</example>
 
 	<para>In the example above, imagine a library libfoo is
 	  installed on the system.  The user does not want this
 	  application to use libfoo, so he toggled the option off in
 	  the <literal>make config</literal> dialog.  But the
 	  application's configure script detects the library present
 	  in the system and includes its support in the resulting
 	  executable.  Now when the user decides to remove libfoo from
 	  the system, the ports system does not protest (no dependency
 	  on libfoo was recorded) but the application breaks.</para>
 
 	<example>
 	  <title>Correct Handling of an Option</title>
 
 	  <programlisting>.if ${PORT_OPTIONS:MFOO}
 LIB_DEPENDS+=		foo:${PORTSDIR}/devel/foo
 CONFIGURE_ARGS+=	--enable-foo
 .else
 CONFIGURE_ARGS+=	--disable-foo
 .endif</programlisting>
 	</example>
 
 	<para>In the second example, the library libfoo is explicitly
 	  disabled.  The configure script does not enable related
 	  features in the application, despite library's presence in
 	  the system.</para>
 
 	<note>
 	  <para>Under some circumstances, the shorthand conditional
 	    syntax can cause problems with complex constructs.
 	    If you receive errors such as <literal>Malformed
 	      conditional</literal>, an alternative syntax can be
 	    used.</para>
 	  <programlisting>.if !empty(VARIABLE:MVALUE)
 # as an alternative to
 .if ${VARIABLE:MVALUE}</programlisting>
 	</note>
       </sect2>
     </sect1>
 
     <sect1 id="makefile-wrkdir">
       <title>Specifying the Working Directory</title>
 
       <para>Each port is extracted in to a working directory, which
 	must be writable.  The ports system defaults to having the
 	<makevar>DISTFILES</makevar> unpack in to a directory called
 	<literal>${DISTNAME}</literal>.  In other words, if you have
 	set:</para>
 
       <programlisting>PORTNAME=	foo
 PORTVERSION=	1.0</programlisting>
 
       <para>then the port's distribution files contain a top-level
 	directory, <filename>foo-1.0</filename>, and the rest of the
 	files are located under that directory.</para>
 
       <para>There are a number of variables you can override if that
 	is not the case.</para>
 
       <sect2>
 	<title><makevar>WRKSRC</makevar></title>
 
 	<para>The variable lists the name of the directory that is
 	  created when the application's distfiles are extracted.  If
 	  our previous example extracted into a directory called
 	  <filename>foo</filename> (and not
 	  <filename>foo-1.0</filename>) you would write:</para>
 
 	<programlisting>WRKSRC=	${WRKDIR}/foo</programlisting>
 
 	<para>or possibly</para>
 
 	<programlisting>WRKSRC=	${WRKDIR}/${PORTNAME}</programlisting>
       </sect2>
 
       <sect2>
 	<title><makevar>NO_WRKSUBDIR</makevar></title>
 
 	<para>If the port does not extract in to a subdirectory at all
 	  then you should set <makevar>NO_WRKSUBDIR</makevar> to
 	  indicate that.</para>
 
 	<programlisting>NO_WRKSUBDIR=	yes</programlisting>
       </sect2>
     </sect1>
 
     <sect1 id="conflicts">
       <title>Conflict Handling</title>
 
       <para>There are three different variables to register a conflict
 	between packages and ports: <makevar>CONFLICTS</makevar>,
 	<makevar>CONFLICTS_INSTALL</makevar> and
 	<makevar>CONFLICTS_BUILD</makevar>.</para>
 
       <note>
 	<para>The conflict variables automatically set the variable
 	  <makevar>IGNORE</makevar>, which is more fully documented
 	  in <xref linkend="dads-noinstall"/>.</para>
       </note>
 
       <para>When removing one of several conflicting ports, it is
 	advisable to retain the <makevar>CONFLICTS</makevar> entries
 	in those other ports for a few months to cater for users who
 	only update once in a while.</para>
 
       <sect2>
 	<title><makevar>CONFLICTS_INSTALL</makevar></title>
 
 	<para>If your package cannot coexist with other packages
 	  (because of file conflicts, runtime incompatibilities,
 	  etc.), list the other package names in the
 	  <makevar>CONFLICTS_INSTALL</makevar> variable.  You can use
 	  shell globs like <literal>*</literal> and
 	  <literal>?</literal> here.  Package names should be
 	  enumerated the same way they appear in
 	  <filename>/var/db/pkg</filename>.  Please make sure that
 	  <makevar>CONFLICTS_INSTALL</makevar> does not match this
 	  port's package itself.  Otherwise enforcing its installation
 	  with <makevar>FORCE_PKG_REGISTER</makevar> will no longer
 	  work.  The CONFLICTS_INSTALL check is done after the build
 	  stage and prior to the install stage.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>CONFLICTS_BUILD</makevar></title>
 
 	<para>If your port cannot be built if a certain port is
 	  already installed, list the other port names in the
 	  <makevar>CONFLICTS_BUILD</makevar> variable.  You can use
 	  shell globs like <literal>*</literal> and
 	  <literal>?</literal> here.  Package names should be
 	  enumerated the same way they appear in
 	  <filename>/var/db/pkg</filename>.  The CONFLICTS_BUILD check
 	  is done prior to the build stage.  Build conflicts are not
 	  recorded in the resulting package.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>CONFLICTS</makevar></title>
 
 	<para>If your port cannot be built if a certain port is
 	  already installed and the resulting package cannot coexist
 	  with the other package, list the other package name in the
 	  <makevar>CONFLICTS</makevar> variable.  You can use shell
 	  globs like <literal>*</literal> and <literal>?</literal>
 	  here.  Packages names should be enumerated the same way they
 	  appear in <filename>/var/db/pkg</filename>.  Please make
 	  sure that <makevar>CONFLICTS_INSTALL</makevar> does not
 	  match this port's package itself.  Otherwise enforcing its
 	  installation with <makevar>FORCE_PKG_REGISTER</makevar> will
 	  no longer work.  The CONFLICTS check is done prior to the
 	  build stage and prior to the install stage.</para>
       </sect2>
     </sect1>
 
     <sect1 id="install">
       <title>Installing Files</title>
 
       <sect2 id="install-macros">
 	<title><makevar>INSTALL_*</makevar> Macros</title>
 
 	<para>Do use the macros provided in
 	  <filename>bsd.port.mk</filename> to ensure correct modes and
 	  ownership of files in your own
 	  <maketarget>*-install</maketarget> targets.</para>
 
 	<itemizedlist>
 	  <listitem>
 
 	    <para><makevar>INSTALL_PROGRAM</makevar> is a command to
 	      install binary executables.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>INSTALL_SCRIPT</makevar> is a command to
 	      install executable scripts.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>INSTALL_LIB</makevar> is a command to
 	      install shared libraries.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>INSTALL_KLD</makevar> is a command to
 	      install kernel loadable modules.  Some architectures
 	      do not like having the modules stripped, so
 	      use this command instead of
 	      <makevar>INSTALL_PROGRAM</makevar>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>INSTALL_DATA</makevar> is a command to
 	      install sharable data.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>INSTALL_MAN</makevar> is a command to
 	      install manpages and other documentation (it does not
 	      compress anything).</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>These are basically the <command>install</command>
 	  command with all the appropriate flags.</para>
       </sect2>
 
       <sect2 id="install-strip">
 	<title>Stripping Binaries and Shared Libraries</title>
 
 	<para>Do not strip binaries manually unless you have to.  All
 	  binaries should be stripped, but the
 	  <makevar>INSTALL_PROGRAM</makevar> macro will install and
 	  strip a binary at the same time (see the next section).  The
 	  <makevar>INSTALL_LIB</makevar> macro does the same thing to
 	  shared libraries.</para>
 
 	<para>If you need to strip a file, but wish to use neither
 	  <makevar>INSTALL_PROGRAM</makevar> nor
 	  <makevar>INSTALL_LIB</makevar> macros,
 	  <makevar>${STRIP_CMD}</makevar> will strip your program or
 	  shared library.  This is typically done within the
 	  <maketarget>post-install</maketarget> target.  For
 	  example:</para>
 
 	<programlisting>post-install:
 	${STRIP_CMD} ${PREFIX}/bin/xdl</programlisting>
 
 	<para>Use the &man.file.1; command on the installed executable
 	  to check whether the binary is stripped or not.  If it does
 	  not say <literal>not stripped</literal>, it is stripped.
 	  Additionally, &man.strip.1; will not strip a previously
 	  stripped program; it will instead exit cleanly.</para>
       </sect2>
 
       <sect2 id="install-copytree">
 	<title>Installing a Whole Tree of Files</title>
 
 	<para>Sometimes, there is a need to install a big number of
 	  files, preserving their hierarchical organization, i.e.,
 	  copying over a whole directory tree from
 	  <makevar>WRKSRC</makevar> to a target directory under
 	  <makevar>PREFIX</makevar>.</para>
 
 	<para>Two macros exist for this situation.  The advantage of
 	  using these macros instead of <command>cp</command> is that
 	  they guarantee proper file ownership and permissions on
 	  target files.  The first macro,
 	  <makevar>COPYTREE_BIN</makevar>, will set all the installed
 	  files to be executable, thus being suitable for installing
 	  into <filename><makevar>PREFIX</makevar>/bin</filename>.
 	  The second macro, <makevar>COPYTREE_SHARE</makevar>, does
 	  not set executable permissions on files, and is therefore
 	  suitable for installing files under
 	  <filename><makevar>PREFIX</makevar>/share</filename>
 	  target.</para>
 
 	<programlisting>post-install:
 	${MKDIR} ${EXAMPLESDIR}
 	(cd ${WRKSRC}/examples &amp;&amp; ${COPYTREE_SHARE} . ${EXAMPLESDIR})</programlisting>
 
 	<para>This example will install the contents of
 	  <filename>examples</filename> directory in the vendor
 	  distfile to the proper examples location of your
 	  port.</para>
 
 	<programlisting>post-install:
 	${MKDIR} ${DATADIR}/summer
 	(cd ${WRKSRC}/temperatures &amp;&amp; ${COPYTREE_SHARE} "June July August" ${DATADIR}/summer)</programlisting>
 
 	<para>And this example will install the data of summer months
 	  to the <filename>summer</filename> subdirectory of a
 	  <filename><makevar>DATADIR</makevar></filename>.</para>
 
 	<para>Additional <command>find</command> arguments can be
 	  passed via the third argument to the
 	  <makevar>COPYTREE_*</makevar> macros.  For example, to
 	  install all files from the first example except Makefiles,
 	  one can use the following command.</para>
 
 	<programlisting>post-install:
 	${MKDIR} ${EXAMPLESDIR}
 	(cd ${WRKSRC}/examples &amp;&amp; \
 		${COPYTREE_SHARE} . ${EXAMPLESDIR} "! -name Makefile")</programlisting>
 
 	<para>Note that these macros does not add the installed files
 	  to <filename>pkg-plist</filename>.  You still need to list
 	  them.</para>
       </sect2>
 
       <sect2 id="install-documentation">
 	<title>Install Additional Documentation</title>
 
 	<para>If your software has some documentation other than the
 	  standard man and info pages that you think is useful for the
 	  user, install it under
 	  <filename><makevar>PREFIX</makevar>/share/doc</filename>.
 	  This can be done, like the previous item, in the
 	  <maketarget>post-install</maketarget> target.</para>
 
 	<para>Create a new directory for your port.  The directory
 	  name should reflect what the port is.  This usually means
 	  <makevar>PORTNAME</makevar>.  However, if you think the user
 	  might want different versions of the port to be installed at
 	  the same time, you can use the whole
 	  <makevar>PKGNAME</makevar>.</para>
 
 	<para>Make the installation dependent on the variable
 	  <literal>DOCS</literal> option so that users can disable it
 	  in <filename>/etc/make.conf</filename>, like this:</para>
 
 	<programlisting>post-install:
 .if ${PORT_OPTIONS:MDOCS}
 	${MKDIR} ${DOCSDIR}
 	${INSTALL_MAN} ${WRKSRC}/docs/xvdocs.ps ${DOCSDIR}
 .endif</programlisting>
 
 	<para>Here are some handy variables and how they are expanded
 	  by default when used in the
 	  <filename>Makefile</filename>:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para><makevar>DATADIR</makevar> gets expanded to
 	      <filename><makevar>PREFIX</makevar>/share/<makevar>PORTNAME</makevar></filename>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>DATADIR_REL</makevar> gets expanded to
 	      <filename>share/<makevar>PORTNAME</makevar></filename>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>DOCSDIR</makevar> gets expanded to
 	      <filename><makevar>PREFIX</makevar>/share/doc/<makevar>PORTNAME</makevar></filename>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>DOCSDIR_REL</makevar> gets expanded to
 	      <filename>share/doc/<makevar>PORTNAME</makevar></filename>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>EXAMPLESDIR</makevar> gets expanded to
 	      <filename><makevar>PREFIX</makevar>/share/examples/<makevar>PORTNAME</makevar></filename>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>EXAMPLESDIR_REL</makevar> gets expanded to
 	      <filename>share/examples/<makevar>PORTNAME</makevar></filename>.</para>
 	  </listitem>
 	</itemizedlist>
 
 	<note>
 	  <para>The <literal>DOCS</literal> option only controls
 	    additional documentation installed in
 	    <makevar>DOCSDIR</makevar>.  It does not apply to standard
 	    man pages and info pages.  Things installed in
 	    <makevar>DATADIR</makevar> and
 	    <makevar>EXAMPLESDIR</makevar> are controlled by
 	    <literal>DATA</literal> and <literal>EXAMPLES</literal>
 	    options, respectively.</para>
 	</note>
 
 	<para>These variables are exported to
 	  <makevar>PLIST_SUB</makevar>.  Their values will appear
 	  there as pathnames relative to
 	  <filename><makevar>PREFIX</makevar></filename> if possible.
 	  That is,
 	  <filename>share/doc/<makevar>PORTNAME</makevar></filename>
 	  will be substituted for <literal>%%DOCSDIR%%</literal> in
 	  the packing list by default, and so on.  (See more on
 	  <filename>pkg-plist</filename> substitution <link
 	    linkend="plist-sub">here</link>.)</para>
 
 	<para>All conditionally installed documentation files and
 	  directories should be included in
 	  <filename>pkg-plist</filename> with the
 	  <literal>%%PORTDOCS%%</literal> prefix, for example:</para>
 
 	<programlisting>%%PORTDOCS%%%%DOCSDIR%%/AUTHORS
 %%PORTDOCS%%%%DOCSDIR%%/CONTACT
 %%PORTDOCS%%@dirrm %%DOCSDIR%%</programlisting>
 
 	<para>As an alternative to enumerating the documentation files
 	  in <filename>pkg-plist</filename>, a port can set the
 	  variable <makevar>PORTDOCS</makevar> to a list of file names
 	  and shell glob patterns to add to the final packing list.
 	  The names will be relative to <makevar>DOCSDIR</makevar>.
 	  Therefore, a port that utilizes <makevar>PORTDOCS</makevar>
 	  and uses a non-default location for its documentation should
 	  set <makevar>DOCSDIR</makevar> accordingly.  If a directory
 	  is listed in <makevar>PORTDOCS</makevar> or matched by a
 	  glob pattern from this variable, the entire subtree of
 	  contained files and directories will be registered in the
 	  final packing list.  If the <literal>DOCS</literal> option
 	  has been unset then files and directories listed in
 	  <makevar>PORTDOCS</makevar> would not be installed or added
 	  to port packing list.  Installing the documentation at
 	  <makevar>PORTDOCS</makevar> as shown above remains up to the
 	  port itself.  A typical example of utilizing
 	  <makevar>PORTDOCS</makevar> looks as follows:</para>
 
 	<programlisting>PORTDOCS=	README.* ChangeLog docs/*</programlisting>
 
 	<note>
 	  <para>The equivalents of <makevar>PORTDOCS</makevar> for
 	    files installed under <makevar>DATADIR</makevar> and
 	    <makevar>EXAMPLESDIR</makevar> are
 	    <makevar>PORTDATA</makevar> and
 	    <makevar>PORTEXAMPLES</makevar>, respectively.</para>
 
 	  <para>You can also use the <filename>pkg-message</filename>
 	    file to display messages upon installation.  See <link
 	      linkend="porting-message">the section on using
 	    <filename>pkg-message</filename></link> for details.  The
 	    <filename>pkg-message</filename> file does not need to be
 	    added to <filename>pkg-plist</filename>.</para>
 	</note>
       </sect2>
 
       <sect2 id="install-subdirs">
 	<title>Subdirectories Under <makevar>PREFIX</makevar></title>
 
 	<para>Try to let the port put things in the right
 	  subdirectories of <makevar>PREFIX</makevar>.  Some ports
 	  lump everything and put it in the subdirectory with the
 	  port's name, which is incorrect.  Also, many ports put
 	  everything except binaries, header files and manual pages in
 	  a subdirectory of <filename>lib</filename>, which does not
 	  work well with the BSD paradigm.  Many of the files should
 	  be moved to one of the following: <filename>etc</filename>
 	  (setup/configuration files), <filename>libexec</filename>
 	  (executables started internally), <filename>sbin</filename>
 	  (executables for superusers/managers),
 	  <filename>info</filename> (documentation for info browser)
 	  or <filename>share</filename> (architecture independent
 	  files).  See &man.hier.7; for details; the rules governing
 	  <filename>/usr</filename> pretty much apply to
 	  <filename>/usr/local</filename> too.  The exception are
 	  ports dealing with USENET <quote>news</quote>.  They may use
 	  <filename><makevar>PREFIX</makevar>/news</filename> as a
 	  destination for their files.</para>
       </sect2>
     </sect1>
   </chapter>
 
   <chapter id="special">
     <title>Special Considerations</title>
 
     <para>There are some more things you have to take into account
       when you create a port.  This section explains the most common
       of those.</para>
 
     <sect1 id="porting-shlibs">
       <title>Shared Libraries</title>
 
       <para>If your port installs one or more shared libraries, define
 	a <makevar>USE_LDCONFIG</makevar> make variable, which will
 	instruct a <filename>bsd.port.mk</filename> to run
 	<literal>&dollar;{LDCONFIG} -m</literal> on the directory
 	where the new library is installed (usually
 	<filename><makevar>PREFIX</makevar>/lib</filename>) during
 	<maketarget>post-install</maketarget> target to register it
 	into the shared library cache.  This variable, when defined,
 	will also facilitate addition of an appropriate
 	<literal>@exec /sbin/ldconfig -m</literal> and
 	<literal>@unexec /sbin/ldconfig -R</literal> pair into your
 	<filename>pkg-plist</filename> file, so that a user who
 	installed the package can start using the shared library
 	immediately and de-installation will not cause the system to
 	still believe the library is there.</para>
 
       <programlisting>USE_LDCONFIG=	yes</programlisting>
 
       <para>If you need, you can override the default directory by
 	setting the <makevar>USE_LDCONFIG</makevar> value to a list of
 	directories into which shared libraries are to be installed.
 	For example if your port installs shared libraries into
 	<filename><makevar>PREFIX</makevar>/lib/foo</filename> and
 	<filename><makevar>PREFIX</makevar>/lib/bar</filename>
 	directories you could use the following in your
 	<filename>Makefile</filename>:</para>
 
       <programlisting>USE_LDCONFIG=	${PREFIX}/lib/foo ${PREFIX}/lib/bar</programlisting>
 
       <para>Please double-check, often this is not necessary at all or
 	can be avoided through <literal>-rpath</literal> or setting
 	<envar>LD_RUN_PATH</envar> during linking (see <filename
 	  role="package">lang/moscow_ml</filename> for an example), or
 	through a shell-wrapper which sets
 	<makevar>LD_LIBRARY_PATH</makevar> before invoking the binary,
 	like <filename role="package">www/seamonkey</filename>
 	does.</para>
 
       <para>When installing 32-bit libraries on 64-bit system, use
 	<makevar>USE_LDCONFIG32</makevar> instead.</para>
 
       <para>Try to keep shared library version numbers in the
 	<filename>libfoo.so.0</filename> format.  Our runtime linker
 	only cares for the major (first) number.</para>
 
       <para>When the major library version number increments in the
 	update to the new port version, all other ports that link to
 	the affected library should have their
 	<makevar>PORTREVISION</makevar> incremented, to force
 	recompilation with the new library version.</para>
     </sect1>
 
     <sect1 id="porting-restrictions">
       <title>Ports with Distribution Restrictions</title>
 
       <para>Licenses vary, and some of them place restrictions on how
 	the application can be packaged, whether it can be sold for
 	profit, and so on.</para>
 
       <important>
 	<para>It is your responsibility as a porter to read the
 	  licensing terms of the software and make sure that the
 	  FreeBSD project will not be held accountable for violating
 	  them by redistributing the source or compiled binaries
 	  either via FTP/HTTP or CD-ROM.  If in doubt, please contact
 	  the &a.ports;.</para>
       </important>
 
       <para>In situations like this, the variables described in the
 	following sections can be set.</para>
 
       <sect2>
 	<title><makevar>NO_PACKAGE</makevar></title>
 
 	<para>This variable indicates that we may not generate a
 	  binary package of the application.  For instance, the
 	  license may disallow binary redistribution, or it may
 	  prohibit distribution of packages created from patched
 	  sources.</para>
 
 	<para>However, the port's <makevar>DISTFILES</makevar> may be
 	  freely mirrored on FTP/HTTP.  They may also be distributed
 	  on a CD-ROM (or similar media) unless
 	  <makevar>NO_CDROM</makevar> is set as well.</para>
 
 	<para><makevar>NO_PACKAGE</makevar> should also be used if the
 	  binary package is not generally useful, and the application
 	  should always be compiled from the source code.  For
 	  example, if the application has configuration information
 	  that is site specific hard coded in to it at compile time,
 	  set <makevar>NO_PACKAGE</makevar>.</para>
 
 	<para><makevar>NO_PACKAGE</makevar> should be set to a string
 	  describing the reason why the package should not be
 	  generated.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>NO_CDROM</makevar></title>
 
 	<para>This variable alone indicates that, although we are
 	  allowed to generate binary packages, we may put neither
 	  those packages nor the port's <makevar>DISTFILES</makevar>
 	  onto a CD-ROM (or similar media) for resale.  However, the
 	  binary packages and the port's <makevar>DISTFILES</makevar>
 	  will still be available via FTP/HTTP.</para>
 
 	<para> If this variable is set along with
 	  <makevar>NO_PACKAGE</makevar>, then only the port's
 	  <makevar>DISTFILES</makevar> will be available, and only via
 	  FTP/HTTP.</para>
 
 	<para><makevar>NO_CDROM</makevar> should be set to a string
 	  describing the reason why the port cannot be redistributed
 	  on CD-ROM.  For instance, this should be used if the port's
 	  license is for <quote>non-commercial</quote> use
 	  only.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>NOFETCHFILES</makevar></title>
 
 	<para>Files defined in the <makevar>NOFETCHFILES</makevar>
 	  variable are not fetchable from any of the
 	  <makevar>MASTER_SITES</makevar>.  An example of such a file
 	  is when the file is supplied on CD-ROM by the vendor.</para>
 
 	<para>Tools which check for the availability of these files
 	  on the <makevar>MASTER_SITES</makevar> should ignore these
 	  files and not report about them.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>RESTRICTED</makevar></title>
 
 	<para>Set this variable alone if the application's license
 	  permits neither mirroring the application's
 	  <makevar>DISTFILES</makevar> nor distributing the binary
 	  package in any way.</para>
 
 	<para><makevar>NO_CDROM</makevar> or
 	  <makevar>NO_PACKAGE</makevar> should not be set along with
 	  <makevar>RESTRICTED</makevar> since the latter variable
 	  implies the former ones.</para>
 
 	<para><makevar>RESTRICTED</makevar> should be set to a string
 	  describing the reason why the port cannot be redistributed.
 	  Typically, this indicates that the port contains proprietary
 	  software and that the user will need to manually download
 	  the <makevar>DISTFILES</makevar>, possibly after registering
 	  for the software or agreeing to accept the terms of an
 	  <acronym>EULA</acronym>.</para>
       </sect2>
 
       <sect2>
 	<title><makevar>RESTRICTED_FILES</makevar></title>
 
 	<para>When <makevar>RESTRICTED</makevar> or
 	  <makevar>NO_CDROM</makevar> is set, this variable defaults
 	  to <literal>${DISTFILES} ${PATCHFILES}</literal>, otherwise
 	  it is empty.  If only some of the distribution files are
 	  restricted, then set this variable to list them.</para>
 
 	<para>Note that the port committer should add an entry to
 	  <filename>/usr/ports/LEGAL</filename> for every listed
 	  distribution file, describing exactly what the restriction
 	  entails.</para>
       </sect2>
 
       <sect2>
 	<title>Examples</title>
 
 	<para>The preferred way to state "the distfiles for this port
 	  must be fetched manually" is as follows:</para>
 
 	<programlisting>.if !exists(${DISTDIR}/${DISTNAME}${EXTRACT_SUFX})
 IGNORE=	may not be redistributed because of licensing reasons. Please visit <replaceable>some-website</replaceable> to accept their license and download ${DISTFILES} into ${DISTDIR}
 .endif</programlisting>
 
 	<para>This both informs the user, and sets the proper metadata
 	  on the user's machine for use by automated programs.</para>
 
 	<para>Note that this stanza must be preceded by an inclusion
 	  of <filename>bsd.port.pre.mk</filename>.</para>
       </sect2>
     </sect1>
 
     <sect1 id="building">
       <title>Building Mechanisms</title>
 
       <sect2 id="parallel-builds">
 	<title>Building Ports in Parallel</title>
 
 	<para>The &os; ports framework supports parallel building
 	  using multiple <command>make</command> sub-processes, which
 	  allows <acronym>SMP</acronym> systems to utilize all of
 	  their available <acronym>CPU</acronym> power, allowing port
 	  builds to be faster and more effective.</para>
 
 	<para>This is achieved by passing <makevar>-jX</makevar> flag
 	  to &man.make.1; running on vendor code.  Unfortunately, not
 	  all ports handle parallel building well.  Therefore it is
 	  required to explicitly enable this feature by adding
 	  <literal>MAKE_JOBS_SAFE=yes</literal> somewhere below the
 	  dependency declaration section of the
 	  <filename>Makefile</filename>.</para>
 
 	<para>Another option for controlling this feature from the
 	  maintainer's point of view is the
 	  <makevar>MAKE_JOBS_UNSAFE=yes</makevar> variable.  It is
 	  used when a port is known to be broken with
 	  <makevar>-jX</makevar> and a user forces the use of multi
 	  processor compilations for all ports in
 	  <filename>/etc/make.conf</filename> with the
 	  <literal>FORCE_MAKE_JOBS=yes</literal> variable.</para>
       </sect2>
 
       <sect2 id="using-make">
 	<title><command>make</command>, <command>gmake</command>, and
 	  <command>imake</command></title>
 
 	<para>If your port uses <application>GNU make</application>,
 	  set <literal>USE_GMAKE=yes</literal>.</para>
 
 	<table frame="none">
 	  <title>Variables for Ports Related to
 	    <application>gmake</application></title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Means</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_GMAKE</makevar></entry>
 		<entry>The port requires <command>gmake</command> to
 		  build.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>GMAKE</makevar></entry>
 		<entry>The full path for <command>gmake</command> if
 		  it is not in the <envar>PATH</envar>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>If your port is an X application that creates
 	  <filename>Makefile</filename> files from
 	  <filename>Imakefile</filename> files using
 	  <application>imake</application>, then set
 	  <literal>USE_IMAKE=yes</literal>.  This will cause the
 	  configure stage to automatically do an <command>xmkmf
 	    -a</command>.  If the <option>-a</option> flag is a
 	  problem for your port, set <literal>XMKMF=xmkmf</literal>.
 	  If the port uses <application>imake</application> but does
 	  not understand the <maketarget>install.man</maketarget>
 	  target, <literal>NO_INSTALL_MANPAGES=yes</literal> should be
 	  set.</para>
 
 	<para>If your port's source <filename>Makefile</filename> has
 	  something else than <maketarget>all</maketarget> as the main
 	  build target, set <makevar>ALL_TARGET</makevar> accordingly.
 	  Same goes for <maketarget>install</maketarget> and
 	  <makevar>INSTALL_TARGET</makevar>.</para>
       </sect2>
 
       <sect2 id="using-configure">
 	<title><command>configure</command> Script</title>
 
 	<para>If your port uses the <command>configure</command>
 	  script to generate <filename>Makefile</filename> files from
 	  <filename>Makefile.in</filename> files, set
 	  <literal>GNU_CONFIGURE=yes</literal>.  If you want to give
 	  extra arguments to the <command>configure</command> script
 	  (the default argument is <literal>--prefix=&dollar;{PREFIX}
 	    --infodir=&dollar;{PREFIX}/&dollar;{INFO_PATH}
 	    --mandir=&dollar;{MANPREFIX}/man
 	    --build=&dollar;{CONFIGURE_TARGET}</literal>), set those
 	  extra arguments in <makevar>CONFIGURE_ARGS</makevar>.  Extra
 	  environment variables can be passed using
 	  <makevar>CONFIGURE_ENV</makevar> variable.</para>
 
 	<table frame="none">
 	  <title>Variables for Ports That Use
 	    <command>configure</command></title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Means</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>GNU_CONFIGURE</makevar></entry>
 		<entry>The port uses <command>configure</command>
 		  script to prepare build.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>HAS_CONFIGURE</makevar></entry>
 		<entry>Same as <makevar>GNU_CONFIGURE</makevar>,
 		  except default configure target is not added to
 		  <makevar>CONFIGURE_ARGS</makevar>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>CONFIGURE_ARGS</makevar></entry>
 		<entry>Additional arguments passed to
 		  <command>configure</command> script.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>CONFIGURE_ENV</makevar></entry>
 		<entry>Additional environment variables to be set
 		  for <command>configure</command> script run.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>CONFIGURE_TARGET</makevar></entry>
 		<entry>Override default configure target.  Default
 		  value is
 		  <literal>&dollar;{MACHINE_ARCH}-portbld-freebsd&dollar;{OSREL}</literal>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
       </sect2>
 
       <sect2 id="using-cmake">
 	<title>Using <command>cmake</command></title>
 
 	<para>For ports that use <application>CMake</application>,
 	  define <literal>USES= cmake</literal>, or
 	  <literal>USES= cmake:outsource</literal> to build in a
 	  separate directory (see below).</para>
 
 	<table frame="none">
 	  <title>Variables for Ports That Use
 	    <command>cmake</command></title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Means</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>CMAKE_ARGS</makevar></entry>
 		<entry>Port specific <application>CMake</application>
 		  flags to be passed to the <command>cmake</command>
 		  binary.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>CMAKE_BUILD_TYPE</makevar></entry>
 		<entry>Type of build (<application>CMake</application>
 		  predefined build profiles).  Default is
 		  <literal>Release</literal>, or
 		  <literal>Debug</literal> if
 		  <makevar>WITH_DEBUG</makevar> is set.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>CMAKE_ENV</makevar></entry>
 		<entry>Environment variables to be set for
 		  <command>cmake</command> binary.  Default is
 		  <literal>&dollar;{CONFIGURE_ENV}</literal>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>CMAKE_SOURCE_PATH</makevar></entry>
 		<entry>Path to the source directory.  Default is
 		  <literal>&dollar;{WRKSRC}</literal>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para><application>CMake</application> supports the following
 	  build profiles: <literal>Debug</literal>,
 	  <literal>Release</literal>,
 	  <literal>RelWithDebInfo</literal> and
 	  <literal>MinSizeRel</literal>.  <literal>Debug</literal> and
 	  <literal>Release</literal> profiles respect system
 	  <literal>*FLAGS</literal>, <literal>RelWithDebInfo</literal>
 	  and <literal>MinSizeRel</literal> will set
 	  <makevar>CFLAGS</makevar> to <literal>-O2 -g</literal> and
 	  <literal>-Os -DNDEBUG</literal> correspondingly.  The
 	  lower-cased value of <makevar>CMAKE_BUILD_TYPE</makevar> is
 	  exported to the <makevar>PLIST_SUB</makevar> and should be
 	  used if port installs <literal>*.cmake</literal> files
 	  depending on the build type (see <filename
 	    role="package">deskutils/strigi</filename> for an
 	  example).  Please note that some projects may define their
 	  own build profiles and/or force particular build type by
 	  setting <literal>CMAKE_BUILD_TYPE</literal> in
 	  <filename>CMakeLists.txt </filename> files.  In order to
 	  make a port for such a project respect
 	  <makevar>CFLAGS</makevar> and <makevar>WITH_DEBUG</makevar>,
 	  the <literal>CMAKE_BUILD_TYPE</literal> definitions must be
 	  removed from those files.</para>
 
 	<para>Most <application>CMake</application>-based projects
 	  support an out-of-source method of building.  The
 	  out-of-source build for a port can be requested by using the
 	  <literal>:outsource</literal> suffix.  When enabled,
 	  <makevar>CONFIGURE_WRKSRC</makevar>,
 	  <makevar>BUILD_WRKSRC</makevar> and
 	  <makevar>INSTALL_WRKSRC</makevar> will be set to
 	  <literal>&dollar;{WRKDIR}/.build</literal> and this
 	  directory will be used to keep all files generated during
 	  configuration and build stages, leaving the source directory
 	  intact.</para>
 
 	<example id="using-cmake-example">
 	  <title><literal>USES= cmake</literal> Example</title>
 
 	  <para>The following snippet demonstrates the use of
 	    <application>CMake</application> for a port.
 	    <makevar>CMAKE_SOURCE_PATH</makevar> is not usually
 	    required, but can be set when the sources are not located
 	    in the top directory, or if only a subset of the project
 	    is intended to be built by the port.</para>
 
 	  <programlisting>USES=			cmake:outsource
 CMAKE_SOURCE_PATH=	&dollar;{WRKSRC}/subproject</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="using-scons">
 	<title>Using <command>scons</command></title>
 
 	<para>If your port uses <application>SCons</application>,
 	  define <literal>USE_SCONS=yes</literal>.</para>
 
 	<table frame="none">
 	  <title>Variables for Ports That Use
 	    <command>scons</command></title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Means</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>SCONS_ARGS</makevar></entry>
 		<entry>Port specific SCons flags passed to the SCons
 		  environment.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>SCONS_BUILDENV</makevar></entry>
 		<entry>Variables to be set in system
 		  environment.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>SCONS_ENV</makevar></entry>
 		<entry>Variables to be set in SCons
 		  environment.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>SCONS_TARGET</makevar></entry>
 		<entry>Last argument passed to SCons, similar to
 		  <makevar>MAKE_TARGET</makevar>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>To make third party <filename>SConstruct</filename>
 	  respect everything that is passed to SCons in
 	  <makevar>SCONS_ENV</makevar> (that is, most importantly,
 	  <makevar>CC/CXX/CFLAGS/CXXFLAGS</makevar>), patch the
 	  <filename>SConstruct</filename> so build
 	  <literal>Environment</literal> is constructed like
 	  this:</para>
 
 	<programlisting>env = Environment(**ARGUMENTS)</programlisting>
 
 	<para>It may be then modified with
 	  <literal>env.Append</literal> and
 	  <literal>env.Replace</literal>.</para>
       </sect2>
     </sect1>
 
     <sect1 id="using-autotools">
       <title>Using GNU Autotools</title>
 
       <sect2 id="using-autotools-introduction">
 	<title>Introduction</title>
 
 	<para>The various GNU autotools provide an abstraction
 	  mechanism for building a piece of software over a wide
 	  variety of operating systems and machine architectures.
 	  Within the Ports Collection, an individual port can make use
 	  of these tools via a simple construct:</para>
 
 	<programlisting>USE_AUTOTOOLS=	<replaceable>tool</replaceable>:<replaceable>version</replaceable>[:<replaceable>operation</replaceable>] ...</programlisting>
 
 	<para>At the time of writing, <replaceable>tool</replaceable>
 	  can be one of <literal>libtool</literal>,
 	  <literal>libltdl</literal>, <literal>autoconf</literal>,
 	  <literal>autoheader</literal>, <literal>automake</literal>
 	  or <literal>aclocal</literal>.</para>
 
 	<para><replaceable>version</replaceable> specifies the
 	  particular tool revision to be used (see
 	  <literal>devel/{automake,autoconf,libtool}[0-9]+</literal>
 	  for valid versions).</para>
 
 	<para><replaceable>operation</replaceable> is an optional
 	  extension to modify how the tool is used.</para>
 
 	<para>Multiple tools can be specified at once, either by
 	  including them all on a single line, or using the
 	  <literal>+=</literal> Makefile construct.</para>
 
 	<para>Finally, there is the special tool, called
 	  <literal>autotools</literal>, which is a convenience
 	  function to bring in all available versions of the autotools
 	  to allow for cross-development work.  This can also be
 	  accomplished by installing the
 	  <literal>devel/autotools</literal> port.</para>
       </sect2>
 
       <sect2 id="using-libtool">
 	<title><command>libtool</command></title>
 
 	<para>Shared libraries using the GNU building framework
 	  usually use <command>libtool</command> to adjust the
 	  compilation and installation of shared libraries to match
 	  the specifics of the underlying operating system.  The usual
 	  practice is to use copy of <command>libtool</command>
 	  bundled with the application.  In case you need to use
 	  external <command>libtool</command>, you can use the version
 	  provided by The Ports Collection:</para>
 
 	<programlisting>USE_AUTOTOOLS=	libtool:<replaceable>version</replaceable>[:env]</programlisting>
 
 	<para>With no additional operations,
 	  <literal>libtool:<replaceable>version</replaceable></literal>
 	  tells the building framework to patch the configure script
 	  with the system-installed copy of
 	  <command>libtool</command>.  The
 	  <makevar>GNU_CONFIGURE</makevar> is implied.  Further, a
 	  number of make and shell variables will be assigned for
 	  onward use by the port.  See
 	  <filename>bsd.autotools.mk</filename> for details.</para>
 
 	<para>With the <literal>:env</literal> operation, only the
 	  environment will be set up.</para>
 
 	<para>Finally, <makevar>LIBTOOLFLAGS</makevar> and
 	  <makevar>LIBTOOLFILES</makevar> can be optionally set to
 	  override the most likely arguments to, and files patched by,
 	  <command>libtool</command>.  Most ports are unlikely to need
 	  this.  See <filename>bsd.autotools.mk</filename> for further
 	  details.</para>
       </sect2>
 
       <sect2 id="using-libltdl">
 	<title><command>libltdl</command></title>
 
 	<para>Some ports make use of the <command>libltdl</command>
 	  library package, which is part of the
 	  <command>libtool</command> suite.  Use of this library does
 	  not automatically necessitate the use of
 	  <command>libtool</command> itself, so a separate construct
 	  is provided.</para>
 
 	<programlisting>USE_AUTOTOOLS=	libltdl:<replaceable>version</replaceable></programlisting>
 
 	<para>Currently, all this does is to bring in a
 	  <makevar>LIB_DEPENDS</makevar> on the appropriate
 	  <command>libltdl</command> port, and is provided as a
 	  convenience function to help eliminate any dependencies on
 	  the autotools ports outside of the
 	  <makevar>USE_AUTOTOOLS</makevar> framework.  There are no
 	  optional operations for this tool.</para>
       </sect2>
 
       <sect2 id="using-autoconf">
 	<title><command>autoconf</command> and
 	  <command>autoheader</command></title>
 
 	<para>Some ports do not contain a configure script, but do
 	  contain an autoconf template in the
 	  <filename>configure.ac</filename> file.  You can use the
 	  following assignments to let <command>autoconf</command>
 	  create the configure script, and also have
 	  <command>autoheader</command> create template headers for
 	  use by the configure script.</para>
 
 	<programlisting>USE_AUTOTOOLS=	autoconf:<replaceable>version</replaceable>[:env]</programlisting>
 
 	<para>and</para>
 
 	<programlisting>USE_AUTOTOOLS=	autoheader:<replaceable>version</replaceable></programlisting>
 
 	<para>which also implies the use of
 	  <literal>autoconf:<replaceable>version</replaceable></literal>.</para>
 
 	<para>Similarly to <command>libtool</command>, the inclusion
 	  of the optional <literal>:env</literal> operation simply
 	  sets up the environment for further use.  Without it,
 	  patching and reconfiguration of the port is carried
 	  out.</para>
 
 	<para>The additional optional variables
 	  <makevar>AUTOCONF_ARGS</makevar> and
 	  <makevar>AUTOHEADER_ARGS</makevar> can be overridden by the
 	  port <filename>Makefile</filename> if specifically
 	  requested.  As with the <command>libtool</command>
 	  equivalents, most ports are unlikely to need this.</para>
       </sect2>
 
       <sect2 id="using-automake">
 	<title><command>automake</command> and
 	  <command>aclocal</command></title>
 
 	<para>Some packages only contain
 	  <filename>Makefile.am</filename> files.  These have to be
 	  converted into <filename>Makefile.in</filename> files using
 	  <command>automake</command>, and the further processed by
 	  <command>configure</command> to generate an actual
 	  <filename>Makefile</filename>.</para>
 
 	<para>Similarly, packages occasionally do not ship with
 	  included <filename>aclocal.m4</filename> files, again
 	  required to build the software.  This can be achieved with
 	  <command>aclocal</command>, which scans
 	  <filename>configure.ac</filename> or
 	  <filename>configure.in</filename>.</para>
 
 	<para><command>aclocal</command> has a similar relationship to
 	  <command>automake</command> as <command>autoheader</command>
 	  does to <command>autoconf</command>, described in the
 	  previous section.  <command>aclocal</command> implies the
 	  use of <command>automake</command>, thus we have:</para>
 
 	<programlisting>USE_AUTOTOOLS=	automake:<replaceable>version</replaceable>[:<replaceable>env</replaceable>]</programlisting>
 
 	<para>and</para>
 
 	<programlisting>USE_AUTOTOOLS=	aclocal:<replaceable>version</replaceable></programlisting>
 
 	<para>which also implies the use of
 	  <literal>automake:<replaceable>version</replaceable></literal>.</para>
 
 	<para>Similarly to <command>libtool</command> and
 	  <command>autoconf</command>, the inclusion of the optional
 	  <literal>:env</literal> operation simply sets up the
 	  environment for further use.  Without it, reconfiguration of
 	  the port is carried out.</para>
 
 	<para>As with <command>autoconf</command> and
 	  <command>autoheader</command>, both
 	  <command>automake</command> and <command>aclocal</command>
 	  have optional argument variables,
 	  <makevar>AUTOMAKE_ARGS</makevar> and
 	  <makevar>ACLOCAL_ARGS</makevar> respectively, which may be
 	  overridden by the port <filename>Makefile</filename> if
 	  required.</para>
       </sect2>
     </sect1>
 
     <sect1 id="using-gettext">
       <title>Using GNU <literal>gettext</literal></title>
 
       <sect2>
 	<title>Basic Usage</title>
 
 	<para>If your port requires <literal>gettext</literal>, set
 	  <literal>USES= gettext</literal>, and your
 	  port will inherit a dependency on <filename
 	    role="package">devel/gettext</filename>. Other values for
 	  <literal>gettext</literal> usage are listed in <xref
 	  linkend="uses-values"/>.</para>
 
 	<para>A rather common case is a port using
 	  <literal>gettext</literal> and <command>configure</command>.
 	  Generally, GNU <command>configure</command> should be able
 	  to locate <literal>gettext</literal> automatically.  If it
 	  ever fails to, hints at the location of
 	  <literal>gettext</literal> can be passed in
 	  <envar>CPPFLAGS</envar> and <envar>LDFLAGS</envar> as
 	  follows:</para>
 
 	<programlisting>USES=	gettext
 CPPFLAGS+=	-I${LOCALBASE}/include
 LDFLAGS+=	-L${LOCALBASE}/lib
 
 GNU_CONFIGURE=	yes</programlisting>
 
 	<para>Of course, the code can be more compact if there are no
 	  more flags to pass to <command>configure</command>:</para>
 
 	<programlisting>USES=	gettext
 GNU_CONFIGURE=	yes</programlisting>
       </sect2>
 
       <sect2>
 	<title>Optional Usage</title>
 
 	<para>Some software products allow for disabling NLS, e.g.,
 	  through passing <option>--disable-nls</option> to
 	  <command>configure</command>.  In that case, your port
 	  should use <literal>gettext</literal> conditionally,
 	  depending on the status of <link
 	    linkend="knobs-without-nls"><makevar>WITHOUT_NLS</makevar></link>.
 	  For ports of low to medium complexity, you can rely on the
 	  following idiom:</para>
 
 	<programlisting>GNU_CONFIGURE=		yes
 
 .include &lt;bsd.port.options.mk&gt;
 
 .if ${PORT_OPTIONS:MNLS}
 USES+=			gettext
 PLIST_SUB+=		NLS=""
 .else
 CONFIGURE_ARGS+=	--disable-nls
 PLIST_SUB+=		NLS="@comment "
 .endif
 
 .include &lt;bsd.port.mk&gt;</programlisting>
 
 	<para>The next item on your to-do list is to arrange so that
 	  the message catalog files are included in the packing list
 	  conditionally.  The <filename>Makefile</filename> part of
 	  this task is already provided by the idiom.  It is explained
 	  in the section on <link linkend="plist-sub">advanced
 	    <filename>pkg-plist</filename> practices</link>.  In a
 	  nutshell, each occurrence of <literal>%%NLS%%</literal> in
 	  <filename>pkg-plist</filename> will be replaced by
 	  <quote><literal>@comment&nbsp;</literal></quote> if NLS is
 	  disabled, or by a null string if NLS is enabled.
 	  Consequently, the lines prefixed by
 	  <literal>%%NLS%%</literal> will become mere comments in the
 	  final packing list if NLS is off; otherwise the prefix will
 	  be just left out.  All you need to do now is insert
 	  <literal>%%NLS%%</literal> before each path to a message
 	  catalog file in <filename>pkg-plist</filename>.  For
 	  example:</para>
 
 	<programlisting>%%NLS%%share/locale/fr/LC_MESSAGES/foobar.mo
 %%NLS%%share/locale/no/LC_MESSAGES/foobar.mo</programlisting>
 
 	<para>In high complexity cases, you may need to use more
 	  advanced techniques than the recipe given here, such as
 	  <link linkend="plist-dynamic">dynamic packing list
 	    generation</link>.</para>
       </sect2>
 
       <sect2>
 	<title>Handling Message Catalog Directories</title>
 
 	<para>There is a point to note about installing message
 	  catalog files.  The target directories for them, which
 	  reside under
 	  <filename><makevar>LOCALBASE</makevar>/share/locale</filename>,
 	  should rarely be created and removed by a port.  The most
 
 	  popular languages have their respective directories listed
 	  in
 	  <filename><makevar>PORTSDIR</makevar>/Templates/BSD.local.dist</filename>.
 	  The directories for many other languages are governed by the
 	  <filename role="package">devel/gettext</filename> port.
 	  Consult its <filename>pkg-plist</filename> and see whether
 	  the port is going to install a message catalog file for a
 	  unique language.</para>
       </sect2>
     </sect1>
 
     <sect1 id="using-perl">
       <title>Using <application>Perl</application></title>
 
       <para>If <makevar>MASTER_SITES</makevar> is set to
 	<makevar>MASTER_SITE_PERL_CPAN</makevar>, then the preferred
 	value of <makevar>MASTER_SITE_SUBDIR</makevar> is the
 	top-level hierarchy name.  For example, the recommended value
 	for <literal>p5-Module-Name</literal> is
 	<literal>Module</literal>.  The top-level hierarchy can be
 	examined at <ulink
 	  url="http://cpan.org/modules/by-module/">cpan.org</ulink>.
 	This keeps the port working when the author of the module
 	changes.</para>
 
       <para>The exception to this rule is when the relevant directory
 	does not exist or the distfile does not exist in that
 	directory.  In such case, using author's id as
 	<makevar>MASTER_SITE_SUBDIR</makevar> is allowed.</para>
 
       <para>All of the tunable knobs below accept either
 	<literal>YES</literal> or a version string like
 	<literal>5.8.0+</literal>.  <literal>YES</literal> means
 	that the port can be used with any of the supported
 	Perl versions.  If a port only
 	works with specific versions of
 	Perl, it can be indicated with a
 	version string, specifying a minimum version (e.g.,
 	<literal>5.7.3+</literal>), a maximum version (e.g.,
 	<literal>5.8.0-</literal>) or an exact version (e.g.,
 	<literal>5.8.3</literal>).</para>
 
       <table frame="none">
 	<title>Variables for Ports That Use
 	  <application>Perl</application></title>
 
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Variable</entry>
 	      <entry>Meaning</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><makevar>USE_PERL5</makevar></entry>
 	      <entry>The port uses Perl 5
 		to build and run.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_PERL5_BUILD</makevar></entry>
 	      <entry>The port uses Perl 5
 		to build.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_PERL5_RUN</makevar></entry>
 	      <entry>The port uses Perl 5
 		to run.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL</makevar></entry>
 	      <entry>The full path of the Perl 5 interpreter,
 		either in the system or installed from a port, but
 		without the version number.  Use this if you need to
 		replace <quote><literal>#!</literal></quote>lines in
 		scripts.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_CONFIGURE</makevar></entry>
 	      <entry>Configure using Perl's MakeMaker.  It implies
 		<makevar>USE_PERL5</makevar>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_MODBUILD</makevar></entry>
 	      <entry>Configure, build and install using Module::Build.
 		It implies <makevar>PERL_CONFIGURE</makevar>.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
 
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Read only variables</entry>
 	      <entry>Means</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><makevar>PERL_VERSION</makevar></entry>
 	      <entry>The full version of Perl
 		installed (e.g., <literal>5.8.9</literal>).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_LEVEL</makevar></entry>
 	      <entry>The installed Perl version as
 		an integer of the form <literal>MNNNPP</literal>
 		(e.g., <literal>500809</literal>).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_ARCH</makevar></entry>
 	      <entry>Where Perl stores architecture
 		dependent libraries.  Defaults to
 		<literal>${ARCH}-freebsd</literal>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_PORT</makevar></entry>
 	      <entry>Name of the Perl port that is
 		installed (e.g., <literal>perl5</literal>).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>SITE_PERL</makevar></entry>
 	      <entry>Directory name where site specific
 		Perl packages go.  This value is
 		added to <makevar>PLIST_SUB</makevar>.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <note>
 	<para>Ports of Perl modules which do not have an official
 	  website should link to <hostid>cpan.org</hostid> in the WWW
 	  line of <filename>pkg-descr</filename>.  The
 	  preferred URL form is
 	  <literal>http://search.cpan.org/dist/Module-Name/</literal>
 	  (including the trailing slash).</para>
       </note>
 
       <note>
 	<para>Do not use <literal>${SITE_PERL}</literal> in dependency
 	  declarations.  Doing so assumes that
 	  <filename>bsd.perl.mk</filename> has been included, which is
 	  not always true.  Ports depending on this port will have
 	  incorrect dependencies if this port's files move later in an
 	  upgrade.  The right way to declare Perl module dependencies
 	  is shown in the example below.</para>
       </note>
 
       <example id="use-perl-dependency-example">
 	<title>Perl Dependency Example</title>
 
 	<programlisting>p5-IO-Tee&gt;=0.64:${PORTSDIR}/devel/p5-IO-Tee</programlisting>
       </example>
     </sect1>
 
     <sect1 id="using-x11">
       <title>Using X11</title>
 
       <sect2 id="x11-variables">
 	<title>X.Org Components</title>
 
 	<para>The X11 implementation available in The Ports Collection
 	  is X.Org.  If your application depends on X components, set
 	  <makevar>USE_XORG</makevar> to the list of required
 	  components.  Available components, at the time of writing,
 	  are:</para>
 
 	<para><literal>bigreqsproto compositeproto damageproto dmx
 	    dmxproto dri2proto evieproto fixesproto fontcacheproto
 	    fontenc fontsproto fontutil glproto ice inputproto kbproto
 	    libfs oldx pciaccess pixman printproto randrproto
 	    recordproto renderproto resourceproto scrnsaverproto sm
 	    trapproto videoproto x11 xau xaw xaw6 xaw7 xbitmaps
 	    xcmiscproto xcomposite xcursor xdamage xdmcp xevie xext
 	    xextproto xf86bigfontproto xf86dgaproto xf86driproto
 	    xf86miscproto xf86rushproto xf86vidmodeproto xfixes xfont
 	    xfontcache xft xi xinerama xineramaproto xkbfile xkbui
 	    xmu xmuu xorg-server xp xpm xprintapputil xprintutil
 	    xproto xproxymngproto xrandr xrender xres xscrnsaver xt
 	    xtrans xtrap xtst xv xvmc xxf86dga xxf86misc
 	    xxf86vm</literal>.</para>
 
 	<para>Always up-to-date list can be found in
 	  <filename>/usr/ports/Mk/bsd.xorg.mk</filename>.</para>
 
 	<para>The Mesa Project is an effort to provide free OpenGL
 	  implementation.  You can specify a dependency on various
 	  components of this project with <makevar>USE_GL</makevar>
 	  variable.  Valid options are: <literal>glut, glu, glw, glew,
 	    gl</literal> and <literal>linux</literal>.  For backwards
 	  compatibility, the value of <literal>yes</literal> maps to
 	  <literal>glu</literal>.</para>
 
 	<example id="use-xorg-example">
 	  <title>USE_XORG Example</title>
 
 	  <programlisting>USE_XORG=	xrender xft xkbfile xt xaw
 USE_GL=		glu</programlisting>
 	</example>
 
 	<table frame="none">
 	  <title>Variables for Ports That Use X</title>
 
 	  <tgroup cols="2">
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_IMAKE</makevar></entry>
 		<entry>The port uses <command>imake</command>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>XMKMF</makevar></entry>
 		<entry>Set to the path of <command>xmkmf</command> if
 		  not in the <envar>PATH</envar>.  Defaults to
 		  <literal>xmkmf -a</literal>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<table frame="none">
 	  <title>Variables for Depending on Individual Parts of
 	    X11</title>
 
 	  <tgroup cols="2">
 	    <tbody>
 	      <row>
 		<entry><makevar>X_IMAKE_PORT</makevar></entry>
 		<entry>Port providing <command>imake</command> and
 		  several other utilities used to build X11.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_LIBRARIES_PORT</makevar></entry>
 		<entry>Port providing X11 libraries.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_CLIENTS_PORT</makevar></entry>
 		<entry>Port providing X clients.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_SERVER_PORT</makevar></entry>
 		<entry>Port providing X server.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_FONTSERVER_PORT</makevar></entry>
 		<entry>Port providing font server.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_PRINTSERVER_PORT</makevar></entry>
 		<entry>Port providing print server.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_VFBSERVER_PORT</makevar></entry>
 		<entry>Port providing virtual framebuffer
 		  server.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_NESTSERVER_PORT</makevar></entry>
 		<entry>Port providing a nested X server.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_FONTS_ENCODINGS_PORT</makevar></entry>
 		<entry>Port providing encodings for fonts.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_FONTS_MISC_PORT</makevar></entry>
 		<entry>Port providing miscellaneous bitmap
 		  fonts.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_FONTS_100DPI_PORT</makevar></entry>
 		<entry>Port providing 100dpi bitmap fonts.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_FONTS_75DPI_PORT</makevar></entry>
 		<entry>Port providing 75dpi bitmap fonts.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_FONTS_CYRILLIC_PORT</makevar></entry>
 		<entry>Port providing cyrillic bitmap fonts.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_FONTS_TTF_PORT</makevar></entry>
 		<entry>Port providing &truetype; fonts.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_FONTS_TYPE1_PORT</makevar></entry>
 		<entry>Port providing Type1 fonts.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>X_MANUALS_PORT</makevar></entry>
 		<entry>Port providing developer oriented manual
 		  pages</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<example id="using-x11-vars">
 	  <title>Using X11-Related Variables</title>
 
 	  <programlisting># Use some X11 libraries and depend on
 # font server as well as cyrillic fonts.
 RUN_DEPENDS=	${LOCALBASE}/bin/xfs:${X_FONTSERVER_PORT} \
 		${LOCALBASE}/lib/X11/fonts/cyrillic/crox1c.pcf.gz:${X_FONTS_CYRILLIC_PORT}
 
 USE_XORG=	x11 xpm</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="x11-motif">
 	<title>Ports That Require Motif</title>
 
 	<para>If your port requires a Motif library, define
 	  <makevar>USE_MOTIF</makevar> in the
 	  <filename>Makefile</filename>.  Default Motif implementation
 	  is <filename
 	    role="package">x11-toolkits/open-motif</filename>.  Users
 	  can choose <filename
 	    role="package">x11-toolkits/lesstif</filename> instead by
 	  setting <makevar>WANT_LESSTIF</makevar> variable.</para>
 
 	<para>The <makevar>MOTIFLIB</makevar> variable will be set by
 	  <filename>bsd.port.mk</filename> to reference the
 	  appropriate Motif library.  Please patch the source of your
 	  port to use <literal>&dollar;{MOTIFLIB}</literal> wherever
 	  the Motif library is referenced in the original
 	  <filename>Makefile</filename> or
 	  <filename>Imakefile</filename>.</para>
 
 	<para>There are two common cases:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>If the port refers to the Motif library as
 	      <literal>-lXm</literal> in its
 	      <filename>Makefile</filename> or
 	      <filename>Imakefile</filename>, simply substitute
 	      <literal>&dollar;{MOTIFLIB}</literal> for it.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>If the port uses <literal>XmClientLibs</literal> in
 	      its <filename>Imakefile</filename>, change it to
 	      <literal>&dollar;{MOTIFLIB} &dollar;{XTOOLLIB}
 		&dollar;{XLIB}</literal>.</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>Note that <makevar>MOTIFLIB</makevar> (usually) expands
 	  to <literal>-L/usr/local/lib -lXm</literal> or
 	  <literal>/usr/local/lib/libXm.a</literal>, so there is no
 	  need to add <literal>-L</literal> or <literal>-l</literal>
 	  in front.</para>
       </sect2>
 
       <sect2>
 	<title>X11 Fonts</title>
 
 	<para>If your port installs fonts for the X Window System, put
 	  them in
 	  <filename><makevar>LOCALBASE</makevar>/lib/X11/fonts/local</filename>.</para>
       </sect2>
 
       <sect2>
 	<title>Getting a Fake <envar>DISPLAY</envar> with Xvfb</title>
 
 	<para>Some applications require a working X11 display for
 	  compilation to succeed.  This pose a problem for machines
 	  that operate headless.  When the following variable is used,
 	  the build infrastructure will start the virtual framebuffer
 	  X server.  The working <envar>DISPLAY</envar> is then passed
 	  to the build.</para>
 
 	<programlisting>USE_DISPLAY=	yes</programlisting>
       </sect2>
 
       <sect2 id="desktop-entries">
 	<title>Desktop Entries</title>
 
 	<para>Desktop entries (<ulink
 	    url="http://standards.freedesktop.org/desktop-entry-spec/latest/">a
 	    Freedesktop standard</ulink>) provide a way to
 	  automatically adjust desktop features when a new program is
 	  installed, without requiring user intervention.  For
 	  example, newly-installed programs automatically appear in
 	  the application menus of compatible desktop environments.
 	  Desktop entries originated in the
 	  <application>GNOME</application> desktop environment, but
 	  are now a standard and also work with
 	  <application>KDE</application> and
 	  <application>Xfce</application>.  This bit of automation
 	  provides a real benefit to the user, and desktop entries are
 	  encouraged for applications which can be used in a desktop
 	  environment.</para>
 
 	<sect3>
 	  <title>Using Predefined <filename>.desktop</filename>
 	    Files</title>
 
 	  <para>Ports that include predefined
 	    <filename>*.desktop</filename> files should
 	    include those files in <filename>pkg-plist</filename>
 	    and install them in the
 	    <filename><makevar>&dollar;LOCALBASE</makevar>/share/applications</filename>
 	    directory.  The <link
 	      linkend="install-macros"><makevar>INSTALL_DATA</makevar>
 	      macro</link> is useful for installing these
 	    files.</para>
 	</sect3>
 
 	<sect3 id="updating-desktop-database">
 	  <title>Updating desktop database</title>
 
 	  <para>If a port has a MimeType entry in its
 	    <filename><replaceable>portname</replaceable>.desktop</filename>,
 	    the desktop database must
 	    be updated after install and deinstall.  To do this,
 	    define <makevar>USES</makevar>= desktop-file-utils.</para>
 	</sect3>
 
 	<sect3 id="desktop-entries-macro">
 	  <title>Creating Desktop Entries with the
 	    <makevar>DESKTOP_ENTRIES</makevar> Macro</title>
 
 	  <para>Desktop entries can be easily created for applications
 	    by using the <makevar>DESKTOP_ENTRIES</makevar> variable.
 	    A file named
 	    <filename><replaceable>name</replaceable>.desktop</filename>
 	    will be created, installed, and added to the
 	    <filename>pkg-plist</filename> automatically.  Syntax
 	    is:</para>
 
 	  <programlisting>DESKTOP_ENTRIES=	"NAME" "COMMENT" "ICON" "COMMAND" "CATEGORY" StartupNotify</programlisting>
 
 	  <para>The list of possible categories is available on the
 	    <ulink
 	      url="http://standards.freedesktop.org/menu-spec/latest/apa.html">Freedesktop
 	      website</ulink>.  <makevar>StartupNotify</makevar>
 	    indicates whether the application is compatible with
 	    <emphasis>startup notifications</emphasis>.  These are
 	    typically a graphic indicator like a clock that appear at
 	    the mouse pointer, menu, or panel to give the user an
 	    indication when a program is starting.  A program that is
 	    compatible with startup notifications clears the indicator
 	    after it has started.  Programs that are not compatible
 	    with startup notifications would never clear the indicator
 	    (potentially confusing and infuriating the user), and
 	    should have <makevar>StartupNotify</makevar> set to
 	    <literal>false</literal> so the indicator is not shown at
 	    all.</para>
 
 	  <para>Example:</para>
 
 	  <programlisting>DESKTOP_ENTRIES=	"ToME" "Roguelike game based on JRR Tolkien's work" \
 			"${DATADIR}/xtra/graf/tome-128.png" \
 			"tome -v -g" "Application;Game;RolePlaying;" \
 			false</programlisting>
 
 	</sect3>
       </sect2>
     </sect1>
 
     <sect1 id="using-gnome">
       <title>Using GNOME</title>
 
       <para>The FreeBSD/GNOME project uses its own set of variables to
 	define which GNOME components a particular port uses.  A
 	<ulink
 	  url="http://www.FreeBSD.org/gnome/docs/porting.html">comprehensive
 	  list of these variables</ulink> exists within the
 	FreeBSD/GNOME project's homepage.</para>
     </sect1>
 
     <sect1 id="using-qt">
       <title>Using Qt</title>
 
       <sect2 id="qt-common">
 	<title>Ports That Require Qt</title>
 
 	<table frame="none">
 	  <title>Variables for Ports That Use Qt</title>
 
 	  <tgroup cols="2">
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_QT_VER</makevar></entry>
 		<entry>The port uses the Qt toolkit.  The only
 		  possible value is <literal>3</literal>.
 		  Appropriate parameters are passed to
 		  <command>configure</command> script and
 		  <command>make</command>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_QT4</makevar></entry>
 		<entry>Specify tool and library dependencies for ports
 		  that use Qt 4.  See <link
 		    linkend="qt4-components">Qt 4 component
 		    selection</link> for more details.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QT_PREFIX</makevar></entry>
 		<entry>Set to the path where Qt installed to
 		  (read-only variable).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>MOC</makevar></entry>
 		<entry>Set to the path of <command>moc</command>
 		  (read-only variable).  Default set according to
 		  <makevar>USE_QT_VER</makevar> value.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QTCPPFLAGS</makevar></entry>
 		<entry>Additional compiler flags passed via
 		  <makevar>CONFIGURE_ENV</makevar> for Qt toolkit.
 		  Default set according to
 		  <makevar>USE_QT_VER</makevar>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QTCFGLIBS</makevar></entry>
 		<entry>Additional libraries for linking passed via
 		  <makevar>CONFIGURE_ENV</makevar> for Qt toolkit.
 		  Default set according to
 		  <makevar>USE_QT_VER</makevar>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QTNONSTANDARD</makevar></entry>
 		<entry>Suppress modification of
 		  <makevar>CONFIGURE_ENV</makevar>,
 		  <makevar>CONFIGURE_ARGS</makevar>,
 		  <makevar>CPPFLAGS</makevar> and
 		  <makevar>MAKE_ENV</makevar>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<table frame="none">
 	  <title>Additional Variables for Ports That Use Qt
 	    4.x</title>
 
 	  <tgroup cols="2">
 	    <tbody>
 	      <row>
 		<entry><makevar>UIC</makevar></entry>
 		<entry>Set to the path of <command>uic</command>
 		  (read-only variable).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QMAKE</makevar></entry>
 		<entry>Set to the path of <command>qmake</command>
 		  (read-only variable).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QMAKESPEC</makevar></entry>
 		<entry>Set to the path of configuration file for
 		  <command>qmake</command> (read-only
 		  variable).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QMAKEFLAGS</makevar></entry>
 		<entry>Additional flags for
 		  <command>qmake</command>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QT_INCDIR</makevar></entry>
 		<entry>Set to Qt 4 include directories (read-only
 		  variable).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QT_LIBDIR</makevar></entry>
 		<entry>Set to Qt 4 libraries path (read-only
 		  variable).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>QT_PLUGINDIR</makevar></entry>
 		<entry>Set to Qt 4 plugins path (read-only
 		  variable).</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>When <makevar>USE_QT_VER</makevar> is set to
 	  <literal>3</literal>, some useful settings are passed to the
 	  <command>configure</command> script:</para>
 
 	<programlisting>CONFIGURE_ARGS+=	--with-qt-includes=${QT_PREFIX}/include \
 			--with-qt-libraries=${QT_PREFIX}/lib \
 			--with-extra-libs=${LOCALBASE}/lib \
 			--with-extra-includes=${LOCALBASE}/include
 CONFIGURE_ENV+=	MOC="${MOC}" LIBS="${QTCFGLIBS}" \
 		QTDIR="${QT_PREFIX}" KDEDIR="${KDE_PREFIX}"
 CPPFLAGS+=	${QTCPPFLAGS}</programlisting>
 
 	<para>If <makevar>USE_QT4</makevar> is set, the following
 	  settings are deployed:</para>
 
 	<programlisting>CONFIGURE_ARGS+=	--with-qt-includes=${QT_INCDIR} \
 			--with-qt-libraries=${QT_LIBDIR} \
 			--with-extra-libs=${LOCALBASE}/lib \
 			--with-extra-includes=${LOCALBASE}/include
 CONFIGURE_ENV+=	MOC="${MOC}" UIC="${UIC}" LIBS="${QTCFGLIBS}" \
 		QMAKE="${QMAKE}" QMAKESPEC="${QMAKESPEC}" QTDIR="${QT_PREFIX}"
 MAKE_ENV+=	QMAKESPEC="${QMAKESPEC}"
 
 PLIST_SUB+=	QT_INCDIR_REL=${QT_INCDIR_REL} \
 		QT_LIBDIR_REL=${QT_LIBDIR_REL} \
 		QT_PLUGINDIR_REL=${QT_PLUGINDIR_REL}</programlisting>
       </sect2>
 
       <sect2 id="qt4-components">
 	<title>Component Selection (Qt 4.x Only)</title>
 
 	<para>Individual Qt 4 tool and library dependencies
 	  must be specified in the <makevar>USE_QT4</makevar>
 	  variable.  Every component
 	  can be suffixed by either <literal>_build</literal> or
 	  <literal>_run</literal>, the suffix indicating whether the
 	  component should be depended on at buildtime or runtime,
 	  respectively.  If unsuffixed, the component will be depended
 	  on at both build- and runtime.  Usually, library components
 	  should be specified unsuffixed, tool components should be
 	  specified with the <literal>_build</literal> suffix and
 	  plugin components should be specified with the
 	  <literal>_run</literal> suffix.  The most commonly used
 	  components are listed below (all available components are
 	  listed in <makevar>_USE_QT4_ALL</makevar> in
 	  <filename>/usr/ports/Mk/bsd.qt.mk</filename>):</para>
 
 	<table frame="none">
 	  <title>Available Qt 4 Library Components</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>corelib</literal></entry>
 		<entry>core library (can be omitted unless the port
 		  uses nothing but <literal>corelib</literal>)</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>gui</literal></entry>
 		<entry>graphical user interface library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>network</literal></entry>
 		<entry>network library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>opengl</literal></entry>
 		<entry>OpenGL library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>qt3support</literal></entry>
 		<entry>Qt 3 compatibility library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>qtestlib</literal></entry>
 		<entry>unit testing library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>script</literal></entry>
 		<entry>script library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>sql</literal></entry>
 		<entry>SQL library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>xml</literal></entry>
 		<entry>XML library</entry>
 	      </row>
 
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>You can determine which libraries the application
 	  depends on, by running <command>ldd</command> on the main
 	  executable after a successful compilation.</para>
 
 	<table frame="none">
 	  <title>Available Qt 4 Tool Components</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>moc</literal></entry>
 		<entry>meta object compiler (needed for almost
 		  every Qt application at buildtime)</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>qmake</literal></entry>
 		<entry>Makefile generator / build utility</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>rcc</literal></entry>
 		<entry>resource compiler (needed if the application
 		  comes with <filename>*.rc</filename> or
 		  <filename>*.qrc</filename> files)</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>uic</literal></entry>
 		<entry>user interface compiler (needed if the
 		  application comes with <filename>*.ui</filename>
 		  files created by Qt Designer - in practice, every Qt
 		  application with a GUI)</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<table frame="none">
 	  <title>Available Qt 4 Plugin Components</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>iconengines</literal></entry>
 		<entry>SVG icon engine plugin (if the application
 		  ships SVG icons)</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>imageformats</literal></entry>
 		<entry>imageformat plugins for GIF, JPEG, MNG and
 		  SVG (if the application ships image files)</entry>
 	      </row>
 
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<example id="qt4-components-example">
 	  <title>Selecting Qt 4 Components</title>
 
 	  <para>In this example, the ported application uses the Qt 4
 	    graphical user interface library, the Qt 4 core library,
 	    all of the Qt 4 code generation tools and Qt 4's Makefile
 	    generator.  Since the <literal>gui</literal> library
 	    implies a dependency on the core library,
 	    <literal>corelib</literal> does not need to be specified.
 	    The Qt 4 code generation tools <literal>moc</literal>,
 	    <literal>uic</literal> and <literal>rcc</literal>, as well
 	    as the Makefile generator <literal>qmake</literal> are
 	    only needed at buildtime, thus they are specified with the
 	    <literal>_build</literal> suffix:</para>
 
 	  <programlisting>USE_QT4=	gui moc_build qmake_build rcc_build uic_build</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="qt-additional">
 	<title>Additional Considerations</title>
 
 	<para>If the application does not provide a
 	  <filename>configure</filename> file but a
 	  <filename>.pro</filename> file, you can use the
 	  following:</para>
 
 	<programlisting>HAS_CONFIGURE=	yes
 
 do-configure:
 	@cd ${WRKSRC} &amp;&amp; ${SETENV} ${CONFIGURE_ENV} \
 		${QMAKE} ${QMAKEFLAGS} PREFIX=${PREFIX} texmaker.pro</programlisting>
 
 	<para>Note the similarity to the <command>qmake</command> line
 	  from the provided <filename>BUILD.sh</filename> script.
 	  Passing <makevar>CONFIGURE_ENV</makevar> ensures
 	  <command>qmake</command> will see the
 	  <makevar>QMAKESPEC</makevar> variable, without which it
 	  cannot work.  <command>qmake</command> generates standard
 	  Makefiles, so it is not necessary to write our own
 	  <maketarget>build</maketarget> target.</para>
 
 	<para>Qt applications often are written to be cross-platform
 	  and often X11/Unix is not the platform they are developed
 	  on, which in turn often leads to certain loose ends,
 	  like:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para><emphasis>Missing additional include
 		paths.</emphasis>  Many applications come with
 	      system tray icon support, but neglect to look for
 	      includes and/or libraries in the X11 directories.  You
 	      can tell <command>qmake</command> to add directories to
 	      the include and library search paths via the command
 	      line, for example:</para>
 
 	    <programlisting>${QMAKE} ${QMAKEFLAGS} PREFIX=${PREFIX} INCLUDEPATH+=${LOCALBASE}/include \
 	LIBS+=-L${LOCALBASE}/lib sillyapp.pro</programlisting>
 	  </listitem>
 
 	  <listitem>
 	    <para><emphasis>Bogus installation paths.</emphasis>
 	      Sometimes data such as icons or .desktop files are by
 	      default installed into directories which are not scanned
 	      by XDG-compatible applications.  <filename
 		role="package">editors/texmaker</filename> is an
 	      example for this - look at
 	      <filename>patch-texmaker.pro</filename> in the
 	      <filename>files</filename> directory of that port for a
 	      template on how to remedy this directly in the
 	      <command>qmake</command> project file.</para>
 	  </listitem>
 	</itemizedlist>
       </sect2>
     </sect1>
 
     <sect1 id="using-kde">
       <title>Using KDE</title>
 
       <sect2 id="kde-variables">
 	<title>Variable Definitions (KDE 3.x Only)</title>
 
 	<table frame="none">
 	  <title>Variables for Ports That Use KDE 3.x</title>
 
 	  <tgroup cols="2">
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_KDELIBS_VER</makevar></entry>
 		<entry>The port uses KDE libraries.  It specifies the
 		  major version of KDE to use and implies
 		  <makevar>USE_QT_VER</makevar> of the appropriate
 		  version.  The only possible value is
 		  <literal>3</literal>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_KDEBASE_VER</makevar></entry>
 		<entry>The port uses KDE base.  It specifies the major
 		  version of KDE to use and implies
 		  <makevar>USE_QT_VER</makevar> of the appropriate
 		  version.  The only possible value is
 		  <literal>3</literal>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
       </sect2>
 
       <sect2 id="kde4-variables">
 	<title>KDE 4 Variable Definitions</title>
 
 	<para>If your application depends on KDE 4.x, set
 	  <makevar>USE_KDE4</makevar> to the list of required
 	  components.  <literal>_build</literal> and
 	  <literal>_run</literal> suffixes can be used to force
 	  components dependency type (e.g.,
 	  <literal>baseapps_run</literal>).  If no suffix is set, a
 	  default dependency type will be used.  If you want to force
 	  both types, add the component twice with both suffixes
 	  (e.g., <literal>automoc4_build automoc4_run</literal>).  The
 	  most commonly used components are listed below (up-to-date
 	  components are documented at the top of
 	  <filename>/usr/ports/Mk/bsd.kde4.mk</filename>):</para>
 
 	<table frame="none">
 	  <title>Available KDE 4 Components</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>kdehier</literal></entry>
 		<entry>Hierarchy of common KDE directories</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>kdelibs</literal></entry>
 		<entry>KDE Developer Platform</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>kdeprefix</literal></entry>
 		<entry>If set, port will be installed into
 		  <literal>&dollar;{KDE4_PREFIX}</literal> instead of
 		  <literal>&dollar;{LOCALBASE}</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>sharedmime</literal></entry>
 		<entry>MIME types database for KDE ports</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>automoc4</literal></entry>
 		<entry>Automatic moc for Qt 4 packages</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>akonadi</literal></entry>
 		<entry>Storage server for KDE-Pim</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>soprano</literal></entry>
 		<entry>Qt 4 RDF framework</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>strigi</literal></entry>
 		<entry>Desktop search daemon</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>libkcddb</literal></entry>
 		<entry>KDE CDDB library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>libkcompactdisc</literal></entry>
 		<entry>KDE library for interfacing with audio
 		  CDs</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>libkdeedu</literal></entry>
 		<entry>Libraries used by educational
 		  applications</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>libkdcraw</literal></entry>
 		<entry>KDE LibRaw library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>libkexiv2</literal></entry>
 		<entry>KDE Exiv2 library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>libkipi</literal></entry>
 		<entry> KDE Image Plugin Interface</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>libkonq</literal></entry>
 		<entry>Konqueror core library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>libksane</literal></entry>
 		<entry>KDE SANE ("Scanner Access Now Easy")
 		  library</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>pimlibs</literal></entry>
 		<entry>KDE-Pim libraries</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>kate</literal></entry>
 		<entry>Text editor framework</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>marble</literal></entry>
 		<entry>Virtual globe</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>okular</literal></entry>
 		<entry>Universal document viewer</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>korundum</literal></entry>
 		<entry>KDE Ruby bindings</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>perlkde</literal></entry>
 		<entry>KDE Perl bindings</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>pykde4</literal></entry>
 		<entry>KDE Python bindings</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>pykdeuic4</literal></entry>
 		<entry>PyKDE user interface compiler</entry>
 	      </row>
 
 	      <row>
 		<entry>smokekde<literal></literal></entry>
 		<entry>KDE SMOKE libraries</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>KDE 4.x ports are installed into
 	  <makevar>KDE4_PREFIX</makevar>, which is
 	  <filename>/usr/local/kde4</filename> currently, to avoid
 	  conflicts with KDE 3.x ports.  This is achieved by
 	  specifying the <literal>kdeprefix</literal> component, which
 	  overrides the default <makevar>PREFIX</makevar>.  The ports
 	  however respect any <makevar>PREFIX</makevar> set via
 	  <envar>MAKEFLAGS</envar> environment variable and/or
 	  <command>make</command> arguments.</para>
 
 	<example id="kde4-components-example">
 	  <title><makevar>USE_KDE4</makevar> Example</title>
 
 	  <para>This is a simple example for a KDE 4 port.
 	    <literal>USES= cmake:outsource</literal> instructs the
 	    port to utilize <application>CMake</application>, a
 	    configuration tool widely used by KDE 4 projects (see
 	    <xref linkend="using-cmake"/> for detailed usage).
 	    <makevar>USE_KDE4</makevar> brings dependency on KDE
 	    libraries and makes port using
 	    <command>automoc4</command> at build stage.
 	    Required KDE components and other dependencies can be
 	    determined through configure log.
 	    <makevar>USE_KDE4</makevar> does not imply
 	    <makevar>USE_QT4</makevar>.  If a port requires some
 	    Qt 4 components, they should be specified in
 	    <makevar>USE_QT4</makevar>.</para>
 
 	  <programlisting>USES=		cmake:outsource
 USE_KDE4=	kdelibs kdeprefix automoc4
 USE_QT4=	moc_build qmake_build rcc_build uic_build</programlisting>
 	</example>
       </sect2>
     </sect1>
 
     <sect1 id="using-java">
       <title>Using Java</title>
 
       <sect2 id="java-variables">
 	<title>Variable Definitions</title>
 
 	<para>If your port needs a Java&trade; Development Kit
 	  (JDK&trade;) to either build, run or even extract the
 	  distfile, then it should define
 	  <makevar>USE_JAVA</makevar>.</para>
 
 	<para>There are several JDKs in the ports collection, from
 	  various vendors, and in several versions.  If your port must
 	  use one of these versions, you can define which one.  The
-	  most current version is <filename
-	    role="package">java/jdk16</filename>.</para>
+	  most current version, and &os; default is <filename
+	    role="package">java/openjdk6</filename>.</para>
 
 	<table frame="none">
 	  <title>Variables Which May be Set by Ports That Use
 	    Java</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Means</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_JAVA</makevar></entry>
 		<entry>Should be defined for the remaining variables
 		  to have any effect.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_VERSION</makevar></entry>
 		<entry>List of space-separated suitable Java versions
 		  for the port.  An optional <literal>"+"</literal>
 		  allows you to specify a range of versions (allowed
 		  values:
 		  <literal>1.5[+] 1.6[+] 1.7[+]</literal>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_OS</makevar></entry>
 		<entry>List of space-separated suitable JDK port
 		  operating systems for the port (allowed values:
 		  <literal>native linux</literal>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_VENDOR</makevar></entry>
 		<entry>List of space-separated suitable JDK port
 		  vendors for the port (allowed values:
 		  <literal>freebsd bsdjava sun
 		    openjdk</literal>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_BUILD</makevar></entry>
 		<entry>When set, it means that the selected JDK port
 		  should be added to the build dependencies of the
 		  port.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_RUN</makevar></entry>
 		<entry>When set, it means that the selected JDK port
 		  should be added to the run dependencies of the
 		  port.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_EXTRACT</makevar></entry>
 		<entry>When set, it means that the selected JDK port
 		  should be added to the extract dependencies of the
 		  port.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>Below is the list of all settings a port will receive
 	  after setting <makevar>USE_JAVA</makevar>:</para>
 
 	<table frame="none">
 	  <title>Variables Provided to Ports That Use Java</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Value</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry><makevar>JAVA_PORT</makevar></entry>
 		<entry>The name of the JDK port (e.g.,
 		  <literal>'java/openjdk6'</literal>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_PORT_VERSION</makevar></entry>
 		<entry>The full version of the JDK port (e.g.,
 		  <literal>'1.6.0'</literal>).  If you only need the
 		  first two digits of this version number, use
 		  <makevar>${JAVA_PORT_VERSION:C/^([0-9])\.([0-9])(.*)$/\1.\2/}</makevar>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_PORT_OS</makevar></entry>
 
 		<entry>The operating system used by the JDK port
 		  (e.g., <literal>'native'</literal>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_PORT_VENDOR</makevar></entry>
 		<entry>The vendor of the JDK port (e.g.,
 		  <literal>'openjdk'</literal>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_PORT_OS_DESCRIPTION</makevar></entry>
 		<entry>Description of the operating system used by the
 		  JDK port (e.g.,
 		  <literal>'Native'</literal>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_PORT_VENDOR_DESCRIPTION</makevar></entry>
 		<entry>Description of the vendor of the JDK port
 		  (e.g., <literal>'OpenJDK BSD Porting
 		    Team'</literal>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_HOME</makevar></entry>
 		<entry>Path to the installation directory of the JDK
 		  (e.g.,
 		  <filename>'/usr/local/openjdk6'</filename>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVAC</makevar></entry>
 		<entry>Path to the Java compiler to use (e.g.,
 		  <filename>'/usr/local/openjdk6/bin/javac'</filename>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAR</makevar></entry>
 		<entry>Path to the <command>jar</command> tool to use
 		  (e.g.,
 		  <filename>'/usr/local/openjdk6/bin/jar'</filename>
 		  or
 		  <filename>'/usr/local/bin/fastjar'</filename>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>APPLETVIEWER</makevar></entry>
 		<entry>Path to the <command>appletviewer</command>
 		  utility (e.g.,
 		  <filename>'/usr/local/openjdk6/bin/appletviewer'</filename>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA</makevar></entry>
 		<entry>Path to the <command>java</command> executable.
 		  Use this for executing Java programs (e.g.,
 		  <filename>'/usr/local/openjdk6/bin/java'</filename>).</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVADOC</makevar></entry>
 		<entry>Path to the <command>javadoc</command> utility
 		  program.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVAH</makevar></entry>
 		<entry>Path to the <command>javah</command>
 		  program.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVAP</makevar></entry>
 		<entry>Path to the <command>javap</command>
 		  program.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_KEYTOOL</makevar></entry>
 		<entry>Path to the <command>keytool</command> utility
 		  program.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_N2A</makevar></entry>
 		<entry>Path to the <command>native2ascii</command>
 		  tool.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_POLICYTOOL</makevar></entry>
 		<entry>Path to the <command>policytool</command>
 		  program.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_SERIALVER</makevar></entry>
 		<entry>Path to the <command>serialver</command>
 		  utility program.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>RMIC</makevar></entry>
 		<entry>Path to the RMI stub/skeleton generator,
 		  <command>rmic</command>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>RMIREGISTRY</makevar></entry>
 		<entry>Path to the RMI registry program,
 		  <command>rmiregistry</command>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>RMID</makevar></entry>
 		<entry>Path to the RMI daemon program
 		  <command>rmid</command>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVA_CLASSES</makevar></entry>
 		<entry>Path to the archive that contains the JDK class
 		  files,
 		  <filename>${JAVA_HOME}/jre/lib/rt.jar</filename>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>You may use the <literal>java-debug</literal> make
 	  target to get information for debugging your port.  It will
 	  display the value of many of the forecited variables.</para>
 
 	<para>Additionally, the following constants are defined so all
 	  Java ports may be installed in a consistent way:</para>
 
 	<table frame="none">
 	  <title>Constants Defined for Ports That Use Java</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Constant</entry>
 		<entry>Value</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry><makevar>JAVASHAREDIR</makevar></entry>
 		<entry>The base directory for everything related to
 		  Java.  Default:
 		  <filename>${PREFIX}/share/java</filename>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVAJARDIR</makevar></entry>
 		<entry>The directory where JAR files should be
 		  installed.  Default:
 		  <filename>${JAVASHAREDIR}/classes</filename>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>JAVALIBDIR</makevar></entry>
 		<entry>The directory where JAR files installed by
 		  other ports are located.  Default:
 		  <filename>${LOCALBASE}/share/java/classes</filename>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>The related entries are defined in both
 	  <makevar>PLIST_SUB</makevar> (documented in
 	  <xref linkend="plist-sub"/>) and
 	  <makevar>SUB_LIST</makevar>.</para>
       </sect2>
 
       <sect2 id="java-building-with-ant">
 	<title>Building with Ant</title>
 
 	<para>When the port is to be built using Apache Ant, it has to
 	  define <makevar>USE_ANT</makevar>.  Ant is thus considered
 	  to be the sub-make command.  When no
 	  <literal>do-build</literal> target is defined by the port, a
 	  default one will be set that simply runs Ant according to
 	  <makevar>MAKE_ENV</makevar>, <makevar>MAKE_ARGS</makevar>
 	  and <makevar>ALL_TARGET</makevar>.  This is similar to the
 	  <makevar>USE_GMAKE</makevar> mechanism, which is documented
 	  in <xref linkend="building"/>.</para>
       </sect2>
 
       <sect2 id="java-best-practices">
 	<title>Best Practices</title>
 
 	<para>When porting a Java library, your port should install
 	  the JAR file(s) in <filename>${JAVAJARDIR}</filename>, and
 	  everything else under
 	  <filename>${JAVASHAREDIR}/${PORTNAME}</filename> (except for
 	  the documentation, see below).  In order to reduce the
 	  packing file size, you may reference the JAR file(s)
 	  directly in the <filename>Makefile</filename>.  Just use the
 	  following statement (where <filename>myport.jar</filename>
 	  is the name of the JAR file installed as part of the
 	  port):</para>
 
 	<programlisting>PLIST_FILES+=	%%JAVAJARDIR%%/myport.jar</programlisting>
 
 	<para>When porting a Java application, the port usually
 	  installs everything under a single directory (including its
 	  JAR dependencies).  The use of
 	  <filename>${JAVASHAREDIR}/${PORTNAME}</filename> is strongly
 	  encouraged in this regard.  It is up the porter to decide
 	  whether the port should install the additional JAR
 	  dependencies under this directory or directly use the
 	  already installed ones (from
 	  <filename>${JAVAJARDIR}</filename>).</para>
 
 	<para>Regardless of the type of your port (library or
 	  application), the additional documentation should be
 	  installed in the <link linkend="install-documentation">same
 	  location</link> as for any other port.  The JavaDoc tool is
 	  known to produce a different set of files depending on the
 	  version of the JDK that is used.  For ports that do not
 	  enforce the use of a particular JDK, it is therefore a
 	  complex task to specify the packing list
 	  (<filename>pkg-plist</filename>).  This is one reason why
 	  porters are strongly encouraged to use the
 	  <makevar>PORTDOCS</makevar> macro.  Moreover, even if you
 	  can predict the set of files that will be generated by
 	  <command>javadoc</command>, the size of the resulting
 	  <filename>pkg-plist</filename> advocates for the use of
 	  <makevar>PORTDOCS</makevar>.</para>
 
 	<para>The default value for <makevar>DATADIR</makevar> is
 	  <filename>${PREFIX}/share/${PORTNAME}</filename>.  It is a
 	  good idea to override <makevar>DATADIR</makevar> to
 	  <filename>${JAVASHAREDIR}/${PORTNAME}</filename> for Java
 	  ports.  Indeed, <makevar>DATADIR</makevar> is automatically
 	  added to <makevar>PLIST_SUB</makevar> (documented in <xref
 	    linkend="plist-sub"/>) so you may use
 	  <literal>%%DATADIR%%</literal> directly in
 	  <filename>pkg-plist</filename>.</para>
 
 	<para>As for the choice of building Java ports from source or
 	  directly installing them from a binary distribution, there
 	  is no defined policy at the time of writing.  However,
 	  people from the <ulink
 	    url="http://www.freebsd.org/java/">&os; Java
 	  Project</ulink> encourage porters to have their ports built
 	  from source whenever it is a trivial task.</para>
 
 	<para>All the features that have been presented in this
 	  section are implemented in <filename>bsd.java.mk</filename>.
 	  If you ever think that your port needs more sophisticated
 	  Java support, please first have a look at the <ulink
-	    url="http://svn.FreeBSD.org/ports/head/Mk/bsd.java.mk?view=markup">bsd.java.mk
+	    url="http://svnweb.FreeBSD.org/ports/head/Mk/bsd.java.mk?view=markup">bsd.java.mk
 	    SVN log</ulink> as it usually takes some time
 	  to document the latest features.  Then, if you think the
 	  support you are lacking would be beneficial to many other
 	  Java ports, feel free to discuss it on the &a.java;.</para>
 
 	<para>Although there is a <literal>java</literal> category for
 	  PRs, it refers to the JDK porting effort from the &os; Java
 	  project.  Therefore, you should submit your Java port in the
 	  <literal>ports</literal> category as for any other port,
 	  unless the issue you are trying to resolve is related to
 	  either a JDK implementation or
 	  <filename>bsd.java.mk</filename>.</para>
 
 	<para>Similarly, there is a defined policy regarding the
 	  <makevar>CATEGORIES</makevar> of a Java port, which is
 	  detailed in <xref linkend="makefile-categories"/>.</para>
       </sect2>
     </sect1>
 
     <sect1 id="using-php">
       <title>Web Applications, Apache and PHP</title>
 
       <sect2 id="using-apache">
 	<title>Apache</title>
 
 	<table frame="none">
 	  <title>Variables for Ports That Use Apache</title>
 
 	  <tgroup cols="2">
 	    <tbody>
 
 	      <row>
 		<entry><makevar>USE_APACHE</makevar></entry>
 		<entry>The port requires Apache.  Possible values:
 		  <literal>yes</literal> (gets any version),
 		  <literal>22</literal>, <literal>24</literal>,
 		  <literal>22-24</literal>, <literal>22+</literal>,
 		  etc.  The default APACHE version is
 		  <literal>22</literal>.  More details are available
 		  in <filename>ports/Mk/bsd.apache.mk</filename> and
 		  at <ulink
 		    url="http://wiki.freebsd.org/Apache/">wiki.freebsd.org/Apache/</ulink>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>APXS</makevar></entry>
 		<entry>Full path to the <command>apxs</command>
 		  binary.  Can be overridden in your port.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>HTTPD</makevar></entry>
 		<entry>Full path to the <command>httpd</command>
 		  binary.  Can be overridden in your port.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>APACHE_VERSION</makevar></entry>
 		<entry>The version of present Apache installation
 		  (read-only variable).  This variable is only
 		  available after inclusion of
 		  <filename>bsd.port.pre.mk</filename>.  Possible
 		  values: <literal>22</literal>,
 		  <literal>24</literal>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>APACHEMODDIR</makevar></entry>
 		<entry>Directory for Apache modules.  This variable is
 		  automatically expanded in
 		  <filename>pkg-plist</filename>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>APACHEINCLUDEDIR</makevar></entry>
 		<entry>Directory for Apache headers.  This variable is
 		  automatically expanded in
 		  <filename>pkg-plist</filename>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>APACHEETCDIR</makevar></entry>
 		<entry>Directory for Apache configuration files.  This
 		  variable is automatically expanded in
 		  <filename>pkg-plist</filename>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<table frame="none">
 	  <title>Useful Variables for Porting Apache Modules</title>
 
 	  <tgroup cols="2">
 	    <tbody>
 
 	      <row>
 		<entry><makevar>MODULENAME</makevar></entry>
 		<entry>Name of the module.  Default value is
 		  <makevar>PORTNAME</makevar>.  Example:
 		  <literal>mod_hello</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>SHORTMODNAME</makevar></entry>
 		<entry>Short name of the module.  Automatically
 		  derived from <makevar>MODULENAME</makevar>, but can
 		  be overridden.  Example:
 		  <literal>hello</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>AP_FAST_BUILD</makevar></entry>
 		<entry>Use <command>apxs</command> to compile and
 		  install the module.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>AP_GENPLIST</makevar></entry>
 		<entry>Also automatically creates a
 		  <filename>pkg-plist</filename>.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>AP_INC</makevar></entry>
 		<entry>Adds a directory to a header search path during
 		  compilation.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>AP_LIB</makevar></entry>
 		<entry>Adds a directory to a library search path
 		  during compilation.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>AP_EXTRAS</makevar></entry>
 		<entry>Additional flags to pass to
 		  <command>apxs</command>.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
       </sect2>
 
       <sect2 id="web-apps">
 	<title>Web Applications</title>
 
 	<para>Web applications should be installed into
 	  <filename><makevar>PREFIX</makevar>/www/<replaceable>appname</replaceable></filename>.
 	  For your convenience, this path is available both in
 	  <filename>Makefile</filename> and in
 	  <filename>pkg-plist</filename> as <makevar>WWWDIR</makevar>,
 	  and the path relative to <makevar>PREFIX</makevar> is
 	  available in <filename>Makefile</filename> as
 	  <makevar>WWWDIR_REL</makevar>.</para>
 
 	<para>The user and group of web server process are available
 	  as <makevar>WWWOWN</makevar> and <makevar>WWWGRP</makevar>,
 	  in case you need to change the ownership of some files.  The
 	  default values of both are <literal>www</literal>.  If you
 	  want different values for your port, use <literal>WWWOWN?=
 	    myuser</literal> notation, to allow user to override it
 	  easily.</para>
 
 	<para>Do not depend on Apache unless the web app explicitly
 	  needs Apache.  Respect that users may wish to run your web
 	  app on different web server than Apache.</para>
       </sect2>
 
       <sect2 id="php-variables">
 	<title>PHP</title>
 
 	<table frame="none">
 	  <title>Variables for Ports That Use PHP</title>
 
 	  <tgroup cols="2">
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_PHP</makevar></entry>
 		<entry>The port requires PHP.  The value
 		  <literal>yes</literal> adds a dependency on PHP.
 		  The list of required PHP extensions can be specified
 		  instead.  Example: <literal>pcre xml
 		    gettext</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>DEFAULT_PHP_VER</makevar></entry>
 		<entry>Selects which major version of PHP will be
 		  installed as a dependency when no PHP is installed
 		  yet.  Default is <literal>5</literal>.  Possible
 		  values: <literal>4</literal>,
 		  <literal>5</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>IGNORE_WITH_PHP</makevar></entry>
 		<entry>The port does not work with PHP of the given
 		  version.  Possible values: <literal>4</literal>,
 		  <literal>5</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_PHPIZE</makevar></entry>
 		<entry>The port will be built as a PHP
 		  extension.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_PHPEXT</makevar></entry>
 		<entry>The port will be treated as a PHP extension,
 		  including installation and registration in the
 		  extension registry.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_PHP_BUILD</makevar></entry>
 		<entry>Set PHP as a build dependency.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WANT_PHP_CLI</makevar></entry>
 		<entry>Want the CLI (command line) version of
 		  PHP.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WANT_PHP_CGI</makevar></entry>
 		<entry>Want the CGI version of PHP.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WANT_PHP_MOD</makevar></entry>
 		<entry>Want the Apache module version of PHP.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WANT_PHP_SCR</makevar></entry>
 		<entry>Want the CLI or the CGI version of PHP.</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WANT_PHP_WEB</makevar></entry>
 		<entry>Want the Apache module or the CGI version of
 		  PHP.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
       </sect2>
 
       <sect2>
 	<title>PEAR Modules</title>
 
 	<para>Porting PEAR modules is a very simple process.</para>
 
 	<para>Use the variables <makevar>FILES</makevar>,
 	  <makevar>TESTS</makevar>, <makevar>DATA</makevar>,
 	  <makevar>SQLS</makevar>, <makevar>SCRIPTFILES</makevar>,
 	  <makevar>DOCS</makevar> and <makevar>EXAMPLES</makevar> to
 	  list the files you want to install.  All listed files will
 	  be automatically installed into the appropriate locations
 	  and added to <filename>pkg-plist</filename>.</para>
 
 	<para>Include
 	  <filename>&dollar;{PORTSDIR}/devel/pear/bsd.pear.mk</filename>
 	  on the last line of the
 	  <filename>Makefile</filename>.</para>
 
 	<example id="pear-makefile">
 	  <title>Example Makefile for PEAR Class</title>
 
 	  <programlisting>PORTNAME=       Date
 PORTVERSION=	1.4.3
 CATEGORIES=	devel www pear
 
 MAINTAINER=	example@domain.com
 COMMENT=	PEAR Date and Time Zone Classes
 
 BUILD_DEPENDS=	${PEARDIR}/PEAR.php:${PORTSDIR}/devel/pear-PEAR
 RUN_DEPENDS:=	${BUILD_DEPENDS}
 
 FILES=		Date.php Date/Calc.php Date/Human.php Date/Span.php     \
 		Date/TimeZone.php
 TESTS=		test_calc.php test_date_methods_span.php testunit.php   \
 		testunit_date.php testunit_date_span.php wknotest.txt   \
 		bug674.php bug727_1.php bug727_2.php bug727_3.php       \
 		bug727_4.php bug967.php weeksinmonth_4_monday.txt       \
 		weeksinmonth_4_sunday.txt weeksinmonth_rdm_monday.txt   \
 		weeksinmonth_rdm_sunday.txt
 DOCS=		TODO
 _DOCSDIR=	.
 
 .include &lt;bsd.port.pre.mk&gt;
 .include "&dollar;{PORTSDIR}/devel/pear/bsd.pear.mk"
 .include &lt;bsd.port.post.mk&gt;</programlisting>
 	</example>
       </sect2>
     </sect1>
 
     <sect1 id="using-python">
       <title>Using Python</title>
 
       <para>The Ports Collection supports parallel installation of
 	multiple Python versions.  Ports should make sure to use a
 	correct <command>python</command> interpreter, according to
 	the user-settable <makevar>PYTHON_VERSION</makevar> variable.
 	Most prominently, this means replacing the path to
 	<command>python</command> executable in scripts with the value
 	of <makevar>PYTHON_CMD</makevar> variable.</para>
 
       <para>Ports that install files under
 	<makevar>PYTHON_SITELIBDIR</makevar> should use the
 	<literal>pyXY-</literal> package name prefix, so their package
 	name embeds the version of Python they are installed
 	into.</para>
 
       <programlisting>PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}</programlisting>
 
       <table frame="none">
 	<title>Most Useful Variables for Ports That Use Python</title>
 
 	<tgroup cols="2">
 	  <tbody>
 	    <row>
 	      <entry><makevar>USE_PYTHON</makevar></entry>
 	      <entry>The port needs Python.  Minimal required version
 		can be specified with values such as
 		<literal>2.6+</literal>.  Version ranges can also be
 		specified, by separating two version numbers with a
 		dash, e.g.: <literal>2.6-2.7</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_PYDISTUTILS</makevar></entry>
 	      <entry>Use Python distutils for configuring, compiling
 		and installing.  This is required when the port comes
 		with <filename>setup.py</filename>.  This overrides
 		the <maketarget>do-build</maketarget> and
 		<maketarget>do-install</maketarget> targets and may
 		also override <maketarget>do-configure</maketarget> if
 		<makevar>GNU_CONFIGURE</makevar> is not
 		defined.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PYTHON_PKGNAMEPREFIX</makevar></entry>
 	      <entry>Used as a <makevar>PKGNAMEPREFIX</makevar> to
 		distinguish packages for different Python versions.
 		Example: <literal>py24-</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PYTHON_SITELIBDIR</makevar></entry>
 	      <entry>Location of the site-packages tree, that contains
 		installation path of Python (usually
 		<makevar>LOCALBASE</makevar>).  The
 		<makevar>PYTHON_SITELIBDIR</makevar> variable can be
 		very useful when installing Python modules.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PYTHONPREFIX_SITELIBDIR</makevar></entry>
 	      <entry>The PREFIX-clean variant of PYTHON_SITELIBDIR.
 		Always use <literal>%%PYTHON_SITELIBDIR%%</literal> in
 		<filename>pkg-plist</filename> when possible.  The
 		default value of
 		<literal>%%PYTHON_SITELIBDIR%%</literal> is
 		<literal>lib/python%%PYTHON_VERSION%%/site-packages</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PYTHON_CMD</makevar></entry>
 	      <entry>Python interpreter command line, including
 		version number.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PYNUMERIC</makevar></entry>
 	      <entry>Dependency line for numeric extension.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PYNUMPY</makevar></entry>
 	      <entry>Dependency line for the new numeric extension,
 		numpy.  (PYNUMERIC is deprecated by upstream
 		vendor).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PYXML</makevar></entry>
 	      <entry>Dependency line for XML extension (not needed for
 		Python 2.0 and higher as it is also in base
 		distribution).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_TWISTED</makevar></entry>
 	      <entry>Add dependency on twistedCore.  The list of
 		required components can be specified as a value of
 		this variable.  Example: <literal>web lore pair
 		  flow</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_ZOPE</makevar></entry>
 	      <entry>Add dependency on Zope, a web application
 		platform.  Change Python dependency to Python 2.7.
 		Set <makevar>ZOPEBASEDIR</makevar> containing a
 		directory with Zope installation.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>A complete list of available variables can be found in
 	<filename>/usr/ports/Mk/bsd.python.mk</filename>.</para>
     </sect1>
 
     <sect1 id="using-tcl">
       <title>Using <application>Tcl/Tk</application></title>
 
       <para>The Ports Collection supports parallel installation of
 	multiple <application>Tcl/Tk</application> versions.  Ports
 	should try to support at least the default
 	<application>Tcl/Tk</application> version and higher with the
 	<makevar>USE_TCL</makevar> and <makevar>USE_TK</makevar>
 	variables.  It is possible to specify the desired version of
 	<command>tcl</command> with the
 	<makevar>WITH_TCL_VER</makevar> variable.</para>
 
       <table frame="none">
 	<title>The Most Useful Variables for Ports That Use
 	  <application>Tcl/Tk</application></title>
 
 	<tgroup cols="2">
 	  <tbody>
 	    <row>
 	      <entry><makevar>USE_TCL</makevar></entry>
 	      <entry>The port depends on the
 		<application>Tcl</application> library (not the
 		shell).  Minimal required version can be specified
 		with values such as 84+.  Individual unsupported
 		versions can be specified with the
 		<makevar>INVALID_TCL_VER</makevar> variable.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_TCL_BUILD</makevar></entry>
 	      <entry>The port needs <application>Tcl</application>
 		only during the build time.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_TCL_WRAPPER</makevar></entry>
 	      <entry>Ports that require the
 		<application>Tcl</application> shell and do not
 		require a specific <literal>tclsh</literal> version
 		should use this new variable.  The
 		<literal>tclsh</literal> wrapper is installed on the
 		system.  The user can specify the desired
 		<command>tcl</command> shell to use.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>WITH_TCL_VER</makevar></entry>
 	      <entry>User-defined variable that sets the desired
 		<application>Tcl</application> version.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar><replaceable>UNIQUENAME</replaceable>_WITH_TCL_VER</makevar></entry>
 	      <entry>Like <makevar>WITH_TCL_VER</makevar>, but
 		per-port.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_TCL_THREADS</makevar></entry>
 	      <entry>Require a threaded build of
 		<application>Tcl/Tk</application>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_TK</makevar></entry>
 	      <entry>The port depends on the
 		<application>Tk</application> library (not the wish
 		shell).  Implies <makevar>USE_TCL</makevar> with the
 		same value.  For more information see the description
 		of <makevar>USE_TCL</makevar> variable.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_TK_BUILD</makevar></entry>
 	      <entry>Analog to the <makevar>USE_TCL_BUILD</makevar>
 		variable.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_TK_WRAPPER</makevar></entry>
 	      <entry>Analog to the <makevar>USE_TCL_WRAPPER</makevar>
 		variable.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>WITH_TK_VER</makevar></entry>
 	      <entry>Analog to the <makevar>WITH_TCL_VER</makevar>
 		variable and implies <makevar>WITH_TCL_VER</makevar>
 		of the same value.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>A complete list of available variables can be found in
 	<filename>/usr/ports/Mk/bsd.tcl.mk</filename>.</para>
     </sect1>
 
     <sect1 id="using-emacs">
       <title>Using Emacs</title>
 
       <para>This section is yet to be written.</para>
     </sect1>
 
     <sect1 id="using-ruby">
       <title>Using Ruby</title>
 
       <table frame="none">
 	<title>Useful Variables for Ports That Use Ruby</title>
 
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Variable</entry>
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
 	      <entry><makevar>USE_RUBY</makevar></entry>
 	      <entry>The port requires Ruby.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_RUBY_EXTCONF</makevar></entry>
 	      <entry>The port uses <filename>extconf.rb</filename> to
 		configure.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_RUBY_SETUP</makevar></entry>
 	      <entry>The port uses <filename>setup.rb</filename> to
 		configure.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>RUBY_SETUP</makevar></entry>
 	      <entry>Set to the alternative name of
 		<filename>setup.rb</filename>.  Common value is
 		<filename>install.rb</filename>.</entry>
 	    </row>
 
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>The following table shows the selected variables available
 	to port authors via the ports infrastructure.  These variables
 	should be used to install files into their proper locations.
 	Use them in <filename>pkg-plist</filename> as much as
 	possible.  These variables should not be redefined in the
 	port.</para>
 
       <table frame="none">
 	<title>Selected Read-Only Variables for Ports That Use
 	  Ruby</title>
 
 	<tgroup cols="3">
 	  <thead>
 	    <row>
 	      <entry>Variable</entry>
 	      <entry>Description</entry>
 	      <entry>Example value</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 
 	    <row>
 	      <entry><makevar>RUBY_PKGNAMEPREFIX</makevar></entry>
 	      <entry>Used as a <makevar>PKGNAMEPREFIX</makevar> to
 		distinguish packages for different Ruby
 		versions.</entry>
 	      <entry><literal>ruby18-</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>RUBY_VERSION</makevar></entry>
 	      <entry>Full version of Ruby in the form of
 		<literal>x.y.z</literal>.</entry>
 	      <entry><literal>1.8.2</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>RUBY_SITELIBDIR</makevar></entry>
 	      <entry>Architecture independent libraries installation
 		path.</entry>
 	      <entry><literal>/usr/local/lib/ruby/site_ruby/1.8</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>RUBY_SITEARCHLIBDIR</makevar></entry>
 	      <entry>Architecture dependent libraries installation
 		path.</entry>
 	      <entry><literal>/usr/local/lib/ruby/site_ruby/1.8/amd64-freebsd6</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>RUBY_MODDOCDIR</makevar></entry>
 	      <entry>Module documentation installation path.</entry>
 	      <entry><literal>/usr/local/share/doc/ruby18/patsy</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>RUBY_MODEXAMPLESDIR</makevar></entry>
 	      <entry>Module examples installation path.</entry>
 	      <entry><literal>/usr/local/share/examples/ruby18/patsy</literal></entry>
 	    </row>
 
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>A complete list of available variables can be found in
 	<filename>/usr/ports/Mk/bsd.ruby.mk</filename>.</para>
 
     </sect1>
 
     <sect1 id="using-sdl">
       <title>Using SDL</title>
 
       <para>The <makevar>USE_SDL</makevar> variable is used to
 	autoconfigure the dependencies for ports which use an SDL
 	based library like <filename
 	  role="package">devel/sdl12</filename> and <filename
 	  role="package">x11-toolkits/sdl_gui</filename>.</para>
 
       <para>The following SDL libraries are recognized at the
 	moment:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>sdl: <filename
 	      role="package">devel/sdl12</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>gfx: <filename
 	      role="package">graphics/sdl_gfx</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>gui: <filename
 	      role="package">x11-toolkits/sdl_gui</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>image: <filename
 	      role="package">graphics/sdl_image</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>ldbad: <filename
 	      role="package">devel/sdl_ldbad</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>mixer: <filename
 	      role="package">audio/sdl_mixer</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>mm: <filename
 	      role="package">devel/sdlmm</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>net: <filename
 	      role="package">net/sdl_net</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>sound: <filename
 	      role="package">audio/sdl_sound</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>ttf: <filename
 	      role="package">graphics/sdl_ttf</filename></para>
 	</listitem>
       </itemizedlist>
 
       <para>Therefore, if a port has a dependency on
 	<filename role="package">net/sdl_net</filename> and
 	<filename role="package">audio/sdl_mixer</filename>,
 	the syntax will be:</para>
 
       <programlisting>USE_SDL=	net mixer</programlisting>
 
       <para>The dependency <filename
 	  role="package">devel/sdl12</filename>, which is required by
 	<filename role="package">net/sdl_net</filename> and <filename
 	  role="package">audio/sdl_mixer</filename>, is automatically
 	added as well.</para>
 
       <para>If you use <makevar>USE_SDL</makevar>, it will
 	automatically:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Add a dependency on
 	    <application>sdl12-config</application> to
 	    <makevar>BUILD_DEPENDS</makevar></para>
 	</listitem>
 
 	<listitem>
 	  <para>Add the variable <makevar>SDL_CONFIG</makevar> to
 	    <makevar>CONFIGURE_ENV</makevar></para>
 	</listitem>
 
 	<listitem>
 	  <para>Add the dependencies of the selected libraries to the
 	    <makevar>LIB_DEPENDS</makevar></para>
 	</listitem>
       </itemizedlist>
 
       <para>To check whether an SDL library is available, you can do
 	it with the <makevar>WANT_SDL</makevar> variable:</para>
 
       <programlisting>WANT_SDL=	yes
 
 .include &lt;bsd.port.pre.mk&gt;
 
 .if ${HAVE_SDL:Mmixer}!=""
 USE_SDL+=	mixer
 .endif
 
 .include &lt;bsd.port.post.mk&gt;</programlisting>
     </sect1>
 
     <sect1 id="using-wx">
       <title>Using <application>wxWidgets</application></title>
 
       <para>This section describes the status of the
 	<application>wxWidgets</application> libraries in the ports
 	tree and its integration with the ports system.</para>
 
       <sect2 id="wx-introduction">
 	<title>Introduction</title>
 
 	<para>There are many versions of the
 	  <application>wxWidgets</application> libraries which
 	  conflict between them (install files under the same name).
 	  In the ports tree this problem has been solved by installing
 	  each version under a different name using version number
 	  suffixes.</para>
 
 	<para>The obvious disadvantage of this is that each
 	  application has to be modified to find the expected version.
 	  Fortunately, most of the applications call the
 	  <command>wx-config</command> script to determine the
 	  necessary compiler and linker flags.  The script is named
 	  differently for every available version.  Majority of
 	  applications respect an environment variable, or accept a
 	  configure argument, to specify which
 	  <command>wx-config</command> script to call.  Otherwise they
 	  have to be patched.</para>
       </sect2>
 
       <sect2 id="wx-version">
 	<title>Version Selection</title>
 
 	<para>To make your port use a specific version of
 	  <application>wxWidgets</application> there are two variables
 	  available for defining (if only one is defined the other
 	  will be set to a default value):</para>
 
 	<table id="wx-ver-sel-table" frame="none">
 	  <title>Variables to Select
 	    <application>wxWidgets</application> Versions</title>
 
 	  <tgroup cols="3">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Description</entry>
 		<entry>Default value</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_WX</makevar></entry>
 		<entry>List of versions the port can use</entry>
 		<entry>All available versions</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_WX_NOT</makevar></entry>
 		<entry>List of versions the port can not use</entry>
 		<entry>None</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>The following is a list of available
 	  <application>wxWidgets</application> versions and the
 	  corresponding ports in the tree:</para>
 
 	<table frame="none">
 	  <title>Available <application>wxWidgets</application>
 	    Versions</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Version</entry>
 		<entry>Port</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>2.4</literal></entry>
 		<entry><filename
 		    role="package">x11-toolkits/wxgtk24</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>2.6</literal></entry>
 		<entry><filename
 		    role="package">x11-toolkits/wxgtk26</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>2.8</literal></entry>
 		<entry><filename
 		    role="package">x11-toolkits/wxgtk28</filename></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<note>
 	  <para>The versions starting from <literal>2.5</literal> also
 	    come in Unicode version and are installed by a slave port
 	    named like the normal one plus a
 	    <literal>-unicode</literal> suffix, but this can be
 	    handled with variables (see <xref
 	      linkend="wx-unicode"/>).</para>
 	</note>
 
 	<para>The variables in <xref linkend="wx-ver-sel-table"/> can
 	  be set to one or more of the following combinations
 	  separated by spaces:</para>
 
 	<table frame="none">
 	  <title><application>wxWidgets</application> Version
 	    Specifications</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Description</entry>
 		<entry>Example</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry>Single version</entry>
 		<entry><literal>2.4</literal></entry>
 	      </row>
 
 	      <row>
 		<entry>Ascending range</entry>
 		<entry><literal>2.4+</literal></entry>
 	      </row>
 
 	      <row>
 		<entry>Descending range</entry>
 		<entry><literal>2.6-</literal></entry>
 	      </row>
 
 	      <row>
 		<entry>Full range (must be ascending)</entry>
 		<entry><literal>2.4-2.6</literal></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>There are also some variables to select the preferred
 	  versions from the available ones.  They can be set to a list
 	  of versions, the first ones will have higher
 	  priority.</para>
 
 	<table frame="none">
 	  <title>Variables to Select Preferred
 	    <application>wxWidgets</application> Versions</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Designed for</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>WANT_WX_VER</makevar></entry>
 		<entry>the port</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WITH_WX_VER</makevar></entry>
 		<entry>the user</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
       </sect2>
 
       <sect2 id="wx-components">
 	<title>Component Selection</title>
 
 	<para>There are other applications that, while not being
 	  <application>wxWidgets</application> libraries, are related
 	  to them.  These applications can be specified in the
 	  <makevar>WX_COMPS</makevar> variable.  The following
 	  components are available:</para>
 
 	<table frame="none">
 	  <title>Available <application>wxWidgets</application>
 	    Components</title>
 
 	  <tgroup cols="3">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 		<entry>Version restriction</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>wx</literal></entry>
 		<entry>main library</entry>
 		<entry>none</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>contrib</literal></entry>
 		<entry>contributed libraries</entry>
 		<entry><literal>none</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>python</literal></entry>
 		<entry><application>wxPython</application>
 		  (<application>Python</application> bindings)</entry>
 		<entry><literal>2.4-2.6</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>mozilla</literal></entry>
 		<entry><application>wxMozilla</application></entry>
 		<entry><literal>2.4</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>svg</literal></entry>
 		<entry><application>wxSVG</application></entry>
 		<entry><literal>2.6</literal></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>The dependency type can be selected for each component
 	  by adding a suffix separated by a semicolon.  If not present
 	  then a default type will be used (see <xref
 	    linkend="wx-def-dep-types"/>).  The following types are
 	  available:</para>
 
 	<table frame="none">
 	  <title>Available <application>wxWidgets</application>
 	    Dependency Types</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>build</literal></entry>
 		<entry>Component is required for building, equivalent
 		  to <makevar>BUILD_DEPENDS</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>run</literal></entry>
 		<entry>Component is required for running, equivalent
 		  to <makevar>RUN_DEPENDS</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>lib</literal></entry>
 		<entry>Component is required for building and running,
 		  equivalent to <makevar>LIB_DEPENDS</makevar></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>The default values for the components are detailed in
 	  the following table:</para>
 
 	<table id="wx-def-dep-types" frame="none">
 	  <title>Default <application>wxWidgets</application>
 	    Dependency Types</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Component</entry>
 		<entry>Dependency type</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>wx</literal></entry>
 		<entry><literal>lib</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>contrib</literal></entry>
 		<entry><literal>lib</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>python</literal></entry>
 		<entry><literal>run</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>mozilla</literal></entry>
 		<entry><literal>lib</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>svg</literal></entry>
 		<entry><literal>lib</literal></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<example id="wx-components-example">
 	  <title>Selecting <application>wxWidgets</application>
 	    Components</title>
 
 	  <para>The following fragment corresponds to a port which
 	    uses <application>wxWidgets</application> version
 	    <literal>2.4</literal> and its contributed
 	    libraries.</para>
 
 	  <programlisting>USE_WX=		2.4
 WX_COMPS=	wx contrib</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="wx-unicode">
 	<title>Unicode</title>
 
 	<para>The <application>wxWidgets</application> library
 	  supports Unicode since version <literal>2.5</literal>.  In
 	  the ports tree both versions are available and can be
 	  selected with the following variables:</para>
 
 	<table id="wx-unicode-var-table" frame="none">
 	  <title>Variables to Select Unicode in
 	    <application>wxWidgets</application>
 	    Versions</title>
 
 	  <tgroup cols="3">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Description</entry>
 		<entry>Designed for</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>WX_UNICODE</makevar></entry>
 		<entry>The port works <emphasis>only</emphasis> with
 		  the Unicode version</entry>
 		<entry>the port</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WANT_UNICODE</makevar></entry>
 		<entry>The port works with both versions but prefers
 		  the Unicode one</entry>
 		<entry>the port</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WITH_UNICODE</makevar></entry>
 		<entry>The port will use the Unicode version</entry>
 		<entry>the user</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WITHOUT_UNICODE</makevar></entry>
 		<entry>The port will use the normal version if
 		  supported (when <makevar>WX_UNICODE</makevar> is not
 		  defined)</entry>
 		<entry>the user</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<warning>
 	  <para>Do not use <makevar>WX_UNICODE</makevar> for ports
 	    that can use both Unicode and normal versions.  If you
 	    want the port to use Unicode by default define
 	    <makevar>WANT_UNICODE</makevar> instead.</para>
 	</warning>
       </sect2>
 
       <sect2 id="wx-version-detection">
 	<title>Detecting Installed Versions</title>
 
 	<para>To detect an installed version you have to define
 	  <makevar>WANT_WX</makevar>.  If you do not set it to a
 	  specific version then the components will have a version
 	  suffix.  The <makevar>HAVE_WX</makevar> variable will be
 	  filled after detection.</para>
 
 	<example id="wx-ver-det-example">
 	  <title>Detecting Installed
 	    <application>wxWidgets</application> Versions and
 	    Components</title>
 
 	  <para>The following fragment can be used in a port that uses
 	    <application>wxWidgets</application> if it is installed,
 	    or an option is selected.</para>
 
 	  <programlisting>WANT_WX=	yes
 
 .include &lt;bsd.port.pre.mk&gt;
 
 .if defined(WITH_WX) || !empty(PORT_OPTIONS:MWX) || !empty(HAVE_WX:Mwx-2.4)
 USE_WX=			2.4
 CONFIGURE_ARGS+=	--enable-wx
 .endif</programlisting>
 
 	  <para>The following fragment can be used in a port that
 	    enables <application>wxPython</application> support if it
 	    is installed or if an option is selected, in addition to
 	    <application>wxWidgets</application>, both version
 	    <literal>2.6</literal>.</para>
 
 	  <programlisting>USE_WX=		2.6
 WX_COMPS=	wx
 WANT_WX=	2.6
 
 .include &lt;bsd.port.pre.mk&gt;
 
 .if defined(WITH_WXPYTHON) || !empty(PORT_OPTIONS:MWXPYTHON) || !empty(HAVE_WX:Mpython)
 WX_COMPS+=		python
 CONFIGURE_ARGS+=	--enable-wxpython
 .endif</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="wx-defined-variables">
 	<title>Defined Variables</title>
 
 	<para>The following variables are available in the port (after
 	  defining one from
 	  <xref linkend="wx-ver-sel-table"/>).</para>
 
 	<table frame="none">
 	  <title>Variables Defined for Ports That Use
 	    <application>wxWidgets</application></title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>WX_CONFIG</makevar></entry>
 		<entry>The path to the
 		  <application>wxWidgets</application>
 		  <command>wx-config</command> script (with different
 		  name)</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WXRC_CMD</makevar></entry>
 		<entry>The path to the
 		  <application>wxWidgets</application>
 		  <command>wxrc</command> program (with different
 		  name)</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WX_VERSION</makevar></entry>
 		<entry>The <application>wxWidgets</application>
 		  version that is going to be used (e.g.,
 		  <literal>2.6</literal>)</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WX_UNICODE</makevar></entry>
 		<entry>If not defined but Unicode is going to be used
 		  then it will be defined</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
       </sect2>
 
       <sect2 id="wx-premk">
 	<title>Processing in
 	  <filename>bsd.port.pre.mk</filename></title>
 
 	<para>If you need to use the variables for running commands
 	  right after including <filename>bsd.port.pre.mk</filename>
 	  you need to define <makevar>WX_PREMK</makevar>.</para>
 
 	<important>
 	  <para>If you define <makevar>WX_PREMK</makevar>, then the
 	    version, dependencies, components and defined variables
 	    will not change if you modify the
 	    <application>wxWidgets</application> port variables
 	    <emphasis>after</emphasis> including
 	    <filename>bsd.port.pre.mk</filename>.</para>
 	</important>
 
 	<example id="wx-premk-example">
 	  <title>Using <application>wxWidgets</application> Variables
 	    in Commands</title>
 
 	  <para>The following fragment illustrates the use of
 	    <makevar>WX_PREMK</makevar> by running the
 	    <command>wx-config</command> script to obtain the full
 	    version string, assign it to a variable and pass it to the
 	    program.</para>
 
 	  <programlisting>USE_WX=		2.4
 WX_PREMK=	yes
 
 .include &lt;bsd.port.pre.mk&gt;
 
 .if exists(${WX_CONFIG})
 VER_STR!=	${WX_CONFIG} --release
 
 PLIST_SUB+=	VERSION="${VER_STR}"
 .endif</programlisting>
 	</example>
 
 	<note>
 	  <para>The <application>wxWidgets</application> variables can
 	    be safely used in commands when they are inside targets
 	    without the need of <makevar>WX_PREMK</makevar>.</para>
 	</note>
       </sect2>
 
       <sect2 id="wx-additional-config-args">
 	<title>Additional <command>configure</command>
 	  Arguments</title>
 
 	<para>Some GNU <command>configure</command> scripts can not
 	  find <application>wxWidgets</application> with just the
 	  <literal>WX_CONFIG</literal> environment variable set,
 	  requiring additional arguments.  The
 	  <makevar>WX_CONF_ARGS</makevar> variable can be used for
 	  provide them.</para>
 
 	<table frame="none">
 	  <title>Legal Values for
 	    <makevar>WX_CONF_ARGS</makevar></title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Possible value</entry>
 		<entry>Resulting argument</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>absolute</literal></entry>
 		<entry><literal>--with-wx-config=${WX_CONFIG}</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>relative</literal></entry>
 		<entry><literal>--with-wx=${LOCALBASE}
 		    --with-wx-config=${WX_CONFIG:T}</literal></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
       </sect2>
     </sect1>
 
     <sect1 id="using-lua">
       <title>Using <application>Lua</application></title>
 
       <para>This section describes the status of the
 	<application>Lua</application> libraries in the ports tree and
 	its integration with the ports system.</para>
 
       <sect2 id="lua-introduction">
 	<title>Introduction</title>
 
 	<para>There are many versions of the
 	  <application>Lua</application> libraries and corresponding
 	  interpreters, which conflict between them (install files
 	  under the same name).  In the ports tree this problem has
 	  been solved by installing each version under a different
 	  name using version number suffixes.</para>
 
 	<para>The obvious disadvantage of this is that each
 	  application has to be modified to find the expected version.
 	  But it can be solved by adding some additional flags to the
 	  compiler and linker.</para>
       </sect2>
 
       <sect2 id="lua-version">
 	<title>Version Selection</title>
 
 	<para>To make your port use a specific version of
 	  <application>Lua</application> there are two variables
 	  available for defining (if only one is defined the other
 	  will be set to a default value):</para>
 
 	<table id="lua-ver-sel-table" frame="none">
 	  <title>Variables to Select <application>Lua</application>
 	    Versions</title>
 
 	  <tgroup cols="3">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 		<entry>Description</entry>
 		<entry>Default value</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>USE_LUA</makevar></entry>
 		<entry>List of versions the port can use</entry>
 		<entry>All available versions</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>USE_LUA_NOT</makevar></entry>
 		<entry>List of versions the port can not use</entry>
 		<entry>None</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>The following is a list of available
 	  <application>Lua</application> versions and the
 	  corresponding ports in the tree:</para>
 
 	<table frame="none">
 	  <title>Available <application>Lua</application>
 	    Versions</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Version</entry>
 		<entry>Port</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>4.0</literal></entry>
 		<entry><filename
 		    role="package">lang/lua4</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>5.0</literal></entry>
 		<entry><filename
 		    role="package">lang/lua50</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>5.1</literal></entry>
 		<entry><filename
 		    role="package">lang/lua</filename></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>The variables in <xref linkend="lua-ver-sel-table"/> can
 	  be set to one or more of the following combinations
 	  separated by spaces:</para>
 
 	<table frame="none">
 	  <title><application>Lua</application> Version
 	    Specifications</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Description</entry>
 		<entry>Example</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry>Single version</entry>
 		<entry><literal>4.0</literal></entry>
 	      </row>
 
 	      <row>
 		<entry>Ascending range</entry>
 		<entry><literal>5.0+</literal></entry>
 	      </row>
 
 	      <row>
 		<entry>Descending range</entry>
 		<entry><literal>5.0-</literal></entry>
 	      </row>
 
 	      <row>
 		<entry>Full range (must be ascending)</entry>
 		<entry><literal>5.0-5.1</literal></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>There are also some variables to select the preferred
 	  versions from the available ones.  They can be set to a list
 	  of versions, the first ones will have higher
 	  priority.</para>
 
 	<table frame="none">
 	  <title>Variables to Select Preferred
 	    <application>Lua</application> Versions</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Designed for</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>WANT_LUA_VER</makevar></entry>
 		<entry>the port</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>WITH_LUA_VER</makevar></entry>
 		<entry>the user</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<example id="lua-version-example">
 	  <title>Selecting the <application>Lua</application>
 	    Version</title>
 
 	  <para>The following fragment is from a port which can use
 	    <application>Lua</application> version
 	    <literal>5.0</literal> or <literal>5.1</literal>, and uses
 	    <literal>5.0</literal> by default.  It can be overridden
 	    by the user with <makevar>WITH_LUA_VER</makevar>.</para>
 
 	  <programlisting>USE_LUA=	5.0-5.1
 WANT_LUA_VER=	5.0</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="lua-components">
 	<title>Component Selection</title>
 
 	<para>There are other applications that, while not being
 	  <application>Lua</application> libraries, are related to
 	  them.  These applications can be specified in the
 	  <makevar>LUA_COMPS</makevar> variable.  The following
 	  components are available:</para>
 
 	<table frame="none">
 	  <title>Available <application>Lua</application>
 	    Components</title>
 
 	  <tgroup cols="3">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 		<entry>Version restriction</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>lua</literal></entry>
 		<entry>main library</entry>
 		<entry>none</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>tolua</literal></entry>
 		<entry>Library for accessing C/C++ code</entry>
 		<entry><literal>4.0-5.0</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>ruby</literal></entry>
 		<entry>Ruby bindings</entry>
 		<entry><literal>4.0-5.0</literal></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<note>
 	  <para>There are more components but they are modules for the
 	    interpreter, not used by applications (only by other
 	    modules).</para>
 	</note>
 
 	<para>The dependency type can be selected for each component
 	  by adding a suffix separated by a semicolon.  If not present
 	  then a default type will be used (see <xref
 	    linkend="lua-def-dep-types"/>).  The following types are
 	  available:</para>
 
 	<table frame="none">
 	  <title>Available <application>Lua</application> Dependency
 	    Types</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>build</literal></entry>
 		<entry>Component is required for building, equivalent
 		  to <makevar>BUILD_DEPENDS</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>run</literal></entry>
 		<entry>Component is required for running, equivalent
 		  to <makevar>RUN_DEPENDS</makevar></entry>
 	      </row>
 
 	      <row>
 		<entry><literal>lib</literal></entry>
 		<entry>Component is required for building and running,
 		  equivalent to <makevar>LIB_DEPENDS</makevar></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<para>The default values for the components are detailed in
 	  the following table:</para>
 
 	<table id="lua-def-dep-types" frame="none">
 	  <title>Default <application>Lua</application> Dependency
 	    Types</title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Component</entry>
 		<entry>Dependency type</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><literal>lua</literal></entry>
 		<entry><literal>lib</literal> for
 		  <literal>4.0-5.0</literal> (shared) and
 		  <literal>build</literal> for <literal>5.1</literal>
 		  (static)</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>tolua</literal></entry>
 		<entry><literal>build</literal> (static)</entry>
 	      </row>
 
 	      <row>
 		<entry><literal>ruby</literal></entry>
 		<entry><literal>lib</literal> (shared)</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<example id="lua-components-example">
 	  <title>Selecting <application>Lua</application>
 	    Components</title>
 
 	  <para>The following fragment corresponds to a port which
 	    uses <application>Lua</application> version
 	    <literal>4.0</literal> and its
 	    <application>Ruby</application> bindings.</para>
 
 	  <programlisting>USE_LUA=	4.0
 LUA_COMPS=	lua ruby</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="lua-version-detection">
 	<title>Detecting Installed Versions</title>
 
 	<para>To detect an installed version you have to define
 	  <makevar>WANT_LUA</makevar>.  If you do not set it to a
 	  specific version then the components will have a version
 	  suffix.  The <makevar>HAVE_LUA</makevar> variable will be
 	  filled after detection.</para>
 
 	<example id="lua-ver-det-example">
 	  <title>Detecting Installed <application>Lua</application>
 	    Versions and Components</title>
 
 	  <para>The following fragment can be used in a port that uses
 	    <application>Lua</application> if it is installed, or an
 	    option is selected.</para>
 
 	  <programlisting>WANT_LUA=	yes
 
 .include &lt;bsd.port.pre.mk&gt;
 
 .if defined(WITH_LUA5) || !empty(PORT_OPTIONS:MLUA5) || !empty(HAVE_LUA:Mlua-5.[01])
 USE_LUA=		5.0-5.1
 CONFIGURE_ARGS+=	--enable-lua5
 .endif</programlisting>
 
 	  <para>The following fragment can be used in a port that
 	    enables <application>tolua</application> support if it is
 	    installed or if an option is selected, in addition to
 	    <application>Lua</application>, both version
 	    <literal>4.0</literal>.</para>
 
 	  <programlisting>USE_LUA=	4.0
 LUA_COMPS=	lua
 WANT_LUA=	4.0
 
 .include &lt;bsd.port.pre.mk&gt;
 
 .if defined(WITH_TOLUA) || !empty(PORT_OPTIONS:MTOLUA) || !empty(HAVE_LUA:Mtolua)
 LUA_COMPS+=		tolua
 CONFIGURE_ARGS+=	--enable-tolua
 .endif</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="lua-defined-variables">
 	<title>Defined Variables</title>
 
 	<para>The following variables are available in the port (after
 	  defining one from <xref
 	    linkend="lua-ver-sel-table"/>).</para>
 
 	<table frame="none">
 	  <title>Variables Defined for Ports That Use
 	    <application>Lua</application></title>
 
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry><makevar>LUA_VER</makevar></entry>
 		<entry>The <application>Lua</application> version that
 		  is going to be used (e.g.,
 		  <literal>5.1</literal>)</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_VER_SH</makevar></entry>
 		<entry>The <application>Lua</application> shared
 		  library major version (e.g.,
 		  <literal>1</literal>)</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_VER_STR</makevar></entry>
 		<entry>The <application>Lua</application> version
 		  without the dots (e.g.,
 		  <literal>51</literal>)</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_PREFIX</makevar></entry>
 		<entry>The prefix where <application>Lua</application>
 		  (and components) is installed</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_SUBDIR</makevar></entry>
 		<entry>The directory under
 		  <filename>${PREFIX}/bin</filename>,
 		  <filename>${PREFIX}/share</filename> and
 		  <filename>${PREFIX}/lib</filename> where
 		  <application>Lua</application> is installed</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_INCDIR</makevar></entry>
 		<entry>The directory where
 		  <application>Lua</application> and
 		  <application>tolua</application> header files are
 		  installed</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_LIBDIR</makevar></entry>
 		<entry>The directory where
 		  <application>Lua</application> and
 		  <application>tolua</application> libraries are
 		  installed</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_MODLIBDIR</makevar></entry>
 		<entry>The directory where
 		  <application>Lua</application> module libraries
 		  (<filename>.so</filename>) are installed</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_MODSHAREDIR</makevar></entry>
 		<entry>The directory where
 		  <application>Lua</application> modules
 		  (<filename>.lua</filename>) are installed</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_PKGNAMEPREFIX</makevar></entry>
 		<entry>The package name prefix used by
 		  <application>Lua</application> modules</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUA_CMD</makevar></entry>
 		<entry>The path to the <application>Lua</application>
 		  interpreter</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>LUAC_CMD</makevar></entry>
 		<entry>The path to the <application>Lua</application>
 		  compiler</entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>TOLUA_CMD</makevar></entry>
 		<entry>The path to the
 		  <application>tolua</application> program</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</table>
 
 	<example id="lua-variables-example">
 	  <title>Telling the Port Where to Find
 	    <application>Lua</application></title>
 
 	  <para>The following fragment shows how to tell a port that
 	    uses a configure script where the
 	    <application>Lua</application> header files and libraries
 	    are.</para>
 
 	  <programlisting>USE_LUA=	4.0
 GNU_CONFIGURE=	yes
 CONFIGURE_ENV=	CPPFLAGS="-I${LUA_INCDIR}" LDFLAGS="-L${LUA_LIBDIR}"</programlisting>
 	</example>
       </sect2>
 
       <sect2 id="lua-premk">
 	<title>Processing in
 	  <filename>bsd.port.pre.mk</filename></title>
 
 	<para>If you need to use the variables for running commands
 	  right after including <filename>bsd.port.pre.mk</filename>
 	  you need to define <makevar>LUA_PREMK</makevar>.</para>
 
 	<important>
 	  <para>If you define <makevar>LUA_PREMK</makevar>, then the
 	    version, dependencies, components and defined variables
 	    will not change if you modify the
 	    <application>Lua</application> port variables
 	    <emphasis>after</emphasis> including
 	    <filename>bsd.port.pre.mk</filename>.</para>
 	</important>
 
 	<example id="lua-premk-example">
 	  <title>Using <application>Lua</application> Variables in
 	    Commands</title>
 
 	  <para>The following fragment illustrates the use of
 	    <makevar>LUA_PREMK</makevar> by running the
 	    <application>Lua</application> interpreter to obtain the
 	    full version string, assign it to a variable and pass it
 	    to the program.</para>
 
 	  <programlisting>USE_LUA=	5.0
 LUA_PREMK=	yes
 
 .include &lt;bsd.port.pre.mk&gt;
 
 .if exists(${LUA_CMD})
 VER_STR!=	${LUA_CMD} -v
 
 CFLAGS+=	-DLUA_VERSION_STRING="${VER_STR}"
 .endif</programlisting>
 	</example>
 
 	<note>
 	  <para>The <application>Lua</application> variables can be
 	    safely used in commands when they are inside targets
 	    without the need of <makevar>LUA_PREMK</makevar>.</para>
 	</note>
       </sect2>
     </sect1>
 
     <sect1 id="using-xfce">
       <title>Using Xfce</title>
 
       <para>The <makevar>USE_XFCE</makevar> variable is used to
 	autoconfigure the dependencies for ports which use an Xfce
 	based library or application like <filename
 	  role="package">x11-toolkits/libxfce4gui</filename> and
 	<filename role="package">x11-wm/xfce4-panel</filename>.</para>
 
       <para>The following Xfce libraries and applications are
 	recognized at the moment:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>libexo: <filename
 	      role="package">x11/libexo</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>libgui: <filename
 	      role="package">x11-toolkits/libxfce4gui</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>libutil: <filename
 	      role="package">x11/libxfce4util</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>libmcs: <filename
 	      role="package">x11/libxfce4mcs</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>mcsmanager: <filename
 	      role="package">sysutils/xfce4-mcs-manager</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>panel: <filename
 	      role="package">x11-wm/xfce4-panel</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>thunar: <filename
 	      role="package">x11-fm/thunar</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>wm: <filename
 	      role="package">x11-wm/xfce4-wm</filename></para>
 	</listitem>
 
 	<listitem>
 	  <para>xfdev: <filename
 	      role="package">dev/xfce4-dev-tools</filename></para>
 	</listitem>
       </itemizedlist>
 
       <para>The following additional parameters are recognized:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>configenv: Use this if your port requires a special
 	    modified <makevar>CONFIGURE_ENV</makevar> to find its
 	    required libraries.</para>
 
 	  <programlisting>-I&dollar;{LOCALBASE}/include -L&dollar;{LOCALBASE}/lib</programlisting>
 
 	  <para>gets added to CPPFLAGS to
 	    <makevar>CONFIGURE_ENV</makevar>.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Therefore, if a port has a dependency on <filename
 	  role="package">sysutils/xfce4-mcs-manager</filename> and
 	requires the special CPPFLAGS in its configure environment,
 	the syntax will be:</para>
 
       <programlisting>USE_XFCE=	mcsmanager configenv</programlisting>
     </sect1>
 
     <sect1 id="using-mozilla">
       <title>Using Mozilla</title>
 
       <table frame="none">
 	<title>Variables for Ports That Use Mozilla</title>
 
 	<tgroup cols="2">
 	  <tbody>
 
 	    <row>
 	      <entry><makevar>USE_GECKO</makevar></entry>
 	      <entry>Gecko backend the port can handle.  Possible
 		values: <literal>libxul</literal>
 		(<filename>libxul.so</filename>),
 		<literal>seamonkey</literal>
 		(<filename>libgtkembedmoz.so</filename>, deprecated,
 		should not be used any more).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_FIREFOX</makevar></entry>
 	      <entry>The port requires Firefox as a runtime
 		dependency.  Possible values: <literal>yes</literal>
 		(get default version), <literal>40</literal>,
 		<literal>36</literal>, <literal>35</literal>.  Default
 		dependency is on version
 		<literal>40</literal>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_FIREFOX_BUILD</makevar></entry>
 	      <entry>The port requires Firefox as a buildtime
 		dependency.  Possible values: see USE_FIREFOX.  This
 		automatically sets USE_FIREFOX and assigns the same
 		value.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_SEAMONKEY</makevar></entry>
 	      <entry>The port requires SeaMonkey as a runtime
 		dependency.  Possible values: <literal>yes</literal>
 		(get default version), <literal>20</literal>,
 		<literal>11</literal> (deprecated, should not be used
 		any more).  Default dependency is on version
 		<literal>20</literal>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_SEAMONKEY_BUILD</makevar></entry>
 	      <entry>The port requires SeaMonkey as a buildtime
 		dependency.  Possible values: see USE_SEAMONKEY.  This
 		automatically sets USE_SEAMONKEY and assigns the same
 		value.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_THUNDERBIRD</makevar></entry>
 	      <entry>The port requires Thunderbird as a runtime
 		dependency.  Possible values: <literal>yes</literal>
 		(get default version), <literal>31</literal>,
 		<literal>30</literal> (deprecated, should not be used
 		any more).  Default dependency is on version
 		<literal>31</literal>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_THUNDERBIRD_BUILD</makevar></entry>
 	      <entry>The port requires Thunderbird as a buildtime
 		dependency.  Possible values: see USE_THUNDERBIRD.
 		This automatically sets USE_THUNDERBIRD and assigns
 		the same value.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>A complete list of available variables can be found in
 	<filename>/usr/ports/Mk/bsd.gecko.mk</filename>.</para>
     </sect1>
 
     <sect1 id="using-databases">
       <title>Using Databases</title>
 
       <table frame="none">
 	<title>Variables for Ports Using Databases</title>
 
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Variable</entry>
 	      <entry>Means</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><makevar>USE_BDB</makevar></entry>
 	      <entry>If variable is set to <literal>yes</literal>,
 		add dependency on <filename
 		  role="package">databases/db41</filename> port.  The
 		variable may also be set to values: 40, 41, 42, 43,
 		44, 46, 47, 48, or 51.  You can declare a range of
 		acceptable values, <makevar>USE_BDB</makevar>=42+ will
 		find the highest installed version, and fall back to
 		42 if nothing else is installed.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_MYSQL</makevar></entry>
 	      <entry>If variable is set to <literal>yes</literal>, add
 		dependency on <filename
 		  role="package">databases/mysql55-client</filename>
 		port.  An associated variable,
 		<makevar>WANT_MYSQL_VER</makevar>, may be set to
 		values such as 323, 40, 41, 50, 51, 52, 55, or
 		60.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_PGSQL</makevar></entry>
 	      <entry>If set to <literal>yes</literal>, add dependency
 		on <filename
 		  role="package">databases/postgresql90-client</filename>
 		port.  An associated variable,
 		<makevar>WANT_PGSQL_VER</makevar>, may be set to
 		values such as 83, 84, 90, 91 or 92.  You can declare
 		a minimum or maximum value;
 		<makevar>WANT_PGSQL_VER</makevar>=
 		<literal> 90+</literal> will cause the
 		port to depend on a minimum version of 9.0.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_SQLITE</makevar></entry>
 	      <entry>If variable is set to <literal>yes</literal>, add
 		dependency on
 		<filename role="package">databases/sqlite3</filename>
 		port.  The variable may also be set to values: 3,
 		2.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>More details are available in <ulink
-	  url="http://svn.FreeBSD.org/ports/head/Mk/bsd.database.mk?view=markup">bsd.database.mk</ulink>.</para>
+	  url="http://svnweb.FreeBSD.org/ports/head/Mk/bsd.database.mk?view=markup">bsd.database.mk</ulink>.</para>
     </sect1>
 
     <sect1 id="rc-scripts">
       <title>Starting and Stopping Services (<literal>rc</literal>
 	Scripts)</title>
 
       <para><filename>rc.d</filename> scripts are used to start
 	services on system startup, and to give administrators a
 	standard way of stopping, starting and restarting the service.
 	Ports integrate into the system <filename>rc.d</filename>
 	framework.  Details on its usage can be found in <ulink
 	  url="&url.books.handbook;/configtuning-rcd.html">the rc.d
 	  Handbook chapter</ulink>.  Detailed explanation of available
 	commands is provided in &man.rc.8; and &man.rc.subr.8;.
 	Finally, there is <ulink url="&url.articles.rc-scripting;">an
 	  article</ulink> on practical aspects of
 	<filename>rc.d</filename> scripting.</para>
 
       <para>One or more <filename>rc.d</filename> scripts can be
 	installed:</para>
 
       <programlisting>USE_RC_SUBR=	doormand</programlisting>
 
       <para>Scripts must be placed in the <filename>files</filename>
 	subdirectory and a <literal>.in</literal> suffix must be added
 	to their filename.  Standard <makevar>SUB_LIST</makevar>
 	expansions will be used for this file.  Use of the
 	<literal>%%PREFIX%%</literal> and
 	<literal>%%LOCALBASE%%</literal> expansions is strongly
 	encouraged as well.  More on <makevar>SUB_LIST</makevar> in
 	<link
 	  linkend="using-sub-files">the relevant
 	  section</link>.</para>
 
       <para>Prior to &os;&nbsp;6.1-RELEASE, integration with
 	&man.rcorder.8; is available by using
 	<makevar>USE_RCORDER</makevar> instead of
 	<makevar>USE_RC_SUBR</makevar>.  However, use of this method
 	is not necessary unless the port has an option to install
 	itself in the base, or the service needs to run prior to the
 	<filename>FILESYSTEMS</filename> <filename>rc.d</filename>
 	script in the base.</para>
 
       <para>As of &os;&nbsp;6.1-RELEASE, local
 	<filename>rc.d</filename> scripts (including those installed
 	by ports) are included in the overall &man.rcorder.8; of the
 	base system.</para>
 
       <para>Example simple <filename>rc.d</filename> script:</para>
 
       <programlisting>#!/bin/sh
 
 # &dollar;FreeBSD&dollar;
 #
 # PROVIDE: doormand
 # REQUIRE: LOGIN
 # KEYWORD: shutdown
 #
 # Add the following lines to /etc/rc.conf.local or /etc/rc.conf
 # to enable this service:
 #
 # doormand_enable (bool):	Set to NO by default.
 #				Set it to YES to enable doormand.
 # doormand_config (path):	Set to %%PREFIX%%/etc/doormand/doormand.cf
 #				by default.
 
 . /etc/rc.subr
 
 name=doormand
 rcvar=doormand_enable
 
 load_rc_config $name
 
 : ${doormand_enable:="NO"}
 : ${doormand_config="%%PREFIX%%/etc/doormand/doormand.cf"}
 
 command=%%PREFIX%%/sbin/${name}
 pidfile=/var/run/${name}.pid
 
 command_args="-p $pidfile -f $doormand_config"
 
 run_rc_command "$1"</programlisting>
 
       <para> Unless there is a good reason to start the service
 	earlier all ports scripts should use</para>
 
       <programlisting>REQUIRE: LOGIN</programlisting>
 
       <para>If the service runs as a particular user (other than root)
 	this is mandatory.</para>
 
       <programlisting>KEYWORD: shutdown</programlisting>
 
       <para>is included in the script above because the mythical port
 	we are using as an example starts a service, and should be
 	shut down cleanly when the system shuts down.  If the script
 	is not starting a persistent service this is not
 	necessary.</para>
 
       <para>For optional configuration elements the &quot;=&quot;
 	style of default variable assignment is preferable to the
 	&quot;:=&quot; style here, since the former sets a default
 	value only if the variable is unset, and the latter sets one
 	if the variable is unset <emphasis>or</emphasis> null.  A user
 	might very well include something like</para>
 
       <programlisting>doormand_flags=""</programlisting>
 
       <para>in their <filename>rc.conf.local</filename> file, and a
 	variable substitution using &quot;:=&quot; would
 	inappropriately override the user's intention.  The
 	<literal>_enable</literal> variable is not optional,
 	and should use the &quot;:&quot; for the default.</para>
 
       <note>
 	<para>No new scripts should be added with the
 	  <filename>.sh</filename> suffix.</para>
       </note>
 
       <sect2>
 	<title>Pre-Commit Checklist</title>
 
 	<para>Before contributing a port with an
 	  <filename>rc.d</filename> script, and more importantly,
 	  before committing one, please consult the following
 	  checklist to be sure that it is ready.</para>
 
 	<procedure>
 	  <step>
 	    <para>If this is a new file, does it have
 	      <filename>.sh</filename> in the file name?  If so that
 	      should be changed to just <filename>file.in</filename>
 	      since new <filename>rc.d</filename> files may not end
 	      with that extension.</para>
 	  </step>
 
 	  <step>
 	    <para>Does the file have a
 	      <literal>&dollar;FreeBSD&dollar;</literal> tag?</para>
 	  </step>
 
 	  <step>
 	    <para>Do the name of the file (minus
 	      <filename>.in</filename>), the
 	      <literal>PROVIDE</literal> line, and
 	      <literal>&dollar;</literal><replaceable>name</replaceable>
 	      all match?  The file name matching
 	      <literal>PROVIDE</literal> makes debugging easier,
 	      especially for &man.rcorder.8; issues.  Matching the
 	      file name and
 	      <literal>&dollar;</literal><replaceable>name</replaceable>
 	      makes it easier to figure out which variables are
 	      relevant in <filename>rc.conf[.local]</filename>.  The
 	      latter is also what you might call &ldquo;policy&rdquo;
 	      for all new scripts, including those in the base
 	      system.</para>
 	  </step>
 
 	  <step>
 	    <para>Is the <literal>REQUIRE</literal> line set to
 	      <literal>LOGIN</literal>?  This is mandatory for scripts
 	      that run as a non-root user.  If it runs as root, is
 	      there a good reason for it to run prior to
 	      <literal>LOGIN</literal>?  If not, it should run there
 	      so that we can loosely group local scripts to a point in
 	      &man.rcorder.8; after most everything in the base is
 	      already running.</para>
 	  </step>
 
 	  <step>
 	    <para>Does the script start a persistent service?  If so,
 	      it should have <literal>KEYWORD:
 		shutdown</literal>.</para>
 	  </step>
 
 	  <step>
 
 	    <para>Make sure there is no <literal>KEYWORD:
 		FreeBSD</literal> present.  This has not been
 	      necessary or desirable for years.  It is also an
 	      indication that the new script was copy/pasted from an
 	      old script, so extra caution should be given to the
 	      review.</para>
 	  </step>
 
 	  <step>
 	    <para>If the script uses an interpreted language like
 	      <command>perl</command>, <command>python</command>, or
 	      <command>ruby</command>, make certain that
 	      <varname>command_interpreter</varname> is set
 	      appropriately.  Otherwise,</para>
 
 	    <screen>&prompt.root; <userinput>service <replaceable>name</replaceable> stop</userinput></screen>
 
 	    <para>will probably not work properly.  See
 	      &man.service.8; for more information.</para>
 	  </step>
 
 	  <step>
 	    <para>Have all occurrences of
 	      <filename>/usr/local</filename> been replaced with
 	      <literal>%%PREFIX%%</literal>?</para>
 	  </step>
 
 	  <step>
 	    <para>Do the default variable assignments come after
 	      <function>load_rc_config</function>?</para>
 	  </step>
 
 	  <step>
 	    <para>Are there default assignments to empty strings?
 	      They should be removed, but double-check that the option
 	      is documented in the comments at the top of the
 	      file.</para>
 	  </step>
 
 	  <step>
 	    <para>Are things that are set in variables actually used
 	      in the script?</para>
 	  </step>
 
 	  <step>
 	    <para>Are options listed in the default
 	      <replaceable>name</replaceable><varname>_flags</varname>
 	      things that are actually mandatory?  If so, they should
 	      be in <varname>command_args</varname>.  The
 	      <option>-d</option> option is a red flag (pardon the
 	      pun) here, since it is usually the option to
 	      &ldquo;daemonize&rdquo; the process, and therefore is
 	      actually mandatory.</para>
 	  </step>
 
 	  <step>
 	    <para>The
 	      <replaceable>name</replaceable><varname>_flags</varname>
 	      variable should never be included in
 	      <varname>command_args</varname> (and vice versa,
 	      although that error is less common).</para>
 	  </step>
 
 	  <step>
 	    <para>Does the script execute any code unconditionally?
 	      This is frowned on.  Usually these things can/should be
 	      dealt with through a
 	      <function>start_precmd</function>.</para>
 	  </step>
 
 	  <step>
 	    <para>All boolean tests should utilize the
 	      <function>checkyesno</function> function.  No
 	      hand-rolled tests for <literal>[Yy][Ee][Ss]</literal>,
 	      etc.</para>
 	  </step>
 
 	  <step>
 	    <para>If there is a loop (for example, waiting for
 	      something to start) does it have a counter to terminate
 	      the loop?  We do not want the boot to be stuck forever
 	      if there is an error.</para>
 	  </step>
 
 	  <step>
 	    <para>Does the script create files or directories that
 	      need specific permissions, for example, a
 	      <filename>pid</filename> file that needs to be owned by
 	      the user that runs the process?  Rather than the
 	      traditional &man.touch.1;/&man.chown.8;/&man.chmod.1;
 	      routine, consider using &man.install.1; with the proper
 	      command line arguments to do the whole procedure with
 	      one step.</para>
 	  </step>
 	</procedure>
       </sect2>
     </sect1>
 
     <sect1 id="users-and-groups">
       <title>Adding Users and Groups</title>
 
       <para>Some ports require a certain user to be on the installed
 	system.  Choose a free UID from 50 to 999 and register it
 	either in <filename>ports/UIDs</filename> (for users) or in
 	<filename>ports/GIDs</filename> (for groups).  Make sure you
 	do not use a UID already used by the system or other
 	ports.</para>
 
       <para>Please include a patch against these two files when you
 	require a new user or group to be created for your
 	port.</para>
 
       <para>Then you can use <makevar>USERS</makevar> and
 	<makevar>GROUPS</makevar> variables in your
 	<filename>Makefile</filename>, and the user will be
 	automatically created when installing the port.</para>
 
       <programlisting>USERS=	pulse
 GROUPS=	pulse pulse-access pulse-rt</programlisting>
 
       <para>The current list of reserved UIDs and GIDs can be found
 	in <filename>ports/UIDs</filename> and
 	<filename>ports/GIDs</filename>.</para>
     </sect1>
 
     <sect1 id="requiring-kernel-sources">
       <title>Ports That Rely on Kernel Sources</title>
 
       <para>Some ports (such as kernel loadable modules) need the
 	kernel source files so that the port can compile.  Here is the
 	correct way to determine if the user has them
 	installed:</para>
 
       <programlisting>.if !exists(${SRC_BASE}/sys/Makefile)
 IGNORE=	requires kernel sources to be installed
 .endif</programlisting>
     </sect1>
   </chapter>
 
   <chapter id="plist">
     <title>Advanced <filename>pkg-plist</filename> Practices</title>
 
     <sect1 id="plist-sub">
       <title>Changing <filename>pkg-plist</filename> Based on Make
 	Variables</title>
 
       <para>Some ports, particularly the <literal>p5-</literal> ports,
 	need to change their <filename>pkg-plist</filename> depending
 	on what options they are configured with (or version of
 	<literal>perl</literal>, in the case of <literal>p5-</literal>
 	ports).  To make this easy, any instances in the
 	<filename>pkg-plist</filename> of
 	<literal>%%OSREL%%</literal>, <literal>%%PERL_VER%%</literal>,
 	and <literal>%%PERL_VERSION%%</literal> will be substituted
 	for appropriately.  The value of <literal>%%OSREL%%</literal>
 	is the numeric revision of the operating system (e.g.,
 	<literal>4.9</literal>).  <literal>%%PERL_VERSION%%</literal>
 	and <literal>%%PERL_VER%%</literal> is the full version number
 	of <command>perl</command> (e.g., <literal>5.8.9</literal>).
 	Several other
 	<literal>%%<replaceable>VARS</replaceable>%%</literal> related
 	to port's documentation files are described in <link
 	  linkend="install-documentation">the relevant
 	  section</link>.</para>
 
       <para>If you need to make other substitutions, you can set the
 	<makevar>PLIST_SUB</makevar> variable with a list of
 	<literal><replaceable>VAR</replaceable>=<replaceable>VALUE</replaceable></literal>
 	pairs and instances of
 	<literal>%%<replaceable>VAR</replaceable>%%</literal> will be
 	substituted with <replaceable>VALUE</replaceable> in the
 	<filename>pkg-plist</filename>.</para>
 
       <para>For instance, if you have a port that installs many files
 	in a version-specific subdirectory, you can put something
 	like</para>
 
       <programlisting>OCTAVE_VERSION=	2.0.13
 PLIST_SUB=	OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
 
       <para>in the <filename>Makefile</filename> and use
 	<literal>%%OCTAVE_VERSION%%</literal> wherever the version
 	shows up in <filename>pkg-plist</filename>.  That way, when
 	you upgrade the port, you will not have to change dozens (or
 	in some cases, hundreds) of lines in the
 	<filename>pkg-plist</filename>.</para>
 
       <para>If your port installs files conditionally on the options
 	set in the port, the usual way of handling it is prefixing the
 	<filename>pkg-plist</filename> lines with a
 	<literal>%%TAG%%</literal> and adding that
 	<literal>TAG</literal> to the <makevar>PLIST_SUB</makevar>
 	variable inside the <filename>Makefile</filename> with a
 	special value of <literal>@comment</literal>, which makes
 	package tools to ignore the line:</para>
 
       <programlisting>.if defined(WITH_X11)
 PLIST_SUB+=	X11=""
 .else
 PLIST_SUB+=	X11="@comment "
 .endif</programlisting>
 
       <para>and in the <filename>pkg-plist</filename>:</para>
 
       <programlisting>%%X11%%bin/foo-gui</programlisting>
 
       <para>This substitution (as well as addition of any <link
 	  linkend="makefile-manpages">manual pages</link>) will be
 	done between the <maketarget>pre-install</maketarget> and
 	<maketarget>do-install</maketarget> targets, by reading from
 	<filename><makevar>PLIST</makevar></filename> and writing to
 	<filename><makevar>TMPPLIST</makevar></filename> (default:
 	<filename><makevar>WRKDIR</makevar>/.PLIST.mktmp</filename>).
 	So if your port builds
 	<filename><makevar>PLIST</makevar></filename> on the fly, do
 	so in or before <maketarget>pre-install</maketarget>.  Also,
 	if your port needs to edit the resulting file, do so in
 	<maketarget>post-install</maketarget> to a file named
 	<filename><makevar>TMPPLIST</makevar></filename>.</para>
 
       <para>Another possibility to modify port's packing list is based
 	on setting the variables <makevar>PLIST_FILES</makevar> and
 	<makevar>PLIST_DIRS</makevar>.  The value of each variable is
 	regarded as a list of pathnames to write to
 	<filename><makevar>TMPPLIST</makevar></filename> along with
 	<filename><makevar>PLIST</makevar></filename> contents.  Names
 	listed in <makevar>PLIST_FILES</makevar> and
 	<makevar>PLIST_DIRS</makevar> are subject to
 	<literal>%%<replaceable>VAR</replaceable>%%</literal>
 	substitution, as described above.  Except for that, names from
 	<makevar>PLIST_FILES</makevar> will appear in the final
 	packing list unchanged, while <literal>@dirrm</literal> will
 	be prepended to names from <makevar>PLIST_DIRS</makevar>.  To
 	take effect, <makevar>PLIST_FILES</makevar> and
 	<makevar>PLIST_DIRS</makevar> must be set before
 	<filename><makevar>TMPPLIST</makevar></filename> is written,
 	i.e., in <maketarget>pre-install</maketarget> or
 	earlier.</para>
     </sect1>
 
     <sect1 id="plist-cleaning">
       <title>Empty Directories</title>
 
       <sect2 id="plist-dir-cleaning">
 	<title>Cleaning Up Empty Directories</title>
 
 	<para>Do make your ports remove empty directories when they
 	  are de-installed.  This is usually accomplished by adding
 	  <literal>@dirrm</literal> lines for all directories that are
 	  specifically created by the port.  You need to delete
 	  subdirectories before you can delete parent
 	  directories.</para>
 
 	<programlisting> :
 lib/X11/oneko/pixmaps/cat.xpm
 lib/X11/oneko/sounds/cat.au
  :
 @dirrm lib/X11/oneko/pixmaps
 @dirrm lib/X11/oneko/sounds
 @dirrm lib/X11/oneko</programlisting>
 
 	<para>However, sometimes <literal>@dirrm</literal> will give
 	  you errors because other ports share the same directory.
 	  You can use <literal>@dirrmtry</literal> to remove only
 	  empty directories without warning.</para>
 
 	<programlisting>@dirrmtry share/doc/gimp</programlisting>
 
 	<para>This will neither print any error messages nor cause
 	  &man.pkg.delete.1; to exit abnormally even if
 	  <filename><makevar>${PREFIX}</makevar>/share/doc/gimp</filename>
 	  is not empty due to other ports installing some files in
 	  there.</para>
       </sect2>
 
       <sect2 id="plist-dir-empty">
 	<title>Creating Empty Directories</title>
 
 	<para>Empty directories created during port installation need
 	  special attention.  They will not get created when
 	  installing the package, because packages only store the
 	  files, and &man.pkg.add.1; creates directories for them as
 	  needed.  To make sure the empty directory is created when
 	  installing the package, add this line to
 	  <filename>pkg-plist</filename> above the corresponding
 	  <literal>@dirrm</literal> line:</para>
 
 	<programlisting>@exec mkdir -p %D/share/foo/templates</programlisting>
       </sect2>
     </sect1>
 
     <sect1 id="plist-config">
       <title>Configuration Files</title>
 
       <para>If your port installs configuration files to
 	<filename><makevar>PREFIX</makevar>/etc</filename> (or
 	elsewhere) do <emphasis>not</emphasis> simply list them in the
 	<filename>pkg-plist</filename>.  That will cause
 	&man.pkg.delete.1; to remove the files carefully edited by
 	the user, and a re-installation will wipe them out.</para>
 
       <para>Instead, install sample file(s) with a
 	<filename><replaceable>filename</replaceable>.sample</filename>
 	suffix.  Then copy the sample file to the real configuration
 	file name, if it does not already exist.  On deinstall
 	delete the configuration file, but only if it is identical
 	to the <filename>.sample</filename> file.
 	You need to handle this both in the port
 	<filename>Makefile</filename>, and in the
 	<filename>pkg-plist</filename> (for installation from the
 	package).</para>
 
       <para>Example of the <filename>Makefile</filename> part:</para>
 
       <programlisting>post-install:
 	@if [ ! -f ${PREFIX}/etc/orbit.conf ]; then \
 		${CP} -p ${PREFIX}/etc/orbit.conf.sample ${PREFIX}/etc/orbit.conf ; \
 	fi</programlisting>
 
       <para>For each configuration file, create the following three
 	lines in <filename>pkg-plist</filename>:</para>
 
       <programlisting>@unexec if cmp -s %D/etc/orbit.conf.sample %D/etc/orbit.conf; then rm -f %D/etc/orbit.conf; fi
 etc/orbit.conf.sample
 @exec if [ ! -f %D/etc/orbit.conf ] ; then cp -p %D/%F %B/orbit.conf; fi</programlisting>
 
       <para>The order of these lines is important.  On deinstallation,
 	the sample file is compared to the actual configuration file.
 	If these files are identical, no changes have been made by the
 	user and the actual file can be safely deleted.  Because the
 	sample file must still exist for the comparison, the
 	<literal>@unexec</literal> line comes before the sample
 	configuration file name.  On installation, if an actual
 	configuration file is not already present, the sample file is
 	copied to the actual file.  The sample file must be present
 	before it can be copied, so the <literal>@exec</literal> line
 	comes after the sample configuration file name.</para>
 
       <para>To debug any issues, temporarily remove the
 	<literal>-s</literal> flag to &man.cmp.1; for more
 	output.</para>
 
       <para>See &man.pkg.create.1; for more information on
 	<literal>%D</literal> and related substitution markers.</para>
 
       <para>If there is a very good reason not to install a working
 	configuration file by default, leave the
 	<literal>@exec</literal> line out of
 	<filename>pkg-plist</filename> and add a <link
 	  linkend="porting-message">message</link> pointing out that
 	the user must copy and edit the file before the software will
 	work.</para>
     </sect1>
 
     <sect1 id="plist-dynamic">
       <title>Dynamic Versus Static Package List</title>
 
       <para>A <emphasis>static package list</emphasis> is a package
 	list which is available in the Ports Collection either as a
 	<filename>pkg-plist</filename> file (with or without variable
 	substitution), or embedded into the
 	<filename>Makefile</filename> via
 	<makevar>PLIST_FILES</makevar> and
 	<makevar>PLIST_DIRS</makevar>.  Even if the contents are
 	auto-generated by a tool or a target in the Makefile
 	<emphasis>before</emphasis> the inclusion into the Ports
 	Collection by a committer, this is still considered a static
 	list, since it is possible to examine it without having to
 	download or compile the distfile.</para>
 
       <para>A <emphasis>dynamic package list</emphasis> is a package
 	list which is generated at the time the port is compiled based
 	upon the files and directories which are installed.  It is not
 	possible to examine it before the source code of the ported
 	application is downloaded and compiled, or after running a
 	<literal>make clean</literal>.</para>
 
       <para>While the use of dynamic package lists is not forbidden,
 	maintainers should use static package lists wherever possible,
 	as it enables users to &man.grep.1; through available ports to
 	discover, for example, which port installs a certain file.
 	Dynamic lists should be primarily used for complex ports where
 	the package list changes drastically based upon optional
 	features of the port (and thus maintaining a static package
 	list is infeasible), or ports which change the package list
 	based upon the version of dependent software used (e.g., ports
 	which generate docs with
 	<application>Javadoc</application>).</para>
 
       <para>Maintainers who prefer dynamic package lists are
 	encouraged to add a new target to their port which generates
 	the <filename>pkg-plist</filename> file so that users may
 	examine the contents.</para>
     </sect1>
 
     <sect1 id="plist-autoplist">
       <title>Automated Package List Creation</title>
 
       <para>First, make sure your port is almost complete, with only
 	<filename>pkg-plist</filename> missing.</para>
 
       <para>Next, create a temporary directory tree into which your
 	port can be installed, and install any dependencies.</para>
 
       <screen>&prompt.root; <userinput>mkdir /var/tmp/`make -V PORTNAME`</userinput>
 &prompt.root; <userinput>mtree -U -f `make -V MTREE_FILE` -d -e -p /var/tmp/`make -V PORTNAME`</userinput>
 &prompt.root; <userinput>make depends PREFIX=/var/tmp/`make -V PORTNAME`</userinput></screen>
 
       <para>Store the directory structure in a new file.</para>
 
       <screen>&prompt.root; <userinput>(cd /var/tmp/`make -V PORTNAME` &amp;&amp; find -d * -type d) | sort &gt; OLD-DIRS</userinput></screen>
 
       <para>Create an empty <filename>pkg-plist</filename>
 	file:</para>
 
       <screen>&prompt.root; <userinput>:&gt;pkg-plist</userinput></screen>
 
       <para>If your port honors <makevar>PREFIX</makevar> (which it
 	should) you can then install the port and create the package
 	list.</para>
 
       <screen>&prompt.root; <userinput>make install PREFIX=/var/tmp/`make -V PORTNAME`</userinput>
 &prompt.root; <userinput>(cd /var/tmp/`make -V PORTNAME` &amp;&amp; find -d * \! -type d) | sort &gt; pkg-plist</userinput></screen>
 
       <para>You must also add any newly created directories to the
 	packing list.</para>
 
       <screen>&prompt.root; <userinput>(cd /var/tmp/`make -V PORTNAME` &amp;&amp; find -d * -type d) | sort | comm -13 OLD-DIRS - | sort -r | sed -e 's#^#@dirrm #' &gt;&gt; pkg-plist</userinput></screen>
 
       <para>Finally, you need to tidy up the packing list by hand; it
 	is not <emphasis>all</emphasis> automated.  Manual pages
 	should be listed in the port's <filename>Makefile</filename>
 	under <makevar>MAN<replaceable>n</replaceable></makevar>, and
 	not in the package list.  User configuration files should be
 	removed, or installed as
 	<filename><replaceable>filename</replaceable>.sample</filename>.
 	The <filename>info/dir</filename> file should not be listed
 	and appropriate <filename>install-info</filename> lines should
 	be added as noted in the <link linkend="makefile-info">info
 	  files</link> section.  Any libraries installed by the port
 	should be listed as specified in the <link
 	  linkend="porting-shlibs">shared libraries</link>
 	section.</para>
 
       <para>Alternatively, use the <command>plist</command> script in
 	<filename>/usr/ports/Tools/scripts/</filename> to build the
 	package list automatically.  The <filename>plist</filename>
 	script is a <application>Ruby</application> script that
 	automates most of the manual steps outlined in the previous
 	paragraphs.</para>
 
       <para>The first step is the same as above: take the first three
 	lines, that is, <command>mkdir</command>,
 	<command>mtree</command> and <command>make depends</command>.
 	Then build and install the port:</para>
 
       <screen>&prompt.root; <userinput>make install PREFIX=/var/tmp/`make -V PORTNAME`</userinput></screen>
 
       <para>And let <command>plist</command> create the
 	<filename>pkg-plist</filename> file:</para>
 
       <screen>&prompt.root; <userinput>/usr/ports/Tools/scripts/plist -Md -m `make -V MTREE_FILE` /var/tmp/`make -V PORTNAME` &gt; pkg-plist</userinput></screen>
 
       <para>The packing list still has to be tidied up by hand as
 	stated above.</para>
 
       <para>Another tool that might be used to create an initial
 	<filename>pkg-plist</filename> is <filename
 	  role="package">ports-mgmt/genplist</filename>.  As with any
 	automated tool, the resulting <filename>pkg-plist</filename>
 	should be checked and manually edited as needed.</para>
     </sect1>
   </chapter>
 
   <chapter id="pkg-files">
     <title>The <filename>pkg-<replaceable>*</replaceable></filename>
       Files</title>
 
     <para>There are some tricks we have not mentioned yet about the
       <filename>pkg-<replaceable>*</replaceable></filename> files
       that come in handy sometimes.</para>
 
     <sect1 id="porting-message">
       <title><filename>pkg-message</filename></title>
 
       <para>If you need to display a message to the installer, you may
 	place the message in <filename>pkg-message</filename>.  This
 	capability is often useful to display additional installation
 	steps to be taken after a &man.pkg.add.1; or to display
 	licensing information.</para>
 
       <para>When some lines about the build-time knobs or warnings
 	have to be displayed, use <makevar>ECHO_MSG</makevar>.  The
 	<filename>pkg-message</filename> file is only for
 	post-installation steps.  Likewise, the distinction between
 	<makevar>ECHO_MSG</makevar> and <makevar>ECHO_CMD</makevar>
 	should be kept in mind.  The former is for printing
 	informational text to the screen, while the latter is for
 	command pipelining:</para>
 
       <programlisting>update-etc-shells:
 	@${ECHO_MSG} "updating /etc/shells"
 	@${CP} /etc/shells /etc/shells.bak
 	@( ${GREP} -v ${PREFIX}/bin/bash /etc/shells.bak; \
 		${ECHO_CMD} ${PREFIX}/bin/bash) &gt;/etc/shells
 	@${RM} /etc/shells.bak</programlisting>
 
       <note>
 	<para>The <filename>pkg-message</filename> file does not need
 	  to be added to <filename>pkg-plist</filename>.  Also, it
 	  will not get automatically printed if the user is using the
 	  port, not the package, so you should probably display it
 	  from the <maketarget>post-install</maketarget> target
 	  yourself.</para>
       </note>
     </sect1>
 
     <sect1 id="pkg-install">
       <title><filename>pkg-install</filename></title>
 
       <para>If your port needs to execute commands when the binary
 	package is installed with &man.pkg.add.1; you can do this via
 	the <filename>pkg-install</filename> script.  This script will
 	automatically be added to the package, and will be run twice
 	by &man.pkg.add.1;: the first time as <literal>&dollar;{SH}
 	  pkg-install &dollar;{PKGNAME} PRE-INSTALL</literal> and the
 	second time as <literal>&dollar;{SH} pkg-install
 	  &dollar;{PKGNAME} POST-INSTALL</literal>.
 	<literal>&dollar;2</literal> can be tested to determine which
 	mode the script is being run in.  The
 	<envar>PKG_PREFIX</envar> environmental variable will be set
 	to the package installation directory.  See &man.pkg.add.1;
 	for additional information.</para>
 
       <note>
 	<para>This script is not run automatically if you install the
 	  port with <command>make install</command>.  If you are
 	  depending on it being run, you will have to explicitly call
 	  it from your port's <filename>Makefile</filename>, with a
 	  line like <literal>PKG_PREFIX=&dollar;{PREFIX} &dollar;{SH}
 	    &dollar;{PKGINSTALL} &dollar;{PKGNAME}
 	    PRE-INSTALL</literal>.</para>
       </note>
     </sect1>
 
     <sect1 id="pkg-deinstall">
       <title><filename>pkg-deinstall</filename></title>
 
       <para>This script executes when a package is removed.</para>
 
       <para>This script will be run twice by &man.pkg.delete.1;.
 	The first time as <literal>&dollar;{SH} pkg-deinstall
 	  &dollar;{PKGNAME} DEINSTALL</literal> and the second time as
 	<literal>&dollar;{SH} pkg-deinstall &dollar;{PKGNAME}
 	  POST-DEINSTALL</literal>.</para>
     </sect1>
 
     <sect1 id="pkg-req">
       <title><filename>pkg-req</filename></title>
 
       <para>If your port needs to determine if it should install or
 	not, you can create a <filename>pkg-req</filename>
 	<quote>requirements</quote> script.  It will be invoked
 	automatically at installation/de-installation time to
 	determine whether or not installation/de-installation should
 	proceed.</para>
 
       <para>The script will be run at installation time by
 	&man.pkg.add.1; as
 	<literal>pkg-req &dollar;{PKGNAME} INSTALL</literal>.
 	At de-installation time it will be run by
 	&man.pkg.delete.1; as
 	<literal>pkg-req &dollar;{PKGNAME} DEINSTALL</literal>.</para>
     </sect1>
 
     <sect1 id="pkg-names">
       <title id="porting-pkgfiles">Changing the Names of
 	<filename>pkg-<replaceable>*</replaceable></filename>
 	Files</title>
 
       <para>All the names of
 	<filename>pkg-<replaceable>*</replaceable></filename> files
 	are defined using variables so you can change them in your
 	<filename>Makefile</filename> if need be.  This is especially
 	useful when you are sharing the same
 	<filename>pkg-<replaceable>*</replaceable></filename> files
 	among several ports or have to write to one of the above files
 	(see <link linkend="porting-wrkdir">writing to places other
 	  than <makevar>WRKDIR</makevar></link> for why it is a bad
 	idea to write directly into the
 	<filename>pkg-<replaceable>*</replaceable></filename>
 	subdirectory).</para>
 
       <para>Here is a list of variable names and their default values.
 	(<makevar>PKGDIR</makevar> defaults to
 	<makevar>${MASTERDIR}</makevar>.)</para>
 
       <informaltable frame="none" pgwide="0">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Variable</entry>
 	      <entry>Default value</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><makevar>DESCR</makevar></entry>
 	      <entry><literal>${PKGDIR}/pkg-descr</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PLIST</makevar></entry>
 	      <entry><literal>${PKGDIR}/pkg-plist</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PKGINSTALL</makevar></entry>
 	      <entry><literal>${PKGDIR}/pkg-install</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PKGDEINSTALL</makevar></entry>
 	      <entry><literal>${PKGDIR}/pkg-deinstall</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PKGREQ</makevar></entry>
 	      <entry><literal>${PKGDIR}/pkg-req</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PKGMESSAGE</makevar></entry>
 	      <entry><literal>${PKGDIR}/pkg-message</literal></entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>Please change these variables rather than overriding
 	<makevar>PKG_ARGS</makevar>.  If you change
 	<makevar>PKG_ARGS</makevar>, those files will not correctly be
 	installed in <filename>/var/db/pkg</filename> upon install
 	from a port.</para>
     </sect1>
 
     <sect1 id="using-sub-files">
       <title>Making Use of <makevar>SUB_FILES</makevar> and
 	<makevar>SUB_LIST</makevar></title>
 
       <para>The <makevar>SUB_FILES</makevar> and
 	<makevar>SUB_LIST</makevar> variables are useful for dynamic
 	values in port files, such as the installation
 	<makevar>PREFIX</makevar> in
 	<filename>pkg-message</filename>.</para>
 
       <para>The <makevar>SUB_FILES</makevar> variable specifies a list
 	of files to be automatically modified.  Each
 	<replaceable>file</replaceable> in the
 	<makevar>SUB_FILES</makevar> list must have a corresponding
 	<filename><replaceable>file</replaceable>.in</filename>
 	present in <makevar>FILESDIR</makevar>.  A modified version
 	will be created in <makevar>WRKDIR</makevar>.  Files defined
 	as a value of <makevar>USE_RC_SUBR</makevar> (or the
 	deprecated <makevar>USE_RCORDER</makevar>) are automatically
 	added to the <makevar>SUB_FILES</makevar>.  For the files
 	<filename>pkg-message</filename>,
 	<filename>pkg-install</filename>,
 	<filename>pkg-deinstall</filename> and
 	<filename>pkg-req</filename>, the corresponding Makefile
 	variable is automatically set to point to the processed
 	version.</para>
 
       <para>The <makevar>SUB_LIST</makevar> variable is a list of
 	<literal>VAR=VALUE</literal> pairs.  For each pair
 	<literal>%%VAR%%</literal> will get replaced with
 	<literal>VALUE</literal> in each file listed in
 	<makevar>SUB_FILES</makevar>.  Several common pairs are
 	automatically defined: <makevar>PREFIX</makevar>,
 	<makevar>LOCALBASE</makevar>, <makevar>DATADIR</makevar>,
 	<makevar>DOCSDIR</makevar>, <makevar>EXAMPLESDIR</makevar>,
 	<makevar>WWWDIR</makevar>, and <makevar>ETCDIR</makevar>.
 	Any line beginning with <literal>@comment</literal> will be
 	deleted from resulting files after a variable
 	substitution.</para>
 
       <para>The following example will replace
 	<literal>%%ARCH%%</literal> with the system architecture in a
 	<filename>pkg-message</filename>:</para>
 
       <programlisting>SUB_FILES=	pkg-message
 SUB_LIST=	ARCH=${ARCH}</programlisting>
 
       <para>Note that for this example, the
 	<filename>pkg-message.in</filename> file must exist in
 	<makevar>FILESDIR</makevar>.</para>
 
       <para>Example of a good
 	<filename>pkg-message.in</filename>:</para>
 
       <programlisting>Now it is time to configure this package.
 Copy %%PREFIX%%/share/examples/putsy/%%ARCH%%.conf into your home directory
 as .putsy.conf and edit it.</programlisting>
     </sect1>
   </chapter>
 
   <chapter id="testing">
     <title>Testing Your Port</title>
 
     <sect1 id="make-describe">
       <title>Running <command>make describe</command></title>
 
       <para>Several of the &os; port maintenance tools, such as
 	&man.portupgrade.1;, rely on a database called
 	<filename>/usr/ports/INDEX</filename> which keeps track of
 	such items as port dependencies.  <filename>INDEX</filename>
 	is created by the top-level
 	<filename>ports/Makefile</filename> via <command>make
 	  index</command>, which descends into each port subdirectory
 	and executes <command>make describe</command> there.  Thus, if
 	<command>make describe</command> fails in any port, no one can
 	generate <filename>INDEX</filename>, and many people will
 	quickly become unhappy.</para>
 
       <note>
 	<para>It is important to be able to generate this file no
 	  matter what options are present in
 	  <filename>make.conf</filename>, so please avoid doing things
 	  such as using <literal>.error</literal> statements when (for
 	  instance) a dependency is not satisfied.  (See <xref
 	    linkend="dads-dot-error"/>.)</para>
       </note>
 
       <para>If <command>make describe</command> produces a string
 	rather than an error message, you are probably safe.  See
 	<filename>bsd.port.mk</filename> for the meaning of the
 	string produced.</para>
 
       <para>Also note that running a recent version of
 	<command>portlint</command> (as specified in the next section)
 	will cause <command>make describe</command> to be run
 	automatically.</para>
     </sect1>
 
     <sect1 id="testing-portlint">
       <title>Portlint</title>
 
       <para>Do check your work with <link
 	  linkend="porting-portlint"><command>portlint</command></link>
 	before you submit or commit it.  <command>portlint</command>
 	warns you about many common errors, both functional and
 	stylistic.  For a new (or repocopied) port, <command>portlint
 	  -A</command> is the most thorough; for an existing port,
 	<command>portlint -C</command> is sufficient.</para>
 
       <para>Since <command>portlint</command> uses heuristics to
 	try to figure out errors, it can produce false positive
 	warnings.  In addition, occasionally something that is
 	flagged as a problem really cannot be done in any other
 	way due to limitations in the ports framework.  When in
 	doubt, the best thing to do is ask on &a.ports;.</para>
     </sect1>
 
     <sect1 id="testing-porttools">
       <title>Port Tools</title>
 
       <para>The <filename
 	  role="package">ports-mgmt/porttools</filename> program is
 	part of the Ports Collection.</para>
 
       <para><command>port</command> is the front-end script, which can
 	help you simplify the testing job.  Whenever you want to test
 	a new port or update an existing one, you can use
 	<command>port test</command> to test your port, including the
 	<link
 	  linkend="testing-portlint"><command>portlint</command></link>
 	checking.  This command also detects and lists any files that
 	are not listed in <filename>pkg-plist</filename>.  See the
 	following example:</para>
 
       <screen>&prompt.root; <userinput>port test /usr/ports/net/csup</userinput></screen>
     </sect1>
 
     <sect1 id="porting-prefix">
       <title><makevar>PREFIX</makevar> and
 	<makevar>DESTDIR</makevar></title>
 
       <para><makevar>PREFIX</makevar> determines where the port will
 	be installed.  It defaults to <filename>/usr/local</filename>,
 	but can be set by the user to a custom path like
 	<filename>/opt</filename>.  Your port must respect the value
 	of this variable.</para>
 
       <para><makevar>DESTDIR</makevar>, if set by the user, determines
 	the complete alternative environment, usually a jail or an
 	installed system mounted somewhere other than
 	<filename>/</filename>.  A port will actually install into
 	<filename><makevar>DESTDIR</makevar>/<makevar>PREFIX</makevar></filename>,
 	and register with the package database in
 	<filename><makevar>DESTDIR</makevar>/var/db/pkg</filename>.
 	As <makevar>DESTDIR</makevar> is handled automatically by the
 	ports infrastructure with &man.chroot.8;, you do not need any
 	modifications or any extra care to write
 	<makevar>DESTDIR</makevar>-compliant ports.</para>
 
       <para>The value of <makevar>PREFIX</makevar> will be set to
 	<makevar>LOCALBASE</makevar> (defaulting to
 	<filename>/usr/local</filename>).  If
 	<makevar>USE_LINUX_PREFIX</makevar> is set,
 	<makevar>PREFIX</makevar> will be <makevar>LINUXBASE</makevar>
 	(defaulting to <filename>/compat/linux</filename>).</para>
 
       <para>Avoiding hard-coded <filename>/usr/local</filename> paths
 	in the source makes the port much more flexible and able to
 	cater to the needs of other sites.  Often, this can be
 	accomplished by simply replacing occurrences of
 	<filename>/usr/local</filename> in the port's various
 	<filename>Makefile</filename>s with
 	<literal>&dollar;{PREFIX}</literal>.  This variable is
 	automatically passed down to every stage of the build and
 	install processes.</para>
 
       <para>Make sure your application is not installing things in
 	<filename>/usr/local</filename> instead of
 	<makevar>PREFIX</makevar>.  A quick test for such hard-coded
 	paths is:</para>
 
       <screen>&prompt.root; <userinput>make clean; make package PREFIX=/var/tmp/`make -V PORTNAME`</userinput></screen>
 
       <para>If anything is installed outside of
 	<makevar>PREFIX</makevar>, the package creation process will
 	complain that it cannot find the files.</para>
 
       <para>This test will not find hard-coded paths inside the
 	port's files, nor will it verify that
 	<makevar>LOCALBASE</makevar> is being used to correctly refer
 	to files from other ports.  The temporarily-installed port in
 	<filename>/var/tmp/`make -V PORTNAME`</filename> should be
 	tested for proper operation to make sure there
 	are no problems with paths.</para>
 
       <para><makevar>PREFIX</makevar> should not be set explicitly
 	in a port's <filename>Makefile</filename>.  Users installing
 	the port may have set <makevar>PREFIX</makevar> to a custom
 	location, and the port should respect that setting.</para>
 
       <para>Refer to programs and files from other ports with the
 	variables mentioned above, not explicit pathnames.  For
 	instance, if your port requires a macro
 	<literal>PAGER</literal> to have the full pathname of
 	<command>less</command>, do not use a literal path of
 	<filename>/usr/local/bin/less</filename>.  Instead, use
 	<literal>&dollar;{LOCALBASE}</literal>:</para>
 
       <programlisting>-DPAGER=\"&dollar;{LOCALBASE}/bin/less\"</programlisting>
 
       <para>The path with <makevar>LOCALBASE</makevar> is more likely
 	to still work if the system administrator has moved the whole
 	<filename>/usr/local</filename> tree somewhere else.</para>
     </sect1>
 
     <sect1 id="testing-tinderbox">
       <title>Tinderbox</title>
 
       <para>If you are an avid ports contributor, you might want to
 	take a look at <application>Tinderbox</application>.  It is a
 	powerful system for building and testing ports based on the
 	scripts used on <link
 	  linkend="build-cluster">Pointyhat</link>.  You can install
 	<application>Tinderbox</application> using <filename
 	  role="package">ports-mgmt/tinderbox</filename> port.  Be
 	sure to read supplied documentation since the configuration is
 	not trivial.</para>
 
       <para>Visit the <ulink
 	  url="http://tinderbox.marcuscom.com/">Tinderbox
 	  website</ulink> for more details.</para>
     </sect1>
   </chapter>
 
   <chapter id="port-upgrading">
     <title>Upgrading an Individual Port</title>
 
     <para>When you notice that a port is out of date compared to the
       latest version from the original authors, you should first
       ensure that you have the latest port.  You can find them in the
       <filename>ports/ports-current</filename> directory of the &os;
       FTP mirror sites.  However, if you are working with more than a
       few ports, you will probably find it easier to use
       <application>Subversion</application> or &man.portsnap.8;
       to keep your whole ports
       collection up-to-date, as described in the <ulink
 	url="&url.books.handbook;/ports-using.html">Handbook</ulink>.
       This will have the added benefit of tracking all the ports'
       dependencies.</para>
 
     <para>The next step is to see if there is an update already
       pending.  To do this, you have two options.  There is a
       searchable interface to the <ulink
 	url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">
       FreeBSD Problem Report (PR) database</ulink> (also known as
       <literal>GNATS</literal>).  Select <literal>ports</literal> in
       the dropdown, and enter the name of the port.</para>
 
     <para>However, sometimes people forget to put the name of the port
       into the Synopsis field in an unambiguous fashion.  In that
       case, you can try the <link linkend="portsmon"> FreeBSD Ports
 	Monitoring System</link> (also known as
       <literal>portsmon</literal>).  This system attempts to classify
       port PRs by portname.  To search for PRs about a particular
       port, use the <ulink
 	url="http://portsmon.FreeBSD.org/portoverview.py">Overview of
 	One Port</ulink>.</para>
 
     <para>If there is no pending PR, the next step is to send an email
       to the port's maintainer, as shown by <command>make
 	maintainer</command>.  That person may already be working on
       an upgrade, or have a reason to not upgrade the port right now
       (because of, for example, stability problems of the new
       version); you would not want to duplicate their work.  Note that
       unmaintained ports are listed with a maintainer of
       <literal>ports@FreeBSD.org</literal>, which is just the general
       ports mailing list, so sending mail there probably will not help
       in this case.</para>
 
     <para>If the maintainer asks you to do the upgrade or there is
       no maintainer, then you have a chance to help out &os; by
       preparing the update yourself!  Please do this by using the
       &man.diff.1; command in the base system.</para>
 
     <para>To create a suitable <command>diff</command> for a single
       patch, copy the file that needs patching to
       <replaceable>something.orig</replaceable>, save your changes to
       <replaceable>something</replaceable> and then create your
       patch:</para>
 
     <informalexample>
       <screen>&prompt.user; <userinput>diff -u something.orig something > something.diff</userinput></screen>
     </informalexample>
 
     <para>Otherwise, you should either use the <command>svn
 	diff</command> method (<xref linkend="svn-diff"/>) or copy the
       contents of the port to an entire different directory and use
       the result of the recursive &man.diff.1; output of the new and
       old ports directories (e.g., if your modified port directory is
       called <filename>superedit</filename> and the original is in our
       tree as <filename>superedit.bak</filename>, then save the result
       of <command>diff -ruN superedit.bak superedit</command>).
       Either unified or context diff is fine, but port committers
       generally prefer unified diffs.  Note the use of the
       <literal>-N</literal> option&mdash;this is the accepted way to
       force diff to properly deal with the case of new files being
       added or old files being deleted.  Before sending us the diff,
       please examine the output to make sure all the changes make
       sense.  (In particular, make sure you first clean out the work
       directories with <command>make clean</command>).</para>
 
     <para>To simplify common operations with patch files, you can use
       <filename>/usr/ports/Tools/scripts/patchtool.py</filename>.
       Before using it, please read
       <filename>/usr/ports/Tools/scripts/README.patchtool</filename>.</para>
 
     <para>If the port is unmaintained, and you are actively using
       it yourself, please consider volunteering to become its
       maintainer.  &os; has over 4000 ports without maintainers, and
       this is an area where more volunteers are always needed.  (For a
       detailed description of the responsibilities of maintainers,
       refer to the section in the <ulink
 	url="&url.books.developers-handbook;/policies.html#POLICIES-MAINTAINER">
 	Developer's Handbook</ulink>.)</para>
 
     <para> The best way to send us the diff is by including it via
       &man.send-pr.1; (category <literal>ports</literal>).  If you are
       maintaining the port, be sure to put <literal>[maintainer
       update]</literal> at the beginning of your synopsis line and set
       the <quote>Class</quote> of your PR to
       <literal>maintainer-update</literal>.  Otherwise, the
       <quote>Class</quote> of your PR should be
       <literal>change-request</literal>.  Please mention any added or
       deleted files in the message, as they have to be explicitly
       specified to &man.svn.1; when doing a commit.  If the diff is
       more than about 20KB, please compress and uuencode it;
       otherwise, just include it in the PR as is.</para>
 
     <para>Before you &man.send-pr.1;, you should review the
       <ulink url="&url.articles.problem-reports;/pr-writing.html">
       Writing the problem report</ulink> section in the Problem
       Reports article; it contains far more information about how to
       write useful problem reports.</para>
 
     <important>
       <para>If your upgrade is motivated by security concerns or a
 	serious fault in the currently committed port, please notify
 	the &a.portmgr; to request immediate rebuilding and
 	redistribution of your port's package.  Unsuspecting users
 	of &man.pkg.add.1; will otherwise continue to install the
 	old version via <command>pkg_add -r</command> for several
 	weeks.</para>
     </important>
 
     <note>
       <para>Once again, please use &man.diff.1; and not &man.shar.1;
 	to send updates to existing ports!  This helps ports
 	committers understand exactly what is being changed.</para>
     </note>
 
     <para>Now that you have done all that, you will want to read about
       how to keep up-to-date in <xref linkend="keeping-up"/>.</para>
 
     <sect1 id="svn-diff">
       <title>Using <literal>SVN</literal> to Make Patches</title>
 
       <para>If you can, please submit a &man.svn.1; diff &mdash; they
 	are easier to handle than diffs between <quote>new and
 	  old</quote> directories.  Plus it is easier for you to see
 	what you have changed and to update your diff if something is
 	modified in the Ports Collection from when you started to work
 	on it until you submit your changes, or if the committer asks
 	you to fix something.</para>
 
       <screen>&prompt.user; <userinput>cd ~/my_wrkdir</userinput> <co id="my-wrkdir"/>
 &prompt.user; <userinput>svn co <replaceable>https://svn0.us-west.FreeBSD.org</replaceable>/ports/head/dns/pdnsd</userinput> <co id="svn-FreeBSD-org"/>
 &prompt.user; <userinput>cd ~/my_wrkdir/pdnsd</userinput></screen>
 
       <calloutlist>
 	<callout arearefs="my-wrkdir">
 
 	  <para>This can be anywhere you want, of course; building
 	    ports is not limited to within <filename
 	      class="directory">/usr/ports/</filename>.</para>
 	</callout>
 
 	<callout arearefs="svn-FreeBSD-org">
 	  <para><ulink
 	      url="https://svn0.us-west.FreeBSD.org/">svn0.us-west.FreeBSD.org</ulink>
 	    is a public <literal>SVN</literal> server.
 	    Select the closest mirror and verify the mirror server
 	    certificate from the list of <ulink
 	      url="&url.books.handbook;/svn-mirrors.html">Subversion
 	      mirror sites</ulink>.</para>
 	</callout>
       </calloutlist>
 
       <para>While in the working directory, make any changes that you
 	would usually make to the port.  If you add or remove a file,
 	use <command>svn</command> to track these changes:</para>
 
       <screen>&prompt.user; <userinput>svn add new_file</userinput>
 &prompt.user; <userinput>svn remove deleted_file</userinput></screen>
 
       <para>Make sure that you check the port using the checklist in
 	<xref linkend="porting-testing"/> and
 	<xref linkend="porting-portlint"/>.</para>
 
       <screen>&prompt.user; <userinput>svn status</userinput>
 &prompt.user; <userinput>svn update</userinput> <co id="svn-update"/></screen>
 
       <calloutlist>
 	<callout arearefs="svn-update">
 	  <para>This will try to merge the differences between your
 	    patch and current SVN; watch the output carefully.  The
 	    letter in front of each file name indicates what was done
 	    with it.  See <xref linkend="table-svn-up"/> for a
 	    complete list.</para>
 	</callout>
       </calloutlist>
 
       <table pgwide="1" frame="none" id="table-svn-up">
 	<title><literal>SVN</literal> Update File Prefixes</title>
 
 	<tgroup cols="2">
 	  <tbody>
 	    <row>
 	      <entry>U</entry>
 	      <entry>The file was updated without problems.</entry>
 	    </row>
 
 	    <row>
 	      <entry>G</entry>
 	      <entry>The file was updated without problems (you will
 		only see this when working against a remote
 		repository).</entry>
 	    </row>
 
 	    <row>
 	      <entry>M</entry>
 	      <entry>The file had been modified, and was merged
 		without conflicts.</entry>
 	    </row>
 
 	    <row>
 	      <entry>C</entry>
 	      <entry>The file had been modified, and was merged with
 		conflicts.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>If you get <literal>C</literal> as a result of
 	<command>svn update</command> it means something changed in
 	the SVN repository and &man.svn.1; was not able to merge your
 	local changes and those from the repository.  It is always a
 	good idea to inspect the changes anyway, since &man.svn.1;
 	does not know anything about how a port should be, so it might
 	(and probably will) merge things that do not make
 	sense.</para>
 
       <para>The last step is to make a unified &man.diff.1;
 	of the files against SVN:</para>
 
       <screen>&prompt.user; <userinput>svn diff &gt; ../`basename ${PWD}`.diff</userinput></screen>
 
       <note>
 	<para>Any files that have been removed should be explicitly
 	  mentioned in the PR, because file removal may not be obvious
 	  to the committer.</para>
       </note>
 
       <para>Send your patch following the guidelines in
 	<xref linkend="port-upgrading"/>.</para>
     </sect1>
 
     <sect1 id="moved-and-updating-files">
       <title>The Files <filename>UPDATING</filename> and
 	<filename>MOVED</filename></title>
 
       <para>If upgrading the port requires special steps like
 	changing configuration files or running a specific program,
 	you should document this in the file
 	<filename>/usr/ports/UPDATING</filename>.  The format of
 	an entry in this file is as follows:</para>
 
       <programlisting>YYYYMMDD:
   AFFECTS: users of portcategory/portname
   AUTHOR: Your name &lt;Your email address&gt;
 
   Special instructions</programlisting>
 
       <para>If you are including exact portmaster or portupgrading
 	instructions, please make sure to get the shell escaping
 	right.</para>
 
       <para>The <filename>/usr/ports/MOVED</filename> file is used to
 	list moved or removed ports.  Each line in the file is made
 	up of the name of the port, where the port was moved to, when,
 	and why.  If the port was removed, the section detailing where
 	it was moved to can be left blank.  Each section must be
 	separated by the <literal>|</literal> (pipe) character, like
 	so:</para>
 
       <programlisting>old name|new name (blank for deleted)|date of move|reason</programlisting>
 
       <para>The date should be entered in the form
 	<literal>YYYY-MM-DD</literal>.  New entries should be added to
 	the end of the file to keep it in chronological order.</para>
 
       <para>If a port was removed but has since been restored,
 	delete the line in this file that states that it was
 	removed.</para>
 
       <para>The changes can be validated with
 	<command>Tools/scripts/MOVEDlint.awk</command>.</para>
     </sect1>
   </chapter>
 
   <chapter id="security">
     <title>Ports Security</title>
 
     <sect1 id="security-intro">
       <title>Why Security is So Important</title>
 
       <para>Bugs are occasionally introduced to the software.
 	Arguably, the most dangerous of them are those opening
 	security vulnerabilities.  From the technical viewpoint,
 	such vulnerabilities are to be closed by exterminating
 	the bugs that caused them.  However, the policies for
 	handling mere bugs and security vulnerabilities are
 	very different.</para>
 
       <para>A typical small bug affects only those users who have
 	enabled some combination of options triggering the bug.
 	The developer will eventually release a patch followed
 	by a new version of the software, free of the bug, but
 	the majority of users will not take the trouble of upgrading
 	immediately because the bug has never vexed them.  A
 	critical bug that may cause data loss represents a graver
 	issue.  Nevertheless, prudent users know that a lot of
 	possible accidents, besides software bugs, are likely to
 	lead to data loss, and so they make backups of important
 	data; in addition, a critical bug will be discovered
 	really soon.</para>
 
       <para>A security vulnerability is all different.  First,
 	it may remain unnoticed for years because often it does
 	not cause software malfunction.  Second, a malicious party
 	can use it to gain unauthorized access to a vulnerable
 	system, to destroy or alter sensitive data; and in the
 	worst case the user will not even notice the harm caused.
 	Third, exposing a vulnerable system often assists attackers
 	to break into other systems that could not be compromised
 	otherwise.  Therefore closing a vulnerability alone is
 	not enough: the audience should be notified of it in most
 	clear and comprehensive manner, which will allow to
 	evaluate the danger and take appropriate actions.</para>
     </sect1>
 
     <sect1 id="security-fix">
       <title>Fixing Security Vulnerabilities</title>
 
       <para>While on the subject of ports and packages, a security
 	vulnerability may initially appear in the original
 	distribution or in the port files.  In the former case, the
 	original software developer is likely to release a patch or a
 	new version instantly, and you will only need to update the
 	port promptly with respect to the author's fix.  If the fix is
 	delayed for some reason, you should either <link
 	  linkend="dads-noinstall">mark the port as
 	<makevar>FORBIDDEN</makevar></link> or introduce a patch file
 	of your own to the port.  In the case of a vulnerable port,
 	just fix the port as soon as possible.  In either case, <link
 	  linkend="port-upgrading">the standard procedure for
 	submitting your change</link> should be followed unless you
 	have rights to commit it directly to the ports tree.</para>
 
       <important>
 	<para>Being a ports committer is not enough to commit to
 	  an arbitrary port.  Remember that ports usually have
 	  maintainers, whom you should respect.</para>
       </important>
 
       <para>Please make sure that the port's revision is bumped
 	as soon as the vulnerability has been closed.
 	That is how the users who upgrade installed packages
 	on a regular basis will see they need to run an update.
 	Besides, a new package will be built and distributed
 	over FTP and WWW mirrors, replacing the vulnerable one.
 	<makevar>PORTREVISION</makevar> should be bumped unless
 	<makevar>PORTVERSION</makevar> has changed in the course
 	of correcting the vulnerability.  That is you should
 	bump <makevar>PORTREVISION</makevar> if you have added a
 	patch file to the port, but you should not if you have updated
 	the port to the latest software version and thus already
 	touched <makevar>PORTVERSION</makevar>.  Please refer to the
 	<link linkend="makefile-naming-revepoch">corresponding
 	  section</link> for more information.</para>
     </sect1>
 
     <sect1 id="security-notify">
       <title>Keeping the Community Informed</title>
 
       <sect2 id="security-notify-vuxml-db">
 	<title>The VuXML Database</title>
 
 	<para>A very important and urgent step to take as early after
 	  a security vulnerability is discovered as possible is to
 	  notify the community of port users about the jeopardy.  Such
 	  notification serves two purposes.  First, should the danger
 	  be really severe it will be wise to apply an instant
 	  workaround.  E.g., stop the affected network service or even
 	  deinstall the port completely until the vulnerability is
 	  closed.  Second, a lot of users tend to upgrade installed
 	  packages only occasionally.  They will know from the
 	  notification that they <emphasis>must</emphasis> update the
 	  package without delay as soon as a corrected version is
 	  available.</para>
 
 	<para>Given the huge number of ports in the tree
 	  a security advisory cannot be issued on each incident
 	  without creating a flood and losing the attention of
 	  the audience when it comes to really serious
 	  matters.  Therefore security vulnerabilities found in
 	  ports are recorded in <ulink
 	    url="http://vuxml.freebsd.org/">the FreeBSD VuXML
 	  database</ulink>.  The Security Officer Team members
 	  also monitor it for issues requiring their
 	  intervention.</para>
 
 	<para>If you have committer rights you can update the VuXML
 	  database by yourself.  So you will both help the Security
 	  Officer Team and deliver the crucial information to the
 	  community earlier.  However, if you are not a committer,
 	  or you believe you have found an exceptionally severe
 	  vulnerability please do not hesitate to
 	  contact the Security Officer Team directly as described
 	  on the <ulink
 	    url="http://www.freebsd.org/security/#how">FreeBSD
 	    Security Information</ulink> page.</para>
 
 	<para>The VuXML database is an
 	  XML document.  Its source file <filename>vuln.xml</filename>
 	  is kept right inside the port <filename
 	    role="package">security/vuxml</filename>.  Therefore
 	  the file's full pathname will be
 	  <filename><envar>PORTSDIR</envar>/security/vuxml/vuln.xml</filename>.
 	  Each time you discover a security vulnerability in a
 	  port please add an entry for it to that file.
 	  Until you are familiar with VuXML, the best thing you can
 	  do is to find an existing entry fitting your case, then copy
 	  it and use it as a template.</para>
       </sect2>
 
       <sect2 id="security-notify-vuxml-intro">
 	<title>A Short Introduction to VuXML</title>
 
 	<para>The full-blown XML format is complex, and far beyond the
 	  scope of this book.  However, to gain basic insight on the
 	  structure of a VuXML entry you need only the notion of tags.
 	  XML tag names are enclosed in angle brackets.  Each opening
 	  &lt;tag&gt; must have a matching closing &lt;/tag&gt;.  Tags
 	  may be nested.  If nesting, the inner tags must be closed
 	  before the outer ones.  There is a hierarchy of tags, i.e.,
 	  more complex rules of nesting them.  This is similar to
 	  HTML.  The major difference is that XML is
 	  e<emphasis>X</emphasis>tensible, i.e., based on defining
 	  custom tags.  Due to its intrinsic structure XML puts
 	  otherwise amorphous data into shape.  VuXML is particularly
 	  tailored to mark up descriptions of security
 	  vulnerabilities.</para>
 
 	<para>Now consider a realistic VuXML entry:</para>
 
 	<programlisting>&lt;vuln vid="f4bc80f4-da62-11d8-90ea-0004ac98a7b9"&gt; <co id="co-vx-vid"/>
   &lt;topic&gt;Several vulnerabilities found in Foo&lt;/topic&gt; <co id="co-vx-top"/>
   &lt;affects&gt;
     &lt;package&gt;
       &lt;name&gt;foo&lt;/name&gt; <co id="co-vx-nam"/>
       &lt;name&gt;foo-devel&lt;/name&gt;
       &lt;name&gt;ja-foo&lt;/name&gt;
       &lt;range&gt;&lt;ge&gt;1.6&lt;/ge&gt;&lt;lt&gt;1.9&lt;/lt&gt;&lt;/range&gt; <co id="co-vx-rng"/>
       &lt;range&gt;&lt;ge&gt;2.*&lt;/ge&gt;&lt;lt&gt;2.4_1&lt;/lt&gt;&lt;/range&gt;
       &lt;range&gt;&lt;eq&gt;3.0b1&lt;/eq&gt;&lt;/range&gt;
     &lt;/package&gt;
     &lt;package&gt;
       &lt;name&gt;openfoo&lt;/name&gt; <co id="co-vx-nm2"/>
       &lt;range&gt;&lt;lt&gt;1.10_7&lt;/lt&gt;&lt;/range&gt; <co id="co-vx-epo"/>
       &lt;range&gt;&lt;ge&gt;1.2,1&lt;/ge&gt;&lt;lt&gt;1.3_1,1&lt;/lt&gt;&lt;/range&gt;
     &lt;/package&gt;
   &lt;/affects&gt;
   &lt;description&gt;
     &lt;body xmlns="http://www.w3.org/1999/xhtml"&gt;
       &lt;p&gt;J. Random Hacker reports:&lt;/p&gt; <co id="co-vx-bdy"/>
       &lt;blockquote
         cite="http://j.r.hacker.com/advisories/1"&gt;
         &lt;p&gt;Several issues in the Foo software may be exploited
           via carefully crafted QUUX requests.  These requests will
           permit the injection of Bar code, mumble theft, and the
           readability of the Foo administrator account.&lt;/p&gt;
       &lt;/blockquote&gt;
     &lt;/body&gt;
   &lt;/description&gt;
   &lt;references&gt; <co id="co-vx-ref"/>
     &lt;freebsdsa&gt;SA-10:75.foo&lt;/freebsdsa&gt; <co id="co-vx-fsa"/>
     &lt;freebsdpr&gt;ports/987654&lt;/freebsdpr&gt; <co id="co-vx-fpr"/>
     &lt;cvename&gt;CAN-2010-0201&lt;/cvename&gt; <co id="co-vx-cve"/>
     &lt;cvename&gt;CAN-2010-0466&lt;/cvename&gt;
     &lt;bid&gt;96298&lt;/bid&gt; <co id="co-vx-bid"/>
     &lt;certsa&gt;CA-2010-99&lt;/certsa&gt; <co id="co-vx-cts"/>
     &lt;certvu&gt;740169&lt;/certvu&gt; <co id="co-vx-ctv"/>
     &lt;uscertsa&gt;SA10-99A&lt;/uscertsa&gt; <co id="co-vx-ucs"/>
     &lt;uscertta&gt;SA10-99A&lt;/uscertta&gt; <co id="co-vx-uct"/>
     &lt;mlist msgid="201075606@hacker.com"&gt;http://marc.theaimsgroup.com/?l=bugtraq&amp;amp;m=203886607825605&lt;/mlist&gt; <co id="co-vx-mls"/>
     &lt;url&gt;http://j.r.hacker.com/advisories/1&lt;/url&gt; <co id="co-vx-url"/>
   &lt;/references&gt;
   &lt;dates&gt;
     &lt;discovery&gt;2010-05-25&lt;/discovery&gt; <co id="co-vx-dsc"/>
     &lt;entry&gt;2010-07-13&lt;/entry&gt; <co id="co-vx-ent"/>
     &lt;modified&gt;2010-09-17&lt;/modified&gt; <co id="co-vx-mod"/>
   &lt;/dates&gt;
 &lt;/vuln&gt;</programlisting>
 
 	<para>The tag names are supposed to be self-explanatory
 	  so we shall take a closer look only at fields you will need
 	  to fill in by yourself:</para>
 
 	<calloutlist>
 	  <callout arearefs="co-vx-vid">
 	    <para>This is the top-level tag of a VuXML entry.  It has
 	      a mandatory attribute, <literal>vid</literal>,
 	      specifying a universally unique identifier (UUID) for
 	      this entry (in quotes).  You should generate a UUID for
 	      each new VuXML entry (and do not forget to substitute it
 	      for the template UUID unless you are writing the entry
 	      from scratch).  You can use &man.uuidgen.1; to generate
 	      a VuXML UUID.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-top">
 	    <para>This is a one-line description of the issue
 	      found.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-nam">
 	    <para>The names of packages affected are listed there.
 	      Multiple names can be given since several packages may
 	      be based on a single master port or software product.
 	      This may include stable and development branches,
 	      localized versions, and slave ports featuring different
 	      choices of important build-time configuration
 	      options.</para>
 
 	    <important>
 	      <para>It is your responsibility to find all such related
 		packages when writing a VuXML entry.  Keep in mind
 		that <literal>make search name=foo</literal> is your
 		friend.  The primary points to look for are as
 		follows:</para>
 
 	      <itemizedlist>
 		<listitem>
 		  <para>the <filename>foo-devel</filename> variant
 		    for a <filename>foo</filename> port;</para>
 		</listitem>
 
 		<listitem>
 		  <para>other variants with a suffix like
 		    <literal>-a4</literal> (for print-related
 		    packages), <literal>-without-gui</literal> (for
 		    packages with X support disabled), or
 		    similar;</para>
 		</listitem>
 
 		<listitem>
 		  <para><literal>jp-</literal>,
 		    <literal>ru-</literal>, <literal>zh-</literal>,
 		    and other possible localized variants in the
 		    corresponding national categories of the ports
 		    collection.</para>
 		</listitem>
 	      </itemizedlist>
 	    </important>
 	  </callout>
 
 	  <callout arearefs="co-vx-rng">
 	    <para>Affected versions of the package(s) are specified
 	      there as one or more ranges using a combination of
 	      <literal>&lt;lt&gt;</literal>,
 	      <literal>&lt;le&gt;</literal>,
 	      <literal>&lt;eq&gt;</literal>,
 	      <literal>&lt;ge&gt;</literal>, and
 	      <literal>&lt;gt&gt;</literal> elements.  The version
 	      ranges given should not overlap.</para>
 
 	    <para>In a range specification, <literal>*</literal>
 	      (asterisk) denotes the smallest version number.  In
 	      particular, <literal>2.*</literal> is less than
 	      <literal>2.a</literal>.  Therefore an asterisk may be
 	      used for a range to match all possible
 	      <literal>alpha</literal>, <literal>beta</literal>, and
 	      <literal>RC</literal> versions.  For instance,
 	      <literal>&lt;ge&gt;2.*&lt;/ge&gt;&lt;lt&gt;3.*&lt;/lt&gt;</literal>
 	      will selectively match every <literal>2.x</literal>
 	      version while
 	      <literal>&lt;ge&gt;2.0&lt;/ge&gt;&lt;lt&gt;3.0&lt;/lt&gt;</literal>
 	      will not since the latter misses
 	      <literal>2.r3</literal> and matches
 	      <literal>3.b</literal>.</para>
 
 	    <para>The above example specifies that affected are
 	      versions from <literal>1.6</literal> to
 	      <literal>1.9</literal> inclusive, versions
 	      <literal>2.x</literal> before <literal>2.4_1</literal>,
 	      and version <literal>3.0b1</literal>.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-nm2">
 	    <para>Several related package groups (essentially, ports)
 	      can be listed in the <literal>&lt;affected&gt;</literal>
 	      section.  This can be used if several software products
 	      (say FooBar, FreeBar and OpenBar) grow from the same
 	      code base and still share its bugs and vulnerabilities.
 	      Note the difference from listing multiple names within a
 	      single &lt;package&gt; section.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-epo">
 	    <para>The version ranges should allow for
 	      <makevar>PORTEPOCH</makevar> and
 	      <makevar>PORTREVISION</makevar> if applicable.  Please
 	      remember that according to the collation rules, a
 	      version with a non-zero <makevar>PORTEPOCH</makevar> is
 	      greater than any version without
 	      <makevar>PORTEPOCH</makevar>, e.g.,
 	      <literal>3.0,1</literal> is greater than
 	      <literal>3.1</literal> or even than
 	      <literal>8.9</literal>.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-bdy">
 	    <para>This is a summary of the issue.  XHTML is used in
 	      this field.  At least enclosing
 	      <literal>&lt;p&gt;</literal> and
 	      <literal>&lt;/p&gt;</literal> should appear.  More
 	      complex mark-up may be used, but only for the sake of
 	      accuracy and clarity: No eye candy please.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-ref">
 	    <para>This section contains references to relevant
 	      documents.  As many references as apply are
 	      encouraged.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-fsa">
 	    <para>This is a <ulink
 		url="http://www.freebsd.org/security/#adv">FreeBSD
 		security advisory</ulink>.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-fpr">
 	    <para>This is a <ulink
 		url="http://www.freebsd.org/support.html#gnats">FreeBSD
 		problem report</ulink>.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-cve">
 	    <para>This is a <ulink
 		url="http://www.cve.mitre.org/">MITRE
 		CVE</ulink> identifier.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-bid">
 	    <para>This is a <ulink
 		url="http://www.securityfocus.com/bid">SecurityFocus
 		Bug ID</ulink>.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-cts">
 	    <para>This is a
 	      <ulink url="http://www.cert.org/">US-CERT</ulink>
 	      security advisory.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-ctv">
 	    <para>This is a <ulink
 		url="http://www.cert.org/">US-CERT</ulink>
 	      vulnerability note.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-ucs">
 	    <para>This is a <ulink
 		url="http://www.cert.org/">US-CERT</ulink>
 	      Cyber Security Alert.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-uct">
 	    <para>This is a <ulink
 		url="http://www.cert.org/">US-CERT</ulink>
 	      Technical Cyber Security Alert.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-mls">
 	    <para>This is a URL to an archived posting in a mailing
 	      list.  The attribute <literal>msgid</literal> is
 	      optional and may specify the message ID of the
 	      posting.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-url">
 	    <para>This is a generic URL.  It should be used only if
 	      none of the other reference categories apply.</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-dsc">
 	    <para>This is the date when the issue was disclosed
 	      (<replaceable>YYYY-MM-DD</replaceable>).</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-ent">
 	    <para>This is the date when the entry was added
 	      (<replaceable>YYYY-MM-DD</replaceable>).</para>
 	  </callout>
 
 	  <callout arearefs="co-vx-mod">
 	    <para>This is the date when any information in the entry
 	      was last modified
 	      (<replaceable>YYYY-MM-DD</replaceable>).  New entries
 	      must not include this field.  It should be added upon
 	      editing an existing entry.</para>
 	  </callout>
 	</calloutlist>
       </sect2>
 
       <sect2 id="security-notify-vuxml-testing">
 	<title>Testing Your Changes to the VuXML Database</title>
 
 	<para>Assume you just wrote or filled in an entry for a
 	  vulnerability in the package <literal>clamav</literal> that
 	  has been fixed in version <literal>0.65_7</literal>.</para>
 
 	<para>As a prerequisite, you need to
 	  <emphasis>install</emphasis> fresh versions of the ports
 	  <filename role="package">ports-mgmt/portaudit</filename>,
 	  <filename role="package">ports-mgmt/portaudit-db</filename>,
 	  and <filename
 	    role="package">security/vuxml</filename>.</para>
 
 	<note>
 	  <para>To run <command>packaudit</command> you must have
 	    permission to write to its
 	    <filename><makevar>DATABASEDIR</makevar></filename>,
 	    typically <filename>/var/db/portaudit</filename>.</para>
 
 	  <para>To use a different directory set the
 	    <filename><makevar>DATABASEDIR</makevar></filename>
 	    environment variable to a different location.</para>
 
 	  <para>If you are working in a directory other than
 	    <filename>${PORTSDIR}/security/vuxml</filename> set the
 	    <filename><makevar>VUXMLDIR</makevar></filename>
 	    environment variable to the directory where
 	    <filename>vuln.xml</filename> is located.</para>
 	</note>
 
 	<para>First, check whether there already is an entry for this
 	  vulnerability.  If there were such an entry, it would match
 	  the previous version of the package,
 	  <literal>0.65_6</literal>:</para>
 
 	<screen>&prompt.user; <userinput>packaudit</userinput>
 &prompt.user; <userinput>portaudit clamav-0.65_6</userinput></screen>
 
 	<para>If there is none found, you have the green light to add
 	  a new entry for this vulnerability.</para>
 
 	<screen>&prompt.user; <userinput>cd ${PORTSDIR}/security/vuxml</userinput>
 &prompt.user; <userinput>make newentry</userinput></screen>
 
 	<para>When you are done verify its syntax and
 	  formatting.</para>
 
 	<screen>&prompt.user; <userinput>make validate</userinput></screen>
 
 	<note>
 	  <para>You will need at least one of the following packages
 	    installed: <filename
 	      role="package">textproc/libxml2</filename>, <filename
 	      role="package">textproc/jade</filename>.</para>
 	</note>
 
 	<para>Now rebuild the <command>portaudit</command> database
 	  from the VuXML file:</para>
 
 	<screen>&prompt.user; <userinput>packaudit</userinput></screen>
 
 	<para>To verify that the <literal>&lt;affected&gt;</literal>
 	  section of your entry will match correct package(s), issue
 	  the following command:</para>
 
 	<screen>&prompt.user; <userinput>portaudit -f /usr/ports/INDEX -r <replaceable>uuid</replaceable></userinput></screen>
 
 	<note>
 	  <para>Please refer to &man.portaudit.1; for better
 	    understanding of the command syntax.</para>
 	</note>
 
 	<para>Make sure that your entry produces no spurious matches
 	  in the output.</para>
 
 	<para>Now check whether the right package versions are matched
 	  by your entry:</para>
 
 	<screen>&prompt.user; <userinput>portaudit clamav-0.65_6 clamav-0.65_7</userinput>
 Affected package: clamav-0.65_6 (matched by clamav&lt;0.65_7)
 Type of problem: clamav remote denial-of-service.
 Reference: &lt;http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-0020ed76ef5a.html&gt;
 
 1 problem(s) found.</screen>
 
 	<para>The former version should match while the
 	  latter one should not.</para>
 
 	<para>Finally, verify whether the web page generated from the
 	  VuXML database looks like expected:</para>
 
 	<screen>&prompt.user; <userinput>mkdir -p ~/public_html/portaudit</userinput>
 &prompt.user; <userinput>packaudit</userinput>
 &prompt.user; <userinput>lynx ~/public_html/portaudit/74a9541d-5d6c-11d8-80e3-0020ed76ef5a.html</userinput></screen>
       </sect2>
     </sect1>
   </chapter>
 
   <chapter id="porting-dads">
     <title>Dos and Don'ts</title>
 
     <sect1 id="dads-intro">
       <title>Introduction</title>
 
       <para>Here is a list of common dos and don'ts that you encounter
 	during the porting process.  You should check your own port
 	against this list, but you can also check ports in the <ulink
 	  url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">PR
 	database</ulink> that others have submitted.  Submit any
 	comments on ports you check as described in <ulink
 	  url="&url.articles.contributing;/contrib-how.html#CONTRIB-GENERAL">Bug
 	Reports and General Commentary</ulink>.  Checking ports in the
 	PR database will both make it faster for us to commit them,
 	and prove that you know what you are doing.</para>
     </sect1>
 
     <sect1 id="porting-wrkdir">
       <title><makevar>WRKDIR</makevar></title>
 
       <para>Do not write anything to files outside
 	<makevar>WRKDIR</makevar>.  <makevar>WRKDIR</makevar> is the
 	only place that is guaranteed to be writable during the port
 	build (see <ulink
 	  url="&url.books.handbook;/ports-using.html#PORTS-CD">
 	  installing ports from a CDROM</ulink> for an example of
 	building ports from a read-only tree).  If you need to modify
 	one of the
 	<filename>pkg-<replaceable>*</replaceable></filename> files,
 	do so by <link
 	  linkend="porting-pkgfiles">redefining a variable</link>, not
 	by writing over it.</para>
     </sect1>
 
     <sect1 id="porting-wrkdirprefix">
       <title><makevar>WRKDIRPREFIX</makevar></title>
 
       <para>Make sure your port honors
 	<makevar>WRKDIRPREFIX</makevar>.  Most ports do not have to
 	worry about this.  In particular, if you are referring to a
 	<makevar>WRKDIR</makevar> of another port, note that the
 	correct location is
 	<filename><makevar>WRKDIRPREFIX</makevar><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename>
 	not
 	<filename><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename>
 	or
 	<filename><makevar>.CURDIR</makevar>/../../<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename>
 	or some such.</para>
 
       <para>Also, if you are defining <makevar>WRKDIR</makevar>
 	yourself, make sure you prepend
 	<literal>&dollar;{WRKDIRPREFIX}&dollar;{.CURDIR}</literal> in
 	the front.</para>
     </sect1>
 
     <sect1 id="porting-versions">
       <title>Differentiating Operating Systems and OS Versions</title>
 
       <para>You may come across code that needs modifications or
 	conditional compilation based upon what version of Unix it is
 	running under.  If you need to make such changes to the code
 	for conditional compilation, make sure you make the changes as
 	general as possible so that we can back-port code to older
 	FreeBSD systems and cross-port to other BSD systems such as
 	4.4BSD from CSRG, BSD/386, 386BSD, NetBSD, and OpenBSD.</para>
 
       <para>The preferred way to tell 4.3BSD/Reno (1990) and newer
 	versions of the BSD code apart is by using the
 	<literal>BSD</literal> macro defined in <ulink
 	  url="http://svnweb.freebsd.org/base/head/sys/sys/param.h?view=markup">sys/param.h</ulink>.
 	Hopefully that file is already included; if not, add the
 	code:</para>
 
       <programlisting>#if (defined(__unix__) || defined(unix)) &amp;&amp; !defined(USG)
 #include &lt;sys/param.h&gt;
 #endif</programlisting>
 
       <para>to the proper place in the <filename>.c</filename> file.
 	We believe that every system that defines these two symbols
 	has <filename>sys/param.h</filename>.  If you find a system
 	that does not, we would like to know.  Please send mail to the
 	&a.ports;.</para>
 
       <para>Another way is to use the GNU Autoconf style of doing
 	this:</para>
 
       <programlisting>#ifdef HAVE_SYS_PARAM_H
 #include &lt;sys/param.h&gt;
 #endif</programlisting>
 
       <para>Do not forget to add <literal>-DHAVE_SYS_PARAM_H</literal>
 	to the <makevar>CFLAGS</makevar> in the
 	<filename>Makefile</filename> for this method.</para>
 
       <para>Once you have <filename>sys/param.h</filename> included,
 	you may use:</para>
 
       <programlisting>#if (defined(BSD) &amp;&amp; (BSD &gt;= 199103))</programlisting>
 
       <para>to detect if the code is being compiled on a 4.3 Net2 code
 	base or newer (e.g., FreeBSD 1.x, 4.3/Reno, NetBSD 0.9,
 	386BSD, BSD/386 1.1 and below).</para>
 
       <para>Use:</para>
 
       <programlisting>#if (defined(BSD) &amp;&amp; (BSD &gt;= 199306))</programlisting>
 
       <para>to detect if the code is being compiled on a 4.4 code base
 	or newer (e.g., FreeBSD 2.x, 4.4, NetBSD 1.0, BSD/386 2.0 or
 	above).</para>
 
       <para>The value of the <literal>BSD</literal> macro is
 	<literal>199506</literal> for the 4.4BSD-Lite2 code base.
 	This is stated for informational purposes only.  It should not
 	be used to distinguish between versions of FreeBSD based only
 	on 4.4-Lite versus versions that have merged in changes from
 	4.4-Lite2.  The <literal>__FreeBSD__</literal> macro should be
 	used instead.</para>
 
       <para>Use sparingly:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><literal>__FreeBSD__</literal> is defined in all
 	    versions of FreeBSD.  Use it if the change you are making
 	    <emphasis>only</emphasis> affects FreeBSD.  Porting
 	    gotchas like the use of <literal>sys_errlist[]</literal>
 	    versus <function>strerror()</function> are Berkeley-isms,
 	    not FreeBSD changes.</para>
 	</listitem>
 
 	<listitem>
 	  <para>In FreeBSD 2.x, <literal>__FreeBSD__</literal> is
 	    defined to be <literal>2</literal>.  In earlier versions,
 	    it is <literal>1</literal>.  Later versions always bump it
 	    to match their major version number.</para>
 	</listitem>
 
 	<listitem>
 	  <para>If you need to tell the difference between a FreeBSD
 	    1.x system and a FreeBSD 2.x or above system, usually the
 	    right answer is to use the <literal>BSD</literal> macros
 	    described above.  If there actually is a FreeBSD specific
 	    change (such as special shared library options when using
 	    <command>ld</command>) then it is OK to use
 	    <literal>__FreeBSD__</literal> and <literal>#if
 	      __FreeBSD__ &gt; 1</literal> to detect a FreeBSD 2.x and
 	    later system.  If you need more granularity in detecting
 	    FreeBSD systems since 2.0-RELEASE you can use the
 	    following:</para>
 
 	  <programlisting>#if __FreeBSD__ &gt;= 2
 #include &lt;osreldate.h&gt;
 #    if __FreeBSD_version &gt;= 199504
 	 /* 2.0.5+ release specific code here */
 #    endif
 #endif</programlisting>
 	</listitem>
       </itemizedlist>
 
       <para>In the hundreds of ports that have been done, there have
 	only been one or two cases where
 	<literal>__FreeBSD__</literal> should have been used.  Just
 	because an earlier port screwed up and used it in the wrong
 	place does not mean you should do so too.</para>
     </sect1>
 
     <sect1 id="freebsd-versions">
       <title><literal>__FreeBSD_version</literal> Values</title>
 
       <para>Here is a convenient list of
 	<literal>__FreeBSD_version</literal> values as defined in
 	<ulink
 	  url="http://svnweb.FreeBSD.org/base/head/sys/sys/param.h?view=markup">sys/param.h</ulink>:</para>
 
       <table frame="none">
 	<title><literal>__FreeBSD_version</literal> Values</title>
 
 	<tgroup cols="3">
 	  <thead>
 	    <row>
 	      <entry>Value</entry>
 	      <entry>Date</entry>
 	      <entry>Release</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>119411</entry>
 	      <entry></entry>
 	      <entry>2.0-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>199501, 199503</entry>
 	      <entry>March 19, 1995</entry>
 	      <entry>2.1-CURRENT</entry>
 	    </row>
 
 	    <row>
 	      <entry>199504</entry>
 	      <entry>April 9, 1995</entry>
 	      <entry>2.0.5-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>199508</entry>
 	      <entry>August 26, 1995</entry>
 	      <entry>2.2-CURRENT before 2.1</entry>
 	    </row>
 
 	    <row>
 	      <entry>199511</entry>
 	      <entry>November 10, 1995</entry>
 	      <entry>2.1.0-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>199512</entry>
 	      <entry>November 10, 1995</entry>
 	      <entry>2.2-CURRENT before 2.1.5</entry>
 	    </row>
 
 	    <row>
 	      <entry>199607</entry>
 	      <entry>July 10, 1996</entry>
 	      <entry>2.1.5-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>199608</entry>
 	      <entry>July 12, 1996</entry>
 	      <entry>2.2-CURRENT before 2.1.6</entry>
 	    </row>
 
 	    <row>
 	      <entry>199612</entry>
 	      <entry>November 15, 1996</entry>
 	      <entry>2.1.6-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>199612</entry>
 	      <entry></entry>
 	      <entry>2.1.7-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>220000</entry>
 	      <entry>February 19, 1997</entry>
 	      <entry>2.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>(not changed)</entry>
 	      <entry></entry>
 	      <entry>2.2.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>(not changed)</entry>
 	      <entry></entry>
 	      <entry>2.2-STABLE after 2.2.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>221001</entry>
 	      <entry>April 15, 1997</entry>
 	      <entry>2.2-STABLE after texinfo-3.9</entry>
 	    </row>
 
 	    <row>
 	      <entry>221002</entry>
 	      <entry>April 30, 1997</entry>
 	      <entry>2.2-STABLE after top</entry>
 	    </row>
 
 	    <row>
 	      <entry>222000</entry>
 	      <entry>May 16, 1997</entry>
 	      <entry>2.2.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>222001</entry>
 	      <entry>May 19, 1997</entry>
 	      <entry>2.2-STABLE after 2.2.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>225000</entry>
 	      <entry>October 2, 1997</entry>
 	      <entry>2.2.5-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>225001</entry>
 	      <entry>November 20, 1997</entry>
 	      <entry>2.2-STABLE after 2.2.5-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>225002</entry>
 	      <entry>December 27, 1997</entry>
 	      <entry>2.2-STABLE after ldconfig -R merge</entry>
 	    </row>
 
 	    <row>
 	      <entry>226000</entry>
 	      <entry>March 24, 1998</entry>
 	      <entry>2.2.6-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>227000</entry>
 	      <entry>July 21, 1998</entry>
 	      <entry>2.2.7-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>227001</entry>
 	      <entry>July 21, 1998</entry>
 	      <entry>2.2-STABLE after 2.2.7-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>227002</entry>
 	      <entry>September 19, 1998</entry>
 	      <entry>2.2-STABLE after &man.semctl.2; change</entry>
 	    </row>
 
 	    <row>
 	      <entry>228000</entry>
 	      <entry>November 29, 1998</entry>
 	      <entry>2.2.8-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>228001</entry>
 	      <entry>November 29, 1998</entry>
 	      <entry>2.2-STABLE after 2.2.8-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>300000</entry>
 	      <entry>February 19, 1996</entry>
 	      <entry>3.0-CURRENT before &man.mount.2; change</entry>
 	    </row>
 
 	    <row>
 	      <entry>300001</entry>
 	      <entry>September 24, 1997</entry>
 	      <entry>3.0-CURRENT after &man.mount.2; change</entry>
 	    </row>
 
 	    <row>
 	      <entry>300002</entry>
 	      <entry>June 2, 1998</entry>
 	      <entry>3.0-CURRENT after &man.semctl.2; change</entry>
 	    </row>
 
 	    <row>
 	      <entry>300003</entry>
 	      <entry>June 7, 1998</entry>
 	      <entry>3.0-CURRENT after ioctl arg changes</entry>
 	    </row>
 
 	    <row>
 	      <entry>300004</entry>
 	      <entry>September 3, 1998</entry>
 	      <entry>3.0-CURRENT after ELF conversion</entry>
 	    </row>
 
 	    <row>
 	      <entry>300005</entry>
 	      <entry>October 16, 1998</entry>
 	      <entry>3.0-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>300006</entry>
 	      <entry>October 16, 1998</entry>
 	      <entry>3.0-CURRENT after 3.0-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>300007</entry>
 	      <entry>January 22, 1999</entry>
 	      <entry>3.0-STABLE after 3/4 branch</entry>
 	    </row>
 
 	    <row>
 	      <entry>310000</entry>
 	      <entry>February 9, 1999</entry>
 	      <entry>3.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>310001</entry>
 	      <entry>March 27, 1999</entry>
 	      <entry>3.1-STABLE after 3.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>310002</entry>
 	      <entry>April 14, 1999</entry>
 	      <entry>3.1-STABLE after C++ constructor/destructor order
 		change</entry>
 	    </row>
 
 	    <row>
 	      <entry>320000</entry>
 	      <entry></entry>
 	      <entry>3.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>320001</entry>
 	      <entry>May 8, 1999</entry>
 	      <entry>3.2-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>320002</entry>
 	      <entry>August 29, 1999</entry>
 	      <entry>3.2-STABLE after binary-incompatible IPFW and
 		socket changes</entry>
 	    </row>
 
 	    <row>
 	      <entry>330000</entry>
 	      <entry>September 2, 1999</entry>
 	      <entry>3.3-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>330001</entry>
 	      <entry>September 16, 1999</entry>
 	      <entry>3.3-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>330002</entry>
 	      <entry>November 24, 1999</entry>
 	      <entry>3.3-STABLE after adding &man.mkstemp.3;
 		to libc</entry>
 	    </row>
 
 	    <row>
 	      <entry>340000</entry>
 	      <entry>December 5, 1999</entry>
 	      <entry>3.4-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>340001</entry>
 	      <entry>December 17, 1999</entry>
 	      <entry>3.4-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>350000</entry>
 	      <entry>June 20, 2000</entry>
 	      <entry>3.5-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>350001</entry>
 	      <entry>July 12, 2000</entry>
 	      <entry>3.5-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>400000</entry>
 	      <entry>January 22, 1999</entry>
 	      <entry>4.0-CURRENT after 3.4 branch</entry>
 	    </row>
 
 	    <row>
 	      <entry>400001</entry>
 	      <entry>February 20, 1999</entry>
 	      <entry>4.0-CURRENT after change in dynamic linker
 		handling</entry>
 	    </row>
 
 	    <row>
 	      <entry>400002</entry>
 	      <entry>March 13, 1999</entry>
 	      <entry>4.0-CURRENT after C++ constructor/destructor
 		order change</entry>
 	    </row>
 
 	    <row>
 	      <entry>400003</entry>
 	      <entry>March 27, 1999</entry>
 	      <entry>4.0-CURRENT after functioning
 		&man.dladdr.3;</entry>
 	    </row>
 
 	    <row>
 	      <entry>400004</entry>
 	      <entry>April 5, 1999</entry>
 	      <entry>4.0-CURRENT after __deregister_frame_info dynamic
 		linker bug fix (also 4.0-CURRENT after EGCS 1.1.2
 		integration)</entry>
 	    </row>
 
 	    <row>
 	      <entry>400005</entry>
 	      <entry>April 27, 1999</entry>
 	      <entry>4.0-CURRENT after &man.suser.9; API change
 		(also 4.0-CURRENT after newbus)</entry>
 	    </row>
 
 	    <row>
 	      <entry>400006</entry>
 	      <entry>May 31, 1999</entry>
 	      <entry>4.0-CURRENT after cdevsw registration
 		change</entry>
 	    </row>
 
 	    <row>
 	      <entry>400007</entry>
 	      <entry>June 17, 1999</entry>
 	      <entry>4.0-CURRENT after the addition of so_cred for
 		socket level credentials</entry>
 	    </row>
 
 	    <row>
 	      <entry>400008</entry>
 	      <entry>June 20, 1999</entry>
 	      <entry>4.0-CURRENT after the addition of a poll syscall
 		wrapper to libc_r</entry>
 	    </row>
 
 	    <row>
 	      <entry>400009</entry>
 	      <entry>July 20, 1999</entry>
 	      <entry>4.0-CURRENT after the change of the kernel's
 		<literal>dev_t</literal> type to <literal>struct
 		  specinfo</literal> pointer</entry>
 	    </row>
 
 	    <row>
 	      <entry>400010</entry>
 	      <entry>September 25, 1999</entry>
 	      <entry>4.0-CURRENT after fixing a hole
 		in &man.jail.2;</entry>
 	    </row>
 
 	    <row>
 	      <entry>400011</entry>
 	      <entry>September 29, 1999</entry>
 	      <entry>4.0-CURRENT after the <literal>sigset_t</literal>
 		datatype change</entry>
 	    </row>
 
 	    <row>
 	      <entry>400012</entry>
 	      <entry>November 15, 1999</entry>
 	      <entry>4.0-CURRENT after the cutover to the GCC 2.95.2
 		compiler</entry>
 	    </row>
 
 	    <row>
 	      <entry>400013</entry>
 	      <entry>December 4, 1999</entry>
 	      <entry>4.0-CURRENT after adding pluggable linux-mode
 		ioctl handlers</entry>
 	    </row>
 
 	    <row>
 	      <entry>400014</entry>
 	      <entry>January 18, 2000</entry>
 	      <entry>4.0-CURRENT after importing OpenSSL</entry>
 	    </row>
 
 	    <row>
 	      <entry>400015</entry>
 	      <entry>January 27, 2000</entry>
 	      <entry>4.0-CURRENT after the C++ ABI change in GCC
 		2.95.2 from -fvtable-thunks to -fno-vtable-thunks by
 		default</entry>
 	    </row>
 
 	    <row>
 	      <entry>400016</entry>
 	      <entry>February 27, 2000</entry>
 	      <entry>4.0-CURRENT after importing OpenSSH</entry>
 	    </row>
 
 	    <row>
 	      <entry>400017</entry>
 	      <entry>March 13, 2000</entry>
 	      <entry>4.0-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>400018</entry>
 	      <entry>March 17, 2000</entry>
 	      <entry>4.0-STABLE after 4.0-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>400019</entry>
 	      <entry>May 5, 2000</entry>
 	      <entry>4.0-STABLE after the introduction of delayed
 		checksums.</entry>
 	    </row>
 
 	    <row>
 	      <entry>400020</entry>
 	      <entry>June 4, 2000</entry>
 	      <entry>4.0-STABLE after merging libxpg4 code into
 		libc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>400021</entry>
 	      <entry>July 8, 2000</entry>
 	      <entry>4.0-STABLE after upgrading Binutils to 2.10.0,
 		ELF branding changes, and tcsh in the base
 		system.</entry>
 	    </row>
 
 	    <row>
 	      <entry>410000</entry>
 	      <entry>July 14, 2000</entry>
 	      <entry>4.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>410001</entry>
 	      <entry>July 29, 2000</entry>
 	      <entry>4.1-STABLE after 4.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>410002</entry>
 	      <entry>September 16, 2000</entry>
 	      <entry>4.1-STABLE after &man.setproctitle.3; moved from
 		libutil to libc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>411000</entry>
 	      <entry>September 25, 2000</entry>
 	      <entry>4.1.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>411001</entry>
 	      <entry></entry>
 	      <entry>4.1.1-STABLE after 4.1.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>420000</entry>
 	      <entry>October 31, 2000</entry>
 	      <entry>4.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>420001</entry>
 	      <entry>January 10, 2001</entry>
 	      <entry>4.2-STABLE after combining libgcc.a and
 		libgcc_r.a, and associated GCC linkage
 		changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>430000</entry>
 	      <entry>March 6, 2001</entry>
 	      <entry>4.3-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>430001</entry>
 	      <entry>May 18, 2001</entry>
 	      <entry>4.3-STABLE after wint_t introduction.</entry>
 	    </row>
 
 	    <row>
 	      <entry>430002</entry>
 	      <entry>July 22, 2001</entry>
 	      <entry>4.3-STABLE after PCI powerstate API
 		merge.</entry>
 	    </row>
 
 	    <row>
 	      <entry>440000</entry>
 	      <entry>August 1, 2001</entry>
 	      <entry>4.4-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>440001</entry>
 	      <entry>October 23, 2001</entry>
 	      <entry>4.4-STABLE after d_thread_t introduction.</entry>
 	    </row>
 
 	    <row>
 	      <entry>440002</entry>
 	      <entry>November 4, 2001</entry>
 	      <entry>4.4-STABLE after mount structure changes (affects
 		filesystem klds).</entry>
 	    </row>
 
 	    <row>
 	      <entry>440003</entry>
 	      <entry>December 18, 2001</entry>
 	      <entry>4.4-STABLE after the userland components of smbfs
 		were imported.</entry>
 	    </row>
 
 	    <row>
 	      <entry>450000</entry>
 	      <entry>December 20, 2001</entry>
 	      <entry>4.5-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>450001</entry>
 	      <entry>February 24, 2002</entry>
 	      <entry>4.5-STABLE after the usb structure element
 		rename.</entry>
 	    </row>
 
 	    <row>
 	      <entry>450004</entry>
 	      <entry>April 16, 2002</entry>
 	      <entry>4.5-STABLE after the
 		<literal>sendmail_enable</literal> &man.rc.conf.5;
 		variable was made to take the value
 		<literal>NONE</literal>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>450005</entry>
 	      <entry>April 27, 2002</entry>
 	      <entry>4.5-STABLE after moving to XFree86 4 by default
 		for package builds.</entry>
 	    </row>
 
 	    <row>
 	      <entry>450006</entry>
 	      <entry>May 1, 2002</entry>
 	      <entry>4.5-STABLE after accept filtering was fixed so
 		that is no longer susceptible to an easy DoS.</entry>
 	    </row>
 
 	    <row>
 	      <entry>460000</entry>
 	      <entry>June 21, 2002</entry>
 	      <entry>4.6-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>460001</entry>
 	      <entry>June 21, 2002</entry>
 	      <entry>4.6-STABLE &man.sendfile.2; fixed to comply with
 		documentation, not to count any headers sent against
 		the amount of data to be sent from the file.</entry>
 	    </row>
 
 	    <row>
 	      <entry>460002</entry>
 	      <entry>July 19, 2002</entry>
 	      <entry>4.6.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>460100</entry>
 	      <entry>June 26, 2002</entry>
 	      <entry>4.6-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>460101</entry>
 	      <entry>June 26, 2002</entry>
 	      <entry>4.6-STABLE after MFC of `sed -i'.</entry>
 	    </row>
 
 	    <row>
 	      <entry>460102</entry>
 	      <entry>September 1, 2002</entry>
 	      <entry>4.6-STABLE after MFC of many new pkg_install
 		features from the HEAD.</entry>
 	    </row>
 
 	    <row>
 	      <entry>470000</entry>
 	      <entry>October 8, 2002</entry>
 	      <entry>4.7-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>470100</entry>
 	      <entry>October 9, 2002</entry>
 	      <entry>4.7-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>470101</entry>
 	      <entry>November 10, 2002</entry>
 	      <entry>Start generated __std{in,out,err}p references
 		rather than __sF.  This changes std{in,out,err} from a
 		compile time expression to a runtime one.</entry>
 	    </row>
 
 	    <row>
 	      <entry>470102</entry>
 	      <entry>January 23, 2003</entry>
 	      <entry>4.7-STABLE after MFC of mbuf changes to replace
 		m_aux mbufs by m_tag's</entry>
 	    </row>
 
 	    <row>
 	      <entry>470103</entry>
 	      <entry>February 14, 2003</entry>
 	      <entry>4.7-STABLE gets OpenSSL 0.9.7</entry>
 	    </row>
 
 	    <row>
 	      <entry>480000</entry>
 	      <entry>March 30, 2003</entry>
 	      <entry>4.8-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>480100</entry>
 	      <entry>April 5, 2003</entry>
 	      <entry>4.8-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>480101</entry>
 	      <entry>May 22, 2003</entry>
 	      <entry>4.8-STABLE after &man.realpath.3; has been made
 		thread-safe</entry>
 	    </row>
 
 	    <row>
 	      <entry>480102</entry>
 	      <entry>August 10, 2003</entry>
 	      <entry>4.8-STABLE 3ware API changes to twe.</entry>
 	    </row>
 
 	    <row>
 	      <entry>490000</entry>
 	      <entry>October 27, 2003</entry>
 	      <entry>4.9-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>490100</entry>
 	      <entry>October 27, 2003</entry>
 	      <entry>4.9-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>490101</entry>
 	      <entry>January 8, 2004</entry>
 	      <entry>4.9-STABLE after e_sid was added to struct
 		kinfo_eproc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>490102</entry>
 	      <entry>February 4, 2004</entry>
 	      <entry>4.9-STABLE after MFC of libmap functionality
 		for rtld.</entry>
 	    </row>
 
 	    <row>
 	      <entry>491000</entry>
 	      <entry>May 25, 2004</entry>
 	      <entry>4.10-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>491100</entry>
 	      <entry>June 1, 2004</entry>
 	      <entry>4.10-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>491101</entry>
 	      <entry>August 11, 2004</entry>
 	      <entry>4.10-STABLE after MFC of revision 20040629 of
 		the package tools</entry>
 	    </row>
 
 	    <row>
 	      <entry>491102</entry>
 	      <entry>November 16, 2004</entry>
 	      <entry>4.10-STABLE after VM fix dealing with unwiring
 		of fictitious pages</entry>
 	    </row>
 
 	    <row>
 	      <entry>492000</entry>
 	      <entry>December 17, 2004</entry>
 	      <entry>4.11-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>492100</entry>
 	      <entry>December 17, 2004</entry>
 	      <entry>4.11-STABLE</entry>
 	    </row>
 
 	    <row>
 	      <entry>492101</entry>
 	      <entry>April 18, 2006</entry>
 	      <entry>4.11-STABLE after adding libdata/ldconfig
 		directories to mtree files.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500000</entry>
 	      <entry>March 13, 2000</entry>
 	      <entry>5.0-CURRENT</entry>
 	    </row>
 
 	    <row>
 	      <entry>500001</entry>
 	      <entry>April 18, 2000</entry>
 	      <entry>5.0-CURRENT after adding addition ELF header
 		fields, and changing our ELF binary branding
 		method.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500002</entry>
 	      <entry>May 2, 2000</entry>
 	      <entry>5.0-CURRENT after kld metadata changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500003</entry>
 	      <entry>May 18, 2000</entry>
 	      <entry>5.0-CURRENT after buf/bio changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500004</entry>
 	      <entry>May 26, 2000</entry>
 	      <entry>5.0-CURRENT after binutils upgrade.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500005</entry>
 	      <entry>June 3, 2000</entry>
 	      <entry>5.0-CURRENT after merging libxpg4 code into
 		libc and after TASKQ interface introduction.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500006</entry>
 	      <entry>June 10, 2000</entry>
 	      <entry>5.0-CURRENT after the addition of AGP
 		interfaces.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500007</entry>
 	      <entry>June 29, 2000</entry>
 	      <entry>5.0-CURRENT after Perl upgrade to 5.6.0</entry>
 	    </row>
 
 	    <row>
 	      <entry>500008</entry>
 	      <entry>July 7, 2000</entry>
 	      <entry>5.0-CURRENT after the update of KAME code to
 		2000/07 sources.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500009</entry>
 	      <entry>July 14, 2000</entry>
 	      <entry>5.0-CURRENT after ether_ifattach() and
 		ether_ifdetach() changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500010</entry>
 	      <entry>July 16, 2000</entry>
 	      <entry>5.0-CURRENT after changing mtree defaults
 		back to original variant, adding -L to follow
 		symlinks.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500011</entry>
 	      <entry>July 18, 2000</entry>
 	      <entry>5.0-CURRENT after kqueue API changed.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500012</entry>
 	      <entry>September 2, 2000</entry>
 	      <entry>5.0-CURRENT after &man.setproctitle.3; moved from
 		libutil to libc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500013</entry>
 	      <entry>September 10, 2000</entry>
 	      <entry>5.0-CURRENT after the first SMPng commit.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500014</entry>
 	      <entry>January 4, 2001</entry>
 	      <entry>5.0-CURRENT after &lt;sys/select.h&gt; moved to
 		&lt;sys/selinfo.h&gt;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500015</entry>
 	      <entry>January 10, 2001</entry>
 	      <entry>5.0-CURRENT after combining libgcc.a and
 		libgcc_r.a, and associated GCC linkage
 		changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500016</entry>
 	      <entry>January 24, 2001</entry>
 	      <entry>5.0-CURRENT after change allowing libc and libc_r
 		to be linked together, deprecating -pthread
 		option.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500017</entry>
 	      <entry>February 18, 2001</entry>
 	      <entry>5.0-CURRENT after switch from struct ucred to
 		struct xucred to stabilize kernel-exported API for
 		mountd et al.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500018</entry>
 	      <entry>February 24, 2001</entry>
 	      <entry>5.0-CURRENT after addition of CPUTYPE make
 		variable for controlling CPU-specific
 		optimizations.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500019</entry>
 	      <entry>June 9, 2001</entry>
 	      <entry>5.0-CURRENT after moving machine/ioctl_fd.h to
 		sys/fdcio.h</entry>
 	    </row>
 
 	    <row>
 	      <entry>500020</entry>
 	      <entry>June 15, 2001</entry>
 	      <entry>5.0-CURRENT after locale names renaming.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500021</entry>
 	      <entry>June 22, 2001</entry>
 	      <entry>5.0-CURRENT after Bzip2 import.
 		Also signifies removal of S/Key.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500022</entry>
 	      <entry>July 12, 2001</entry>
 	      <entry>5.0-CURRENT after SSE support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500023</entry>
 	      <entry>September 14, 2001</entry>
 	      <entry>5.0-CURRENT after KSE Milestone 2.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500024</entry>
 	      <entry>October 1, 2001</entry>
 	      <entry>5.0-CURRENT after d_thread_t,
 		and moving UUCP to ports.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500025</entry>
 	      <entry>October 4, 2001</entry>
 	      <entry>5.0-CURRENT after ABI change for descriptor
 		and creds passing on 64 bit platforms.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500026</entry>
 	      <entry>October 9, 2001</entry>
 	      <entry>5.0-CURRENT after moving to XFree86 4 by default
 		for package builds, and after the new libc strnstr()
 		function was added.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500027</entry>
 	      <entry>October 10, 2001</entry>
 	      <entry>5.0-CURRENT after the new libc strcasestr()
 		function was added.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500028</entry>
 	      <entry>December 14, 2001</entry>
 	      <entry>5.0-CURRENT after the userland components of
 		smbfs were imported.</entry>
 	    </row>
 
 	    <row>
 	      <entry>(not changed)</entry>
 	      <entry></entry>
 	      <entry>5.0-CURRENT after the new C99 specific-width
 		integer types were added.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500029</entry>
 	      <entry>January 29, 2002</entry>
 	      <entry>5.0-CURRENT after a change was made in the return
 		value of &man.sendfile.2;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500030</entry>
 	      <entry>February 15, 2002</entry>
 	      <entry>5.0-CURRENT after the introduction of the
 		type <literal>fflags_t</literal>, which is the
 		appropriate size for file flags.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500031</entry>
 	      <entry>February 24, 2002</entry>
 	      <entry>5.0-CURRENT after the usb structure element
 		rename.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500032</entry>
 	      <entry>March 16, 2002</entry>
 	      <entry>5.0-CURRENT after the introduction of
 		Perl 5.6.1.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500033</entry>
 	      <entry>April 3, 2002</entry>
 	      <entry>5.0-CURRENT after the
 		<literal>sendmail_enable</literal> &man.rc.conf.5;
 		variable was made to take the value
 		<literal>NONE</literal>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500034</entry>
 	      <entry>April 30, 2002</entry>
 	      <entry>5.0-CURRENT after mtx_init() grew a third
 		argument.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500035</entry>
 	      <entry>May 13, 2002</entry>
 	      <entry>5.0-CURRENT with Gcc 3.1.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500036</entry>
 	      <entry>May 17, 2002</entry>
 	      <entry>5.0-CURRENT without Perl in /usr/src</entry>
 	    </row>
 
 	    <row>
 	      <entry>500037</entry>
 	      <entry>May 29, 2002</entry>
 	      <entry>5.0-CURRENT after the addition of
 		&man.dlfunc.3;</entry>
 	    </row>
 
 	    <row>
 	      <entry>500038</entry>
 	      <entry>July 24, 2002</entry>
 	      <entry>5.0-CURRENT after the types of some struct
 		sockbuf members were changed and the structure was
 		reordered.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500039</entry>
 	      <entry>September 1, 2002</entry>
 	      <entry>5.0-CURRENT after GCC 3.2.1 import.
 		Also after headers stopped using
 		_BSD_FOO_T_ and started using _FOO_T_DECLARED.
 		This value can also be used as a conservative
 		estimate of the start of &man.bzip2.1; package
 		support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500040</entry>
 	      <entry>September 20, 2002</entry>
 	      <entry>5.0-CURRENT after various changes to disk
 		functions were made in the name of removing dependency
 		on disklabel structure internals.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500041</entry>
 	      <entry>October 1, 2002</entry>
 	      <entry>5.0-CURRENT after the addition of
 		&man.getopt.long.3; to libc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500042</entry>
 	      <entry>October 15, 2002</entry>
 	      <entry>5.0-CURRENT after Binutils 2.13 upgrade, which
 		included new FreeBSD emulation, vec, and output
 		format.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500043</entry>
 	      <entry>November 1, 2002</entry>
 	      <entry>5.0-CURRENT after adding weak pthread_XXX stubs
 		to libc, obsoleting libXThrStub.so.
 		5.0-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500100</entry>
 	      <entry>January 17, 2003</entry>
 	      <entry>5.0-CURRENT after branching for
 		RELENG_5_0</entry>
 	    </row>
 
 	    <row>
 	      <entry>500101</entry>
 	      <entry>February 19, 2003</entry>
 	      <entry>&lt;sys/dkstat.h&gt; is empty and should
 		not be included.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500102</entry>
 	      <entry>February 25, 2003</entry>
 	      <entry>5.0-CURRENT after the d_mmap_t interface
 		change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500103</entry>
 	      <entry>February 26, 2003</entry>
 	      <entry>5.0-CURRENT after taskqueue_swi changed to run
 		without Giant, and taskqueue_swi_giant added to run
 		with Giant.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500104</entry>
 	      <entry>February 27, 2003</entry>
 	      <entry>cdevsw_add() and cdevsw_remove() no
 		longer exists.
 		Appearance of MAJOR_AUTO allocation facility.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500105</entry>
 	      <entry>March 4, 2003</entry>
 	      <entry>5.0-CURRENT after new cdevsw initialization
 		method.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500106</entry>
 	      <entry>March 8, 2003</entry>
 	      <entry>devstat_add_entry() has been replaced by
 		devstat_new_entry()</entry>
 	    </row>
 
 	    <row>
 	      <entry>500107</entry>
 	      <entry>March 15, 2003</entry>
 	      <entry>Devstat interface change; see sys/sys/param.h
 		1.149</entry>
 	    </row>
 
 	    <row>
 	      <entry>500108</entry>
 	      <entry>March 15, 2003</entry>
 	      <entry>Token-Ring interface changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500109</entry>
 	      <entry>March 25, 2003</entry>
 	      <entry>Addition of vm_paddr_t.</entry>
 	    </row>
 
 	    <row>
 	      <entry>500110</entry>
 	      <entry>March 28, 2003</entry>
 	      <entry>5.0-CURRENT after &man.realpath.3; has been made
 		thread-safe</entry>
 	    </row>
 
 	    <row>
 	      <entry>500111</entry>
 	      <entry>April 9, 2003</entry>
 	      <entry>5.0-CURRENT after &man.usbhid.3; has been synced
 		with NetBSD</entry>
 	    </row>
 
 	    <row>
 	      <entry>500112</entry>
 	      <entry>April 17, 2003</entry>
 	      <entry>5.0-CURRENT after new NSS implementation
 		and addition of POSIX.1 getpw*_r, getgr*_r
 		functions</entry>
 	    </row>
 
 	    <row>
 	      <entry>500113</entry>
 	      <entry>May 2, 2003</entry>
 	      <entry>5.0-CURRENT after removal of the old rc
 		system.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501000</entry>
 	      <entry>June 4, 2003</entry>
 	      <entry>5.1-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501100</entry>
 	      <entry>June 2, 2003</entry>
 	      <entry>5.1-CURRENT after branching for
 		RELENG_5_1.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501101</entry>
 	      <entry>June 29, 2003</entry>
 	      <entry>5.1-CURRENT after correcting the semantics of
 		sigtimedwait(2) and sigwaitinfo(2).</entry>
 	    </row>
 
 	    <row>
 	      <entry>501102</entry>
 	      <entry>July 3, 2003</entry>
 	      <entry>5.1-CURRENT after adding the lockfunc and
 		lockfuncarg fields to
 		&man.bus.dma.tag.create.9;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501103</entry>
 	      <entry>July 31, 2003</entry>
 	      <entry>5.1-CURRENT after GCC 3.3.1-pre 20030711 snapshot
 		integration.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501104</entry>
 	      <entry>August 5, 2003</entry>
 	      <entry>5.1-CURRENT 3ware API changes to twe.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501105</entry>
 	      <entry>August 17, 2003</entry>
 	      <entry>5.1-CURRENT dynamically-linked /bin and /sbin
 		support and movement of libraries to /lib.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501106</entry>
 	      <entry>September 8, 2003</entry>
 	      <entry>5.1-CURRENT after adding kernel support for
 		Coda 6.x.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501107</entry>
 	      <entry>September 17, 2003</entry>
 	      <entry>5.1-CURRENT after 16550 UART constants moved from
 		<filename>&lt;dev/sio/sioreg.h&gt;</filename> to
 		<filename>&lt;dev/ic/ns16550.h&gt;</filename>.
 		Also when libmap functionality was unconditionally
 		supported by rtld.</entry>
 	    </row>
 
 	    <row>
 	      <entry>501108</entry>
 	      <entry>September 23, 2003</entry>
 	      <entry>5.1-CURRENT after PFIL_HOOKS API update</entry>
 	    </row>
 
 	    <row>
 	      <entry>501109</entry>
 	      <entry>September 27, 2003</entry>
 	      <entry>5.1-CURRENT after adding kiconv(3)</entry>
 	    </row>
 
 	    <row>
 	      <entry>501110</entry>
 	      <entry>September 28, 2003</entry>
 	      <entry>5.1-CURRENT after changing default operations
 		for open and close in cdevsw</entry>
 	    </row>
 
 	    <row>
 	      <entry>501111</entry>
 	      <entry>October 16, 2003</entry>
 	      <entry>5.1-CURRENT after changed layout of
 		cdevsw</entry>
 	    </row>
 
 	    <row>
 	      <entry>501112</entry>
 	      <entry>October 16, 2003</entry>
 	      <entry> 5.1-CURRENT after adding kobj multiple
 		inheritance</entry>
 	    </row>
 
 	    <row>
 	      <entry>501113</entry>
 	      <entry>October 31, 2003</entry>
 	      <entry> 5.1-CURRENT after the if_xname change in
 		struct ifnet</entry>
 	    </row>
 
 	    <row>
 	      <entry>501114</entry>
 	      <entry>November 16, 2003</entry>
 	      <entry> 5.1-CURRENT after changing /bin and /sbin to
 		be dynamically linked</entry>
 	    </row>
 
 	    <row>
 	      <entry>502000</entry>
 	      <entry>December 7, 2003</entry>
 	      <entry>5.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>502010</entry>
 	      <entry>February 23, 2004</entry>
 	      <entry>5.2.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>502100</entry>
 	      <entry>December 7, 2003</entry>
 	      <entry>5.2-CURRENT after branching for
 		RELENG_5_2</entry>
 	    </row>
 
 	    <row>
 	      <entry>502101</entry>
 	      <entry>December 19, 2003</entry>
 	      <entry>5.2-CURRENT after __cxa_atexit/__cxa_finalize
 		functions were added to libc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502102</entry>
 	      <entry>January 30, 2004</entry>
 	      <entry>5.2-CURRENT after change of default thread
 		library from libc_r to libpthread.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502103</entry>
 	      <entry>February 21, 2004</entry>
 	      <entry>5.2-CURRENT after device driver API
 		megapatch.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502104</entry>
 	      <entry>February 25, 2004</entry>
 	      <entry>5.2-CURRENT after getopt_long_only()
 		addition.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502105</entry>
 	      <entry>March 5, 2004</entry>
 	      <entry>5.2-CURRENT after NULL is made into ((void *)0)
 		for C, creating more warnings.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502106</entry>
 	      <entry>March 8, 2004</entry>
 	      <entry>5.2-CURRENT after pf is linked to the build and
 		install.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502107</entry>
 	      <entry>March 10, 2004</entry>
 	      <entry>5.2-CURRENT after time_t is changed to a
 		64-bit value on sparc64.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502108</entry>
 	      <entry>March 12, 2004</entry>
 	      <entry>5.2-CURRENT after Intel C/C++ compiler support in
 		some headers and execve(2) changes to be more strictly
 		conforming to POSIX.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502109</entry>
 	      <entry>March 22, 2004</entry>
 	      <entry>5.2-CURRENT after the introduction of the
 		bus_alloc_resource_any API</entry>
 	    </row>
 
 	    <row>
 	      <entry>502110</entry>
 	      <entry>March 27, 2004</entry>
 	      <entry>5.2-CURRENT after the addition of UTF-8
 		locales</entry>
 	    </row>
 
 	    <row>
 	      <entry>502111</entry>
 	      <entry>April 11, 2004</entry>
 	      <entry>5.2-CURRENT after the removal of the getvfsent(3)
 		API</entry>
 	    </row>
 
 	    <row>
 	      <entry>502112</entry>
 	      <entry>April 13, 2004</entry>
 	      <entry>5.2-CURRENT after the addition of the .warning
 		directive for make.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502113</entry>
 	      <entry>June 4, 2004</entry>
 	      <entry>5.2-CURRENT after ttyioctl() was made mandatory
 		for serial drivers.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502114</entry>
 	      <entry>June 13, 2004</entry>
 	      <entry>5.2-CURRENT after import of the ALTQ
 		framework.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502115</entry>
 	      <entry>June 14, 2004</entry>
 	      <entry>5.2-CURRENT after changing sema_timedwait(9) to
 		return 0 on success and a non-zero error code on
 		failure.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502116</entry>
 	      <entry>June 16, 2004</entry>
 	      <entry>5.2-CURRENT after changing kernel dev_t to be
 		pointer to struct cdev *.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502117</entry>
 	      <entry>June 17, 2004</entry>
 	      <entry>5.2-CURRENT after changing kernel udev_t to
 		dev_t.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502118</entry>
 	      <entry>June 17, 2004</entry>
 	      <entry>5.2-CURRENT after adding support for
 		CLOCK_VIRTUAL and CLOCK_PROF to clock_gettime(2) and
 		clock_getres(2).</entry>
 	    </row>
 
 	    <row>
 	      <entry>502119</entry>
 	      <entry>June 22, 2004</entry>
 	      <entry>5.2-CURRENT after changing network interface
 		cloning overhaul.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502120</entry>
 	      <entry>July 2, 2004</entry>
 	      <entry>5.2-CURRENT after the update of the package tools
 		to revision 20040629.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502121</entry>
 	      <entry>July 9, 2004</entry>
 	      <entry>5.2-CURRENT after marking Bluetooth code as
 		non-i386 specific.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502122</entry>
 	      <entry>July 11, 2004</entry>
 	      <entry>5.2-CURRENT after the introduction of the KDB
 		debugger framework, the conversion of DDB into a
 		backend and the introduction of the GDB
 		backend.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502123</entry>
 	      <entry>July 12, 2004</entry>
 	      <entry>5.2-CURRENT after change to make VFS_ROOT take a
 		struct thread argument as does vflush.  Struct
 		kinfo_proc now has a user data pointer.  The switch of
 		the default X implementation to
 		<literal>xorg</literal> was also made at this
 		time.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502124</entry>
 	      <entry>July 24, 2004</entry>
 	      <entry>5.2-CURRENT after the change to separate the way
 		ports rc.d and legacy scripts are started.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502125</entry>
 	      <entry>July 28, 2004</entry>
 	      <entry>5.2-CURRENT after the backout of the previous
 		change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502126</entry>
 	      <entry>July 31, 2004</entry>
 	      <entry>5.2-CURRENT after the removal of
 		kmem_alloc_pageable() and the import of gcc
 		3.4.2.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502127</entry>
 	      <entry>August 2, 2004</entry>
 	      <entry>5.2-CURRENT after changing the UMA kernel
 		API to allow ctors/inits to fail.</entry>
 	    </row>
 
 	    <row>
 	      <entry>502128</entry>
 	      <entry>August 8, 2004</entry>
 	      <entry>5.2-CURRENT after the change of the
 		vfs_mount signature as well as global replacement of
 		PRISON_ROOT with SUSER_ALLOWJAIL for the suser(9)
 		API.</entry>
 	    </row>
 
 	    <row>
 	      <entry>503000</entry>
 	      <entry>August 23, 2004</entry>
 	      <entry>5.3-BETA/RC before the pfil API change</entry>
 	    </row>
 
 	    <row>
 	      <entry>503001</entry>
 	      <entry>September 22, 2004</entry>
 	      <entry>5.3-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>503100</entry>
 	      <entry>October 16, 2004</entry>
 	      <entry>5.3-STABLE after branching for RELENG_5_3</entry>
 	    </row>
 
 	    <row>
 	      <entry>503101</entry>
 	      <entry>December 3, 2004</entry>
 	      <entry>5.3-STABLE after addition of glibc style
 		&man.strftime.3; padding options.</entry>
 	    </row>
 
 	    <row>
 	      <entry>503102</entry>
 	      <entry>February 13, 2005</entry>
 	      <entry>5.3-STABLE after OpenBSD's nc(1) import
 		MFC.</entry>
 	    </row>
 
 	    <row>
 	      <entry>503103</entry>
 	      <entry>February 27, 2005</entry>
 	      <entry>5.4-PRERELEASE after the MFC of the fixes in
 		<filename>&lt;src/include/stdbool.h&gt;</filename> and
 		<filename>&lt;src/sys/i386/include/_types.h&gt;</filename>
 		for using the GCC-compatibility of the Intel C/C++
 		compiler.</entry>
 	    </row>
 
 	    <row>
 	      <entry>503104</entry>
 	      <entry>February 28, 2005</entry>
 	      <entry>5.4-PRERELEASE after the MFC of the change of
 		ifi_epoch from wall clock time to uptime.</entry>
 	    </row>
 
 	    <row>
 	      <entry>503105</entry>
 	      <entry>March 2, 2005</entry>
 	      <entry>5.4-PRERELEASE after the MFC of the fix of
 		EOVERFLOW check in vswprintf(3).</entry>
 	    </row>
 
 	    <row>
 	      <entry>504000</entry>
 	      <entry>April 3, 2005</entry>
 	      <entry>5.4-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>504100</entry>
 	      <entry>April 3, 2005</entry>
 	      <entry>5.4-STABLE after branching for RELENG_5_4</entry>
 	    </row>
 
 	    <row>
 	      <entry>504101</entry>
 	      <entry>May 11, 2005</entry>
 	      <entry>5.4-STABLE after increasing the default
 		thread stacksizes</entry>
 	    </row>
 
 	    <row>
 	      <entry>504102</entry>
 	      <entry>June 24, 2005</entry>
 	      <entry>5.4-STABLE after the addition of sha256</entry>
 	    </row>
 
 	    <row>
 	      <entry>504103</entry>
 	      <entry>October 3, 2005</entry>
 	      <entry>5.4-STABLE after the MFC of if_bridge</entry>
 	    </row>
 
 	    <row>
 	      <entry>504104</entry>
 	      <entry>November 13, 2005</entry>
 	      <entry>5.4-STABLE after the MFC of bsdiff and
 		portsnap</entry>
 	    </row>
 
 	    <row>
 	      <entry>504105</entry>
 	      <entry>January 17, 2006</entry>
 	      <entry>5.4-STABLE after MFC of ldconfig_local_dirs
 		change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>505000</entry>
 	      <entry>May 12, 2006</entry>
 	      <entry>5.5-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>505100</entry>
 	      <entry>May 12, 2006</entry>
 	      <entry>5.5-STABLE after branching for RELENG_5_5</entry>
 	    </row>
 
 	    <row>
 	      <entry>600000</entry>
 	      <entry>August 18, 2004</entry>
 	      <entry>6.0-CURRENT</entry>
 	    </row>
 
 	    <row>
 	      <entry>600001</entry>
 	      <entry>August 27, 2004</entry>
 	      <entry>6.0-CURRENT after permanently enabling PFIL_HOOKS
 		in the kernel.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600002</entry>
 	      <entry>August 30, 2004</entry>
 	      <entry>6.0-CURRENT after initial addition of
 		ifi_epoch to struct if_data.  Backed out after a
 		few days.  Do not use this value.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600003</entry>
 	      <entry>September 8, 2004</entry>
 	      <entry>6.0-CURRENT after the re-addition of the
 		ifi_epoch member of struct if_data.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600004</entry>
 	      <entry>September 29, 2004</entry>
 	      <entry>6.0-CURRENT after addition of the struct inpcb
 		argument to the pfil API.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600005</entry>
 	      <entry>October 5, 2004</entry>
 	      <entry>6.0-CURRENT after addition of the "-d
 		DESTDIR" argument to newsyslog.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600006</entry>
 	      <entry>November 4, 2004</entry>
 	      <entry>6.0-CURRENT after addition of glibc style
 		&man.strftime.3; padding options.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600007</entry>
 	      <entry>December 12, 2004</entry>
 	      <entry>6.0-CURRENT after addition of 802.11 framework
 		updates.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600008</entry>
 	      <entry>January 25, 2005</entry>
 	      <entry>6.0-CURRENT after changes to VOP_*VOBJECT()
 		functions and introduction of MNTK_MPSAFE flag for
 		Giantfree filesystems.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600009</entry>
 	      <entry>February 4, 2005</entry>
 	      <entry>6.0-CURRENT after addition of the cpufreq
 		framework and drivers.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600010</entry>
 	      <entry>February 6, 2005</entry>
 	      <entry>6.0-CURRENT after importing OpenBSD's
 		nc(1).</entry>
 	    </row>
 
 	    <row>
 	      <entry>600011</entry>
 	      <entry>February 12, 2005</entry>
 	      <entry>6.0-CURRENT after removing semblance of SVID2
 		<literal>matherr()</literal> support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600012</entry>
 	      <entry>February 15, 2005</entry>
 	      <entry>6.0-CURRENT after increase of default thread
 		stacks' size.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600013</entry>
 	      <entry>February 19, 2005</entry>
 	      <entry>6.0-CURRENT after fixes in
 		<filename>&lt;src/include/stdbool.h&gt;</filename> and
 		<filename>&lt;src/sys/i386/include/_types.h&gt;</filename>
 		for using the GCC-compatibility of the Intel C/C++
 		compiler.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600014</entry>
 	      <entry>February 21, 2005</entry>
 	      <entry>6.0-CURRENT after EOVERFLOW checks in
 		vswprintf(3) fixed.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600015</entry>
 	      <entry>February 25, 2005</entry>
 	      <entry>6.0-CURRENT after changing the struct if_data
 		member, ifi_epoch, from wall clock time to
 		uptime.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600016</entry>
 	      <entry>February 26, 2005</entry>
 	      <entry>6.0-CURRENT after LC_CTYPE disk format
 		changed.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600017</entry>
 	      <entry>February 27, 2005</entry>
 	      <entry>6.0-CURRENT after NLS catalogs disk format
 		changed.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600018</entry>
 	      <entry>February 27, 2005</entry>
 	      <entry>6.0-CURRENT after LC_COLLATE disk format
 		changed.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600019</entry>
 	      <entry>February 28, 2005</entry>
 	      <entry>Installation of acpica includes into
 		/usr/include.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600020</entry>
 	      <entry>March 9, 2005</entry>
 	      <entry>Addition of MSG_NOSIGNAL flag to send(2)
 		API.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600021</entry>
 	      <entry>March 17, 2005</entry>
 	      <entry>Addition of fields to cdevsw</entry>
 	    </row>
 
 	    <row>
 	      <entry>600022</entry>
 	      <entry>March 21, 2005</entry>
 	      <entry>Removed gtar from base system.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600023</entry>
 	      <entry>April 13, 2005</entry>
 	      <entry>LOCAL_CREDS, LOCAL_CONNWAIT socket options added
 		to unix(4).</entry>
 	    </row>
 
 	    <row>
 	      <entry>600024</entry>
 	      <entry>April 19, 2005</entry>
 	      <entry>&man.hwpmc.4; and related tools added to
 		6.0-CURRENT.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600025</entry>
 	      <entry>April 26, 2005</entry>
 	      <entry>struct icmphdr added to 6.0-CURRENT.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600026</entry>
 	      <entry>May 3, 2005</entry>
 	      <entry>pf updated to 3.7.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600027</entry>
 	      <entry>May 6, 2005</entry>
 	      <entry>Kernel libalias and ng_nat introduced.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600028</entry>
 	      <entry>May 13, 2005</entry>
 	      <entry>POSIX ttyname_r(3) made available through
 		unistd.h and libc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600029</entry>
 	      <entry>May 29, 2005</entry>
 	      <entry>6.0-CURRENT after libpcap updated to v0.9.1 alpha
 		096.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600030</entry>
 	      <entry>June 5, 2005</entry>
 	      <entry>6.0-CURRENT after importing NetBSD's
 		if_bridge(4).</entry>
 	    </row>
 
 	    <row>
 	      <entry>600031</entry>
 	      <entry>June 10, 2005</entry>
 	      <entry>6.0-CURRENT after struct ifnet was broken out
 		of the driver softcs.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600032</entry>
 	      <entry>July 11, 2005</entry>
 	      <entry>6.0-CURRENT after the import of libpcap
 		v0.9.1.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600033</entry>
 	      <entry>July 25, 2005</entry>
 	      <entry>6.0-STABLE after bump of all shared library
 		versions that had not been changed since
 		RELENG_5.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600034</entry>
 	      <entry>August 13, 2005</entry>
 	      <entry>6.0-STABLE after credential argument is added to
 		dev_clone event handler.  6.0-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600100</entry>
 	      <entry>November 1, 2005</entry>
 	      <entry>6.0-STABLE after 6.0-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>600101</entry>
 	      <entry>December 21, 2005</entry>
 	      <entry>6.0-STABLE after incorporating scripts from the
 		local_startup directories into the base
 		&man.rcorder.8;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600102</entry>
 	      <entry>December 30, 2005</entry>
 	      <entry>6.0-STABLE after updating the ELF types and
 		constants.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600103</entry>
 	      <entry>January 15, 2006</entry>
 	      <entry>6.0-STABLE after MFC of pidfile(3) API.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600104</entry>
 	      <entry>January 17, 2006</entry>
 	      <entry>6.0-STABLE after MFC of ldconfig_local_dirs
 		change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>600105</entry>
 	      <entry>February 26, 2006</entry>
 	      <entry>6.0-STABLE after NLS catalog support of
 		csh(1).</entry>
 	    </row>
 
 	    <row>
 	      <entry>601000</entry>
 	      <entry>May 6, 2006</entry>
 	      <entry>6.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>601100</entry>
 	      <entry>May 6, 2006</entry>
 	      <entry>6.1-STABLE after 6.1-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>601101</entry>
 	      <entry>June 22, 2006</entry>
 	      <entry>6.1-STABLE after the import of csup.</entry>
 	    </row>
 
 	    <row>
 	      <entry>601102</entry>
 	      <entry>July 11, 2006</entry>
 	      <entry>6.1-STABLE after the iwi(4) update.</entry>
 	    </row>
 
 	    <row>
 	      <entry>601103</entry>
 	      <entry>July 17, 2006</entry>
 	      <entry>6.1-STABLE after the resolver update to
 		BIND9, and exposure of reentrant version of
 		netdb functions.</entry>
 	    </row>
 
 	    <row>
 	      <entry>601104</entry>
 	      <entry>August 8, 2006</entry>
 	      <entry>6.1-STABLE after DSO (dynamic shared
 		objects) support has been enabled in
 		OpenSSL.</entry>
 	    </row>
 
 	    <row>
 	      <entry>601105</entry>
 	      <entry>September 2, 2006</entry>
 	      <entry>6.1-STABLE after 802.11 fixups changed the
 		api for the IEEE80211_IOC_STA_INFO ioctl.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602000</entry>
 	      <entry>November 15, 2006</entry>
 	      <entry>6.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>602100</entry>
 	      <entry>September 15, 2006</entry>
 	      <entry>6.2-STABLE after 6.2-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602101</entry>
 	      <entry>December 12, 2006</entry>
 	      <entry>6.2-STABLE after the addition of Wi-Spy
 		quirk.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602102</entry>
 	      <entry>December 28, 2006</entry>
 	      <entry>6.2-STABLE after pci_find_extcap()
 		addition.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602103</entry>
 	      <entry>January 16, 2007</entry>
 	      <entry>6.2-STABLE after MFC of dlsym change to look for
 		a requested symbol both in specified dso and its
 		implicit dependencies.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602104</entry>
 	      <entry>January 28, 2007</entry>
 	      <entry>6.2-STABLE after MFC of ng_deflate(4) and
 		ng_pred1(4) netgraph nodes and new compression and
 		encryption modes for ng_ppp(4) node.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602105</entry>
 	      <entry>February 20, 2007</entry>
 	      <entry>6.2-STABLE after MFC of BSD licensed version of
 		&man.gzip.1; ported from NetBSD.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602106</entry>
 	      <entry>March 31, 2007</entry>
 	      <entry>6.2-STABLE after MFC of PCI MSI and MSI-X
 		support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602107</entry>
 	      <entry>April 6, 2007</entry>
 	      <entry>6.2-STABLE after MFC of ncurses 5.6 and wide
 		character support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602108</entry>
 	      <entry>April 11, 2007</entry>
 	      <entry>6.2-STABLE after MFC of CAM 'SG' peripheral
 		device, which implements a subset of Linux SCSI SG
 		passthrough device API.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602109</entry>
 	      <entry>April 17, 2007</entry>
 	      <entry>6.2-STABLE after MFC of readline 5.2 patchset
 		002.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602110</entry>
 	      <entry>May 2, 2007</entry>
 	      <entry>6.2-STABLE after MFC of pmap_invalidate_cache(),
 		pmap_change_attr(), pmap_mapbios(),
 		pmap_mapdev_attr(), and pmap_unmapbios() for amd64 and
 		i386.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602111</entry>
 	      <entry>June 11, 2007</entry>
 	      <entry>6.2-STABLE after MFC of BOP_BDFLUSH and caused
 		breakage of the filesystem modules KBI.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602112</entry>
 	      <entry>September 21, 2007</entry>
 	      <entry>6.2-STABLE after libutil(3) MFC's.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602113</entry>
 	      <entry>October 25, 2007</entry>
 	      <entry>6.2-STABLE after MFC of wide and single byte
 		ctype separation.  Newly compiled binary that
 		references to ctype.h may require a new symbol,
 		__mb_sb_limit, which is not available on older
 		systems.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602114</entry>
 	      <entry>October 30, 2007</entry>
 	      <entry>6.2-STABLE after ctype ABI forward compatibility
 		restored.</entry>
 	    </row>
 
 	    <row>
 	      <entry>602115</entry>
 	      <entry>November 21, 2007</entry>
 	      <entry>6.2-STABLE after back out of wide and single byte
 		ctype separation.</entry>
 	    </row>
 
 	    <row>
 	      <entry>603000</entry>
 	      <entry>November 25, 2007</entry>
 	      <entry>6.3-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>603100</entry>
 	      <entry>November 25, 2007</entry>
 	      <entry>6.3-STABLE after 6.3-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>603101</entry>
 	      <entry>December 7, 2007</entry>
 	      <entry>6.3-STABLE after fixing
 		multibyte type support in bit macro.</entry>
 	    </row>
 
 	    <row>
 	      <entry>603102</entry>
 	      <entry>April 24, 2008</entry>
 	      <entry>6.3-STABLE after adding l_sysid to struct
 		flock.</entry>
 	    </row>
 
 	    <row>
 	      <entry>603103</entry>
 	      <entry>May 27, 2008</entry>
 	      <entry>6.3-STABLE after MFC of the
 		<function>memrchr</function> function.</entry>
 	    </row>
 
 	    <row>
 	      <entry>603104</entry>
 	      <entry>June 15, 2008</entry>
 	      <entry>6.3-STABLE after MFC of support for
 		<literal>:u</literal> variable modifier in
 		make(1).</entry>
 	    </row>
 
 	    <row>
 	      <entry>604000</entry>
 	      <entry>October 4, 2008</entry>
 	      <entry>6.4-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>604100</entry>
 	      <entry>October 4, 2008</entry>
 	      <entry>6.4-STABLE after 6.4-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700000</entry>
 	      <entry>July 11, 2005</entry>
 	      <entry>7.0-CURRENT.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700001</entry>
 	      <entry>July 23, 2005</entry>
 	      <entry>7.0-CURRENT after bump of all shared library
 		versions that had not been changed since
 		RELENG_5.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700002</entry>
 	      <entry>August 13, 2005</entry>
 	      <entry>7.0-CURRENT after credential argument is added to
 		dev_clone event handler.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700003</entry>
 	      <entry>August 25, 2005</entry>
 	      <entry>7.0-CURRENT after memmem(3) is added to
 		libc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700004</entry>
 	      <entry>October 30, 2005</entry>
 	      <entry>7.0-CURRENT after solisten(9) kernel arguments
 		are modified to accept a backlog parameter.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700005</entry>
 	      <entry>November 11, 2005</entry>
 	      <entry>7.0-CURRENT after IFP2ENADDR() was changed to
 		return a pointer to IF_LLADDR().</entry>
 	    </row>
 
 	    <row>
 	      <entry>700006</entry>
 	      <entry>November 11, 2005</entry>
 	      <entry>7.0-CURRENT after addition of
 		<literal>if_addr</literal> member to <literal>struct
 		  ifnet</literal> and IFP2ENADDR() removal.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700007</entry>
 	      <entry>December 2, 2005</entry>
 	      <entry>7.0-CURRENT after incorporating scripts from the
 		local_startup directories into the base
 		&man.rcorder.8;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700008</entry>
 	      <entry>December 5, 2005</entry>
 	      <entry>7.0-CURRENT after removal of MNT_NODEV mount
 		option.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700009</entry>
 	      <entry>December 19, 2005</entry>
 	      <entry>7.0-CURRENT after ELF-64 type changes and symbol
 		versioning.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700010</entry>
 	      <entry>December 20, 2005</entry>
 	      <entry>7.0-CURRENT after addition of hostb and vgapci
 		drivers, addition of pci_find_extcap(), and changing
 		the AGP drivers to no longer map the aperture.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700011</entry>
 	      <entry>December 31, 2005</entry>
 	      <entry>7.0-CURRENT after tv_sec was made time_t on
 		all platforms but Alpha.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700012</entry>
 	      <entry>January 8, 2006</entry>
 	      <entry>7.0-CURRENT after ldconfig_local_dirs
 		change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700013</entry>
 	      <entry>January 12, 2006</entry>
 	      <entry>7.0-CURRENT after changes to
 		<filename>/etc/rc.d/abi</filename> to support
 		<filename>/compat/linux/etc/ld.so.cache</filename>
 		being a symlink in a readonly filesystem.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700014</entry>
 	      <entry>January 26, 2006</entry>
 	      <entry>7.0-CURRENT after pts import.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700015</entry>
 	      <entry>March 26, 2006</entry>
 	      <entry>7.0-CURRENT after the introduction of version 2
 		of &man.hwpmc.4;'s ABI.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700016</entry>
 	      <entry>April 22, 2006</entry>
 	      <entry>7.0-CURRENT after addition of &man.fcloseall.3;
 		to libc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700017</entry>
 	      <entry>May 13, 2006</entry>
 	      <entry>7.0-CURRENT after removal of ip6fw.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700018</entry>
 	      <entry>July 15, 2006</entry>
 	      <entry>7.0-CURRENT after import of snd_emu10kx.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700019</entry>
 	      <entry>July 29, 2006</entry>
 	      <entry>7.0-CURRENT after import of OpenSSL
 		0.9.8b.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700020</entry>
 	      <entry>September 3, 2006</entry>
 	      <entry>7.0-CURRENT after addition of bus_dma_get_tag
 		function</entry>
 	    </row>
 
 	    <row>
 	      <entry>700021</entry>
 	      <entry>September 4, 2006</entry>
 	      <entry>7.0-CURRENT after libpcap 0.9.4 and tcpdump 3.9.4
 		import.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700022</entry>
 	      <entry>September 9, 2006</entry>
 	      <entry>7.0-CURRENT after dlsym change to look for a
 		requested symbol both in specified dso and its
 		implicit dependencies.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700023</entry>
 	      <entry>September 23, 2006</entry>
 	      <entry>7.0-CURRENT after adding new sound IOCTLs for the
 		OSSv4 mixer API.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700024</entry>
 	      <entry>September 28, 2006</entry>
 	      <entry>7.0-CURRENT after import of OpenSSL
 		0.9.8d.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700025</entry>
 	      <entry>November 11, 2006</entry>
 	      <entry>7.0-CURRENT after the addition of libelf.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700026</entry>
 	      <entry>November 26, 2006</entry>
 	      <entry>7.0-CURRENT after major changes on sound
 		sysctls.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700027</entry>
 	      <entry>November 30, 2006</entry>
 	      <entry>7.0-CURRENT after the addition of Wi-Spy
 		quirk.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700028</entry>
 	      <entry>December 15, 2006</entry>
 	      <entry>7.0-CURRENT after the addition of sctp calls to
 		libc</entry>
 	    </row>
 
 	    <row>
 	      <entry>700029</entry>
 	      <entry>January 26, 2007</entry>
 	      <entry>7.0-CURRENT after the GNU &man.gzip.1;
 		implementation was replaced with a BSD licensed
 		version ported from NetBSD.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700030</entry>
 	      <entry>February 7, 2007</entry>
 	      <entry>7.0-CURRENT after the removal of IPIP tunnel
 		encapsulation (VIFF_TUNNEL) from the IPv4 multicast
 		forwarding code.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700031</entry>
 	      <entry>February 23, 2007</entry>
 	      <entry>7.0-CURRENT after the modification of
 		bus_setup_intr() (newbus).</entry>
 	    </row>
 
 	    <row>
 	      <entry>700032</entry>
 	      <entry>March 2, 2007</entry>
 	      <entry>7.0-CURRENT after the inclusion of ipw(4) and
 		iwi(4) firmware.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700033</entry>
 	      <entry>March 9, 2007</entry>
 	      <entry>7.0-CURRENT after the inclusion of ncurses wide
 		character support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700034</entry>
 	      <entry>March 19, 2007</entry>
 	      <entry>7.0-CURRENT after changes to how insmntque(),
 		getnewvnode(), and vfs_hash_insert() work.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700035</entry>
 	      <entry>March 26, 2007</entry>
 	      <entry>7.0-CURRENT after addition of a notify mechanism
 		for CPU frequency changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700036</entry>
 	      <entry>April 6, 2007</entry>
 	      <entry>7.0-CURRENT after import of the ZFS
 		filesystem.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700037</entry>
 	      <entry>April 8, 2007</entry>
 	      <entry>7.0-CURRENT after addition of CAM 'SG' peripheral
 		device, which implements a subset of Linux SCSI SG
 		passthrough device API.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700038</entry>
 	      <entry>April 30, 2007</entry>
 	      <entry>7.0-CURRENT after changing &man.getenv.3;,
 		&man.putenv.3;, &man.setenv.3; and &man.unsetenv.3; to
 		be POSIX conformant.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700039</entry>
 	      <entry>May 1, 2007</entry>
 	      <entry>7.0-CURRENT after the changes in 700038 were
 		backed out.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700040</entry>
 	      <entry>May 10, 2007</entry>
 	      <entry>7.0-CURRENT after the addition of &man.flopen.3;
 		to libutil.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700041</entry>
 	      <entry>May 13, 2007</entry>
 	      <entry>7.0-CURRENT after enabling symbol versioning, and
 		changing the default thread library to libthr.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700042</entry>
 	      <entry>May 19, 2007</entry>
 	      <entry>7.0-CURRENT after the import of gcc
 		4.2.0.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700043</entry>
 	      <entry>May 21, 2007</entry>
 	      <entry>7.0-CURRENT after bump of all shared library
 		versions that had not been changed since
 		RELENG_6.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700044</entry>
 	      <entry>June 7, 2007</entry>
 	      <entry>7.0-CURRENT after changing the argument for
 		vn_open()/VOP_OPEN() from file descriptor index to the
 		struct file *.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700045</entry>
 	      <entry>June 10, 2007</entry>
 	      <entry>7.0-CURRENT after changing &man.pam.nologin.8; to
 		provide an account management function instead of an
 		authentication function to the PAM framework.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700046</entry>
 	      <entry>June 11, 2007</entry>
 	      <entry>7.0-CURRENT after updated 802.11 wireless
 		support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700047</entry>
 	      <entry>June 11, 2007</entry>
 	      <entry>7.0-CURRENT after adding TCP LRO interface
 		capabilities.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700048</entry>
 	      <entry>June 12, 2007</entry>
 	      <entry>7.0-CURRENT after
 		RFC 3678 API support added to the IPv4 stack.
 		Legacy RFC 1724 behavior of the IP_MULTICAST_IF
 		ioctl has now been removed; 0.0.0.0/8 may no longer
 		be used to specify an interface index.
 		struct ipmreqn should be used instead.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700049</entry>
 	      <entry>July 3, 2007</entry>
 	      <entry>7.0-CURRENT after importing pf from OpenBSD
 		4.1</entry>
 	    </row>
 
 	    <row>
 	      <entry>(not changed)</entry>
 	      <entry></entry>
 	      <entry>7.0-CURRENT after adding IPv6 support for
 		FAST_IPSEC, deleting KAME IPSEC, and renaming
 		FAST_IPSEC to IPSEC.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700050</entry>
 	      <entry>July 4, 2007</entry>
 	      <entry>7.0-CURRENT after converting setenv/putenv/etc.
 		calls from traditional BSD to POSIX.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700051</entry>
 	      <entry>July 4, 2007</entry>
 	      <entry>7.0-CURRENT after adding new mmap/lseek/etc
 		syscalls.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700052</entry>
 	      <entry>July 6, 2007</entry>
 	      <entry>7.0-CURRENT after moving I4B headers to
 		include/i4b.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700053</entry>
 	      <entry>September 30, 2007</entry>
 	      <entry>7.0-CURRENT after the addition of support for
 		PCI domains</entry>
 	    </row>
 
 	    <row>
 	      <entry>700054</entry>
 	      <entry>October 25, 2007</entry>
 	      <entry>7.0-CURRENT after MFC of wide and single byte
 		ctype separation.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700055</entry>
 	      <entry>October 28, 2007</entry>
 	      <entry>7.0-RELEASE, and 7.0-CURRENT after ABI backwards
 		compatibility to the FreeBSD 4/5/6 versions of the
 		PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs was
 		MFCed, which required the ABI of the PCIOCGETCONF
 		IOCTL to be broken again</entry>
 	    </row>
 
 	    <row>
 	      <entry>700100</entry>
 	      <entry>December 22, 2007</entry>
 	      <entry>7.0-STABLE after 7.0-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>700101</entry>
 	      <entry>February 8, 2008</entry>
 	      <entry>7.0-STABLE after the MFC of m_collapse().</entry>
 	    </row>
 
 	    <row>
 	      <entry>700102</entry>
 	      <entry>March 30, 2008</entry>
 	      <entry>7.0-STABLE after the MFC of
 		kdb_enter_why().</entry>
 	    </row>
 
 	    <row>
 	      <entry>700103</entry>
 	      <entry>April 10, 2008</entry>
 	      <entry>7.0-STABLE after adding l_sysid to struct
 		flock.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700104</entry>
 	      <entry>April 11, 2008</entry>
 	      <entry>7.0-STABLE after the MFC of procstat(1).</entry>
 	    </row>
 
 	    <row>
 	      <entry>700105</entry>
 	      <entry>April 11, 2008</entry>
 	      <entry>7.0-STABLE after the MFC of umtx
 		features.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700106</entry>
 	      <entry>April 15, 2008</entry>
 	      <entry>7.0-STABLE after the MFC of &man.write.2; support
 		to &man.psm.4;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700107</entry>
 	      <entry>April 20, 2008</entry>
 	      <entry>7.0-STABLE after the MFC of F_DUP2FD command
 		to &man.fcntl.2;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700108</entry>
 	      <entry>May 5, 2008</entry>
 	      <entry>7.0-STABLE after some &man.lockmgr.9; changes,
 		which makes it necessary to include
 		<filename>sys/lock.h</filename> in order to use
 		&man.lockmgr.9;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700109</entry>
 	      <entry>May 27, 2008</entry>
 	      <entry>7.0-STABLE after MFC of the
 		<function>memrchr</function> function.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700110</entry>
 	      <entry>August 5, 2008</entry>
 	      <entry>7.0-STABLE after MFC of kernel NFS lockd
 		client.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700111</entry>
 	      <entry>August 20, 2008</entry>
 	      <entry>7.0-STABLE after addition of physically
 		contiguous jumbo frame support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>700112</entry>
 	      <entry>August 27, 2008</entry>
 	      <entry>7.0-STABLE after MFC of kernel DTrace
 		support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>701000</entry>
 	      <entry>November 25, 2008</entry>
 	      <entry>7.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>701100</entry>
 	      <entry>November 25, 2008</entry>
 	      <entry>7.1-STABLE after 7.1-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>701101</entry>
 	      <entry>January 10, 2009</entry>
 	      <entry>7.1-STABLE after <function>strndup</function>
 		merge.</entry>
 	    </row>
 
 	    <row>
 	      <entry>701102</entry>
 	      <entry>January 17, 2009</entry>
 	      <entry>7.1-STABLE after cpuctl(4) support
 		added.</entry>
 	    </row>
 
 	    <row>
 	      <entry>701103</entry>
 	      <entry>February 7, 2009</entry>
 	      <entry>7.1-STABLE after the merge of
 		multi-/no-IPv4/v6 jails.</entry>
 	    </row>
 
 	    <row>
 	      <entry>701104</entry>
 	      <entry>February 14, 2009</entry>
 	      <entry>7.1-STABLE after the store of the suspension
 		owner in the struct mount, and introduction of
 		vfs_susp_clean method into the struct vfsops.</entry>
 	    </row>
 
 	    <row>
 	      <entry>701105</entry>
 	      <entry>March 12, 2009</entry>
 	      <entry>7.1-STABLE after the incompatible change
 		to the kern.ipc.shmsegs sysctl to allow to allocate
 		larger SysV shared memory segments on 64bit
 		architectures.</entry>
 	    </row>
 
 	    <row>
 	      <entry>701106</entry>
 	      <entry>March 14, 2009</entry>
 	      <entry>7.1-STABLE after the merge of a fix for
 		POSIX semaphore wait operations.</entry>
 	    </row>
 
 	    <row>
 	      <entry>702000</entry>
 	      <entry>April 15, 2009</entry>
 	      <entry>7.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>702100</entry>
 	      <entry>April 15, 2009</entry>
 	      <entry>7.2-STABLE after 7.2-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>702101</entry>
 	      <entry>May 15, 2009</entry>
 	      <entry>7.2-STABLE after ichsmb(4) was changed to
 		use left-adjusted slave addressing to match other
 		SMBus controller drivers.</entry>
 	    </row>
 
 	    <row>
 	      <entry>702102</entry>
 	      <entry>May 28, 2009</entry>
 	      <entry>7.2-STABLE after MFC of the
 		<function>fdopendir</function> function.</entry>
 	    </row>
 
 	    <row>
 	      <entry>702103</entry>
 	      <entry>June 06, 2009</entry>
 	      <entry>7.2-STABLE after MFC of PmcTools.</entry>
 	    </row>
 
 	    <row>
 	      <entry>702104</entry>
 	      <entry>July 14, 2009</entry>
 	      <entry>7.2-STABLE after MFC of the
 		<function>closefrom</function> system call.</entry>
 	    </row>
 
 	    <row>
 	      <entry>702105</entry>
 	      <entry>July 31, 2009</entry>
 	      <entry>7.2-STABLE after MFC of the SYSVIPC ABI
 		change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>702106</entry>
 	      <entry>September 14, 2009</entry>
 	      <entry>7.2-STABLE after MFC of the x86 PAT
 		enhancements and addition of d_mmap_single() and
 		the scatter/gather list VM object type.</entry>
 	    </row>
 
 	    <row>
 	      <entry>703000</entry>
 	      <entry>February 9, 2010</entry>
 	      <entry>7.3-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>703100</entry>
 	      <entry>February 9, 2010</entry>
 	      <entry>7.3-STABLE after 7.3-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>704000</entry>
 	      <entry>December 22, 2010</entry>
 	      <entry>7.4-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>704100</entry>
 	      <entry>December 22, 2010</entry>
 	      <entry>7.4-STABLE after 7.4-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800000</entry>
 	      <entry>October 11, 2007</entry>
 	      <entry>8.0-CURRENT.  Separating wide and single byte
 		ctype.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800001</entry>
 	      <entry>October 16, 2007</entry>
 	      <entry>8.0-CURRENT after libpcap 0.9.8 and tcpdump 3.9.8
 		import.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800002</entry>
 	      <entry>October 21, 2007</entry>
 	      <entry>8.0-CURRENT after renaming kthread_create()
 		and friends to kproc_create() etc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800003</entry>
 	      <entry>October 24, 2007</entry>
 	      <entry>8.0-CURRENT after ABI backwards compatibility
 		to the FreeBSD 4/5/6 versions of the PCIOCGETCONF,
 		PCIOCREAD and PCIOCWRITE IOCTLs was added, which
 		required the ABI of the PCIOCGETCONF IOCTL to be
 		broken again</entry>
 	    </row>
 
 	    <row>
 	      <entry>800004</entry>
 	      <entry>November 12, 2007</entry>
 	      <entry>8.0-CURRENT after agp(4) driver moved from
 		src/sys/pci to src/sys/dev/agp</entry>
 	    </row>
 
 	    <row>
 	      <entry>800005</entry>
 	      <entry>December 4, 2007</entry>
-	      <entry>8.0-CURRENT after
-		<ulink
-		  url="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/kern_mbuf.c#rev1.35">changes
-		  to the jumbo frame allocator</ulink>.</entry>
+	      <entry>8.0-CURRENT after changes to the jumbo frame
+		allocator (rev <svnref>174247</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>800006</entry>
 	      <entry>December 7, 2007</entry>
 	      <entry>8.0-CURRENT after the addition of callgraph
 		capture functionality to &man.hwpmc.4;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800007</entry>
 	      <entry>December 25, 2007</entry>
 	      <entry>8.0-CURRENT after kdb_enter() gains a "why"
 		argument.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800008</entry>
 	      <entry>December 28, 2007</entry>
 	      <entry>8.0-CURRENT after LK_EXCLUPGRADE option
 		removal.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800009</entry>
 	      <entry>January 9, 2008</entry>
 	      <entry>8.0-CURRENT after introduction of
 		&man.lockmgr.disown.9;</entry>
 	    </row>
 
 	    <row>
 	      <entry>800010</entry>
 	      <entry>January 10, 2008</entry>
 	      <entry>8.0-CURRENT after the &man.vn.lock.9; prototype
 		change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800011</entry>
 	      <entry>January 13, 2008</entry>
 	      <entry>8.0-CURRENT after the &man.VOP.LOCK.9; and
 		&man.VOP.UNLOCK.9; prototype changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800012</entry>
 	      <entry>January 19, 2008</entry>
 	      <entry>8.0-CURRENT after introduction of
 		&man.lockmgr.recursed.9;, &man.BUF.RECURSED.9; and
 		&man.BUF.ISLOCKED.9; and the removal of
 		<function>BUF_REFCNT()</function>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800013</entry>
 	      <entry>January 23, 2008</entry>
 	      <entry>8.0-CURRENT after introduction of the
 		<quote>ASCII</quote> encoding.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800014</entry>
 	      <entry>January 24, 2008</entry>
 	      <entry>8.0-CURRENT after changing the prototype of
 		&man.lockmgr.9; and removal of
 		<function>lockcount()</function> and
 		<function>LOCKMGR_ASSERT()</function>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800015</entry>
 	      <entry>January 26, 2008</entry>
 	      <entry>8.0-CURRENT after extending the types
 		of the &man.fts.3; structures.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800016</entry>
 	      <entry>February 1, 2008</entry>
 	      <entry>8.0-CURRENT after adding an argument to
 		MEXTADD(9)</entry>
 	    </row>
 
 	    <row>
 	      <entry>800017</entry>
 	      <entry>February 6, 2008</entry>
 	      <entry>8.0-CURRENT after the introduction of
 		LK_NODUP and LK_NOWITNESS options in the
 		&man.lockmgr.9; space.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800018</entry>
 	      <entry>February 8, 2008</entry>
 	      <entry>8.0-CURRENT after the addition of
 		m_collapse.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800019</entry>
 	      <entry>February 9, 2008</entry>
 	      <entry>8.0-CURRENT after the addition of current
 		working directory, root directory, and jail
 		directory support to the kern.proc.filedesc
 		sysctl.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800020</entry>
 	      <entry>February 13, 2008</entry>
 	      <entry>8.0-CURRENT after introduction of
 		&man.lockmgr.assert.9; and
 		<function>BUF_ASSERT</function> functions.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800021</entry>
 	      <entry>February 15, 2008</entry>
 	      <entry>8.0-CURRENT after introduction of
 		&man.lockmgr.args.9; and LK_INTERNAL flag
 		removal.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800022</entry>
 	      <entry>(backed out)</entry>
 	      <entry>8.0-CURRENT after changing the default system ar
 		to BSD &man.ar.1;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800023</entry>
 	      <entry>February 25, 2008</entry>
 	      <entry>8.0-CURRENT after changing the prototypes of
 		&man.lockstatus.9; and &man.VOP.ISLOCKED.9;, more
 		specifically retiring the
 		<literal>struct thread</literal> argument.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800024</entry>
 	      <entry>March 1, 2008</entry>
 	      <entry>8.0-CURRENT after axing out the
 		<function>lockwaiters</function> and
 		<function>BUF_LOCKWAITERS</function> functions,
 		changing the return value of
 		<function>brelvp</function> from void to int and
 		introducing new flags for &man.lockinit.9;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800025</entry>
 	      <entry>March 8, 2008</entry>
 	      <entry>8.0-CURRENT after adding F_DUP2FD command
 		to &man.fcntl.2;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800026</entry>
 	      <entry>March 12, 2008</entry>
 	      <entry>8.0-CURRENT after changing the priority parameter
 		to cv_broadcastpri such that 0 means no
 		priority.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800027</entry>
 	      <entry>March 24, 2008</entry>
 	      <entry>8.0-CURRENT after changing the bpf monitoring ABI
 		when zerocopy bpf buffers were added.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800028</entry>
 	      <entry>March 26, 2008</entry>
 	      <entry>8.0-CURRENT after adding l_sysid to struct
 		flock.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800029</entry>
 	      <entry>March 28, 2008</entry>
 	      <entry>8.0-CURRENT after reintegration of the
 		<function>BUF_LOCKWAITERS</function> function and the
 		addition of &man.lockmgr.waiters.9;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800030</entry>
 	      <entry>April 1, 2008</entry>
 	      <entry>8.0-CURRENT after the introduction of the
 		&man.rw.try.rlock.9; and &man.rw.try.wlock.9;
 		functions.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800031</entry>
 	      <entry>April 6, 2008</entry>
 	      <entry>8.0-CURRENT after the introduction of the
 		<function>lockmgr_rw</function> and
 		<function>lockmgr_args_rw</function>
 		functions.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800032</entry>
 	      <entry>April 8, 2008</entry>
 	      <entry>8.0-CURRENT after the implementation of the
 		openat and related syscalls, introduction of the
 		O_EXEC flag for the &man.open.2;, and providing the
 		corresponding linux compatibility syscalls.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800033</entry>
 	      <entry>April 8, 2008</entry>
 	      <entry>8.0-CURRENT after added &man.write.2; support for
 		&man.psm.4; in native operation level.  Now arbitrary
 		commands can be written to
 		<devicename>/dev/psm%d</devicename> and status can be
 		read back from it.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800034</entry>
 	      <entry>April 10, 2008</entry>
 	      <entry>8.0-CURRENT after introduction of the
 		<function>memrchr</function> function.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800035</entry>
 	      <entry>April 16, 2008</entry>
 	      <entry>8.0-CURRENT after introduction of the
 		<function>fdopendir</function> function.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800036</entry>
 	      <entry>April 20, 2008</entry>
 	      <entry>8.0-CURRENT after switchover of 802.11 wireless
 		to multi-bss support (aka vaps).</entry>
 	    </row>
 
 	    <row>
 	      <entry>800037</entry>
 	      <entry>May 9, 2008</entry>
 	      <entry>8.0-CURRENT after addition of multi routing
 		table support (aka setfib(1), setfib(2)).</entry>
 	    </row>
 
 	    <row>
 	      <entry>800038</entry>
 	      <entry>May 26, 2008</entry>
 	      <entry>8.0-CURRENT after removal of netatm and
 		ISDN4BSD.  Also, the addition of the
 		Compact C Type (CTF) tools.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800039</entry>
 	      <entry>June 14, 2008</entry>
 	      <entry>8.0-CURRENT after removal of sgtty.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800040</entry>
 	      <entry>June 26, 2008</entry>
 	      <entry>8.0-CURRENT with kernel NFS lockd client.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800041</entry>
 	      <entry>July 22, 2008</entry>
 	      <entry>8.0-CURRENT after addition of arc4random_buf(3)
 		and arc4random_uniform(3).</entry>
 	    </row>
 
 	    <row>
 	      <entry>800042</entry>
 	      <entry>August 8, 2008</entry>
 	      <entry>8.0-CURRENT after addition of cpuctl(4).</entry>
 	    </row>
 
 	    <row>
 	      <entry>800043</entry>
 	      <entry>August 13, 2008</entry>
 	      <entry>8.0-CURRENT after changing bpf(4) to use a
 		single device node, instead of device cloning.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800044</entry>
 	      <entry>August 17, 2008</entry>
 	      <entry>8.0-CURRENT after the commit of the first step of
 		the vimage project renaming global variables to be
 		virtualized with a V_ prefix with macros to map them
 		back to their global names.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800045</entry>
 	      <entry>August 20, 2008</entry>
 	      <entry>8.0-CURRENT after the integration of the
 		MPSAFE TTY layer, including changes to various
 		drivers and utilities that interact with it.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800046</entry>
 	      <entry>September 8, 2008</entry>
 	      <entry>8.0-CURRENT after the separation of the GDT
 		per CPU on amd64 architecture.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800047</entry>
 	      <entry>September 10, 2008</entry>
 	      <entry>8.0-CURRENT after removal of VSVTX, VSGID
 		and VSUID.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800048</entry>
 	      <entry>September 16, 2008</entry>
 	      <entry>8.0-CURRENT after converting the kernel NFS mount
 		code to accept individual mount options in the
 		nmount() iovec, not just one big
 		struct nfs_args.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800049</entry>
 	      <entry>September 17, 2008</entry>
 	      <entry>8.0-CURRENT after the removal of &man.suser.9;
 		and &man.suser.cred.9;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800050</entry>
 	      <entry>October 20, 2008</entry>
 	      <entry>8.0-CURRENT after buffer cache API
 		change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800051</entry>
 	      <entry>October 23, 2008</entry>
 	      <entry>8.0-CURRENT after the removal of the
 		&man.MALLOC.9; and &man.FREE.9; macros.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800052</entry>
 	      <entry>October 28, 2008</entry>
 	      <entry>8.0-CURRENT after the introduction of accmode_t
 		and renaming of VOP_ACCESS 'a_mode' argument
 		to 'a_accmode'.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800053</entry>
 	      <entry>November 2, 2008</entry>
 	      <entry>8.0-CURRENT after the prototype change of
 		&man.vfs.busy.9; and the introduction of its
 		MBF_NOWAIT and MBF_MNTLSTLOCK flags.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800054</entry>
 	      <entry>November 22, 2008</entry>
 	      <entry>8.0-CURRENT after the addition of buf_ring,
 		memory barriers and ifnet functions to facilitate
 		multiple hardware transmit queues for cards that
 		support them, and a lockless ring-buffer
 		implementation to enable drivers to more efficiently
 		manage queuing of packets.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800055</entry>
 	      <entry>November 27, 2008</entry>
 	      <entry>8.0-CURRENT after the addition of Intel&trade;
 		Core, Core2, and Atom support to
 		&man.hwpmc.4;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800056</entry>
 	      <entry>November 29, 2008</entry>
 	      <entry>8.0-CURRENT after the introduction of
 		multi-/no-IPv4/v6 jails.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800057</entry>
 	      <entry>December 1, 2008</entry>
 	      <entry>8.0-CURRENT after the switch to the
 		ath hal source code.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800058</entry>
 	      <entry>December 12, 2008</entry>
 	      <entry>8.0-CURRENT after the introduction of
 		the VOP_VPTOCNP operation.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800059</entry>
 	      <entry>December 15, 2008</entry>
 	      <entry>8.0-CURRENT incorporates the
 		new arp-v2 rewrite.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800060</entry>
 	      <entry>December 19, 2008</entry>
 	      <entry>8.0-CURRENT after the addition of makefs.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800061</entry>
 	      <entry>January 15, 2009</entry>
 	      <entry>8.0-CURRENT after TCP Appropriate Byte
 		Counting.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800062</entry>
 	      <entry>January 28, 2009</entry>
 	      <entry>8.0-CURRENT after removal of minor(),
 		minor2unit(), unit2minor(), etc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800063</entry>
 	      <entry>February 18, 2009</entry>
 	      <entry>8.0-CURRENT after GENERIC config change to use
 		the USB2 stack, but also the addition of
 		fdevname(3).</entry>
 	    </row>
 
 	    <row>
 	      <entry>800064</entry>
 	      <entry>February 23, 2009</entry>
 	      <entry>8.0-CURRENT after the USB2 stack is moved to and
 		replaces dev/usb.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800065</entry>
 	      <entry>February 26, 2009</entry>
 	      <entry>8.0-CURRENT after the renaming of all functions
 		in libmp(3).</entry>
 	    </row>
 
 	    <row>
 	      <entry>800066</entry>
 	      <entry>February 27, 2009</entry>
 	      <entry>8.0-CURRENT after changing USB devfs handling and
 		layout.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800067</entry>
 	      <entry>February 28, 2009</entry>
 	      <entry>8.0-CURRENT after adding getdelim(), getline(),
 		stpncpy(), strnlen(), wcsnlen(), wcscasecmp(), and
 		wcsncasecmp().</entry>
 	    </row>
 
 	    <row>
 	      <entry>800068</entry>
 	      <entry>March 2, 2009</entry>
 	      <entry>8.0-CURRENT after renaming the ushub devclass to
 		uhub.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800069</entry>
 	      <entry>March 9, 2009</entry>
 	      <entry>8.0-CURRENT after libusb20.so.1 was renamed to
 		libusb.so.1.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800070</entry>
 	      <entry>March 9, 2009</entry>
 	      <entry>8.0-CURRENT after merging IGMPv3 and
 		Source-Specific Multicast (SSM) to the IPv4
 		stack.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800071</entry>
 	      <entry>March 14, 2009</entry>
 	      <entry>8.0-CURRENT after gcc was patched to use C99
 		inline semantics in c99 and gnu99 mode.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800072</entry>
 	      <entry>March 15, 2009</entry>
 	      <entry>8.0-CURRENT after the IFF_NEEDSGIANT flag has
 		been removed; non-MPSAFE network device drivers are no
 		longer supported.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800073</entry>
 	      <entry>March 18, 2009</entry>
 	      <entry>8.0-CURRENT after the dynamic string token
 		substitution has been implemented for rpath and needed
 		paths.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800074</entry>
 	      <entry>March 24, 2009</entry>
 	      <entry>8.0-CURRENT after tcpdump 4.0.0 and
 		libpcap 1.0.0 import.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800075</entry>
 	      <entry>April 6, 2009</entry>
 	      <entry>8.0-CURRENT after layout of structs vnet_net,
 		vnet_inet and vnet_ipfw has been changed.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800076</entry>
 	      <entry>April 9, 2009</entry>
 	      <entry>8.0-CURRENT after adding delay profiles in
 		dummynet.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800077</entry>
 	      <entry>April 14, 2009</entry>
 	      <entry>8.0-CURRENT after removing VOP_LEASE() and
 		vop_vector.vop_lease.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800078</entry>
 	      <entry>April 15, 2009</entry>
 	      <entry>8.0-CURRENT after struct rt_weight fields have
 		been added to struct rt_metrics and struct
 		rt_metrics_lite, changing the layout of struct
 		rt_metrics_lite.  A bump to RTM_VERSION was made, but
 		backed out.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800079</entry>
 	      <entry>April 15, 2009</entry>
 	      <entry>8.0-CURRENT after struct llentry pointers are
 		added to struct route and struct route_in6.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800080</entry>
 	      <entry>April 15, 2009</entry>
 	      <entry>8.0-CURRENT after layout of struct inpcb has been
 		changed.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800081</entry>
 	      <entry>April 19, 2009</entry>
 	      <entry>8.0-CURRENT after the layout of struct
 		malloc_type has been changed.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800082</entry>
 	      <entry>April 21, 2009</entry>
 	      <entry>8.0-CURRENT after the layout of struct ifnet has
 		changed, and with if_ref() and if_rele() ifnet
 		refcounting.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800083</entry>
 	      <entry>April 22, 2009</entry>
 	      <entry>8.0-CURRENT after the implementation of a
 		low-level Bluetooth HCI API.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800084</entry>
 	      <entry>April 29, 2009</entry>
 	      <entry>8.0-CURRENT after IPv6 SSM and MLDv2
 		changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800085</entry>
 	      <entry>April 30, 2009</entry>
 	      <entry>8.0-CURRENT after enabling support for
 		VIMAGE kernel builds with one active image.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800086</entry>
 	      <entry>May 8, 2009</entry>
 	      <entry>8.0-CURRENT after adding support for input lines
 		of arbitrarily length in patch(1).</entry>
 	    </row>
 
 	    <row>
 	      <entry>800087</entry>
 	      <entry>May 11, 2009</entry>
 	      <entry>8.0-CURRENT after some VFS KPI changes.  The
 		thread argument has been removed from the FSD parts of
 		the VFS.  <function>VFS_*</function> functions do not
 		need the context any more because it always refers to
 		<varname>curthread</varname>.  In some special cases,
 		the old behavior is retained.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800088</entry>
 	      <entry>May 20, 2009</entry>
 	      <entry>8.0-CURRENT after net80211 monitor mode
 		changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800089</entry>
 	      <entry>May 23, 2009</entry>
 	      <entry>8.0-CURRENT after adding UDP control block
 		support.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800090</entry>
 	      <entry>May 23, 2009</entry>
 	      <entry>8.0-CURRENT after virtualizing interface
 		cloning.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800091</entry>
 	      <entry>May 27, 2009</entry>
 	      <entry>8.0-CURRENT after adding hierarchical jails
 		and removing global securelevel.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800092</entry>
 	      <entry>May 29, 2009</entry>
 	      <entry>8.0-CURRENT after changing
 		<function>sx_init_flags()</function> KPI.  The
 		<constant>SX_ADAPTIVESPIN</constant> is retired and a
 		new <constant>SX_NOADAPTIVE</constant> flag is
 		introduced in order to handle the reversed
 		logic.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800093</entry>
 	      <entry>May 29, 2009</entry>
 	      <entry>8.0-CURRENT after adding mnt_xflag to
 		struct mount.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800094</entry>
 	      <entry>May 30, 2009</entry>
 	      <entry>8.0-CURRENT after adding
 		&man.VOP.ACCESSX.9;.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800095</entry>
 	      <entry>May 30, 2009</entry>
 	      <entry>8.0-CURRENT after changing the polling KPI.
 		The polling handlers now return the number of packets
 		processed.  A new
 		<constant>IFCAP_POLLING_NOCOUNT</constant> is also
 		introduced to specify that the return value is
 		not significant and the counting should be
 		skipped.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800096</entry>
 	      <entry>June 1, 2009</entry>
 	      <entry>8.0-CURRENT after updating to the new netisr
 		implementation and after changing the way we
 		store and access FIBs.</entry>
 	      <!--
 		Had been 96 and 97 but were folded because we are
 		running out of numbers.
 	      -->
 	    </row>
 
 	    <row>
 	      <entry>800097</entry>
 	      <entry>June 8, 2009</entry>
 	      <entry>8.0-CURRENT after the introduction of vnet
 		destructor hooks and infrastructure.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800097</entry>
 	      <entry>June 11, 2009</entry>
 	      <entry>8.0-CURRENT after the introduction of netgraph
 		outbound to inbound path call detection and queuing,
 		which also changed the layout of struct
 		thread.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800098</entry>
 	      <entry>June 14, 2009</entry>
 	      <entry>8.0-CURRENT after OpenSSL 0.9.8k import.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800099</entry>
 	      <entry>June 22, 2009</entry>
 	      <entry>8.0-CURRENT after NGROUPS update and moving
 		route virtualization into its own VImage
 		module.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800100</entry>
 	      <entry>June 24, 2009</entry>
 	      <entry>8.0-CURRENT after SYSVIPC ABI change.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800101</entry>
 	      <entry>June 29, 2009</entry>
 	      <entry>8.0-CURRENT after the removal of the
 		/dev/net/* per-interface character
 		devices.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800102</entry>
 	      <entry>July 12, 2009</entry>
 	      <entry>8.0-CURRENT after padding was added to
 		struct sackhint, struct tcpcb, and struct
 		tcpstat.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800103</entry>
 	      <entry>July 13, 2009</entry>
 	      <entry>8.0-CURRENT after replacing struct tcpopt
 		with struct toeopt in the TOE driver interface
 		to the TCP syncache.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800104</entry>
 	      <entry>July 14, 2009</entry>
 	      <entry>8.0-CURRENT after the addition of the
 		linker-set based per-vnet allocator.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800105</entry>
 	      <entry>July 19, 2009</entry>
 	      <entry>8.0-CURRENT after version bump for all
 		shared libraries that do not have symbol versioning
 		turned on.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800106</entry>
 	      <entry>July 24, 2009</entry>
 	      <entry>8.0-CURRENT after introduction of OBJT_SG
 		VM object type.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800107</entry>
 	      <entry>August 2, 2009</entry>
 	      <entry>8.0-CURRENT after making the newbus subsystem
 		Giant free by adding the newbus sxlock and
 		8.0-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800108</entry>
 	      <entry>November 21, 2009</entry>
 	      <entry>8.0-STABLE after implementing EVFILT_USER kevent
 		filter.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800500</entry>
 	      <entry>January 7, 2010</entry>
 	      <entry>8.0-STABLE after
 		<literal>__FreeBSD_version</literal> bump to make
 		<command>pkg_add -r</command> use
 		packages-8-stable.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800501</entry>
 	      <entry>January 24, 2010</entry>
 	      <entry>8.0-STABLE after change of the
 		<function>scandir(3)</function> and
 		<function>alphasort(3)</function> prototypes to
 		conform to SUSv4.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800502</entry>
 	      <entry>January 31, 2010</entry>
 	      <entry>8.0-STABLE after addition of
 		<function>sigpause(3)</function>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800503</entry>
 	      <entry>February 25, 2010</entry>
 	      <entry>8.0-STABLE after addition of SIOCGIFDESCR
 		and SIOCSIFDESCR ioctls to network interfaces.  These
 		ioctl can be used to manipulate interface description,
 		as inspired by OpenBSD.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800504</entry>
 	      <entry>March 1, 2010</entry>
 	      <entry>8.0-STABLE after MFC of importing x86emu, a
 		software emulator for real mode x86 CPU from
 		OpenBSD.</entry>
 	    </row>
 
 	    <row>
 	      <entry>800505</entry>
 	      <entry>May 18, 2010</entry>
 	      <entry>8.0-STABLE after MFC of adding liblzma, xz,
 		xzdec, and lzmainfo.</entry>
 	    </row>
 
 	    <row>
 	      <entry>801000</entry>
 	      <entry>June 14, 2010</entry>
 	      <entry>8.1-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>801500</entry>
 	      <entry>June 14, 2010</entry>
 	      <entry>8.1-STABLE after 8.1-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>801501</entry>
 	      <entry>November 3, 2010</entry>
 	      <entry>8.1-STABLE after KBI change in struct sysentvec,
 		and implementation of PL_FLAG_SCE/SCX/EXEC/SI and
 		pl_siginfo for ptrace(PT_LWPINFO) .</entry>
 	    </row>
 
 	    <row>
 	      <entry>802000</entry>
 	      <entry>December 22, 2010</entry>
 	      <entry>8.2-RELEASE</entry>
 	    </row>
 
 	    <row>
 	      <entry>802500</entry>
 	      <entry>December 22, 2010</entry>
 	      <entry>8.2-STABLE after 8.2-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802501</entry>
 	      <entry>February 28, 2011</entry>
 	      <entry>8.2-STABLE after merging DTrace changes,
 		including support for userland tracing.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802502</entry>
 	      <entry>March 6, 2011</entry>
 	      <entry>8.2-STABLE after merging log2 and log2f
 		into libm.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802503</entry>
 	      <entry>May 1, 2011</entry>
 	      <entry>8.2-STABLE after upgrade of the gcc to the last
 		GPLv2 version from the FSF gcc-4_2-branch.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802504</entry>
 	      <entry>May 28, 2011</entry>
 	      <entry>8.2-STABLE after introduction of the KPI and
 		supporting infrastructure for modular congestion
 		control.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802505</entry>
 	      <entry>May 28, 2011</entry>
 	      <entry>8.2-STABLE after introduction of Hhook and Khelp
 		KPIs.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802506</entry>
 	      <entry>May 28, 2011</entry>
 	      <entry>8.2-STABLE after addition of OSD to struct
 		tcpcb.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802507</entry>
 	      <entry>June 6, 2011</entry>
 	      <entry>8.2-STABLE after ZFS v28 import.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802508</entry>
 	      <entry>June 8, 2011</entry>
 	      <entry>8.2-STABLE after removal of the schedtail event
 		handler and addition of the sv_schedtail method to
 		struct sysvec.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802509</entry>
 	      <entry>July 14, 2011</entry>
 	      <entry>8.2-STABLE after merging the SSSE3 support
 		into binutils.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802510</entry>
 	      <entry>July 19, 2011</entry>
 	      <entry>8.2-STABLE after addition of
 		RFTSIGZMB flag for
 		<function>rfork(2)</function>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802511</entry>
 	      <entry>September 9, 2011</entry>
 	      <entry>8.2-STABLE after addition of automatic detection
 		of USB mass storage devices which do not support the
 		no synchronize cache SCSI command.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802512</entry>
 	      <entry>September 10, 2011</entry>
 	      <entry>8.2-STABLE after merging of
 		re-factoring of auto-quirk.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802513</entry>
 	      <entry>October 25, 2011</entry>
 	      <entry>8.2-STABLE after merging of the MAP_PREFAULT_READ
 		flag to <function>mmap(2)</function>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802514</entry>
 	      <entry>November 16, 2011</entry>
 	      <entry>8.2-STABLE after merging of
 		addition of posix_fallocate(2) syscall.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802515</entry>
 	      <entry>January 6, 2012</entry>
 	      <entry>8.2-STABLE after merging of addition of the
 		posix_fadvise(2) system call.</entry>
 	    </row>
 
 	    <row>
 	      <entry>802516</entry>
 	      <entry>January 16, 2012</entry>
 	      <entry>8.2-STABLE after merging gperf 3.0.3</entry>
 	    </row>
 
 	    <row>
 	      <entry>802517</entry>
 	      <entry>February 15, 2012</entry>
 	      <entry>8.2-STABLE after introduction of the new
 		extensible sysctl(3) interface NET_RT_IFLISTL
 		to query address lists (rev
-		<svnref>231769</svnref>.</entry>
+		<svnref>231769</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>803000</entry>
 	      <entry>March 3, 2012</entry>
 	      <entry>8.3-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>803500</entry>
 	      <entry>March 3, 2012</entry>
 	      <entry>8.3-STABLE after branching releng/8.3
 		(RELENG_8_3).</entry>
 	    </row>
 
 	    <row>
 	      <entry>804000</entry>
 	      <entry>March 28, 2013</entry>
 	      <entry>8.4-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>804500</entry>
 	      <entry>March 28, 2013</entry>
 	      <entry>8.4-STABLE after 8.4-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900000</entry>
 	      <entry>August 22, 2009</entry>
 	      <entry>9.0-CURRENT.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900001</entry>
 	      <entry>September 8, 2009</entry>
 	      <entry>9.0-CURRENT after importing x86emu, a software
 		emulator for real mode x86 CPU from OpenBSD.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900002</entry>
 	      <entry>September 23, 2009</entry>
 	      <entry>9.0-CURRENT after implementing the EVFILT_USER
 		kevent filter functionality.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900003</entry>
 	      <entry>December 2, 2009</entry>
 	      <entry>9.0-CURRENT after addition of
 		<function>sigpause(3)</function> and PIE
 		support in csu.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900004</entry>
 	      <entry>December 6, 2009</entry>
 	      <entry>9.0-CURRENT after addition of libulog and its
 		libutempter compatibility interface.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900005</entry>
 	      <entry>December 12, 2009</entry>
 	      <entry>9.0-CURRENT after addition of
 		<function>sleepq_sleepcnt()</function>, which can be
 		used to query the number of waiters on a specific
 		waiting queue.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900006</entry>
 	      <entry>January 4, 2010</entry>
 	      <entry>9.0-CURRENT after change of the
 		<function>scandir(3)</function> and
 		<function>alphasort(3)</function> prototypes to
 		conform to SUSv4.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900007</entry>
 	      <entry>January 13, 2010</entry>
 	      <entry>9.0-CURRENT after the removal of utmp(5) and
 		the addition of utmpx (see
 		<function>getutxent(3)</function>) for improved
 		logging of user logins and system events.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900008</entry>
 	      <entry>January 20, 2010</entry>
 	      <entry>9.0-CURRENT after the import of BSDL bc/dc and
 		the deprecation of GNU bc/dc.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900009</entry>
 	      <entry>January 26, 2010</entry>
 	      <entry>9.0-CURRENT after the addition of SIOCGIFDESCR
 		and SIOCSIFDESCR ioctls to network interfaces.  These
 		ioctl can be used to manipulate interface description,
 		as inspired by OpenBSD.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900010</entry>
 	      <entry>March 22, 2010</entry>
 	      <entry>9.0-CURRENT after the import of zlib
 		1.2.4.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900011</entry>
 	      <entry>April 24, 2010</entry>
 	      <entry>9.0-CURRENT after adding soft-updates
 		journalling.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900012</entry>
 	      <entry>May 10, 2010</entry>
 	      <entry>9.0-CURRENT after adding liblzma, xz, xzdec,
 		and lzmainfo.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900013</entry>
 	      <entry>May 24, 2010</entry>
 	      <entry>9.0-CURRENT after bringing in USB fixes for
 		linux(4).</entry>
 	    </row>
 
 	    <row>
 	      <entry>900014</entry>
 	      <entry>June 10, 2010</entry>
 	      <entry>9.0-CURRENT after adding Clang.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900015</entry>
 	      <entry>July 22, 2010</entry>
 	      <entry>9.0-CURRENT after the import of BSD grep.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900016</entry>
 	      <entry>July 28, 2010</entry>
 	      <entry>9.0-CURRENT after adding mti_zone to
 		struct malloc_type_internal.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900017</entry>
 	      <entry>August 23, 2010</entry>
 	      <entry>9.0-CURRENT after changing back default grep to
 		GNU grep and adding WITH_BSD_GREP knob.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900018</entry>
 	      <entry>August 24, 2010</entry>
 	      <entry>9.0-CURRENT after the
 		<function>pthread_kill(3)</function> -generated signal
 		is identified as SI_LWP in si_code.  Previously,
 		si_code was SI_USER.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900019</entry>
 	      <entry>August 28, 2010</entry>
 	      <entry>9.0-CURRENT after addition of the
 		MAP_PREFAULT_READ flag to
 		<function>mmap(2)</function>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900020</entry>
 	      <entry>September 9, 2010</entry>
 	      <entry>9.0-CURRENT after adding drain functionality
 		to sbufs, which also changed the layout of
 		struct sbuf.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900021</entry>
 	      <entry>September 13, 2010</entry>
 	      <entry>9.0-CURRENT after DTrace has grown support
 		for userland tracing.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900022</entry>
 	      <entry>October 2, 2010</entry>
 	      <entry>9.0-CURRENT after addition of the BSDL man
 		utilities and retirement of GNU/GPL man
 		utilities.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900023</entry>
 	      <entry>October 11, 2010</entry>
 	      <entry>9.0-CURRENT after updating xz to git 20101010
 		snapshot.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900024</entry>
 	      <entry>November 11, 2010</entry>
 	      <entry>9.0-CURRENT after libgcc.a was replaced
 		by libcompiler_rt.a.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900025</entry>
 	      <entry>November 12, 2010</entry>
 	      <entry>9.0-CURRENT after the introduction of the
 		modularised congestion control.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900026</entry>
 	      <entry>November 30, 2010</entry>
 	      <entry>9.0-CURRENT after the introduction of Serial
 		Management Protocol (SMP) passthrough and the
 		XPT_SMP_IO and XPT_GDEV_ADVINFO CAM CCBs.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900027</entry>
 	      <entry>December 5, 2010</entry>
 	      <entry>9.0-CURRENT after the addition of log2 to
 		libm.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900028</entry>
 	      <entry>December 21, 2010</entry>
 	      <entry>9.0-CURRENT after the addition of the Hhook
 		(Helper Hook), Khelp (Kernel Helpers) and Object
 		Specific Data (OSD) KPIs.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900029</entry>
 	      <entry>December 28, 2010</entry>
 	      <entry>9.0-CURRENT after the modification of the TCP
 		stack to allow Khelp modules to interact with it via
 		helper hook points and store per-connection data in
 		the TCP control block.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900030</entry>
 	      <entry>January 12, 2011</entry>
 	      <entry>9.0-CURRENT after the update of libdialog to
 		version 20100428.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900031</entry>
 	      <entry>February 7, 2011</entry>
 	      <entry>9.0-CURRENT after the addition of
 		<function>pthread_getthreadid_np(3)</function>.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900032</entry>
 	      <entry>February 8, 2011</entry>
 	      <entry>9.0-CURRENT after the removal of the uio_yield
 		prototype and symbol.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900033</entry>
 	      <entry>February 18, 2011</entry>
 	      <entry>9.0-CURRENT after the update of binutils to
 		version 2.17.50.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900034</entry>
 	      <entry>March 8, 2011</entry>
 	      <entry>9.0-CURRENT after the struct sysvec
 		(sv_schedtail) changes.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900035</entry>
 	      <entry>March 29, 2011</entry>
 	      <entry>9.0-CURRENT after the update of base gcc and
 		libstdc++ to the last GPLv2 licensed revision.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900036</entry>
 	      <entry>April 18, 2011</entry>
 	      <entry>9.0-CURRENT after the removal of libobjc and
 		Objective-C support from the base system.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900037</entry>
 	      <entry>May 13, 2011</entry>
 	      <entry>9.0-CURRENT after importing the libprocstat(3)
 		library and fuser(1) utility to the base
 		system.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900038</entry>
 	      <entry>May 22, 2011</entry>
 	      <entry>9.0-CURRENT after adding a lock flag argument to
 		VFS_FHTOVP(9).</entry>
 	    </row>
 
 	    <row>
 	      <entry>900039</entry>
 	      <entry>June 28, 2011</entry>
 	      <entry>9.0-CURRENT after importing pf from OpenBSD
 		4.5.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900040</entry>
 	      <entry>July 19, 2011</entry>
 	      <entry>Increase default MAXCPU for FreeBSD to 64 on
 		amd64 and ia64 and to 128 for XLP (mips).</entry>
 	    </row>
 
 	    <row>
 	      <entry>900041</entry>
 	      <entry>August 13, 2011</entry>
 	      <entry>9.0-CURRENT after the implementation of Capsicum
 		capabilities; fget(9) gains a rights argument.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900042</entry>
 	      <entry>August 28, 2011</entry>
 	      <entry>Bump shared libraries' version numbers for
 		libraries whose ABI has changed in preparation for
 		9.0.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900043</entry>
 	      <entry>September 2, 2011</entry>
 	      <entry>Add automatic detection of USB mass storage
 		devices which do not support the no synchronize cache
 		SCSI command.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900044</entry>
 	      <entry>September 10, 2011</entry>
 	      <entry>Re-factor auto-quirk.  9.0-RELEASE.</entry>
 	    </row>
 
 <!-- Note: at one point 900045 was documented as follows, even though
  it was never committed:
 	    <row>
 	      <entry>900045</entry>
 	      <entry>Oct 13, 2011</entry>
 	      <entry>All non-compatibility system call entry points
 		have been prefixed with sys_.</entry>
 	    </row>
 -->
 
 	    <row>
 	      <entry>900045</entry>
 	      <entry>January 2, 2012</entry>
 	      <entry>9-CURRENT after MFC of true/false from
 		1000002.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900500</entry>
 	      <entry>January 2, 2012</entry>
 	      <entry>9.0-STABLE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900501</entry>
 	      <entry>January 6, 2012</entry>
 	      <entry>9.0-STABLE after merging of addition of the
 		posix_fadvise(2) system call.</entry>
 	    </row>
 
 	    <row>
 	      <entry>900502</entry>
 	      <entry>January 16, 2012</entry>
 	      <entry>9.0-STABLE after merging gperf 3.0.3</entry>
 	    </row>
 
 	    <row>
 	      <entry>900503</entry>
 	      <entry>February 15, 2012</entry>
 	      <entry>9.0-STABLE after introduction of the new
 		extensible sysctl(3) interface NET_RT_IFLISTL
 		to query address lists (rev
 		<svnref>231768</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>900504</entry>
 	      <entry>March 3, 2012</entry>
 	      <entry>9.0-STABLE after changes related to mounting
 		of filesystem inside a jail (rev
 		<svnref>232728</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>900505</entry>
 	      <entry>March 13, 2012</entry>
 	      <entry>9.0-STABLE after introduction of new tcp(4)
 		socket options: TCP_KEEPINIT, TCP_KEEPIDLE,
 		TCP_KEEPINTVL, and TCP_KEEPCNT (rev
 		<svnref>232945</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>900506</entry>
 	      <entry>May 22, 2012</entry>
 	      <entry>9.0-STABLE after introduction of the
 		<function>quick_exit</function> function and
 		related changes required for C++11 (rev
 		<svnref>235786</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>901000</entry>
 	      <entry>August 5, 2012</entry>
 	      <entry>9.1-RELEASE.</entry>
 	    </row>
 
 	    <row>
 	      <entry>901500</entry>
 	      <entry>August 6, 2012</entry>
 	      <entry>9.1-STABLE after branching releng/9.1
 		(RELENG_9_1).</entry>
 	    </row>
 
 	    <row>
 	      <entry>901501</entry>
 	      <entry>November 11, 2012</entry>
 	      <entry>9.1-STABLE after LIST_PREV() added to queue.h
 	      (rev <svnref>242893</svnref>) and KBI change in USB
 	      serial devices (rev <svnref>240659</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>901502</entry>
 	      <entry>November 28, 2012</entry>
 	      <entry>9.1-STABLE after USB serial jitter buffer
 		requires rebuild of USB serial device modules.</entry>
 	    </row>
 
 	    <row>
 	      <entry>901503</entry>
 	      <entry>February 21, 2013</entry>
 	      <entry>9.1-STABLE after USB moved to the driver
 		structure requiring a rebuild of all USB modules.
 		Also indicates the presence of nmtree.</entry>
 	    </row>
 
 	    <row>
 	      <entry>901504</entry>
 	      <entry>March 15, 2013</entry>
 	      <entry>9.1-STABLE after install gained -l, -M, -N and
 		related flags and cat gained the -l option.</entry>
 	    </row>
 
 	    <row>
 	      <entry>901505</entry>
 	      <entry>June 13, 2013</entry>
 	      <entry>9.1-STABLE after fixes in ctfmerge boostrapping
 		(rev <svnref>249243</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000000</entry>
 	      <entry>September 26, 2011</entry>
 	      <entry>10.0-CURRENT.</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000001</entry>
 	      <entry>November 4, 2011</entry>
 	      <entry>10-CURRENT after addition of the posix_fadvise(2)
 		system call.</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000002</entry>
 	      <entry>December 12, 2011</entry>
 	      <entry>10-CURRENT after defining boolean true/false in
 		sys/types.h, sizeof(bool) may have changed (rev
 		<svnref>228444</svnref>).  10-CURRENT after xlocale.h
 		was introduced (rev
 		<svnref>227753</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000003</entry>
 	      <entry>December 16, 2011</entry>
 	      <entry>10-CURRENT after major changes to carp(4),
 		changing size of struct&nbsp;in_aliasreq,
 		struct&nbsp;in6_aliasreq (rev <svnref>228571</svnref>)
 		and straitening arguments check of SIOCAIFADDR (rev
 		<svnref>228574</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000004</entry>
 	      <entry>January 1, 2012</entry>
 	      <entry>10-CURRENT after the removal of skpc(9) and the
 		addition of memcchr(9) (rev
 		<svnref>229200</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000005</entry>
 	      <entry>January 16, 2012</entry>
 	      <entry>10-CURRENT after the removal of support for
 		SIOCSIFADDR, SIOCSIFNETMASK, SIOCSIFBRDADDR,
 		SIOCSIFDSTADDR ioctls (rev
 		<svnref>230207</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000006</entry>
 	      <entry>January 26, 2012</entry>
 	      <entry>10-CURRENT after introduction of read capacity
 		data asynchronous notification in the cam(4) layer
 		(rev <svnref>230590</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000007</entry>
 	      <entry>February 5, 2012</entry>
 	      <entry>10-CURRENT after introduction of new tcp(4)
 		socket options: TCP_KEEPINIT, TCP_KEEPIDLE,
 		TCP_KEEPINTVL, and TCP_KEEPCNT (rev
 		<svnref>231025</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000008</entry>
 	      <entry>February 11, 2012</entry>
 	      <entry>10-CURRENT after introduction of the new
 		extensible sysctl(3) interface NET_RT_IFLISTL
 		to query address lists (rev
 		<svnref>231505</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000009</entry>
 	      <entry>February 25, 2012</entry>
 	      <entry>10-CURRENT after import of libarchive 3.0.3
 		(rev <svnref>232153</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000010</entry>
 	      <entry>March 31, 2012</entry>
 	      <entry>10-CURRENT after xlocale cleanup (rev
 		<svnref>233757</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000011</entry>
 	      <entry>April 16, 2012</entry>
 	      <entry>10-CURRENT import of LLVM/Clang 3.1 trunk r154661
 		(rev <svnref>234353</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000012</entry>
 	      <entry>May 2, 2012</entry>
 	      <entry>10-CURRENT jemalloc import
 		(rev <svnref>234924</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000013</entry>
 	      <entry>May 22, 2012</entry>
 	      <entry>10-CURRENT after byacc import
 		(rev <svnref>235788</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000014</entry>
 	      <entry>June 27, 2012</entry>
 	      <entry>10-CURRENT after BSD sort becoming the default
 		sort (rev <svnref>237629</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000015</entry>
 	      <entry>July 12, 2012</entry>
 	      <entry>10-CURRENT after import of OpenSSL 1.0.1c
 		(rev <svnref>238405</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>(not changed)</entry>
 	      <entry>July 13, 2012</entry>
 	      <entry>10-CURRENT after the fix for LLVM/Clang 3.1
 		regression (rev <svnref>238429</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000016</entry>
 	      <entry>August 8, 2012</entry>
 	      <entry>10-CURRENT after KBI change in &man.ucom.4;
 		(rev <svnref>239179</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000017</entry>
 	      <entry>August 8, 2012</entry>
 	      <entry>10-CURRENT after adding streams feature to the
 		USB stack (rev <svnref>239214</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000018</entry>
 	      <entry>September 8, 2012</entry>
 	      <entry>10-CURRENT after major rewrite of &man.pf.4;
 		(rev <svnref>240233</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000019</entry>
 	      <entry>October 6, 2012</entry>
 	      <entry>10-CURRENT after &man.pfil.9; KBI/KPI changed
 		to supply packets in net byte order to AF_INET
 		filter hooks (rev <svnref>241245</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000020</entry>
 	      <entry>October 16, 2012</entry>
 	      <entry>10-CURRENT after the network interface cloning
 		KPI changed and struct if_clone becoming opaque (rev
 		<svnref>241610</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000021</entry>
 	      <entry>October 22, 2012</entry>
 	      <entry>10-CURRENT after removal of support for
 		non-MPSAFE filesystems and addition of support for
 		FUSEFS (rev
 		<svnref>241519</svnref>,
 		<svnref>241897</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000022</entry>
 	      <entry>October 22, 2012</entry>
 	      <entry>10-CURRENT after the entire IPv4 stack switched
 		to network byte order for IP packet header storage
 		(rev <svnref>241913</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000023</entry>
 	      <entry>November 5, 2012</entry>
 	      <entry>10-CURRENT after jitter buffer in the common USB
 		serial driver code, to temporarily store characters
 		if the TTY buffer is full.  Add flow stop and start
 		signals when this happens (rev
 		<svnref>242619</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000024</entry>
 	      <entry>November 5, 2012</entry>
 	      <entry>10-CURRENT after clang was made the default
 		compiler on i386 and amd64
 		(rev <svnref>242624</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000025</entry>
 	      <entry>November 17, 2012</entry>
 	      <entry>10-CURRENT after the sin6_scope_id member
 		variable in struct sockaddr_in6 was changed to being
 		filled by the kernel before passing the structure to
 		the userland via sysctl or routing socket.  This means
 		the KAME-specific embedded scope id in
 		sin6_addr.s6_addr[2] is always cleared in userland
 		application (rev <svnref>243443</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000026</entry>
 	      <entry>January 11, 2013</entry>
 	      <entry>10-CURRENT after install gained the -N flag (rev
 		<svnref>245313</svnref>).  May also be used to
 		indicate the presence of nmtree.</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000027</entry>
 	      <entry>January 29, 2013</entry>
 	      <entry>10-CURRENT after cat gained the -l flag (rev
 		<svnref>246083</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000028</entry>
 	      <entry>February 13, 2013</entry>
 	      <entry>10-CURRENT after USB moved to the driver structure
 		requiring a rebuild of all USB modules (rev
 		<svnref>246759</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000029</entry>
 	      <entry>March 4, 2013</entry>
 	      <entry>10-CURRENT after the introduction of tickless
 		callout facility which also changed the layout of
 		struct callout (rev <svnref>247777</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000030</entry>
 	      <entry>March 12, 2013</entry>
 	      <entry>10-CURRENT after KPI breakage introduced in the
 		VM subsystem to support read/write locking (rev
 		<svnref>248084</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000031</entry>
 	      <entry>April 26, 2013</entry>
 	      <entry>10-CURRENT after the dst parameter of the
 		ifnet <function>if_output</function> method was
 		changed to take const qualifier (rev
 		<svnref>249925</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000032</entry>
 	      <entry>May 1, 2013</entry>
 	      <entry>10-CURRENT after the introduction of the
 		<function>accept4</function> (rev
 		<svnref>250154</svnref>) and
 		<function>pipe2</function> (rev
 		<svnref>250159</svnref>) system calls.</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000033</entry>
 	      <entry>May 21, 2013</entry>
 	      <entry>10-CURRENT after flex 2.5.37 import (rev
 		<svnref>250881</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000034</entry>
 	      <entry>June 3, 2013</entry>
 	      <entry>10-CURRENT after the addition of the following
 		functions to libm: <function>cacos</function>,
 		<function>cacosf</function>,
 		<function>cacosh</function>,
 		<function>cacoshf</function>,
 		<function>casin</function>,
 		<function>casinf</function>,
 		<function>casinh</function>,
 		<function>casinhf</function>,
 		<function>catan</function>,
 		<function>catanf</function>,
 		<function>catanh</function>,
 		<function>catanhf</function>,
 		<function>logl</function>,
 		<function>log2l</function>,
 		<function>log10l</function>,
 		<function>log1pl</function>,
 		<function>expm1l</function> (rev
 		<svnref>251294</svnref>).</entry>
 	    </row>
 
 	    <row>
 	      <entry>1000035</entry>
 	      <entry>June 8, 2013</entry>
 	      <entry>10-CURRENT after the introduction of the
 		<function>aio_mlock</function> system call (rev
 		<svnref>251526</svnref>).</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <note>
 	<para>Note that 2.2-STABLE sometimes identifies itself as
 	  <quote>2.2.5-STABLE</quote> after the 2.2.5-RELEASE.  The
 	  pattern used to be year followed by the month, but we
 	  decided to change it to a more straightforward major/minor
 	  system starting from 2.2.  This is because the parallel
 	  development on several branches made it infeasible to
 	  classify the releases simply by their real release dates.
 	  If you are making a port now, you do not have to worry about
 	  old -CURRENTs; they are listed here just for your
 	  reference.</para>
       </note>
     </sect1>
 
     <sect1 id="dads-after-port-mk">
       <title>Writing Something After
 	<filename>bsd.port.mk</filename></title>
 
       <para>Do not write anything after the <literal>.include
 	  &lt;bsd.port.mk&gt;</literal> line.  It usually can be
 	avoided by including <filename>bsd.port.pre.mk</filename>
 	somewhere in the middle of your <filename>Makefile</filename>
 	and <filename>bsd.port.post.mk</filename> at the end.</para>
 
       <note>
 	<para>Include either the
 	  <filename>bsd.port.pre.mk</filename>/<filename>bsd.port.post.mk</filename>
 	  pair or <filename>bsd.port.mk</filename> only; do not mix
 	  these two usages.</para>
       </note>
 
       <para><filename>bsd.port.pre.mk</filename> only defines a few
 	variables, which can be used in tests in the
 	<filename>Makefile</filename>,
 	<filename>bsd.port.post.mk</filename> defines the rest.</para>
 
       <para>Here are some important variables defined in
 	<filename>bsd.port.pre.mk</filename> (this is not the complete
 	list, please read <filename>bsd.port.mk</filename> for the
 	complete list).</para>
 
       <informaltable frame="none" pgwide="0">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Variable</entry>
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><makevar>ARCH</makevar></entry>
 	      <entry>The architecture as returned by <command>uname
 		  -m</command> (e.g., <literal>i386</literal>)</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>OPSYS</makevar></entry>
 	      <entry>The operating system type, as returned by
 		<command>uname -s</command> (e.g.,
 		<literal>FreeBSD</literal>)</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>OSREL</makevar></entry>
 	      <entry>The release version of the operating system
 		(e.g., <literal>2.1.5</literal> or
 		<literal>2.2.7</literal>)</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>OSVERSION</makevar></entry>
 	      <entry>The numeric version of the operating system; the
 		same as <link
 		  linkend="freebsd-versions"><literal>__FreeBSD_version</literal></link>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>LOCALBASE</makevar></entry>
 	      <entry>The base of the <quote>local</quote> tree (e.g.,
 		<literal>/usr/local</literal>)</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PREFIX</makevar></entry>
 	      <entry>Where the port installs itself (see <link
 		  linkend="porting-prefix">more on
 		  <makevar>PREFIX</makevar></link>).</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <note>
 	<para>If you have to define the variables
 	  <makevar>USE_IMAKE</makevar> or
 	  <makevar>MASTERDIR</makevar>, do so before including
 	  <filename>bsd.port.pre.mk</filename>.</para>
       </note>
 
       <para>Here are some examples of things you can write after
 	<filename>bsd.port.pre.mk</filename>:</para>
 
       <programlisting># no need to compile lang/perl5 if perl5 is already in system
 .if ${OSVERSION} &gt; 300003
 BROKEN=	perl is in system
 .endif</programlisting>
 
       <para>You did remember to use tab instead of spaces after
 	<literal>BROKEN=</literal> and
 	<!-- smiley -->:-).</para>
     </sect1>
 
     <sect1 id="dads-sh-exec">
       <title>Use the <function>exec</function> Statement in Wrapper
 	Scripts</title>
 
       <para>If the port installs a shell script whose purpose is to
 	launch another program, and if launching that program is the
 	last action performed by the script, make sure to launch the
 	program using the <function>exec</function> statement, for
 	instance:</para>
 
       <programlisting>#!/bin/sh
 exec %%LOCALBASE%%/bin/java -jar %%DATADIR%%/foo.jar "$@"</programlisting>
 
       <para>The <function>exec</function> statement replaces the shell
 	process with the specified program.  If
 	<function>exec</function> is omitted, the shell process
 	remains in memory while the program is executing, and
 	needlessly consumes system resources.</para>
     </sect1>
 
     <sect1 id="dads-rational">
       <title>Do Things Rationally</title>
 
       <para>The <filename>Makefile</filename> should do things simply
 	and reasonably.  If you can make it a couple of lines shorter
 	or more readable, then do so.  Examples include using a make
 	<literal>.if</literal> construct instead of a shell
 	<literal>if</literal> construct, not redefining
 	<maketarget>do-extract</maketarget> if you can redefine
 	<makevar>EXTRACT*</makevar> instead, and using
 	<makevar>GNU_CONFIGURE</makevar> instead of
 	<literal>CONFIGURE_ARGS
 	  += --prefix=&dollar;{PREFIX}</literal>.</para>
 
       <para>If you find yourself having to write a lot of new code to
 	try to do something, please go back and review
 	<filename>bsd.port.mk</filename> to see if it contains an
 	existing implementation of what you are trying to do.  While
 	hard to read, there are a great many seemingly-hard problems
 	for which <filename>bsd.port.mk</filename> already provides a
 	shorthand solution.</para>
     </sect1>
 
     <sect1 id="dads-cc">
       <title>Respect Both <makevar>CC</makevar> and
 	<makevar>CXX</makevar></title>
 
       <para>The port must respect both <makevar>CC</makevar> and
 	<makevar>CXX</makevar> variables.  What we mean by this is
 	that the port must not set the values of these variables
 	absolutely, overriding existing values; instead, it may
 	append whatever values it needs to the existing values.  This
 	is so that build options that affect all ports can be set
 	globally.</para>
 
       <para>If the port does not respect these variables,
 	please add <literal>NO_PACKAGE=ignores either cc or
 	  cxx</literal> to the <filename>Makefile</filename>.</para>
 
       <para>An example of a <filename>Makefile</filename> respecting
 	both <makevar>CC</makevar> and <makevar>CXX</makevar>
 	variables follows.  Note the <makevar>?=</makevar>:</para>
 
       <programlisting>CC?= gcc</programlisting>
 
       <programlisting>CXX?= g++</programlisting>
 
       <para>Here is an example which respects neither
 	<makevar>CC</makevar> nor <makevar>CXX</makevar>
 	variables:</para>
 
       <programlisting>CC= gcc</programlisting>
 
       <programlisting>CXX= g++</programlisting>
 
       <para>Both <makevar>CC</makevar> and <makevar>CXX</makevar>
 	variables can be defined on FreeBSD systems in
 	<filename>/etc/make.conf</filename>.  The first example
 	defines a value if it was not previously set in
 	<filename>/etc/make.conf</filename>, preserving any
 	system-wide definitions.  The second example clobbers
 	anything previously defined.</para>
     </sect1>
 
     <sect1 id="dads-cflags">
       <title>Respect <makevar>CFLAGS</makevar></title>
 
       <para>The port must respect the <makevar>CFLAGS</makevar>
 	variable.  What we mean by this is that the port must not
 	set the value of this variable absolutely, overriding the
 	existing value; instead, it may append whatever values it
 	needs to the existing value.  This is so that build options
 	that affect all ports can be set globally.</para>
 
       <para>If it does not, please add <literal>NO_PACKAGE=ignores
 	  cflags</literal> to the
 	<filename>Makefile</filename>.</para>
 
       <para>An example of a <filename>Makefile</filename> respecting
 	the <makevar>CFLAGS</makevar> variable follows.  Note the
 	<makevar>+=</makevar>:</para>
 
       <programlisting>CFLAGS+= -Wall -Werror</programlisting>
 
       <para>Here is an example which does not respect the
 	<makevar>CFLAGS</makevar> variable:</para>
 
       <programlisting>CFLAGS= -Wall -Werror</programlisting>
 
       <para>The <makevar>CFLAGS</makevar> variable is defined on
 	FreeBSD systems in <filename>/etc/make.conf</filename>.  The
 	first example appends additional flags to the
 	<makevar>CFLAGS</makevar> variable, preserving any system-wide
 	definitions.  The second example clobbers anything previously
 	defined.</para>
 
       <para>You should remove optimization flags from the third party
 	<filename>Makefile</filename>s.  System
 	<makevar>CFLAGS</makevar> contains system-wide optimization
 	flags.  An example from an unmodified
 	<filename>Makefile</filename>:</para>
 
       <programlisting>CFLAGS= -O3 -funroll-loops -DHAVE_SOUND</programlisting>
 
       <para>Using system optimization flags, the
 	<filename>Makefile</filename> would look similar to the
 	following example:</para>
 
       <programlisting>CFLAGS+= -DHAVE_SOUND</programlisting>
     </sect1>
 
     <sect1 id="dads-pthread">
       <title>Threading Libraries</title>
 
       <para>The threading library must be linked to the binaries using
 	a special flag <literal>-pthread</literal> on &os;.  If
 	a port insists on linking <literal>-lpthread</literal>
 	directly, patch it to use <literal>-pthread</literal>.</para>
 
       <note>
 	<para>If building the port errors out with
 	  <literal>unrecognized option '-pthread'</literal>, it may be
 	  desirable to use <command>cc</command> as linker by setting
 	  <makevar>CONFIGURE_ENV</makevar> to
 	  <literal>LD=${CC}</literal>.  The
 	  <literal>-pthread</literal> option is not supported by
 	  <command>ld</command> directly.</para>
       </note>
     </sect1>
 
     <sect1 id="dads-freedback">
       <title>Feedback</title>
 
       <para>Do send applicable changes/patches to the original
 	author/maintainer for inclusion in next release of the code.
 	This will only make your job that much easier for the next
 	release.</para>
     </sect1>
 
     <sect1 id="dads-readme">
       <title><filename>README.html</filename></title>
 
       <para>Do not include the <filename>README.html</filename> file.
 	This file is not part of the SVN collection but is generated
 	using the <command>make readme</command> command.</para>
 
       <note>
 	<para>If <command>make readme</command> fails, make sure that
 	  the default value of <makevar>ECHO_MSG</makevar> has not
 	  been modified by the port.</para>
       </note>
     </sect1>
 
     <sect1 id="dads-noinstall">
       <title>Marking a Port Not Installable with
 	<makevar>BROKEN</makevar>, <makevar>FORBIDDEN</makevar>, or
 	<makevar>IGNORE</makevar></title>
 
       <para>In certain cases users should be prevented from installing
 	a port.  To tell a user that a port should not be installed,
 	there are several <command>make</command> variables that can
 	be used in a port's <filename>Makefile</filename>.  The value
 	of the following <command>make</command> variables will be the
 	reason that is given back to users for why the port refuses to
 	install itself.  Please use the correct
 	<command>make</command> variable as each make variable conveys
 	radically different meanings to both users, and to automated
 	systems that depend on the <filename>Makefile</filename>s,
 	such as <link linkend="build-cluster">the ports build
 	cluster</link>, <link linkend="freshports">FreshPorts</link>,
 	and <link linkend="portsmon">portsmon</link>.</para>
 
       <sect2 id="dads-noinstall-variables">
 	<title>Variables</title>
 
 	<itemizedlist>
 	  <listitem>
 	    <para><makevar>BROKEN</makevar> is reserved for ports that
 	      currently do not compile, install, or deinstall
 	      correctly.  It should be used for ports where the
 	      problem is believed to be temporary.</para>
 
 	    <para>If instructed, the build cluster will still attempt
 	      to try to build them to see if the underlying problem
 	      has been resolved.  (However, in general, the cluster is
 	      run without this.)</para>
 
 	    <para>For instance, use <makevar>BROKEN</makevar> when a
 	      port:</para>
 
 	    <itemizedlist>
 	      <listitem>
 		<para>does not compile</para>
 	      </listitem>
 
 	      <listitem>
 		<para>fails its configuration or installation
 		  process</para>
 	      </listitem>
 
 	      <listitem>
 		<para>installs files outside of
 		  <filename>${LOCALBASE}</filename></para>
 	      </listitem>
 
 	      <listitem>
 		<para>does not remove all its files cleanly upon
 		  deinstall (however, it may be acceptable, and
 		  desirable, for the port to leave user-modified files
 		  behind)</para>
 	      </listitem>
 	    </itemizedlist>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>FORBIDDEN</makevar> is used for ports that
 	      contain a security vulnerability or induce grave concern
 	      regarding the security of a FreeBSD system with a given
 	      port installed (e.g., a reputably insecure program or a
 	      program that provides easily exploitable services).
 	      Ports should be marked as <makevar>FORBIDDEN</makevar>
 	      as soon as a particular piece of software has a
 	      vulnerability and there is no released upgrade.  Ideally
 	      ports should be upgraded as soon as possible when a
 	      security vulnerability is discovered so as to reduce the
 	      number of vulnerable FreeBSD hosts (we like being known
 	      for being secure), however sometimes there is a
 	      noticeable time gap between disclosure of a
 	      vulnerability and an updated release of the vulnerable
 	      software.  Do not mark a port
 	      <makevar>FORBIDDEN</makevar> for any reason other than
 	      security.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><makevar>IGNORE</makevar> is reserved for ports that
 	      should not be built for some other reason.  It should be
 	      used for ports where the problem is believed to be
 	      structural.  The build cluster will not, under any
 	      circumstances, build ports marked as
 	      <makevar>IGNORE</makevar>.  For instance, use
 	      <makevar>IGNORE</makevar> when a port:</para>
 
 	    <itemizedlist>
 	      <listitem>
 		<para>compiles but does not run properly</para>
 	      </listitem>
 
 	      <listitem>
 		<para>does not work on the installed version of
 		  &os;</para>
 	      </listitem>
 
 	      <listitem>
 		<para>requires &os; kernel sources to build, but the
 		  user does not have them installed</para>
 	      </listitem>
 
 	      <listitem>
 		<para>has a distfile which may not be automatically
 		  fetched due to licensing restrictions</para>
 	      </listitem>
 
 	      <listitem>
 		<para>does not work with some other currently
 		  installed port (for instance, the port depends on
 		  <filename role="package">www/apache20</filename> but
 		  <filename role="package">www/apache22</filename> is
 		  installed)</para>
 	      </listitem>
 	    </itemizedlist>
 
 	    <note>
 	      <para>If a port would conflict with a currently
 		installed port (for example, if they install a file in
 		the same place that performs a different function),
 		<link linkend="conflicts">use
 		<makevar>CONFLICTS</makevar> instead</link>.
 		<makevar>CONFLICTS</makevar> will set
 		<makevar>IGNORE</makevar> by itself.</para>
 	    </note>
 	  </listitem>
 
 	  <listitem>
 	    <para>If a port should be marked <makevar>IGNORE</makevar>
 	      only on certain architectures, there are two other
 	      convenience variables that will automatically set
 	      <makevar>IGNORE</makevar> for you:
 	      <makevar>ONLY_FOR_ARCHS</makevar> and
 	      <makevar>NOT_FOR_ARCHS</makevar>.  Examples:</para>
 
 	    <programlisting>ONLY_FOR_ARCHS=	i386 amd64</programlisting>
 
 	    <programlisting>NOT_FOR_ARCHS=	ia64 sparc64</programlisting>
 
 	    <para>A custom <makevar>IGNORE</makevar> message can be
 	      set using <makevar>ONLY_FOR_ARCHS_REASON</makevar> and
 	      <makevar>NOT_FOR_ARCHS_REASON</makevar>.  Per
 	      architecture entries are possible with
 	      <makevar>ONLY_FOR_ARCHS_REASON_<replaceable>ARCH</replaceable></makevar>
 	      and
 	      <makevar>NOT_FOR_ARCHS_REASON_<replaceable>ARCH</replaceable></makevar>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>If a port fetches i386 binaries and installs them,
 	      <makevar>IA32_BINARY_PORT</makevar> should be set.  If
 	      this variable is set, it will be checked whether the
 	      <filename>/usr/lib32</filename> directory is available
 	      for IA32 versions of libraries and whether the kernel
 	      has IA32 compatibility compiled in.  If one of these two
 	      dependencies is not satisfied, <makevar>IGNORE</makevar>
 	      will be set automatically.</para>
 	  </listitem>
 	</itemizedlist>
       </sect2>
 
       <sect2 id="dads-noinstall-notes">
 	<title>Implementation Notes</title>
 
 	<para>The strings should not be quoted.
 	  Also, the wording of the string should be somewhat
 	  different due to the way the information is shown to the
 	  user.  Examples:</para>
 
 	<programlisting>BROKEN=	this port is unsupported on FreeBSD 5.x</programlisting>
 
 	<programlisting>IGNORE=	is unsupported on FreeBSD 5.x</programlisting>
 
 	<para>resulting in the following output from
 	  <command>make describe</command>:</para>
 
 	<programlisting>===&gt;  foobar-0.1 is marked as broken: this port is unsupported on FreeBSD 5.x.</programlisting>
 
 	<programlisting>===&gt;  foobar-0.1 is unsupported on FreeBSD 5.x.</programlisting>
       </sect2>
     </sect1>
 
     <sect1 id="dads-deprecated">
       <title>Marking a Port for Removal with
 	<makevar>DEPRECATED</makevar> or
 	<makevar>EXPIRATION_DATE</makevar></title>
 
       <para>Do remember that <makevar>BROKEN</makevar> and
 	<makevar>FORBIDDEN</makevar> are to be used as a temporary
 	resort if a port is not working.  Permanently broken ports
 	should be removed from the tree entirely.</para>
 
       <para>When it makes sense to do so, users can be warned about
 	a pending port removal with <makevar>DEPRECATED</makevar>
 	and <makevar>EXPIRATION_DATE</makevar>.  The former is
 	simply a string stating why the port is scheduled for removal;
 	the latter is a string in ISO 8601 format (YYYY-MM-DD).  Both
 	will be shown to the user.</para>
 
       <para>It is possible to set <makevar>DEPRECATED</makevar>
 	without an <makevar>EXPIRATION_DATE</makevar> (for instance,
 	recommending a newer version of the port), but the converse
 	does not make any sense.</para>
 
       <para>There is no set policy on how much notice to give.
 	Current practice seems to be one month for security-related
 	issues and two months for build issues.  This also gives any
 	interested committers a little time to fix the
 	problems.</para>
     </sect1>
 
     <sect1 id="dads-dot-error">
       <title>Avoid Use of the <literal>.error</literal>
 	Construct</title>
 
       <para>The correct way for a <filename>Makefile</filename> to
 	signal that the port can not be installed due to some external
 	factor (for instance, the user has specified an illegal
 	combination of build options) is to set a non-blank value to
 	<makevar>IGNORE</makevar>.  This value will be formatted and
 	shown to the user by <command>make install</command>.</para>
 
       <para>It is a common mistake to use <literal>.error</literal>
 	for this purpose.  The problem with this is that many
 	automated tools that work with the ports tree will fail in
 	this situation.  The most common occurrence of this is seen
 	when trying to build <filename>/usr/ports/INDEX</filename>
 	(see <xref linkend="make-describe"/>).  However, even more
 	trivial commands such as <command>make maintainer</command>
 	also fail in this scenario.  This is not acceptable.</para>
 
       <example id="dot-error-breaks-index">
 	<title>How to Avoid Using <literal>.error</literal></title>
 
 	<para>Assume that someone has the line</para>
 
 	<programlisting>USE_POINTYHAT=yes</programlisting>
 
 	<para>in <filename>make.conf</filename>.  The first of the
 	  next two <filename>Makefile</filename> snippets will cause
 	  <command>make index</command> to fail, while the second one
 	  will not:</para>
 
 	<programlisting>.if USE_POINTYHAT
 .error "POINTYHAT is not supported"
 .endif</programlisting>
 
 	<programlisting>.if USE_POINTYHAT
 IGNORE=	POINTYHAT is not supported
 .endif</programlisting>
       </example>
     </sect1>
 
     <sect1 id="dads-sysctl">
       <title>Usage of <filename>sysctl</filename></title>
 
       <para>The usage of <filename>sysctl</filename> is discouraged
 	except in targets.  This is because the evaluation of any
 	<literal>makevar</literal>s, such as used during
 	<command>make index</command>, then has to run the command,
 	further slowing down that process.</para>
 
       <para>Usage of &man.sysctl.8; should always be done with the
 	<makevar>SYSCTL</makevar> variable, as it contains the fully
 	qualified path and can be overridden, if one has such a
 	special need.</para>
     </sect1>
 
     <sect1 id="dads-rerolling-distfiles">
       <title>Rerolling Distfiles</title>
 
       <para>Sometimes the authors of software change the content of
 	released distfiles without changing the file's name.  You have
 	to verify that the changes are official and have been
 	performed by the author.  It has happened in the past that the
 	distfile was silently altered on the download servers with the
 	intent to cause harm or compromise end user security.</para>
 
       <para>Put the old distfile aside, download the new one, unpack
 	them and compare the content with &man.diff.1;.  If you see
 	nothing suspicious, you can update
 	<filename>distinfo</filename>.  Be sure to summarize the
 	differences in your PR or commit log, so that other people
 	know that you have taken care to ensure that nothing bad has
 	happened.</para>
 
       <para>You might also want to contact the authors of the software
 	and confirm the changes with them.</para>
     </sect1>
 
     <sect1 id="dads-avoiding-linuxisms">
       <title>Avoiding Linuxisms</title>
 
       <para>Do not use <filename>/proc</filename> if there are any
 	other ways of getting the information, e.g.,
 	<function>setprogname(argv[0])</function> in
 	<function>main()</function> and then &man.getprogname.3; if
 	you want to <quote>know your name</quote>.</para>
 
       <para>Do not rely on behaviour that is undocumented by
 	<acronym>POSIX</acronym>.</para>
 
       <para>Do not record timestamps in the critical path of the
 	application if it also works without.  Getting timestamps may
 	be slow, depending on the accuracy of timestamps in the
 	<acronym>OS</acronym>.  If timestamps are really needed,
 	determine how precise they have to be and use an
 	<acronym>API</acronym> which is documented to just deliver the
 	needed precision.</para>
 
       <para>A number of simple syscalls (for example
 	&man.gettimeofday.2;, &man.getpid.2;) are much faster on
 	&linux; than on any other operating system due to caching and
 	the vsyscall performance optimizations.  Do not rely on them
 	being cheap in performance-critical applications.  In general,
 	try hard to avoid syscalls if possible.</para>
 
       <para>Do not rely on &linux;-specific socket behaviour.  In
 	particular, default socket buffer sizes are different (call
 	&man.setsockopt.2; with <literal>SO_SNDBUF</literal> and
 	<literal>SO_RCVBUF</literal>, and while &linux;'s &man.send.2;
 	blocks when the socket buffer is full, &os;'s will fail and
 	set <literal>ENOBUFS</literal> in errno.</para>
 
       <para>If relying on non-standard behaviour is required,
 	encapsulate it properly into a generic <acronym>API</acronym>,
 	do a check for the behaviour in the configure stage, and stop
 	if it is missing.</para>
 
       <para>Check the <ulink
 	  url="http://www.freebsd.org/cgi/man.cgi">man pages</ulink>
 	to see if the function used is a <acronym>POSIX</acronym>
 	interface (in the <quote>STANDARDS</quote> section of the man
 	page).</para>
 
       <para>Do not assume that <filename>/bin/sh</filename> is
 	<application>bash</application>.  Ensure that a command line
 	passed to &man.system.3; will work with a
 	<acronym>POSIX</acronym> compliant shell.</para>
 
       <para>A list of common <application>bash</application>isms is
 	available <ulink
 	  url="https://wiki.ubuntu.com/DashAsBinSh">here</ulink>.</para>
 
       <para>Do not <literal>#include
 	  <filename>&lt;stdint.h&gt;</filename></literal> if
 	<filename>inttypes.h</filename> is sufficient.  This will
 	ensure that the software builds on older versions of
 	&os;.</para>
 
       <para>Check that headers are included in the
 	<acronym>POSIX</acronym> or man page recommended way, e.g.,
 	<filename>sys/types.h</filename> is often forgotten, which is
 	not as much of a problem for &linux; as it is for &os;.</para>
 
       <para>Compile threaded applications with
 	<quote>-pthread</quote>, not <quote>-lpthread</quote> or
 	variations thereof.</para>
 
     </sect1>
 
     <sect1 id="dads-misc">
       <title>Miscellanea</title>
 
       <para>The files <filename>pkg-descr</filename> and
 	<filename>pkg-plist</filename> should each be double-checked.
 	If you are reviewing a port and feel they can be worded
 	better, do so.</para>
 
       <para>Do not copy more copies of the GNU General Public License
 	into our system, please.</para>
 
       <para>Please be careful to note any legal issues! Do not let us
 	illegally distribute software!</para>
     </sect1>
 
   </chapter>
 
   <chapter id="porting-samplem">
     <title>A Sample <filename>Makefile</filename></title>
 
     <para>Here is a sample <filename>Makefile</filename> that you can
       use to create a new port.  Make sure you remove all the extra
       comments (ones between brackets)!</para>
 
     <para>It is recommended that you follow this format (ordering of
       variables, empty lines between sections, etc.).  This format is
       designed so that the most important information is easy to
       locate.  We recommend that you use <link
 	linkend="porting-portlint">portlint</link> to check the
       <filename>Makefile</filename>.</para>
 
     <programlisting>[the header...just to make it easier for us to identify the ports.]
 # Created by: Satoshi Asami &lt;asami@FreeBSD.org&gt;
 [The optional <emphasis>Created by:</emphasis> line names the person who originally
 created the port.  Note that the <quote>:</quote> is followed by a space
 and not a tab character.
 If this line is present, future maintainers should
 not change or remove it except at the original author's request.]
 
 # &dollar;FreeBSD&dollar;
 [ ^^^^^^^^^ This will be automatically replaced with RCS ID string by SVN
 when it is committed to our repository.  If upgrading a port, do not alter
 this line back to "&dollar;FreeBSD&dollar;".  SVN deals with it automatically.]
 
 [section to describe the port itself and the master site - PORTNAME
  and PORTVERSION are always first, followed by CATEGORIES,
  and then MASTER_SITES, which can be followed by MASTER_SITE_SUBDIR.
  PKGNAMEPREFIX and PKGNAMESUFFIX, if needed, will be after that.
  Then comes DISTNAME, EXTRACT_SUFX and/or DISTFILES, and then
  EXTRACT_ONLY, as necessary.]
 PORTNAME=	xdvi
 PORTVERSION=	18.2
 CATEGORIES=	print
 [do not forget the trailing slash ("/")!
  if you are not using MASTER_SITE_* macros]
 MASTER_SITES=	${MASTER_SITE_XCONTRIB}
 MASTER_SITE_SUBDIR=	applications
 PKGNAMEPREFIX=	ja-
 DISTNAME=	xdvi-pl18
 [set this if the source is not in the standard ".tar.gz" form]
 EXTRACT_SUFX=	.tar.Z
 
 [section for distributed patches -- can be empty]
 PATCH_SITES=	ftp://ftp.sra.co.jp/pub/X11/japanese/
 PATCHFILES=	xdvi-18.patch1.gz xdvi-18.patch2.gz
 
 [maintainer; *mandatory*!  This is the person who is volunteering to
  handle port updates, build breakages, and to whom a users can direct
  questions and bug reports.  To keep the quality of the Ports Collection
  as high as possible, we no longer accept new ports that are assigned to
  "ports@FreeBSD.org".]
 MAINTAINER=	asami@FreeBSD.org
 COMMENT=	A DVI Previewer for the X Window System
 
 [dependencies -- can be empty]
 RUN_DEPENDS=	gs:${PORTSDIR}/print/ghostscript
 LIB_DEPENDS=	Xpm:${PORTSDIR}/graphics/xpm
 
 [this section is for other standard bsd.port.mk variables that do not
  belong to any of the above]
 [If it asks questions during configure, build, install...]
 IS_INTERACTIVE=	yes
 [If it extracts to a directory other than ${DISTNAME}...]
 WRKSRC=		${WRKDIR}/xdvi-new
 [If the distributed patches were not made relative to ${WRKSRC}, you
  may need to tweak this]
 PATCH_DIST_STRIP=	-p1
 [If it requires a "configure" script generated by GNU autoconf to be run]
 GNU_CONFIGURE=	yes
 [If it requires GNU make, not /usr/bin/make, to build...]
 USE_GMAKE=	yes
 [If it is an X application and requires "xmkmf -a" to be run...]
 USE_IMAKE=	yes
 [et cetera.]
 
 [non-standard variables to be used in the rules below]
 MY_FAVORITE_RESPONSE=	"yeah, right"
 
 [then the special rules, in the order they are called]
 pre-fetch:
 	i go fetch something, yeah
 
 post-patch:
 	i need to do something after patch, great
 
 pre-install:
 	and then some more stuff before installing, wow
 
 [and then the epilogue]
 .include &lt;bsd.port.mk&gt;</programlisting>
   </chapter>
 
   <chapter id="keeping-up">
     <title>Keeping Up</title>
 
     <para>The &os; Ports Collection is constantly changing.  Here is
       some information on how to keep up.</para>
 
     <sect1 id="freshports">
       <title>FreshPorts</title>
 
       <para>One of the easiest ways to learn about updates that have
 	already been committed is by subscribing to <ulink
 	  url="http://www.FreshPorts.org/">FreshPorts</ulink>.  You
 	can select multiple ports to monitor.  Maintainers are
 	strongly encouraged to subscribe, because they will receive
 	notification of not only their own changes, but also any
 	changes that any other &os; committer has made.  (These are
 	often necessary to keep up with changes in the underlying
 	ports framework&mdash;although it would be most polite to
 	receive an advance heads-up from those committing such
 	changes, sometimes this is overlooked or just simply
 	impractical.  Also, in some cases, the changes are very minor
 	in nature.  We expect everyone to use their best judgement in
 	these cases.)</para>
 
       <para>If you wish to use FreshPorts, all you need is an account.
 	If your registered email address is
 	<literal>@FreeBSD.org</literal>, you will see the opt-in link
 	on the right hand side of the webpages.  For those of you who
 	already have a FreshPorts account, but are not using your
 	<literal>@FreeBSD.org</literal> email address, just change
 	your email to <literal>@FreeBSD.org</literal>, subscribe, then
 	change it back again.</para>
 
       <para>FreshPorts also has a sanity test feature which
 	automatically tests each commit to the FreeBSD ports tree.  If
 	subscribed to this service, you will be notified of any errors
 	which FreshPorts detects during sanity testing of your
 	commits.</para>
     </sect1>
 
     <sect1 id="svnweb">
       <title>The Web Interface to the Source Repository</title>
 
       <para>It is possible to browse the files in the source
 	repository by using a web interface.  Changes that affect the
 	entire port system are now documented in the <ulink
 	  url="http://svnweb.FreeBSD.org/ports/head/CHANGES">CHANGES</ulink>
 	file.  Changes that affect individual ports
 	are now documented in the <ulink
 	  url="http://svnweb.FreeBSD.org/ports/head/UPDATING">UPDATING</ulink>
 	file.  However, the definitive answer to
 	any question is undoubtedly to read the source code of <ulink
 	  url="http://svnweb.FreeBSD.org/ports/head/Mk/bsd.port.mk">bsd.port.mk</ulink>,
 	and associated files.</para>
     </sect1>
 
     <sect1 id="ports-mailling-list">
       <title>The &os; Ports Mailing List</title>
 
       <para>If you maintain ports, you should consider following the
 	&a.ports;.  Important changes to the way ports work will be
 	announced there, and then committed to
 	<filename>CHANGES</filename>.</para>
 
       <para>If this mailing list is too high volume you may consider
 	following &a.ports-announce; which is moderated and has no
 	discussion.</para>
     </sect1>
 
     <sect1 id="build-cluster">
       <title>The &os; Port Building Cluster on
 	<hostid role="hostname">pointyhat.FreeBSD.org</hostid></title>
 
       <para>One of the least-publicized strengths of &os; is that
 	an entire cluster of machines is dedicated to continually
 	building the Ports Collection, for each of the major OS
 	releases and for each Tier-1 architecture.  You can find
 	the results of these builds at <ulink
 	  url="http://pointyhat.FreeBSD.org/">package building logs
 	  and errors</ulink>.</para>
 
       <para>Individual ports are built unless they are specifically
 	marked with <makevar>IGNORE</makevar>.  Ports that are
 	marked with <makevar>BROKEN</makevar> will still be attempted,
 	to see if the underlying problem has been resolved.  (This
 	is done by passing <makevar>TRYBROKEN</makevar> to the
 	port's <filename>Makefile</filename>.)</para>
     </sect1>
 
     <sect1 id="distfile-survey">
       <title>Portscout: the &os; Ports Distfile Scanner</title>
 
       <para>The build cluster is dedicated to building the latest
 	release of each port with distfiles that have already been
 	fetched.  However, as the Internet continually changes,
 	distfiles can quickly go missing.  <ulink
 	  url="http://portscout.FreeBSD.org">Portscout</ulink>, the
 	&os; Ports distfile scanner, attempts to query every download
 	site for every port to find out if each distfile is still
 	available.  <application>Portscout</application> can generate
 	<acronym>HTML</acronym> reports and send emails about newly
 	available ports to those who request them.  Unless not
 	otherwise subscribed, maintainers are asked to check
 	periodically for changes, either by hand or using the
 	<acronym>RSS</acronym> feed.</para>
 
       <para><application>Portscout</application>'s first page gives
 	the email address of the port maintainer, the number of ports
 	the maintainer is responsible for, the number of those ports
 	with new distfiles, and the percentage of those ports that are
 	out-of-date.  The search function allows for searching by
 	email address for a specific maintainer, and for selecting
 	whether or not only out-of-date ports should be shown.</para>
 
       <para>Upon clicking on a maintainer's email address,
 	a list of all of their ports is displayed, along with port
 	category, current version number, whether or not there is a
 	new version, when the port was last updated, and finally when
 	it was last checked.  A search function on this page allows
 	the user to search for a specific port.</para>
 
       <para>Clicking on a port name in the list displays the
 	<ulink url="http://freshports.org">FreshPorts</ulink> port
 	information.</para>
     </sect1>
 
     <sect1 id="portsmon">
       <title>The &os; Ports Monitoring System</title>
 
       <para>Another handy resource is the <ulink
 	  url="http://portsmon.FreeBSD.org"> FreeBSD Ports Monitoring
 	  System</ulink> (also known as <literal>portsmon</literal>).
 	This system comprises a database that processes information
 	from several sources and allows it to be browsed via a web
 	interface.  Currently, the ports Problem Reports (PRs), the
 	error logs from the build cluster, and individual files from
 	the ports collection are used.  In the future, this will be
 	expanded to include the distfile survey, as well as other
 	sources.</para>
 
       <para>To get started, you can view all information about a
 	particular port by using the <ulink
 	  url="http://portsmon.FreeBSD.org/portoverview.py">
 	  Overview of One Port</ulink>.</para>
 
       <para>As of this writing, this is the only resource available
 	that maps GNATS PR entries to portnames.  (PR submitters do
 	not always include the portname in their Synopsis, although we
 	would prefer that they did.)  So, <literal>portsmon</literal>
 	is a good place to start if you want to find out whether an
 	existing port has any PRs filed against it and/or any build
 	errors; or, to find out if a new port that you may be thinking
 	about creating has already been submitted.</para>
     </sect1>
   </chapter>
 
   <chapter id="appendices">
     <title>Appendices</title>
 
     <sect1 id="uses-values">
       <title>Values of <makevar>USES</makevar></title>
 
       <table frame="none">
 	<title>Values of <makevar>USES</makevar></title>
 
 	<tgroup cols="3">
 	  <thead>
 	    <row>
 	      <entry>Feature</entry>
 	      <entry>Arguments</entry>
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    &values.uses;
 	  </tbody>
 	</tgroup>
       </table>
     </sect1>
   </chapter>
 </book>
diff --git a/en_US.ISO8859-1/htdocs/java/install.xml b/en_US.ISO8859-1/htdocs/java/install.xml
index 036022a6ed..5079f72596 100644
--- a/en_US.ISO8859-1/htdocs/java/install.xml
+++ b/en_US.ISO8859-1/htdocs/java/install.xml
@@ -1,54 +1,44 @@
 <?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/doc/share/xml/xhtml10-freebsd.dtd" [
 <!ENTITY title "FreeBSD &java; Project: How To Install">
 ]>
 <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.developers">
 
 <p>When installing Java on FreeBSD you have the choice between
 different Java Development Kits:</p>
 
 <h3><a name="openjdk">OpenJDK on FreeBSD</a></h3>
 
 <p>This is a native port of OpenJDK to FreeBSD.</p>
 
 <p><code>cd /usr/ports/java/openjdk6
 <br/>make install clean
 </code></p>
 
-<h3><a name="jdk">Oracle JDK on FreeBSD</a></h3>
-
-<p>This is the effort of the Java FreeBSD porting project.
-By the use of patchsets and the JDK source code released by Oracle,
-this port builds a native JDK for FreeBSD.</p>
-
-<p><code>cd /usr/ports/java/jdk16
-<br/>make install clean
-</code></p>
-
 <h3><a name="linux-sun-jdk">Oracle JDK for Linux</a></h3>
 
 <p>This port installs the Java Development Kit from Oracle which was built for Linux. It will run under FreeBSD using the Linux compatibility.</p>
 
 <p><code>cd /usr/ports/java/linux-sun-jdk16
 <br/>make install clean
 </code></p>
 
 <p><b>Note:</b> Please note that due to the current licensing policy the
 Oracle JDK on FreeBSD binaries can not be distributed and you are only
 permitted to use them personally.  Due to the same reasons you have to
 manually fetch the source code and patchset for FreeBSD.</p>
 
 <p>If you should have trouble, you can see the <a href="../doc/en_US.ISO8859-1/books/handbook/ports.html">
 FreeBSD Handbook section on &quot;installing applications&quot;</a> for
 help.</p>
 
 </body>
 </html>
diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml
index 9bfbe5ee01..018f6e21b8 100644
--- a/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml
+++ b/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml
@@ -1,618 +1,754 @@
 <?xml version="1.0" encoding="utf-8" ?>
 <!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" "http://www.FreeBSD.org/XML/www/share/xml/statusreport.dtd" >
 <!-- $FreeBSD$ -->
 <report>
   <date>
     <month>April-June</month>
 
     <year>2013</year>
   </date>
 
   <section>
     <title>Introduction</title>
 
     <p>This report covers &os;-related projects between April and June
       2013.  This is the second of four reports planned for 2013.</p>
 
     <!-- XXX: theraven's part goes here -->
 
     <!-- XXX: keep updating the number of entries -->
     <p>Thanks to all the reporters for the excellent work!  This report
-      contains 12 entries and we hope you enjoy reading it.</p>
+      contains 14 entries and we hope you enjoy reading it.</p>
 
     <!-- XXX: set date for the next set of submissions -->
     <p>The deadline for submissions covering between July and September 2013
       is not yet decided.</p>
   </section>
 
   <category>
     <name>team</name>
 
     <description>&os; Team Reports</description>
   </category>
 
   <category>
     <name>proj</name>
 
     <description>Projects</description>
   </category>
 
   <category>
     <name>kern</name>
 
     <description>Kernel</description>
   </category>
 
   <category>
     <name>arch</name>
 
     <description>Architectures</description>
   </category>
 
   <category>
     <name>bin</name>
 
     <description>Userland Programs</description>
   </category>
 
   <category>
     <name>ports</name>
 
     <description>Ports</description>
   </category>
 
   <category>
     <name>docs</name>
 
     <description>Documentation</description>
   </category>
 
   <project cat='proj'>
     <title>PC-BSD</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Kris</given>
 	  <common>Moore</common>
 	</name>
 	<email>kmoore@FreeBSD.org</email>
       </person>
     </contact>
 
     <links>
       <url href="http://www.pcbsd.org">PC-BSD Home Page</url>
     </links>
 
     <body>
       <p>Progress on moving PC-BSD &amp; TrueOS to a "rolling release"
 	is happening quickly.  We have implemented our own package
 	repository, fully based on <tt>pkg(8)</tt>, which is updated twice
 	monthly, and are now hosting dedicated
 	<tt>freebsd-update(8)</tt> systems.  In addition to the
 	<tt>9.1-RELEASE</tt> ISO images, we have begun to create a
 	<tt>9-STABLE</tt> branch as well, using
 	<tt>freebsd-update(8)</tt> to push out the latest world and
 	kernel binaries on a monthly basis.</p>
 
       <p>We are currently working on an implementation of ZFS Boot
 	Environments for desktops and servers.  These users to install
 	updates or experimental versions in separate ZFS clones and
 	select the one to run at boot time, providing an easy way of
 	testing upgrades before deployment.</p>
     </body>
   </project>
 
   <project cat='kern'>
     <title>Wireless Networking Improvements</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Adrian</given>
 	  <common>Chadd</common>
 	</name>
 	<email>adrian@FreeBSD.org</email>
       </person>
     </contact>
 
     <links/>
 
     <body>
       <p>Recently the &os; wireless networking stack has received
 	updates in the following areas:</p>
 
       <ul>
 	<li>Improved transmit locking in <tt>net80211(4)</tt> to
 	  eliminate a whole class of subtle race conditions leading to
 	  out-of-order packets being handed to the driver.</li>
 
 	<li>Spectral scan (FFT) information is now available for the
 	  AR9280, AR9285, AR9287 series NICs.</li>
 
 	<li>Added support for AR93xx, AR94xx, AR95xx NICs &mdash;
 	  <tt>hostap</tt>, <tt>adhoc</tt> and <tt>station</tt> modes
 	  have been tested, including 3x3 stream support for the those
 	  NICs where appropriate.</li>
 
 	<li>Implemented ps-poll handling in <tt>hostap</tt> mode.  This
 	  was required for correct behaviour with stations that implement
 	  aggressive power save.</li>
 
 	<li>Added AR933x SoC support &mdash; including all on-board
 	  peripherals &mdash; the <tt>8devices.com</tt> Carambola-2
 	  board is now fully supported and will run &os; from NOR
 	  flash.</li>
       </ul>
     </body>
   </project>
 
   <project cat='arch'>
     <title>Intel IOMMU (VT-d, DMAR) Support</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Konstantin</given>
 	  <common>Belousov</common>
 	</name>
 	<email>kib@FreeBSD.org</email>
       </person>
     </contact>
 
     <links>
       <url href="http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/vt-directed-io-spec.html"/>
       <url href="http://lists.freebsd.org/pipermail/freebsd-arch/2013-May/014368.html"/>
       <url href="http://people.freebsd.org/~kib/misc/dmar.1.patch"/>
     </links>
 
     <body>
       <p>A VT-d driver was developed that implements the
 	<tt>busdma(9)</tt> interface using the DMA Remap units (DMARs)
 	found in current Intel chipsets.  The driver provides
 	reliability and security improvements for the system by
 	facilitating restricted access to main memory from busmastering
 	devices.</p>
 
       <p>It also eliminates bounce buffering (copying) by allocating
 	remapped regions that satisfy a device's access limitations.</p>
 
       <p>With additional work to define a suitable interface the VT-d
 	driver will also provide PCI pass-through functionality for
 	hypervisors.</p>
 
       <p>This project is sponsored by the &os; Foundation.</p>
     </body>
 
     <help>
       <task>Implement workarounds for chipset errata.</task>
 
       <task>Commit to HEAD after additional testing.</task>
 
       <task>Rebalance MSI/MSI-X using interrupt remapping unit, also
 	required for x2APIC use on big machines.</task>
 
       <task>Integrate with the Intel GPU MMU and handle Ironlake and
 	SandyBridge errata for the GFXVTd unit.</task>
 
       <task>Provide an interface for VMM (hypervisors).</task>
 
       <task>Consider implementing a driver for AMD's IOMMU.</task>
     </help>
   </project>
 
   <project cat='kern'>
     <title>Multi-threaded Pagedaemon</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Konstantin</given>
 	  <common>Belousov</common>
 	</name>
 	<email>kib@FreeBSD.org</email>
       </person>
     </contact>
 
     <links>
       <url href="http://people.freebsd.org/~kib/misc/pagedaemon-numa.1.patch"/>
     </links>
 
     <body>
       <p>This project aims to improve scalability of the virtual memory
 	subsystem.  Based on a prototype change from Jeff Roberson,
 	per-domain page queues and per-domain pagedaemon working threads
 	have been implemented to enable this.  At the moment, the
 	domains coincide with the NUMA proximity domains, but this is
 	not neccessary and could be improved with further separation to
 	allow more parallelism in the pagedaemon.</p>
 
       <p>The patch is relatively simple, with the most delicate parts
 	being the page laundry and OOM logic, which requires coordination
 	between all pagedaemon threads to prevent false triggering.</p>
 
       <p>Testing on diverse workloads and on real multi-socket machines
 	is required.</p>
 
       <p>This project is sponsored by the &os; Foundation.</p>
     </body>
 
     <help>
       <task>Debug on multi-domain NUMA machine.</task>
 
       <task>Test, get review and commit.</task>
     </help>
   </project>
 
   <project cat='bin'>
     <title>HAST Module for <tt>bsnmpd(1)</tt></title>
 
     <contact>
       <person>
 	<name>
 	  <given>Mikolaj</given>
 	  <common>Golub</common>
 	</name>
 	<email>trociny@FreeBSD.org</email>
       </person>
     </contact>
 
     <links/>
 
     <body>
       <p>HAST module for <tt>bsnmpd(1)</tt> has been committed to
 	-CURRENT and merged to 8.x and 9.x -STABLE branches.  The module
 	allows to monitor and manage HAST via the SNMP protocol.</p>
     </body>
   </project>
 
   <project cat='team'>
     <title>&os; Release Engineering Team</title>
 
     <contact>
       <person>
 	<name>&os; Release Engineering Team</name>
 	<email>re@FreeBSD.org</email>
       </person>
     </contact>
 
     <links>
       <url href="http://www.freebsd.org/releases/8.4R/errata.html"/>
       <url href="http://www.freebsd.org/releases/9.2R/schedule.html"/>
     </links>
 
     <body>
       <p>The &os;&nbsp;8.4-RELEASE cycle completed on June 7, 2013,
 	approximately two months behind the original schedule.  Please
 	be sure to read the Errata Notices for any post-release issues
 	discovered after 8.4-RELEASE.</p>
 
       <p>The &os;&nbsp;9.2-RELEASE process will begin July 6, 2013.
 	Unless any critical issues arise, &os;&nbsp;9.2-RELEASE is
 	expected to be available late August or early September.</p>
 
       <p>Users tracking the &os;&nbsp;9.<i>X</i> branch are encouraged
 	to test the -BETA and -RC builds whenever possible, and provide
 	feedback and report issues to the <a
 	  href="http://lists.freebsd.org/pipermail/freebsd-stable">freebsd-stable
 	  mailing list</a>.</p>
     </body>
   </project>
 
   <project cat='proj'>
     <title>Virtual Private Systems</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Klaus</given>
 	  <common>Ohrhallinger</common>
 	</name>
 	<email>k@7he.at</email>
       </person>
     </contact>
 
     <links>
       <url href="http://www.7he.at/freebsd/vps/"/>
       <url href="http://svnweb.freebsd.org/base/projects/vps/"/>
     </links>
 
     <body>
       <p>VPS for &os; is an OS-level based virtualization implementation
 	that supports advanced features like live migration.  It has
 	been recently imported into the Project's Subversion repository
 	as a project branch.  The code is currently of alpha
 	quality.</p>
     </body>
 
     <help>
       <task>Test with many different guest setups/applications.  All
 	feedback is highly appreciated.</task>
     </help>
   </project>
 
   <project cat='ports'>
     <title>KDE/&os;</title>
 
     <contact>
       <person>
 	<name>
 	  <given>KDE</given>
 	  <common>&os;</common>
 	</name>
 	<email>kde@FreeBSD.org</email>
       </person>
     </contact>
 
     <links>
       <url href="http://FreeBSD.kde.org">KDE/&os; home page</url>
       <url href="http://FreeBSD.kde.org/area51.php">area51</url>
     </links>
 
     <body>
       <p>The KDE/&os; Team have continued to improve the experience of
 	KDE software and Qt under &os;.  During this quarter, the team
 	has kept most of the KDE and Qt ports up-to-date, working on the
 	following releases:</p>
 
       <ul>
 	<li>KDE SC: 4.10.2, 4.10.3, 4.10.4</li>
 	<li>Qt: 5.0.2 (area51)</li>
 	<li>PyQt: 4.10.2; QScintilla 2.7.2; SIP: 4.14.7</li>
 	<li>KDevelop: 4.5.1</li>
 	<li>Calligra: 2.6.2</li>
 	<li>CMake: 2.8.11.1</li>
 	<li>Digikam (and KIPI-plugins): 3.1.0, 3.2.0 </li>
 	<li>KDE Telepathy: 0.6.0, 0.6.1</li>
       </ul>
 
       <p>As a result &mdash; according to <a
 	  href="http://portscout.freebsd.org/kde@freebsd.org.html">PortScout</a>
 	&mdash; <tt>kde@</tt> has 473 ports (up from 431), of which
 	98.73% are up-to-date (up from 93.5%).  iXsystems Inc.
 	continues to provided a machine for the team to build packages
 	and to test updates.  iXsystems Inc. has been providing the
 	KDE/&os; Team with support for quite a long time and we are very
 	grateful for that.  This quarter, we would also like to thank
 	Steve Wills (<tt>swills@</tt>) for providing access to another
 	machine so that we can do our work even faster.</p>
 
       <p>While a great deal of the team's efforts are focused towards
 	packaging released code, we also take a proactive stand in
 	making sure future versions of the software we port is also
 	going to work well on &os;.  This involves being in close
 	contact with upstream, raising awareness of &os; as an active
 	project and also sending actual patches that most of the time
 	benefit many other operating systems besides &os; itself.  In
 	this regard, we have been dedicating a lot of time making sure
 	both <tt>clang</tt> and <tt>libc++</tt> are fully supported in
 	KDE and Qt.  Not only has this resulted in many patches being
 	sent to these projects, but the exposure to these large code
 	bases have been beneficial to the Clang-on-&os; project as well.
 	Dimitry Andric (<tt>dim@</tt>) has been of great help as a point
 	of contact for all the issues we have faced.</p>
 
       <p>As usual, the team is always looking for more testers and
 	porters so please contact us and visit our home page.  It would
 	be especially useful to have more helping hands on tasks such as
 	getting rid of the dependency on the defunct HAL project and
 	providing integration with KDE's Bluedevil Bluetooth
 	interface.</p>
     </body>
 
     <help>
       <task>Update out-of-date ports, see <a
 	  href="http://portscout.freebsd.org/kde@freebsd.org.html">PortScout</a>
 	for a list.</task>
       <task>Work on KDE 4.11 and Qt 5.</task>
       <task>Make sure the whole KDE stack (including Qt) builds and works
 	correctly with <tt>clang</tt> and <tt>libc++</tt>.</task>
       <task>Remove the dependency on HAL.</task>
     </help>
   </project>
 
   <project cat='docs'>
     <title>Upgrading the Documentation Set to DocBook 5.0</title>
 
     <contact>
       <person>
 	<name>
 	  <given>G&aacute;bor</given>
 	  <common>K&ouml;vesd&aacute;n</common>
 	</name>
 	<email>gabor@FreeBSD.org</email>
       </person>
     </contact>
 
     <body>
       <p>The Documentation Project has been using old versions of markup
 	standards until recently when we switched to a real XML
 	toolchain and DocBook 4.5.  However, we still depend on obsolete
 	technologies &mdash; DSSSL and Jade.  Besides, DocBook 5.0
 	provides cleaner markup and some nice new features.</p>
 
       <p>The objective of this project is to upgrade the documentation
 	set to DocBook 5.0 and to find a way to properly render our
 	sources without using DSSSL, since the DSSSL stylesheets are
 	discontinued and cannot render DocBook 5.0.  The documentation
 	sources have already been successfully transformed to DocBook
 	5.0 and updates to the rendering process are under
 	development.  The common opinion among &os; developers is that
 	Java is a heavy dependency that should be avoided.  This has
 	suggested the transformation of DocBook sources to TeX and use
 	TeX as a rendering backend.  There are two ways to do this; the
 	sources can be transformed either directly or through the XSL FO
 	output generated by the stylesheets provided for the DocBook Project.
 	The latter approach has been chosen as a preferred
 	way since it better fits the existing documentation
 	infrastructure and provides easier customization.</p>
 
       <p>This project is generously funded by The &os; Foundation.</p>
     </body>
 
     <help>
       <task>Finish the implementation of the rendering process.</task>
 
       <task>Integrate the rendering solution into the
 	infrastructure.</task>
 
       <task>Merge back changes to <tt>head</tt>.</task>
     </help>
   </project>
 
   <project cat='kern'>
     <title>AMD GPU Kernel Mode-setting Support</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Jean-S&eacute;bastien</given>
 	  <common>P&eacute;dron</common>
 	</name>
 	<email>dumbbell@FreeBSD.org</email>
       </person>
 
       <person>
 	<name>
 	  <given>Konstantin</given>
 	  <common>Belousov</common>
 	</name>
 	<email>kib@FreeBSD.org</email>
       </person>
     </contact>
 
     <links>
       <url
 	href="https://wiki.freebsd.org/AMD_GPU">Project status on the wiki</url>
     </links>
 
     <body>
       <p>Due to non-&os;-related activities from April to end of June,
 	the project progressed slowly:</p>
 
       <ul>
 	<li>Some important problems in TTM were fixed and several others
 	  are being worked out.  Applications affected by these bugs are
 	  non-linear video editing software (which do not use Xv to
 	  preview the video) or "screen" of VirtualBox, for
 	  instance.</li>
 
 	<li>Regarding the locking issue with OpenGL, no work has been
 	  done yet.  <tt>glxgears</tt> works but some modern desktop
 	  environments or WebGL demos hang.  Once TTM bugs described
 	  above are fixed, this is the next target.</li>
 
 	<li>Patches to Mesa to make it build out-of-the-box were
 	  submitted upstream.  As of writing, some were committed but
 	  not all of them.  Additionally, as result of a joint work with
 	  Jonathan Gray (of OpenBSD), Mesa should work on &os;, OpenBSD,
 	  and hopefully on other BSD flavors without additional
 	  patches.</li>
       </ul>
 
 	<p>Several users tested the driver.  Andriy Gapon, Jonathan
 	  Gray, and Mark Kettenis (of OpenBSD) submitted patches.  kyzh
 	  kindly donated several discrete cards from different series.
 	  A big thanks to all those contributors!</p>
 
 	<p>The driver is still not stable enough for a wider call for
 	  testers.</p>
     </body>
 
     <help>
       <task>Write instructions for the wiki to explain how to test the
 	driver.</task>
     </help>
   </project>
 
   <project cat='kern'>
     <title>Realtek RTL8188CU/RTL8192CU USB Wireless Driver</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Rui</given>
 	  <common>Paulo</common>
 	</name>
 	<email>rpaulo@FreeBSD.org</email>
       </person>
 
       <person>
 	<name>
 	  <given>Kevin</given>
 	  <common>Lo</common>
 	</name>
 	<email>kevlo@FreeBSD.org</email>
       </person>
     </contact>
 
     <body>
       <p>The <tt>urtwn(4)</tt> driver was imported from OpenBSD.  This
 	is a driver for very small Realtek USB WiFi cards which are pretty
 	inexpensive and can do 802.11n at the maximum theoretical speed
 	of 150 Mbps.  They make a good addition to embedded systems such
 	as the Raspberry Pi and the BeagleBone.  The driver requires
 	firmware that is available in the &os; Ports Collection
 	(<tt>net/urtwn-firmware-kmod</tt>).  Note that 802.11n is not
 	yet supported.</p>
     </body>
   </project>
 
   <project cat='kern'>
     <title>ZFS TRIM and Enhanced <tt>BIO_DELETE</tt> Support</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Pawel Jakub</given>
 	  <common>Dawidek</common>
 	</name>
 	<email>pjd@FreeBSD.org</email>
       </person>
 
       <person>
 	<name>
 	  <given>Steven</given>
 	  <common>Hartland</common>
 	</name>
 	<email>smh@FreeBSD.org</email>
       </person>
     </contact>
 
     <body>
       <p>As of the end of June, &os;'s ZFS implementation now includes
 	TRIM support in <tt>head</tt>, <tt>stable/9</tt>, and
 	<tt>stable/8</tt> branches.  This allows ZFS to help maintain
 	high performance on flash-based devices such as SSD's even under
 	high-load conditions.</p>
 
       <p>When creating new pools and adding new devices to existing
 	pools it first performs a full-device level TRIM to help ensure
 	optimum starting performance.  This behaviour can be overridden
 	by setting the <tt>vfs.zfs.vdev.trim_on_init</tt> sysctl
 	variable to <tt>0</tt> if for example the disks are new or have
 	already been secure erased, which can also now be done using
 	<tt>camcontrol(8)</tt> security actions.</p>
 
       <p>In order to support TRIM, the kernel requires the underlying
 	device driver supports <tt>BIO_DELETE</tt>.  This is currently
 	mapped through to hardware methods such as ATA TRIM and SCSI
 	UNMAP, which are commonly supported by SSDs via CAM.</p>
 
       <p>In order to increase the supported hardware base, CAM's SCSI
 	layer was also enhanced to allow ATA TRIM via SATL ATA
 	Passthrough to be used in addition to the existing UNMAP and WS
 	methods.  This allows SATA disks attached to SCSI controllers
 	with CAM based drivers such as <tt>mps(4)</tt> and
 	<tt>mpt(4)</tt> to provide delete support.</p>
 
       <p>Stats for ZFS TRIM can be monitored by looking at the sysctl
 	variables under <tt>kstat.zfs.misc.zio_trim</tt> in addition to
 	live GEOM delete stats via the <tt>gstat -d</tt> command.</p>
 
       <p>This project was sponsored by <a
 	  href="http://www.multiplay.com">Multiplay</a> and implemented by
 	Pawel Jakub Dawidek.</p>
     </body>
   </project>
+
+  <project cat='arch'>
+    <title>Superpages for ARMv7</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Zbigniew</given>
+	  <common>Bodek</common>
+	</name>
+	<email>zbb@semihalf.com</email>
+      </person>
+
+      <person>
+	<name>
+	  <given>Grzegorz</given>
+	  <common>Bernacki</common>
+	</name>
+	<email>gjb@semihalf.com</email>
+      </person>
+
+      <person>
+	<name>
+	  <given>Rafal</given>
+	  <common>Jaworowski</common>
+	</name>
+	<email>raj@semihalf.com</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf"/>
+      <url href="https://wiki.freebsd.org/ARMSuperpages"/>
+      <url href="https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git"/>
+    </links>
+
+    <body>
+      <p>The ARM architecture is more and more prevalent, not only in
+	the mobile and embedded space.  Among the more interesting
+	industry trends emerging in the recent months, there has been
+	the concept of "ARM server".  Some top-tier companies, e.g.
+	Dell and HP, have already started to develop such systems.</p>
+
+      <p>Key to success of &os; in these new areas is dealing with the
+	sophisticated features of the platform, for example adding
+	support for superpages.</p>
+
+      <p>The objective of this project is to enable &os;/arm to utilize
+	superpages which would allow efficient use of TLB translations
+	(by enlarging TLB coverage), leading to improved performance in
+	many applications and scalability.  This is intended to work on
+	ARMv7-based processors, however compatibility with ARMv6 will be
+	preserved.</p>
+
+      <p>The following steps have been made since the last status
+	report:</p>
+
+      <ul>
+	<li>Implement <tt>pmap_copy()</tt> to support <tt>fork()</tt>
+	  system calls.</li>
+	<li>Support for multiple page sizes.</li>
+	<li>Implement superpage creation, promotion, demotion, and
+	  eviction mechanisms.</li>
+	<li>Implement PV entry management for superpages.</li>
+	<li>Partially integrate code to the <tt>head</tt> branch.</li>
+      </ul>
+
+      <p>Next steps:</p>
+
+      <ul>
+	<li>Test and benchmark.</li>
+	<li>Complete integration into &os; <tt>head</tt>.</li>
+      </ul>
+
+      <p>This project is jointly sponsored by The &os; Foundation and
+	Semihalf sp.j.</p>
+    </body>
+
+    <help>
+      <task>Start utilizing superpages on ARMv6/v7.</task>
+      <task>Find bugs and debug.</task>
+    </help>
+  </project>
+
+  <project cat='proj'>
+    <title>LLDB Debugger Port</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Ed</given>
+	  <common>Maste</common>
+	</name>
+	<email>emaste@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://wiki.freebsd.org/lldb"/>
+    </links>
+
+    <body>
+      <p>LLDB is the the debugger project in the LLVM family.  It
+	supports the Mac OS X, Linux, and &os; platforms, but the latter
+	has recently suffered under a lack of maintenance.</p>
+
+      <p>After cleaning bit rot in LLDB's &os; support, it again builds
+	and can be used for basic debugging of single-threaded
+	applications.  The test suite also runs to completion, although
+	it experiences a large number of failures.</p>
+
+      <p>Ed Maste has been granted an LLDB commit bit, and is now
+	committing ongoing bug fixes and development directly to the
+	upstream repository.  There is a significant amount of work
+	still to be done, with one goal being the incorporation of
+	<tt>lldb</tt> into the base system.</p>
+
+      <p>This project is sponsored by DARPA/AFRL in collaboration with
+	SRI International and the University of Cambridge.</p>
+    </body>
+
+    <help>
+      <task>Add support for multithreaded processes.</task>
+      <task>Fix watchpoints.</task>
+      <task>Add support for remote debuging (<tt>gdbserver</tt> /
+	<tt>debugserver</tt>).</task>
+      <task>Add support for core files.</task>
+      <task>Add support for kernel debugging.</task>
+      <task>Verify i386 and ARM architectures.</task>
+      <task>Implement MIPS target support.</task>
+      <task>Verify cross-debugging.</task>
+      <task>Investigate and fix test suite failures.</task>
+      <task>Prepare <tt>lldb</tt> for incorporation into the base
+	system.</task>
+    </help>
+  </project>
 </report>
diff --git a/en_US.ISO8859-1/htdocs/ports/references.xml b/en_US.ISO8859-1/htdocs/ports/references.xml
index b83128734a..bd97b9e91f 100644
--- a/en_US.ISO8859-1/htdocs/ports/references.xml
+++ b/en_US.ISO8859-1/htdocs/ports/references.xml
@@ -1,93 +1,93 @@
 <?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/doc/share/xml/xhtml10-freebsd.dtd" [
 <!ENTITY title 'FreeBSD Ports -- References'>
 <!ENTITY % ports.ent SYSTEM "ports.ent">
 %ports.ent;
 <!ENTITY email 'ports'>
 %statistics.ent;
 ]>
 <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.ports">
 
 &searchform;
 
 <hr/>
 
 <p>To start learning more about ports and packages, see
   <a href="&base;/doc/en_US.ISO8859-1/books/handbook/ports.html">
   Installing Applications: Packages and Ports</a>, a section of the
   <a href="&base;/doc/en_US.ISO8859-1/books/handbook/index.html">
   FreeBSD Handbook</a>.
 </p>
 
 <p>The
   <a href="&base;/doc/en_US.ISO8859-1/books/porters-handbook/index.html">
   Porter's Handbook</a> is the master reference for both creating new
   ports and maintaining existing ports, including a section on
   <a href="&base;/doc/en_US.ISO8859-1/books/porters-handbook/keeping-up.html">
   Keeping Up</a>.  It also contains more detail about the topics below, as
   well as more references for further study.
 </p>
 
 <p>You may also find the following to be useful:</p>
 
 <ul>
   <li>The archives of the
     <a href="http://docs.FreeBSD.org/mail/current/freebsd-ports.html">
     FreeBSD ports mailing list</a>.
   </li>
 
   <li>The article
     <a href="&base;/doc/en_US.ISO8859-1/articles/contributing-ports/index.html">
     Contributing to the FreeBSD Ports Collection</a>.
   </li>
 
   <li>
     <a href="http://www.FreshPorts.org">FreshPorts.org</a> is a
     valuable tool for further information about individual ports,
     such as current version, last checkin, and many other useful
     statistics.  You may subscribe to a mailing list to get the
     latest information about your favorite ports.
   </li>
 <!--
  <li>Here is a graph of the
    <a href="growth/status.png">rapid rate of growth</a>
    of the Ports Collection.</li>
 -->
 
   <li>The manual pages for
     <a href="&base;/cgi/man.cgi?query=ftp"><tt>ftp</tt></a>,
     <a href="&base;/cgi/man.cgi?query=pkg_add"><tt>pkg_add</tt></a>, and
     <a href="&base;/cgi/man.cgi?query=ports"><tt>ports</tt></a>.
   </li>
 
   <li>The
     <a href="http://pointyhat.FreeBSD.org">ports and packages build cluster</a>.
   </li>
 
   <li>The
     <a href="&base;/portmgr/">Ports Management Team</a> (portmgr) pages.
   </li>
 
   <li>The
-    <a href="http://cvsweb.FreeBSD.org">
+    <a href="http://svnweb.FreeBSD.org">
     Web Interface to the Source Repository</a>
     allows you to browse the files in the source repository.  Changes
     that affect the entire port system are now documented in the
-    <a href="http://cvsweb.FreeBSD.org/ports/CHANGES">CHANGES</a> file.
+    <a href="http://svnweb.FreeBSD.org/ports/head/CHANGES?view=markup">CHANGES</a> file.
     Changes that affect individual ports are now documented in the
-    <a href="http://cvsweb.FreeBSD.org/ports/UPDATING">UPDATING</a> file.
+    <a href="http://svnweb.FreeBSD.org/ports/head/UPDATING?view=markup">UPDATING</a> file.
     However, the definitive answer to any question is undoubtedly to read
-    the source code of <a href="http://cvsweb.FreeBSD.org/ports/Mk/bsd.port.mk">
+    the source code of <a href="http://svnweb.FreeBSD.org/ports/head/Mk/bsd.port.mk?view=markup">
     bsd.port.mk</a>, and associated files.
   </li>
 </ul>
 
 </body>
 </html>
diff --git a/es_ES.ISO8859-1/books/handbook/disks/chapter.xml b/es_ES.ISO8859-1/books/handbook/disks/chapter.xml
index 37a0547506..c2809bf416 100644
--- a/es_ES.ISO8859-1/books/handbook/disks/chapter.xml
+++ b/es_ES.ISO8859-1/books/handbook/disks/chapter.xml
@@ -1,4211 +1,4205 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!--
      The FreeBSD Documentation Project
 
      The FreeBSD Spanish Documentation Project
 
      %SOURCE% en_US.ISO8859-1/books/handbook/disks/chapter.xml
      %SRCID%    0.0
 
      $FreeBSD$
 -->
 
 <chapter id="disks">
   <title>Almacenamiento</title>
 
   <sect1 id="disks-synopsis">
     <title>Sinopsis</title>
 
 
     <para>Este capítulo trata sobre el uso de discos en &os;.
       Esto incluye discos basados en memoria, discos conectados
       a través de la red, dispositivos de almacenamiento SCSI/IDE
       estándar y dispositivos que utilizan el interfaz
       USB.</para>
 
     <para>Tras leer este capítulo:</para>
     <itemizedlist>
       <listitem><para>Conocerá la terminología que se usa en
         &os; para describir la organización de datos en un disco
         físico (particiones y porciones).</para>
       </listitem>
       <listitem><para>Sabrá cómo añadir discos duros
         a su sistema.</para>
       </listitem>
       <listitem>
         <para>Sabrá cómo configurar &os; para utilizar
           dispositivos de almacenamiento USB.</para>
       </listitem>
       <listitem><para>Sabrá cómo configurar sistemas virtuales
         de ficheros, como los discos de memoria.
         </para></listitem>
       <listitem>
         <para>Sabrá cómo usar cuotas para limitar el uso del
           espacio en disco.</para>
       </listitem>
       <listitem>
         <para>Sabrá cómo cifrar discos para hacerlos más
           seguros ante un atacante.</para>
       </listitem>
       <listitem>
         <para>Sabrá cómo se crean y graban los CD y DVD en
           &os;.</para>
       </listitem>
       <listitem>
         <para>Conocerá diversas opciones de almacenamiento de copias
           de seguridad.</para>
       </listitem>
       <listitem>
         <para>Sabrá cómo usar diversos programas de respaldo
           que pueden utilizarse en &os;.</para>
       </listitem>
       <listitem>
         <para>Sabrá cómo hacer copias de seguridad utilizando
           disquetes (floppy).</para>
       </listitem>
       <listitem>
         <para>Sabrá en qué consiste una instantánea
           (<quote>snapshot</quote>) y cómo utilizarla
           de forma eficiente.</para>
       </listitem>
     </itemizedlist>
 
     <para>Antes de leer este capítulo:</para>
 
     <itemizedlist>
       <listitem>
         <para>Debe saber cómo configurar e instalar un nuevo kernel
           en &os; (<xref linkend="kernelconfig"/>).</para>
       </listitem>
     </itemizedlist>
 
   </sect1>
 
   <sect1 id="disks-naming">
     <title>Nombres de dispositivo</title>
 
     <para>A continuación le mostraremos una lista de dispositivos
       de físicos almacenamiento soportados por &os;
       y los nombres de dispositivo asociados con ellos.</para>
 
     <table id="disk-naming-physical-table" frame="none">
       <title>Convenciones para nombrar discos físicos</title>
 
       <tgroup cols="2">
 	<thead>
 	  <row>
 	    <entry>Tipo de unidad</entry>
 	    <entry>Nombre de dispositivo de la unidad</entry>
 	  </row>
 	</thead>
 	<tbody>
 	  <row>
 	    <entry>Discos duros IDE</entry>
 	    <entry><literal>ad</literal></entry>
 	  </row>
 	  <row>
 	    <entry>Unidades CDROM IDE</entry>
 	    <entry><literal>acd</literal></entry>
 	  </row>
 	  <row>
 	    <entry>Discos duros SCSI y dispositivos de almacenamiento masivo
               USB</entry>
 	    <entry><literal>da</literal></entry>
 	  </row>
 	  <row>
 	    <entry>Unidades CDROM SCSI</entry>
 	    <entry><literal>cd</literal></entry>
 	  </row>
 	  <row>
 	    <entry>Diferentes tipos de unidades CDROM no estándares</entry>
 	    <entry><literal>mcd</literal> para CD-ROM Mitsumi,
 	      <literal>scd</literal> para CD-ROM Sony,
 	      <literal>matcd</literal> para CD-ROM Matsushita/Panasonic
-		<footnote>
-                  <para>El controlador &man.matcd.4; ha sido eliminado
-                    de la rama FreeBSD&nbsp;4.X el 5 de octubre
-                    de 2002 y no existe en FreeBSD&nbsp;5.0 y
-                    versiones posteriores.</para>
-		</footnote>
 	    </entry>
 	  </row>
 	  <row>
 	    <entry>Unidades de disquete (floppy)</entry>
 	    <entry><literal>fd</literal></entry>
 	  </row>
 	  <row>
 	    <entry>Unidades de cinta SCSI</entry>
 	    <entry><literal>sa</literal></entry>
             </row>
 	  <row>
 	    <entry>Unidades de cinta IDE</entry>
 	    <entry><literal>ast</literal></entry>
 	  </row>
 	  <row>
 	    <entry>Unidades Flash</entry>
 	    <entry><literal>fla</literal> para dispositivos &diskonchip;</entry>
 	  </row>
 	  <row>
 	    <entry>Unidades RAID</entry>
 	    <entry><literal>aacd</literal> para &adaptec; AdvancedRAID,
 	      <literal>mlxd</literal> y <literal>mlyd</literal>
 	      para &mylex;,
 	      <literal>amrd</literal> para AMI &megaraid;,
 	      <literal>idad</literal> para Compaq Smart RAID,
 	      <literal>twed</literal> para &tm.3ware; RAID.</entry>
 	  </row>
 	</tbody>
       </tgroup>
     </table>
   </sect1>
 
   <sect1 id="disks-adding">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>David</firstname>
 	  <surname>O'Brien</surname>
 	  <contrib>Texto original de </contrib>
 	</author>
       </authorgroup>
       <!-- 26 Apr 1998 -->
     </sect1info>
 
     <title>Añadir discos</title>
 
     <indexterm>
       <primary>discos</primary>
       <secondary>añadir</secondary>
     </indexterm>
 
     <para>Digamos que queremos añadir un nuevo disco SCSI a una
       máquina que solo tiene un disco.  Comience por apagar el
       sistema e instale el disco siguiendo las instrucciones del fabricante
       de la computadora, del disco y de la controladora.  Debido a la gran
       variedad de procedimientos posibles los detalles están más
       allá del alcance de este texto.</para>
 
     <para>Entre como usuario <username>root</username>.  Una vez instalado el
       disco inspeccione <filename>/var/run/dmesg.boot</filename>
       para asegurarse de que el sistema encontró el nuevo disco.
       Continuando con nuestro ejemplo, el disco recién añadido
       será
       <devicename>da1</devicename> y queremos montarlo en
       <filename>/1</filename> (si está añadiendo un disco IDE,
       el nombre de dispositivo será
       <devicename>wd1</devicename> en sistemas anteriores a 4.0, y
       <devicename>ad1</devicename> en sistemas 4.X y 5.X).</para>
 
     <indexterm><primary>particiones</primary></indexterm>
     <indexterm><primary>slices</primary></indexterm>
     <indexterm>
       <primary><command>fdisk</command></primary>
     </indexterm>
 
     <para>&os; funciona en computadoras IBM-PC y compatibles, por lo tanto
       tendrá en cuenta las particiones de la BIOS del PC, que son
       diferentes del tipo de partición que se ha venido usando en
       BSD.  Un disco para PC puede contener hasta cuatro entradas de
       particiones BIOS.  Si el disco va a utilizarse íntegramente
       con &os; puede usar el modo
       <emphasis>dedicado</emphasis>.  Si no, &os; tendrá que
       instalarse dentro de una las particiones BIOS.  En &os; se llama
       slices (<quote>porciones</quote> o <quote>rebanadas</quote>) a las
       particiones de PC BIOS para no confundirlas con las particiones BSD.
       También puede utilizar slices en un disco dedicado a
       &os; pero que se está usando en un sistema que también
       tiene otro sistema operativo instalado.
       Esta es una buena manera de evitar confundir la versión de
       <command>fdisk</command> de otros sistemas operativos.</para>
 
     <para>Desde el punto de vista de las slices el disco se
       añadirá como <filename>/dev/da1s1e</filename>.
       Se interpreta del siguiente modo: disco SCSI, unidad
       número 1 (segundo disco SCSI), slice 1 (partición 1
       de PC BIOS), y partición BSD <filename>e</filename>.
       Si es un disco dedicado, el disco se añadirá como
       <filename>/dev/da1e</filename>.</para>
 
 
     <para>Debido al uso de enteros de 32-bits para almacenar el número
       de sectores, &man.bsdlabel.8; (llamado &man.disklabel.8; en
       &os;&nbsp;4.X) está limitado a 2^32-1 sectores por disco
       ó 2TB (en la mayoría de los casos).  El formato de
       &man.fdisk.8; permite un sector de arranque de un máximo de
       más de 2^32-1 y no más de 2^32-1 de longitud, limitando
       las particiones a 2TB y los discos a 4TB (también en
       la mayoría de los casos).  El formato &man.sunlabel.8; tiene
       una limitación de 2^32-1 sectores por partición y 8
       particiones en un espacio máximo de 16TB.  Si va a usar discos
       mayores puede usar particiones &man.gpt.8;.</para>
 
     <sect2>
       <title>Uso de &man.sysinstall.8;</title>
       <indexterm>
         <primary><application>sysinstall</application></primary>
         <secondary>añadir discos</secondary>
       </indexterm>
       <indexterm>
 	<primary>su</primary>
       </indexterm>
       <procedure>
 	<step>
 	  <title>Navegar en <application>Sysinstall</application></title>
 
 
           <para>Puede utilizar <command>sysinstall</command>
             (<command>/stand/sysinstall</command> en versiones de &os;
             anteriores a 5.2) para particionar y etiquetar un
             disco nuevo usando sus intuitivos menús.
             Entre como el usuario <username>root</username> o utilice
             <command>su</command>.  Ejecute
             <command>sysinstall</command> y entre al menú
             <literal>Configure</literal>.  Dentro de
             <literal>FreeBSD Configuration Menu</literal>, descienda
             y seleccione la opción <literal>Fdisk</literal>.</para>
 	</step>
 
 	<step>
 	  <title>Editor de particiones <application>fdisk</application></title>
 
           <para>Una vez dentro de <application>fdisk</application>,
             teclée <userinput>A</userinput> si quiere usar el
             disco entero con &os;  Cuando se le pregunte
             <quote>remain cooperative with any future
             possible operating systems</quote>
             <footnote><para>
             Mantener el disco accesible a sistemas operativos que pudieran
             necesitar acceder al mismo en algún momento.
             </para></footnote>, responda <literal>YES</literal>.
             Escriba los cambios al disco pulsando <userinput>W</userinput>.
             Salga del editor FDISK pulsando <userinput>q</userinput>.
             A continuación se le preguntará sobre el
             <quote>Master Boot Record</quote>.  Debido a que está
             añadiendo un nuevo disco a un sistema que ya está
             instalado, tendrá que seleccionar
             <literal>None</literal>.</para>
 	</step>
 
 	<step>
 	  <title>Editor de etiquetas de disco</title>
 
 	  <indexterm><primary>particiones BSD</primary></indexterm>
 
           <para>A continuación, debe salir de
             <application>sysinstall</application> e iniciarlo de nuevo.
             Siga las instrucciones arriba expuestas, pero esta vez elija la
             opción <literal>Label</literal>.  De este modo
             accederá al
             <literal>editor de etiquetas de disco</literal>.
             En él  creará las particiones BSD
             tradicionales.  Un disco puede tener hasta ocho particiones,
             etiquetadas desde la <literal>a</literal> a la
             <literal>h</literal>.
             Algunas de las etiquetas de las particiones tienen
             usos especiales.  La partición <literal>a</literal>
             se utiliza para la partición raíz
             (<filename>/</filename>), por lo tanto sólo su disco
             de sistema (esto es, el disco desde el cual arranca)
             tendrá una partición <literal>a</literal>.
             La partición <literal>b</literal> se usa como
             partición swap; puede tener más de una
             partición swap y puede alojarlas en más de un
             disco.  La partición <literal>c</literal>
             hace referencia al disco entero en modo dedicado, o a
             la slice de &os; completa en modo slice.  Las demás
             particiones son para el resto de los usos típicos.</para>
 
           <para>El editor de etiquetas de
             <application>sysinstall</application>
             creará la partición <literal>e</literal> como
             partición <quote>ni raíz, ni swap</quote>.
             En el editor de etiquetas crée un solo sistema de
             ficheros tecleando <userinput>C</userinput>.  Cuando se
             le pregunte si debe etiquetarse como FS (sistema de ficheros) o
             swap, elija <literal>FS</literal> y teclée un punto de
             montaje (por ejemplo <filename>/mnt</filename>).  Al
             añadir un disco en modo
             <quote>post-instalación</quote>
             <application>sysinstall</application> no creará
             automáticamente las entradas correspondientes en
             <filename>/etc/fstab</filename>, por lo que el punto de
             montaje que usted especifique no tiene importancia.</para>
 
           <para>Ahora puede escribir la nueva etiqueta al disco y
             crear un sistema de ficheros en él tecleando
             <userinput>W</userinput>.  Ignore cualquier error que
             pudiera generar <application>sysinstall</application> acerca
             de dificultades para montar la nueva partición.  Salga del
             editor de etiquetas y de <application>sysinstall</application>.
             </para>
 	</step>
 
 	<step>
 	  <title>Terminar</title>
 
           <para>El último paso es editar
             <filename>/etc/fstab</filename>
             y añadir una entrada para su nuevo disco.</para>
 	</step>
       </procedure>
     </sect2>
 
     <sect2>
       <title>Uso de utilidades de línea de comandos</title>
 
       <sect3>
 	<title>Uso de slices</title>
 
         <para>Esta configuración le permitirá a su
           disco convivir sin sobresaltos con otro sistema operativo
           que pueda estar instalado en su sistema y no
           confundirá a las utilidades <command>fdisk</command> de
           esos otros sistemas operativos.  Se recomienda utilizar este
           método para instalar discos nuevos.
           <emphasis>Utilice el modo dedicado sólamente si tiene
           un buen motivo para hacerlo</emphasis>.</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
 &prompt.root; <userinput>fdisk -BI da1</userinput> #Initialice el nuevo disco.
 &prompt.root; <userinput>disklabel -B -w -r da1s1 auto</userinput> #Etiquételo.
 &prompt.root; <userinput>disklabel -e da1s1</userinput> # Edite la etiqueta de disco que acaba de crear y añada particiones.
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>newfs /dev/da1s1e</userinput> # Repita este paso por cada partición que crée.
 &prompt.root; <userinput>mount /dev/da1s1e /1</userinput> # Monte la partición o particiones.
 &prompt.root; <userinput>vi /etc/fstab</userinput> # Añada la/s entrada/s apropiadas en <filename>/etc/fstab</filename>.</screen>
 
         <para>Si tiene un disco IDE, sustituya <filename>ad</filename>
           por <filename>da</filename>.  En sistemas anteriores a 4.X
           utilice <filename>wd</filename>.</para>
       </sect3>
 
       <sect3>
 	<title>Dedicado</title>
 	<indexterm><primary>OS/2</primary></indexterm>
 
         <para>Si no va a compartir el nuevo disco con otro sistema
           operativo puede utilizar el modo <literal>dedicado</literal>.
           Recuerde que este modo puede confundir a los sistemas operativos
           de Microsoft, aunque no podrán dañar por ello el
           disco o su contenido.  Tenga en cuenta que &os; (de IBM)
           se <quote>apropiará</quote> de cualquier partición
           que encuentre y no entienda.</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
 &prompt.root; <userinput>disklabel -Brw da1 auto</userinput>
 &prompt.root; <userinput>disklabel -e da1</userinput>				# crear partición `e'
 &prompt.root; <userinput>newfs -d0 /dev/da1e</userinput>
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>vi /etc/fstab</userinput>				# agregar una entrada para /dev/da1e
 &prompt.root; <userinput>mount /1</userinput></screen>
 
         <para>Una forma alternativa de hacerlo sería:</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 count=2</userinput>
 &prompt.root; <userinput>disklabel /dev/da1 | disklabel -BrR da1 /dev/stdin</userinput>
 &prompt.root; <userinput>newfs /dev/da1e</userinput>
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>vi /etc/fstab</userinput>					# añadir una entrada para /dev/da1e
 &prompt.root; <userinput>mount /1</userinput></screen>
 
         <note><para>A partir de &os;&nbsp;5.1-RELEASE, la utilidad
           &man.bsdlabel.8; reemplazó al antiguo programa
           &man.disklabel.8;.  En &man.bsdlabel.8; se han eliminado muchos
           parámetros y opciones obsoletas;
           en los ejemplos de arriba la opción <option>-r</option>
           debe eliminarse si se usa &man.bsdlabel.8;.  Para más
           información diríjase al manual
           de &man.bsdlabel.8;.</para></note>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="raid">
     <title>RAID</title>
 
     <sect2 id="raid-soft">
       <title>Software RAID</title>
 
       <sect3 id="ccd">
 	<sect3info>
 	  <authorgroup>
 	    <author>
 	      <firstname>Christopher</firstname>
 	      <surname>Shumway</surname>
 	      <contrib>Texto original de </contrib>
 	    </author>
 	  </authorgroup>
 	  <authorgroup>
 	    <author>
 	      <firstname>Jim</firstname>
 	      <surname>Brown</surname>
 	      <contrib>Revisado por </contrib>
 	    </author>
 	  </authorgroup>
 	</sect3info>
 
 	<title>Configuración de controlador de disco
 	  concatenado (CCD)</title>
 
 <indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
 <indexterm>
   <primary>RAID</primary><secondary>CCD</secondary>
 </indexterm>
 
         <para>Al escoger una solución de almacenamiento masivo
           los factores más importantes a considerar son velocidad,
           fiabilidad y coste.  Es raro tener los tres por igual;
           normalmente un dispositivo de almacenamiento masivo veloz y
           fiable es caro, y para recortar los costes suele sacrificarse
           la velocidad o la fiabilidad.</para>
 
         <para>Al diseñar el sistema descrito más adelante se
           eligió el coste como el factor más importante,
           seguido de la velocidad, y luego la fiabilidad.
           La velocidad de transferencia de datos para este sistema está,
           en última instancia, limitada por la red.  Y mientras que la
           confiabilidad es muy importante, el controlador CCD descrito
           más adelante sirve datos que están respaldados
           en CD-R y pueden ser reemplazados sin dificultad.</para>
 
         <para>Al escoger una solución de almacenamiento masivo el
           primer paso es definir sus necesidades.  Si prefiere velocidad o
           fiabilidad por encima del coste, el resultado será
           distinto del que vamos a describir en esta sección.
           </para>
 
 
 	<sect4 id="ccd-installhw">
 	  <title>Instalación del hardware</title>
 
           <para>Además del disco IDE, el núcleo del
             disco CCD está compuesto por tres discos IDE
             discos IDE Western Digital de 30GB y 5400 RPM, que
             ofrecen aproximadamente 90GB de almacenamiento.
             Lo ideal sería que cada disco IDE tuviera
             su propio cable y controlador, pero para minimizar
             costes no se utilizaron controladores IDE adicionales.
             En lugar de eso se configuraron los discos
             con <quote>jumpers</quote> para que cada controlador IDE
             tuviera un maestro y un esclavo.</para>
 
           <para>Despues de reiniciar la BIOS se configuró
             para que detectara automáticamente los discos
             conectados.
             &os; los detectó al reiniciar:</para>
 
 	  <programlisting>ad0: 19574MB &lt;WDC WD205BA&gt; [39770/16/63] at ata0-master UDMA33
 ad1: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata0-slave UDMA33
 ad2: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-master UDMA33
 ad3: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-slave UDMA33</programlisting>
 
           <note><para>Si &os; no detecta todos los discos
             asegúrese de que ha colocado correctamente los
             <quote>jumpers</quote>.  La mayoría de los discos IDE
             tienen  un <quote>jumper</quote> <quote>Cable Select</quote>.
             Este <emphasis>no</emphasis> es el
             <quote>jumper</quote> que define la relación
             maestro/esclavo.  Consulte la documentación
             del disco para identificar el <quote>jumper</quote>
             correcto.</para></note>
 
           <para>El siguiente paso es estudiar cómo conectarlos
             para que formen parte del sistema de ficheros.  Investigue
             Debe investigar &man.vinum.8;
             (<xref linkend="vinum-vinum"/>) y &man.ccd.4;. Nosotros
             elegimos &man.ccd.4; para nuestra
             configuración.</para>
 	</sect4>
 
 	<sect4 id="ccd-setup">
 	  <title>Configuración de CCD</title>
 
           <para>El controlador &man.ccd.4; le permite tomar
             varios discos idénticos y concatenarlos
             en un solo sistema lógico de ficheros.
             Para poder usar &man.ccd.4; necesita un
             kernel compilado con soporte de &man.ccd.4;.
             Añada esta línea al fichero de
             configuración de su kernel, recompile y
             reinstale su kernel:</para>
 
 	  <programlisting>pseudo-device   ccd     4</programlisting>
 
           <para>En sistemas 5.X, use la siguiente línea:</para>
 
 	  <programlisting>device   ccd</programlisting>
 
           <note><para>En FreeBSD&nbsp;5.X no es necesario especificar
             un número de dispositivos &man.ccd.4;, ya que el controlador
             de dispositivo &man.ccd.4; es capaz de clonarse a sí
             mismo (se crearán nuevas instancias de dispositivo
             automáticamente según vayan haciendo falta).
             </para></note>
 
           <para>El soporte de &man.ccd.4; también puede
             cargarse como módulo en &os; 3.0 y
             posteriores.</para>
 
           <para>Para configurar &man.ccd.4; tendrá que
             usar &man.disklabel.8; para etiquetar los
             discos:</para>
 
 	  <programlisting>disklabel -r -w ad1 auto
 disklabel -r -w ad2 auto
 disklabel -r -w ad3 auto</programlisting>
 
           <para>Esto crea una etiqueta de disco para
             <devicename>ad1c</devicename>,
             <devicename>ad2c</devicename> y
             <devicename>ad3c</devicename> que abarcan
             el disco completo.</para>
 
         <note><para>A partir de &os;&nbsp;5.1-RELEASE
           &man.bsdlabel.8; reemplazó al antiguo programa
           &man.disklabel.8;.  En &man.bsdlabel.8; se eliminaron muchas
           opciones y parámetros obsoletos;
           en los ejemplos de arriba la opción <option>-r</option>
           deben obviarse.  Para más información consulte
           &man.bsdlabel.8;.</para></note>
 
           <para>El siguiente paso es cambiar el tipo de etiqueta
             de disco.  Edite los discos con &man.disklabel.8;:
             </para>
 
 	  <programlisting>disklabel -e ad1
 disklabel -e ad2
 disklabel -e ad3</programlisting>
 
           <para>Esto abre la etiqueta de disco de cada disco
             con el editor declarado en la variable de
             entorno <envar>EDITOR</envar>, por defecto &man.vi.1;.</para>
 
           <para>Esta es una etiqueta de disco sin modificar:</para>
 
 	  <programlisting>8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)</programlisting>
 
           <para>&man.ccd.4; necesita que añada una nueva
             partición <literal>e</literal>.  Puede copiarla desde la
             partición <literal>c</literal>, pero el tipo de sistema de
             ficheros (la opción <option>fstype</option>) debe ser
             <userinput>4.2BSD</userinput>.  La etiqueta del disco
             debería tener este aspecto:</para>
 
 	  <programlisting>8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)
   e: 60074784        0    4.2BSD        0     0     0   # (Cyl.    0 - 59597)</programlisting>
 
 	</sect4>
 
 	<sect4 id="ccd-buildingfs">
 	  <title>Contrucción del sistema de ficheros</title>
 
             <para>Puede que todavía no exista el
               nodo de dispositivo para <devicename>ccd0c</devicename>.
               Si es así, ejecute lo siguiente:
               </para>
 
 	  <programlisting>cd /dev
 sh MAKEDEV ccd0</programlisting>
 
           <note><para>En FreeBSD 5.0 &man.devfs.5; administrará
             automáticamente los nodos de dispositivos en
             <filename>/dev</filename>, así que no tendrá que
             usar <command>MAKEDEV</command>.</para></note>
 
           <para>Una vez etiquetados todos los discos construya
             el &man.ccd.4;. Utilice
             &man.ccdconfig.8; con opciones similares a las siguientes:</para>
 
 	    <programlisting>ccdconfig ccd0<co id="co-ccd-dev"/> 32<co id="co-ccd-interleave"/> 0<co id="co-ccd-flags"/> /dev/ad1e<co id="co-ccd-devs"/> /dev/ad2e /dev/ad3e</programlisting>
 
           <para>El uso y el significado de cada una de las opciones se
             muestra más abajo:</para>
 
           <calloutlist>
             <callout arearefs="co-ccd-dev">
             <para>El primer argumento es el dispositivo a configurar, en este
               caso <filename>/dev/ccd0c</filename>.  La parte
               <filename>/dev/</filename> es opcional.</para>
             </callout>
 
             <callout arearefs="co-ccd-interleave">
 
             <para>El intervalo para el sistema de ficheros.  El intervalo
               define el tamaño de una banda en bloques de disco,
               normalmente 512 bytes.  Por lo tanto, un intervalo
               de 32 equivaldría 16.384 bytes.</para>
             </callout>
 
             <callout arearefs="co-ccd-flags">
             <para>Banderas para &man.ccdconfig.8;. Si desea disponer
               sus discos en espejo use aquí una bandera.
               Esta configuración no necesita discos en espejo,
               por lo que está dispuesta a 0 (cero).</para>
             </callout>
 
             <callout arearefs="co-ccd-devs">
             <para>Los últimos argumentos de &man.ccdconfig.8;
               son los dispositivos a colocar en el array.  Utilice
               la ruta completa para cada dispositivo.</para>
             </callout>
           </calloutlist>
 
 
           <para>Despues de ejecutar &man.ccdconfig.8; el &man.ccd.4;
             estará configurado y podrá instalar un sistema
             de ficheros.  Consulte las opciones de &man.newfs.8; y
             ejecute:</para>
 
 	  <programlisting>newfs /dev/ccd0c</programlisting>
 
 
 	</sect4>
 
 	<sect4 id="ccd-auto">
 	  <title>Automatización</title>
 
           <para>Seguramente querrá que
             &man.ccd.4; esté dispuesto tras cada reinicio.  Para
             ello, debe configurarlo.  Guarde su configuración
             en <filename>/etc/ccd.conf</filename> mediante lo
             siguiente:</para>
 
 	  <programlisting>ccdconfig -g &gt; /etc/ccd.conf</programlisting>
 
           <para>Durante el reinicio, el <quote>script</quote>
             <command>/etc/rc</command>
             ejecuta <command>ccdconfig -C</command> si encuentra
             el fichero <filename>/etc/ccd.conf</filename>.  De este modo
             &man.ccd.4; queda configurado automáticamente para que
             pueda montarse.</para>
 
           <note><para>Si ha arrancando en modo mono usuario necesita
             ejecutar el siguiente comando antes de que pueda montar
             el &man.ccd.4; para configurar el array:</para>
 
 	  <programlisting>ccdconfig -C</programlisting>
           </note>
 
           <para>Para montar automaticamente el &man.ccd.4;
             coloque una entrada para &man.ccd.4; en
             <filename>/etc/fstab</filename> para que se monte
             durante el arranque:</para>
 
 	  <programlisting>/dev/ccd0c              /media       ufs     rw      2       2</programlisting>
 	</sect4>
       </sect3>
 
       <sect3 id="vinum">
 	<title>El administrador de volúmenes Vinum</title>
 
 <indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
 <indexterm>
   <primary>RAID</primary>
   <secondary>Vinum</secondary>
 </indexterm>
 
         <para>El administrador de volúmenes Vinum es un
           controlador de dispositivos de bloque que implementa
           unidades de disco virtuales.  Aísla los discos hardware de
           la interfaz de dispositivos de bloque y mapea datos de
           modo que revierta en un incremento de flexibilidad,
           rendimiento y fiabilidad comparados con el sistema de slices
           de almacenamiento de disco tradicional.
           &man.vinum.8; implementa los modelos RAID-0, RAID-1 y
           RAID-5, individualmente o combinados.</para>
 
 	<para>Consulte el <xref linkend="vinum-vinum"/> para mayor
           información sobre &man.vinum.8;.</para>
       </sect3>
     </sect2>
 
     <sect2 id="raid-hard">
       <title>RAID por Hardware</title>
 
       <indexterm>
 	<primary>RAID</primary>
 	<secondary>hardware</secondary>
       </indexterm>
 
       <para>FreeBSD admite una gran variedad de controladores
         <acronym>RAID</acronym> por hardware.  Estos dispositivos
         controlan un subsistema <acronym>RAID</acronym> sin necesidad
         de software específico para &os; que administre el
         array.</para>
 
       <para>Puede controlar la mayoría de las operaciones de disco con
         una tarjeta que incorpore <acronym>BIOS</acronym>.
         El siguiente texto es una breve
         descripción de configuración utilizando una
         controladora Promise <acronym>RAID</acronym> <acronym>IDE</acronym>.
         Cuando se instala esta tarjeta e inicia el sistema despliega
         un <quote>prompt</quote> pidiendo información.  Siga las
         instrucciones para entrar a la pantalla de configuración de la
         tarjeta.  Ahí tendrá posibilidad de combinar todos los
         discos que haya conectado.  Hecho esto el disco (o discos)
         aparecerán como una sola unidad en &os;.  Pueden configurarse
         otros niveles de
         <acronym>RAID</acronym>.</para>
     </sect2>
 
     <sect2>
       <title>Reconstrucción de arrays ATA RAID1</title>
 
       <para>&os; le permite reemplazar en caliente un disco dañado.
         Esto requiere que lo intercepte antes de reiniciar.</para>
 
       <para>Probablemente vea algo como lo siguiente en
         <filename>/var/log/messages</filename> o en la salida de
         &man.dmesg.8;:</para>
 
       <programlisting>ad6 on monster1 suffered a hard error.
 ad6: READ command timeout tag=0 serv=0 - resetting
 ad6: trying fallback to PIO mode
 ata3: resetting devices .. done
 ad6: hard error reading fsbn 1116119 of 0-7 (ad6 bn 1116119; cn 1107 tn 4 sn 11)\\
 status=59 error=40
 ar0: WARNING - mirror lost</programlisting>
 
       <para>Consulte &man.atacontrol.8; para más
         información:</para>
 
       <screen>&prompt.root; <userinput>atacontrol list</userinput>
 ATA channel 0:
 	Master:      no device present
 	Slave:   acd0 &lt;HL-DT-ST CD-ROM GCR-8520B/1.00&gt; ATA/ATAPI rev 0
 
 ATA channel 1:
 	Master:      no device present
 	Slave:       no device present
 
 ATA channel 2:
 	Master:  ad4 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
 	Slave:       no device present
 
 ATA channel 3:
 	Master:  ad6 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
 	Slave:       no device present
 
 &prompt.root; <userinput>atacontrol status ar0</userinput>
 ar0: ATA RAID1 subdisks: ad4 ad6 status: DEGRADED</screen>
 
       <procedure>
 	<step>
           <para>Primero debe desconectar el disco del array para
             que pueda retirarlo con seguridad:</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol detach 3</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Reemplace el disco.</para>
 	</step>
 
 	<step>
 	  <para>Conecte el disco de repuesto:</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol attach 3</userinput>
 Master:  ad6 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
 Slave:   no device present</screen>
 	</step>
 
 	<step>
 	  <para>Reconstruya el array:</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol rebuild ar0</userinput></screen>
 	</step>
 
 	<step>
 
           <para>El comando de reconstrucción no responderá hasta
             que termine la tarea.  Puede abrir otra terminal (mediante
             <keycombo action="simul"><keycap>Alt</keycap> <keycap>F<replaceable>n</replaceable></keycap></keycombo>)
             y revisar el progreso ejecutando lo siguiente:</para>
 
 	  <screen>&prompt.root; <userinput>dmesg | tail -10</userinput>
 [texto eliminado]
 ad6: removed from configuration
 ad6: deleted from ar0 disk1
 ad6: inserted into ar0 disk1 as spare
 
 &prompt.root; <userinput>atacontrol status ar0</userinput>
 ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed</screen>
 	</step>
 
 	<step>
           <para>Espere hasta que termine la operación.</para>
 	</step>
       </procedure>
     </sect2>
   </sect1>
 
   <sect1 id="usb-disks">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Texto de </contrib>
 	</author>
       </authorgroup>
       <!-- Jul 2004 -->
     </sect1info>
 
     <title>Dispositivos de almacenamiento USB</title>
     <indexterm>
       <primary>USB</primary>
       <secondary>discos</secondary>
     </indexterm>
 
     <para>Hoy día hay una enorme cantidad de soluciones de
       almacenamiento externoque usan el bus serie universal (USB):
       discos duros, <quote>mecheros</quote> (o
       <quote>lápices</quote>) USB, grabadoras de
       CD-R, etc. &os; puede usar estos dispositivos.</para>
 
     <sect2>
       <title>Configuración</title>
 
       <para>El controlador de dispositivos de almacenamiento masivo
         USB, &man.umass.4;, ofrece soporte para dispositivos de
         almacenamiento USB.  Si usa el kernel <filename>GENERIC</filename>
         no necesita cambiar nada en su configuración.  Si
         utiliza un kernel personalizado asegúrese de que su
         fichero de configuración del kernel contiene las
         siguientes líneas:</para>
 
       <programlisting>device scbus
 device da
 device pass
 device uhci
 device ohci
 device usb
 device umass</programlisting>
 
       <para>El controlador &man.umass.4; usa el subsistema SCSI para
         acceder a los dispositivos de almacenamiento USB y su
         dispositivo USB aparecerá en el sistema como
         dispositivo SCSI.  Dependiendo del chipset USB de su
         placa base sólamente necesitará
         <literal>device uhci</literal> o
         <literal>device ohci</literal>;  en cualquier caso tener
         los dos en el fichero de configuración del kernel
         no provocará ningún daño.  No olvide
         compilar e instalar el nuevo kernel si hizo alguna
         modificación.</para>
 
       <note>
         <para>Si su dispositivo USB es una grabadora CD-R o DVD el
           controlador SCSI CD-ROM, &man.cd.4;, debe ser añadirse al
           kernel mediante la siguiente línea:</para>
 
 	<programlisting>device cd</programlisting>
 
         <para>Dado que la grabadora aparece como una unidad
           SCSI no tiene que usar el controlador &man.atapicam.4;
           en la configuración del kernel.</para>
       </note>
 
       <para>En &os;&nbsp;5.X y en la rama 4.X desde &os;&nbsp;4.10-RELEASE
         el soporte para controladores USB 2.0 se incorpora al sistema del
         siguiente modo:</para>
 
       <programlisting>device ehci</programlisting>
 
       <para>Tenga en cuenta que &man.uhci.4; y
         &man.ohci.4; siguen siendo necesarios si quiere disponer de
         soporte para USB 1.X.</para>
 
       <note>
         <para>En &os;&nbsp;4.X, El d&aelig;mon USB (&man.usbd.8;) debe
           ejecutarse para poder ver ciertos tipos de dispositivo USB.
           Para habilitarlo, añada
           <literal>usbd_enable="YES"</literal> en
           <filename>/etc/rc.conf</filename> y reinicie la
           máquina.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Prueba de la configuración</title>
 
       <para>La configuración está lista para probarse:
         conecte su dispositivo USB; en el búfer de mensajes del
         sistema (&man.dmesg.8;), la unidad debe aparecer como algo
         similar a esto:</para>
 
       <screen>umass0: USB Solid state disk, rev 1.10/1.00, addr 2
 GEOM: create disk da0 dp=0xc2d74850
 da0 at umass-sim0 bus 0 target 0 lun 0
 da0: &lt;Generic Traveling Disk 1.11&gt; Removable Direct Access SCSI-2 device
 da0: 1.000MB/s transfers
 da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C)</screen>
 
       <para>Obviamente la marca, el nodo de dispositivo
         (<devicename>da0</devicename>) y otros detalles
         pueden diferir dependiendo de su hardware.</para>
 
       <para>Ya que el dispositivo USB aparece como uno SCSI,
         puede usar <command>camcontrol</command> para ver una lista
         de dispositivos USB conectados al
         sistema:</para>
 
       <screen>&prompt.root; <userinput>camcontrol devlist</userinput>
 &lt;Generic Traveling Disk 1.11&gt;      at scbus0 target 0 lun 0 (da0,pass0)</screen>
 
       <para>Si la unidad tiene un sistema de ficheros puede montarla.
         La <xref linkend="disks-adding"/> contiene información que
         le resultará muy útil para formatear y crear
         particiones en el disco USB en caso de necesitarlo.</para>
 
       <para>Si desconecta el dispositivo (el disco debe desmontarse
         previamente), debería ver en el búfer de mensajes
         del sistema algo parecido a esto:</para>
 
       <screen>umass0: at uhub0 port 1 (addr 2) disconnected
 (da0:umass-sim0:0:0:0): lost device
 (da0:umass-sim0:0:0:0): removing device entry
 GEOM: destroy disk da0 dp=0xc2d74850
 umass0: detached</screen>
     </sect2>
 
     <sect2>
       <title>Lecturas recomendadas</title>
 
       <para>Ademas de las secciones
         <link linkend="disks-adding">Cómo añadir discos</link>
         y <link linkend="mount-unmount">Montado y desmontado de sistemas
         ficheros</link>, consulte las siguientes páginas man:
         &man.umass.4;, &man.camcontrol.8; y
         &man.usbdevs.8;.</para>
     </sect2>
   </sect1>
 
   <sect1 id="creating-cds">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Mike</firstname>
 	  <surname>Meyer</surname>
 	  <contrib>Texto de </contrib>
 	  <!-- mwm@mired.org -->
 	</author>
       </authorgroup>
       <!-- Apr 2001 -->
     </sect1info>
 
     <title>Creación y uso de medios ópticos (CD)</title>
     <indexterm>
       <primary>CDROM</primary>
       <secondary>creación</secondary>
     </indexterm>
 
     <sect2>
       <title>Introducción</title>
 
       <para>Los CD tienen muchas opciones que los hacen distintos de
         los discos convencionales.  Al principio los usuarios no
         podían escribirlos.  Su diseño permite que leamos
         en ellos sin el retardo del movimiento de una cabeza lectora
         de una pista a otra.
         También son mucho más fáciles de transportar
         de un sistema a otro que muchos otros soportes de
         información.</para>
 
       <para>Los CD tienen pistas, pero son una sección de los
         que permiten lectura contínua, no una propiedad
         física del disco.  Para crear un CD en &os; debe
         preparar los ficheros de datos que van a constituir las pistas
         del CD y luego escribir las pistas al CD.</para>
 
       <indexterm><primary>ISO 9660</primary></indexterm>
       <indexterm>
         <primary>sistema de ficheros</primary>
         <secondary>ISO 9660</secondary>
       </indexterm>
       <para>El sistema de ficheros ISO 9660 se diseñó
         para gestionar estas diferencias.  Por desgracia implementa
         límites de sistema de ficheros que eran comunes en la
         época en que se diseñó.
         Por suerte también proporciona un mecanismo de extensiones
         que permite que CD escritos excediendo dichos límites
         funcionen en sistemas que no soportan esas extensiones.</para>
 
       <indexterm>
         <primary><filename role="package">sysutils/cdrtools</filename></primary>
       </indexterm>
       <para>El port <filename role="package">sysutils/cdrtools</filename>
         incluye &man.mkisofs.8;, un programa que le permitirá
         crear un fichero de datos que contenga un sistema de
         ficheros ISO 9660.  Incorpora opciones que soportan varias
         extensiones.  Se describe más adelante.</para>
 
       <indexterm>
         <primary>grabadora de CD</primary>
         <secondary>ATAPI</secondary>
       </indexterm>
       <para>Qué herramienta usar para grabar el CD depende de si
         su grabadora es ATAPI o no.  Las grabadoras de CD ATAPI usan el
         programa <command><link linkend="burncd">burncd</link></command>,
         que forma parte del sistema base.  Las grabadoras SCSI y USB usan
         <command><link linkend="cdrecord">cdrecord</link></command>, del
         port <filename role="package">sysutils/cdrtools</filename>.</para>
 
       <para><command>burncd</command> no soporta cualquier unidad de
         grabación.  Para saber si una unidad está
         soportada consulte la siguiente lista de
         <ulink url="http://www.freebsd.dk/ata/">unidades CD-R/RW soportadas</ulink>.</para>
 
       <note>
       <indexterm>
 	<primary>grabadora de CD</primary>
 	<secondary>controlador ATAPI/CAM</secondary>
       </indexterm>
         <para>Si utiliza &os;&nbsp;5.X, &os;&nbsp;4.8-RELEASE
           o posteriores, puede utilizar
           <command><link linkend="cdrecord">cdrecord</link></command> y
           otras herramientas para unidades SCSI en hardware ATAPI con
           el <link linkend="atapicam">módulo ATAPI/CAM</link>.</para>
       </note>
 
       <para>Si quiere usar un interfaz gráfico con su software
         de grabación de CD quizás le guste
         <application>X-CD-Roast</application> o
         <application>K3b</application>.  Puede instalar estas herramientas
         como paquetes o desde los ports
         <filename role="package">sysutils/xcdroast</filename> y
         <filename role="package">sysutils/k3b</filename>, respectivamente.
         <application>X-CD-Roast</application> y
         <application>K3b</application> requieren el
         <link linkend="atapicam">módulo ATAPI/CAM</link>
         si usa hardware ATAPI.</para>
     </sect2>
 
     <sect2 id="mkisofs">
       <title>mkisofs</title>
 
       <para>El programa &man.mkisofs.8; (que forma parte del
         port <filename role="package">sysutils/cdrtools</filename>)
         genera un sistema de ficheros ISO 9660 que es una imagen
         de un árbol de directorios en el espacio de nombres
         del sistema de ficheros &unix;.  Esta es la forma más simple
         de usarlo:</para>
 
       <screen>&prompt.root; <userinput>mkisofs -o <replaceable>ficherodeimagen.iso</replaceable> <replaceable>/ruta/del/árbol</replaceable></userinput></screen>
 
       <indexterm>
         <primary>sistemas de ficheros</primary>
         <secondary>ISO 9660</secondary>
       </indexterm>
       <para>Este comando creará un
         <replaceable>ficherodeimagen.iso</replaceable>
         que contenga un sistema de ficheros ISO 9660 que es una copia del
         árbol ubicado en
         <replaceable>/ruta/al/árbol</replaceable>. En el
         proceso, mapeará los nombres de fichero a nombres que
         se ajusten a las limitaciones del estándar del sistema
         de ficheros ISO 9660, y excluirá ficheros que posean
         nombres no característicos de sistemas de ficheros
         ISO.</para>
 
       <indexterm>
         <primary>sistemas de ficheros</primary>
         <secondary>HFS</secondary>
       </indexterm>
       <indexterm>
         <primary>sistemas de ficheros</primary>
         <secondary>Joliet</secondary>
       </indexterm>
 
       <para>Existe gran cantidad de opciones que permiten superar
         esas restricciones.  En particular, <option>-R</option>
         habilita las extensiones Rock Ridge comunes para sistemas
         &unix;, <option>-J</option> habilita las extensiones Joliet
         usadas por sistemas Microsoft y <option>-hfs</option> puede
         usarse para crear sistemas de ficheros utilizados por
         &macos;.</para>
 
       <para>Puede utilizar <option>-U</option> para deshabilitar
         todas las restricciones de nombres de fichero si quiere crear un
         CD que se vaya a usar exclusivamente en sistemas &os;.  Cuando se
         usa con <option>-R</option> produce una imagen de sistema
         de ficheros que es idéntica al árbol &os;
         origen, aunque puede violar el estándar ISO 9660
         de múltiples formas.</para>
 
       <indexterm>
         <primary>CDROMs</primary>
         <secondary>creación cd CD arrancables</secondary>
       </indexterm>
       <para>La última opción de uso general es
         <option>-b</option>.  Se usa para configurar la ubicación
         de la imagen de arranque que se usará al crear un CD
         arrancable <quote>El Torito</quote>.
         Esta opción usa como argumento la ruta a la imagen de
         arranque desde la raíz del árbol de directorios que
         se va a escribir en el CD.  Por defecto &man.mkisofs.8;
         crea una imagen ISO en un modo llamado <quote>de emulación
         de disquete (floppy)</quote>, y por lo tanto espera que
         la imagen de arranque sea exactamente de 1.200, 1.440 o
         2880&nbsp;KB de tamaño.  Algunos cargadores de arranque,
         como el que se usa en los discos de la distribución &os;,
         no utilizan modo de emulación: se usa la opción
         <option>-no-emul-boot</option>.  Por tanto, si
         <filename>/tmp/miarranque</filename> tiene un sistema &os;
         arrancable con la imagen de arranque en
         <filename>/tmp/miarranque/boot/cdboot</filename> podría
         crear la imagen en un sistema de ficheros ISO 9660 en
         <filename>/tmp/arrancable.iso</filename> de la siguiente manera:</para>
 
       <screen>&prompt.root; <userinput>mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/arrancable.iso /tmp/miarranque</userinput></screen>
 
       <para>Hecho esto, si tiene <devicename>vn</devicename>
         (FreeBSD&nbsp;4.X), o <devicename>md</devicename>
         (FreeBSD&nbsp;5.X)
         configurado en su kernel, puede montar el sistema de
         ficheros del siguiente modo:</para>
 
       <screen>&prompt.root; <userinput>vnconfig -e vn0c /tmp/arrancable.iso</userinput>
 &prompt.root; <userinput>mount -t cd9660 /dev/vn0c /mnt</userinput></screen>
 
       <para>En FreeBSD&nbsp;4.X y FreeBSD&nbsp;5.X proceda del siguiente
         modo:</para>
 
       <screen>&prompt.root; <userinput>mdconfig -a -t vnode -f /tmp/arrancable.iso -u 0</userinput>
 &prompt.root; <userinput>mount -t cd9660 /dev/md0 /mnt</userinput></screen>
 
       <para>Ahora puede verificar que <filename>/mnt</filename>
         y <filename>/tmp/miarranque</filename> sean idénticos.</para>
 
       <para>Existen muchas otras opciones que puede usar para depurar el
         comportamiento de &man.mkisofs.8;, sobre todo en lo que se refiere
         al esquema ISO 9660 y la creación de discos Joliet y HFS.
         Consulte el manual de &man.mkisofs.8;.</para>
     </sect2>
 
     <sect2 id="burncd">
       <title>burncd</title>
       <indexterm>
         <primary>CDROM</primary>
         <secondary>grabar</secondary>
       </indexterm>
       <para>Si tiene una grabadora ATAPI puede usar
         <command>burncd</command> para grabar una imagen ISO en un
         CD.  <command>burncd</command> forma parte del sistema base, y
         está en <filename>/usr/sbin/burncd</filename>.  Su uso
         es muy sencillo, ya que tiene pocas opciones:</para>
 
       <screen>&prompt.root; <userinput>burncd -f <replaceable>unidaddecd</replaceable> data <replaceable>ficheroimagen.iso</replaceable> fixate</userinput></screen>
 
       <para>Esto grabará una copia de <replaceable>ficheroimagen.iso</replaceable>
         en <replaceable>unidadcd</replaceable>.  El dispositivo por
         defecto es <filename>/dev/acd0</filename>
         (o <filename>/dev/acd0c</filename> en &os;&nbsp;4.X).
         Consulte &man.burncd.8; para ver las opciones de configuración
         de velocidad de escritura, expulsión de CD una vez grabado, y
         escritura de datos de audio.</para>
     </sect2>
 
     <sect2 id="cdrecord">
       <title>cdrecord</title>
 
       <para>Si no dispone de una grabadora ATAPI de CD, tendrá que
         usar <command>cdrecord</command> para grabar sus CD.
         <command>cdrecord</command> no forma parte del sistema
         base; instálelo  desde el port
         <filename role="package">sysutils/cdrtools</filename> o
         como paquete.  Los cambios en el sistema base pueden
         hacer que las versiones binarias del programa fallen.
         Tendrá que actualizar el port cuando actualice su sistema
         o, si está
         <link linkend="stable">siguiendo la rama -STABLE</link>,
         actualizar el port cuando haya una nueva versión
         disponible.</para>
 
       <para>Aunque <command>cdrecord</command> tiene muchas opciones, el
         uso básico es incluso más simple que
         el de <command>burncd</command>.  Así se graba una imagen
         ISO 9660:</para>
 
       <screen>&prompt.root; <userinput>cdrecord dev=<replaceable>dispositivo</replaceable> <replaceable>ficheroimagen.iso</replaceable></userinput></screen>
 
       <para>La parte complicada de utilizar <command>cdrecord</command> es
         encontrar qué <option>dev</option> usar.  Utilice la
         bandera <option>-scanbus</option> para dar con la
         configuración apropiada.  La salida será parecida a
         la siguiente:</para>
       <indexterm>
         <primary>CDROMs</primary>
         <secondary>grabar</secondary>
       </indexterm>
       <screen>&prompt.root; <userinput>cdrecord -scanbus</userinput>
 Cdrecord 1.9 (i386-unknown-freebsd4.2) Copyright (C) 1995-2000 J&ouml;rg Schilling
 Using libscg version 'schily-0.1'
 scsibus0:
         0,0,0     0) 'SEAGATE ' 'ST39236LW       ' '0004' Disk
         0,1,0     1) 'SEAGATE ' 'ST39173W        ' '5958' Disk
         0,2,0     2) *
         0,3,0     3) 'iomega  ' 'jaz 1GB         ' 'J.86' Removable Disk
         0,4,0     4) 'NEC     ' 'CD-ROM DRIVE:466' '1.26' Removable CD-ROM
         0,5,0     5) *
         0,6,0     6) *
         0,7,0     7) *
 scsibus1:
         1,0,0   100) *
         1,1,0   101) *
         1,2,0   102) *
         1,3,0   103) *
         1,4,0   104) *
         1,5,0   105) 'YAMAHA  ' 'CRW4260         ' '1.0q' Removable CD-ROM
         1,6,0   106) 'ARTEC   ' 'AM12S           ' '1.06' Scanner
         1,7,0   107) *</screen>
 
       <para>Esta lista muestra los valores <option>dev</option> apropiados para
         los dispositivos de la lista.  Localice su grabadora de CD y
         utilice los tres números separados por comas como valor
         para <option>dev</option>.  En este caso, el dispositivo CDW
         es 1,5,0 y por tanto la entrada apropiada sería
         <option>dev=1,5,0</option>.  Hay modos más
         fáciles de especificar este valor; consulte &man.cdrecord.1;
         para más detalles.  También es el lugar donde buscar
         información sobre la escritura de pistas de audio,
         controlar la velocidad de escritura y muchas más cosas.</para>
     </sect2>
 
     <sect2 id="duplicating-audiocds">
       <title>Copiar CD de audio</title>
 
       <para>Puede duplicar un CD de audio extrayendo los datos de audio del
         CD a ficheros y escribir estos ficheros en un CD virgen.
         El proceso es ligeramente diferente en unidades ATAPI y
         SCSI.</para>
 
       <procedure>
 	<title>Unidades SCSI</title>
 
 	<step>
           <para>Use <command>cdda2wav</command> para extraer el audio.</para>
 
 	  <screen>&prompt.user; <userinput>cdda2wav -v255 -D2,0 -B -Owav</userinput></screen>
 	</step>
 
 	<step>
           <para>Use <command>cdrecord</command> para escribir
             los ficheros <filename>.wav</filename>.</para>
 
 	  <screen>&prompt.user; <userinput>cdrecord -v dev=<replaceable>2,0</replaceable> -dao -useinfo  *.wav</userinput></screen>
 
           <para>Asegúrese de que <replaceable>2,0</replaceable>
             este configurado apropiadamente, como se describe en la
             <xref linkend="cdrecord"/>.</para>
 	</step>
       </procedure>
 
       <procedure>
 	<title>Unidades ATAPI</title>
 
 	<step>
           <para>El controlador de CD ATAPI hace que cada pista sea
             accesible como
             <filename>/dev/acd<replaceable>d</replaceable>t<replaceable>nn</replaceable></filename>,
             donde <replaceable>d</replaceable> es el número
             de unidad y <replaceable>nn</replaceable> es el
             número de pista expresado con dos dígitos
             decimales, precedido por un cero si es necesario.
             La primera pista del primer disco es
             <filename>/dev/acd0t01</filename>, la segunda es
             <filename>/dev/acd0t02</filename>, la tercera es
             <filename>/dev/acd0t03</filename> y así
             sucesivamente.</para>
 
           <para>Asegúrese de que existen los ficheros apropiados
             en <filename>/dev</filename>.</para>
 
 	  <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV acd0t99</userinput></screen>
 
           <note><para>En FreeBSD 5.0 &man.devfs.5; creará
             y gestionará automáticamente las entradas
             necesarias en <filename>/dev</filename>, así que
             no será necesario usar
             <command>MAKEDEV</command>.</para></note>
 	</step>
 
 	<step>
           <para>Extraer cada pista con &man.dd.1;.  También
             deberá declarar un tamaño específico de
             bloque al extraer los ficheros.</para>
 
 	  <screen>&prompt.root; <userinput>dd if=/dev/acd0t01 of=pista1.cdr bs=2352</userinput>
 &prompt.root; <userinput>dd if=/dev/acd0t02 of=pista2.cdr bs=2352</userinput>
 ...
 </screen>
 	</step>
 
 	<step>
           <para>Grabar los ficheros extraídos a disco con
             <command>burncd</command>.  Debe declarar que son
             ficheros de audio y que <command>burncd</command> debe cerrar
             (<quote>fixate</quote>) el disco al terminar la
             grabación.</para>
 
 	  <screen>&prompt.root; <userinput>burncd -f <replaceable>/dev/acd0</replaceable> audio pista1.cdr pista2.cdr <replaceable>...</replaceable> fixate</userinput></screen>
 	</step>
       </procedure>
     </sect2>
 
     <sect2 id="imaging-cd">
       <title>Duplicar CDs de datos</title>
 
       <para>Puede copiar un CD de datos a un fichero de
         imagen que será funcionalmente equivalente al fichero
         de imagen creado con &man.mkisofs.8;, y puede usarlo
         para duplicar cualquier CD de datos.  El ejemplo dado
         aquí asume que su dispositivo CDROM es
         <devicename>acd0</devicename>.  Sustitúyalo por el
         dispositivo CDROM correcto para su configuración.
         Bajo &os;&nbsp;4.X, se debe añadir una
         <literal>c</literal> al final del nombre del dispositivo para
         indicar la partición entera o, en el caso de los CDROM,
         el disco entero.</para>
 
       <screen>&prompt.root; <userinput>dd if=/dev/acd0 of=fichero.iso bs=2048</userinput></screen>
 
       <para>Hecha la imagen puede garbarla en un CD como se
         describió anteriormente.</para>
     </sect2>
 
     <sect2 id="mounting-cd">
       <title>Uso de CD de datos</title>
 
       <para>Ahora que ha creado un CDROM de datos estándar
         tal vez quiera montarlo y leer los datos que contiene.  Por
         defecto &man.mount.8; asume que los sistemas de ficheros
         son de tipo <literal>ufs</literal>.  Si trata de
         hacer algo como</para>
 
       <screen>&prompt.root; <userinput>mount /dev/cd0 /mnt</userinput></screen>
 
       <para>recibirá un error como este:
         <errorname>Incorrect super block</errorname> y no se
         montará.  Un CDROM no es un sistema de ficheros
         <literal>UFS</literal> así que los intentos de montarlo
         como tal fallarán. Tendrá que decirle a &man.mount.8;
         que el sistema de ficheros es de tipo <literal>ISO9660</literal>
         y funcionará.  Puede hacerlo mediante la
         opción <option>-t cd9660</option>.
         Por ejemplo, si quiere montar el dispositivo CDROM
         <filename>/dev/cd0</filename>  en
         <filename>/mnt</filename> ejecute:</para>
 
           <screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen>
 
       <para>Tenga en cuenta que el nombre de su dispositivo
         (<filename>/dev/cd0</filename> en este ejemplo) puede
         ser diferente, dependiendo de la interfaz que su CDROM
         utilice.  Además la opción <option>-t cd9660</option>
         sólo ejecuta &man.mount.cd9660.8;.  El ejemplo de arriba
         puede resumirse del siguiente modo:</para>
 
 <screen>&prompt.root; <userinput>mount_cd9660 /dev/cd0 /mnt</userinput></screen>
 
       <para>En general puede usar CDROM de datos de cualquier
         fabricante, aunque los discos con ciertas extensiones
         ISO 9660 pueden mostrar un comportamiento extraño.
         Por ejemplo, los discos Joliet almacenan todos los nombres
         de fichero en caracteres unicode de dos-bytes.  El kernel
         de &os; no comprende unicode
         (<emphasis>todavía</emphasis>) así que
         los caracteres que no están en inglés aparecen
         como signos de interrogación.  (Si utiliza &os; 4.3
         o alguna versión posterior, el controlador CD9660 incluye
         unas estructuras llamadas <quote>ganchos</quote>, que le
         permitirán cargar una tabla de conversión unicode
         apropiada cuando haga falta.  Hay módulos para algunas
         de las codificaciones más comunes en el port
         <filename role="package">sysutils/cd9660_unicode</filename>.)</para>
 
       <para>Es posible que reciba un error <errorname>Device not
         configured</errorname> al tratar de montar un CDROM.
         Generalmente esto significa que la unidad de CDROM piensa que no
         hay disco en la bandeja, o que la unidad no es visible
         en el bus.  Puede llevar un par de segundos el que una
         unidad de CDROM se dé cuenta de que ha sido alimentada,
         por lo tanto sea paciente.</para>
 
       <para>Algunas veces un CDROM SCSI puede <quote>perdido</quote> debido
         a que no tuvo tiempo suficiente para responder al reset del
         bus.  Si tiene un CDROM SCSI añada la siguiente opción
         a su fichero de  configuración del kernel y
         <link linkend="kernelconfig-building">recompile su kernel</link>.</para>
 
       <programlisting>options SCSI_DELAY=15000</programlisting>
 
       <para>Esto le indica a su bus SCSI que haga una pausa de 15
         segundos durante el arranque para darle ocasión
         a su unidad de CDROM de responder al reset del bus.</para>
     </sect2>
 
     <sect2 id="rawdata-cd">
       <title>Grabar CD de datos <quote>crudos</quote> (Raw)</title>
 
       <para>Puede guardar un fichero directamente a CD
         sin crear un sistema de ficheros ISO 9660.  Algunas
         personas hacen esto al crear respaldos.  Es un proceso
         más rápido que grabar un CD
         estándar:</para>
 
       <screen>&prompt.root; <userinput>burncd -f /dev/acd1 -s 12 data fichero.tar.gz fixate</userinput></screen>
 
       <para>Para recuperar los datos guardardados de este modo en un CD,
         debe leer los datos desde el nodo de dispositivo
         <quote>crudo</quote>:</para>
 
       <screen>&prompt.root; <userinput>tar xzvf /dev/acd1</userinput></screen>
 
       <para>No puede montar este disco como lo haría con un
         CDROM normal.  Estos CDROM no pueden leerse en ningún
         sistema operativo que no sea &os;.  Si quiere montar el CD
         o compartir los datos con otro sistema operativo debe utilizar
         &man.mkisofs.8; como se describió previamente.</para>
     </sect2>
 
     <sect2 id="atapicam">
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Marc</firstname>
 	    <surname>Fonvieille</surname>
 	    <contrib>Original de </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
 
       <title>Uso del controlador ATAPI/CAM</title>
 
       <indexterm>
 	<primary>Grabadora de CD</primary>
 	<secondary>controlador ATAPI/CAM</secondary>
       </indexterm>
 
       <para>Este controlador permite que dispositivos ATAPI
         (CD-ROM, CD-RW, unidades DVD, etc) sean accesibles  a través
         del subsistema SCSI y por lo tanto permite el uso de
         aplicaciones como
         <filename role="package">sysutils/cdrdao</filename> o
 	&man.cdrecord.1;.</para>
 
       <para>Para usar este controlador necesitará añadir
         la siguiente línea al fichero de configuración
         de su kernel:</para>
 
       <programlisting>device atapicam</programlisting>
 
       <para>Es posible que necesite también las siguientes
         líneas en el fichero de configuración
         de su kernel:</para>
 
       <programlisting>device ata
 device scbus
 device cd
 device pass</programlisting>
 
       <para>(que, por otra parte, ya deberín estar presentes).</para>
 
       <para>Recompile, instale su nuevo kernel y reinicie
         su máquina.  Durante el proceso de arranque su
         grabadora debe ser detectada; veamos un ejemplo:</para>
 
       <screen>acd0: CD-RW &lt;MATSHITA CD-RW/DVD-ROM UJDA740&gt; at ata1-master PIO4
 cd0 at ata1 bus 0 target 0 lun 0
 cd0: &lt;MATSHITA CDRW/DVD UJDA740 1.00&gt; Removable CD-ROM SCSI-0 device
 cd0: 16.000MB/s transfers
 cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed</screen>
 
       <para>Puede acceder a la unidad a través del
         del nombre de dispositivo <filename>/dev/cd0</filename>;
         por ejemplo, para montar un CDROM en <filename>/mnt</filename>,
         teclée lo siguiente:</para>
 
       <screen>&prompt.root; <userinput>mount -t cd9660 <replaceable>/dev/cd0</replaceable> /mnt</userinput></screen>
 
       <para>Como <username>root</username>, puede ejecutar el
         siguiente comando para obtener las direcciones SCSI
         del dispositivo:</para>
 
       <screen>&prompt.root; <userinput>camcontrol devlist</userinput>
 &lt;MATSHITA CDRW/DVD UJDA740 1.00&gt;   at scbus1 target 0 lun 0 (pass0,cd0)</screen>
 
       <para>Según esto, <literal>1,0,0</literal> será la
         dirección SCSI a utilizar con &man.cdrecord.1;
         y otras aplicaciones SCSI.</para>
 
       <para>Para mayor información sobre sistemas
         ATAPI/CAM y SCSI, diríjase a las páginas
         de manual &man.atapicam.4; y &man.cam.4;.</para>
     </sect2>
   </sect1>
 
   <sect1 id="creating-dvds">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Texto de </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Andy</firstname>
 	  <surname>Polyakov</surname>
 	  <contrib>Con colaboraciones de </contrib>
 	</author>
       </authorgroup>
       <!-- Feb 2004 -->
     </sect1info>
 
     <title>Crear y utilizar medios ópticos (DVDs)</title>
     <indexterm>
       <primary>DVD</primary>
       <secondary>grabar</secondary>
     </indexterm>
 
     <sect2>
       <title>Introducción</title>
 
       <para>Comparado con el CD, el DVD es la nueva generación
         de tecnología de almacenamiento en medios ópticos.
         El DVD puede almacenar más datos que cualquier CD y
         hoy día es el estándar para publicación
         de vídeo.</para>
 
       <para>Se pueden definir cinco formatos de grabación para
         lo que llamamos un DVD grabable:</para>
 
       <itemizedlist>
 	<listitem>
           <para>DVD-R: Este fué el primer formato de grabación
             de DVD.  El DVD-R estándar fué definido por el
             <ulink url="http://www.dvdforum.com/forum.shtml">DVD Forum</ulink>.
             Este formato es de una sola escritura.</para>
 	</listitem>
 
 	<listitem>
           <para>DVD-RW: Esta es la versión reescribible
             del DVD-R estándar.  Un DVD-RW puede reescribirse
             unas 1.000 veces.</para>
 	</listitem>
 
 	<listitem>
           <para>DVD-RAM: Este es también un formato
             reescribible soportado por el DVD Forum.  Un
             DVD-RAM puede verse como un disco duro extraíble.
             Este medio no es compatible con la
             mayoría de las unidades DVD-ROM y reproductores
             de video DVD; hay muy pocas grabadoras de DVD que soporten
             el formato DVD-RAM.</para>
 	</listitem>
 
 	<listitem>
           <para>DVD+RW: Este es un formato reescribible definido
             por la
             <ulink url="http://www.dvdrw.com/">DVD+RW Alliance</ulink>.
             Un DVD+RW puede reescribirse unas 1000 veces.</para>
 	</listitem>
 
 	<listitem>
           <para>DVD+R: Este un formato es la versión
             de una sola escritura del formato DVD+RW.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Un DVD grabable de una capa puede almacenar hasta
         4.700.000.000&nbsp;bytes, es decir, 4'38&nbsp;GB o
         4485&nbsp;MB (1 kilobyte son 1.024 bytes).</para>
 
       <note>
         <para>Debemos hacer una distinción entre medio físico
           y aplicación.  Un DVD de vídeo es una estructura
           de fichero específica que puede escribirse en cualquier
           medio físico consistente en un DVD grabable: DVD-R, DVD+R,
           DVD-RW, etc.  Antes de elegir el tipo de medio, debe
           asegurarse que la grabadora y el reproductor de DVD de
           vídeo (un reproductor independiente o una unidad DVD-ROM
           en una computadora) son compatibles con el medio que
           pretende utilizar.</para></note>
     </sect2>
 
     <sect2>
       <title>Configuración</title>
 
       <para>Utilice &man.growisofs.1; para grabar el DVD.  Forma parte
         de las herramientas <application>dvd+rw-tools</application>
         (<filename role="package">sysutils/dvd+rw-tools</filename>).
         Las <application>dvd+rw-tools</application> permiten usar todos
         los tipos de DVD.</para>
 
       <para>Estas herramientas utilizan el subsistema SCSI para
         acceder a los dispositivos, por lo tanto el
         <link linkend="atapicam">soporte ATAPI/CAM</link> debe estar
         presente en su kernel.  Si su grabadora usa el interfaz
         USB no tendrá que hacerlo, pero tendrá que leer
         la
         <xref linkend="usb-disks"/> para más información sobre
         la configuración de dispositivos USB.</para>
 
       <para>También debe que habilitar el acceso DMA para
         dispositivos ATAPI. Para ello añada la siguiente
         línea a
         <filename>/boot/loader.conf</filename>:</para>
 
       <programlisting>hw.ata.atapi_dma="1"</programlisting>
 
       <para>Antes de intentar utilizar
         <application>dvd+rw-tools</application> debe consultar las
         <ulink url="http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html">notas
         de compatibilidad de hardware de dvd+rw-tools</ulink> por si
         apareciera cualquier información relacionada con su
         grabadora de DVD.</para>
 
       <note>
         <para>Si desea un interfaz gráfico debería
           echar un vistazo a <application>K3b</application>
           (<filename role="package">sysutils/k3b</filename>),  que ofrece
           un interfaz de usuario amigable para &man.growisofs.1;
           y muchas otras herramientas de grabación.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Quemado de DVD de datos</title>
 
       <para>&man.growisofs.1; es un <quote>frontend</quote> de
         <link linkend="mkisofs">mkisofs</link>, invocará
         a &man.mkisofs.8; para crear una estructura de sistema de
         ficheros y realizará la escritura del DVD.
         Esto significa que no necesita crear una imagen de los
         datos antes del proceso de escritura.</para>
 
       <para>La grabación en DVD+R o DVD-R de los datos del
         directorio <filename class="directory">/ruta/a/los/datos</filename>,
         se hace del siguiente modo:</para>
 
       <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/ruta/a/los/datos</replaceable></userinput></screen>
 
       <para>Las opciones <option>-J -R</option> se suministran a
         &man.mkisofs.8; para la creación del sistema de
         ficheros (en este caso: un sistema de ficheros ISO 9660
         con extensiones Joliet y Rock Ridge).  Consulte la
         página de manual &man.mkisofs.8; para más
         detalles.</para>
 
       <para>La opción <option>-Z</option> se usa
         la sesión inicial de grabación en todos los casos,
         sesiones múltiples o no. El dispositivo DVD del
         ejemplo,
         <replaceable>/dev/cd0</replaceable>, debe ajustarse de
         acuerdo a la configuración de su sistema.  El parámero
         <option>-dvd-compat</option> cerrar&acute; el disco (no
         se podrá añadir nada a la grabación).
         Por contra, esto le brindará una mejor compatibilidad del
         medio con unidades DVD-ROM.</para>
 
       <para>También es posible grabar una imagen pre-masterizada,
         por ejemplo para guardar la imagen
         <replaceable>ficheroimagen.iso</replaceable>:</para>
 
       <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z <replaceable>/dev/cd0</replaceable>=<replaceable>ficheroimagen.iso</replaceable></userinput></screen>
 
       <para>La velocidad de escritura se detecta y configura
         automáticamente según el medio y la unidad que
         se esté utilizando.  Si quiere forzar la velocidad de
         escritura utilice el
         parámetro <option>-speed=</option>.  Para más
         información consulte la página de manual
         &man.growisofs.1;.</para>
     </sect2>
 
     <sect2>
       <title>Grabación de un DVD de vídeo</title>
 
       <indexterm>
 	<primary>DVD</primary>
 	<secondary>DVD-Video</secondary>
       </indexterm>
 
       <para>Un DVD de vídeo es una estructura de ficheros
         específica basada en las especificiones ISO 9660 y
         micro-UDF (M-UDF).  El DVD de vídeo también
         dispone de una jerarquía de estructura de datos
         específica; por esta razón es necesario un
         programa especializado para crear tal DVD:
         <filename role="package">multimedia/dvdauthor</filename>.
         </para>
 
       <para>Si ya tiene una imagen de un sistema de ficheros de DVD
         de vídeo grábelo de la misma manera que cualquier
         otra imagen; consulte la sección previa para ver un
         ejemplo.  Si ha creado el DVD y el resultado está en,
         por ejemplo, el directorio
         <filename class="directory">/ruta/al/vídeo</filename>, use
         el siguiente comando para grabar el DVD de vídeo:</para>
 
       <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -dvd-video <replaceable>/ruta/al/vídeo</replaceable></userinput></screen>
 
       <para>La opción <option>-dvd-video</option>
         de &man.mkisofs.8; hará posible la creación
         de una estructura de sistema de ficheros de DVD de vídeo.
         Además, la opción <option>-dvd-video</option>
         implica la opción
         <option>-dvd-compat</option> de &man.growisofs.1;.</para>
     </sect2>
 
     <sect2>
       <title>Uso de un DVD+RW</title>
 
       <indexterm>
 	<primary>DVD</primary>
 	<secondary>DVD+RW</secondary>
       </indexterm>
 
       <para>A diferencia de un CD-RW, un DVD+RW virgen necesita ser
         formateado antes de usarse por primera vez.  El programa
         &man.growisofs.1; se encargará de ello automáticamente
         cuando sea necesario, lo cual es el método
         <emphasis>recomendado</emphasis>. De todas formas puede usted
         usar el comando <command>dvd+rw-format</command> para
         formatear el DVD+RW:</para>
 
       <screen>&prompt.root; <userinput>dvd+rw-format <replaceable>/dev/cd0</replaceable></userinput></screen>
 
       <para>Necesita ejecutar esta operación solamente una vez,
         recuerde que sólo los DVD+RW vírgenes necesitan
         ser formateados.  Hecho eso ya puede usar el DVD+RW de la
         forma expuesta en las secciones previas.</para>
 
       <para>Si desea guardar nuevos datos (grabar un sistema de
         ficheros totalmente nuevo, no añadir más datos) en
         un DVD+RW no necesita borrarlo, sólo tiene que escribir
         sobre la grabación anterior (realizando una
         nueva sesión inicial):</para>
 
       <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/ruta/alos/datosnuevos</replaceable></userinput></screen>
 
       <para>El formato DVD+RW ofrece la posibilidad de añadir
         datos fácilmente a una grabación previa.
         La operación consiste en fusionar una nueva sesión
         a la existente, no es escritura multisesión;
         &man.growisofs.1; <emphasis>hará crecer</emphasis> el
         sistema de ficheros ISO 9660 presente en el medio.</para>
 
       <para>Si, por ejemplo, añadir datos al DVD+RW del ejemplo
         anterior tenemos que usar lo siguiente:</para>
 
       <screen>&prompt.root; <userinput>growisofs -M <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/ruta/alos/datosnuevos</replaceable></userinput></screen>
 
       <para>Las mismas opciones de &man.mkisofs.8; que utilizamos
         para quemar la sesión inicial pueden usarse en
         ulteriores escritura.</para>
 
       <note>
         <para>Puede usar la opción <option>-dvd-compat</option>
           si desea mejor la compatibilidad de medios con unidades
           DVD-ROM.  Si la usa en un DVD+RW no evitará que
           pueda añadir más datos.</para>
       </note>
 
       <para>Si por alguna razón desea borrar el contenido del
         medio, haga lo siguiente:</para>
 
       <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable>=<replaceable>/dev/zero</replaceable></userinput></screen>
     </sect2>
 
     <sect2>
       <title>Uso de un DVD-RW</title>
 
       <indexterm>
 	<primary>DVD</primary>
 	<secondary>DVD-RW</secondary>
       </indexterm>
 
       <para>Un DVD-RW acepta dos formatos de disco: el incremental
         secuencial y el de sobreescritura restringida.  Por defecto
         los discos DVD-RW están en formato secuencial.
         </para>
 
       <para>Un DVD-RW virgen puede utilizarse directamente sin
         necesidad de formateo, sin embargo un DVD-RW no virgen en
         formato secuencial necesita ser borrado antes de poder guardar
         una nueva sesión inicial.</para>
 
       <para>Para borrar un DVD-RW en modo secuencial, ejecute:</para>
 
       <screen>&prompt.root; <userinput>dvd+rw-format -blank=full <replaceable>/dev/cd0</replaceable></userinput></screen>
 
       <note>
         <para>Un borrado total (<option>-blank=full</option>) tardará
           aproximadamente una hora en un medio 1x.  Un borrado rápido
           puede realizarse con la opción <option>-blank</option>
           si el DVD-RW fué grabado en modo Disk-At-Once (DAO).
           Para grabar el DVD-RW en modo DAO use el comando:</para>
 
 	<screen>&prompt.root; <userinput>growisofs -use-the-force-luke=dao -Z <replaceable>/dev/cd0</replaceable>=<replaceable>ficheroimagen.iso</replaceable></userinput></screen>
 
         <para>La opción <option>-use-the-force-luke=dao</option>
           no es imprescindible, ya que &man.growisofs.1; trata
           de detectar el medio (borrado rápido) y entrar en
           escritura DAO.</para>
 
         <para>Debería usarse el modo de reescritura restringida
           en los DVD-RW, pues este formato es más flexible que el
           formato de incremento secuencial, el formato por defecto.</para>
       </note>
 
       <para>Para escribir datos en un DVD-RW secuencial proceda del
          mismo modo que con los demás formatos de DVD:</para>
 
       <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/ruta/alos/datos</replaceable></userinput></screen>
 
       <para>Si desea añadir datos a una grabación
         previa tendrá que usar la opción
         <option>-M</option> de &man.growisofs.1;.
         si añade datos a un DVD-RW en modo incremental secuencial
         se creará en el disco una nueva sesión
         y el resultado será un disco multisesión.</para>
 
       <para>Un DVD-RW en formato de sobreescritura restringido no
         necesita ser borrado antes de una nueva sesión
         inicial, sólo tiene que sobreescribir el disco con la
         opción <option>-Z</option>.  esto es similar al
         caso DVD+RW.  También es posible ampliar un sistema
         de ficheros ISO 9660 ya existente y escrito en el disco del
         mismo modo que para un DVD+RW con la opción
         <option>-M</option>.  El resultado será un DVD
         de una sesión.</para>
 
       <para>Para poner un DVD-RW en el formato de sobreescritura
         restringido haga lo siguiente:</para>
 
       <screen>&prompt.root; <userinput>dvd+rw-format <replaceable>/dev/cd0</replaceable></userinput></screen>
 
       <para>Para devolverlo al formato secuencial use:</para>
 
       <screen>&prompt.root; <userinput>dvd+rw-format -blank=full <replaceable>/dev/cd0</replaceable></userinput></screen>
     </sect2>
 
     <sect2>
       <title>Multisesión</title>
 
       <para>Muy pocas unidades DVD-ROM soportan
         DVDs multisesión.  La mayoría de las veces (y
         si tiene suerte) solamente leerán la primera
         sesión.  Los DVD+R, DVD-R y DVD-RW en formato secuencial
         pueden aceptar multisesiones.  El concepto de multisesión
         no existe en los formatos de sobreescritura restringida
         de DVD+RW y DVD-RW.</para>
 
       <para>Usando el siguiente comando despues de una sesión
         inicial (no-cerrada) en un DVD+R, DVD-R o DVD-RW en formato
         secuencial añadirá una nueva sesión
         al disco:</para>
 
       <screen>&prompt.root; <userinput>growisofs -M <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/ruta/alos/nuevosdatos</replaceable></userinput></screen>
 
       <para>Usando este comando con un DVD+RW o un DVD-RW en modo
         de sobreescritura restringida, agregará datos
         fusionando la nueva sesión a la ya existente.  El
         resultado será un disco de una sola sesión.
         Este es el procedimiento habitual para añadir
         datos tras la escritura inicial.</para>
 
       <note>
         <para>Una cierta cantidad de espacio en el medio se usa en
           cada sesión al finalizar e iniciar sesiones;
           por tanto, se deben añadir sesiones con grandes
           cantidades de datos para optimizar el espacio del DVD.
           El número de sesiones está limitado a
           154 para un DVD+R, aproximadamente 2.000 para un DVD-R y
           127 para un DVD+R de doble capa.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Para mayor información</title>
 
       <para>Para más información sobre
         un DVD,puede ejecutar el comando
         <command>dvd+rw-mediainfo <replaceable>/dev/cd0</replaceable></command>
         con el disco en la unidad.</para>
 
       <para>Tiene más información sobre
         <application>dvd+rw-tools</application> en la
         manual &man.growisofs.1;, en el
         <ulink url="http://fy.chalmers.se/~appro/linux/DVD+RW/">sitio
         web de dvd+rw-tools</ulink> y en los archivos de la
         <ulink url="http://lists.debian.org/cdwrite/">lista de correos
         de cdwrite</ulink>.</para>
 
       <note>
         <para>Si va a enviar un informe de problemas es imperativo que
           adjunte la salida que <command>dvd+rw-mediainfo</command> produjo
           al grabar (o no grabar) el medio.  Sin esta salida será
           prácticamente imposible ayudarle.</para>
       </note>
     </sect2>
   </sect1>
 
   <sect1 id="floppies">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Julio</firstname>
 	  <surname>Merino</surname>
 	  <contrib>Texto original de </contrib>
 	</author>
       </authorgroup>
       <!-- 24 Dec 2001 -->
       <authorgroup>
 	<author>
 	  <firstname>Martin</firstname>
 	  <surname>Karlsson</surname>
 	  <contrib>Reescrito por </contrib>
 	</author>
       </authorgroup>
       <!-- 27 Apr 2003 -->
     </sect1info>
 
     <title>Creación y uso de disquetes (floppies)</title>
 
     <para>Poder almacenar datos en discos flexibles es útil algunas
       veces, por ejemplo cuando no se tiene cualquier otro
       medio de almacenamiento extraible o cuando se necesita transferir
       una cantidad pequeña de datos a otro sistema.</para>
 
     <para>Esta sección explicará cómo usar
       disquetes en &os;.  Cubrirá principalmente el
       formateo y utilización de disquetes DOS
       de 3.5 pulgadas, pero los conceptos son similares en
       otros formatos de disquete.</para>
 
     <sect2>
       <title>Formateo de disquetes</title>
 
       <sect3>
 	<title>El dispositivo</title>
 
         <para>El acceso a los disquetes se efectúa a través
           de entradas en <filename>/dev</filename>, igual que en
           otros dispositivos.  Para acceder al disquete
           <quote>crudo</quote> (raw) en versiones 4.X y anteriores, se usa
           <filename>/dev/fd<replaceable>N</replaceable></filename>,
           donde <replaceable>N</replaceable> representa el
           número de unidad, generalmente 0, o
           <filename>/dev/fd<replaceable>NX</replaceable></filename>,
           donde <replaceable>X</replaceable> representa una
           letra.</para>
 
         <para>En versiones 5.0 o posteriores, simplemente use
           <filename>/dev/fd<replaceable>N</replaceable></filename>.</para>
 
 	<sect4>
 	  <title>El tamaño de disco en versiones 4.X y anteriores</title>
 
           <para>También existen dispositivos
             <filename>/dev/fd<replaceable>N</replaceable>.<replaceable>tamaño</replaceable></filename>,
             donde <replaceable>tamaño</replaceable> es el
             tamaño del disquete en kilobytes.  Estas entradas se
             usan durante el formateo a bajo nivel para determinar el
             tamaño del disco.  En los siguientes ejemplos se
             usará el tamaño de 1440kB.</para>
 
           <para>Algunas veces las entradas bajo <filename>/dev</filename>
             tendrán que ser (re)creadas.  Para ello, ejecute:</para>
 
 	  <screen>&prompt.root; <userinput>cd /dev &amp;&amp; ./MAKEDEV "fd*"</userinput></screen>
 	</sect4>
 
 	<sect4>
 	  <title>El tamaño de disco en versiones 5.0 y
             posteriores</title>
 
           <para>En 5.0, &man.devfs.5; administrará
             automáticamente los nodos de dispositivo en
             <filename>/dev</filename>, así que el uso de
             <command>MAKEDEV</command> no es necesario.</para>
 
           <para>El tamaño de disco deseado se pasa a &man.fdformat.1;
             mediante la bandera <option>-f</option>.  Los
             tamaños soportados aparecen en
             &man.fdcontrol.8;, pero tenga muy en cuenta que
             1440kB es el que funciona mejor.</para>
 	</sect4>
       </sect3>
 
       <sect3>
 	<title>Formatear</title>
 
         <para>Un disquete necesita ser formateado a bajo nivel
           antes de poder usarse.  Esto suele hacerlo el fabricante,
           pero el formateo es una buena manera de revisar
           la integridad del medio.  Aunque es posible forzar
           tamaños de disco más grandes (o pequeños),
           1440kB es para lo que la mayoría de los disquetes
           están diseñados.</para>
 
         <para>Para formatear un disquete a bajo nivel debe usar
           &man.fdformat.1;.  Esta utilidad espera el nombre del
           dispositivo como argumento.</para>
 
          <para>Tome nota de cualquier mensaje de error, ya que
            éstos pueden ayudarle a determinar si el disco está
            bien o mal.</para>
 
 	<sect4>
 	  <title>Formateo en versiones 4.X y anteriores</title>
 
           <para>Use el dispositivo
             <filename>/dev/fd<replaceable>N</replaceable>.<replaceable>tamaño</replaceable></filename>
             para formatear el disquete.  Inserte un disco de
             3'5 pulgadas en su unidad y ejecute:</para>
 
 	  <screen>&prompt.root; <userinput>/usr/sbin/fdformat /dev/fd0.1440</userinput></screen>
 
 	</sect4>
 
 	<sect4>
 	  <title>Formateo en versiones 5.0 y posteriores</title>
 
           <para>Use el dispositivo
             <filename>/dev/fd<replaceable>N</replaceable></filename>
             para formatear el disquete.  Inserte un disco de
             3'5 pulgadas en su unidad y ejecute:</para>
 
 	  <screen>&prompt.root; <userinput>/usr/sbin/fdformat -f 1440 /dev/fd0</userinput></screen>
 
 	</sect4>
       </sect3>
     </sect2>
 
 
 
     <sect2>
       <title>La etiqueta de disco</title>
 
       <para>Tras un formato del disco a bajo nivel necesitará
         colocar una etiqueta de disco en él.  Esta etiqueta
         de disco será destruida más tarde, pero es
         necesaria para que el sistema determine el tamaño del
         disco y su geometría.</para>
 
       <para>La nueva etiqueta de disco ocupará todo
         el disco, y contendrá toda la información
         apropiada sobre la geometría del disquete.
         Los valores de geometría para la etiqueta de disco
         están en
 	<filename>/etc/disktab</filename>.</para>
 
       <para>Ejecute &man.disklabel.8; así:</para>
 
       <screen>&prompt.root; <userinput>/sbin/disklabel -B -r -w /dev/fd0 fd1440</userinput></screen>
 
       <note><para>Desde &os;&nbsp;5.1-RELEASE
         &man.bsdlabel.8; reemplazó al viejo programa
         &man.disklabel.8;.  En &man.bsdlabel.8; se eliminaron muchas
         opciones y parámetros obsoletos; en el ejemplo de arriba
         la opción <option>-r</option> no debe usarse.
         Para mayor información consulte la página de
         manual de &man.bsdlabel.8;.</para></note>
 
     </sect2>
 
     <sect2>
       <title>El sistema de ficheros</title>
 
       <para>Ahora el disquete está listo para ser formateado
         a alto nivel.  Esto colocará un sistema de ficheros
         nuevo en el disco y permitirá a &os; leer y escribir en
         el disco.  Después de crear el sistema de ficheros
         se destruye la etiqueta de disco, así que si desea
         reformatearlo, tendrá que recrear la etiqueta
         de disco.</para>
 
       <para>El sistema de ficheros del disquete puede ser UFS o
         o FAT.  FAT suele ser una mejor opción para
         disquetes.</para>
 
       <para>Para formatear un disquete ejecute:</para>
 
       <screen>&prompt.root; <userinput>/sbin/newfs_msdos /dev/fd0</userinput></screen>
 
       <para>El disco está para su uso.</para>
     </sect2>
 
 
     <sect2>
       <title>Uso de un disquete</title>
 
 
       <para>Para usar el disquete móntelo con &man.mount.msdos.8;
         (en versiones 4.X y anteriores) o con &man.mount.msdosfs.8;
         (en versiones 5.X o posteriores).  También se puede
         usar <filename role="package">emulators/mtools</filename>.
         </para>
     </sect2>
   </sect1>
 
   <sect1 id="backups-tapebackups">
     <title>Creación y uso de cintas de datos</title>
 
     <indexterm><primary>medios de cinta</primary></indexterm>
 
     <para>Los principales medios de cinta son 4mm, 8mm, QIC, mini-cartridge
       y DLT.</para>
 
     <sect2 id="backups-tapebackups-4mm">
       <title>4mm (DDS: Digital Data Storage)</title>
 
       <indexterm>
         <primary>medios de cinta</primary>
 	<secondary>cintas DDS (4mm)</secondary>
       </indexterm>
       <indexterm>
         <primary>medios de cinta</primary>
 	<secondary>cintas QIC</secondary>
       </indexterm>
       <para>Las cintas de 4mm están reemplazando a las QIC como los
         medios de respaldo más frecuentes en estaciones de trabajo.
         Esta tendencia se aceleró en gran medida cuando Conner
         adquirió Archive, un fabricante líder de unidades
         QIC, y abandonó la producción de unidades QIC.
         Las unidades de 4mm son pequeñas y silenciosas pero no tienen
         la reputación de fiabilidad de la que disfrutan las
         unidades de 8mm.  Los cartuchos son más baratos  y más
         pequeños (3 x 2 x 0.5 pulgadas, 76 x 51 x 12 mm) que los
         cartuchos de 8mm. En el caso de las cintas de 4mm, igual que las
         de  8mm, tienen un cabezal con una vida comparativamente más
         corta.  Ambos utilizan el escaneado en espiral.</para>
 
 
       <para>El ancho de datos de estas unidades comienza por aprox.
         150&nbsp;kB/s,  con un pico de aprox. ~500&nbsp;kB/s.
         La capacidad de datos va de los
         1'3&nbsp;GB a 2'0&nbsp;GB.  La compresión
         por hardware, disponible con la mayoría de estas unidades,
         dobla aproximadamente la capacidad.  Existen unidades de biblioteca
         de cinta multi-unidad con 6 unidades en un solo armario y
         cambio de cinta automático.  Las capacidades de estas
         bibliotecas alcanzan los 240&nbsp;GB.</para>
 
       <para>El estándar DDS-3 soporta capacidades de cinta
         de hasta 12&nbsp;GB (o 24&nbsp;GB con compresión).</para>
 
       <para>Las unidades de 4mm, igual que las unidades de 8mm, utilizan
         escaneo en espiral.  Tanto unas como otras tienen las mismas
         ventajas y desventajas.</para>
 
       <para>Las cintas deben renovarse por otras después de 2,000
         pasadas ó 100 respaldos completos.</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-8mm">
       <title>8mm (Exabyte)</title>
       <indexterm>
         <primary>medios de cinta</primary>
 	<secondary>cintas Exabyte (8mm)</secondary>
       </indexterm>
 
       <para>Las cintas de 8mm son las unidades de cinta SCSI más comunes;
         son la mejor opción de cintas reemplazables y eso hace que
         las unidades de cinta Exabyte 8mm de 2&nbsp;GB sean casi
         omnipresentes.  Las unidades de 8mm son fiables, prácticas y
         silenciosas.  Los cartuchos son baratos y bastante pequeños
         (4.8 x 3.3 x 0.6 pulgadas; 122 x 84 x 15 mm).  Una desventaja de las
         cintas de 8mm es la vida relativamente corta del cabezal y de la
         propia cinta debido a la alta tasa de movimiento relativo de la cinta
         por los cabezales.</para>
 
       <para>El ancho de datos varía de aprox. 250&nbsp;kB/s
         hasta los 500&nbsp;kB/s.  La capacidad va desde los
         300&nbsp;MB hasta los 7&nbsp;GB.  La compresión por
         hardware, disponible con la mayoría de estas unidades,
         dobla aproximadamente la capacidad.  Estas unidades están
         disponibles como unidades solas o como unidades de biblioteca
         de cinta multi-unidad con 6 unidades y 120 cintas en un solo
         armario.  Las cintas las cambia automáticamente la unidad.
         La capacidad de dichas bibliotecas alcanza los 840+&nbsp;GB.</para>
 
       <para>El modelo Exabyte <quote>Mammoth</quote> soporta 12&nbsp;GB en
         una cinta (24&nbsp;GB con compresión) y cuesta aproximadamente
         el doble que las unidades de cinta convencionales.</para>
 
       <para>Los datos se graban en cinta utilizando escaneo en espiral.
         Las cabezas se posicionan en ángulo en relación al
         medio (6 grados aproximadamente).  La cinta se envuelve cerca de 270
         grados en el cilindro que soporta las cabezas.  El cilindro gira
         mientras la cinta se desliza sobre el cilindro.  El resultado es
         una alta densidad de datos y pistas almacenadas muy pegadas,
         dispuestas en ángulo a través de la cinta de un
         extremo al otro.</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-qic">
       <title>QIC</title>
       <indexterm>
         <primary>medios de cinta</primary>
 	<secondary>QIC-150</secondary>
       </indexterm>
 
       <para>Las cintas y unidades QIC-150 son, quizás, las unidades y
         medios de cinta más comunes.  Las unidades de cinta QIC son
         las unidades de respaldo <quote>serias</quote> menos caras.
         La desventaja es el coste del medio.  Las cintas QIC son caras
         comparadas con las cintas de 8mm o de 4mm, hasta 5 veces el precio de
         almacenamiento de datos por GB.  No obstante, si sus necesidades
         pueden satisfacerse con media docena de cintas, QIC tal vez sea la
         decisión correcta.  QIC es la unidad de cinta
         <emphasis>más</emphasis>  común.  Casi en todas partes
         tienen una unidad QIC de una u otra densidad.  Y ese es el problema,
         QIC ofrece un enorme número de densidades en cintas
         físicamente similares (algunas veces idénticas).
         Las unidades QIC son cualquier cosa menos silenciosas.
         Hacen bastante ruido antes de iniciar la grabación de datos
         y son claramente audibles siempre que leen, escriben o hacen una
         búsqueda.  Las cintas QIC miden 6 x 4 x 0.7 pulgadas;
         152 x 102 x 17 mm.</para>
 
       <para>El ancho de datos varía de aprox. 150&nbsp;kB/s a aprox.
         500&nbsp;kB/s.  La capacidad de datos varía de 40&nbsp;MB
         a 15&nbsp;GB. La compresión por hardware existe en muchas de
         las nuevas unidades QIC.  Las unidades QIC se ven con menos
         frecuencia y además están siendo suplantadas por
         unidades DAT.</para>
 
       <para>Los datos se graban en la cinta en pistas.  Las pistas
         discurren a lo largo del extenso eje de la cinta de un extremo
         al otro.  El número de pistas, y por lo tanto el ancho de
         una pista varía según la capacidad de la cinta.
         La mayoría, si no todas las unidades nuevas, ofrecen
         compatibilidad con modelos anteriores al menos para lectura
         (y también en muchos casos de escritura).  QIC tiene
         buena reputación en cuanto a seguridad de los datos
         (las piezas mecánicas son más simples y
         más robustas que en las unidades de búsqueda
         en espiral).</para>
 
       <para>Las cintas deben ser sustituirse por otras después de
         5,000 respaldos.</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-dlt">
       <title>DLT</title>
       <indexterm>
         <primary>medios de cinta</primary>
 	<secondary>DLT</secondary>
       </indexterm>
 
       <para>DLT tiene la tasa de transferencia de datos más
         rápida de todos los tipos de unidades mostradas aquí.
         La cinta de 1/2" (12'5mm) está alojada en un cartucho
         de un solo cilindro (4 x 4 x 1 pulgadas; 100 x 100 x 25 mm).
         El cartucho tiene una puerta giratoria a lo largo de todo un
         lado del cartucho.  El mecanismo de la unidad abre esta puerta
         para extraer el <quote>líder</quote>.  El <quote>lider</quote>
         de la cinta tiene un agujero oval que la unidad utiliza para
         <quote>enganchar</quote> la cinta.  El cilindro de levantamiento
         está dentro de la unidad de cinta.  Los demás
         cartuchos descritos en este texto  (los cartuchos de 9
         pistas son la única excepción) tienen el cilindro
         proveedor alojados dentro del propio cartucho de cinta.</para>
 
       <para>El ancho de datos es aproximadamente de 1'5&nbsp;MB/s, tres veces
         el ancho de unidades de cinta de 4mm, de 8mm o QIC.  Las capacidades
         de datos varían entre 10&nbsp;GB y 20&nbsp;GB en una sola
         unidad.  Hay unidades multicinta y con cargadores multi-cinta,
         y bibliotecas multiunidad que pueden albergar de 5 a 900 cintas
         con una a 20 unidades, con lo que pueden alcanzar desde
         50&nbsp;GB hasta 9&nbsp;TB de almacenamiento.</para>
 
       <para>Con compresión, el formato DLT Type IV soporta hasta
         70&nbsp;GB de capacidad.</para>
 
       <para>Los datos se almacenan en cinta en pistas paralelas a la
         dirección del movimiento de la cinta (como en las cintas
         QIC).  Se escriben dos pistas al mismo tiempo.  El tiempo de vida
         de lectura/escritura es relativamente largo.  Una vez que la cinta
         no hay movimiento relativo entre las cabezas y la cinta.</para>
     </sect2>
 
     <sect2>
       <title id="backups-tapebackups-ait">AIT</title>
       <indexterm>
         <primary>medios de cinta</primary>
 	<secondary>AIT</secondary>
       </indexterm>
 
       <para>AIT es un nuevo formato de Sony, y puede almacenar hasta
         50&nbsp;GB (con compresión) por cinta.  Las cintas contienen
         chips de memoria que retienen un índice de los
         contenidos de la cinta.  Este índice puede ser leido
         rápidamente para determinar la posición
         de los ficheros en la cinta, en lugar de los varios minutos que
         requeriría el proceso con otras cintas.
         <application>SAMS:Alexandria</application> puede gestionar
         más de 40 bibliotecas de cinta AIT, comunicándose
         directamente con el chip de memoria de la cinta para desplegar
         el contenido en pantalla, determinar qué ficheros fueron
         respaldados a qué cinta, ubicar la cinta correcta, cargarla
         y restaurar los datos desde la cinta.</para>
 
       <para>Las bibliotecas como ésta cuestan alrededor de 20.000
         dólares, lo que las aleja bastante del alcance de los
         aficionados.</para>
     </sect2>
 
     <sect2>
       <title>Estreno de una cinta</title>
 
       <para>La primera vez que trate de leer o escribir una
         cinta nueva, completamente en blanco, la operación
         fallará.  El mensaje de la consola se parecerá
         al siguiente:</para>
 
       <screen>sa0(ncr1:4:0): NOT READY asc:4,1
 sa0(ncr1:4:0):  Logical unit is in process of becoming ready</screen>
 
       <para>La cinta no contiene un bloque identificador (bloque número
         0).  Todas las unidades de cinta QIC desde la adopción del
         estándar QIC-525 escriben un bloque identificador en la
         cinta.  Existen dos soluciones:</para>
 
       <itemizedlist>
 	<listitem>
           <para><command>mt fsf 1</command> hace que la unidad de cinta
             escriba un bloque identificador a la cinta.</para>
 	</listitem>
 
 	<listitem>
           <para>Use el botón del panel frontal para expulsar
             la cinta.</para>
 
           <para>Inserte nuevamente la cinta y haga un <command>dump</command>
             de datos a la cinta.</para>
 
           <para><command>dump</command> devolverá
             <errorname>DUMP: End of tape detected</errorname> y la consola
             mostrará
             <errorname>HARDWARE FAILURE info:280 asc:80,96</errorname>.</para>
 
           <para>Rebobine la cinta usando: <command>mt rewind</command>.</para>
 
           <para>A partir de ese momento podrá utilizar la cinta.</para>
 	</listitem>
       </itemizedlist>
 
     </sect2>
   </sect1>
 
   <sect1 id="backups-floppybackups">
     <title>Respaldos en disquetes</title>
 
     <sect2 id="floppies-using">
       <title>?Puedo utilizar disquetes para respaldar mis datos?</title>
       <indexterm><primary>respaldo en discos flexibles</primary></indexterm>
       <indexterm><primary>discos flexibles</primary></indexterm>
 
       <para>Los disquetes no son realmente el medio ideal
         para hacer respaldos debido a que:</para>
 
       <itemizedlist>
 	<listitem>
           <para>El medio no es fiable, especialmente después de
             largos periodos de tiempo.</para>
 	</listitem>
 
 	<listitem>
           <para>El respaldo y la restauración es muy lento.</para>
 	</listitem>
 
 	<listitem>
           <para>Tienen una capacidad muy limitada (los dís de
             respaldar un disco duro entero en una docena de disquetes
             pasaron hace mucho).</para>
 	</listitem>
       </itemizedlist>
 
       <para>De todas maneras, si no tiene otro método para respaldar
         sus datos los disquetes son una mejor solución que no tener
         ningún respaldo.</para>
 
       <para>Si tiene que utilizar disquetes asegúrese de usar
         discos de buena calidad.  Los disquetes que han estado
         almacenados en la oficina durante un par de años son una
         mala elección.  Lo mejor sería que utilizara discos
         nuevos de un fabricante respetado.</para>
     </sect2>
 
     <sect2 id="floppies-creating">
       <title>?Cómo respaldo mis datos a discos flexibles?</title>
 
       <para>La mejor manera de respaldar a un disquete
         es usar &man.tar.1; con la opción <option>-M</option>
         (multi volumen), que permite que el respaldo se guarde en
         varios disquetes.</para>
 
       <para>Para respaldar todos los ficheros en el directorio actual y
         sus subdirectorios use esto (como <username>root</username>):</para>
 
       <screen>&prompt.root; <userinput>tar Mcvf /dev/fd0 *</userinput></screen>
 
       <para>Cuando el primer disquete esté lleno
         &man.tar.1; le solicitará que inserte el siguiente
         volumen (debido a que &man.tar.1; es independiente del medio
         se refiere a volúmenes; en éste contexto se refiere a
         disquetes).</para>
 
       <screen>Prepare volume #2 for /dev/fd0 and hit return:</screen>
 
       <para>Esto se repite (con el número de volumen incrementando)
         hasta que todos los ficheros especificados hayan sido archivados.</para>
     </sect2>
 
     <sect2 id="floppies-compress">
 
       <title>?Puedo comprimir mis respaldos?</title>
       <indexterm>
         <primary><command>tar</command></primary>
       </indexterm>
       <indexterm>
         <primary><command>gzip</command></primary>
       </indexterm>
       <indexterm><primary>compresión</primary></indexterm>
 
       <para>Desafortunadamente, &man.tar.1; no permite
         el uso de la opción <option>-z</option> para archivos
         multi-volumen.  Puede, por supuesto, hacer un &man.gzip.1;
         a todos los ficheros, mandarlos con &man.tar.1; a los
         disquetes, <emphasis>y después hacer &man.gunzip.1;
         a los archivos</emphasis></para>
     </sect2>
 
     <sect2 id="floppies-restoring">
 
       <title>?Cómo recupero mis respaldos?</title>
 
       <para>Para restaurar el archivo completo use:</para>
 
       <screen>&prompt.root; <userinput>tar Mxvf /dev/fd0</userinput></screen>
 
       <para>Hay dos maneras que puede usar para restaurar
         ficheros específicos.  La primera, puede comenzar por el
         primer disco flexible y usar:</para>
 
       <screen>&prompt.root; <userinput>tar Mxvf /dev/fd0 <replaceable>nombredefichero</replaceable></userinput></screen>
 
       <para>La utilidad &man.tar.1; le pedirá que inserte el resto de
         disquetes hasta que encuentre el fichero requerido.</para>
 
       <para>La segunda manera es: si sabe en qué disco se encuentra
         el fichero puede insertar ese disco y usar el comando expuesto
         arriba.  Tenga en cuenta que si el primer fichero en el disquete
         es la continuación del anterior
         &man.tar.1; le advertirá que no puede restaurarlo
         <emphasis>incluso si no se lo ha solicitado</emphasis></para>
     </sect2>
   </sect1>
 
   <sect1 id="backup-basics">
     <title>Bases para respaldos</title>
 
     <para>Los tres principales programas para respaldos son
       &man.dump.8;, &man.tar.1; y &man.cpio.1;.</para>
 
     <sect2>
       <title>Dump y Restore</title>
       <indexterm>
         <primary>backup software</primary>
 	<secondary>dump / restore</secondary>
       </indexterm>
       <indexterm><primary><command>dump</command></primary></indexterm>
       <indexterm><primary><command>restore</command></primary></indexterm>
 
       <para>Los programas &unix; que se han usado durante muchos
         años para hacer copias de seguridad son
         <command>dump</command> y <command>restore</command>.
         Operan en las unidades como una colección de bloques de
         disco, bajo la abstracción de ficheros, los enlaces y
         directorios creados por el sistema de ficheros.
         <command>dump</command> respalda un sistema de ficheros completo
         en un dispositivo.  No es capaz de respaldar solamente parte
         de un sistema de ficheros o un árbol de directorios
         que se extienda por más de un sistema de ficheros.
         <command>dump</command> no escribe ficheros y directorios a
         cinta, escribe los bloques de datos <quote>crudos</quote> (raw)
         que conforman los ficheros y directorios.</para>
 
       <note><para>Si utiliza <command>dump</command> en su directorio
         raíz, no respaldará
         <filename>/home</filename>, <filename>/usr</filename> ni
         muchos otros directorios, ya que suelen ser puntos de montaje
         de otros sistemas de ficheros o enlaces simbólicos hacia
         dichos sistemas de ficheros.</para></note>
 
       <para><command>dump</command> tiene peculiaridades que se mantienen
         desde sus primeros días en la Version 6 de AT&amp;T UNIX
         (alrededor de 1975).  Los parámetros por defecto
         son los adecuados para cintas de 9 pistas (6250 bpi), pero no para
         los medios de alta densidad disponibles hoy en día
         (hasta 62,182 ftpi).  Estos valores por defecto deben
         obviarse en la línea de comandos para aprovechar la
         capacidad de las unidades de cinta actuales.</para>
 
       <indexterm><primary><filename>.rhosts</filename></primary></indexterm>
 
       <para>También es posible respaldar datos a través de
         la red a una unidad de cinta conectada a otra computadora con
         <command>rdump</command> y <command>rrestore</command>.  Ambos
         programas dependen de &man.rcmd.3; y &man.ruserok.3; para
         acceder a la unidad de cinta remota.  Por consiguiente, el usuario
         que realiza el respaldo debe estar listado en el fichero
         <filename>.rhosts</filename> de la computadora remota.  Los
         argumentos para <command>rdump</command> y <command>rrestore</command>
         deben ser adecuados para usarse en la computadora remota.
         Cuando realice un <command>rdump</command> desde &os;
         a una unidad de cinta Exabyte conectada a una Sun llamada
         <hostid>komodo</hostid>, use:</para>
 
       <screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nsa8 /dev/da0a 2>&amp;1</userinput></screen>
 
       <para>Advertencia: existen implicaciones de seguridad al
         permitir autentificación mediante
         <filename>.rhosts</filename>.  Le recomendamos que
         evalúe la situación cuidadosamente.</para>
 
       <para>También es posible usar <command>dump</command> y
         <command>restore</command> de una forma más segura
         a través de <command>ssh</command>.</para>
 
       <example>
 	<title>Utilizando <command>dump</command> a través de
           <application>ssh</application></title>
 
 	<screen>&prompt.root; <userinput>/sbin/dump -0uan -f - /usr | gzip -2 | ssh -c blowfish \
           usuario@maquinaobjetivo.ejemplo.com dd of=/misficherosgrandes/dump-usr-l0.gz</userinput></screen>
 
       </example>
 
       <para>Uso del método integrado de <command>dump</command>,
         configurando la variable de ambiente <envar>RSH</envar>:</para>
 
       <example>
 	<title>Uso de <command>dump</command> a través de
            <application>ssh</application> con <envar>RSH</envar>
            configurada</title>
 
 	<screen>&prompt.root; <userinput>RSH=/usr/bin/ssh /sbin/dump -0uan -f usuario@maquinaobjetivo.ejemplo.com:/dev/sa0 /usr</userinput></screen>
 
       </example>
 
     </sect2>
 
     <sect2>
       <title><command>tar</command></title>
       <indexterm>
         <primary>software de respaldo</primary>
         <secondary><command>tar</command></secondary>
       </indexterm>
 
       <para>&man.tar.1; también es de la época de
         la Version 6 de AT&amp;T UNIX (alrededor de 1975).
         <command>tar</command> trabaja en cooperación con el
         sistema de ficheros; escribe ficheros y directorios a
         cinta.  <command>tar</command> no soporta el rango completo
         de opciones que ofrece &man.cpio.1;, pero no requiere el
         inusual comando de pipeline que utiliza
         <command>cpio</command>.</para>
 
       <indexterm><primary><command>tar</command></primary></indexterm>
 
       <para>En FreeBSD 5.3 y posteriores, tiene a su disposición
         GNU <command>tar</command>
         y el comando por defecto <command>bsdtar</command>.
         La versión GNU puede ser invocada mediante
         <command>gtar</command>.  Soporta dispositivos remotos mediante
         la misma sintaxis que <command>rdump</command>.  Para hacer un
         <command>tar</command> a una unidad de cinta conectada a una
         Sun llamada <hostid>komodo</hostid>, use:</para>
 
       <screen>&prompt.root; <userinput>/usr/bin/gtar cf komodo:/dev/nsa8 . 2>&amp;1</userinput></screen>
 
       <para>Puede hacer lo mismo con o con
         <command>bsdtar</command> usando un <quote>pipe</quote> y
         <command>rsh</command> para mandar los datos a una unidad
         de cinta remota.</para>
 
       <screen>&prompt.root; <userinput>tar cf - . | rsh <replaceable>nombredemaquina</replaceable> dd of=<replaceable>dispositivo-de-cinta</replaceable> obs=20b</userinput></screen>
 
       <para>Si le preocupa la seguridad del proceso de hacer un
         respaldo a través de una red debe usar
         <command>ssh</command> en lugar de <command>rsh</command>.
         </para>
     </sect2>
 
     <sect2>
       <title><command>cpio</command></title>
       <indexterm>
         <primary>software de respaldo</primary>
         <secondary><command>cpio</command></secondary>
       </indexterm>
 
       <para>&man.cpio.1; es el programa de intercambio de archivos de
         cinta para medios magnéticos.  <command>cpio</command>
         tiene opciones (entre muchas otras) para realizar intercambio de
         bytes, escribir un número diferente de formatos de
         archivo y hacer <quote>pipe</quote> de datos hacia otros programas.
         Esta última opción hace de <command>cpio</command>
         una elección excelente para medios de instalación.
         <command>cpio</command> no sabe cómo recorrer el árbol
         de directorios, así que debe facilitarle una lista de
         directorios a través de
         <filename>stdin</filename>.</para>
 
       <indexterm><primary><command>cpio</command></primary></indexterm>
 
       <para><command>cpio</command> no permite respaldos a través
         de la red.  Puede usar un pipe y <command>rsh</command>
         para mandar los datos a una unidad de cinta remota.</para>
 
       <screen>&prompt.root; <userinput>for f in <replaceable>lista_directorios; do</replaceable></userinput>
 <userinput>find $f &lt;&lt; backup.list</userinput>
 <userinput>done</userinput>
 &prompt.root; <userinput>cpio -v -o --format=newc &lt; backup.list | ssh <replaceable>usuario</replaceable>@<replaceable>máquina</replaceable> "cat > <replaceable>dispositivo_de_respaldo</replaceable>"</userinput></screen>
 
       <para>Donde <replaceable>lista_directorios</replaceable> es la lista de
         directorios que desea respaldar,
         <replaceable>usuario</replaceable>@<replaceable>máquina</replaceable>
         es la combinación  usuario/nombre de equipo que realizará
         el respaldo y <replaceable>dispositivo_de_respaldo</replaceable>
         es donde el respaldo se escribirá efectivamente (por ejemplo
         <filename>/dev/nsa0</filename>).</para>
     </sect2>
 
     <sect2>
       <title><command>pax</command></title>
       <indexterm>
         <primary>software de respaldo</primary>
         <secondary><command>pax</command></secondary>
       </indexterm>
       <indexterm><primary><command>pax</command></primary></indexterm>
       <indexterm><primary>POSIX</primary></indexterm>
       <indexterm><primary>IEEE</primary></indexterm>
 
       <para>&man.pax.1; es la respuesta IEEE/&posix; a
         <command>tar</command> y <command>cpio</command>.
         A través de los años las diversas versiones
         de <command>tar</command> y <command>cpio</command> se han
         vuelto ligeramente incompatibles, así que en lugar
         de pelear por hacerlo completamente estándar,
         &posix; creó una nueva utilidad de archivado.
         <command>pax</command> trata de leer y escribir muchos de
         los diversos formatos de <command>cpio</command> y
         <command>tar</command>, además de nuevos formatos
         propios.  Su conjunto de comandos se parece más a
         <command>cpio</command> que a
 	<command>tar</command>.</para>
     </sect2>
 
     <sect2 id="backups-programs-amanda">
 
       <title><application>Amanda</application></title>
 
       <indexterm>
         <primary>software de respaldo</primary>
         <secondary><application>Amanda</application></secondary>
       </indexterm>
 
       <indexterm><primary><application>Amanda</application></primary></indexterm>
 
       <!-- Remove link until <port> tag is available -->
 
       <para><application>Amanda</application> (Advanced Maryland
         Network Disk Archiver) es un sistema de respaldos cliente/servidor,
         en lugar de un solo programa.  Un servidor
         <application>Amanda</application>
         respaldará a una sola unidad de cinta cualquier cantidad de
         computadoras que tengan clientes <application>Amanda</application>
         y una conexión de red al servidor
         <application>Amanda</application>.
         Un problema común en sitios con gran cantidad de discos
         grandes es que la cantidad de tiempo requerida para respaldar los
         datos directamente a cinta excede la cantidad de tiempo disponible
         para la tarea.  <application>Amanda</application> resuelve este
         problema.  <application>Amanda</application> puede usar un
         <quote>disco intermedio</quote> para respaldar varios sistemas de
         ficheros al mismo tiempo.
         <application>Amanda</application> crea
         <quote>conjuntos de archivo</quote>, esto es, un grupo de cintas
         usadas durante un periodo de tiempo para crear respaldos completos
         de todos los sistemas de ficheros listados en el fichero de
         configuración de <application>Amanda</application>.
         El <quote>conjunto de archivo</quote> también contiene
         respaldos incrementales nocturnos (o diferenciales) de todos los
         sistemas de ficheros.  Para restaurar un sistema de ficheros
         dañado hace falta el respaldo completo más reciente
         y los respaldos incrementales.</para>
 
      <para>El fichero de configuración ofrece un control
        exhaustivo de los respaldos y del tráfico de red que
        <application>Amanda</application> genera.
        <application>Amanda</application> usará cualquiera de
        los programas de respaldo mencionados arriba para escribir los
        datos a cinta.  Puede instalar <application>Amanda</application>
        como paquete y como port.  No forma parte del sistema base.</para>
       </sect2>
 
     <sect2>
       <title>No hacer nada</title>
 
       <para><quote>No hacer nada</quote> no es un programa, pero
         es la estrategia de respaldo más extendida.  No tiene
         coste.  No hay un calendario de respaldos a seguir.  Simplemente
         hay que decir <emphasis>que no</emphasis>.  Si algo le sucediera a
         sus datos <emphasis>sonría y acostúmbrese a su nueva
         situación</emphasis>.</para>
 
       <para>Si su tiempo y sus datos valen poco o nada, entonces
         <quote>no hacer nada</quote> es el programa de respaldo más
         adecuado para usted.  Pero cuidado, &unix; es una herramienta
         muy poderosa y puede suceder que dentro de seis meses
         tenga un montón de ficheros que sean valiosos para
         usted.</para>
 
       <para><quote>No hacer nada</quote> es el método correcto de
         respaldo para <filename>/usr/obj</filename> y otros árboles
         de directorios que pueden ser fácilmente recreados por su
         computadora.  Un ejemplo son los archivos que forman la
         versión HTML o &postscript; de este manual.
         Estos documentos han sido generados desde ficheros SGML.
         Crear respaldos de los archivos HTML o &postscript; no es
         necesario dado que los ficheros SGML se respaldan regularmente.
         </para>
     </sect2>
 
     <sect2>
       <title>?Cuál es el mejor programa de respaldos?</title>
       <indexterm>
         <primary>LISA</primary>
       </indexterm>
 
       <para>&man.dump.8;.
         <emphasis>Y no hay más que hablar.</emphasis>
         Elizabeth D. Zwicky realizó pruebas de estrés a
         a todos los programas de copia de seguridad aquí
         expuestos.  La elección clarísima para preservar
         todos sus datos y todas las peculiaridades de sus sistemas de
         ficheros &unix; es <command>dump</command>.
         Elizabeth creó sistemas de ficheros conteniendo una gran
         variedad de condiciones inusuales (y algunos no tan inusuales)
         y probó cada programa haciendo un respaldo y restaurando
         esos sistemas de ficheros.  Esas peculiaridades incluían:
         ficheros con y un bloque nulo, ficheros con caracteres
         extraños en sus nombres, ficheros que no se podían
         leer ni escribir, dispositivos, ficheros que cambiaban de
         tamaño durante el respaldo, ficheros que eran creados/borrados
         durante el respaldo y cosas así.  Elizabeth presentó los
         resultados en LISA V en octubre de 1991.
         Consulte <ulink url="http://berdmann.dyndns.org/zwicky/testdump.doc.html">torture-testing
         Backup and Archive Programs</ulink>.</para>
     </sect2>
 
     <sect2>
       <title>Procedimiento de restauración de emergencia</title>
 
       <sect3>
 	<title>Antes del desastre</title>
 
         <para>Solamente existen cuatro pasos que debe realizar
           en preparación de cualquier desastre que pudiera
           ocurrir.</para>
 	<indexterm>
     <primary><command>disklabel</command></primary>
   </indexterm>
 
         <para>Primero, imprima la etiqueta de disco de cada uno
           de sus discos (<command>disklabel da0 | lpr</command>),
           su tabla de sistemas de ficheros
           (<filename>/etc/fstab</filename>) y todos los mensajes de
           arranque, dos copias de cada uno.</para>
 
 	<indexterm><primary>fix-it floppies</primary></indexterm>
         <para>Segundo, asegúrese que los disquetes de rescate
           (<filename>boot.flp</filename> y <filename>fixit.flp</filename>)
           tienen todos sus dispositivos.  La manera más fácil
           de revisarlo es reiniciar su máquina con el disquete
           en la unidad y revisar los mensajes de arranque.  Si todos sus
           dispositivos aparecen en la lista y funcionan, pase al tercer
           paso.</para>
 
         <para>Si ha habido algún problema tiene que crear dos
           disquetes de arranque personalizados, que deben tener un
           kernel que pueda montar todos sus discos y acceder a su
           unidad de cinta.  Estos discos deben contener:
           <command>fdisk</command>, <command>disklabel</command>,
           <command>newfs</command>, <command>mount</command> y
           cualquier programa de respaldo que utilice.  Estos
           programas deben estar enlazados estáticamente.  Si
           usa <command>dump</command>, el disquete debe
           contener <command>restore</command>.</para>
 
         <para>Tercero, use cintas de respaldo regularmente.  Cualquier
           cambio que haga después de su último respaldo puede
           perderse irremediablemente.  Proteja contra escritura las cintas
           de respaldo.</para>
 
         <para>Cuarto, pruebe los disquetes (ya sea <filename>boot.flp</filename>
           y <filename>fixit.flp</filename> o los dos discos personalizados
           que creó en el segundo paso) y las cintas de respaldo.
           Documente el procedimiento.  Almacene estas notas con los
           discos de arranque, las impresiones y las cintas de respaldo.
           Estará tan perturbado cuando restaure su sistema  que las
           notas pueden pueden evitar que destruya sus cintas de respaldo.
           (?Como? en lugar de <command>tar xvf /dev/sa0</command>,
           puede teclear accidentalmente <command>tar cvf /dev/sa0</command>
           y sobreescribir su cinta).</para>
 
         <para>Como medida adicional de seguridad haga discos de inicio
           y dos cintas de respaldo cada vez.  Almacene una de cada
           en una ubicación remota.  Una ubicación remota
           <emphasis>NO</emphasis> es el sótano del mismo edificio.
           Muchas firmas alojadas en el World Trade Center aprendieron esta
           leccón de la manera más difícil.  Esa
           ubicación remota debe estar separada físicamente
           de sus computadoras y unidades de disco por una distancia
           significativa.</para>
 
 	<example>
 	  <title>Un <quote>script</quote> para la creación de discos
             flexibles de arranque</title>
 
 	<programlisting><![CDATA[#!/bin/sh
 #
 # create a restore floppy
 #
 # format the floppy
 #
 PATH=/bin:/sbin:/usr/sbin:/usr/bin
 
 fdformat -q fd0
 if [ $? -ne 0 ]
 then
 	 echo "Bad floppy, please use a new one"
 	 exit 1
 fi
 
 # place boot blocks on the floppy
 #
 disklabel -w -B /dev/fd0c fd1440
 
 #
 # newfs the one and only partition
 #
 newfs -t 2 -u 18 -l 1 -c 40 -i 5120 -m 5 -o space /dev/fd0a
 
 #
 # mount the new floppy
 #
 mount /dev/fd0a /mnt
 
 #
 # create required directories
 #
 mkdir /mnt/dev
 mkdir /mnt/bin
 mkdir /mnt/sbin
 mkdir /mnt/etc
 mkdir /mnt/root
 mkdir /mnt/mnt			# for the root partition
 mkdir /mnt/tmp
 mkdir /mnt/var
 
 #
 # populate the directories
 #
 if [ ! -x /sys/compile/MINI/kernel ]
 then
 	 cat &lt;&lt; EOM
 The MINI kernel does not exist, please create one.
 Here is an example config file:
 #
 # MINI - A kernel to get FreeBSD onto a disk.
 #
 machine         "i386"
 cpu             "I486_CPU"
 ident           MINI
 maxusers        5
 
 options         INET                    # needed for _tcp _icmpstat _ipstat
                                         #            _udpstat _tcpstat _udb
 options         FFS                     #Berkeley Fast File System
 options         FAT_CURSOR              #block cursor in syscons or pccons
 options         SCSI_DELAY=15           #Be pessimistic about Joe SCSI device
 options         NCONS=2                 #1 virtual consoles
 options         USERCONFIG              #Allow user configuration with -c XXX
 
 config          kernel	root on da0 swap on da0 and da1 dumps on da0
 
 device          isa0
 device          pci0
 
 device          fdc0	at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
 device          fd0	at fdc0 drive 0
 
 device          ncr0
 
 device          scbus0
 
 device          sc0	at isa? port "IO_KBD" tty irq 1 vector scintr
 device          npx0	at isa? port "IO_NPX" irq 13 vector npxintr
 
 device          da0
 device          da1
 device          da2
 
 device          sa0
 
 pseudo-device   loop            # required by INET
 pseudo-device   gzip            # Exec gzipped a.out's
 EOM
 	 exit 1
 fi
 
 cp -f /sys/compile/MINI/kernel /mnt
 
 gzip -c -best /sbin/init > /mnt/sbin/init
 gzip -c -best /sbin/fsck > /mnt/sbin/fsck
 gzip -c -best /sbin/mount > /mnt/sbin/mount
 gzip -c -best /sbin/halt > /mnt/sbin/halt
 gzip -c -best /sbin/restore > /mnt/sbin/restore
 
 gzip -c -best /bin/sh > /mnt/bin/sh
 gzip -c -best /bin/sync > /mnt/bin/sync
 
 cp /root/.profile /mnt/root
 
 cp -f /dev/MAKEDEV /mnt/dev
 chmod 755 /mnt/dev/MAKEDEV
 
 chmod 500 /mnt/sbin/init
 chmod 555 /mnt/sbin/fsck /mnt/sbin/mount /mnt/sbin/halt
 chmod 555 /mnt/bin/sh /mnt/bin/sync
 chmod 6555 /mnt/sbin/restore
 
 #
 # create the devices nodes
 #
 cd /mnt/dev
 ./MAKEDEV std
 ./MAKEDEV da0
 ./MAKEDEV da1
 ./MAKEDEV da2
 ./MAKEDEV sa0
 ./MAKEDEV pty0
 cd /
 
 #
 # create minimum file system table
 #
 cat > /mnt/etc/fstab &lt;&lt;EOM
 /dev/fd0a    /    ufs    rw  1  1
 EOM
 
 #
 # create minimum passwd file
 #
 cat > /mnt/etc/passwd &lt;&lt;EOM
 root:*:0:0:Charlie &amp;:/root:/bin/sh
 EOM
 
 cat > /mnt/etc/master.passwd &lt;&lt;EOM
 root::0:0::0:0:Charlie &amp;:/root:/bin/sh
 EOM
 
 chmod 600 /mnt/etc/master.passwd
 chmod 644 /mnt/etc/passwd
 /usr/sbin/pwd_mkdb -d/mnt/etc /mnt/etc/master.passwd
 
 #
 # umount the floppy and inform the user
 #
 /sbin/umount /mnt
 echo "The floppy has been unmounted and is now ready."]]></programlisting>
 
         </example>
 
       </sect3>
 
       <sect3>
 	<title>Después del desastre</title>
 
         <para>La pregunta clave es: ?sobrevivió su hardware?
           Ha estado haciendo respaldos regularmente, así que no hay
           necesidad de preocuparse por el software.</para>
 
         <para>Si el hardware ha sufrido daños los componentes deben
           reemplazarse antes de intentar de usar su sistema.</para>
 
         <para>Si su hardware está bien revise sus discos de arranque.
           Si usa disquetes de arranque personalizados arranque en modo
           monousuario (teclée <literal>-s</literal> en el
           en el <quote>prompt</quote> de arranque <prompt>boot:</prompt>).
           Sáltese el siguiente párrafo.</para>
 
         <para>Si utiliza usando los discos <filename>boot.flp</filename>
           y <filename>fixit.flp</filename>, siga leyendo.  Inserte el disco
           <filename>boot.flp</filename> en la primera unidad de disquete
           y arranque la máquina.  El menú de instalación
           original se desplegará en pantalla.  Seleccione la
           opción <literal>Fixit--Repair mode with CDROM or
           floppy.</literal>.  Inserte el disco <filename>fixit.flp</filename>
           cuando se le pida.  Tanto <command>restore</command> como los
           demás programas que necesitará están en
           <filename class="directory">/mnt2/rescue</filename>
           (<filename class="directory">/mnt2/stand</filename> para versiones
           de &os; anteriores a 5.2).</para>
 
 	<para>Recupere cada sistema de ficheros por separado.</para>
 
 	<indexterm>
     <primary><command>mount</command></primary>
   </indexterm>
 	<indexterm><primary>partición raíz</primary></indexterm>
 	<indexterm>
     <primary><command>disklabel</command></primary>
   </indexterm>
 	<indexterm>
     <primary><command>newfs</command></primary>
   </indexterm>
         <para>Trate de montar (por ejemplo
           <command>mount /dev/da0a /mnt</command>) la partición
           raíz de su primer disco.  Si la etiqueta del disco
           ha sufrido daños use <command>disklabel</command>
           para reparticionar y etiquetar el disco de forma que coincida con
           la etiqueta que imprimió y guardó previamente.   Use
           <command>newfs</command> para crear de nuevo sus sistemas de
           ficheros.  Monte de nuevo la partición raíz del
           disquete en modo lectura/escritura
           (<command>mount -u -o rw /mnt</command>).  Ejecute su programa de
           respaldo y utilice las cintas de respaldo para restaurar sus datos
           en este sistema de ficheros
           (<command>restore vrf /dev/sa0</command>).
           Desmonte el sistema de ficheros (<command>umount /mnt</command>).
           Repita el proceso con cada sistema de ficheros que sufrió
           daños.</para>
 
         <para>Una vez que su sistema esté en marcha respalde sus
           datos en cintas nuevas.  Cualquiera que haya sido la causa de
           la caída o pérdida de datos puede suceder de nuevo.
           Una hora más que gaste ahora puede ahorrarle mucho
           sufrimiento más adelante.</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="disks-virtual">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Reorganizado y mejorado por </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title>Sistemas de ficheros en red, memoria y respaldados en fichero</title>
 
     <indexterm><primary>discos virtuales</primary></indexterm>
     <indexterm>
       <primary>discos</primary>
       <secondary>virtuales</secondary>
     </indexterm>
 
     <para>Además de los discos que conecta físicamente en
       su máquina (discos flexibles, CDs, discos duros, etc.)
       &os; permite usar otro tipo de discos:
       <firstterm>los discos virtuales</firstterm>.</para>
 
     <indexterm><primary>NFS</primary></indexterm>
     <indexterm><primary>Coda</primary></indexterm>
     <indexterm>
       <primary>discos</primary>
       <secondary>memoria</secondary>
     </indexterm>
     <para>Esto incluye sistemas de ficheros en red como
       <link linkend="network-nfs">NFS</link> y Coda, sistemas de
       ficheros basados en memoria y sistemas de ficheros basados en
       fichero.</para>
 
     <para>Según la versión de &os; que utilice tendrá
       que utilizar diferentes herramientas para la creación y
       uso de sistemas de ficheros en memoria y sistemas de ficheros
       basados en fichero.</para>
 
     <note>
       <para>Los usuarios de FreeBSD&nbsp;4.X tendrán que usar
         &man.MAKEDEV.8; para crear los dispositivos requeridos.
         FreeBSD&nbsp;5.0 y posteriores usan &man.devfs.5; para
         gestionar los nodos de dispositivo correspondientes de forma
         transparente para el usuario.</para>
     </note>
 
     <sect2 id="disks-vnconfig">
 
       <title>Sistema de ficheros basado en fichero en FreeBSD&nbsp;4.X</title>
       <indexterm>
         <primary>discos</primary>
         <secondary>file-backed (4.X)</secondary>
       </indexterm>
 
       <para>La utilidad &man.vnconfig.8; configura y habilita vnodes
         de dispositivos de pseudodisco.  Un <firstterm>vnode</firstterm>
         es una representación de un fichero y es el enfoque de
         la actividad de fichero.  Esto significa que &man.vnconfig.8;
         utiliza ficheros para crear y operar un sistema de ficheros.
         Un uso posible es el montaje de imágenes de disquetes o CD
         almacenadas como ficheros.</para>
 
       <para>Para poder usar &man.vnconfig.8; necesitará tener
         &man.vn.4; en el fichero de configuración de su
         kernel:</para>
 
       <programlisting>pseudo-device vn</programlisting>
 
       <para>Para montar una imagen de un sistema de ficheros:</para>
 
       <example>
 	<title>Uso de vnconfig para montar una imagen de un sistema de
           ficheros bajo &os;&nbsp;4.X</title>
 
 	<screen>&prompt.root; <userinput>vnconfig vn<replaceable>0</replaceable> <replaceable>imagendedisco</replaceable></userinput>
 &prompt.root; <userinput>mount /dev/vn<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput></screen>
       </example>
 
       <para>Para crear una nueva imagen de un sistema de ficheros con
         &man.vnconfig.8;:</para>
 
       <example>
 	<title>Creación de una imagen nueva de un sistema de ficheros
           respaldado en un archivo con <command>vnconfig</command></title>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>nuevaimagen</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput>
 5120+0 records in
 5120+0 records out
 &prompt.root; <userinput>vnconfig -s labels -c vn<replaceable>0</replaceable> <replaceable>nuevaimagen</replaceable></userinput>
 &prompt.root; <userinput>disklabel -r -w vn<replaceable>0</replaceable> auto</userinput>
 &prompt.root; <userinput>newfs vn<replaceable>0</replaceable>c</userinput>
 Warning: 2048 sector(s) in last cylinder unallocated
 /dev/vn0c:     10240 sectors in 3 cylinders of 1 tracks, 4096 sectors
         5.0MB in 1 cyl groups (16 c/g, 32.00MB/g, 1280 i/g)
 super-block backups (for fsck -b #) at:
  32
 &prompt.root; <userinput>mount /dev/vn<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 /dev/vn0c        4927        1     4532     0%    /mnt</screen>
       </example>
     </sect2>
 
     <sect2 id="disks-mdconfig">
       <title>Sistemas de ficheros basados en fichero en
         FreeBSD&nbsp;5.X</title>
       <indexterm>
         <primary>discos</primary>
         <secondary>file-backed (5.X)</secondary>
       </indexterm>
 
       <para>&man.mdconfig.8; se usa para configurar y habilitar discos
         habilitar discos de memoria, &man.md.4;, en FreeBSD&nbsp;5.X.
         Para usar &man.mdconfig.8;, tendrá que cargar el módulo
         &man.md.4; o añadir soporte para el mismo el el fichero de
         configuración del kernel:</para>
 
       <programlisting>device md</programlisting>
 
       <para>&man.mdconfig.8; soporta tres tipos de discos virtuales
         en memoria: discos de memoria asignados mediante
         &man.malloc.9;, discos de memoria usando un fichero o
         espacio de swap como respaldo.  Un uso posible es
         montar imágenes de disquetes o CD archivadas.
         </para>
 
       <para>Para montar una imagen de un sistema de ficheros:</para>
 
       <example>
 	<title>Uso de <command>mdconfig</command> para montar una imagen
           de un sistema de ficheros en &os;&nbsp;5.X</title>
 
 	<screen>&prompt.root; <userinput>mdconfig -a -t vnode -f <replaceable>imagendedisco</replaceable> -u <replaceable>0</replaceable></userinput>
 &prompt.root; <userinput>mount /dev/md<replaceable>0</replaceable> <replaceable>/mnt</replaceable></userinput></screen>
       </example>
 
       <para>Para crear una imagen nueva de un sistema de ficheros
         con &man.mdconfig.8;:</para>
 
       <example>
 	<title>Creación de un disco respaldado en fichero
           con <command>mdconfig</command></title>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>nuevaimagen</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput>
 5120+0 records in
 5120+0 records out
 &prompt.root; <userinput>mdconfig -a -t vnode -f <replaceable>nuevaimagen</replaceable> -u <replaceable>0</replaceable></userinput>
 &prompt.root; <userinput>disklabel -r -w md<replaceable>0</replaceable> auto</userinput>
 &prompt.root; <userinput>newfs md<replaceable>0</replaceable>c</userinput>
 /dev/md0c: 5.0MB (10240 sectors) block size 16384, fragment size 2048
 	using 4 cylinder groups of 1.27MB, 81 blks, 256 inodes.
 super-block backups (for fsck -b #) at:
  32, 2624, 5216, 7808
 &prompt.root; <userinput>mount /dev/md<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 /dev/md0c        4846        2     4458     0%    /mnt</screen>
       </example>
 
       <para>Si no especifica el número de unidad con la
         opción <option>-u</option> &man.mdconfig.8;
         usará la designación automática de
         &man.md.4; para seleccionar un dispositivo sin usar.
         El nombre de la unidad designada se enviará a la salida
         esándar como <devicename>md4</devicename>.  Para más
         información sobre &man.mdconfig.8; consulte su página
         de manual.</para>
 
       <note><para>A partir de &os;&nbsp;5.1-RELEASE
         &man.bsdlabel.8; reemplazó a
         &man.disklabel.8;.  En &man.bsdlabel.8; se eliminaron muchas
         opciones y parámetros obsoletos.  En el ejemplo de
         arriba ignore la opción <option>-r</option>.
         Para más información consulte la página
         de manual de &man.bsdlabel.8;.</para></note>
 
       <para>&man.mdconfig.8; es muy útil, aunque requiere
         muchas líneas de comando para crear un sistema de ficheros
         basado en un fichero.  FreeBSD&nbsp;5.0 incorpora &man.mdmfs.8;,
         que configura un disco &man.md.4; utilizando
         &man.mdconfig.8;, pone un sistema de ficheros UFS en él
         mediante &man.newfs.8; y lo monta usando &man.mount.8;.
         Por ejemplo, si desea crear y montar la misma imagen de
         sistema de ficheros de arriba, simplemente teclée
         lo siguiente:</para>
 
       <example>
         <title>Configurar y montar un disco basado en un fichero con
           <command>mdmfs</command></title>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>nuevaimagen</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput>
 5120+0 records in
 5120+0 records out
 &prompt.root; <userinput>mdmfs -F <replaceable>newimage</replaceable> -s <replaceable>5</replaceable>m md<replaceable>0</replaceable> <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md0        4846    2  4458     0%    /mnt</screen>
       </example>
 
       <para>Si utiliza la opción <option>md</option> sin
         número de unidad, &man.mdmfs.8; usará la
         opción de auto unidad de &man.md.4; para
         selecionar automáticamente un dispositivo sin usar.  Para
         más información sobre &man.mdmfs.8;
         diríjase a la página de manual.</para>
 
     </sect2>
 
     <sect2 id="disks-md-freebsd4">
 
       <title>Sistemas de ficheros basados en memoria en FreeBSD&nbsp;4.X</title>
 
       <indexterm>
         <primary>discos</primary>
         <secondary>sistemas de ficheros en memoria (4.X)</secondary>
       </indexterm>
 
       <para>El controlador &man.md.4; es un modo sencillo y eficiente de
         crear sistemas de ficheros basados en memoria en FreeBSD&nbsp;4.X.
         &man.malloc.9; se usa para ubicar la memoria.</para>
 
       <para>Sencillamete toma un sistema de ficheros que usted ha
         preparado con, por ejemplo, &man.vnconfig.8;, y:</para>
 
       <example>
 	<title>Disco de memoria md en FreeBSD&nbsp;4.X</title>
 
 	<screen>&prompt.root; <userinput>dd if=<replaceable>nuevaimagen</replaceable> of=/dev/md<replaceable>0</replaceable></userinput>
 5120+0 records in
 5120+0 records out
 &prompt.root; <userinput>mount /dev/md<replaceable>0c</replaceable> <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 /dev/md0c        4927        1     4532     0%    /mnt</screen>
       </example>
 
       <para>Para más información por favor consulte
         la página de manual de &man.md.4;.</para>
     </sect2>
 
     <sect2 id="disks-md-freebsd5">
       <title>sistemas de ficheros basados en memoria en
         FreeBSD&nbsp;5.X</title>
       <indexterm>
         <primary>discos</primary>
         <secondary>sistemas de ficheros en memoria (5.X)</secondary>
       </indexterm>
 
       <para>Se usan las mismas herramientas para tratar con sistemas
         de ficheros basados en memoria o en ficheros:
         &man.mdconfig.8; o &man.mdmfs.8;.  El almacenamiento de
         sistemas de ficheros basados en memoria requiere el uso de
 	&man.malloc.9;.</para>
 
       <example>
 	<title>Creación de un nuevo disco basado en memoria con
 	  <command>mdconfig</command></title>
 
 	<screen>&prompt.root; <userinput>mdconfig -a -t malloc -s <replaceable>5</replaceable>m -u <replaceable>1</replaceable></userinput>
 &prompt.root; <userinput>newfs -U md<replaceable>1</replaceable></userinput>
 /dev/md1: 5.0MB (10240 sectors) block size 16384, fragment size 2048
 	using 4 cylinder groups of 1.27MB, 81 blks, 256 inodes.
 	with soft updates
 super-block backups (for fsck -b #) at:
  32, 2624, 5216, 7808
 &prompt.root; <userinput>mount /dev/md<replaceable>1</replaceable> <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md1        4846    2  4458     0%    /mnt</screen>
       </example>
 
       <example>
 	<title>Creación de un nuevo disco basado en memoria con
 	  <command>mdmfs</command></title>
 	<screen>&prompt.root; <userinput>mdmfs -M -s <replaceable>5</replaceable>m md<replaceable>2</replaceable> <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md2        4846    2  4458     0%    /mnt</screen>
       </example>
 
       <para>En lugar de usar un sistema de ficheros respaldado en
         &man.malloc.9;, es posible utilizar swap; lo único que
         debe hacer es sustituir <option>malloc</option> por
         <option>swap</option> en la línea de comando de
         &man.mdconfig.8;.  &man.mdmfs.8; por defecto
         (sin <option>-M</option>) crea un disco basado en swap).  Para
         más información, consulte las
         páginas de manual de &man.mdconfig.8; y de
         &man.mdmfs.8;.</para>
     </sect2>
 
     <sect2>
       <title>Desconexión del sistema de un disco de memoria</title>
       <indexterm>
         <primary>discos</primary>
         <secondary>desconectar un disco de memoria</secondary>
       </indexterm>
 
       <para>Cuando un sistema de ficheros basado en memoria o
         basado en fichero no se usa puede liberar recursos del sistema.
         Lo primero es desmontar el sistema de ficheros: use
         &man.mdconfig.8; para desconectar el disco del sistema y liberar
         dichos recursos.</para>
 
       <para>Por ejemplo, para desconectar y liberar todos los
         recursos usados por <filename>/dev/md4</filename>:</para>
 
       <screen>&prompt.root; <userinput>mdconfig -d -u <replaceable>4</replaceable></userinput></screen>
 
       <para>Es posible listar información sobre dispositivos
         &man.md.4; configurados en el sistema mediante
         <command>mdconfig -l</command>.</para>
 
       <para>En FreeBSD&nbsp;4.X se usa &man.vnconfig.8; para desconectar
         el dispositivo.  Por ejemplo, para desconectar y
         liberar todos los recursos usados por
         <filename>/dev/vn4</filename>:</para>
 
       <screen>&prompt.root; <userinput>vnconfig -u vn<replaceable>4</replaceable></userinput></screen>
 
 
     </sect2>
   </sect1>
 
   <sect1 id="snapshots">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Escrito por </contrib>
 	</author>
       </authorgroup>
       <!-- 15 JUL 2002 -->
     </sect1info>
 
     <title>Instantáneas (<quote>snapshots</quote>) de sistemas
       de ficheros</title>
 
     <indexterm>
       <primary>sistemas de ficheros</primary>
       <secondary>snapshots</secondary>
     </indexterm>
 
       <para>FreeBSD&nbsp;5.0 ofrece una característica relacionada
         con
         <link linkend="soft-updates">Soft Updates</link>: las
         instantáneas del sistema de ficheros.</para>
 
       <para>Las instantáneas permiten a un usuario crear
         imágenes de uno o más sistemas de ficheros dados, y
         tratarlas como un fichero.  Los ficheros de instantánea
         deben crearse en el sistema de ficheros en el que se realiza la
         acción, y un usuario puede crear hasta 20 (veinte)
         instantáneas por sistema de ficheros.  Las
         instantáneas activas se graban en el superbloque, lo que
         hace que sigan ahí independientemente de montajes,
         remontajes y reinicios del sistema.  Cuando ya no necesite
         una instantánea puede borrarla con &man.rm.1;.
         Las instantáneas pueden borrarse en cualquier orden pero
         puede que no pueda recuperar todo el espacio debido a que otra
         instantánea puede reclamar algunos bloques liberados.</para>
 
       <para>La bandera inalterable de fichero <option>snapshot</option>
         se activa con &man.mksnap.ffs.8; después de la creación
         inicial de un fichero de instantánea.  &man.unlink.1;
         hace una excepción con los ficheros de instantánea,
         ya que permite que se les borre.</para>
 
       <para>Las instantáneas se crean con &man.mount.8;.
         Veamos un ejemplo.  Vamos a colocar una instantánea de
         <filename>/var</filename> en
         <filename>/var/snapshot/snap</filename>:</para>
 
 <screen>&prompt.root; <userinput>mount -u -o snapshot /var/snapshot/snap /var</userinput></screen>
 
       <para>También puede usar &man.mksnap.ffs.8; para
         crear una instantánea:</para>
 
 <screen>&prompt.root; <userinput>mksnap_ffs /var /var/snapshot/snap</userinput></screen>
 
       <para>Si busca ficheros de instantánea en un sistema de
         de ficheros (por ejemplo <filename>/var</filename>) puede usar
         &man.find.1;:</para>
 
 <screen>&prompt.root; <userinput>find /var -flags snapshot</userinput></screen>
 
       <para>Una instantánea tiene distintos usos:</para>
 
       <itemizedlist>
 	<listitem>
           <para>Algunos administradores usan un fichero de
             instantánea como respaldo, puesto que la instantánea
             puede guardarse en CD o cinta.</para>
 	</listitem>
 
 	<listitem>
           <para>Integridad de ficheros; &man.fsck.8; puede ejecutarse
             en una instantánea.  Asumiendo que el sistema de
             ficheros estuviera limpio cuando se montó se debe
             obtener un resultado limpio (e intacto).  En esencia el
             proceso &man.fsck.8; hace esto mismo en segundo plano.</para>
 	</listitem>
 
 	<listitem>
           <para>Ejecución de &man.dump.8; en la instantánea.
             Se obtendrá un dump consistente con el sistema de
             ficheros y los sellos de hora de la instantánea.
             &man.dump.8; también puede leer una instantánea,
             crear una imagen dump y eliminar la instantánea en
             un comando usando la opción
             <option>-L</option>.</para>
 	</listitem>
 
 	<listitem>
           <para>Ejecutar un &man.mount.8; contra la instantánea
             como una imagen congelada del sistema de ficheros.
             Para montar la instantánea
             <filename>/var/snapshot/snap</filename> ejecute:</para>
 
 <screen>&prompt.root; <userinput>mdconfig -a -t vnode -f /var/snapshot/snap -u 4</userinput>
 &prompt.root; <userinput>mount -r /dev/md4 /mnt</userinput></screen>
 
 	</listitem>
       </itemizedlist>
 
       <para>Podrá recorrer la jerarquía de su sistema de
         ficheros <filename>/var</filename> congelado montado en
         <filename>/mnt</filename>.  Todo estará en el mismo estado
         en el que estaba cuando creó la instantánea.
         La única excepción es que cualquier
         instantánea anterior aparecerá como un fichero
         de longitud cero.  Cuando haya acabado de usar una
         instantánea puede desmontarla con:</para>
 
 <screen>&prompt.root; <userinput>umount /mnt</userinput>
 &prompt.root; <userinput>mdconfig -d -u 4</userinput></screen>
 
       <para>Para más información sobre
         <option>softupdates</option> e instantáneas de sistemas
         ficheros, incluyendo textos técnicos, visite el sitio
         web de Marshall Kirk McKusick:
 	<ulink url="http://www.mckusick.com/"></ulink>.</para>
   </sect1>
 
   <sect1 id="quotas">
     <title>Cuotas en sistemas de ficheros</title>
     <indexterm>
       <primary>contabilidad</primary>
       <secondary>espacio en disco</secondary>
     </indexterm>
     <indexterm><primary>cuotas de disco</primary></indexterm>
 
     <para>Las cuotas son una opción del sistema
       operativo que le permite limitar la cantidad de espacio en
       disco y/o el número de fichero que un usuario o
       miembros de un grupo pueden crear en el sistema, pudiendo
       además hacerlo de forma independiente en cada sistema de
       ficheros.
       Suele usarse principalmente en sistemas de tiempo compartido,
       donde se busca limitar la cantidad de recursos que cualquier
       usuario o grupo pueden utilizar.
       Esto evitará que un usuario o un grupo de usuarios
       consuma todos el espacio disponible en disco.</para>
 
     <sect2>
       <title>Configuración del sistema para habilitar
        cuotas de disco</title>
 
       <para>Antes de intentar configurar el uso de cuotas de disco
         hay que asegurarse de que las cuotas están activadas en el
         kernel.  La siguiente línea debe estar en el fichero de
         de configuración del kernel:</para>
 
       <programlisting>options QUOTA</programlisting>
 
       <para>El kernel <filename>GENERIC</filename> no lo tiene activado
         por defecto, así que tendrá que configurar,
         compilar e instalar un kernel personalizado para
         poder usar cuotas de disco.  Por favor, consulte el
         <xref linkend="kernelconfig"/> para más información
         sobre la configuración del kernel.</para>
 
       <para>A continuación tendrá que habilitar
         las cuotas de disco en <filename>/etc/rc.conf</filename>.
         Añadale la siguiente línea:</para>
 
       <programlisting>enable_quotas="YES"</programlisting>
       <indexterm>
         <primary>cuotas de disco</primary>
         <secondary>revisión</secondary>
       </indexterm>
 
       <para>Hay una variable que le permitirá efectuar un
         control más exhaustivo sobre el arranque de cuotas.
         Normalmente se revisa la integridad de cuotas de cada sistema
         de ficheros en el arranque; el responsable es
         &man.quotacheck.8;.  &man.quotacheck.8; se asegura de que los
         datos que hay en su base de datos de cuotas reflejen
         realmente los datos del sistema de ficheros.  Es un proceso
         que lleva mucho tiempo y que afectará significativamente
         al tiempo que tardará su sistema en arrancar.  Si desea
         saltarse ese paso puede usar una variable al efecto en
         <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>check_quotas="NO"</programlisting>
 
       <para>Para concluir tendrá que editar
         <filename>/etc/fstab</filename> para habilitar las cuotas de disco
         para cada sistema de ficheros.  Es aquí donde podrá
         habilitar cuotas por usuario, por grupo, o ambos en todos sus
         sistemas de ficheros.</para>
 
       <para>Para habilitar cuotas por usuario en un sistema de
         ficheros añada la opción <option>userquota</option> al
         campo de opciones en la entrada de <filename>/etc/fstab</filename>
         que corresponda al sistema de ficheros en el que quiere habilitar
         las cuotas.  Veamos un ejemplo:</para>
 
       <programlisting>/dev/da1s2g   /home    ufs rw,userquota 1 2</programlisting>
 
       <para>En el caso de las cuotas de grupo es muy similar.
         Use la opción <option>groupquota</option> en lugar
         de <option>userquota</option>.  Para habilitar
         cuotas por usuario y por grupo modifique la entrada
         de este modo:</para>
 
       <programlisting>/dev/da1s2g    /home    ufs rw,userquota,groupquota 1 2</programlisting>
 
       <para>Por defecto los ficheros de cuota se guardan en
         el directorio raíz del sistema de ficheros con los
         nombres <filename>quota.user</filename> y
         <filename>quota.group</filename>
         para cuotas de usuario y grupo respectivamente.
         Consulte &man.fstab.5; para más información.
         Aunque la página de manual de &man.fstab.5; diga que puede
         especificar otra ubicación para los ficheros de
         cuota, no se recomienda hacerlo debido a que las diversas herramientas
         de gestió cuotas no parecen sobrellevar esto
         adecuadamente.</para>
 
       <para>Hecho todo esto puede reiniciar su sistema con el nuevo
         kernel.  <filename>/etc/rc</filename> ejecutará
         automáticamente los comandos apropiados para crear los
         ficheros de cuota iniciales que requieran todas las entradas en
         en <filename>/etc/fstab</filename>, así que no hay
         necesidad de crear ficheros de cuota de longitud cero.</para>
 
       <para>En el curso normal de operaciones no se le debería
         pedir que ejecute &man.quotacheck.8;, &man.quotaon.8; o
         &man.quotaoff.8; manualmente.  Sin embargo, tal vez quiera leer
         sus páginas de manual para familiarizarse con su
         funcionamiento.</para>
     </sect2>
 
     <sect2>
       <title>Configuración de límites de cuota</title>
       <indexterm>
         <primary>cuotas de disco</primary>
         <secondary>límites</secondary>
       </indexterm>
 
       <para>Una vez que tenga configurado su sistema para usar cuotas
         verifique que en realidad estén habilitadas.  Una manera
         sencilla de hacer esto es ejecutar:</para>
 
       <screen>&prompt.root; <userinput>quota -v</userinput></screen>
 
       <para>Debe ver un resumen de una sola línea de uso del
         disco y los límites de cuota actuales para cada sistema
         de ficheros donde estén habilitadas las cuotas.</para>
 
       <para>Ahora puede iniciar la asignación
         de límites de cuota con &man.edquota.8;.</para>
 
       <para>Tiene varias opciones para imponer límites en el
         espacio de disco que un usuario o grupo puede ocupar, y
         cuántos ficheros pueden crear.  Puede limitar el uso de
         disco basándose en el espacio en disco (cuotas de bloque) o
         en el número de ficheros (cuotas de inodo) o una
         combinación de ambas.  Cada uno de estos límites
         a su vez se divide en dos categorías: límites
         duros y suaves.</para>
 
       <indexterm><primary>límite duro</primary></indexterm>
       <para>Un límite duro no puede ser excedido.  Una vez que
         un usuario alcanza su límite duro no puede realizar
         más ubicaciones en el sistema de ficheros en cuestión.
         Por ejemplo, si el usuario tiene un límite duro de
         500 kbytes en un sistema de ficheros y está utilizando
         490 kbytes, el usuario solo puede ocupar
         otros 10 kbytes.  Un intento de ocupar 11 kbytes más
         fallará.</para>
 
       <indexterm><primary>límite suave</primary></indexterm>
       <para>Los límites suaves pueden excederse por un periodo
         Este periodo de tiempo recibe el nombre de periodo de gracia, que
         por defecto es una semana.  Si un usuario sobrepasa su periodo de
         gracia el límite suave se convertirá en
         un límite duro y no se permitir&acute;n usos de disco
         adicionales.  Cuando el usuario devuelve su cuota de uso de
         recursos a un punto por debajo de su límite suave
         el periodo de gracia se reinicia.</para>
 
       <para>Veamos un ejemplo de uso de &man.edquota.8;.
         Si se usa &man.edquota.8; se entra en el el editor declarado en
         la variable de entorno
         <envar>EDITOR</envar>, o en el editor <application>vi</application>
         si no ha modificado el valor por defecto de la variable
         <envar>EDITOR</envar>, para que pueda editar los
         límites de cuota.</para>
 
       <screen>&prompt.root; <userinput>edquota -u test</userinput></screen>
 
       <programlisting>Quotas for user test:
 /usr: kbytes in use: 65, limits (soft = 50, hard = 75)
         inodes in use: 7, limits (soft = 50, hard = 60)
 /usr/var: kbytes in use: 0, limits (soft = 50, hard = 75)
         inodes in use: 0, limits (soft = 50, hard = 60)</programlisting>
 
       <para>Debería ver dos líneas por cada sistema
         de ficheros que tenga habilitadas las cuotas.  Una línea
         para los límites de bloque y una línea para
         límites de inodo. Por ejemplo, para elevar los límites
         de este usuario de un límite suave de 50 y un límite
         duro de 75 a un límite suave de 500 y un límite
         duro de 600, cambie:</para>
 
       <programlisting>/usr: kbytes in use: 65, limits (soft = 50, hard = 75)</programlisting>
 
       <para>por:</para>
 
       <programlisting>/usr: kbytes in use: 65, limits (soft = 500, hard = 600)</programlisting>
 
       <para>Los nuevos límites de cuota se aplicarán en
         cuanto salga del editor.</para>
 
       <para>Algunas veces se quieren activar límites de cuota
         en un rango de UIDs. Esto puede realizarse con la opción
         <option>-p</option> de &man.edquota.8;. Primero asigne el
         límite de cuota deseado a un usuario y luego
         ejecute
         <command>edquota -p protouser startuid-enduid</command>.  Por
         ejemplo, si el usuario <username>test</username> tiene el
         límite de cuota deseado, el siguiente comando puede
         usarse para duplicar esos límites de cuota para los
         UIDs de 10,000 hasta 19,999:</para>
 
       <screen>&prompt.root; <userinput>edquota -p test 10000-19999</userinput></screen>
 
       <para>Para más información consulte la página de
         manual &man.edquota.8;.</para>
     </sect2>
 
     <sect2>
       <title>Revisión de los límites de cuota y
         uso de disco</title>
       <indexterm>
         <primary>cuotas de disco</primary>
         <secondary>revisando</secondary>
       </indexterm>
 
       <para>Puede usar &man.quota.1; o
         &man.repquota.8; para revisar los límites de
         cuota y uso del disco.  El comando &man.quota.1;
         le permitirá revisar cuotas individuales de
         usuario o grupo y uso del disco.  Un usuario puede
         sólamente examinar su propia cuota y la cuota de un
         grupo al que pertenezca.  Sólamente el superusuario
         puede ver las cuotas de todos los usuarios y grupos.
         &man.repquota.8; permite obtener
         un resumen de todas las cuotas y uso del disco de todos los
         sistemas de ficheros con cuotas habilitadas.</para>
 
       <para>En el siguiente ejemplo vemos la salida de
         <command>quota -v</command> para un usuario
         que tiene límites de cuota en dos sistemas
         de ficheros.</para>
 
       <programlisting>Disk quotas for user test (uid 1002):
      Filesystem  usage    quota   limit   grace   files   quota   limit   grace
            /usr      65*     50      75   5days       7      50      60
        /usr/var       0      50      75               0      50      60</programlisting>
 
       <indexterm><primary>periodo de gracia</primary></indexterm>
       <para>En el sistema de ficheros <filename>/usr</filename> del
         ejemplo este usuario está actualmente
         15 kbytes sobre su límite suave de 50 kbytes y le quedan 5
         días de su periodo de gracia.  Observe el asterisco,
         <literal>*</literal> que indica que el usuario está
         actualmente por encima de su límite de cuota.</para>
 
       <para>Normalmente los sistemas de ficheros en los que el usuario
         no esté utilizando espacio en disco no se mostrarán
         en la salida del comando &man.quota.1;, incluso si tiene
         un límite de cuota asignado para esos sistemas
         de fichero.  La opción <option>-v</option>
         desplegará esos sistemas de ficheros, en nuestro ejemplo
         el sistema de ficheros <filename>/usr/var</filename>.</para>
     </sect2>
 
     <sect2>
       <title>Cuotas en NFS</title>
       <indexterm><primary>NFS</primary></indexterm>
 
       <para>Las cuotas son impuestas por el subsistema de cuotas en el
         servidor NFS.  El d&aelig;mon &man.rpc.rquotad.8; facilita la
         información a &man.quota.1; en los clientes
         NFS, permitiéndoles a los usuarios de esas máquinas
         ver sus estadísticas de cuota.</para>
 
       <para>Habilite  <command>rpc.rquotad</command> en
 	<filename>/etc/inetd.conf</filename> del siguiente modo:</para>
 
       <programlisting>rquotad/1      dgram rpc/udp wait root /usr/libexec/rpc.rquotad rpc.rquotad</programlisting>
 
       <para>Y reinicie <command>inetd</command>:</para>
 
       <screen>&prompt.root; <userinput>kill -HUP `cat /var/run/inetd.pid`</userinput></screen>
     </sect2>
   </sect1>
 
 
   <sect1 id="disks-encrypting">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Lucky</firstname>
 	  <surname>Green</surname>
 	  <contrib>Escrito por </contrib>
 	  <affiliation>
 	    <address><email>shamrock@cypherpunks.to</email></address>
 	  </affiliation>
 	</author>
       </authorgroup>
       <!-- 11 MARCH 2003 -->
     </sect1info>
 
     <title>Cifrado de particiones de disco</title>
     <indexterm>
       <primary>discos</primary>
       <secondary>cifrado</secondary></indexterm>
 
     <para>&os; ofrece un alto grado de protección
       contra el acceso no autorizado a los datos.  Los Permisos de fichero
       y MAC (Mandatory Access Control, controles de acceso obligatorio,
       consulte el <xref linkend="mac"/>) ayudan a evitar que otros
       tengan acceso no autorizado a los datos mientras el sistema
       operativo está funcionando y la computadora está
       encendida.  Sin embargo los permisos impuestos por el
       sistema operativo son irrelevantes si un atacante tiene acceso
       físico al sistema y puede simplemente mover el disco
       duro de la computadora a otro sistema para copiar
       y analizar datos sensibles.</para>
 
     <para>Independientemente de cómo un atacante pueda
       conseguir acceso a un disco duro a a un sistema apagado,
       <application>el cifrado de disco basado en GEOM
       (GEOM Based Disk Encryption, gbde)</application> puede proteger
       los datos de los sistemas de ficheros del sistema incluso
       contra atacantes muy decididos y con recursos adecuados a
       su disposición.   A diferencia de otros métodos de
       cifrado más difíciles de usar, que cifran
       únicamente ficheos individuales,
       <application>gbde</application> cifra sistemas de ficheros
       completos de forma transparente.  Ni un solo texto en limpio
       llega a tocar el disco duro.</para>
 
     <sect2>
       <title>Habilitar gbde en el kernel</title>
 
       <procedure>
 	<step>
 	  <title>Conviértase en <username>root</username></title>
 
           <para>La configuración de <application>gbde</application>
             requiere privilegios de superusuario.</para>
 
 	  <screen>&prompt.user; <userinput>su -</userinput>
 Password:</screen>
 	</step>
 
 	<step>
           <title>Verifique la versión del sistema operativo</title>
 
 	  <para>&man.gbde.4; requiere FreeBSD 5.0 o posterior.</para>
 
 	  <screen>&prompt.root; <userinput>uname -r</userinput>
 5.0-RELEASE</screen>
 	</step>
 
 	<step>
           <title>Añada soporte de &man.gbde.4; al fichero de
             configuración de su kernel</title>
 
           <para>Añada la siguiente línea al fichero de
             configuración de su kernel con el editor que
             prefiera:</para>
 
 	  <para><literal>options GEOM_BDE</literal></para>
 
           <para>Configure, recompile e instale el kernel de &os;.
             Este proceso se detalla en el
             <xref linkend="kernelconfig"/>.</para>
 
 	  <para>Reinicie con el nuevo kernel.</para>
 	</step>
       </procedure>
     </sect2>
 
 
     <sect2>
       <title>Preparación del disco duro cifrado</title>
 
       <para>El siguiente ejemplo asume que añade a su sistema
         un disco duro nuevo que contendrá una sola
         partición cifrada.  Esta partición se
         montará como <filename>/private</filename>.
         <application>gbde</application> puede usarse también
         para cifrar <filename>/home</filename> y
         <filename>/var/mail</filename>,
         pero esto requeriría instrucciones más complejas que
         las que se pretenden dar en esta introducción.</para>
 
       <procedure>
 	<step>
 	  <title>Añada el nuevo disco</title>
 
           <para>Instale el nuevo disco en el sistema como se explicó
             en la <xref linkend="disks-adding"/>.  En nuestro ejemplo hemos
             añadido una nueva partición de disco como
             <filename>/dev/ad4s1c</filename>.  Los dispositivos
             <filename>/dev/ad0s1<replaceable>*</replaceable></filename>
             representan particiones &os; estándar que i
             existían previamente en el sistema.</para>
 
 	  <screen>&prompt.root; <userinput>ls /dev/ad*</userinput>
 /dev/ad0        /dev/ad0s1b     /dev/ad0s1e     /dev/ad4s1
 /dev/ad0s1      /dev/ad0s1c     /dev/ad0s1f     /dev/ad4s1c
 /dev/ad0s1a     /dev/ad0s1d     /dev/ad4</screen>
 	</step>
 
 	<step>
           <title>Crée un directorio para los ficheros
             <quote>lock</quote> de gbde</title>
 
 	  <screen>&prompt.root; <userinput>mkdir /etc/gbde</userinput></screen>
 
           <para>Los ficheros <quote>lock</quote> de
             <application>gbde</application>
             contienen información que <application>gbde</application>
             requiere para acceder a las particiones cifradas.   Sin el
             acceso a los ficheros <quote>lock</quote>
             <application>gbde</application> no podrá descifrar los
             datos alojados en la partición cifrada sin una cantidad
             significativa de trabajo, tarea para la que además
             no le resultará de ayuda este software.  Cada
             partición cifrada utiliza un fichero
             <quote>lock</quote> separado.</para>
 	</step>
 
 	<step>
 	  <title>Inicialice la partición gbde</title>
 
           <para>Una partición <application>gbde</application>
             debe inicializarse antes de que pueda utilizarse.
             Esta inicialización sólo debe hacerse
             una vez:</para>
 
 	  <screen>&prompt.root; <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c</userinput></screen>
 
           <para>&man.gbde.8; abrirá su editor para que pueda
             configurar las opciones de configuración que se
             le presentarán en una plantilla.
             Para utilizar UFS1 o UFS2, ponga el sector_size a 2048:</para>
 
 	  <programlisting>$<!-- This is not the space you are looking
 for-->FreeBSD: src/sbin/gbde/template.txt,v 1.1 2002/10/20 11:16:13 phk Exp $
 #
 # El tamaño de sector (sector size) es la unidad de datos más
 # pequeña que podrá leer o escribir.  Si la elige demasiado
 # pequeña reducirá el rendimiento y la cantidad de espacio
 # útil.  Si la elige demasiado grande puede hacer que los sistemas
 # de ficheros no funcionen.  512 es el tamaño mínimo y
 # siempre funciona.  Si va a usar UFS utilice
 #
 sector_size     =       2048
 [...]
 </programlisting>
 
           <para>&man.gbde.8; le pedirá dos veces que escriba la
             contraseña que debe usarse para asegurar los datos.
             La contraseña debe ser la misma las dos veces.  La
             capacidad de <application>gbde</application> de proteger sus
             datos depende íntegramente de la calidad de la
             contraseña que elija.
 	  <footnote>
           <para>Si quiere ayuda para seleccionar una contraseña
             segura que además sea fácil de recordar visite
             el sitio web
             <ulink url="http://world.std.com/~reinhold/diceware.html">Diceware
             Passphrase</ulink>.</para></footnote></para>
 
           <para>El fichero <command>gbde init</command> crea un fichero
             <quote>lock</quote> para su partición
             <application>gbde</application>, que en nuestro ejemplo
             está en
 	    <filename>/etc/gbde/ad4s1c</filename>.</para>
 
 	  <caution>
             <para>Es imprescindible que los ficheros <quote>lock</quote>
               de <application>gbde</application>
               <emphasis>deben</emphasis> respaldarse junto con
               el contenido de cualquier partición cifrada.
               Aunque la sola acció de borrar
               un fichero <quote>lock</quote> no puede evitar que un atacante
               motivado descifre una partición
               <application>gbde</application> sin el fichero
               <quote>lock</quote>, el propietario legítimo
               no podrá acceder a los datos en la partición
               cifrada sin una cantidad notable de trabajo, que es
               necesario señalar que no entra dentro de las funciones
               de &man.gbde.8; ni de su diseñador.</para>
 	  </caution>
 	</step>
 
 	<step>
           <title>Conecte al kernel la partición cifrada</title>
 
 	  <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c</userinput></screen>
 
           <para>Se le pedirá la contraseña que elijió
             al inicializar la partición cifrada.  El
             nuevo dispositivo cifrado aparecerá en
             <filename>/dev</filename> como
 	    <filename>/dev/nombre_de_dispositivo.bde</filename>:</para>
 
 	  <screen>&prompt.root; <userinput>ls /dev/ad*</userinput>
 /dev/ad0        /dev/ad0s1b     /dev/ad0s1e     /dev/ad4s1
 /dev/ad0s1      /dev/ad0s1c     /dev/ad0s1f     /dev/ad4s1c
 /dev/ad0s1a     /dev/ad0s1d     /dev/ad4        /dev/ad4s1c.bde</screen>
 	</step>
 
 	<step>
           <title>Crée un sistema de ficheros en el dispositivo
             cifrado</title>
 
           <para>Una vez el dispositivo cifrado está conectado
             al kernel puede crear un sistema de ficheros en el
             dispositivo con &man.newfs.8;.  Dado que es más
             rápido inicializar un sistema de ficheros del
             nuevo UFS2 que un sistema de ficheros del tradicional
             UFS1, le recomendamos encarecidamente usar
             &man.newfs.8; con la opción
             <option>-O2</option>.</para>
 
           <note><para>La opción <option>-O2</option> es el
             valor por defecto en &os;&nbsp;5.1-RELEASE
             y siguientes.</para></note>
 
 	  <screen>&prompt.root; <userinput>newfs -U -O2 /dev/ad4s1c.bde</userinput></screen>
 
 	  <note>
             <para>&man.newfs.8; debe ejecutarse en una
               partición <application>gbde</application>
               conectada, que podrá identificar por la extensión
 	      <filename><replaceable>*</replaceable>.bde</filename>
               del nombre del dispositivo.</para>
 	  </note>
 	</step>
 
 	<step>
           <title>Montar la partición cifrada</title>
 
           <para>Crée un punto de montaje para el sistema cifrado
             de ficheros.</para>
 
 	  <screen>&prompt.root; <userinput>mkdir /private</userinput></screen>
 
           <para>Montar el sistema cifrado de ficheros.</para>
 
 	  <screen>&prompt.root; <userinput>mount /dev/ad4s1c.bde /private</userinput></screen>
 	</step>
 
 	<step>
           <title>Verificar que el sistema cifrado de ficheros esté
             disponible</title>
 
           <para>el sistema cifrado de ficheros debería ser visible
             para &man.df.1; y estar listo para su uso.</para>
 
 	  <screen>&prompt.user; <userinput>df -H</userinput>
 Filesystem        Size   Used  Avail Capacity  Mounted on
 /dev/ad0s1a      1037M    72M   883M     8%    /
 /devfs            1.0K   1.0K     0B   100%    /dev
 /dev/ad0s1f       8.1G    55K   7.5G     0%    /home
 /dev/ad0s1e      1037M   1.1M   953M     0%    /tmp
 /dev/ad0s1d       6.1G   1.9G   3.7G    35%    /usr
 /dev/ad4s1c.bde   150G   4.1K   138G     0%    /private</screen>
 	</step>
       </procedure>
     </sect2>
 
     <sect2>
       <title>Montaje de sistemas cifrados de ficheros</title>
 
       <para>Todos los sistemas cifrados de ficheros deben reconectarse al
         kernel después de cada arranque.  Además, antes de
         poder utilizarlo debe revisarlo por si contuviera errores y montarlo.
         Todo el proceso debe ser ejecutado por el usuario
         <username>root</username>.</para>
 
       <procedure>
 	<step>
           <title>Conectar la partición gbde al kernel</title>
 
 	  <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c</userinput></screen>
 
           <para>Se le pedirá la contraseña que
             elijió en la inicialización
             de la partición cifrada gbde.</para>
 	</step>
 
 	<step>
           <title>Revisión de errores en el sistema de ficheros</title>
 
           <para>Como que los sistemas cifrados de ficheros no pueden
             aparecer en <filename>/etc/fstab</filename> (lo que haría
             que fueran montados automáticamente), los sistemas
             de ficheros deben revisarse manualmente mediante &man.fsck.8;
             antes de montarlos.</para>
 
 	  <screen>&prompt.root; <userinput>fsck -p -t ffs /dev/ad4s1c.bde</userinput></screen>
 	</step>
 
 	<step>
           <title>Montar los sistemas cifrados de ficheros</title>
 
 	  <screen>&prompt.root; <userinput>mount /dev/ad4s1c.bde /private</userinput></screen>
 
           <para>El sistema cifrado de ficheros está listo para su
             uso.</para>
 	</step>
       </procedure>
 
       <sect3>
         <title>Montar automáticamente particiones cifradas</title>
 
         <para>Es posible usar un <quote>script</quote> para automatizar
           la conexión, revisión y el montaje de una
           partición cifrada, pero por razones de seguridad el
           <quote>script</quote> no debe contener la
           contraseña de &man.gbde.8;.  Se recomienda
           ejecutar esos <quote>scripts</quote> se ejecuten de forma manual
           proporcionando la contraseña vía consola o
           &man.ssh.1;.</para>
       </sect3>
     </sect2>
 
       <sect2>
         <title>Protección criptográfica que usa gbde</title>
 
         <para>&man.gbde.8; cifra el XXX sector payload usando AES de 128 bits
           en modo CBC.  Cada sector en el disco se cifra con una clave
           AES diferente.  Para más información sobre el
           diseño criptográfico de
           <application>gbde</application>, incluyendo cómo se
           derivan las claves de sector a partir de la contraseña
           consulte &man.gbde.4;.</para>
       </sect2>
 
       <sect2>
         <title>Problemas de compatibilidad</title>
 
         <para>&man.sysinstall.8; es incompatible con dispositivos
           <application>gbde</application> cifrados.  Todos los
           dispositivos <devicename><replaceable>*</replaceable>.bde</devicename>
           deben desconectarse del kernel antes de iniciar
           &man.sysinstall.8; o se <quote>congelará</quote> durante
           la prueba inicial de dispositivos.  Para desconectar el
           el dispositivo cifrado de nuestro ejemplo haga lo siguiente:
           </para>
 
 	<screen>&prompt.root; <userinput>gbde detach /dev/ad4s1c</userinput></screen>
 
       <para>Tenga en cuenta también que, como &man.vinum.4; no
         utiliza el subsistema &man.geom.4;, no es posible usar
         <application>gbde</application> en volúmenes
 	<application>vinum</application>.</para>
       </sect2>
 
   </sect1>
 </chapter>
diff --git a/hu_HU.ISO8859-2/books/handbook/install/chapter.xml b/hu_HU.ISO8859-2/books/handbook/install/chapter.xml
index 99694a019f..38b1fab9c7 100644
--- a/hu_HU.ISO8859-2/books/handbook/install/chapter.xml
+++ b/hu_HU.ISO8859-2/books/handbook/install/chapter.xml
@@ -1,7186 +1,7186 @@
 <?xml version="1.0" encoding="iso-8859-2"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <!-- The FreeBSD Hungarian Documentation Project
      Translated by: PALI, Gabor <pgj@FreeBSD.org>
      %SOURCE%	en_US.ISO8859-1/books/handbook/install/chapter.xml
      %SRCID%	1.413
 -->
 
 <chapter id="install" lang="hu">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Átszervezte, átrendezte és egyes
 	  részeit átdolgozta: </contrib>
       </author>
     </authorgroup>
 
     <authorgroup>
       <author>
 	<firstname>Randy</firstname>
 	<surname>Pratt</surname>
 	<contrib>A sysinstall bemutatása, ábrái
 	  és bemásolása: </contrib>
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>A &os; telepítése</title>
 
   <sect1 id="install-synopsis">
     <title>Áttekintés</title>
 
     <indexterm><primary>telepítés</primary></indexterm>
 
     <para>A &os; telepítéséhez egy könnyen
       használható szöveges
       telepítõprogram, a
       <application>sysinstall</application> használható.
       Ez a &os; alapértelmezett telepítõprogramja,
       habár ezt a különféle
       gyártók kedvük szerint lecserélhetik.
       Ebben a fejezetben bemutatjuk a &os;
       <application>sysinstall</application>
       segítségével történõ
       telepítését.</para>
 
     <para>A fejezet elolvasása során
       megismerjük:</para>
 
     <itemizedlist>
       <listitem>
 	<para>hogyan készítsünk
 	  telepítõlemezeket a &os;-hez;</para>
       </listitem>
 
       <listitem>
 	<para>a &os; miként hivatkozza és osztja fel a
 	  merevlemezeinket;</para>
       </listitem>
 
       <listitem>
 	<para>hogyan indítsuk el a
 	  <application>sysinstall</application> programot;</para>
       </listitem>
 
       <listitem>
 	<para>milyen kérdéseket tesz fel nekünk a
 	  <application>sysinstall</application>, mire gondol, hogyan is
 	  kell azokat megválaszolni.</para>
       </listitem>
     </itemizedlist>
 
     <para>A fejezet elolvasásához ajánlott:</para>
 
     <itemizedlist>
       <listitem>
 	<para>a telepítendõ &os; verzióhoz
 	  tartozó támogatott hardvereket felsoroló
 	  lista átolvasása és benne a saját
 	  hardvereszközeink megkeresése.</para>
       </listitem>
     </itemizedlist>
 
     <note>
       <para>Általánosan elmondható, hogy a most
 	következõ telepítési
 	utasítások az &i386; (<quote>PC
 	kompatibilis</quote>) architektúrájú
 	számítógépekre vonatkoznak.  Ahol
 	erre szükség van, ott más platformokra
 	vonatkozó utasítások is szerepelhetnek.
 	Habár ezt a leírás igyekszünk a
 	lehetõ legjobban naprakészen tartani,
 	elképzelhetõ, hogy felfedezhetünk kisebb
 	eltéréseket a telepítõben és az
 	itt leírtak közt.  Ezért ezt a fejezetet
 	inkább egy általános
 	útmutatónak javasoljuk, nem pedig egy szó
 	szerint értelmezendõ
 	kézikönyvként.</para>
     </note>
 
   </sect1>
 
   <sect1 id="install-hardware">
     <title>Hardverkövetelmények</title>
 
     <sect2 id="install-hardware-minimal">
       <title>Minimális konfiguráció</title>
 
       <para>A &os; telepítéséhez
 	szükséges minimális
 	konfiguráció &os; verziónként
 	és architektúránként
 	eltérõ.</para>
 
       <para>A minimális konfigurációt a &os;
 	honlapján a <ulink
 	url="http://www.FreeBSD.org/releases/index.html">kiadásokról
 	szóló oldalon</ulink>, az <quote>Installation
 	Notes</quote> részben találhatjuk meg.  Ezt a
 	következõ szakaszokban foglaljuk össze.  A &os;
 	telepítésének
 	módszerétõl függõen
 	szükségünk lehet egy hajlékonylemezes
 	(floppy) vagy CD-ROM meghajtóra, esetleg egy
 	hálózati kártyára.  Ezt a <xref
 	  linkend="install-boot-media"/>ban tárgyaljuk.</para>
 
       <sect3>
 	<title>&os;/&arch.i386; és &os;/&arch.pc98;</title>
 
 	<para>A &os;/&arch.i386; és &os;/&arch.pc98;
 	  egyaránt egy 486 vagy jobb processzort és
 	  legalább 24&nbsp;MB memóriát
 	  igényel.  A legkisebb telepítéshez
 	  legalább 150&nbsp;MB szabad lemezterület
 	  szükséges.</para>
 
 	<note>
 	  <para>Régebbi konfigurációk esetén
 	    nem egy gyorsabb processzor, hanem inkább több
 	    memória beszerzése, illetve több
 	    lemezterület felszabadítása a
 	    fontosabb.</para>
 	</note>
 
       </sect3>
 
       <sect3>
 	<title>&os;/&arch.alpha;</title>
 
 	<indexterm><primary>Alpha</primary></indexterm>
 
 	<note>
 	  <para>Az Alpha támogatás a &os;&nbsp;7.0
 	    beindulásával
 	    eltávolításra került.  A
 	    &os;&nbsp;6.<replaceable>X</replaceable> sorozat az
 	    utolsó, amely valamilyen támogatást
 	    ajánl ehhez az architektúrához.  Ezzel
 	    kapcsolatban részletesebben a <ulink
 	      url="http://www.FreeBSD.org/releases/index.html">kiadásokkal</ulink>
 	    kapcsolatos információkat tartalmazó
 	    oldalon olvashatunk a &os; honlapján.</para>
 	</note>
       </sect3>
 
       <sect3>
 	<title>&os;/&arch.amd64;</title>
 
 	<para>Két típusú processzor képes
 	  futtatni a &os;/&arch.amd64; verzióját.  Az
 	  elsõ ezek közül az AMD64 processzorok,
 	  beleértve az &amd.athlon;64, &amd.athlon;64-FX,
 	  &amd.opteron; vagy újabb processzorokat.</para>
 
 	<para>A &os;/&arch.amd64; verzióját
 	  kihasználni képes processzorok másik
 	  csoportja az &intel; EM64T
 	  architektúrájára épülõ
 	  processzorok.  Ilyen processzor például az
 	  &intel;&nbsp;&core;&nbsp;2 Duo, Quad és Extreme
 	  processzorcsaládok, valamint az &intel;&nbsp;&xeon;
 	  3000, 5000 és 7000 sorozatszámú
 	  processzorai.</para>
 
 	<para>Ha nVidia nForce3 Pro-150 alapú géppel
 	  rendelkezünk, ki <emphasis>kell</emphasis> kapcsolnunk a
 	  BIOS-ban az IO APIC használatát.  Ha nem
 	  találnánk ilyen beállítást,
 	  akkor helyette magát az ACPI-t kell kikapcsolnunk.  A
 	  Pro-150 chipsetnek vannak bizonyos hibái, amelyekre
 	  eddig még nem sikerült megfelelõ
 	  megoldást találnunk.</para>
 
       </sect3>
 
       <sect3>
 	<title>&os;/&arch.sparc64;</title>
 
 	<para>A &os;/&arch.sparc64; telepítéséhez
 	  egy támogatott platformra van
 	  szükségünk (lásd: <xref
 	  linkend="install-hardware-supported"/>).</para>
 
 	<para>A &os;/&arch.sparc64; telepítéséhez
 	  egy egész lemezre lesz szükségünk,
 	  mivel a rendszer jelenleg nem képes megosztani azt
 	  más operációs rendszerekkel.</para>
 
       </sect3>
     </sect2>
 
     <sect2 id="install-hardware-supported">
       <title>Támogatott hardverek</title>
 
       <para>A &os; minden kiadásához mellékelik a
 	támogatott hardverek listáját <quote>&os;
 	Hardware Notes</quote> címmel.  Ez a dokumentum
 	többnyire a <filename>HARDWARE.TXT</filename> nevû
 	állomány, amelyet a rendszer CD-n vagy FTP-n
 	keresztül elérhetõ változatának
 	gyökerében vagy a
 	<application>sysinstall</application>
 	dokumentációkat tartalmazó
 	menüjében találhatunk meg.</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-pre">
     <title>A telepítés elõtt elvégzendõ
       feladatok</title>
 
     <sect2 id="install-inventory">
       <title>Készítsünk leltárt a
 	számítógépünkrõl</title>
 
       <para>A &os; telepítése elõtt érdemes
 	összeszedni, pontosan mi minden is található
 	a számítógépünkben.  A &os;
 	telepítõrutinjai mutatni fogják a
 	különbözõ komponensek (merevlemezek,
 	hálózati kártyák,
 	CD-meghajtók és a többi) modelljét
 	és gyártóját.  A &os;
 	ezenkívü megpróbálja kideríteni
 	a megjelenõ eszközök pontos
 	konfigurációját is, beleértve a
 	használt IRQ és IO portok
 	kiosztását.  A PC-s hardverek
 	különféle szeszélyei miatt azonban ez az
 	iménti folyamat nem minden esetben
 	megbízható, ezért elõfordulhat, hogy
 	helyesbíteni kell a &os; által
 	megállapított értékeket.</para>
 
       <para>Ha már van a gépünkön egy
 	másik operációs rendszer,
 	például &windows; vagy &linux;, akkor
 	mindenképpen hasznos lehet az általa
 	felkínált eszközökkel lekérdezni
 	a hardvereink beállításait.  Ha nem
 	lennénk biztosak benne, hogy az adott
 	bõvítõkártyákat pontosan milyen
 	beállításokkal is használjuk,
 	nézzük meg ezeket magán a
 	kártyán.  A népszerû IRQ
 	értékek általában a 3, 5 és
 	7, valamint az IO portok számát
 	általában tizenhatos számrendszerben
 	szerepeltetik, például 0x330.</para>
 
       <para>Javasoljuk, hogy nyomtassuk ki vagy írjuk le ezeket a
 	paramétereket a &os; telepítése elõtt.
 	Ehhez rendezzük ezeket egy táblázatban,
 	valahogy így:</para>
 
       <table pgwide="1" frame="none">
 	<title>Példa egy eszközleltárra</title>
 
 	<tgroup cols="4">
 	  <colspec colwidth="2*"/>
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="4*"/>
 	  <thead>
 	    <row>
 	      <entry>Eszköz neve</entry>
 	      <entry>IRQ</entry>
 	      <entry>IO portok</entry>
 	      <entry>Megjegyzés</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
 	      <entry>Elsõ merevlemez</entry>
 	      <entry>-</entry>
 	      <entry>-</entry>
 	      <entry>Mérete 40&nbsp;GB, gyártmánya
 		Seagate, elsõdleges IDE master</entry>
 	    </row>
 	    <row>
 	      <entry>CD-ROM meghajtó</entry>
 	      <entry>-</entry>
 	      <entry>-</entry>
 	      <entry>Elsõdleges IDE slave</entry>
 	    </row>
 	    <row>
 	      <entry>Második merevlemez</entry>
 	      <entry>-</entry>
 	      <entry>-</entry>
 	      <entry>Mérete 20&nbsp;GB, gyártmánya
 		IBM, másodlagos IDE master</entry>
 	    </row>
 	    <row>
 	      <entry>Elsõ IDE vezérlõ</entry>
 	      <entry>14</entry>
 	      <entry>0x1f0</entry>
 	      <entry></entry>
 	    </row>
 	    <row>
 	      <entry>Hálózati kártya</entry>
 	      <entry>-</entry>
 	      <entry>-</entry>
 	      <entry>&intel; 10/100</entry>
 	    </row>
 	    <row>
 	      <entry>Modem</entry>
 	      <entry>-</entry>
 	      <entry>-</entry>
 	      <entry>&tm.3com; 56K-s faxmodem, COM1</entry>
 	    </row>
 	    <row>
 	      <entry>&hellip;</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>Ahogy elkészítettük a
 	számítógépünk
 	alkatrészeit tartalmazó listát, vessük
 	ezeket össze a telepítendõ &os; kiadás
 	által megkövetelt eszközökkel.</para>
 
     </sect2>
 
     <sect2>
       <title>Mentsük le az adatainkat</title>
 
       <para>Amennyiben a &os; telepítéséhez
 	használt számítógép
 	számunkra értékes adatokat tárol,
 	igyekezzünk lementeni ezeket, és a &os;
 	tényleges telepítése elõtt
 	gyõzõdjünk is meg róla, hogy a
 	mentés sikeres volt.  A &os; telepítõrutinjai
 	természetesen megerõsítést fognak
 	kérni bármilyen adat lemezre írása
 	elõtt, azonban ha egyszer már elindítottuk a
 	folyamatot, már semmit sem tudunk
 	visszafordítani.</para>
 
     </sect2>
 
     <sect2 id="install-where">
       <title>Döntsük el a &os;
 	telepítésének helyét</title>
 
       <para>Ha a &os; telepítéséhez az egész
 	merevlemezünket fel akarjuk használni, akkor
 	még nincs miért izgatnunk magunkat &mdash;
 	nyugodtan átléphetjük ezt a szakaszt.</para>
 
       <para>Amikor viszont a &os;-t más operációs
 	rendszerek mellé szeretnénk telepíteni,
 	ismernünk kell, miként is helyezkednek el az adatok
 	a lemezeken, és hogy ez miként is érint
 	bennünket.</para>
 
       <sect3 id="install-where-i386">
 	<title>A lemezek kiosztása a &os;/&arch.i386;
 	  esetén</title>
 
 	<para>A PC-k által használt lemezek
 	  különálló darabokra
 	  tagolhatóak.  Ezeket a darabokat
 	  <firstterm>partíciók</firstterm>nak
 	  nevezzük.  Mivel azonban a &os; maga is tárol
 	  partíciókat, ezért ez az elnevezés
 	  pillanatok alatt megtévesztõvé
 	  válhat, ezért ezeket a lemezdarabokat a &os;
 	  lemezslice-oknak vagy egyszerûen csak slice-oknak
 	  hívja.  Például a PC-s
 	  lemezpartíciókkal dolgozó,
 	  <command>fdisk</command> nevû &os;-s segédprogram
 	  partíciók helyett is slice-okra hivatkozik.  A
 	  PC lemezenként alapvetõen csak négy
 	  partíciót enged meg.  Ezeket a
 	  partíciókat nevezik <firstterm>elsõdleges
 	  partícióknak</firstterm>.  Ettõl a
 	  korlátozástól egy új típus,
 	  a <firstterm>kiterjesztett partíció</firstterm>
 	  létrehozásával szabadultak meg, amivel
 	  így négynél több
 	  partíció is készíthetõ.
 	  Lemezenként egyetlen ilyen kiterjesztett
 	  partíció található, de ezen
 	  belül speciális, ún.  <firstterm>logikai
 	  partíciók</firstterm> hozhatóak
 	  létre.</para>
 
 	<para>Minden partíciónak van egy
 	  <firstterm>partíció-azonosítója</firstterm>,
 	  melyet a partíción található
 	  adatok típusának
 	  megállapítására használnak.
 	  A &os; partícióinak azonosítója a
 	  <literal>165</literal>.</para>
 
 	<para>Általánosságban véve minden
 	  operációs rendszer így azonosítja
 	  a partíciókat.  Például a DOS
 	  és annak leszármazottai, mint
 	  például a &windows;, minden elsõdleges
 	  és logikai partícióhoz egy
 	  <devicename>C:</devicename>-tõl induló
 	  <firstterm>meghajtó-betûjelet</firstterm>
 	  társít.</para>
 
 	<para>A &os;-t egy elsõdleges partícióra kell
 	  telepíteni.  A &os; az összes adatát,
 	  beleértve minden általunk létrehozott
 	  állományt is, ezen az egyetlen
 	  partíción fogja elhelyezni.  Ha viszont
 	  több lemezünk van, többen is, vagy akár
 	  mindegyiken létrehozhatunk &os;-s
 	  partíciókat.  A &os; telepítésekor
 	  azonban legalább egy ilyen partíciónak
 	  használhatónak kell lennie.  Ez lehet elõre
 	  megtisztított üres partíciói is,
 	  vagy akár egy olyan partíció, amelyen
 	  már nem használt adatok vannak.</para>
 
 	<para>Ha már mindegyik partíciónk betelt,
 	  akkor a többi operációs rendszer
 	  által felkínált eszközök
 	  (például &ms-dos;-ban vagy &windows;-ban az
 	  <command>fdisk</command>) valamelyikével
 	  elõször fel kell közülük
 	  szabadítanunk egyet a &os;
 	  számára.</para>
 
 	<para>Amennyiben akadna egy használható
 	  partíció, akkor használjuk azt.  Ekkor
 	  azonban elõfordulhat, hogy ehhez elõször a
 	  meglévõk közül össze kell majd
 	  zsugorítanunk valamelyiket.</para>
 
 	<para>A &os; legkisebb telepíthetõ változata
 	  nagyjából 100&nbsp;MB lemezterületet
 	  igényel.  Azonban ez egy <emphasis>nagyon</emphasis>
 	  kicsi változat és szinte semmi helyet nem hagy a
 	  saját állományainknak.  Sokkal
 	  valósághûbb, ha grafikus felület
 	  nélkül nagyjából 250&nbsp;MB-ot
 	  mondunk, és legalább 350&nbsp;MB-ot a grafikus
 	  felület használata esetén.  Ha ezeken
 	  felül további szoftvereket is telepíteni
 	  kívánunk, még több helyre lesz
 	  szükségünk.</para>
 
 	<para>Amikor a &os; számára akarunk helyet
 	  csinálni, vagy partíciókat akarunk
 	  átméretezni, használjuk
 	  például a
 	  <application>&partitionmagic;</application> nevû
 	  kereskedelmi szoftvert, vagy esetleg egy olyan szabad
 	  szoftvert, mint például a
 	  <application>GParted</application>.  Ismereteink szerint a
 	  <application>&partitionmagic;</application> és a
 	  <application>GParted</application> is
 	  használható az <acronym>NTFS</acronym>
 	  partíciókkal.  A
 	  <application>GParted</application> számos live linuxos
 	  disztribúción megtalálható, ilyen
 	  többek közt a <ulink
 	    url="http://www.sysresccd.org">SystemRescueCD</ulink>.</para>
 
 	<para>Gondok lehetnek azonban a &microsoft; Vista által
 	  használt partíciókkal.  Ezért nem
 	  árt, ha az átméretezésekor a
 	  kezünk ügyében van a Vista
 	  telepítõ CD-je.  Természetesen, mint minden
 	  lemezkarbantási mûvelet esetén, ilyenkor is
 	  határozottan ajánlott biztonsági
 	  mentéseket készíteni.</para>
 
 	<warning>
 	  <para>Az említett eszközök helytelen
 	    használata megsemmisítheti a lemezeinken
 	    tárolt adatokat, ezért a használatuk
 	    elõtt gondoskodjunk friss,
 	    mûködõképes biztonsági
 	    mentésekrõl.</para>
 	</warning>
 
 	<example>
 	  <title>Meglevõ partíció használata a
 	    méret megváltoztatása
 	    nélkül</title>
 
 	  <para>Tegyük fel, hogy a
 	    számítógépünkben egyetlen
 	    4&nbsp;GB méretû lemez van, amelyen
 	    megtalálható a &windows; valamelyik
 	    verziója, és ezt a lemezt korábban
 	    két, egyaránt 2&nbsp;GB méretû
 	    meghajtóra osztottuk, a
 	    <devicename>C:</devicename>-re és
 	    <devicename>D:</devicename>-re.  1&nbsp;GB adatunk van a
 	    <devicename>C:</devicename> meghajtón és
 	    fél&nbsp;GB a <devicename>D:</devicename>-n.</para>
 
 	  <para>Mindez tehát azt jelenti, hogy a
 	    lemezünkön két partíció
 	    található, betûjelenként egy.  Ha
 	    átmásoljuk a <devicename>D:</devicename>
 	    meghajtón levõ adatainkat a
 	    <devicename>C:</devicename> meghajtóra, akkor ezzel
 	    felszabadíthatjuk a &os; számára a
 	    második partíciót.</para>
 	</example>
 
 	<example>
 	  <title>Meglevõ partíció
 	    zsugorítása</title>
 
 	  <para>Tegyük fel, hogy a
 	    számítógépünkben egyetlen
 	    4&nbsp;GB méretû lemez van, amelyet teljes
 	    egészében a &windows; valamelyik
 	    példánya foglal el.  A &windows;
 	    telepítése során ezért minden
 	    bizonnyal egyetlen nagy partíciót hoztunk
 	    létre, amely a <devicename>C:</devicename>
 	    betûjelet kapta és a mérete 4&nbsp;GB.
 	    Jelen pillanatban másfél&nbsp;GB helyet
 	    használunk a lemezen, és szeretnénk a
 	    &os; számára 2&nbsp;GB helyet
 	    felszabadítani.</para>
 
 	  <para>A &os; telepítéséhez a
 	    következõk valamelyikét kell
 	    tennünk:</para>
 
 	  <orderedlist>
 	    <listitem>
 	      <para>Mentsük le a &windows;-os adatainkat,
 		telepítsük újra a &windows;-t
 		úgy, hogy egy 2&nbsp;GB méretû
 		partíciót választunk neki a
 		telepítése során.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>A partíció
 		összezsugorítására
 		használjuk az elõbb említett
 		alkalmazásokat, például a
 		<application>&partitionmagic;</application>-et.</para>
 	    </listitem>
 	  </orderedlist>
 	</example>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Szedjük össze a hálózati
 	beállításainkat</title>
 
       <para>Amennyiben a &os; telepítésének
 	részeként hálózatra is
 	szándékozunk csatlakozni (például
 	egy FTP vagy NFS szerverrõl akarunk telepíteni),
 	ismernünk kell a hálózatra vonatkozó
 	beállításainkat is.  A telepítõ
 	rá fog kérdezni ezekre az
 	információkra, amelyek megadása után
 	a &os; a telepítés befejezéséhez
 	csatlakozni tud majd a hálózatra.</para>
 
       <sect3>
 	<title>Csatlakozás Ethernet-hálózaton,
 	  kábel- vagy DSL-modemen keresztül</title>
 
 	<para>Ha egy Ethernet-hálózathoz, vagy
 	  magához az internethez csatlakozunk egy DSL- vagy
 	  kábelmodemen keresztül, akkor az alábbi
 	  adatokra lesz szükségünk:</para>
 
 	<orderedlist>
 	  <listitem>
 	    <para>IP-cím</para>
 	  </listitem>
 	  <listitem>
 	    <para>Az alapértelmezett átjáró
 	      IP-címe</para>
 	  </listitem>
 	  <listitem>
 	    <para>A gépünk neve</para>
 	  </listitem>
 	  <listitem>
 	    <para>DNS (névfeloldó) szerverek
 	      IP-címei</para>
 	  </listitem>
 	  <listitem>
 	    <para>Hálózati maszk</para>
 	  </listitem>
 	</orderedlist>
 
 	<para>Ha nem ismerjük ezeket, érdeklõdjünk
 	  a rendszergazdától vagy a
 	  szolgáltatónktól.
 	  Elképzelhetõ az is, hogy mindezen
 	  információkat <firstterm>DHCP</firstterm>
 	  segítségével, automatikusan kapjuk meg.
 	  Ezt is mindenképpen jegyezzük fel.</para>
 
       </sect3>
 
       <sect3>
 	<title>Kapcsolódás modemmel</title>
 
 	<para>Ha az internet-szolgáltatónkhoz
 	  hagyományos modemen keresztül csatlakozunk, akkor
 	  is tudjuk telepíteni a &os;-t interneten
 	  keresztül, azonban ez nagyon sokáig
 	  tarthat.</para>
 
 	<para>Ehhez tudnunk kell:</para>
 
 	<orderedlist>
 	  <listitem>
 	    <para>Az internet-szolgáltatónk
 	      behívószámát</para>
 	  </listitem>
 	  <listitem>
 	    <para>A soros (COM) port számát, amelyen
 	      keresztül a modem kapcsolódik a
 	      gépünkhöz</para>
 	  </listitem>
 	  <listitem>
 	    <para>Az internet-szolgáltatónktól
 	      kapott felhasználói nevet és
 	      jelszót</para>
 	  </listitem>
 	</orderedlist>
 
       </sect3>
     </sect2>
 
     <sect2>
       <title>Olvassuk el &os; hibajegyzékét</title>
 
       <para>Habár a &os; Projekt igyekszik a &os; minden egyes
 	kiadását a lehetõ
 	legmegbízhatóbban felkészíteni,
 	hibák óhatatlanul is maradnak bennük.  Nagyon
 	ritka esetekben ezek a hibák magára a
 	telepítés folyamatára is kihathatnak.
 	Amint ezeket a problémákat sikerül
 	felderíteni és javítani, rögvest
 	megjelennek a &os; honlapján található
 	<ulink
 	  url="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">
 	hibajegyzékben</ulink> (angolul).  A
 	telepítés elõtt ezért mindig
 	ajánlott átolvasni ezt a dokumentumot, így
 	megbizonyosodunk róla, hogy semmilyen utólag
 	felmerült probléma nem akadályozza
 	munkánkat.</para>
 
       <para>Az összes kiadáshoz tartozó
 	információ, beleértve az egyes
 	kiadások hibajegyzékeit is, a <ulink
 	url="&url.base;/index.html">&os;
 	honlapjáról</ulink> a <ulink
 	url="&url.base;/releases/index.html">kiadásokra
 	vonatkozó információkat</ulink>
 	tartalmazó részen érhetõ el
 	(angolul).</para>
 
     </sect2>
 
     <sect2>
       <title>Szerezzük be a &os; telepítéséhez
 	szükséges állományokat</title>
 
       <para>A &os; telepítése az alábbi helyek
 	bármelyikén megtalálható
 	állományok felhasználásával
 	történik:</para>
 
       <itemizedlist>
 	<title>Lokálisan:</title>
 
 	<listitem>
 	  <para>CD vagy DVD</para>
 	</listitem>
 
 	<listitem>
 	  <para>Ugyanazon a számítógépen
 	    levõ &ms-dos; partíció</para>
 	</listitem>
 
 	<listitem>
 	  <para>Pendrive (USB-flash-tároló)</para>
 	</listitem>
 
 	<listitem>
 	  <para>SCSI- vagy QIC-szalag</para>
 	</listitem>
 
 	<listitem>
 	  <para>Floppylemezek</para>
 	</listitem>
       </itemizedlist>
 
       <itemizedlist>
 	<title>Hálózaton keresztül:</title>
 
 	<listitem>
 	  <para>FTP oldalról, tûzfalon keresztül vagy
 	    szükség szerint HTTP proxy
 	    használatával</para>
 	</listitem>
 
 	<listitem>
 	  <para>NFS szerverrõl</para>
 	</listitem>
 
 	<listitem>
 	  <para>Párhuzamos vagy soros vonali kapcsolaton
 	    keresztül</para>
 	</listitem>
       </itemizedlist>
 
       <para>Ha megvásároltuk a &os; telepítõ
 	CD-jét vagy DVD-jét, akkor már mindennel
 	rendelkezünk a telepítéshez.
 	Lépjünk bátran tovább a
 	következõ szakaszra (<xref
 	linkend="install-boot-media"/>)!</para>
 
       <para>Ha eddig még nem szereztük volna be a &os;
 	telepítéséhez szükséges
 	állományokat, ugorjunk a <xref
 	linkend="install-diff-media"/>hoz, ahol megtudhatjuk, hogyan
 	készítsük elõ a &os;
 	telepítését az imént felsorolt
 	helyzetekben.  A szakasz elolvasása után pedig
 	jöjjünk vissza ide, majd folytassuk az olvasást
 	a <xref linkend="install-boot-media"/>ban.</para>
 
     </sect2>
 
     <sect2 id="install-boot-media">
       <title>Készítsünk egy
 	rendszerindító lemezt</title>
 
       <para>A &os; telepítése úgy kezdõdik,
 	hogy a számítógépünkkel a &os;
 	telepítõjét indítjuk el &mdash; ez
 	viszont nem egy olyan program, amit más
 	operációs rendszerben el tudunk indítani.
 	A számítógépünk
 	általában a merevlemezünkre telepített
 	operációs rendszert indítja el, azonban
 	beállítható úgy is, hogy az
 	indulásához egy ún.
 	<quote>rendszerindító</quote> (bootolható)
 	floppy lemezt használjon.  Napjaink
 	számítógépei azonban a
 	CD-meghajtóban levõ CD-krõl vagy USB
 	lemezrõl is el tudnak indulni.</para>
 
       <tip>
 	<para>Ha CD-n vagy DVD-n megvan a &os; telepítõje
 	  (akár megvettük, akár éppen magunk
 	  készítettük) és a
 	  számítógépünk tud CD-rõl
 	  vagy DVD-rõl rendszert indítani (a BIOS-ban van
 	  egy <quote>Boot Order</quote> vagy hozzá hasonló
 	  nevû beállítás), akkor kihagyhatjuk
 	  ezt a szakaszt.  A &os; CD- és DVD image-ek
 	  kiírásával egy
 	  rendszerindításra alkalmas lemezt kapunk,
 	  amirõl minden további elõkészület
 	  nélkül telepíthetünk.</para>
       </tip>
 
       <para>Rendszerindításra alkalmas pendrive-ot az
 	alábbi lépések mentén tudunk
 	készíteni:</para>
 
       <procedure>
 	<step>
 	  <title>Az image állomány
 	    letöltése</title>
 
 	  <para>A pendrive-okhoz készült image
 	    állományok a <filename
 	      class="directory">ISO-IMAGES/</filename>
 	    könyvtárból tölthetõek le,
 	    <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>architektúra</replaceable>/ISO-IMAGES/<replaceable>verzió</replaceable>/&os;-&rel.current;-RELEASE-<replaceable>architektúra</replaceable>-memstick.img</literal>
 	    néven.  Az
 	    <replaceable>architektúra</replaceable> és
 	    <replaceable>verzió</replaceable> helyére a
 	    telepítendõ architektúrát
 	    és verziószámot
 	    helyettesítsük be.  Ennek megfelelõen
 	    tehát például a
 	    &os;/&arch.i386;&nbsp;&rel.current;-RELEASE változata
 	    a <ulink
 	      url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img"></ulink>
 	    címrõl érhetõ el.</para>
 
 	  <para>A pendrive image <filename>.img</filename>
 	    kiterjesztéssel rendelkezik.  A <filename
 	      class="directory">ISO-IMAGES/</filename>
 	    könyvtár általában több
 	    különféle állományt
 	    tartalmaz, ezek közül kell választanunk a
 	    &os; telepítendõ változatának,
 	    és sok esetben a telepítéshez
 	    rendelkezésre álló hardver
 	    típusának megfelelõen.</para>
 
 	  <important>
 	    <para>A következõ lépés
 	      megkezdése elõtt
 	      <emphasis>készítsünk biztonsági
 	      mentést</emphasis> a pendrive
 	      tartalmáról, mivel minden rajta levõ
 	      adat <emphasis>törlõdni</emphasis> fog.</para>
 	  </important>
 	</step>
 
 	<step>
 	  <title>A pendrive
 	    elõkészítése</title>
 
 	  <warning>
 	    <para>Az itt található példában
 	      a rendszerindításhoz és így a
 	      mûvelet végrehajtásához a
 	      <filename>/dev/da0</filename> nevû eszközt
 	      fogjuk használni.  Ezt ne felejtsük el
 	      helyettesíteni a rendszerünkön erre a
 	      célra használt eszköz nevével,
 	      máskülönben kárt tehetünk az
 	      adatainkban.</para>
 	  </warning>
 
 	  <para>A <varname>kern.geom.debugflags</varname>
 	    változó értékének
 	    megfelelõ beállításával
 	    engedélyezzük a céleszközön a
 	    Master Boot Record írását.</para>
 
 	  <screen><userinput>&prompt.root; sysctl kern.geom.debugflags=16</userinput></screen>
 	</step>
 
 	<step>
 	  <title>Az image pendrive-ra írása</title>
 
 	  <para>Az <filename>.img</filename> kiterjesztésû
 	    állományt <emphasis>nem</emphasis>
 	    egyszerûen a pendrive-ra kell másolni, ez a
 	    lemez teljes tartalmát magában foglalja.
 	    Ennek megfelelõen <emphasis>nem</emphasis>
 	    egyszerûen állományokat kell
 	    másolnunk az egyik lemezrõl a másikra.
 	    Helyette a &man.dd.1; parancs
 	    segítségével írjuk az image
 	    állomány tartalmát
 	    közvetlenül a lemezre.</para>
 
 	  <screen>&prompt.root; <userinput>dd if=&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img of=/dev/<replaceable>da0</replaceable> bs=64k</userinput></screen>
 	</step>
       </procedure>
 
       <para>Rendszerindításra alkalmas floppy lemezt az
 	alábbi lépések mentén tudunk
 	készíteni:</para>
 
       <procedure>
 	<step>
 	  <title>A rendszerindító lemezek image-einek
 	    beszerzése</title>
 
 	  <important>
 	    <para>A &os; 8.0 kiadásától
 	      kezdõdõen megszûnik a floppy lemezek
 	      támogatása.  Helyette
 	      telepítsünk pendrive-ról, amelyrõl
 	      fentebb olvashatunk, vagy egyszerûen
 	      használjunk CD-t vagy DVD-t.</para>
 	  </important>
 
 	  <para>A rendszerindító lemezek a
 	    telepítõeszköz
 	    <filename>floppies/</filename>
 	    könyvtárában találhatóak,
 	    illetve letölthetõek az
 	    <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>architektúra</replaceable>/<replaceable>változat</replaceable>-RELEASE/floppies/</literal>
 	    helyrõl.  Az
 	    <replaceable>architektúra</replaceable>
 	    és <replaceable>változat</replaceable>
 	    helyére természtesen írjuk be a
 	    telepíteni kívánt
 	    architektúrát és verziót.
 	    Így például a
 	    &os;/&arch.i386;&nbsp;&rel.current;-RELEASE
 	    rendszerindító lemezei az <ulink
 	      url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/"></ulink>
 	    címrõl érhetõek el.</para>
 
 	  <para>A floppyk image-ei <filename>.flp</filename>
 	    kiterjesztésûek.  A
 	    <filename>floppies/</filename> könyvtár
 	    számos különféle image-et tartalmaz,
 	    ezek közül leginkább a
 	    telepítendõ &os; változat, valamint
 	    emellett olykor konkrétan a hardver határozza
 	    meg a használandót.  Az esetek
 	    túlnyomó részében négy
 	    floppyra lesz szükségünk:
 	    <filename>boot.flp</filename>,
 	    <filename>kern1.flp</filename>,
 	    <filename>kern2.flp</filename> és
 	    <filename>kern3.flp</filename>.  A lemezek image-eit
 	    illetõ legfrissebb információkat
 	    ugyanazon a könyvtáron belül szereplõ
 	    <filename>README.TXT</filename> állományban
 	    olvashatjuk (angolul).</para>
 
 	  <important>
 	    <para>Az FTP-hez használt programunkat az image-ek
 	      letöltése során ne felejtsük el
 	      <emphasis>bináris (binary)</emphasis>
 	      átviteli módban használni.  Egyes
 	      böngészõk hajlamosak ugyanis
 	      <emphasis>szöveges (text vagy ASCII)</emphasis>
 	      átviteli módot használni, ami viszont
 	      csak abból vehetõ észre, hogy nem
 	      tudjuk a lemezekrõl elindítani a
 	      rendszert.</para>
 	  </important>
 	</step>
 
 	<step>
 	  <title>A floppyk
 	    elõkészítése</title>
 
 	  <para>Mindegyik letöltendõ image-hez elõ kell
 	    készíteni egy-egy hajlékonylemezt.
 	    Nagyon fontos, hogy ezek a lemezek teljesen
 	    hibátlanok legyenek.  Errõl a legkönnyebben
 	    úgy gyõzõdhetünk meg, ha a lemezeket
 	    magunk formázzuk, és nem bízunk a
 	    különféle elõreformázott
 	    (preformatted) floppykban.  A &windows;-ban
 	    található formázó
 	    segédprogram sem árul el nekünk semmit a
 	    lemezeken található hibás
 	    részekrõl, egyszerûen csak
 	    <quote>rossznak</quote> (bad) jelöli meg és
 	    figyelmen kívül hagyja ezeket.
 	    Határozottan ajánljuk, hogy amennyiben a
 	    telepítésnek ezt a módját
 	    választjuk, mindig használjunk teljesen
 	    új floppykat.</para>
 
 	  <important>
 	    <para>Ha megpróbáljuk telepíteni a
 	      &os;-t, és a telepítõprogram
 	      összeomlik, lefagy vagy bármilyen
 	      furcsaságot mûvel, elsõként
 	      mindenképpen a floppykra gyanakodhatunk.  Ilyenkor
 	      írjuk ki az image-eket új lemezekre
 	      és próbálkozzunk újra a
 	      telepítéssel.</para>
 	  </important>
 	</step>
 
 	<step>
 	  <title>Az image állományok írása a
 	    floppykra</title>
 
 	  <para>Az <filename>.flp</filename> kiterjesztésû
 	    állományok <emphasis>nem</emphasis> a lemezre
 	    másolható hagyományos
 	    állományok, hanem a lemezek teljes
 	    tartalmának képei, ezért ezeket
 	    egyszerûen <emphasis>nem</emphasis> másolhatjuk
 	    egyik lemezrõl a másikra.  Az image-ek
 	    közvetlen lemezreírásához ehelyett
 	    kifejezetten erre a célra alkalmas
 	    eszközöket kell használnunk.</para>
 
 	  <indexterm><primary>DOS</primary></indexterm>
 
 	  <para>Azok számára, akik a floppykat
 	    &ms-dos;/&windows; rendszerû
 	    számítógépeken
 	    kívánják elkészíteni,
 	    mellékeltünk egy <command>fdimage</command>
 	    nevû segédprogramot.</para>
 
 	  <para>Ha a CD-meghajtónk betûjele
 	    például <devicename>E:</devicename> és a
 	    telepítõ CD-n található image-eket
 	    szeretnénk kiírni vele, akkor ezt a parancsot
 	    kell kiadnunk:</para>
 
 	  <screen><prompt>E:\&gt;</prompt> <userinput>tools\fdimage floppies\boot.flp A:</userinput></screen>
 
 	  <para>Ezután ismételten adjuk ki az
 	    iménti parancsot minden egyes használni
 	    kívánt <filename>.flp</filename>
 	    állományra, azonban elõtte mindig
 	    tegyünk be egy újabb floppyt, és a
 	    ráírt image-ek neveivel folyamatosan
 	    címkézzük fel a lemezeket.  A megadott
 	    parancsot természetesen mindig írjuk át
 	    a konkrét <filename>.flp</filename>
 	    állományok tényleges
 	    elérési útvonalainak megfelelõen.
 	    Ha nincs CD-nk, akkor az <command>fdimage</command>
 	    programot az &os; FTP oldalán található
 	    <ulink
 	    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename
 	    class="directory">tools</filename>
 	    könyvtárból</ulink> is
 	    letölthetjük.</para>
 
 	  <para>Amikor a lemezeket egy &unix; rendszeren
 	    készítenénk el (például
 	    egy másik &os; rendszeren), akkor a &man.dd.1;
 	    parancs is használható az image
 	    állományok közvetlen
 	    lemezreírásához.  &os; alatt így
 	    néz ki a paraméterezése:</para>
 
 	  <screen>&prompt.root; <userinput>dd if=boot.flp of=/dev/fd0</userinput></screen>
 
 	  <para>&os;-n a <filename>/dev/fd0</filename> az elsõ
 	    hajlékonylemezes meghajtóra hivatkozik
 	    (tehát az <devicename>A:</devicename>
 	    betûjelû meghajtóra).  Ennek
 	    megfelelõen a <filename>/dev/fd1</filename> jelenti a
 	    <devicename>B:</devicename> meghajtót és
 	    így tovább.  Más &unix;
 	    változatok esetleg más neveket
 	    használhatnak a hajlékonylemezes
 	    meghajtók megnevezésére, ezért
 	    errõl érdemes ilyenkor
 	    tájékozódni az adott rendszerhez
 	    tartozó dokumentációban.</para>
 	</step>
       </procedure>
 
       <para>Most már készen állunk a &os;
 	telepítésére!</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-start">
     <title>A telepítés megkezdése</title>
 
     <important>
       <para>Alapértelmezés szerint a
 	telepítés egészen addig nem fog semmit sem
 	írni a lemezekre, amíg a következõ
 	üzenet fel nem bukkan:</para>
 
       <literallayout class="monospaced">Last Chance: Are you SURE you want continue the installation?
 
 If you're running this on a disk with data you wish to save then WE
 STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding!
 
 We can take no responsibility for lost disk contents!</literallayout>
 
       <para>A szöveg fordítása:</para>
 
       <literallayout class="monospaced">Utolsó esély: BIZTOSAN folytatni kívánja a telepítést?
 
 Ha olyan lemezre szeretne telepíteni, amelyen fontos adatok
 találhatóak, HATÁROZOTTAN JAVASOLJUK, hogy a továbblépés elõtt
 KÉSZÍTSEN RÓLUK MEGBÍZHATÓ BIZTONSÁGI MÁSOLATOT!
 
 Nem vállalunk semmilyen felelõsséget az elveszett adatokért!</literallayout>
 
       <para>A telepítõbõl tehát a fenti,
 	végsõ figyelmeztetés elõtt
 	bármikor ki lehet lépni anélkül, hogy
 	a merevlemezünkön levõ adatokat
 	veszélyeztetnénk.  Ha úgy
 	érezzük, hogy valamit véletlenül rosszul
 	állítottunk volna be a telepítés
 	során, ekkor még minden komolyabb kár
 	okozása nélkül kikapcsolhatjuk a
 	számítógépünket.</para>
     </important>
 
     <sect2 id="install-starting">
       <title>A rendszer indítása</title>
 
       <sect3 id="install-starting-i386">
 	<title>Rendszerindítás &i386;-on</title>
 
       <procedure>
 	<step>
 	  <para>Kezdjünk egy kikapcsolt
 	    számítógéppel.</para>
 	</step>
 
 	<step>
 	  <para>Kapcsoljuk be a
 	    számítógépet.  Az
 	    indulása során látnunk kell egy olyan
 	    opciót, amivel be tudunk lépni a rendszer
 	    beállításait tartalmazó
 	    menübe, avagy a BIOS-ba.  Ezt többnyire a
 	    <keycap>F2</keycap>, <keycap>F10</keycap>,
 	    <keycap>Del</keycap> vagy a <keycombo action="simul">
 	    <keycap>Alt</keycap><keycap>S</keycap></keycombo>
 	    lenyomásával érhetjük el.  Ezek
 	    közül használjuk a képernyõn
 	    megjelenõ billentyûket.  Elõfordulhat, hogy
 	    induláskor a
 	    számítógépünk semmilyen
 	    szöveget, csak egy képet mutat.  Ilyenkor
 	    általában a <keycap>Esc</keycap>
 	    billentyû megnyomására eltûnik a
 	    kép és láthatóvá
 	    válnak a számunkra fontos
 	    üzenetek.</para>
 	</step>
 
 	<step>
 	  <para>Miután beléptünk a menübe,
 	    keressük meg azt a beállítást,
 	    amely a rendszerindításhoz használt
 	    eszközt határozza meg.  Ennek a neve sokszor
 	    <quote>Boot Order</quote> (rendszerindítási
 	    sorrend) vagy valami hozzá hasonló.  Itt
 	    mindenféle eszköz felsorolását
 	    találjuk: <literal>Floppy</literal>,
 	    <literal>CDROM</literal>, <literal >First Hard
 	    Disk</literal> (elsõ merevlemezes meghajtó)
 	    és így tovább.</para>
 
 	  <para>Ha CD-rõl akarjuk a telepítést
 	    elindítani, akkor akkor a <literal>CDROM</literal>
 	    eszközt válasszuk.  Ha bármilyen
 	    kétség merülne fel bennünk,
 	    keressük meg ezt a beállítást a
 	    számítógéphez és/vagy az
 	    alaplaphoz kapott kézikönyvben.</para>
 
 	  <para>Igényeink szerint végezzük el a
 	    beállítást, majd mentsük el
 	    és lépjünk ki.  Most indítsuk
 	    újra a
 	    számítógépet.</para>
 	</step>
 
 	<step>
 	  <para>Ha a <xref linkend="install-boot-media"/>ban
 	    leírtak szerint rendszerindító
 	    pendrive-ot készítettünk, akkor
 	    bekapcsolás elõtt csatlakoztassuk a
 	    számítógéphez.</para>
 
 	  <para>Ha CD-rõl indítjuk a
 	    telepítést, akkor kapcsoljuk be a
 	    számítógépet és az
 	    elindulása után igyekezzünk minél
 	    hamarabb betenni a lemezt a meghajtóba.</para>
 
 	  <note>
 	    <para>A &os;&nbsp;7.3 és az azt megelõzõ
 	      változatokban a <xref
 		linkend="install-boot-media"/>ban leírtak szerint
 	      elõkészített floppy-ról is el
 	      tudjuk kezdeni a telepítést.  Ezek egyike
 	      lesz az elsõ rendszerindító lemez, a
 	      <filename>boot.flp</filename>.  Helyezzük ezt a
 	      lemezt a meghajtóba, és indítsuk el
 	      vele a számítógépet.</para>
 	  </note>
 
 	  <para>Ha minden próbálkozásunk
 	    ellenére a
 	    számítógépünk a megszokott
 	    módon indul és a meglevõ
 	    operációs rendszert tölti be, akkor a
 	    következõkkel lehet a gond:</para>
 
 	  <orderedlist>
 	    <listitem>
 	      <para>A lemezeket nem raktuk be eléggé
 		korán.  Hagyjuk benn ezeket és
 		próbáljuk meg ismét
 		újraindítani a
 		számítógépet.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Nem állítottuk be jól a BIOS-t.
 		Próbáljuk meg egészen addig
 		újra végrehajtani az elõzõ
 		lépést, amíg a megfelelõ
 		beállítást el nem
 		találjuk.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>A BIOS nem támogatja a kiválasztott
 		eszközrõl történõ
 		rendszerindítást.</para>
 	    </listitem>
 	  </orderedlist>
 	</step>
 
 	<step>
 	  <para>A &os; megkezdi az indulását.  Ha
 	    CD-rõl indítjuk, akkor valami ehhez
 	    hasonlót fogunk látni (a konkrét
 	    verzióra vonatkozó adatokat itt most
 	    kihagytuk):</para>
 
 	  <screen>Booting from CD-Rom...
 645MB medium detected
 CD Loader 1.2
 
 Building the boot loader arguments
 Looking up /BOOT/LOADER... Found
 Relocating the loader and the BTX
 Starting the BTX loader
 
 BTX loader 1.00 BTX version is 1.02
 Console: internal video/keyboard
 BIOS CD is cd0
 BIOS drive C: is disk0
 BIOS drive D: is disk1
 BIOS 639kB/261056kB available memory
 
 FreeBSD/i386 bootstrap loader, Revision 1.1
 
 Loading /boot/defaults/loader.conf
 /boot/kernel/kernel text=0x64daa0 data=0xa4e80+0xa9e40 syms=[0x4+0x6cac0+0x4+0x88e9d]
 \</screen>
 
 	  <para>Amikor floppyról indítjuk a rendszert,
 	    ehhez hasonlóval találkozhatunk (itt sem
 	    szerepelnek most verzióadatok):</para>
 
 	  <screen>Booting from Floppy...
 Uncompressing ... done
 
 BTX loader 1.00  BTX version is 1.01
 Console: internal video/keyboard
 BIOS drive A: is disk0
 BIOS drive C: is disk1
 BIOS 639kB/261120kB available memory
 
 FreeBSD/i386 bootstrap loader, Revision 1.1
 
 Loading /boot/defaults/loader.conf
 /kernel text=0x277391 data=0x3268c+0x332a8 |
 
 Insert disk labelled "Kernel floppy 1" and press any key...</screen>
 
 	  <para>Kövessük a képernyõn
 	    megjelenõ utasítást (<quote>Helyezze be a
 	    "Kernel floppy 1" címkéjû lemezt
 	    és nyomjon meg egy billentyût...</quote>),
 	    tehát vegyük ki a <filename>boot.flp</filename>
 	    image-hez tartozó lemezt és tegyük be
 	    helyette a <filename>kern1.flp</filename> image-hez
 	    tartozó lemezt, majd nyomjuk le az
 	    <keycap>Enter</keycap> billentyût.  Várjuk meg
 	    amíg a rendszer megkezdi az indulást az
 	    elsõ lemezrõl, majd az utasításoknak
 	    megfelelõen folyamatosan tegyük be a soron
 	    következõ lemezeket.</para>
 	</step>
 
 	<step>
 	  <para>Miután elindítottuk a rendszert
 	    CD-rõl, pendrive-ról vagy floppy-ról, a
 	    rendszerindítási folyamat be fogja hozni a
 	    &os; rendszertöltõjének
 	    menüjét:</para>
 
 	  <figure id="boot-loader-menu">
 	    <title>&os; rendszerbetöltõ menüje</title>
 
 	    <mediaobject>
 	      <imageobject>
 		<imagedata fileref="install/boot-loader-menu"/>
 	      </imageobject>
 	    </mediaobject>
 	  </figure>
 
 	  <para>Várjuk ki a tíz másodperces
 	    szünetet vagy egybõl nyomjuk le az
 	    <keycap>Enter</keycap> billentyût.</para>
 	</step>
       </procedure>
       </sect3>
 
       <sect3>
 	<title>Rendszerindítás &sparc64;-en</title>
 
 	<para>A legtöbb &sparc64; alapú rendszert úgy
 	  állították be, hogy automatikusan
 	  lemezrõl induljon.  A &os;
 	  telepítéséhez azonban
 	  hálózaton keresztül vagy CD-rõl kell
 	  indítanunk a rendszert, ezért
 	  módosítanunk kell a PROM (az OpenFirmware)
 	  beállításait.</para>
 
 	<para>Mindehhez indítsuk újra a rendszert
 	  és várjuk meg, amíg feltûnik a
 	  rendszerindító üzenet.  A konkrét
 	  üzenet nagyban függ a
 	  számítógép
 	  típusától, azonban valami ilyesmi
 	  lesz:</para>
 
     <screen>Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
 Copyright 1998-2001 Sun Microsystems, Inc.  All rights reserved.
 OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
 Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
 
 	<para>Amikor megpróbálja a rendszert
 	  elindítani a lemezrõl, a PROM
 	  parancssorának bekéréshez nyomjuk le a
 	  billentyûzeten az <keycombo
 	  action="simul"><keycap>L1</keycap>
 	  <keycap>A</keycap></keycombo> vagy a <keycombo action="simul">
 	  <keycap>Stop</keycap><keycap>A</keycap></keycombo>
 	  billentyûket, esetleg a soros konzolon keresztül
 	  küldjünk egy <command>BREAK</command> parancsot
 	  (például a &man.tip.1; vagy &man.cu.1; man
 	  oldalakon szereplõ <command>~#</command> parancs
 	  használatával).  Körülbelül
 	  így néz ki:</para>
 
 	  <screen><prompt>ok     </prompt><co id="prompt-single"/>
 <prompt>ok {0} </prompt><co id="prompt-smp"/></screen>
 
 	  <calloutlist>
 	    <callout arearefs="prompt-single">
 	      <para>Ez a fajta parancssor csak az egy processzorral
 		rendelkezõ rendszereken jelenik meg.</para>
 	    </callout>
 
 	    <callout arearefs="prompt-smp">
 	      <para>Ez a fajta parancssor többprocesszoros (SMP)
 		rendszereken jelenik meg, ahol a szám az
 		éppen aktív processzor
 		sorszámát jelöli.</para>
 	    </callout>
 	  </calloutlist>
 
 	<para>Most helyezzük a CD-t a meghajtóba, és
 	  a PROM parancssorában pedig gépeljük be
 	  <command>boot cdrom</command> parancsot.</para>
       </sect3>
     </sect2>
 
     <sect2 id="view-probe">
       <title>Az eszközkeresés eredményeinek
 	vizsgálata</title>
 
       <para>A képernyõn megjelenõ utolsó
 	pár száz sor mindig eltárolódik,
 	késõbb tetszõlegesen
 	átvizsgálhatóak.</para>
 
       <para>A puffer tartalmának
 	átnézéséhez nyomjuk le a
 	<keycap>Scroll Lock</keycap> billentyût, amivel
 	bekapcsoljuk a korábban megjelent üzenetek
 	közti visszalépést.  Itt a
 	nyílbillentyûk, vagy a <keycap>PageUp</keycap>
 	és <keycap>PageDown</keycap> billentyûk
 	használhatóak a kiírások
 	átböngészéséhez.  A
 	<keycap>Scroll Lock</keycap> ismételt
 	lenyomásával kiléphetünk ebbõl a
 	módból.</para>
 
       <para>Tegyük most mi is ezt, és nézzük az
 	összes olyan üzenetet, amely a rendszermag
 	indulása során keletkezett.  A <xref
 	linkend="install-dev-probe"/>ban látható
 	szövegekhez hasonlóakat fogunk találni,
 	habár ez a számítógépben
 	található konkrét
 	eszközöktõl függõen eltérõ
 	lehet.</para>
 
       <figure id="install-dev-probe">
 	<title>Példa az eszközkeresés
 	  eredményeire</title>
 
 	<screen>avail memory = 253050880 (247120K bytes)
 Preloaded elf kernel "kernel" at 0xc0817000.
 Preloaded mfs_root "/mfsroot" at 0xc0817084.
 md0: Preloaded image &lt;/mfsroot&gt; 4423680 bytes at 0xc03ddcd4
 
 md1: Malloc disk
 Using $PIR table, 4 entries at 0xc00fde60
 npx0: &lt;math processor&gt; on motherboard
 npx0: INT 16 interface
 pcib0: &lt;Host to PCI bridge&gt; on motherboard
 pci0: &lt;PCI bus&gt; on pcib0
 pcib1:&lt;VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge&gt; at device 1.0 on pci0
 pci1: &lt;PCI bus&gt; on pcib1
 pci1: &lt;Matrox MGA G200 AGP graphics accelerator&gt; at 0.0 irq 11
 isab0: &lt;VIA 82C586 PCI-ISA bridge&gt; at device 7.0 on pci0
 isa0: &lt;iSA bus&gt; on isab0
 atapci0: &lt;VIA 82C586 ATA33 controller&gt; port 0xe000-0xe00f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0 &lt;VIA 83C572 USB controller&gt; port 0xe400-0xe41f irq 10 at device 7.2 on pci
 0
 usb0: &lt;VIA 83572 USB controller&gt; on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr1
 uhub0: 2 ports with 2 removable, self powered
 pci0: &lt;unknown card&gt; (vendor=0x1106, dev=0x3040) at 7.3
 dc0: &lt;ADMtek AN985 10/100BaseTX&gt; port 0xe800-0xe8ff mem 0xdb000000-0xeb0003ff ir
 q 11 at device 8.0 on pci0
 dc0: Ethernet address: 00:04:5a:74:6b:b5
 miibus0: &lt;MII bus&gt; on dc0
 ukphy0: &lt;Generic IEEE 802.3u media interface&gt; on miibus0
 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 ed0: &lt;NE2000 PCI Ethernet (RealTek 8029)&gt; port 0xec00-0xec1f irq 9 at device 10.
 0 on pci0
 ed0 address 52:54:05:de:73:1b, type NE2000 (16 bit)
 isa0: too many dependant configs (8)
 isa0: unexpected small tag 14
 orm0: &lt;Option ROM&gt; at iomem 0xc0000-0xc7fff on isa0
 fdc0: &lt;NEC 72065B or clone&gt; at port 0x3f0-0x3f5,0x3f7 irq 6 drq2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: &lt;1440-KB 3.5&rdquo; drive&gt; on fdc0 drive 0
 atkbdc0: &lt;Keyboard controller (i8042)&gt; at port 0x60,0x64 on isa0
 atkbd0: &lt;AT Keyboard&gt; flags 0x1 irq1 on atkbdc0
 kbd0 at atkbd0
 psm0: &lt;PS/2 Mouse&gt; irq 12 on atkbdc0
 psm0: model Generic PS/@ mouse, device ID 0
 vga0: &lt;Generic ISA VGA&gt; at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: &lt;System console&gt; at flags 0x100 on isa0
 sc0: VGA &lt;16 virtual consoles, flags=0x300&gt;
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: &lt;Parallel port&gt; at port 0x378-0x37f irq 7 on isa0
 pppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/15 bytes threshold
 plip0: &lt;PLIP network interface&gt; on ppbus0
 ad0: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata0-master UDMA33
 acd0: CD-RW &lt;LITE-ON LTR-1210B&gt; at ata1-slave PIO4
 Mounting root from ufs:/dev/md0c
 /stand/sysinstall running as init on vty0</screen>
       </figure>
 
       <para>Figyelmesen olvassuk át az üzeneteket, és
 	bizonyosodjuk meg róla, hogy a &os; minden
 	számunkra fontos eszközt felismert.  Ha nem
 	látunk egy eszközt, akkor azt
 	valószínûleg nem találta meg.  Egy
 	<link linkend="kernelconfig">saját rendszermag</link>
 	létrehozásával azonban fel tudunk
 	ismertetni olyan eszközöket is, amelyek
 	támogatása eredetileg nem szerepel a
 	<filename>GENERIC</filename> rendszermagban.  Ilyenek
 	például a hangkártyák.</para>
 
       <para>A &os;&nbsp;6.2 vagy késõbbi
 	változataiban az eszközök felkutatása
 	után a <xref linkend="config-country"/>ban
 	láthatóak következnek.  Itt a
 	nyílbillentyûk segítségével
 	választhatjuk ki az országot (country),
 	térséget (region) vagy csoportot (group).  Az
 	<keycap>Enter</keycap> lenyomása után pillanatok
 	alatt beállítódik az országunk.  Ha
 	meg akarjuk ismételni az iménti
 	beállítást, pillanatok alatt ki tudunk
 	lépni a <application>sysinstall</application>
 	programból.</para>
 
       <figure id="config-country">
 	<title>Az ország kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/config-country"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Ha országként <guimenuitem>United
 	States</guimenuitem> (Egyesült Államok) került
 	beállításra, akkor a szabványos
 	amerikai billentyûzet-kiosztás
 	állítódik be.  A többi ország
 	esetében az alábbi menü jelenik meg.  A
 	kurzormozgató billentyûk
 	segítségével ekkor keressük meg ki a
 	számunkra megfelelõ kiosztást, és az
 	<keycap>Enter</keycap> billentyû lenyomásával
 	válasszuk ki.</para>
 
       <figure id="config-keymap">
 	<title>A billentyûzet típusának
 	  kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/config-keymap"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <figure id="sysinstall-exit">
 	<title>Kilépés a
 	  <application>sysinstall</application> programból</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/sysinstall-exit"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A telepítõprogram
 	fõképernyõjén válasszuk ki a
 	nyílbillentyûkkel az <guimenuitem>Exit
 	Install</guimenuitem> (<quote>Kilépés a
 	telepítésbõl</quote>) menüpontot.  Erre
 	a következõ üzenet fog megjelenni:</para>
 
       <screen>                      User Confirmation Requested
          Are you sure you wish to exit? The system will reboot
 
                             [ Yes ]    No</screen>
 
       <para>Az üzenet fordítása:</para>
 
       <screen>                  Felhasználói megerõsítés szükséges
          Valóban ki akar lépni? A rendszer ezt követõen újra fog
          indulni
 
                            [ Igen ]    Nem</screen>
 
       <para>Ha a &gui.yes; választ adjuk és a CD-t az
 	újraindításkor is a meghajtóban
 	hagyjuk, akkor a telepítõprogram még egyszer
 	el fog indulni.</para>
 
       <para>Ha floppyról indítottuk volna a rendszert, az
 	újraindítás elõtt vegyük ki a
 	<filename>boot.flp</filename> image-et tartalmazó
 	lemezt.</para>
     </sect2>
   </sect1>
 
   <sect1 id="using-sysinstall">
     <title>A <application>sysinstall</application>
       bemutatása</title>
 
     <para>A <application>sysinstall</application> a &os; Projekt
       által fejlesztett telepítõprogram.  Konzol
       alapú, menükre és képernyõkre
       oszlik, amelyeken a beállításokat és a
       telepítési folyamat
       irányítását tudjuk
       elvégezni.</para>
 
     <para>A <application>sysinstall</application>
       menürendszerét több más billentyû
       mellett legfõképpen a nyílbillentyûkkel,
       az <keycap>Enter</keycap>, <keycap>Tab</keycap> és a
       <keycap>Szóköz</keycap> billentyûkkel
       kezelhetjük.  Ezek és az általuk
       elvégezhetõ feladatok részletes
       leírása a <application>sysinstall</application>
       használatáról szóló
       információk között
       található.</para>
 
     <para>Ennek megtekintéséhez elõször
       gyõzõdjünk meg róla, hogy a <xref
       linkend="sysinstall-main3"/> által illusztrált
       helyzetnek megfelelõen kiválasztottuk a
       <guimenuitem>Usage</guimenuitem> (<quote>Használat</quote>)
       menüpontot és a <guibutton>[Select]</guibutton>
       (<quote>Kiválaszt</quote>) feliratú gombon
       állunk, majd nyomjuk le az <keycap>Enter</keycap>
       billentyût.</para>
 
     <para>Ezt követõen megjelenik a menürendszer
       használatát bemutató leírás.
       Miután végigolvastuk, a fõmenübe az
       <keycap>Enter</keycap> billentyû lenyomásával
       tudunk visszajutni.</para>
 
     <figure id="sysinstall-main3">
       <title>A <quote>Usage</quote> kiválasztása a
 	<application>sysinstall</application>
 	fõmenüjében</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="install/main1"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
     <sect2 id="select-doc">
       <title>A dokumentációs menü
 	kiválasztása</title>
 
       <para>A fõmenüben a nyílbillentyûkkel
 	válasszuk a <guimenuitem>Doc</guimenuitem>
 	feliratú menüpontot és nyomjuk meg az
 	<keycap>Enter</keycap> billentyût.</para>
 
       <figure id="main-doc">
 	<title>A dokumentációs menü
 	  kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-doc"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Ezzel megjelenik a dokumentációs
 	menü.</para>
 
       <figure id="docmenu1">
 	<title>A <application>sysinstall</application>
 	  dokumentációs menüje</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/docmenu1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Feltétlenül olvassuk el az itt
 	található leírásokat.</para>
 
       <para>A dokumentumok elolvasásához elõször
 	válasszunk közülük a
 	nyílbillentyûkkel, majd nyomjuk meg az
 	<keycap>Enter</keycap> billentyût.  A dokumentum
 	elolvasása után az <keycap>Enter</keycap>
 	lenyomásával tudunk visszatérni a
 	dokumentációs menübe.</para>
 
       <para>A dokumentációs menübõl a
 	fõmenübe úgy tudunk kilépni, ha a
 	nyílbillentyûkkel kiválasztjuk az
 	<guimenuitem>Exit</guimenuitem>
 	(<quote>Kilépés</quote>) menüpontot és
 	megnyomjuk az <keycap>Enter</keycap> billentyût.</para>
 
     </sect2>
 
     <sect2 id="keymap">
       <title>A billentyûkiosztás menüjének
 	kiválasztása</title>
 
       <para>A billentyûzetkiosztás
 	megváltoztatásához válasszuk ki a
 	nyílbillentyûk segítségével a
 	<guimenuitem>Keymap</guimenuitem> menüpontot a
 	menübõl és nyomjuk meg az
 	<keycap>Enter</keycap> billentyût.  Erre
 	természetesen csak akkor lesz
 	szükségünk, ha nem szabványos vagy nem
 	angol billentyûzetet használunk.</para>
 
       <figure id="sysinstall-keymap">
 	<title>A <application>sysinstall</application>
 	  fõmenüje</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-keymap"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A különbözõ
 	billentyûkiosztásoknak megfelelõ
 	menüpontok a fel/le nyílak és a
 	<keycap>Szóköz</keycap> billentyû
 	segítségével választhatóak
 	ki.  A <keycap>Szóköz</keycap> ismételt
 	lenyomásával töröljük a
 	választásunkat.  A befejezéshez
 	válasszuk ki a nyilakkal a &gui.ok; gombot és
 	nyomjuk le az <keycap>Enter</keycap> billentyût.</para>
 
       <para>A mellékelt képen a lista egy része
 	látható csupán.  Ha a <keycap>Tab</keycap>
 	billentyûvel a &gui.cancel; gombot választjuk, akkor
 	az alapértelmezett billentyûkiosztást kapjuk
 	és visszakerülünk a fõmenübe.</para>
 
       <figure id="sysinstall-keymap-menu">
 	<title>A <application>sysinstall</application>
 	  billentyûkiosztást beállító
 	  menüje</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/keymap"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
     </sect2>
 
     <sect2 id="viewsetoptions">
       <title>A telepítés beállításai
 	tartalmazó képernyõ</title>
 
     <para>Válasszuk az <guimenuitem>Options</guimenuitem>
       (<quote>Beállítások</quote>) menüpontot,
       majd nyomjuk le az <keycap>Enter</keycap> billentyût.</para>
 
     <figure id="sysinstall-options">
       <title>A <application>sysinstall</application>
 	fõmenüje</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="install/main-options"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
       <figure id="options">
 	<title>A <application>sysinstall</application>
 	  beállításai</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/options"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Az itt szereplõ alapértelmezett
 	értékek a legtöbb felhasználó
 	számára minden további nélkül
 	megfelelnek, nem szükséges a
 	megváltoztatásuk.  A kiadás neve
 	(<quote>release name</quote>) mezõ értéke a
 	telepítendõ verziótól
 	függõen változhat.</para>
 
       <para>A kiválasztott mezõ rövid
 	leírása a képernyõ alján,
 	kékkel kiemelten jelenik meg.  A <guimenuitem>Use
 	Defaults</guimenuitem> (<quote>Az alapértelmezések
 	használata</quote>) beállítás az
 	alapértelmezésére állítja
 	vissza az összes értéket.</para>
 
       <para>Az <keycap>F1</keycap> lenyomásával
 	elolvashatjuk a különbözõ
 	beállításokhoz tartozó
 	súgót.</para>
 
       <para>A <keycap>Q</keycap> billentyûvel
 	visszatérhetünk a fõmenübe.</para>
 
     </sect2>
 
     <sect2 id="start-install">
       <title>Egy szabványos telepítés
 	megkezdése</title>
 
       <para>A <guimenuitem>Standard</guimenuitem>
 	(<quote>Szabványos</quote>) elnevezésû
 	menüpont által felkínált
 	telepítési módszer ajánlott a
 	&unix;-szal vagy a &os;-vel most ismerkedõk
 	számára.  A telepítés
 	megkezdéséhez a nyilakkal válasszuk ki a
 	<guimenuitem>Standard</guimenuitem> menüpontot, majd
 	nyomjuk meg az <keycap>Enter</keycap> billentyût.</para>
 
       <figure id="sysinstall-standard">
 	<title>Egy szabványos telepítés
 	  megkezdése</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-std"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
     </sect2>
   </sect1>
 
   <sect1 id="install-steps">
     <title>Lemezterület lefoglalása</title>
 
     <para>Elsõ feladatunk lemezterületet foglalni a &os;
       számára, majd megcímkézni azt, hogy a
       <application>sysinstall</application> elõ tudja
       készíteni.  Ehhez tisztában kell lennünk
       azzal, hogy a &os; milyen formában is keresi az adatokat a
       lemezünkön.</para>
 
     <sect2 id="install-drive-bios-numbering">
       <title>A BIOS meghajtószámozása</title>
 
       <para>Egy témára különösen
 	tekintettel kell lennünk mielõtt
 	telepítenénk és
 	beállítanánk a &os;-t a
 	rendszerünkön, fõleg abban az esetben, ha
 	több merevlemezünk is van.</para>
 
       <indexterm><primary>DOS</primary></indexterm>
       <indexterm><primary>Microsoft Windows</primary></indexterm>
 
       <para>Egy BIOS-függõ operációs rendszert,
 	például &ms-dos;-t vagy &windows;-t futattó
 	PC esetén a BIOS az operációs rendszer
 	beleegyezésével képes elvonatkoztatni a
 	lemezek megszokott sorrendjétõl.  Ennek
 	köszönhetõen a felhasználó nem csak
 	az ún.  <quote>primary master</quote> (elsõdleges
 	master) merevlemezes meghajtótól tudja
 	elindítani a rendszert.  Ez kifejezetten kényelmes
 	megoldás az olyan felhasználók
 	számára, akik az elsõvel teljesen
 	megegyezõ második merevlemez
 	megvásárlásával
 	kialakították a rendszerük egyszerû
 	és egyben a legolcsóbb biztonsági
 	mentését, amire a <application><trademark
 	class="registered">Ghost</trademark></application> vagy
 	<application>XCOPY</application> programokkal tudnak rendszeres
 	másolatokat készíteni.  Így, ha az
 	elsõdleges meghajtó tönkremegy vagy
 	vírus támadja meg, esetleg az
 	operációs rendszer egy hiba miatt
 	használhatatlanná teszi, akkor a BIOS-t
 	utasíthatjuk a meghajtók logikai
 	cseréjére és ezzel könnyen helyre
 	tudjuk állítani.  Olyan, mintha a ház
 	felnyitása nélkül felcseréltük
 	volna a lemezeket bekötõ kábeleket.</para>
 
       <indexterm><primary>SCSI</primary></indexterm>
       <indexterm><primary>BIOS</primary></indexterm>
 
       <para>A SCSI-vezérlõkkel szerelt drágább
 	rendszerek gyakran tartalmaznak olyan
 	BIOS-bõvítéseket, amelyeken keresztül a
 	SCSI-lemezek ugyanígy tetszõlegesen
 	átrendezhetõek, egészen hét
 	meghajtóig.</para>
 
       <para>Az ilyen lehetõségek használatához
 	szokott felhasználókat azonban könnyen
 	csalódás érheti, amikor a &os; nem az
 	elvárásaiknak megfelelõen cselekszik.  A &os;
 	ugyanis nem használja a BIOS-t és nem ismeri a
 	<quote>BIOS logikai
 	meghajtókiosztását</quote>.  Ez
 	meghökkentõ eredményekre vezethet, fõleg
 	akkor, amikor paramétereiket tekintve a meghajtók
 	fizikailag teljesen megegyeznek és ráadásul
 	egymás másolatait tartalmazzák.</para>
 
       <para>A &os; telepítése elõtt mindig
 	állítsuk vissza a BIOS-ban a meghajtók
 	eredeti sorrendjét, és a
 	használatához hagyjuk is így ezt a
 	beállítást.  Ha valamiért
 	mégis meg kellene cserélnünk a
 	meghajtókat, akkor ezentúl válasszuk a
 	nehezebb utat: nyissuk ki a gépházat és
 	kössük át a kábeleket, tegyük
 	át a jumpereket mi magunk.</para>
 
       <sidebar>
 	<title>Részlet Frédi és Vili
 	  különleges kalandjaiból:</title>
 
 	<para>Vili fogott egy öreg Winteles
 	  számítógépet, hogy
 	  készítsen belõle egy &os;-s rendszert
 	  Frédinek.  Vili ehhez beszerel egy
 	  SCSI-meghajtót, ami így nullás
 	  SCSI-egység lesz, majd telepíti rá a
 	  &os;-t.</para>
 
 	<para>Frédi nekilát használni a rendszert,
 	  azonban pár nap elteltével tapasztalja, hogy az
 	  öregecske SCSI-meghajtó számos
 	  apróbb hibát jelez, és ezért
 	  szól Vilinek.</para>
 
 	<para>Néhány nappal késõbb Vili
 	  eldönti, ideje pontot tenni az ügy
 	  végére, ezért a raktárban
 	  levõ SCSI-lemezek köztül elhoz az eredetivel
 	  egy teljesen megegyezõt.  Az elõzetes
 	  felületellenõrzés eredményei szerint a
 	  meghajtó tökéletesen mûködik,
 	  ezért Vili beszerelni ezt a meghajtót a
 	  négyes SCSI-egységként, majd
 	  lemásolja a nullás meghajtó
 	  tartalmát a négyesre.  Miután beszerelte
 	  a tökéletesen üzemelõ új
 	  meghajtót, Vili úgy határoz, ideje
 	  megkezdeni a használatát, ezért
 	  beállítja a SCSI BIOS-át, hogy a rendszer
 	  a nullás helyett ezentúl a négyes
 	  egységrõl induljon.  A &os; elindul és
 	  mindenki örül.</para>
 
 	<para>Frédi ezután folytatja megszokott
 	  munkáját, majd Vili és Frédi
 	  úgy gondolják, itt az ideje az újabb
 	  izgalmaknak &mdash; frissítsünk a &os; egy
 	  újabb változatára.  Vili ekkor
 	  eltávolítja a nullás
 	  SCSI-egységet, mivel már egyébként
 	  is kezdett tönkremenni, és kicseréli egy
 	  másik teljesen azonos lemezes meghajtóra.  Vili
 	  ezt követõen Frédi internetrõl
 	  letöltött varázslatos floppyjainak
 	  segítségével feltelepíti a &os;
 	  új verzióját az új nullás
 	  SCSI-egységre.  A telepítés minden gond
 	  nélkül lezajlik.</para>
 
 	<para>Frédi próbálgatja is a &os; új
 	  változatát néhány napig, és
 	  számára ez elegendõ
 	  bizonyíték ahhoz, hogy a munkahelyén is
 	  használja.  Ideje hát átmásolni a
 	  régi munkáit, ezért Frédi
 	  csatlakoztatja a (korábbi &os; változat
 	  legfrissebb változatát tartalmazó)
 	  négyes SCSI-egységet.  Frédin azonban
 	  hirtelen aggodalom tör ki, hiszen a négyes
 	  SCSI-egységen sehol sem találja munkája
 	  féltett eredményeit.</para>
 
 	<para>Hova tûntek azok a komisz adatok?</para>
 
 	<para>Amikor Vili másolatot készített az
 	  eredeti nullás SCSI-egységrõl a
 	  négyes SCSI-egységre, a négyes
 	  egység egy <quote>új klón</quote> lett.
 	  Amikor a rendszerindításhoz Vili
 	  átrendezte a meghajtókat a SCSI BIOS-ban, azzal
 	  csak magát csapta be, ugyanis a &os; továbbra is
 	  a nullás SCSI-egységrõl indult el!  A BIOS
 	  által kiválasztott meghajtóról az
 	  effajta beállítások
 	  hatására ugyan behozható a
 	  rendszerindító és -betöltõ
 	  programok egy része, de amikor a &os; rendszermagja
 	  átveszi a vezérlést, a BIOS által
 	  meghatározott sorrendiség figyelmen
 	  kívül marad és a &os; visszatér a
 	  meghajtók eredeti rendezéséhez.
 	  Tehát ebben az esetben a rendszer továbbra is az
 	  eredeti nullás SCSI-egységrõl folytatja a
 	  mûködést, és Frédi összes
 	  adata itt található, nem pedig a négyes
 	  SCSI-egységen.  A négyes
 	  SCSI-egységrõl futó rendszer
 	  illuziója így mindössze az emberi
 	  elvárások szüleménye.</para>
 
 	<para>Örömmel említjük meg, hogy egyetlen
 	  byte-nyi adat sem sérült meg vagy pusztult el a
 	  jelenség felfedezése során.  A
 	  korábbi nullás SCSI-egységet még
 	  sikerült megmenteni a szemétdombról
 	  és Frédi összes munkája
 	  visszakerült (és Vili most már el tud
 	  számolni nulláig).</para>
 
 	<para>Habár a tanmesénkben
 	  SCSI-meghajtókról esett szó, ugyanez
 	  fennáll az IDE-meghajtókra is.</para>
       </sidebar>
 
     </sect2>
 
     <sect2 id="main-fdisk">
       <title>Slice-ok létrehozása az FDisk
 	használatával</title>
 
       <note>
 	<para>Itt még semmilyen változtatás nem
 	  kerül lemezre.  Ha úgy érezzük, hogy
 	  valamit rosszul csináltunk és újra el
 	  akarjuk kezdeni a telepítést, a menük
 	  segítségével büntetlenül
 	  távozhatunk a
 	  <application>sysinstall</application>ból és
 	  újra próbálkozhatunk, vagy az
 	  <keycap>U</keycap> billentyû lenyomásával
 	  aktiválhatjuk az <guimenuitem>Undo</guimenuitem>
 	  (<quote>Visszacsinál</quote>) funkciót.  Ha
 	  véletlenül összezavarodtunk volna és
 	  nem találunk kilépési
 	  lehetõséget, akkor bármikor ki tudjuk
 	  kapcsolni a számítógépet.</para>
       </note>
 
       <para>A <application>sysinstall</application>ban a
 	szabványos telepítés megkezdésekor
 	az alábbi üzenet jelenik meg:</para>
 
       <screen>                                 Message
  In the next menu, you will need to set up a DOS-style ("fdisk")
  partitioning scheme for your hard disk. If you simply wish to devote
  all disk space to FreeBSD (overwriting anything else that might be on
  the disk(s) selected) then use the (A)ll command to select the default
  partitioning scheme followed by a (Q)uit. If you wish to allocate only
  free space to FreeBSD, move to a partition marked "unused" and use the
  (C)reate command.
                                 [  OK  ]
 
                       [ Press enter or space ]</screen>
 
       <para>Az üzenet fordítása:</para>
 
       <screen>                                  Üzenet
  A most következõ menüben össze kell állítanunk a merevlemezünk
  DOS-szerû ("fdiskes") partícióit. Amennyiben egyszerûen csak át
  akarjuk adni az összes lemezterületet a FreeBSD számára (ezzel
  felülírva mindent, ami a kiválasztott lemezeken található), akkor
  az alapértelmezett partíció-kiosztás kiválasztásához használjuk az
  (A)ll (Mind), majd utána a (Q)uit (Kilépés) parancsokat. Ha viszont
  csak az éppen szabad területet szánjuk a FreeBSD-nek, lépjünk egy
  "unused" ("üres") feliratú partícióra és használjuk a (C)reate
  (Létrehozás) parancsot.
 
                                [  OK  ]
 
             [ Nyomja le az Enter vagy a Szóköz billentyût ]</screen>
 
       <para>Az utasításnak megfelelõen nyomjuk le az
 	<keycap>Enter</keycap> billentyût.  Ezután a
 	rendszermag által az eszközök
 	felkutatása során megtalált összes
 	merevlemezes meghajtót láthatjuk.  A <xref
 	linkend="sysinstall-fdisk-drive1"/> egy két IDE-lemezzel
 	rendelkezõ rendszert mutat be, amelyeknek nevei rendre
 	<devicename>ad0</devicename> és
 	<devicename>ad2</devicename>.</para>
 
       <figure id="sysinstall-fdisk-drive1">
 	<title>A meghajtó kiválasztása az FDisk
 	  számára</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-drive1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Feltûnhet, hogy itt nem szerepel az
 	<devicename>ad1</devicename>.  Vajon miért maradt
 	ki?</para>
 
       <para>Képzeljük el, mi történne, ha
 	két IDE-csatolós merevlemezünk lenne: az
 	egyik az elsõ IDE-vezérlõn, a másik
 	pedig a második IDE-vezérlõn lenne master.
 	Ha a &os; a megtalálásuk szerint
 	<devicename>ad0</devicename> és
 	<devicename>ad1</devicename> nevekkel számozná
 	ezeket, attól még minden remekül
 	mûködhetne.</para>
 
       <para>Ha azonban beszerelnénk egy harmadik lemezt,
 	például egy slave eszközt kapcsolnánk az
 	elsõ IDE-vezérlõre, akkor már ez lenne a
 	<devicename>ad1</devicename>, és ennek megfelelõen a
 	korábban <devicename>ad1</devicename>
 	megnevezésû meghajtó pedig az
 	<devicename>ad2</devicename>.  Mivel az
 	állományrendszerek felkutatására
 	általában az eszközneveket (mint amilyen a
 	<devicename>ad1s1a</devicename>) használják,
 	ezért ilyenkor azt tapasztalhatnánk, hogy bizonyos
 	állományrendszerek helytelenül jelennek meg,
 	ezért meg kell változtatnunk a &os; ezeket
 	érintõ beállításait.</para>
 
       <para>A probléma megoldására a rendszermag
 	beállítható úgy, hogy az
 	IDE-lemezeket a kapcsolódásuk szerint
 	azonosítsa, ne pedig a megtalálásuk
 	sorrendje szerint.  Ezzel a kialakítással a
 	második IDE-vezérlõn található
 	master lemez <emphasis>mindig</emphasis> az
 	<devicename>ad2</devicename> eszköz lesz, tehát
 	még olyankor is, amikor egyáltalán nincs a
 	rendszerünkben <devicename>ad0</devicename> vagy
 	<devicename>ad1</devicename> eszköz.</para>
 
       <para>Ez a beállítás
 	alapértelmezés a &os; rendszermagjában,
 	és ez magyarázza, hogy az iménti
 	ábra miért csak <devicename>ad0</devicename>
 	és <devicename>ad2</devicename> eszközöket
 	mutat.  Tehát a képen szereplõ
 	számítógép mind a két
 	IDE-vezérlõjének master
 	csatornáján található egy-egy
 	IDE-lemez, a slave csatornákon pedig nincs egy
 	sem.</para>
 
       <para>Itt válasszuk ki azt a lemezt, amelyre a &os;-t
 	telepíteni kívánjuk, majd nyomjuk meg a
 	&gui.ok; gombot.  Erre az <xref linkend="sysinstall-fdisk1"/>
 	által bemutatott képernyõvel elindul az
 	<application>FDisk</application>.</para>
 
       <para>Az <application>FDisk</application> képernyõje
 	három részre osztható.</para>
 
       <para>Az elsõ részben, amely a képernyõ
 	felsõ két sorát foglalja össze,
 	láthatjuk az éppen kiválasztott lemez
 	adatait: a &os; szerinti nevét, a paramétereit
 	és az összméretét.</para>
 
       <para>A második részben láthatjuk a lemezen
 	megtalálható slice-okat: hol kezdõdnek
 	(Offset) és hol érnek véget (End);
 	mekkorák (Size); a &os; milyen névvel hivatkozik
 	rájuk (Name); milyen leírás (Description)
 	és altípus (Subtype) tartozik hozzájuk.  A
 	példában két kicsi üres slice-ot
 	láthatunk, ami a PC-k lemezkiosztására
 	jellemzõ.  Ezenkívül felfedezhetünk egy
 	nagyobb méretû <acronym>FAT</acronym>
 	típusú slice-ot is, amely az &ms-dos; / &windows;
 	világban szinte minden bizonnyal a
 	<devicename>C:</devicename> betûjelet viseli, valamint egy
 	kiterjesztett slice-ot is, amely az &ms-dos; / &windows;
 	számára további meghajtókat is
 	tartalmazhat.</para>
 
       <para>A harmadik részben az
 	<application>FDisk</application>
 	mûködtetésére használható
 	parancsok láthatóak.</para>
 
       <figure id="sysinstall-fdisk1">
 	<title>Átlagos Fdisk partíciók
 	  szerkesztés elõtt</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-edit1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A most következõ teendõink attól
 	függenek, hogy miként is akarjuk felosztani a
 	lemezünket.</para>
 
       <para>Ha az egész lemezt a &os; használatára
 	áldozzuk (és amikor majd
 	megerõsítjük a
 	<application>sysinstall</application> számára a
 	továbblépést, a lemezen így minden
 	más adat törlõdni fog), akkor nyomjuk le az
 	<keycap>A</keycap> billentyût, amely megfelel a
 	<guimenuitem>Use Entire Disk</guimenuitem> (Az egész
 	lemez használata) menüpontnak.  A létezõ
 	slice-ok eltávolításra kerülnek
 	és helyettük megjelenik egy
 	<literal>unused</literal> (üres) jelzésû kis
 	méretû terület (elvégre PC-rõl
 	beszélünk), valamint egy nagyobb slice a &os;
 	számára.  Ha így jártunk el, akkor
 	válasszuk ki nyilakkal a frissen létrejött
 	&os; slice-ot és az <keycap>S</keycap> billentyû
 	lenyomásával jelöljük be
 	indíthatónak (bootable).  A képernyõ
 	ekkor a <xref linkend="sysinstall-fdisk2"/> által
 	mutatotthoz fog erõsen hasonlítani.  A
 	<literal>Flags</literal> (Beállítások)
 	oszlopban láthatjuk az <literal>A</literal>
 	jelzést, amelybõl kiderül, hogy az adott slice
 	<emphasis>aktív</emphasis>, tehát róla tud
 	indulni a rendszer.</para>
 
       <para>Ha a &os; számára egy meglevõ slice
 	törlésével szeretnénk helyet
 	csinálni, akkor ehhez válasszuk ki
 	nyílbillentyûkkel a használni kivánt
 	slice-ot és nyomjuk le a <keycap>D</keycap>
 	billentyût.  Ezután nyomjuk le a <keycap>C</keycap>
 	billentyût is, amire felbukkan a létrehozandó
 	slice méretét kérdezõ ablak.  Adjuk
 	meg a számunkra megfelelõ méretet a
 	számunkra megfelelõ formában, majd
 	zárjuk le az <keycap>Enter</keycap>
 	lenyomásával.  Az ablakban szereplõ
 	alapértelmezett érték a
 	létrehozható lehetõ legnagyobb
 	méretû slice-ot adja meg, ami vagy a legnagyobb
 	összefüggõ üres terület, vagy pedig az
 	egész merevlemez összterülete lehet.</para>
 
       <para>Ha már korábban
 	készítettünk elõ helyet a &os;-nek
 	(például egy
 	<application>&partitionmagic;</application> vagy egy
 	hozzá hasonló alkalmazás
 	segítségével), akkor csak elegendõ az
 	új slice létrehozásához megnyomnunk
 	a <keycap>C</keycap> billentyût.  Ekkor szintén
 	megkérdezésre kerül a
 	létrehozandó slice mérete.</para>
 
       <figure id="sysinstall-fdisk2">
 	<title>Particionálás az Fdisk <quote>Using Entire
 	  Disk</quote> funkciójával</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-edit2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Amikor befejeztük, nyomjuk le a <keycap>Q</keycap>
 	billentyût.  Ekkor a <application>sysinstall</application>
 	elmenti a beállított értékeket,
 	azonban a lemezre ekkor még nem kerülnek ki.</para>
 
     </sect2>
 
     <sect2 id="bootmgr">
       <title>A rendszerválasztó
 	telepítése</title>
 
       <para>Mindezek után lehetõségünk
 	nyílik telepíteni egy
 	rendszerválasztót (boot manager).
 	Általában véve akkor van
 	szükségünk a &os;
 	rendszerválasztójának
 	telepítésére, ha:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Egynél több meghajtónk van, és
 	    közülük nem az elsõ meghajtóra
 	    telepítjük a &os;-t.</para>
 	</listitem>
 
 	<listitem>
 	  <para>A &os;-t ugyanazon a lemezen más
 	    operációs rendszerek mellé
 	    telepítjük, és szeretnénk
 	    választhatóvá tenni, hogy a
 	    számítógép
 	    indításakor a &os; vagy a többi
 	    operációs rendszer induljon-e el.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Amennyiben a &os; lesz az egyetlen operációs
 	rendszer a gépünkön és az elsõ
 	merevlemezes meghajtóra telepítjük, akkor a
 	<guimenuitem>Standard</guimenuitem> (Szabványos)
 	rendszerválasztó tökéletesen megteszi.
 	Ha viszont a &os; indításához egy
 	másik rendszerválasztót szeretnénk
 	használni, válasszuk a
 	<guimenuitem>None</guimenuitem> (Nincs) opciót.</para>
 
       <para>Válasszunk, majd nyomjuk le az <keycap>Enter</keycap>
 	billentyût!</para>
 
       <figure id="sysinstall-bootmgr">
 	<title>A <application>sysinstall</application>
 	  rendszerválasztókat tartalmazó
 	  menüje</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/boot-mgr"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Az <keycap>F1</keycap> billentyû
 	lenyomásán keresztül elérhetõ
 	súgóképernyõn olvashatunk az egy
 	merevlemezen több operációs rendszer
 	használatával kapcsolatos
 	problémákról.</para>
 
     </sect2>
 
     <sect2>
       <title>Slice-ok létrehozása egy másik
 	meghajtón</title>
 
       <para>Ha egynél több meghajtónk van, a program
 	a rendszerválasztó képernyõje
 	után ismét visszatér a meghajtók
 	kiválasztásához.  Amennyiben a &os;-t egy
 	másik meghajtóra is telepíteni
 	szeretnénk, itt válasszuk ki azt és
 	ismételjük meg vele az imént az
 	<application>FDisk</application> programmal végzett
 	felosztási folyamatot.</para>
 
       <important>
 	<para>Amikor a &os;-t nem az elsõ meghajtóra
 	  telepítjük, akkor a &os;
 	  rendszerválasztóját mind a két
 	  meghajtóra telepíteni kell.</para>
       </important>
 
       <figure id="sysinstall-fdisk-drive2">
 	<title>Kilépés a
 	  meghajtóválasztó
 	  menübõl</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-drive2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A <keycap>Tab</keycap> billentyûvel tudunk
 	váltani a legutoljára kiválasztott
 	meghajtó, a &gui.ok; és a &gui.cancel; gombok
 	között.</para>
 
       <para>Az &gui.ok; gombra álláshoz nyomjuk le egyszer
 	a <keycap>Tab</keycap>ot, majd a telepítés
 	folytatásához nyomjuk le az <keycap>Enter</keycap>
 	billentyût.</para>
     </sect2>
 
     <sect2 id="bsdlabeleditor">
       <title>Partíciók létrehozása a
 	<application>Disklabel</application>
 	segítségével</title>
 
       <para>A következõ lépésként
 	létre kell hoznunk partíciókat a frissen
 	létrehozott slice-okban.  Ne felejtsük el, hogy
 	minden partíció rendelkezik egy
 	<literal>a</literal>-tól <literal>h</literal>-ig
 	terjedõ betûjellel, amelyek közül a
 	<literal>b</literal>, <literal>c</literal> és
 	<literal>d</literal> jelzésûeknek külön
 	szerepe van, amire tekintettel kell lennünk.</para>
 
       <para>Bizonyos alkalmazások kedvelnek egyes
 	partíciókiosztási sémákat,
 	különösen az egynél több lemezen
 	elhelyezkedõ partíciókat.  Azonban az
 	elsõ &os; telepítésünk során
 	még nem annyira fontos koncentrálnunk a
 	lemezünk hatékony felosztására.
 	Sokkal inkább fontosabb, hogy elõször
 	egyszerûen csak telepítsük a &os;-t és
 	tanuljuk meg a használatát.  Amikor már
 	jobban ismerni fogjuk az operációs rendszert, a
 	partíciók kiosztásának
 	megváltoztatásához mindig újra
 	tudjuk telepíteni a &os;-t.</para>
 
       <para>Ebben a sémában négy
 	partíció szerepel &mdash; egy a
 	lapozóállománynak és három az
 	állományrendszereknek.</para>
 
       <table frame="none" pgwide="1">
 	<title>Az elsõ lemez partícióinak
 	  kiosztása</title>
 
 	<tgroup cols="4">
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="4*"/>
 
 	  <thead>
 	    <row>
 	      <entry>Partíció</entry>
 	      <entry>Állományrendszer</entry>
 	      <entry>Méret</entry>
 	      <entry>Leírás</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><literal>a</literal></entry>
 	      <entry><filename>/</filename></entry>
 	      <entry>1&nbsp;GB</entry>
 	      <entry>Ez a rendszerindításhoz
 		használt, más néven a
 		gyökér állományrendszer (root
 		filesystem).  Minden további
 		állományrendszer ehhez csatlakozik
 		valahol.  Ennek az állományrendszernek
 		1&nbsp;GB méret elfogadható, mivel nem
 		fogunk túlságosan sok adatot
 		tárolni rajta, a &os; telepítõje is
 		csak nagyjából 128&nbsp;MB adatot fog ide tenni.  Az
 		így fennmaradó lemezterület
 		felhasználható átmeneti adatok
 		tárolására, illetve a
 		<filename>/</filename> könyvtárban helyet ad
 		a &os; késõbbi változatainak
 		terjeszkedéséhez is.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>b</literal></entry>
 	      <entry>-</entry>
 	      <entry>RAM mérete x 2-3</entry>
-	      <entry><footnote>
+	      <entry>
 		<para>A rendszer lapozóállománya a
 		  <literal>b</literal> partíción
 		  tárolódik.  Itt a megfelelõ
 		  méret megválasztása egyfajta
 		  mûvészet, azonban minden esetben
 		  hasznosnak bizonyulhat, ha tudjuk, hogy
 		  méretnek mindig érdemes a fizikai avagy
 		  központi memória (RAM)
 		  méretének két, esetleg
 		  háromszorosát választani.  Legyen
 		  mindig legalább 64&nbsp;MB-nyi
 		  méretû
 		  lapozóállományunk, és ha
 		  32&nbsp;MB RAM-nál kevesebb van a
 		  számítógépünkben,
 		  akkor is legalább 64&nbsp;MB-ra
 		  állítsuk be.</para>
 
 		<para>Ha egynél több lemezünk van,
 		  mindegyikre rakhatunk
 		  lapozóállományt, ezzel a &os;
 		  mindegyikõjüket fel tudja használni
 		  lapozásra, amivel pedig gyakorlatilag
 		  felgyorsítja a folyamatot.  Ilyenkor
 		  számoljunk úgy, hogy elõször
 		  meghatározzuk a teljes
 		  lapozóállomány
 		  méretét (például
 		  128&nbsp;MB), majd ezt elosztjuk a
 		  rendelkezésünkre álló
 		  lemezek számával (például
 		  kettõ).  Ebbõl
 		  kiszámítható az egyes lemezeken
 		  elhelyezendõ lapozóállomány
 		  mérete, ami most a példánk
 		  szerint 64&nbsp;MB lesz.</para>
-	      </footnote></entry>
+	      </entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>e</literal></entry>
 	      <entry><filename>/var</filename></entry>
 	      <entry>512&nbsp;MB-tl 4096&nbsp;MB-ig</entry>
 	      <entry>A <filename>/var</filename> könyvtár
 		foglalja magában az állandó
 		változó
 		naplóállományokat, valamint a
 		többi, adminisztrációhoz
 		használt állományt.  Ezek
 		többsége a &os; mindennapos
 		mûködése közben folyamatosan
 		íródnak vagy olvasódnak.  Ha ezeket
 		az állományokat egy külön
 		állományrendszerre rakjuk, akkor ezzel
 		segítünk a &os;-nek optimalizálni az
 		ilyen állományok
 		elérését anélkül, hogy
 		ez hatással lenne a többi, más
 		hozzáférési gyakorisággal
 		bíró állományra.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>f</literal></entry>
 	      <entry><filename>/usr</filename></entry>
 	      <entry>A lemez többi része (legalább
 		8&nbsp;GB)</entry>
 	      <entry>Az összes többi állomány
 		többnyire a <filename>/usr</filename>
 		könyvtárban és annak
 		alkönyvtáraiban helyezkedik el.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <warning>
 	<para>Az imént megadott értékeket csak
 	  példaként adtuk meg és csak a tapasztalt
 	  felhasználók számára
 	  ajánljuk.  A többi felhasználónak
 	  inkább a partíciók automatikus
 	  kiosztását javasoljuk a &os;
 	  partíciószerkesztõjében
 	  található <literal>Auto Defaults</literal>
 	  opció használatával.</para>
       </warning>
 
       <para>Ha a &os;-t egynél több lemezre
 	telepítjük, akkor a korábban megadott
 	többi slice-ban is létre kell hoznunk
 	partíciókat.  Ezt legegyszerûbben úgy
 	tehetjük meg, ha minden lemezen létrehozunk
 	két partíciót: egyet a
 	lapozóállománynak, egyet pedig az
 	állományrendszernek.</para>
 
       <table frame="none" pgwide="1">
 	<title>Több lemez partícióinak
 	  kiosztása</title>
 
 	<tgroup cols="4">
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="2*"/>
 	  <colspec colwidth="3*"/>
 
 	  <thead>
 	    <row>
 	      <entry>Partíció</entry>
 	      <entry>Állományrendszer</entry>
 	      <entry>Méret</entry>
 	      <entry>Leírás</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><literal>b</literal></entry>
 	      <entry>-</entry>
 	      <entry>Lásd a leírást</entry>
 	      <entry>Ahogy már korábban is
 		említettük, szét tudjuk osztani a
 		lapozóállományt a lemezek
 		között.  Habár az <literal>a</literal>
 		partíció szabad, a hagyományok
 		mégis azt diktálják, hogy a
 		lapozáshoz használt terület maradjon
 		a <literal>b</literal> partíción.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>e</literal></entry>
 	      <entry>/disk<replaceable>n</replaceable></entry>
 	      <entry>A lemez többi része</entry>
 	      <entry>A lemez fennmaradó része egyetlen
 		nagy partícióval fedhetõ le.  Ez az
 		<literal>e</literal> partíció helyett
 		lehetne minden további nélkül az
 		<literal>a</literal> partíció, azonban a
 		hagyományok szerint az <literal>a</literal>
 		partíciónak a rendszer gyökér
 		állományrendszerét
 		(<filename>/</filename>) kell tartalmaznia.  Nekünk
 		ugyan nem kellene ezt a megszokást
 		követnünk, azonban a
 		<application>sysinstall</application> viszont így
 		tesz, ezért ezzel a választással
 		csak magunkkal teszünk jót.  Az
 		állományrendszer bárhová
 		csatlakoztatható &mdash; ebben a
 		példában a lemezeket rendre a
 		<filename>/disk<replaceable>n</replaceable></filename>
 		könyvtárakhoz csatoltuk, ahol az
 		<replaceable>n</replaceable> az adott lemez
 		sorszáma.  De itt természetesen más
 		rendszert is követhetünk.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>A partíciók elrendezésének
 	kigondolása után most már létre is
 	hozathatjuk ezeket a <application>sysinstall</application>
 	segítségével.  Ekkor a következõ
 	üzenetet fogjuk látni:</para>
 
       <screen>                                 Message
  Now, you need to create BSD partitions inside of the fdisk
  partition(s) just created. If you have a reasonable amount of disk
  space (1GMB or more) and don't have any special requirements, simply
  use the (A)uto command to allocate space automatically. If you have
  more specific needs or just don't care for the layout chosen by
  (A)uto, press F1 for more information on manual layout.
 
                                 [  OK  ]
                           [ Press enter or space ]</screen>
 
       <para>Az üzenet fordítása:</para>
 
       <screen>                                  Üzenet
 Most létre kell hoznunk az fdiskkel nemrég elkészített partíciókban a
 BSD-s partíciókat. Ha van hozzá elegendõ helyünk (1G vagy több) és
 nincs semmilyen különleges elvárásunk, akkor egyszerûen csak osszuk
 fel automatikusan az (A)uto paranccsal. Amennyiben azonban ennél
 többre lenne szükségünk, vagy csak nincs szükségünk az (A)uto által
 felkínált sémára, az F1 lenyomására bõvebb információkat is kaphatunk
 a kézi kiosztás lehetõségeirõl.
 
                                 [  OK  ]
             [ Nyomja le az Enter vagy a Szóköz billentyût ]</screen>
 
       <para>Nyomjuk le a <keycap>Enter</keycap> billentyût a &os;
 	partíciószerkesztõjének, avagy a
 	<application>Disklabel</application>
 	elindításához.</para>
 
       <para>A <xref linkend="sysinstall-label"/> mutatja a
 	<application>Disklabel</application> elsõ
 	elindulásakor megjelenõ képet.  A
 	képernyõ három részre
 	tagolható.</para>
 
       <para>A felsõ pár sorban a jelenleg használt
 	lemez nevét láthatjuk, valamint azt a slice-ot,
 	ami az általunk létrehozott
 	partíciókat tartalmazza (itt a
 	<application>Disklabel</application> a <literal>Partition
 	name</literal> megnevezéssel hivatkozik a slice-ra).  A
 	képernyõn továbbá láthatjuk a
 	slice-ban levõ szabad helyet is, vagyis azt a helyet, amely
 	ugyan a slice-hoz tartozik, viszont még nem
 	rendeltünk hozzá partíciót.</para>
 
       <para>A képernyõ közepén
 	találhatóak az eddig már létrehozott
 	partíciók, az általuk tartalmazott
 	állományrendszerek, azok mérete és
 	az állományrendszerek
 	létrehozására vonatkozó
 	különbözõ
 	beállítások.</para>
 
       <para>A képernyõ alsó harmadában a
 	<application>Disklabel</application> programban
 	használható billentyûk felsorolása
 	szerepel.</para>
 
       <figure id="sysinstall-label">
 	<title>A <application>sysinstall</application> Disklabel
 	  partíciószerkesztõje</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-ed1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A <application>Disklabel</application> képes
 	magától partíciókat
 	készíteni a nekik megfelelõ
 	alapértelmezett méretekkel.  A
 	partíciók automatikus méretét egy
 	belsõ partícióméretezõ algoritmus
 	számítja ki a lemez összmérete
 	alapján.  Próbáljuk most mi is ezt ki,
 	és nyomjuk le az <keycap>A</keycap> billentyût.
 	Ekkor a <xref linkend="sysinstall-label2"/> szerint
 	illusztráltaknak megfelelõ képernyõt
 	tapasztalhatunk.  A használt lemez
 	méretétõl függõen az
 	alapértelmezett értékek megfelelõek
 	lesznek vagy sem.  Ez igazából nem
 	számít, hiszen nem kell feltétlenül
 	elfogadnunk az alapértelmezetten
 	megállapított értékeket.</para>
 
 	<note>
 	  <para>Az alapértelmezett
 	    partícionálási sémában a
 	    <filename>/tmp</filename> könyvtár nem a
 	    <filename>/</filename> könyvtár része
 	    lesz, hanem saját partíciót kapott.
 	    Ezzel igyekszünk elkerülni, hogy a
 	    <filename>/</filename> partíció
 	    átmenetileg tárolt állományokkal
 	    teljen be.</para>
 	</note>
 
       <figure id="sysinstall-label2">
 	<title>A <application>sysinstall</application> Disklabel
 	  partíciószerkesztõje,
 	  alapértelmezett értékekkel</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-auto"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Ha nem az alapértelmezett partíciókat
 	szeretnénk használni, és le akarjuk
 	váltani ezeket a saját magunk által
 	megadottakra, akkor a nyílbillentyûkkel
 	válasszuk ki az elsõ partíciót
 	és a törléséhez nyomjuk meg a
 	<keycap>D</keycap> billentyût.  Hasonlóan
 	járjunk el az összes többi javasolt
 	partíció törléséhez.</para>
 
       <para>Az elsõ (<literal>a</literal>, vagyis a
 	<filename>/</filename> könyvtárként, azaz a
 	gyökérként csatolt) partíció
 	elkészítéséhez elõször
 	gyõzõdjünk arról, hogy a felsõ sorban
 	a megfelelõ slice van kiválasztva, majd nyomjuk meg
 	a <keycap>C</keycap> billentyût.  Ekkor az új
 	partíció méretét kérdezõ
 	párbeszédablak jelenik meg (lásd: <xref
 	linkend="sysinstall-label-add"/>).  Itt a méret a lemez
 	blokkjainak számában adható meg, amit
 	viszont <literal>M</literal>-mel lezárva megabyte-ban,
 	<literal>G</literal>-vel gigabyte-ban vagy
 	<literal>C</literal>-vel cilinderben is
 	kifejezhetünk.</para>
 
       <figure id="sysinstall-label-add">
 	<title>Szabad hely a
 	  gyökérpartíción</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Az alapértelmezés szerint
 	felkínált méret az egész slice-ot
 	lefoglaló partíciót hoz létre.
 	Amennyiben a korábbi példában
 	tárgyalt partícióméreteket
 	kívánjuk használni, akkor a
 	<keycap>Backspace</keycap> billentyû
 	használatával töröljük ki az
 	így megadott értéket, és helyette
 	gépeljük be, hogy <userinput>512M</userinput>, ahogy
 	ez a <xref linkend="sysinstall-label-add2"/>
 	segítségével is látható.  A
 	bevitelt zárjuk a &gui.ok; gomb
 	lenyomásával.</para>
 
       <figure id="sysinstall-label-add2">
 	<title>A gyökérpartíció
 	  méretének szerkesztése</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Miután meghatároztuk a partíció
 	méretét, a telepítõ megkérdezi,
 	hogy a létrehozandó partícióban
 	állományrendszer vagy
 	lapozóállomány foglaljon-e helyet.  Ennek a
 	párbeszédablakját a <xref
 	linkend="sysinstall-label-type"/> mutatja.  Mivel az elsõ
 	partíciónk állományrendszert fog
 	tartalmazni, ezért mindenképpen az
 	<guimenuitem>FS</guimenuitem> paramétert válasszuk
 	ki, majd nyomjuk meg az <keycap>Enter</keycap>
 	billentyût.</para>
 
       <figure id="sysinstall-label-type">
 	<title>A gyökérpartíció
 	  típusának kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-fs"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Végezetül, mivel egy
 	állományrendszert hoztunk létre, meg kell
 	mondanunk a <application>Disklabel</application>nek, hova
 	csatlakoztassa.  A hozzá tartozó
 	párbeszédablak a <xref
 	linkend="sysinstall-label-mount"/>n látható.  A
 	gyökér állományrendszer
 	csatlakozási pontja a <filename>/</filename>,
 	ezért itt csak annyit adjunk meg, hogy
 	<userinput>/</userinput> és zárjuk az
 	<keycap>Enter</keycap> billentyû
 	lenyomásával.</para>
 
       <figure id="sysinstall-label-mount">
 	<title>A gyökér csatlakozási pontjának
 	  megadása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A képernyõn látható lista
 	ezután az újonnan létrehozott
 	partíciónak megfelelõen frissül.  A
 	többi partícióra ugyanígy meg kell
 	ismételnünk ezt a mûveletsort.  Arra azonban
 	figyeljünk, hogy a lapozásra használt
 	partíciót
 	létrehozásánál a szerkesztõ nem
 	fogja megkérdezni a csatlakozási pontot, hiszen az
 	ilyen típusú partíciókat sosem
 	csatlakoztatjuk.  A <filename>/usr</filename>, vagyis az
 	utolsó partíció
 	készítése során a slice
 	fennmaradó részének
 	lefoglalásához már nyugodtan meghagyhatjuk
 	a felajánlott értéket.</para>
 
       <para>A &os; partíciószerkesztõjének
 	utolsó képernyõje a <xref
 	linkend="sysinstall-label4"/>n hasonlóhoz, habár az
 	általunk választott értékek minden
 	bizonnyal eltérnek.  A mûvelet
 	befejezéséhez nyomjuk le a <keycap>Q</keycap>
 	billentyût.</para>
 
       <figure id="sysinstall-label4">
 	<title>A Disklabel partíciószerkesztõ</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-ed2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 id="install-choosing">
     <title>A telepítendõ összetevõk
       kiválasztása</title>
 
     <sect2 id="distset">
       <title>A terjesztések típusának
 	kiválasztása</title>
 
       <para>A telepítendõ terjesztések típusa
 	nagyban függ attól, hogy a rendszerünket mire
 	szándékozzuk majd használni és
 	mennyi szabad hely áll rendelkezésünkre.  Az
 	elõre megadott beállítások a
 	lehetõ legkisebb konfiguráció
 	telepítésétõl egészen a
 	komplett rendszer telepítéséig terjednek.
 	A &unix; és/vagy &os; világában még
 	az új felhasználók számára
 	szinte tökéletesen megfelelõnek bizonyulhat az
 	egyik ilyen elõkészített
 	beállítás kiválasztása.  A
 	terjesztések kiválogatása pedig
 	általában a tapasztaltabb
 	felhasználók számára lehet
 	hasznos.</para>
 
       <para>Az <keycap>F1</keycap> billentyûvel többet is
 	megtudhatunk a terjesztések különbözõ
 	típusairól és bennük
 	található összetevõkrõl.
 	Miután befejeztük a súgó
 	áttanulmányozását, nyomjuk le az
 	<keycap>Enter</keycap> billentyût, és ezzel
 	visszatérünk a terjesztések
 	kiválasztását tartalmazó
 	menübe.</para>
 
       <para>Ha grafikus felületet szeretnénk
 	használni, akkor az X szerver
 	beállítását az
 	alapértelmezett munkakörnyezet
 	beállítását a &os;
 	telepítése után kell megtenni.  Az X
 	szerver beállításáról
 	részletesebben a <xref linkend="x11"/>ban
 	olvashatunk.</para>
 
       <para>Ha egy saját rendszermag
 	építését is fontolgatjuk, akkor
 	olyan terjesztést válasszuk, amiben a
 	forráskód (kernel source) is
 	megtalálható.  A saját rendszermag
 	építésének
 	hátterérõl és
 	mikéntjérõl lásd a <xref
 	  linkend="kernelconfig"/>et.</para>
 
       <para>Értelemszerûen a legsokoldalúbb rendszer
 	az, amiben minden megtalálató.  Így
 	aztán, ha a lemezünk is megengedi, a nyilak
 	és az <keycap>Enter</keycap> használatával
 	válasszuk a <guimenuitem>All</guimenuitem> (Minden)
 	opciót, ahogy azt az <xref linkend="distribution-set1"/>
 	is mutatja.  Ha viszont úgy érezzük, hogy
 	ehhez nem eléggé nagy a lemezünk, akkor
 	válasszuk az igényeinkhez jobban illeszkedõ
 	típust.  Sokat azonban ne üljünk a
 	tökéletes megoldás
 	kiötlésén, hiszen ezek a terjesztések
 	még a telepítés befejezése
 	után is hozzáadhatóak a
 	rendszerünkhöz.</para>
 
       <figure id="distribution-set1">
 	<title>A terjesztések kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/dist-set"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
 
     <sect2 id="portscol">
       <title>A Portgyûjtemény
 	telepítése</title>
 
       <para>Miután kiválasztottuk a nekünk
 	megfelelõ terjesztést, a telepítõprogram
 	felajánlja a &os; Portgyûjteményének
 	(Ports Collection) telepítésének
 	lehetõségét.  A portok
 	gyûjteménye a szoftverek
 	telepítésének egyszerû és
 	kényelmes módja.  A Portgyûjtemény
 	önmaga nem tartalmazza a szoftverek
 	lefordításához szükséges
 	forráskódot, hanem helyette csupán azokat
 	az állományokat, amelyek a
 	különbözõ külsõs programok
 	letöltéséhez,
 	fordításához és
 	telepítéséhez kellenek.  A <xref
 	linkend="ports"/>ben megtalálhatjuk, miként is kell
 	használni ezt a gyûjteményt.</para>
 
       <para>A telepítõprogram nem fogja ellenõrizni a
 	kibontásához szükséges helyet,
 	ezért csak abban az esetben válasszuk ezt a
 	lehetõséget, ha mindenképpen elfér a
 	merevlemezünkön.  A &os; jelenlegi, &rel.current;
 	változatában a Portgyûjtemény
 	nagyjából &ports.size; helyet foglal el a lemezen.
 	A &os; frissebb verzióiban nyugodtan
 	feltételezhetünk ennél valamivel nagyobb
 	értéket is.</para>
 
 <screen>                         User Confirmation Requested
  Would you like to install the FreeBSD ports collection?
 
  This will give you ready access to over &os.numports; ported software packages,
  at a cost of around &ports.size; of disk space when "clean" and possibly much
  more than that if a lot of the distribution tarballs are loaded
  (unless you have the extra CDs from a FreeBSD CD/DVD distribution
  available and can mount it on /cdrom, in which case this is far less
  of a problem).
 
  The Ports Collection is a very valuable resource and well worth having
  on your /usr partition, so it is advisable to say Yes to this option.
 
  For more information on the Ports Collection &amp; the latest ports,
  visit:
      http://www.FreeBSD.org/ports
 
                               [ Yes ]     No</screen>
 
       <para>Az üzenet fordítása:</para>
 
 <screen>                      Felhasználói megerõsítés szükséges
  Szeretné telepíteni a FreeBSD portjainak gyûjteményét?
 
  Ezen keresztül közel &os.numports; portolt szoftvercsomaghoz tudunk
  könnyedén hozzáférni, amelyek "tiszta" állapotukban nagyjából
  &ports.size; lemezterületünkbe kerülnek, ami a késõbbiekben
  valószínûleg majd növekedni fog, ahogy letöltjük a különbözõ
  szoftverekhez tartozó állományokat (hacsak nincs meg a FreeBSD
  valamelyik CD- vagy DVD alapú terjesztésének az összes lemeze,
  amelyeket a /cdrom könyvtárba csatlakoztatva el tudjuk ezeket érni,
  mert ekkor kevesebb gondunk lesz vele).
 
  A Portgyûjtemény egy nagyon értékes erõforrás, amelynek megéri helyet
  szentelni a /usr partíciónkon, ezért javasoljuk, hogy válassza az
  "Igen" opciót. A Portgyûjteményrõl és annak legújabb portjairól a
  http://www.FreeBSD.org/ports oldalon olvashat részletesebben.
 
                              [ Igen ]     Nem</screen>
 
       <para>A Portgyûjtemény
 	telepítéséhez a &gui.yes; gombot, ennek
 	kihagyásához pedig a &gui.no; gombot
 	válasszuk ki a nyilakkal, majd az <keycap>Enter</keycap>
 	lenyomásával mehetünk tovább.  Ekkor a
 	kiválasztott terjesztések menüje fog
 	újra megjelenni.</para>
 
       <figure id="distribution-set2">
 	<title>A terjesztések telepítésének
 	  megerõsítése</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/dist-set2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Ha elégedettek vagyunk a
 	beállításokkal, válasszuk ki a
 	nyilakkal az <guimenuitem>Exit</guimenuitem> menüpontot,
 	gyõzõdjünk meg róla, hogy a &gui.ok;
 	gombon állunk, majd nyomjuk le az <keycap>Enter</keycap>
 	billentyût a folytatáshoz.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="install-media">
     <title>A telepítés eszközének
       kiválasztása</title>
 
     <para>Ha CD-rõl vagy DVD-rõl telepítünk, akkor
       a következõ képernyõn a
       nyílbillentyûkkel válasszuk ki a
       <guimenuitem>Install from a CDROM or DVD</guimenuitem>
       (Telepítés CD-rõl vagy DVD-rõl)
       menüpontot.  Ügyeljünk a &gui.ok; gomb
       kiválasztására is, majd a
       telepítés megkezdéséhez nyomjuk meg az
       <keycap>Enter</keycap> billenyût.</para>
 
     <para>A telepítés másfajta módszereinek
       alkalmazásához válasszuk ki a menüpontok
       közül a nekünk megfelelõt és
       kövessük a megjelenõ
       utasításokat.</para>
 
     <para>Az <keycap>F1</keycap> billentyû
       lenyomására megjelenik az adott
       telepítõeszközhöz tartozó
       súgó.  Innen az <keycap>Enter</keycap>
       lenyomása után térhetünk vissza a
       menühöz.</para>
 
     <figure id="choose-media">
       <title>A telepítési eszköz
 	kiválasztása</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="install/media"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
     <note>
       <title>Telepítés FTP szerverrõl</title>
 
       <indexterm>
 	<primary>telepítés</primary>
 	<secondary>hálózat</secondary>
 	<tertiary>FTP</tertiary>
       </indexterm>
 
       <para>Három FTP-s telepítési mód
 	közül választhatunk: aktív,
 	passzív vagy HTTP proxyn keresztül.</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>Aktív FTP: <guimenuitem>Install from an FTP
 	    server</guimenuitem> (Telepítés FTP
 	    szerverrõl)</term>
 
 	  <listitem>
 	    <para>Ezzel a beállítással az
 	      összes FTP-n keresztüli átvitel
 	      <quote>aktív</quote> módban
 	      történik.  Ez tûzfalak esetén nem
 	      mûködik, de gyakran alkalmazható olyan
 	      régebbi FTP szerverek esetén, amelyek nem
 	      ismerik az passzív adatátvitelt.  Ha (az
 	      alapértelmezett) passzív módban
 	      megakadna a kapcsolat, próbáljunk meg
 	      helyette az aktívat.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Passzív FTP: <guimenuitem>Install from an FTP
 	    server through a firewall</guimenuitem>
 	    (Telepítés tûzfalon keresztül FTP
 	    szerverrõl)</term>
 
 	  <listitem>
 	    <indexterm>
 	      <primary>FTP</primary>
 	      <secondary>passzív mód</secondary>
 	    </indexterm>
 
 	    <para>Ezzel a beállítással a
 	      <application>sysinstall</application> programot az FTP
 	      mûvelet végrehajtásakor a
 	      <quote>passzív</quote> mód
 	      használatára utasítjuk.  Így
 	      át tudunk menni olyan tûzfalakon is, amelyek
 	      nem engedik a véletlenszerû TCP portokon
 	      érkezõ kapcsolatokat.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>FTP HTTP proxyn keresztül: <guimenuitem>Install
 	    from an FTP server through a http proxy</guimenuitem>
 	    (Telepítés HTTP proxyn keresztül FTP
 	    szerverrõl)</term>
 
 	  <listitem>
 	    <indexterm>
 	      <primary>FTP</primary>
 	      <secondary>HTTP proxyn keresztül</secondary>
 	    </indexterm>
 
 	    <para>Ezzel a beállítással
 	      megmondhatjuk a <application>sysinstall</application>
 	      programnak, hogy (egy böngészõhöz
 	      hasonlóan) a HTTP protokollon keresztül
 	      használja az FTP mûveletek
 	      elvégzéséhez használt proxyt.
 	      Ennek a proxynak lesz a feladata az átadott
 	      kérések lefordítása és
 	      elküldése az FTP szervernek.  Ennek
 	      köszönhetõen át tudunk menni olyan
 	      tûzfalakon is, amelyek egyáltalán nem
 	      engednek semmilyen FTP mûveletet, azonban tartozik
 	      hozzájuk egy HTTP proxy.  Ilyenkor az FTP szerver
 	      beállításai mellett meg kell adnunk
 	      ezt a HTTP proxyt is.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>Az FTP szervert proxyn keresztül
 	általában úgy érjük el, hogy a
 	felhasználói név részeként
 	egy <quote>@</quote> jellel elválasztva megadjuk a
 	ténylegesen elérni kívánt szerver
 	nevét.  A proxy szerver ezután
 	<quote>helyettesíti</quote> a valódi szervert.
 	Például tegyük fel, hogy a <hostid
 	role="fqdn">ftp.FreeBSD.org</hostid> szerverrõl akarunk
 	telepíteni az 1234 porton várakozó <hostid
 	role="fqdn">ize.minta.com</hostid> proxy
 	használatával.</para>
 
       <para>Ehhez lépjünk be a
 	beállításokat tartalmazó
 	menübe, állítsuk az FTP kapcsolathoz
 	használt felhasználói nevet az
 	<literal>ftp@ftp.FreeBSD.org</literal> értékre,
 	majd jelszónak adjuk meg az e-mail címünket.
 	Telepítési eszközként adjuk meg az
 	FTP-t (vagy a passzív FTP-t, amennyiben a proxy ismeri)
 	és a
 	<literal>ftp://ize.minta.com:1234/pub/FreeBSD</literal>
 	címet.</para>
 
       <para>Mivel az <hostid role="fqdn">ftp.FreeBSD.org</hostid>
 	címrõl származó
 	<filename>/pub/FreeBSD</filename> könyvtár a <hostid
 	role="fqdn">ize.minta.com</hostid> szerveren keresztül
 	érhetõ el számunkra, ezért
 	lényegében <emphasis>arról</emphasis> a
 	géprõl fogunk telepíteni (amely pedig a
 	telepítõ kéréseire elhozza a <hostid
 	role="fqdn">ftp.FreeBSD.org</hostid> szervertõl az
 	állományokat).</para>
     </note>
 
   </sect1>
 
   <sect1 id="install-final-warning">
     <title>A telepítés
       véglegesítése</title>
 
     <para>Ezután ha óhajtjuk, megkezdhetjük a
       telepítést.  Ez egyben az utolsó
       lehetõségünk a telepítés
       megszakítására és merevlemezünket
       érintõ változtatások
       érvénytelenítésére.</para>
 
     <screen>                       User Confirmation Requested
  Last Chance! Are you SURE you want to continue the installation?
 
  If you're running this on a disk with data you wish to save then WE
  STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding!
 
  We can take no responsibility for lost disk contents!
 
                              [ Yes ]    No</screen>
 
     <para>Az üzenet fordítása:</para>
 
     <screen>                    Felhasználói megerõsítés szükséges
  Utolsó esély: BIZTOSAN folytatni kívánja a telepítést?
 
  Ha olyan lemezre szeretne telepíteni, amelyen fontos adatok
  találhatóak, HATÁROZOTTAN JAVASOLJUK, hogy a továbblépés elõtt
  KÉSZÍTSEN RÓLUK MEGBÍZHATÓ BIZTONSÁGI MÁSOLATOT!
 
  Nem vállalunk semmilyen felelõsséget az elvesztett adatokért!
 
                             [ Igen ]    Nem</screen>
 
     <para>A továbblépéshez válasszuk a
       &gui.yes; gombot és nyomjuk meg az <keycap>Enter</keycap>
       billentyût.</para>
 
     <para>A telepítés idõtartama a
       kiválasztott terjesztéstõl, a
       telepítésre használt eszköztõl
       és számítógépünk
       sebességétõl függ.  A folyamat
       elõrehaladásáról üzenetek sorozata
       tájékoztat minket.</para>
 
     <para>A telepítés befejezése után a
       következõ üzenet jelenik meg:</para>
 
     <screen>                               Message
 
 Congratulations! You now have FreeBSD installed on your system.
 
 We will now move on to the final configuration questions.
 For any option you do not wish to configure, simply select No.
 
 If you wish to re-enter this utility after the system is up, you may
 do so by typing: /usr/sbin/sysinstall.
 
                                  [ OK ]
 
                       [  Press enter or space  ]</screen>
 
     <para>A szöveg fordítása:</para>
 
     <screen>                               Üzenet
 
 Gratulálunk, sikeresen telepítette a FreeBSD rendszert a számítógépére!
 
 Most rátérünk az utolsó néhány kérdésre. A "Nem" választásával
 egyszerûen átugorhatjuk mindazt, amit nem szeretnénk beállítani. Ezt a
 segédprogramot a rendszer újbóli elindítása után a "/usr/sbin/sysinstall"
 parancs begépelésével tudjuk elérni.
 
                                  [ OK ]
 
             [ Nyomja le az Enter vagy a Szóköz billentyût ]</screen>
 
     <para>Az <keycap>Enter</keycap> billentyû
       lenyomásával megkezdhetjük a
       telepítés utáni
       beállításokat.</para>
 
     <para>A &gui.no; gomb kiválasztásával és
       az <keycap>Enter</keycap> lenyomásával
       megszakíthatjuk a telepítést, így a
       rendszerünkön semmilyen változtatás nem
       történik.  Ilyenkor a következõ üzenet
       jelenik meg:</para>
 
     <screen>                                Message
 Installation complete with some errors.  You may wish to scroll
 through the debugging messages on VTY1 with the scroll-lock feature.
 You can also choose "No" at the next prompt and go back into the
 installation menus to retry whichever operations have failed.
 
                                  [ OK ]</screen>
 
     <para>Az üzenet fordítása:</para>
 
     <screen>                                 Üzenet
 A telepítés során hiba történt. A Scroll Lock használatával érdemes
 átnézni a VTY1 terminál megjelenõ üzeneteket. A következõ ablakban a
 "Nem" választásával vissza tudunk menni a telepítõmenühöz és
 megpróbálkozhatunk ismét a sikertelen mûveletek végrehajtásával.
 
                                  [ OK ]</screen>
 
     <para>Ez az üzenet azért jelent meg, mert semmit sem
       sikerült telepíteni.  Innen az <keycap>Enter</keycap>
       megnyomásával térhetünk vissza a
       fõmenübe, majd onnan tudunk kilépni a
       telepítõbõl.</para>
 
   </sect1>
 
   <sect1 id="install-post">
     <title>A telepítés után</title>
 
     <para>A sikeres telepítést különféle
       beállítások követik.
       Közülük az új &os; rendszer
       indítása elõtt bármelyik
       megismételhetõ a beállítások
       opcióit tartalmazó menü újbóli
       használatával, vagy pedig a telepítés
       után a <command>sysinstall</command> parancs
       kiadásával, majd a
       <guimenuitem>Configure</guimenuitem>
       (Beállítások) menüpont
       kiválasztásával.</para>
 
     <sect2 id="inst-network-dev">
       <title>A hálózati eszközök
 	beállítása</title>
 
       <para>A következõ képernyõ már nem
 	jelenik meg, ha az FTP szerveren keresztüli
 	telepítéshez korábban már
 	beállítottuk a PPP kapcsolatot.  Ez a
 	korábbiakban említettek szerint
 	állítható be.</para>
 
       <para>Ha többet szeretnénk megtudni a helyi
 	hálózatokról (LAN), vagy a &os;-t
 	átjáróként, illetve
 	útválasztóként
 	kívánjuk beállítani, olvassuk el az
 	<link linkend="advanced-networking">Egyéb haladó
 	hálózati témák</link>
 	címû fejezetet.</para>
 
       <screen>                      User Confirmation Requested
    Would you like to configure any Ethernet or PPP network devices?
 
                              [ Yes ]   No</screen>
 
       <para>Fordítása:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
   Szeretnénk beállítani valamilyen Ethernet- vagy PPP hálózati eszközt?
 
                             [ Igen ]   Nem</screen>
 
       <para>A hálózati eszközeink
 	beállításához válasszuk a
 	&gui.yes; gombot, majd nyomjuk meg az <keycap>Enter</keycap>
 	billentyût.  Ellenkezõ esetben a &gui.no; gombbal
 	mehetünk tovább.</para>
 
       <figure id="ed-config1">
 	<title>Az Ethernet-eszköz
 	  kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ed0-conf"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A beállítandó csatoló
 	kiválasztásához használjuk a
 	nyílbillentyûket és utána nyomjuk meg
 	az <keycap>Enter</keycap> billentyût.</para>
 
       <screen>                      User Confirmation Requested
        Do you want to try IPv6 configuration of the interface?
 
                               Yes   [ No ]</screen>
 
       <para>Fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
            Megpróbálkozik az IPv6 beállításával a csatolón?
 
                              Igen   [ Nem ]</screen>
 
       <para>A példánkban szereplõ helyi
 	hálózatban az aktuális internetes protokoll
 	(<acronym>IPv4</acronym>) egyelõre megfelelõ,
 	ezért válasszuk a &gui.no; gombot és
 	nyomjuk meg az <keycap>Enter</keycap> billentyût.</para>
 
       <para>Amennyiben <acronym>RA</acronym>-szerveren keresztül
 	egy már létezõ <acronym>IPv6</acronym>
 	hálózathoz csatlakozunk, akkor válasszuk a
 	&gui.yes; gombot és nyomjuk meg az <keycap>Enter</keycap>
 	billentyût.  Ezt követõen az RA-szerverek
 	felderítése kezdõdik meg, ami
 	néhány másodpercig eltarthat.</para>
 
       <screen>                             User Confirmation Requested
         Do you want to try DHCP configuration of the interface?
 
                               Yes   [ No ]</screen>
 
       <para>Az üzenet fordítása:</para>
 
       <screen>                          Felhasználói megerõsítés szükséges
             Megpróbálkozik a DHCP használatával a csatolón?
 
                              Igen   [ Nem ]</screen>
 
       <para>Ha nincs szükségünk a DHCP (Dynamic Host
 	Configuration Protocol, azaz a Dinamikus
 	állomáskonfigurációs protokoll)
 	használatára, akkor a &gui.no; gomb
 	kiválasztásával majd az
 	<keycap>Enter</keycap> lenyomásával
 	továbbléphetünk.</para>
 
       <para>A &gui.yes; gomb kiválasztására elindul
 	a <application>dhclient</application> nevû program,
 	és amennyiben sikerrel jár, magától
 	kitölti a hálózati
 	beállításokra vonatkozó adatokat.
 	Ennek részleteit a <xref linkend="network-dhcp"/>ben
 	találhatjuk meg.</para>
 
       <para>Az alábbi hálózati
 	beállító képernyõ mutatja a
 	helyi hálózat
 	átjárójaként használni
 	kívánt Ethernet-eszköz
 	konfigurációját.</para>
 
       <figure id="ed-config2">
 	<title>Az ed0 hálózati
 	  beállítása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ed0-conf2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A <keycap>Tab</keycap> billentyûvel tudunk
 	navigálni az adatlap mezõi között
 	és kitölteni ezeket a megfelelõ
 	információkkal:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>Host
 	    (Számítógépnév)</term>
 
 	  <listitem>
 	    <para>A számítógépünk
 	      teljes neve, amely a példában most <hostid
 	      role="fqdn">k6-2.example.com</hostid>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Domain (Tartomány)</term>
 
 	  <listitem>
 	    <para>Annak a tartománynak a neve, amelyben a
 	      számítógépünk a
 	      található.  Ez itt konkrétan a
 	      <hostid role="domainname">example.com</hostid>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>IPv4 Gateway (IPv4-átjáró)</term>
 
 	  <listitem>
 	    <para>A helyben nem elérhetõ célok
 	      megközelítésére használt
 	      gép IP-címe.  Ezt a mezõt
 	      mindenképpen töltsük ki akkor, ha a
 	      számítógépünk valamilyen
 	      hálózatba van kötve.  Azonban
 	      <emphasis>hagyjuk üresen</emphasis>, ha a
 	      számítógép a
 	      hálózat átjárója az
 	      internet felé.  Az IPv4
 	      átjárót más néven
 	      <quote>default gateway</quote>-nek (alapértelmezett
 	      átjárónak) vagy <quote>default
 	      route</quote>-nak (alapértelmezett
 	      útvonalnak) is nevezik.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Name server (Névszerver)</term>
 
 	  <listitem>
 	    <para>A helyi DNS (névfeloldó) szerverünk
 	      IP-címe.  Ha nem található ilyen a
 	      helyi hálózatunkon, akkor az
 	      internet-szolgáltató DNS szerverének
 	      címét (a példában ez a <hostid
 	      role="ipaddr">208.163.10.2</hostid>) adjuk meg.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>IPv4 address (IPv4-cím)</term>
 
 	  <listitem>
 	    <para>A csatoló IP-címe, amely az
 	      ábrán a <hostid
 	      role="ipaddr">192.168.0.1</hostid>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Netmask (Hálózati maszk)</term>
 
 	  <listitem>
 	    <para>A helyi hálózatban használt
 	      címtartomány a <hostid
 	      role="ipaddr">192.168.0.0</hostid> - <hostid
 	      role="ipaddr">192.168.0.255</hostid>, amihez a <hostid
 	      role="netmask">255.255.255.0</hostid>
 	      hálózati maszk tartozik.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Extra options to ifconfig (Az ifconfig további
 	    beállításai)</term>
 
 	  <listitem>
 	    <para>Az <command>ifconfig</command> parancs adott
 	      csatolóra vonatkozó egyéb
 	      beállításai.  Jelen esetünkben
 	      itt semmi sem szerepel.</para>
 	  </listitem>
 	</varlistentry>
 
       </variablelist>
 
       <para>Miután végeztünk, a <keycap>Tab</keycap>
 	billentyû lenyomásával válasszuk ki a
 	&gui.ok; gombot és nyomjuk le az <keycap>Enter</keycap>
 	billentyût.</para>
 
       <screen>                      User Confirmation Requested
         Would you like to bring the ed0 interface up right now?
 
                              [ Yes ]   No</screen>
 
       <para>A fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
                      Aktiválja most az ed0 csatolót?
 
                             [ Igen ]   Nem</screen>
 
       <para>A &gui.yes; gomb kiválasztásával, majd
 	az <keycap>Enter</keycap> lenyomásával
 	csatlakoztatjuk a számítógépet a
 	hálózathoz, ami ezután
 	használhatóvá válik.  Ez azonban a
 	telepítés számára nem jelent
 	túlságosan sokat, hiszen ettõl
 	függetlenül a számítógépet
 	egyébként is újra kell majd
 	indítanunk.</para>
 
     </sect2>
 
     <sect2 id="gateway">
       <title>Az átjáró
 	beállítása</title>
 
       <screen>                       User Confirmation Requested
        Do you want this machine to function as a network gateway?
 
                               [ Yes ]    No</screen>
 
       <para>A fordítás:</para>
 
       <screen>                    Felhasználói megerõsítés szükséges
        Ezt a számítógépet hálózati átjáróként is használni akarja?
 
                              [ Igen ]    Nem</screen>
 
       <para>Ha a számítógépet a helyi
 	hálózat átjárójaként
 	használni akarjuk gépek közti csomagok
 	továbbítására, akkor
 	válasszuk a &gui.yes; gombot és nyomjuk meg
 	hozzá az <keycap>Enter</keycap> billentyût.  Ha
 	viszont ez a gép csupán a hálózat
 	egy tagja, akkor válasszuk a &gui.no; gombot és a
 	folytatáshoz nyomjuk meg az <keycap>Enter</keycap>
 	billentyût.</para>
 
     </sect2>
 
     <sect2 id="inetd-services">
       <title>A hálózati szolgáltatások
 	beállítása</title>
 
       <screen>                      User Confirmation Requested
 Do you want to configure inetd and the network services that it provides?
 
                                Yes   [ No ]</screen>
 
       <para>Fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
 Beállítja az inetd démont és az általa felkínált hálózati szolgáltatásokat?
 
                               Igen   [ Nem ]</screen>
 
       <para>Ha itt a &gui.no; gombot választjuk, akkor ezzel
 	kikapcsoljuk a különbözõ
 	szolgáltatásokat, például a
 	<application>telnetd</application> démont.  Ez azt
 	jelenti, hogy a távoli felhasználók nem
 	lesznek képesek a <application>telnet</application>
 	program használatával belépni erre a
 	számítógépre.  A helyi
 	felhasználók viszont továbbra is
 	képesek lesznek távoli
 	számítógépeket elérni a
 	<application>telnet</application>
 	segítségével.</para>
 
       <para>Az <filename>/etc/inetd.conf</filename>
 	átírásával azonban ezek a
 	szolgáltatások késõbb
 	természetesen engedélyezhetõek.  A <xref
 	linkend="network-inetd-overview"/> foglalkozik a téma
 	részleteivel.</para>
 
       <para>A &gui.yes; gomb választásával
 	már a telepítés során
 	beállíthatjuk a szolgáltatásokat.
 	Ekkor egy további párbeszédablak is
 	felbukkan:</para>
 
       <screen>                      User Confirmation Requested
 The Internet Super Server (inetd) allows a number of simple Internet
 services to be enabled, including finger, ftp and telnetd.  Enabling
 these services may increase risk of security problems by increasing
 the exposure of your system.
 
 With this in mind, do you wish to enable inetd?
 
                              [ Yes ]   No</screen>
 
       <para>Fordítása:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
 A fõ internetes kiszolgáló (az inetd) számos egyszerû internetes
 szolgáltatás, többek közt a finger, ftp és telnet elérését teszi
 lehetõvé. Ezen szolgáltatások engedélyezése azonban a felmerülõ
 biztonsági problémák kockázatát, mivel ezzel rendszerünket jobban
 kitesszük támadásoknak.
 
 Mindezek tudatában használni kívánja az inetd démont?
 
                             [ Igen ]   Nem</screen>
 
       <para>A folytatáshoz válasszuk a &gui.yes;
 	gombot.</para>
 
       <screen>                      User Confirmation Requested
 inetd(8) relies on its configuration file, /etc/inetd.conf, to determine
 which of its Internet services will be available.  The default FreeBSD
 inetd.conf(5) leaves all services disabled by default, so they must be
 specifically enabled in the configuration file before they will
 function, even once inetd(8) is enabled.  Note that services for
 IPv6 must be separately enabled from IPv4 services.
 
 Select [Yes] now to invoke an editor on /etc/inetd.conf, or [No] to
 use the current settings.
 
                              [ Yes ]   No</screen>
 
       <para>Fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
 Az inetd(8) démonnak az elérhetõ internetes szolgáltatások
 megállapításához szüksége van a beállításait tartalmazó
 /etc/inetd.conf állományra. A FreeBSD-hez tartozó inetd.conf(5)
 állomány alapértelmezés szerint az összes szolgáltatást letiltja,
 ezért a mûködéséhez minden egyes szolgáltatást külön kell engedélyezni
 az említett állományban, még abban az esetben is, ha az inetd(8)
 démont korábban már engedélyeztük. Az IPv6 szolgáltatások az IPv4
 szolgáltatásoktól külön engedélyezendõek.
 
 Az [ Igen ] választásával behívjuk az /etc/inetd.conf szerkesztését,
 míg a [ Nem ] választásával pedig az imént felvázolt beállításokat
 fogadjuk el.
 
                             [ Igen ]   Nem</screen>
 
       <para>A &gui.yes; gomb kiválasztásával
 	lehetõségünk nyílik
 	szolgáltatásokat engedélyezni a sorok
 	elején található <literal>#</literal> jel
 	törlésével.</para>
 
       <figure id="inetd-edit">
 	<title>Az <filename>inetd.conf</filename>
 	  módosítása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/edit-inetd-conf"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Miután felvettük az összes használni
 	kívánt szolgáltatást, az
 	<keycap>Esc</keycap> billentyû lenyomásával
 	elõhozhatjuk azt a menüt, ahol elmenthetjük a
 	módosításainkat és
 	kiléphetünk.</para>
 
     </sect2>
 
     <sect2 id="ssh-login">
       <title>Az SSH-n keresztüli bejelentkezés
 	engedélyezése</title>
 
       <indexterm>
 	<primary>SSH</primary>
 	<secondary>sshd</secondary>
       </indexterm>
 
       <screen>                      User Confirmation Requested
                   Would you like to enable SSH login?
                            Yes        [  No  ]</screen>
 
       <para>Fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
                Engedélyezi az SSH-n keresztüli bejelentkezést?
                           Igen        [  Nem  ]</screen>
 
       <para>A &gui.yes; gomb kiválasztása
 	engedélyezi az <application>OpenSSH</application>-hoz
 	tartozó &man.sshd.8; démont, aminek
 	segítségével a
 	számítógépünkre
 	biztonságosan be tudunk jelentkezni
 	távolról.  Az <application>OpenSSH</application>
 	részleteirõl lásd a <xref
 	linkend="openssh"/>t.</para>
 
     </sect2>
 
     <sect2 id="ftpanon">
       <title>Anonim FTP</title>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>anonim</secondary>
       </indexterm>
 
       <screen>                      User Confirmation Requested
  Do you want to have anonymous FTP access to this machine?
 
                               Yes    [ No ]</screen>
 
       <para>Fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
  Hozzáférhetõ legyen ez a számítógép anonim FTP használatán keresztül?
 
                              Igen    [ Nem ]</screen>
 
       <sect3 id="deny-anon">
 	<title>Az anonim FTP tiltása</title>
 
 	<para>Az alapértelmezett &gui.no; gomb
 	  kiválasztásával és az
 	  <keycap>Enter</keycap> billentyû
 	  lenyomásával a jelszóval védett
 	  FTP hozzáféréssel rendelkezõ
 	  felhasználók továbbra is elérhetik
 	  a számítógépünket.</para>
 
       </sect3>
 
       <sect3 id="ftpallow">
 	<title>Az anonim FTP engedélyezése</title>
 
 	<para>Ha ezt választjuk, akkor anonim FTP kapcsolaton
 	  keresztül bárki hozzáférhet a
 	  számítógépünkhöz.  Ebben
 	  az esetben azonban alaposan meg kell fontolnunk
 	  néhány biztonsági
 	  következményt.  A
 	  beállítással járó
 	  kockázatokról az <xref linkend="security"/>ben
 	  olvashatunk többet.</para>
 
 	<para>Az anonim FTP bekapcsolásához a
 	  nyílbillentyûkkel válasszuk ki a &gui.yes;
 	  feliratú gombot és nyomjuk meg az
 	  <keycap>Enter</keycap> billentyût.  Ekkor egy
 	  további párbeszédablak is
 	  megjelenik:</para>
 
 	<screen>                       User Confirmation Requested
  Anonymous FTP permits un-authenticated users to connect to the system
  FTP server, if FTP service is enabled.  Anonymous users are
  restricted to a specific subset of the file system, and the default
  configuration provides a drop-box incoming directory to which uploads
  are permitted.  You must separately enable both inetd(8), and enable
  ftpd(8) in inetd.conf(5) for FTP services to be available.  If you
  did not do so earlier, you will have the opportunity to enable inetd(8)
  again later.
 
  If you want the server to be read-only you should leave the upload
  directory option empty and add the -r command-line option to ftpd(8)
  in inetd.conf(5)
 
  Do you wish to continue configuring anonymous FTP?
 
                           [ Yes ]         No</screen>
 
 	<para>Az üzenet fordítása:</para>
 
 	<screen>                     Felhasználói megerõsítés szükséges
 
  Az anonim FTP használatával a rendszer FTP szolgáltatásához
  hitelesítetlen felhasználók is hozzáférhetnek, amennyiben az aktív. A
  névtelen felhasználók az állományrendszernek csak egy részét érhetik
  el, valamint az alapbeállítások szerint a feltöltést egy külön erre
  a célra fenntartott könyvtárba végezhetik el. Az FTP szolgáltatás
  használatát külön engedélyeznünk kell az inetd(8) démon részérõl és
  az inetd.conf(5) állományban található ftpd(8) démon aktiválásával.
  Ha eddig még nem tettük volna meg, akkor az inetd(8) használatát
  késõbb még újra engedélyezhetjük.
 
  Ha csak letöltést kívánunk engedni, akkor hagyjuk a feltöltési
  könyvtárra vonatkozó paramétert üresen és az inetd.conf(5)
  állományban az ftpd(8) parancssorához adjuk hozzá az -r kapcsolót.
 
  Folytatja az anonim FTP beállítását?
 
                          [ Igen ]         Nem</screen>
 
 	<para>Az üzenet értesít minket arról,
 	  hogy az anonim FTP kapcsolatok
 	  engedélyezéséhez az FTP
 	  szolgáltatást az
 	  <filename>/etc/inetd.conf</filename> állományban
 	  is be kell majd kapcsolni, lásd <xref
 	  linkend="inetd-services"/>.  Válasszuk a &gui.yes;
 	  gombot és a folytatáshoz nyomjuk meg az
 	  <keycap>Enter</keycap> billentyût.  Ekkor a
 	  következõ képernyõ jön
 	  elõ:</para>
 
 	<figure id="anon-ftp2">
 	  <title>Az anonim FTP
 	    alapbeállításai</title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/ftp-anon1"/>
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
 	<para>A beállítások kitöltése
 	  során a <keycap>Tab</keycap> billentyûvel
 	  mozoghatunk az adatmezõk között:</para>
 
 	<variablelist>
 	  <varlistentry>
 	    <term>UID (felhasználói
 	      azonosító)</term>
 
 	    <listitem>
 	      <para>A névtelen FTP felhasználókhoz
 		társított felhasználói
 		azonosító.  A feltöltött
 		állomány tulajdonosa ez az
 		azonosító lesz.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>Group (csoport)</term>
 
 	    <listitem>
 	      <para>A névtelen FTP felhasználók
 		csoportja.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>Comment (megjegyzés)</term>
 
 	    <listitem>
 	      <para>Ez a szöveg szerepel a
 		felhasználónál az
 		<filename>/etc/passwd</filename>
 		állományban.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>FTP Root Directory (az FTP gyökere)</term>
 
 	    <listitem>
 	      <para>Itt találhatóak az anonim FTP-n
 		keresztül elérhetõ
 		állományok.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>Upload Subdirectory (feltöltési
 	      könyvtár)</term>
 
 	    <listitem>
 	      <para>A névtelen FTP felhasználók
 		által feltöltött
 		állományok ide kerülnek.</para>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
 
 	<para>Az FTP gyökere alapból a
 	  <filename>/var</filename> könyvtár lesz.  Ha a
 	  becsült FTP-forgalom
 	  lebonyolításához itt nem
 	  rendelkezünk elegendõ hellyel, akkor az
 	  <filename>/usr</filename> könyvtárban
 	  található <filename>/usr/ftp</filename>
 	  alkönyvtár is beállítható az
 	  FTP gyökerének.</para>
 
 	<para>Ha elfogadhatónak találjuk az
 	  értékeket, nyomjuk le az <keycap>Enter</keycap>
 	  billentyût a folytatáshoz.</para>
 
 	<screen>                          User Confirmation Requested
          Create a welcome message file for anonymous FTP users?
 
                               [ Yes ]    No</screen>
 
 	<para>Fordítás:</para>
 
 	<screen>                       Felhasználói megerõsítés szükséges
         Létre kíván hozni egy köszöntõ üzenetet tartalmazó állományt
         az anonim FTP felhasználók számára?
 
                              [ Igen ]    Nem</screen>
 
 	<para>A &gui.yes; választásával és
 	  az <keycap>Enter</keycap> megnyomásával az
 	  üzenet szerkesztéséhez egy
 	  szövegszerkesztõ fog elindulni.</para>
 
 	<figure id="anon-ftp4">
 	  <title>Az FTP köszöntõ üzenetének
 	    szerkesztése</title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/ftp-anon2"/>
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
 	<para>Ez az <command>ee</command> szövegszerkesztõ.
 	  Az üzenet átírásához
 	  használjuk a megadott utasításokat, de
 	  akár késõbb is módosíthatjuk
 	  ezt a kedvenc szövegszerkesztõnkkel.  Ehhez a
 	  módosítandó állomány neve
 	  és helye a szerkesztõ
 	  képernyõjének alján
 	  olvasható.</para>
 
 	<para>A kilépéshez az <keycap>Esc</keycap>
 	  lenyomására felbukkanó menüben
 	  alapból az <guimenuitem>a) leave editor</guimenuitem>
 	  (kilépés a szerkesztõbõl)
 	  menüpont érhetõ el, ezért itt az
 	  <keycap>Enter</keycap> lenyomásával
 	  léphetünk tovább.  Az
 	  <keycap>Enter</keycap> ismételt
 	  lenyomásával elmenthetjük a
 	  módosításainkat.</para>
 
       </sect3>
     </sect2>
 
     <sect2 id="nfsconf">
       <title>A hálózati állományrendszer
 	beállítása</title>
 
       <para>A hálózati állományrendszer
 	(Network File System, NFS) állományok
 	közzétételét teszi
 	lehetõvé hálózaton keresztül.
 	Használata során egy
 	számítógép
 	beállítható szervernek, kliensnek vagy
 	akár mindkettõnek.  Ezzel kapcsolatban a <xref
 	linkend="network-nfs"/> ajánlott
 	elolvasásra.</para>
 
       <sect3 id="nsf-server-options">
 	<title>Az NFS szerver</title>
 
 	<screen>                       User Confirmation Requested
  Do you want to configure this machine as an NFS server?
 
                               Yes    [ No ]</screen>
 
 	<para>A fordítása:</para>
 
 	<screen>                   Felhasználói megerõsítés szükséges
    Be akarja állítani NFS szervernek ezt a számítógépet?
 
                              Igen    [ Nem ]</screen>
 
 	<para>Ha nincs szükségünk a
 	  hálózati állományrendszer szerver
 	  részére, akkor válasszuk a &gui.no;
 	  gombot és nyomjuk le az <keycap>Enter</keycap>
 	  billentyût.</para>
 
 	<para>Amennyiben a &gui.yes; gombot választjuk, egy
 	  üzenet fogja közölni velünk, hogy
 	  létre kell hoznunk az <filename>exports</filename>
 	  állományt.</para>
 
 	<screen>                               Message
 Operating as an NFS server means that you must first configure an
 /etc/exports file to indicate which hosts are allowed certain kinds of
 access to your local filesystems.
 Press [Enter] now to invoke an editor on /etc/exports
                                [ OK ]</screen>
 
 	<para>Az üzenet fordítása:</para>
 
 	<screen>                               Üzenet
 Az NFS szerver mûködtetéséhez elõször az /etc/exports állomány
 összeállításán keresztül meg kell adnunk, hogy milyen gépek milyen
 típusú hozzáféréssel rendelkezzenek a helyi állományrendszereinken.
 Az [Enter] lenyomására megkezdõdik az /etc/exports állomány
 szerkesztése.
                               [ OK ]</screen>
 
 	<para>Az <keycap>Enter</keycap> billentyû
 	  lenyomásával továbbléphetünk.
 	  Ekkor az <filename>exports</filename> állomány
 	  létrehozására és
 	  szerkesztésére egy szövegszerkesztõ
 	  indul el.</para>
 
 	<figure id="nfs-server-edit">
 	  <title>Az <filename>exports</filename>
 	    szerkesztése</title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/nfs-server-edit"/>
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
 	<para>A exportálni kívánt
 	  állományrendszerek felsorolásához
 	  használjuk képernyõn a megadott
 	  utasításokat, vagy tegyük meg ezt
 	  késõbb az általunk választott
 	  szövegszerkesztõ segítségével.
 	  Ilyenkor ne felejtsük el megjegyezni az
 	  állomány képernyõ alján
 	  látható nevét és
 	  helyét.</para>
 
 	<para>Amikor végeztünk, az <keycap>Esc</keycap>
 	  billentyûvel felhozható menüben
 	  alapból az <guimenuitem>a) leave editor</guimenuitem>
 	  (kilépés a szövegszerkesztõbõl)
 	  menüpont aktív, ezért itt a
 	  folytatáshoz egyszerûen nyomjuk le az
 	  <keycap>Enter</keycap> billentyût.</para>
 
       </sect3>
 
       <sect3 id="nfs-client-options">
 	<title>Az NFS kliens</title>
 
 	<para>Az NFS kliens beállításával
 	  NFS szerverekhez tudunk hozzáférni.</para>
 
 	<screen>                       User Confirmation Requested
  Do you want to configure this machine as an NFS client?
 
                               Yes   [ No ]</screen>
 
 	<para>Fordítás:</para>
 
 	<screen>                    Felhasználói megerõsítés szükséges
       Beállítja NFS kliensnek ezt a számítógépet?
 
                              Igen   [ Nem ]</screen>
 
 	<para>A nyílbillentyûkkel igényeinknek
 	  megfelelõen válasszuk a &gui.yes; vagy &gui.no;
 	  gombokat és utána nyomjuk meg az
 	  <keycap>Enter</keycap> billentyût.</para>
 
       </sect3>
     </sect2>
 
     <sect2 id="console">
       <title>A rendszerkonzol beállításai</title>
 
       <para>Számos beállítás
 	kapcsolódik a rendszerben található
 	konzolok testreszabásához.</para>
 
       <screen>                      User Confirmation Requested
        Would you like to customize your system console settings?
 
                               [ Yes ]  No</screen>
 
       <para>Fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
                Testreszabja a rendszerkonzol beállításait?
 
                              [ Igen ]  Nem</screen>
 
       <para>A beállítások
 	megtekintéséhez és
 	megváltoztatásához válasszuk a
 	&gui.yes; gombot és nyomjuk le az <keycap>Enter</keycap>
 	billentyût.</para>
 
       <figure id="saver-options">
 	<title>A rendszerkonzol beállításai</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A képernyõkímélõ
 	beállítása egy gyakori opció.  A
 	nyilak használatával álljunk a
 	<guimenuitem>Saver</guimenuitem> menüpontra, majd nyomjuk
 	le az <keycap>Enter</keycap> billentyût.</para>
 
       <figure id="saver-select">
 	<title>A képernyõkímélõ
 	  beállításai</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A nyilakkal válasszuk ki a használni
 	kívánt
 	képernyõkímélõt és nyomjuk
 	meg hozzá az <keycap>Enter</keycap> billentyût.
 	Ekkor a rendszerkonzol beállításait
 	tartalmazó menü jelenik meg ismét.</para>
 
       <para>Az aktivizálódás ideje
 	alapbeállítás szerint 300 másodperc.
 	Ennek megváltoztatásához válasszuk
 	ismét a <guimenuitem>Saver</guimenuitem> menüpontot.
 	A képernyõkímélõ
 	beállításait tartalmazó menüben
 	a nyílbillentyûkkel válasszuk a
 	<guimenuitem>Timeout</guimenuitem> (Idõkorlát)
 	menüpontot és nyomjuk meg az <keycap>Enter</keycap>
 	billentyût.  Ekkor egy párbeszédablak jelenik
 	meg:</para>
 
       <figure id="saver-timeout">
 	<title>A képernyõkímélõhöz
 	  tartozó idõkorlát
 	  beállítása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Miután megváltoztattuk az
 	értéket, a rendszerkonzol
 	beállításához a &gui.ok; gomb
 	kiválasztásával, majd az
 	<keycap>Enter</keycap> billentyû lenyomásával
 	térhetünk vissza.</para>
 
       <figure id="saver-exit">
 	<title>Kilépés a rendszerkonzol
 	  beállító
 	  menüjébõl</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver4"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A <guimenuitem>Exit</guimenuitem> (Kilépés)
 	választásával és az
 	<keycap>Enter</keycap> lenyomásával folytathatjuk
 	tovább a telepítés utólagos
 	beállításait.</para>
 
     </sect2>
 
     <sect2 id="timezone">
       <title>Az idõzóna
 	beállítása</title>
 
       <para>Ha kiválasztjuk
 	számítógépünk
 	számára a megfelelõ
 	idõzónát, akkor lehetõvé
 	tesszük, hogy magától elvégezze a
 	helyi idõhöz kapcsolódó összes
 	szükséges korrekciót és helyesen
 	kezelje az idõzónákhoz
 	kapcsolódó többi funkciót.</para>
 
       <para>A példában az Egyesült Államok
 	keleti idõzónájában elhelyezkedõ
 	számítógépet láthatunk.  A mi
 	beállításaink természetesen a
 	saját földrajzi helyzetünktõl
 	függenek.</para>
 
       <screen>                      User Confirmation Requested
           Would you like to set this machine's time zone now?
 
                             [ Yes ]   No</screen>
 
       <para>Fordítás:</para>
 
       <screen>                    Felhasználói megerõsítés szükséges
                  Beállítja most a számítógép idõzónáját?
 
                            [ Igen ]   Nem</screen>
 
       <para>A &gui.yes; gomb és az <keycap>Enter</keycap>
 	billentyû segítségével
 	kiválaszthatjuk az idõzóna
 	beállítását.</para>
 
       <screen>                       User Confirmation Requested
  Is this machine's CMOS clock set to UTC? If it is set to local time
  or you don't know, please choose NO here!
 
                               Yes   [ No ]</screen>
 
       <para>Fordítás:</para>
 
       <screen>                     Felhasználói megerõsítés szükséges
  A számítógép órája az egységes világidõhöz (UTC) van beállítva? Ha a
  helyi idõhöz vagy nem tudjuk, akkor itt válasszuk a NEM gombot!
 
                              Igen   [ Nem ]</screen>
 
       <para>A számítógépünk
 	órájának
 	beállításának megfelelõen
 	válasszuk a &gui.yes; vagy &gui.no; gombot, és
 	nyomjuk meg az <keycap>Enter</keycap> billentyût.</para>
 
       <figure id="set-timezone-region">
 	<title>A térség kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A nyilakkal kiválasztható a megfelelõ
 	térség, amit aztán az
 	<keycap>Enter</keycap> billentyûvel tudunk
 	lezárni.</para>
 
       <figure id="set-timezone-country">
 	<title>Az ország kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A megfelelõ ország a
 	nyílbillentyûkkel, valamint az
 	<keycap>Enter</keycap> billentyûvel
 	választható ki.</para>
 
       <figure id="set-timezone-locality">
 	<title>Az idõzóna kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A nekünk megfelelõ idõzóna a nyilakkal
 	választható meg, amit ezután az
 	<keycap>Enter</keycap> billentyûvel tudunk
 	jóváhagyni.</para>
 
       <screen>                            Confirmation
             Does the abbreviation 'EDT' look reasonable?
 
                             [ Yes ]   No</screen>
 
       <para>Az üzenet fordítása:</para>
 
       <screen>                             Megerõsítés
                  Ezek szerint az 'EDT' elfogadható?
 
                            [ Igen ]   Nem</screen>
 
       <para>Erõsítsük meg, hogy az idõzóna
 	helyes-e.  Ha rendbenlevõnek látszik, nyomjuk meg az
 	<keycap>Enter</keycap> billentyût a
 	folytatáshoz.</para>
     </sect2>
 
     <sect2 id="linuxcomp">
       <title>Linux binárisok használata</title>
 
       <note>
 	<para>Ez a rész csak a
 	  &os;&nbsp;7.<replaceable>X</replaceable>
 	  telepítésére vonatkozik,
 	  &os;&nbsp;8.<replaceable>X</replaceable> esetén ez a
 	  képernyõ nem jelenik meg.</para>
       </note>
 
       <screen>                      User Confirmation Requested
           Would you like to enable Linux binary compatibility?
 
                             [ Yes ]   No</screen>
 
       <para>A fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
                Engedélyezi a Linux binárisok futtatását?
 
                            [ Igen ]   Nem</screen>
 
       <para>A &gui.yes; gomb kiválasztásával
 	és az <keycap>Enter</keycap> lenyomásával
 	megengedjük, hogy a Linuxra készült
 	szoftvereket futtassunk &os;-n.  A telepítõ ennek
 	biztosításához még további
 	csomagokat is fel fog rakni.</para>
 
       <para>Ha FTP-n keresztül telepítünk, akkor a
 	számítógépnek csatlakoznia kell az
 	internetre.  Ilyenkor elõfordulhat, hogy az FTP szerveren
 	nem találhatóak meg a &linux;
 	kompatibilitással kapcsolatos csomagok.  Ezeket azonban
 	késõbb is telepíthetjük.</para>
 
     </sect2>
 
     <sect2 id="mouse">
       <title>Az egér beállításai</title>
 
       <para>Ezen beállítás
 	használatával egy háromgombos
 	egérrel lehetõségünk adódik a
 	konzol és a felhasználói programok
 	között kivágni és bemásolni
 	szövegeket.  Kétgombos egér használata
 	esetén nézzük meg a &man.moused.8; man
 	oldalán, miként tudjuk emulálni a
 	háromgombos mûködést.  A
 	következõ példa egy nem USB-s (tehát
 	PS/2-es vagy soros portra csatlakozó) egér
 	beállítását
 	illusztrálja:</para>
 
       <screen>                      User Confirmation Requested
          Does this system have a PS/2, serial, or bus mouse?
 
                             [ Yes ]    No </screen>
 
       <para>Fordítás:</para>
 
       <screen>                   Felhasználói megerõsítés szükséges
       Csatlakozik a rendszeréhez PS/2-es, soros vagy buszos egér?
 
                            [ Igen ]    Nem</screen>
 
       <para>A PS/2, soros vagy buszos egér
 	használatához válasszuk a &gui.yes; gombot,
 	illetve az USB-s egérhez pedig a &gui.no; gombot, majd
 	nyomjuk meg az <keycap>Enter</keycap> billentyût.</para>
 
       <figure id="mouse-protocol">
 	<title>Az egér által használt protokoll
 	  típusának
 	  beállítása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A nyílbillentyûk használatával
 	keressük ki a <guimenuitem>Type</guimenuitem>
 	(Típus) menüpontot és nyomjuk le az
 	<keycap>Enter</keycap> billentyût.</para>
 
       <figure id="set-mouse-protocol">
 	<title>Az egér protokolljának
 	  beállítása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A példában használt egér
 	típusa PS/2, ezért itt a
 	alapértelmezés szerint felkínált
 	<guimenuitem>Auto</guimenuitem> megfelelõ.  A protokoll
 	megváltoztatásához a nyilakkal
 	válasszunk ki egy másikat.  Ezután
 	gondoskodjunk róla, hogy az &gui.ok; gombot
 	választottuk ki és a kilépéshez
 	nyomjuk meg az <keycap>Enter</keycap> billentyût.</para>
 
       <figure id="config-mouse-port">
 	<title>Az egér portjának
 	  beállítása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A nyílbillentyûkkel válasszuk ki a
 	<guimenuitem>Port</guimenuitem> menüpontot és
 	nyomjuk meg az <keycap>Enter</keycap> billentyût.</para>
 
       <figure id="set-mouse-port">
 	<title>Az egér portjának
 	  kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse4"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Mivel a példában szereplõ rendszerhez egy
 	PS/2 egér csatlakozik, ezért az
 	alapértelmezett <guimenuitem>PS/2</guimenuitem>
 	menüpont megfelelõnek tûnik.  A port
 	megváltoztatásához használjuk a
 	nyilakat, majd nyomjuk le az <keycap>Enter</keycap>
 	billentyût.</para>
 
       <figure id="test-daemon">
 	<title>Az egérdémon
 	  engedélyezése</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse5"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Befejezésül a egérhez tartozó
 	démon aktiválásához és
 	kipróbálásához válasszuk ki a
 	nyilakkal az <guimenuitem>Enable</guimenuitem>
 	(Engedélyezés) menüpontot.</para>
 
       <figure id="test-mouse-daemon">
 	<title>Az egérdémon
 	  kipróbálása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse6"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Próbáljuk mozgatni a képernyõn
 	megjelenõ egérkurzort, és
 	ellenõrizzük, hogy a kurzor a mozdulatainknak
 	megfelelõen reagál-e.  Ha mindent rendben
 	találunk, akkor válasszuk a &gui.yes; gombot
 	és nyomjuk le az <keycap>Enter</keycap> billentyût.
 	Ellenkezõ esetben az egeret nem jól
 	állítottuk be &mdash; válasszuk a &gui.no;
 	gombot és kísérletezzünk tovább
 	más beállításokkal.</para>
 
       <para>Az utólagos beállítások
 	folytatásához válasszuk elõször
 	az <guimenuitem>Exit</guimenuitem> (Kilépés)
 	menüpontot, majd nyomjuk meg az <keycap>Enter</keycap>
 	billentyût.</para>
 
     </sect2>
 
     <sect2 id="packages">
       <title>Csomagok telepítése</title>
 
       <para>A csomagok elõre lefordított binárisokat
 	tartalmaznak, és használatukkal igen
 	kényelmesen tudunk szoftvereket telepíteni.</para>
 
       <para>Szemléltetés céljából
 	most bemutatjuk az egyik ilyen csomag
 	telepítését.  Természetesen
 	igény szerint más csomagokat is
 	hozzávehetünk.  A telepítés
 	után a <command>sysinstall</command> parancs
 	használható további csomagok
 	telepítésére.</para>
 
       <screen>                     User Confirmation Requested
  The FreeBSD package collection is a collection of hundreds of
  ready-to-run applications, from text editors to games to WEB servers
  and more. Would you like to browse the collection now?
 
                             [ Yes ]   No</screen>
 
       <para>Az üzenet fordítása:</para>
 
       <screen>                 Felhasználói megerõsítés szükséges
  A FreeBSD csomaggyûjteménye többezernyi azonnal használható
  alkalmazást tartalmaz, a szövegszerkesztõktõl a játékokon keresztül a
  WEBszervereken át szinte mindent. Át kívánja lapozni most ezt a
  gyûjteményt?
 
                            [ Igen ]   Nem</screen>
 
       <para>A &gui.yes; kiválasztása és az
 	<keycap>Enter</keycap> lenyomása után a
 	csomagválasztó képernyõ
 	következik:</para>
 
       <figure id="package-category">
 	<title>A csomagok kategóriájának
 	  kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-cat"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Ekkor csak az adott telepítõeszközön
 	elérhetõ csomagok fognak megjelenni.</para>
 
       <para>Az összes csomagot az <guimenuitem>All</guimenuitem>
 	(Mind) menüpont kiválasztásával
 	láthatjuk, vagy leszûkíthetjük ezt egy
 	adott kategóriára is.  Álljunk a
 	kiválasztott kategóriához tartozó
 	menüpontra és nyomjuk meg az <keycap>Enter</keycap>
 	billentyût.</para>
 
       <para>Ezután egy menü fogja felsorolni az adott
 	kategórián belül telepíthetõ
 	csomagokat:</para>
 
       <figure id="package-select">
 	<title>Csomag kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-sel"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A példában a <application>bash</application>
 	parancsértelmezõt választottuk ki.
 	Válogassunk kedvünkre a csomagok között,
 	és álljunk a telepíteni
 	kívántakra, majd a
 	<keycap>Szóköz</keycap> billentyû
 	lenyomásával jelöljük be ezeket.  Minden
 	egyes csomag rövid leírása a
 	képernyõ bal alsó sarkában
 	olvasható.</para>
 
       <para>A <keycap>Tab</keycap> billentyû
 	segítségével mozoghatunk az utoljára
 	kiválasztott csomag, az &gui.ok; és &gui.cancel;
 	gombok között.</para>
 
       <para>Miután bejelöltük az összes
 	telepítésre szánt csomagot, a
 	csomagválasztó menübe úgy tudunk
 	visszatérni, ha a <keycap>Tab</keycap> billentyûvel
 	átváltunk az &gui.ok; gombra és nyomjuk meg
 	az <keycap>Enter</keycap> billentyût.</para>
 
       <para>Ezeken felül a bal és jobb nyilak
 	használhatóak az &gui.ok; és &gui.cancel;
 	gombok közti váltásra.  Ugyanezzel a
 	módszerrel választható ki az &gui.ok; gomb
 	is, ami után az <keycap>Enter</keycap> billentyû
 	megnyomásával visszajutunk a
 	csomagválasztó menübe.</para>
 
       <figure id="package-install">
 	<title>Csomagok telepítése</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-install"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A nyilakkal és a <keycap>Tab</keycap>
 	billentyûvel válasszuk ki az
 	<guibutton>[&nbsp;Install&nbsp;]</guibutton>
 	(Telepítés) gombot és nyomjuk meg az
 	<keycap>Enter</keycap> billentyût.  Ekkor meg kell
 	erõsítenünk a csomagok
 	telepítését:</para>
 
       <figure id="package-install-confirm">
 	<title>Csomagok telepítésének
 	  megerõsítése</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-confirm"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Az &gui.ok; kiválasztása majd az
 	<keycap>Enter</keycap> billentyû lenyomása
 	indítja el a csomagok telepítését.
 	A telepítés befejezéséig
 	különbözõ üzenetek fognak megjelenni.
 	Figyeljünk az ilyenkor felbukkanó
 	hibaüzenetekre!</para>
 
       <para>A beállítások
 	véglegesítése a csomagok
 	telepítése után folytatódik.
 	Amennyiben egyetlen csomagot sem választottunk és
 	szeretnénk továbblépni, akkor is az
 	<guibutton>Install</guibutton> (Telepítés) gombot
 	válasszuk.</para>
 
     </sect2>
 
     <sect2 id="addusers">
       <title>Felhasználók és csoportok
 	felvétele</title>
 
       <para>A telepítés során legalább egy
 	felhasználót érdemes hozzáadnunk a
 	rendszerhez, mivel a rendszer használatához
 	így nem kell <username>root</username>
 	felhasználóként bejelentkezni.
 	Általánosságban véve ahhoz
 	egyébként is kicsi a
 	gyökérpartíció, hogy
 	<username>root</username> felhasználóként
 	(rendszeradminisztrátorként) futtassunk rajta
 	programokat, és gyorsan be is telik.  A nagyobb
 	veszélyt azonban itt olvashatjuk:</para>
 
       <screen>                     User Confirmation Requested
  Would you like to add any initial user accounts to the system? Adding
  at least one account for yourself at this stage is suggested since
  working as the "root" user is dangerous (it is easy to do things which
  adversely affect the entire system).
 
                             [ Yes ]   No</screen>
 
       <screen>                  Felhasználói megerõsítés szükséges
  Szeretnénk mosta rendszerbe felvenni felhasználói fiókokat? Ebben a
  lépésben legalább egy felhasználó felvétele javasolt, hiszen "root"
  felhasználóként veszélyes dolgozni (mivel így könnyen tehetünk olyan
  dolgokat, amelyek káros hatással lehetnek rendszerünkre).
 
                            [ Igen ]   Nem</screen>
 
       <para>Ezért válasszuk a &gui.yes; gombot és
 	az <keycap>Enter</keycap> billentyû
 	lenyomásával lépjünk tovább a
 	felhasználók felvételéhez.</para>
 
       <figure id="add-user2">
 	<title>Felhasználók
 	  kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A nyílbillentyûkkel válasszuk ki a
 	<guimenuitem>User</guimenuitem> (Felhasználó)
 	menüpontot és nyomjuk meg az <keycap>Enter</keycap>
 	billentyût.</para>
 
       <figure id="add-user3">
 	<title>A felhasználó adatainak
 	  megadása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Amikor a <keycap>Tab</keycap> billentyûvel
 	lépkedünk a kitöltendõ mezõk
 	között, a képernyõ alsó
 	részén az alábbi leírások
 	magyarázzák az egyes mezõk
 	tartalmát:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>Login ID (Bejelentkezési
 	    azonosító)</term>
 
 	  <listitem>
 	    <para>Az új felhasználó
 	      bejelentkezési neve (kötelezõ).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>UID (Felhasználói
 	    azonosító)</term>
 
 	  <listitem>
 	    <para>A felhasználó számszerû
 	      azonosítója (automatikusan
 	      létrejön, ha üresen hagyjuk).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Group (Csoport)</term>
 
 	  <listitem>
 	    <para>A felhasználó bejelentkezési
 	      csoportjának neve (automatikusan
 	      létrejön, ha üresen hagyjuk).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Password (Jelszó)</term>
 
 	  <listitem>
 	    <para>A felhasználó jelszava (óvatosan
 	      bánjunk ezzel a mezõvel!)</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Full name (Teljes név)</term>
 
 	  <listitem>
 	    <para>A felhasználó teljes neve
 	      (megjegyzés).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Member groups (További csoportok)</term>
 
 	  <listitem>
 	    <para>A felhasználó ezen csoportoknak is tagja
 	      (tehát rendelkezik az
 	      engedélyeikkel).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Home directory (Felhasználói
 	    könyvtár)</term>
 
 	  <listitem>
 	    <para>A felhasználó saját
 	      könyvtára (ha üresen hagyjuk, az
 	      alapértelmezés szerint töltõdik
 	      ki).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Login shell (Parancsértelmezõl)</term>
 	  <listitem>
 	    <para>A felhasználó által
 	      használt parancsértelmezõ (ha
 	      üresen hagyjuk, az alapértelmezés
 	      szerint töltõdik, mint például
 	      <filename>/bin/sh</filename>).</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>Az ábrán a bejelentkezés után
 	használt parancsértelmezõt a
 	<filename>/bin/sh</filename>
 	parancsértelmezõrõl a
 	<filename>/usr/local/bin/bash</filename>
 	parancsértelmezõre változtattuk, így
 	most a korábban telepített
 	<application>bash</application> parancsértelmezõt
 	fogjuk használni.  Itt ne is próbáljunk nem
 	létezõ parancsértelmezõt
 	kiválasztani, hiszen ekkor nem tudunk majd bejelentkezni.
 	A BSD világban egyébként a C shell a
 	leggyakrabban használt, amelyet a
 	<filename>/bin/tcsh</filename> megadásával
 	választhatjuk ki.</para>
 
       <para>Az ábrán szereplõ
 	felhasználót ezenkívül még a
 	<groupname>wheel</groupname> csoportba is felvettük, aminek
 	köszönhetõen képes lesz a
 	rendszerünkben a <username>root</username>
 	felhasználói jogaival rendelkezõ
 	rendszeradminisztrátorrá válni.</para>
 
       <para>Amikor mindent megfelelõnek találunk, nyomjunk
 	az &gui.ok; gombra és ekkor ismét a
 	felhasználók és csoportok
 	karbantartását tartalmazó menü jelenik
 	meg:</para>
 
       <figure id="add-user4">
 	<title>Kilépés a felhasználók
 	  és csoportok menüjébõl</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Csoportokat is létre tudunk hozni, amennyiben erre
 	szükségünk lenne.  Ez a rész a
 	telepítés befejezése után
 	továbbra is elérhetõ a
 	<command>sysinstall</command> parancs
 	segítségével.</para>
 
       <para>Amikor befejeztük a felhasználók
 	hozzáadását, a nyilakkal válasszuk
 	ki az <guimenuitem>Exit</guimenuitem> (Kilépés)
 	menüpontot és a telepítés
 	folytatásához nyomjuk meg az
 	<keycap>Enter</keycap> billentyût.</para>
 
     </sect2>
 
     <sect2 id="rootpass">
       <title>A <username>root</username> felhasználó
 	jelszavának megadása</title>
 
       <screen>                        Message
  Now you must set the system manager's password.
  This is the password you'll use to log in as "root".
 
                          [ OK ]
 
                [ Press enter or space ]</screen>
 
       <para>Fordítása:</para>
 
       <screen>                         Üzenet
  Most meg kell adnia a rendszergazda jelszavát. Ezt a jelszót
  kell a "root" felhasználó bejelentkezésekor használni.
 
                          [ OK ]
 
      [ Nyomja le az Enter vagy a Szóköz billentyût ]</screen>
 
       <para>A <username>root</username> felhasználó
 	jelszavának beállításához
 	nyomjuk meg az <keycap>Enter</keycap> billentyût.</para>
 
       <para>A jelszót kétszer kell megadnunk.  Felesleges
 	megemlíteni, hogy gondoskodjunk arról az
 	esetrõl is, ha véletlenül elfelejtenénk
 	ezt a jelszót.  Megemlítjük, hogy az itt
 	begépelt jelszó nem lesz látható
 	és a betûk helyett sem jelennek meg
 	csillagok.</para>
 
       <screen>New password:
 Retype new password :</screen>
 
       <para>A jelszó sikeres megadása után a
 	telepítés folytatódik.</para>
 
     </sect2>
 
     <sect2 id="exit-inst">
       <title>Kilépés a
 	telepítõbõl</title>
 
       <para>Ha be szeretnénk még állítani
 	<link linkend="network-services">egyéb
 	hálózati szolgáltatást</link> vagy
 	valamilyen más konfigurációs
 	lépést kívánunk még
 	elvégezni, ezen a ponton megtehetjük vagy a
 	telepítés után a
 	<command>sysinstall</command> parancs
 	kiadásával.</para>
 
       <screen>                     User Confirmation Requested
  Visit the general configuration menu for a chance to set any last
  options?
 
                               Yes   [ No ]</screen>
 
       <para>Fordítás:</para>
 
       <screen>                  Felhasználói megerõsítés szükséges
  Végignézi még utoljára a beállításokat arra az esetre, ha véletlenül
  kihagytunk volna valamit?
 
                              Igen   [ Nem ]</screen>
 
       <para>Ha a nyilakkal a &gui.no; gombot választjuk, majd
 	megnyomjuk rajta az <keycap>Enter</keycap> billentyût,
 	akkor visszatérünk a telepítõ
 	fõmenüjébe.</para>
 
       <figure id="final-main">
 	<title>Kilépés a
 	  telepítõbõl</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mainexit"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Válasszuk ki a nyílbillentyûkkel a
 	<guibutton>[X&nbsp;Exit&nbsp;Install]</guibutton>
 	(Kilépés a telepítõbõl) gombot
 	és nyomjuk meg az <keycap>Enter</keycap> billentyût.
 	Ezután meg kell erõsítenünk
 	kilépési szándékunkat:</para>
 
       <screen>                     User Confirmation Requested
  Are you sure you wish to exit? The system will reboot.
 
                             [ Yes ]   No</screen>
 
       <para>Fordítás:</para>
 
       <screen>                  Felhasználói megerõsítés szükséges
          Valóban ki akar lépni? A rendszer ezt követõen újra fog
          indulni!
 
                            [ Igen ]    Nem</screen>
 
       <para>Válasszuk a &gui.yes; gombot.  Ha
 	CD-meghajtóról indítottuk a
 	telepítést, akkor a következõ
 	üzenet fog figyelmeztetni minket a lemez
 	kivételére:</para>
 
       <screen>                     Message
  Be sure to remove the media from the drive.
 
                     [ OK ]
            [ Press enter or space ]</screen>
 
       <para>Fordítás:</para>
 
       <screen>                     Üzenet
  Ne felejtsük el kivenni a CD-lemezt a meghajtóból.
 
                     [ OK ]
         [ Nyomjunk Entert vagy szóközt ]</screen>
 
       <para>A CD-meghajtó egészen az
 	újraindítás megkezdéséig
 	zárolt lesz, ezért csak ekkor tudjuk (gyorsan)
 	kivenni a meghajtóból a lemezt.  Nyomjuk meg az
 	&gui.ok; gombot az újraindításhoz.</para>
 
       <para>A rendszer újraindul, legyünk résen
 	és figyeljük a megjelenõ hibaüzeneteket,
 	errõl bõvebben lásd a <xref
 	linkend="freebsdboot"/>ban.</para>
     </sect2>
 
     <sect2 id="network-services">
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Tom</firstname>
 	    <surname>Rhodes</surname>
 	    <contrib>Írta: </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
 
       <title>További hálózati
 	szolgálatások
 	beállítása</title>
 
       <para>A hálózati szolgáltatások
 	terén csekély tapasztalattal rendelkezõ
 	kezdõ felhasználók számára
 	ijesztõ lehet ezek beállítása.  A
 	hálózatok és többek közt az
 	internet kezelése napjaink modern operációs
 	rendszereink, így a &os;-nek is az egyik fontos
 	területe.  Ezért nagyon hasznos ismernünk
 	valamennyire a &os; által felkínált
 	hálózati lehetõségeket.  A
 	telepítés közben ezért a
 	felhasználónak tisztában kell lennie a
 	rendelkezésére álló
 	szolgáltatásokkal.</para>
 
       <para>A hálózati szolgáltatások olyan
 	programok, amelyek a hálózat minden
 	részérõl fogadnak adatokat.  Mindent el kell
 	követnünk annak érdekében, hogy ezek a
 	programok ne tehessenek semmilyen <quote>kárt</quote>.
 	Sajnos a programozók sem tökéletesek,
 	és az idõk során már elõfordult
 	párszor, hogy a hálózati
 	szolgáltatásokban maradtak hibák, amelyek
 	kihasználásával a támadók
 	rossz dolgokat tudtak csinálni.  Ezért fontos,
 	hogy csak is azokat a szolgáltatásokat
 	engedélyezzük, amelyekre ténylegesen
 	szükségünk van.  Ha nem tudjuk eldönteni,
 	akkor az a legjobb, ha egészen addig egyiket sem
 	engedélyezzük, amíg valóban
 	szükségünk nem lesz rájuk.  A
 	<application>sysinstall</application> újbóli
 	elindításával vagy az
 	<filename>/etc/rc.conf</filename> megfelelõ
 	beállításával mindig tudunk
 	új szolgáltatásokat
 	aktiválni.</para>
 
       <para>A <guimenuitem>Networking</guimenuitem>
 	(Hálózatok) menüpont
 	kiválasztása után valami ilyesmit
 	láthatunk:</para>
 
       <figure id="network-configuration">
 	<title>A hálózati beállítások
 	  menüjének felsõ szintje</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/net-config-menu1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Ezek közül a <guimenuitem>Interfaces</guimenuitem>
 	(Csatolók), vagyis az elsõ menüpontról
 	korábban már szó esett a <xref
 	linkend="inst-network-dev"/>ban, ezért ez most nyugodtan
 	kihagyható.</para>
 
       <para>Az <guimenuitem>AMD</guimenuitem> menüpont
 	kiválasztásával engedélyezzük a
 	<acronym>BSD</acronym> automatikus
 	csatlakoztatásokért felelõs
 	segédeszközét (AMD, az AutoMounter Daemon).
 	Ezt általában az <acronym>NFS</acronym>
 	protokollal (lásd lentebb) együtt szokás
 	használni a távoli
 	állományrendszerek automatikus
 	csatlakoztatásához.  Itt nincs szükség
 	semmilyen különleges
 	beállításra.</para>
 
       <para>A következõ sorban az <guimenuitem>AMD
 	Flags</guimenuitem> (Az AMD beállításai)
 	menüpont szerepel.  Kiválasztása után
 	az <acronym>AMD</acronym> beállításait
 	bekérõ ablak fog felbukkani.  Ez már
 	számos alapértelmezett
 	beállítást tartalmaz:</para>
 
       <screen>-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map</screen>
 
       <para>A <option>-a</option> kapcsolóval adjuk meg a
 	csatlakozási pontok alapértelmezett helyét,
 	amely ebben az esetben az <filename>/.amd_mnt</filename>.  A
 	<option>-l</option> kapcsolóval adjuk meg az
 	alapértelmezett <filename>log</filename> (napló)
 	állományt, habár a
 	<literal>syslogd</literal> használata során az
 	összes naplózási tevékenység a
 	rendszer naplózó démonján fut majd
 	keresztül.  A <filename class="directory">/host</filename>
 	könyvtárba fognak csatlakozni a távoli
 	gépek exportált állományrendszerei,
 	míg a <filename class="directory">/net</filename>
 	könyvtárba a különbözõ
 	<acronym>IP</acronym>-címekrõl exportált
 	állományrendszerek kerülnek
 	csatlakoztatásra.  Az <filename>/etc/amd.map</filename>
 	állomány tartalmazza az <acronym>AMD</acronym>
 	exportjainak alapértelmezett
 	beállításait.</para>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>anonim</secondary>
       </indexterm>
 
       <para>Az <guimenuitem>Anon FTP</guimenuitem> menüponton
 	keresztül engedélyezhetjük az anonim
 	<acronym>FTP</acronym> kapcsolatokat.  A menüpont
 	kiválasztásával
 	számítógépünket egy anonim
 	<acronym>FTP</acronym> szerverré tehetjük, azonban
 	legyünk tekintettel a beállításhoz
 	tartozó biztonsági veszélyekre!  A
 	kiválasztásakor egy ablak tájékoztat
 	minket a beállítás részleteirõl
 	és felmerülõ biztonsági
 	kockázatokról.</para>
 
       <para>A <guimenuitem>Gateway</guimenuitem>
 	(Átjáró) menüpont
 	használatával a korábbiakban
 	tárgyaltak szerint állíthatjuk be
 	számítógépünket
 	hálózati átjárónak.
 	Ugyanekkor a <guimenuitem>Gateway</guimenuitem> menüben
 	nyílik lehetõségük kikapcsolni ezt a
 	beállítást, amennyiben a
 	telepítési folyamat korábbi
 	lépései során véletlenül
 	engedélyeztük volna.</para>
 
       <para>Az <guimenuitem>Inetd</guimenuitem> menüpont
 	segítségével beállíthatjuk,
 	vagy akár teljesen ki is kapcsolhatjuk a korábban
 	tárgyalt &man.inetd.8; démont.</para>
 
       <para>A <guimenuitem>Mail</guimenuitem> (Levelezés)
 	menüpontban beállíthatjuk a rendszer
 	alapértelmezett <acronym>MTA</acronym> avagy
 	levéltovábbító
 	ügynökét (Mail Transfer Agent).  Ennek
 	hatására a következõ menü jelenik
 	meg:</para>
 
       <figure id="mta-selection">
 	<title>Az alapértelmezett MTA
 	  kiválasztása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mta-main"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Itt válaszhatunk, hogy a
 	különbözõ levélküldõ
 	rendszerek közül melyiket telepítsük
 	alapértelmezettként.  Egy ilyen alkalmazás
 	lényegében nem több, mint egy
 	levélküldésre használt szerver, amely
 	továbbítja a rendszerben vagy az interneten
 	található felhasználók
 	számára a leveleket.</para>
 
       <para>A <guimenuitem>Sendmail</guimenuitem>
 	választásával a &os; alapból
 	felkínált megoldását, a
 	népszerû <application>sendmail</application>
 	szervert telepíthetjük.  A <guimenuitem>Sendmail
 	local</guimenuitem> (Helyi Sendmail) menüpont
 	kiválasztásával szintén a
 	<application>sendmail</application> lesz a
 	telepítendõ levélküldõ szerver,
 	azonban nem lesz képes az internetrõl
 	érkezõ leveleket fogadni.  Az itt felsorolt
 	többi beállítás, tehát a
 	<guimenuitem>Postfix</guimenuitem> és
 	<guimenuitem>Exim</guimenuitem>, a
 	<guimenuitem>Sendmail</guimenuitem>
 	beállításához hasonlóan
 	zajlik.  Mind a kettõ elektronikus levelek
 	kézbesítésére
 	használható, azonban bizonyos
 	felhasználók a <application>sendmail</application>
 	helyett inkább ezek valamelyikét
 	használják.</para>
 
       <para>Valamelyik vagy éppen semelyik
 	levéltovábbító szerver
 	kiválasztása után az <guimenuitem>NFS
 	client</guimenuitem> (NFS kliens)
 	beállítására vonatkozó
 	menü jelentkezik.</para>
 
       <para>Az <guimenuitem>NFS client</guimenuitem>
 	beállításával a rendszerünk
 	<acronym>NFS</acronym> szerverekkel lesz képes
 	kapcsolatba lépni.  Egy ilyen <acronym>NFS</acronym>
 	szerver az <acronym>NFS</acronym> protokoll
 	segítségével a hálózaton
 	keresztül elérhetõvé tesz
 	állományrendszereket.  Ha gépünk
 	független, akkor nem fontos kiválasztanunk ezt a
 	menüpontot.  A rendszernek késõbb
 	további beállításokra is
 	szüksége lehet, amelyekrõl az <xref
 	linkend="network-nfs"/>ban olvashatunk
 	részletesebben.</para>
 
       <para>Az <guimenuitem>NFS server</guimenuitem> (NFS szerver)
 	menüpont kiválasztásával
 	hozzájárulunk, hogy rendszerünk
 	<acronym>NFS</acronym> szerverként üzemeljen.  Ehhez
 	meg kell adnunk az <acronym>RPC</acronym>, vagyis a
 	távoli eljáráshívások
 	kiszolgálásának
 	elindításához szükséges
 	adatokat is.  Az <acronym>RPC</acronym>
 	használatával a különbözõ
 	kiszolgálók és programok között
 	tudjuk vezérelni a kapcsolatot.</para>
 
       <para>A sorban az <guimenuitem>Ntpdate</guimenuitem>
 	beállítása következik, ahol az
 	idõszinkronizációhoz kapcsolódó
 	opciókat találjuk.  Kiválasztásakor
 	az ábrán szereplõhöz hasonló
 	menü fog megjelenni:</para>
 
       <figure id="Ntpdate-config">
 	<title>Az Ntpdate beállítása</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ntp-config"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Ebbõl a menübõl válasszuk ki a
 	hozzánk legközelebb levõ szevert.  Egy
 	közeli szerver megadásával az
 	idõszinkronizáció sokkalta pontosabbá
 	válik, mivel a tõlünk távolabbi
 	szerverek kapcsolatának késleltetése
 	nagyobb lehet.</para>
 
       <para>A következõ beállítás az
 	<acronym>PCNFSD</acronym>.  Ennek kiválasztása
 	során a Portgyûjteménybõl
 	telepítésre kerül a <filename
 	role="package">net/pcnfsd</filename> csomag.  Ez
 	lényegében egy hasznos segédprogram,
 	amellyel olyan operációs rendszerek
 	számára tudunk hitelesítést
 	szolgáltatni az <acronym>NFS</acronym> használata
 	során, amelyek maguktól erre nem képesek,
 	mint például a &microsoft; &ms-dos;
 	rendszere.</para>
 
       <para>A többi beállítás
 	megtekintéséhez egy kicsit lejjebb kell haladnunk
 	a listában:</para>
 
       <figure id="Network-configuration-cont">
 	<title>A hálózati beállítások
 	  menüjének alsó szintje</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/net-config-menu2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Az &man.rpcbind.8; és &man.rpc.statd.8;, valamint az
 	&man.rpc.lockd.8; segédprogramok mind a távoli
 	eljáráshívásokhoz (Remote Procedure
 	Call, <acronym>RPC</acronym>) használhatóak.  Az
 	<command>rpcbind</command> segédprogram az
 	<acronym>NFS</acronym> szerverei és kliensei
 	között felügyeli a kapcsolatot, ezért a
 	használata az <acronym>NFS</acronym> szerverek és
 	kliensek mûködéséhez elengedhetetlen.
 	Az állapot figyeléséhez az
 	<application>rpc.statd</application> démon felveszi a
 	kapcsolatot a többi gépen futó
 	<application>rpc.statd</application> démonokkal.  A
 	jelentett állapotok általában a
 	<filename>/var/db/statd.status</filename>
 	állományban találhatóak.  Itt a
 	következõként felsorolt elem az
 	<guimenuitem>rpc.lockd</guimenuitem>, amelynek
 	kiválasztásával
 	állományzárolási
 	szolgáltatásokat érhetünk el.  Ezt
 	többnyire az <application>rpc.statd</application>
 	démonnal együtt alkalmazzák a
 	zárolásokat kérõ gépek
 	és a kérések gyakoriságának
 	nyilvántartására.  Míg ezekkel a
 	beállításokkal gyönyörûen
 	nyomon lehet követni a mûködést, az
 	<acronym>NFS</acronym> szerverek és kliensek
 	megfelelõ mûködéséhez nem
 	kötelezõ a használatuk.</para>
 
       <para>Ahogy haladunk tovább a listában, a
 	következõ elem a <guimenuitem>Routed</guimenuitem>,
 	vagyis az útválasztásért
 	felelõs démon lesz.  A &man.routed.8;
 	segédprogram a hálózati
 	útválasztó táblázatokat
 	tartja karban, felderíti az elérhetõ
 	útválasztókat és
 	kérésre bármelyik hozzá fizikailag
 	csatlakozó gép számára átadja
 	az általa nyilvántartott
 	útválasztási adatokat.  Ezt
 	leginkább a helyi hálózat
 	átjárójaként mûködõ
 	számítógépek
 	használják.  Kiválasztásakor egy
 	ablak fog rákérdezni a segédprogram
 	helyére.  Az itt alapból felkínált
 	érték általában megfelelõ,
 	ezért nyugtázhatjuk az <keycap>Enter</keycap>
 	billentyû lenyomásával.  Ezt
 	követõen egy másik menü jelenik meg, ahol
 	a <application>routed</application>
 	beállításait adhatjuk meg.  Itt
 	alapértelmezés szerint a <option>-q</option>
 	kapcsoló szerepel.</para>
 
       <para>A következõ sor az
 	<guimenuitem>Rwhod</guimenuitem>
 	beállításé, aminek
 	kiválasztásával el tudjuk indíttatni
 	az &man.rwhod.8; démont a rendszer
 	elindítása során.  Az
 	<command>rwhod</command> segédprogram a
 	rendszerüzeneteket a hálózaton
 	idõközönként szétküldi vagy
 	<quote>figyelõ</quote> (consumer) módban
 	összegyûjti ezeket.  Ennek pontosabb részleteit
 	az &man.ruptime.1; és &man.rwho.1; man oldalakon
 	találhatjuk meg.</para>
 
       <para>Az &man.sshd.8; démoné az utolsó
 	elõtti beállítás.  Ez az
 	<application>OpenSSH</application> biztonságos shell
 	szervere, melyet a szabványos
 	<application>telnet</application> és
 	<acronym>FTP</acronym> szerverek helyett ajánlanak.  Az
 	<application>sshd</application> szerver tehát két
 	gép közti biztonságos, titkosított
 	kapcsolatok létrehozására
 	használható.</para>
 
       <para>A lista végén a <guimenuitem>TCP
 	Extensions</guimenuitem> (TCP kiterjesztések)
 	menüpontot találhatjuk.
 	Segítségével a <acronym>TCP</acronym>
 	<acronym>RFC</acronym>&nbsp;1323 és
 	<acronym>RFC</acronym>&nbsp;1644 dokumentumokban leírt
 	kiterjesztéseinek használatát
 	engedélyezhetjük.  Ezzel egyes gépek
 	esetén felgyorsulhat a kapcsolat, azonban más
 	esetekben pedig eldobódhat.  Ez szerverek
 	használatánál nem ajánlott, viszont
 	független gépeknél kifizetõdõ
 	lehet.</para>
 
       <para>Most, miután beállítottuk a
 	hálózati szolgáltatásokat,
 	lépjünk vissza a lista elején
 	található <guimenuitem>X&nbsp;Exit</guimenuitem>
 	(Kilépés) menüpontra és folytassuk a
 	beállítást a következõ
 	opcióval, vagy egyszerûen az
 	<guimenuitem>X&nbsp;Exit</guimenuitem> kétszeri
 	kiválasztásával, majd a
 	<guibutton>[X&nbsp;Exit&nbsp;Install]</guibutton>
 	(Kilépés a telepítõbõl) gomb
 	lenyomásával lépjünk ki a
 	<application>sysinstall</application> programból.</para>
 
     </sect2>
 
     <sect2 id="freebsdboot">
       <title>A &os; indulása</title>
 
       <sect3 id="freebsdboot-i386">
 	<title>A &os;/&arch.i386; indulása</title>
 
 	<para>Ha minden remekült ment, a képernyõn
 	  lentrõl felfelé gördülõ
 	  üzeneteket fogunk látni, majd a rendszer
 	  várni fog tõlünk egy bejelentkezési
 	  nevet.  A kiírt üzeneteket között a
 	  <keycap>Scroll Lock</keycap> lenyomása után a
 	  <keycap>PgUp</keycap> és <keycap>PgDn</keycap>
 	  billentyûk használatával tudunk lapozni.  A
 	  <keycap>Scroll Lock</keycap> ismételt
 	  lenyomásával visszatérünk a
 	  bejelentkezéshez.</para>
 
 	<para>Nem minden esetben lesz látható az
 	  összes üzenet (a puffer végessége
 	  miatt), de miután bejelentkeztünk, ezeket a
 	  <command>dmesg</command> parancs kiadásával is
 	  megnézhetjük.</para>
 
 	<para>Bejelentkezni a telepítéskor megadott
 	  felhasználói név/jelszó
 	  párossal tudunk (a példában ez most
 	  <username>rpratt</username>).  Lehetõleg ne
 	  jelentkezzünk be <username>root</username>
 	  felhasználóként!</para>
 
 	<para>A rendszer indításakor jellemzõen
 	  elõforduló üzenetek (a verzióra
 	  vonatkozó adatokat kihagytuk):</para>
 
 	<screen>Copyright (c) 1992-2002 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
 
 Timecounter "i8254"  frequency 1193182 Hz
 CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU)
   Origin = "AuthenticAMD"  Id = 0x580  Stepping = 0
   Features=0x8001bf&lt;FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX&gt;
   AMD Features=0x80000800&lt;SYSCALL,3DNow!&gt;
 real memory  = 268435456 (262144K bytes)
 config&gt; di sn0
 config&gt; di lnc0
 config&gt; di le0
 config&gt; di ie0
 config&gt; di fe0
 config&gt; di cs0
 config&gt; di bt0
 config&gt; di aic0
 config&gt; di aha0
 config&gt; di adv0
 config&gt; q
 avail memory = 256311296 (250304K bytes)
 Preloaded elf kernel "kernel" at 0xc0491000.
 Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c.
 md0: Malloc disk
 Using $PIR table, 4 entries at 0xc00fde60
 npx0: &lt;math processor&gt; on motherboard
 npx0: INT 16 interface
 pcib0: &lt;Host to PCI bridge&gt; on motherboard
 pci0: &lt;PCI bus&gt; on pcib0
 pcib1: &lt;VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge&gt; at device 1.0 on pci0
 pci1: &lt;PCI bus&gt; on pcib1
 pci1: &lt;Matrox MGA G200 AGP graphics accelerator&gt; at 0.0 irq 11
 isab0: &lt;VIA 82C586 PCI-ISA bridge&gt; at device 7.0 on pci0
 isa0: &lt;ISA bus&gt; on isab0
 atapci0: &lt;VIA 82C586 ATA33 controller&gt; port 0xe000-0xe00f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0: &lt;VIA 83C572 USB controller&gt; port 0xe400-0xe41f irq 10 at device 7.2 on pci0
 usb0: &lt;VIA 83C572 USB controller&gt; on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 chip1: &lt;VIA 82C586B ACPI interface&gt; at device 7.3 on pci0
 ed0: &lt;NE2000 PCI Ethernet (RealTek 8029)&gt; port 0xe800-0xe81f irq 9 at
 device 10.0 on pci0
 ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit)
 isa0: too many dependant configs (8)
 isa0: unexpected small tag 14
 fdc0: &lt;NEC 72065B or clone&gt; at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: &lt;1440-KB 3.5" drive&gt; on fdc0 drive 0
 atkbdc0: &lt;keyboard controller (i8042)&gt; at port 0x60-0x64 on isa0
 atkbd0: &lt;AT Keyboard&gt; flags 0x1 irq 1 on atkbdc0
 kbd0 at atkbd0
 psm0: &lt;PS/2 Mouse&gt; irq 12 on atkbdc0
 psm0: model Generic PS/2 mouse, device ID 0
 vga0: &lt;Generic ISA VGA&gt; at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: &lt;System console&gt; at flags 0x1 on isa0
 sc0: VGA &lt;16 virtual consoles, flags=0x300&gt;
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: &lt;Parallel port&gt; at port 0x378-0x37f irq 7 on isa0
 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/15 bytes threshold
 ppbus0: IEEE1284 device found /NIBBLE
 Probing for PnP devices on ppbus0:
 plip0: &lt;PLIP network interface&gt; on ppbus0
 lpt0: &lt;Printer&gt; on ppbus0
 lpt0: Interrupt-driven port
 ppi0: &lt;Parallel I/O&gt; on ppbus0
 ad0: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata0-master using UDMA33
 ad2: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata1-master using UDMA33
 acd0: CDROM &lt;DELTA OTC-H101/ST3 F/W by OIPD&gt; at ata0-slave using PIO4
 Mounting root from ufs:/dev/ad0s1a
 swapon: adding /dev/ad0s1b as swap device
 Automatic boot in progress...
 /dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1a: clean, 48752 free (552 frags, 6025 blocks, 0.9% fragmentation)
 /dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1f: clean, 128997 free (21 frags, 16122 blocks, 0.0% fragmentation)
 /dev/ad0s1g: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1g: clean, 3036299 free (43175 frags, 374073 blocks, 1.3% fragmentation)
 /dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS
 /dev/ad0s1e: clean, 128193 free (17 frags, 16022 blocks, 0.0% fragmentation)
 Doing initial network setup: hostname.
 ed0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
         inet6 fe80::5054::5ff::fede:731b%ed0 prefixlen 64 tentative scopeid 0x1
         ether 52:54:05:de:73:1b
 lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; mtu 16384
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
         inet6 ::1 prefixlen 128
         inet 127.0.0.1 netmask 0xff000000
 Additional routing options: IP gateway=YES TCP keepalive=YES
 routing daemons:.
 additional daemons: syslogd.
 Doing additional network setup:.
 Starting final network daemons: creating ssh RSA host key
 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:
 cd:76:89:16:69:0e:d0:6e:f8:66:d0:07:26:3c:7e:2d root@k6-2.example.com
  creating ssh DSA host key
 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:
 f9:a1:a9:47:c4:ad:f9:8d:52:b8:b8:ff:8c:ad:2d:e6 root@k6-2.example.com.
 setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib
 /usr/local/lib
 a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
 starting standard daemons: inetd cron sshd usbd sendmail.
 Initial rc.i386 initialization:.
 rc.i386 configuring syscons: blank_time screensaver moused.
 Additional ABI support: linux.
 Local package initialization:.
 Additional TCP options:.
 
 FreeBSD/i386 (k6-2.example.com) (ttyv0)
 
 login: rpratt
 Password:</screen>
 
 	<para>Az RSA és DSA kulcsok generálása a
 	  lassabb gépeken sokág is eltarthat, habár
 	  ez mindig csak a friss telepítések utáni
 	  elsõ indításkor történik meg.
 	  A rendszer késõbbi indulásai ettõl
 	  már gyorsabbak lesznek.</para>
 
 	<para>Ha X szervert is beállítottunk és
 	  választottunk hozzá egy alapértelmezett
 	  munkakörnyezetet, akkor ezt a parancssorból a
 	  <command>startx</command> kiadásával
 	  elindíthatjuk el.</para>
       </sect3>
     </sect2>
 
     <sect2 id="shutdown">
       <title>A &os; leállítása</title>
 
       <para>Fontos, hogy mindig szabályosan
 	állítsuk le az operációs rendszert,
 	ne kapcsoljuk ki csak úgy egyszerûen a
 	számítógépünket!  A
 	leállításhoz elõször a
 	<command>su</command> parancs kiadásával, majd itt
 	a <username>root</username> jelszavának
 	megadásával vegyük fel az ehhez
 	szükséges rendszeradminisztrátori
 	jogosultságokat.  Ez viszont csak abban az esetben fog
 	mûködni, ha a felhasználónk tagja a
 	<groupname>wheel</groupname> csoportnak.  Minden más
 	esetben egyszerûen jelentkezzünk be
 	<username>root</username> felhasználóként
 	és használjuk a <command>shutdown -h now</command>
 	parancsot.</para>
 
       <screen>The operating system has halted.
 Please press any key to reboot.</screen>
 
       <para>A fenti üzenet jelzi, hogy a
 	leállító parancs kiadása után
 	már kikapcsolhatjuk a
 	számítógépet, vagy ha ehelyett egy
 	billentyût nyomunk le, akkor a gép
 	újraindul.</para>
 
       <para>A <keycombo action="simul"> <keycap>Ctrl</keycap>
 	<keycap>Alt</keycap> <keycap>Del</keycap> </keycombo>
 	billentyûkombináció
 	használatával is újra tudjuk
 	indítani a rendszert, azonban ez normál
 	mûködés közben nem ajánlott.</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-trouble">
     <title>Hibakeresés</title>
 
     <indexterm>
       <primary>telepítés</primary>
       <secondary>hibakeresés</secondary>
     </indexterm>
 
     <para>A most következõ szakaszban azokra a
       telepítés során felmerülõ
       problémákra próbálunk meg
       megoldásokat adni, amelyeket eddig már sokan
       jeleztek nekünk.  Ezek mellett szerepel néhány
       kérdés és válasz is a &os; és
       az &ms-dos; vagy &windows; közös
       használatáról.</para>
 
     <sect2>
       <title>Mit tegyünk ha valami nem mûködik</title>
 
       <para>A PC architektúra különféle
 	korlátozásai miatt szinte lehetetlen 100%-ban
 	megbízhatóvá tenni az eszközök
 	felderítését, azonban ennek hibája
 	kapcsán néhány dolgot még tenni
 	tudunk.</para>
 
       <para>Ellenõrizzük a <ulink
 	  url="http://www.FreeBSD.org/releases/index.html">Hardware
 	  Notes</ulink> (Hardverjegyzék) címû
 	dokumentumban, hogy az adott hardvert a &os; valóban
 	ismeri.</para>
 
       <para>Amennyiben a hardvereszközünket a rendszer ismeri,
 	azonban még mindig jelentkeznek fagyások vagy
 	egyéb gondok, készítenünk kell egy
 	<link linkend="kernelconfig">saját rendszermag</link>ot.
 	Ezzel olyan eszközök támogatását
 	is beépíthetjük a rendszermagba, amelyek
 	eredetileg nem szerepelnek a <filename>GENERIC</filename>
 	rendszermagban.  A telepítéshez
 	készített rendszerindító lemezeken
 	található rendszermag a legtöbb eszközt
 	a gyári IRQ, IO-cím és DMA csatorna
 	beállításaik mentén
 	próbálja felkutatni.  Ha viszont a
 	hardverünket átállítottuk, ennek
 	megfelelõen módosítanunk kell a rendszermag
 	beállításait és újra kell
 	fordítanunk, hogy a &os; tudja, hol is keresse az
 	eszközt.</para>
 
       <para>Olyan is adódhat, hogy egy nem létezõ
 	eszköz keresése egy utána keresendõ
 	másik, jelenlevõ eszköz
 	felkutatását akadályozza meg.  Ilyenkor az
 	ütközõ meghajtókat le kell tiltani.</para>
 
       <note>
 	<para>Egyes problémák elkerülhetõek vagy
 	  csillapíthatóak a különbözõ
 	  hardverösszetevõk, különösen az
 	  alaplapi firmware frissítésével.  Az
 	  alaplap firmware-jére sokszor csak
 	  <acronym>BIOS</acronym>-ként hivatkoznak, és a
 	  legtöbb alaplap- vagy
 	  számítógépgyártó
 	  honlapján találhatjuk meg ezeket, valamint a
 	  rájuk vonatkozó
 	  utasításokat.</para>
 
 	<para>A legtöbb gyártó azonban erõsen
 	  tiltakozik az alaplapi
 	  <acronym>BIOS</acronym>-frissítések ellen,
 	  és csak indokolt esetekben, például
 	  kritikus javításoknál javasolják.
 	  A frissítés kimenetele
 	  <emphasis>lehet</emphasis> rossz is, aminek
 	  következménye a <acronym>BIOS</acronym>
 	  tartós károsodása.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Az &ms-dos; és &windows;
 	állományrendszereinek használata</title>
 
       <para>A &os; jelenleg nem támogatja a <application>Double
 	Space&trade;</application> alkalmazással
 	tömörített állományrendszereket,
 	ezért a &os; csak úgy tud az adataihoz
 	hozzáférni, ha elõtte
 	kitömörítjük ezeket.  Ezt a
 	<guimenuitem>Start</guimenuitem> menü
 	<guimenuitem>Programs</guimenuitem> (Programok) &gt;
 	<guimenuitem>System Tools</guimenuitem>
 	(Rendszereszközök) menüjében
 	található <application>Compression
 	Agent</application> (Lemeztömörítés)
 	elindításával tehetjük meg.</para>
 
       <para>A &os; támogatja az &ms-dos; alapú (gyakran
 	csak FAT típusúnak nevezett)
 	állományrendszereket.  A &man.mount.msdosfs.8;
 	parancs segítségével az ilyen rendszerek
 	könnyedén becsatlakoztathatók a már
 	létezõ könyvtárszerkezetbe, amivel
 	így el tudjuk érni a tartalmát.  A
 	&man.mount.msdosfs.8; programot általában nem
 	közvetlenül hívjuk meg, hanem az
 	<filename>/etc/fstab</filename> vagy a &man.mount.8;
 	segédprogram megfelelõ
 	paraméterezésével.</para>
 
       <para>Az <filename>/etc/fstab</filename> állományban
 	általában így néz ki egy ilyen
 	sor:</para>
 
       <programlisting>/dev/ad0sN  /dos	msdosfs rw 0 0</programlisting>
 
       <note>
 	<para>A mûvelet végrehajtásához a
 	  <filename>/dos</filename> könyvtárnak már
 	  léteznie kell.  Az <filename>/etc/fstab</filename>
 	  pontos formátumával kapcsolatban a &man.fstab.5;
 	  man oldalt olvassuk el.</para>
       </note>
 
       <para>Az &ms-dos; állományrendszerek esetében
 	a &man.mount.8; parancsot többnyire így adjuk
 	ki:</para>
 
       <screen>&prompt.root; <userinput>mount -t msdosfs /dev/ad0s1 /mnt</userinput></screen>
 
       <para>Ebben a példában a &ms-dos;
 	állományrendszer az elsõdleges merevlemez
 	elsõ partícióján helyezkedik el.  A mi
 	helyzetünk ettõl eltérõ lehet,
 	ezért ehhez vizsgáljuk meg a
 	<command>dmesg</command> és <command>mount</command>
 	parancsok kimeneteit.  Segítségükkel
 	elegendõ információt tudunk összeszedni
 	a gépünkön található
 	partíciók
 	kiosztásáról.</para>
 
       <note>
 	<para>Elõfordulhat, hogy a &os; a többi
 	  operációs rendszertõl eltérõ
 	  módon számozza a slice-okat (vagyis az &ms-dos;
 	  partíciókat).  Konkrétan: a kiterjesztett
 	  &ms-dos; partíciók általában
 	  nagyobb sorszámot kapnak, mint az elsõdleges
 	  &ms-dos; partíciók.  Az &man.fdisk.8;
 	  segédprogram segíthet
 	  megállapítani, hogy mely slice-ok tartoznak a
 	  &os;-hez és melyek más operációs
 	  rendszerekhez.</para>
       </note>
 
       <para>A &man.mount.ntfs.8; parancs használatával az
 	NTFS partíciók hasonló módon
 	csatlakoztathatóak.</para>
     </sect2>
 
     <sect2>
       <title>Kérdések és válaszok</title>
 
       <qandaset>
 	<qandaentry>
 	  <question>
 	    <para>A rendszerem teljesen leáll amikor az
 	      indítás során eszközöket
 	      próbál megtalálni, vagy
 	      furcsán viselkedik a telepítés
 	      során, esetleg a floppy meghajtót nem is
 	      keresi.</para>
 	  </question>
 	  <answer>
 	    <para>A &os; az i386, amd64 és ia64 platformokon az
 	      indítás közben az eszközök
 	      felderítésében erõsen
 	      építkeznek a rendszeren elérhetõ
 	      ACPI szolgáltatásra.  Sajnos még
 	      mindig vannak hibák az ACPI meghajtóban, az
 	      alaplapokban és a BIOS-okban.  A
 	      rendszerbetöltõ harmadik fokozatában
 	      viszont az <literal>hint.acpi.0.disabled</literal>
 	      megadásával kikapcsolható az ACPI
 	      használata:</para>
 
 	    <screen><userinput>set hint.acpi.0.disabled="1"</userinput></screen>
 
 	    <para>Ez a beállítás a rendszer minden
 	      egyes indításakor törlõdik,
 	      ezért a <literal>hint.acpi.0.disabled="1"</literal>
 	      bejegyzést fel kell vennünk a
 	      <filename>/boot/loader.conf</filename>
 	      állományba.  A rendszerbetöltõ
 	      mûködésérõl
 	      részletesebben a <xref linkend="boot-synopsis"/>ban
 	      olvashatunk.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>A &os; telepítése után
 	      elõször indítom el a merevlemezrõl a
 	      rendszert, a rendszermag betöltõdik és
 	      nekilát felkutatni a hardvereszközöket,
 	      azonban megáll a következõ
 	      üzenettel:</para>
 
 	    <screen>changing root device to ad1s1a panic: cannot mount root</screen>
 
 	    <para>Mi lehet a gond?  Mit tegyek?</para>
 
 	    <para>Mit jelent a
 	    <literal>bios_drive:interface(unit,partition)kernel_name</literal>
 	      a rendszerindítás során
 	      megjelenõ súgóban?</para>
 	  </question>
 	  <answer>
 	    <para>Ez egy régóta fennálló
 	      probléma olyan rendszerek esetén, ahol a
 	      rendszerindításhoz használt lemez nem
 	      az elsõ.  A BIOS a &os;-tõl eltérõ
 	      sorszámozást használ, és az
 	      általa alkalmazott megfeleltetések
 	      megfejtése nehézkes.</para>
 
 	    <para>Amikor a rendszer indítására
 	      használt lemez nem az elsõ lemez a
 	      rendszerünkben, segítenünk kell a
 	      &os;-nek a megtalálásában.
 	      Két gyakori helyzet alakulhat ki, és mind a
 	      kettõben el kell árulnunk a &os;-nek, hogy hol
 	      található a rendszer
 	      indításához használható
 	      gyökér állományrendszer.  Ezt a
 	      lemez BIOS-ban nyilvántartott
 	      sorszámának, típusának
 	      és a neki megfelelõ &os; szerinti
 	      lemezszám megadásával tehetjük
 	      meg.</para>
 
 	    <para>Az elsõ szituációban két
 	      IDE-lemezünk van, mind a kettõt
 	      masterként állítottuk be a
 	      hozzájuk tartozó IDE-buszokon, és a
 	      közülük a másodikról akarjuk
 	      indítani a &os;-t.  A BIOS ezeket 0.  és 1.
 	      lemezként látja, miközben a &os; pedig
 	      <devicename>ad0</devicename> és
 	      <devicename>ad2</devicename>
 	      eszközként.</para>
 
 	    <para>A &os; 1.  BIOS-számozású lemezen
 	      van, amelynek a típusa <literal>ad</literal>
 	      és a &os; szerinti a 2 sorszámot viseli.
 	      Ezért ezt kell használnunk:</para>
 
 	    <screen><userinput>1:ad(2,a)kernel</userinput></screen>
 
 	    <para>Ha az elsõdleges buszon van egy slave
 	      meghajtónk, akkor mindez nem szükséges
 	      (és valószínûleg rossz
 	      is).</para>
 
 	    <para>A második szituációban egy
 	      SCSI-lemezrõl akarjuk indítani a rendszert,
 	      miközben egy vagy több IDE-lemez is
 	      található a gépünkben.  Ebben az
 	      esetben a &os; szerinti sorszám kisebb lesz, mint a
 	      BIOS szerinti.  Ha tehát a két
 	      IDE-lemezünk mellett van még egy SCSI-lemez
 	      is, akkor annak a BIOS szerinti sorszáma 2, a
 	      típusa <literal>da</literal> és a &os;
 	      szerinti sorszáma pedig 0.  Ennek megfelelõen
 	      a</para>
 
 	    <screen><userinput>2:da(0,a)kernel</userinput></screen>
 
 	    <para>sorral tudjuk elárulni a &os;-nek, hogy a BIOS
 	      szerint 2.  lemezrõl akarjuk indítani, amely a
 	      rendszerben található elsõ
 	      SCSI-lemeznek felel meg.  Ha csak egy IDE-lemezünk
 	      van, akkor a sort kezdjük az <literal>1:</literal>
 	      beírásával.</para>
 
 	    <para>Miután megtaláltuk a megfelelõ
 	      értékeket, a hozzá tartozó
 	      sort egy szövegszerkesztõ
 	      segítségével tegyük
 	      közvetlenül a <filename>/boot.config</filename>
 	      állományba.  A &os; ezen
 	      állomány tartalmát fogja
 	      alapból felhasználni a
 	      <literal>boot:</literal>
 	      bekérésénél, hacsak
 	      másképpen nem utasítjuk.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>A telepítés után
 	      elõször próbálom meg
 	      elindítani a merevlemezrõl a &os;-t, azonban a
 	      rendszerválasztó mindig csak
 	      <literal>F?</literal> opciókat kínál
 	      fel, és a rendszer indítása sem halad
 	      tovább.</para>
 	  </question>
 	  <answer>
 	    <para>A &os; telepítése során rosszul
 	      adtunk meg a partíciószerkesztõben a
 	      merevlemezhez tartozó geometriát.
 	      Menjünk vissza a
 	      partíciószerkesztõhöz és
 	      adjuk meg újra a merevlemezünk helyes
 	      geometriáját.  Ennek
 	      használatához pedig a &os;-t is újra
 	      kell telepítenünk.</para>
 
 	    <para>Ha egyáltalán képtelenek vagyunk
 	      megállapítani a merevlemezhez tartozó
 	      geometriát, akkor próbáljuk meg ezt:
 	      a lemez elején hozzunk létre egy kis
 	      méretû DOS partíciót és
 	      rakjuk utána a &os;-t.  Amikor a
 	      telepítõprogram észreveszi a DOS
 	      partíciót, megpróbálja
 	      magától kikövetkeztetni belõle a
 	      helyes geometriát, ami általában
 	      mûködik is.</para>
 
 	    <para>Ez a tanács ugyan már nem
 	      érvényes, de álljon itt
 	      felvilágosításként:</para>
 
 	    <blockquote>
 	      <para>Ha teljesen egy &os; alapú szerver vagy
 		munkaállomás
 		kialakítására szánjuk a
 		számítógépünket,
 		és nem törõdünk a DOS-szal,
 		Linuxszal és a többi operációs
 		rendszerrel történõ
 		(jövõbeli) kompatibilitással,
 		használhatjuk akár az egész lemezt
 		is (a partíciószerkesztõben ez az
 		<guimenuitem>A</guimenuitem> opció).  Ezzel egy
 		olyan nem szabványos
 		beállítást
 		engedélyezünk, amivel a &os; elfoglalja a
 		lemezt annak legelsõ szektorától a
 		legutolsó szektoráig.  Ilyenkor ugyan el
 		tudunk tekinteni a geometriával kapcsolatos
 		beállításoktól, azonban
 		így a &os;-n kívül semmilyen
 		más operációs rendszert nem tudunk
 		majd futtatni a gépen.</para>
 	    </blockquote>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>A rendszer megtalálja a &man.ed.4;
 	      hálózati kártyámat, azonban
 	      folyamatosan hibát ad
 	      idõtúllépésre hivatkozva.</para>
 	  </question>
 	  <answer>
 	    <para>Az említett kártya
 	      valószínûleg a
 	      <filename>/boot/device.hints</filename>
 	      állományban
 	      beállítottaktól eltérõ
 	      IRQ-t használ.  A &man.ed.4; meghajtó
 	      alapértelmezés szerint nem használ
 	      <quote>szoftveres</quote>
 	      beállításokat (amiket DOS-ban az
 	      EZSETUP használatával adunk meg), viszont
 	      engedélyezhetjük, ha a
 	      kártyánál megadjuk az
 	      <literal>-l</literal>
 	      beállítást.</para>
 
 	    <para>Hardveresen ezt a kártyán levõ
 	      jumperek segítségével
 	      állíthatjuk be (ehhez változtassuk
 	      meg a rendszermag beállításait is,
 	      amennyiben szükséges), vagy a
 	      <literal>-l</literal> kapcsolón keresztül a
 	      <literal>hint.ed.0.irq="-l"</literal>
 	      megadásával utasíthatjuk a
 	      rendszermagot az IRQ szoftveres
 	      beállítására.</para>
 
 	    <para>Másik lehetõség, amikor a
 	      kártyánk a 9-es IRQ-t használja,
 	      amelyet általában megosztanak a 2-es
 	      IRQ-val, ami gyakori problémák
 	      forrása (különösen abban az esetben,
 	      amikor a VGA kártya a 2-es IRQ-t használja!)
 	      lehet.  Lehetõleg ne használjuk a 2-es
 	      és 9-es IRQ-kat.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <indexterm>
 	      <primary>színek</primary>
 	      <secondary>kontraszt</secondary>
 	    </indexterm>
 
 	    <para>Amikor a <application>sysinstall</application>
 	      programot egy X11 terminálban futtatom, a
 	      sárga színû betûket viszonylag
 	      nehéz olvasni a világosszürke
 	      háttérrel.  Esetleg lehet valahogy
 	      növelni a kontrasztot az alkalmazás
 	      használatakor?</para>
 	  </question>
 
 	  <answer>
 	    <para>Ha az X11 telepítése után a
 	      <application>sysinstall</application> által
 	      választott színekkel nem olvasható a
 	      szöveg &man.xterm.1; vagy &man.rxvt.1;
 	      terminálokban, akkor vegyük fel a
 	      következõ sort a felhasználói
 	      könyvtárunkban levõ
 	      <filename>.Xdefaults</filename>
 	      konfigurációs állományunkba:
 	      <literal>XTerm*color7:#c0c0c0</literal>.  Ezzel majd egy
 	      sötétebb szürke hátteret
 	      kapunk.</para>
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect2>
   </sect1>
 
   <sect1 id="install-advanced">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Valentino</firstname>
 	  <surname>Vaschetto</surname>
 	  <contrib>Írta: </contrib>
 	</author>
 
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Frissítette: </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title>Telepítési útmutató
       haladóknak</title>
 
     <para>Ebben a szakaszban megtudhatjuk, hogyan telepítsük
       a &os;-t speciális esetekben.</para>
 
     <sect2 id="headless-install">
       <title>A &os; telepítése billentyûzet vagy
 	monitor nélkül</title>
 
       <indexterm>
 	<primary>telepítés</primary>
 	<secondary>fej nélküli (soros konzol)</secondary>
       </indexterm>
       <indexterm><primary>soros konzol</primary></indexterm>
 
       <para>A telepítés ezen fajtáját
 	<quote>fej nélküli
 	telepítésnek</quote> (headless install)
 	hívják, mivel a gép, amire a &os;-t
 	telepíteni akarjuk, nem rendelkezik monitorral vagy
 	éppen még VGA kimenettel sem.  Felmerülhet a
 	kérdés: hogyan lehetséges mindez?  A soros
 	vonali konzol használatával!  A soros konzol
 	segítségével lényegében egy
 	másik számítógép
 	monitorját és billentyûzetét
 	használjuk.  Ennek
 	megvalósításához
 	elsõként kövessük a
 	rendszerindító pendrive
 	készítésének <xref
 	  linkend="install-boot-media"/>ban leírt
 	lépéseit, vagy töltsük le a
 	megfelelõ ISO image-et a telepítéshez,
 	lásd <xref linkend="install-cdrom"/>.</para>
 
       <para>A következõ lépésekkel tehetjük
 	képessé a soros konzolon keresztüli
 	rendszerindításra: (CD-lemez használata
 	esetén az elsõ lépésre nincs
 	szükség)</para>
 
       <procedure>
 	<step>
 	  <title>A rendszerindító pendrive
 	    átállítása soros
 	    konzolra</title>
 
 	    <indexterm><primary><command>mount</command></primary></indexterm>
 
 	    <para>Ha a korábban elõkészített
 	      pendrive-val most csak egyszerûen
 	      elindítanánk a &os;-t, akkor a megszokott
 	      telepítési módban indulna el.  Mi
 	      viszont azt akarjuk, hogy a telepítéshez a
 	      &os; a soros konzolon keresztül induljon el.  Ehhez
 	      csatlakoztassuk az eszközt a
 	      számítógéphez, valamint a
 	      &man.mount.8; paranccsal &os; rendszerünkhöz
 	      pedig a hozzátartozó
 	      állományrendszert.</para>
 
 	    <screen>&prompt.root; <userinput>mount /dev/<replaceable>da0a</replaceable> <replaceable>/mnt</replaceable></userinput></screen>
 
 	    <note>
 	      <para>A konkrét eszköznevet és
 		csatlakozási pontot módosítsuk a
 		saját környezetünknek
 		megfelelõen.</para>
 	    </note>
 
 	    <para>Most, miután már fizikailag és
 	      logikailag is csatlakoztattuk a pendrive-ot, be kell
 	      állítanunk a soros konzol
 	      használatára rendszerindítás
 	      közben.  Ehhez egy <filename>loader.conf</filename>
 	      nevû állományt kell elhelyeznünk a
 	      pendrive állományrendszerén a soros
 	      konzolra (mint rendszerkonzolra) vonatkozó
 	      beállítással:</para>
 
 	    <screen>&prompt.root; <userinput>echo 'console="comconsole"' &gt;&gt; <replaceable>/mnt/</replaceable>/boot/loader.conf</userinput></screen>
 
 	    <para>Miután a pendrive-on sikeresen
 	      elvégeztük a szükséges
 	      beállítást, válasszuk le a
 	      &man.umount.8; parancs kiadásával:</para>
 
 	    <screen>&prompt.root; <userinput>umount <replaceable>/mnt</replaceable></userinput></screen>
 
 	    <para>Most már leválaszthatjuk a pendrive-ot,
 	      és ugorjunk közvetlenül a harmadik
 	      lépésre.</para>
 	  </step>
 
 	  <step>
 	    <title>A null-modem kábel
 	      csatlakoztatása</title>
 
 	    <indexterm><primary>null-modem
 	      kábel</primary></indexterm>
 
 	    <para>Össze kell kötnünk a két
 	      számítógépet egy <link
 		linkend="term-cables-null">null-modem
 	      kábel</link>lel.  Nincs más teendõnk,
 	      mit összekapcsolni a két gép soros
 	      portjait.  <emphasis>Itt a szokásos soros
 	      kábel nem mûködik</emphasis>,
 	      konkrétan null-modem kábelre van
 	      szükség, mivel benne néhány
 	      vezetéket máshogy kötöttek
 	      be.</para>
 	  </step>
 
 	  <step>
 	    <title>A telepítõ CD
 	      beállítása soros konzolra</title>
 
 	    <indexterm>
 	      <primary><command>mount</command></primary>
 	    </indexterm>
 
 	    <para>Ha a telepítésre szánt ISO
 	      image-bõl készített lemezzel (lásd
 	      <xref linkend="install-cdrom"/>) a &os; normál
 	      módban indul el.  A soros konzol
 	      használatához viszont kibontani,
 	      módosítani és
 	      újragenerálni kell az adott image-et
 	      mielõtt lemezre írnánk.</para>
 
       <para>A korábban, például a
 	<filename>&os;-<replaceable>8.1</replaceable>-RELEASE-<replaceable>i386</replaceable>-disc1.iso</filename>
 	néven letöltött image-bõl a &man.tar.1;
 	segédprogrammal tudjuk kinyerni a benne tárolt
 	összes állományt:</para>
 
 	    <screen>&prompt.root; <userinput>mkdir <replaceable>/a/hasznalt/iso/helye</replaceable></userinput>
 &prompt.root; <userinput>tar -C <replaceable>/a/hasznalt/iso/helye</replaceable> -pxvf &os;-<replaceable>8.1</replaceable>-RELEASE-<replaceable>i386</replaceable>-disc1.iso</userinput></screen>
 
 	    <para>Ezt követõen módosítanunk kell
 	      a telepítõlemezt a soros konzol
 	      használatára.  Ehhez egy
 	      <filename>loader.conf</filename> állományt
 	      kell hozzáadnunk a kibontott ISO image
 	      tartalmához.  Ebben állítjuk be a
 	      soros konzolt rendszerkonzolnak:</para>
 
 	    <screen>&prompt.root; <userinput>echo 'console="comconsole"' &gt;&gt; <replaceable>/a/hasznalt/iso/helye</replaceable>/boot/loader.conf</userinput></screen>
 
 	    <para>Ezután készítsünk egy
 	      új ISO image-et a módosított tartalom
 	      alapján.  Ehhez a <filename
 		role="package">sysutils/cdrtools</filename> port
 	      részeként elérhetõ
 	      &man.mkisofs.8; segédprogramot
 	      használjuk:</para>
 
 	    <screen>&prompt.root; <userinput>mkisofs -v -b boot/cdboot -no-emul-boot -r -J -V "<replaceable>soroskonzolos</replaceable>" -o <replaceable>soroskonzolos</replaceable>-&os;-<replaceable>8.1</replaceable>-RELEASE-<replaceable>i386</replaceable>-disc1.iso <replaceable>/a/hasznalt/iso/helye</replaceable></userinput></screen>
 
 	    <para>Most már van egy megfelelõen
 	      összeállított ISO image-ünk, amelyet
 	      CD-lemezre tudunk írni a kedvenc
 	      CD-író alkalmazásunkkal.</para>
 	  </step>
 
 	  <step>
 	    <title>A telepítés
 	      indítása</title>
 
 	    <para>Most már ideje elkezdeni a
 	      telepítést.  Tegyük a
 	      <filename>boot.flp</filename> image-et tartalmazó
 	      lemezt a fej nélkül telepítendõ
 	      gép meghajtójába és kapcsoljuk
 	      be.</para>
 	  </step>
 
 	  <step>
 	    <title>Kapcsolódás a fej nélküli
 	      gépre</title>
 
 	    <indexterm><primary><command>cu</command></primary></indexterm>
 
 	    <para>Ezután a &man.cu.1; parancs
 	      felhasználásával kapcsolódjunk
 	      rá a gépre:</para>
 
 	    <screen>&prompt.root; <userinput>cu -l /dev/cuau0</userinput></screen>
 
 	    <para>Ezt &os;&nbsp;7.<replaceable>X</replaceable>
 	      esetén így kell használnunk:</para>
 
 	    <screen>&prompt.root; <userinput>cu -l /dev/cuad0</userinput></screen>
 	  </step>
       </procedure>
 
       <para>Ezzel készen is vagyunk!  Innentõl a
 	<command>cu</command> által megnyitott kapcsolaton
 	keresztül tudjuk vezérelni a fej nélküli
 	számítógépet.  Hamarosan
 	betölti a rendszermagot, majd megkérdezi a
 	használt terminál típusát.  Itt
 	válasszuk ki a színes &os; konzolt (&os; color
 	console) és folytassuk a telepítést a
 	megszokott módon.</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-diff-media">
     <title>Saját telepítõeszköz
       elkészítése</title>
 
     <note>
       <para>Az ismétlések elkerülése
 	végett a továbbiakban a <quote>&os; lemez</quote>
 	a megvásárolható vagy a magunk által
 	készített &os; CD-re vagy DVD-re
 	vonatkozik.</para>
     </note>
 
     <para>Adódhatnak olyan esetek, amikor létre kell
       hoznunk a &os; telepítésére használt
       saját eszközünket és/vagy
       forrásunkat.  Ez lehet egy tetszõleges fizikai
       eszköz, például szalag, vagy bármilyen
       olyan forrás, ahonnan a
       <application>sysinstall</application> képes
       állományokat elérni, például
       egy FTP oldal vagy egy &ms-dos; partíció.</para>
 
     <para>Például:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Egy &os; lemezünk van és több
 	  hálózaton kapcsolódó
 	  számítógépünk.
 	  Készíteni akarunk egy helyi FTP oldalt a &os;
 	  lemez felhasználásával, és
 	  így a hálózaton levõ gépre az
 	  internet helyett innen telepítjük a
 	  rendszert.</para>
       </listitem>
 
       <listitem>
 	<para>Van egy &os; lemezünk, azonban a &os;-nek nem
 	  sikerült felismernie a CD/DVD-meghajtónkat,
 	  viszont az &ms-dos;/&windows;-nak igen.  Felmásoljuk a
 	  &os; telepítéséhez használt
 	  állományokat ugyanazon a
 	  számítógépen
 	  található egyik DOS partícióra,
 	  majd a &os;-t ezekkel telepítjük.</para>
       </listitem>
 
       <listitem>
 	<para>A gépben, amelyre telepíteni akarunk, nincs
 	  CD/DVD-meghajtó vagy hálózati
 	  kártya, viszont <quote>Laplink
 	  stílusú</quote> soros vagy párhuzamos
 	  kábellel hozzá tudunk kapcsolódni egy
 	  olyan számítógéprõl, amelyben
 	  viszont van.</para>
       </listitem>
 
       <listitem>
 	<para>Készíteni akarunk a &os;
 	  telepítésére használható
 	  szalagot.</para>
       </listitem>
     </itemizedlist>
 
     <sect2 id="install-cdrom">
       <title>Telepítõ CD
 	készítése</title>
 
       <para>A &os; Projekt minden kiadás részeként
 	architektúránként
 	elérhetõvé tesz legalább két CD
 	image-et (<quote>ISO image-et</quote>).  Ha rendelkezünk
 	CD-íróval, ezeket az image-eket fel-, illetve ki
 	tudjuk írni (<quote>égetni</quote>) CD-re,
 	és a &os; telepítésére tudjuk
 	használni.  Tehát ha van a kezünk
 	ügyében CD-író és olcsón
 	jutunk nagyobb sebességû
 	interneteléréshez, akkor a &os;
 	telepítésének ez a legkönnyebb
 	módja.</para>
 
       <procedure>
 	<step>
 	  <title>A megfelelõ ISO image-ek
 	    letöltése</title>
 
 	  <para>Az egyes kiadások ISO image-ei
 	    letölthetõek a
 	    <filename>ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-<replaceable>architektúra</replaceable>/<replaceable>változat</replaceable></filename>
 	    címrõl vagy annak legközelebbi
 	    tükrözésérõl.  Az
 	    <replaceable>architektúra</replaceable> és
 	    <replaceable>változat</replaceable> részeket
 	    igényeinknek megfelelõen
 	    helyettesítsük.</para>
 
 	  <para>Az említett könyvtár
 	    általában a következõ lemezek
 	    image-eit tartalmazza:</para>
 
 	  <table frame="none">
 	    <title>FreeBSD 7.<replaceable>X</replaceable> és
 	      8.<replaceable>X</replaceable> ISO image-ek nevei
 	      és jelentései</title>
 
 	    <tgroup cols="2">
 	      <thead>
 
 		<row>
 		  <entry>Állománynév</entry>
 		  <entry>Tartalom</entry>
 		</row>
 	      </thead>
 	      <tbody>
 		<row>
 		  <entry><filename>&os;-<replaceable>változat</replaceable>-RELEASE-<replaceable>architektúra</replaceable>-bootonly.iso</filename></entry>
 
 		  <entry>Ezzel a CD image-dzsel tudjuk a &os;
 		    CD-meghajtóról
 		    indításával elkezdeni a
 		    telepítést.  Fontos tudnunk azonban,
 		    hogy ez az image nem tartalmazza a &os;
 		    telepítéséhez
 		    szükséges komponenseket.  Ezt a rendszer
 		    indítása után
 		    hálózaton keresztül
 		    (például egy FTP szerver
 		    segítségével) tudjuk
 		    megtenni.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>&os;-<replaceable>változat</replaceable>-RELEASE-<replaceable>architektúra</replaceable>-dvd1.iso.gz</filename></entry>
 
 		  <entry>Ez a DVD image minden, az alap &os; rendszer
 		    telepítéséhez
 		    szükséges komponenst tartalmaz,
 		    bináris csomagokkal és
 		    dokumentációval együtt.
 		    Ezenkívül még
 		    <quote>élõ</quote> rendszert is tudunk
 		    indítani vele, közvetlenül a
 		    lemezrõl.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>&os;-<replaceable>változat</replaceable>-RELEASE-<replaceable>architektúra</replaceable>-memstick.img</filename></entry>
 
 		  <entry>Ez az image egy USB pendrive-ra
 		    írható, és minden olyan
 		    számítógépen
 		    használható, amely képes ilyen
 		    eszközrõl elindulni.  Támogatja az
 		    <quote>élõ</quote> módot is,
 		    amellyel rendszerünket
 		    állíthatjuk helyre.  Ez az image nem
 		    érhetõ el &os;&nbsp;7.3 vagy
 		    korábbi rendszerek esetén.</entry>
 		</row>
 
 
 		<row>
 		  <entry><filename>&os;-<replaceable>változat</replaceable>-RELEASE-<replaceable>architektúra</replaceable>-disc1.iso</filename></entry>
 
 		  <entry>Ez az image tartalmazza az alap &os;
 		    operációs rendszert és a
 		    hozzá tartozó
 		    dokumentációt, de semmilyen más
 		    további csomagot nem.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>&os;-<replaceable>változat</replaceable>-RELEASE-<replaceable>architektúra</replaceable>-disc2.iso</filename></entry>
 
 		  <entry>Ezen az image-en bináris csomagok
 		    találhatóak.  Ilyen a &os;&nbsp;8.0
 		    és az utána következõ
 		    változatoknál már
 		    nincs.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>&os;-<replaceable>változat</replaceable>-RELEASE-<replaceable>architektúra</replaceable>-disc3.iso</filename></entry>
 
 		  <entry>Ez egy másik image, amelyen
 		    szintén bináris csomagok
 		    találhatóak.  Ilyen a &os;&nbsp;8.0
 		    és az utána következõ
 		    változatoknál már
 		    nincs.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>&os;-<replaceable>változat</replaceable>-RELEASE-<replaceable>architektúra</replaceable>-docs.iso</filename></entry>
 
 		  <entry>A &os; dokumentációja.</entry>
 		</row>
 
 		<row>
 		  <entry><filename>&os;-<replaceable>változat</replaceable>-RELEASE-<replaceable>architektúra</replaceable>-livefs.iso</filename></entry>
 
 		  <entry>Ez az image a
 		    rendszerhelyreállításhoz
 		    használt <quote>élõ</quote>
 		    indítási módot
 		    támogatja, telepítést
 		    alapvetõen nem lehet vele
 		    végezni.</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </table>
 
 	  <note>
 	    <para>A &os;&nbsp;7.3 és a &os;&nbsp;8.1 elõtti
 	      7.<replaceable>X</replaceable>, illetve
 	      8.<replaceable>X</replaceable> kiadások egy
 	      ettõl eltérõ elnevezési
 	      sémát követnek: a hozzájuk
 	      tartozó ISO image-ek neveiben nem szerepel a
 	      <literal>&os;-</literal> elõtag.</para>
 	  </note>
 
 	  <para>Le <emphasis>kell</emphasis> töltenünk az
 	    elsõ lemez vagy (ha elérhetõ) a
 	    <literal>bootonly</literal> lemez ISO image-einek
 	    egyikét.  A kettõt egyszerre viszont ne
 	    töltsük le, mivel a <literal>disc1</literal> image
 	    tartalmaz mindent, ami a <literal>bootonly</literal>
 	    image-en megtalálható.</para>
 
 	  <para>Akkor használjuk a <literal>bootonly</literal>
 	    jelzésû image-et, ha
 	    szélessávú
 	    interneteléréssel rendelkezünk.
 	    Segítségével el tudjuk kezdeni a &os;
 	    telepítését, és
 	    szükség szerint a port/csomagrendszer
 	    (lásd <xref linkend="ports"/>)
 	    használatával csomagokat tudunk letölteni
 	    és telepíteni.</para>
 
 	  <para>A DVD image-ét (<literal>dvd1</literal>) akkor
 	    érdemes használni, ha a &os; adott
 	    kiadásának telepítése mellett
 	    igényt tartunk valamennyi csomagra is.</para>
 
 	  <para>A további lemezek image-ei is hasznosak lehetnek,
 	    de nem feltétlenül kellenek a
 	    telepítéshez, fõleg abban az esetben,
 	    amikor gyors interneteléréssel
 	    rendelkezünk.</para>
 	</step>
 
 	<step>
 	  <title>A CD-k írása</title>
 
 	  <para>Ezután lemezekre kell írnunk a
 	    letöltött image-eket.  Amennyiben ezt egy
 	    másik &os; rendszeren végezzük, ennek
 	    részleteirõl a <xref linkend="creating-cds"/>
 	    számol be (különösen a <xref
 	    linkend="burncd"/> és a <xref linkend="cdrecord"/>
 	    leírása).</para>
 
 	  <para>Ha másik platformon végezzük ezt a
 	    mûveletet, akkor az adott platformon
 	    felkínált CD-író szoftverekkel
 	    kell dolgoznunk.  Az image-ek szabványos ISO
 	    formátumúak, amelyet szinte az összes
 	    CD-író alkalmazás ismer.</para>
 	</step>
       </procedure>
 
       <note>
 	<para>Ha kíváncsiak vagyunk egy saját &os;
 	  kiadás elkészítésére,
 	  olvassuk el a <ulink
 	  url="&url.articles.releng.en;">kiadások
 	  szervezésérõl szóló cikket
 	  (angolul)</ulink>.</para>
       </note>
 
     </sect2>
 
     <sect2 id="install-ftp">
       <title>Helyi FTP oldal létrehozása &os;
 	lemezzel</title>
 
       <indexterm>
 	<primary>telepítés</primary>
 	<secondary>hálózat</secondary>
 	<tertiary>FTP</tertiary>
       </indexterm>
 
       <para>A &os; lemezeken az FTP oldalakéhoz hasonló
 	elrendezést találunk.  Ez megkönnyíti
 	a hálózatunkban található
 	számítógépekhez a &os;
 	telepítésére használható
 	helyi FTP oldal létrehozását.</para>
 
       <procedure>
 	<step>
 	  <para>Az FTP oldalnak otthont adó &os;
 	    számítógépen tegyük a CD-t
 	    a meghajtóba, majd csatlakoztassuk a
 	    <filename>/cdrom</filename> könyvtárba.</para>
 
 	  <screen>&prompt.root; <userinput>mount /cdrom</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Hozzunk létre egy anonim FTP
 	    hozzáférést az
 	    <filename>/etc/passwd</filename> állományban.
 	    A &man.vipw.8; segítségével
 	    tehát illesszük be a következõ sort az
 	    <filename>/etc/passwd</filename>
 	    állományba:</para>
 
 	  <programlisting>ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
 	</step>
 
 	<step>
 	  <para>Gondoskodjuk róla, hogy az FTP
 	    szolgáltatás engedélyezve legyen az
 	    <filename>/etc/inetd.conf</filename>
 	    állományban.</para>
 	</step>
       </procedure>
 
       <para>Most már bárki, aki képes csatlakozni
 	ehhez a számítógéphez, a
 	telepítés típusának ki tudja
 	választani az FTP-t.  Az FTP oldalak
 	menüjében válassza az <quote>Other</quote>
 	(Egyéb) pontot, majd adja meg az
 	<userinput>ftp://<replaceable>gépnév</replaceable></userinput>
 	címet.</para>
 
       <note>
 	<para>Ha az FTP-n csatlakozó kliensek
 	  rendszerindításhoz használt eszköze
 	  (általában a floppy) verziója nem egyezik
 	  meg tökéletesen a helyi FTP oldalon
 	  találhatóval, akkor a
 	  <application>sysinstall</application> nem engedi a
 	  telepítést.  Ha a változatok nem
 	  hasonlóak és ezt felül akarjuk
 	  bírálni, akkor be kell lépnünk az
 	  <guimenu>Options</guimenu> (Beállítások)
 	  menübe, ahol át kell állítanunk a
 	  terjesztés nevét (distribution name)
 	  <guimenuitem>any</guimenuitem> (bármelyik)-re.</para>
       </note>
 
       <warning>
 	<para>A fenti megközelítés
 	  kizárólag csak egy tûzfallal védett
 	  helyi hálózaton javasolt.  FTP
 	  szolgáltatás létrehozása az
 	  interneten (és nem a helyi hálózatunkban)
 	  levõ számítógépek
 	  számára különbözõ
 	  támadásoknak és egyéb
 	  kellemetlenségeknek teszi ki a
 	  számítógépünket.
 	  Határozottan javasoljuk, hogy ebben az esetben
 	  különösen ügyeljünk a
 	  biztonságra.</para>
       </warning>
     </sect2>
 
       <sect2>
 	<title>Telepítõfloppyk
 	  létrehozása</title>
 
       <indexterm>
 	<primary>telepítés</primary>
 	<secondary>floppy</secondary>
       </indexterm>
 
 	<para>Ha floppylemezrõl kellene telepítenünk
 	  (amit viszont <emphasis>semmiképpen sem</emphasis>
 	  ajánlanánk) egy nem támogatott
 	  hardvereszköz miatt, vagy mert egyszerûen
 	  szeretjük a dolgok nehezebbik oldalát megfogni,
 	  akkor ehhez elõször elõ kell
 	  készítenünk pár lemezt.</para>
 
 	<para>Legalább annyi 1,44&nbsp;MB-os lemezre van
 	  szükségünk, mint amennyire
 	  ráférnek a <filename>base</filename>
 	  (alapterjesztés) könyvtárban
 	  található állományok.  Ha DOS-ban
 	  hozzuk létre ezeket a lemezeket, akkor a
 	  használatukhoz meg <emphasis>kell</emphasis>
 	  formázni ezeket az &ms-dos; <command>FORMAT</command>
 	  parancsával.  &windows; használata esetén
 	  az Windows Explorerben (Intézõben) tudjuk
 	  megformázni a lemezeket (kattintsunk a jobb gombbal az
 	  <devicename>A:</devicename> meghajtóra, majd
 	  válasszuk a <quote>Format</quote>
 	  (Formázás) menüpontot).</para>
 
 	<para><emphasis>Ne</emphasis> bízzunk a gyárilag
 	  formázott (<quote>pre-formatted</quote>
 	  jelzésû) lemezekben!  Menjünk biztosra
 	  és formázzuk meg mi magunk is lemezeket.  A
 	  felhasználóinktól régebben
 	  számtalan olyan panasz érkezett, amely a
 	  helytelenül megformázott lemezbõl fakadt,
 	  ezért erre most kiemelten felhívjuk a
 	  figyelmet.</para>
 
 	<para>A formázás abban az esetben sem bizonyul
 	  rossz ötletnek, ha egy másik &os; gépen
 	  gyártjuk le a lemezeket, habár nem kell
 	  mindegyik lemezre DOS állományrendszert
 	  tennünk.  Helyette a <command>bsdlabel</command>
 	  és <command>newfs</command> parancsok
 	  használatával UFS
 	  állományrendszert is tehetünk rájuk,
 	  ahogy (1,44&nbsp;MB méretû lemezek esetén)
 	  ezt az alábbi parancsok mutatják:</para>
 
 	<screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
 &prompt.root; <userinput>bsdlabel -w fd0.1440 floppy3</userinput>
 &prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
 
 	<para>Ezután a többi
 	  állományrendszerhez hasonlóan a lemezeket
 	  tudjuk csatlakoztatni és írni.</para>
 
 	<para>Miután megformáztuk a lemezeket,
 	  rájuk kell másolnunk az
 	  állományokat.  A terjesztésekhez
 	  tartozó állományokat adott
 	  méretû darabokra szeleteltük, így
 	  kényelmesen ráférnek egy
 	  hagyományos 1,44&nbsp;MB méretû floppyra.
 	  Menjünk végig az összes floppyn és
 	  mindegyikre pakoljuk fel a lehetõ legtöbb
 	  állományt egészen addig, amíg
 	  így az összes szükséges
 	  terjesztést össze nem szedtük.  A floppykon
 	  minden terjesztés kerüljön egy
 	  hozzá tartozó alkönyvtárba,
 	  például: <filename>a:\base\base.aa</filename>,
 	  <filename>a:\base\base.ab</filename> és így
 	  tovább.</para>
 
 	<important>
 	  <para>Az elsõ lemezre rá kell másolnunk a
 	    <filename>base.inf</filename> nevû
 	    állományt is, mivel ennek
 	    beolvasásával lesz képes
 	    kitalálni a telepítõ, hogy a
 	    terjesztések összeszedése és
 	    összefûzése során mennyi darabot
 	    keressen.</para>
 	</important>
 
 	<para>Ahogy elérkezünk a
 	  telepítõeszköz
 	  kiválasztásához a telepítés
 	  folyamatában, ott válasszuk a
 	  <guimenuitem>Floppy</guimenuitem> menüpontot, majd
 	  utána kövessük a felbukkanó
 	  üzeneteket.</para>
 
       </sect2>
 
       <sect2 id="install-msdos">
 	<title>Telepítés &ms-dos;
 	  partícióról</title>
 
 	<indexterm>
 	  <primary>telepítés</primary>
 	  <secondary>MS-DOS partícióról</secondary>
 	</indexterm>
 
 	<para>Amikor egy &ms-dos; partícióról
 	  akarunk telepíteni,
 	  elõkészítés gyanánt
 	  másoljuk a terjesztésekhez tartozó
 	  állományokat a partícióra egy
 	  <filename>freebsd</filename> könyvtárba.  Ez lesz
 	  például a <filename>c:\freebsd</filename>.
 	  Ebben a könyvtárban igyekezzük minél
 	  jobban megtartani a CD vagy az FTP oldal
 	  könyvtárszerkezetét, ezért erre a
 	  CD-rõl történõ
 	  átmásolásra a DOS
 	  <command>xcopy</command> parancsát javasoljuk.
 	  Például így tudjuk
 	  elõkészíteni a &os; legegyszerûbb
 	  változatának
 	  telepítését:</para>
 
 	<screen><prompt>C:\&gt;</prompt> <userinput>md c:\freebsd</userinput>
 <prompt>C:\&gt;</prompt> <userinput>xcopy e:\bin c:\freebsd\bin\ /s</userinput>
 <prompt>C:\&gt;</prompt> <userinput>xcopy e:\manpages c:\freebsd\manpages\ /s</userinput></screen>
 
 	<para>A fentiekben feltételeztük, hogy ehhez a
 	  <devicename>C:</devicename> meghajtón elég
 	  szabad helyünk van, valamint az
 	  <devicename>E:</devicename> meghajtón érjük
 	  el a CD-t.</para>
 
 	<para>Ha nincs CD-meghajtónk, az <ulink
 	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">ftp.FreeBSD.org</ulink>
 	  címrõl letölthetjük a
 	  terjesztésket.  Minden egyes terjesztés
 	  külön könyvtárban
 	  található, tehát például a
 	  <emphasis>base</emphasis> (alap) terjesztés az <ulink
 	  url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/base/">&rel.current;/base/</ulink>
 	  könyvtárban található.</para>
 
 	<para>Mindegyik telepítendõ terjesztést (ami
 	  még elfér) másoljuk át az &ms-dos;
 	  partíció <filename>c:\freebsd</filename>
 	  könyvtárába &mdash; a
 	  telepítéshez egyébként
 	  egyedül a <literal>BIN</literal> terjesztés
 	  szükséges.</para>
 
       </sect2>
 
       <sect2>
 	<title>Telepítõszalag
 	  létrehozása</title>
 
 	<indexterm>
 	  <primary>telepítés</primary>
 	  <secondary>QIC/SCSI-szalagról</secondary>
 	</indexterm>
 
 	<para>Valószínûleg a szalagos módszer
 	  a legegyszerûbb, egyfajta élõ FTP-s vagy CD-s
 	  telepítés.  A telepítõprogram arra
 	  számít, hogy a szalagon az
 	  állományok egymás után
 	  helyezkednek el.  Tehát miután beszereztük
 	  a nekünk kellõ terjesztésekhez tartozó
 	  összes állományt, egyszerûen
 	  vegyük fel ezeket a szalagra:</para>
 
 	<screen>&prompt.root; <userinput>cd /freebsd/distdir</userinput>
 &prompt.root; <userinput>tar cvf /dev/rwt0 dist1 ... dist2</userinput></screen>
 
 	<para>Mielõtt telepítenénk,
 	  ellenõrizzük, hogy legyen elég helyünk
 	  valamelyik (a telepítés során majd
 	  kiválasztható átmeneti)
 	  könyvtárban ahhoz, hogy az itt létrehozott
 	  szalag <emphasis>teljes</emphasis> tartalma elférjen
 	  benne.  Mivel a szalagok csak szekvenciálisan
 	  érhetõek el, ezért ennél a
 	  módszernél jó sok ideiglenes
 	  tárhelyre lesz szükségünk.</para>
 
 	<note>
 	  <para>A telepítés megkezdése után
 	    a szalagnak már <emphasis>azelõtt</emphasis> a
 	    meghajtóban kell lennie, hogy
 	    rendszerindító floppyról
 	    elindítanánk a rendszert,
 	    máskülönben nem találja meg.</para>
 	</note>
 
       </sect2>
 
       <sect2>
 	<title>Mielõtt hálózatról
 	  telepítenénk</title>
 
 	<indexterm>
 	  <primary>telepítés</primary>
 	  <secondary>hálózat</secondary>
 	  <tertiary>soros (PPP)</tertiary>
 	</indexterm>
 	<indexterm>
 	  <primary>telepítés</primary>
 	  <secondary>hálózat</secondary>
 	  <tertiary>párhuzamos (PLIP)</tertiary>
 	</indexterm>
 	<indexterm>
 	  <primary>telepítés</primary>
 	  <secondary>hálózat</secondary>
 	  <tertiary>Ethernet</tertiary>
 	</indexterm>
 
 	<para>Háromféle hálózati
 	  telepítési mód létezik: Ethernet
 	  (szabványos Ethernet-vezérlõvel), soros
 	  port (PPP) vagy párhuzamos port (PLIP
 	  (laplink kábel)).</para>
 
 	<para>Valószínûleg az
 	  Ethernet-csatlakozó választásával
 	  érjük el a leggyorsabb hálózati
 	  telepítést.  A &os; ismeri a legtöbb PC-s
 	  Ethernet kártyát.  Az ismert
 	  kártyák (és a hozzájuk
 	  tartozó beállítások) a &os; egyes
 	  kiadásának hardverjegyzékében
 	  (Hardware Notes) találhatóak meg.  Amennyiben
 	  egy támogatott PCMCIA Ethernet kártyát
 	  használunk, mindig a laptop bekapcsolása
 	  <emphasis>elõtt</emphasis> helyezzük be!  A &os;
 	  telepítés közben sajnos nem
 	  támogatja a PCMCIA kártyák
 	  menetközbeni behelyezését.</para>
 
 	<para>Ezenkívül még ismernünk kell a
 	  hálózaton kapott IP-címünket, az
 	  általa használt címosztály
 	  hálózati maszkját, a gépünk
 	  nevét.  Ha PPP kapcsolaton keresztül
 	  telepítünk és nincs statikus
 	  IP-címünk, akkor minden bizonnyal az
 	  internet-szolgáltatónktól kaptunk egyet
 	  dinamikusan.  A konkrét hálózati
 	  beállításokat a hálózatunk
 	  rendszergazdájától is érdemes
 	  megkérdezni.  Ha a hálózaton levõ
 	  többi gépre névvel és nem
 	  IP-címmel hivatkozunk, akkor
 	  szükségünk lesz még egy
 	  név(feloldó) szerverre és az internet
 	  eléréséhez egy
 	  átjáró címére is (ha PPP-t
 	  használunk, ez a szolgáltatónk
 	  IP-címe lesz).  Ha FTP-rõl HTTP proxy
 	  használatával telepítünk, akkor a
 	  proxy címe is kelleni fog.  Ha magunktól nem
 	  vagyunk képesek ezekre a kérdésekre
 	  válaszolni, akkor az ilyen típusú
 	  telepítés megkezdése
 	  <emphasis>elõtt</emphasis> tényleg
 	  segítséget kell kérnünk egy
 	  rendszergazdától vagy az
 	  internet-szolgáltatónktól.</para>
 
 	<para>Ha modemet használunk, akkor a PPP szinte biztosan
 	  megfelel nekünk.  Gondoskodjunk róla, hogy
 	  már a telepítés korai szakaszában
 	  rendelkezésünkre áll az
 	  internet-szolgáltatónkkal kapcsolatosan minden
 	  hasznos információ.</para>
 
 	<para>Ha PAP vagy CHAP használatával
 	  kapcsolódunk a szolgáltatónkhoz
 	  (másképp szólva &windows;-ban így
 	  tudunk szkriptek nélkül csatlakozni),
 	  mindössze a <command>dial</command> parancsot kell
 	  kiadnunk a <application>ppp</application>
 	  parancssorában.  Minden más esetben tudnunk kell
 	  a modemünk saját <quote>AT parancsaival</quote>
 	  tárcsázni az
 	  internet-szolgáltatónkat, hiszen ehhez a PPP
 	  tárcsázó csak egy nagyon kezdetleges
 	  terminálemulációt nyújt.  Ezzel
 	  kapcsolatban olvassuk el <link linkend="userppp">a
 	  kézikönyv</link> és a <ulink
 	  url="&url.books.faq.en;/ppp.html">GYIK</ulink>
 	  idevágó részeit.  Ha gondjaink
 	  akadnának, a naplózás a <command>set log
 	  local ...</command> parancs kiadásával
 	  átirányítható
 	  közvetlenül a képernyõre.</para>
 
 	<para>Ha kötött módon tudunk csatlakozni egy
 	  másik (2.0-R vagy késõbbi
 	  verziójú) &os; géphez, akkor
 	  megpróbálkozhatunk a párhuzamos
 	  <quote>laplink</quote> kábellel.  A párhuzamos
 	  porton keresztüli adatátvitel sebessége a
 	  soros vonalénál jóval nagyobb
 	  (egészen 50&nbsp;kbyte/mp), ezért vele a
 	  telepítés is gyorsabb.</para>
 
 	<sect3>
 	  <title>Mielõtt NFS-rõl
 	    telepítenénk</title>
 
 	  <indexterm>
 	    <primary>telepítés</primary>
 	    <secondary>hálózat</secondary>
 	    <tertiary>NFS</tertiary>
 	  </indexterm>
 
 	  <para>A telepítés NFS-en keresztül szinte
 	    magától értetõdik.
 	    Egyszerûen csak másoljuk a &os;
 	    terjesztéseihez tartozó
 	    állományokat az NFS szerverre és
 	    állítsuk be rá az NFS
 	    telepítõeszközt.</para>
 
 	  <para>Ha a szerver csak <quote>privilegizált
 	    portokat</quote> ismer (ami általában
 	    alapértelmezett a Sun
 	    munkaállomásoknál), a
 	    telepítés megkezdése elõtt az
 	    <guimenu>Options</guimenu>
 	    (Beállítások) menüben be kell
 	    állítani az <literal>NFS Secure</literal>
 	    (Biztonságos NFS) opciót.</para>
 
 	  <para>Ha egy gyenge minõségû és kis
 	    adatátviteli sebességû Ethernet
 	    kártyánk van, akkor emellett még
 	    hasznos lehet beállítani az <literal>NFS
 	    Slow</literal> (Lassú NFS) opciót is.</para>
 
 	  <para>Az NFS-en keresztüli telepítés
 	    mûködéséhez a szervernek
 	    támogatnia kell az alkönyvtárak
 	    csatlakoztatását is, tehát
 	    például ha a &os;&nbsp;&rel.current;
 	    terjesztésünk a
 	    <filename>ziggy:/usr/archive/stuff/FreeBSD</filename>
 	    könyvtárban található, akkor
 	    <hostid>ziggy</hostid> nevû gépnek
 	    lehetõvé kell tennie a
 	    <filename>/usr/archive/stuff/FreeBSD</filename>
 	    könyvtár közvetlen
 	    csatlakoztatását is, nem csak a
 	    <filename>/usr</filename> vagy
 	    <filename>/usr/archive/stuff</filename>
 	    könyvtárakét.</para>
 
 	  <para>A &os; <filename>/etc/exports</filename>
 	    állományában ezt az
 	    <option>-alldirs</option> beállítással
 	    vezérelhetjük.  Más NFS szervereken
 	    esetleg más megszokásokat kell
 	    követnünk.  Amennyiben a szervertõl
 	    <errorname>permission denied</errorname>
 	    (hozzáférés megtagadva) üzeneteket
 	    kapjuk, valószínû, hogy ezt nem
 	    állítottuk be megfelelõen.</para>
 
 	</sect3>
       </sect2>
   </sect1>
 </chapter>
diff --git a/it_IT.ISO8859-15/books/handbook/install/chapter.xml b/it_IT.ISO8859-15/books/handbook/install/chapter.xml
index 3fdb9b38d6..634d056073 100644
--- a/it_IT.ISO8859-15/books/handbook/install/chapter.xml
+++ b/it_IT.ISO8859-15/books/handbook/install/chapter.xml
@@ -1,5519 +1,5513 @@
 <?xml version="1.0" encoding="iso-8859-15"?>
 <!--
      The FreeBSD Italian Documentation Project
 
      $FreeBSD$
      Original revision: 1.337
 -->
 
 <chapter id="install">
   <chapterinfo>
     <authorgroup>
       <author>
         <firstname>Jim</firstname>
 
         <surname>Mock</surname>
 
         <contrib>Ristrutturato, riorganizzato, ed in parte
           riscritto da </contrib>
       </author>
     </authorgroup>
 
     <authorgroup>
       <author>
         <firstname>Randy</firstname>
 
         <surname>Pratt</surname>
 
         <contrib>Il tour guidato su sysinstall, e gli screenshot sono
           di </contrib>
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>Installazione di FreeBSD</title>
 
   <sect1 id="install-synopsis">
     <title>Sinossi</title>
 
     <indexterm><primary>installazione</primary></indexterm>
 
     <para>FreeBSD è fornito di un programma di installazione basato su
       testo, facile da usare, chiamato <application>sysinstall</application>.
       Questo è il programma di installazione di default di FreeBSD,
       sebbene i fornitori siano liberi di usare la loro suite di installazione
       se preferiscono.  Questo capitolo descrive come usare
       <application>sysinstall</application> per installare FreeBSD.</para>
 
     <para>Dopo aver letto questo capitolo, saprai:</para>
 
     <itemizedlist>
       <listitem>
         <para>Come creare i dischi di installazione di FreeBSD.</para>
       </listitem>
 
       <listitem>
         <para>Come FreeBSD fa riferimento, e suddivide i tuoi hard disk.</para>
       </listitem>
 
       <listitem>
         <para>Come far partire <application>sysinstall</application>.</para>
       </listitem>
 
       <listitem>
         <para>Le domande che <application>sysinstall</application> ti
           farà, cosa vogliono dire, e come rispondere.</para>
       </listitem>
     </itemizedlist>
 
     <para>Prima di leggere capitolo, dovresti:</para>
 
     <itemizedlist>
       <listitem>
         <para>Leggere la lista dell'hardware supportato inclusa nella versione
           di FreeBSD che stai installando, e verificare che il tuo hardware
           sia supportato.</para>
       </listitem>
     </itemizedlist>
 
     <note>
       <para>In generale, queste istruzioni di installazione sono scritte per
         computer con architettura &i386; (<quote>PC compatibile</quote>).
         Dove richiesto, saranno fornite istruzioni specifiche per altre
         piattaforme (ad esempio, Alpha).  Sebbene questa guida sia
         aggiornata il più possibile, potresti trovare piccole differenze
         tra la procedura di installazione e quello che viene mostrato qui.
         È consigliato usare questo capitolo come una guida generale
         piuttosto che un manuale di installazione vero e proprio.</para>
     </note>
   </sect1>
 
   <sect1 id="install-pre">
     <title>Compiti Prima dell'Installazione</title>
 
     <sect2 id="install-inventory">
       <title>Inventario del Tuo Computer</title>
 
       <para>Prima di installare FreeBSD dovresti fare un inventario dei
         componenti del tuo computer.  Durante l'installazione di FreeBSD
         ti verranno mostrati tutti i componenti (hard disk, schede di
         rete, CDROM, e così via), il loro modello e chi li fabbrica.
         FreeBSD tenter&aacute; di determinare la configurazione corretta per i
         vari dispositivi, incluse le informazioni riguardo la corretta
         configurazione sia dell'IRQ che delle porte I/O da usare.  A causa
         della varietà di hardware dei PC non è detto che il
         processo venga completato con successo, quindi potrai avere bisogno
         di modificare la tua configurazione.</para>
 
       <para>Se hai già un altro sistema operativo installato, ad
         esempio &windows; o Linux, potrebbe essere una buona idea vedere come
         è configurato l'hardware su quei sistemi operativi.  Se non sei
         sicuro della configurazione usata da una certa scheda di espansione,
         potresti trovare la configurazione stampata sulla scheda stessa.  I
         numeri IRQ più comuni sono 3, 5 e 7,e le porte di indirizzo
         I/O sono di norma scritte in numeri esadecimali, come 0x330.</para>
 
       <para>Raccomandiamo di scrivere o di stampare queste informazioni prima
         di installare FreeBSD.  Può essere d'aiuto usare una tabella,
         come questa:</para>
 
       <table pgwide="1" frame="none">
         <title>Esempio di Inventario dei Dispositivi</title>
 
         <tgroup cols="4">
           <colspec colwidth="2*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="4*"/>
 
           <thead>
             <row>
               <entry>Nome Dispositivo</entry>
 
               <entry>IRQ</entry>
 
               <entry>porte di I/O</entry>
 
               <entry>Note</entry>
             </row>
           </thead>
 
           <tbody>
             <row>
               <entry>Primo hard disk</entry>
 
               <entry>N/A</entry>
 
               <entry>N/A</entry>
 
               <entry>40&nbsp;GB, fabbricato da Seagate, primo IDE master</entry>
             </row>
 
             <row>
               <entry>CDROM</entry>
 
               <entry>N/A</entry>
 
               <entry>N/A</entry>
 
               <entry>Primo IDE slave</entry>
             </row>
 
             <row>
               <entry>Secondo hard disk</entry>
 
               <entry>N/A</entry>
 
               <entry>N/A</entry>
 
               <entry>20&nbsp;GB, fabbricato da IBM, secondo IDE master</entry>
             </row>
 
             <row>
               <entry>Primo controller IDE</entry>
 
               <entry>14</entry>
 
               <entry>0x1f0</entry>
 
               <entry></entry>
             </row>
 
             <row>
               <entry>Scheda di rete</entry>
 
               <entry>N/A</entry>
 
               <entry>N/A</entry>
 
               <entry>&intel; 10/100</entry>
             </row>
 
             <row>
               <entry>Modem</entry>
 
               <entry>N/A</entry>
 
               <entry>N/A</entry>
 
               <entry>&tm.3com; 56K faxmodem, su COM1</entry>
             </row>
 
             <row>
               <entry>&hellip;</entry>
             </row>
           </tbody>
         </tgroup>
       </table>
     </sect2>
 
     <sect2>
       <title>Backup Dei Tuoi Dati</title>
 
       <para>Se il computer dove installerai FreeBSD contiene dati importanti,
         fai un backup dei dati, quindi verifica il backup prima di iniziare
         un'installazione di FreeBSD.  La procedura di installazione di FreeBSD
         ti avviserà prima di scrivere dati sul tuo disco, ma una volta
         confermato il processo questo non può più essere
         annullato.</para>
     </sect2>
 
     <sect2 id="install-where">
       <title>Decidere Dove Installare FreeBSD</title>
 
       <para>Se vuoi usare l'intero disco per installare FreeBSD, puoi saltare
         tranquillamente questa sezione.</para>
 
       <para>Altrimenti, se vuoi che FreeBSD coesista con altri sistemi
         operativi allora hai bisogno di una conoscenza basilare di come i dati
         sono organizzati sul disco.</para>
 
       <sect3 id="install-where-i386">
         <title>Disposizione Del Disco per &i386;</title>
 
         <para>Un disco di un PC può essere suddiviso in diverse parti.
           Queste parti vengono chiamate
           <firstterm>partizioni</firstterm>.  Per sua natura, un PC supporta
           solo quattro partizioni per disco.  Queste partizioni sono chiamate
           <firstterm>partizioni primarie</firstterm>.   Per aggirare questa
           limitazione e avere più di quattro partizioni, è stata
           progettata un nuovo tipo di partizione, la <firstterm>partizione
             estesa</firstterm>.  Un disco può contenere una sola
           partizione estesa.  All'interno di questa partizione estesa possono
           essere create partizioni speciali, chiamate <firstterm>partizioni
             logiche</firstterm>.</para>
 
         <para>Ogni partizione ha un'<firstterm>ID di partizione</firstterm>, che
           è un numero usato per identificare il tipo di dati nella
           partizione.  L'ID di partizione di FreeBSD è
           <literal>165</literal>.</para>
 
         <para>In generale, ogni sistema operativo che usi identificherà
           le sue partizioni in un modo particolare.  Per esempio, il DOS, e i
           suoi discendenti, come &windows;, assegnano ad ogni partizione
           primaria e logica una <firstterm>lettera di dispositivo</firstterm>,
           cominciando con <devicename>C:</devicename>.</para>
 
         <para>FreeBSD deve essere installato su una partizione primaria.
           I dati di FreeBSD, inclusi i tuoi file, possono risiedere tutti su
           questa unica partizione.  Comunque, se hai più dischi, puoi
           creare una partizione FreeBSD su tutti i dischi (o su parte di essi).
           Quando installi FreeBSD, devi avere una partizione disponibile.
           Questa potrebbe essere una nuova partizione che hai preparato,
           o potrebbe essere una partizione esistente che contiene dati che
           non ti interessano più.</para>
 
         <para>Se già usi tutte le partizioni di ogni tuo disco, dovrai
           liberare una partizione per FreeBSD utilizzando i programmi forniti
           dagli altri sistemi operativi che usi (es., <command>fdisk</command>
           su DOS o &windows;).</para>
 
         <para>Se hai una partizione libera puoi usare quella.  Comunque,
           potresti avere la necessità di restringere una o più
           delle tue partizioni.</para>
 
         <para>Un'installazione minima di FreeBSD richiede un piccolo spazio di
           100&nbsp;MB sull'hard disk.  Comunque, questa è
           <emphasis>proprio</emphasis> un'installazione minima, che non
           lascia molto spazio per altri tuoi file.  Una partizione minima
           più realistica è di 250&nbsp;MB, senza ambiente grafico,
           e di 350&nbsp;MB o anche di più se vuoi un'interfaccia grafica.
           Se hai intenzione di installare diverso software di terze parti, avrai
           bisogno di molto più spazio.</para>
 
         <para>Puoi usare programmi commerciali come ad esempio
           <application>&partitionmagic;</application> o programmi free come
           <application>GParted</application> per ridimensionare le
           tue partizioni e creare spazio per FreeBSD.  La directory
           <filename>tools</filename> sul CDROM contiene due software gratuiti
           che possono eseguire questo compito, <application>FIPS</application> e
           <application>PResizer</application>.  La documentazione per entrambi
           questi strumenti è disponibile nella stessa directory.
           <application>FIPS</application>, <application>PResizer</application>,
           e <application>&partitionmagic;</application> possono ridimensionare
           partizioni <acronym>FAT16</acronym> e <acronym>FAT32</acronym> &mdash;
           usate da &ms-dos; fino a &windows; ME.
           Sia <application>&partitionmagic;</application> che
           <application>GParted</application> sono noti per maneggiare
           anche partizioni <acronym>NTFS</acronym>.</para>
 
         <warning>
           <para>L'uso scorretto di questi programmi può causare la
             perdita di dati nel tuo hard disk.  Assicurati di avere un backup
             recente e funzionante prima di usare questi strumenti.</para>
         </warning>
 
         <example>
           <title>Usare una Partizione Esistente</title>
 
           <para>Supponiamo che tu abbia un computer con un singolo disco di
             4&nbsp;GB con già installato una versione di &windows;, e che
             tu abbia suddiviso il disco in due lettere di dispositivo,
             <devicename>C:</devicename> e <devicename>D:</devicename>, ognuno
             dei quali ha dimensioni pari a 2&nbsp;GB.  Hai 1&nbsp;GB di dati
             su <devicename>C:</devicename>, e 0.5&nbsp;GB di dati su
             <devicename>D:</devicename>.</para>
 
           <para>Questo significa che il tuo disco ha due partizioni, una per
             lettera.  Puoi copiare tutti i tuoi dati da
             <devicename>D:</devicename> a <devicename>C:</devicename>, in modo
             da liberare la seconda partizione, pronta per FreeBSD.</para>
         </example>
 
         <example>
           <title>Restringere una Partizione Esistente</title>
 
           <para>Supponiamo che tu abbia un computer con un singolo disco da
             4&nbsp;GB dove è già installata una versione di
             &windows;.  Quando hai installato &windows; hai creato un'unica
             grande partizione, il dispositivo <devicename>C:</devicename> con
             capacità pari a 4&nbsp;GB.  Hai usato 1.5&nbsp;GB di
             spazio, e vorresti usarne 2&nbsp;GB per FreeBSD.</para>
 
           <para>Per installare FreeBSD hai due differenti
             possibilità:</para>
 
           <orderedlist>
             <listitem>
               <para>Fare il backup dei tuoi dati in &windows;, e installarlo di
                 nuovo, occupando solamente 2&nbsp;GB.</para>
             </listitem>
 
             <listitem>
               <para>Utilizzare uno strumento come
                 <application>&partitionmagic;</application>, come descritto
                 in precedenza, per restringere la partizione di
                 &windows;.</para>
             </listitem>
           </orderedlist>
         </example>
       </sect3>
 
       <sect3>
         <title>Disposizione del Disco per Alpha</title>
 
         <indexterm><primary>Alpha</primary></indexterm>
 
         <para>Dovrai dedicare un intero disco per FreeBSD su Alpha.  Attualmente
           non è possibile condividere un disco con altri sistemi
           operativi.  A seconda della macchina Alpha che possiedi, il disco
           può essere sia SCSI che IDE, sempre che la tua macchina sia
           capace di fare il boot da essi.</para>
 
         <para>Seguendo la convenzione dei manuali della Digital / Compaq tutti
           gli input SRM sono maiuscoli.  SRM è case insensitive.</para>
 
         <para>Per determinare i nomi e i tipi dei dischi nella tua macchina,
           usa il comando <literal>SHOW DEVICE</literal> dal prompt della console
           SRM:</para>
 
         <screen>&gt;&gt;&gt;<userinput>SHOW DEVICE</userinput>
 dka0.0.0.4.0               DKA0           TOSHIBA CD-ROM XM-57  3476
 dkc0.0.0.1009.0            DKC0                       RZ1BB-BS  0658
 dkc100.1.0.1009.0          DKC100             SEAGATE ST34501W  0015
 dva0.0.0.0.1               DVA0
 ewa0.0.0.3.0               EWA0              00-00-F8-75-6D-01
 pkc0.7.0.1009.0            PKC0                  SCSI Bus ID 7  5.27
 pqa0.0.0.4.0               PQA0                       PCI EIDE
 pqb0.0.1.4.0               PQB0                       PCI EIDE</screen>
 
         <para>Questo esempio è stato preso da una Digital Personal
           Workstation 433au e mostra tre dischi collegati alla macchina.
           Il primo è un lettore CDROM chiamato
           <devicename>DKA0</devicename>, mentre gli altri due dischi sono
           chiamati rispettivamente <devicename>DKC0</devicename> e
           <devicename>DKC100</devicename>.</para>
 
         <para>I nomi dei dischi del tipo <devicename>DKx</devicename> , sono
           dischi SCSI.  Per esempio <devicename>DKA100</devicename>
           è riferito al disco SCSI con ID 1 sul primo bus SCSI (A),
           mentre <devicename>DKC300</devicename> si riferisce al disco SCSI con
           ID 3 sul terzo bus SCSI (C).  Il nome del dispositivo
           <devicename>PKx</devicename> si riferisce all'adattatore SCSI.
           Come visto nell'output di <literal>SHOW DEVICE</literal> i CDROM SCSI
           sono trattati come dischi SCSI.</para>
 
         <para>I dischi IDE hanno un nome del tipo <devicename>DQx</devicename>,
           mentre ai nomi <devicename>PQx</devicename> sono associati i
           controller IDE.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Raccogli i Dettagli di Configurazione della tua Rete</title>
 
       <para>Se intendi installare FreeBSD tramite una connessione di rete
         (per esempio, un'installazione tramite FTP, oppure un server NFS),
         allora dovrai conoscere la tua configurazione di rete.  Ti verranno
         richieste queste informazioni durante l'installazione in modo che
         FreeBSD possa connettersi alla rete e completare l'installazione.</para>
 
       <sect3>
         <title>Connessione a una Rete Ethernet o tramite un Modem
           Cable/DSL</title>
 
         <para>Se hai la possibilità di connetterti a una rete Ethernet,
           o se hai una connessione a Internet tramite un adattatore Ethernet
           via cavo o DSL, allora avrai bisogno delle seguenti
           informazioni:</para>
 
         <orderedlist>
           <listitem>
             <para>Indirizzo IP</para>
           </listitem>
 
           <listitem>
             <para>Indirizzo IP del gateway di default</para>
           </listitem>
 
           <listitem>
             <para>Il nome host (hostname)</para>
           </listitem>
 
           <listitem>
             <para>Indirizzi IP dei server DNS</para>
           </listitem>
 
           <listitem>
             <para>Maschera di Rete</para>
           </listitem>
         </orderedlist>
 
         <para>Se non conosci queste informazioni, puoi chiederle al tuo
           amministratore di sistema oppure al tuo provider.  Potrebbero dirti
           che queste informazioni sono assegnate automaticamente,
           usando <firstterm>DHCP</firstterm>.  Se così fosse, prendi
           nota.</para>
       </sect3>
 
       <sect3>
         <title>Connessione Tramite Modem</title>
 
         <para>Se ti connetti al tuo ISP usando un modem puoi installare
           FreeBSD da Internet, e questo richiederà molto tempo.</para>
 
         <para>In questo caso dovrai sapere:</para>
 
         <orderedlist>
           <listitem>
             <para>Il numero di telefono per la connessione del tuo ISP</para>
           </listitem>
 
           <listitem>
             <para>La porta COM: sulla quale il tuo modem è
               connesso</para>
           </listitem>
 
           <listitem>
             <para>Il nome utente e relativa password del tuo account
               dell'ISP</para>
           </listitem>
         </orderedlist>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Controllare i Possibili Errori di FreeBSD Post-Release</title>
 
       <para>Sebbene il progetto di FreeBSD si impegna per
         assicurare che ogni release di FreeBSD sia stabile il più
         possibile, può capitare che ogni tanto qualche bug sfugga durante
         il processo di costruzione della release.  In rare occasioni questi bug
         interessano il processo di installazione.  Non appena questi problemi
         sono scoperti e fixati, gli stessi sono segnalati nella <ulink
           url="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">FreeBSD
           Errata</ulink>, che è possibile trovare sul sito web di
         FreeBSD.  Dovresti verificare questo documento prima di iniziare
         l'installazione in modo tale da essere a conoscenza dei bug
         esistenti.</para>
 
       <para>Le informazioni sulle varie release, inclusi i vari errata
         per ogni release, possono essere trovati nella sezione <ulink
           url="&url.base;/releases/index.html">informazioni di release</ulink>
         sul <ulink url="&url.base;/index.html">sito web di
           FreeBSD</ulink>.</para>
     </sect2>
 
     <sect2>
       <title>Ottenere i File di Installazione di FreeBSD</title>
 
       <para>Il processo di installazione di FreeBSD può installare
          FreeBSD prendendo file da una delle seguenti fonti:</para>
 
       <itemizedlist>
         <title>Media Locale</title>
 
         <listitem>
           <para>Un CDROM o DVD</para>
         </listitem>
 
         <listitem>
           <para>Una partizione DOS sullo stesso computer</para>
         </listitem>
 
         <listitem>
           <para>Un nastro magnetico SCSI o QIC</para>
         </listitem>
 
         <listitem>
           <para>Floppy disk</para>
         </listitem>
       </itemizedlist>
 
       <itemizedlist>
         <title>Rete</title>
 
         <listitem>
           <para>Un sito FTP, passando attraverso un firewall, o usando un proxy
             HTTP, a seconda della necessità</para>
         </listitem>
 
         <listitem>
           <para>Un server NFS</para>
         </listitem>
 
         <listitem>
           <para>Una connessione parallela o seriale dedicata</para>
         </listitem>
       </itemizedlist>
 
       <para>Se hai comprato il CD o il DVD di FreeBSD allora hai già
         tutto ciò che necessiti, e dovresti passare alla prossima
         sezione (<xref linkend="install-floppies"/>).</para>
 
       <para>Se non ti sei procurato i file di installazione di FreeBSD dovresti
         saltare alla <xref linkend="install-diff-media"/> che spiega
         come prepararsi all'installazione di FreeBSD.  Dopo aver letto
         quella sezione, puoi tornare indietro e leggere la <xref
           linkend="install-floppies"/>.</para>
     </sect2>
 
     <sect2 id="install-floppies">
       <title>Preparare i Media per il Boot</title>
 
       <para>Il processo di installazione di FreeBSD ha inizio avviando il tuo
         computer nel programma di installazione di FreeBSD&mdash;non è
         un programma che puoi avviare da un altro sistema operativo.
         Normalmente il tuo computer fa il boot usando il sistema operativo
         installato sul tuo hard disk, ma puoi configurare il tuo computer
         affinchè faccia il boot da floppy disk <quote>avviabili</quote>.
         Inoltre la maggior parte dei computer odierni possono fare il boot da
         CDROM.</para>
 
       <tip>
         <para>Se possiedi FreeBSD su CDROM o su DVD (sia che l'hai comprato
           o preparato per conto tuo), ed il tuo computer consente di fare il
           boot da CDROM o DVD (solitamente tramite un'opzione del BIOS
           chiamata <quote>Boot Order</quote> o simili), allora puoi saltare
           questa sezione.  Le immagini CDROM o DVD di FreeBSD sono avviabili
           e possono essere utilizzate per installare FreeBSD senza altre
           preparazioni particolari.</para>
       </tip>
 
       <para>Per creare un'immagine floppy avviabile, segui i seguenti
         passi :</para>
 
       <procedure>
         <step>
           <title>Ottenere l'Immagine Floppy Avviabile</title>
 
           <para>I dischi avviabili sono disponibili nel tuo media di
             installazione nella directory <filename>floppies/</filename>,
             inoltre possono essere scaricate dalla directory
             <filename>floppies/</filename>,
             <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>&lt;arch&gt;</replaceable>/<replaceable>&lt;version&gt;</replaceable>-RELEASE/floppies/</literal>.
             Sostituisci <replaceable>&lt;arch&gt;</replaceable>
             e <replaceable>&lt;version&gt;</replaceable> rispettivamente con
             l'architettura e il numero di versione che vuoi installare.
             Per esempio, le immagini floppy avviabili per
             &os;&nbsp;&rel.current;-RELEASE per &i386; sono disponibili
             in <ulink
               url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/"></ulink>.</para>
 
           <para>Le immagini floppy hanno l'estensione <filename>.flp</filename>.
             La directory <filename>floppies/</filename> contiene diverse
             immagini, a seconda della versione di FreeBSD che vuoi installare, e
             in alcuni casi, a seconda dell'hardware che possiedi.
             Nella maggior parte dei casi avrai bisogno di
             tre floppy, <filename>boot.flp</filename>,
             <filename>kern1.flp</filename>, e <filename>kern2.flp</filename>.
             Consulta il file <filename>README.TXT</filename> che puoi trovare
             nella stessa directory al fine di avere maggiori informazioni
             riguardanti le immagine floppy.</para>
 
           <note>
             <para>Possono essere necessari driver di dispositivi aggiuntivi
               per sistemi 5.X più vecchi di &os;&nbsp;5.3.
               Queste driver sono forniti dall'immagine
               <filename>drivers.flp</filename>.</para>
           </note>
 
           <important>
             <para>Il tuo programma FTP deve usare la <emphasis>modalità
               binaria</emphasis> per poter scaricare queste immagini floppy.
               Alcuni browser web usano la modalità
               <emphasis>testo</emphasis> (chiamata anche
               <emphasis>ASCII</emphasis>), e ti accorgerai di questo se non
               riuscirai ad avviare da floppy.</para>
           </important>
         </step>
 
         <step>
           <title>Preparare i Dischetti Floppy</title>
 
           <para>Devi preparare un disco floppy per ogni immagine che hai
             scaricato.  Questi dischetti non devono avere difetti.  Il
             metodo più semplice per verificare ciò è
             formattare i dischi.  Non avere fiducia dei dischetti
             pre-formattati.  Lo strumento di formattazione in &windows; non
             segnala l'eventuale presenza di blocchi danneggiati, semplicemente
             li segna come <quote>difettosi</quote> e li ignora.  È
             consigliabile usare dei nuovi dischetti floppy se hai in mente di
             procedere con questo tipo di installazione.</para>
 
           <important>
             <para>Se stai tentando di installare FreeBSD ed il programma di
               installazione crasha, freeza, o non procede come dovrebbe, la
               prima cosa da sospettare sono proprio i floppy.  Prova a scrivere
               i file di immagine floppy su nuovi dischi e riprova.</para>
           </important>
         </step>
 
         <step>
           <title>Scrivere i File Immagine sui Floppy Disk</title>
 
           <para>I file <filename>.flp</filename> <emphasis>non</emphasis>
             sono dei file regolari da copiare sul dischetto.  Sono
             immagini di un contenuto completo di un dischetto.  Questo significa
             che <emphasis>non</emphasis> puoi copiare semplicemente i file
             da un dischetto ad un altro.  Invece, devi usare uno strumento
             specifico per scrivere le immagini direttamente sul
             dischetto.</para>
 
           <indexterm><primary>DOS</primary></indexterm>
 
           <para>Se stai creando i floppy su un computer con in esecuzione
             &ms-dos;/&windows;, allora puoi usare l'utility chiamata
             <command>fdimage</command>.</para>
 
           <para>Se vuoi usare le immagini che stanno nel CDROM, ed il CDROM
             è sul dispositivo <devicename>E:</devicename>, puoi
             impartire questo comando:</para>
 
           <screen><prompt>E:\&gt;</prompt> <userinput>tools\fdimage floppies\kern.flp A:</userinput></screen>
 
           <para>Ripeti questo comando per ogni file <filename>.flp</filename>,
             sostituendo ogni volta il disco floppy, e poi assicurati
             di etichettare ogni floppy con il nome del file che hai
             copiato.  Aggiusta il comando come necessario, a seconda di dove
             hai collocato i file <filename>.flp</filename>.  Se non
             hai il CDROM, puoi scaricare <command>fdimage</command> dalla
             <ulink
               url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">directory
               <filename class="directory">tools</filename></ulink>
             sul sito FTP di FreeBSD.</para>
 
           <para>Se stai creando i floppy su sistema &unix; (come un altro
             sistema FreeBSD) puoi usare il comando &man.dd.1; per scrivere i
             file immagine direttamente sul disco.  Su FreeBSD, dovresti
             eseguire:</para>
 
           <screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput></screen>
 
           <para>Su FreeBSD, <filename>/dev/fd0</filename> è
             riferito al primo floppy disk (il dispositivo
             <devicename>A:</devicename>).  <filename>/dev/fd1</filename> sarebbe
             il dispositivo <devicename>B:</devicename>, e cosi via.  Altre
             varianti &unix; potrebbero avere nomi differenti per i dispositivi
             floppy disk, e se necessario consulta la documentazione del sistema
             che stai usando.</para>
         </step>
       </procedure>
 
       <para>Adesso sei pronto per iniziare ad installare FreeBSD.</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-start">
     <title>Iniziare l'Installazione</title>
 
     <important>
       <para>Per default, l'installazione non apporterà nessun
         cambiamento sul tuo disco (o dischi) fino a quando non vedi questo
         messaggio:</para>
 
       <literallayout class="monospaced">Last Chance: Are you SURE you want continue the installation?
 
 If you're running this on a disk with data you wish to save then WE
 STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding!
 
 We can take no responsibility for lost disk contents!</literallayout>
 
       <para>Il processo di installazione può essere sospeso in qualunque
         momento prima dell'avvertimento finale senza cancellare dati sul tuo
         hard disk.  Se ti sei accorto di aver configurato qualcosa di sbagliato
         puoi ancora spegnere il computer prima di quel avvertimento, senza che
         venga creato alcun danno.</para>
     </important>
 
     <sect2 id="install-starting">
       <title>Avvio</title>
 
       <sect3 id="install-starting-i386">
         <title>Avvio per &i386;</title>
 
         <procedure>
           <step>
             <para>Iniziamo con il computer spento.</para>
           </step>
 
           <step>
             <para>Accendi il computer.  Appena acceso dovrebbe visualizzare
               un'opzione per entrare nel menù di sistema, chiamato anche
               BIOS, solitamente tramite tasti come <keycap>F2</keycap>,
               <keycap>F10</keycap>, <keycap>Del</keycap>, o
               <keycombo action="simul">
                 <keycap>Alt</keycap>
                 <keycap>S</keycap>
               </keycombo>.  Usa la combinazione di tasti indicata sullo schermo.
               In alcuni casi il tuo computer può visualizzare un'immagine
               durante la fase di avvio.  In genere, premendo
               <keycap>Esc</keycap> l'immagine sparirà e sarai in grado
               di vedere i messaggi di avvio.</para>
           </step>
 
           <step>
             <para>Trova il settaggio che controlla da quali dispositivi il
               sistema tenta l'avvio.  Di solito questo settaggio viene
               identificato con <quote>Boot Order</quote> e in genere mostra
               una lista di dispositivi, come <literal>Floppy</literal>,
               <literal>CDROM</literal>, <literal>First Hard Disk</literal>, e
               così via.</para>
 
             <para>Se vuoi partire con il boot da floppy, assicurati di avere
               selezionato il floppy disk come primo dispositivo di avvio.
               Se invece vuoi partire con il boot da CDROM allora seleziona
               questo come primo dispositivo di avvio.  In caso di dubbio, puoi
               consultare il manuale che ti hanno dato assieme al computer, e/o
               con la scheda madre.</para>
 
             <para>Una volta apportato la modifica, salva ed esci dal BIOS.
               Il computer dovrebbe fare un riavvio.</para>
           </step>
 
           <step>
             <para>Se hai bisogno di preparare i floppy di boot, come descritto
               nella <xref linkend="install-floppies"/>, allora uno di
               questi sarà il primo dischetto di boot, probabilmente
               quello contenente l'immagine <filename>kern.flp</filename>.
               Metti questo disco nel tuo floppy.</para>
 
             <para>Se vuoi fare il boot da CDROM, allora dovrai accendere il
               computer, e inserire il CDROM prima che puoi.</para>
 
             <para>Se il computer parte normalmente e carica il sistema operativo
               già esistente, allora:</para>
 
             <orderedlist>
               <listitem>
                 <para>I dischi non sono stati inseriti prima dell'inizio
                   della fase di avvio.  Lasciali inseriti, e riavvia il
                   computer.</para>
               </listitem>
 
               <listitem>
                 <para>I recenti cambiamenti apportati nel BIOS non sono
                   corretti.  Dovresti rifare i passaggi fino a quando avrai
                   successo.</para>
               </listitem>
 
               <listitem>
                 <para>Il tuo BIOS non supporta il boot dal tuo media
                   desiderato.</para>
               </listitem>
             </orderedlist>
           </step>
 
           <step>
             <para>FreeBSD si avvierà.  Se hai scelto di partire da CDROM
               probabilmente vedrai schermate come queste (le informazioni sulla
               versione sono state omesse):</para>
 
             <screen>Verifying DMI Pool Data ........
 Boot from ATAPI CD-ROM :
  1. FD 2.88MB  System Type-(00)
 Uncompressing ... done
 
 BTX loader 1.00 BTX version is 1.01
 Console: internal video/keyboard
 BIOS drive A: is disk0
 BIOS drive B: is disk1
 BIOS drive C: is disk2
 BIOS drive D: is disk3
 BIOS 639kB/261120kB available memory
 
 FreeBSD/i386 bootstrap loader, Revision 0.8
 
 /kernel text=0x277391 data=0x3268c+0x332a8 |
 
 |
 Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [kernel] in 9 seconds... _</screen>
 
             <para>Se hai fatto il boot da floppy, vedrai simili informazioni sul
               tuo schermo (le informazioni sulla versione sono state
               omesse):</para>
 
             <screen>Verifying DMI Pool Data ........
 
 BTX loader 1.00  BTX version is 1.01
 Console: internal video/keyboard
 BIOS drive A: is disk0
 BIOS drive C: is disk1
 BIOS 639kB/261120kB available memory
 
 FreeBSD/i386 bootstrap loader, Revision 0.8
 
 /kernel text=0x277391 data=0x3268c+0x332a8 |
 
 Please insert MFS root floppy and press enter:</screen>
 
             <para>Segui queste istruzioni, rimuovi il disco
               <filename>kern.flp</filename>, inserisci il disco
               <filename>mfsroot.flp</filename>, e premi <keycap>Invio</keycap>.
               &os;&nbsp;5.3 e superiori hanno ulteriori dischi, come descritto
               nella <link linkend="install-floppies">sezione precedente</link>.
               Avvia dal primo floppy; quando indicato, inserisci gli altri
               dischi.</para>
           </step>
 
           <step>
             <para>Indipendentemente se hai fatto il boot da floppy o da CDROM,
               il processo di avvio arriverà a questo punto:</para>
 
             <screen>Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [kernel] in 9 seconds... _</screen>
 
             <para>Aspetta dieci secondi o premi
               <keycap>Invio</keycap></para>
           </step>
         </procedure>
       </sect3>
 
       <sect3>
         <title>Avvio per Alpha</title>
 
         <indexterm><primary>Alpha</primary></indexterm>
 
         <procedure>
           <step>
             <para>Iniziamo con il computer spento.</para>
           </step>
 
           <step>
             <para>Accendi il computer e attendi che arrivi
               al prompt di avvio.</para>
           </step>
 
           <step>
             <para>Se hai la necessità di preparare i floppy di avvio,
               come descritto nella <xref linkend="install-floppies"/>
               allora uno di questi sarà il primo disco di avvio,
               probabilmente quello che contiene <filename>kern.flp</filename>.
               Inserisci questo disco nel tuo floppy e digita il seguente
               comando per avviare da dischetto (sostituisci il nome del tuo
               floppy se necessario):</para>
 
             <screen>&gt;&gt;&gt;<userinput>BOOT DVA0 -FLAGS '' -FILE ''</userinput></screen>
 
             <para>Se stai avviando da CDROM, inserisci il CDROM nel lettore
               e digita il seguente comando per avviare l'installazione
               (sostituisci il nome del lettore CDROM se necessario):</para>
 
             <screen>&gt;&gt;&gt;<userinput>BOOT DKA0 -FLAGS '' -FILE ''</userinput></screen>
           </step>
 
           <step>
             <para>In fase di avvio partirà FreeBSD.  Se hai fatto
               il boot tramite floppy, ad un certo punto vedrai questo
               messaggio:</para>
 
             <screen>Please insert MFS root floppy and press enter:</screen>
 
             <para>Segui queste istruzioni e rimuovi il disco
               <filename>kern.flp</filename>, inserisci il disco
               <filename>mfsroot.flp</filename>, poi premi
               <keycap>Invio</keycap>.</para>
           </step>
 
           <step>
             <para>Indipendentemente se hai fatto il boot da floppy o da CDROM,
               il processo di avvio arriverà a questo punto:</para>
 
             <screen>Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [kernel] in 9 seconds... _</screen>
 
             <para>Puoi sia aspettate dieci secondi, oppure premere
               <keycap>Invio</keycap>.  In questo modo verrà caricato
               il menù di configurazione del kernel.</para>
           </step>
         </procedure>
       </sect3>
     </sect2>
 
     <sect2 id="view-probe">
       <title>Rivedere i Risultati del Probe dei Dispositivi</title>
 
       <para>Le ultime cento righe che sono state visualizzate sullo
         schermo sono memorizzate e possono essere riviste.</para>
 
       <para>Per rivedere il buffer, premi <keycap>Scroll Lock</keycap>.
         Ti permetterà di scorrere nel video.  Puoi usare i tasti freccia,
         oppure <keycap>PageUp</keycap> e <keycap>PageDown</keycap>
         per vedere i risultati.  Premi di nuovo <keycap>Scroll Lock</keycap>
         per fermare lo scrolling.</para>
 
       <para>Usa questa tecnica per rivedere i messaggi che sono stati
         visualizzati quando il kernel ha effettuato il probe dei dispositivi.
         Vedrai del testo simile alla <xref linkend="install-dev-probe"/>,
         anche se questo potrebbe essere diverso a seconda dei dispositivi
         che hai nel tuo computer.</para>
 
       <figure id="install-dev-probe">
         <title>Risultati Tipo del Probe dei Dispositivi</title>
 
         <screen>avail memory = 253050880 (247120K bytes)
 Preloaded elf kernel "kernel" at 0xc0817000.
 Preloaded mfs_root "/mfsroot" at 0xc0817084.
 md0: Preloaded image &lt;/mfsroot&gt; 4423680 bytes at 0xc03ddcd4
 
 md1: Malloc disk
 Using $PIR table, 4 entries at 0xc00fde60
 npx0: &lt;math processor&gt; on motherboard
 npx0: INT 16 interface
 pcib0: &lt;Host to PCI bridge&gt; on motherboard
 pci0: &lt;PCI bus&gt; on pcib0
 pcib1:&lt;VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge&gt; at device 1.0 on pci0
 pci1: &lt;PCI bus&gt; on pcib1
 pci1: &lt;Matrox MGA G200 AGP graphics accelerator&gt; at 0.0 irq 11
 isab0: &lt;VIA 82C586 PCI-ISA bridge&gt; at device 7.0 on pci0
 isa0: &lt;iSA bus&gt; on isab0
 atapci0: &lt;VIA 82C586 ATA33 controller&gt; port 0xe000-0xe00f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0 &lt;VIA 83C572 USB controller&gt; port 0xe400-0xe41f irq 10 at device 7.2 on pci
 0
 usb0: &lt;VIA 83572 USB controller&gt; on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr1
 uhub0: 2 ports with 2 removable, self powered
 pci0: &lt;unknown card&gt; (vendor=0x1106, dev=0x3040) at 7.3
 dc0: &lt;ADMtek AN985 10/100BaseTX&gt; port 0xe800-0xe8ff mem 0xdb000000-0xeb0003ff ir
 q 11 at device 8.0 on pci0
 dc0: Ethernet address: 00:04:5a:74:6b:b5
 miibus0: &lt;MII bus&gt; on dc0
 ukphy0: &lt;Generic IEEE 802.3u media interface&gt; on miibus0
 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 ed0: &lt;NE2000 PCI Ethernet (RealTek 8029)&gt; port 0xec00-0xec1f irq 9 at device 10.
 0 on pci0
 ed0 address 52:54:05:de:73:1b, type NE2000 (16 bit)
 isa0: too many dependant configs (8)
 isa0: unexpected small tag 14
 orm0: &lt;Option ROM&gt; at iomem 0xc0000-0xc7fff on isa0
 fdc0: &lt;NEC 72065B or clone&gt; at port 0x3f0-0x3f5,0x3f7 irq 6 drq2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: &lt;1440-KB 3.5" drive&gt; on fdc0 drive 0
 atkbdc0: &lt;Keyboard controller (i8042)&gt; at port 0x60,0x64 on isa0
 atkbd0: &lt;AT Keyboard&gt; flags 0x1 irq1 on atkbdc0
 kbd0 at atkbd0
 psm0: &lt;PS/2 Mouse&gt; irq 12 on atkbdc0
 psm0: model Generic PS/@ mouse, device ID 0
 vga0: &lt;Generic ISA VGA&gt; at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: &lt;System console&gt; at flags 0x100 on isa0
 sc0: VGA &lt;16 virtual consoles, flags=0x300&gt;
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: &lt;Parallel port&gt; at port 0x378-0x37f irq 7 on isa0
 pppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/15 bytes threshold
 plip0: &lt;PLIP network interface&gt; on ppbus0
 ad0: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata0-master UDMA33
 acd0: CD-RW &lt;LITE-ON LTR-1210B&gt; at ata1-slave PIO4
 Mounting root from ufs:/dev/md0c
 /stand/sysinstall running as init on vty0</screen>
       </figure>
 
       <para>Analizza attentamente i risultati del probe per assicurarti che
         FreeBSD ha trovato tutti i dispositivi che ti aspetti.  Se non è
         stato trovato un dispositivo, allora questo non sarà in elenco.
         Se il driver del dispositivo richiede la configurazione di IRQ e
         indirizzi di porta allora assicurati di averli inseriti
         correttamente.</para>
 
       <para>Se hai la necessità di modificare dei settaggi
         per il probe dei dispositivi indicati nell'UserConfig, esci dal
         programma <application>sysinstall</application> e ricomincia da capo.
         Questo è anche un modo per prendere confidenza con il processo.</para>
 
       <figure id="sysinstall-exit">
         <title>Selezionare l'Uscita di Sysinstall</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/sysinstall-exit"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Usa i tasti freccia per selezionare
         <guimenuitem>Exit Install</guimenuitem> dal menù principale
         di installazione.  Ti apparirà il seguente messaggio:</para>
 
       <screen>                      User Confirmation Requested
          Are you sure you wish to exit? The system will reboot
            (be sure to remove any floppies from the drives).
 
                             [ Yes ]    No</screen>
 
       <para>Il programma d'installazione partirà nuovamente se il CDROM
         è ancora nel driver ed è selezionata &gui.yes;.</para>
 
       <para>Se hai avviato da floppy sarà necessario rimuovere il
         floppy <filename>mfsroot.flp</filename> e mettere
         <filename>kern.flp</filename> prima di riavviare.</para>
     </sect2>
   </sect1>
 
   <sect1 id="using-sysinstall">
     <title>Introduzione a Sysinstall</title>
 
     <para>L'utility <application>sysinstall</application> è
       l'applicazione di installazione fornita dal FreeBSD Project.  È
       basata sulla console ed è suddivisa in diversi menù e
       schermate che puoi usare per configurare e controllare il processo di
       installazione.</para>
 
     <para>Il sistema a menù di <application>sysinstall</application>
       è governabile tramite i tasti freccia, <keycap>Invio</keycap>,
       <keycap>Spazio</keycap>, e altri tasti.  Una descrizione dettagliata
       di questi tasti e ciò che essi fanno sono contenuti nel
       documento sull'uso di <application>sysinstall</application>.</para>
 
     <para>Per vedere queste informazioni, assicurati che sia evidenziata
       l'entry <guimenuitem>Usage</guimenuitem> e che sia selezionato il
       bottone <guibutton>[Select]</guibutton>, come mostrato in
       <xref linkend="sysinstall-main3"/>, quindi premi
       <keycap>Invio</keycap>.</para>
 
     <para>In questo modo verranno visualizzate le istruzioni per usare il
       sistema a menù.  Premi <keycap>Invio</keycap> per ritornare al
       menù principale.</para>
 
     <figure id="sysinstall-main3">
       <title>Come Selezionare Usage dal Menù Principale di
         Sysinstall</title>
 
       <mediaobject>
         <imageobject>
           <imagedata fileref="install/main1"/>
         </imageobject>
       </mediaobject>
     </figure>
 
     <sect2 id="select-doc">
       <title>Come Selezionare il Menù della Documentazione</title>
 
       <para>Dal menù principale, seleziona con i tasti freccia
         <guimenuitem>Doc</guimenuitem> e premi <keycap>Invio</keycap>.</para>
 
       <figure id="main-doc">
         <title>Come Selezionare il Menù della Documentazione</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/main-doc"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Verrà mostrato il menù della documentazione.</para>
 
       <figure id="docmenu1">
         <title>Menù della Documentazione di Sysinstall</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/docmenu1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>È importante leggere la documentazione.</para>
 
       <para>Per visualizzare un documento, selezionalo con i tasti freccia e
         premi <keycap>Invio</keycap>.  Quando hai finito di leggere il
         documento, premi <keycap>Invio</keycap> per ritornare al menù
         della documentazione.</para>
 
       <para>Per ritornare al Menù di Installazione Principale,
         seleziona <guimenuitem>Exit</guimenuitem> con i tasti freccia e
         premi <keycap>Invio</keycap>.</para>
     </sect2>
 
     <sect2 id="keymap">
       <title>Come Selezionare il Menù Tastiera</title>
 
       <para>Per cambiare la mappatura della tastiera, usa i tasti freccia per
         selezionare <guimenuitem>Keymap</guimenuitem> dal menù e premi
         <keycap>Invio</keycap>.  Questo è richiesto solo se stati usando
         una tastiera non-standard o una tastiera non americana.</para>
 
       <figure id="sysinstall-keymap">
         <title>Menù Principale di Sysinstall</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/main-keymap"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Una diversa mappatura della tastiera può essere selezionata
         nel menù usando i tasti freccia e premendo
         <keycap>Spazio</keycap>.  Premi di nuovo <keycap>Spazio</keycap>
         per deselezionare la tua scelta.  Quando hai finito, scegli &gui.ok;
         usando i tasti freccia e premi <keycap>Invio</keycap>.</para>
 
       <para>Nel successivo screen-shot ne viene mostrata una lista parziale.
         Se selezioni &gui.cancel; premendo <keycap>Tab</keycap> userai la
         mappatura di default e ritornerai al Menù dell'Installazione
         Principale.</para>
 
       <figure id="sysinstall-keymap-menu">
         <title>Menù della Mappatura della Tastiera di Sysinstall</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/keymap"/>
           </imageobject>
         </mediaobject>
       </figure>
     </sect2>
 
     <sect2 id="viewsetoptions">
       <title>Schermata delle Opzioni di Installazione</title>
 
       <para>Seleziona <guimenuitem>Options</guimenuitem> e premi
         <keycap>Invio</keycap>.</para>
 
       <figure id="sysinstall-options">
         <title>Menù Principale di Sysinstall</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/main-options"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <figure id="options">
         <title>Opzioni di Sysinstall</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/options"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>I valori di default sono adeguati per la maggior parte degli utenti
         e solitamente non necessitano modifiche.  Il nome della release
         varierà a seconda della versione che si sta installando.</para>
 
       <para>La descrizione dell'elemento selezionato apparirà illuminato
         in blu in fondo alla schermata.  Nota che una di queste opzioni
         è <guimenuitem>Use Defaults</guimenuitem> per resettare
         tutti i valori ai rispettivi valori di default.</para>
 
       <para>Premi <keycap>F1</keycap> per leggere la schermata di aiuto
         delle varie opzioni.</para>
 
       <para>Premendo <keycap>Q</keycap> ritornerai al Menù di
         Installazione Principale.</para>
     </sect2>
 
     <sect2 id="start-install">
       <title>Iniziare una Installazione Standard</title>
 
       <para>L'installazione <guimenuitem>Standard</guimenuitem> è
         raccomandata per i novizi &unix; o di FreeBSD.  Usa i tasti freccia
         per selezionare <guimenuitem>Standard</guimenuitem> quindi premi
         <keycap>Invio</keycap> per cominciare l'installazione.</para>
 
       <figure id="sysinstall-standard">
         <title>Iniziare l'Installazione Standard</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/main-std"/>
           </imageobject>
         </mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 id="install-steps">
     <title>Allocazione dello Spazio su Disco</title>
 
     <para>Prima di tutto devi allocare dello spazio su disco per FreeBSD, ed
       etichettare quello spazio in modo tale che
       <application>sysinstall</application> possa utilizzarlo.  Per fare questo
       devi conoscere come FreeBSD si aspetta di trovare le informazioni sul
       disco.</para>
 
     <sect2 id="install-drive-bios-numbering">
       <title>Numerazione dei Dispositivi nel BIOS</title>
 
       <para>Prima di installare e configurare FreeBSD sul tuo sistema,
         c'è una cosa importante che devi sapere, specialmente se hai
         più dischi.</para>
 
       <indexterm><primary>DOS</primary></indexterm>
 
       <indexterm><primary>Microsoft Windows</primary></indexterm>
 
       <para>In un PC con un sistema operativo dipendente dal BIOS come &ms-dos;
         o &microsoft.windows;, il BIOS è in grado di ricavare il
         corretto ordine dei dischi, e il sistema operativo concorda con un
         eventuale cambiamento.  Questo consente all'utente di effettuare il boot
         da un disco diverso dal <quote>master primario</quote>.  Questo è
         conveniente soprattutto per alcuni utenti che hanno convenuto che il
         modo più semplice e conveniente per mantenere un sistema
         di backup è di comperare un secondo disco identico al primo,
         e effettuare consuete copie del primo disco sul secondo usando
         <application><trademark
           class="registered">Ghost</trademark></application> o
         <application>XCOPY</application>.  Quindi, se il primo disco fa fiasco,
         è sotto le minacce di un virus, o è scarabocchiato da
         un'imperfezione del sistema operativo stesso, può essere
         facilmente recuperato istruendo il BIOS a swappare logicamente i due
         dischi.  È come cambiare i cavi sui dischi, ma senza dover
         aprire il case.</para>
 
       <indexterm><primary>SCSI</primary></indexterm>
 
       <indexterm><primary>BIOS</primary></indexterm>
 
       <para>I sistemi più costosi con controller SCSI spesso includono
         delle estensioni del BIOS che consentono di riordinare i dischi SCSI
         in modo simile a quanto sopra esposto per un massimo di sette
         dispositivi.</para>
 
       <para>Un utente che è abituato ad usare queste caratteristiche
         può rimanere sorpreso quando vede che i risultati con FreeBSD
         non sono quelli che si aspettava.  FreeBSD non usa il BIOS, e non sa
         nulla riguardo alla <quote>mappatura logica dei dispositivi del
           BIOS</quote>.  Questo può portare a delle situazioni che
         lasciano perplessi, in particolar modo quando i dischi hanno
         un'identica geometria fisica, e sono dei clone di un altro disco.</para>
 
       <para>Quando si ha a che fare con FreeBSD, ripristinare sempre il BIOS
         alla numerazione naturale prima di installare FreeBSD, e lasciarla in
         quel modo.  Se hai bisogno di scambiare i dispositivi, fallo, ma fallo
         fisicamente, aprendo il case e cambiando i cavi e jumper in modo
         opportuno.</para>
 
       <sidebar>
         <title>Un esempio di un'avventura insolita riguardo i File di Bill e
           Fred:</title>
 
         <para>Bill distrugge una vecchia box Wintel per fare una box FreeBSD per
           Fred.  Bill installa un solo disco SCSI come l'unità zero
           SCSI ed installa FreeBSD su di esso.</para>
 
         <para>Fred inizia ad usare il sistema, ma dopo alcuni giorni nota che
           il vecchio disco SCSI riporta numerosi errori e riferisce questo fatto
           a Bill.</para>
 
         <para>Dopo un pò, Bill decide di risolvere la situazione,
           così prende un disco SCSI identico nella stanza
           dell'<quote>archivio</quote> di dischi.  Una scansione iniziale
           indica che il disco funziona bene, dunque Bill installa questo disco
           come la quarta unità SCSI e crea una copia dell'immagine del
           disco zero nel disco quattro.  Ora che il nuovo disco è
           installato e funziona bene, Bill decide che è una buona idea
           iniziare ad usarlo, quindi usa le funzionalità nel BIOS SCSI
           per riordinare i dischi in modo tale che il sistema effettui il boot
           dal disco quattro.  FreeBSD viene avviato e funziona in modo
           corretto.</para>
 
         <para>Fred continua il suo lavoro per parecchi giorni, quando Bill e
           Fred decidono che è ora di una nuova avventura &mdash; tempo
           di aggiornare ad una nuova versione di FreeBSD.  Bill rimuove
           l'unità SCSI zero perchè era un pò fiacca e la
           sostituisce con un'altra unità disco identica prendendola
           dall'<quote>archivio</quote>.  Bill quindi installa la nuova versione
           di FreeBSD nella nuova unità SCSI zero usando i floppy FTP di
           Internet di Fred.  L'installazione ha successo.</para>
 
         <para>Fred usa la nuova versione di FreeBSD per alcuni giorni, e si
           convince che è sufficientemente buona per usarla nel
           dipartimento di ingegneria.  È ora di copiare tutto il suo
           lavoro della vecchia versione.  Fred monta la quarta unità SCSI
           (l'ultima copia della vecchia versione di FreeBSD).  Fred è
           costernato dal fatto che nulla del suo precedente lavoro è
           presente nella quarta unità SCSI.</para>
 
         <para>Dove sono andati i dati?</para>
 
         <para>Quando Bill ha fatto una copia dell'immagine dell'unità
           SCSI zero di origine sulla quarta unità SCSI, la quarta
           unità divenne un <quote>clone</quote>.  Quando Bill ha
           riordinato il BIOS SCSI affinchè si poteva effettuare il boot
           dalla quarta unità SCSI, ha solo ingannato se stesso.
           FreeBSD stava ancora girando sull'unità SCSI zero.
           Questo tipo di modifica al BIOS farà in modo che tutto il
           codice di boot e del loader sia prelevato dal dispositivo indicato
           nel BIOS, ma quando i driver del kernel di FreeBSD prendono il
           controllo, la numerazione dei dispositivi del BIOS sarà
           ignorata, e FreeBSD considererà la numerazione standard
           dei dispositivi.  Nel nostro esempio, il sistema ha continuato
           ad operare sull'unità SCSI zero originale, e tutti i dati
           di Fred erano lì, e non sulla quarta unità SCSI.
           Il fatto che il sistema sembrava in esecuzione sulla quarta
           unità SCSI era semplicemente un artificio delle aspettative
           umane.</para>
 
         <para>Siamo contenti di dire che nessun dato è stato cancellato
           o artefatto dalla scoperta di questo fenomeno.  L'unità zero
           SCSI utilizzata in precedenza è stata recuperata dalla
           pila di hard disk, ed è stato recuperato tutto il lavoro
           di Fred, (e ora Bill sa che puè contare anche sull'unità
           zero).</para>
 
         <para>Sebbene siano stati utilizzati dispositivi SCSI in questo esempio,
           lo stesso concetto si applica ai dispositivi IDE.</para>
       </sidebar>
     </sect2>
 
     <sect2 id="main-fdisk">
       <title>Come Creare le Slice con FDisk</title>
 
       <note>
         <para>Tutte le modifiche che fai ora non saranno scritte su disco.
           Se pensi di aver fatto un errore e vuoi ricominciare dall'inizio
           puoi usare il menù di <application>sysinstall</application>
           per uscire e tentare un'altra volta o premere il tasto
           <keycap>U</keycap> per usare l'opzione
           <guimenuitem>Undo</guimenuitem>.  Se sei confuso e non riesci
           a capire come uscire dall'applicazione puoi sempre riavviare il
           computer.</para>
       </note>
 
       <para>Dopo aver scelto un'installazione standard in
         <application>sysinstall</application> ti verrà mostrato
         questo messaggio:</para>
 
       <screen>                                 Message
  In the next menu, you will need to set up a DOS-style ("fdisk")
  partitioning scheme for your hard disk. If you simply wish to devote
  all disk space to FreeBSD (overwriting anything else that might be on
  the disk(s) selected) then use the (A)ll command to select the default
  partitioning scheme followed by a (Q)uit. If you wish to allocate only
  free space to FreeBSD, move to a partition marked "unused" and use the
  (C)reate command.
                                 [  OK  ]
 
                       [ Press enter or space ]</screen>
 
       <para>Premi <keycap>Invio</keycap> come segnalato.  Ti verrà
         mostrato un elenco di tutti gli hard disk che il kernel
         ha trovato quando ha effettuato il probe dei dispositivi.
         La <xref linkend="sysinstall-fdisk-drive1"/> mostra un esempio con un
         sistema con due dischi IDE.  Questi sono chiamati
         <devicename>ad0</devicename> e <devicename>ad2</devicename>.</para>
 
       <figure id="sysinstall-fdisk-drive1">
         <title>Come Selezionare il Dispositivo per FDisk</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/fdisk-drive1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Ti potresti chiedere perchè <devicename>ad1</devicename>
         non è elencato nella lista.  Perchè è stato
         omesso?</para>
 
       <para>Considera ciò che succederebbe se hai due hard disk IDE,
         uno come master sul primo controller IDE, ed uno come master sul
         secondo controller IDE.  Se FreeBSD li enumera come li trova,
         allora saranno <devicename>ad0</devicename> e
         <devicename>ad1</devicename>.</para>
 
       <para>Ma se vuoi aggiungere un terzo hard disk, come dispositivo
         slave sul primo controller IDE, allora questo sarà
         <devicename>ad1</devicename>, ed il precedente
         <devicename>ad1</devicename> diventerà
         <devicename>ad2</devicename>.  Poichè i nome dei dispositivi
         (come <devicename>ad1s1a</devicename>) sono usati per determinare i
         filesystem, potresti improvvisamente scoprire che alcuni dei tuoi
         filesystem non appaiono più correttamente, e avrai
         necesità di modificare la tua configurazione di FreeBSD.</para>
 
       <para>Per aggirare questo problema, il kernel può essere
         configurato per denominare i dischi IDE in base alla loro posizione,
         e non in base all'ordine di rilevamento degli stessi.  Con questo
         schema il disco master sul secondo controller IDE sarà
         <emphasis>sempre</emphasis> <devicename>ad2</devicename>,
         anche se non sono presenti i dispositivi
         <devicename>ad0</devicename> e <devicename>ad1</devicename>.</para>
 
       <para>Questa configurazione è di default per il kernel di
         FreeBSD, ed è per questo che il display visualizza
         <devicename>ad0</devicename> e <devicename>ad2</devicename>.
         La macchina sulla quale è stato preso questo screenshot aveva
         dischi IDE su entrambi i canali master dei controller IDE, e nessun
         disco sui canali slave.</para>
 
       <para>Dovresti selezionare il disco sul quale vuoi installare FreeBSD, poi
         premi &gui.ok;.  Verrà avviato <application>FDisk</application>,
         con una schermata simile a quella nella <xref
           linkend="sysinstall-fdisk1"/>.</para>
 
       <para>La schermata di <application>FDisk</application> è divisa in
         tre sezioni.</para>
 
       <para>La prima sezione, comprendente le prime due linee della schermata,
         mostra i dettagli dell'hard disk selezionato, includendo il nome
         di FreeBSD, la geometria del disco, e la sua capacità.</para>
 
       <para>La seconda sezione mostra le slice che sono attualmente sul disco,
         dove esse cominciano e dove finiscono, quanto sono grandi, il nome
         assegnato da FreeBSD, la loro descrizione ed il loro tipo.  Questo
         esempio mostra due piccole slice inutilizzate, che sono uno degli
         artefatti degli schemi di progetto del PC.  Mostra anche una grande
         slice <acronym>FAT</acronym>, che apparirà quasi certamente come
         <devicename>C:</devicename> in &ms-dos; / &windows;, ed una slice
         estesa, che può contenere altre lettere dei dispositivi per
         &ms-dos; / &windows;.</para>
 
       <para>La terza sezione mostra i comandi che sono disponibili in
         <application>FDisk</application>.</para>
 
       <figure id="sysinstall-fdisk1">
         <title>Partizioni Tipiche in Fdisk prima delle Modifiche</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/fdisk-edit1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Cosa farai ora dipende da come vuoi splittare il tuo disco.</para>
 
       <para>Se vuoi usare FreeBSD su tutto il tuo disco (cancellerai tutti
         gli altri dati su questo disco quando confermerai in
         <application>sysinstall</application> che vuoi continuare il processo di
         installazione) allora premi <keycap>A</keycap>, che corrisponde
         all'opzione <guimenuitem>Use Entire Disk</guimenuitem>.  Le slice
         esistenti saranno rimosse, e sostituite con una piccola area
         etichettata come <literal>unused</literal> (ancora, un artefatto
         della progettazione del disco del PC), e una grande slice per FreeBSD.
         Fatto questo, dovresti selezionare la slice di FreeBSD che hai appena
         creato usando i tasti freccia, e quindi premere <keycap>S</keycap>
         affinchè la slice sia avviabile.  La schermata avrà
         un aspetto del tutto simile alla <xref
           linkend="sysinstall-fdisk2"/>.  Nota la <literal>A</literal> nella
         colonna dei <literal>Flag</literal>, che indica che la slice è
         <emphasis>active</emphasis>, e verrà avviata al boot.</para>
 
       <para>Se vuoi cancellare una slice esistente per fare spazio a FreeBSD
         allora devi selezionare la slice con i tasti freccia, e quindi premere
         <keycap>D</keycap>.  Quindi premi <keycap>C</keycap>, e ti verrà
         chiesto la dimensione della slice che vuoi creare.  Scegli la
         dimensione appropriata e premi <keycap>Invio</keycap>.  Il valore
         predefinito in questo riquadro rappresenta la dimensione massima che
         la tua slice può avere, che potrebbe essere il blocco contiguo
         più lungo di spazio non ancora allocato oppure l'intero
         disco.</para>
 
       <para>Se hai già creato lo spazio per FreeBSD (magari usando un
         tool come <application>&partitionmagic;</application>) allora puoi
         premere <keycap>C</keycap> per creare una nuova slice.  Di nuovo,
         ti verrà chiesta la dimensione della slice che vorresti
         creare.</para>
 
       <figure id="sysinstall-fdisk2">
         <title>Partizionare con Fdisk Usando l'Intero Disco</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/fdisk-edit2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Quando hai finito, premi <keycap>Q</keycap>.  Le tue modifiche
         saranno salvate da <application>sysinstall</application>, ma non
         saranno ancora applicate al disco.</para>
     </sect2>
 
     <sect2 id="bootmgr">
       <title>Installare il Boot Manager</title>
 
       <para>Ora hai due scelte per installare il boot manager.  In generale,
         potresti installare il boot manager di FreeBSD se:</para>
 
       <itemizedlist>
         <listitem>
           <para>Hai più di un disco, ed hai installato FreeBSD su
             un disco diverso dal primo.</para>
         </listitem>
 
         <listitem>
           <para>Hai installato FreeBSD accanto ad un altro sistema operativo
             sullo stesso disco, e vorresti scegliere se avviare FreeBSD
             o l'altro sistema operativo quando accendi il computer.</para>
         </listitem>
       </itemizedlist>
 
       <para>Se FreeBSD è il solo sistema operativo sulla
         macchina, installato sul primo hard disk, allora il boot manager
         <guimenuitem>Standard</guimenuitem> sarà sufficiente.
         Scegli <guimenuitem>None</guimenuitem> se stai usando un boot manager
         di terze parti capace di avviare FreeBSD.</para>
 
       <para>Fai la tua scelta e premi <keycap>Invio</keycap>.</para>
 
       <figure id="sysinstall-bootmgr">
         <title>Il Menù di Sysinstall del Boot Manager</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/boot-mgr"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Per l'aiuto in linea, puoi premere <keycap>F1</keycap>, dove
         troverai informazioni sui problemi che potresti incontrare quando
         tenti di condividere un hard disk tra più sistemi
         operativi.</para>
     </sect2>
 
     <sect2>
       <title>Creare una Slice per un Altro Dispositivo</title>
 
       <para>Se hai più di un dispositivo, ritornerai alla schermata
         di Selezione dei Dispositivi dopo la scelta del boot manager.  Se
         desideri installare FreeBSD su più di un disco, a questo punto
         puoi selezionare un altro disco e ripetere la fase di partizionamento
         usando <application>FDisk</application>.</para>
 
       <important>
         <para>Se non stai installando FreeBSD sul primo dispositivo, allora
           il boot manager di FreeBSD deve essere installato su entrambi i
           dispositivi.</para>
       </important>
 
       <figure id="sysinstall-fdisk-drive2">
         <title>Uscire dalla Selezione dei Dischi</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/fdisk-drive2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Con <keycap>Tab</keycap> puoi saltare tra l'ultimo disco
         selezionato, &gui.ok;, e &gui.cancel;.</para>
 
       <para>Premi <keycap>Tab</keycap> una volta per selezionare &gui.ok;,
         quindi premi <keycap>Invio</keycap> per continuare
         l'installazione.</para>
     </sect2>
 
     <sect2 id="bsdlabeleditor">
       <title>Creare una Partizione Usando
         <application>Disklabel</application></title>
 
       <para>Ora devi creare alcune partizioni all'interno di ogni slice che hai
         appena creato.  Ricorda che ogni partizione è etichettata da
         lettere, dalla <literal>a</literal> fino alla <literal>h</literal>, e le
         partizioni <literal>b</literal>, <literal>c</literal>, e
         <literal>d</literal> hanno dei significati formali ai quali dovresti
         attenerti.</para>
 
       <para>Certe applicazioni possono trarre beneficio da alcuni schemi di
         partizioni particolari, soprattutto se le puoi collocare su più
         dischi.  Comunque, per la tua prima installazione di FreeBSD, non hai
         bisogno di dare troppo peso a come partizionare il disco.  È
         più importante che installi FreeBSD ed impari ad usarlo.  Puoi
         sempre reinstallare FreeBSD per cambiare il tuo schema delle partizioni
         quando avrai più familiarità con il sistema
         operativo.</para>
 
       <para>Questo schema caratterizza quattro partizioni &mdash;una per lo
         swap, e le altre tre per i filesystem.</para>
 
       <table frame="none" pgwide="1">
         <title>Schema di Partizionamento per il Primo Disco</title>
 
         <tgroup cols="4">
           <colspec colwidth="1*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="4*"/>
 
           <thead>
             <row>
               <entry>Partizione</entry>
 
               <entry>filesystem</entry>
 
               <entry>Dimensione</entry>
 
               <entry>Descrizione</entry>
             </row>
           </thead>
 
           <tbody>
             <row>
               <entry><literal>a</literal></entry>
 
               <entry><filename>/</filename></entry>
 
               <entry>100&nbsp;MB</entry>
 
               <entry>Questo è il filesystem root.  Ogni altro filesystem
                 sarà montato da qualche parte sotto di esso.  100&nbsp;MB
                 è una dimensione ragionevole per questo filesystem.
                 Non memorizzerai troppi dati su di esso, per un'installazione
                 regolare di FreeBSD ci saranno circa 40&nbsp;MB di dati.  Lo
                 spazio rimanente è per i dati temporanei, e lascia
                 anche una spazio di scorta nel caso in cui le versioni
                 future di FreeBSD dovessero richiedere più spazio
                 in <filename>/</filename>.</entry>
             </row>
 
             <row>
               <entry><literal>b</literal></entry>
 
               <entry>N/A</entry>
 
               <entry>2-3 x RAM</entry>
 
               <entry>Lo spazio di swap del sistema è su questa
                 partizione.  Scegliere la giusta quantità di swap
                 può non essere così semplice.  Una buona regola
                 è che il tuo spazio di swap dovrebbe essere due o tre
                 volte maggiore della tua memoria fisica (RAM).  Dovresti avere
                 almeno 64&nbsp;MB di swap, quindi se nel tuo computer hai meno
                 di 32&nbsp;MB di RAM allora setta lo swap a
                 64&nbsp;MB.  Se hai più di un disco puoi mettere lo
                 spazio swap su ogni disco.  FreeBSD userà ogni disco per
                 lo swap, velocizzando le azioni di swapping.  In questo caso,
                 calcola l'ammontare totale di swap di cui necessiti
                 (per esempio, 128&nbsp;MB), e quindi dividi questo numero per
                 il numero di dischi che hai (per esempio, due dischi) per
                 ottenere l'ammontare di spazio che dovresti settare su
                 ogni disco, in questo esempio, 64&nbsp;MB di swap per ogni
                 disco.</entry>
             </row>
 
             <row>
               <entry><literal>e</literal></entry>
 
               <entry><filename>/var</filename></entry>
 
               <entry>50&nbsp;MB</entry>
 
               <entry>La directory <filename>/var</filename> contiene dei file
                 che variano costantemente; i file di log, e gli altri file
                 di amministrazione.  Molti di questi file sono letti o scritti
                 frequentemente durante l'esecuzione giornaliera di FreeBSD.
                 Mettere questi file su un altro filesystem consente a FreeBSD di
                 ottimizzare l'accesso a questi file senza coinvolgere altri file
                 in altre directory che non hanno lo stesso tipo di
                 accesso.</entry>
             </row>
 
             <row>
               <entry><literal>f</literal></entry>
 
               <entry><filename>/usr</filename></entry>
 
               <entry>Il Resto del disco</entry>
 
               <entry>Tutti gli altri file saranno tipicamente memorizzati in
                 <filename>/usr</filename> e sotto le sue sotto
                 directory.</entry>
             </row>
           </tbody>
         </tgroup>
       </table>
 
       <para>Se installi FreeBSD su più dischi devi creare anche delle
         partizioni nelle altre slice che configuri.  La maniera più
         facile di fare questo è creare due partizioni su ogni disco, una
         per lo spazio di swap, ed una per il filesystem.</para>
 
       <table frame="none" pgwide="1">
         <title>Schema di Partizionamento per Dischi Successivi</title>
 
         <tgroup cols="4">
           <colspec colwidth="1*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="2*"/>
           <colspec colwidth="3*"/>
 
           <thead>
             <row>
               <entry>Partizione</entry>
 
               <entry>Filesystem</entry>
 
               <entry>Dimensione</entry>
 
               <entry>Descrizione</entry>
             </row>
           </thead>
 
           <tbody>
             <row>
               <entry><literal>b</literal></entry>
 
               <entry>N/A</entry>
 
               <entry>Guarda la descrizione</entry>
 
               <entry>Come già discusso, puoi dividere lo swap su ogni
                 disco.  Anche se la partizione <literal>a</literal> è
                 libera, per convenzione lo spazio swap sta nella
                 partizione <literal>b</literal>.</entry>
             </row>
 
             <row>
               <entry><literal>e</literal></entry>
 
               <entry>/disk<replaceable>n</replaceable></entry>
 
               <entry>Il resto del disco</entry>
 
               <entry>Il resto del disco è messo in una grande
                 partizione.  Questo potrebbe essere facilmente messo sulla
                 partizione <literal>a</literal>, invece della partizione
                 <literal>e</literal>.  Comunque, la convenzione dice che
                 la partizione <literal>a</literal> su una slice è
                 riservata per il filesystem root (<filename>/</filename>).
                 Non devi necessariamente seguire questa convenzione, ma
                 <application>sysinstall</application> lo fa, e quindi se segui
                 la convenzione avrai una installazione alla regola.
                 Puoi scegliere di montare questo filesystem dove vuoi; in questo
                 esempio si propone di montare i filesystem sotto le directory
                 <filename>/disk<replaceable>n</replaceable></filename>, dove
                 <replaceable>n</replaceable> è un numero che cambia per
                 ogni disco.  Ma puoi usare un altro schema se
                 preferisci.</entry>
             </row>
           </tbody>
         </tgroup>
       </table>
 
       <para>Avendo scelto il tuo schema di partizionamento lo puoi creare con
         <application>sysinstall</application>.  Vedrai questo messaggio:</para>
 
       <screen>                                 Message
  Now, you need to create BSD partitions inside of the fdisk
  partition(s) just created. If you have a reasonable amount of disk
  space (200MB or more) and don't have any special requirements, simply
  use the (A)uto command to allocate space automatically. If you have
  more specific needs or just don't care for the layout chosen by
  (A)uto, press F1 for more information on manual layout.
 
                                 [  OK  ]
                           [ Press enter or space ]</screen>
 
       <para>Premi <keycap>Invio</keycap> per avviare l'editor delle partizioni
         di FreeBSD, chiamato <application>Disklabel</application>.</para>
 
       <para>La <xref linkend="sysinstall-label"/> mostra la schermata quando
         avvii <application>Disklabel</application>.  Il display è diviso
         in tre sezioni.</para>
 
       <para>Le prime linee mostrano il nome del disco sul quale stai lavorando
         attualmente, e la slice che contiene le partizioni che stai creando
         (a questo punto <application>Disklabel</application> usa il termine
         <literal>Nome della Partizione</literal> piuttosto che nome della
         slice).  Questa schermata mostra anche la quantità di spazio
         libero nella slice; cioè lo spazio che è stato allocato
         per la slice, anche se ancora non è stato assegnato ad una
         partizione.</para>
 
       <para>Al centro della schermata sono mostrate le partizioni che sono
         state create, il nome del filesystem che ogni partizione contiene, la
         loro dimensione, ed alcune opzioni attinenti alla creazione del
         filesystem.</para>
 
       <para>La parte bassa dello schermo mostra le combinazioni di tasti valide
         in <application>Disklabel</application>.</para>
 
       <figure id="sysinstall-label">
         <title>Editor di Disklabel in Sysinstall</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/disklabel-ed1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para><application>Disklabel</application> può creare
         automaticamente le partizioni ed assegnare loro una dimensione di
         default.  Prova questa funzione premendo <keycap>A</keycap>.  Vedrai
         una schermata simile a quella mostrata in <xref
           linkend="sysinstall-label2"/>.  A seconda della dimensione del disco
         che stai usando, i valori di default potrebbero essere differenti.
         Questo non è fatale, poichè puoi anche non accettare
         i valori di default .</para>
 
       <note>
         <para>Il partizionamento di default
           predispone alla directory <filename>/tmp</filename> una propria
           partizione al posto di essere inclusa nella partizione
           <filename>/</filename>.  Questo evita il possibile riempimento
           della partizione <filename>/</filename> con i file
           temporanei.</para>
       </note>
 
       <figure id="sysinstall-label2">
         <title>L'Editor Disklabel di Sysinstall con i Valori di Default</title>
 
         <mediaobject>
           <imageobject>
           <imagedata fileref="install/disklabel-auto"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Se scegli di non usare le partizioni di default e desideri
         sostituirle con quelle che vuoi tu, usa i tasti freccia per selezionare
         la prima partizione, e premi <keycap>D</keycap> per cancellarla.  Ripeti
         questa operazione per cancellare tutte le partizioni che ritieni
         opportune.</para>
 
       <para>Per creare la prima partizione (<literal>a</literal>, montata come
         <filename>/</filename> &mdash; root), assicurati che sia selezionata
         in cima allo schermo la slice corretta e premi <keycap>C</keycap>.
         Apparirà una finestra di dialogo per inserire la dimensione
         della nuova partizione (come mostrato nella <xref
           linkend="sysinstall-label-add"/>).  Puoi immettere la dimensione
         come il numero di blocchi del disco che vuoi usare, o come un numero
         seguito da <literal>M</literal> per megabyte, da <literal>G</literal>
         per gigabyte, da <literal>C</literal> per cilindri.</para>
 
       <note>
         <para>A partire da FreeBSD&nbsp;5.X, gli utenti possono: selezionare
           <acronym>UFS2</acronym> (che è di default per &os;&nbsp;5.1 e
           superiori) usando l'opzione <literal>Custom Newfs</literal>
           (<keycap>Z</keycap>), creare le etichette con
           <literal>Auto Defaults</literal> e modificarle con l'opzione
           <literal>Custom Newfs</literal> oppure aggiungendo
           <option>-O 2</option> durante la normale fase di creazione.
           Non dimenticare di aggiungere <option>-U</option> per
           SoftUpDate se vuoi usare l'opzione
           <literal>Custom Newfs</literal></para>
       </note>
 
       <figure id="sysinstall-label-add">
         <title>Spazio per la Partizione Root</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/disklabel-root1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>La grandezza di default mostrata creerà una partizione
         che prende il resto della slice.  Se stai usando le dimensioni di
         partizioni usate nell'esempio precedente, allora cancella la figura
         esistente usando <keycap>Backspace</keycap>, e poi digita
         <userinput>64M</userinput>, come è mostrato in
         <xref linkend="sysinstall-label-add2"/>.  Poi premi
         &gui.ok;.</para>
 
       <figure id="sysinstall-label-add2">
         <title>Modifica della Dimensione della Partizione di Root</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/disklabel-root2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Dopo aver scelto la dimensione della partizione ti verrà
         chiesto se la partizione conterrà una filesystem o uno spazio
         di swap.  La finestra di dialogo è mostrata nella <xref
           linkend="sysinstall-label-type"/>.  La prima partizione
         conterrà un filesystem, quindi assicurati che sia selezionato
         <guimenuitem>FS</guimenuitem> e premi <keycap>Invio</keycap>.</para>
 
       <figure id="sysinstall-label-type">
         <title>Scelta del Tipo della Partizione Root</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/disklabel-fs"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Alla fine, poichè stai creando un filesystem, devi dire a
         <application>Disklabel</application> dove sarà montato il
         filesystem.  La finestra di dialogo è mostrata nella
         <xref linkend="sysinstall-label-mount"/>.  Il punto di mount del
         filesystem root è <filename>/</filename>, dunque digita
         <userinput>/</userinput>, e poi premi <keycap>Invio</keycap>.</para>
 
       <figure id="sysinstall-label-mount">
         <title>Scelta del Punto di Mount della Root</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/disklabel-root3"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Lo schermo sarà aggiornato e ti mostrerà la partizione
         appena creata.  Devi ripete questa procedura per le altre partizioni.
         Quando crei la partizione di swap, non ti verrà richiesto di
         inserire il punto di mount del filesystem, poichè le partizioni
         di swap non sono mai montate.  Quando crei l'ultima partizione,
         <filename>/usr</filename>, puoi lasciare la dimensione suggerita,
         per usare il rimanente spazio della slice.</para>
 
       <para>La schermata finale dell'Editor DiskLabel di FreeBSD sarà
         simile alla <xref linkend="sysinstall-label4"/>, sebbene i valori scelti
         potrebbero essere differenti.  Premi <keycap>Q</keycap> per
         finire.</para>
 
       <figure id="sysinstall-label4">
         <title>L'Editor Disklabel di Sysinstall</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/disklabel-ed2"/>
           </imageobject>
         </mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 id="install-choosing">
     <title>Scegliere Cosa Installare</title>
 
     <sect2 id="distset">
       <title>Scegliere il Tipo di Distribuzione</title>
 
       <para>Scegliere quale tipo di distribuzione installare dipenderà
         in maggior parte dall'uso del sistema e di quanto spazio hai
         disponibile.  Le opzioni predefinite spaziano da installare la
         configurazione più leggera possibile fino ad arrivare ad
         installare ogni cosa.  Quelli che sono nuovi di &unix; e/o
         di FreeBSD dovrebbero quasi certamente selezionare una di queste
         opzioni inscatolate.  La personalizzazione di un tipo di distribuzione
         è roba da utenti un pò più esperti.</para>
 
       <para>Premi <keycap>F1</keycap> per avere più informazioni
         sulle opzioni del tipo di distribuzione e ciò che contengono.
         Quando hai finito con l'help, premendo <keycap>Invio</keycap>
         ritornerai al Menu di Selezione della Distribuzione.</para>
 
       <para>Se desideri un'interfaccia grafica allora dovresti scegliere un
         tipo di distribuzione preceduto da una <literal>X</literal>.  La
         configurazione del server X e la selezione di un desktop di default
         deve essere fatta dopo l'installazione di &os;.  Maggiori informazioni
         riguardo la configurazione di un server X possono essere trovate
         nel <xref linkend="x11"/>.</para>
 
       <para>La versione di default di X11 che viene installata dipende dalla
         versione di FreeBSD che stai installando.  Per le versioni di FreeBSD
         precedenti alla 5.3, viene installato
         <application>&xfree86; 4.X</application>.  Per &os;&nbsp;5.3 e
         successive, viene installato di default
         <application>&xorg;</application>.</para>
 
       <para>Se pensi di compilare un kernel custom, seleziona un'opzione che
         include il codice sorgente.  Per altre informazioni sul perchè
         dovrebbe essere costruito un kernel custom o su come costruirlo, guarda
         il <xref linkend="kernelconfig"/>.</para>
 
       <para>Ovviamente, il sistema più versatile è quello che
         include tutto.  Se c'è abbastanza spazio su disco, seleziona
         <guimenuitem>All</guimenuitem> come mostrato nella
         <xref linkend="distribution-set1"/> usando i tasti freccia e premi
         <keycap>Invio</keycap>.  Se hai qualche preoccupazione per lo spazio
         di disco usa un'opzione che ti è più conveniente
         per la tua situazione.  Non cercare la scelta perfetta,
         poichè potrai aggiungere altre distribuzioni anche dopo
         l'installazione.</para>
 
       <figure id="distribution-set1">
         <title>Scegliere le Distribuzioni</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/dist-set"/>
           </imageobject>
         </mediaobject>
       </figure>
     </sect2>
 
     <sect2 id="portscol">
       <title>Installare la Collezione dei Port</title>
 
       <para>Dopo aver selezionato la distribuzione desiderata, ti viene data
         l'opportunità di installare la FreeBSD Port Collection.
         La collezione dei port è un modo semplice e conveniente di
         installare software.  La collezione dei port non contiene il codice
         sorgente necessario per compilare il software.  Invece, è
         una collezione di file che automatizza il download, la compilazione e
         l'installazione delle applicazioni di terze-parti.  Il
         <xref linkend="ports"/> discute su come usare la collezione dei
         port.</para>
 
       <para>Il programma di installazione non verifica se hai lo spazio
         adeguato.  Scegli questa opzione soltanto se hai uno spazio sul disco
         rigido sufficiente.  Per FreeBSD &rel.current;, la FreeBSD
         Ports Collection occupa circa  &ports.size; di spazio su disco.
         Puoi assumere un valore più grande per le versioni di FreeBSD
         più recenti.</para>
 
       <screen>                         User Confirmation Requested
  Would you like to install the FreeBSD ports collection?
 
  This will give you ready access to over &os.numports; ported software packages,
  at a cost of around &ports.size; of disk space when "clean" and possibly much
  more than that if a lot of the distribution tarballs are loaded
  (unless you have the extra CDs from a FreeBSD CD/DVD distribution
  available and can mount it on /cdrom, in which case this is far less
  of a problem).
 
  The ports collection is a very valuable resource and well worth having
  on your /usr partition, so it is advisable to say Yes to this option.
 
  For more information on the ports collection &amp; the latest ports,
  visit:
      http://www.FreeBSD.org/ports
 
                               [ Yes ]     No</screen>
 
       <para>Seleziona &gui.yes; con i tasti freccia per installare la
         collezione dei port, oppure &gui.no; per saltare questa opzione.
         Premi <keycap>Invio</keycap> per continuare.
         Verrà visualizzato il menu della scelta della
         distribuzione.</para>
 
       <figure id="distribution-set2">
         <title>Conferma della Distribuzione</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/dist-set2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Se sei soddisfatto delle opzioni, seleziona
         <guimenuitem>Exit</guimenuitem> con i tasti freccia, assicurati che
         &gui.ok; sia selezionato, quindi premi <keycap>Invio</keycap> per
         continuare.</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-media">
     <title>Scegli il Tuo Media di Installazione</title>
 
     <para>Se vuoi installare da CDROM o da DVD, usa i tasti freccia per
       evidenziare <guimenuitem>Install from a FreeBSD CD/DVD</guimenuitem>.
       Assicurati che &gui.ok; sia evidenziato, e poi premi
       <keycap>Invio</keycap> per procedere con l'installazione.</para>
 
     <para>Per gli altri metodi di installazione, scegli l'opzione
       appropriata e segui le istruzioni.</para>
 
     <para>Premi <keycap>F1</keycap> per visualizzare l'help in linea sui media
       di installazione.  Premi <keycap>Invio</keycap> per tornare
       al menù di selezione dei media.</para>
 
     <figure id="choose-media">
       <title>Scelta del Media di Installazione</title>
 
       <mediaobject>
         <imageobject>
           <imagedata fileref="install/media"/>
         </imageobject>
       </mediaobject>
     </figure>
 
     <note>
       <title>Modi di Installazione via FTP</title>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>network</secondary>
         <tertiary>FTP</tertiary>
       </indexterm>
 
       <para>Ci sono tre modi di installazione via FTP che puoi scegliere:
         FTP attivo, FTP passivo, o via un proxy HTTP.</para>
 
       <variablelist>
         <varlistentry>
           <term>FTP Attivo: <guimenuitem>Install from an FTP
               server</guimenuitem></term>
 
           <listitem>
             <para>Questa opzione farà tutti i trasferimenti FTP usando
               la modalità <quote>Attiva</quote>.  Questa modalità
               non funzionerà attraverso i firewall, ma funzionerà
               con server FTP vecchi che non supportano la modalità
               passiva.  Se la tua connessione ha problemi con la modalità
               passiva (il default), prova quella attiva!</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>FTP Passivo: <guimenuitem>Install from an FTP server through a
               firewall</guimenuitem></term>
 
           <listitem>
             <indexterm>
               <primary>FTP</primary>
               <secondary>modalità passivo</secondary>
             </indexterm>
 
             <para>Questa opzione istruisce <application>sysinstall</application>
               ad usare la modalità <quote>Passiva</quote> per tutte le
               operazioni FTP.  Questo consente all'utente di passare attraverso
               firewall che non permettono connessioni in entrate su porte TCP
               random.</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>FTP tramite un proxy HTTP: <guimenuitem>Install from an FTP
               server through a http proxy</guimenuitem></term>
 
           <listitem>
             <indexterm>
               <primary>FTP</primary>
               <secondary>tramite proxy HTTP</secondary>
             </indexterm>
 
             <para>Questa opzione istruisce <application>sysinstall</application>
               a usare il protocollo HTTP (come un browser web) per connettersi
               a un proxy per tutte le operazioni FTP.  Il proxy
               tradurrà le richieste e invierà loro al server FTP.
               Questo permette all'utente di passare attraverso i firewall
               che non permettono FTP del tutto, ma offrono un proxy HTTP.
               In questo caso, devi specificare il proxy oltre al server
               FTP.</para>
           </listitem>
         </varlistentry>
       </variablelist>
 
       <para>Per un proxy FTP server, dovresti di solito dare il nome del server
         che realmente vuoi come parte del nome utente, seguito dal carattere
         <quote>@</quote>.  Il server proxy quindi <quote>raggira</quote>
         il server reale.  Per esempio, assumiamo che vuoi installare
         da <hostid role="fqdn">ftp.FreeBSD.org</hostid>, usando il server
         proxy FTP <hostid role="fqdn">foo.example.com</hostid>, in ascolto
         sulla porta 1024.</para>
 
       <para>In questo caso, vai alle opzioni del menù, setta il
         nome utente FTP come <literal>ftp@ftp.FreeBSD.org</literal>, e il tuo
         indirizzo email come password.  Come media di installazione,
         specifica FTP (o FTP passivo, se il proxy lo supporta), e l'URL
         <literal>ftp://foo.example.com:1234/pub/FreeBSD</literal>.</para>
 
       <para>Poichè <filename>/pub/FreeBSD</filename> da
         <hostid role="fqdn">ftp.FreeBSD.org</hostid> è proxato sotto
         <hostid role="fqdn">foo.example.com</hostid>, sei in grado di
         installare da <emphasis>questa</emphasis> macchina (che prenderà
         i file da <hostid role="fqdn">ftp.FreeBSD.org</hostid> richiesti
         dall'installazione).</para>
     </note>
   </sect1>
 
   <sect1 id="install-final-warning">
     <title>Procedere con l'Installazione</title>
 
     <para>Se lo desideri l'installazione può ora procedere.  Questa
       è anche l'ultima opportunità per interrompere
       l'installazione per impedire cambiamenti al disco.</para>
 
     <screen>                       User Confirmation Requested
  Last Chance! Are you SURE you want to continue the installation?
 
  If you're running this on a disk with data you wish to save then WE
  STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding!
 
  We can take no responsibility for lost disk contents!
 
                              [ Yes ]    No</screen>
 
     <para>Seleziona &gui.yes; e premi <keycap>Invio</keycap> per
       procedere.</para>
 
     <para>Il tempo di installazione varierà a seconda della
       distribuzione che hai scelto, dei media di installazione, e della
       velocità del computer.  Verranno visualizzati una serie di
       messaggi indicanti lo stato.</para>
 
     <para>L'installazione è completa quando viene visualizzato
       il seguente messaggio:</para>
 
     <screen>                               Message
 
 Congratulations! You now have FreeBSD installed on your system.
 
 We will now move on to the final configuration questions.
 For any option you do not wish to configure, simply select No.
 
 If you wish to re-enter this utility after the system is up, you may
 do so by typing: /stand/sysinstall .
 
                                  [ OK ]
 
                       [  Press enter to continue  ]</screen>
 
     <para>Premi <keycap>Invio</keycap> per procedere con la configurazione
       post-installazione.</para>
 
     <para>Seleziona &gui.no; e premi <keycap>Invio</keycap> per interrompere
       l'installazione in modo tale che nessuna modifica venga effettuata sul tuo
       sistema.  Apparirà il seguente messaggio</para>
 
     <screen>                                Message
 Installation complete with some errors.  You may wish to scroll
 through the debugging messages on VTY1 with the scroll-lock feature.
 You can also choose "No" at the next prompt and go back into the
 installation menus to retry whichever operations have failed.
 
                                  [ OK ]</screen>
 
     <para>Questo messaggio viene visualizzato quando non installi nulla.
       Premi <keycap>Invio</keycap> per ritornare al menù di
       installazione principale per uscire dall'installazione.</para>
   </sect1>
 
   <sect1 id="install-post">
     <title>Post-installazione</title>
 
     <para>Dopo una corretta installazione segue la configurazione di varie
       opzioni.  Un'opzione può essere configurata rientrando nelle
       opzioni di configurazione prima dell'avvio del nuovo sistema
       FreeBSD o dopo l'installazione usando <command>sysinstall</command>
       (<command>/stand/sysinstall</command> nelle versioni di &os; prima
       della 5.2) e selezionando <guimenuitem>Configure</guimenuitem>.</para>
 
     <sect2 id="inst-network-dev">
       <title>Configurazione del Dispositivo di Rete</title>
 
       <para>Se hai configurato precedentemente PPP per l'installazione FTP,
         questa schermata non sarà visualizzata ora ma puoi configurarlo
         più avanti come descritto sotto.</para>
 
       <para>Per informazioni dettagliate riguardo alla LAN e alla configurazione
         di FreeBSD come gateway/router fai riferimento al capitolo
         <link linkend="advanced-networking">Networking Avanzato</link>.</para>
 
       <screen>                      User Confirmation Requested
    Would you like to configure any Ethernet or SLIP/PPP network devices?
 
                              [ Yes ]   No</screen>
 
       <para>Per configurare un dispositivo di rete, seleziona &gui.yes; e
         premi <keycap>Invio</keycap>.  Altrimenti, seleziona &gui.no;
         per continuare.</para>
 
       <figure id="ed-config1">
         <title>Selezione del Dispositivo Ethernet</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/ed0-conf"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Seleziona con i tasti freccia l'interfaccia che deve essere
         configurata e premi <keycap>Invio</keycap>.</para>
 
       <screen>                      User Confirmation Requested
        Do you want to try IPv6 configuration of the interface?
 
                               Yes   [ No ]</screen>
 
       <para>In questa LAN privata, il corrente protocollo di Internet
         (<acronym>IPv4</acronym>) era già sufficiente e è
         stato selezionato &gui.no; con i tasti freccia ed è stato premuto
         <keycap>Invio</keycap>.</para>
 
       <para>Se sei connesso ad una rete <acronym>IPv6</acronym> già
         esistente con un server <acronym>RA</acronym>, puoi selezionare
         &gui.yes; e premere <keycap>Invio</keycap>.  Lo scan dei server RA
         impiegherà un pò di secondi.</para>
 
       <screen>                             User Confirmation Requested
         Do you want to try DHCP configuration of the interface?
 
                               Yes   [ No ]</screen>
 
       <para>Se il DHCP (Dynamic Host Configuration Protocol) non è usato
         seleziona &gui.no; con i tasti freccia e premi
         <keycap>Invio</keycap>.</para>
 
       <para>Selezionando &gui.yes; si avvierà
         <application>dhclient</application>, e se tutto va bene, setterà
         in automatico le informazioni sulla configurazione della rete.
         Fai riferimento alla <xref linkend="network-dhcp"/> per altre
         informazioni.</para>
 
       <para>La seguente schermata di configurazione della rete mostra la
         configurazione di un dispositivo Ethernet per un sistema
         che funzionerà da gateway per una LAN.</para>
 
       <figure id="ed-config2">
         <title>Settare la Configurazione di Rete per ed0</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/ed0-conf2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Usa il <keycap>Tab</keycap> per selezionare i campi e riempili
         con le giuste informazioni:</para>
 
       <variablelist>
         <varlistentry>
           <term>Host</term>
 
           <listitem>
             <para>Il nome host assoluto, come
               <hostid role="fqdn">k6-2.example.com</hostid> in questo
               caso.</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Domain</term>
 
           <listitem>
             <para>Il nome del dominio nel quale si trova la tua macchina, come
               <hostid role="domainname">example.com</hostid> in questo
               caso.</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>IPv4 Gateway</term>
 
           <listitem>
             <para>L'indirizzo IP dell'host che inoltra i pacchetti verso
               destinazioni non locali.  Devi settarlo se la tua macchina
               è un nodo di una rete.
               <emphasis>Lascia questo campo vuoto</emphasis> se la
               macchina è il gateway di Internet per la rete.  Il
               gateway IPv4 è anche conosciuto come il gateway di
               default o l'instradamento di default.</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Name server</term>
 
           <listitem>
             <para>L'indirizzo IP del tuo server DNS locale.  Su questa lan
               privata non c'è un server DNS locale quindi è
               stato usato l'indirizzo IP del server DNS del provider
               (<hostid role="ipaddr">208.163.10.2</hostid>).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>IPv4 address</term>
 
           <listitem>
             <para>L'indirizzo IP in uso su questa interfaccia è
               <hostid role="ipaddr">192.168.0.1</hostid></para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Netmask</term>
 
           <listitem>
             <para>Il blocco di indirizzi in uso per questa lan è un
               blocco di classe C (<hostid role="ipaddr">192.168.0.0</hostid> -
               <hostid role="ipaddr">192.168.255.255</hostid>).
               La netmask di default per una rete di classe C è
               (<hostid role="netmask">255.255.255.0</hostid>).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Extra options to ifconfig</term>
 
           <listitem>
             <para>Altre opzioni di <command>ifconfig</command> per l'interfaccia
               di rete che potresti voler aggiungere.  In questo caso
               nessuna.</para>
           </listitem>
         </varlistentry>
       </variablelist>
 
       <para>Usa il <keycap>Tab</keycap> per selezionare &gui.ok;
         quando hai finito e poi premi <keycap>Invio</keycap>.</para>
 
 
       <screen>                      User Confirmation Requested
         Would you like to Bring Up the ed0 interface right now?
 
                              [ Yes ]   No</screen>
 
       <para>Selezionando &gui.yes; e premendo <keycap>Invio</keycap>
         si porterà la macchina all'interno della rete pronta per l'uso.
         Comunque, questo non è fondamentale durante l'installazione,
         poichè la macchina deve essere riavviata.</para>
     </sect2>
 
     <sect2 id="gateway">
       <title>Configurare Il Gateway</title>
 
       <screen>                       User Confirmation Requested
        Do you want this machine to function as a network gateway?
 
                               [ Yes ]    No</screen>
 
       <para>Se la macchina dovrà essere utilizzata come gateway per una
         LAN inoltrando pacchetti tra altre macchine allora seleziona
         &gui.yes; e premi <keycap>Invio</keycap>.  Se la macchina è un
         nodo di una rete allora seleziona &gui.no; e premi
         <keycap>Invio</keycap> per continuare.</para>
     </sect2>
 
     <sect2 id="inetd-services">
       <title>Configurare I Servizi di Internet</title>
 
       <screen>                      User Confirmation Requested
 Do you want to configure inetd and the network services that it provides?
 
                                Yes   [ No ]</screen>
 
       <para>Se selezioni &gui.no;, diversi servizi tipo
         <application>telnetd</application> non saranno avviati.  Questo
         significa che gli utenti remoti non saranno in grado di
         fare una sessione <application>telnet</application> su questa
         macchina.  Gli utenti locali saranno tuttavia in grado di
         accedere alla macchina con <application>telnet</application>.</para>
 
       <para>Questi servizi possono essere avviati dopo l'installazione
         editando <filename>/etc/inetd.conf</filename> con l'editor di testo che
         preferisci.  Leggi la <xref linkend="network-inetd-overview"/> per
         più informazioni.</para>
 
       <para>Seleziona &gui.yes; se desideri configurare questi servizi durante
         l'installazione.  Ti verrà proposta un'ulteriore
         conferma:</para>
 
       <screen>                      User Confirmation Requested
 The Internet Super Server (inetd) allows a number of simple Internet
 services to be enabled, including finger, ftp and telnetd.  Enabling
 these services may increase risk of security problems by increasing
 the exposure of your system.
 
 With this in mind, do you wish to enable inetd?
 
                              [ Yes ]   No</screen>
 
       <para>Seleziona &gui.yes; per continuare.</para>
 
       <screen>                      User Confirmation Requested
 inetd(8) relies on its configuration file, /etc/inetd.conf, to determine
 which of its Internet services will be available.  The default FreeBSD
 inetd.conf(5) leaves all services disabled by default, so they must be
 specifically enabled in the configuration file before they will
 function, even once inetd(8) is enabled.  Note that services for
 IPv6 must be separately enabled from IPv4 services.
 
 Select [Yes] now to invoke an editor on /etc/inetd.conf, or [No] to
 use the current settings.
 
                              [ Yes ]   No</screen>
 
       <para>Scegliendo &gui.yes; ti sarà consentito aggiungere
         servizi eliminando <literal>#</literal> all'inizio delle relative
         linee.</para>
 
       <figure id="inetd-edit">
         <title>Editare <filename>inetd.conf</filename></title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/edit-inetd-conf"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Dopo che hai aggiunto i servizi desiderati, premendo
         <keycap>Esc</keycap> ti verrà mostrato un menù che
         ti consente di uscire salvando i cambiamenti che hai
         apportato.</para>
     </sect2>
 
     <sect2 id="ftpanon">
       <title>FTP Anonimo</title>
 
       <indexterm>
         <primary>FTP</primary>
         <secondary>anonimo</secondary>
       </indexterm>
 
       <screen>                      User Confirmation Requested
  Do you want to have anonymous FTP access to this machine?
 
                               Yes    [ No ]</screen>
 
       <sect3 id="deny-anon">
         <title>Negare l'FTP Anonimo</title>
 
         <para>Selezionando &gui.no; e premendo <keycap>Invio</keycap>
           consentirai a chi ha un account con password di usare l'FTP
           per accedere alla macchina.</para>
       </sect3>
 
       <sect3 id="ftpallow">
         <title>Consentire l'FTP anonimo</title>
 
         <para>Chiunque può accedere alla tua macchina se
           permetti connessioni FTP anonime.  Dovrebbero essere considerate
           alcune implicazioni di sicurezza prima di abilitare questa opzione.
           Per altre informazioni sulla sicurezza guarda il
           <xref linkend="security"/>.</para>
 
         <para>Per consentire l'FTP anonimo, usa i tasti freccia e seleziona
           &gui.yes; e premi <keycap>Invio</keycap>.
           Ti verrà visualizzato il seguente messaggio:</para>
 
         <figure id="anon-ftp2">
           <title>Configurazione FTP Anonima di default</title>
 
           <mediaobject>
             <imageobject>
               <imagedata fileref="install/ftp-anon1"/>
             </imageobject>
           </mediaobject>
         </figure>
 
         <para>Premendo <keycap>F1</keycap> visualizzerai l'help in linea:</para>
 
         <screen>This screen allows you to configure the anonymous FTP user.
 
 The following configuration values are editable:
 
 UID:     The user ID you wish to assign to the anonymous FTP user.
          All files uploaded will be owned by this ID.
 
 Group:   Which group you wish the anonymous FTP user to be in.
 
 Comment: String describing this user in /etc/passwd
 
 
 FTP Root Directory:
 
         Where files available for anonymous FTP will be kept.
 
 Upload subdirectory:
 
         Where files uploaded by anonymous FTP users will go.</screen>
 
         <para>Di default la directory root dell'ftp sarà
           <filename>/var</filename>.  Se prevedi che lo spazio FTP non sia
           sufficiente, potresti usare la directory <filename>/usr</filename>
           settando la directory root dell'FTP a
           <filename>/usr/ftp</filename>.</para>
 
         <para>Quando sei soddisfatto delle modifiche, premi
           <keycap>Invio</keycap> per continuare.</para>
 
         <screen>                          User Confirmation Requested
          Create a welcome message file for anonymous FTP users?
 
                               [ Yes ]    No</screen>
 
         <para>Se selezioni &gui.yes; e premi <keycap>Invio</keycap>,
           verrà avviato un editor che ti permetterà di
           modificare il messaggio di benvenuto.</para>
 
         <figure id="anon-ftp4">
           <title>Editare il Messaggio di Benvenuto dell'FTP</title>
 
           <mediaobject>
             <imageobject>
               <imagedata fileref="install/ftp-anon2"/>
             </imageobject>
           </mediaobject>
         </figure>
 
         <para>L'editor è <command>ee</command>.
           Usa le istruzioni per cambiare il messaggio oppure cambia
           il messaggio più tardi usando un editor di testo a tua scelta.
           Nota il nome/locazione del file in fondo alla schermata
           dell'editor.</para>
 
         <para>Premendo <keycap>Esc</keycap> un menù pop-up ti
           sceglierà di default
           <guimenuitem>a) leave editor</guimenuitem>.
           Premi <keycap>Invio</keycap> per uscire e continuare.  Premi
           di nuovo <keycap>Invio</keycap> per salvare gli eventuali
           cambiamenti.</para>
       </sect3>
     </sect2>
 
     <sect2 id="nfsconf">
       <title>Configurare NFS (Network File System)</title>
 
       <para>NFS (Network File System) consente la condivisione di file
         attraverso una rete.  Una macchina può essere configurata come
         server, client, o entrambi.  Fai riferimento alla
         <xref linkend="network-nfs"/> per altre informazioni.</para>
 
       <sect3 id="nsf-server-options">
         <title>Server NFS</title>
 
         <screen>                       User Confirmation Requested
  Do you want to configure this machine as an NFS server?
 
                               Yes    [ No ]</screen>
 
         <para>Se non c'è bisogno di un server NFS, seleziona &gui.no;
           e premi <keycap>Invio</keycap>.</para>
 
         <para>Se scegli &gui.yes;, ti apparirà un messaggio che dice che
           il file <filename>exports</filename> deve essere creato.</para>
 
         <screen>                               Message
 Operating as an NFS server means that you must first configure an
 /etc/exports file to indicate which hosts are allowed certain kinds of
 access to your local filesystems.
 Press [Enter] now to invoke an editor on /etc/exports
                                [ OK ]</screen>
 
         <para>Premi <keycap>Invio</keycap> per continuare.  Verrà
           avviato un editor di testo al fine di creare ed editare il file
           <filename>exports</filename>.</para>
 
         <figure id="nfs-server-edit">
           <title>Editare <filename>exports</filename></title>
 
           <mediaobject>
             <imageobject>
               <imagedata fileref="install/nfs-server-edit"/>
             </imageobject>
           </mediaobject>
         </figure>
 
         <para>Usa le istruzione per aggiungere i filesystem che desideri
           esportare oppure fallo dopo l'installazione con il tuo editor
           preferito.  Nota il nome/locazione del file in fondo alla schermata
           dell'editor.</para>
 
         <para>Premi <keycap>Invio</keycap> e ti verrà mostrato un
           menù con selezionato
           <guimenuitem>a) leave editor</guimenuitem>.  Premi
           <keycap>Invio</keycap> per uscire e continuare.</para>
       </sect3>
 
       <sect3 id="nfs-client-options">
         <title>Client NFS</title>
 
         <para>Il client NFS consente alla tua macchina di accedere ai server
           NFS.</para>
 
         <screen>                       User Confirmation Requested
  Do you want to configure this machine as an NFS client?
 
                               Yes   [ No ]</screen>
 
         <para>Con i tasti freccia, seleziona &gui.yes; o &gui.no; come
           desiderato e premi <keycap>Invio</keycap>.</para>
       </sect3>
     </sect2>
 
     <sect2 id="securityprofile">
       <title>Profilo della Sicurezza</title>
 
       <para>Un <quote>profilo della sicurezza</quote> è un insieme
         di opzioni di configurazione che tentano di raggiungere il desiderato
         rapporto sicurezza/convenienza abilitando o disabilitando certi
         programmi e settaggi.  Con il profilo di sicurezza più severo,
         pochi programmi saranno abilitati di default.  Questo è
         uno dei principi basi per la sicurezza: non mandare in esecuzione nulla
         se non quello che usi.</para>
 
       <para>Per cortesia nota che il profilo di sicurezza è
         giusto una configurazione di default.  Tutti i programmi possono
         essere abilitati o disabilitati dopo che hai installato FreeBSD
         modificando o aggiungendo le appropriate linee in
         <filename>/etc/rc.conf</filename>.  Per altre informazioni,
         consulta la magina man &man.rc.conf.5;.</para>
 
       <para>La seguente tabella descrive la configurazione di ogni profilo di
         sicurezza.  Le colonne sono i profili di sicurezza che puoi scegliere,
         e le righe sono i programmi o le caratteristiche che il rispettivo
         profilo abilita o disabilita.</para>
 
       <table>
         <title>Profili di sicurezza disponibili</title>
 
         <tgroup cols="3">
           <thead>
             <row>
               <entry></entry>
 
               <entry>Extreme</entry>
 
               <entry>Moderate</entry>
             </row>
           </thead>
 
           <tbody>
             <row>
               <entry>&man.sendmail.8;</entry>
 
               <entry>NO</entry>
 
               <entry>SI</entry>
             </row>
 
             <row>
               <entry>&man.sshd.8;</entry>
 
               <entry>NO</entry>
 
               <entry>SI</entry>
             </row>
 
             <row>
               <entry>&man.portmap.8;</entry>
 
               <entry>NO</entry>
 
-              <entry>FORSE
-                <footnote>
-                  <para>Il portmapper è abilitato se la macchina è
+              <entry>FORSE (Il portmapper è abilitato se la macchina è
                     stata configurata in precedenza come un client o server
-                    NFS.</para>
-                </footnote>
+                    NFS.)
               </entry>
             </row>
 
             <row>
               <entry>NFS server</entry>
 
               <entry>NO</entry>
 
               <entry>SI</entry>
             </row>
 
             <row>
               <entry>&man.securelevel.8;</entry>
 
-              <entry>YES
-                <footnote>
-                  <para>Se hai scelto un profilo di sicurezza che regola
+              <entry>YES (Se hai scelto un profilo di sicurezza che regola
                     il securelevel a <quote>Extreme</quote> o
                     <quote>High</quote>, devi essere consapevole delle
                     implicazioni.  Per favore leggi prima la pagina man
                     &man.init.8; e poni particolare attenzione al significato
                     dei livelli di sicurezza, o potresti incontrare grossi
-                    problemi in seguito!</para>
-                </footnote>
+                    problemi in seguito!)
               </entry>
 
               <entry>NO</entry>
             </row>
           </tbody>
         </tgroup>
       </table>
 
       <screen>                       User Confirmation Requested
  Do you want to select a default security profile for this host (select
  No for "medium" security)?
 
                             [ Yes ]    No</screen>
 
       <para>Selezionando &gui.no; e premendo <keycap>Invio</keycap> setterai
         il profilo di sicurezza su medio.</para>
 
       <para>Selezionando &gui.yes; e premendo <keycap>Invio</keycap> ti
         sarà consentito selezionare un diverso profilo di
         sicurezza.</para>
 
       <figure id="security-profile">
         <title>Opzioni del Profilo di Sicurezza</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/security"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Premi <keycap>F1</keycap> per visualizzare l'help in linea.
         Premi <keycap>Invio</keycap> per ritornare al menù di
         selezione.</para>
 
       <para>Usa i tasti freccia per scegliere <guimenuitem>Medium</guimenuitem>
         a meno di essere sicuro che necessiti di un altro livello di sicurezza.
         Con &gui.ok; selezionato, premi <keycap>Invio</keycap>.</para>
 
       <para>Verrà visualizzato un messaggio di conferma a seconda del
         settaggio di sicurezza che hai scelto.</para>
 
       <screen>                                 Message
 
 Moderate security settings have been selected.
 
 Sendmail and SSHd have been enabled, securelevels are
 disabled, and NFS server setting have been left intact.
 PLEASE NOTE that this still does not save you from having
 to properly secure your system in other ways or exercise
 due diligence in your administration, this simply picks
 a standard set of out-of-box defaults to start with.
 
 To change any of these settings later, edit /etc/rc.conf
 
                                   [OK]</screen>
 
       <screen>                                 Message
 
 Extreme security settings have been selected.
 
 Sendmail, SSHd, and NFS services have been disabled, and
 securelevels have been enabled.
 PLEASE NOTE that this still does not save you from having
 to properly secure your system in other ways or exercise
 due diligence in your administration, this simply picks
 a more secure set of out-of-box defaults to start with.
 
 To change any of these settings later, edit /etc/rc.conf
 
                                   [OK]</screen>
 
       <para>Premi <keycap>Invio</keycap> per continuare con la
         post-installazione.</para>
 
       <warning>
         <para>Il profilo di sicurezza non è una soluzione miracolosa!
           Anche se usi il settaggio estremo, devi stare al passo con i problemi
           di sicurezza leggendo la mailing lista appropriata
           (<xref linkend="eresources-mail"/>), usando ottime password e
           frasi-password, e attenendosi alle comuni prassi di sicurezza.
           Qui semplicemente setti il desiderato rapporto sicurezza/convenienza
           della macchina.</para>
       </warning>
     </sect2>
 
     <sect2 id="console">
       <title>Settaggio della Console di Sistema</title>
 
       <para>Ci sono parecchie opzioni disponibili per personalizzare la
         console di sistema.</para>
 
       <screen>                      User Confirmation Requested
        Would you like to customize your system console settings?
 
                               [ Yes ]  No</screen>
 
       <para>Per vedere e configurare le opzioni, seleziona &gui.yes; e premi
         <keycap>Invio</keycap>.</para>
 
       <figure id="saver-options">
         <title>Opzioni di Configurazione della Console di Sistema</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/console-saver1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Un'opzione comunemente usata è lo screen saver.  Usa
         i tasti freccia per selezionare <guimenuitem>Saver</guimenuitem> e
         premi <keycap>Invio</keycap>.</para>
 
 
       <figure id="saver-select">
         <title>Opzioni dello Screen Saver</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/console-saver2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Scegli lo screen saver che desideri usando i tasti freccia
         e quindi premi <keycap>Invio</keycap>.  Verrà mostrato il
         menù di Configurazione della Console di Sistema.</para>
 
       <para>Il tempo di inattesa di default è di 300 secondi.
         Per modificare l'intervallo di tempo,
         seleziona <guimenuitem>Saver</guimenuitem> di nuovo.
         Nel menù delle opzioni dello Screen Saver, seleziona
         <guimenuitem>Timeout</guimenuitem> usando i tasti freccia e premi
         <keycap>Invio</keycap>.  Verrà mostrato un menù:</para>
 
       <figure id="saver-timeout">
         <title>Timeout dello Screen Saver</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/console-saver3"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Puoi cambiare il valore, quindi seleziona &gui.ok; e
         premi <keycap>Invio</keycap> per ritornare al menù di
         Configurazione della Console di Sistema.</para>
 
       <figure id="saver-exit">
         <title>Uscire dalla Configurazione della Console di Sistema</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/console-saver4"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Selezionando <guimenuitem>Exit</guimenuitem> e premendo
         <keycap>Invio</keycap> continuerai con le configurazioni
         post-installazione.</para>
     </sect2>
 
     <sect2 id="timezone">
       <title>Regolazione della Zona di Fuso Orario</title>
 
       <para>Il settaggio della zona di fuso orario per la tua macchina ti
         consentirà di correggere automaticamente i cambiamenti
         di tempo regionali e di realizzare altre funzioni relative
         al fuso orario.</para>
 
       <para>L'esempio mostrato è per una macchina situata nella zona
         di fuso orario orientale degli stati Uniti.  La tua selezione
         dipenderà dalla tua locazione geografica.</para>
 
       <screen>                      User Confirmation Requested
           Would you like to set this machine's time zone now?
 
                             [ Yes ]   No</screen>
 
       <para>Seleziona &gui.yes; e premi <keycap>Invio</keycap> per settare la
         zona di fuso orario.</para>
 
       <screen>                       User Confirmation Requested
  Is this machine's CMOS clock set to UTC? If it is set to local time
  or you don't know, please choose NO here!
 
                               Yes   [ No ]</screen>
 
       <para>Seleziona &gui.yes; o &gui.no; a seconda di come è
         configurato l'orologio della macchina e poi premi
         <keycap>Invio</keycap>.</para>
 
       <figure id="set-timezone-region">
         <title>Selezione della tua Regione</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/timezone1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>La regione appropriata viene selezionata usando i tasti freccia
         e quindi premendo <keycap>Invio</keycap>.</para>
 
       <figure id="set-timezone-country">
         <title>Selezione della tua Nazione</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/timezone2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Scegli la nazione appropriata usando i tasti freccia e premi
         <keycap>Invio</keycap>.</para>
 
       <figure id="set-timezone-locality">
         <title>Selezione della Tua Zona di Fuso Orario</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/timezone3"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>La zona di fuso orario appropriata viene selezionata usando i tasti
         freccia e premendo <keycap>Invio</keycap>.</para>
 
       <screen>                            Confirmation
             Does the abbreviation 'EDT' look reasonable?
 
                             [ Yes ]   No</screen>
 
       <para>Viene richiesta una conferma per l'abbreviazione per la zona di fuso
         orario.  Se va bene, premi <keycap>Invio</keycap> per continuare con
         la configurazione post-installazione.</para>
     </sect2>
 
     <sect2 id="linuxcomp">
       <title>Compatibilità Linux</title>
 
       <screen>                      User Confirmation Requested
           Would you like to enable Linux binary compatibility?
 
                             [ Yes ]   No</screen>
 
       <para>Selezionando &gui.yes; e premendo <keycap>Invio</keycap>,
         potrai eseguire applicazioni Linux su FreeBSD.  Verranno installati
         i package per la compatibilità Linux.</para>
 
       <para>Se stai facendo l'installazione via FTP, la macchina
         necessiterà di collegarsi a Internet.  A volte il sito remoto
         non ha tutte le distribuzioni così come la compatibilità
         Linux binaria.  Puoi sempre installarlo più tardi.</para>
     </sect2>
 
     <sect2 id="mouse">
       <title>Configurazione del Mouse</title>
 
       <para>Questa opzione ti consentirà di tagliare ed incollare il
         testo nella console e nei programmi utenti con un mouse a 3 pulsanti.
         Se usi un mouse a 2 pulsanti, fai riferimento alla pagina man,
         &man.moused.8;, dopo l'installazione per i dettagli sull'emulazione
         del terzo pulsante.  Questo esempio descrive una configurazione di un
         mouse non USB (come un mouse PS/2 o via porta COM):</para>
 
       <screen>                      User Confirmation Requested
          Does this system have a non-USB mouse attached to it?
 
                             [ Yes ]    No </screen>
 
       <para>Seleziona &gui.yes; per un mouse non-USB o &gui.no; per un mouse
         USB e poi premi <keycap>Invio</keycap>.</para>
 
       <figure id="mouse-protocol">
         <title>Selezione del Tipo di Protocollo del Mouse</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/mouse1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Usa i tasti freccia per selezionare <guimenuitem>Type</guimenuitem>
         e premi <keycap>Invio</keycap>.</para>
 
       <figure id="set-mouse-protocol">
         <title>Settare il Protocollo del Mouse</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/mouse2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Il mouse usato in questo esempio è di tipo PS/2, quindi
         l'opzione di default <guimenuitem>Auto</guimenuitem> era appropriata.
         Per cambiare il protocollo, usa i tasti freccia e seleziona un'altra
         opzione.  Assicurati che &gui.ok; sia selezionato e premi
         <keycap>Invio</keycap> per uscire da questo menù.</para>
 
       <figure id="config-mouse-port">
         <title>Configurare la Porta del Mouse</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/mouse3"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Usa i tasti freccia per selezionare <guimenuitem>Port</guimenuitem>
         e premi <keycap>Invio</keycap>.</para>
 
       <figure id="set-mouse-port">
         <title>Settare la Porta del Mouse</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/mouse4"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Questo sistema aveva un mouse PS/2, dunque l'opzione
         di default <guimenuitem>PS/2</guimenuitem> andava bene.  Per
         cambiare la porta, usa i tasti freccia e premi
         <keycap>Invio</keycap>.</para>
 
       <figure id="test-daemon">
         <title>Abilitare il Demone del Mouse</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/mouse5"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Per ultimo, usa i tasti freccia per selezionare
         <guimenuitem>Enable</guimenuitem>, e premi <keycap>Invio</keycap>
         per abilitare e testare il demone del mouse.</para>
 
       <figure id="test-mouse-daemon">
         <title>Test del Demone del Mouse</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/mouse6"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Muovi il cursore sullo schermo e verifica che il cursore risponda
         in modo appropriato.  Se lo fa, seleziona &gui.yes; e premi
         <keycap>Invio</keycap>.  Se non lo fa, allora il mouse non è
         stato configurato correttamente &mdash; seleziona &gui.no; e prova ad
         usare delle differenti opzioni di configurazione.</para>
 
       <para>Seleziona <guimenuitem>Exit</guimenuitem> con i tasti freccia
         e premi <keycap>Invio</keycap> per continuare con la configurazione
         di post-installazione.</para>
     </sect2>
 
     <sect2 id="network-services">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>Tom</firstname>
 
             <surname>Rhodes</surname>
 
             <contrib>Contributo di </contrib>
           </author>
         </authorgroup>
       </sect2info>
 
       <title>Configurare I Servizi Addizionali di Rete</title>
 
       <para>La configurazione dei servizi di rete può spaventare
         i nuovi utenti se questi non hanno alle spalle una conoscenza in
         quest'area.  La rete, Internet incluso, è cruciale per tutti
         i moderni sistemi operativi &os; incluso; detto ciò, è
         del tutto utile conoscere le grandi capacità di rete di &os;.
         Fare questo durante l'installazione permetterà
         agli utenti di avere alcune conoscenze dei vari servizi che sono
         disponibili.</para>
 
       <para>I servizi di rete sono programmi che accettano input da qualunque
         posto sulla rete.  Sono stati fatti molti sforzi per assicurare
         che questi programmi non fanno nulla di <quote>dannoso</quote>.
         Sfortunatamente, i programmatori non sono perfetti e in passato
         ci sono stati casi dove alcuni bug nei servizi di rete sono stati
         sfruttati da aggressori per fare cose maligne.  È importante
         che abiliti sono i servizi di rete che sai di aver bisogno.
         Se sei nel dubbio è meglio non abilitare un servizio di rete
         fino a quando scopri di averlo bisogno.  Lo puoi sempre abilitare
         successivamente ri-avviando <application>sysinstall</application>
         o usando le funzionalità fornite dal file
         <filename>/etc/rc.conf</filename>.</para>
 
       <para>Selezionando l'opzione <guimenu>Networking</guimenu> verrà
         visualizzato un menù simile a questo:</para>
 
       <figure id="network-configuration">
         <title>Configurazione di Alto-Livello della Rete</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/net-config-menu1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>La prima opzione, <guimenuitem>Interfaces</guimenuitem>,
         è stata trattata precedentemente durante la
         <xref linkend="inst-network-dev"/>, e quindi questa opzione può
         essere tranquillamente ignorata.</para>
 
       <para>Selezionando l'opzione <guimenuitem>AMD</guimenuitem> verrà
         aggiunto il supporto per l'utility di mount automatica di
         <acronym>BSD</acronym>.  Di solito questo viene usato in combinazione
         con il protocollo <acronym>NFS</acronym> (vedi sotto) per montare
         automaticamente i filesystem remoti.  Non è
         richiesta alcuna configurazione speciale.</para>
 
       <para>La linea successiva è l'opzione
         <guimenuitem>AMD Flags</guimenuitem>.  Quando selezionata,
         viene visualizzato un menù per settare delle flag specifiche
         di <acronym>AMD</acronym>.  Il menù contiene già
         una serie di opzioni di default:</para>
 
       <screen>-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map</screen>
 
       <para>L'opzione <literal>-a</literal> setta la locazione di mount
         di default che è qui specificata come
         <filename>/.amd_mnt</filename>.  L'opzione <literal>-l</literal>
         specifica il file di <filename>log</filename>; di default; comunque,
         quando viene usato <literal>syslogd</literal> tutte le attività
         di log saranno inviate al demone di log del sistema. La directory
         <filename class="directory">/host</filename> è usata per
         montare un filesystem esportato da un host remoto, mentre
         la directory <filename class="directory">/net</filename> è
         usata per montare un filesystem esportato da un indirizzo
         <acronym>IP</acronym>.  Il file <filename>/etc/amd.map</filename>
         definisce le opzioni di default per le esportazioni
         <acronym>AMD</acronym>.</para>
 
       <indexterm>
         <primary>FTP</primary>
         <secondary>anonimo</secondary>
       </indexterm>
 
       <para>L'opzione <guimenuitem>Anon FTP</guimenuitem> permette
         connessioni <acronym>FTP</acronym> anonime.  Seleziona questa
         opzione per rendere questa macchina un server
         <acronym>FTP</acronym> anonimo.  Sii consapevole dei rischi di
         sicurezza che questa opzione comporta.  Verrà
         visualizzato un altro menù nel quale vengono spiegati più
         nel dettaglio i rischi di sicurezza e la configurazione.</para>
 
       <para>Il menù di configurazione <guimenuitem>Gateway</guimenuitem>
         configurerà la macchina per essere un gateway come spiegato
         in precedenza.  Lo puoi usare per deselezionare l'opzione
         <guimenuitem>Gateway</guimenuitem> se l'hai selezionata sbadatamente
         nel processo di installazione.</para>
 
       <para>L'opzione <guimenuitem>Inetd</guimenuitem> può essere
         usata per configurare o disabilitare completamente il demone
         &man.inetd.8; come discusso sopra.</para>
 
       <para>L'opzione <guimenuitem>Mail</guimenuitem> è usata per
         configurare l'<acronym>MTA</acronym> (Mail Transfer Agent) di default
         per il sistema.  Selezionando questa opzione apparirà
         il seguente menù:</para>
 
       <figure id="mta-selection">
         <title>Selezione dell'MTA di default</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/mta-main"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Ti viene data una scelta per quale <acronym>MTA</acronym>
         di default installare e configurare.  Un <acronym>MTA</acronym> non
         è altro che un server di posta che consegna email agli
         utenti sul sistema o via Internet.</para>
 
       <para>Selezionando <guimenuitem>Sendmail</guimenuitem> verrà
         installato il famoso server <application>sendmail</application>,
         di default per FreeBSD.  L'opzione
         <guimenuitem>Sendmail local</guimenuitem> imposterà
         <application>sendmail</application> per essere l'<acronym>MTA</acronym>
         di default, ma disabilita la sua funzionalità di ricevere
         email in ingresso provenienti da Internet.  Le alternative,
         <guimenuitem>Postfix</guimenuitem> e <guimenuitem>Exim</guimenuitem>
         si comportano in modo simile a <guimenuitem>Sendmail</guimenuitem>.
         Sono entrambi distributori di email; ad ogni modo, alcuni
         utenti preferiscono queste alternative all'<acronym>MTA</acronym>
         <application>sendmail</application>.</para>
 
       <para>Dopo aver scelto o meno un <acronym>MTA</acronym>,
         apparirà il menù di configurazione della rete con la
         prossima opzione <guimenuitem>NFS client</guimenuitem>.</para>
 
       <para>L'opzione <guimenuitem>NFS client</guimenuitem> configurerà
         il sistema per comunicare con un server tramite <acronym>NFS</acronym>.
         Un server <acronym>NFS</acronym> rende i filesystem disponibili a
         altre macchine sulla rete tramite il protocollo <acronym>NFS</acronym>.
         Se questa è una macchina a se stante, questa opzione
         può non essere selezionata.  Il sistema può
         richiedere un'ulteriore configurazione in seguito; consulta la
         <xref linkend="network-nfs"/> per maggiori informazioni sulla
         configurazione riguardo client e server.</para>
 
       <para>Sotto all'opzione precedente c'è l'opzione
         <guimenuitem>NFS server</guimenuitem>, che ti permette di configurare
         il sistema come un server <acronym>NFS</acronym>.  Questo
         aggiunge le informazioni richieste per avviare <acronym>RPC</acronym>,
         servizi di chiamata a procedura remota.  <acronym>RPC</acronym> è
         usato per coordinare le connessioni tra host e i programmi.</para>
 
       <para>La prossima linea è l'opzione
         <guimenuitem>Ntpdate</guimenuitem>, che tratta la sincronizzazione
         del tempo.  Quando selezionato, viene mostrato un menù come
         questo:</para>
 
       <figure id="Ntpdate-config">
         <title>Configurazione di Ntpdate</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/ntp-config"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Da questo menù, seleziona il server più
         vicino alla tua posizione.  Selezionando il più vicino renderai
         la sincronizzazione del tempo più accurata poichè
         un server lontano dalla tua posizione potrebbe avere una latenza
         di connessione maggiore.</para>
 
       <para>La prossima opzione è <acronym>PCNFSD</acronym>.
         Questa opzione installerà il package
         <filename role="package">net/pcnfsd</filename> dalla collezione dei
         port.  Questa è un'utilità che fornisce servizi di
         autenticazione <acronym>NFS</acronym> per i sistemi che sono
         incapaci di fornirne dei propri, come il sistema operativo
         &ms-dos; della Microsoft.</para>
 
       <para>Adesso scorri in giù per vedere le altre
         opzioni:</para>
 
       <figure id="Network-configuration-cont">
         <title>Configurazione della Rete di Basso-Livello</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/net-config-menu2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Le utility &man.rpcbind.8;, &man.rpc.statd.8;, e
         &man.rpc.lockd.8; sono tutte usate per <acronym>RPC</acronym>
         (Chiamate a Procedura Remote).  L'utility <command>rpcbind</command>
         gestisce la comunicazione con server e client <acronym>NFS</acronym>,
         ed è richiesta per i server <acronym>NFS</acronym> per operare
         correttamente.  Il demone <application>rpc.statd</application>
         interagisce con il demone <application>rpc.statd</application> su
         altri host per fornire un controllo sullo stato.  Lo stato riportato
         è solitamente tenuto nel file
         <filename>/var/db/statd.status</filename>.  La prossima opzione qui
         elencata è l'opzione <guimenuitem>rpc.lockd</guimenuitem>, che,
         quando selezionata, fornisce servizi di locking dei file.  Viene
         solitamente usato con <application>rpc.statd</application> per
         controllare quali host stanno richiedendo lock e con quale frequenza.
         Mentre queste ultime due opzioni sono meravigliose per il debugging,
         non sono richieste per i client e server <acronym>NFS</acronym>
         per operare correttamente.</para>
 
       <para>Come puoi vedere avanzando nella lista il prossimo elemento
         è <guimenuitem>Routed</guimenuitem>, che è il demone
         di instradamento.  L'utility &man.routed.8; gestisce le tabelle
         di instradamento di rete, trova router multicast, e fornisce una
         copia della tabella di instradamento ad ogni host fisicamente
         connesso previa richiesta via rete.  Questo è principalmente
         usato per le macchine che fungono da gateway per una lan.  Quando
         selezionato, verrà visualizzato un menù che richiede
         la locazione di default dell'utility.  La locazione di default è
         già definita e può essere selezionata con il tasto
         <keycap>Invio</keycap>.  Poi ti sarà presentato un
         altro menù, questa volta per impostare le flag che desideri
         passare a <application>routed</application>.  Sullo schermo dovrebbe
         apparire la flag di default <literal>-q</literal>.</para>
 
       <para>La prossima linea è l'opzione
         <guimenuitem>Rwhod</guimenuitem> che, quando
         selezionata, avvierà il demone &man.rwhod.8; durante
         l'inizializzazione del sistema.  L'utility <command>rwhod</command>
         invia periodicamente via rete messaggi di sistema broadcast, o in
         modalità <quote>consumatore</quote> li colleziona.  Altre
         informazioni possono essere trovate nella pagine man &man.ruptime.1;
         e &man.rwho.1;.</para>
 
       <para>L'ultima opzione della lista è per il demone
         &man.sshd.8;.  Questo è il server di shell sicuro di
         <application>OpenSSH</application> ed è altamente raccomandato
         al posto dei server <application>telnet</application> e
         <acronym>FTP</acronym>.  Il server <application>sshd</application>
         è usato per creare una connessione sicura da un host ad un altro
         usando connessioni cifrate.</para>
 
       <para>In fine c'è l'opzione
         <guimenuitem>TCP Extensions</guimenuitem>.  Questo abilita le
         estensioni <acronym>TCP</acronym> definite nelle
         <acronym>RFC</acronym>&nbsp;1323 e <acronym>RFC</acronym>&nbsp;1644.
         Mentre su molti host questo può velocizzare le connessioni,
         potrebbe anche causare la perdita di alcune connessioni.  Non
         è raccomandato per server, ma può essere un beneficio
         per macchine a se stanti.</para>
 
       <para>Ora che hai configurato i servizi di rete, puoi scorrere in alto
         fino all'opzione <guimenuitem>Exit</guimenuitem> e continuare con la
         prossima sezione di configurazione.</para>
     </sect2>
 
     <sect2 id="x-server">
       <title>Configurare il Server X</title>
 
       <note>
         <para>A partire da &os;&nbsp;5.3-RELEASE, la configurazione del
           server X è stata rimossa da
           <application>sysinstall</application>, devi installare e configurare
           il server X dopo l'installazione di &os;.
           Maggiori informazioni riguardo all'installazione e alla configurazione
           del server X possono essere trovate nel <xref linkend="x11"/>.
           Puoi saltare questa sezione se non stai installando una versione di
           &os; antecedente la 5.3-RELEASE.</para>
       </note>
 
       <para>Per usare un'interfaccia utente grafica come ad esempio
         <application>KDE</application>, <application>GNOME</application>, o
         altri, hai bisogno di configurare il server X.</para>
 
       <note>
         <para>Per far girare <application>&xfree86;</application>
           come utente non <username>root</username> avrai bisogno di
           avere <filename role="package">x11/wrapper</filename> installato.
           Questo è installato di default a partire da FreeBSD 4.7.
           Per le versioni precedenti questo può
           essere installato dal menù di selezione dei package.</para>
       </note>
 
       <para>Per vedere se la tua scheda video è supportata,
          vai sul sito di <ulink
           url="http://www.xfree86.org/">&xfree86;</ulink>.</para>
 
       <screen>                      User Confirmation Requested
         Would you like to configure your X server at this time?
 
                             [ Yes ]   No</screen>
 
       <warning>
         <para>È necessario conoscere le specifiche del tuo monitor
           e alcune informazioni della scheda video.  Settaggi non corretti
           potrebbero creare danni all'attrezzatura.  Se non hai queste
           informazioni, seleziona &gui.no; e quando hai le informazioni esegui
           la configurazione dopo l'installazione usando
           <command>sysinstall</command>
           (<command>/stand/sysinstall</command> nelle versioni di &os; dopo la
           5.2), selezionando <guimenuitem>Configure</guimenuitem> e poi
           <guimenuitem>XFree86</guimenuitem>.  Una configurazione
           errata del server X a questo punto può lasciare la
           macchina in uno stato di blocco.  È consigliato configurare
           il server X una volta che l'installazione è stata
           completata.</para>
       </warning>
 
       <para>Se hai le informazioni della scheda grafica e del monitor, seleziona
         &gui.yes; e premi <keycap>Invio</keycap> per procedere alla
         configurazione del server X.</para>
 
       <figure id="xserver2">
         <title>Selezione del Menù del Metodo di Configurazione</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/xf86setup"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Ci sono diversi modi per configurare il server X.
         Usa i tasti freccia per selezionarne uno e premi <keycap>Invio</keycap>.
         Assicurati di leggere tutte le istruzioni attentamente.</para>
 
       <para>I metodi <application>xf86cfg</application> e
         <application>xf86cfg -textmode</application> potrebbero richiedere
         alcuni secondi all'avvio con uno schermo nero.  Abbiate pazienza.</para>
 
       <para>Di seguito verrà illustrato l'uso del tool di configurazione
         <application>xf86config</application>.  Le scelte di configurazione
         che farai dipenderanno dall'hardware nel sistema e quindi le tue
         scelte saranno probabilmente diverse da quelle qui mostrate:</para>
 
       <screen>                                Message
  You have configured and been running the mouse daemon.
  Choose "/dev/sysmouse" as the mouse port and "SysMouse" or
  "MouseSystems" as the mouse protocol in the X configuration utility.
 
                                  [ OK ]
 
                       [ Press enter to continue ]</screen>
 
       <para>Questo indica che è stato rilevato il demone del mouse
         precedentemente configurato.  Premi <keycap>Invio</keycap> per
         continuare.</para>
 
       <para>Avviando <application>xf86config</application>
         verrà visualizzata una breve introduzione:</para>
 
       <screen>This program will create a basic XF86Config file, based on menu selections you
 make.
 
 The XF86Config file usually resides in /usr/X11R6/etc/X11 or /etc/X11. A sample
 XF86Config file is supplied with XFree86; it is configured for a standard
 VGA card and monitor with 640x480 resolution. This program will ask for a
 pathname when it is ready to write the file.
 
 You can either take the sample XF86Config as a base and edit it for your
 configuration, or let this program produce a base XF86Config file for your
 configuration and fine-tune it.
 
 Before continuing with this program, make sure you know what video card
 you have, and preferably also the chipset it uses and the amount of video
 memory on your video card. SuperProbe may be able to help with this.
 
 Press enter to continue, or ctrl-c to abort.</screen>
 
       <para>Premendo <keycap>Invio</keycap> comincerà la
         configurazione del mouse.  Assicurati di seguire le istruzioni e usa
         <quote>Mouse Systems</quote> come protocollo e
         <devicename>/dev/sysmouse</devicename> come porta del mouse;
         l'uso di un mouse PS/2 è mostrato a titolo illustrativo.</para>
 
       <screen>First specify a mouse protocol type. Choose one from the following list:
 
  1.  Microsoft compatible (2-button protocol)
  2.  Mouse Systems (3-button protocol) &amp; FreeBSD moused protocol
  3.  Bus Mouse
  4.  PS/2 Mouse
  5.  Logitech Mouse (serial, old type, Logitech protocol)
  6.  Logitech MouseMan (Microsoft compatible)
  7.  MM Series
  8.  MM HitTablet
  9.  Microsoft IntelliMouse
 
 If you have a two-button mouse, it is most likely of type 1, and if you have
 a three-button mouse, it can probably support both protocol 1 and 2. There are
 two main varieties of the latter type: mice with a switch to select the
 protocol, and mice that default to 1 and require a button to be held at
 boot-time to select protocol 2. Some mice can be convinced to do 2 by sending
 a special sequence to the serial port (see the ClearDTR/ClearRTS options).
 
 Enter a protocol number: 2
 
 You have selected a Mouse Systems protocol mouse. If your mouse is normally
 in Microsoft-compatible mode, enabling the ClearDTR and ClearRTS options
 may cause it to switch to Mouse Systems mode when the server starts.
 
 Please answer the following question with either 'y' or 'n'.
 Do you want to enable ClearDTR and ClearRTS? n
 
 You have selected a three-button mouse protocol. It is recommended that you
 do not enable Emulate3Buttons, unless the third button doesn't work.
 
 Please answer the following question with either 'y' or 'n'.
 Do you want to enable Emulate3Buttons? y
 
 Now give the full device name that the mouse is connected to, for example
 /dev/tty00. Just pressing enter will use the default, /dev/mouse.
 On FreeBSD, the default is /dev/sysmouse.
 
 Mouse device: /dev/sysmouse</screen>
 
       <para>Il prossimo oggetto da configurare è la tastiera.  Un modello
         generico a 101 tasti è mostrato a titolo di esempio.
         Si possono usare diversi nomi per le varianti o semplicemente
         premi <keycap>Invio</keycap> per accettare il valore di default.</para>
 
       <screen>Please select one of the following keyboard types that is the better
 description of your keyboard. If nothing really matches,
 choose 1 (Generic 101-key PC)
 
   1  Generic 101-key PC
   2  Generic 102-key (Intl) PC
   3  Generic 104-key PC
   4  Generic 105-key (Intl) PC
   5  Dell 101-key PC
   6  Everex STEPnote
   7  Keytronic FlexPro
   8  Microsoft Natural
   9  Northgate OmniKey 101
  10  Winbook Model XP5
  11  Japanese 106-key
  12  PC-98xx Series
  13  Brazilian ABNT2
  14  HP Internet
  15  Logitech iTouch
  16  Logitech Cordless Desktop Pro
  17  Logitech Internet Keyboard
  18  Logitech Internet Navigator Keyboard
  19  Compaq Internet
  20  Microsoft Natural Pro
  21  Genius Comfy KB-16M
  22  IBM Rapid Access
  23  IBM Rapid Access II
  24  Chicony Internet Keyboard
  25  Dell Internet Keyboard
 
 Enter a number to choose the keyboard.
 
 1
 
 
 Please select the layout corresponding to your keyboard
 
 
   1  U.S. English
   2  U.S. English w/ ISO9995-3
   3  U.S. English w/ deadkeys
   4  Albanian
   5  Arabic
   6  Armenian
   7  Azerbaidjani
   8  Belarusian
   9  Belgian
  10  Bengali
  11  Brazilian
  12  Bulgarian
  13  Burmese
  14  Canadian
  15  Croatian
  16  Czech
  17  Czech (qwerty)
  18  Danish
 
 Enter a number to choose the country.
 Press enter for the next page
 
 1
 
 
 Please enter a variant name for 'us' layout. Or just press enter
 for default variant
 
 us
 
 
 Please answer the following question with either 'y' or 'n'.
 Do you want to select additional XKB options (group switcher,
 group indicator, etc.)? n</screen>
 
       <para>Ora, procediamo alla configurazione del monitor.
         Non eccedere alla potenza del tuo monitor.  Potrebbero accadere dei
         danni.  Se hai alcuni dubbi, fai la configurazione quando hai
         le informazioni.</para>
 
       <screen>Now we want to set the specifications of the monitor. The two critical
 parameters are the vertical refresh rate, which is the rate at which the
 whole screen is refreshed, and most importantly the horizontal sync rate,
 which is the rate at which scanlines are displayed.
 
 The valid range for horizontal sync and vertical sync should be documented
 in the manual of your monitor. If in doubt, check the monitor database
 /usr/X11R6/lib/X11/doc/Monitors to see if your monitor is there.
 
 Press enter to continue, or ctrl-c to abort.
 
 
 
 You must indicate the horizontal sync range of your monitor. You can either
 select one of the predefined ranges below that correspond to industry-
 standard monitor types, or give a specific range.
 
 It is VERY IMPORTANT that you do not specify a monitor type with a horizontal
 sync range that is beyond the capabilities of your monitor. If in doubt,
 choose a conservative setting.
 
     hsync in kHz; monitor type with characteristic modes
  1  31.5; Standard VGA, 640x480 @ 60 Hz
  2  31.5 - 35.1; Super VGA, 800x600 @ 56 Hz
  3  31.5, 35.5; 8514 Compatible, 1024x768 @ 87 Hz interlaced (no 800x600)
  4  31.5, 35.15, 35.5; Super VGA, 1024x768 @ 87 Hz interlaced, 800x600 @ 56 Hz
  5  31.5 - 37.9; Extended Super VGA, 800x600 @ 60 Hz, 640x480 @ 72 Hz
  6  31.5 - 48.5; Non-Interlaced SVGA, 1024x768 @ 60 Hz, 800x600 @ 72 Hz
  7  31.5 - 57.0; High Frequency SVGA, 1024x768 @ 70 Hz
  8  31.5 - 64.3; Monitor that can do 1280x1024 @ 60 Hz
  9  31.5 - 79.0; Monitor that can do 1280x1024 @ 74 Hz
 10  31.5 - 82.0; Monitor that can do 1280x1024 @ 76 Hz
 11  Enter your own horizontal sync range
 
 Enter your choice (1-11): 6
 
 You must indicate the vertical sync range of your monitor. You can either
 select one of the predefined ranges below that correspond to industry-
 standard monitor types, or give a specific range. For interlaced modes,
 the number that counts is the high one (e.g. 87 Hz rather than 43 Hz).
 
  1  50-70
  2  50-90
  3  50-100
  4  40-150
  5  Enter your own vertical sync range
 
 Enter your choice: 2
 
 You must now enter a few identification/description strings, namely an
 identifier, a vendor name, and a model name. Just pressing enter will fill
 in default names.
 
 The strings are free-form, spaces are allowed.
 Enter an identifier for your monitor definition: Hitachi</screen>
 
       <para>Ora tocca alla selezione della scheda video da una lista.
         Se passi la tua scheda dalla lista, continua a premere
         <keycap>Invio</keycap> e la lista ricomincerà da capo.
         Viene mostrato solo uno stralcio della lista.</para>
 
       <screen>Now we must configure video card specific settings. At this point you can
 choose to make a selection out of a database of video card definitions.
 Because there can be variation in Ramdacs and clock generators even
 between cards of the same model, it is not sensible to blindly copy
 the settings (e.g. a Device section). For this reason, after you make a
 selection, you will still be asked about the components of the card, with
 the settings from the chosen database entry presented as a strong hint.
 
 The database entries include information about the chipset, what driver to
 run, the Ramdac and ClockChip, and comments that will be included in the
 Device section. However, a lot of definitions only hint about what driver
 to run (based on the chipset the card uses) and are untested.
 
 If you can't find your card in the database, there's nothing to worry about.
 You should only choose a database entry that is exactly the same model as
 your card; choosing one that looks similar is just a bad idea (e.g. a
 GemStone Snail 64 may be as different from a GemStone Snail 64+ in terms of
 hardware as can be).
 
 Do you want to look at the card database? y
 
 
 
 288  Matrox Millennium G200 8MB                        mgag200
 289  Matrox Millennium G200 SD 16MB                    mgag200
 290  Matrox Millennium G200 SD 4MB                     mgag200
 291  Matrox Millennium G200 SD 8MB                     mgag200
 292  Matrox Millennium G400                            mgag400
 293  Matrox Millennium II 16MB                         mga2164w
 294  Matrox Millennium II 4MB                          mga2164w
 295  Matrox Millennium II 8MB                          mga2164w
 296  Matrox Mystique                                   mga1064sg
 297  Matrox Mystique G200 16MB                         mgag200
 298  Matrox Mystique G200 4MB                          mgag200
 299  Matrox Mystique G200 8MB                          mgag200
 300  Matrox Productiva G100 4MB                        mgag100
 301  Matrox Productiva G100 8MB                        mgag100
 302  MediaGX                                           mediagx
 303  MediaVision Proaxcel 128                          ET6000
 304  Mirage Z-128                                      ET6000
 305  Miro CRYSTAL VRX                                  Verite 1000
 
 Enter a number to choose the corresponding card definition.
 Press enter for the next page, q to continue configuration.
 
 288
 
 Your selected card definition:
 
 Identifier: Matrox Millennium G200 8MB
 Chipset:    mgag200
 Driver:     mga
 Do NOT probe clocks or use any Clocks line.
 
 Press enter to continue, or ctrl-c to abort.
 
 
 
 Now you must give information about your video card. This will be used for
 the "Device" section of your video card in XF86Config.
 
 You must indicate how much video memory you have. It is probably a good
 idea to use the same approximate amount as that detected by the server you
 intend to use. If you encounter problems that are due to the used server
 not supporting the amount memory you have (e.g. ATI Mach64 is limited to
 1024K with the SVGA server), specify the maximum amount supported by the
 server.
 
 How much video memory do you have on your video card:
 
  1  256K
  2  512K
  3  1024K
  4  2048K
  5  4096K
  6  Other
 
 Enter your choice: 6
 
 Amount of video memory in Kbytes: 8192
 
 You must now enter a few identification/description strings, namely an
 identifier, a vendor name, and a model name. Just pressing enter will fill
 in default names (possibly from a card definition).
 
 Your card definition is Matrox Millennium G200 8MB.
 
 The strings are free-form, spaces are allowed.
 Enter an identifier for your video card definition:</screen>
 
       <para>Andando ancora avanti, sono settate le modalità video per
         la risoluzione desiderata.  Tipicamente, utili range sono 640x480,
         800x600 e 1024x768, ma questi sono in funzione delle capacità
         della scheda video, della dimensione del monitor, e del comfort degli
         occhi.  Quando selezioni una profondità di colore, seleziona
         la più alta che la tua scheda supporta.</para>
 
       <screen>For each depth, a list of modes (resolutions) is defined. The default
 resolution that the server will start-up with will be the first listed
 mode that can be supported by the monitor and card.
 Currently it is set to:
 
 "640x480" "800x600" "1024x768" "1280x1024" for 8-bit
 "640x480" "800x600" "1024x768" "1280x1024" for 16-bit
 "640x480" "800x600" "1024x768" "1280x1024" for 24-bit
 
 Modes that cannot be supported due to monitor or clock constraints will
 be automatically skipped by the server.
 
  1  Change the modes for 8-bit (256 colors)
  2  Change the modes for 16-bit (32K/64K colors)
  3  Change the modes for 24-bit (24-bit color)
  4  The modes are OK, continue.
 
 Enter your choice: 2
 
 Select modes from the following list:
 
  1  "640x400"
  2  "640x480"
  3  "800x600"
  4  "1024x768"
  5  "1280x1024"
  6  "320x200"
  7  "320x240"
  8  "400x300"
  9  "1152x864"
  a  "1600x1200"
  b  "1800x1400"
  c  "512x384"
 
 Please type the digits corresponding to the modes that you want to select.
 For example, 432 selects "1024x768" "800x600" "640x480", with a
 default mode of 1024x768.
 
 Which modes? 432
 
 You can have a virtual screen (desktop), which is screen area that is larger
 than the physical screen and which is panned by moving the mouse to the edge
 of the screen. If you don't want virtual desktop at a certain resolution,
 you cannot have modes listed that are larger. Each color depth can have a
 differently-sized virtual screen
 
 Please answer the following question with either 'y' or 'n'.
 Do you want a virtual screen that is larger than the physical screen? n
 
 
 
 For each depth, a list of modes (resolutions) is defined. The default
 resolution that the server will start-up with will be the first listed
 mode that can be supported by the monitor and card.
 Currently it is set to:
 
 "640x480" "800x600" "1024x768" "1280x1024" for 8-bit
 "1024x768" "800x600" "640x480" for 16-bit
 "640x480" "800x600" "1024x768" "1280x1024" for 24-bit
 
 Modes that cannot be supported due to monitor or clock constraints will
 be automatically skipped by the server.
 
  1  Change the modes for 8-bit (256 colors)
  2  Change the modes for 16-bit (32K/64K colors)
  3  Change the modes for 24-bit (24-bit color)
  4  The modes are OK, continue.
 
 Enter your choice: 4
 
 
 
 Please specify which color depth you want to use by default:
 
   1  1 bit (monochrome)
   2  4 bits (16 colors)
   3  8 bits (256 colors)
   4  16 bits (65536 colors)
   5  24 bits (16 million colors)
 
 Enter a number to choose the default depth.
 
 4</screen>
 
       <para>In fine, devi salvare la configurazione.  Assicurati di digitare
         <filename>/etc/X11/XF86Config</filename> come la locazione per salvare
         la configurazione.</para>
 
       <screen>I am going to write the XF86Config file now. Make sure you don't accidently
 overwrite a previously configured one.
 
 Shall I write it to /etc/X11/XF86Config? y</screen>
 
       <para>Se la configurazione fallisce, puoi provare a rifarla selezionando
         &gui.yes; quando appare il seguente messaggio:</para>
 
       <screen>          User Confirmation Requested
 The XFree86 configuration process seems to have
 failed.  Would you like to try again?
 
              [ Yes ]         No</screen>
 
       <para>Se hai difficoltà a configurare
         <application>&xfree86;</application>, seleziona
         &gui.no; e premi <keycap>Invio</keycap>
         e prosegui con il processo di installazione.  Dopo
         l'installazione puoi usare <command>xf86cfg -textmode</command>
         oppure <command>xf86config</command> come <username>root</username>
         per accedere alle utility di configurazione a linea di comando.
         C'è un altro metodo per configurare
         <application>&xfree86;</application>, descritto nel
         <xref linkend="x11"/>.  Se hai deciso di non configurare
         <application>&xfree86;</application> il prossimo menù
         sarà per la selezione dei package.</para>
 
       <para>Il settaggio di default che permette di killare il server è
         la sequenza di tasti <keycombo
           action='simul'><keycap>Ctrl</keycap><keycap>Alt</keycap>
           <keycap>Backspace</keycap></keycombo>.
         Puoi usarla se qualcosa nel settaggio del server è sbagliato
         prevenendo danni all'hardware.</para>
 
       <para>Il settaggio di default che permette di saltare da una
         modalità video all'altra mentre X è in esecuzione è
         la sequenza di tasti <keycombo
           action='simul'><keycap>Ctrl</keycap><keycap>Alt</keycap>
             <keycap>+</keycap></keycombo> o
           <keycombo action='simul'><keycap>Ctrl</keycap><keycap>Alt</keycap>
             <keycap>-</keycap></keycombo>.
       </para>
 
       <para>Dopo che hai <application>&xfree86;</application> in esecuzione,
         puoi aggiustare la schermata in altezza, larghezza o centrarla
         usando <application>xvidtune</application>.</para>
 
       <para>Ci sono avvisi che segnalano che settaggi impropri possono
         danneggiare il tuo equipaggiamento.  Considerali.  Se sei in dubbio,
         non farlo.  Invece, usa i controlli del monitor per aggiustare la
         schermata per X Window.  Così facendo ci potrebbero essere delle
         incongruenze di visualizzazione quando passi alla modalità testo,
         ma questo è meglio rispetto al danneggiamento
         dell'equipaggiamento.</para>
 
       <para>Leggi la pagina man di &man.xvidtune.1; prima di fare qualsiasi
         regolazione.</para>
 
       <para>Al seguito di una configurazione di
         <application>&xfree86;</application> andata a buon fine, si
         procederà alla selezione di un desktop di default.</para>
     </sect2>
 
     <sect2 id="default-desktop">
       <title>Selezionare il Desktop X di Default</title>
 
       <note>
         <para>A partire da &os;&nbsp;5.3-RELEASE, la possibilità
           di selezione del desktop X è stata rimossa da
           <application>sysinstall</application>, devi configurare il desktop
           X dopo l'installazione di &os;.  Maggiori informazioni riguardo
           all'installazione e configurazione di un desktop X possono
           essere trovate nel <xref linkend="x11"/>.  Puoi saltare questa sezione
           se non stai installando una versione di &os; precedente
           a 5.3-RELEASE.</para>
       </note>
 
       <para>Sono disponibili diversi gestori di finestre.  Essi spaziano
         da ambienti veramente basilari fino a ambienti con desktop completi
         che includono diverse applicazioni.  Alcuni richiedono uno spazio
         di disco minimo e poca memoria mentre altri con maggiori
         funzionalità richiedono più risorse.  Il miglior modo
         per determinare quale gestore di finestre utilizzare è provarne
         alcuni.  Sono disponibili dalla collezione dei port o come package
         e possono essere aggiunti dopo l'installazione.</para>
 
       <para>Puoi selezionare uno dei desktop più popolari e sarà
         installato ed configurato come il desktop di default.  Ciò
         ti permetterà di avviarlo appena dopo l'installazione.</para>
 
       <figure id="x-desktop">
         <title>Selezione del Desktop di Default</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/desktop"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Usa i tasti freccia per selezionare un desktop e premi
         <keycap>Invio</keycap>.  Verrà avviata l'installazione
         del desktop selezionato.</para>
     </sect2>
 
     <sect2 id="packages">
       <title>Installazione dei Package</title>
 
       <para>I package sono binari pre-compilati e risultano essere un modo
         conveniente per installare applicazioni.</para>
 
       <para>A scopo illustrativo viene mostrata l'installazione di un
         package.  Puoi installare ulteriori package se lo desideri.
         Dopo l'installazione puoi usare <command>sysinstall</command>
         (<command>/stand/sysinstall</command> nelle versioni di &os; dopo la
         5.2) per aggiungere ulteriori package.</para>
 
       <screen>                     User Confirmation Requested
  The FreeBSD Package collection is a collection of hundreds of
  ready-to-run applications, from text editors to games to WEB servers
  and more. Would you like to browse the collection now?
 
                             [ Yes ]   No</screen>
 
       <para>Selezionando &gui.yes; e premendo <keycap>Invio</keycap>
         verranno visualizzate le seguenti schermate per la selezione
         dei package:</para>
 
       <figure id="package-category">
         <title>Selezione della Categoria dei Package</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/pkg-cat"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Soltanto i package che risiedono sul media di installazione
         corrente sono disponibili per l'installazione in un dato
         istante.</para>
 
       <para>Se si seleziona <guimenuitem>All</guimenuitem> saranno visualizzati
         tutti i package disponibili oppure puoi selezionare una categoria
         particolare.  Evidenzia la tua selezione con i tasti freccia e premi
         <keycap>Invio</keycap>.</para>
 
       <para>Verrà visualizzato un menù con i package disponibili
         in base alla selezione effettuata:</para>
 
       <figure id="package-select">
         <title>Selezione dei Package</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/pkg-sel"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>È stata selezionata la shell <application>bash</application>.
         Puoi selezionare altre cose portandoti sul package e premendo il tasto
         <keycap>Spazio</keycap>.  Apparirà una breve descrizione di ogni
         package nell'angolo in basso a sinistra dello schermo.</para>
 
       <para>Premendo il tasto <keycap>Tab</keycap> passerai ciclicamente
         dall'ultimo package selezionato, da &gui.ok;, e da &gui.cancel;.</para>
 
       <para>Quando hai finito di selezionare i package che vuoi installare,
         premi <keycap>Tab</keycap> una volta per andare a &gui.ok; e premi
         <keycap>Invio</keycap> per tornare al menù della selezione
         dei package.</para>
 
       <para>Con i tasti freccia sinistra e destra puoi passare tra &gui.ok; e
         &gui.cancel;.  Questo metodo può essere anche
         usato per selezionare &gui.ok; e premere <keycap>Invio</keycap>
         per tornare al menù di selezione dei package.</para>
 
       <figure id="package-install">
         <title>Installazione dei Package</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/pkg-install"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Usa <keycap>Tab</keycap> e con i tasti freccia seleziona
         <guibutton>[&nbsp;Install&nbsp;]</guibutton> e premi
         <keycap>Invio</keycap>.  Dovrai confermare l'installazione dei
         package:</para>
 
       <figure id="package-install-confirm">
         <title>Conferma dell'Installazione dei Package</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/pkg-confirm"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Selezionando &gui.ok; e premendo <keycap>Invio</keycap>
         inizierà l'installazione dei package.  Appariranno
         dei messaggi di installazione fino al completamento della stessa.
         Prendi nota se c'è qualche messaggio di errore.</para>
 
       <para>La configurazione finale continua dopo che i package
         sono stati installati.  Se decidi di non selezionare alcun package,
         e vuoi ritornare alla configurazione finale, seleziona comunque
         <guibutton>Install</guibutton>.</para>
     </sect2>
 
     <sect2 id="addusers">
       <title>Aggiungere Utenti/Gruppi</title>
 
       <para>Dovresti aggiungere almeno un utente durante l'installazione
         in modo che puoi usare il sistema senza doverti loggare come
         <username>root</username>.  La partizione root è generalmente
         di dimensioni ridotte ed eseguire applicazione da
         <username>root</username> può riempirla facilmente.
         Viene segnalato un pericolo:</para>
 
       <screen>                     User Confirmation Requested
  Would you like to add any initial user accounts to the system? Adding
  at least one account for yourself at this stage is suggested since
  working as the "root" user is dangerous (it is easy to do things which
  adversely affect the entire system).
 
                             [ Yes ]   No</screen>
 
       <para>Seleziona &gui.yes; e premi <keycap>Invio</keycap> per continuare
         nell'aggiunta di un utente.</para>
 
       <figure id="add-user2">
         <title>Selezione di un Utente</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/adduser1"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Seleziona <guimenuitem>User</guimenuitem> con i tasti freccia e
         premi <keycap>Invio</keycap>.</para>
 
       <figure id="add-user3">
         <title>Aggiungere Informazioni dell'Utente</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/adduser2"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Le seguenti descrizioni appariranno nella parte bassa dello schermo
         ogni qual volta gli elementi sono selezionati con <keycap>Tab</keycap>
         per assistere all'immissione delle informazioni richieste:</para>
 
       <variablelist>
         <varlistentry>
           <term>Login ID</term>
 
           <listitem>
             <para>Il nome di login del nuovo utente (obbligatorio).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>UID</term>
 
           <listitem>
             <para>L'ID numerico per questo utente (lasciare bianco per una
               scelta automatica).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Group</term>
 
           <listitem>
             <para>Il nome del gruppo di login per questo utente (lasciate
               bianco per una scelta automatica).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Password</term>
 
           <listitem>
             <para>La password per questo utente (inserisci questo campo
               con cura!).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Full name</term>
 
           <listitem>
             <para>Il nome completo dell'utente (commento).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Member groups</term>
 
           <listitem>
             <para>I gruppi a cui questo utente appartiene (cioè i diritti
               di accesso concessi).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Home directory</term>
 
           <listitem>
             <para>La directory home dell'utente (lasciare in bianco per
               il default).</para>
           </listitem>
         </varlistentry>
 
         <varlistentry>
           <term>Login shell</term>
 
           <listitem>
             <para>La shell di login dell'utente (lasciare in bianco per il
               default, per esempio <filename>/bin/sh</filename>).</para>
           </listitem>
         </varlistentry>
       </variablelist>
 
       <para>La shell di login è stata modificata da
         <filename>/bin/sh</filename> a
         <filename>/usr/local/bin/bash</filename> per usare la shell
         <application>bash</application> che è stata in precedenza
         installata come package.  Non tentare di usare una shell che non
         esiste o non sarai in grado di effettuare il login.  La shell
         più comune usata nel mondo-BSD è la schell C, che
         può essere indicata come <filename>/bin/tcsh</filename>.</para>
 
       <para>L'utente è stata aggiunto al gruppo
         <groupname>wheel</groupname> al fine di poter diventare un superutente
         con privilegi di <username>root</username>.</para>
 
       <para>Quando sei soddisfatto, premi &gui.ok; e ti verrà
         visualizzato il menù di gestione degli utenti e dei
         gruppi:</para>
 
       <figure id="add-user4">
         <title>Uscire dal menù di Gestione degli Utenti e dei
           Gruppi</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/adduser3"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>I gruppi possono essere aggiunti anche adesso se necessario.
         Altrimenti, puoi farlo usando <command>sysinstall</command>
         (<command>/stand/sysinstall</command> nelle versioni di &os; dopo la
         5.2) dopo che hai completato l'installazione.</para>
 
       <para>Quando hai terminato di aggiungere gli utenti, seleziona
         <guimenuitem>Exit</guimenuitem> con i tasti freccia e premi
         <keycap>Invio</keycap> per continuare l'installazione.</para>
     </sect2>
 
     <sect2 id="rootpass">
       <title>Settare la Password di <username>root</username></title>
 
       <screen>                        Message
  Now you must set the system manager's password.
  This is the password you'll use to log in as "root".
 
                          [ OK ]
 
                [ Press enter to continue ]</screen>
 
       <para>Premi <keycap>Invio</keycap> per settare la password
         di <username>root</username>.</para>
 
       <para>La password dovrà essere battuta correttamente
         per due volte.  Inutile a dirsi, assicurati di avere un modo di trovare
         la password nel caso dovessi dimenticarla.  Nota che la password che
         digiti non è mostrata, e non vengono visualizzati neppure gli
         asterischi.</para>
 
       <screen>Changing local password for root.
 New password :
 Retype new password :</screen>
 
       <para>L'installazione continuerà dopo che la
         password è stata inserita correttamente.</para>
     </sect2>
 
     <sect2 id="exit-inst">
       <title>Uscire dall'Installazione</title>
 
       <para>Se hai bisogno di configurare altri dispositivi di rete
         o altre configurazioni, lo puoi fare a questo punto o dopo
         con <command>sysinstall</command>
         (<command>/stand/sysinstall</command> nelle versioni di &os; dopo la
         5.2).</para>
 
       <screen>                     User Confirmation Requested
  Visit the general configuration menu for a chance to set any last
  options?
 
                               Yes   [ No ]</screen>
 
       <para>Seleziona &gui.no; con i tasti freccia e premi
         <keycap>Invio</keycap> per tornare al menù di Installazione
         Principale.</para>
 
       <figure id="final-main">
         <title>Uscire dall'Installazione</title>
 
         <mediaobject>
           <imageobject>
             <imagedata fileref="install/mainexit"/>
           </imageobject>
         </mediaobject>
       </figure>
 
       <para>Seleziona con i tasti freccia
         <guibutton>[X Exit Install]</guibutton> e premi <keycap>Invio</keycap>.
         Ti sarà chiesto di confermare l'uscita
         dall'installazione:</para>
 
       <screen>                     User Confirmation Requested
  Are you sure you wish to exit? The system will reboot (be sure to
  remove any floppies from the drives).
 
                             [ Yes ]   No</screen>
 
       <para>Seleziona &gui.yes; e rimuovi il floppy se hai avviato tramite
         floppy.  Il CDROM è bloccato fino a quando la macchina
         non verrà riavviata.  Il CDROM verrà quindi sbloccato
         e il disco può essere rimosso dal dispositivo
         (velocemente).</para>
 
       <para>Il sistema verrà riavviato, guarda eventuali messaggi
         di errore che potrebbero apparire.</para>
     </sect2>
 
     <sect2 id="freebsdboot">
       <title>Avvio di FreeBSD</title>
 
       <sect3 id="freebsdboot-i386">
         <title>Avvio di FreeBSD su &i386;</title>
 
         <para>Se tutto è andato bene, vedrai alcuni messaggi
           scorrere sullo schermo a arriverai al prompt di login.
           Puoi controllare il contenuto dei messaggi premendo
           <keycap>Scroll-Lock</keycap> e usando <keycap>PgUp</keycap>
           e <keycap>PgDn</keycap>.  Premendo <keycap>Scroll-Lock</keycap>
           un'altra volta ritornerai al prompt.</para>
 
         <para>Il messaggio completo non può essere visualizzato (per
           limitazioni del buffer) ma può essere visto dalla
           linea di comando dopo aver effettuato il login digitando al prompt
           <command>dmesg</command>.</para>
 
         <para>Accedi usando il nome utente e la password che hai settato
           durante l'installazione (<username>rpratt</username>, in questo
           esempio).  Evita di loggarti come <username>root</username> se non ne
           hai bisogno.</para>
 
         <para>Tipici messaggi di avvio (le informazioni sulla versione sono
           state omesse):</para>
 
         <screen>Copyright (c) 1992-2002 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
 
 Timecounter "i8254"  frequency 1193182 Hz
 CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU)
   Origin = "AuthenticAMD"  Id = 0x580  Stepping = 0
   Features=0x8001bf&lt;FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX&gt;
   AMD Features=0x80000800&lt;SYSCALL,3DNow!&gt;
 real memory  = 268435456 (262144K bytes)
 config&gt; di sn0
 config&gt; di lnc0
 config&gt; di le0
 config&gt; di ie0
 config&gt; di fe0
 config&gt; di cs0
 config&gt; di bt0
 config&gt; di aic0
 config&gt; di aha0
 config&gt; di adv0
 config&gt; q
 avail memory = 256311296 (250304K bytes)
 Preloaded elf kernel "kernel" at 0xc0491000.
 Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c.
 md0: Malloc disk
 Using $PIR table, 4 entries at 0xc00fde60
 npx0: &lt;math processor&gt; on motherboard
 npx0: INT 16 interface
 pcib0: &lt;Host to PCI bridge&gt; on motherboard
 pci0: &lt;PCI bus&gt; on pcib0
 pcib1: &lt;VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge&gt; at device 1.0 on pci0
 pci1: &lt;PCI bus&gt; on pcib1
 pci1: &lt;Matrox MGA G200 AGP graphics accelerator&gt; at 0.0 irq 11
 isab0: &lt;VIA 82C586 PCI-ISA bridge&gt; at device 7.0 on pci0
 isa0: &lt;ISA bus&gt; on isab0
 atapci0: &lt;VIA 82C586 ATA33 controller&gt; port 0xe000-0xe00f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0: &lt;VIA 83C572 USB controller&gt; port 0xe400-0xe41f irq 10 at device 7.2 on pci0
 usb0: &lt;VIA 83C572 USB controller&gt; on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 chip1: &lt;VIA 82C586B ACPI interface&gt; at device 7.3 on pci0
 ed0: &lt;NE2000 PCI Ethernet (RealTek 8029)&gt; port 0xe800-0xe81f irq 9 at
 device 10.0 on pci0
 ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit)
 isa0: too many dependant configs (8)
 isa0: unexpected small tag 14
 fdc0: &lt;NEC 72065B or clone&gt; at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: &lt;1440-KB 3.5" drive&gt; on fdc0 drive 0
 atkbdc0: &lt;keyboard controller (i8042)&gt; at port 0x60-0x64 on isa0
 atkbd0: &lt;AT Keyboard&gt; flags 0x1 irq 1 on atkbdc0
 kbd0 at atkbd0
 psm0: &lt;PS/2 Mouse&gt; irq 12 on atkbdc0
 psm0: model Generic PS/2 mouse, device ID 0
 vga0: &lt;Generic ISA VGA&gt; at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: &lt;System console&gt; at flags 0x1 on isa0
 sc0: VGA &lt;16 virtual consoles, flags=0x300&gt;
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: &lt;Parallel port&gt; at port 0x378-0x37f irq 7 on isa0
 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/15 bytes threshold
 ppbus0: IEEE1284 device found /NIBBLE
 Probing for PnP devices on ppbus0:
 plip0: &lt;PLIP network interface&gt; on ppbus0
 lpt0: &lt;Printer&gt; on ppbus0
 lpt0: Interrupt-driven port
 ppi0: &lt;Parallel I/O&gt; on ppbus0
 ad0: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata0-master using UDMA33
 ad2: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata1-master using UDMA33
 acd0: CDROM &lt;DELTA OTC-H101/ST3 F/W by OIPD&gt; at ata0-slave using PIO4
 Mounting root from ufs:/dev/ad0s1a
 swapon: adding /dev/ad0s1b as swap device
 Automatic boot in progress...
 /dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1a: clean, 48752 free (552 frags, 6025 blocks, 0.9% fragmentation)
 /dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1f: clean, 128997 free (21 frags, 16122 blocks, 0.0% fragmentation)
 /dev/ad0s1g: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1g: clean, 3036299 free (43175 frags, 374073 blocks, 1.3% fragmentation)
 /dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS
 /dev/ad0s1e: clean, 128193 free (17 frags, 16022 blocks, 0.0% fragmentation)
 Doing initial network setup: hostname.
 ed0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
         inet6 fe80::5054::5ff::fede:731b%ed0 prefixlen 64 tentative scopeid 0x1
         ether 52:54:05:de:73:1b
 lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; mtu 16384
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
         inet6 ::1 prefixlen 128
         inet 127.0.0.1 netmask 0xff000000
 Additional routing options: IP gateway=YES TCP keepalive=YES
 routing daemons:.
 additional daemons: syslogd.
 Doing additional network setup:.
 Starting final network daemons: creating ssh RSA host key
 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:
 cd:76:89:16:69:0e:d0:6e:f8:66:d0:07:26:3c:7e:2d root@k6-2.example.com
  creating ssh DSA host key
 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:
 f9:a1:a9:47:c4:ad:f9:8d:52:b8:b8:ff:8c:ad:2d:e6 root@k6-2.example.com.
 setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib
 /usr/local/lib
 a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
 starting standard daemons: inetd cron sshd usbd sendmail.
 Initial rc.i386 initialization:.
 rc.i386 configuring syscons: blank_time screensaver moused.
 Additional ABI support: linux.
 Local package initialization:.
 Additional TCP options:.
 
 FreeBSD/i386 (k6-2.example.com) (ttyv0)
 
 login: rpratt
 Password:</screen>
 
         <para>La generazione delle chiavi RSA e DSA può richiedere un
           pò di tempo sulle macchine lente.  Questo succede solo al primo
           avvio di una nuova installazione.  I successivi avvii saranno
           più veloci.</para>
 
         <para>Se è stato configurato il server X ed è stato
           scelto un Desktop di default, questo può essere avviato
           digitando sulla linea di comando <command>startx</command>.</para>
     </sect3>
 
     <sect3>
       <title>Avvio di FreeBSD su Alpha</title>
 
       <indexterm><primary>Alpha</primary></indexterm>
 
       <para>Una volta finita la procedura di installazione, sarai in grado di
         avviare FreeBSD scrivendo qualcosa di simile a questo nel prompt
         SRM:</para>
 
       <screen>&gt;&gt;&gt;<userinput>BOOT DKC0</userinput></screen>
 
       <para>Questo istruisce il firmware ad avviare il disco specificato.
         Per avviare FreeBSD in automatico in futuro, usa questi comandi:</para>
 
       <screen><prompt>&gt;&gt;&gt;</prompt> <userinput>SET BOOT_OSFLAGS A</userinput>
 <prompt>&gt;&gt;&gt;</prompt> <userinput>SET BOOT_FILE ''</userinput>
 <prompt>&gt;&gt;&gt;</prompt> <userinput>SET BOOTDEF_DEV DKC0</userinput>
 <prompt>&gt;&gt;&gt;</prompt> <userinput>SET AUTO_ACTION BOOT</userinput></screen>
 
       <para>I messaggi di avvio saranno simili (ma non identici) a quelli
         prodotti dall'avvio di FreeBSD su &i386;.</para>
       </sect3>
     </sect2>
 
     <sect2 id="shutdown">
       <title>Lo Shutdown di FreeBSD</title>
 
       <para>È importante spegnere (effettuare lo shutdown) in modo
         adeguato il sistema operativo.  Non farlo rimuovendo l'alimentazione.
         Innanzitutto, diventa superuser digitando <command>su</command>
         dalla linea di comando ed inserendo la password di
         <username>root</username>.  Questo funziona solo se l'utente è
         un membro del gruppo <groupname>wheel</groupname>.  Altrimenti, loggati
         come <username>root</username> e usa
         <command>shutdown -h now</command>.</para>
 
       <screen>The operating system has halted.
 Please press any key to reboot.</screen>
 
       <para>Quando appare il messaggio
         <quote>Please press any key to reboot</quote> puoi togliere con
         sicurezza l'alimentazione.  Se premi qualunque tasto invece di premere
         il bottone per togliere l'alimentazione, il sistema verrà
         riavviato.</para>
 
       <para>Potresti anche usare la combinazione di tasti
         <keycombo action="simul">
           <keycap>Ctrl</keycap>
           <keycap>Alt</keycap>
           <keycap>Del</keycap>
         </keycombo> per riavviare il sistema, comunque questo non è
         raccomandato durante un normale funzionamento.</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-supported-hardware">
     <title>Hardware Supportato</title>
 
     <indexterm><primary>hardware</primary></indexterm>
 
     <para>FreeBSD attualmente gira su una varietà di PC con bus ISA, VLB,
       EISA, e PCI con processori Intel, AMD, Cyrix, o processori NexGen
       <quote>x86</quote>, così come su diverse macchine basate
       sul processore Compaq Alpha.  Supporta configurazioni generiche di
       dispositivi IDE o ESDI, svariati controller SCSI, schede PCMCIA,
       dispositivi USB, e schede seriale e di rete.  FreeBSD supporta anche il
       bus microchannel (MCA) di IBM.</para>
 
     <para>Un elenco di hardware supportato da FreeBSD è fornito con
       ogni release di FreeBSD nell'Hardware Note di FreeBSD.  Questo documento
       può essere trovato nel file <filename>HARDWARE.TXT</filename>,
       nella directory root di una distribuzione CDROM o FTP o nel menù
       di documentazione di <application>sysinstall</application>.  Per ogni
       architettura, vengono elencati i dispositivi hardware che sono noti
       essere supportati dalla release di FreeBSD.  Copie della lista
       dell'hardware supportato per diverse release ed architetture possono
       essere trovate nella pagina del sito Web di FreeBSD <ulink
         url="http://www.FreeBSD.org/releases/index.html">Informazioni di
         Release</ulink>.</para>
   </sect1>
 
   <sect1 id="install-trouble">
     <title>Localizzazione dei guasti</title>
 
     <indexterm>
       <primary>installazione</primary>
       <secondary>localizzazione dei guasti</secondary>
     </indexterm>
 
     <para>Questa sezione copre la localizzazione di alcuni problemi riguardo
       all'installazione, come problemi comuni che sono stati segnalati dagli
       utenti.  Ci sono anche alcune domande e risposte per le persone
       che desiderano avere FreeBSD e &ms-dos; sulla stessa macchina.</para>
 
     <sect2>
       <title>Che Cosa Fare se Qualche Cosa va Storto</title>
 
       <para>A causa di varie limitazioni dell'architettura del PC, è
         impossibile che la fase di probe sia accurata al 100%, comunque ci sono
         alcune cose che puoi fare se il probe fallisce.</para>
 
       <para>Controlla il documento Hardware Note per la tua versione di
         FreeBSD per assicurarti che il tuo hardware sia supportato.</para>
 
       <para>Se il tuo hardware è supportato e continui ad avere
         esperienze di blocco o altri problemi, resetta il computer,
         e quando ti viene data la possibilità entra nella
         configurazione visuale del kernel.  Il kernel sui dischetti
         di avvio è configurato assumendo che la maggior parte
         dei dispositivi hardware sono nella loro configurazioni di fabbrica
         in termini di IRQ, indirizzi di IO, e canali DMA.  Se
         il tuo hardware è stato riconfigurato, probabilmente
         hai bisogno di usare l'editor di configurazione per dire a FreeBSD
         dove trovare le cose.</para>
 
       <para>È anche possibile che un probe di un dispositivo non presente
         porti a un fallimento di un successivo probe per un dispositivo
         presente.  In questo caso, i probe per i driver che vanno in
         conflitto dovrebbero essere disabilitati.</para>
 
       <note>
         <para>Alcuni problemi di installazione possono essere evitati o
           alleviati con un aggiornamento del firmware dei vari
           componenti hardware, scheda madre in primis.  Il
           firmware della scheda madre può anche essere chiamato
           <acronym>BIOS</acronym> e la maggior parte dei produttori di
           schede madri o di computer hanno un sito web dove  poter localizzare
           gli aggiornamenti e le relative informazioni.</para>
 
         <para>La maggior parte dei produttori non consiglia l'aggiornamento
           del <acronym>BIOS</acronym> della scheda madre a meno che ci sia
           una buona ragione per farlo, che potrebbe essere una sorta
           di aggiornamento critico.  Il processo di aggiornamento
           <emphasis>può</emphasis> non andare per il verso giusto,
           causando danni permanenti al chip del <acronym>BIOS</acronym>.</para>
       </note>
 
       <warning>
         <para>Non disabilitare alcuni driver di cui avrai bisogno durante
           l'installazione, come quello per lo schermo
           (<devicename>sc0</devicename>).  Se l'installazione si ferma o
           fallisce misteriosamente dopo aver lasciato l'editor di
           configurazione, probabilmente hai rimosso o modificato qualcosa
           che non dovevi.  Riavvia e prova di nuovo.</para>
       </warning>
 
       <para>Nella modalità di configurazione, puoi:</para>
 
       <itemizedlist>
         <listitem>
           <para>Elencare i driver dei dispositivi installati nel kernel.</para>
         </listitem>
 
         <listitem>
           <para>Disabilitare i driver dei dispositivi per l'hardware che non
             è presente nel tuo sistema.</para>
         </listitem>
 
         <listitem>
           <para>Cambiare IRQ, DRQ, e gli indirizzi delle porte di IO usati
             da un driver di dispositivo.</para>
         </listitem>
       </itemizedlist>
 
       <para>Dopo che hai sistemato il kernel in base alla tua configurazione
         hardware, premi <command>Q</command> per avviare con i nuovi
         settaggi.  Una volta completata l'installazione, ogni modifica
         che hai fatto nella modalità di configurazione sarà
         permanente in modo tale che non devi riconfigurare ogni volta
         che avvii.  Tuttavia è molto probabile che tu voglia costruirti
         un <link linkend="kernelconfig">kernel su misura</link>.</para>
     </sect2>
 
     <sect2>
       <title>Questioni su Partizioni &ms-dos;</title>
 
       <indexterm><primary>DOS</primary></indexterm>
 
       <para>Molti utenti desiderano installare &os; su un <acronym>PC</acronym>
         popolato da sistemi operativi &microsoft;.  Per queste situazioni,
         &os; ha un utility di nome <application>FIPS</application>.  Questa
         utility può essere trovata nella directory
         <filename>tools</filename> su CD-ROM di installazione, o può
         essere scaricata da uno dei vari <link linkend="mirrors">mirror di
           &os;</link>.</para>
 
       <para>L'utility <application>FIPS</application> ti consente di suddividere
         una partizione &ms-dos; esistente in due pezzi, preservando la
         partizione originale e permettendo di installare &os; nella seconda
         parte libera.  Prima devi deframmentare la tua partizione &ms-dos;
         usando l'utility di &windows;
         <application>Deframmentazione dei Dischi</application> (vai in Explorer,
         clicca con il destro sull'hard disk, e scegli di deframmentarlo),
         oppure usando <application>Norton Disk Tools</application>.  Adesso
         puoi eseguire l'utility <application>FIPS</application>.  Ti verranno
         mostrate delle informazioni di supporto, segui le informazioni a video.
         Fatto ciò, puoi riavviare ed installare &os; sulla nuova slice
         libera.  Guarda il menù <guimenuitem>Distributions</guimenuitem>
         per una stima di quanto spazio libero necessiti per il tipo di
         installazione voluto.</para>
 
       <para>Esiste anche un prodotto molto utile della PowerQuest
         (<ulink
           url="http://www.powerquest.com/">http://www.powerquest.com</ulink>)
         chiamato <application>&partitionmagic;</application>.  Questa
         applicazione ha più funzionalità di
         <application>FIPS</application>, ed è altamente raccomandato
         se hai intenzione di aggiungere/rimuovere spesso sistemi operativi.
         È a pagamento, quindi se hai intenzione di installare in modo
         permanente &os;, <application>FIPS</application> probabilmente fa
         al caso tuo.</para>
     </sect2>
 
     <sect2>
       <title>Usare filesystem &ms-dos; e &windows;</title>
 
       <para>A tutt'oggi, &os; non supporta filesystem compressi con
         l'utility <application>Double Space&trade;</application>.  Quindi il
         filesystem dovrà essere decompresso prima che &os; possa
         accedere ai dati.  Questo può essere fatto eseguendo
         l'<application>Agente di Compressione</application> raggiungibile da
         <guimenuitem>start</guimenuitem> &gt;
         <guimenuitem>Programs</guimenuitem> &gt;
         <guimenuitem>System Tools</guimenuitem>.</para>
 
       <para>&os; supporta filesystem basati su &ms-dos;.  Questo
         richiede di usare il comando &man.mount.msdosfs.8;
         con i parametri opportuni.
         L'uso più comune è:</para>
 
       <screen>&prompt.root; <userinput>mount_msdosfs /dev/ad0s1 /mnt</userinput></screen>
 
       <para>In questo esempio, il filesystems &ms-dos; è localizzato
         sulla prima partizione dell'hard disk primario.  La tua situazione
         potrebbe essere differente, verifica l'output dei comandi
         <command>dmesg</command>, e <command>mount</command>.  Questi,
         dovrebbero produrre abbastanza informazioni per darti un'idea
         del layout della partizione.</para>
 
       <note>
         <para>I filesystem &ms-dos; estesi in genere sono mappati dopo le
           partizioni di &os;.  In altre parole, il numero della slice potrebbe
           essere più alto di quello usato da &os;.  Per esempio, la
           prima partizione &ms-dos; potrebbe essere
           <filename>/dev/ad0s1</filename>, la partizione di &os;
           potrebbe essere <filename>/dev/ad0s2</filename>, con la partizione
           &ms-dos; estesa in <filename>/dev/ad0s3</filename>.  Per alcuni,
           tutto ciò potrebbe causare della confusione all'inizio.</para>
       </note>
 
       <para>Le partizioni NTFS possono essere montate in modo simile usando
         il comando &man.mount.ntfs.8;.</para>
     </sect2>
 
     <sect2>
       <title>Domande e Risposte degli Utenti di Alpha</title>
 
       <indexterm><primary>Alpha</primary></indexterm>
 
       <para>Questa sezione risponde ad alcune questioni comuni relative
         all'installazione di FreeBSD su sistemi Alpha.</para>
 
       <qandaset>
         <qandaentry>
           <question>
             <para>Posso avviare dalla console ARC o da quella del BIOS
               Alpha?</para>
           </question>
 
 	  <answer>
           <indexterm><primary>ARC</primary></indexterm>
           <indexterm><primary>Alpha BIOS</primary></indexterm>
           <indexterm><primary>SRM</primary></indexterm>
 
             <para>No.  &os;, come Compaq Tru64 e VMS, non si avviano dalla
               console SRM.</para>
           </answer>
         </qandaentry>
 
         <qandaentry>
           <question>
             <para>Aiuto, non ho spazio!  Devo cancellare tutto prima?</para>
           </question>
 
           <answer>
             <para>Sfortunatamente, si.</para>
           </answer>
         </qandaentry>
 
         <qandaentry>
           <question>
             <para>Posso montare il mio Compaq True64 o il filesystem
               VMS?</para>
           </question>
 
           <answer>
             <para>No, non in questo caso.</para>
           </answer>
         </qandaentry>
       </qandaset>
     </sect2>
   </sect1>
 
   <sect1 id="install-advanced">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Valentino</firstname>
 
           <surname>Vaschetto</surname>
 
           <contrib>Contributo di </contrib>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>Guida per un'Installazione Avanzata</title>
 
     <para>Questa sezione descrive come installare FreeBSD in casi
       speciali.</para>
 
     <sect2 id="headless-install">
       <title>Installare FreeBSD su un Sistema senza Monitor e Tastiera</title>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>headless (console seriale)</secondary>
       </indexterm>
 
       <indexterm><primary>console seriale</primary></indexterm>
 
       <para>Questo tipo di installazione è chiamata
         <quote>installazione headless</quote>, poichè la macchina
         sulla quale stai cercando di installare FreeBSD non ha un monitor, o
         non ha neanche un output VGA.  Come è possibile ti chiederai?
         Usando una console seriale.  Una console seriale sostanzialmente
         usa un'altra macchina per fungere da monitor e tastiera primari per
         un sistema.  Per fare questo, segui le fasi per creare i floppy
         di installazione, come spiegato nella <xref
           linkend="install-floppies"/>.</para>
 
       <para>Per modificare questi floppy per avviare in una console seriale,
         segui questi passi:</para>
 
       <procedure>
         <step>
           <title>Abilitare i Floppy di Avvio per Avviare in una Console
             Seriale</title>
 
           <indexterm>
             <primary><command>mount</command></primary>
           </indexterm>
 
           <para>Se hai avviato con i floppy che hai appena creato, FreeBSD
             dovrebbe avviare la sua modalità di installazione standard.
             Noi vogliamo che FreeBSD avvii un console seriale per la nostra
             installazione.  Per fare questo, devi montare il floppy
             <filename>kern.flp</filename> nel tuo sistema FreeBSD usando il
             comando &man.mount.8;.</para>
 
           <screen>&prompt.root; <userinput>mount /dev/fd0 /mnt</userinput></screen>
 
           <para>Adesso che hai il tuo floppy montato, portati nella directory
             <filename class="directory">/mnt</filename>:</para>
 
           <screen>&prompt.root; <userinput>cd /mnt</userinput></screen>
 
           <para>È qui che devi configurare il floppy per avviare
             una console seriale.  Devi creare un file di nome
             <filename>boot.config</filename> contenente
             <literal>/boot/loader -h</literal>.  Tutto quello che fa è
             passare un flag al bootloader per avviare una console
             seriale.</para>
 
           <screen>&prompt.root; <userinput>echo "/boot/loader -h" &gt; boot.config</userinput></screen>
 
           <para>Adesso che hai il tuo floppy configurato correttamente,
             devi smontare il floppy usando il comando &man.umount.8;:</para>
 
           <screen>&prompt.root; <userinput>cd /</userinput>
 &prompt.root; <userinput>umount /mnt</userinput></screen>
 
           <para>Adesso puoi rimuovere il floppy.</para>
         </step>
 
         <step>
           <title>Connettere il Cavo Null-Modem</title>
 
           <indexterm><primary>cavo null modem</primary></indexterm>
 
           <para>Devi connettere un <link
               linkend="term-cables-null">cavo null-modem</link> tra le due
             macchine.  Connetti il cavo alla porta seriale delle due
             macchine.  <emphasis>Un cavo seriale normale non
               funzionerà</emphasis>, hai bisogno di un cavo null-modem
             perchè ha alcuni segnali incrociati.</para>
         </step>
 
         <step>
           <title>Avviare per l'Installazione</title>
 
           <para>È tempo di andare avanti e cominciare con
             l'installazione.  Inserisci il floppy <filename>kern.flp</filename>
             nella macchina sulla quale vuoi fare l'installazione headless,
             e accendila.</para>
         </step>
 
         <step>
           <title>Connettersi alla Macchina Headless</title>
 
           <indexterm>
             <primary><command>cu</command></primary>
           </indexterm>
 
           <para>Adesso devi connetterti alla macchina con &man.cu.1;:</para>
 
           <screen>&prompt.root; <userinput>cu -l /dev/cuaa0</userinput></screen>
         </step>
       </procedure>
 
       <para>Ci siamo! Dovresti essere in grado di controllare la macchina
         headless attraverso la tua sessione <command>cu</command>.  Ti
         verrà chiesto di inserire <filename>mfsroot.flp</filename>, e poi
         dovrai scegliere il tipo di terminale da usare.  Seleziona la console
         a colori di FreeBSD e procedi con la tua installazione!</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-diff-media">
     <title>Preparare i Propri Media di Installazione</title>
 
     <note>
       <para>Per evitare ripetizioni, <quote>il disco di FreeBSD</quote>
         in questo contesto significa il CDROM o DVD che ti sei procurato.</para>
     </note>
 
     <para>Ci possono essere delle situazioni in cui hai bisogno di creare
       dei media di installazione di FreeBSD e/o delle fonti per l'installazione.
       Potrebbe essere un media fisico, come un nastro, o una fonte che
       <application>sysinstall</application> può usare per recuperare i
       file, come un sito FTP locale, o una partizione &ms-dos;.</para>
 
     <para>Per esempio:</para>
 
     <itemizedlist>
       <listitem>
         <para>Hai molte macchine connesse alla tua rete locale, e un
           disco di FreeBSD.  Vuoi creare un sito FTP locale usando il
           contenuto del disco di FreeBSD, e quindi dare la possibilità
           alle tue macchine di usare questo sito FTP locale senza la
           necessità di doversi collegare a Internet.</para>
       </listitem>
 
       <listitem>
         <para>Hai un disco di FreeBSD, e FreeBSD non riconosce il tuo lettore
           CD/DVD, ma &ms-dos;/&windows; lo riconosce.  Vuoi copiare i file
           di installazione di FreeBSD su una partizione DOS posta sul
           medesimo computer, e quindi installare FreeBSD usando quei
           file.</para>
       </listitem>
 
       <listitem>
         <para>Il computer sul quale vuoi installare FreeBSD non ha un lettore
           CD/DVD ne una scheda di rete, ma puoi connettere un cavo
           <quote>Laplink-style</quote> seriale o parallelo ad un altro computer
           fornito di quei supporti.</para>
       </listitem>
 
       <listitem>
         <para>Vuoi creare un nastro che può essere usato per
           installare FreeBSD.</para>
       </listitem>
     </itemizedlist>
 
     <sect2 id="install-cdrom">
       <title>Creare un CDROM di Installazione</title>
 
       <para>Come parte di ogni release, il progetto FreeBSD mette a
         disposizione due immagini CDROM (<quote>immagini ISO</quote>).
         Queste immagini possono essere scritte (<quote>burnate</quote>) su
         CD se hai un masterizzatore, e quindi possono essere usate per
         installare FreeBSD.  Se hai un masterizzatore, e la banda di rete
         è conveniente, allora questo è il modo più
         semplice per installare FreeBSD.</para>
 
       <procedure>
         <step>
           <title>Scaricare le Immagini ISO Corrette</title>
 
           <para>Le immagini ISO per ogni release possono essere scaricate da
             <filename>ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-<replaceable>arch</replaceable>/<replaceable>version</replaceable></filename>
             o dal mirror più vicino.  Sostituisci
             <replaceable>arch</replaceable> e
             <replaceable>versione</replaceable> in modo appropriato.</para>
 
           <para>Quella directory normalmente contiene le seguenti
             immagini:</para>
 
           <table frame="none">
             <title>Nomi e Significati delle Immagini ISO di
               FreeBSD 4.<replaceable>X</replaceable></title>
 
             <tgroup cols="2">
               <thead>
                 <row>
                   <entry>Nome del File</entry>
 
                   <entry>Contenuto</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-miniinst.iso</filename></entry>
 
                   <entry>Tutto quello di cui hai bisogno per installare
                     FreeBSD.</entry>
                 </row>
 
                 <row>
                   <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc1.iso</filename></entry>
 
                   <entry>Tutto quello di cui hai bisogno per installare FreeBSD,
                     e anche molti package addizionali di terze parti
                     che potresti provare.</entry>
                 </row>
 
                 <row>
                   <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc2.iso</filename></entry>
 
                   <entry>Un <quote>filesystem live</quote>, usato in
                     congiunzione con l'utility  <quote>Repair</quote>
                     di <application>sysinstall</application>.
                     Una copia dell'albero CVS di FreeBSD.  Sul disco anche altri
                     package addizionali di terze parti.</entry>
                 </row>
               </tbody>
             </tgroup>
           </table>
 
           <table frame="none">
             <title>Nomi e Significati delle Immagini ISO di
               FreeBSD 5.<replaceable>X</replaceable></title>
 
             <tgroup cols="2">
               <thead>
                 <row>
                   <entry>Nome del File</entry>
 
                   <entry>Contenuto</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-bootonly.iso</filename></entry>
 
                   <entry>Tutto ciò di cui hai bisogno per avviare
                     il kernel di FreeBSD e partire con l'interfaccia di
                     installazione.  I file di installazione devono essere
                     messi su FTP o su altre fonti di supporto.</entry>
                 </row>
 
                 <row>
                   <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-miniinst.iso</filename></entry>
 
                   <entry>Tutto ciò di cui hai bisogno per installare
                     FreeBSD.</entry>
                 </row>
 
                 <row>
                   <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc1.iso</filename></entry>
 
                   <entry>Tutto ciò di cui hai bisogno per installare
                     &os; e un <quote>live filesystem</quote>, che è
                     usato in congiunzione con l'utility <quote>Repair</quote>
                     in <application>sysinstall</application>.</entry>
                 </row>
 
                 <row>
                   <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc2.iso</filename></entry>
 
                   <entry>La documentazione di &os; e molte applicazioni di
                     terze parti.</entry>
                 </row>
               </tbody>
             </tgroup>
           </table>
 
           <para><emphasis>Devi</emphasis> scaricare o l'immagine ISO miniinst,
             o l'immagine del disco uno.  Non le scaricare entrambe,
             poichè l'immagine del disco uno contiene tutto ciò
             che contiene l'immagine ISO miniinst.</para>
 
           <note>
             <para>L'immagine ISO miniinst è solo disponibile per le
               release antecedenti la 5.4-RELEASE.</para>
           </note>
 
           <para>Usa la miniinst ISO se l'accesso ad Internet è costoso
             per te.  Ti permetterà di installare FreeBSD, e puoi sempre
             installare i package di terze parti scaricandoli usando il sistema
             dei port/package (guarda il <xref linkend="ports"/>) se
             necessario.</para>
 
           <para>Usa l'immagine del disco uno se vuoi installare una release
             di &os; e se vuoi anche un
             modesto assortimento di package di terze parti.</para>
 
           <para>Le altre immagini sono utili, ma non essenziali,
             soprattutto se hai un accesso ad Internet ad alta
             velocità.</para>
         </step>
 
         <step>
           <title>Scrivere i CD</title>
 
           <para>Devi scrivere le immagini dei CD sul disco.  Se
             hai intenzione di farlo da un'altra macchina FreeBSD allora
             guarda la <xref linkend="creating-cds"/> per maggiori
             informazioni (in particolare, la <xref linkend="burncd"/> e
             la <xref linkend="cdrecord"/>).</para>
 
           <para>Se lo fai su un'altra piattaforma allora devi usare
             qualche utility per controllare il tuo masterizzatore
             di CD esistente su tale piattaforma.  Le immagini fornite
             sono nel formato standard ISO, supportato da molte applicazioni
             di masterizzazione dei CD.</para>
         </step>
       </procedure>
 
       <note>
         <para>Se sei interessato a costruirti una release di FreeBSD
           personalizzata, guarda l'<ulink
             url="&url.articles.releng;">Articolo di Progettazione delle
             Release</ulink>.</para>
       </note>
     </sect2>
 
     <sect2 id="install-ftp">
       <title>Creare un Sito FTP Locale con un Disco di FreeBSD</title>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>rete</secondary>
         <tertiary>FTP</tertiary>
       </indexterm>
 
       <para>I dischi di FreeBSD sono strutturati alla stessa maniera di un sito
         FTP.  Questo rende semplice la creazione di un sito FTP locale che
         può essere usato da altre macchine sulla tua rete per
         installare FreeBSD.</para>
 
       <procedure>
         <step>
           <para>Sul computer FreeBSD che ospiterà il sito FTP,
             assicurati che il CDROM è nel lettore, e montato
             su <filename>/cdrom</filename>.</para>
 
           <screen>&prompt.root; <userinput>mount /cdrom</userinput></screen>
         </step>
 
         <step>
           <para>Crea un account per FTP anonimo in
             <filename>/etc/passwd</filename>.  Fallo editando
             <filename>/etc/passwd</filename> usando &man.vipw.8; aggiungendo
             questa linea:</para>
 
           <programlisting>ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
         </step>
 
         <step>
           <para>Assicurati che il servizio FTP sia abilitato in
             <filename>/etc/inetd.conf</filename>.</para>
         </step>
       </procedure>
 
       <para>Chiunque che possa connettersi via rete alla tua macchina
         può ora scegliere il tipo di media FTP digitando
         <userinput>ftp://<replaceable>tua macchina</replaceable></userinput>
         dopo aver selezionato <quote>Altro</quote> nel menù dei siti
         FTP durante l'installazione.</para>
 
       <note>
         <para>Se il media di avvio (di solito dischetti floppy) usato dai
           tuoi client FTP non è della stessa versione fornita dal
           sito FTP locale, allora <application>sysinstall</application>
           non ti lascierà completare l'installazione.  Se le versioni
           non sono simili e vuoi comunque procedere, devi andare nel menù
           <guimenu>Options</guimenu> e modificare il nome della distribuzione in
           <guimenuitem>any</guimenuitem>.</para>
       </note>
 
       <warning>
         <para>Questo approccio è OK per una macchina sulla tua rete
           locale, che è protetta dal tuo firewall.  Offrire
           servizi FTP ad altre macchine su Internet (non sulla tua lan) espone
           il tuo computer all'attenzione dei cracker e di altri maligni.
           Raccomandiamo fortemente di seguire buone norme di sicurezza.</para>
       </warning>
     </sect2>
 
     <sect2>
       <title>Creare i Floppy di Installazione</title>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>floppy</secondary>
       </indexterm>
 
       <para>Se devi installare da floppy disk (che suggeriamo di
         <emphasis>non</emphasis> fare), a causa di hardware non supportato
         o semplicemente perchè insisti nel fare le cose tenacemente,
         devi prima preparare un pò di floppy per l'installazione.</para>
 
       <para>Come minimo, avrai bisogno di molti floppy da 1.44&nbsp;MB o da
         1.2&nbsp;MB per contenere tutti i file della directory
         <filename>bin</filename> (distribuzione binaria).  Se stai preparando
         i floppy da DOS, allora questi <emphasis>devono</emphasis> essere
         formattati usando il comando <command>FORMAT</command> di &ms-dos;.
         Se stai usando &windows; usa Explorer per formattare i dischi
         (clicca con il tasto destro sul dispositivo <devicename>A:</devicename>,
         e scegli <quote>Format</quote>).</para>
 
       <para><emphasis>Non</emphasis> fidarti dei floppy pre-formattati di
         fabbrica.  Formattali di nuovo, per essere sicuro.  In passato molti
         problemi riportati dai nostri utenti si sono poi rilevati causati
         dall'uso di media non correttamente formattati, ecco perchè
         stiamo mettendo in evidenzia questo fatto.</para>
 
       <para>Se crei i floppy su un'altra macchina FreeBSD, un format
         è ancora una buona idea, benchè non devi necessariamente
         mettere un filesystem DOS su ogni floppy.  Puoi usare
         i comandi <command>bsdlabel</command> e <command>newfs</command> per
         mettere un filesystem UFS su ogni flopply, come mostra la seguente
         sequenza di comandi (per un floppy da 3.5" 1.44&nbsp;MB):</para>
 
       <screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
 &prompt.root; <userinput>bsdlabel -w -r fd0.1440 floppy3</userinput>
 &prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
 
       <note>
         <para>Usa <literal>fd0.1200</literal> e
           <literal>floppy5</literal> per i dischetti da 5.25"
             1.2&nbsp;MB.</para>
       </note>
 
       <para>Puoi montarli e scriverci come qualsiasi altro tipo di
         file ystem.</para>
 
       <para>Dopo che hai formattato i flopply, dovrai copiarvi i file
         necessari.  I files della distribuzione sono splittati in pezzi
         di dimensioni tali che cinque di essi possono stare su un singolo
         floppy convenzionale da 1.44&nbsp;MB.  Crea tutti i tuoi
         floppy, fino a quando avrai tutte le distribuzioni disponibili
         in questo formato.  Ogni distribuzione dovrebbe andare in una
         sotto directory del floppy, esempio:
         <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>,
         e così via.</para>
 
       <para>Una volta che arrivi alla schermata dei Media durante il processo
         di installazione, seleziona <guimenuitem>Floppy</guimenuitem> e
         segui le indicazioni che ti saranno fornite.</para>
     </sect2>
 
     <sect2 id="install-msdos">
       <title>Installazione da una Partizione &ms-dos;</title>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>da MS-DOS</secondary>
       </indexterm>
 
       <para>Per preparare un'installazione da una partizione &ms-dos;, devi
         copiare i file dalla distribuzione in una directory chiamata
         <filename>freebsd</filename> nella directory root della partizione.  Per
         esempio, <filename>c:\freebsd</filename>.  La struttura della
         directory del CDROM o del sito FTP deve essere parzialmente riprodotta
         in questa directory, dunque consigliamo di usare il comando
         <command>xcopy</command> del DOS se stai copiando da un CD.  Per
         esempio, per preparare un'installazione minima di
         FreeBSD:</para>
 
       <screen><prompt>C:\&gt;</prompt> <userinput>md c:\freebsd</userinput>
 <prompt>C:\&gt;</prompt> <userinput>xcopy e:\bin c:\freebsd\bin\ /s</userinput>
 <prompt>C:\&gt;</prompt> <userinput>xcopy e:\manpages c:\freebsd\manpages\ /s</userinput></screen>
 
       <para>Assumendo che <devicename>C:</devicename> è dove hai spazio
         libero e <devicename>E:</devicename> è il CDROM.</para>
 
       <para>Se non hai un lettore CDROM, puoi scaricare la distribuzione da
         <ulink
           url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">ftp.FreeBSD.org</ulink>.
         Ogni distribuzione è nella propria directory; per esempio, la
         distribuzione <emphasis>base</emphasis> può essere trovata
         nella directory <ulink
           url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/base/">&rel.current;/base/</ulink>.</para>
 
       <para>Se desideri installare diverse distribuzioni da una partizione
         &ms-dos; (ed hai lo spazio per farlo), installa ciascuna
         distribuzione in <filename>c:\freebsd</filename> &mdash;
         la distribuzione <literal>BIN</literal> è la sola
         richiesta per un'installazione minima.</para>
     </sect2>
 
     <sect2>
       <title>Creare un'Installazione su Nastro</title>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>da Nastro QIC/SCSI</secondary>
       </indexterm>
 
       <para>Installare da un nastro magnetico è probabilmente un
         metodo più facile e breve rispetto a un'installazione da FTP
         o da CDROM.  Il programma di installazione si aspetta
         che i file siano semplicemente magnetizzati su nastro.  Dopo che
         hai ottenuto tutti i file della distribuzione a cui sei interessato,
         semplicemente fai un tar su nastro:</para>
 
       <screen>&prompt.root; <userinput>cd /freebsd/distdir</userinput>
 &prompt.root; <userinput>tar cvf /dev/rwt0 dist1 ... dist2</userinput></screen>
 
       <para>Quando fai l'installazione, assicurati di lasciare abbastanza
         spazio in qualche directory temporanea (che ti sarà consentito
         scegliere) per disporre il contenuto <emphasis>completo</emphasis> del
         nastro che hai creato.  A causa di un accesso non-random dei nastri,
         questo metodo di installazione richiede un pò di tempo per
         la memorizzazione temporanea.</para>
 
       <note>
         <para>Quando comincia l'installazione, il nastro deve essere
           nel lettore <emphasis>prima</emphasis> dell'avvio da floppy.
           Altrimenti il probe dell'installazione potrebbe fallire nel
           tentativo di cercarlo.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Prima di Installare via Rete</title>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>rete</secondary>
         <tertiary>seriale (SLIP o PPP)</tertiary>
       </indexterm>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>rete</secondary>
         <tertiary>parallelo (PLIP)</tertiary>
       </indexterm>
 
       <indexterm>
         <primary>installazione</primary>
         <secondary>rete</secondary>
         <tertiary>Ethernet</tertiary>
       </indexterm>
 
       <para>Sono disponibili tre tipi di installazioni di rete.
         Via porta seriale (SLIP o PPP), via porta parallela (PLIP (cavo
         laplink)), o via Ethernet (un controller Ethernet standard
         (inclusi alcuni PCMCIA)).</para>
 
       <para>Il supporto SLIP è piuttosto vecchio, e limitato
         principalmente a link connessi fisicamente, come con un cavo seriale
         cablato tra un computer portatile e un altro computer.  Il collegamento
         dovrebbe essere fisico poichè SLIP a tutt'oggi non offre
         una capacità di chiamata remota; questa caratteristica è
         fornita dall'utility PPP, che dovrebbe essere usata al posto
         di SLIP quando possibile.</para>
 
       <para>Se userai un modem, allora PPP è quasi certamente la tua
         unica scelta.  Assicurati di avere le informazioni del tuo provider
         a portata di mano che ti saranno richieste nel processo di
         installazione.</para>
 
       <para>Se usi PAP o CHAP per la connessione al tuo ISP (in altre parole,
         se puoi connetterti all'ISP in &windows; senza usare uno script), allora
         tutto quello che dovrai fare è digitare
         <command>dial</command> nel prompt di <application>ppp</application>.
         Altrimenti, avrai bisogno di sapere come chiamare il tuo ISP usando
         <quote>comandi AT</quote> specifici del tuo modem, poichè
         PPP fornisce solo un semplice emulatore di terminale.  Per cortesia
         fai riferimento al <link linkend="userppp">manuale</link> per il
         ppp-utente e alle <ulink url="&url.books.faq;/ppp.html">FAQ</ulink>.
         Se hai problemi, puoi mandare i log a video usando il comando
         <command>set log local ...</command>.</para>
 
       <para>Se è disponibile una connessione fisica ad un altro FreeBSD
         (2.0-R o successivi), potresti considerare l'installazione via
         cavo parallelo <quote>laplink</quote>.  La velocità di
         trasferimento di dati via porta parallela è molto più
         alta rispetto a quella realizzabile via seriale (fino a
         50&nbsp;kbyte/sec), ottenendo quindi un'installazione rapida.</para>
 
       <para>Alla fine, per un'installazione più veloce possibile
         via rete, un adattatore Ethernet è sempre una buona scelta!
         FreeBSD supporta le più comuni schede di rete Ethernet per PC;
         una tabella di schede supportate (e i rispettivi settaggi richiesti)
         viene fornita nell'Hardware Note per ogni release di FreeBSD.
         Se usi una delle scheda PCMCIA Ethernet supportate, assicurati
         di inserirla <emphasis>prima</emphasis> di accendere il portatile!
         FreeBSD, sfortunatamente, non supporta ancora l'inserimento a caldo
         di una scheda PCMCIA durante l'installazione.</para>
 
       <para>Inoltre dovrai sapere il tuo indirizzo IP della rete, il valore
         della netmask per la tua classe di indirizzi, e il nome della tua
         macchina.  Se stai installando tramite una connessione PPP e non hai un
         IP statico, non temere, l'indirizzo IP può essere dinamicamente
         assegnato dal tuo ISP.  Il tuo amministratore di sistema ti dirà
         quali valori usare per il tuo setup di rete.  Se farai riferimento
         ad altri host tramite nomi piuttosto che tramite indirizzi IP, avrai
         bisogno di conoscere anche il server dns e forse anche l'indirizzo di
         un gateway (se stai usando PPP, è l'indirizzo IP del tuo
         provider) per poter comunicare con il server dns.  Se vuoi installare
         via FTP passando per un proxy HTTP, avrai bisogno anche dell'indirizzo
         del proxy.  Se non conosci tutte o in parte queste informazioni,
         dovrai parlare con il tuo amministratore di sistema o con l'ISP
         <emphasis>prima</emphasis> di tentare questo tipo di
         installazione.</para>
 
       <sect3>
         <title>Prima di Installare via  NFS</title>
 
         <indexterm>
           <primary>installazione</primary>
           <secondary>rete</secondary>
           <tertiary>NFS</tertiary>
         </indexterm>
 
         <para>L'installazione tramite NFS è abbastanza semplice.
           Devi copiare semplicemente i file della distribuzione interessata
           in un server NFS e quindi puntare il media al server NFS.</para>
 
         <para>Se questo server supporta solo <quote>porte privilegiate</quote>
           (come in genere succede nelle workstation di Sun), dovrai settare
           l'opzione <literal>NFS Secure</literal> nel menì
           <guimenu>Options</guimenu> prima di procedere con
           l'installazione.</para>
 
         <para>Se hai una scheda Ethernet di scarsa qualità con dei
           trasferimenti di rete molto lenti, potresti anche selezionare il
           flag <literal>NFS Slow</literal>.</para>
 
         <para>Affinchè l'installazione NFS abbia successo, il server
           deve supportare il mount di sotto directory, per esempio, se la
           directory della distribuzione di FreeBSD&nbsp;&rel.current;
           è in: <filename>ziggy:/usr/archive/stuff/FreeBSD</filename>,
           allora <hostid>ziggy</hostid> dovrà permettere il mount
           diretto di <filename>/usr/archive/stuff/FreeBSD</filename>,
           e non solo di <filename>/usr</filename> o di
           <filename>/usr/archive/stuff</filename>.</para>
 
         <para>Nel file <filename>/etc/exports</filename> di FreeBSD, questo
           comportamento è controllato dalle opzioni
           <option>-alldirs</option>.  Altri server NFS potrebbero avere
           diverse regole.  Se ottieni il messaggio
           <quote>permesso negato</quote> dal server, allora è
           probabile che non hai abilitato queste opzioni.</para>
       </sect3>
     </sect2>
   </sect1>
 </chapter>
diff --git a/ja_JP.eucJP/books/faq/book.xml b/ja_JP.eucJP/books/faq/book.xml
index e73c949b6d..5c0273a63f 100644
--- a/ja_JP.eucJP/books/faq/book.xml
+++ b/ja_JP.eucJP/books/faq/book.xml
@@ -1,15137 +1,15133 @@
 <?xml version="1.0" encoding="euc-jp"?>
 <!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
 	"../../../share/xml/freebsd45.dtd">
 
 <!-- The FreeBSD Japanese Documentation Project -->
 <!-- Original revision: 1.204 -->
 
 <book lang='ja'>
   <bookinfo>
     <title>FreeBSD 2.X¡¢3.X¡¢4.X ¤Ë¤Ä¤¤¤Æ¤Î FAQ (¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤ÎÅú¤¨)</title>
 
     <corpauthor>FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È</corpauthor>
 
     <copyright>
       <year>1995</year>
       <year>1996</year>
       <year>1997</year>
       <year>1998</year>
       <year>1999</year>
       <year>2000</year>
       <year>2001</year>
       <holder>FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È</holder>
     </copyright>
 
     &legalnotice;
 
     <releaseinfo>$FreeBSD$</releaseinfo>
 
     <abstract>
       <para>
         ¤³¤Îʸ½ñ¤Ï FreeBSD ¥·¥¹¥Æ¥à¡¦¥Ð¡¼¥¸¥ç¥ó 2.X¡¢3.X¡¢4.X ¤Ë¤Ä¤¤¤Æ¤Î FAQ ¤Ç¤¹¡£
         ÆäËÃǤï¤ê¤¬¤Ê¤¤¸Â¤ê¡¢¤É¤Î¹àÌܤâ FreeBSD 2.0.5 °Ê¹ß¤Î¤â¤Î¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£
         &lt;XXX&gt; ¤Î¤Ä¤¤¤Æ¤¤¤ë¹àÌܤϤޤÀºî¶ÈÃæ¤Î¤â¤Î¤Ç¤¹¡£
         ¤³¤Î FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È¤Ë¶¨ÎϤ·¤¿¤¤¤È»×¤ï¤ì¤ëÊý¤Ï¡¢
         &a.doc;
         ¤Þ¤Ç (±Ñ¸ì¤Ç) ÅŻҥ᡼¥ë¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
         ¤³¤Îʸ½ñ¤ÎºÇ¿·¥Ð¡¼¥¸¥ç¥ó¤Ï¡¢¤¤¤Ä¤Ç¤â
         <ulink url="http://www.jp.FreeBSD.org/">ÆüËܹñÆâÈÇ FreeBSD World Wide Web ¥µ¡¼¥Ð</ulink>¤ä
         <ulink url="http://www.FreeBSD.org/">FreeBSD World Wide Web ¥µ¡¼¥Ð</ulink>¤Ç
         ¸«¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
         ¤Þ¤¿¡¢¤Ò¤È¤Ä¤ÎµðÂç¤Ê <ulink url="book.html">HTML</ulink>
         ¥Õ¥¡¥¤¥ë¤È¤·¤Æ HTTP ¤Ç¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
         ¥×¥ì¡¼¥ó¥Æ¥­¥¹¥È¡¢PostScript¡¢PDF¡¢¤ª¤è¤Ó¤½¤Î¾¤Î·Á¼°¤Î¤â¤Î¤Ï
         <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">FreeBSD
           FTP ¥µ¡¼¥Ð</ulink>¤ËÃÖ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
         ¤Þ¤¿¡¢<ulink url="http://www.FreeBSD.org/search/search.html">FAQ
           ¤Î¸¡º÷</ulink>¤â²Äǽ¤Ç¤¹¡£</para>
 
       <para>
         <note>
           <para>2005 ǯ 6 ·î¸½ºß¡¢HTML Èǰʳ°¤ÎÆüËܸì FAQ ¤ÏÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£</para>
         </note>
       </para>
 
       <para>
         ÆüËܸìÈǤκîÀ®¤Ï FreeBSD ÆüËܸì¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È¤¬
         ¥ª¥ê¥¸¥Ê¥ë¤Î±Ñ¸ìÈǤò¤â¤È¤Ë¤·¤Æ¹Ô¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
         FreeBSD FAQ ÆüËܸìÌõ¤ª¤è¤Ó¡¢ FreeBSD FAQ ÆüËܸìÈǤΤߤ˴ØÏ¢¤¹¤ë¤³¤È¤Ï¡¢
         &a.jp.doc-jp; ¤Ë¤ª¤¤¤ÆÆüËܸì¤ÇµÄÏÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
         ɬÍפ˱þ¤¸¤ÆÆüËܸì¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È¤«¤é¡¢
         FreeBSD Documentation Project ¤ËÂФ·¤Æ¥Õ¥£¡¼¥É¥Ð¥Ã¥¯¤ò¹Ô¤Ê¤¤¤Þ¤¹¤Î¤Ç¡¢
         ±Ñ¸ì¤¬ÆÀ°Õ¤Ç¤Ê¤¤Êý¤Ï
         &a.jp.doc-jp; ¤Þ¤ÇÆüËܸì¤Ç¥³¥á¥ó¥È¤ò¤ª´ó¤»¤¯¤À¤µ¤¤¡£</para>
 
       <para>¤Þ¤¿¡¢¤³¤Î FreeBSD FAQ ¤È¤ÏÊ̤ˡ¢ÆüËܤΠFreeBSD ¥æ¡¼¥¶Í­»Ö¤Ë¤è¤Ã¤Æ
         &a.jp.users-jp;
         ¤ä¥Ë¥å¡¼¥¹¥°¥ë¡¼¥×
         <ulink url="news:fj.os.bsd.freebsd">fj.os.bsd.freebsd</ulink>
         ¤Ê¤É¤Ø¤ÎÅê¹Æ¤ò¤â¤È¤ËºîÀ®¤µ¤ì¤¿
         <ulink url="http://www.jp.FreeBSD.org/QandA/">QandA</ulink>
         ¤¬¸ø³«¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
         ÆäËÆüËܸì´Ä¶­¤Ê¤ÉÆüËܸÇÍ­¤ÎÏÃÂ꤬½¼¼Â¤·¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢
         ¤³¤Á¤é¤â¹ç¤ï¤»¤Æ¤´Í÷¤¯¤À¤µ¤¤¡£</para>
     </abstract>
   </bookinfo>
 
   <preface id="preface">
     <title>¤Þ¤¨¤¬¤­</title>
 
     <para>
       <emphasis>Ìõ:
         &a.kuriyama;¡¢
         &a.hanai;¡¢
         &a.jp.nakai;¡¢
         &a.motoyuki;¡¢
         &a.jp.sugimura;¡¢
         1997 ǯ 11 ·î 5 Æü
       </emphasis>
     </para>
 
     <para>
       FreeBSD 2.X-4.X FAQ ¤Ø¤è¤¦¤³¤½!
     </para>
 
     <para>
       Usenet ¤Î FAQ ¤¬¤½¤¦¤Ç¤¢¤ë¤è¤¦¤Ë¡¢
       ¤³¤Îʸ½ñ¤â FreeBSD ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ë´Ø¤·¤Æ
       ÉÑÈˤ˿Ҥͤé¤ì¤ë¼ÁÌä¤òÌÖÍ夹¤ë¤³¤È¤òÌÜŪ¤È¤·¤Æ¤¤¤Þ¤¹
       (¤â¤Á¤í¤ó¤½¤ì¤ËÂФ¹¤ëÅú¤¨¤â!)¡£
       FAQ ¤ÏËÜÍè¥Ð¥ó¥ÉÉý¤ò¸º¤é¤·¡¢
       Ʊ¤¸¼ÁÌ䤬²¿Å٤ⷫ¤êÊÖ¤µ¤ì¤ë¤Î¤òÈò¤±¤ë¤¿¤á¤Ëºî¤é¤ì¤¿¤â¤Î¤Ç¤¹¤¬¡¢
       ºÇ¶á¤ÏÍ­ÍѤʾðÊ󸻤ȸ«¤Ê¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤­¤Þ¤·¤¿¡£
     </para>
 
     <para>
       ¤³¤Î FAQ ¤ò¤Ç¤­¤ë¸Â¤êÍ­ÍѤʤâ¤Î¤Ë¤·¤è¤¦¤È¡¢
       ¤¢¤é¤æ¤ëÅØÎϤ¬¤Ï¤é¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
       ¤â¤·²¿¤«¤·¤é¤Î²þÁ±°Æ¤¬É⤫¤ó¤À¤é¡¢¤¼¤Ò
       &a.faq; ¤Þ¤Ç¥á¡¼¥ë¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="what-is-FreeBSD">
           <para>FreeBSD ¤Ã¤Æ²¿?</para>
         </question>
 
         <answer>
           <para>FreeBSD ¤È¤Ï°ì¸À¤Ç¸À¤¨¤Ð¡¢¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³Ø¥Ð¡¼¥¯¥ì¥¤¹»¤«¤é
             ¥ê¥ê¡¼¥¹¤µ¤ì¤¿ <quote>4.4BSD-Lite</quote> ¤È <quote>4.4BSD-Lite2</quote> ¤Ë¤è¤ë
             ¶¯²½¤Î°ìÉô¤ËͳÍ褹¤ë¡¢
             i386 ¤ª¤è¤Ó Alpha/AXP ·Ï¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸þ¤±¤Î
             UN*X ¥é¥¤¥¯¤Ê¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ç¤¹¡£
             ´ÖÀÜŪ¤Ë¤ÏƱ¤¸¥Ð¡¼¥¯¥ì¥¤¹»¤Î <quote>Net/2</quote> ¤ò William Jolitz ¤¬
             i386 ·Ï¤Ë°Ü¿¢¤·¤¿ <quote>386BSD</quote> ¤â´ð¤Ë¤·¤Æ¤¤¤Þ¤¹¤¬¡¢
             386BSD ¤Î¥³¡¼¥É¤Ï¤Û¤È¤ó¤É»Ä¤Ã¤Æ¤¤¤Þ¤»¤ó¡£
             FreeBSD ¤Ë¤Ä¤¤¤Æ¤Î¾ÜºÙ¤È¡¢²¿¤¬¤Ç¤­¤ë¤«¤Ë¤Ä¤¤¤Æ¤Ï
             <ulink url="http://www.FreeBSD.org/">FreeBSD ¤Î¥Û¡¼¥à¥Ú¡¼¥¸</ulink>
             ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             FreeBSD ¤Ï´ë¶È¤ä¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥µ¡¼¥Ó¥¹¥×¥í¥Ð¥¤¥À¡¢¸¦µæ¼Ô¡¢
             ¥³¥ó¥Ô¥å¡¼¥¿ÀìÌç²È¡¢³ØÀ¸¡¢²ÈÄí¤Î¥æ¡¼¥¶¤Ê¤É¤Ë¤è¤ê¡¢¶È̳¤ä¶µ°é¡¢
             ¸ä³Ú¤ËÍѤ¤¤é¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤é¤Ë´Ø¤·¤Æ¤Ï
             <ulink url="http://www.FreeBSD.org/gallery/gallery.html"
                    >FreeBSD ¥®¥ã¥é¥ê¡¼</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             FreeBSD ¤Ë´Ø¤¹¤ë¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï
             <ulink url="../handbook/index.html">FreeBSD
             ¥Ï¥ó¥É¥Ö¥Ã¥¯</ulink>¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="FreeBSD-goals">
           <para>FreeBSD ¤¬Ìܻؤ·¤Æ¤¤¤ë¤â¤Î</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¥×¥í¥¸¥§¥¯¥È¤ÎÌÜŪ¤Ï¡¢
             ¤¤¤«¤Ê¤ëÍÑÅӤˤâ»ÈÍѤǤ­¡¢
             ²¿¤éÀ©¸Â¤Î¤Ê¤¤¥½¥Õ¥È¥¦¥§¥¢¤ò¶¡µë¤¹¤ë¤³¤È¤Ç¤¹¡£
             »ä¤¿¤Á¤Î¿¤¯¤Ï¡¢
             ¥³¡¼¥É (¤½¤·¤Æ¥×¥í¥¸¥§¥¯¥È) ¤ËÂФ·¤Æ¤«¤Ê¤ê¤ÎÅê»ñ¤ò¤·¤Æ¤­¤Æ¤ª¤ê¡¢
             ¤³¤ì¤«¤é¤â¿¾¯¤ÎÂå½þ¤Ï¤¢¤Ã¤Æ¤âÅê»ñ¤ò³¤±¤Æ¹Ô¤¯¤Ä¤â¤ê¤Ç¤¹¡£
             ¤¿¤À¡¢Â¾¤Î¿Íã¤Ë¤âƱ¤¸¤è¤¦¤ÊÉéô¤ò¤¹¤ë¤è¤¦¤Ë¼çÄ¥¤·¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             FreeBSD ¤Ë¶½Ì£¤ò»ý¤Ã¤Æ¤¤¤ë°ì¿Í»Ä¤é¤º¤¹¤Ù¤Æ¤Î¿Í¡¹¤Ë¡¢
             ÌÜŪ¤ò¸ÂÄꤷ¤Ê¤¤¤Ç¥³¡¼¥É¤òÄ󶡤¹¤ë¤³¤È¡£
             ¤³¤ì¤¬¡¢
             »ä¤¿¤Á¤ÎºÇ½é¤Î¤½¤·¤ÆºÇÂç¤Î¡ÖǤ̳¡×¤Ç¤¢¤ë¤È¿®¤¸¤Æ¤¤¤Þ¤¹¡£
             ¤½¤¦¤¹¤ì¤Ð¡¢¥³¡¼¥É¤Ï²Äǽ¤Ê¸Â¤ê¹­¤¯»È¤ï¤ì¡¢
             ºÇÂç¤Î²¸·Ã¤ò¤â¤¿¤é¤¹¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£
             ¤³¤ì¤¬¡¢»ä¤¿¤Á¤¬Ç®Îõ¤Ë»Ù»ý¤·¤Æ¤¤¤ë¥Õ¥ê¡¼¥½¥Õ¥È¥¦¥§¥¢¤ÎºÇ¤â´ðËÜŪ¤ÊÌÜŪ¤Ç¤¢¤ë¤È¡¢
             »ä¤Ï¿®¤¸¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             »ä¤¿¤Á¤Î¥½¡¼¥¹¥Ä¥ê¡¼¤Ë´Þ¤Þ¤ì¤ë¥½¡¼¥¹¤Î¤¦¤Á¡¢GNU
             °ìÈ̸øÍ­»ÈÍѵöÂú (GPL) ¤Þ¤¿¤Ï GNU ¥é¥¤¥Ö¥é¥ê
             °ìÈ̸øÍ­»ÈÍѵöÂú (LGPL) ¤Ë½¾¤Ã¤Æ¤¤¤ë¤â¤Î¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             ¿¾¯À©¸Â¤¬²Ê¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤¿¤À¤·¡¢
             ¥½¡¼¥¹¥³¡¼¥É¤Ø¤Î¥¢¥¯¥»¥¹¤ÎÊݾڤȤ¤¤¦¡¢
             °ìÈ̤ÎÀ©¸Â¤È¤Ï¤¤¤ï¤ÐµÕ¤ÎÀ©¸Â¤Ç¤¹¡£
             ¤¿¤À¤· GPL ¥½¥Õ¥È¥¦¥§¥¢¤ò¾¦ÍѤÇÍøÍѤ¹¤ë¾ì¹ç¡¢
             ¤µ¤é¤ËÊ£»¨¤Ë¤Ê¤ë¤Î¤ÏÈò¤±¤é¤ì¤Þ¤»¤ó¡£
             ¤½¤Î¤¿¤á¡¢¤½¤ì¤é¤Î¥½¥Õ¥È¥¦¥§¥¢¤ò¡¢¤è¤êÀ©¸Â¤Î¾¯¤Ê¤¤
             BSD Ãøºî¸¢¤Ë½¾¤Ã¤¿¥½¥Õ¥È¥¦¥§¥¢¤ÇÃÖ¤­´¹¤¨¤ëÅØÎϤò¡¢
             ²Äǽ¤Ê¸Â¤êÆü¡¹Â³¤±¤Æ¤¤¤Þ¤¹¡£
           </para>
 
             <note>
               <title>ÌõÃí</title>
               <para>
                 GPL ¤Ç¤Ï¡¢¡Ö¥½¡¼¥¹¥³¡¼¥É¤ò¼ÂºÝ¤Ë¼õ¤±¼è¤ë¤«¡¢
                 ¤¢¤ë¤¤¤Ï´õ˾¤·¤µ¤¨¤¹¤ì¤Ð¤½¤ì¤òÆþ¼ê¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¢¤ë¤³¤È¡×¤òµá¤á¤Æ¤¤¤Þ¤¹¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="why-called-FreeBSD">
           <para>¤É¤¦¤·¤Æ FreeBSD ¤È¸Æ¤Ð¤ì¤Æ¤¤¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             <itemizedlist>
               <listitem>
                 <para>̵ÎÁ (free) ¤Ç»È¤¦¤³¤È¤¬¤Ç¤­¤ë (¾¦ÍøÍѤâ´Þ¤à)¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î´°Á´¤Ê¥½¡¼¥¹¥³¡¼¥É¤¬¼«Í³ (freely) ¤Ë¼ê¤ËÆþ¤ê¡¢
                   ¾¦ÍøÍÑ¡¦Èó¾¦ÍøÍѤˤ«¤«¤ï¤é¤º¡¢ºÇÄã¸Â¤ÎÀ©¸Â¤Ç¾¤Î»Å»ö¤Ø¤ÎÍøÍÑ¡¢ÇÛÉÛ¡¢Æ³Æþ¤¬²Äǽ¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>²þÎɤä¥Ð¥°¥Õ¥£¥Ã¥¯¥¹¤¬¤¢¤ë¾ì¹ç¡¢
                   ï¤Ç¤â (free) ¤½¤Î¥³¡¼¥É¤òÄó½Ð¤Ç¤­¡¢
                   ¥½¡¼¥¹¥Ä¥ê¡¼¤Ë²Ã¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹
                   (¤¤¤¯¤Ä¤«¤Î´Êñ¤Ê¾ò·ï¤Ë¤Ï½¾¤Ã¤Æ¤â¤é¤¤¤Þ¤¹)¡£</para>
               </listitem>
 
             </itemizedlist>
           </para>
 
           <para>
             Êì¹ñ¸ì¤¬±Ñ¸ì¤Ç¤Ê¤¤ÆɼԤΤ¿¤á¤Ë¡¢¤³¤³¤Ç¤Ï <quote>free</quote>
             ¤È¤¤¤¦Ã±¸ì¤¬Æó¤Ä¤Î°ÕÌ£¤ÇÍѤ¤¤é¤ì¤Æ¤¤¤ë¤³¤È¤ò»ØŦ¤·¤Æ¤ª¤¯¤Èʬ¤«¤ê¤ä¤¹¤¤¤«¤âÃΤì¤Þ¤»¤ó¡£
             ¤Ò¤È¤Ä¤Ï¡Ö̵ÎÁ¤Ç¤¢¤ë¡×¤È¤¤¤¦¤³¤È¡¢
             ¤â¤¦¤Ò¤È¤Ä¤Ï¡Ö¼«Ê¬¤Î¤ä¤ê¤¿¤¤¤è¤¦¤Ë¤Ç¤­¤ë¡×¤È¤¤¤¦¤³¤È¤Ç¤¹¡£
             FreeBSD ¤Î¥³¡¼¥É¤Ç<emphasis>¤Ç¤­¤Ê¤¤</emphasis>¤¤¤¯¤Ä¤«¤Î¤³¤È
             (¼«Ê¬¤¬½ñ¤¤¤¿¤â¤Î¤À¤Èµ¶¤ë¤Ê¤É) ¤ò½ü¤±¤Ð¡¢
             ¤¢¤Ê¤¿¤Ï¼«Ê¬¤Î¤ä¤ê¤¿¤¤¤³¤È¤ò¤ä¤ë¤³¤È¤¬²Äǽ¤Ê¤Î¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="latest-version">
           <para>FreeBSD ¤ÎºÇ¿·¥Ð¡¼¥¸¥ç¥ó¤Ï?</para>
         </question>
         <answer>
 
           <para>
             <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.3-RELEASE/">4.3</ulink>
             ¤¬ºÇ¿·¤Î <emphasis>STABLE</emphasis> ¥Ð¡¼¥¸¥ç¥ó¤Ç¡¢
             2001 ǯ 4 ·î¤Ë¥ê¥ê¡¼¥¹¤µ¤ì¤Þ¤·¤¿¡£
             ¤Þ¤¿¡¢¤³¤ì¤ÏºÇ¿·¤Î <emphasis>RELEASE</emphasis>
             ¥Ð¡¼¥¸¥ç¥ó¤Ç¤â¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ´Êñ¤Ë¸À¤Ã¤Æ¤·¤Þ¤¦¤È¡¢<emphasis>-STABLE</emphasis>
             ¤ÏºÇ¿·¤Î <emphasis>-CURRENT</emphasis>
             ¤Î¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Î¤¹¤Ð¤é¤·¤¤¿·µ¡Ç½¤Î¿ô¡¹¤è¤ê¤â¡¢
             °ÂÄêÀ­¤ÈÊѹ¹²ó¿ô¤Î¾¯¤Ê¤µ¤ò¹¥¤à ISP ¤ä¡¢
             ¾¤Î´ë¶È¤Î¥æ¡¼¥¶¤ò¥¿¡¼¥²¥Ã¥È¤Ë¤·¤Æ¤¤¤Þ¤¹¡£
             ¥ê¥ê¡¼¥¹¤Ï¤³¤ÎÆó¼ïÎà¤Î¥Ö¥é¥ó¥Á¤Ç¹Ô¤Ê¤ï¤ì¤Þ¤¹¤¬¡¢
             (<emphasis>-STABLE</emphasis> ¤ÈÈæ³Ó¤¹¤ë¤È¿¾¯)
             ÉÔ°ÂÄê¤ÊÆ°ºî¤¬¤¢¤ë¤È¤¤¤¦¤³¤È¤òµöÍƤǤ­¤ë¤Ê¤é¡¢
             ɬÍפȤʤë¤Î¤Ï <emphasis>-CURRENT</emphasis> ¤ÎÊý¤À¤±¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ³Æ¥ê¥ê¡¼¥¹¤Ï<link linkend="release-freq">
               ¿ô¥«·îËè</link>¤Ë¤·¤«¹Ô¤Ê¤ï¤ì¤Þ¤»¤ó¡£
             ¿¤¯¤Î¿Í¡¹¤¬ FreeBSD ¤Î¥½¡¼¥¹¤ò¤½¤Î¥ê¥ê¡¼¥¹¤è¤ê¤â
             ºÇ¿·¤Î¾õÂ֤˰ݻý¤·¤Æ¤¤¤ë
             (<link linkend="current">FreeBSD-current</link> ¤È
             <link linkend="stable">FreeBSD-stable</link>
             ¤Ë´Ø¤¹¤ë¼ÁÌä¤â»²¾È¤·¤Æ¤¯¤À¤µ¤¤) ¤Î¤Ç¤¹¤¬¡¢
             ¥½¡¼¥¹¤È¤¤¤¦¤Î¤Ï¾ï¤Ë²þÊѤµ¤ì³¤±¤Æ¤¤¤ë¤¿¤á¡¢
             ¤½¤¦¤¹¤ë¤³¤È¤Ï°ì¼ï¤Î´·Îã¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="current">
           <para>FreeBSD-CURRENT¤Ã¤Æ²¿?</para>
         </question>
 
         <answer>
           <para>
             <ulink url="../handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink>
             ¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î³«È¯¥Ð¡¼¥¸¥ç¥ó¤Ç¡¢
             ¤ä¤¬¤Æ 5.0-RELEASE ¤È¤Ê¤ê¤Þ¤¹¡£¤è¤Ã¤Æ¤³¤ì¤Ï¡¢¤½¤³¤Ë·È¤ï¤Ã¤Æ¤¤¤ë³«È¯¼Ô¤ä¡¢
             ¤É¤ó¤Ê¾ã³²¤ò¤â¾è¤ê±Û¤¨¤Æ¤¤¤±¤ë¥¿¥Õ¤Ê°¦¹¥²È¤¿¤Á¤Ë¤È¤Ã¤Æ¤Î¤ß¶½Ì£¤ÎÂоݤȤʤë¤â¤Î¤Ç¤¹¡£
             -CURRENT ¤Î»ÈÍѤ˺ݤ·¤Æ¤Î¾ÜºÙ¤Ï
             <ulink url="../handbook/index.html">FreeBSD ¥Ï¥ó¥É¥Ö¥Ã¥¯</ulink>
             ¤Î
             <ulink url="../handbook/cutting-edge.html#CURRENT">´ØÏ¢¤¹¤ë¥»¥¯¥·¥ç¥ó</ulink>
             ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ËÆëÀ÷¤ß¤¬¤Ê¤¤¾ì¹ç¤ä¡¢
             ¤½¤ì¤¬°ì»þŪ¤ËȯÀ¸¤·¤Æ¤¤¤ëÌäÂê¤Ê¤Î¤«¡¢
             ¤½¤ì¤È¤âËܼÁŪ¤ÊÌäÂ꤫¤ò¸«¶Ë¤á¤ëǽÎϤ¬¤Ê¤¤¾ì¹ç¤Ï¡¢
             FreeBSD-CURRENT ¤ò»È¤¦¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¤³¤Î¥Ö¥é¥ó¥Á¤Ï»þ¡¹µÞ·ã¤Ë³ÈÄ¥¤µ¤ì¤¿¤ê¡¢
             ¥·¥¹¥Æ¥à¤¬¹½ÃۤǤ­¤Ê¤¤¾õÂ֤ˤʤ뤳¤È¤â¤·¤ç¤Ã¤Á¤å¤¦¤¢¤ê¤Þ¤¹¡£
             FreeBSD-CURRENT ¤ò»È¤¦¿Í¤ÏÌäÂê¤òʬÀϤ·¡¢
             ¡Ö¾®¤µ¤Ê·ç´Ù¡×¤Ç¤Ï¤Ê¤¯¡¢
             ÌÀ¤é¤«¤Ë´Ö°ã¤¤¤Ç¤¢¤ë¤È»×¤ï¤ì¤ë¤â¤Î¤À¤±¤òÊó¹ð¤Ç¤­¤ë¤â¤Î¤ÈÁÛÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¡Ömake world ¤·¤¿¤é group ´Ø·¸¤Ç¥¨¥é¡¼¤¬¤Ç¤Þ¤·¤¿¡×¤Î¤è¤¦¤Ê¼ÁÌä¤Ï¡¢
             -CURRENT ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ç¤Ï·ÚÊΤδ㺹¤·¤Ç¤¢¤·¤é¤ï¤ì¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>ËèÆü¡¢¤½¤Î»þÅÀ¤Î -CURRENT ¤È -STABLE ¤Î¥³¡¼¥É¤ò¸µ¤Ë
             <ulink url="http://www.FreeBSD.org/releases/snapshots.html">snapshot</ulink>
             ¤¬ºîÀ®¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¸½ºß¤Ï¡¢¤½¤Î snapshot ¤ÎÇÛÉÛ¤âÍøÍѲÄǽ¤Ç¤¹¡£
             ¤½¤ì¤¾¤ì¤Î snapshot ¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤ÊÌÜŪ¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             <itemizedlist>
 
               <listitem>
                 <para>¥¤¥ó¥¹¥È¡¼¥ë¥×¥í¥°¥é¥à¤ÎºÇ¿·ÈǤΥƥ¹¥È¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   »î¤·¤Æ¤ß¤¿¤¤¤±¤ì¤É¡¢
                   ´ðÁÃŪ¤Ê½ê¤«¤éËèÆüÊѤï¤ë¤è¤¦¤Ê¤â¤Î¤òÄɤ¤¤«¤±¤ë»þ´Ö¤â¥Ð¥ó¥ÉÉý¤â̵¤¤¡¢
                   ¤È¤¤¤¦¿Í¤Ë¤â -CURRENT ¤ä -STABLE ¤ò»È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¡£
                   ¤Þ¤¿¡¢¤½¤Î¤è¤¦¤Ê¿Í¤¿¤Á¤Î¥·¥¹¥Æ¥à°Ü¹Ô¤Î¤¿¤á¤Î¼ê¤Ã¼è¤êÁᤤÊýË¡¤òÄ󶡤¹¤ë¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   ¤¢¤È¤Ç¤È¤ó¤Ç¤â¤Ê¤¤¤³¤È¤ò¤·¤Æ¤·¤Þ¤Ã¤¿»þ¤Î¤¿¤á¤Ë¡¢
                   ÌäÂê¤È¤Ê¤ë¥³¡¼¥É¤ÎÆÃÄê¤Î»²¾È´ð½àÅÀ¤òÊݸ¤·¤Æ¤ª¤¯¡£
                   (Ä̾ï¤Ï CVS ¤¬¤³¤¦¤¤¤¦¥Ï¥×¥Ë¥ó¥°¤Î¤è¤¦¤Ê¶²¤í¤·¤¤»öÂÖ¤òËɻߤ·¤Æ
                   ¤¤¤ë¤ó¤Ç¤¹¤±¤É¤Í :)
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   ¥Æ¥¹¥È¤¬É¬Íפʿ·¤·¤¤µ¡Ç½¤ò¡¢
                   ¤Ç¤­¤ë¸Â¤ê¿¤¯¤Î±£¤ì¥Æ¥¹¥¿¡¼¤Ë»î¤·¤Æ¤â¤é¤¦¡£</para>
               </listitem>
 
             </itemizedlist>
           </para>
 
           <para>
             ¤É¤ó¤ÊÌÜŪ¤Ç¤¢¤ì¡¢-CURRENT snapshot ¤¬
             <quote>À½ÉÊ¥ì¥Ù¥ë¤ÎÉʼÁ</quote>
             ¤Ç¤¢¤ë¤È¤Î¹Í¤¨¤Ë´ð¤Å¤¯Í×µá¤Ï¹Ô¤ï¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£
             °ÂÄêÀ­¤ä¥Æ¥¹¥È½½Ê¬À­¤Ë¤³¤À¤ï¤ë¿Í¤Ï¡¢
             ´°Á´¤Ê¥ê¥ê¡¼¥¹¡¢¤¢¤ë¤¤¤Ï -STABLE snapshot ¤«¤éÎ¥¤ì¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¥ê¥ê¡¼¥¹¤Ï¡¢5.0-CURRENT ¤¬
             <ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/"
                    >ftp://current.FreeBSD.org/pub/FreeBSD/</ulink>
             ¤«¤é¡¢4-STABLE ¤¬
             <ulink url="ftp://releng4.FreeBSD.org/pub/FreeBSD"
                    >releng4.FreeBSD.org</ulink>
             ¤«¤éľÀÜÆþ¼ê²Äǽ¤Ç¤¹¡£
             ¤Þ¤¿¡¢3-STABLE ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ï¡¢
             ¤³¤Îʸ¾Ï¤Î¼¹É®»þÅÀ (2000 ǯ 5 ·î)
             ¤ÇºîÀ®¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£</para>
 
           <para>¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¥ê¥ê¡¼¥¹¤Ï¡¢
             ¸½ºß¡¢³«È¯¤äÊݼéºî¶È¤¬¹Ô¤Ê¤ï¤ì¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¥Ö¥é¥ó¥Á¤Ë¤ª¤¤¤Æ¡¢
             Ê¿¶Ñ¤·¤Æ°ìÆü°ì²óºîÀ®¤µ¤ì¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="stable">
           <para>FreeBSD-STABLE ¤Î¥³¥ó¥»¥×¥È¤Ï²¿¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 2.0.5 ¤¬¥ê¥ê¡¼¥¹¤µ¤ì¤¿¸å¡¢»ä¤¿¤Á¤Ï FreeBSD ¤Î³«È¯¤ò
             2 ·ÏÅý¤Ëʬ³ä¤¹¤ë¤³¤È¤Ë¤·¤Þ¤·¤¿¡£
             °ì¤Ä¤Ï <ulink url="../handbook/stable.html">-STABLE</ulink>
             ¤È¤¤¤¦¥Ö¥é¥ó¥Á¤Ç¡¢¥Ð¥°¤Î½¤Àµ¤Ï¤·¤Ã¤«¤ê¥Æ¥¹¥È¤µ¤ì¡¢
             µ¡Ç½¤Î¶¯²½¤Ï¾¯¤·¤º¤Ä¤·¤«¹Ô¤ï¤ì¤Þ¤»¤ó
             (µÞ¤ÊÊѹ¹¤ä¼Â¸³Åªµ¡Ç½¤ò˾¤Þ¤Ê¤¤¡¢
             ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥µ¡¼¥Ó¥¹¥×¥í¥Ð¥¤¥À¤ä±ÄÍø´ë¶È¸þ¤±)¡£
             ¤â¤¦°ìÊý¤Î¥Ö¥é¥ó¥Á¤Ï
             <ulink url="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>
             ¤Ç¡¢2.0 ¤¬¥ê¥ê¡¼¥¹¤µ¤ì¤Æ°ÊÍè
             5.0-RELEASE (¤½¤·¤Æ¤½¤Î¸å¤â) ¤Ø¸þ¤±¤ÆÌ®¡¹¤È³¤¤¤Æ¤¤¤ë¤â¤Î¤Ç¤¹¡£
             ASCII ¤ÇÉÁ¤¤¤¿´Êñ¤Ê¿Þ¤¬¤ï¤«¤ê¤ä¤¹¤¤¤«¤Ï¼«¿®¤¬¤¢¤ê¤Þ¤»¤ó¤¬¡¢
             ¤³¤ó¤Ê´¶¤¸¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>                 2.0
                   |
                   |
                   |  [2.1-STABLE]
  *BRANCH*       2.0.5 -&gt; 2.1 -&gt; 2.1.5 -&gt; 2.1.6 -&gt; 2.1.7.1  [2.1-STABLE ½ªÎ»]
                   |                         (1997/03)
                   |
                   |
                   |  [2.2-STABLE]
  *BRANCH*       2.2.1 -&gt; 2.2.2-RELEASE -&gt; 2.2.5 -&gt; 2.2.6 -&gt; 2.2.7 -&gt; 2.2.8 [½ªÎ»]
                   |         (1997/03)     (1997/10)   (1998/04)   (1998/07)   (1998/12)
                   |
                   |
                3.0-SNAPs  (1997 ǯÂè°ì»ÍȾ´ü³«»Ï)
                   |
                   |
                3.0-RELEASE (1998/10)
                   |
                   |  [3.0-STABLE]
  *BRANCH*      3.1-RELEASE  (1999/02) -&gt; 3.2 -&gt; 3.3 -&gt; 3.4 -&gt; 3.5 -&gt; 3.5.1
                   |                   (1999/05) (1999/09) (1999/12) (2000/06) (2000/07)
                   |  [4.0-STABLE]
  *BRANCH*        4.0  (2000/03) -&gt;4.1 -&gt; 4.1.1 -&gt; 4.2 -&gt; 4.3 -&gt; ... ¾­Íè¤Î 4.x ¥ê¥ê¡¼¥¹ ...
                   |
                   |             (2000/07)   (2000/09)   (2000/11)
                   |
                  \|/
                   +
           [5.0-CURRENT ¤È¤·¤Æ·Ñ³Ãæ]</programlisting>
 
           <para>
             -CURRENT ¥Ö¥é¥ó¥Á¤Ï
             5.0 ¤È¤½¤ÎÀè¤Ø¸þ¤±¤Æ¤æ¤Ã¤¯¤ê¤È¿Ê²½¤ò³¤±¤Æ¤¤¤Þ¤¹¡£
             ½¾Í褢¤Ã¤¿ 2.2-STABLE ¥Ö¥é¥ó¥Á¤Ï 2.2.8 ¤Î¥ê¥ê¡¼¥¹¤ò¤â¤Ã¤Æ½ªÎ»¤·¤Þ¤·¤¿¡£
             3-STABLE ¤¬¤½¤ì¤ËÂå¤ï¤ê¡¢2000 ǯ 7 ·î¤Ë
             3.5.1-RELEASE (ºÇ¸å¤Î 3.X ¥ê¥ê¡¼¥¹)
             ¤¬¥ê¥ê¡¼¥¹¤µ¤ì¤Þ¤·¤¿¡£
             2000 ǯ 3 ·î (3.5 ¤Î¸ø³«Á°¤Ë¤Ê¤ê¤Þ¤¹¤¬) ¤Ë¤Ï¡¢
             3-STABLE ¥Ö¥é¥ó¥Á¤Ï¤Û¤Ü¡¢4-STABLE ¥Ö¥é¥ó¥Á¤Ë¤è¤Ã¤ÆÃÖ¤­´¹¤¨¤é¤ì¤Þ¤·¤¿¡£
             4.3-RELEASE ¤Ï 2001 ǯ 4 ·î¤Ë¥ê¥ê¡¼¥¹¤µ¤ì¤Þ¤·¤¿¡£
             4-STABLE ¤Ï¸½ºß -STABLE ¥Ö¥é¥ó¥Á¤Ç³èȯ¤Ë³«È¯¤¬Â³¤±¤é¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢
             3-STABLE ¤Ø¤Î¥Ð¥°¤Î½¤Àµ (¤Û¤È¤ó¤É¤¬¥»¥­¥å¥ê¥Æ¥£´ØÏ¢¤Î¤â¤Î)
             ¤â¤Þ¤À¹Ô¤Ê¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
             3.X ¥Ö¥é¥ó¥Á¤Ï 2000 ǯ¤Î²Æ¤Ë¤Ï¸ø¼°¤Ë³«È¯¤¬½ªÎ»¤¹¤ëͽÄê¤Ç¤¹¡£
             ¸½ºß¤Î <quote>current branch</quote> ¤Ï 5.0-CURRENT ¤Ç¤¢¤ê¡¢
             ºÇ½é¤Î 5.0 ·ÏÎó¤Î¥ê¥ê¡¼¥¹Í½Äê¤Ï¤Þ¤À·èÄꤷ¤Æ¤¤¤Þ¤»¤ó¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="release-freq">
           <para>FreeBSD ¤Î¥ê¥ê¡¼¥¹¤Ï¤¤¤Äºî¤é¤ì¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¥³¥¢¥Á¡¼¥à¤Ï¸¶Â§Åª¤Ë¡¢
             ¿·¤·¤¤µ¡Ç½¤ä¥Ð¥°¥Õ¥£¥Ã¥¯¥¹¤¬½¼Ê¬½¸¤Þ¤ê¡¢
             ¥ê¥ê¡¼¥¹¤Î°ÂÄêÀ­¤ò»¤Ê¤¦¤³¤È¤¬Ìµ¤¤¤è¤¦¡¢
             ¤µ¤Þ¤¶¤Þ¤ÊÊѹ¹¤¬½½Ê¬¤Ë°ÂÄꤷ¤Æ¤¤¤ë¤È¤¤¤¦¾ò·ï¤òËþ¤¿¤·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Î¤ß¡¢
             ¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤Î FreeBSD ¤ò¥ê¥ê¡¼¥¹¤·¤Þ¤¹¡£
             ¤¿¤È¤¨¤³¤ÎÍÑ¿´¿¼¤µ¤¬¿·¤·¤¤µ¡Ç½¤¬»È¤¨¤ë¤è¤¦¤Ë¤Ê¤ë¤³¤È¤ò
             ÂÔ¤Á˾¤ó¤Ç¤¤¤ë¥æ¡¼¥¶¤òÍßµáÉÔËþ¤Ë¤µ¤»¤ë¤È¤·¤Æ¤â¡¢
             ¿¤¯¤Î¥æ¡¼¥¶¤Ï¤³¤Î¤³¤È¤ò FreeBSD
             ¤ÎºÇ¤âÎɤ¤½ê¤Î°ì¤Ä¤À¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>¥ê¥ê¡¼¥¹¤ÎºîÀ®¤Ï¡¢Ê¿¶ÑŪ¤Ë¸À¤Ã¤Æ¤ª¤è¤½ 4 ¥ö·î¤´¤È¤Ë¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£</para>
 
           <para>¤â¤¦¾¯¤·»É·ã¤¬Íߤ·¤¤ (¤¢¤ë¤¤¤ÏÂÔ¤Á±ó¤·¤¤) Êý¡¹¸þ¤±¤Ë¤Ï¡¢
             ËèÆü¥Ð¥¤¥Ê¥ê¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤¬ºîÀ®¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¾åµ­¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="available-platforms">
           <para>FreeBSD ¤Ï PC ÍѤÀ¤±¤·¤«¤Ê¤¤¤Î?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 3.x °Ê¹ß¤Ï x86 ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤ÈƱÍÍ¡¢
             <ulink url="http://www.FreeBSD.org/alpha/alpha.html">DEC Alpha</ulink> ¤Ç¤âÆ°ºî¤·¤Þ¤¹¡£
             ¤Þ¤¿¡¢SPARC¡¢PowerPC¡¢IA64 ¤Ø¤Î°Ü¿¢¤È¤¤¤¦¶½Ì£¿¼¤¤Ïä⤢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             °Û¤Ê¤ë¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Î¥Þ¥·¥ó¤ò
             »ý¤Ã¤Æ¤¤¤Æ¡¢¤æ¤Ã¤¯¤êÂԤƤʤ¤¤È¤¤¤¦¾ì¹ç¤Ë¤Ï¼¡¤Î URL ¤ò
             »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             <ulink url="http://www.netbsd.org/">NetBSD</ulink>
             ¤Þ¤¿¤Ï
             <ulink url="http://www.openbsd.org/">OpenBSD</ulink>¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="responsible">
           <para>FreeBSD ¤ÎÀÕǤ¼Ô¤Ï¤¤¤Ã¤¿¤¤Ã¯?</para>
         </question>
 
         <answer>
           <para>
             ¥×¥í¥¸¥§¥¯¥È¤ÎÁ´ÂÎŪ¤ÊÊý¸þÀ­¤ä¡¢
             ï¤Ë¥½¡¼¥¹¥Ä¥ê¡¼¤Ë¥³¡¼¥É¤Î½ñ¤­¹þ¤ß¸¢¸Â¤òÍ¿¤¨¤ë¤«¡¢
             ¤Ê¤É¤È¤¤¤Ã¤¿ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ë´Ø¤¹¤ë½ÅÍפʰջ׷èÄê¤Ï¡¢
             9 ̾¤«¤é¤Ê¤ë<ulink url="../handbook/staff.html#STAFF-CORE">¥³¥¢¥Á¡¼¥à
               (core team)</ulink> ¤Ë¤è¤Ã¤Æ¤Ê¤µ¤ì¤Þ¤¹¡£
             ¥½¡¼¥¹¥Ä¥ê¡¼¤òľÀÜÊѹ¹¤Ç¤­¤ë¿Í¤Ï¤â¤Ã¤È¿¤¯¡¢
             200 ̾°Ê¾å¤Î<ulink url="../handbook/staff:committers.html">¥½¡¼¥¹¥Ä¥ê¡¼´ÉÍý¼Ô
               (committer)</ulink> ¤¬¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¤·¤«¤·¡¢<link linkend="mailing">¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</link>¤ÇÀè¹Ô¤·¤ÆµÄÏÀ¤µ¤ì¤ë¡¢
             Ä̾ï¤ÎÊѹ¹¤Ç¤Ï¤Ê¤¤¤â¤Î¤ÎµÄÏÀ¤Ø¤Î»²²Ã¤Ë¤Ï¡¢°ìÀÚÀ©¸Â¤Ï¤¢¤ê¤Þ¤»¤ó¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="where-get">
           <para>¤É¤³¤«¤é FreeBSD ¤òÆþ¼ê¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Î¤¹¤Ù¤Æ¤Î¼çÍפʥê¥ê¡¼¥¹¤Ï anonymous FTP ·Ðͳ¤Ç
             <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP ¥µ¥¤¥È</ulink>
             ¤«¤éÆþ¼ê¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             <itemizedlist>
               <listitem>
                 <para>
                   ¸½ºß¤Î 3.X-STABLE ¥ê¥ê¡¼¥¹¡¢3.5.1-RELEASE ¤Ï
                   <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.5.1-RELEASE/"
                          >3.5.1-RELEASE ¤Î¥Ç¥£¥ì¥¯¥È¥ê</ulink>¤Ë¤¢¤ê¤Þ¤¹¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>¸½ºß¤Î 4-STABLE ¥ê¥ê¡¼¥¹¡¢4.3-RELEASE ¤Ï
                   <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.3-RELEASE/"
                          >4.3-RELEASE ¤Î¥Ç¥£¥ì¥¯¥È¥ê</ulink>¤Ë¤¢¤ê¤Þ¤¹¡£</para>
               </listitem>
 
               <listitem>
                 <para>
                   <ulink url="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X
                     Snapshot</ulink> ¤Ï¡¢¤Û¤Ü°ìÆü¤Ë°ì²óºîÀ®¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
                 </para>
               </listitem>
 
             <listitem>
               <para><ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/">5.0 Snapshot</ulink>
                   ¥ê¥ê¡¼¥¹¤Ï <link linkend="current">-CURRENT</link>
                   ¥Ö¥é¥ó¥ÁÍѤ˰ìÆü¤Ë°ì²óºîÀ®¤µ¤ì¤Æ¤ª¤ê¡¢
                   ¤³¤ì¤é¤Ï½ã¿è¤ËºÇÀèü¤Î³«È¯¼Ô¤ª¤è¤Ó¥Æ¥¹¥¿¡¼¤Î¤¿¤á¤ËÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£
                 </para>
               </listitem>
 
             </itemizedlist>
           </para>
 
           <para>¤Þ¤¿¡¢FreeBSD ¤Ï CD-ROM ¤Ç¤âÆþ¼ê¤Ç¤­¡¢¼¡¤Î¤È¤³¤í¤ÇÃíʸ¤Ç¤­¤Þ¤¹¡£</para>
 
           <address>BSDi
           <street>4041 Pike Lane, Suite F</street>
           <city>Concord</city>, <state>CA</state>
           <postcode>94520</postcode>
           <country>USA</country>
 
           <phone>Orders:       +1 800 786-9907</phone>
           <phone>Questions:    +1 925 674-0783</phone>
           <fax>FAX:            +1 925 674-0821</fax>
           <otheraddr>email:    <ulink url="mailto:orders@osd.bsdi.com">BSDi Orders address</ulink></otheraddr>
           <otheraddr>WWW:      <ulink url="http://www.osd.bsdi.com/">BSDi Home page</ulink></otheraddr><phone>Orders:  +1 800 786-9907</phone></address>
 
           <para>¥ª¡¼¥¹¥È¥é¥ê¥¢¤Ç¤Ï¡¢¼¡¤Î¤È¤³¤í¤ËÌ䤤¹ç¤ï¤»¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <address>Advanced Multimedia Distributors
           <street>Factory 1/1 Ovata Drive</street>
           <city>Tullamarine, Melbourne</city>
           <state>Victoria</state>
           <country>Australia</country>
           <phone>Voice:        +61 3 9338 6777</phone>
 
           <otheraddr>CDROM Support BBS</otheraddr>
           <street>17 Irvine St</street>
           <city>Peppermint Grove</city>, <state>WA</state>
           <postcode>6011</postcode>
           <phone>Voice:        +61 9 385-3793</phone>
           <fax>Fax:            +61 9 385-2360</fax></address>
 
           <para>¥¤¥®¥ê¥¹¤Î¾ì¹ç¤Ï¼¡¤Î¤È¤³¤í¤Ç¤¹¡£</para>
 
           <address>The Public Domain &amp; Shareware Library
           <street>Winscombe House, Beacon Rd</street>
           <city>Crowborough</city>
           <state>Sussex. TN6 1UL</state>
           <phone>Voice:        +44 1892 663-298</phone>
           <fax>Fax:            +44 1892 667-473</fax></address>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mailing">
           <para>FreeBSD ¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ë¤Ä¤¤¤ÆÃΤꤿ¤¤¤Î¤Ç¤¹¤¬?</para>
         </question>
 
         <answer>
 
           <para>
             ´°Á´¤Ê¾ðÊó¤¬
             <ulink url="../handbook/eresources.html#ERESOURCES-MAIL">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ÎÀá</ulink>
             ¤Ë¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="newsgroups">
           <para>FreeBSD ¤Î¥Ë¥å¡¼¥¹¥°¥ë¡¼¥×¤Ï²¿¤¬¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>´°Á´¤Ê¾ðÊó¤¬
             <ulink url="../handbook/eresources-news.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¥Ë¥å¡¼¥¹¥°¥ë¡¼¥×¤ÎÀá</ulink>¤Ë¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="irc">
           <para>FreeBSD ¤Î IRC
             (Internet Relay Chat) ¤Ë¤Ä¤¤¤Æ²¿¤«¾ðÊó¤Ï¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤¢¤ê¤Þ¤¹¡£
             °Ê²¼¤Î¤è¤¦¤Ë¡¢¤Û¤È¤ó¤É¤Îͭ̾¤Ê IRC ¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤Ï
             FreeBSD ¤Î¥Á¥ã¥Ã¥È¥Á¥ã¥ó¥Í¥ë¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <itemizedlist>
             <listitem>
               <para>EFNet ¤Î Channel <literal>#FreeBSD</literal> ¤Ï
                 FreeBSD ´Ø·¸¤Î¥Õ¥©¡¼¥é¥à¤Ç¤¹¤¬¡¢
                 ¤½¤³¤Çµ»½ÑŪ¥µ¥Ý¡¼¥È¤ò´üÂÔ¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
                 ¤½¤³¤Ë¤¤¤ë¿Í¤¿¤Á¤Ï¤¢¤Ê¤¿¤ò¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤òÆɤà¤È¤«¡¢
                 ¸¦µæ¤ò¤¹¤ë¤È¤«¤È¤¤¤Ã¤¿¶ìÏ«¤«¤é±ó¤¶¤±¤è¤¦¤È¤·¤Þ¤¹¡£
                 ¤Þ¤ºÂè°ì¤Ë¡¢¤³¤ì¤Ï¥Á¥ã¥Ã¥È¥Á¥ã¥ó¥Í¥ë¤Ç¤¢¤ê¡¢
                 ¤½¤³¤Ë¤¢¤ë¥È¥Ô¥Ã¥¯¥¹¤ÏÎø¿ÍÊ罸¡¢¥¹¥Ý¡¼¥Ä¡¢
                 ³Ëʼ´ï¤È¤¤¤Ã¤¿¤è¤¦¤Ê¤â¤Î¤Ç¤¢¤ê¡¢
                 FreeBSD ¤âƱÎó¤Ë°·¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
                 °ì±þÃí°Õ¤·¤Þ¤·¤¿¤«¤é¤Í! ¤³¤ì¤Ï
                 <hostid>irc.chat.org</hostid> ¤Î¥µ¡¼¥Ð¡¼¾å¤Ë¤¢¤ê¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>EFNet ¤Î Channel <emphasis>#FreeBSDhelp</emphasis> ¤Ï
                 FreeBSD ¥æ¡¼¥¶¤Î¥Ø¥ë¥×ÀìÍÑ¥Á¥ã¥Í¥ë¤Ç¤¹¡£
                 »²²Ã¼Ô¤Ï <emphasis>#FreeBSD</emphasis>
                 ¥Á¥ã¥Í¥ë¤è¤ê¤â¿ÆÀڤ˼ÁÌä¤ËÅú¤¨¤Æ¤¯¤ì¤Þ¤¹¡£</para>
              </listitem>
 
             <listitem>
               <para>DALNET ¤Î Channel <literal>#FreeBSD</literal>
                 ¤Ï¥¢¥á¥ê¥«¤Ç¤Ï
                 <hostid>irc.dal.net</hostid>¡¢
                 ¥è¡¼¥í¥Ã¥Ñ¤Ç¤Ï
                 <hostid>irc.eu.dal.net</hostid>
                 ¤Ë¤¢¤ê¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>UNDERNET ¤Î Channel <literal>#FreeBSD</literal>
                 ¤Ï¥¢¥á¥ê¥«¤Ç¤Ï
                 <hostid>us.undernet.org</hostid>¡¢
                 ¥è¡¼¥í¥Ã¥Ñ¤Ç¤Ï <hostid>eu.undernet.org</hostid>
                 ¤Ë¤¢¤ê¤Þ¤¹¡£
                 ¤³¤³¤Ï¥Ø¥ë¥×¥Á¥ã¥ó¥Í¥ë¤Ç¤¹¡£
                 ¥É¥­¥å¥á¥ó¥È¤òÆɤá¤ë½àÈ÷¤ò¤·¤Æ¤«¤éÍøÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
               </para>
             </listitem>
 
             <listitem>
               <para><ulink url="http://www.hybnet.net/">HybNet</ulink> ¤Î
                 Channel <literal>#FreeBSD</literal>¡£
                 ¤³¤Î¥Á¥ã¥ó¥Í¥ë¤Ï¤Ø¥ë¥×¥Á¥ã¥ó¥Í¥ë<emphasis>¤Ç¤¹</emphasis>¡£
                 ¥µ¡¼¥Ð¡¼¤Î¥ê¥¹¥È¤Ï <ulink
                 url="http://www.hybnet.net/">HybNet ¤Î¥¦¥§¥Ö¥µ¥¤¥È</ulink>
                 ¤Ë¤¢¤ê¤Þ¤¹¡£
               </para>
             </listitem>
           </itemizedlist>
 
           <para>¤½¤ì¤¾¤ì¤Î¥Á¥ã¥ó¥Í¥ë¤ÏÊ̸ĤΤâ¤Î¤Ç¡¢
             ¸ß¤¤¤ËÀܳ¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£
             ¥Á¥ã¥Ã¥È¤Î¥¹¥¿¥¤¥ë¤â°ã¤Ã¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢
             ¼«Ê¬¤Î¥Á¥ã¥Ã¥È¤Î¥¹¥¿¥¤¥ë¤Ë¤¢¤Ã¤¿¤â¤Î¤ò¸«¤Ä¤±¤ë¤¿¤á¤Ë°ì¤Ä°ì¤Ä»î¤¹¤Î¤â¤¤¤¤¤Ç¤·¤ç¤¦¡£
             ¤¢¤é¤æ¤ë¼ïÎà¤Î IRC ¥È¥é¥Õ¥£¥Ã¥¯¤Î¤¿¤á¡¢¼ºÎé¤Ê¤³¤È¤ò¤¤¤¦¼ã¼Ô¤¿¤Á
             (ǯÇÚ¤ÎÊý¤Ï¾¯¿ô¤Ç¤¹) ¤Î¤¿¤á¤Ëµ¡·ù¤ò»¤Í¤¿¤ê¡¢
             ¼ê¤ËÉ館¤Ê¤¯¤Ê¤Ã¤Æ¤âµ¤¤Ë¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="books">
           <para>FreeBSD ¤ÎËÜ</para>
         </question>
 
         <answer>
           <para>
             &a.doc; ¤Ë¥³¥ó¥¿¥¯¥È¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤
             (¤µ¤é¤Ë»²²Ã¤¹¤ì¤Ð¤â¤Ã¤È¤è¤¤¤Ç¤·¤ç¤¦)¡£
             ¤³¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ï FreeBSD ´ØÏ¢¤Îʸ½ñ¤Ë´Ø¤¹¤ëµÄÏÀ¤Î¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
             FreeBSD ¤Ë´Ø¤¹¤ë¼ÁÌä¤ËÂФ·¤Æ¤Ï¡¢
             &a.questions;
             ¤È¤¤¤¦¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para><ulink url="../handbook/index.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯</ulink>¤â¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤Ï¸½ºßºî¶ÈÃæ¤Ç¡¢
             ÉÔ´°Á´¤À¤Ã¤¿¤êºÇ¿·¾ðÊó¤Ç¤Ê¤¤¤â¤Î¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>
             FreeBSD ¤Î¥¬¥¤¥ÉËܤηèÄêÈǤϡ¢
             Greg Lehey »á¤Ë¤è¤ë <quote>The Complete FreeBSD</quote> ¤Ç¤¹¡£
             ¤³¤ì¤Ï BSDi (°ÊÁ°¤Î Walnut Creek CDROM) Books
             ¤«¤é½ÐÈǤµ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¸½ºß¤ÏÂè»°ÈǤˤʤäƤ¤¤Æ¡¢
             ¥¤¥ó¥¹¥È¡¼¥ë¡¢¥·¥¹¥Æ¥à´ÉÍý¥¬¥¤¥É¡¢¥×¥í¥°¥é¥àÀßÄê¤Î¥Ø¥ë¥×¡¢
             ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Þ¤Ç¤ÎÆâÍƤ¬ 773
             ¥Ú¡¼¥¸¤Ë¤ï¤¿¤Ã¤Æ½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ÎËÜ¤Ï (¤½¤·¤Æ¸½ºß¤Î FreeBSD ¥ê¥ê¡¼¥¹¤Ï)
             <ulink url="http://www.osd.bsdi.com/">BSDi</ulink>¡¢
             <ulink url="http://www.cheapbytes.com/">CheapBytes</ulink>¡¢
             ¤Þ¤¿¤ÏºÇ´ó¤ê¤Î½ñŹ¤ÇÃíʸ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ISBN ¥³¡¼¥É¤Ï 1-57176-246-9 ¤Ç¤¹
             (¤³¤ì°Ê³°¤Î¥³¡¼¥É¤Î¾ì¹ç¤â¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó)¡£</para>
 
           <para>
             ¤Þ¤¿¡¢FreeBSD ¤Ï Berkeley 4.4BSD-Lite
             ¥Ù¡¼¥¹¤Ê¤Î¤Ç¡¢Â¿¤¯¤Î 4.4BSD ¤Î¥Þ¥Ë¥å¥¢¥ë¤¬
             FreeBSD ¤Ë¤â±þÍѤǤ­¤Þ¤¹¡£
             O'Reilly and Associates
             ¤¬°Ê²¼¤Î¥Þ¥Ë¥å¥¢¥ë¤ò½ÐÈǤ·¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             <itemizedlist>
 
               <listitem>
                 <para><xref linkend="biblio-44sysman"/></para>
               </listitem>
 
               <listitem>
                 <para><xref linkend="biblio-44userman"/></para>
               </listitem>
 
               <listitem>
                 <para><xref linkend="biblio-44suppman"/></para>
               </listitem>
 
               <listitem>
                 <para><xref linkend="biblio-44progman"/></para>
               </listitem>
 
               <listitem>
                 <para><xref linkend="biblio-44progsupp"/></para>
               </listitem>
 
             </itemizedlist>
           </para>
 
           <para>
             ¤³¤ì¤é¤Î¾ÜºÙ¤ÊÀâÌÀ¤¬ WWW ·Ðͳ¤Ç
             <ulink url="http://gnn.com/gnn/bus/ora/category/bsd.html">4.4BSD
               books description</ulink>
             ¤«¤éÆɤळ¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ÈÎÇä¿ô¤¬¾¯¤Ê¤¤¤¿¤á¤³¤ì¤é¤Î¥Þ¥Ë¥å¥¢¥ë¤ÏÆþ¼ê¤·¤Ë¤¯¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             4.4BSD ¤Î¥«¡¼¥Í¥ë¹½À®¤Ë¤Ä¤¤¤Æ¤è¤êÅ°ÄìŪ¤ËÃΤꤿ¤¤¤Î¤Ê¤é¡¢
             <xref linkend="biblio-44kernel"/> ¤Ê¤é´Ö°ã¤¤¤Ê¤¤¤Ç¤·¤ç¤¦¡£</para>
 
           <para>¥·¥¹¥Æ¥à´ÉÍý¤Ë¤Ä¤¤¤Æ¤ÎÎɽñ¤¬ <xref
             linkend="biblio-nemeth3rd"/> ¤Ç¤¹¡£</para>
 
           <note><para>½éÈǤǤϤʤ¯¡¢»ç¿§¤Î¥«¥Ð¡¼¤ÎÂè»°ÈǤǤ¢¤ë¤«³Îǧ¤·¤Æ¤¯¤À
             ¤µ¤¤¡£</para></note>
 
           <para>
             ¤³¤ÎËÜ¤Ï TCP/IP ¤À¤±¤Ç¤Ê¤¯ DNS¡¢NFS¡¢SLIP/PPP¡¢sendmail¡¢
             INN/NNTP¡¢°õºþ¤Ê¤É¤Î´ðÁäò°·¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¹â²Á¤Ç¤¹¤¬¡¢Ç㤦²ÁÃͤϤ¢¤ê¤Þ¤¹¡£
             Âè»°ÈǤǤϡ¢Solaris, HP/UX, FreeBSD ¤ª¤è¤Ó Linux ¤ò¼è¤ê°·¤Ã¤Æ¤¤¤Þ¤¹¡£
           </para>
           <!-- hrs/2000/03/09 &#xx; should not be used -->
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="access-pr">
           <para>¾ã³²Êó¹ð (PR; Problem Report)
             ¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë¥¢¥¯¥»¥¹¤¹¤ëÊýË¡¤Ï?</para>
         </question>
 
         <answer>
           <para>
             ¥æ¡¼¥¶¤«¤é¤ÎÊѹ¹Í׵᤬¤Þ¤È¤á¤é¤ì¤Æ¤¤¤ë
             Problem Report ¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ï¡¢
             ¾ã³²Êó¹ð¤Î web ¥Ù¡¼¥¹¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤òÄ̤·¤Æ¡¢
             <ulink url="http://www.FreeBSD.org/ja/send-pr.html">Äó½Ð</ulink>¤È<ulink url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">Ì䤤¹ç¤ï¤»</ulink>¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤Þ¤¿¡¢&man.send-pr.1; ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¡¢
             ÅŻҥ᡼¥ë·Ðͳ¤Ç¾ã³²Êó¹ð¤äÊѹ¹Í×µá¤òÄó½Ð¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="doc-formats">
           <para>¥×¥ì¥¤¥ó¥Æ¥­¥¹¥È (ASCII) ÈÇ ¤ä
             PostScript ÈǤΠFreeBSD ʸ½ñ¤Ï¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>¤Ï¤¤¡¢¤â¤Á¤í¤ó¤¢¤ê¤Þ¤¹¡£
             ¿ô¿¤¯¤Î°Û¤Ê¤ë¥Õ¥©¡¼¥Þ¥Ã¥È¡¢°µ½Ì·Á¼°¤Îʸ½ñ¤¬ FreeBSD FTP ¥µ¥¤¥È¤Î
             <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink>
             ¤È¤¤¤¦¥Ç¥£¥ì¥¯¥È¥ê¤«¤éÆþ¼ê²Äǽ¤Ç¤¹¡£</para>
 
           <para>ʸ½ñ¤Ï¡¢¼¡¤Î¤è¤¦¤Ê¤µ¤Þ¤¶¤Þ¤Ê´ÑÅÀ¤«¤éʬÎव¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
           <itemizedlist>
             <listitem>
               <para><literal>faq</literal> ¤ä <literal>handbook</literal>
                 ¤È¤¤¤Ã¤¿Ê¸½ñ̾¤Ë¤è¤ëʬÎà¡£</para>
             </listitem>
 
             <listitem>
               <para>ʸ½ñ¤Î¸À¸ì¤È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ë¤è¤ëʬÎà¡£¤³¤ì¤Ï
                 FreeBSD ¥·¥¹¥Æ¥à¤Î <filename>/usr/share/locale</filename>
                 ¤Ë¤¢¤ë locale ̾¤Ë´ð¤Å¤¤¤Æ¤¤¤Þ¤¹¡£
                 ¸½ºßÍøÍѲÄǽ¤Ê¸À¸ì¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ï°Ê²¼¤Î¤È¤ª¤ê¤Ç¤¹¡£</para>
 
               <informaltable frame="none">
                 <tgroup cols="2">
                   <thead>
                     <row>
                       <entry>̾Á°</entry>
 
                       <entry>°ÕÌ£</entry>
                     </row>
                   </thead>
 
                   <tbody>
                     <row>
                       <entry><literal>en_US.ISO8859-1</literal></entry>
 
                       <entry>±Ñ¸ì (Êƹñ)</entry>
                     </row>
 
                     <row>
                       <entry><literal>de_DE.ISO_8859-1</literal></entry>
 
                       <entry>¥É¥¤¥Ä¸ì</entry>
                      </row>
 
                     <row>
                       <entry><literal>es_ES.ISO8859-1</literal></entry>
 
                       <entry>¥¹¥Ú¥¤¥ó¸ì</entry>
                     </row>
 
                     <row>
                       <entry><literal>fr_FR.ISO8859-1</literal></entry>
 
                       <entry>¥Õ¥é¥ó¥¹¸ì</entry>
                     </row>
 
                     <row>
                       <entry><literal>ja_JP.eucJP</literal></entry>
 
                       <entry>ÆüËܸì (EUC ¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°)</entry>
                     </row>
 
                     <row>
                       <entry><literal>ru_RU.KOI8-R</literal></entry>
 
                       <entry>¥í¥·¥¢¸ì (KOI8-R ¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°)</entry>
                     </row>
 
                     <row>
                       <entry><literal>zh_TW.Big5</literal></entry>
 
                       <entry>Ãæ¹ñ¸ì (Big5 ¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°)</entry>
                     </row>
                   </tbody>
                 </tgroup>
               </informaltable>
 
               <note>
                 <para>¸À¸ì¤Ë¤è¤Ã¤Æ¤Ï½àÈ÷¤µ¤ì¤Æ¤¤¤Ê¤¤Ê¸½ñ¤â¸ºß¤·¤Þ¤¹¡£</para>
               </note>
             </listitem>
 
             <listitem>
               <para>ʸ½ñ¤Î·Á¼°¤Ë¤è¤ëʬÎà¡£
                 ʸ½ñ¤Ï¿ô¿¤¯¤Î°Û¤Ê¤ë½ÐÎÏ·Á¼°¤òÍÑ°Õ¤·¡¢
                 ²Äǽ¤Ê¸Â¤ê½ÀÆð¤ÊÂбþ¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Æ¤¤¤Þ¤¹¡£
                 ¸½ºß¡¢ÍøÍѲÄǽ¤Êʸ½ñ·Á¼°¤Ï°Ê²¼¤Î¤È¤ª¤ê¤Ç¤¹¡£</para>
 
               <informaltable frame="none">
                 <tgroup cols="2">
                   <thead>
                     <row>
                       <entry>ʸ½ñ·Á¼°</entry>
 
                       <entry>°ÕÌ£</entry>
                     </row>
                   </thead>
 
                   <tbody>
                     <row>
                       <entry><literal>html-split</literal></entry>
 
                       <entry>¥µ¥¤¥º¤Î¾®¤µ¤¤¡¢
                         ¥ê¥ó¥¯¤µ¤ì¤¿Ê£¿ô¤Î HTML ¥Õ¥¡¥¤¥ë</entry>
                     </row>
 
                     <row>
                       <entry><literal>html</literal></entry>
 
                       <entry>ʸ½ñÁ´ÂΤò´Þ¤ó¤À¡¢Ã±°ì¤ÎÂ礭¤Ê¥Õ¥¡¥¤¥ë</entry>
                     </row>
 
                     <row>
                       <entry><literal>pdb</literal></entry>
 
                       <entry><ulink url="http://www.iSilo.com/">iSilo</ulink> ¤ÇÍøÍѲÄǽ¤Ê
                         Palm Pilot ¥Ç¡¼¥¿¥Ù¡¼¥¹·Á¼°
                       </entry>
                     </row>
 
                     <row>
                       <entry><literal>pdf</literal></entry>
 
                       <entry>Adobe ¼Ò¤Î PDF (Portable Document Format) ·Á¼°</entry>
                     </row>
 
                     <row>
                       <entry><literal>ps</literal></entry>
 
                       <entry>Postscript ·Á¼°</entry>
                     </row>
 
                     <row>
                       <entry><literal>rtf</literal></entry>
 
                       <entry>Microsoft ¼Ò¤Î¥ê¥Ã¥Á¥Æ¥­¥¹¥È·Á¼°<footnote>
                           <para>¤³¤Î·Á¼°¤ò Word ¤ÇÆɤ߹þ¤ó¤À¾ì¹ç¡¢
                             ¥Ú¡¼¥¸ÈÖ¹æ¤Ï¼«Æ°Åª¤Ë¹¹¿·¤µ¤ì¤Þ¤»¤ó¡£
                             ¥Ú¡¼¥¸ÈÖ¹æ¤ò¹¹¿·¤¹¤ë¤Ë¤Ïʸ½ñ¤òÆɤ߹þ¤ó¤Ç¤«¤é
                             <keycap>CTRL</keycap>+<keycap>A</keycap>¡¢
                             <keycap>CTRL</keycap>+<keycap>END</keycap>¡¢
                             <keycap>F9</keycap> ¤ò²¡¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
                         </footnote>
                       </entry>
                     </row>
 
                     <row>
                       <entry><literal>txt</literal></entry>
 
                       <entry>¥×¥ì¥¤¥ó¥Æ¥­¥¹¥È·Á¼°</entry>
                     </row>
                   </tbody>
                 </tgroup>
               </informaltable>
             </listitem>
 
             <listitem>
               <para>°µ½Ì¤È package ·Á¼°¤Ë¤è¤ëʬÎà¡£
                 ¸½ºßÍøÍѤµ¤ì¤Æ¤¤¤ë¤Î¤Ï¼¡¤Î 3 ¼ïÎà¤Ç¤¹¡£</para>
 
               <orderedlist>
                 <listitem>
                   <para><literal>html-split</literal> ·Á¼°¤Î¾ì¹ç¡¢
                     ¥Õ¥¡¥¤¥ë¤Ï¤Þ¤º¡¢&man.tar.1; ¤ò»È¤Ã¤Æ¤Þ¤È¤á¤é¤ì¡¢
                     ¤Þ¤È¤á¤é¤ì¤¿ <filename>.tar</filename>
                     ¥Õ¥¡¥¤¥ë¤Ï¼¡¤Ë²òÀ⤹¤ëÊý¼°¤Ç°µ½Ì¤µ¤ì¤Þ¤¹¡£</para>
                 </listitem>
 
                 <listitem>
                   <para>¤½¤Î¾¤Î·Á¼°¤Î¾ì¹ç¡¢¥Õ¥¡¥¤¥ë¤Ï
                     <filename>book.<replaceable>format</replaceable></filename>
                     (¤¿¤È¤¨¤Ð <filename>book.pdb</filename>¡¢
                     <filename>book.html</filename> ¤Ê¤É)
                     ¤È¤¤¤¦Ã±°ì¤Î¥Õ¥¡¥¤¥ë¤Ç¤¹¡£</para>
 
                   <para>¾å¤Ë¤¢¤²¤¿¥Õ¥¡¥¤¥ë¤Ï
                     3 ¼ïÎà¤ÎÊý¼°¤Î¤¤¤º¤ì¤«¤Ç°µ½Ì¤µ¤ì¤Þ¤¹¡£</para>
 
                   <informaltable frame="none">
                     <tgroup cols="2">
                       <thead>
                         <row>
                           <entry>Êý¼°</entry>
 
                           <entry>ÀâÌÀ</entry>
                         </row>
                       </thead>
 
                       <tbody>
                         <row>
                           <entry><literal>zip</literal></entry>
 
                           <entry>Zip ·Á¼°¡£
                             FreeBSD ¤Ç°µ½Ì¤ò¸µ¤ËÌ᤹¤Ë¤Ï¡¢¤Þ¤º
                             <filename>archivers/unzip</filename> ¤Î port
                             ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</entry>
                         </row>
 
                         <row>
                           <entry><literal>gz</literal></entry>
 
                           <entry>GNU Zip ·Á¼°¡£°µ½Ì¤ò¸µ¤ËÌ᤹¤Ë¤Ï¡¢
                             FreeBSD ¤Ë´Þ¤Þ¤ì¤ë &man.gunzip.1; ¤ò»È¤¤¤Þ¤¹¡£</entry>
                         </row>
 
                         <row>
                           <entry><literal>bz2</literal></entry>
 
                           <entry>BZip2 ·Á¼°¡£
                             ¾¤Î·Á¼°¤ËÈæ¤Ù¤ÆÉáµÚ¤·¤Æ¤¤¤Þ¤»¤ó¤¬¡¢
                             °ìÈÌŪ¤Ë¥Õ¥¡¥¤¥ë¥µ¥¤¥º¤¬¾®¤µ¤¯¤Ê¤ê¤Þ¤¹¡£
                             °µ½Ì¤ò¸µ¤ËÌ᤹¤Ë¤Ï¡¢
                             <filename>archivers/bzip2</filename> port
                             ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£</entry>
                         </row>
                       </tbody>
                     </tgroup>
                   </informaltable>
 
                   <para>Postscript ÈǤΥϥó¥É¥Ö¥Ã¥¯¤¬ BZip2
                     ·Á¼°¤Ç°µ½Ì¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢¥Õ¥¡¥¤¥ë̾¤Ï
                     <filename>handbook/</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤ÎÃæ¤Î
                     <filename>book.xml.bz2</filename> ¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
                 </listitem>
 
                 <listitem>
                   <para>¤µ¤Þ¤¶¤Þ¤Ê·Á¼°¤ËÀ°·Á¤µ¤ì¤¿Ê¸½ñ¤Ï¡¢°Ê²¼¤Ë½Ò¤Ù¤ë¤è¤¦¤Ë
                     FreeBSD ¤Î package ¤È¤·¤Æ¤âÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
                 </listitem>
               </orderedlist>
             </listitem>
           </itemizedlist>
 
           <para>¥À¥¦¥ó¥í¡¼¥É¤¹¤ëʸ½ñ¤È°µ½Ì·Á¼°¤òÁªÂò¤·¤¿¤é¡¢
             ʸ½ñ¤ò FreeBSD <emphasis>package</emphasis>
             ¤È¤·¤Æ¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¤«¤É¤¦¤«·è¤á¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
           <para>package ¤È¤·¤Æ¥À¥¦¥ó¥í¡¼¥É¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¾ì¹ç¤Ë¤Ï¡¢
             ʸ½ñ¤ò &man.pkg.add.1; ¤ä &man.pkg.delete.1;
             ¤È¤¤¤Ã¤¿¡¢ÉáÄ̤ΠFreeBSD package
             ´ÉÍý¥·¥¹¥Æ¥à¤òÍѤ¤¤¿´ÉÍý¤¬²Äǽ¤Ç¤¢¤ë¤È¤¤¤¦ÍøÅÀ¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>ʸ½ñ¤Î package ¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤Ë·è¤á¤¿¤é¡¢
             ¤Þ¤º¤Ï¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¥Õ¥¡¥¤¥ë̾¤òÃΤëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ʸ½ñ¤Î package ¤Ï¡¢<filename>packages</filename>
             ¤È¤¤¤¦¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤½¤·¤Æ¤½¤ì¤¾¤ì¤Î package ¥Õ¥¡¥¤¥ë¤Ï¡¢
             <filename><replaceable>ʸ½ñ̾</replaceable>.<replaceable>¸À¸ì</replaceable>.<replaceable>¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°</replaceable>.<replaceable>·Á¼°</replaceable>.tgz</filename>
             ¤È¤¤¤¦¤è¤¦¤Ê̾Á°¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
 
           <para>¤¿¤È¤¨¤Ð¡¢FAQ ¤Î±Ñ¸ìÈÇ¤Ç PDF ·Á¼°¤Î¤â¤Î¤Ï¡¢
             <filename>faq.en_US.ISO8859-1.pdf.tgz</filename>
             ¤È¤¤¤¦¥Õ¥¡¥¤¥ë̾¤Ç¤¹¡£</para>
 
           <para>¥Õ¥¡¥¤¥ë̾¤¬¤ï¤«¤Ã¤¿¤é¡¢
             ¼¡¤Î¤è¤¦¤Ê¥³¥Þ¥ó¥É¤Ç±Ñ¸ìÈǤΠPDF ·Á¼° FAQ ¤Î package
             ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.en_US.ISO8859-1.pdf.tgz</userinput></screen>
 
           <para>¥¤¥ó¥¹¥È¡¼¥ë¤Î½ªÎ»¸å¤Ï
             &man.pkg.info.1; ¤ò»È¤¤¡¢
             ¥Õ¥¡¥¤¥ë¤¬¤É¤³¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤¿¤«¤òÄ´¤Ù¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>pkg_info -f faq.en_US.ISO8859-1.pdf</userinput>
 Information for faq.en_US.ISO8859-1.pdf:
 
 Packing list:
         Package name: faq.en_US.ISO8859-1.pdf
         CWD to /usr/share/doc/en_US.ISO8859-1/books/faq
 File: book.pdf
         CWD to .
 File: +COMMENT (ignored)
 File: +DESC (ignored)</screen>
 
           <para>¤´Í÷¤Ë¤Ê¤ë¤È¤ï¤«¤ë¤È¤ª¤ê¡¢<filename>book.pdf</filename> ¤Ï
             <filename>/usr/share/doc/en_US.ISO8859-1/books/faq</filename>
             ¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£</para>
 
           <para>package ¤òÍøÍѤ·¤Ê¤¤¾ì¹ç¤Ï¡¢
             ¼«Ê¬¤Ç°µ½Ì¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤Æ¸µ¤ËÌᤷ¡¢
             ŬÀڤʾì½ê¤Ë¤½¤ì¤ò¥³¥Ô¡¼¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>¤¿¤È¤¨¤Ð¡¢Ê¬³ä¤µ¤ì¤¿ HTML ÈǤΠFAQ ¤Ç¡¢
             &man.gzip.1; ¤Ç°µ½Ì¤µ¤ì¤Æ¤¤¤ë¤â¤Î¤Ï
             <filename>en_US.ISO8859-1/books/faq/book.html-split.tar.gz</filename>
             ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤Ç¤¹¡£
             ¤³¤ì¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤Æ°µ½Ì¤ò¸µ¤ËÌ᤹¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤¹¤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£</para>
 
           <screen>&prompt.root; <userinput>fetch ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz</userinput>
 &prompt.root; <userinput>gzip -d book.html-split.tar.gz</userinput>
 &prompt.root; <userinput>tar xvf book.html-split.tar</userinput></screen>
 
           <para>¤³¤¦¤¹¤ë¤È¡¢Ê£¿ô¤Î <filename>.html</filename>
             ¥Õ¥¡¥¤¥ë¤¬ºîÀ®¤µ¤ì¤Þ¤¹¡£ Ãæ¿´¤È¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ï
             <filename>index.html</filename> ¤È¤¤¤¦Ì¾Á°¤Î¥Õ¥¡¥¤¥ë¤Ç¡¢
             Ìܼ¡¤äÁ°½ñ¤­¡¢Ê¸½ñ¤Î¾¤ÎÉôʬ¤Ø¤Î¥ê¥ó¥¯¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ï¡¢É¬Íפ˱þ¤¸¤Æ¾¤Î¾ì½ê¤Ë¥³¥Ô¡¼¤·¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£</para>
          </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="become-web-mirror">
           <para>FreeBSD ¤Î¥¦¥§¥Ö¥µ¥¤¥È¤Î¥ß¥é¡¼¥µ¥¤¥È¤Ë¤Ê¤ê¤¿¤¤¤Ç¤¹!</para>
         </question>
 
         <answer>
           <para>¾µÃΤ·¤Þ¤·¤¿!
             ¥¦¥§¥Ö¥Ú¡¼¥¸¤ò¥ß¥é¡¼¤¹¤ë¤Ë¤Ï¤¤¤¯¤Ä¤«¤Î¼êÃʤ¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>
             <itemizedlist>
               <listitem>
                 <para><application>CVSup</application> ¤ò»È¤¤¤Þ¤¹¡£
                   <application>CVSup</application> ¤ò»È¤Ã¤Æ
                   <application>CVSup</application> ¥µ¡¼¥Ð¤ËÀܳ¤¹¤ë¤³¤È¤Ç¡¢
                   À°·Á¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤ò¼è¤Ã¤Æ¤¯¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
               <para>¥¦¥§¥Ö¥Ú¡¼¥¸¤ò¼èÆÀ¤¹¤ë¾ì¹ç¤Ï¡¢
                 <filename>/usr/share/examples/cvsup/www-supfile</filename>
                 ¤Ë¤¢¤ë supfile ¤ÎÎã¤ò»²¹Í¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
               </listitem>
 
               <listitem>
                 <para>
                   FTP ¤ò»È¤Ã¤Æ¥ß¥é¡¼¥ê¥ó¥°¤·¤Þ¤¹¡£
                   ¤¢¤Ê¤¿¤Î¹¥¤­¤Ê FTP ¥ß¥é¡¼¥ê¥ó¥°¥Ä¡¼¥ë¤ò»È¤Ã¤Æ¡¢
                   FTP ¥µ¡¼¥Ð¤ËÃÖ¤¤¤Æ¤¢¤ë web
                   ¥µ¥¤¥È¤Î¥³¥Ô¡¼¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
                   ¥¿¥¦¥ó¥í¡¼¥É¤Ïñ½ã¤Ë ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-CURRENT/www
                   ¤«¤é»Ï¤á¤Æ¤¯¤À¤µ¤¤¡£</para>
               </listitem>
             </itemizedlist>
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="translation">
           <para>¤³¤Îʸ½ñ¤ò¾¤Î¸À¸ì¤ËËÝÌõ¤·¤¿¤¤¤Î¤Ç¤¹¤¬?</para>
         </question>
 
         <answer>
           <para>
             Ê󽷤ϻÙʧ¤¨¤Þ¤»¤ó¤¬¡¢
             ʸ½ñ¤ÎËÝÌõ¤òÄó½Ð¤·¤Æ¤¯¤À¤µ¤ëÊý¤Ë¤Ï¡¢
             ¥Õ¥ê¡¼¤Î CD¡¢T ¥·¥ã¥Ä¤Î¼êÇۤ䡢
             ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Ë¤¢¤ë¹×¸¥¼Ô°ìÍ÷¤Ø¤ÎÅÐÏ¿¤ò¹Ô¤Ê¤¤¤¿¤¤¤È»×¤¤¤Þ¤¹¡£
             ËÝÌõºî¶È¤ò¤Ï¤¸¤á¤ëÁ°¤Ë¡¢
             &a.doc;
             ¤ØÏ¢Íí¤¹¤ë¤è¤¦¤Ë¤ª´ê¤¤¤·¤Þ¤¹¡£
             ËÝÌõºî¶È¤ò¼êÅÁ¤¦¤È¤¤¤¦¿Í¤¬¸½¤ï¤ì¤ë¤«¤âÃΤì¤Þ¤»¤ó¤·¡£
             ´û¤ËËÝÌõ¥Á¡¼¥à¤¬¤¢¤Ã¤Æ¡¢¤¢¤Ê¤¿¤Î»²²Ã¤ò´¿·Þ¤·¤Æ¤¯¤ì¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="other-info-sources">
           <para>¤½¤Î¾¤Î¾ðÊó</para>
         </question>
 
         <answer>
           <para>
             °Ê²¼¤Î¥Ë¥å¡¼¥¹¥°¥ë¡¼¥×¤Ë¤Ï FreeBSD
             ¥æ¡¼¥¶¤ËľÀÜ´Ø·¸¤Î¤¢¤ëµÄÏÀ¤¬¹Ô¤ï¤ì¤Æ¤Þ¤¹¡£
           </para>
 
           <itemizedlist>
             <listitem>
               <para><ulink url="news:comp.unix.bsd.freebsd.announce">comp.unix.bsd.freebsd.announce</ulink> (moderated)</para>
             </listitem>
 
             <listitem>
               <para><ulink url="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</ulink></para>
             </listitem>
 
             <listitem>
               <para><ulink url="news:comp.unix.bsd.misc">comp.unix.bsd.misc</ulink></para>
             </listitem>
 
           </itemizedlist>
 
           <para>Web ¾å¤Î¥ê¥½¡¼¥¹:</para>
 
           <itemizedlist>
             <listitem>
               <para><ulink url="http://www.FreeBSD.org/">FreeBSD ¤Î¥Û¡¼¥à¥Ú¡¼¥¸</ulink></para>
             </listitem>
 
             <listitem>
               <para><anchor id="pao"/>
                 ¥é¥Ã¥×¥È¥Ã¥× PC ¤ò»ý¤Ã¤Æ¤¤¤ëÊý¤Ï¡¢
                 ̤¦¤³¤È¤Ê¤¯ÆüËܤÎ<ulink url="http://www.jp.FreeBSD.org/PAO/">ºÙÀî ã¸Ê»á¤Î
                   Mobile Computing ¤Î¥Ú¡¼¥¸</ulink> ¤ò¸«¤Þ¤·¤ç¤¦¡£
               </para>
             </listitem>
 
             <listitem>
               <para><anchor id="smp"/>
                 SMP (Symmetric MultiProcessing) ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¡¢
                 <ulink url="http://people.FreeBSD.org/~fsmp/SMP/SMP.html">SMP
                   ¥µ¥Ý¡¼¥È¥Ú¡¼¥¸</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
               </para>
             </listitem>
 
             <listitem>
               <para><anchor id="multimedia"/>
                 FreeBSD ¤Î¥Þ¥ë¥Á¥á¥Ç¥£¥¢¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¡¢
                 <ulink url="http://people.FreeBSD.org/~faulkner/multimedia/mm.html">¥Þ¥ë¥Á¥á¥Ç¥£¥¢</ulink>¤Î¥Ú¡¼¥¸¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
                 ÆäË
                 <ulink url="http://people.FreeBSD.org/~ahasty/Bt848.html">Bt848</ulink>
                 ¥Ó¥Ç¥ª¥­¥ã¥×¥Á¥ã¥Á¥Ã¥×¤Ë¶½Ì£¤Î¤¢¤ëÊý¤Ï¡¢
                 ¥ê¥ó¥¯¤ò¤¿¤É¤Ã¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
               </para>
             </listitem>
           </itemizedlist>
 
           <para>FreeBSD ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Ë¤Ï¡¢
             ¼Â¤Ë´°À®¤µ¤ì¤¿<ulink url="../handbook/bibliography.html">»²¹Í¿Þ½ñ</ulink>¤Î°ìÍ÷¤¬¤¢¤ê¡¢
             Ç㤦¤Ù¤­Ëܤò¤µ¤¬¤·¤Æ¤¤¤ëÊý¤ÏÆɤà²ÁÃͤ¬¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
     </qandaset>
   </preface>
 
   <chapter id="install">
     <title>¥¤¥ó¥¹¥È¡¼¥ë</title>
 
     <para>
       <emphasis>Ìõ:
         &a.iwasaki;¡¢
         &a.jp.mrt;¡¢
         1997 ǯ 11 ·î 8 Æü</emphasis>
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="floppy-download">
           <para>FreeBSD ¤òÆþ¼ê¤¹¤ë¤Ë¤Ï¡¢¤É¤Î¥Õ¥¡¥¤¥ë¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ì¤ÐÎɤ¤¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 3.1-RELEASE °ÊÁ°¤Ç¤Ï¡¢
             ¥¤¥ó¥¹¥È¡¼¥ë¤ÎºÝ¤ËɬÍפʤΤÏ
             <filename>floppies/boot.flp</filename> ¤È̾Á°¤Î¤Ä¤¤¤¿
             °ì¤Ä¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¥¤¥á¡¼¥¸¤À¤±¤Ç¤·¤¿¡£
             ¤·¤«¤· FreeBSD 3.1-RELEASE °Ê¹ß¡¢
             Éý¹­¤¤¼ïÎà¤Î¥Ï¡¼¥É¥¦¥§¥¢¥µ¥Ý¡¼¥È¤¬´ðËÜ¥·¥¹¥Æ¥à¤ËÄɲ䵤졢
             ¤½¤Î¥µ¥Ý¡¼¥È¤¬É¬ÍפȤ¹¤ëÍÆÎ̤òÊ䤦¤¿¤á¡¢
             3.X ¤È 4.X ¤Î·ÏÎó¤Ç¤Ï¿·¤¿¤Ë¡¢
             <filename>floppies/kernel.flp</filename>
             ¤ª¤è¤Ó
             <filename>floppies/mfsroot.flp</filename>
             ¤È¤¤¤¦¡¢Æó¤Ä¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¥¤¥á¡¼¥¸¤ò»È¤¦¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
             ¤³¤ì¤é¤Î¥¤¥á¡¼¥¸¤ò¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë½ñ¤­¹þ¤à¤Ë¤Ï¡¢
             <command>fdimage</command> ¤ä
             &man.dd.1; ¤È¤¤¤Ã¤¿¥Ä¡¼¥ë¤¬É¬ÍפȤʤê¤Þ¤¹¡£
           </para>
 
           <para>
             (DOS ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤«¤é¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ê¤É¤Ç)
             ¤¢¤Ê¤¿¼«¿È¤¬¼êÆ°¤ÇÇÛÉÛ¥Õ¥¡¥¤¥ë¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¾ì¹ç¤Ë¤Ï¡¢
             °Ê²¼¤ÎÇÛÉÛ¥Õ¥¡¥¤¥ë¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¤³¤È¤ò¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
           </para>
 
           <itemizedlist>
             <listitem>
               <para><filename>bin/</filename></para>
             </listitem>
 
             <listitem>
               <para><filename>manpages/</filename></para>
             </listitem>
 
             <listitem>
               <para><filename>compat*/</filename></para>
             </listitem>
 
             <listitem>
               <para><filename>doc/</filename></para>
             </listitem>
 
             <listitem>
               <para><filename>src/ssys.*</filename></para>
             </listitem>
           </itemizedlist>
 
           <para>
             ¤³¤Î¼ê½ç¤Î´°Á´¤ÊÀâÌÀ¤È¡¢°ìÈÌŪ¤Ê¥¤¥ó¥¹¥È¡¼¥ë»þ¤ÎÌäÂê¤Ë¤Ä¤¤¤Æ¤Ï
             <ulink url="../handbook/install.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¥¤¥ó¥¹¥È¡¼¥ë¤ÎÀá</ulink>
             ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="floppy-image-too-large">
           <para>¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¥¤¥á¡¼¥¸¤¬°ìËç¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ËǼ¤Þ¤é¤Ê¤¤¤ß¤¿¤¤!</para>
         </question>
 
         <answer>
           <para>
             3.5 ¥¤¥ó¥Á (1.44MB) ¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë¤Ï¡¢
             1474560 ¥Ð¥¤¥È¤Î¥Ç¡¼¥¿¤ò³ÊǼ¤Ç¤­¤Þ¤¹¡£
             ¥Ö¡¼¥È¥¤¥á¡¼¥¸¤Ï¤Á¤ç¤¦¤É 1474560 ¥Ð¥¤¥È¤ÎÂ礭¤µ¤Ç¤¹¡£
           </para>
 
           <para>¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ò½àÈ÷¤¹¤ëºÝ¤Î¤è¤¯¤¢¤ë´Ö°ã¤¤¤Ë¤Ï¡¢
             °Ê²¼¤Î¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <itemizedlist>
             <listitem>
               <para><acronym>FTP</acronym>
                 ¤Ë¤è¤Ã¤Æ¥Õ¥í¥Ã¥Ô¡¼¥¤¥á¡¼¥¸¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ëºÝ¤Ë¡¢
                 <emphasis>¥Ð¥¤¥Ê¥ê (binary)</emphasis> ¥â¡¼¥É¤Ë¤·¤Æ¤¤¤Ê¤«¤Ã¤¿¡£
               </para>
 
               <para>FTP ¥¯¥é¥¤¥¢¥ó¥È¤ÎÃæ¤Ë¤Ï¡¢
                 žÁ÷¥â¡¼¥É¤Î¥Ç¥Õ¥©¥ë¥È¤ò<emphasis>¥¢¥¹¥­¡¼ (ascii)</emphasis> ¥â¡¼¥É¤Ë¤·¤Æ¡¢
                 ¥¯¥é¥¤¥¢¥ó¥È¦¥·¥¹¥Æ¥à¤Î´·½¬¤Ë¤¢¤¦¤è¤¦¡¢
                 ¤¹¤Ù¤Æ¤Î¹ÔËö¤Îʸ»ú¤òÊѹ¹¤¹¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
                 ¤³¤Î¾ì¹ç¤Ï¾ï¤Ë¡¢¥Ö¡¼¥È¥¤¥á¡¼¥¸¤¬²õ¤ì¤¿¤â¤Î¤Ë¤Ê¤ê¤Þ¤¹¡£
                 ¥À¥¦¥ó¥í¡¼¥É¤·¤¿¥Ö¡¼¥È¥¤¥á¡¼¥¸¤Î¥µ¥¤¥º¤ò¥Á¥§¥Ã¥¯¤·¤Æ¤¯¤À¤µ¤¤¡£
                 ¥µ¡¼¥Ð¾å¤Î¤â¤Î¤È<emphasis>Àµ³Î¤Ë</emphasis>°ìÃפ·¤Ê¤±¤ì¤Ð¡¢
                 ¥À¥¦¥ó¥í¡¼¥É¤Î½èÍý¤òµ¿¤¤¤Þ¤·¤ç¤¦¡£
               </para>
 
               <para>¤³¤ì¤ò²óÈò¤¹¤ë¤Ë¤Ï¡¢
                 ¥µ¡¼¥Ð¤ËÀܳ¤·¤Æ¥¤¥á¡¼¥¸¤Î¥À¥¦¥ó¥í¡¼¥É¤ò³«»Ï¤¹¤ëÁ°¤Ë
                 FTP ¤Î¥³¥Þ¥ó¥É¥×¥í¥ó¥×¥È¤Ç
                 <command>binary</command> ¤È¥¿¥¤¥×¤·¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>¥Ö¡¼¥È¥¤¥á¡¼¥¸¤ò
                 DOS ¤Î <command>copy</command> ¥³¥Þ¥ó¥É
                 (¤Þ¤¿¤Ï GUI ¤ÎƱÅù¤Î¥Ä¡¼¥ë) ¤Ç¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ØžÁ÷¤·¤¿¡£
               </para>
 
               <para><command>copy</command>
                 ¤Î¤è¤¦¤Ê¥×¥í¥°¥é¥à¤Ï¡¢
                 ľÀܵ¯Æ°¤¹¤ë¤è¤¦¤ËºîÀ®¤µ¤ì¤¿¥Ö¡¼¥È¥¤¥á¡¼¥¸¤ò¤¦¤Þ¤¯½èÍý¤Ç¤­¤Þ¤»¤ó¡£
                 ¥¤¥á¡¼¥¸¤Ë¤Ï¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Î´°Á´¤ÊÃæ¿È¤¬¥È¥é¥Ã¥¯Ã±°Ì¤Ç³ÊǼ¤µ¤ì¤Æ¤ª¤ê¡¢
                 ¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¾å¤ËÄ̾ï¤Î¥Õ¥¡¥¤¥ë¤È¤·¤Æ
                 ³ÊǼ¤µ¤ì¤ë¤è¤¦¤ËÁÛÄꤵ¤ì¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
                 <ulink url="../handbook/install.html">FreeBSD
                   ¤Î¥¤¥ó¥¹¥È¡¼¥ë</ulink>¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¡¢
                 Äã¥ì¥Ù¥ë¤Î¥Ä¡¼¥ë (¤¿¤È¤¨¤Ð
                 <command>fdimage</command> ¤ä
                 <command>rawrite</command>) ¤ò»ÈÍѤ·¤Æ
                 <quote>¤½¤Î¤Þ¤Þ¤Î (raw)</quote> ¤Î¾õÂ֤ǥեí¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë
                 žÁ÷¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
               </para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="install-instructions-location">
           <para>FreeBSD ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ë¤Ä¤¤¤Æ¤ÎÀâÌÀ½ñ¤Ï¤É¤³¤Ë¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¥¤¥ó¥¹¥È¡¼¥ë¤ÎÀâÌÀ½ñ¤Ï<ulink url="../handbook/install.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Î¾Ï</ulink>¤Ë¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="need-to-run">
           <para>FreeBSD ¤òÆ°ºî¤µ¤»¤ë¤Ë¤Ï²¿¤¬É¬ÍפǤ¹¤«?</para>
         </question>
 
         <answer>
           <para>
             386 °Ê¾å¤Î PC¡¢5MB °Ê¾å¤Î RAM¡¢
             ¤½¤·¤ÆºÇÄã 60MB ¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯ÍÆÎ̤¬É¬ÍפȤʤê¤Þ¤¹¡£
             ¥í¡¼¥¨¥ó¥É¤Î MDA ¥«¡¼¥É¤Ç¤âÆ°ºî¤·¤Þ¤¹¤¬¡¢
             X11R6 ¤ò»È¤¦¤Ë¤Ï VGA ¤«¤½¤ì°Ê¾å¤Î¥Ó¥Ç¥ª¥«¡¼¥É¤¬É¬ÍפȤʤê¤Þ¤¹¡£
           </para>
 
           <para>
             <xref linkend="hardware" remap="¥Ï¡¼¥É¥¦¥§¥¢¥³¥ó¥Ñ¥Á¥Ó¥ê¥Æ¥£"/>
               ¤â¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="four-meg-ram-install">
           <para>4MB ¤·¤«¥á¥â¥ê¤¬¤Ê¤¤¤Î¤Ç¤¹¤¬¡¢¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             4MB ¤Î¥·¥¹¥Æ¥à¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤¿ºÇ¸å¤Î FreeBSD ¤Ï
             FreeBSD 2.1.7 ¤Ç¤·¤¿¡£2.2 ¤ò´Þ¤à¤è¤ê¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤Î
             FreeBSD ¤Ï¿·µ¬¤Î¥¤¥ó¥¹¥È¡¼¥ë¤ËºÇÄã 5MB ¤ÏɬÍפˤʤê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤¿¤À¤·¡¢¥¤¥ó¥¹¥È¡¼¥ë¥×¥í¥°¥é¥à¤¬ 4MB ¤Ç¤ÏÆ°ºî¤·¤Ê¤¤¤À¤±¤Ç¡¢
             3.0 ¤ò´Þ¤à FreeBSD ¤Î¤¹¤Ù¤Æ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ï 4MB ¤Î RAM
             ¤Ç<emphasis>Æ°ºî²Äǽ</emphasis>¤Ç¤¹¡£
             ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë»þ¤À¤±¤µ¤é¤Ë 4MB Äɲ䷤Ƥª¤­¡¢
             ¥·¥¹¥Æ¥à¤¬¥»¥Ã¥È¥¢¥Ã¥×¤µ¤ì¤ÆÆ°ºî¤¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤¿¸å¡¢
             ¤Þ¤¿ 4MB ¤ò¼è¤ê½Ð¤·¤Æ¸µ¤ËÌ᤹¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
             ¤¢¤ë¤¤¤Ï 4MB ¤è¤ê¿¤¯¥á¥â¥ê¤òÅëºÜ¤·¤¿¥·¥¹¥Æ¥à¤Ë¥Ç¥£¥¹¥¯¤ò»ý¤Ã¤Æ¤¤¤­¡¢
             ¤½¤Î¥Þ¥·¥ó¤Ç¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¸å¤Ë¥Ç¥£¥¹¥¯¤òÌ᤹¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¤Þ¤¿¡¢FreeBSD 2.1.7 ¤Ç¤¢¤Ã¤Æ¤â¡¢4MB
             ¤Ç¤Ï¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Ê¤¤¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£
             Àµ³Î¤Ë¤Ï¡¢640KB ¤Î¥Ù¡¼¥¹¥á¥â¥ê + 3MB ¤Î³ÈÄ¥¥á¥â¥ê¤Ç¤Ï¡¢
             ¥¤¥ó¥¹¥È¡¼¥ë¤Ï¤Ç¤­¤Þ¤»¤ó¡£¤â¤·¥Þ¥·¥ó¤Î¥Þ¥¶¡¼¥Ü¡¼¥É¤¬
             640KB ¤«¤é 1MB
             ¤ÎÎΰè¤Ç¡Ö¼º¤ï¤ì¤¿¡×¥á¥â¥ê¤òºÆ¥Þ¥Ã¥×¤Ç¤­¤ë¾ì¹ç¤Ï¡¢
             FreeBSD 2.1.7 ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             BIOS ¤Î¥»¥Ã¥È¥¢¥Ã¥×²èÌ̤ǡ¢<quote>remap</quote>
             ¤Î¥ª¥×¥·¥ç¥ó¤òõ¤·¤ÆÍ­¸ú (enable) ¤Ë¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
             ¤Þ¤¿¡¢ROM shadowing
             ¤ò̵¸ú (disable) ¤Ë¤¹¤ëɬÍפ⤢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ´Êñ¤Ê¤ä¤êÊý¤È¤·¤Æ¤Ï¡¢¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë»þ¤À¤±¤¢¤È
             4MB Äɲ䷤Ƥª¤¯ÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£
             ɬÍפʥª¥×¥·¥ç¥ó¤À¤±¤òÁªÂò¤·¤Æ¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤·¡¢
             ¤Þ¤¿ 4MB ¤ò¼è¤ê½Ð¤·¤Æ¤â¤È¤ËÌ᤻¤Ð¤¤¤¤¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¤Þ¤¿¡¢2.0.5 ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¡¢
             ¤½¤ì¤«¤é 2.1.7 ¤Î¥¤¥ó¥¹¥È¡¼¥é¤Î
             <quote>upgrade</quote>
             ¥ª¥×¥·¥ç¥ó¤Ç¥·¥¹¥Æ¥à¤ò 2.1.7 ¤Ø¥¢¥Ã¥×¥°¥ì¡¼¥É
             ¤¹¤ë¤È¤¤¤¦¤ä¤êÊý¤â¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¤¢¤È¤Ç¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤Î¹½ÃÛ¤ò¤·¤¿¾ì¹ç¤Ë¤Ï¡¢
             4MB ¤Ç¤âÆ°ºî¤·¤Þ¤¹¡£
             2MB ¤Çµ¯Æ°¤ËÀ®¸ù¤·¤¿¿Í¤â¤¤¤Þ¤¹ (¤Ç¤â¤½¤Î¥·¥¹¥Æ¥à¤Ï¡¢
             ¤Û¤È¤ó¤É»È¤¤¤â¤Î¤Ë¤Ê¤ê¤Þ¤»¤ó¤Ç¤·¤¿ :-))¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="custom-boot-floppy">
           <para>¼«Ê¬ÍѤΥ¤¥ó¥¹¥È¡¼¥ë¥Õ¥í¥Ã¥Ô¡¼¤òºî¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             ¸½ºß¤Ï¥«¥¹¥¿¥à¥¤¥ó¥¹¥È¡¼¥ë¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¡Ö¤À¤±¡×¤òºî¤ëÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¥«¥¹¥¿¥à¥¤¥ó¥¹¥È¡¼¥ë¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¥¤¥á¡¼¥¸¤ò´Þ¤à¡¢
             release ´Ä¶­Á´ÂΤò¿·¤¿¤Ëºî¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¥«¥¹¥¿¥à¤Î release ´Ä¶­¤ò¤Ä¤¯¤ë¤Ë¤Ï¡¢
             <link linkend="custrel">¤³¤³¤Î»Ø¼¨</link>¤Ë¤·¤¿¤¬¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="windows-coexist">
           <para>Ʊ¤¸¥Þ¥·¥ó¤Ç Windows 95/98 ¤È¶¦Â¸¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Þ¤º Windows 95/98 ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤«¤é¡¢¤½¤Î¤¢¤È¤Ç FreeBSD
             ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£FreeBSD ¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤¬ Win95
             ¤È FreeBSD ¤Î¥Ö¡¼¥È´ÉÍý¤ò¤·¤Æ¤¯¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
             Windows 95/98 ¤ò¸å¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¾ì¹ç¤Ï¤Ò¤É¤¤¤³¤È¤Ë¡¢
             Ì䤤¹ç¤ï¤»¤ë¤³¤È¤â¤Ê¤¯¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ò¾å½ñ¤­¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
             ¤½¤¦¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤¿¾ì¹ç¤Ï¼¡¤ÎÀá¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="win95-damaged-boot-manager">
           <para>Windows 95/98 ¤¬¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤òÄÙ¤·¤Á¤ã¤Ã¤¿! ¤É¤¦¤ä¤Ã¤ÆÌ᤹¤Î?</para>
         </question>
 
         <answer>
           <para>
             ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ÎºÆ¥¤¥ó¥¹¥È¡¼¥ë¤ÎÊýË¡¤È¤·¤Æ¡¢
             FreeBSD ¤Ç¤Ï°Ê²¼¤Ë¼¨¤¹»°Ä̤ê¤ÎÊýË¡¤¬ÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
           <itemizedlist>
             <listitem>
               <para>DOS ¤òµ¯Æ°¤·¡¢FreeBSD ¤ÎÇÛÉÛʪ¤ÎÃæ¤Ë¤¢¤ë
                 <filename>tools/</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤Ø°ÜÆ°¤·¡¢
                 <filename>bootinst.exe</filename> ¤òõ¤·¤Æ¤¯¤À¤µ¤¤¡£
                 ¤½¤·¤Æ¼¡¤Î¤è¤¦¤Ë¼Â¹Ô¤·¤Þ¤¹¡£
                 </para>
 
               <screen><prompt>...\TOOLS&gt;</prompt> <userinput>bootinst.exe boot.bin</userinput></screen>
 
               <para>
                 ¤³¤¦¤¹¤ë¤³¤È¤Ç¡¢
                 ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤¬ºÆ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>
                 FreeBSD ¤Î¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤«¤éµ¯Æ°¤·¡¢
                 ¡Ö¥«¥¹¥¿¥à¡×¥¤¥ó¥¹¥È¡¼¥ë¥á¥Ë¥å¡¼¤òÁªÂò¤·¡¢
                 ³¤¤¤Æ¡Ö¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¡×¤òÁªÂò¤·¤Þ¤¹¡£
                 ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤¿¥É¥é¥¤¥Ö
                 (¿ʬºÇ½é¤Î¤â¤Î) ¤òÁªÂò¤·¡¢
                 ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥¨¥Ç¥£¥¿¤Ë¤¿¤É¤êÃ夤¤¿¤é¡¢
                 (²¿¤âÊѹ¹¤»¤º) ¤½¤Î¤Þ¤Þ (W)rite ¤ò»ØÄꤷ¤Þ¤¹¡£
                 ³Îǧ¤Î¥á¥Ã¥»¡¼¥¸¤¬½Ð¤Þ¤¹¤Î¤Ç¡Ö¤Ï¤¤(Y)¡×¤ÈÅú¤¨¡¢
                 ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ãÁªÂò¤Î²èÌÌ¤Ç³Î¼Â¤Ë <quote>Boot Manager</quote>
                 ¤òÁªÂò¤·¤Þ¤¹¡£
                 ¤³¤ì¤Ç¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤¬¥Ç¥£¥¹¥¯¤ËºÆ¤Ó½ñ¤­¹þ¤Þ¤ì¤Þ¤¹¡£
                 ¥¤¥ó¥¹¥È¡¼¥ë¥á¥Ë¥å¡¼¤«¤éÈ´¤±¤ÆºÆµ¯Æ°¤¹¤ë¤È¡¢
                 ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ï¸µÄ̤ê¤Ë¤Ê¤ê¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>FreeBSD µ¯Æ°¥Õ¥í¥Ã¥Ô¡¼ (¤â¤·¤¯¤Ï CD-ROM) ¤«¤éµ¯Æ°¤·¡¢
                 <quote>Fixit</quote> ¥á¥Ë¥å¡¼¤òÁªÂò¤·¤Þ¤¹¡£
                 Fixit ¥Õ¥í¥Ã¥Ô¡¼¤« CD-ROM #2 (<quote>live</quote>
                 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥ª¥×¥·¥ç¥ó) ¤Î¹¥¤­¤ÊÊý¤òÁªÂò¤·¤Æ
                 fixit ¥·¥§¥ë¤ËÆþ¤ê¤Þ¤¹¡£
                 ¤½¤·¤Æ¡¢¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
               <screen><prompt>Fixit#</prompt> <userinput>fdisk -B -b /boot/boot0 <replaceable>µ¯Æ°¥Ç¥Ð¥¤¥¹</replaceable></userinput></screen>
 
               <para><replaceable>µ¯Æ°¥Ç¥Ð¥¤¥¹</replaceable> ¤ÎÉôʬ¤Ï¡¢¤¿¤È¤¨¤Ð
                 <devicename>ad0</devicename> (°ìÈÖÌܤΠIDE ¥Ç¥£¥¹¥¯)¡¢
                 <devicename>ad4</devicename> (¥»¥«¥ó¥À¥ê IDE ¥³¥ó¥È¥í¡¼¥é¤Î°ìÈÖÌܤΠIDE ¥Ç¥£¥¹¥¯)¡¢
                 <devicename>da0</devicename> (°ìÈÖÌܤΠSCSI ¥Ç¥£¥¹¥¯)
                 ¤Ê¤É¤È¤¤¤Ã¤¿¡¢¼ÂºÝ¤Îµ¯Æ°¥Ç¥Ð¥¤¥¹¤òɽ¤·¤Æ¤¤¤Þ¤¹¡£</para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="boot-on-thinkpad">
           <para>
             IBM Thinkpad ¤Î A¡¢T¡¢X ¥·¥ê¡¼¥º¤Î¤¤¤º¤ì¤«¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£
             FreeBSD ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¤éµ¯Æ°¤·¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤·¤¿¡£
             ¤É¤¦¤¹¤ì¤Ð¤¤¤¤¤Ç¤¹¤«?
           </para>
         </question>
 
         <answer>
         <para>
           ¤³¤ì¤é¤Î¥Þ¥·¥ó¤Ë»È¤ï¤ì¤Æ¤¤¤ë½é´ü¤Î¥ê¥Ó¥¸¥ç¥ó¤Î IBM BIOS
           ¤Ë¤Ï¥Ð¥°¤¬¤¢¤ê¡¢FreeBSD ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¥Ç¥£¥¹¥¯¥µ¥¹¥Ú¥ó¥ÉÍѤÎ
           FAT Îΰè¤À¤È¸íǧ¤·¤Þ¤¹¡£ ¤½¤Î¤¿¤á¡¢BIOS ¤¬ FreeBSD ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò
           ¸¡½Ð¤·¤¿¤È¤³¤í¤Ç¥·¥¹¥Æ¥à¤¬¥Ï¥ó¥° (Ää»ß) ¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
         </para>
 
         <para>
           IBM <footnote><para>¤³¤ì¤Ï Keith Frechette
           <email>kfrechet@us.ibm.com</email> ¤«¤é¤Î¥á¡¼¥ë¤Ë¤è¤ê¤Þ¤¹¡£</para></footnote>
           ¤Ë¤è¤ì¤Ð¡¢°Ê²¼¤Î¥â¥Ç¥ë/BIOS ¥ê¥ê¡¼¥¹ÈÖ¹æ¤Ë¤Ï½¤Àµ¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
         </para>
 
           <informaltable frame="none">
             <tgroup cols="2">
               <thead>
                 <row>
                   <entry>¥â¥Ç¥ë</entry>
                   <entry>BIOS ¥ê¥Ó¥¸¥ç¥óÈÖ¹æ</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry>T20</entry>
                   <entry>IYET49WW °Ê¹ß</entry>
                 </row>
 
                 <row>
                   <entry>T21</entry>
                   <entry>KZET22WW °Ê¹ß</entry>
                 </row>
 
                 <row>
                   <entry>A20p</entry>
                   <entry>IVET62WW °Ê¹ß</entry>
                 </row>
 
                 <row>
                   <entry>A20m</entry>
                   <entry>IWET54WW °Ê¹ß</entry>
                 </row>
 
                 <row>
                   <entry>A21p</entry>
                   <entry>KYET27WW °Ê¹ß</entry>
                 </row>
 
                 <row>
                   <entry>A21m</entry>
                   <entry>KXET24WW °Ê¹ß</entry>
                 </row>
 
                 <row>
                   <entry>A21e</entry>
                   <entry>KUET30WW</entry>
                 </row>
               </tbody>
             </tgroup>
           </informaltable>
 
         <para>¤½¤ì¤è¤ê¿·¤·¤¤¥ê¥Ó¥¸¥ç¥ó¤Î BIOS ¤Ë¤Þ¤¿¥Ð¥°¤¬Æþ¤ê¹þ¤ó¤À¤«
           ¤â¤·¤ì¤Ê¤¤¤È¤¤¤¦Êó¹ð¤¬¤¢¤ê¤Þ¤·¤¿¡£Jacques Vidrine ¤Ï
           <email>mobile@freebsd.org</email> ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ë¤¢¤Æ¤¿ <ulink
           url="http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=200565+208320+/usr/local/www/db/text/2001/freebsd-mobile/20010429.freebsd-mobile">¥á¥Ã¥»¡¼¥¸</ulink>
           ¤Ç¡¢¤³¤ì°Ê¹ß¤Î IBM ¤Î laptop ¤Ç FreeBSD ¤¬Àµ¾ï¤Ëµ¯Æ°¤·¤Ê¤¤
           ¾ì¹ç¤Ë¤ª¤½¤é¤¯¤¦¤Þ¤¯¹Ô¤¯¡¢BIOS ¤ò¥¢¥Ã¥×¥°¥ì¡¼¥É¤Þ¤¿¤Ï
           ¥À¥¦¥ó¥°¥ì¡¼¥É¤Ç¤­¤ë¼ê½ç¤òÀâÌÀ¤·¤Æ¤¤¤Þ¤¹¡£</para>
 
         <para>
           ¤â¤·ÌäÂê¤Î¤¢¤ë BIOS ¤ò»È¤Ã¤Æ¤¤¤Æ¥¢¥Ã¥×¥°¥ì¡¼¥É¤¬Áª¤Ù¤Ê¤¤¾ì¹ç¡¢
           FreeBSD ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤«¤é FreeBSD ¤¬»È¤Ã¤Æ¤¤¤ë¥Ñ¡¼¥Æ¥£¥·¥ç¥ó ID ¤òÊѹ¹¤·¡¢
           Êѹ¹¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó ID ¤òÀµ¤·¤¯°·¤¦¤³¤È¤Î¤Ç¤­¤ë
           ¿·¤·¤¤µ¯Æ°¥Ö¥í¥Ã¥¯¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤Ç²ò·è¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
         </para>
 
         <para>
           ¤½¤ì¤Ë¤Ï¤Þ¤º¡¢
           ¥»¥ë¥Õ¥Æ¥¹¥È²èÌ̤òÄ̲᤹¤ë¾õÂ֤ˤޤǥޥ·¥ó¤ò²óÉü¤µ¤»¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           ¤½¤Î¤¿¤á¤Ë¤Ï¡¢¥Þ¥·¥ó¤¬¥×¥é¥¤¥Þ¥ê¥Ç¥£¥¹¥¯¤«¤é FreeBSD
           ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¸«¤Ä¤±¤Ê¤¤¤è¤¦¤Ë¤·¤Æµ¯Æ°¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
           ¤¿¤È¤¨¤Ð¡¢°ìÅ٥ϡ¼¥É¥Ç¥£¥¹¥¯¤ò³°¤·¤Æ¤·¤Þ¤Ã¤Æ¡¢¤½¤Î¥Ç¥£¥¹¥¯¤ò¸Å¤¤ ThinkPad
           (ThinkPad 600 ¤Ê¤É) ¤ä¥Ç¥¹¥¯¥È¥Ã¥× PC ¤ËŬÀÚ¤ÊÊÑ´¹¥±¡¼¥Ö¥ë¤ÇÀܳ¤·¤Þ¤¹¡£
           ¤½¤Î¸å FreeBSD ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºï½ü¤·¡¢
           ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ò¸µ¤Î ThinkPad ¤ËÌᤷ¤Þ¤¹¡£
           ¤³¤¦¤¹¤ë¤³¤È¤Ç ThinkPad ¤Ïµ¯Æ°²Äǽ¤Ê¾õÂÖ¤ËÌá¤ë¤Ï¤º¤Ç¤¹¡£
         </para>
 
         <para>
           ¥Þ¥·¥ó¤¬¤Á¤ã¤ó¤ÈÆ°¤¯¤è¤¦¤Ë¤Ê¤Ã¤¿¤é¡¢
           °Ê²¼¤ÎÉüµì¼ê½ç¤Ë½¾¤Ã¤Æ FreeBSD ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
         </para>
 
           <procedure>
             <step>
               <para>
                 <ulink url="http://people.freebsd.org/~bmah/ThinkPad/">http://people.freebsd.org/~bmah/ThinkPad/</ulink>
                 ¤«¤é
                 <filename>boot1</filename> ¤È
                 <filename>boot2</filename>
                 ¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤Þ¤¹¡£ ¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ï¡¢
                 ¤¢¤È¤ÇɬÍפˤʤä¿»þ¡¢¼è¤ê½Ð¤»¤ë¾ì½ê¤ËÃÖ¤¤¤Æ¤ª¤­¤Þ¤¹¡£
               </para>
             </step>
 
             <step>
               <para>ThinkPad ¤ËÉáÄÌ¤Ë FreeBSD ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
                 ¤¿¤À¤·¡¢<literal>Dangerously Dedicated</literal>
                 ¥â¡¼¥É¤ò»È¤Ã¤Æ¤Ï<emphasis>¤¤¤±¤Þ¤»¤ó</emphasis>¡£
                 ¤Þ¤¿¡¢¥¤¥ó¥¹¥È¡¼¥ë¤¬½ª¤ï¤Ã¤Æ¤âºÆµ¯Æ°¤·¤Æ¤Ï<emphasis>¤¤¤±¤Þ¤»¤ó</emphasis>¡£</para>
             </step>
 
             <step>
               <para>
                 <quote>¶ÛµÞ¥Û¥í¥°¥é¥Õ¥£¥Ã¥¯¥·¥§¥ë (Emergency Holographic Shell)</quote>
                 (<keycombo><keycap>ALT</keycap><keycap>F4</keycap></keycombo>)
                 ¤ËÀÚ¤êÂؤ¨¤ë¤«¡¢<quote>fixit</quote> ¥·¥§¥ë¤òµ¯Æ°¤·¤Þ¤¹¡£
               </para>
             </step>
 
             <step>
               <para>
                 &man.fdisk.8; ¤ò»È¤Ã¤Æ FreeBSD ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó ID ¤ò
                 <literal>165</literal> ¤«¤é <literal>166</literal> ¤Ë
                 Êѹ¹¤·¤Þ¤¹ (¤³¤ì¤Ï OpenBSD ¤Ç»È¤ï¤ì¤Æ¤¤¤ë¤â¤Î¤Ç¤¹)¡£
               </para>
             </step>
 
             <step>
               <para>
                 <filename>boot1</filename> ¤È
                 <filename>boot2</filename>
                 ¤Î¥Õ¥¡¥¤¥ë¤ò¥í¡¼¥«¥ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë»ý¤Ã¤ÆÍè¤Þ¤¹¡£
               </para>
             </step>
 
             <step>
               <para>
                 &man.disklabel.8; ¤ò»È¤Ã¤Æ
                 <filename>boot1</filename> ¤È
                 <filename>boot2</filename> ¤ò
                 FreeBSD ¤Î¥¹¥é¥¤¥¹¤Ë½ñ¤­¹þ¤ß¤Þ¤¹¡£
               </para>
 
               <screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 ad0s<replaceable>n</replaceable></userinput></screen>
 
               <para>
                 <replaceable>n</replaceable> ¤Ï¡¢
                 ¤¢¤Ê¤¿¤¬ FreeBSD ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¥¹¥é¥¤¥¹¤ÎÈÖ¹æ¤Ç¤¹¡£
               </para>
             </step>
 
             <step>
               <para>
                 ºÆµ¯Æ°¤·¤Þ¤¹¡£µ¯Æ°¥×¥í¥ó¥×¥È¤Ï <literal>OpenBSD</literal>
                 ¤È¼¨¤·¤Þ¤¹¤¬¡¢¼ÂºÝ¤Ë¤Ï¡¢¤½¤ì¤Ç FreeBSD ¤¬µ¯Æ°¤·¤Þ¤¹¡£
               </para>
             </step>
          </procedure>
 
           <para>
             ¤³¤ÎÊýË¡¤Ç FreeBSD ¤È OpenBSD
             ¤ò¥Ç¥å¥¢¥ë¥Ö¡¼¥È¤¹¤ëÊýË¡¤Ï¡¢ÆɼԤؤÎÎý½¬ÌäÂê¤È¤·¤Þ¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="install-bad-blocks">
           <para>ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Î¤¢¤ë¥Ç¥£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>FreeBSD 3.0 °ÊÁ°¤Î¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
             ÉÔÎÉ¥Ö¥í¥Ã¥¯¤ò¼«Æ°Åª¤ËºÆ¥Þ¥Ã¥Ô¥ó¥°¤¹¤ë
             <command>bad144</command> ¤È¤¤¤¦¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤·¤¿¤¬¡¢
             ¸½ºß¤Î IDE ¥É¥é¥¤¥Ö¤Ï¥É¥é¥¤¥Ö¼«¿È¤¬¤³¤Îµ¡Ç½¤òÈ÷¤¨¤Æ¤¤¤ë¤¿¤á¡¢
             <command>bad144</command> ¤Ï FreeBSD ¥½¡¼¥¹¥Ä¥ê¡¼¤«¤éºï½ü¤µ¤ì¤Þ¤·¤¿¡£
             FreeBSD 3.0 ¤«¤½¤ì°Ê¹ß¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¤¤¤È»×¤Ã¤Æ¤¤¤ë¤Ê¤é¡¢
             Èæ³ÓŪ¿·¤·¤¤¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ò¹ØÆþ¤¹¤ë¤³¤È¤ò¶¯¤¯¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
             ¿·¤·¤¤¥É¥é¥¤¥Ö¤ò¹ØÆþ¤¹¤ëµ¤¤¬¤Ê¤±¤ì¤Ð¡¢FreeBSD 2.x ¤òÍøÍѤ¹¤ë¤Ù¤­¤Ç¤¹¡£</para>
 
           <para>¸½ºß¤Î IDE ¥É¥é¥¤¥Ö¤ÇÉÔÎÉ¥Ö¥í¥Ã¥¯¤Ë¤è¤ë¥¨¥é¡¼¤¬È¯À¸¤·¤¿¾ì¹ç¡¢
             ¤Þ¤â¤Ê¤¯¥É¥é¥¤¥Ö¤¬¸Î¾ã¤¹¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹
             (¤½¤ì¤Ï¤½¤Î¥É¥é¥¤¥ÖÆ⢤κƥޥåԥ󥰵¡Ç½¤Ç¤Ï
             ÉÔÎÉ¥Ö¥í¥Ã¥¯¤¬½¤Àµ¤Ç¤­¤Ê¤¯¤Ê¤Ã¤¿¤È¤¤¤¦¤³¤È¤Ç¤¢¤ê¡¢
             ¥Ç¥£¥¹¥¯¤¬¤Ò¤É¤¯²õ¤ì¤Æ¤¤¤ë¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹)¡£
             ¿·¤·¤¤¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤Ë¸ò´¹¤·¤Þ¤·¤ç¤¦¡£</para>
 
           <para>ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Î¤¢¤ë SCSI ¥É¥é¥¤¥Ö¤Î¾ì¹ç¤Ï¡¢
             <link linkend="awre">¤³¤Î²óÅú</link>¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="boot-floppy-strangeness">
           <para>¥¤¥ó¥¹¥È¡¼¥é¤«¤éµ¯Æ°¤·¤¿¤éÊѤʤ³¤È¤Ë¤Ê¤ê¤Þ¤·¤¿!</para>
         </question>
 
         <answer>
           <para>
             ¥¤¥ó¥¹¥È¡¼¥é¤«¤éµ¯Æ°¤·¤è¤¦¤È¤·¤¿¤È¤­¤Ë¡¢¥Þ¥·¥ó¤¬¸Ç¤Þ¤Ã¤Æ¤·
             ¤Þ¤¦¤È¤«¼«Á³¤ÈºÆµ¯Æ°¤·¤Æ¤·¤Þ¤¦¤È¤¤¤Ã¤¿¸½¾Ý¤Ç¤¢¤ì¤Ð¡¢
             ¼¡¤Î»°¤Ä¤Î¹àÌܤò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <orderedlist>
             <listitem>
               <para>¿·ÉʤΡ¢¥Õ¥©¡¼¥Þ¥Ã¥È¤·¤¿¤Æ¤Î¡¢
                 ¥¨¥é¡¼¤Î¤Ê¤¤¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ò»È¤Ã¤Æ¤¤¤Þ¤¹¤«?
                 (»°Ç¯´Ö¤â¥Ù¥Ã¥É¤Î²¼¤ËÊüÃÖ¤µ¤ì¤Æ¤¤¤¿»¨»ï¤ÎÉÕÏ¿¤ß¤¿¤¤¤Ê¤ä¤Ä¤Ç¤Ï¤Ê¤¯¤Æ¡¢
                 Çã¤Ã¤Æ¤­¤¿¤Ð¤«¤ê¤Î¿·Éʤò»È¤Ã¤Æ¤¯¤À¤µ¤¤)
               </para>
             </listitem>
 
             <listitem>
               <para>¥Õ¥í¥Ã¥Ô¡¼¥¤¥á¡¼¥¸¤ò¥Ð¥¤¥Ê¥ê¥â¡¼¥É¤Ç¥À¥¦¥ó¥í¡¼¥É¤·¤Þ¤·¤¿¤«?
                 (º¤¤Ã¤¿´é¤ò¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£»ä¤¿¤Á¤ÎÃæ¤Ç°ìÈÖÍ¥½¨¤Ê¿Í¤Ç¤µ¤¨¡¢
                 ¾¯¤Ê¤¯¤È¤â°ì²ó¤Ï¥Ð¥¤¥Ê¥ê¥Õ¥¡¥¤¥ë¤ò
                 ASCII ¥â¡¼¥É¤Ç»×¤¤¤¬¤±¤º¥À¥¦¥ó¥í¡¼¥É¤·¤¿¤³¤È¤¬¤¢¤ë¤Î¤Ç¤¹!)
               </para>
             </listitem>
 
             <listitem>
               <para>Windows95 ¤¢¤ë¤¤¤Ï Windows98 ¤ò»ÈÍѤ·¤Æ¤¤¤ë¤Ê¤é¡¢
                 ¤¢¤ê¤Î¤Þ¤Þ¤ÎËÜʪ¤Î DOS ¤Ç
                 <command>fdimage</command> ¤«
                 <command>rawrite</command> ¤ò¼Â¹Ô¤·¤Þ¤·¤¿¤«?
                 ¤³¤ì¤é¤Î OS ¤Ï¥Ç¥£¥¹¥¯ºîÀ®¥×¥í¥°¥é¥à¤Î¤è¤¦¤Ê¡¢
                 ¥Ï¡¼¥É¥¦¥§¥¢¤ËľÀܽñ¤­¹þ¤ß¤ò¹Ô¤Ê¤¦¥×¥í¥°¥é¥à¤Ë´³¾Ä¤¹¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
                 GUI ¤ÎÃæ¤Î DOS ¥·¥§¥ëÆâÉô¤ÇÆ°ºî¤·¤Æ¤¤¤ë¾ì¹ç¤Ç¤â¡¢
                 ¤³¤ÎÌäÂê¤ÏȯÀ¸¤·¤Þ¤¹¡£</para>
             </listitem>
           </orderedlist>
 
           <para>¤Þ¤¿¡¢Netscape
             ¤Ç¥Ö¡¼¥È¥¤¥á¡¼¥¸¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¾ì¹ç¤âÌäÂ꤬¤¢¤ë¤³¤È¤¬Êó¹ð¤µ¤ì¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢
             ¤Ç¤­¤ì¤ÐÊ̤ΠFTP ¥¯¥é¥¤¥¢¥ó¥È¤ò»È¤¦¤Î¤¬¤è¤¤¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="no-install-cdrom">
           <para>ATAPI CD-ROM ¤«¤éµ¯Æ°¤·¤¿¤Î¤Ç¤¹¤¬¡¢
             ¥¤¥ó¥¹¥È¡¼¥ë¥×¥í¥°¥é¥à¤Ï CD-ROM ¤¬¸«¤Ä¤«¤ê¤Þ¤»¤ó¤È¸À¤Ã¤Æ¤­¤Þ¤¹¡£
             CD-ROM ¤Ï¤É¤³¤Ë¹Ô¤Ã¤Æ¤·¤Þ¤Ã¤¿¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>¤³¤ÎÌäÂê¤ÏÄ̾CD-ROM ¥É¥é¥¤¥Ö¤ÎÀßÄê¥ß¥¹¤Ë¤è¤Ã¤ÆȯÀ¸¤·¤Þ¤¹¡£
             ÂçÉôʬ¤Î PC ¤Î CD-ROM ¥É¥é¥¤¥Ö¤Ï¡¢
             ¥»¥«¥ó¥À¥ê¦¤Î IDE
             ¥³¥ó¥È¥í¡¼¥é¤Î¥¹¥ì¡¼¥Ö¥Ç¥Ð¥¤¥¹¤È¤·¤ÆÀܳ¤µ¤ì¡¢
             ¥Þ¥¹¥¿¥Ç¥Ð¥¤¥¹¤¬¤Ê¤¤¾õÂ֤ǽв٤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ÎÀܳÊýË¡¤Ï ATAPI µ¬³Ê°ãÈ¿¤Ê¤Î¤Ç¡¢
             Windows ¤Ïµ¬³Ê¤É¤ª¤ê¤ËÆ°¤¤¤¿¤ê¡¢Æ°¤«¤Ê¤«¤Ã¤¿¤ê¤·¤Þ¤¹¤¬¡¢
             BIOS ¤Ïµ¯Æ°»þ¤Ëµ¬³Ê°ãÈ¿¤ò̵»ë¤·¤Þ¤¹¡£
             ¤½¤Î¤¿¤á BIOS ¤Ïµ¯Æ°»þ¤Ë CD-ROM ¤ò¸«¤Ä¤±¤é¤ì¤Þ¤¹¤¬¡¢
             FreeBSD ¤Ï CD-ROM ¤ò¸«¤Ä¤±¤é¤ì¤º¡¢
             ¥¤¥ó¥¹¥È¡¼¥ë¤ò´°Î»¤Ç¤­¤Ê¤¤¤Î¤Ç¤¹¡£</para>
 
           <para>CD-ROM ¤¬ Àܳ¤µ¤ì¤Æ¤¤¤ë
             IDE ¥³¥ó¥È¥í¡¼¥é¤Î¥Þ¥¹¥¿¥Ç¥Ð¥¤¥¹¤È¤Ê¤ë¤è¤¦¤ËÀßÄꤹ¤ë¤«¡¢
             ¤â¤·¤¯¤Ï¥Þ¥¹¥¿¡¢
             ¥¹¥ì¡¼¥Ö¤ÎξÊý¤Ë¥Ç¥Ð¥¤¥¹¤¬Àܳ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¥·¥¹¥Æ¥à¤òºÆ¹½À®¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cannot-install-tape">
           <para>¤¢¤ì¤ì? ¥Æ¡¼¥×¤«¤é¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤»¤ó!</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 2.1.7R ¤ò¥Æ¡¼¥×¤«¤é¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¾ì¹ç¡¢
             tar ¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤ò 10 (5120 ¥Ð¥¤¥È)
             ¤Ë¤·¤¿¥Æ¡¼¥×¤òºî¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¥Ç¥Õ¥©¥ë¥È ¤Î tar ¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤Ï 20 (10240 ¥Ð¥¤¥È) ¤Ç¡¢
             ¤³¤Î¥Ç¥Õ¥©¥ë¥È¥µ¥¤¥º¤Çºî¤é¤ì¤¿¥Æ¡¼¥×¤Ç¤Ï FreeBSD 2.1.7R
             ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
             ¤â¤·¤³¤¦¤·¤¿¥Æ¡¼¥×¤ò»È¤¦¤È¡¢
             ¥ì¥³¡¼¥É¥µ¥¤¥º¤¬Â礭¤¹¤®¤ë¤È¤¤¤¦¥¨¥é¡¼¤¬µ¯¤­¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="parallel-connect">
           <para>PLIP ·Ðͳ¤ÇÆó¤Ä FreeBSD box ¤òÀܳ¤·¤¿¤¤¤Î¤Ç¤¹¤¬</para>
         </question>
 
         <answer>
           <para>Laplink ¥Ñ¥é¥ì¥ë¥±¡¼¥Ö¥ë¤òÍÑ°Õ¤·¤Æ¡¢
             ξÊý¤Î PC ¤Î¥«¡¼¥Í¥ë¤Ë <devicename>lpt</devicename>
             ¥É¥é¥¤¥Ð¤¬ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.user; <userinput>dmesg | grep lp</userinput>
 lpt0 at 0x378-0x37f irq 7 on isa
 lpt0: Interrupt-driven port
 lp0: TCP/IP capable interface</screen>
 
           <para>
             ¥Ñ¥é¥ì¥ë¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ë Laplink
             ¥Ñ¥é¥ì¥ë¥±¡¼¥Ö¥ë¤òÀܳ¤·¤Þ¤¹¡£
           </para>
 
           <para>
             <username>root</username>
             ¤Ë¤Ê¤Ã¤Æ¡¢Î¾Êý¤Ç <devicename>lp0</devicename>
             ¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¤¥ó¥¿¥Õ¥§¡¼¥¹¥Ñ¥é¥á¡¼¥¿¤òÀßÄꤷ¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢¥Û¥¹¥È <hostid>max</hostid> ¤È <hostid>moritz</hostid> ¤òÀܳ¤·¤¿¤¤¾ì¹ç¡¢
           </para>
 
           <programlisting>                max &lt;-----&gt; moritz
 IP Address      10.0.0.1        10.0.0.2</programlisting>
 
           <para>max ¦¤Ç¼¡¤Î¤è¤¦¤Ë¤·¤Æ¡¢</para>
 
           <screen>&prompt.root; <userinput>ifconfig lp0 10.0.0.1 10.0.0.2</userinput></screen>
 
           <para>moritz ¦¤ÇƱÍͤ˼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>ifconfig lp0 10.0.0.2 10.0.0.1</userinput></screen>
           <para>°Ê¾å¤Ç¤¹!
             &man.lp.4; ¤È &man.lpt.4;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤â»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>¤Þ¤¿¡¢
             <filename>/etc/hosts</filename> ¤Ë¥Û¥¹¥È¤ÎÄɲä⤷¤Þ¤·¤ç¤¦¡£
           </para>
 
           <programlisting>127.0.0.1               localhost.my.domain localhost
 10.0.0.1                max.my.domain max
 10.0.0.2                moritz.my.domain moritz</programlisting>
 
           <para>
             Æ°ºî³Îǧ¤Ï¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <para><hostid>max</hostid> ¦:</para>
 
           <screen>&prompt.user; <userinput>ifconfig lp0</userinput>
 lp0: flags=8851&lt;UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
         inet 10.0.0.1 --&gt; 10.0.0.2 netmask 0xff000000</screen>
 
           <screen>&prompt.user; <userinput>netstat -r</userinput>
 Routing tables
 
 Internet:
 Destination        Gateway            Flags     Refs     Use     Netif Expire
 moritz              max              UH          4   127592       lp0</screen>
 
           <screen>&prompt.user; <userinput>ping -c 4 moritz</userinput>
 PING moritz (10.0.0.2): 56 data bytes
 64 bytes from 10.0.0.2: icmp_seq=0 ttl=255 time=2.774 ms
 64 bytes from 10.0.0.2: icmp_seq=1 ttl=255 time=2.530 ms
 64 bytes from 10.0.0.2: icmp_seq=2 ttl=255 time=2.556 ms
 64 bytes from 10.0.0.2: icmp_seq=3 ttl=255 time=2.714 ms
 
 --- moritz ping statistics ---
 4 packets transmitted, 4 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="install-PLIP">
           <para>¥é¥Ã¥×¥È¥Ã¥× PC ¤Ë PLIP ·Ðͳ¤Ç¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¼¡¤Î¤è¤¦¤Ë¤·¤Æ¡¢Æó¤Ä¤Î¥³¥ó¥Ô¥å¡¼¥¿¤ò Laplink
             ¥Ñ¥é¥ì¥ë¥±¡¼¥Ö¥ë¤ÇÀܳ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <table>
             <title>¥Í¥Ã¥È¥ï¡¼¥¯ÀܳÍѤΥѥé¥ì¥ë¥±¡¼¥Ö¥ë¤Î·ëÀþ</title>
 
             <tgroup cols="5">
               <thead>
                 <row>
                   <entry>A-name</entry>
 
                   <entry>A ¦</entry>
 
                   <entry>B ¦</entry>
 
                   <entry>ÀâÌÀ</entry>
 
                   <entry>¥Ý¡¼¥È / ¥Ó¥Ã¥È</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry><literallayout>DATA0
 -ERROR</literallayout></entry>
 
                   <entry><literallayout>2
 15</literallayout></entry>
 
                   <entry><literallayout>15
 2</literallayout></entry>
 
                   <entry>Data</entry>
 
                   <entry><literallayout>0/0x01
 1/0x08</literallayout></entry>
                 </row>
 
                 <row>
                   <entry><literallayout>DATA1
 +SLCT</literallayout></entry>
 
                   <entry><literallayout>3
 13</literallayout></entry>
 
                   <entry><literallayout>13
 3</literallayout></entry>
 
                   <entry>Data</entry>
 
                   <entry><literallayout>0/0x02
 1/0x10</literallayout></entry>
                 </row>
 
                 <row>
                   <entry><literallayout>DATA2
 +PE</literallayout></entry>
 
                   <entry><literallayout>4
 12</literallayout></entry>
 
                   <entry><literallayout>12
 4</literallayout></entry>
 
                   <entry>Data</entry>
 
                   <entry><literallayout>0/0x04
 1/0x20</literallayout></entry>
                 </row>
 
                 <row>
                   <entry><literallayout>DATA3
 -ACK</literallayout></entry>
 
                   <entry><literallayout>5
 10</literallayout></entry>
 
                   <entry><literallayout>10
 5</literallayout></entry>
 
                   <entry>Strobe</entry>
 
                   <entry><literallayout>0/0x08
 1/0x40</literallayout></entry>
                 </row>
 
                 <row>
                   <entry><literallayout>DATA4
 BUSY</literallayout></entry>
 
                   <entry><literallayout>6
 11</literallayout></entry>
 
                   <entry><literallayout>11
 6</literallayout></entry>
 
                   <entry>Data</entry>
 
                   <entry><literallayout>0/0x10
 1/0x80</literallayout></entry>
                 </row>
 
                 <row>
                   <entry>GND</entry>
 
                   <entry>18-25</entry>
 
                   <entry>18-25</entry>
 
                   <entry>GND</entry>
 
                   <entry>-</entry>
                 </row>
               </tbody>
             </tgroup>
           </table>
 
           <para>¤Þ¤¿¡¢
             <link linkend="pao">Mobile Computing
               ¤Ë¤Ä¤¤¤Æ¤Î¥Ú¡¼¥¸</link>¤â¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="geometry">
           <para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤Ë¤Ï¡¢
             ¤É¤Î¥¸¥ª¥á¥È¥ê¤ò»È¤¦¤Ù¤­¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
             <note>
               <para>¤³¤³¤Ç¥Ç¥£¥¹¥¯¤Î¡Ö¥¸¥ª¥á¥È¥ê¡×¤È¤Ï¡¢¥Ç¥£¥¹¥¯¤Î¥·¥ê¥ó¥À¡¢¥Ø¥Ã¥À¡¢
                 ¥È¥é¥Ã¥¯Åö¤ê¤Î¥»¥¯¥¿¤Î¿ô¤ò°ÕÌ£¤·¤Æ¤¤¤Þ¤¹ - Êص¹¾å¡¢
                 C/H/S ¤È¤¹¤ë¤³¤È¤Ë¤·¤Þ¤¹¡£¤³¤ì¤Ï¥Ç¥£¥¹¥¯¤Î¤É¤ÎÎΰè¤ÇÆɤ߽ñ¤­¤ò
                 ¹Ô¤Ê¤¦¤«¤ò PC ¤Î BIOS ¤¬·èÄꤹ¤ë¼êÃʤȤʤê¤Þ¤¹¡£</para>
             </note>
 
           <para>
             ¤³¤ì¤Ë¤Ä¤¤¤Æ¤Ï¤¢¤ëÍýͳ¤Î¤¿¤á¤Ë¡¢¸í²ò¤µ¤ì¤Æ¤¤¤ëÅÀ¤¬Â¿¤¤¤è¤¦¤Ç¤¹¡£
             ¤Þ¤ººÇ½é¤Ë¡¢FreeBSD ¤Ï¥Ç¥£¥¹¥¯¥Ö¥í¥Ã¥¯¤ÇÆ°ºî¤·¤Æ¤¤¤ë¤¿¤á¡¢
             SCSI ¥É¥é¥¤¥Ö¤Î <quote>ʪÍýŪ</quote> ¤Ê¥¸¥ª¥á¥È¥ê¤È¤¤¤¦¸À¤¤Êý¤Ï¡¢
             ¤Þ¤Ã¤¿¤¯¸«Åö°ã¤¤¤Î¤â¤Î¤Ç¤¹¡£»ö¼Â¡¢
             ¥»¥¯¥¿¤ÎÌ©Å٤ϥǥ£¥¹¥¯¤Ë¤è¤Ã¤Æ¤Þ¤Á¤Þ¤Á¤Ç¤¢¤ë¤¿¤á¡¢
             ʪÍýŪ¤Ê¥¸¥ª¥á¥È¥ê¤È¤¤¤¦¤â¤Î¤Ï¸ºß¤·¤Þ¤»¤ó¡£
             À½Â¤¼Ô¤¬ <quote>ËÜÅö¤Î</quote> ʪÍýŪ¤Ê¥¸¥ª¥á¥È¥ê¤È¸øɽ¤·¤Æ¤¤¤ë¤â¤Î¤ÏÄ̾
             Èà¤é¤¬¸¡ºº¤·¤ÆÆÀ¤¿ºÇ¾®¤Î»ÈÍÑÉÔ²ÄÍÆÎ̤ηë²Ì¤Î¥¸¥ª¥á¥È¥ê¤Î¤³¤È¤Ç¤¹¡£
             IDE ¤Î¾ì¹ç¡¢FreeBSD ¤Ï C/H/S ¤ÇÆ°ºî¤·¤Þ¤¹¤¬¡¢
             ºÇ¶á¤Î¥É¥é¥¤¥Ö¤Ï¤¹¤Ù¤Æ¡¢¤³¤ì¤òÆâÉô¤Ç»²¾È¤¹¤ë¥Ö¥í¥Ã¥¯¤ËÊÑ´¹¤·¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ÌäÂê¤Ï¤È¤Ê¤ë¤Î¤Ï<emphasis>ÏÀÍýŪ¤Ê</emphasis>¥¸¥ª¥á¥È¥ê¤Ç¤¹¡£
             ¤³¤ì¤Ï BIOS ¤¬¤½¤Î¥Ç¥£¥¹¥¯¤Î¥¸¥ª¥á¥È¥ê¤Ë¤Ä¤¤¤ÆÄ´¤Ù¤¿ºÝ¤Ë¼èÆÀ¤µ¤ì¤ë¤â¤Î¤Ç¤¢¤ê¡¢
             ¤½¤Î¸å¤Î¥Ç¥£¥¹¥¯¤Ø¤Î¥¢¥¯¥»¥¹¤Ë»ÈÍѤ·¤Þ¤¹¡£
             FreeBSD ¤Ïµ¯Æ°»þ¤Ë BIOS ¤ò»ÈÍѤ¹¤ë¤¿¤á¡¢
             ¤³¤ì¤òÀµ¤·¤¯¼èÆÀ¤¹¤ë¤³¤È¤ÏÈó¾ï¤Ë½ÅÍפʤ³¤È¤Ê¤Î¤Ç¤¹¡£
             ¼ÂºÝ¤Ë¡¢¥Ç¥£¥¹¥¯¾å¤ËÊ£¿ô¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬¤¢¤ë¾ì¹ç¤Ï¡¢
             ¥¸¥ª¥á¥È¥ê¤Ï¤É¤³¤«¤é¤Ç¤âƱ¤¸¤è¤¦¤Ë²ò¼á¤µ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤½¤¦¤·¤Ê¤¤¤È¡¢µ¯Æ°»þ¤Ë¿¼¹ï¤ÊÌäÂ꤬ȯÀ¸¤·¤Þ¤¹¡£
           </para>
 
           <para>
             SCSI ¥Ç¥£¥¹¥¯¤Ç¤Ï¡¢
             »ÈÍѤ¹¤ë¥¸¥ª¥á¥È¥ê¤Ï¥³¥ó¥È¥í¡¼¥é¤Î³ÈÄ¥ BIOS
             ¥È¥é¥ó¥¹¥ì¡¼¥·¥ç¥ó (<quote>&gt;1GB ¤Î
             DOS ¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤Î¥µ¥Ý¡¼¥È</quote>
             ¤È¤â¸Æ¤Ð¤ì¤Þ¤¹) ¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤«¤É¤¦¤«¤Ë¤è¤ê¤Þ¤¹¡£
             ̵¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢N ¥·¥ê¥ó¥À¡¢64 ¥Ø¥Ã¥É¡¢
             32 ¥»¥¯¥¿/¥È¥é¥Ã¥¯¤ò»ÈÍѤ·¤Þ¤¹¤¬¡¢
             ¤³¤³¤Ç `N' ¤Ï MB ñ°Ì¤Î¥Ç¥£¥¹¥¯ÍÆÎ̤Ǥ¹¡£
             ¤¿¤È¤¨¤Ð¡¢2GB ¥Ç¥£¥¹¥¯¤Ï¸«¤«¤±¾å 2048 ¥·¥ê¥ó¥À¡¢64 ¥Ø¥Ã¥É¡¢
             32 ¥»¥¯¥¿/¥È¥é¥Ã¥¯¤È¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤½¤ì¤¬¡ÖÍ­¸ú¡×¤Ë¤Ê¤Ã¤Æ¤ª¤ê (MS-DOS
             ¤Ç¤Ï¤³¤ÎÊýË¡¤Ç¡¢¤¢¤ëÀ©¸Â¤ò²óÈò¤¹¤ë¾ì¹ç¤â¤¢¤ê¤Þ¤¹)¡¢
             ¥Ç¥£¥¹¥¯ÍÆÎ̤¬ 1GB ¤ò±Û¤¨¤ë¾ì¹ç¤Ï¡¢M ¥·¥ê¥ó¥À¡¢
             63 ¥»¥¯¥¿/¥È¥é¥Ã¥¯ (64 ¡Ö¤Ç¤Ï¤Ê¤¯¡×)¡¢
             255 ¥Ø¥Ã¥É¤ò»ÈÍѤ·¤Þ¤¹¡£
             `M' ¤Ï MB ñ°Ì¤Î¥Ç¥£¥¹¥¯ÍÆÎ̤ò 7.844238(!)
             ¤Ç³ä¤Ã¤¿ÃͤȤʤê¤Þ¤¹¡£
             ¤È¤¤¤¦¤³¤È¤Ç¡¢2GB ¥Ç¥£¥¹¥¯¤ÎÎã¤Ç¤Ï¡¢
             261 ¥·¥ê¥ó¥À¡¢63 ¥»¥¯¥¿/¥È¥é¥Ã¥¯¡¢255 ¥Ø¥Ã¥É¤È¤Ê¤ê¤Þ¤¹¡£
             (ÌõÃí: °Ê¾å¤Ï Adaptec ¼Ò¤È NCR ¼ÒÀ½¤Î SCSI ¥¢¥À¥×¥¿¤Î¾ì¹ç¤Ç¤¹¡£
             SCSI ¥¢¥À¥×¥¿¤Ë¤è¤Ã¤ÆÊÑ´¹¤Î¿ôÃͤ¬ÊѤï¤Ã¤Æ¤¯¤ë¤Î¤Ç¥Þ¥Ë¥å¥¢¥ë¤ò
             »²¾È¤·¤Æ¤¯¤À¤µ¤¤)¡£
           </para>
 
           <para>
             ¤³¤ì¤Ë¤Ä¤¤¤Æ¤è¤¯Ê¬¤«¤é¤Ê¤¤¾ì¹ç¤ä
             FreeBSD ¤¬¥¤¥ó¥¹¥È¡¼¥ëÃæ¤ËÀµ¤·¤¯¥¸¥ª¥á¥È¥ê¤ò¼èÆÀ¤Ç¤­¤Ê¤¤¾ì¹ç¡¢
             ¤³¤ì¤ò²óÈò¤¹¤ë¤â¤Ã¤È¤â´Êñ¤ÊÊýË¡¤Ï¡¢
             ¥Ç¥£¥¹¥¯¤Ë¾®¤µ¤Ê DOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºî¤ë¤³¤È¤Ç¤¹¡£
             ¤½¤¦¤¹¤ë¤ÈÀµ¤·¤¤¥¸¥ª¥á¥È¥ê¤¬¼èÆÀ¤µ¤ì¤ë¤Ï¤º¤Ç¤¹ (¤½¤·¤Æ¡¢
             »Ä¤·¤Æ¤ª¤­¤¿¤¯¤Ê¤¤¤È¤«¡¢
             ¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤Î¥×¥í¥°¥é¥ß¥ó¥°ÍѤ˻Ȥ¤¤¿¤¤¾ì¹ç¤Ê¤É¤Ë¤Ï¡¢
             ¤¤¤Ä¤Ç¤â¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥¨¥Ç¥£¥¿¤Ç DOS
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºï½ü¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹)¡£
           </para>
 
           <para>
             ¤â¤¦°ì¤Ä¤ÎÊýË¡¤È¤·¤Æ¡¢FreeBSD
             ¤È°ì½ï¤ËÇÛÉÛ¤µ¤ì¤Æ¤¤¤ë¥Õ¥ê¡¼¤Ç»È¤¨¤ë¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ë
             <filename>pfdisk.exe</filename>
             (FreeBSD CD-ROM ¤Î <filename>tools</filename>
             ¥Ç¥£¥ì¥¯¥È¥ê¤ä¡¢Â¾¤Î¤µ¤Þ¤¶¤Þ¤Ê FTP
             ¥µ¥¤¥È¤Ë¤¢¤ê¤Þ¤¹)¤È¸Æ¤Ð¤ì¤ë¤â¤Î¤¬¤¢¤ê¡¢
             ¥Ç¥£¥¹¥¯¾å¤Î¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬»ÈÍѤ·¤Æ¤¤¤ë
             ¥¸¥ª¥á¥È¥ê¤òÄ´¤Ù¤ë¤Î¤ËÌòΩ¤Á¤Þ¤¹¡£
             ¤³¤Î¥¸¥ª¥á¥È¥ê¾ðÊó¤Ï¡¢
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥¨¥Ç¥£¥¿¤ËÆþÎϤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="disk-divide-restrictions">
           <para>¥Ç¥£¥¹¥¯¤Îʬ³ä¤Î»ÅÊý¤Ç²¿¤«À©¸Â¤Ï¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Ï¤¤¡£
             BIOS ¤¬¥«¡¼¥Í¥ë¤òµ¯Æ°¤Ç¤­¤ë¤è¤¦¤Ë¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤¬
             1024 ¥·¥ê¥ó¥À°ÊÆâ¤Ë¤¢¤ë¤³¤È¤ò³Îǧ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹ (¤³¤ì¤Ï
             FreeBSD ¤Ç¤Ï¤Ê¤¯ PC ¤Î BIOS ¤ÎÀ©¸Â¤Ç¤¹)¡£
           </para>
 
           <para>
             SCSI ¥É¥é¥¤¥Ö¤Ç¤Ï¡¢Ä̾ï¤Ï¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤¬ºÇ½é¤Î 1024MB
             ¤Ë¼ý¤Þ¤Ã¤Æ¤¤¤ë¤³¤È¤¬Á°Äó¤È¤Ê¤ê¤Þ¤¹ (¤Þ¤¿¤Ï³ÈÄ¥ BIOS
             ¥È¥é¥ó¥¹¥ì¡¼¥·¥ç¥ó¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤ÏºÇ½é¤Î 4096MB -
             ¾¤Î¼ÁÌä¤ò¤´Í÷¤¯¤À¤µ¤¤)¡£IDE ¤Ç¤½¤ì¤ËÁêÅö¤¹¤ëÃÍ¤Ï 504MB
             ¤È¤Ê¤ê¤Þ¤¹ (ÌõÃí: E-IDE
             Âбþ¤Î BIOS ÅëºÜ¥Þ¥·¥ó¤Î¾ì¹ç¤Ï
             IDE ¤Î 504MB ¤È¤¤¤¦À©¸Â¤Ï¤¢¤ê¤Þ¤»¤ó)¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="disk-manager">
           <para>ÂçÍÆÎ̥ǥ£¥¹¥¯¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢¥Ç¥£¥¹¥¯¥Þ¥Í¡¼¥¸¥ã¤Ï»È¤¨¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Ï Ontrack Disk Manager ¤òǧ¼±¤·¡¢¤³¤ì¤ò¹Íθ¤Ë¤¤¤ì¤Þ¤¹¡£
             ¾¤Î¥Ç¥£¥¹¥¯¥Þ¥Í¡¼¥¸¥ã¤Ï¥µ¥Ý¡¼¥È¤·¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¥Ç¥£¥¹¥¯Á´ÂΤò FreeBSD ¤Ç»È¤¤¤¿¤¤¾ì¹ç¡¢
             ¥Ç¥£¥¹¥¯¥Þ¥Í¡¼¥¸¥ã¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£
             BIOS ¤¬°·¤¨¤ëÍÆÎÌ (Ä̾ï 504MB) ¤¤¤Ã¤Ñ¤¤¤Ç¥Ç¥£¥¹¥¯¤ÎÀßÄê¤ò¹Ô¤Ê¤¦¤È¡¢
             FreeBSD ¤Ï¼ÂºÝ¤ÎÍÆÎ̤ò»»½Ð¤¹¤ë¤Ï¤º¤Ç¤¹¡£
             MFM ¥³¥ó¥È¥í¡¼¥éÉÕ¤­¤Î¸Å¤¤¥Ç¥£¥¹¥¯¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
             FreeBSD ¤Ë»ÈÍѤ¹¤ë¥·¥ê¥ó¥À¿ô¤ò¾ÜºÙ¤Ë»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             FreeBSD
             ¤È¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬Æþ¤Ã¤Æ¤¤¤ë¥Ç¥£¥¹¥¯¤ò»ÈÍѤ·¤¿¤¤¾ì¹ç¤Ï¡¢
             ¥Ç¥£¥¹¥¯¥Þ¥Í¡¼¥¸¥ã¤Ê¤·¤Ç¤â¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£
             FreeBSD
             ¤Îµ¯Æ°¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤È¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥àÍѤΥ¹¥é¥¤¥¹¤¬¡¢
             ºÇ½é¤Î 1024 ¥·¥ê¥ó¥ÀÆâ¤Ë¼ý¤Þ¤Ã¤Æ¤¤¤ë»ö¤ò³Îǧ¤¹¤ë¤À¤±¤Ç¤¹¡£
             µ¤¤Ë¤Ê¤ëÊý¤Ï¡¢µ¯Æ°¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò 20
             ¥á¥¬¥Ð¥¤¥È¤°¤é¤¤¤Ë¤·¤ÆÂ礭¤á¤Ë¤¹¤ë¤È¤è¤¤¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-os">
           <para>FreeBSD ¤Îµ¯Æ°»þ¤Ë
             <literal>Missing Operating System</literal>
             ¤Èɽ¼¨¤µ¤ì¤Þ¤¹</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Ï FreeBSD ¤ä DOS¡¢
             ¤½¤Î¤Û¤«¤Î OS ¤¬¥Ç¥£¥¹¥¯Îΰè<link linkend="geometry">¥¸¥ª¥á¥È¥ê</link>
             ¤Î¤È¤é¤¨Êý¤Ç¾×Æͤ·¤¢¤Ã¤Æ¤¤¤ë¤³¤È¤«¤éµ¯¤³¤ëŵ·¿Åª¤ÊÎã¤Ç¤¹¡£
             ¤³¤¦¤Ê¤Ã¤¿¤é FreeBSD
             ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·Ä¾¤¹°Ê³°¤Ë¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢
             ¾¤Î¤È¤³¤í¤ÇÀâÌÀ¤·¤¿¼ê½ç¤Ë¤·¤¿¤¬¤Ã¤Æ¤ä¤ì¤Ð¡¢
             ¤Û¤Ü´Ö°ã¤¤¤Ê¤¯¤¦¤Þ¤¯¤¤¤¯¤Ï¤º¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="stop-at-boot-manager">
           <para>¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Î <literal>F?</literal> ¥×¥í¥ó¥×¥È¤¬É½¼¨¤µ¤ì¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Ï¤¹¤Ç¤ËÁ°¤Ë¼ÁÌ䤵¤ì¤Æ¤¤¤ëÌäÂê¤Î¤â¤¦°ì¤Ä¤Î¾É¾õ¤Ç¤¹¡£
             BIOS ¤Î¥¸¥ª¥á¥È¥ê¤È FreeBSD ¤Î¥¸¥ª¥á¥È¥êÀßÄ꤬°ìÃפ·¤Æ¤¤¤Ê¤¤¤Î¤Ç¤¹!
             ¥³¥ó¥È¥í¡¼¥é¤ä BIOS ¤¬¥·¥ê¥ó¥À¤ÎÊÑ´¹ (<literal>&gt;1GB ¥É¥é¥¤¥Ö¤Î
             ¥µ¥Ý¡¼¥È</literal>¤È¤â¸Æ¤Ð¤ì¤Þ¤¹) ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤¿¤é¡¢
             ¤½¤ÎÀßÄê¤ò̵¸ú²½¤·¤Æ FreeBSD ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·Ä¾¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="need-complete-sources">
           <para>¥½¡¼¥¹¤òÁ´Éô¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëɬÍפϤ¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             °ìÈÌŪ¤Ë¤Ï¡Ö¤¤¤¤¤¨¡×¤Ç¤¹¡£
             ¤·¤«¤·ºÇÄã¤Ç¤â¡¢<literal>base</literal>
             ¥½¡¼¥¹¥­¥Ã¥È (¤³¤ì¤Ë¤Ï¤³¤Î FAQ
             ¤Ç½Ò¤Ù¤é¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Î¤¤¤¯¤Ä¤«¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹) ¤È¡¢
             <literal>sys</literal> (kernel)
             ¥½¡¼¥¹¥­¥Ã¥È (¤³¤ì¤Ë¤Ï¥«¡¼¥Í¥ë¤Î¥½¡¼¥¹¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹)
             ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë»ö¤ò¶¯¤¯¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
             Ä̾²¿¤«¤Î¼Â¹Ô¤Ë¥½¡¼¥¹¤¬É¬Íפˤʤë»ö¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¤·¤«¤·¡¢¥«¡¼¥Í¥ë¤ò¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¤¹¤ë¤¿¤á¤Î¥×¥í¥°¥é¥à &man.config.8;
             ¤ò¼Â¹Ô¤¹¤ë»þ¤ÏÎã³°¤Ç¤¹¡£
             ¥«¡¼¥Í¥ë¤Î¥½¡¼¥¹¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Ê¤¯¤Æ¤â¤è¤¤Îã¤È¤·¤Æ¡¢
             ¤É¤³¤«Ê̤ξì½ê¤«¤é¥«¡¼¥Í¥ë¤Î¥½¡¼¥¹¤òÆɤ߹þ¤ßÀìÍÑ¤Ç NFS
             ¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤Þ¤¿¡¢
             ¤½¤³¤«¤é¿·¤·¤¤¥Ð¥¤¥Ê¥ê¤òºîÀ®¤Ç¤­¤ë¤è¤¦¤Ë¤â¤Ê¤Ã¤Æ¤¤¤Þ¤¹
             (¥«¡¼¥Í¥ë¥½¡¼¥¹¤ÎÀ©¸Â¤¬¤¢¤ë¤Î¤Ç¡¢Ä¾ÀÜ <filename>/usr/src</filename>
             ¤ò¥Þ¥¦¥ó¥È¤¹¤ë»ö¤Ï¤ª¤¹¤¹¤á¤Ç¤­¤Þ¤»¤ó¡£
             ¤½¤ì¤è¤ê¤â¤É¤³¤«Ê̤Υǥ£¥ì¥¯¥È¥ê¤Ë¥Þ¥¦¥ó¥È¤·¤Æ¡¢
             ¥½¡¼¥¹¥Ä¥ê¡¼¤ÎÊ£À½¤¬¤Ç¤­¤ë¤è¤¦¤ËŬÀڤ˥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤òÄ¥¤Ã¤Æ¤¯¤À¤µ¤¤)¡£
           </para>
 
           <para>
             ¥½¡¼¥¹¤ò¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Ë»ý¤Á¡¢
             ¤½¤³¤«¤é¥·¥¹¥Æ¥à¤ò¥Ó¥ë¥É¤¹¤ë¤è¤¦¤Ë¤·¤Æ¤ª¤±¤Ð¡¢
             FreeBSD ¤Î¾­Íè¤Î¥ê¥ê¡¼¥¹¤Ø¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤¬¤º¤Ã¤È´Êñ¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¼ÂºÝ¤Ë¥½¡¼¥¹¤Î¥µ¥Ö¥»¥Ã¥È¤òÁªÂò¤¹¤ë¤Ë¤Ï¡¢
             ¥·¥¹¥Æ¥à¥¤¥ó¥¹¥È¡¼¥ë¥Ä¡¼¥ë¤Î¡ÖÇÛÉÛ¥Õ¥¡¥¤¥ë¡×¥á¥Ë¥å¡¼¤Ë¤¢¤ë¡¢
             ¡Ö¥«¥¹¥¿¥à¡×¥á¥Ë¥å¡¼¤ò»ÈÍѤ·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="need-kernel">
           <para>¥«¡¼¥Í¥ë¤Ïɬ¤ººî¤êľ¤µ¤Ê¤¯¤Á¤ã¤Ê¤é¤Ê¤¤¤ó¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¥«¡¼¥Í¥ë¤ò¿·¤·¤¯ºî¤êľ¤¹¤Î¤Ï¸µ¡¹¡¢
             FreeBSD ¤Î¥¤¥ó¥¹¥È¡¼¥ë»þ¤Ëɬ¿Ü¤Îºî¶È¤Ç¤·¤¿¡£
             ¤Ç¤âºÇ¶á¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï¡¢
             ¤È¤Æ¤â¥æ¡¼¥¶¥Õ¥ì¥ó¥É¥ê¤Ê¥«¡¼¥Í¥ëÀßÄê¥Ä¡¼¥ë¤Î²¸·Ã¤ò¼õ¤±¤Æ¤¤¤Þ¤¹¡£
             FreeBSD ¤Îµ¯Æ°¥×¥í¥ó¥×¥È (boot:) ¤Ç <option>-c</option>
             ¤È¥¿¥¤¥×¤¹¤ì¤Ð¥Ó¥¸¥å¥¢¥ë¤ÊÀßÄê²èÌ̤ˤʤꡢ
             ¤Û¤È¤ó¤É¤Î°ìÈÌŪ¤Ê ISA
             ¥«¡¼¥É¤Ë¤Ä¤¤¤Æ¤Î¥«¡¼¥Í¥ë¤ÎÀßÄê¤ò¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             º£¤Ç¤â¡¢
             ɬÍפʥǥХ¤¥¹¥É¥é¥¤¥Ð¤À¤±¤òÁȤ߹þ¤ó¤À¥«¡¼¥Í¥ë¤òºî¤ë¤³¤È¤Ï¤è¤¤»ö¤È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤Û¤ó¤Î¤Á¤ç¤Ã¤È¤À¤±¥á¥â¥ê¤òÀáÌó¤Ç¤­¤Þ¤¹¤«¤é¤Í¡£
             ¤Ç¤â¤Û¤È¤ó¤É¤Î¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
             ¤â¤Ï¤ä¤É¤¦¤·¤Æ¤â¤ä¤é¤Ê¤¯¤Á¤ã¤Ê¤é¤Ê¤¤¤³¤È¤Ç¤Ï¤Ê¤¤¤Î¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="password-encryption">
           <para>DES ¤È MD5¡¢¤É¤Á¤é¤Î¥Ñ¥¹¥ï¡¼¥É¤ò»È¤¦¤Ù¤­¤Ê¤Î¤Ç¤·¤ç¤¦¤«?
             ¤Þ¤¿¡¢¥æ¡¼¥¶¤¬¤É¤Á¤é¤ò»È¤¦¤³¤È¤Ë¤Ê¤ë¤«»ØÄꤹ¤ëÊýË¡¤Ï¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>FreeBSD ¤Îɸ½à¤Î¥Ñ¥¹¥ï¡¼¥É¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï
             <emphasis>MD5</emphasis> ¤ò»È¤Ã¤¿¤â¤Î¤Ç¤¹¡£ ¤³¤ì¤Ï
             <emphasis>DES</emphasis> ¥¢¥ë¥´¥ê¥º¥à¤Ë´ð¤Å¤¤¤¿¼êË¡¤òÍѤ¤¤ë
             UNIX ¤ÎÅÁÅýŪ¤Ê¥Ñ¥¹¥ï¡¼¥É¥Õ¥©¡¼¥Þ¥Ã¥È¤è¤ê°ÂÁ´ (secure) ¤À¤È
             ¿®¤¸¤é¤ì¤Æ¤¤¤ë¤â¤Î¤Ç¤¹¡£ DES ¥Ñ¥¹¥ï¡¼¥É¤Ï
             ¤¢¤Ê¤¿¤¬ FreeBSD ¤Î¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤ò¡¢
             °ÂÁ´À­¤ËÎô¤ë¥Ñ¥¹¥ï¡¼¥É¥Õ¥©¡¼¥Þ¥Ã¥È¤òÍøÍѤ·¤Æ¤¤¤ë¸Å¤¤ OS
             ¤È¶¦Í­¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¯¤Ê¤Ã¤¿¤È¤­¤Î¤¿¤á¤Ë
             ÍøÍѲÄǽ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹ (¤³¤ì¤ÏÍøÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢
             sysinstall ¤«¤é <quote>crypto</quote> ÇÛÉÛʪ¤Î¥¤¥ó¥¹¥È¡¼¥ë
             Áª¤Ö¤«¡¢¥½¡¼¥¹¤«¤é build ¤·¤Æ¤¤¤ë¤Ê¤é¡¢
             crypto ¤Î¥½¡¼¥¹¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹)¡£
             ¿·¤·¤¤¥Ñ¥¹¥ï¡¼¥É¤Ë¤É¤Á¤é¤Î¥Ñ¥¹¥ï¡¼¥É¥Õ¥©¡¼¥Þ¥Ã¥È¤ò»È¤¦¤«¤Ï
             <filename>/etc/login.conf</filename> ¤ÎÃæ¤Î
             <quote>passwd_format</quote> ¤È¤¤¤¦ login
             ¥±¡¼¥Ñ¥Ó¥ê¥Æ¥£¤ÇÀ©¸æ¤µ¤ì¤Þ¤¹¡£¤³¤Î¥±¡¼¥Ñ¥Ó¥ê¥Æ¥£¤Ï
             <quote>des</quote> (ÍøÍѤǤ­¤ë¤Ê¤é) ¤«
             <quote>md5</quote> ¤Î¤É¤Á¤é¤«¤ÎÃͤò¼è¤ê¤Þ¤¹¡£
             login ¥±¡¼¥Ñ¥Ó¥ê¥Æ¥£¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï &man.login.conf.5; ¤ò
             »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="boot-floppy-hangs">
           <para>¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤Çµ¯Æ°¤¹¤ë¤È¡¢
             <literal>Probing Devices...</literal>
             ¤Î²èÌ̤ǥϥ󥰥¢¥Ã¥×¤·¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             IDE Zip ¤« Jaz ¥É¥é¥¤¥Ö¤¬Àܳ¤µ¤ì¤Æ¤¤¤¿¤é¡¢
             ¤½¤ì¤ò¼è¤ê³°¤·¤Æ¤â¤¦°ìÅٻ¤Æ¤ß¤Þ¤·¤ç¤¦¡£
             ¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤Ï¤³¤Î¼ï¤Î¥É¥é¥¤¥Ö¤ò¸íǧ¤·¤Æ¤·¤Þ¤¦¤Î¤Ç¤¹¡£
             ¥·¥¹¥Æ¥à¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤¿¸å¤Ï¡¢¤½¤Î¥É¥é¥¤¥Ö¤òºÆÅÙÀܳ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤¦¤Þ¤¯¤¤¤±¤Ð¤³¤ÎÌäÂê¤Ï¾­Íè¤Î¥ê¥ê¡¼¥¹¤Ç²ò·è¤µ¤ì¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="panic-on-install-reboot">
           <para>¥¤¥ó¥¹¥È¡¼¥ë½ªÎ»¸å¤Ë¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤¹¤ë¤È¡¢
             <literal>panic: cant mount root</literal>
             ¤Î¥¨¥é¡¼¤È¤Ê¤ê¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             ¤³¤Î¥¨¥é¡¼¤Ï¥Ç¥£¥¹¥¯¥Ç¥Ð¥¤¥¹¤Ë¤Ä¤¤¤Æ¡¢
             µ¯Æ°¥Ö¥í¥Ã¥¯¤È¥«¡¼¥Í¥ë¤Îǧ¼±¤¬º®Í𤷤Ƥ¤¤ë¤¿¤á¤Ëµ¯¤³¤ê¤Þ¤¹¡£
             ¤³¤Î¥¨¥é¡¼¤ÏÄ̾
             2 Âæ¤Î IDE ¥Ç¥£¥¹¥¯¤¬¤½¤ì¤¾¤ìÊ̤ΠIDE
             ¥³¥ó¥È¥í¡¼¥é¤Î¥Þ¥¹¥¿¡¼¤Ë°ì¤Ä¤º¤ÄÀܳ¤µ¤ì¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤Ë¤ª¤¤¤Æ¡¢
             FreeBSD ¤¬¥»¥«¥ó¥À¥ê IDE
             ¥³¥ó¥È¥í¡¼¥é¤ËÀܳ¤µ¤ì¤¿¥Ç¥£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤ËȯÀ¸¤·¤Þ¤¹¡£
             µ¯Æ°¥Ö¥í¥Ã¥¯¤Ï FreeBSD ¤¬
             wd1 (2 ÂæÌܤΠBIOS
             ¥Ç¥£¥¹¥¯) ¤Ë¥¤¥ó¥¹¥È¡¼¥ë
             ¤µ¤ì¤Æ¤¤¤ë¤Èǧ¼±¤¹¤ë¤Î¤ËÂФ·¡¢
             ¥«¡¼¥Í¥ë¤Ï¥»¥«¥ó¥À¥ê IDE ¤Î 1 ÂæÌܤΥϡ¼¥É¥Ç¥£¥¹¥¯¤Ç¤¢¤ë
             wd2
             ¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤Èǧ¼±¤¹¤ë¤Î¤Ç¤¹¡£
             ¥Ç¥Ð¥¤¥¹¸¡½Ð¸å¤Ç¡¢
             ¥«¡¼¥Í¥ë¤Ïµ¯Æ°¥Ö¥í¥Ã¥¯¤¬µ¯Æ°¥Ç¥£¥¹¥¯¤À¤Èǧ¼±¤·¤¿¥Ç¥£¥¹¥¯¤Ç¤¢¤ë
             wd1 ¤ò¥Þ¥¦¥ó¥È¤·¤è¤¦¤È¤·¤Þ¤¹¡£
             ¤·¤«¤·¡¢¼ÂºÝ¤Ë¤Ïµ¯Æ°¥Ç¥£¥¹¥¯¤Ï
             wd2 ¤Ê¤Î¤Ç¼ºÇÔ¤·¤Æ¤·¤Þ¤¦¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¤³¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤Ë¤Ï¡¢°Ê²¼¤Î¤É¤ì¤«°ì¤Ä¤ò¹Ô¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <orderedlist>
 
             <listitem>
               <para>FreeBSD 3.3 °Ê¹ß¤òÍøÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
                 ¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¤Æ¡¢<literal>Booting kernel in 10 seconds; hit
                   [Enter] to interrupt</literal>
                 ¤¬É½¼¨¤µ¤ì¤Æ¤¤¤ë´Ö¤Ë <literal>Enter</literal> ¥­¡¼¤ò²¡¤·¤Þ¤¹¡£
                 ¤¹¤ë¤È¡¢¥Ö¡¼¥È¥í¡¼¥À¤Ë°Ü¹Ô¤·¤Þ¤¹¡£
               </para>
 
               <para>¤½¤¦¤·¤¿¤é¡¢<literal>set
                   root_disk_unit="<replaceable>disk_number</replaceable>"</literal>
                 ¤ÈÆþÎϤ·¤Þ¤¹¡£ FreeBSD ¤¬ºÇ½é¤Î IDE
                 ¥³¥ó¥È¥í¡¼¥é¤Î¥Þ¥¹¥¿¡¼¤ËÀܳ¤µ¤ì¤¿¥É¥é¥¤¥Ö¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ì¤Ð¡¢
                 <replaceable>disk_number</replaceable> ¤Ï
                 <literal>0</literal> ¤Ç¤¹¡£
                 ¤Þ¤¿¡¢
                 ºÇ½é¤Î IDE ¥³¥ó¥È¥í¡¼¥é¤Î¥¹¥ì¡¼¥Ö¤Ê¤é <literal>1</literal>¡¢
                 ÆóÈÖÌܤΠIDE ¥³¥ó¥È¥í¡¼¥é¤Î¥Þ¥¹¥¿¡¼¤Ê¤é <literal>2</literal>¡¢
                 ÆóÈÖÌܤΠIDE ¥³¥ó¥È¥í¡¼¥é¤Î¥¹¥ì¡¼¥Ö¤Ê¤é <literal>3</literal> ¤Ë¤Ê¤ê¤Þ¤¹¡£
               </para>
 
               <para>¤½¤Î¸å¡¢<literal>boot</literal> ¤ÈÆþÎϤ·¤Þ¤¹¡£
                 ¥·¥¹¥Æ¥à¤Ï¤­¤Á¤ó¤ÈºÆµ¯Æ°¤¹¤ë¤Ï¤º¤Ç¤¹¡£</para>
 
               <para>¤³¤ÎÊѹ¹¤ò¹±µ×Ū¤Ê¤â¤Î¤Ë¤¹¤ë (¤Ä¤Þ¤ê¡¢
                 ºÆµ¯Æ°¤äÅŸ»¤òÆþ¤ì¤ëÅ٤ˤ³¤ÎÁàºî¤ò¤¹¤ëɬÍפ¬¤Ê¤¤¤è¤¦¤Ë¤¹¤ë) ¤Ë¤Ï¡¢
                 <filename>/boot/loader.conf.local</filename> ¤Ë
                 <literal>root_disk_unit="<replaceable>disk_number</replaceable>"</literal>
                 ¤È¤¤¤¦¹Ô¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£</para>
             </listitem>
 
             <listitem>
               <para>
                 FreeBSD 3.2 °ÊÁ°¤òÍøÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
                 Boot: ¥×¥í¥ó¥×¥È¤Ç
                 <literal>1:wd(2,a)kernel</literal>
                 ¤ÈÆþÎϤ·¤Æ¥¨¥ó¥¿¡¼¥­¡¼¤ò²¡¤·¤Þ¤¹¡£
                 ¥·¥¹¥Æ¥à¤¬µ¯Æ°¤·¤¿¤é¡¢
 
                 <command>echo "1:wd(2,a)kernel" &gt; /boot.config</command>
 
                 ¤È¤¤¤¦¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤³¤ì¤ò¥Ç¥Õ¥©¥ë¥È¤Î¥Ö¡¼¥Èʸ»úÎó¤È¤·¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>FreeBSD ¤Î¥Ç¥£¥¹¥¯¤ò¥×¥é¥¤¥Þ¥ê IDE ¥³¥ó¥È¥í¡¼¥é¤ËÀܳ¤·¤Æ¡¢
                 ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬Ï¢Â³¤·¤¿¥É¥é¥¤¥ÖÈÖ¹æ¤Çǧ¼±¤µ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>¥«¡¼¥Í¥ë¤Î¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ç wd
                 ¤Î¹Ô¤ò°Ê²¼¤Î¤è¤¦¤ËÊѹ¹¤·¡¢
                 <ulink url="../handbook/kernelconfig.html">¥«¡¼¥Í¥ë¤ÎºÆ¹½ÃÛ</ulink>¤ò¹Ô¤Ã¤Æ¡¢
                 ¿·¤·¤¤¥«¡¼¥Í¥ë¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£</para>
 
               <programlisting>controller      wdc0    at isa? port "IO_WD1" bio irq 14 vector wdintr
 disk            wd0     at wdc0 drive 0
 # disk            wd1     at wdc0 drive 1 # ¤³¤Î¹Ô¤ò¥³¥á¥ó¥È¥¢¥¦¥È
 
 controller      wdc1    at isa? port "IO_WD2" bio irq 15 vector wdintr
 disk            wd1     at wdc1 drive 0 # wd2 ¤«¤é wd1 ¤ØÊѹ¹
 disk            wd2     at wdc1 drive 1 # wd3 ¤«¤é wd2 ¤ØÊѹ¹</programlisting>
 
               <para>¥Ç¥£¥¹¥¯¤ÎÀܳ¤òÊѹ¹¤·¤Æ¸µ¤ÎÀßÄê¤ËÌᤷ¤¿¤¤¾ì¹ç¤Ï¡¢¥Ç¥£¥¹¥¯¤ò
                 ¤ªË¾¤ß¤ÎÀßÄê¤ÎÄ̤ê¤ÎÀܳ¤ËÌᤷ¤Æ¤«¤éºÆµ¯Æ°¤·¤Þ¤¹¡£
                 ¥·¥¹¥Æ¥à¤ÏÀµ¾ï¤Ëµ¯Æ°¤¹¤ë¤Ï¤º¤Ç¤¹¡£</para>
             </listitem>
           </orderedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="memory-limits">
           <para>¥á¥â¥ê¤ÎÂ礭¤µ¤ÎÀ©¸Â¤Ï?</para>
         </question>
 
         <answer>
           <para>
             ǧ¼±¤Ç¤­¤ë¥á¥â¥ê¤Î¾å¸Â¤Ï¡¢4GB ¤Ç¤¹¡£
             ¤³¤Î¹½À®¤Ï»î¸³ºÑ¤ß¤Ç¡¢
             ¾ÜºÙ¤Ï <ulink url="ftp://ftp.cdrom.com/archive-info/configuration">wcarchive's
               configuration</ulink> ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
             ¤³¤Î¤è¤¦¤Ë¤¿¤¯¤µ¤ó¤Î¥á¥â¥ê¤ò¥Þ¥·¥ó¤ËƳÆþ¤·¤è¤¦¤È¤¤¤¦¾ì¹ç¤Ë¤Ï¡¢
             Ãí°Õ¤¬É¬ÍפǤ¹¡£ECC µ¡Ç½¤ò¥µ¥Ý¡¼¥È¤·¡¢¤Ê¤ª¤«¤Ä
             ÍÆÎÌÀ­Éé²Ù (ÌõÃí: ¿¤¯¤Î¥á¥â¥êÁǻҤÏÍÆÎÌÀ­Éé²Ù¤È¤·¤ÆƯ¤­¤Þ¤¹¤¬¡¢
             ¥á¥â¥ê¥Ð¥¹¾å¤ËÍÆÎÌÀ­Éé²Ù¤¬Áý¤¨¤ë¤È¿®¹æ¤ÎÅÁ㤬Ã٤졢¸íÆ°ºî¤Î¸¶°ø¤È¤Ê¤ê¤Þ¤¹) ¤ò
             Ä㸺¤µ¤»¤ë¤¿¤á¡¢18 ¥Á¥Ã¥×¹½À®¤Î¥á¥â¥ê¥â¥¸¥å¡¼¥ë¤è¤ê
             9 ¥Á¥Ã¥×¹½À®¤Î¥á¥â¥ê¥â¥¸¥å¡¼¥ë¤òÁªÂò¤¹¤ë¤³¤È¤¬¡¢¤ª¤½¤é¤¯Ë¾¤Þ¤·¤¤¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ffs-limits">
           <para>ffs ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÂ礭¤µ¤ÎÀ©¸Â¤Ï?</para>
         </question>
 
         <answer>
           <para>
             ffs ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¾ì¹ç¡¢
             ÏÀÍýŪ¤ÊºÇÂç¤Î¾å¸Â¤Ï 8 TB (2G ¥Ö¥í¥Ã¥¯)¡¢
             ¥Ç¥Õ¥©¥ë¥È¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤ò 8K ¤È¤¹¤ë¤È 16 TB¤È¤Ê¤ê¤Þ¤¹¡£
             ¼ÂºÝÌäÂê¤È¤·¤Æ¡¢1 TB ¤Î¥½¥Õ¥È¥¦¥§¥¢¤Î¸Â³¦¤¬¤¢¤ê¤Þ¤¹¤¬¡¢
             ½¤Àµ¤¹¤ì¤Ð 4 TB ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬²Äǽ¤Ç¤¹ (¼ÂºÝ¤Ë¸ºß¤·¤Þ¤¹)¡£
           </para>
 
           <para>°ì¤Ä¤Î ffs ¤Î¥Õ¥¡¥¤¥ë¤ÎºÇÂç¤Î¥µ¥¤¥º¤Ï¡¢¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤¬ 4K ¤Î¾ì¹ç¤Ç
             Ìó 1G ¥Ö¥í¥Ã¥¯ (4 TB)¤Ç¤¹¡£</para>
 
           <table>
             <title>ºÇÂç¥Õ¥¡¥¤¥ë¥µ¥¤¥º</title>
 
             <tgroup cols="5">
               <thead>
                 <row>
                   <entry>fs ¥Ö¥í¥Ã¥¯¥µ¥¤¥º</entry>
 
                   <entry>2.2.7-stable</entry>
 
                   <entry>3.0-current</entry>
 
                   <entry>Æ°ºî³ÎǧºÑ¤ß¤Î¥µ¥¤¥º</entry>
 
                   <entry>Æ°ºî¤¹¤ë¤Ï¤º¤Î¥µ¥¤¥º</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry>4K</entry>
 
                   <entry>4T-1</entry>
 
                   <entry>4T-1</entry>
 
                   <entry>4T-1</entry>
 
                   <entry>&gt;4T</entry>
                 </row>
 
                 <row>
                   <entry>8K</entry>
 
                   <entry>&gt;32G</entry>
 
                   <entry>8T-1</entry>
 
                   <entry>&gt;32G</entry>
 
                   <entry>32T-1</entry>
                 </row>
 
                 <row>
                   <entry>16K</entry>
 
                   <entry>&gt;128G</entry>
 
                   <entry>16T-1</entry>
 
                   <entry>&gt;128G</entry>
 
                   <entry>32T-1</entry>
                 </row>
 
                 <row>
                   <entry>32K</entry>
 
                   <entry>&gt;512G</entry>
 
                   <entry>32T-1</entry>
 
                   <entry>&gt;512G</entry>
 
                   <entry>64T-1</entry>
                 </row>
 
                 <row>
                   <entry>64K</entry>
 
                   <entry>&gt;2048G</entry>
 
                   <entry>64T-1</entry>
 
                   <entry>&gt;2048G</entry>
 
                   <entry>128T-1</entry>
                 </row>
               </tbody>
             </tgroup>
           </table>
 
           <para>
             fs ¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤¬ 4K ¤Î¾ì¹ç¤Ï»°½Å´ÖÀÜ¥Ö¥í¥Ã¥¯¤¬»ÈÍѤµ¤ì¡¢
             ¤¤¤º¤ì¤Î¾ì¹ç¤Ç¤â»°½Å´ÖÀÜ¥Ö¥í¥Ã¥¯¤ò»ÈÍѤ·¤Æɽ¸½¤Ç¤­¤ëºÇÂç¤Î
             fs ¥Ö¥í¥Ã¥¯ÈÖ¹æ (¤ª¤è¤½ 1K^3 + 1K^2 + 1K) ¤ËÀ©¸Â¤µ¤ì¤ë¤Ï¤º¤Ê¤Î¤Ç¤¹¤¬¡¢
             ¼ÂºÝ¤Ï fs ¥Ö¥í¥Ã¥¯ÈÖ¹æ¤Î (´Ö°ã¤Ã¤¿) ¾å¸Â 1G-1 ¤ÇÀ©¸Â¤µ¤ì¤Þ¤¹¡£
             fs ¥Ö¥í¥Ã¥¯ÈÖ¹æ¤ÎÀ©¸Â¤Ï 2G-1 ¤È¤Ê¤ë¤Ï¤º¤Ç¤¹¡£2G-1 ÉÕ¶á¤Ë
             fs ¥Ö¥í¥Ã¥¯ÈÖ¹æ¤Î¥Ð¥°¤¬Â¿¾¯¤¢¤ê¤Þ¤¹¤¬¡¢fs ¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤¬
             4K ¤Î¾ì¹ç¤Ï¡¢¤³¤³¤Þ¤Ç¤Î¥Ö¥í¥Ã¥¯ÈÖ¹æ¤Ë¤ÏÅþ㤷¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤¬ 8K °Ê¾å¤Î¾ì¹ç¡¢¤¤¤º¤ì¤Î¾ì¹ç¤â
             fs ¥Ö¥í¥Ã¥¯ÈÖ¹æ¤Î¾å¸Â 2G-1 ¤ÇÀ©¸Â¤µ¤ì¤ë¤Ï¤º¤Ç¤¹¤¬¡¢
             ¼ÂºÝ¤Ï fs ¥Ö¥í¥Ã¥¯ÈÖ¹æ¤Î¾å¸Â
             1G-1 ¤ÇÀ©¸Â¤µ¤ì¤Þ¤¹¡£
             Î㳰Ū¤Ë -STABLE ¤Ç¤Ï»°½Å´ÖÀÜ¥Ö¥í¥Ã¥¯¤Þ¤Ç¤ÏÅþ㤷¤Ê¤¤¤¿¤á¡¢
             À©¸Â¤ÏÆó½Å´ÖÀÜ¥Ö¥í¥Ã¥¯¤Çɽ¸½¤Ç¤­¤ëºÇÂç¤Î
             fs ¥Ö¥í¥Ã¥¯ÈÖ¹æ (¤ª¤è¤½ (blocksize/4)^2 + (blocksize/4)) ¤È¤Ê¤ê¤Þ¤¹¡£
             -CURRENT ¤Ç¤Ï¤³¤ÎÀ©¸Â¤òĶ¤¨¤ë¤ÈÌäÂê¤ò°ú¤­µ¯¤³¤¹¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             Àµ¤·¤¤À©¸ÂÃͤǤ¢¤ë 2G-1 ¥Ö¥í¥Ã¥¯¤ò»ÈÍѤ¹¤ë¤ÈÌÀ¤é¤«¤ËÌäÂ꤬½Ð¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tb-on-floppy">
           <para>¥Õ¥í¥Ã¥Ô¡¼¤Ë 1 TB ¤Î¥Õ¥¡¥¤¥ë¤ò³ÊǼ¤¹¤ë¤Ë¤Ï?</para>
           <para><emphasis>´ó¹Æ: Bruce Evans¡¢1998 ǯ 9 ·î</emphasis></para>
         </question>
 
         <answer>
           <para>
             ¤ï¤¿¤·¤Î¤È¤³¤í¤Ç¤Ï¡¢
             ¥Õ¥í¥Ã¥Ô¡¼¤Ë¤¤¤¯¤Ä¤«¤Î¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë¤òÊݸ¤·¤Æ¤¤¤Þ¤¹ :-)¡£
             ºÇÂç¤Î¥Õ¥¡¥¤¥ë¥µ¥¤¥º¤ÏºÇÂç¤Î¥Ç¥£¥¹¥¯¥µ¥¤¥º¤È¤Ï¤¢¤Þ¤ê´Ø·¸¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ºÇÂç¤Î¥Ç¥£¥¹¥¯¥µ¥¤¥º¤Ï 1 TB ¤Ç¤¹¡£
             ¥Õ¥¡¥¤¥ë¥µ¥¤¥º¤¬¥Ç¥£¥¹¥¯¥µ¥¤¥º¤è¤êÂ礭¤¯¤Ê¤ê¤¦¤ë¤È¤¤¤¦¤Î¤Ï»ÅÍͤǤ¹¡£
           </para>
 
           <para>
             °Ê²¼¤ÎÎã¤Ï¡¢32K ¤Î¥Ç¥£¥¹¥¯ÍÆÎÌ (3
             ¤Ä¤Î´ÖÀÜ¥Ö¥í¥Ã¥¯¤È 1 ¤Ä¤Î¥Ç¡¼¥¿¥Ö¥í¥Ã¥¯) ¤ò»È¤Ã¤Æ¡¢
             ¾®¤µ¤Ê¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë
             8T-1 ¤ÎÂ礭¤µ¤Î¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Þ¤¹¡£
             ¤³¤³¤Ç¤Î dd ¥³¥Þ¥ó¥É¤ÏÂ礭¤Ê¥Õ¥¡¥¤¥ë¤¬°·¤¨¤ë¤â¤Î¤¬É¬ÍפǤ¹¡£
           </para>
 
           <screen>&prompt.user; <userinput>cat foo</userinput>
 df .
 dd if=/dev/zero of=z bs=1 seek=`echo 2^43 - 2 | bc` count=1
 ls -l z
 du z
 df .
 &prompt.user; <userinput>sh foo</userinput>
 Filesystem  1024-blocks     Used    Avail Capacity  Mounted on
 /dev/da0a         64479    27702    31619    47%    /
 1+0 records in
 1+0 records out
 1 bytes transferred in 0.000187 secs (5346 bytes/sec)
 -rw-r--r--  1 bde  bin  8796093022207 Sep  7 16:04 z
 32      z
 Filesystem  1024-blocks     Used    Avail Capacity  Mounted on
 /dev/da0a         64479    27734    31587    47%    /</screen>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="archsw-readin-failed-error">
           <para>¿·¤·¤¤¥«¡¼¥Í¥ë¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤¿¤é¡¢µ¯Æ°»þ¤Ë
             <literal>archsw.readin.failed</literal>
             ¤È¤¤¤¦¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤¬É½¼¨¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤·¤¿¡£</para>
         </question>
 
         <answer>
           <para>¥í¡¼¥À¤¬¥¹¥¿¡¼¥È¤¹¤ëÁ°¤Î | ¤¬É½¼¨¤µ¤ì¤Æ¤¤¤ë¤È¤­¤Ë²¿¤«¥­¡¼¤ò²¡¤¹¤³¤È¤Ç¡¢
             µ¯Æ°¤Î¥»¥«¥ó¥É¥¹¥Æ¡¼¥¸¤«¤éľÀÜ¡¢µ¯Æ°¤¹¤ë¥«¡¼¥Í¥ë¤ò»ØÄꤷ¤Æµ¯Æ°¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             Æäˡ¢¥«¡¼¥Í¥ë¤Î¥½¡¼¥¹¤ò¹¹¿·¤·¡¢<emphasis>make world
               ¤·¤Ê¤¤¤Ç</emphasis>¿·¤·¤¤¥«¡¼¥Í¥ë¤À¤±¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¾ì¹ç¤Ë¤³¤Î¾É¾õ¤¬¸½¤ï¤ì¤Þ¤¹¡£
             ¤³¤¦¤¤¤¦Áàºî¤ÏÆ°ºî¤¬Êݾڤµ¤ì¤Þ¤»¤ó¡£¤­¤Á¤ó¤È make world ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="upgrade-3x-4x">
            <para>3.X ¤«¤é 4.X ¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤¿¤éÎɤ¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¤Ï¡¢
             ¥Ð¥¤¥Ê¥ê¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò»È¤¦¤³¤È¤ò<emphasis>¶¯¤¯</emphasis>¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
             4-STABLE ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ï
             <ulink
             url="ftp://releng4.FreeBSD.org/">releng4.FreeBSD.org</ulink>
             ¤«¤éÆþ¼ê²Äǽ¤Ç¤¹¡£</para>
 
           <para>¥½¡¼¥¹¤ò»È¤Ã¤Æ¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¾ì¹ç¤Ï¡¢¾ÜºÙ¤Ë¤Ä¤¤¤Æ
             <ulink url="http://www.FreeBSD.org/handbook/cutting-edge.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯</ulink>¤ò»²¾È¤¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <caution>
           <para>¥½¡¼¥¹¤ò»È¤Ã¤¿¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ï¡¢
             ´·¤ì¤Æ¤¤¤Ê¤¤¥æ¡¼¥¶¤Ë¤Ï¤Þ¤Ã¤¿¤¯¤ª¤¹¤¹¤á¤Ç¤­¤Þ¤»¤ó¡£
             3.X ¤«¤é 4.X ¤Ø¤Î¾ì¹ç¤ÏÆäˤ½¤¦¤Ç¤¹¡£
             ¥½¡¼¥¹¤ò»È¤Ã¤¿¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò»î¤¹Á°¤Ë¡¢
             ¼ê½ç¤òÃí°Õ¿¼¤¯Æɤà¤è¤¦¤Ë¿´¤¬¤±¤Æ¤¯¤À¤µ¤¤¡£</para>
           </caution>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="security-profiles">
           <para><quote>¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë</quote>
             (<quote>security profiles</quote>) ¤È¤Ï²¿¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para><quote>¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë</quote>¤È¤Ï¡¢ÆÃÄê¤Î
             ¥×¥í¥°¥é¥à¤ä¤½¤Î¾¤ÎÀßÄê¤òÍ­¸ú¤Ë¤·¤¿¤ê̵¸ú¤Ë¤¹¤ë¤³¤È¤Ç¡¢µá¤á¤ë
             ÈæΨ¤Ç°ÂÁ´¤ÈÊØÍø¤µ¤ò¼Â¸½¤·¤è¤¦¤È¤¹¤ë¹½À®¤ÎÁªÂò»è¤Î½¸¤Þ¤ê¤Î
             ¤³¤È¤Ç¤¹¡£¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë¤¬¸·¤·¤¤¤Û¤É¡¢¥Ç¥Õ¥©¥ë¥È¤Ç
             Í­¸ú¤Ë¤Ê¤ë¥×¥í¥°¥é¥à¤¬¸º¤ê¤Þ¤¹¡£¤³¤ì¤Ï¡¢Æ°¤«¤µ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤
             ¤â¤Î°Ê³°¤Ï¡¢²¿¤âÆ°¤«¤·¤Æ¤Ï¤¤¤±¤Ê¤¤¤È¤¤¤¦¥»¥­¥å¥ê¥Æ¥£¤Î
             ´ðËÜŪ¸¶Â§¤Î°ì¤Ä¤Ç¤¹¡£</para>
 
           <para>¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë¤Ï¡¢Ã±¤Ë¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Ç¤¢¤ë
             ¤È¤¤¤¦¤³¤È¤Ëµ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£FreeBSD ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿
             ¤¢¤È¤Ë <filename>/etc/rc.conf</filename> ¤ËŬÀڤʹԤòÊÔ½¸¤·¤¿¤ê
             Äɲ乤ì¤Ð¡¢¤É¤Î¥×¥í¥°¥é¥à¤Ç¤âÍ­¸ú¤Ë¤·¤¿¤ê̵¸ú¤Ë¤·¤¿¤ê¤Ç¤­¤Þ¤¹¡£
             ¸å¼Ô¤Ë¤Ä¤¤¤Æ¾Ü¤·¤¤¤³¤È¤Ï &man.rc.conf.5; ¤Î¥Þ¥Ë¥å¥¢¥ë¤ò
             ¤´Í÷¤¯¤À¤µ¤¤¡£</para>
 
           <para>°Ê²¼¤Ë¡¢³Æ¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë¤¬²¿¤ò¹Ô¤¦¤«¤òÀâÌÀ¤·¤¿
             ɽ¤ò·ÇºÜ¤·¤Þ¤¹¡£Îó¤Ï¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë¤ÎÁªÂò»è¤Ç¡¢¹Ô¤Ï
             Í­¸ú¤Þ¤¿¤Ï̵¸ú¤Ë¤Ê¤ë¥×¥í¥°¥é¥à¤äµ¡Ç½¤Ç¤¹¡£</para>
 
           <table>
             <title>»ØÄê¤Ç¤­¤ë¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë</title>
 
             <tgroup cols="5">
               <thead>
                 <row>
                   <entry></entry>
 
                   <entry>Extreme</entry>
 
                   <entry>High</entry>
 
                   <entry>Moderate</entry>
 
                   <entry>Low</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry>&man.inetd.8;</entry>
 
                   <entry>NO</entry>
 
                   <entry>NO</entry>
 
                   <entry>YES</entry>
 
                   <entry>YES</entry>
                 </row>
 
                 <row>
                   <entry>&man.sendmail.8;</entry>
 
                   <entry>NO</entry>
 
                   <entry>YES</entry>
 
                   <entry>YES</entry>
 
                   <entry>YES</entry>
                 </row>
 
                 <row>
                   <entry>&man.sshd.8;</entry>
 
                   <entry>NO</entry>
 
                   <entry>YES</entry>
 
                   <entry>YES</entry>
 
                   <entry>YES</entry>
                 </row>
 
                 <row>
                   <entry>&man.portmap.8;</entry>
 
                   <entry>NO</entry>
 
                   <entry>NO</entry>
 
-                  <entry>¤ª¤½¤é¤¯ <footnote>
-                    <para>¥¤¥ó¥¹¥È¡¼¥ë»þ¤Ë¡¢¤¹¤Ç¤Ë¥Þ¥·¥ó¤ò
+                  <entry>¤ª¤½¤é¤¯ (¥¤¥ó¥¹¥È¡¼¥ë»þ¤Ë¡¢¤¹¤Ç¤Ë¥Þ¥·¥ó¤ò
                       NFS ¥¯¥é¥¤¥¢¥ó¥È¤Þ¤¿¤Ï¥µ¡¼¥Ð¤È¤·¤ÆÀßÄꤷ¤Æ¤¤¤ë¤È¡¢
-                      ¥Ý¡¼¥È¥Þ¥Ã¥Ñ¤¬Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
-                    </footnote>
+                      ¥Ý¡¼¥È¥Þ¥Ã¥Ñ¤¬Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£)
                   </entry>
 
                   <entry>YES</entry>
                 </row>
 
                 <row>
                   <entry>NFS server</entry>
 
                   <entry>NO</entry>
 
                   <entry>NO</entry>
 
                   <entry>YES</entry>
 
                   <entry>YES</entry>
                 </row>
 
                 <row>
                   <entry>&man.securelevel.8;</entry>
 
-                  <entry>YES (2) <footnote>
-                    <para>securelevel ¤òÀßÄꤹ¤ë¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë
+                  <entry>YES (2) (securelevel ¤òÀßÄꤹ¤ë¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë
                       (Extreme ¤Þ¤¿¤Ï High) ¤òÁªÂò¤¹¤ë¾ì¹ç¡¢¤½¤Î±Æ¶Á¤ò
                       ¾µÃΤ·¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£&man.init.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¤ò
                       Æɤߡ¢¥»¥­¥å¥ê¥Æ¥£¥ì¥Ù¥ë¤Î°ÕÌ£¤Ë¤Ä¤¤¤ÆÆäËÃí°Õ¤ò
                       ʧ¤Ã¤Æ¤¯¤À¤µ¤¤¡£¤½¤¦¤·¤Ê¤¤¤È¡¢¸å¤Ç¿¼¹ï¤ÊÌäÂ꤬
-                      µ¯¤­¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£</para>
-                    </footnote>
+                      µ¯¤­¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£)
                     </entry>
 
                   <entry>YES (1)</entry>
 
                   <entry>NO</entry>
 
                   <entry>NO</entry>
                 </row>
               </tbody>
             </tgroup>
           </table>
 
             <warning>
               <para>¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë¤ÏËâË¡¤ÎÌô¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
                 High ¤ËÀßÄꤷ¤¿¤é¡¢Å¬Åö¤Ê <ulink
                 url="../handbook/eresources.html#ERESOURCES-MAIL">
                 ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</ulink>¤òÆɤó¤À¤ê¡¢ÎɼÁ¤Ê¥Ñ¥¹¥ï¡¼¥É¤ä
                 ¥Ñ¥¹¥Õ¥ì¡¼¥º¤òÍѤ¤¤¿¤ê¡¢¥»¥­¥å¥ê¥Æ¥£¤Ë¤Ä¤¤¤Æ¤Î¤è¤¤½¬´·¤ò
                 ¼é¤Ã¤¿¤ê¤·¤Ê¤¯¤Æ¤¤¤¤¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£µá¤á¤ë¥»¥­¥å¥ê¥Æ¥£¤È
                 ÊØÍø¤µ¤ÎÈæΨ¤ò¼ê·Ú¤ËÀßÄꤷ¤Æ¤¯¤ì¤ë¤À¤±¤Ç¤¹¡£</para>
             </warning>
 
             <note>
               <para>¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë¤Îµ¡¹½¤Ï¡¢FreeBSD ¤òºÇ½é¤Ë
                 ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë»þ¤Ë»È¤¦¤³¤È¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£¤¹¤Ç¤Ë
                 FreeBSD ¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤Ê¤é¡¢Ã±¤Ëµá¤á¤ëµ¡Ç½¤ò
                 Í­¸ú¤Ë¤·¤¿¤ê̵¸ú¤Ë¤·¤¿¤ê¤¹¤ëÊý¤¬¡¢¤ª¤½¤é¤¯¸úΨ¤¬
                 ¤è¤¤¤Ç¤·¤ç¤¦¡£¤â¤·¡¢ËÜÅö¤Ë¥»¥­¥å¥ê¥Æ¥£¥×¥í¥Õ¥¡¥¤¥ë¤ò
                 »È¤¤¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢&man.sysinstall.8; ¤òºÆ¼Â¹Ô¤¹¤ì¤Ð
                 ÀßÄê¤Ç¤­¤Þ¤¹¡£</para>
             </note>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="hardware">
     <title>¥Ï¡¼¥É¥¦¥§¥¢¥³¥ó¥Ñ¥Á¥Ó¥ê¥Æ¥£</title>
 
     <para>
       <emphasis>Ìõ:
         ¤Ë¤·¤« <email>nishika@cheerful.com</email>¡¢
         1997 ǯ 11 ·î 12 Æü</emphasis>
     </para>
 
 
     <qandaset>
       <qandaentry>
         <question id="supported-hard-drives">
           <para>FreeBSD ¤Ï¡¢
             ¤É¤ó¤Ê¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Ï¡¢EIDE ¤È SCSI
             ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹ (¸ß´¹¥³¥ó¥È¥í¡¼¥é¤â´Þ¤ß¤Þ¤¹¡£
             ¼¡¤ÎÀỲ¾È)¡£
             ¤Þ¤¿Æȼ«¤Î <quote>Western Digital</quote>
             ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»ÈÍѤ·¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¥É¥é¥¤¥Ö (MFM¡¢
             RLL¡¢ESDI¡¢¤â¤Á¤í¤ó IDE) ¤â¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             Æȼ«»ÅÍͤΥ¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»ÈÍѤ¹¤ë
             ESDI ¥³¥ó¥È¥í¡¼¥é¤Ç¤ÏÆ°ºî¤·¤Ê¤¤¤â¤Î¤¬¤¢¤ê¡¢
             WD1002/3/6/7
             ¤È¤½¤Î¸ß´¹¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤È¾×Æͤ·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="supported-scsi-controllers">
           <para>¤É¤Î SCSI ¥³¥ó¥È¥í¡¼¥é¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para><ulink url="../handbook/install.html#INSTALL-HW">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯</ulink>¤Ëµ­¤µ¤ì¤Æ¤¤¤ë´°Á´¤Ê¥ê¥¹¥È¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="supported-cdrom-drives">
           <para>¤É¤ó¤Ê CD-ROM ¥É¥é¥¤¥Ö¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë SCSI ¥³¥ó¥È¥í¡¼¥é¤ËÀܳ¤Ç¤­¤ë SCSI
             ¥É¥é¥¤¥Ö¤Ï¡¢¤¹¤Ù¤Æ¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¤Þ¤¿¡¢°Ê²¼¤ÎÀìÍÑ CD-ROM
             ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤â¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
           </para>
 
             <itemizedlist>
               <listitem>
                 <para>¥ß¥Ä¥ß LU002 (8bit)¡¢LU005 (16bit) ¤ª¤è¤Ó FX001D (16bit 2ÇÜ®)¡£</para>
               </listitem>
 
               <listitem>
                 <para>¥½¥Ë¡¼ CDU 31/33A</para>
               </listitem>
 
               <listitem>
                 <para>Sound Blaster Èó SCSI ¥¿¥¤¥×¤Î CD-ROM</para>
               </listitem>
 
               <listitem>
                 <para>¾¾²¼/Panasonic CD-ROM</para>
               </listitem>
 
               <listitem>
                 <para>ATAPI ¸ß´¹¤Î IDE CD-ROM</para>
               </listitem>
             </itemizedlist>
 
           <para>
             SCSI ¤Ç¤Ê¤¤¥«¡¼¥É¤Ï¤¹¤Ù¤Æ¡¢SCSI ¥É¥é¥¤¥Ö¤è¤ê¤â¶Ë¤á¤ÆÆ°ºî®ÅÙ¤¬
             ÃÙ¤¤¤³¤È¤¬ÃΤé¤ì¤Æ¤ª¤ê¡¢ATAPI CD-ROM ¤Ë¤ÏÆ°ºî¤·¤Ê¤¤¤â¤Î¤â¤¢¤ë¤è¤¦¤Ç¤¹¡£
           </para>
 
           <para>
             BSDi ¤Î FreeBSD 2.2 CD-ROM ¤«¤é¤Ï CD ¤«¤é¤ÎľÀܵ¯Æ°¤¬
             ¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="supported-cdrw-drives">
           <para>FreeBSD ¤Ï¡¢¤É¤Î CD-RW ¥É¥é¥¤¥Ö¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>FreeBSD ¤Ï ATAPI ¸ß´¹¤Î IDE CD-R ¤Þ¤¿¤Ï CD-RW ¥É¥é¥¤¥Ö¤Ç
             ¤¢¤ì¤ÐÂбþ¤·¤Æ¤¤¤Þ¤¹¡£FreeBSD ¥Ð¡¼¥¸¥ç¥ó 4.0 °Ê¹ß¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             &man.burncd.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¤ò¤´Í÷¤¯¤À¤µ¤¤¡£¤½¤ì°ÊÁ°¤Î
             ¥Ð¡¼¥¸¥ç¥ó¤Î FreeBSD ¤Ç¤Ï¡¢
             <filename>/usr/share/examples/atapi</filename> ¤Ë¤¢¤ëÎã¤ò
             ¤´Í÷¤¯¤À¤µ¤¤¡£</para>
 
           <para>¤Þ¤¿¡¢FreeBSD ¤Ï SCSI ¤Î CD-R ¤Þ¤¿¤Ï CD-RW ¥É¥é¥¤¥Ö¤Ë¤â
             Âбþ¤·¤Æ¤¤¤Þ¤¹¡£ports ¤Þ¤¿¤Ï packages ¤«¤é
             <command>cdrecord</command> ¥³¥Þ¥ó¥É¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¡¢
             ¥«¡¼¥Í¥ë¤Ë <devicename>pass</devicename> ¥Ç¥Ð¥¤¥¹¤¬ÁȤ߹þ¤Þ¤ì¤Æ
             ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="zip-support">
           <para>ZIP ¥É¥é¥¤¥Ö¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤â¤Á¤í¤ó¡¢
             FreeBSD ¤Ï SCSI ZIP ¥É¥é¥¤¥Ö (³°ÉÕ¤±) ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             ZIP ¥É¥é¥¤¥Ö¤Ï SCSI ID ¤ò 5 ¤« 6 ¤ËÀßÄꤷ¤¿¾õÂ֤Ǥʤé»ÈÍѤǤ­¤Þ¤¹¤¬¡¢
             ¤â¤· SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤Î BIOS ¤¬¥µ¥Ý¡¼¥È¤·¤Æ¤µ¤¨¤¤¤ì¤Ð
             ZIP ¥É¥é¥¤¥Ö¤«¤éµ¯Æ°¤µ¤»¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
             ¤É¤Î¥Û¥¹¥È¥¢¥À¥×¥¿¤¬ SCSI ID ¤ò 0 ¤ä 1 °Ê³°¤ËÀßÄꤷ¤¿¥Ç¥Ð¥¤¥¹¤«¤é
             µ¯Æ°¤Ç¤­¤ë¤Î¤«¤Ï¤ï¤«¤ê¤Þ¤»¤ó¡£¤½¤¦¤·¤¿¤¤¾ì¹ç¤Ï¡¢¥¢¥À¥×¥¿¤Î
             ¥É¥­¥å¥á¥ó¥È¤ò»²¾È¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
           <para>
             ATAPI (IDE) ZIP ¥É¥é¥¤¥Ö¤Ï¡¢FreeBSD 2.2.6
             °Ê¹ß¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Ð¡¼¥¸¥ç¥ó 3.0 °Ê¹ß¤Î FreeBSD ¤Ç¤Ï¡¢
             ¥Ñ¥é¥ì¥ë¥Ý¡¼¥ÈÀܳ¤Î ZIP ¥É¥é¥¤¥Ö¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             ºÇ¶á¤Î¥Ð¡¼¥¸¥ç¥ó¤Î FreeBSD ¤ò¤ª»È¤¤¤Ç¤·¤¿¤é¡¢
             ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë
             <devicename>scbus0</devicename>¡¢
             <devicename>da0</devicename>¡¢
             <devicename>ppbus0</devicename>¡¢
             <devicename>vp0</devicename>
             ¤Î³Æ¥É¥é¥¤¥Ð¤¬µ­½Ò¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
             (GENERIC ¥«¡¼¥Í¥ë¤Ë¤Ï <devicename>vp0</devicename>
             ¤ò½ü¤¯¤¹¤Ù¤Æ¤Î¥É¥é¥¤¥Ð¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹)¡£
             ¤³¤ì¤é¤¹¤Ù¤Æ¤Î¥É¥é¥¤¥Ð¤¬¤¢¤ì¤Ð¡¢
             ¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤Î¥É¥é¥¤¥Ö¤Ï
             <devicename>/dev/da0s4</devicename>
             ¤È¤Ê¤ê¤Þ¤¹¡£
             ¥Ç¥£¥¹¥¯¤Ï
             <command>mount /dev/da0s4 /mnt</command> ¤È¤¹¤ë¤«
             <command>mount_msdos /dev/da0s4 /mnt</command> (DOS ¥Ç¥£¥¹¥¯¤Î¾ì¹ç)
             ¤È¤¹¤ë¤³¤È¤Ç¥Þ¥¦¥ó¥È¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¤½¤ì¤«¤é<link linkend="jaz">¥ê¥à¡¼¥Ð¥Ö¥ë¥É¥é¥¤¥Ö¤Ë´Ø¤¹¤ëÃí°Õ</link>¤ª¤è¤Ó¡¢
             <link linkend="disklabel">¡Ö¥Õ¥©¡¼¥Þ¥Ã¥È¡×¤Ë´Ø¤¹¤ëÃí°Õ</link>¤Ë¤Ä¤¤¤Æ¤â
             ³Îǧ¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="jaz-zip-removable-support">
           <para>¤Ç¤Ï¡¢JAZ ¤ä EZ¡¢
             ¤½¤ì¤«¤é¤½¤Î¾¤Î¥ê¥à¡¼¥Ð¥Ö¥ë¥É¥é¥¤¥Ö¤Ï¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Ç¤Ï¡¢IDE ¥Ð¡¼¥¸¥ç¥ó¤Î EZ
             ¥É¥é¥¤¥Ö¤ò½ü¤¯¤¹¤Ù¤Æ¤Î SCSI ¥Ç¥Ð¥¤¥¹¤Ï¡¢
             SCSI ¤Î¥Ç¥£¥¹¥¯¤ÈƱÅù¤Ë°·¤ï¤ì¤Þ¤¹¡£
             ¤Þ¤¿ IDE EZ ¤Ï IDE ¥É¥é¥¤¥Ö¤ÈƱÅù¤È¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para><anchor id="jaz"/>
               ¥·¥¹¥Æ¥à²ÔƯÃæ¤Î¥á¥Ç¥£¥¢¸ò´¹¤Ë¤Ä¤¤¤Æ
               FreeBSD ¤¬¤É¤ì¤Û¤É¤¦¤Þ¤¯Æ°¤¯¤«Ä꤫¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
               ¤â¤Á¤í¤ó¥á¥Ç¥£¥¢¤òÆþ¤ìÂؤ¨¤ëÁ°¤Ë¤½¤Î¥É¥é¥¤¥Ö¤Î¥Þ¥¦¥ó¥È¤ò²ò½ü¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Ê¤¤¤Ç¤·¤ç¤¦¤·¡¢
               FreeBSD ¤¬¤½¤ì¤é¤òǧ¼±¤¹¤ë¤Ë¤Ï¡¢
               µ¯Æ°»þ¤Ë³°Éô¥æ¥Ë¥Ã¥È¤Ë¤âÅŸ»¤¬ÅêÆþ¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Ê¤¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para><link linkend="disklabel">¡Ö¥Õ¥©¡¼¥Þ¥Ã¥È¡×¤Ë´Ø¤¹¤ëÃí°Õ</link>¤â»²¾È¤Î¤³¤È¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multiport-serial-support">
           <para>¤É¤Î¥Þ¥ë¥Á¥Ý¡¼¥È¥·¥ê¥¢¥ë¥«¡¼¥É¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>°ìÍ÷¤Ï
             <ulink url="../handbook/install-hw.html#INSTALL-MISC">¤½¤Î¾¤Î¥Ç¥Ð¥¤¥¹</ulink>¤ÎÀá¤Ë¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ̵̾¤Î¥«¡¼¥É¤Ë¤â¤¦¤Þ¤¯Æ°¤¯¤â¤Î¤¬¤¢¤ê¡¢
             ÆÃ¤Ë AST ¸ß´¹¤È¤¤¤ï¤ì¤Æ¤¤¤ë¤â¤Î¤Ë¿¤¯¸«¤é¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             ¥«¡¼¥ÉÀßÄê¤Î¾ÜºÙ¤Ê¾ðÊó¤Ï¡¢&man.sio.4;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="usbkbd">
           <para>USB ¥­¡¼¥Ü¡¼¥É¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢FreeBSD ¤Ç»È¤¨¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             USB ¥Ç¥Ð¥¤¥¹¤Ï FreeBSD 3.1 ¤«¤é¥µ¥Ý¡¼¥È¤µ¤ì¤Þ¤·¤¿¤¬¡¢
             ¼ÂÁõ¤Ï FreeBSD 3.2 ¤Ç¤¢¤Ã¤Æ¤â¤Þ¤À´°Á´¤Ç¤Ï¤Ê¤¤¤¿¤á¡¢
             ɬ¤º¤·¤â°ÂÄꤷ¤ÆÆ°ºî¤¹¤ë¤È¤Ï¸Â¤ê¤Þ¤»¤ó¡£
             ¤â¤·¡¢¤½¤ì¤Ç¤â USB ¥­¡¼¥Ü¡¼¥É¤ò»È¤Ã¤Æ¤ß¤¿¤¤¤È¤¤¤¦¿Í¤Ï¡¢
             °Ê²¼¤Î¼ê½ç¤ò»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <procedure>
             <step>
               <para>FreeBSD 3.2 ¤«¡¢¤½¤ì°Ê¹ß¤ò»È¤¤¤Þ¤¹¡£</para>
             </step>
 
             <step>
               <para>
                 ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤Î¹Ô¤òÄɲä·¡¢
                 ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Þ¤¹¡£
               </para>
 
               <programlisting>device  uhci
 device  ohci
 device  usb
 device  ukbd
 options KBD_INSTALL_CDEV</programlisting>
 
               <para>FreeBSD 4.0 ¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
                 Âå¤ï¤ê¤Ë¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
               <programlisting>controller      uhci0
 controller      ohci0
 controller      usb0
 controller      ukbd0
 options         KBD_INSTALL_CDEV</programlisting>
             </step>
 
             <step>
               <para><filename>/dev</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤Ë°ÜÆ°¤·¡¢
                 ¼¡¤Î¤è¤¦¤Ë¤·¤Æ¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤òºîÀ®¤·¤Þ¤¹¡£</para>
 
               <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV kbd0 kbd1</userinput></screen>
             </step>
 
             <step>
               <para><filename>/etc/rc.conf</filename> ¤òÊÔ½¸¤·¡¢
                 °Ê²¼¤Î¹Ô¤òÄɲä·¤Þ¤¹¡£</para>
 
               <programlisting>usbd_enable="YES"
 usbd_flags=""</programlisting>
             </step>
           </procedure>
 
           <para>
             ¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤µ¤»¤¿¸å¡¢
             AT¡¢USB ξÊý¤Î¥­¡¼¥Ü¡¼¥É¤¬Àܳ¤µ¤ì¤Æ¤¤¤ì¤Ð¡¢
             AT ¥­¡¼¥Ü¡¼¥É¤Ï <devicename>/dev/kbd0</devicename> ¤Ë¡¢
             USB ¥­¡¼¥Ü¡¼¥É¤Ï <devicename>/dev/kbd1</devicename>¤Ë¤Ê¤ê¤Þ¤¹¡£
             °ìÊý¡¢USB ¥­¡¼¥Ü¡¼¥É¤À¤±¤¬Àܳ¤µ¤ì¤Æ¤¤¤ë¤Ê¤é¡¢
             <devicename>/dev/ukbd0</devicename> ¤È¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             USB ¥­¡¼¥Ü¡¼¥É¤ò¥³¥ó¥½¡¼¥ë¤ÇÍøÍѤ¹¤ë¤Ë¤Ï¡¢
             ¤½¤ì¤ò¥³¥ó¥½¡¼¥ë¥É¥é¥¤¥Ð¤ËÂФ·¤ÆÌÀ¼¨Åª¤Ë»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¥·¥¹¥Æ¥à¤Î½é´ü²½¤ÎºÝ¤Ë¡¢¼¡¤Ë¼¨¤¹¤è¤¦¤Ê¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd1 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>
 
           <para>
             ¤¿¤À¤·¡¢USB ¥­¡¼¥Ü¡¼¥É¤·¤«Àܳ¤µ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢¤½¤ì¤Ï
             <devicename>/dev/kbd0</devicename> ¤È¤·¤Æ¥¢¥¯¥»¥¹¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢
             ¥³¥Þ¥ó¥É¤Ï¼¡¤Î¤è¤¦¤Ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤´Ãí°Õ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd0 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>
 
           <para>
             ¾å¤Î¥³¥Þ¥ó¥É¤Ï¡¢<filename>/etc/rc.i386</filename>
             ¤ËÄɲ乤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¤³¤ÎÀßÄê¤ò°ìÅٹԤʤäƤ¤¤ì¤Ð¡¢
             X ´Ä¶­¤Ç¤âÆä˾¤ÎÀßÄê¤Ê¤·¤Ë USB ¥­¡¼¥Ü¡¼¥É¤¬ÍøÍѤǤ­¤Þ¤¹¡£
           </para>
 
           <para>
             USB ¥­¡¼¥Ü¡¼¥É¤Î³èÀþÁÞÈ´ (¥Û¥Ã¥È¥×¥é¥°µ¡Ç½) ¤Ï¡¢
             ¤Þ¤À¤ª¤½¤é¤¯¤­¤Á¤ó¤ÈÆ°ºî¤·¤Ê¤¤¤È»×¤ï¤ì¤Þ¤¹¡£
             ¥È¥é¥Ö¥ë¤òÈò¤±¤ë¤¿¤á¤Ë¤â¡¢¥­¡¼¥Ü¡¼¥É¤Ï¥·¥¹¥Æ¥à¤òµ¯Æ°¤µ¤»¤ëÁ°¤ËÀܳ¤·¤Æ¤ª¤­¡¢
             ¥·¥ã¥Ã¥È¥À¥¦¥ó¤¹¤ë¤Þ¤Ç¤Ï¤º¤µ¤Ê¤¤¤è¤¦¤Ë¤·¤¿Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¡¢&man.ukbd.4; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="busmouse">
           <para>ÄÁ¤·¤¤¥Ð¥¹¥Þ¥¦¥¹¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢¤É¤Î¤è¤¦¤ËÀßÄꤹ¤ì¤Ð¤¤¤¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Ï Microsoft¡¢Logitech¡¢
             ATI Åù¤Î¥á¡¼¥«¡¼¤«¤é½Ð¤Æ¤¤¤ë¥Ð¥¹¥Þ¥¦¥¹¤È InPort
             ¥Ð¥¹¥Þ¥¦¥¹¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£FreeBSD 2.X ¤Î¾ì¹ç¡¢
             ¥Ð¥¹¥Þ¥¦¥¹¤Î¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Ï GENERIC ¥«¡¼¥Í¥ë¤Ëɸ½à¤Ç´Þ¤Þ¤ì¤Þ¤¹¤¬¡¢
             FreeBSD 3.X °Ê¹ß¤Ç¤Ïɸ½à¤Ç´Þ¤Þ¤ì¤Æ¤¤¤Þ¤»¤ó¡£¤â¤·¥Ð¥¹¥Þ¥¦¥¹¤Î¥Ç¥Ð¥¤¥¹
             ¥É¥é¥¤¥Ð¤ò´Þ¤à¥«¡¼¥Í¥ë¤ò¼«Ê¬¤Ç¹½ÃÛ¤¹¤ë¾ì¹ç¤Ë¤Ï¡¢
             ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤Î¹Ô¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>¤½¤ì¤Ï FreeBSD 3.0 ¤ò´Þ¤à¡¢¤½¤ì°ÊÁ°¤Î¥ê¥ê¡¼¥¹¤Î¾ì¹ç¤Ï¼¡¤Î¤È¤ª¤ê¡¢</para>
 
           <programlisting>device mse0 at isa? port 0x23c tty irq5 vector mseintr</programlisting>
 
           <para>FreeBSD 3.X ¤Ç¤Ï¡¢¼¡¤Î¤È¤ª¤ê¤Ç¤¹¡£</para>
 
           <programlisting>device mse0 at isa? port 0x23c tty irq5</programlisting>
 
           <para>¤½¤·¤Æ FreeBSD 4.X ¤È¤½¤ì°Ê¹ß¤Ç¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
 
           <programlisting>device mse0 at isa? port 0x23c irq5</programlisting>
 
           <para>
             Ä̾ï¥Ð¥¹¥Þ¥¦¥¹¤Ë¤ÏÀìÍѤΥ¤¥ó¥¿¥Õ¥§¡¼¥¹¥«¡¼¥É¤¬Éí°¤·¤Æ¤¤¤Þ¤¹¡£
             ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¥«¡¼¥É¤Ë¤è¤Ã¤Æ¤Ï¥Ý¡¼¥È¥¢¥É¥ì¥¹¤ä³ä¤ê¹þ¤ßÈÖ¹æ¤ò¾åµ­¤Î
             ÀßÄê°Ê³°¤ËÊѹ¹¤Ç¤­¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¾Ü¤·¤¯¤Ï¥Ð¥¹¥Þ¥¦¥¹¤Î¥Þ¥Ë¥å¥¢¥ë¤È
             &man.mse.4; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ps2mouse">
           <para>PS/2 ¥Þ¥¦¥¹ (¡Ö¥Þ¥¦¥¹¥Ý¡¼¥È¥Þ¥¦¥¹¡×¡¢¡Ö¥­¡¼¥Ü¡¼¥É¥Þ¥¦¥¹¡×) ¤ò
             »È¤¦¤Ë¤Ï¤É¤Î¤è¤¦¤ËÀßÄꤹ¤ì¤Ð¤¤¤¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤¢¤Ê¤¿¤¬ 2.2.5 °Ê¹ß¤Î¥Ð¡¼¥¸¥ç¥ó FreeBSD ¤ò»È¤Ã¤Æ¤¤¤ë¤Î¤Ê¤é¡¢
             ɬÍפʥɥ饤¥Ð <devicename>psm</devicename>
             ¤Ï¥«¡¼¥Í¥ë¤Ë´Þ¤Þ¤ì¤Æ¤¤¤ÆÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¥«¡¼¥Í¥ë¤Ïµ¯Æ°»þ¤Ë PS/2 ¥Þ¥¦¥¹¤ò¸¡½Ð¤¹¤ë¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¤¢¤Ê¤¿¤Î»È¤Ã¤Æ¤¤¤ë FreeBSD
             ¤¬Èæ³ÓŪ¿·¤·¤¤¤±¤ì¤ÉÁ°¤Î¥Ð¡¼¥¸¥ç¥ó (2.1.x °Ê¹ß) ¤Î¤â¤Î¤Ê¤é¡¢
             ¥¤¥ó¥¹¥È¡¼¥ë¤Î»þ¤Ë¡¢Ã±¤Ë¥«¡¼¥Í¥ë¤Î¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¤Î¥á¥Ë¥å¡¼¾å¤Ç
             PS/2 ¥Þ¥¦¥¹¤òÍ­¸ú²½¤¹¤ë¤À¤±¤Ç¤¹¡¢¤¢¤ë¤¤¤Ï¸å¤Ç
             <prompt>boot:</prompt> ¥×¥í¥ó¥×¥È¾å¤Ç
             <option>-c</option> ¤ò»ØÄꤹ¤ë¤³¤È¤Ç¤â¥á¥Ë¥å¡¼¤Ï¸½¤ì¤Þ¤¹¡£
             ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï̵¸ú¤ËÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢
             ÌÀ¼¨Åª¤ËÍ­¸ú²½¤·¤Æ¤¢¤²¤Ê¤¤¤È¤¤¤±¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤¢¤Ê¤¿¤Î»È¤Ã¤Æ¤¤¤ë FreeBSD ¤¬Èæ³ÓŪ¸Å¤¤¤â¤Î¤Ê¤é¡¢
             ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤Î¹Ô¤ò²Ã¤¨¤Æ
             ¥«¡¼¥Í¥ë¤òºÆ¥³¥ó¥Ñ¥¤¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤½¤ì¤Ï FreeBSD 3.0 ¤ò´Þ¤à¡¢¤½¤ì°ÊÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï¼¡¤Î¤È¤ª¤ê¡¢</para>
 
             <programlisting>device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr</programlisting>
 
             <para>FreeBSD 3.1 ¤ò´Þ¤à¡¢¤½¤ì°Ê¹ß¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï¼¡¤Î¤È¤ª¤ê¡¢</para>
 
             <programlisting>device psm0 at isa? tty irq 12</programlisting>
 
             <para>FreeBSD 4.0 ¤È¤½¤ì°Ê¹ß¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï¼¡¤Î¤È¤ª¤ê¤Ç¤¹¡£</para>
 
             <programlisting>device psm0 at atkbdc? irq 12</programlisting>
 
           <para>
             ¥«¡¼¥Í¥ë¤ÎºÆ¹½ÃۤˤĤ¤¤Æ¤è¤¯ÃΤé¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢
             <ulink url="../handbook/kernelconfig.html">¥«¡¼¥Í¥ë¤Î¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó</ulink>¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             µ¯Æ°»þ¤Ë¥«¡¼¥Í¥ë¤¬ <devicename>psm0</devicename> ¤ò¸¡½Ð¤·¤¿¤é¡¢
             <devicename>psm0</devicename> ¤Î¥¨¥ó¥È¥ê¤¬ <filename>/dev</filename>
             ¤ÎÃæ¤Ë¤¢¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£¤½¤ì¤Ë¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
 
            <screen>&prompt.root; <userinput>cd /dev; sh MAKEDEV psm0</userinput></screen>
 
             ¤³¤ì¤Ï <username>root</username> ¤Ç¥í¥°¥¤¥ó¤·¤Æ¤¤¤ë¤È¤­¤Ë¹Ô¤Ê¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="moused">
           <para>X Window System °Ê³°¤Î´Ä¶­¤Ç¥Þ¥¦¥¹¤ò»È¤¦¤³¤È¤Ï²Äǽ¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤â¤·¥Ç¥Õ¥©¥ë¥È¤Î¥³¥ó¥½¡¼¥ë¥É¥é¥¤¥Ð¤Ç¤¢¤ë syscons
             ¤ò»È¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
             ¥Æ¥­¥¹¥È¥³¥ó¥½¡¼¥ë¾å¤Ç¥Þ¥¦¥¹¤ò»È¤Ã¤Æ¡¢
             ¥Æ¥­¥¹¥È¤Î¥«¥Ã¥È¥¢¥ó¥É¥Ú¡¼¥¹¥È¤¬¤Ç¤­¤Þ¤¹¡£
             ¥Þ¥¦¥¹¥Ç¡¼¥â¥ó¤Ç¤¢¤ë moused ¤òµ¯Æ°¤·¡¢
             ²¾ÁÛ¥³¥ó¥½¡¼¥ë¤Ç¥Þ¥¦¥¹¥Ý¥¤¥ó¥¿¤òÍ­¸ú¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
            <screen>&prompt.root; <userinput>moused -p /dev/<replaceable>xxxx</replaceable> -t <replaceable>yyyy</replaceable></userinput>
 &prompt.root; <userinput>vidcontrol -m on</userinput></screen>
 
           <para>
             ¤³¤³¤Ç <replaceable>xxxx</replaceable>
             ¤Ï¥Þ¥¦¥¹¤Î¥Ç¥Ð¥¤¥¹Ì¾¡¢
             <replaceable>yyyy</replaceable>
             ¤Ï¥Þ¥¦¥¹¤Î¥×¥í¥È¥³¥ë¥¿¥¤¥×¤Ç¤¹¡£
             ¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¥×¥í¥È¥³¥ë¥¿¥¤¥×¤Ë¤Ä¤¤¤Æ¤Ï
             &man.moused.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¥·¥¹¥Æ¥à¤òµ¯Æ°¤¹¤ë»þ¤Ë¼«Æ°Åª¤Ë
             moused ¤òµ¯Æ°¤·¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
             FreeBSD 2.2.1 ¤Ç¤Ï°Ê²¼¤ÎÊÑ¿ô¤ò
             <filename>/etc/sysconfig</filename>
             ¤ÇÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <programlisting>mousedtype="<replaceable>yyyy</replaceable>"
 mousedport="<replaceable>xxxx</replaceable>"
 mousedflags=""</programlisting>
 
           <para>
             FreeBSD 2.2.2 °Ê¹ß¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï
             <filename>/etc/rc.conf</filename>
             ¤Ç°Ê²¼¤Î¤è¤¦¤ËÀßÄꤷ¤Þ¤¹¡£</para>
 
           <programlisting>moused_type="<replaceable>yyyy</replaceable>"
 moused_port="<replaceable>xxxx</replaceable>"
 moused_flags=""</programlisting>
 
            <para>FreeBSD 3.1 ¤È¤½¤ì°Ê¹ß¤Ç PS/2 ¥Þ¥¦¥¹¤òÍøÍѤ¹¤ë¾ì¹ç¤Ï¡¢
               <literal>moused_enable=&quot;YES&quot;</literal> ¤ò
               <filename>/etc/rc.conf</filename> ¤Ë½ñ¤­²Ã¤¨¤ë¤À¤±¤Ç¤¹¡£</para>
 
           <para>
             ¤Þ¤¿¡¢µ¯Æ°»þ¤Ë¤¹¤Ù¤Æ¤Î²¾ÁÛüËö¤Ç¡¢
             ɸ½à¤Î¥³¥ó¥½¡¼¥ë¤Ë²Ã¤¨¥Þ¥¦¥¹¥Ç¡¼¥â¥ó¤â»È¤¨¤ë¤è¤¦¤Ë¤·¤¿¤¤¡¢
             ¤È¤¤¤¦¾ì¹ç¤Ë¤Ï¡¢°Ê²¼¤Î¹Ô¤ò
             <filename>/etc/rc.conf</filename> ¤Ë²Ã¤¨¤Þ¤¹¡£
           </para>
 
           <programlisting>allscreens_flags="-m on"</programlisting>
 
           <para>
             FreeBSD 2.2.6 °Ê¹ß¤Î¾ì¹ç¤Ç
             Èæ³ÓŪ¿·¤·¤¤¥·¥ê¥¢¥ë¥Þ¥¦¥¹¤ò»È¤Ã¤Æ¤¤¤ë¤Ê¤é¤Ð¡¢
             ¥Þ¥¦¥¹¥Ç¡¼¥â¥ó¤Ï¥Þ¥¦¥¹¤Î¥×¥í¥È¥³¥ë¥¿¥¤¥×¤ò¼«Æ°È½Ê̤Ǥ­¤Þ¤¹¡£
             ¼«Æ°È½Ê̤ò»î¤ß¤ë¤Ë¤Ï¡¢¥×¥í¥È¥³¥ë¥¿¥¤¥×¤È¤·¤Æ
             <literal>auto</literal>
             ¤ò»ØÄꤷ¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Þ¥¦¥¹¥Ç¡¼¥â¥ó¤ò¼Â¹ÔÃæ¤Ï¡¢¥Þ¥¦¥¹¥Ç¡¼¥â¥ó¤È¾¤Î¥×¥í¥°¥é¥à
             (¤¿¤È¤¨¤Ð X Window System)
             ¤Î´Ö¤Ç¥Þ¥¦¥¹¤Ø¤Î¥¢¥¯¥»¥¹¤òÄ´À°¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤³¤ÎÌäÂê¤Ë¤Ä¤¤¤Æ¤Ï <link linkend="x-and-moused">X ¤È¥Þ¥¦¥¹</link>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="text-mode-cut-paste">
           <para>¥Þ¥¦¥¹¤ò»È¤Ã¤Æ¡¢
             ¥Æ¥­¥¹¥È¥³¥ó¥½¡¼¥ë¤Ç¥«¥Ã¥È¥¢¥ó¥É¥Ú¡¼¥¹¥È¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤¿¤é¤è¤¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¥Þ¥¦¥¹¥Ç¡¼¥â¥ó¤òµ¯Æ°
             (<link linkend="moused">Á°¤Î¼ÁÌä¤ËÂФ¹¤ëÅú¤¨</link>¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤)
             ¤·¤¿¤¢¤È¡¢
             ¥Ü¥¿¥ó 1 (º¸¥Ü¥¿¥ó) ¤ò²¡¤·¤Ê¤¬¤é¥Þ¥¦¥¹¤òÆ°¤«¤·¤ÆÈϰϤò»ØÄꤷ¤Þ¤¹¡£
             ¥Ü¥¿¥ó 2 (Ãæ¥Ü¥¿¥ó) ¤Þ¤¿¤Ï¥Ü¥¿¥ó 3 (±¦¥Ü¥¿¥ó) ¤ò¥¯¥ê¥Ã¥¯¤¹¤ë¤È¥Æ¥­¥¹¥È
             ¥«¡¼¥½¥ë¤Î°ÌÃÖ¤ËÁªÂò¤·¤¿ÈϰϤΥƥ­¥¹¥È¤¬¥Ú¡¼¥¹¥È¤µ¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             FreeBSD 2.2.6 °Ê¹ß¤Ç¤Ï¡¢¥Ü¥¿¥ó 2
             ¤ò¥¯¥ê¥Ã¥¯¤¹¤ë¤È¥Ú¡¼¥¹¥È¤µ¤ì¡¢¥Ü¥¿¥ó 3
             ¤ò¥¯¥ê¥Ã¥¯¤·¤¿¾ì¹ç¤Ë´û¸¤ÎÁªÂòÈϰϤ¬¸½ºß¤Î¥Þ¥¦¥¹¥Ý¥¤¥ó¥¿¤Î°ÌÃÖ¤Þ¤Ç
             ¡Ö±äĹ¤Þ¤¿¤Ïû½Ì¡×¤µ¤ì¤Þ¤¹¡£¤â¤·¥Þ¥¦¥¹¤ËÃæ¥Ü¥¿¥ó¤¬¤Ê¤¤¤Ê¤é¡¢
             moused ¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤ÆÃæ¥Ü¥¿¥ó¤Î¥¨¥ß¥å¥ì¡¼¥·¥ç¥ó¤ò¤¹¤ë¤«¡¢
             ¾¤Î¥Ü¥¿¥ó¤òÃæ¥Ü¥¿¥ó¤È¤·¤Æ»È¤¦»ö¤¬¤Ç¤­¤Þ¤¹¡£
             ¾Ü¤·¤¯¤Ï &man.moused.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="usbmouse">
           <para>USB ¥Þ¥¦¥¹¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢FreeBSD ¤Ç»È¤¨¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             USB ¥Ç¥Ð¥¤¥¹¤Ï FreeBSD 3.1 ¤«¤é¥µ¥Ý¡¼¥È¤µ¤ì¤Þ¤·¤¿¤¬¡¢
             ¼ÂÁõ¤Ï FreeBSD 3.2 ¤Ç¤¢¤Ã¤Æ¤â¤Þ¤À´°Á´¤Ç¤Ï¤Ê¤¤¤¿¤á¡¢
             ɬ¤º¤·¤â°ÂÄꤷ¤ÆÆ°ºî¤¹¤ë¤È¤Ï¸Â¤ê¤Þ¤»¤ó¡£
             ¤â¤·¡¢¤½¤ì¤Ç¤â USB ¥Þ¥¦¥¹¤ò»È¤Ã¤Æ¤ß¤¿¤¤¤È¤¤¤¦¿Í¤Ï¡¢
             °Ê²¼¤Î¼ê½ç¤ò»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <procedure>
             <step>
               <para>FreeBSD 3.2 ¤«¡¢¤½¤ì°Ê¹ß¤ò»È¤¤¤Þ¤¹¡£</para>
             </step>
 
             <step>
               <para>
                 ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤Î¹Ô¤òÄɲä·¡¢
                 ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Þ¤¹¡£
               </para>
 
               <programlisting>device  uhci
 device  ohci
 device  usb
 device  ums</programlisting>
 
               <para>FreeBSD 4.0 ¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
                 Âå¤ï¤ê¤Ë¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
               <programlisting>controller      uhci0
 controller      ohci0
 controller      usb0
 device          ums0</programlisting>
             </step>
 
             <step>
               <para><filename>/dev</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤Ë°ÜÆ°¤·¡¢
                 ¼¡¤Î¤è¤¦¤Ë¤·¤Æ¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤òºîÀ®¤·¤Þ¤¹¡£</para>
 
               <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV ums0</userinput></screen>
             </step>
 
             <step>
               <para><filename>/etc/rc.conf</filename> ¤òÊÔ½¸¤·¡¢
                 °Ê²¼¤Î¹Ô¤òÄɲä·¤Þ¤¹¡£</para>
 
               <programlisting>moused_enable="YES"
 moused_type="auto"
 moused_port="/dev/ums0"
 moused_flags=""
 usbd_enable="YES"
 usbd_flags=""</programlisting>
 
               <para>moused ¤ÎÀßÄê¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
                 <link linkend="moused">Á°¹à</link>¤â»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
               </para>
             </step>
 
             <step>
               <para>
                 X ¤Î¥»¥Ã¥·¥ç¥ó¤Ç USB ¥Þ¥¦¥¹¤ò»È¤¦¤Ë¤Ï¡¢
                 <filename>XF86Config</filename> ¤òÊÔ½¸¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
                 XFree86 3.3.2¡¢¤â¤·¤¯¤Ï¤½¤ì°Ê¹ß¤òÍøÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
                 <emphasis>Pointer</emphasis>
                 ¥»¥¯¥·¥ç¥ó¤¬¼¡¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
               </para>
 
               <programlisting>Device          "/dev/sysmouse"
 Protocol        "Auto"</programlisting>
 
               <para>
                 ¤½¤ì¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Î XFree86 ¤òÍøÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
                 <emphasis>Pointer</emphasis>
                 ¥»¥¯¥·¥ç¥ó¤¬¼¡¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
               </para>
 
               <programlisting>Device          "/dev/sysmouse"
 Protocol        "SysMouse"</programlisting>
             </step>
           </procedure>
 
           <para>X ´Ä¶­¤Ç¤Î¥Þ¥¦¥¹¤ÎÍøÍѤˤĤ¤¤Æ¤Ï¡¢
             <link linkend="x-and-moused">¾¤Î¹à</link>¤â»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             USB ¥Þ¥¦¥¹¤Î³èÀþÁÞÈ´ (¥Û¥Ã¥È¥×¥é¥°µ¡Ç½) ¤Ï¡¢
             ¤Þ¤À¤ª¤½¤é¤¯¤­¤Á¤ó¤ÈÆ°ºî¤·¤Ê¤¤¤È»×¤ï¤ì¤Þ¤¹¡£
             ¥È¥é¥Ö¥ë¤òÈò¤±¤ë¤¿¤á¤Ë¤â¡¢¥Þ¥¦¥¹¤Ï¥·¥¹¥Æ¥à¤òµ¯Æ°¤µ¤»¤ëÁ°¤ËÀܳ¤·¤Æ¤ª¤­¡¢
             ¥·¥ã¥Ã¥È¥À¥¦¥ó¤¹¤ë¤Þ¤Ç¤Ï¤º¤µ¤Ê¤¤¤è¤¦¤Ë¤·¤¿Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mouse-wheel-buttons">
           <para>¤ï¤¿¤·¤Î¥Þ¥¦¥¹¤Ë¤Ï¥Û¥¤¡¼¥ëµ¡Ç½¤äÊØÍø¤Ê¥Ü¥¿¥ó¤¬¤Ä¤¤¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢
             ¤³¤ì¤Ï FreeBSD ¤Ç¤â»È¤¨¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             Åú¤¨¤Ï»ÄÇ°¤Ê¤¬¤é¡Ö¾ì¹ç¤Ë¤è¤ê¤Þ¤¹¡×¤Ç¤¹¡£
             ¤³¤¦¤·¤¿¥Þ¥¦¥¹¤ÎÉÕ²ÃŪ¤Êµ¡Ç½¤ÏÂçÄñ¤Î¾ì¹ç¡¢Æüì¤Ê¥É¥é¥¤¥Ð¤òɬÍפȤ·¤Þ¤¹¡£
             ¥Þ¥¦¥¹¤Î¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤ä¥æ¡¼¥¶¤Î¥×¥í¥°¥é¥à¤¬
             ¤½¤Î¥Þ¥¦¥¹¤ËÂФ¹¤ë¸ÇÍ­¤Î¥µ¥Ý¡¼¥È¤ò¤·¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢
             ɸ½àŪ¤Ê 2 ¥Ü¥¿¥ó/3 ¥Ü¥¿¥ó¥Þ¥¦¥¹¤Î¤è¤¦¤Ë¿¶Éñ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             X ¥¦¥£¥ó¥É¥¦¥·¥¹¥Æ¥à¤Î´Ä¶­¤Ç¤Î¥Û¥¤¡¼¥ë¤Î»È¤¤Êý¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             <link linkend="x-and-wheel">X ¤È¥Û¥¤¡¼¥ë</link>¤Î¹à¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="psmerr">
           <para>
             ¤ï¤¿¤·¤Î¥Þ¥¦¥¹¤Ï¤­¤Á¤ó¤ÈÆ°¤¤¤Æ¤¯¤ì¤Ê¤¤¤è¤¦¤Ç¤¹¡£
             ¥Þ¥¦¥¹¥«¡¼¥½¥ë¤¬²èÌÌÃæ¤ò¤È¤Ó¤Þ¤ï¤ê¤Þ¤¹¡£
             ¤³¤Î¥Þ¥¦¥¹¤Ë¤Ï¥Û¥¤¡¼¥ë¤¬¤Ä¤¤¤Æ¤¤¤Æ¡¢
             Àܳ¤Ï PS/2 ¥Ý¡¼¥È¤Ç¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 3.2 ¤ª¤è¤Ó¤½¤ì°ÊÁ°¤Î PS/2 ¥Þ¥¦¥¹¥É¥é¥¤¥Ð psm ¤Ë¤Ï¡¢
             Logitech ¥â¥Ç¥ë M-S48 ¤È¤½¤Î
             OEM ¤Î¥Û¥¤¡¼¥ë¥Þ¥¦¥¹¤ÇÉÔ¶ñ¹ç¤¬È¯À¸¤·¤Þ¤¹¡£
             °Ê²¼¤Î¥Ñ¥Ã¥Á¤ò <filename>/sys/i386/isa/psm.c</filename>
             ¤ËŬÍѤ·¤Æ¡¢¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>Index: psm.c
 ===================================================================
 RCS file: /src/CVS/src/sys/i386/isa/Attic/psm.c,v
 retrieving revision 1.60.2.1
 retrieving revision 1.60.2.2
 diff -u -r1.60.2.1 -r1.60.2.2
 --- psm.c	1999/06/03 12:41:13	1.60.2.1
 +++ psm.c	1999/07/12 13:40:52	1.60.2.2
 @@ -959,14 +959,28 @@
      sc->mode.packetsize = vendortype[i].packetsize;
 
      /* set mouse parameters */
 +#if 0
 +    /*
 +     * A version of Logitech FirstMouse+ won't report wheel movement,
 +     * if SET_DEFAULTS is sent...  Don't use this command.
 +     * This fix was found by Takashi Nishida.
 +     */
      i = send_aux_command(sc->kbdc, PSMC_SET_DEFAULTS);
      if (verbose >= 2)
  	printf("psm%d: SET_DEFAULTS return code:%04x\n", unit, i);
 +#endif
      if (sc->config &amp; PSM_CONFIG_RESOLUTION) {
          sc->mode.resolution
  	    = set_mouse_resolution(sc->kbdc,
 -	        (sc->config &amp; PSM_CONFIG_RESOLUTION) - 1);
 +				   (sc->config &amp; PSM_CONFIG_RESOLUTION) - 1);
 +    } else if (sc->mode.resolution >= 0) {
 +	sc->mode.resolution
 +	    = set_mouse_resolution(sc->kbdc, sc->dflt_mode.resolution);
 +    }
 +    if (sc->mode.rate > 0) {
 +	sc->mode.rate = set_mouse_sampling_rate(sc->kbdc, sc->dflt_mode.rate);
      }
 +    set_mouse_scaling(sc->kbdc, 1);
 
      /* request a data packet and extract sync. bits */
      if (get_mouse_status(sc->kbdc, stat, 1, 3) &lt; 3) {</programlisting>
 
           <para>FreeBSD 3.2
             ¤è¤ê¿·¤·¤¤¥ê¥ê¡¼¥¹¤Ç¤Ï¤­¤Á¤ó¤ÈÆ°ºî¤¹¤ë¤Ï¤º¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="laptop-mouse-trackball">
           <para>¥é¥Ã¥×¥È¥Ã¥× PC ¤Î¥Þ¥¦¥¹/¥È¥é¥Ã¥¯¥Ü¡¼¥ë/¥¿¥Ã¥Á¥Ñ¥Ã¥É¤Ï»È¤¨¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             <link linkend="ps2mouse">Á°¤Î¼ÁÌä¤ËÂФ¹¤ëÅú¤¨</link>¤È¡¢
             <link linkend="pao">¥â¥Ð¥¤¥ë¥³¥ó¥Ô¥å¡¼¥Æ¥£¥ó¥°¤Î¥Ú¡¼¥¸</link>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tape-support">
           <para>¤É¤ó¤Ê¥Æ¡¼¥×¥É¥é¥¤¥Ö¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Ï SCSI ¤È QIC-36 (QIC-02 ¥¤¥ó¥¿¥Õ¥§¡¼¥¹ÉÕ¤­)
             ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤é¤Ë¤Ï 8-mm (Exabyte ¤È¸Æ¤Ð¤ì¤Æ¤¤¤Þ¤¹) ¤ä DAT ¥É¥é¥¤¥Ö¤â´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ½é´ü¤Î 8-mm ¥É¥é¥¤¥Ö¤ÎÃæ¤Ë¤Ï SCSI-2
             ¤È¤Þ¤Ã¤¿¤¯¸ß´¹À­¤ò»ý¤¿¤Ê¤¤¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤é¤Ï FreeBSD ¾å¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tape-changer-support">
           <para>¤É¤ó¤Ê¥Æ¡¼¥×¥Á¥§¥ó¥¸¥ã¡¼¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 2.2 ¤Ï &man.ch.4; ¥Ç¥Ð¥¤¥¹¤È &man.chio.1;
             ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤¿ SCSI ¥Á¥§¥ó¥¸¥ã¡¼¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             ¼ÂºÝ¤Î¥Á¥§¥ó¥¸¥ã¡¼¤ÎÀ©¸æÊýË¡¤Î¾ÜºÙ¤Ï¡¢&man.chio.1;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>»ÈÍѤ·¤Æ¤¤¤ëÀ½Éʤ¬ <application>AMANDA</application>
             ¤Î¤è¤¦¤Ë¥Á¥§¥ó¥¸¥ã¡¼¤ËÂбþºÑ¤ß¤Î¤â¤Î¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢
             ¼¡¤Î¤³¤È¤Ë¤Ä¤¤¤Æα°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤ì¤é¤ÎÀ½ÉʤÏǤ°Õ¤Î¥Ý¥¤¥ó¥È´Ö¤Î¥Æ¡¼¥×¤Î°ÜÆ°¤òÀ©¸æ¤¹¤ë¤À¤±¤Ê¤Î¤Ç¡¢
             ¥Æ¡¼¥×¤¬¤É¤Î¥¹¥í¥Ã¥È¤ËÆþ¤Ã¤Æ¤¤¤ë¤«¡¢¸½ºß¥É¥é¥¤¥Ö¤Ë¤¢¤ë¥Æ¡¼¥×¤¬
             ¤É¤Î¥¹¥í¥Ã¥È¤ËÌá¤ë¤Ù¤­¤«¤òÇÄ°®¤·¤Æ¤ª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sound-card-support">
           <para>¤É¤ó¤Ê¥µ¥¦¥ó¥É¥«¡¼¥É¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Ï SoundBlaster¡¢SoundBlaster Pro¡¢SoundBlaster 16¡¢
             Pro Audio Spectrum 16¡¢AdLib ¤½¤ì¤«¤é Gravis UltraSound ¥µ¥¦¥ó¥É¥«¡¼¥É¤ò
             ¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£MPU-401 ¤ä¤½¤Î¸ß´¹¥«¡¼¥É¤âµ¡Ç½¤ËÀ©¸Â¤Ï¤¢¤ë¤â¤Î¤Î
             ¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¥Þ¥¤¥¯¥í¥½¥Õ¥È¥µ¥¦¥ó¥É¥·¥¹¥Æ¥à¤Î¥¹¥Ú¥Ã¥¯¤Ë½àµò
             ¤·¤¿¥«¡¼¥É¤â¡¢<devicename>pcm</devicename> ¥É¥é¥¤¥Ð¤Ç¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
             <note>
               <para>
                 ¤³¤ì¤é¤Ï¥µ¥¦¥ó¥É¤Ë¤Ä¤¤¤Æ¤Î¤ß¤ÎÏäǤ¹! ¤³¤ì¤é¤Î¥É¥é¥¤¥Ð¤Ï
                 CD-ROM¡¢SCSI¡¢¥«¡¼¥É¾å¤Ë¤¢¤ë¥¸¥ç¥¤¥¹¥Æ¥£¥Ã¥¯¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤»¤ó
                 (SoundBlaster ¤ÏÎã³°¤Ç¤¹)¡£SoundBlaster SCSI ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ÈÈó SCSI
                 CD-ROM ¤Ï¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤¬¡¢¤½¤Î¥Ç¥Ð¥¤¥¹¤«¤é¤Ïµ¯Æ°¤Ç¤­¤Þ¤»¤ó¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="es1370-silent-pcm">
           <para><devicename>pcm</devicename>
             ¥É¥é¥¤¥Ð¤Ç es1370 ¤«¤é²»¤¬½Ð¤Ê¤¤¤Î¤Ï¤É¤¦¤Ë¤«¤Ê¤ê¤Þ¤»¤ó¤«?</para>
         </question><answer>
 
           <para>¥Þ¥·¥ó¤òµ¯Æ°¤¹¤ë¤´¤È¤Ë°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <screen>&prompt.root; <userinput>mixer pcm 100 vol 100 cd 100</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="network-cards">
           <para>¤É¤ó¤Ê¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤è¤ê´°Á´¤Ê°ìÍ÷¤Ë¤Ä¤¤¤Æ¤Ï<ulink url="../handbook/install-hw.html#INSTALL-NICS">¥¤¡¼¥µ¥Í¥Ã¥È¥«¡¼¥É</ulink>¤ÎÀá¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="no-math-coprocessor">
           <para>¿ôÃͱ黻¥³¥×¥í¥»¥Ã¥µ¤ò»ý¤Ã¤Æ¤¤¤Þ¤»¤ó¤¬¡¢²¿¤«¤Þ¤º¤¤¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
             <note>
               <para>
                 ¤³¤ì¤é¤Ï 386/486SX/486SLC ¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë±Æ¶Á¤·¤Þ¤¹
                 - ¤Û¤«¤Î¥Þ¥·¥ó¤Ç¤Ï CPU ¤ËÆ⢤µ¤ì¤Æ¤¤¤Þ¤¹¡£
               </para>
             </note>
 
           <para>
             °ìÈ̤ˤ³¤ì¤é¤ÏÌäÂê¤È¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
             ¤·¤«¤·¡¢¿ôÃͱ黻¥¨¥ß¥å¥ì¡¼¥·¥ç¥ó¥³¡¼¥É¤Î¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤«¡¢
             Àµ³Î¤µ¤Î¤¤¤º¤ì¤«¤òÁªÂò¤¹¤ë¾õ¶·¤¬¤¢¤ê¤Þ¤¹
             (¾Ü¤·¤¯¤Ï <link linkend="emul">FP
               ¥¨¥ß¥å¥ì¡¼¥·¥ç¥ó</link> ¤Ë¤Ä¤¤¤Æ¤ÎÀá¤ò¤´Í÷¤¯¤À¤µ¤¤)¡£
             ¤È¤¯¤Ë¡¢X ¾å¤Ç¸Ì¤òÉÁ¤¯ºÝ¤Ë¤È¤Æ¤âÃÙ¤¯¤Ê¤ë¤³¤È¤Ç¤·¤ç¤¦¡£
             ¿ôÃͱ黻¥³¥×¥í¥»¥Ã¥µ¤ò¹ØÆþ¤µ¤ì¤ë¤³¤È¤ò¶¯¤¯¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
             ¤È¤Æ¤âÌòΩ¤Ä¤³¤È¤Ç¤·¤ç¤¦¡£
           </para>
 
             <note>
               <para>
                 ¾¤Î¿ôÃͱ黻¥³¥×¥í¥»¥Ã¥µ¤è¤ê¤âÍ¥¤ì¤¿¥³¥×¥í¥»¥Ã¥µ¤â¤¢¤ê¤Þ¤¹¡£
                 ¤³¤ì¤Ï¸À¤¤¤Ë¤¯¤¤¤³¤È¤Ê¤Î¤Ç¤¹¤¬¡¢Intel ¤òÇ㤦¤¿¤á¤ËÌöµ¯¤Ë¤Ê¤ë¿Í¤â¤¤¤Ê¤¤¤Ç¤·¤ç¤¦¡£
                 ¤½¤ì¤¬ FreeBSD ¾å¤ÇÆ°¤¯¤È¤¤¤¦³Î¿®¤¬¤Ê¤¤¤Î¤Ê¤é¡¢¥¯¥í¡¼¥ó¤Ë¤´ÍÑ¿´¤ò¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="other-device-support">
           <para>FreeBSD ¤¬¥µ¥Ý¡¼¥È¤¹¤ë¥Ç¥Ð¥¤¥¹¤Ï¾¤Ë¤â¤¢¤ë¤ó¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para><ulink url="../handbook/install-hw.html#INSTALL-MISC">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯</ulink>¤Ëµ­¤µ¤ì¤Æ¤¤¤ë¡¢
             ¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¾¤Î¥Ç¥Ð¥¤¥¹¤Î°ìÍ÷¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="power-management-support">
           <para>¥Ñ¥ï¡¼¥Þ¥Í¡¼¥¸¥á¥ó¥Èµ¡Ç½ÉÕ¤­¤Î¥é¥Ã¥×¥È¥Ã¥× PC ¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡Ä¡£</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Ï°ìÉô¤Î¥Þ¥·¥ó¤Î <acronym>APM</acronym> ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             <filename>LINT</filename> ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë ¤Î
             <acronym>APM</acronym> ¤ÎÉôʬ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
             ¤µ¤é¤Ë¾Ü¤·¤¤¤³¤È¤Ï &man.apm.4; ¤ËºÜ¤Ã¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="micron-hang-boot">
           <para>Micron ¥·¥¹¥Æ¥à¤¬µ¯Æ°»þ¤Ë¸Ç¤Þ¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             ÆÃÄê¤Î Micron À½¤Î¥Þ¥¶¡¼¥Ü¡¼¥É¤ÎÃæ¤Ë¤Ï¡¢PCI BIOS ¤¬µ¬³ÊÄ̤ê¤Ë
             ¼ÂÁõ¤µ¤ì¤Æ¤¤¤Ê¤¤¤¿¤á¤Ë FreeBSD ¤Îµ¯Æ°¤Ë¼ºÇÔ¤¹¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
             ¤½¤Î BIOS ¤Ï¡¢PCI ¥Ç¥Ð¥¤¥¹¤ò¤¢¤ë¥¢¥É¥ì¥¹¤ÇÀßÄꤷ¤¿¤ÈÊó¹ð¤¹¤ë¤Ë¤â
             ´Ø¤ï¤é¤º¡¢¼ÂºÝ¤Ë¤Ï¤½¤¦¤·¤Æ¤¤¤Ê¤¤¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¤³¤ÎÌäÂê¤ò²óÈò¤¹¤ë¤Ë¤Ï¡¢BIOS ¤Î
             <quote>Plug and Play Operating System</quote>
             ¤ò̵¸ú¤ËÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£¤Þ¤¿¡¢¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï
             <ulink url="http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron">http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron</ulink>
             ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="newer-adaptec-support">
           <para>¿·¤·¤¤ Adaptec ¥³¥ó¥È¥í¡¼¥é¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢
             FreeBSD ¤¬¸¡½Ð¤Ç¤­¤Ê¤¤¤è¤¦¤Ç¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             ¿·¤·¤¤ AIC789x ¥·¥ê¡¼¥º¤Î Adaptec ¥Á¥Ã¥×¤Ï¡¢3.0 ¤Ç¥Ç¥Ó¥å¡¼¤·¤¿ CAM SCSI
             ¥Õ¥ì¡¼¥à¥ï¡¼¥¯¤Ç¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ 2.2-STABLE ¤Î¥Ñ¥Ã¥Á¤Ï
             <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/</ulink> ¤Ë¤¢¤ê¤Þ¤¹¡£
             CAM ¥·¥¹¥Æ¥à¤¬Æþ¤Ã¤Æ¤¤¤ë¹âµ¡Ç½¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤Ï
             <ulink url="http://people.FreeBSD.org/~abial/cam-boot/">http://people.FreeBSD.org/~abial/cam-boot/</ulink> ¤Ë¤¢¤ê¤Þ¤¹¡£
             ¤É¤Á¤é¤Î¾ì¹ç¤Ë¤·¤Æ¤â¡¢ºî¶È¤ò»Ï¤á¤ëÁ°¤Ë <filename>README</filename>
             ¤ò¤ªÆɤߤ¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="internal-plugnplay-modem">
           <para>Æ⢤ΠPlug &amp; Play
             ¥â¥Ç¥à¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢FreeBSD ¤¬¸¡½Ð¤Ç¤­¤Ê¤¤¤è¤¦¤Ç¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             ¥â¥Ç¥à¤Î PnP ID ¤ò ¥·¥ê¥¢¥ë¥É¥é¥¤¥Ð¤Î PnP ID
             ¥ê¥¹¥È¤ËÄɲ乤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£
             Plug &amp; Play ¥µ¥Ý¡¼¥È¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢
             <literal>controller pnp0</literal> ¤ò¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó
             ¥Õ¥¡¥¤¥ë¤ËÉÕ¤±²Ã¤¨¡¢
             ¿·¤·¤¤¥«¡¼¥Í¥ë¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¥«¡¼¥Í¥ë¤Ï¡¢¸¡½Ð¤·¤¿¤¹¤Ù¤Æ¤Î¥Ç¥Ð¥¤¥¹¤Î
             PnP ID ¤òɽ¼¨¤·¤Þ¤¹¡£
             ¥â¥Ç¥à¤ÎÍó¤Ë¤¢¤ë PnP ID ¤ò <filename>/sys/i386/isa/sio.c</filename>
             ¤Î 2777 ¹ÔÌܤ¯¤é¤¤¤Ë¤¢¤ë¥Æ¡¼¥Ö¥ë¤Ë½ñ¤­Æþ¤ì¤Æ¤¯¤À¤µ¤¤¡£
             ¥Æ¡¼¥Ö¥ë¤ò¸«¤Ä¤±¤ë¤Ë¤Ï¡¢¹½Â¤ÂÎ
             <literal>siopnp_ids[]</literal> ¤Îʸ»úÎó <literal>SUP1310</literal>
             ¤òõ¤·¤Þ¤¹¡£
             ¥«¡¼¥Í¥ë¤òºî¤êľ¤·¤¿¤é¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤¦¤¹¤ì¤Ð¡¢¥â¥Ç¥à¤¬¸¡½Ð¤µ¤ì¤ë¤Ï¤º¤Ç¤¹¡£
           </para>
 
           <para>
             µ¯Æ°»þ¤Î¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¤ÎºÝ¤Ë¡¢<literal>pnp</literal>
             ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ PnP ¤ÎÀßÄê¤ò¥Þ¥Ë¥å¥¢¥ë¤Ç¹Ô¤Ê¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ¤½¤Î¾ì¹ç¡¢¥â¥Ç¥à¤ò¸¡½Ð¤µ¤»¤ë¤¿¤á¤Î¥³¥Þ¥ó¥É¤Ï</para>
 
           <programlisting>pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8</programlisting>
 
             <para>¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="serial-console-prompt">
           <para>¥·¥ê¥¢¥ë¥³¥ó¥½¡¼¥ë¤Ç boot: ¥×¥í¥ó¥×¥È¤òɽ¼¨¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤¤¤¤?</para>
         </question>
 
         <answer>
             <orderedlist>
               <listitem>
                 <para>
                   <literal>options COMCONSOLE</literal>
                   ¤ò»ØÄꤷ¤Æ¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   ¤½¤·¤Æ <filename>/boot.config</filename>
                   ¤òºîÀ®¤·¤Æ <option>-P</option> ¤È¤À¤±½ñ¤­Æþ¤ì¤Æ¤¯¤À¤µ¤¤¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>¤½¤Î¸å¡¢¥­¡¼¥Ü¡¼¥É¤ò¥·¥¹¥Æ¥à¤«¤éÈ´¤­¤Þ¤¹¡£</para>
               </listitem>
             </orderedlist>
 
           <para>
             <filename>/usr/src/sys/i386/boot/biosboot/README.serial</filename> ¤Ë¡¢
             ¤³¤ì¤Ë´Ø¤¹¤ë¾ðÊ󤬽ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="micron-3comnic-failure">
           <para>¤Ê¤¼ Micron ¥³¥ó¥Ô¥å¡¼¥¿¤Ç 3Com PCI ¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤¬Æ°¤«¤Ê¤¤¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>
             ÆÃÄê¤Î Micron À½¤Î¥Þ¥¶¡¼¥Ü¡¼¥É¤ÎÃæ¤Ë¤Ï¡¢PCI BIOS ¤¬µ¬³ÊÄ̤ê¤Ë
             ¼ÂÁõ¤µ¤ì¤Æ¤¤¤Ê¤¤¤¿¤á¤Ë FreeBSD ¤Îµ¯Æ°¤Ë¼ºÇÔ¤¹¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
             ¤½¤Î BIOS ¤Ï¡¢PCI ¥Ç¥Ð¥¤¥¹¤ò¤¢¤ë¥¢¥É¥ì¥¹¤ÇÀßÄꤷ¤¿¤ÈÊó¹ð¤¹¤ë¤Ë¤â
             ´Ø¤ï¤é¤º¡¢¼ÂºÝ¤Ë¤Ï¤½¤¦¤·¤Æ¤¤¤Ê¤¤¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¤³¤ÎÌäÂê¤ò²óÈò¤¹¤ë¤Ë¤Ï¡¢BIOS ¤Î
             <quote>Plug and Play Operating System</quote>
             ¤ò̵¸ú¤ËÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£¤Þ¤¿¡¢¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï
             <ulink url="http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron">http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron</ulink>
             ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="smp-support">
           <para>Âоη¿¥Þ¥ë¥Á¥×¥í¥»¥·¥ó¥° (SMP) ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>SMP ¤Ï¡¢3.0-STABLE ¤È¤½¤ì°Ê¹ß¤Î¥ê¥ê¡¼¥¹¤Ç¤Î¤ß¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             <emphasis>GENERIC</emphasis> ¥«¡¼¥Í¥ë¤Ç¤Ï SMP ¤ÏÍ­¸ú²½¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¤Î¤Ç¡¢
             SMP ¤òÍ­¸ú²½¤¹¤ë¤Ë¤Ï¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             <filename>/sys/i386/conf/LINT</filename> ¤ò¸«¤Æ¡¢
             ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤Ë¤É¤Î¥ª¥×¥·¥ç¥ó¤òÄɲ乤ì¤ÐÎɤ¤¤Î¤«³Î¤«¤á¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="asusk7v-boot-failure">
           <para>ASUS K7V ¥Þ¥¶¡¼¥Ü¡¼¥É¤Î¥·¥¹¥Æ¥à¤Ç¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤ò»È¤¦¤È¡¢
             ¥·¥¹¥Æ¥à¤¬¥Ï¥ó¥°¥¢¥Ã¥×¤·¤Þ¤¹¡£
             Âбþºö¤Ï¤¢¤ê¤Þ¤»¤ó¤«?
           </para>
         </question>
 
         <answer>
           <para>BIOS ¥»¥Ã¥È¥¢¥Ã¥×¤Ç
             <quote>µ¯Æ°»þ¤Î¥¦¥£¥ë¥¹Êݸǽ</quote> ¤ò̵¸ú²½¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
     </qandaset>
   </chapter>
 
   <chapter id="troubleshoot">
     <title>¥È¥é¥Ö¥ë¥·¥å¡¼¥Æ¥£¥ó¥°</title>
 
     <para>
       <emphasis>Ìõ:
         &a.jp.yoshiaki;¡¢
         1997 ǯ 11 ·î 10 Æü</emphasis>
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="awre">
           <para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ËÉÔÎÉ¥Ö¥í¥Ã¥¯¤¬¤¢¤ê¤Þ¤¹!</para>
         </question>
 
         <answer>
           <para>
             SCSI ¥Ç¥£¥¹¥¯¤Î¾ì¹ç¤Ï¼«Æ°Åª¤ËºÆ¥Þ¥Ã¥×¤¹¤ëµ¡Ç½¤¬¤¢¤ë¤Ï¤º¤Ç¤¹¡£
             ¤·¤«¤·¡¢Íý²ò¤·Æñ¤¤Íýͳ¤«¤é¿¤¯¤Î¥É¥é¥¤¥Ö¤¬¤³¤Îµ¡Ç½¤¬Ìµ¸ú²½
             ¤µ¤ì¤Æ½Ð²Ù¤µ¤ì¤Æ¤¤¤Þ¤¹¡Ä¡£
           </para>
 
           <para>
             ¤³¤ì¤òÍ­¸ú²½¤¹¤ë¤Ë¤Ï¡¢
             ºÇ½é¤Î¥Ç¥Ð¥¤¥¹¤Î¥â¡¼¥É¥Ú¡¼¥¸¤òÊѹ¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤Ï¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë¤³¤È¤Ç¡¢FreeBSD
             ¾å¤Ç¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹
             (<username>root</username> ¸¢¸Â¤Ç¹Ô¤Ê¤¤¤Þ¤¹)¡£
           </para>
 
          <screen>&prompt.root; <userinput>scsi -f /dev/rsd0c -m 1 -e -P 3</userinput></screen>
 
           <para>
             ¤½¤·¤Æ¡¢<acronym>AWRE</acronym> ¤È <acronym>ARRE</acronym>
             ¤ÎÃͤò 0 ¤«¤é 1 ¤ØÊѹ¹¤·¤Þ¤¹
           </para>
 
           <screen>AWRE (Auto Write Reallocation Enbld):  1
 ARRE (Auto Read Reallocation Enbld):  1</screen>
 
           <para>
             °Ê²¼¤Ï¡¢<ulink url="mailto:tedm@toybox.placo.com">Ted
               Mittelstaedt »á</ulink>¤«¤é´ó¤»¤é¤ì¤¿¤â¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             IDE ¥É¥é¥¤¥Ö¤Î¾ì¹ç¤ÏÄ̾ÉÔÎÉ¥Ö¥í¥Ã¥¯¤ÏÀøºßŪ¤Ê¾ã³²¤ÎÃû¸õ¤Ç¤¹¡£
             ºÇ¶á¤Î IDE ¥É¥é¥¤¥Ö¤Ï¡¢ÆâÉô¤ÎÉÔÎÉ¥Ö¥í¥Ã¥¯ºÆ¥Þ¥Ã¥Ô¥ó¥°µ¡Ç½¤òÍ­¸ú¤Ë¤·¤¿¾õÂÖ¤Ç
             ½Ð²Ù¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤Þ¤¿¡¢º£Æü¤Î IDE ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥á¡¼¥«¤Ï¡¢
             ½Ð²Ù°Ê¹ß¤ËÉÔÎÉ¥Ö¥í¥Ã¥¯¤¬È¯À¸¤¹¤ë¤³¤È¤Ë´Ø¤·¤ÆÊݾڤòÄ󶡤·¤Æ¤¤¤Æ¡¢
             ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Î¤¢¤ë¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ò¸ò´¹¤¹¤ë¥µ¡¼¥Ó¥¹¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¤â¤·¡¢ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Î¤¢¤ë IDE ¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤òÉüµì¤·¤è¤¦¤È»×¤¦¤Ê¤é¡¢
             IDE ¥É¥é¥¤¥Ö¥á¡¼¥«¤¬Ä󶡤¹¤ë IDE ¿ÇÃÇ¥×¥í¥°¥é¥à¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤Æ¡¢
             ¤½¤Î¥É¥é¥¤¥Ö¤Ë»È¤Ã¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£¤³¤Î¼ï¤Î¥×¥í¥°¥é¥à¤ÏÂçÄñ¡¢
             ¥É¥é¥¤¥Ö¤ÎÀ©¸æÉôʬ¤ËÂФ·¤ÆÉÔÎÉ¥Ö¥í¥Ã¥¯¤òºÆÁöºº¤·¡¢
             ÉÔÎÉ¥Ö¥í¥Ã¥¯¤ò»ÈÍÑÉÔǽ¤Ë¤¹¤ë¤è¤¦¤Ë¥»¥Ã¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ESDI¡¢RLL ¤ª¤è¤Ó MFM ¥É¥é¥¤¥Ö¤Î¾ì¹ç¡¢
             ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Ï¥É¥é¥¤¥Ö¤ÎÀµ¾ï¤ÊÉôʬ¤Ç¤¢¤ê¡¢
             °ìÈÌŪ¤Ë¸À¤Ã¤Æ¾ã³²¤òɽ¤¹¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             PC ¤Ç¤Ï¡¢¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¥³¥ó¥È¥í¡¼¥é¥«¡¼¥É¤È
             BIOS ¤¬ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Î»ÈÍÑÉÔǽ²½¤Îºî¶È¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£
             DOS ¤Ê¤É¡¢¥Ç¥£¥¹¥¯¥¢¥¯¥»¥¹¤Ë BIOS
             ¤ò·Ðͳ¤¹¤ë OS ¤Ë¤È¤Ã¤Æ¤ÏÍ­¸ú¤ËƯ¤­¤Þ¤¹¤¬¡¢FreeBSD
             ¤Î¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ð¤Ï BIOS ¤òÍøÍѤ·¤Þ¤»¤ó¡£¤½¤Î¤¿¤á¡¢
             ÂåÂؤȤ·¤Æ bad144 ¤È¤¤¤¦µ¡¹½¤¬Â¸ºß¤·¤Þ¤¹¡£
             bad144 ¤Ï¡¢wd ¥É¥é¥¤¥Ð¤Ç¤À¤± (¤Ä¤Þ¤ê FreeBSD 4.0
             ¤Ç¤Ï¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Ê¤¤)Æ°ºî¤·¡¢SCSI ¥É¥é¥¤¥Ð¤ËÍøÍѤ¹¤ë¤³¤È¤Ï
             <emphasis>¤Ç¤­¤Þ¤»¤ó</emphasis>¡£bad144 ¤Ï¡¢
             ¸¡½Ð¤µ¤ì¤¿ÉÔÎÉ¥»¥¯¥¿¤ò¥¹¥Ú¥·¥ã¥ë¥Õ¥¡¥¤¥ë¤Ëµ­Ï¿¤¹¤ë¤È¤¤¤¦µ¡Ç½¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             bad144 ¤òÍøÍѤ¹¤ë¾å¤Ç¡¢Ãí°Õ¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤ÅÀ¤¬°ì¤Ä¤¢¤ê¤Þ¤¹¡£
             ¤½¤ì¤Ï¡¢ÉÔÎÉ¥Ö¥í¥Ã¥¯¥¹¥Ú¥·¥ã¥ë¥Õ¥¡¥¤¥ë¤Ï¡¢
             ¥Ç¥£¥¹¥¯¤ÎºÇ½ª¥È¥é¥Ã¥¯¤ËÃÖ¤«¤ì¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£
             ¤³¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢¥Ç¥£¥¹¥¯¤ÎÀèƬ¤ÎÉնᡢ
             <filename>/kernel</filename>
             ¥Õ¥¡¥¤¥ë¤¬°ÌÃÖ¤·¤Æ¤¤¤ë¤Ç¤¢¤í¤¦Éôʬ¤ÇȯÀ¸¤·¤¿ÉÔÎÉ¥»¥¯¥¿¤¬µ­Ï¿¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤·¤¿¤¬¤Ã¤Æ¡¢¤³¤Î¥Õ¥¡¥¤¥ë¤Ï BIOS
             ¥³¡¼¥ë¤ò»È¤Ã¤Æ¥«¡¼¥Í¥ë¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤àµ¯Æ°¥×¥í¥°¥é¥à¤¬¡¢
             ¥¢¥¯¥»¥¹²Äǽ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤³¤ì¤Ï¤Ä¤Þ¤ê¡¢bad144 ¤òÍøÍѤ¹¤ë¥Ç¥£¥¹¥¯¤Ï
             1024 ¥·¥ê¥ó¥À¡¢16 ¥Ø¥Ã¥É¡¢63 ¥»¥¯¥¿¤òĶ¤¨¤Æ¤Ï¤Ê¤é¤Ê¤¤¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¡¢
             bad144 ¤òÍøÍѤ·¤¿¥Ç¥£¥¹¥¯¤¬¼Â¼Á 500MB ¤òĶ¤¨¤é¤ì¤Ê¤¤¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             bad144 ¤ò»È¤¦¤Ë¤Ï¡¢FreeBSD ¤Î¥¤¥ó¥¹¥È¡¼¥ë»þ¤Ëɽ¼¨¤µ¤ì¤ë fdisk ²èÌ̤Ç
             <quote>Bad Block</quote> Áöºº¤ò ON ¤ËÀßÄꤹ¤ë¤À¤±¤Ç¤¹¡£
             ¤³¤ì¤Ï¡¢FreeBSD 2.2.7 °Ê¹ß¤Çµ¡Ç½¤·¤Þ¤¹¡£
             ¥Ç¥£¥¹¥¯¤Ï¡¢1024 ¥·¥ê¥ó¥À°ÊÆâ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤Ï»öÁ°¤Ë¾¯¤Ê¤¯¤È¤â 4 »þ´Ö¡¢
             ¥Ç¥£¥¹¥¯¤¬²¹Å٤ˤè¤Ã¤ÆËÄÄ¥¤·¡¢
             ¥È¥é¥Ã¥¯¤Ë¶Ê¤¬¤ê¤¬½Ð¤ë¤Þ¤Ç²óž¤µ¤»¤ë¤³¤È¤ò¤ªÁ¦¤á¤·¤Þ¤¹
             (ÌõÃí: ²¹ÅÙÊѲ½¤ËÂФ¹¤ëËÄÄ¥¤Ë¤è¤Ã¤Æ¡¢
             ¥Ç¥£¥¹¥¯¤¬Èù¾®ÊÑ·Á¤¹¤ë¤³¤È¤Ë¤è¤êȯÀ¸¤¹¤ëÉÔÎÉ¥»¥¯¥¿¤ò³Î¼Â¤Ë¸¡½Ð¤¹¤ë¤¿¤á¤Ç¤¹)¡£
           </para>
 
           <para>
             ÂçÍÆÎ̤ΠESDI ¥É¥é¥¤¥Ö¤Î¤è¤¦¤Ë 1024 ¥·¥ê¥ó¥À¤òĶ¤¨¤ë¥Ç¥£¥¹¥¯¤Î¾ì¹ç¡¢
             DOS ¾å¤Ç¤½¤Î¥Ç¥£¥¹¥¯¤¬ÍøÍѤǤ­¤ë¤è¤¦¡¢
             ESDI ¥³¥ó¥È¥í¡¼¥é¤ÏÆüì¤ÊÊÑ´¹¥â¡¼¥É¤òÍøÍѤ·¤Þ¤¹¡£
             fdisk ¤Î <quote>set geometry</quote> ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ
             <quote>ÊÑ´¹¤µ¤ì¤¿ (translated)</quote>
             ¥¸¥ª¥á¥È¥ê¤ËÀÚÂؤ¨¤ë¤È¡¢wd ¥É¥é¥¤¥Ð¤Ï¤³¤ÎÊÑ´¹¥â¡¼¥É¤ò²ò¼á¤Ç¤­¤Þ¤¹¡£
             ¤½¤ÎºÝ¡¢FreeBSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºîÀ®¤¹¤ë¤Î¤Ë
             <quote>dangerously dedicated</quote>
             ¥â¡¼¥É¤òÍøÍѤ·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
             ¤³¤Î¥â¡¼¥É¤Ï¡¢¤½¤Î¤è¤¦¤Ê¥¸¥ª¥á¥È¥ê¤ò̵»ë¤¹¤ë¤«¤é¤Ç¤¹¡£
             ¤¿¤È¤¨ fdisk ¤¬¥ª¡¼¥Ð¡¼¥é¥¤¥É¤µ¤ì¤¿¥¸¥ª¥á¥È¥ê¾ðÊó¤ò»È¤Ã¤¿¤È¤·¤Æ¤â¡¢
             °ÍÁ³¤È¤·¤Æ¥Ç¥£¥¹¥¯¤Î¿¿¤ÎÂ礭¤µ¤òÊÝ»ý¤·¤Æ¤¤¤ë¤¿¤á¡¢Â礭¤¹¤®¤ë FreeBSD
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºîÀ®¤·¤è¤¦¤È¤·¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£
             ¥Ç¥£¥¹¥¯¥¸¥ª¥á¥È¥ê¾ðÊó¤¬ÊÑ´¹¤µ¤ì¤¿¥¸¥ª¥á¥È¥ê¾ðÊó¤Ë¤«¤ï¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
             ¼êÆ°¤Ç¥Ö¥í¥Ã¥¯¿ô¤òÆþÎϤ·¡¢
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºîÀ®¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ÂçÍÆÎ̤ΠESDI ¥Ç¥£¥¹¥¯¤ò ESDI ¥³¥ó¥È¥í¡¼¥é¤Ç¥»¥Ã¥È¥¢¥Ã¥×¤¹¤ë¤Ë¤Ï¡¢
             ¤Á¤ç¤Ã¤È¤·¤¿¥È¥ê¥Ã¥¯¤ò»È¤¤¤Þ¤¹¡£¤Þ¤º¡¢DOS ¤Î¥Ç¥£¥¹¥¯¤Çµ¯Æ°¤·¤Æ
             ¤½¤Î¥Ç¥£¥¹¥¯¤ò DOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤È¤·¤Æ¥Õ¥©¡¼¥Þ¥Ã¥È¤·¤Þ¤¹¡£
             ¤½¤·¤Æ FreeBSD ¤òµ¯Æ°¤·¡¢¥¤¥ó¥¹¥È¡¼¥é¤Î fdisk ²èÌ̤Ç
             DOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤È¥Ö¥í¥Ã¥¯¿ô¤òÆɤߤȤꡢ¥á¥â¤·¤Æ¤ª¤­¤Þ¤¹¡£
             ¥¸¥ª¥á¥È¥ê¾ðÊó¤ò DOS ¤¬ÍøÍѤ·¤Æ¤¤¤ë¤â¤Î¤ÈƱ°ì¤ËºÆÀßÄꤷ¡¢
             DOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºï½ü¤·¤Æ <quote>cooperative</quote> FreeBSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò
             ÀèÄøµ­Ï¿¤·¤¿¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤ò»È¤Ã¤ÆºîÀ®¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òµ¯Æ°²Äǽ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ËÀßÄꤷ¡¢ÉÔÎÉ¥Ö¥í¥Ã¥¯Áöºº¤ò
             Í­¸ú¤Ë¤·¤Þ¤¹¡£ ¼ÂºÝ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤Ï¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬ºîÀ®¤µ¤ì¤ëÁ°¤Ë
             bad144 ¤¬ºÇ½é¤Ë¼Â¹Ô¤µ¤ì¤Þ¤¹ (Alt-F2 ¤ò²¡¤¹¤³¤È¤Ç¾õ¶·¤ò³Îǧ¤Ç¤­¤Þ¤¹)¡£
             ÉÔÎÉ¥»¥¯¥¿¥Õ¥¡¥¤¥ë¤òºîÀ®Ãæ¤Ë²¿¤é¤«¤Î¾ã³²¤¬È¯À¸¤·¤¿¤Ê¤é¡¢
             ¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¤Æ¡¢¤â¤¦°ìÅٺǽ餫¤é¤ä¤êľ¤·¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¤ª¤½¤é¤¯¥Ç¥£¥¹¥¯¥¸¥ª¥á¥È¥ê¾ðÊó¤ÎÀßÄê¤òÂ礭¤¯¤·¤¹¤®¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦
             (¤ä¤êľ¤·¤Ï¡¢DOS ¤Ë¤è¤ë¥Õ¥©¡¼¥Þ¥Ã¥È¤È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó³ÎÊݤò´Þ¤ß¤Þ¤¹)¡£
           </para>
 
           <para>
             ¤â¤·¡¢ÉÔÎÉ¥Ö¥í¥Ã¥¯¤ÎºÆ¥Þ¥Ã¥Ô¥ó¥°¤òÍ­¸ú¤Ë¤·¤Æ¤¤¤ÆÉÔÎÉ¥Ö¥í¥Ã¥¯¤¬¸«ÉÕ¤«¤Ã¤¿¤é¡¢
             ¥É¥é¥¤¥Ö¤Î¸ò´¹¤ò¹Í¤¨¤Æ¤¯¤À¤µ¤¤¡£ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Ï¡¢»þ´Ö¤È¤È¤â¤Ë°­²½¤¹¤ë¤«¤é¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bustek742a-eisa-scsi">
           <para>Bustek 742a EISA SCSI ¤¬Ç§¼±¤µ¤ì¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             ¤³¤Î¾ðÊó¤Ï 742a ¤Î¤¿¤á¤Î¤â¤Î¤Ç¤¹¤¬¡¢Â¾¤Î Buslogic ¥«¡¼¥É¤Ë¤Ä¤¤¤Æ¤â
             ƱÍͤΤ³¤È¤¬¸À¤¨¤Þ¤¹¡£(Bustek = Buslogic)
           </para>
 
           <para>
             742a ¥«¡¼¥É¤Ë¤ÏÂ礭¤¯¤ï¤±¤Æ 2 ¤Ä¤Î¡Ö¥Ð¡¼¥¸¥ç¥ó¡×¤¬Â¸ºß¤·¤Þ¤¹¡£
             ¥Ï¡¼¥É¥¦¥§¥¢¥ê¥Ó¥¸¥ç¥ó¤Î A-G ¤È H °Ê¹ß¤Ç¤¹¡£¥ê¥Ó¥¸¥ç¥ó¤Î
             ʸ»ú¤Ï¥«¡¼¥É¤Î¶ù¤Ë¤¢¤ë¥¢¥»¥ó¥Ö¥êÈÖ¹æ¤Î¸å¤í¤Ë¤¢¤ê¤Þ¤¹¡£
             742a ¤ÏÆó¤Ä¤Î ROM ¥Á¥Ã¥×¤ò»ý¤Ã¤Æ¤ª¤ê¡¢°ì¤Ä¤Ï BIOS ¥Á¥Ã¥×¤Ç
             ¤â¤¦°ì¤Ä¤Ï¥Õ¥¡¡¼¥à¥¦¥§¥¢¥Á¥Ã¥×¤Ç¤¹¡£FreeBSD ¤Ï¤¢¤Ê¤¿¤Î
             »ý¤Ã¤Æ¤¤¤ë¤â¤Î¤¬¤É¤Î BIOS ¥Ð¡¼¥¸¥ç¥ó¤«¤ÏÌäÂꤢ¤ê¤Þ¤»¤ó¤¬¡¢
             ¥Õ¥¡¡¼¥à¥¦¥§¥¢¥Ð¡¼¥¸¥ç¥ó¤Ë¤Ä¤¤¤Æ¤ÏÌäÂê¤È¤Ê¤ê¤Þ¤¹¡£
             Buslogic ¤Îµ»½Ñ¥µ¥Ý¡¼¥ÈÉôÌç¤ËÏ¢Íí¤¹¤ì¤Ð¡¢¥¢¥Ã¥×¥°¥ì¡¼¥ÉÈǤÎ
             ROM ¤òÁ÷¤Ã¤Æ¤¯¤ì¤ë¤³¤È¤Ç¤·¤ç¤¦¡£BIOS ¥Á¥Ã¥×¤È
             ¥Õ¥¡¡¼¥à¥¦¥§¥¢¥Á¥Ã¥×¤Ï¥Ú¥¢¤Ç½Ð²Ù¤µ¤ì¤Þ¤¹¡£
             ¥¢¥À¥×¥¿¥«¡¼¥É¤Î¥Ï¡¼¥É¥¦¥§¥¢¥ê¥Ó¥¸¥ç¥ó¤Ë¤¢¤ï¤»¤¿
             ºÇ¤â¿·¤·¤¤¥Õ¥¡¡¼¥à¥¦¥§¥¢ ROM ¤ò»ÈÍѤ·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¥ê¥Ó¥¸¥ç¥ó A-G ¤Î¥«¡¼¥É¤Ë¤Ï¡¢2.41/2.21 ¤Þ¤Ç¤Î
             BIOS/¥Õ¥¡¡¼¥à¥¦¥§¥¢¤Î¥»¥Ã¥È¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¥ê¥Ó¥¸¥ç¥ó H °Ê¹ß¤Î¥«¡¼¥É¤Ë¤Ï¡¢ºÇ¿·¤Î¤â¤Î¤Ç¤¢¤ë
             4.70/3.37 ¤Î BIOS/¥Õ¥¡¡¼¥à¥¦¥§¥¢¤Î¥»¥Ã¥È¤ò
             »ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤é¤Î¥Õ¥¡¡¼¥à¥¦¥§¥¢¤Î°ã¤¤¤Ï¡¢
             ¥Õ¥¡¡¼¥à¥¦¥§¥¢ 3.37 ¤¬ ¡Ö¥é¥¦¥ó¥É¥í¥Ó¥óÊý¼°¡×
             ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤È¤³¤í¤«¤é¤­¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             Buslogic ¤Î¥«¡¼¥É¤Ë¤Ï¡¢À½Â¤ÈÖ¹æ¤â¹ï°õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¸Å¤¤
             ¥Ï¡¼¥É¥¦¥§¥¢¥ê¥Ó¥¸¥ç¥ó¤Î¥«¡¼¥É¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢Buslogic ¤Î RMA
             ÉôÌç¤ËÌ䤤¹ç¤ï¤»¤ÆÀ½Â¤ÈÖ¹æ¤òÅÁ¤¨¤ë¤È¡¢¿·¤·¤¤¥Ï¡¼¥É¥¦¥§¥¢¥ê¥Ó¥¸¥ç¥ó¤Î
             ¥«¡¼¥É¤Ë¸ò´¹¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤â¤·¥«¡¼¥É¤¬½½Ê¬¿·¤·¤±¤ì¤Ð¡¢Èà¤é¤Ï
             ¸ò´¹¤Ë±þ¤¸¤Æ¤¯¤ì¤ë¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             FreeBSD 2.1 ¤Ï ¥Õ¥¡¡¼¥à¥¦¥§¥¢¥ê¥Ó¥¸¥ç¥ó 2.21
             °Ê¹ß¤Î¤â¤Î¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤è¤ê¤â¸Å¤¤¥Õ¥¡¡¼¥à¥¦¥§¥¢¥ê¥Ó¥¸¥ç¥ó¤Î¤â¤Î¤Ï¡¢
             Buslogic ¥«¡¼¥É¤È¤·¤ÆÀµ¾ï¤Ëǧ¼±¤µ¤ì¤Þ¤»¤ó¡£
             ¤·¤«¤·¡¢Adaptec 1540 ¤È¤·¤Æǧ¼±¤µ¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ½é´ü¤Î Buslogic ¤Î¥Õ¥¡¡¼¥à¥¦¥§¥¢¤Ï AHA1540 ¡Ö¸ß´¹¡×¥â¡¼¥É¤ò
             »ý¤Ã¤Æ¤¤¤Þ¤¹¡£¤·¤«¤·¡¢EISA ¥«¡¼¥É¤Ë¤È¤Ã¤Æ¤³¤ì¤Ï
             ¤è¤¤¤³¤È¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¸Å¤¤¥Ï¡¼¥É¥¦¥§¥¢¥ê¥Ó¥¸¥ç¥ó¤Î¥«¡¼¥É¤ò»ý¤Ã¤Æ¤¤¤Æ¥Õ¥¡¡¼¥à¥¦¥§¥¢
             2.21 ¤òÆþ¼ê¤¹¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢¥¸¥ã¥ó¥Ñ W1 ¤Î°ÌÃÖ¤ò¥Ç¥Õ¥©¥ë¥È¤Î
             A-B ¤«¤é B-C ¤Ë¹ç¤ï¤»¤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="hpnetserver-scsi-failure">
           <para>HP Netserver ¾å¤Î¥ª¥ó¥Ü¡¼¥É SCSI ¥³¥ó¥È¥í¡¼¥é¤¬Ç§¼±¤µ¤ì¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             ´ðËÜŪ¤Ë¤³¤ì¤Ï´ûÃΤÎÌäÂê¤Ç¤¹¡£HP Netserver ¥Þ¥·¥ó¤Î
             EISA ¥ª¥ó¥Ü¡¼¥É SCSI ¥³¥ó¥È¥í¡¼¥é¤Ï EISA ¤Î¥¹¥í¥Ã¥ÈÈÖ¹æ 11
             ¤òÀêÍ­¤·¤Þ¤¹¤¬¡¢¡ÖËÜÅö¤Î¡×EISA
             ¥¹¥í¥Ã¥È¤Ï¤¹¤Ù¤Æ¤½¤ì¤è¤ê¤âÁ°¤Î¥¢¥É¥ì¥¹¤ËÇÛÃÖ¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¤¹¡£
             »ÄÇ°¤Ê¤¬¤é¡¢
             10 Èְʾå¤Î EISA ¥¹¥í¥Ã¥È¤Ï PCI
             ¤Ë³ä¤êÅö¤Æ¤é¤ì¤¿¥¢¥É¥ì¥¹¶õ´Ö¤È¾×Æͤ·¡¢FreeBSD
             ¤Î¼«Æ°¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¤Ï¡¢
             ¸½¾õ¤Ç¤Ï¤¦¤Þ¤¯¤³¤Î¾õ¶·¤ò½èÍý¤Ç¤­¤Æ¤¤¤Ê¤¤¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¤Ç¤¹¤«¤é¸½»þÅÀ¤Ç¤ÎºÇÎɤÎÊýË¡¤Ï¡¢¥«¡¼¥Í¥ë¥ª¥×¥·¥ç¥ó¤Î
             <literal>EISA_SLOTS</literal> ¤ò 12 ¤ËÊѤ¨¡¢
             ¥¢¥É¥ì¥¹¶õ´Ö¤Î¾×Æͤ¬¤Ê¤¤¤«¤Î
             ¤è¤¦¤Ê¤Õ¤ê¤ò¤µ¤»¤ë¤³¤È¤Ç¤¹ :)
             <ulink url="../handbook/kernelconfig.html">¥«¡¼¥Í¥ë¤ÎºÆ¹½ÃÛ</ulink>¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¤·¤Æ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>
             ¤â¤Á¤í¤ó¡¢¤³¤ì¤Ï¤³¤Î¤è¤¦¤Ê¥Þ¥·¥ó¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëºÝ¤Ë
             ¡ÖÍñ¤¬À褫¡¢
             ·Ü¤¬À褫¡×¤È¤¤¤Ã¤¿ÌäÂê¤òÀ¸¤ß½Ð¤¹¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¤³¤ÎÌäÂê¤ò²óÈò¤¹¤ë¤¿¤á¤Ë¡¢
             <emphasis>¥æ¡¼¥¶¥³¥ó¥Õ¥£¥° (UserConfig)</emphasis>
             ¤ÎÃæ¤Ë¤ÏÆÃÊ̤ʻÅÁȤߤ¬ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤³¤Î¤È¤­ <quote>visual</quote> ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ï»ÈÍѤ»¤º¡¢
             ¥³¥Þ¥ó¥É¥é¥¤¥ó¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£Ã±½ã¤Ë
           </para>
 
           <programlisting>eisa 12
 quit</programlisting>
 
           <para>
             ¤È¥×¥í¥ó¥×¥È¾å¤«¤éÂǤÁ¹þ¤ß¡¢
             ¸å¤ÏÉáÄ̤˥¤¥ó¥¹¥È¡¼¥ë¤ò¹Ô¤Ê¤Ã¤Æ¤¯¤À¤µ¤¤¡£
             ¤È¤Ë¤«¤¯¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë¤ò¹Ô¤Ê¤¦¤³¤È¤ò
             ¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
           </para>
 
           <para>
             ¤¦¤Þ¤¯¤¤¤±¤Ð¡¢¾­Íè¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¤³¤ÎÌäÂ꤬²ò·è¤·¤Æ¤¤¤ë¤³¤È¤Ç¤·¤ç¤¦¡£
           </para>
 
             <note>
               <para>HP Netserver
                 ¤Ç¤Ï<literal>´í¸±³Ð¸ç¤ÎÀìÍѥǥ£¥¹¥¯</literal>¤Ï»ÈÍѤǤ­¤Þ¤»¤ó¡£
                 ¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï <link linkend="dedicate">¤³¤ÎÃí°Õ»ö¹à</link>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cmd640-ide">
           <para>¤³¤Î CMD640 IDE ¥³¥ó¥È¥í¡¼¥é¤Ï¤É¤³¤«¤ª¤«¤·¤¤¤è¤¦¤Ç¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             ¤½¤ì¤Ï²õ¤ì¤Æ¤¤¤ë¤Î¤Ç¤¹¡£Î¾Êý¤Î¥Á¥ã¥ó¥Í¥ë¤òƱ»þ¤ËÀ©¸æ¤Ç¤­¤Ê¤¤¤Î¤Ç¤¹¡£
           </para>
 
           <!-- hrs/2000/03/09 needs &man.wd.4; -->
           <para>
             ¸½ºß¡¢¤³¤Î¥Á¥Ã¥×¤ò»È¤Ã¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤ò¼«Æ°Åª¤Ë¸¡½Ð¤·¤Æ¡¢
             ¤¦¤Þ¤¯Æ°¤«¤¹¤¿¤á¤Î¤·¤¯¤ß¤¬»È¤¨¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¤¯¤ï¤·¤¯¤Ï wd(4) ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             CMD640 IDE ¥³¥ó¥È¥í¡¼¥é¤ò»È¤Ã¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤Ç FreeBSD 2.2.1
             ¤¢¤ë¤¤¤Ï 2.2.2 ¤ò»È¤¤¡¢
             ¤«¤Ä¥»¥«¥ó¥À¥ê¤Î¥Á¥ã¥Í¥ë¤ò»È¤¤¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢
             <literal>options "CMD640"</literal>
             ¤òÍ­¸ú¤Ë¤·¤Æ¥«¡¼¥Í¥ë¤òºî¤êľ¤·¤Æ¤¯¤À¤µ¤¤¡£
             FreeBSD 2.2.5 °Ê¹ß¤Ç¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¤½¤¦¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ed1-timeout">
           <para><literal>ed1: timeout</literal>
             ¤Î¤è¤¦¤Ê¥á¥Ã¥»¡¼¥¸¤¬¤¤¤Ä¤â½Ð¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             ¤¿¤Ö¤ó IRQ ¤Î¾×Æͤ¬¸¶°ø¤Ç¤·¤ç¤¦ (Æó¤Ä¤Î¥Ü¡¼¥É¤¬Æ±¤¸ IRQ
             ¤ò»ÈÍѤ·¤Æ¤¤¤ë¤Ê¤É)¡£FreeBSD 2.0.5R
             °ÊÁ°¤Ï¤³¤ì¤Ë´Ø¤·¤Æ´²Âç¤Ç¡¢
             IRQ ¤Î¾×Æͤ¬¤¢¤Ã¤Æ¤â¥Í¥Ã¥È¥ï¡¼¥¯¥É¥é¥¤¥Ð¤Ïµ¡Ç½¤·¤Æ¤¤¤Þ¤·¤¿¡£
             ¤·¤«¤· 2.0.5R °Ê¹ß¤Ï¤â¤Ï¤ä¡¢IRQ ¤Î¾×Æͤ˴²Âç¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             <option>-c</option> ¥ª¥×¥·¥ç¥ó¤ò¤Ä¤±¤Æµ¯Æ°¤·¡¢
             ed0/de0/... ¤Î¥¨¥ó¥È¥ê¤ò¥Ü¡¼¥É¤ÎÀßÄê¤Ë¹ç¤ï¤»¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤Î BNC
             ¥³¥Í¥¯¥¿ (ÌõÃí: 10BASE-2 ¥¿¥¤¥×¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹)
             ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢
             ¥Ç¥Ð¥¤¥¹¤Î¥¿¥¤¥à¥¢¥¦¥È¤Ï¥¿¡¼¥ß¥Í¡¼¥·¥ç¥ó¤ÎÉÔÎɤˤè¤Ã¤Æ¤âµ¯¤­¤Þ¤¹¡£
             ¤³¤ì¤ò¥Á¥§¥Ã¥¯¤¹¤ë¤Ë¤Ï¥±¡¼¥Ö¥ë¤ò³°¤·¤Æ¥¿¡¼¥ß¥Í¡¼¥¿¤òľÀÜ NIC
             ¤ËÀܳ¤·¤Þ¤¹¡£¤½¤·¤Æ¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤¬¾Ã¤¨¤ë¤«¤É¤¦¤«
             ³Îǧ¤·¤Þ¤¹¡£
           </para>
 
           <para>
             NE2000 ¥³¥ó¥Ñ¥Á¥Ö¥ë¥«¡¼¥É¤Î¤Ê¤«¤Ë¤Ï¡¢
             UTP ¥Ý¡¼¥È¤Î¥ê¥ó¥¯¤¬¤Ê¤«¤Ã¤¿¤ê¥±¡¼¥Ö¥ë¤¬Àܳ¤µ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë
             ¤³¤Î¥¨¥é¡¼¤ò½Ð¤¹¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mount-cd-superblock">
           <para>CDROM ¤ò¥Þ¥¦¥ó¥È¤·¤è¤¦¤È¤¹¤ë¤È
             <literal>Incorrect super block</literal> ¤È¸À¤ï¤ì¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>&man.mount.8;
             ¤Ë¥Þ¥¦¥ó¥È¤·¤¿¤¤¥Ç¥Ð¥¤¥¹¤Î¥¿¥¤¥×¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï &man.mount.8;
             ¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò
             <literal>ufs</literal> ¤È¤ß¤Ê¤·¤Þ¤¹¡£CDROM ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò
             ¥Þ¥¦¥ó¥È¤·¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð <option>-t cd9660</option>
             ¤È &man.mount.8; ¤Ë¥ª¥×¥·¥ç¥ó¤ò¤Ä¤±¤ÆÌÀ¼¨¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤Ï¤â¤Á¤í¤ó
             CDROM ¤¬ ISO 9660 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤¢¤ë¾ì¹ç¤Ç¤¹¡£¤Û¤È¤ó¤É¤Î
             CDROM ¤Ï¤³¤Î·Á¼°¤Ç¤¹¡£1.1R ¤Î FreeBSD ¤Ç¤Ï (ÌõÃí: 2.1.5R¡¢
             2.2R ¤Ç¤âƱÍͤǤ¹) ¼«Æ°Åª¤Ë
             Rock Ridge ³ÈÄ¥ (Ť¤¥Õ¥¡¥¤¥ë̾¤Ø¤ÎÂбþ) ¤ò¤¦¤Þ¤¯²ò¼á¤·¤Þ¤¹¡£
           </para>
 
           <para>
             CDROM ¤Î¥Ç¥Ð¥¤¥¹ <devicename>/dev/cd0c</devicename>
             ¤ò
             <filename>/mnt</filename>
             ¤Ë¥Þ¥¦¥ó¥È¤·¤¿¤¤¾ì¹ç¤ÎÎã¤Ç¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0c /mnt</userinput></screen>
 
           <para>¥Ç¥Ð¥¤¥¹¤Î̾Á°¤Ï¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ë¤è¤Ã¤Æ¤ÏÊ̤Î̾Á°¤Ë¤Ê¤Ã¤Æ¤¤¤ë
             ¤«¤â¤·¤ì¤Ê¤¤¤Î¤ÇÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤
             (<devicename>/dev/cd0c</devicename> ¤Ï¤³¤Î¾ì¹ç¤ÎÎã¤Ç¤¹)¡£
             ¥ª¥×¥·¥ç¥ó <option>-t cd9660</option> ¤Ë¤è¤Ã¤Æ
             <command>mount_cd9660</command>
             ¥³¥Þ¥ó¥É¤¬¼Â¹Ô¤µ¤ì¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤³¤Î¤¿¤áÎã¤Ï¼¡¤Î¤è¤¦¤Ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>mount_cd9660 /dev/cd0c /mnt</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cdrom-not-configured">
           <para>CDROM ¤ò¥Þ¥¦¥ó¥È¤·¤è¤¦¤È¤¹¤ë¤È
             <literal>Device not configured</literal>
             ¤È¸À¤ï¤ì¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Ï °ìÈÌŪ¤Ë CDROM ¥É¥é¥¤¥Ö¤ÎÃæ¤Ë CDROM ¤¬Æþ¤Ã¤Æ¤¤¤Ê¤¤¤«¡¢
             ¥É¥é¥¤¥Ö¤¬¥Ð¥¹¾å¤Ë¸«¤¨¤Ê¤¤¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£¥É¥é¥¤¥Ö¤Ë CDROM
             ¤òÆþ¤ì¤ë¤«¡¢IDE (ATAPI) ¤Ç¤¢¤ì¤Ð master/slave
             ¤Î¾õÂÖ¤ò¥Á¥§¥Ã¥¯¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤Þ¤¿¡¢CDROM ¥É¥é¥¤¥Ö¤Ë CDROM
             ¤òÆþ¤ì¤Æ¤«¤éǧ¼±¤¹¤ë¤Þ¤Ç¤Ë¤Ï¿ôÉ䫤«¤ê¤Þ¤¹¤Î¤Ç¡¢
             ¾¯¤·ÂԤäƤߤƤ¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             SCSI CDROM ¤Ç¤Ï¥Ð¥¹¥ê¥»¥Ã¥È¤Ø¤Î±þÅú»þ´Ö¤¬ÃÙ¤¤¤¿¤á¤Ë¡¢
             ¼ºÇÔ¤¹¤ë¤³¤È¤¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             SCSI CDROM ¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
             ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤Î¹Ô¤ò²Ã¤¨¤Æ
             ºÆ¥³¥ó¥Ñ¥¤¥ë¤·¤Æ»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>options "SCSI_DELAY=15"</programlisting>
 
             <note>
               <title>ÌõÃí</title>
               <para>
                 ¸½ºß¤Î GENERIC ¥«¡¼¥Í¥ë¤Ç¤Ï¾å¤ÎÀßÄê¤Ï¥Ç¥Õ¥©¥ë¥È¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
                 ÌäÂ꤬¤¢¤ë¾ì¹ç¤Ï <literal>SCSI_DELAY</literal>
                 ¤Î¿ôÃͤòÁý¤ä¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cdrom-unicode-filenames">
           <para>CDROM ¤ò¥Þ¥¦¥ó¥È¤¹¤ë¤È¡¢¥Õ¥¡¥¤¥ë̾Ãæ¤Î±Ñ¿ô»ú°Ê³°¤Î
             ʸ»ú¤¬¡¢<quote>?</quote> ¤Èɽ¼¨¤µ¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>¤â¤Ã¤È¤â¤¢¤ê¤½¤¦¤Ê¤Î¤Ï¡¢¤½¤Î CDROM ¤¬
             <quote>Joliet</quote> ³ÈÄ¥¤òÍøÍѤ·¤Æ¥Õ¥¡¥¤¥ë¤ª¤è¤Ó
             ¥Ç¥£¥ì¥¯¥È¥ê¤Ë´Ø¤¹¤ë¾ðÊó¤òÊݸ¤·¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£¤³¤Î³ÈÄ¥¤Ï¡¢
             ¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë̾¤ò Unicode ¤Î 2 ¥Ð¥¤¥Èʸ»ú¤ÇÊݸ¤¹¤ë¤è¤¦¤Ë
             µ¬Äꤷ¤Æ¤¤¤Þ¤¹¡£¸½ºß¡¢FreeBSD ¥«¡¼¥Í¥ë¤ËÈÆÍÑŪ¤Ê Unicode
             ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤òƳÆþ¤¹¤ëºî¶È¤¬¹Ô¤ï¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢
             ¤Þ¤À´°Î»¤·¤Æ¤¤¤Þ¤»¤ó¡£¤·¤¿¤¬¤Ã¤Æ¡¢CD9660
             ¥É¥é¥¤¥Ð¤Ï¥Õ¥¡¥¤¥ë̾¤Îʸ»ú¤ò²òÆɤǤ­¤Þ¤»¤ó¡£</para>
 
           <para>°ì»þŪ¤Ê²ò·èºö¤È¤·¤Æ¡¢FreeBSD 4.3R °Ê¹ß¤Ç¤Ï¡¢CD9660
             ¥É¥é¥¤¥Ð¤ËÆÃÊ̤ʻųݤ±¤ò»Ü¤·¤Æ¡¢¥æ¡¼¥¶¡¼¤¬¤½¤Î¾ì¤ÇŬÀÚ¤Ê
             ÊÑ´¹É½¤òÆɤ߹þ¤á¤ë¤è¤¦¤Ë¤·¤Þ¤·¤¿¡£°ìÈÌŪ¤Ê¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ë
             Âбþ¤·¤¿¤¤¤¯¤Ä¤«¤Î¥â¥¸¥å¡¼¥ë¤¬
             <filename>sysutils/cd9660_unicode</filename> port
             ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
           <note>
             <title>ÌõÃí</title>
             <para>¤³¤Îµ­½Ò¤Ï¸Å¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£<ulink
               url="../../../en_US.ISO8859-1/books/faq/disks.html#CDROM-UNICODE-FILENAMES">
               ±Ñ¸ìÈǤε­½Ò</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
           </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="printer-slow">
           <para>»ä¤Î¥×¥ê¥ó¥¿¤Ï¤È¤Æ¤Ä¤â¤Ê¤¯ÃÙ¤¤¤Î¤Ç¤¹¡£
             ¤É¤¦¤·¤¿¤é¤è¤¤¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>
             ¥Ñ¥é¥ì¥ë¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ç¡¢ÌäÂê¤Ï¤È¤ó¤Ç¤â¤Ê¤¯ÃÙ¤¤¤À¤±¤Ç¤¢¤ë¤Ê¤é¡¢
             ¥×¥ê¥ó¥¿¥Ü¡¼¥È¤ò <quote>polled</quote>
             ¥â¡¼¥É¤ËÀßÄꤷ¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <screen>&prompt.root; <userinput>lptcontrol -p</userinput></screen>
 
           <para>
             HP ¤Î¿·¤·¤¤¥×¥ê¥ó¥¿¤Ë¤Ï¡¢
             ³ä¤ê¹þ¤ß¥â¡¼¥É¤Ç»È¤¨¤Ê¤¤¤â¤Î¤¬¤¢¤ë¤è¤¦¤Ç¤¹
             (´°Á´¤Ë¤ï¤«¤Ã¤¿¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬)¡£
             ¥¿¥¤¥ß¥ó¥°¤ÎÌäÂê¤Î¤è¤¦¤Ë»×¤ï¤ì¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="signal11">
           <para>¤ï¤¿¤·¤Î¥×¥í¥°¥é¥à¤Ï»þ¡¹
             <literal>Signal 11</literal>
             ¤Î¥¨¥é¡¼¤Ç»ß¤Þ¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>Signal 11 ¥¨¥é¡¼¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬
             µö²Ä¤òÍ¿¤¨¤Æ¤¤¤Ê¤¤¥á¥â¥ê¤Ë¥¢¥¯¥»¥¹¤·¤è¤¦¤È¤·¤¿¤È¤­¤ËȯÀ¸¤·¤Þ¤¹¡£
             ¤³¤Î¤è¤¦¤Ê¤³¤È¤¬¥é¥ó¥À¥à¤Ê´Ö³Ö¤Çµ¯¤Ã¤Æ¤¤¤ë¤è¤¦¤Ê¤é¡¢
             Ãí°Õ¿¼¤¯Ä´ºº¤·¤Æ¤¤¤Ã¤¿Êý¤¬Îɤ¤¤Ç¤¹¡£</para>
 
           <para>¤³¤Î¼ê¤ÎÌäÂê¤Ï¤¿¤¤¤Æ¤¤¤Î¾ì¹ç¡¢°Ê²¼¤Î¤É¤Á¤é¤«¤Ç¤¹¡£</para>
 
           <orderedlist>
             <listitem>
               <para>¤½¤ÎÌäÂ꤬ÆÃÄê¤Î¡¢
                 ¤¢¤Ê¤¿¤¬¼«Ê¬¤Ç³«È¯¤·¤¿¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ç¤Î¤ßµ¯¤Ã¤Æ¤¤¤ë¤Ê¤é¡¢
                 ¤¢¤Ê¤¿¤Î¥³¡¼¥É¤Ë¥Ð¥°¤¬¤¢¤ë¤Î¤Ç¤·¤ç¤¦¡£</para>
             </listitem>
 
             <listitem>
               <para>¤½¤ì¤¬ FreeBSD ¤Î¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î°ìÉô¤È´ØÏ¢¤¹¤ëÌäÂê¤Ê¤é¡¢
                 ¥³¡¼¥É¤Ë¥Ð¥°¤¬¤¢¤ë¤È¤¤¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
                 ¤·¤«¤·¤Û¤È¤ó¤É¤Î¾ì¹ç¡¢
                 ÉáÄ̤ΠFAQ ¤ÎÆɼԤ¬¤½¤Î¤è¤¦¤Ê¥³¡¼¥É¤ò»È¤¦¤è¤¦¤Ë¤Ê¤ë¤º¤Ã¤ÈÁ°¤Ë¡¢
                 ¤½¤¦¤¤¤Ã¤¿ÌäÂê¤Ïȯ¸«¤µ¤ì¡¢½¤Àµ¤µ¤ì¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹
                 (¤½¤ì¤¬ -current ¤ÎÌòÌܤʤΤǤ¹¤«¤é)¡£</para>
             </listitem>
           </orderedlist>
 
           <para>¤½¤ì¤¬ FreeBSD ¤Î¥Ð¥°¤Ç¤Ï¡Ö¤Ê¤¤¡×¤È¤¤¤¦·èÄêŪ¤Ê¥±¡¼¥¹¤È¤·¤Æ¡¢
             ¤½¤ÎÌäÂê¤ÎȯÀ¸¤¬¥×¥í¥°¥é¥à¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤¤¤ë¤È¤­¤Ç¤¢¤ê¡¢
             ¥³¥ó¥Ñ¥¤¥ëËè¤ËËè²ó¡¢¥³¥ó¥Ñ¥¤¥é¤ÎµóÆ°¤¬ÊѤë¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>¤¿¤È¤¨¤Ð¡¢¤¢¤Ê¤¿¤¬ <quote>make buildworld</quote> ¤ò¼Â¹Ô¤·¤Æ¤¤¤Æ¡¢
             ¥³¥ó¥Ñ¥¤¥é¤¬ ls.c ¤«¤é ls.o ¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤è¤¦¤È¤·¤¿¤È¤­¤Ë
             ¥³¥ó¥Ñ¥¤¥ë¤Ë¼ºÇÔ¤·¤¿¤È¤·¤Þ¤¹¡£¤â¤¦°ìÅÙ <quote>make buildworld</quote>
             ¤ò¼Â¹Ô¤·¤¿¤È¤­¤Ë¡¢¤Þ¤Ã¤¿¤¯Æ±¤¸¾ì½ê¤Ç¥³¥ó¥Ñ¥¤¥ë¤¬¼ºÇÔ¤·¤¿¤Î¤Ê¤é¡¢
             ¤½¤ì¤Ï build ¤¬²õ¤ì¤Æ¤¤¤ë (ÌõÃí: ¤Ä¤Þ¤ê¥½¡¼¥¹¤Ë¥Ð¥°¤¬¤¢¤ë)
             ¤È¸À¤¦¤³¤È¤Ç¤¹ -- ¥½¡¼¥¹¤ò¹¹¿·¤·¤Æ¤ä¤ê¤Ê¤ª¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
             ¤â¤·¥³¥ó¥Ñ¥¤¥ë¤¬Ê̤ξì½ê¤Ç¤·¤¯¤¸¤Ã¤Æ¤¤¤¿¤é¡¢
             ¤½¤ì¤Ï¥Ï¡¼¥É¥¦¥§¥¢¤ÎÌäÂê¤Ç¤¹¡£</para>
 
           <para>¤¢¤Ê¤¿¤Î¤ä¤ë¤Ù¤­»ö¤Ï:</para>
 
           <para>Á°¼Ô¤Î¾ì¹ç¤Ï¡¢
             ¤½¤Î¥×¥í¥°¥é¥à¤Î´Ö°ã¤Ã¤¿¥¢¥É¥ì¥¹¤Ø¥¢¥¯¥»¥¹¤·¤è¤¦¤È¤·¤Æ¤¤¤ëÉôʬ¤ò¡¢
             gdb Åù¤Î¥Ç¥Ð¥Ã¥¬¤Ç¸«¤Ä¤±¤Æ½¤Àµ¤·¤Þ¤¹¡£</para>
 
           <para>¸å¼Ô¤Î¾ì¹ç¤Ï¡¢
             ¥Ï¡¼¥É¥¦¥§¥¢¤ËÌäÂ꤬¤Ê¤¤¤³¤È¤ò³Î¤«¤á¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>¤½¤Î°ìÈÌŪ¤Ê¸¶°ø¤È¤·¤Æ :</para>
 
           <orderedlist>
             <listitem>
               <para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬Ç®¤ò»ý¤Á¤¹¤®¤Æ¤¤¤ë¤«¤âÃΤì¤Þ¤»¤ó:
                 ¥±¡¼¥¹¤Î¥Õ¥¡¥ó¤¬¤Á¤ã¤ó¤ÈÆ°¤¤¤Æ¤¤¤Æ¥Ç¥£¥¹¥¯¤òÎä¤ä¤·¤Æ¤¤¤ë¤«
                 ³Î¤«¤á¤Æ¤¯¤À¤µ¤¤ (¤¿¤Ö¤ó¡¢Â¾¤ÎÉôÉʤâ²áÇ®¤·¤Æ¤¤¤Þ¤¹)¡£</para>
             </listitem>
 
             <listitem>
               <para>CPU ¤¬¥ª¡¼¥Ð¡¼¥Ò¡¼¥È¤·¤Æ¤¤¤Þ¤¹:
                 CPU ¤ò¥ª¡¼¥Ð¡¼¥¯¥í¥Ã¥¯¤·¤Æ¤¤¤Þ¤»¤ó¤«? ¤µ¤â¤Ê¤±¤ì¤Ð
                 CPU ¥Õ¥¡¥ó¤¬»à¤ó¤Ç¤¤¤ë¤Î¤«¤â¤·¤ì¤Þ¤»¤ó¡£
                 ¤¤¤º¤ì¤Ë¤»¤è¡¢¾¯¤Ê¤¯¤È¤âÌäÂê²ò·è¤Î´Ö¤Ç¤Ï
                 ¥Ï¡¼¥É¥¦¥§¥¢¤¬Æ°¤¯¤Ù¤¯»ØÄꤵ¤ì¤¿¾ò·ï¤ÇÆ°¤«¤·¤Æ¤¯¤À¤µ¤¤¡£
                 ¥¯¥í¥Ã¥¯¤Ï¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤ËÌᤷ¤Æ¤¯¤À¤µ¤¤¡£</para>
 
               <para>¤â¤·¤¢¤Ê¤¿¤¬¥¯¥í¥Ã¥¯¥¢¥Ã¥×¤ò¤·¤Æ¤¤¤ë¤Î¤Ê¤é¡¢
                 ÃÙ¤¤¥·¥¹¥Æ¥à¤Ç¤â¡¢¥·¥¹¥Æ¥à¤¬¾Æ¤­ÉÕ¤¤¤Æ
                 Ç㤤´¹¤¨¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¯¤Ê¤ë¤è¤ê¤º¤Ã¤È¥Þ¥·¤À¤È¤¤¤¦¤³¤È¤ò
                 ³Ð¤¨¤Æ¤ª¤¤¤¿Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£
                 Â礭¤¤¥³¥ß¥å¥Ë¥Æ¥£¤Ç¤ÏÆäˡ¢
                 ¤¢¤Ê¤¿¤¬¤½¤ì¤¬°ÂÁ´¤À¤È»×¤Ã¤Æ¤¤¤ë¤«¤É¤¦¤«¤Ï´Ø·¸¤Ê¤¯¡¢
                 ¥ª¡¼¥Ð¡¼¥¯¥í¥Ã¥¯¤·¤¿¥·¥¹¥Æ¥à¤ËȯÀ¸¤·¤¿ÌäÂê¤Ë¤ÏƱ¾ðŪ¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£</para>
             </listitem>
 
             <listitem>
               <para>²ø¤·¤¤¥á¥â¥ê:
                 ¤â¤·Ê£¿ô¤Î SIMM ¤ä DIMM ¤ò»È¤Ã¤Æ¤¤¤ë¤Ê¤é¤½¤ì¤òÁ´ÉôÈ´¤¤¤Æ¤«¤é
                 ³Æ SIMM ¤ä DIMM ¤òÊ̸ĤËÁȤ߹þ¤ó¤À¥·¥¹¥Æ¥à¤òΩ¤Á¾å¤²¤Æ¤ë¤³¤È¤Ç
                 ¤É¤Î DIMM/SIMM ¤¬²ø¤·¤¤¤Î¤«¡¢¤½¤ì¤È¤âÁȹç¤ï¤»¤¬°­¤¤¤Î¤«
                 ¤ÈÌäÂê¤ÎÉý¤¬¶¹¤Þ¤ê¤Þ¤¹¡£</para>
             </listitem>
 
             <listitem>
               <para>³Ú´ÑŪ¤¹¤®¤ë¥Þ¥¶¡¼¥Ü¡¼¥É¤ÎÀßÄê:
                 ¤Û¤È¤ó¤É¤Î¾ì¹ç¤Ëɸ½àÀßÄê¤Ç½½Ê¬¤Ê¥¿¥¤¥ß¥ó¥°¤ò¡¢
                 BIOS ¤ÎÀßÄê¤ä¥Þ¥¶¡¼¥Ü¡¼¥É¾å¤Î¥¸¥ã¥ó¥Ñ¥Ô¥ó¤òÊѤ¨¤ë¤³¤È¤Ç¡¢
                 ¤µ¤Þ¤¶¤Þ¤ËÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤·¤«¤·»þ¤Ë¤Ï RAM ¤Î
                 ¥¢¥¯¥»¥¹¥¦¥§¥¤¥È¤òÄ㤯¤·¤¹¤®¤¿¤ê <quote>RAM Speed: Turbo</quote> ¤ä
                 ¤½¤Î¼ê¤Î BIOS ¤ÎÀßÄê¤Ç¤ª¤«¤·¤ÊµóÆ°¤¬µ¯¤³¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
                 BIOS ¤òɸ½à¤ÎÀßÄê¤ËÌ᤹¤È¤¤¤¦¤Î¤Ï¤¤¤¤¥¢¥¤¥Ç¥£¥¢¤Ç¤¹¤¬¡¢
                 ¤½¤ÎÁ°¤Ë¤¢¤Ê¤¿¤ÎÀßÄê¤ò½ñ¤­Î±¤á¤Æ¤ª¤¤¤¿Êý¤¬¤¤¤¤¤Ç¤·¤ç¤¦¡£</para>
             </listitem>
 
             <listitem>
               <para>¥Þ¥¶¡¼¥Ü¡¼¥É¤Ø¤ÎÅŸ»¤¬°ÂÄꤷ¤Æ¤¤¤Ê¤¤¡£
                 ¤â¤·»È¤Ã¤Æ¤¤¤Ê¤¤ I/O ¥Ü¡¼¥É¤ä¥Ï¡¼¥É¥Ç¥£¥¹¥¯¡¢
                 CDROM Åù¤¬¤¢¤ë¤Ê¤é¡¢°ìö¤½¤ì¤é¤«¤éÅŸ»¥±¡¼¥Ö¥ë¤òÈ´¤­¡¢
                 ÅŸ»¤¬¾®¤µ¤ÊÉé²Ù¤Ê¤é¤Ê¤ó¤È¤«Æ°ºî¤¹¤ë¤«³Îǧ¤·¤Þ¤·¤ç¤¦¡£
                 ¤¢¤ë¤¤¤ÏÊ̤ÎÅŸ»¤ò»î¤·¤Æ¤ß¤Þ¤·¤ç¤¦¡£
                 ¤½¤Î»þ¤Ï¤Ê¤ë¤Ù¤¯¡¢¾¯¤·ÍÆÎ̤ÎÂ礭¤¤¤â¤Î¤Ç»î¤·¤Þ¤·¤ç¤¦
                 (¤¿¤È¤¨¤Ð¡¢º£¤ÎÅŸ»ÍÆÎ̤¬ 250W ¤À¤Ã¤¿¤é 300W
                 ¤Î¤â¤Î¤ò»î¤·¤Þ¤¹)¡£</para>
             </listitem>
           </orderedlist>
 
           <para>SIG11 FAQ (²¼¤Ë¼¨¤·¤Þ¤¹) ¤Ë¤Ï¤³¤ì¤é¤ÎÌäÂê¤Î¤¹¤Ù¤Æ¤¬
             ¾Ü¤·¤¯ÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£Linux ¤Î»ëÅÀ¤Ë´ð¤Å¤¯¤â¤Î¤Ç¤¹¤¬¡¢
             ¤³¤ì¤âÆɤó¤Ç¤ª¤¤¤¿Êý¤¬¤¤¤¤¤Ç¤·¤ç¤¦¡£¤½¤³¤Ç¤Ï¤Þ¤¿¡¢
             ¥á¥â¥ê¤Î¥Æ¥¹¥È¤ò¹Ô¤¦¥½¥Õ¥È¥¦¥§¥¢¤ä¡¢
             ¥Ï¡¼¥É¥¦¥§¥¢¤¬¤Ê¤¼ÌäÂê¤Î¤¢¤ë¥á¥â¥ê¤ò¸«Æ¨¤·¤Æ¤·¤Þ¤¦¤«¤Ë¤Ä¤¤¤Æ¤â
             µÄÏÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
           <para>ºÇ¸å¤Ë¡¢¤³¤ì¤é¤¬¤É¤ì¤â½õ¤±¤Ë¤Ê¤é¤Ê¤«¤Ã¤¿¤é¡¢
             FreeBSD ¤Î¥Ð¥°¤òȯ¸«¤·¤¿²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
             °Ê²¼¤ÎÀâÌÀ¤òÆɤó¤Ç¾ã³²Êó¹ð¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>¾ÜºÙ¤Ê FAQ ¤Ï¡¢<ulink url="http://www.bitwizard.nl/sig11/">
               the SIG11 problem FAQ</ulink> ¤Ë¤¢¤ê¤Þ¤¹¡£</para>
           </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="screen-loses-sync">
           <para>µ¯Æ°¤Î»þ¤Ë²èÌ̤¬¿¿¤Ã°Å¤Ë¤Ê¤Ã¤ÆƱ´ü¤â¼è¤ì¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Ï ATI Mach 64 ¥Ó¥Ç¥ª¥«¡¼¥É¤Î´ûÃΤÎÌäÂê¤Ç¤¹¡£
             ¤³¤ÎÌäÂê¤Ï¥«¡¼¥É¤¬¥¢¥É¥ì¥¹ <literal>2e8</literal> ¤ò»È¤¤¡¢
             4 ÈÖÌܤΥ·¥ê¥¢¥ë¥Ý¡¼¥È¤â¤³¤³¤ò»È¤¦¤È¤¤¤¦¤³¤È¤Ë¤¢¤ê¤Þ¤¹¡£
             &man.sio.4; ¥É¥é¥¤¥Ð¤Î¥Ð¥° (»ÅÍÍ?) ¤Î¤¿¤á¡¢
             4 ÈÖÌܤΥ·¥ê¥¢¥ë¥Ý¡¼¥È¤¬¤Ê¤¯¤Æ¤â¡¢
             Ä̾盧¤Î¥¢¥É¥ì¥¹¤ò»È¤¦ sio3 (4 ÈÖÌܤΥݡ¼¥È¤Ë¤¢¤¿¤ê¤Þ¤¹)
             ¤ò̵¸ú¤Ë¤·¤Æ¤â¡¢¥É¥é¥¤¥Ð¤Ï¤³¤Î¥¢¥É¥ì¥¹¤ò¤µ¤ï¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Ð¥°¤¬½¤Àµ¤µ¤ì¤ë¤Þ¤Ç¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤·¤ÆÂн褷¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
             <orderedlist>
               <listitem>
                 <para>µ¯Æ°¥×¥í¥ó¥×¥È¤¬½Ð¤¿¤é <option>-c</option> ¤ÈÆþÎϤ·¤Þ¤¹
                   (¤³¤ì¤Ë¤è¤ê¥«¡¼¥Í¥ë¤Ï¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥â¡¼¥É¤ËÆþ¤ê¤Þ¤¹)¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   <devicename>sio0</devicename>,
                   <devicename>sio1</devicename>,
                   <devicename>sio2</devicename>,
                   <devicename>sio3</devicename> (¤³¤ì¤é¤¹¤Ù¤Æ) ¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£
                   ¤³¤ì¤Ë¤è¤Ã¤Æ &man.sio.4; ¥É¥é¥¤¥Ð¤ÏÆ°ºî¤·¤Ê¤¯¤Ê¤ê¤Þ¤¹¤¬¡¢ÌäÂê¤Ï¤¢¤ê¤Þ¤»¤ó¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>exit ¤ÈÆþÎϤ·¤Æµ¯Æ°¤ò³¹Ô¤·¤Þ¤¹¡£</para>
               </listitem>
             </orderedlist>
 
           <para>
             ¤â¤·¥·¥ê¥¢¥ë¥Ý¡¼¥È¤òÍ­¸ú¤Ë¤·¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð°Ê²¼¤ÎÊѹ¹¤ò¹Ô¤Ê¤Ã¤Æ
             ¿·¤·¤¤¥«¡¼¥Í¥ë¤òºî¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             <filename>/usr/src/sys/i386/isa/sio.c</filename> ¤ÎÃæ¤Ç 1 ¥õ½ê¤¢¤ë
             <literal>0x2e8</literal> ¤È¤¤¤¦Ê¸»úÎó¤òõ¤·¡¢
             ¤³¤Îʸ»úÎó¤È¤½¤Î¼êÁ°¤Ë¤¢¤ë¥³¥ó¥Þ¤òºï½ü¤·¤Þ¤¹
             (¸å¤í¤Î¥³¥ó¥Þ¤Ï»Ä¤·¤Þ¤¹)¡£
             ¸å¤ÏÄ̾ï¤Î¼ê³¤­¤Ë¤·¤¿¤¬¤Ã¤Æ¿·¤·¤¤¥«¡¼¥Í¥ë¤òºî¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ÎÂнè¤ò¹Ô¤Ê¤Ã¤¿¸å¤Ç¤â¤Þ¤À
             X ¥¦¥£¥ó¥É¥¦¥·¥¹¥Æ¥à¤Ï¤¦¤Þ¤¯Æ°¤«¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ¤½¤Î¾ì¹ç¤Ï¡¢
             »ÈÍѤ·¤Æ¤¤¤ë XFree86 ¤¬¤¹¤¯¤Ê¤¯¤È¤â XFree86 3.3.3
             °Ê¹ß¤Ç¤¢¤ë¤³¤È¤ò³Î¤«¤á¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤ì°Ê¹ß¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
             Mach64 ¥«¡¼¥É¤ä¤½¤ì¤é¤Î¥«¡¼¥É¤Î¤¿¤á¤Ë¤Ä¤¯¤é¤ì¤¿
             X ¥µ¡¼¥Ð ¤ÎÁȹþ¤ß¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="reallybigram">
           <para>128MB ¤Î RAM ¤¬¤¢¤ë¤Î¤Ç¤¹¤¬¡¢64MB ¤·¤«Ç§¼±¤·¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤¬¥á¥â¥ê¤Î¥µ¥¤¥º¤ò BIOS ¤«¤é¼èÆÀ¤¹¤ëÊýË¡¤ÎÀ©¸Â¤Ë¤è¤ê¡¢
             KB ñ°Ì¤Ç 16 ¥Ó¥Ã¥Èʬ¤Þ¤Ç¤·¤«¸¡½Ð¤Ç¤­¤Þ¤»¤ó (¤¹¤Ê¤ï¤ÁºÇÂç
             65535KB=64MB ¤Ç¤¹¡£¤³¤ì¤è¤ê¾¯¤Ê¤¤¾ì¹ç¤â¤¢¤ê¤Þ¤¹¡£
             ¤¢¤ë BIOS ¤Î¾ì¹ç¤Ï¥á¥â¥ê¥µ¥¤¥º¤¬ 16MB ¤ËÀ©¸Â¤µ¤ì¤Þ¤¹)¡£
             64MB °Ê¾å¤Î¥á¥â¥ê¤òÀѤó¤Ç¤¤¤ë¾ì¹ç¡¢
             FreeBSD ¤Ï¤½¤ì¤ò¸¡½Ð¤·¤è¤¦¤È¤·¤Þ¤¹¡£
             ¤·¤«¤·¤½¤Î»î¤ß¤Ï¼ºÇÔ¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤³¤ÎÌäÂê¤ò²óÈò¤¹¤ë¤Ë¤Ï¡¢
             °Ê²¼¤Ë¼¨¤¹¥«¡¼¥Í¥ë¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ´°Á´¤Ê¥á¥â¥ê¾ðÊó¤ò BIOS ¤«¤é¼èÆÀ¤¹¤ëÊýË¡¤â¤¢¤ê¤Þ¤¹¤¬¡¢
             µ¯Æ°¥Ö¥í¥Ã¥¯¤Ë¶õ¤­¤¬Ìµ¤¤¤¿¤á¼ÂÁõ¤Ç¤­¤Þ¤»¤ó¡£
             µ¯Æ°¥Ö¥í¥Ã¥¯¤ÎÌäÂ꤬²ò·è¤µ¤ì¤ì¤Ð¡¢
             ¤¤¤Ä¤«³ÈÄ¥ BIOS µ¡Ç½¤ò»ÈÍѤ·¤Æ´°Á´¤Ê¥á¥â¥ê¾ðÊó¤ò¼èÆÀ¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
             ¤È¤ê¤¢¤¨¤º¸½ºß¤Ï¡¢¥«¡¼¥Í¥ë¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para><literal>options "MAXMEM=<replaceable>n</replaceable>"</literal></para>
 
           <para>
             <replaceable>n</replaceable> ¤Ë¤Ï¡¢
             ¥­¥í¥Ð¥¤¥Èñ°Ì¤Ç¥á¥â¥ê¤ÎÎ̤ò»ØÄꤷ¤Þ¤¹¡£128MB
             ¤Î¾ì¹ç¤Ï¡¢<literal>131072</literal> ¤È¤Ê¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="panic-kmemmap-too-small">
           <para>FreeBSD 2.0 ¤¬
             <literal>kmem_map too small!</literal>
             ¤È¸À¤Ã¤Æ¥Ñ¥Ë¥Ã¥¯¤·¤Þ¤¹¡£</para>
         </question>
 
         <answer>
             <note>
               <para>¥á¥Ã¥»¡¼¥¸¤Ï¡¢<literal>mb_map too small!</literal>
                 ¤Î¾ì¹ç¤â¤¢¤ê¤Þ¤¹¡£
               </para>
             </note>
 
           <para>
             ¤³¤Î¥Ñ¥Ë¥Ã¥¯¤Ï¡¢¥Í¥Ã¥È¥ï¡¼¥¯¥Ð¥Ã¥Õ¥¡ (ÆÃ¤Ë mbuf
             ¥¯¥é¥¹¥¿) ¤Î²¾ÁÛ¥á¥â¥ê¤¬Ìµ¤¯¤Ê¤Ã¤¿¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
             °Ê²¼¤Î¥ª¥×¥·¥ç¥ó¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤ËÄɲä·¤Æ
             mbuf ¥¯¥é¥¹¥¿¤Ë»ÈÍѤǤ­¤ë²¾ÁÛ¥á¥â¥ê¤ÎÎ̤òÁý¤ä¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para><literal>options "NMBCLUSTERS=<replaceable>n</replaceable>"</literal></para>
 
           <para>
             <replaceable>n</replaceable>
             ¤Ë¤Ï¡¢
             Ʊ»þ¤Ë»ÈÍѤ·¤¿¤¤ TCP ¥³¥Í¥¯¥·¥ç¥ó¤Î¿ô¤Ë±þ¤¸¤Æ
             512 ¤«¤é 4096 ¤Þ¤Ç¤Î¿ôÃͤò»ØÄê¤Ç¤­¤Þ¤¹¡£
             ¤È¤ê¤¢¤¨¤º 2048 ¤ò»î¤·¤Æ¤ß¤ë¤Î¤ò¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
             ¤³¤ì¤Ç¥Ñ¥Ë¥Ã¥¯¤Ï´°Á´¤ÎͽËɤǤ­¤ë¤Ï¤º¤Ç¤¹¡£
             mbuf ¥¯¥é¥¹¥¿¤Î³ä¤êÅö¤Æ¡¢»ÈÍѾõ¶·¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             <command>netstat -m</command> ¤ÇÃΤ뤳¤È¤¬¤Ç¤­¤Þ¤¹
             (&man.netstat.1; ¤ò¤´Í÷¤¯¤À¤µ¤¤)¡£
             <literal>NMBCLUSTERS</literal> ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤÏ
             <literal>512 + MAXUSERS * 16</literal> ¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cmap-busy-panic">
           <para>¿·¤·¤¤¥«¡¼¥Í¥ë¤ÇºÆµ¯Æ°¤¹¤ë¤È
             <literal>CMAP busy panic</literal>
             ¤È¤Ê¤Ã¤Æ¥Ñ¥Ë¥Ã¥¯¤òµ¯¤³¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
           </para>
         </question>
 
         <answer>
           <para>
             ¥Õ¥¡¥¤¥ë <filename>/var/db/kvm_*.db</filename>
             ¤Ë¤ª¤¤¤ÆÈϰϳ°¤Î¥Ç¡¼¥¿¤ò¸¡½Ð¤¹¤ë¤¿¤á¤Î¥í¥¸¥Ã¥¯¤Ï¼ºÇÔ¤¹¤ë¤³¤È¤¬¤¢¤ê¡¢
             ¤³¤¦¤·¤¿Ì·½â¤Î¤¢¤ë¥Õ¥¡¥¤¥ë¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¥Ñ¥Ë¥Ã¥¯¤ò°ú¤­µ¯¤³¤¹¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ì¤¬µ¯¤³¤Ã¤¿¤Ê¤é¡¢¥·¥ó¥°¥ë¥æ¡¼¥¶¤ÇºÆµ¯Æ°¤·¤¿¸å¤Ë¡¢
             °Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>rm /var/db/kvm_*.db</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="brkadrint-illegal-host-access">
           <para><literal>ahc0: brkadrint,  Illegal Host Access at seqaddr 0x0</literal>
             ¤È¤¤¤¦¥¨¥é¡¼¤¬½Ð¤Þ¤¹</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Ï Ultrastor SCSI Host Adapter ¤È¾×Æͤ·¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             µ¯Æ°»þ¤Ë kernel configuration ¥á¥Ë¥å¡¼¤ËÆþ¤ê¡¢
             ÌäÂê¤òµ¯¤³¤·¤Æ¤¤¤ë
             <devicename>uha0</devicename>
             ¤ò disable ¤Ë¤·¤Þ¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mail-loopback">
           <para>sendmail ¤¬ <literal>mail loops back to myself</literal>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤ò½Ð¤¹¤Î¤Ç¤¹¤¬¡£</para>
         </question>
 
         <answer>
           <para>
             ¤³¤Î»ö¤Ï¡¢sendmail FAQ ¤Ë¼¡¤Î¤è¤¦¤Ë½ñ¤¤¤Æ¤¢¤ê¤Þ¤¹¡£
           </para>
 
 <literallayout>        * "Local configuration error" ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬½Ð¤Þ¤¹¡£¤¿¤È¤¨¤Ð:
 
         553 relay.domain.net config error: mail loops back to myself
         554 &lt;user@domain.net&gt;... Local configuration error
 
         ¤Î¤è¤¦¤Êʪ¤Ç¤¹¤¬¡¢¤É¤Î¤è¤¦¤Ë¤·¤¿¤é¤³¤ÎÌäÂê¤ò²ò·è¤Ç¤­¤Þ¤¹¤«?
 
         ¤³¤ì¤Ï¡¢¤¿¤È¤¨¤Ð domain.net ¤Î¤è¤¦¤Ê¥É¥á¥¤¥ó°¸¤Æ¤Î¥á¡¼¥ë¤ò MX record ¤Ç
         ÆÃÄê¤Î¥Û¥¹¥È (¤³¤³¤Ç¤Ï relay.domain.net) ¤ËÁ÷¤í¤¦¤È¤·¤¿¤Î¤Ë¡¢
         ¤½¤Î¥Û¥¹¥È¤Ç¤Ï domain.net °¸¤Æ¤Î¥á¡¼¥ë¤ò¼õ¤±¼è¤ì¤ë¤è¤¦¤ÊÀßÄê¤Ë
         ¤Ê¤Ã¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ç¤¹¡£ÀßÄê¤ÎºÝ¤Ë FEATURE(use_cw_file) ¤ò
         »ØÄꤷ¤Æ¤¢¤ë¾ì¹ç¤Ë¤Ï /etc/sendmail.cw ¤ÎÃæ¤Ë domain.net ¤ò
         Äɲ䷤Ƥ¯¤À¤µ¤¤¡£¤â¤·¤¯¤Ï¡¢/etc/sendmail.cf ¤ÎÃæ¤Ë
         "Cw domain.net" ¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
             </literallayout>
 
           <para>
             ¤â¤Ï¤ä¸½ºß¤Î
             <ulink url="ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/sendmail-faq">sendmail FAQ</ulink>
             ¤Ï sendmail release ¤È¤Ï°ì½ï¤Ë¤ÏÊݼ餵¤ì¤Æ¤¤¤Þ¤»¤ó¡£
             ¤·¤«¤·¼¡¤Î¥Í¥Ã¥È¥Ë¥å¡¼¥¹¤ËÄê´üŪ¤ËÅê¹Æ¤µ¤ì¤Æ¤Þ¤¹¡£
             <ulink url="news:comp.mail.sendmail">comp.mail.sendmail</ulink>¡¢
             <ulink url="news:comp.mail.misc">comp.mail.misc</ulink>¡¢
             <ulink url="news:comp.mail.smail">comp.mail.smail</ulink>¡¢
             <ulink url="news:comp.answers">comp.answers</ulink>¡¢
             <ulink url="news:news.answers">news.answers</ulink>¡£
             ¤Þ¤¿¡¢¥á¡¼¥ë·Ðͳ¤Ç¥³¥Ô¡¼¤òÆþ¼ê¤¹¤ë¾ì¹ç¤Ï
             <ulink url="mailto:mail-server@rtfm.mit.edu">mail-server@rtfm.mit.edu</ulink>
             °¸¤Þ¤ÇËÜʸ¤Ë <literal>send usenet/news.answers/mail/sendmail-faq</literal>
             ¤È½ñ¤¤¤ÆÁ÷¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="remote-fullscreen">
           <para>¥ê¥â¡¼¥È¥Þ¥·¥ó¾å¤Î¥Õ¥ë¥¹¥¯¥ê¡¼¥ó¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤¬¤¦¤Þ¤¯Æ°¤«¤Ê¤¤</para>
         </question>
 
         <answer>
           <para>
             ¥ê¥â¡¼¥È¥Þ¥·¥ó¤Î¥¿¡¼¥ß¥Ê¥ë¥¿¥¤¥×¤¬ FreeBSD
             ¤Î¥³¥ó¥½¡¼¥ë¤ÇɬÍפȤµ¤ì¤Æ¤¤¤ë <literal>cons25</literal>
             °Ê³°¤Î¤â¤Î¤Ç¤¹¡£
           </para>
 
           <para>¤³¤ÎÌäÂê¤ò²ò·è¤·¤¦¤ëÊýË¡¤Ï¤¤¤í¤¤¤í¤¢¤ê¤Þ¤¹:</para>
 
             <itemizedlist>
               <listitem>
                 <para>¥ê¥â¡¼¥È¥Þ¥·¥ó¤Ë¥í¥°¥¤¥ó¤·¤¿¸å¡¢
                   ¤½¤Î¥ê¥â¡¼¥È¥Þ¥·¥ó¤¬
                   <literal>ansi</literal> ¤«
                   <literal>sco</literal>
                   ¤Î¥¿¡¼¥ß¥Ê¥ë¥¿¥¤¥×¤òÃΤäƤ¤¤ë¤Ê¤é¡¢
                   shell ÊÑ¿ô¤Î TERM ¤Ë¤½¤ì¤é¤Î¤¤¤º¤ì¤«¤òÀßÄꤷ¤Þ¤¹¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>FreeBSD ¤Î¥³¥ó¥½¡¼¥ë¦¤Ç
                   <application>screen</application>
                   ¤Î¤è¤¦¤Ê VT100 ¥¨¥ß¥å¥ì¡¼¥¿¤ò»ÈÍѤ·¤Þ¤¹¡£
                   <application>screen</application>
                   ¤Ï°ì¤Ä¤Î¥¿¡¼¥ß¥Ê¥ë¤ÎÃæ¤ÇÊ£¿ô¤Î¥»¥Ã¥·¥ç¥ó¤òÊÂÎóÆ°ºî¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤·¡¢
                   ËÜÍè¤Îµ¡Ç½¤âÍ¥¤ì¤Æ¤¤¤Þ¤¹¡£
                   ³Æ¡¹¤Î <application>screen</application> ¤Î¥¦¥£¥ó¥É¥¦¤Ï
                   VT100 ¥¿¡¼¥ß¥Ê¥ë¤Î¤è¤¦¤Ë¿¶¤ëÉñ¤¦¤Î¤Ç¡¢
                   ¥ê¥â¡¼¥È¦¤ÇÀßÄꤵ¤ì¤ë¤Ù¤­ TERM ÊÑ¿ô¤Ï
                   <literal>vt100</literal> ¤È¤Ê¤ê¤Þ¤¹¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>¥ê¥â¡¼¥È¥Þ¥·¥ó¤Î¥¿¡¼¥ß¥Ê¥ë¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë
                   <literal>cons25</literal>
                   ¤Î¥¨¥ó¥È¥ê¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
                   ¤³¤Î¥¤¥ó¥¹¥È¡¼¥ëÊýË¡¤Ï¥ê¥â¡¼¥È¥Þ¥·¥ó¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ë°Í¸¤·¤Þ¤¹¡£
                   ¥ê¥â¡¼¥È¤Î¥·¥¹¥Æ¥à¤Î¥·¥¹¥Æ¥à´ÉÍý¥Þ¥Ë¥å¥¢¥ë¤¬Ìò¤ËΩ¤Ä¤³¤È¤Ç¤·¤ç¤¦¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>FreeBSD ¦¤Ç X ¥µ¡¼¥Ð¤òµ¯Æ°¤·¤Æ¡¢
                   ¥ê¥â¡¼¥È¥Þ¥·¥ó¤Ë <command>xterm</command>
                   ¤ä <command>rxvt</command>
                   ¤Î¤è¤¦¤Ê X ¥Ù¡¼¥¹¤Î¥¿¡¼¥ß¥Ê¥ë¥¨¥ß¥å¥ì¡¼¥¿¤ò»È¤Ã¤Æ¥í¥°¥¤¥ó¤·¤Þ¤¹¡£
                   (ÌõÃí: ÆüËܸ줬ɬÍפʾì¹ç¤Ï <command>kterm</command> Åù¤ò
                   ÍøÍѤ·¤Þ¤¹)
                   ¥ê¥â¡¼¥È¥Û¥¹¥È¤Î TERM ÊÑ¿ô¤Ï
                   <literal>xterm</literal> ¤â¤·¤¯¤Ï
                   <literal>vt100</literal> (ÌõÃí: ¤â¤·¤¯¤Ï <literal>kterm</literal>)
                   ¤ËÀßÄꤷ¤Þ¤¹¡£
                 </para>
               </listitem>
             </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="calcru-negative">
           <para>»ä¤Î¥Þ¥·¥ó¤Ç <literal>calcru: negative time...</literal>
             ¤Èɽ¼¨¤µ¤ì¤ë¤Î¤Ç¤¹¤¬</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Ï¡¢³ä¤ê¹þ¤ß¤Ë´ØÏ¢¤¹¤ë¤µ¤Þ¤¶¤Þ¤ÊÉÔ¶ñ¹ç¤Ë¤è¤Ã¤ÆȯÀ¸¤·¤Þ¤¹¡£
             ¤¢¤ë¤¤¤Ï¡¢¤¢¤ë¥Ç¥Ð¥¤¥¹¤¬¸µ¡¹»ý¤Ã¤Æ¤¤¤ë¥Ð¥°¤¬É½Ì̲½¤·¤¿¤Î¤«¤âÃΤì¤Þ¤»¤ó¡£
             ¤³¤Î¾É¾õ¤òºÆ¸½¤µ¤»¤ë°ì¤Ä¤ÎÊýË¡¤È¤·¤Æ¡¢¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¾å¤Ç¡¢
             TCP/IP ¤ò Â礭¤Ê MTU
             ¤ÇÁö¤é¤»¤ë¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
             ¥°¥é¥Õ¥£¥Ã¥¯¥¢¥¯¥»¥é¥ì¡¼¥¿¤¬¤³¤Î¾É¾õ¤òµ¯¤³¤¹¤³¤È¤¬¤¢¤ê¤Þ¤¹¤¬¡¢
             ¤½¤Î¾ì¹ç¤Ï¤Þ¤º¡¢¥«¡¼¥É¤Î³ä¤ê¹þ¤ßÀßÄê¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤³¤ÎÌäÂê¤ÎÉûºîÍѤȤ·¤Æ¡¢
             ¥×¥í¥»¥¹¤¬ <quote>SIGXCPU exceeded cpu time limit</quote>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤È¤È¤â¤Ë½ªÎ»¤·¤Æ¤·¤Þ¤¦¡¢¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>
             1998 ǯ 11 ·î 29 Æü¤Ë¸ø³«¤µ¤ì¤¿ FreeBSD 3.0 °Ê¹ß¤Ç
             ¤³¤ÎÌäÂ꤬²ò·è¤·¤Ê¤¤¤Ê¤é¡¢¼¡¤Î sysctl ÊÑ¿ô¤ò¥»¥Ã¥È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>sysctl -w kern.timecounter.method=1</userinput></screen>
 
           <para>
             ¤³¤ì¤Ï¡¢¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤Ø¶¯¤¤±Æ¶Á¤òÍ¿¤¨¤Þ¤¹¤¬¡¢
             ÌäÂê¤ÎȯÀ¸¤ËÈæ¤Ù¤ì¤Ð¤ª¤½¤é¤¯µ¤¤Ë¤Ê¤é¤Ê¤¤ÄøÅ٤Ǥ·¤ç¤¦¡£
             ¤â¤·¡¢¤³¤ì¤Ç¤â¤Þ¤ÀÌäÂ꤬»Ä¤ë¤è¤¦¤Ê¤é¡¢
             ¥«¡¼¥Í¥ë¥ª¥×¥·¥ç¥ó¤Î <literal>NTIMECOUNTER</literal>
             ¤òÂ礭¤ÊÃͤËÁý¤ä¤·¤Æ¤¯¤À¤µ¤¤¡£
             <literal>NTIMECOUNTER=20</literal>
             ¤Ë¤Þ¤ÇÁý¤ä¤·¤Æ¤â²ò·è¤·¤Ê¤¤¾ì¹ç¤Ï¡¢
             ·×»þ½èÍý¤Î¿®ÍêÀ­¤¬ÊݤƤʤ¤Äø¤Î³ä¤ê¹þ¤ß¤¬¡¢
             ¤½¤Î¥Þ¥·¥ó¾å¤Çµ¯¤³¤Ã¤Æ¤¤¤ë¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="pcm0-not-found">
           <para><literal>pcm0 not found</literal> ¤È¤¤¤¦É½¼¨¤ò¸«¤¿¤ê
             ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë¤Ï <literal>device pcm0</literal> ¤È
             ½ñ¤¤¤Æ¤¢¤ë¤Î¤Ë¥µ¥¦¥ó¥É¥«¡¼¥É¤¬ <literal>pcm1</literal> ¤È¤·¤Æ
             ȯ¸«¤µ¤ì¤¿¤ê¤·¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>¤³¤ì¤Ï FreeBSD 3.x ¤Ç PCI ¤Î¥µ¥¦¥ó¥É¥«¡¼¥É¤ò»È¤Ã¤Æ¤¤¤ë¤È¤­¤Ë
             ȯÀ¸¤·¤Þ¤¹¡£<literal>pcm0</literal> ¥Ç¥Ð¥¤¥¹¤Ï ISA
             ¤Î¥«¡¼¥ÉÀìÍѤËͽÌ󤵤ì¤Æ¤¤¤ë¤â¤Î¤Ç¤¹¡£¤³¤Î¤¿¤á¡¢
             ¤¢¤Ê¤¿¤¬ PCI ¥«¡¼¥É¤ò»ý¤Ã¤Æ¤¤¤ë¤È¤­¤Ï¤³¤Î¥¨¥é¡¼¤¬É½¼¨¤µ¤ì¡¢
             ¥«¡¼¥É¤Ï <literal>pcm1</literal> ¤È¤·¤Æ¸¡½Ð¤µ¤ì¤Þ¤¹¡£
           </para>
 
             <note>
               <para>¤³¤Î·Ù¹ð¤ò¡¢Ã±¤Ë¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤ÎÅö³º¹Ô¤ò
                 <literal>device pcm1</literal> ¤ËÊѹ¹¤¹¤ë¤³¤È¤Ç
                 ÍÞÀ©¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£¤½¤Î»þ¤Ï <literal>pcm1</literal>
                 ¤¬ ISA ¥«¡¼¥É¤Î¤¿¤á¤ËͽÌ󤵤졢PCI ¤Î¥«¡¼¥É¤Ï
                 <literal>pcm2</literal> ¤È¤·¤Æ
                 (<literal>pcm1 not found</literal> ¤Î·Ù¹ð¤È¤È¤â¤Ë)
                 ¸¡½Ð¤µ¤ì¤Þ¤¹¡£</para>
             </note>
 
           <para>
             PCI ¤Î¥µ¥¦¥ó¥É¥«¡¼¥É¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤Ê¤é¤Ð¡¢°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ
             <literal>snd0</literal> ¥Ç¥Ð¥¤¥¹¤Î¤«¤ï¤ê¤Ë <literal>snd1</literal>
             ¤òºî¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV snd1</userinput></screen>
 
           <para>¤³¤Î¾õ¶·¤Ï FreeBSD 4.x ¤Ç¤ÏÀ¸¤¸¤Þ¤»¤ó¡£Â¿¤¯¤ÎÅØÎϤηë²Ì¤è¤ê
             <emphasis>PnP Ãæ¿´</emphasis>¤Ëºî¤êÂؤ¨¤é¤ì¡¢
             ¸½ºß¡¢<literal>pcm0</literal> ¥Ç¥Ð¥¤¥¹¤Ï ISA
             ¥«¡¼¥ÉÀìÍѤËͽÌ󤵤줿¤â¤Î¤Ç¤Ï¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="pnp-not-found">
           <para>¥×¥é¥°¥¢¥ó¥É¥×¥ì¥¤¤Î¥«¡¼¥É¤¬Ç§¼±¤µ¤ì¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿
             (¤Þ¤¿¤Ï¡¢<literal>unknown</literal> ¤Èǧ¼±¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿)¡£</para>
         </question>
 
         <answer>
           <para>¸½ºß¤Î FreeBSD 4.x ¤Ï¤è¤ê <emphasis>PnP Ãæ¿´</emphasis>¤Ë
             ¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£¤½¤ÎÉûºîÍѤαƶÁ¤Ç¡¢FreeBSD 3.x ¤ÇÆ°¤¤¤Æ¤¤¤¿ PnP ¥Ç¥Ð¥¤¥¹
             (¤¿¤È¤¨¤Ð¥µ¥¦¥ó¥É¥«¡¼¥É¤äÆ⢥â¥Ç¥à) ¤ÎÃæ¤Ë¤Ï¡¢
             Æ°¤«¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤¿¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>¤³¤ÎµóÆ°¤Î¸¶°ø¤Ï Peter Wemm ¤¬ freebsd-questions
             ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ë½ñ¤¤¤¿¡¢°Ê²¼¤Î
             ¡ÖFreeBSD 4.x ¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤·¤¿¤È¤³¤íÆ⢥â¥Ç¥à¤¬
             ¸«¤Ä¤«¤é¤Ê¤¯¤Ê¤Ã¤¿¡×¤È¤¤¤¦¥á¡¼¥ë¤Ç²òÀ⤵¤ì¤Æ¤¤¤Þ¤¹¡£
             (¤ï¤«¤ê¤ä¤¹¤¯¤¹¤ë¤¿¤á¤Ë <literal>[]</literal> Æâ¤Ë
             ¥³¥á¥ó¥È¤ò²Ã¤¨¤Þ¤·¤¿)¡£</para>
 
           <blockquote>
             <para>PnP BIOS ¤Ï¤¢¤é¤«¤¸¤á¡¢[¥â¥Ç¥à¤ò]
               ¥Ý¡¼¥È¶õ´Ö¤Ë¸ºß¤·¤Æ¤¤¤ë¤«¤Î¤è¤¦¤ËÀßÄꤷ¤Þ¤¹¡£
               ¤½¤Î¤¿¤á [3.x ¤Ç¤Ï] ½¾Íè¤Î¼êË¡¤Ë´ð¤Å¤¯ ISA
               ¥Ç¥Ð¥¤¥¹¤Î¸¡º÷¤Ë¤è¤ê¡¢¥â¥Ç¥à¤Î¸ºß¤ò¡Öȯ¸«¡×¤Ç¤­¤Þ¤¹¡£
             </para>
 
             <para>4.0 ¤Î ISA ¥³¡¼¥É¤Ï¡¢¤è¤ê PnP Ãæ¿´¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
               [3.x ¤Ç¤Ï] ISA ¥Ç¥Ð¥¤¥¹¤Î¸¡º÷¤¬¡Ö¤Ï¤°¤ì¤¿¡×¥Ç¥Ð¥¤¥¹¤òȯ¸«¤·¤Æ¡¢
               ¼¡¤Ë PNP ¥Ç¥Ð¥¤¥¹ ID ¤Î¥Þ¥Ã¥Á¤¬¹Ô¤Ê¤ï¤ì¤ë¤³¤È¤Ç¥ê¥½¡¼¥¹¤Î¶¥¹ç¤¬È¯À¸¤·¡¢
               ¥Ç¥Ð¥¤¥¹¤Î¸¡º÷¤Ë¼ºÇÔ¤¹¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
               ¤·¤¿¤¬¤Ã¤Æ¡¢4.0 ¤Î ISA ¥³¡¼¥É¤Ç¤Ï
               Æó½Å¤Ë¸¡º÷¤·¤Ê¤¤¤è¤¦¡¢¥×¥í¥°¥é¥Þ¥Ö¥ë¤Ê¥«¡¼¥É¤ò
               ºÇ½é¤Ë̵¸ú¤Ë¤·¤Æ¤¤¤Þ¤¹¡£
               ¤³¤ì¤Ï¡¢Âбþ¤·¤Æ¤¤¤ë PnP ¥Ï¡¼¥É¥¦¥§¥¢¤Î PnP ID ¤¬¡¢
               ͽ¤á¤ï¤«¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ë¡¢¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
               ¥æ¡¼¥¶¤¬¤³¤ÎµóÆ°¤Ë¤â¤Ã¤È¼ê¤òÆþ¤ì¤é¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤¬
               TODO ¥ê¥¹¥ÈÃæ¤Ë¤¢¤²¤é¤ì¤Æ¤¤¤Þ¤¹¡£</para>
           </blockquote>
 
           <para>3.0 ¤ÇÆ°ºî¤·¤Æ¤¤¤¿¥Ç¥Ð¥¤¥¹¤ò 4.0 ¤Ç¤âÆ°ºî¤¹¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢
             ¤½¤ì¤Î PnP ID ¤òÄ´¤Ù¡¢ISA ¥Ç¥Ð¥¤¥¹¤Î¸¡º÷¤¬
             PnP ¥Ç¥Ð¥¤¥¹¤Î¼±Ê̤˻ȤäƤ¤¤ë¥ê¥¹¥È¤Ë¤½¤ì¤òÄɲ乤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¥Ç¥Ð¥¤¥¹¤Î¸¡º÷¤Ë»È¤ï¤ì¤ë &man.pnpinfo.8; ¤òÍѤ¤¤Æ¡¢
             PnP ID ¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢Æ⢥â¥Ç¥à¤Ë´Ø¤¹¤ë &man.pnpinfo.8; ¤Î½ÐÎϤϡ¢
             °Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>pnpinfo</userinput>
 Checking for Plug-n-Play devices...
 
 Card assigned CSN #1
 Vendor ID PMC2430 (0x3024a341), Serial Number 0xffffffff
 PnP Version 1.0, Vendor Version 0
 Device Description: Pace 56 Voice Internal Plug &amp; Play Modem
 
 Logical Device ID: PMC2430 0x3024a341 #0
         Device supports I/O Range Check
 TAG Start DF
     I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8
         [16-bit addr]
     IRQ: 4  - only one type (true/edge)</screen>
 
           <para>[more TAG lines elided]</para>
 
           <screen>
 TAG End DF
 End Tag
 
 Successfully got 31 resources, 1 logical fdevs
 -- card select # 0x0001
 
 CSN PMC2430 (0x3024a341), Serial Number 0xffffffff
 
 Logical device #0
 IO:  0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8
 IRQ 5 0
 DMA 4 0
 IO range check 0x00 activate 0x01</screen>
 
           <para>ɬÍפʾðÊó¤Ï¡¢½ÐÎϤÎËÁƬ¤Ë¤¢¤ë
             <quote>Vendor ID</quote> ¹Ô¤Ë¤¢¤ê¤Þ¤¹¡£
             ¤«¤Ã¤³¤ÎÃæ¤Î 16 ¿Ê¿ô (Îã¤ÎÃæ¤Ç¤Ï 0x3024a341) ¤¬ PnP ID ¤Ç¡¢
             ľÁ°¤Îʸ»úÎó (PMC2430) ¤Ï¥æ¥Ë¡¼¥¯¤Ê ASCII ID ¤Ç¤¹¡£
             ¤³¤Î¾ðÊó¤Ï¥Õ¥¡¥¤¥ë <filename>/usr/src/sys/isa/sio.c</filename> ¤Ë
             Äɲ乤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>¤Þ¤º¼ºÇÔ¤·¤¿¤È¤­¤ËÈ÷¤¨¤Æ <filename>sio.c</filename> ¤Î
             ¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¼è¤ë¤Ù¤­¤Ç¤¹¡£¾ã³²Êó¹ð¤òÁ÷¤ë¤¿¤á¤Ë½¤Àµ¥Ñ¥Ã¥Á¤ò
             ºî¤ë»þ¤Ë¤âɬÍפˤʤë¤Ç¤·¤ç¤¦ (send-pr ¤·¤è¤¦¤È¤·¤Æ¤¤¤Þ¤¹¤è¤Í?)¡£
             <filename>sio.c</filename> ¤òÊÔ½¸¤·¤Æ°Ê²¼¤Î¹Ô¤òõ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <programlisting>static struct isa_pnp_id sio_ids[] = {</programlisting>
 
           <para>¤½¤·¤Æ¤¢¤Ê¤¿¤Î¥Ç¥Ð¥¤¥¹¤Î¥¨¥ó¥È¥ê¤òÄɲ乤ëÀµ¤·¤¤¾ì½ê¤òõ¤·¤Þ¤¹¡£
             ¥¨¥ó¥È¥ê¤Ï°Ê²¼¤Î¤è¤¦¤Ê·Á¤ò¤·¤Æ¤¤¤Æ¡¢&man.pnpinfo.8; ¤Î
             ½ÐÎϤˤ¢¤ë <emphasis>¥Ç¥Ð¥¤¥¹¤ÎÀâÌÀ</emphasis>¤ÎÁ´Éô
             (¤â¤·¼ý¤Þ¤ì¤Ð) ¤«°ìÉô¤È¤È¤â¤Ë¹Ô¤Î±¦¤ÎÊý¤Î¥³¥á¥ó¥ÈÎΰè¤Ë½ñ¤«¤ì¤Æ¤¤¤ë
             ASCII ¥Ù¥ó¥À ID ¤Ç¥½¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
           <programlisting>{0x0f804f3f, NULL},     /* OZO800f - Zoom 2812 (56k Modem) */
 {0x39804f3f, NULL},     /* OZO8039 - Zoom 56k flex */
 {0x3024a341, NULL},     /* PMC2430 - Pace 56 Voice Internal Modem */
 {0x1000eb49, NULL},     /* ROK0010 - Rockwell ? */
 {0x5002734a, NULL},     /* RSS0250 - 5614Jx3(G) Internal Modem */</programlisting>
 
           <para>¤¢¤Ê¤¿¤Î¥Ç¥Ð¥¤¥¹¤Î16¿Ê¿ô¤Î¥Ù¥ó¥À ID ¤òÀµ¤·¤¤¾ì½ê¤Ë
             Äɲä·¡¢¥Õ¥¡¥¤¥ë¤ò¥»¡¼¥Ö¤·¤Æ¥«¡¼¥Í¥ë¤òºî¤êľ¤·¤ÆºÆµ¯Æ°¤·¤Þ¤¹¡£
             ¤¢¤Ê¤¿¤Î¥Ç¥Ð¥¤¥¹¤Ï FreeBSD 3.x ¤Î»þ¤ÈƱ¤¸¤è¤¦¤Ë
             <literal>sio</literal> ¤È¤·¤Æ¸«¤Ä¤«¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nlist-failed">
           <para><command>top</command> ¤ä <command>systat</command> ¤Î
             ¼Â¹ÔÃæ¤Ë <errorname>nlist failed</errorname> ¤È¤¤¤¦
             ¥¨¥é¡¼¤¬¤Ç¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>¤³¤Î¥¨¥é¡¼¤Ï¡¢
             ¼Â¹Ô¤·¤è¤¦¤È¤·¤¿¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤¬
             ¤¢¤ë¥«¡¼¥Í¥ë¥·¥ó¥Ü¥ë¤ò¸¡º÷¤·¤¿·ë²Ì¡¢
             ²¿¤é¤«¤ÎÍýͳ¤Ç¤½¤Î¸¡º÷¤Ë¼ºÇÔ¤·¤¿¡¢¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤Ï¡¢°Ê²¼¤Ë¼¨¤¹¤¤¤º¤ì¤«¤ÎÍýͳ¤Ë¤è¤ë¤â¤Î¤Ç¤¹¡£</para>
 
           <itemizedlist>
             <listitem>
               <para>¥«¡¼¥Í¥ë¤È¥æ¡¼¥¶¥é¥ó¥É¤¬Æ±´ü¤·¤Æ¤¤¤Ê¤¤ (¤Ä¤Þ¤ê
                 ¥«¡¼¥Í¥ë¤Ï¿·¤·¤¤¤â¤Î¤ò¹½ÃÛ¤·¤¿¤¬¡¢
                 <maketarget>installworld</maketarget> ¤Ï¹Ô¤Ê¤Ã¤Æ¤¤¤Ê¤¤¡£
                 ¤¢¤ë¤¤¤Ï¤½¤ÎµÕ) ¤Î¤Ç¡¢
                 ¥·¥ó¥Ü¥ë¥Æ¡¼¥Ö¥ë¤¬¥æ¡¼¥¶¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¹Í¤¨¤Æ¤¤¤ë¤â¤Î¤È°Û¤Ê¤Ã¤Æ¤¤¤ë¡£
                 ¤â¤·¤³¤Î¥±¡¼¥¹¤Ê¤é¡¢°ìÏ¢¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¼ê½ç¤Ë½¾¤Ã¤Æ¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò¹Ô¤Ê¤Ã¤Æ¤¯¤À¤µ¤¤
                 (Àµ¤·¤¤¤ä¤êÊý¤Ï <filename>/usr/src/UPDATING</filename>
                 ¤Ë½ñ¤¤¤Æ¤¢¤ê¤Þ¤¹)¡£</para>
             </listitem>
 
             <listitem>
               <para>¥«¡¼¥Í¥ë¤ò¥í¡¼¥É¤¹¤ë¤Î¤Ë
                 <command>/boot/loader</command> ¤ò»È¤ï¤º¡¢
                 ľÀÜ boot2 (&man.boot.8; »²¾È) ¤«¤é¥í¡¼¥É¤·¤Æ¤¤¤ë¡£
                 ¤â¤Á¤í¤ó
                 <command>/boot/loader</command>
                 ¤ò»È¤ï¤Ê¤¯¤È¤âÌäÂê¤Ï¤Ê¤¤¤Î¤Ç¤¹¤¬¡¢
                 <command>/boot/loader</command> ¤Ï°ìÈÌŪ¤Ë¡¢
                 ¥æ¡¼¥¶¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤«¤é¥«¡¼¥Í¥ë¥·¥ó¥Ü¥ë¤ò
                 ¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Îµ¡Ç½¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="connection-delay">
           <para>&man.ssh.1; ¤ä &man.telnet.1; ¤Ç¥³¥ó¥Ô¥å¡¼¥¿¤ËÀܳ¤¹¤ë
             ¤Î¤Ë¡¢¤É¤¦¤·¤Æ¤³¤ó¤Ê¤Ë»þ´Ö¤¬¤«¤«¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¾É¾õ: TCP ¥³¥Í¥¯¥·¥ç¥ó¤¬³ÎΩ¤·¤Æ¤«¤é¡¢
             ¥¯¥é¥¤¥¢¥ó¥È¥½¥Õ¥È¥¦¥§¥¢¤¬¥Ñ¥¹¥ï¡¼¥É¤ò¿Ò¤Í¤Æ¤¯¤ë¤Þ¤Ç
             (&man.telnet.1; ¤Î¾ì¹ç¤Ï¡¢¥í¥°¥¤¥ó¥×¥í¥ó¥×¥È¤¬É½¼¨¤µ¤ì¤ë¤Þ¤Ç)
             ¤ËŤ¤»þ´Ö¤¬¤«¤«¤ë¡¢¤È¤¤¤¦¤â¤Î¡£</para>
 
           <para>ÌäÂê: ¤ª¤½¤é¤¯¡¢¥µ¡¼¥Ð¥½¥Õ¥È¥¦¥§¥¢¤¬¥¯¥é¥¤¥¢¥ó¥È¤Î
             IP ¥¢¥É¥ì¥¹¤«¤é¥Û¥¹¥È̾¤ò²ò·è¤·¤è¤¦¤È¤·¤Æ¡¢Ã٤줬À¸¤¸¤Æ¤¤¤ë
             ¤Î¤Ç¤·¤ç¤¦¡£FreeBSD ¤ËÉÕ°¤¹¤ë SSH ¤ä Telnet ¤ò´Þ¤à¿¤¯¤Î
             ¥µ¡¼¥Ð¥½¥Õ¥È¥¦¥§¥¢¤Ï¡¢¤³¤Î̾Á°²ò·è¤ò¤ª¤³¤Ê¤¤¤Þ¤¹¡£¤³¤ì¤Ï¡¢
             ´ÉÍý¼Ô¤¬¸åÆü»²¾È¤¹¤ë¥í¥°¥Õ¥¡¥¤¥ë¤Ë¡¢¤½¤Î¾¤Î¾ðÊó¤È°ì½ï¤Ë
             ¥Û¥¹¥È̾¤òµ­Ï¿¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤Î¤¬ÌÜŪ¤Ç¤¹¡£</para>
 
           <para>ÂнèË¡: ¤â¤·¡¢¤¢¤Ê¤¿¤Î¥³¥ó¥Ô¥å¡¼¥¿ (¥¯¥é¥¤¥¢¥ó¥È)
             ¤«¤é¤É¤Î¥µ¡¼¥Ð¤ËÀܳ¤¹¤ë¾ì¹ç¤Ë¤âÌäÂ꤬µ¯¤³¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
             ¥¯¥é¥¤¥¢¥ó¥È¤ËÌäÂ꤬¤¢¤ê¤Þ¤¹¡£¤½¤·¤Æ¡¢Ã¯¤«¤¬¤¢¤Ê¤¿¤Î
             ¥³¥ó¥Ô¥å¡¼¥¿ (¥µ¡¼¥Ð) ¤ËÀܳ¤¹¤ë¤È¤­¤À¤±ÌäÂ꤬µ¯¤³¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
             ¤½¤Î¥µ¡¼¥Ð¤ÎÌäÂê¤Ç¤¹¡£</para>
 
           <para>ÌäÂ꤬¥¯¥é¥¤¥¢¥ó¥È¤Ë¤¢¤ë¾ì¹ç¡¢Í£°ì¤ÎÂнèË¡¤Ï
             ¥µ¡¼¥Ð¤¬¤½¤Î¥¯¥é¥¤¥¢¥ó¥È¤Î̾Á°¤ò²ò·è¤Ç¤­¤ë¤è¤¦¤Ë DNS ¤ò½¤Àµ¤¹¤ë¤³¤È¤Ç¤¹¡£
             ¾É¾õ¤¬¥í¡¼¥«¥ë¥Í¥Ã¥È¥ï¡¼¥¯¤ÇȯÀ¸¤·¤Æ¤¤¤ë¤Ê¤é¡¢¥µ¡¼¥Ð¤ÎÀßÄê¤Ë
             ¸¶°ø¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢¤³¤Î¤Þ¤Þ³¤­¤òÆɤߤޤ·¤ç¤¦¡£
             ¤½¤¦¤Ç¤Ï¤Ê¤¯¡¢¥°¥í¡¼¥Ð¥ë¤Ê¥¤¥ó¥¿¡¼¥Í¥Ã¥È´Ä¶­¤ÇȯÀ¸¤·¤Æ¤¤¤ë¤Ê¤é¡¢
             ISP ¤ËÏ¢Íí¤·¤ÆÌäÂê¤Î½¤Àµ¤ò¤ª´ê¤¤¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤²ÄǽÀ­¤¬¹â¤¤¤Ç¤·¤ç¤¦¡£</para>
 
           <para>ÌäÂ꤬¥µ¡¼¥Ð¤Ë¤¢¤Ã¤Æ¡¢¾É¾õ¤¬¥í¡¼¥«¥ë¥Í¥Ã¥È¥ï¡¼¥¯¤Ç
             ȯÀ¸¤·¤Æ¤¤¤ë¤Ê¤é¡¢¥í¡¼¥«¥ë¤Î¥¢¥É¥ì¥¹ÈϰϤˤ¢¤ë¥¢¥É¥ì¥¹¤ò¡¢
             ¤½¤ì¤ËÂбþ¤¹¤ë¥Û¥¹¥È̾¤Ë²ò·è¤¹¤ëÌä¹ç¤»¤ò½èÍý¤Ç¤­¤ë¤è¤¦¤Ë¡¢
             ¥µ¡¼¥Ð¤òÀßÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¾Ü¤·¤¯¤Ï¡¢&man.hosts.5; ¤ª¤è¤Ó &man.named.8;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¤ò¤´Í÷¤¯¤À¤µ¤¤¡£¥°¥í¡¼¥Ð¥ë¤Ê¥¤¥ó¥¿¡¼¥Í¥Ã¥È´Ä¶­¤Î¾ì¹ç¤Ï¡¢
             ¥µ¡¼¥Ð¤Î¥ê¥¾¥ë¥Ð¤¬Àµ¤·¤¯Æ°ºî¤·¤Æ¤¤¤Ê¤¤¤Î¤¬¸¶°ø¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ³Îǧ¤¹¤ë¤Ë¤Ï¡¢Â¾¤Î¥Û¥¹¥È (¤¿¤È¤¨¤Ð
             <hostid>www.yahoo.com</hostid>) ¤ò°ú¤¤¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
             ¤¦¤Þ¤¯¤¤¤«¤Ê¤±¤ì¤Ð¡¢¤¢¤Ê¤¿¤Î¥³¥ó¥Ô¥å¡¼¥¿¤ÎÌäÂê¤Ç¤¹¡£</para>
         </answer>
       </qandaentry>
       <qandaentry>
         <question id="file-table-full">
           <para><errorname>file: table is full</errorname> ¤È¤¤¤¦
             ¥á¥Ã¥»¡¼¥¸¤¬·«¤êÊÖ¤· dmesg ¤Ë¤¢¤é¤ï¤ì¤Þ¤¹¡£
           </para>
         </question>
         <answer>
           <para>
             ¤³¤Î¥¨¥é¡¼¤Ï¡¢¥·¥¹¥Æ¥à¤Î¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤ò»È¤¤²Ì¤¿¤·¤Æ
             ¤·¤Þ¤Ã¤¿»þ¤ËȯÀ¸¤·¤Þ¤¹¡£¥á¥â¥êÃæ¤Î¥Õ¥¡¥¤¥ë¥Æ¡¼¥Ö¥ë¤¬°ìÇÕ¤Ë
             ¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¡£
           </para>
           <para>²ò·èË¡:</para>
           <para>
             ¼êÆ°¤Ç sysctl ÊÑ¿ô
             <varname>kern.maxfiles</varname> ¤Î¸Â³¦ÃͤòÄ´À°¤·¤Þ¤¹¡£
           </para>
           <screen>&prompt.root; <userinput>sysctl -w kern.maxfiles=n</userinput></screen>
           <para><varname>n</varname> ¤Ï¡¢¥·¥¹¥Æ¥àÍ×·ï¤Ë¹ç¤ï¤»¤Æ¤¯¤À¤µ¤¤¡£
             ¥ª¡¼¥×¥ó¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¡¢¥½¥±¥Ã¥È¤Þ¤¿¤Ï fifo ¤Î¤½¤ì¤¾¤ì¤¬
             ¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤ò¾ÃÈñ¤·¤Þ¤¹¡£µ¬ÌϤÎÂ礭¤Ê¥µ¡¼¥Ð¤Ï¡¢
             Ʊ»þ¤Ë¼Â¹Ô¤µ¤ì¤ë¥µ¡¼¥Ó¥¹¤Ë±þ¤¸¤Æ¡¢¤¤¤È¤â¤¿¤ä¤¹¤¯²¿Ëü¤â¤Î
             ¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤òÍ׵ᤷ¤Þ¤¹¡£</para>
           <para>¥«¡¼¥Í¥ë¤ËÀßÄꤵ¤ì¤¿¥Ç¥Õ¥©¥ë¥È¤Î¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î
             ¿ô¤ò·èÄꤹ¤ë¤Î¤Ï¡¢¼¡¤Î</para>
           <programlisting>maxusers        32</programlisting>
           <para>¥«¡¼¥Í¥ëÀßÄê¥Õ¥¡¥¤¥ë¤Î <varname>maxusers</varname> ¹Ô
             ¤Ç¤¹¡£<varname>kern.maxfiles</varname> ¤Ï¤³¤ÎÃͤËÈæÎ㤷¤Æ
             Áý²Ã¤·¤Þ¤¹¡£
           </para>
           <para>¸½ºßÀßÄꤵ¤ì¤Æ¤¤¤ë <varname>kern.maxfiles</varname> ¤Î
             Ãͤϡ¢¼¡¤Î¥³¥Þ¥ó¥É¤ÇÄ´¤Ù¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
           <screen>&prompt.root; <userinput>sysctl kern.maxfiles</userinput>
 kern.maxfiles: 1064
           </screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="laptop-clock-skew">
           <para>laptop ¤Î»þ´Ö¤¬¶¸¤Ã¤Æ¡¢Â礭¤¯¿Ê¤ó¤À¤êÃ٤줿¤ê¤·¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>laptop ¤Ë¤ÏÆó¤Ä°Ê¾å¤Î»þ·×¤¬Æ⢤µ¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢FreeBSD
             ¤¬´Ö°ã¤Ã¤¿Êý¤òÁªÂò¤·¤Æ»ÈÍѤ·¤Æ¤¤¤Þ¤¹¡£</para>
 
           <para>&man.dmesg.8; ¤ò¼Â¹Ô¤·¤Æ
             <literal>Timecounter</literal> ¤ò´Þ¤à¹Ô¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ºÇ¸å¤Ë½ÐÎϤµ¤ì¤¿¹Ô¤¬ FreeBSD ¤¬ÁªÂò¤·¤¿¤â¤Î¤Ç¡¢¤Þ¤º´Ö°ã¤¤
             ¤Ê¤¯ <literal>TSC</literal> ¤Ç¤·¤ç¤¦¡£</para>
 
           <screen>&prompt.root; <userinput>dmesg | grep Timecounter</userinput>
 Timecounter "i8254"  frequency 1193182 Hz
 Timecounter "TSC"  frequency 595573479 Hz</screen>
 
           <para>&man.sysctl.3; ÊÑ¿ô
             <literal>kern.timecounter.hardware</literal> ¤ò³Îǧ¤¹¤ì¤Ð
             ΢ÉÕ¤±¤¬¤È¤ì¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>sysctl kern.timecounter.hardware</userinput>
 kern.timecounter.hardware: TSC</screen>
 
           <para>¥Ð¥Ã¥Æ¥ê¶îÆ°¤·¤Æ¤¤¤ë»þ¤Ë¡¢BIOS ¤¬ CPU ¤Î®ÅÙ¤òÊѤ¨¤ë¤¿¤á¤Ë
             TSC ¥¯¥í¥Ã¥¯¤òÊѹ¹¤·¤¿¤ê¡¢ÅÅÎÏÀáÌó¥â¡¼¥É¤ËÆþ¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
             ¤·¤«¤·¡¢FreeBSD ¤Ï¤½¤¦¤¤¤Ã¤¿Ä´À°¤ò´ØÃΤ·¤Ê¤¤¤Î¤Ç¡¢
             »þ´Ö¤¬Áá¤Þ¤Ã¤¿¤êÃ٤줿¤ê¤¹¤ë¤è¤¦¤Ç¤¹¡£</para>
 
           <para>¾åµ­¤ÎÎã¤Ç¤Ï¡¢<literal>i8254</literal> ¥¯¥í¥Ã¥¯¤âÍøÍѤǤ­¤Þ¤¹¡£
             &man.sysctl.3; ÊÑ¿ô <literal>kern.timecounter.hardware</literal>
             ¤Ë¤½¤Î̾¾Î¤ò½ñ¤­¹þ¤ó¤ÇÁªÂò¤Ç¤­¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>sysctl -w kern.timecounter.hardware=i8254</userinput>
 kern.timecounter.hardware: TSC -&gt; i8254</screen>
 
           <para>¤³¤ì¤Ç¡¢laptop ¤Ï¤è¤êÀµ³Î¤Ê»þ´Ö¤ò¹ï¤à¤Ç¤·¤ç¤¦¡£</para>
 
           <para>¤³¤ÎÊѹ¹¤òµ¯Æ°»þ¤Ë¼«Æ°¤Ç¹Ô¤¦¤Ë¤Ï¡¢¼¡¤Î¹Ô¤ò
             <filename>/etc/sysctl.conf</filename> ¤ËÄɲ䷤Ƥ¯¤À¤µ¤¤¡£</para>
 
           <programlisting>kern.timecounter.hardware=i8254</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="boot-read-error">
           <para>BIOS ²èÌ̤¬½Ð¤¿¸å¡¢FreeBSD ¤Î¥Ö¡¼¥È¥í¡¼¥À¤¬
             <errorname>Read error</errorname> ¤Èɽ¼¨¤·¤Æ»ß¤Þ¤Ã¤Æ
             ¤·¤Þ¤¤¤Þ¤¹¡£
           </para>
         </question>
 
         <answer>
           <para>FreeBSD ¤Î¥Ö¡¼¥È¥í¡¼¥À¤¬¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥¸¥ª¥á¥È¥ê¤òÀµ¤·¤¯
             ǧ¼±¤·¤Æ¤¤¤Ê¤¤¤è¤¦¤Ç¤¹¡£FreeBSD ¤Î¥¹¥é¥¤¥¹¤ò
             fdisk ¤Ë¤è¤Ã¤Æ¼êÆ°¤ÇºîÀ®¤·¤¿¤êÊѹ¹¤·¤¿¤ê¤¹¤ëºÝ¤Ë¡¢
             ¥¸¥ª¥á¥È¥ê¤ò¸í¤Ã¤Æ»ØÄꤷ¤Æ¤·¤Þ¤Ã¤¿¤Î¤Ç¤·¤ç¤¦¡£
           </para>
           <para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥¸¥ª¥á¥È¥ê¤ÎÀµ¤·¤¤Ãͤϡ¢¥Þ¥·¥ó¤Î BIOS ¤«¤é
             ÆÀ¤é¤ì¤Þ¤¹¡£¤½¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥·¥ê¥ó¥À¡¢¥Ø¥Ã¥É¡¢¥»¥¯¥¿¤Î
             ¿ô¤òõ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
           <para>&man.sysinstall.8; ¤Î fdisk ¤Ë¤ª¤¤¤Æ¡¢
             <keycap>G</keycap> ¤òÆþÎϤ·¤Æ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥¸¥ª¥á¥È¥ê¤ò
             ÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
 	  </para>
           <para>¥·¥ê¥ó¥À¡¢¥Ø¥Ã¥É¡¢¥»¥¯¥¿¤Î¿ô¤òÆþÎϤ¹¤ë¥À¥¤¥¢¥í¥°¤¬½Ð¤Æ¤­¤Þ¤¹¡£
             BIOS ¤«¤éÆÀ¤¿Ãͤò¼ÐÀþ (/) ¤Ç¶èÀڤäÆÆþÎϤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
           <para>5000 ¥·¥ê¥ó¥À¡¢250 ¥Ø¥Ã¥É¡¢60 ¥»¥¯¥¿¤Ê¤é¡¢
             <userinput>5000/250/60</userinput>
 	    ¤ÈÆþÎϤ·¤Þ¤¹¡£
           </para>
           <para>¥ê¥¿¡¼¥ó¥­¡¼¤ò²¡¤·¤ÆÃͤòÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£¤½¤ì¤«¤é
             <keycap>W</keycap> ¤òÆþÎϤ·¤Æ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ë¿·¤·¤¤¥Ñ¡¼¥Æ¥£
             ¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤ò½ñ¤­¹þ¤ó¤Ç¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bootmanager-restore">
           <para>Ê̤Υª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬¡¢¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ò
             ²õ¤·¤Æ¤·¤Þ¤¤¤Þ¤·¤¿¡£¤É¤¦¤¹¤ì¤ÐÉüµì¤Ç¤­¤ë¤Ç¤·¤ç¤¦¤«¡£
           </para>
         </question>
 
         <answer>
           <para>&man.sysinstall.8; ¤òΩ¤Á¾å¤²¤Æ Configure (ÀßÄê)¡¢Fdisk
             ¤Î½ç¤ËÁªÂò¤·¤Æ¤¯¤À¤µ¤¤¡£¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤¬ÃÖ¤«¤ì¤Æ¤¤¤¿
             ¥Ç¥£¥¹¥¯¤òÁªÂò¤·¤Æ¡¢<keycap>¥¹¥Ú¡¼¥¹</keycap>¥­¡¼¤ò
             ²¡¤·¤Æ¤¯¤À¤µ¤¤¡£<keycap>W</keycap> ¤ò²¡¤·¤ÆÊѹ¹¤ò
             ¥Ç¥£¥¹¥¯¤Ë½ñ¤­¹þ¤ó¤Ç¤¯¤À¤µ¤¤¡£¤É¤Î¥Ö¡¼¥È¥í¡¼¥À¤ò
             ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤«¿Ò¤Í¤é¤ì¤Þ¤¹¡£¤³¤³¤ÇÁªÂò¤¹¤ì¤ÐÌ᤻¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="commercial">
     <title>¾¦ÍÑ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó</title>
 
     <para>
       <emphasis>Ìõ:
         »³²¼ ½ß <email>junkun@esys.tsukuba.ac.jp</email>¡¢
         1997 ǯ 11 ·î 10 Æü</emphasis></para>
 
       <note>
         <para>
           ¤³¤Î¾Ï¤Ï¤Þ¤À¤Þ¤À¾ðÊó¤¬Â­¤ê¤Þ¤»¤ó¡£
           ¾ðÊó¤òÄɲ䷤Ƥ¯¤ì¤ë¤è¤¦¤Ê´ë¶È¤òÂÔ¤Á˾¤ó¤Ç¤¤¤Þ¤¹¡£
           FreeBSD ¥°¥ë¡¼¥×¤Ï¤³¤³¤ËºÜ¤Ã¤Æ¤¤¤ë´ë¶È¤«¤é¤Î¶âÁ¬Åª¤Ê»Ù±ç¤ò´üÂÔ¤·¤Æ¤Ï¤¤¤Þ¤»¤ó¤Î¤Ç¡¢
           Êô»Åºî¶È¤Î°ì¤Ä¤È¤·¤Æ·ÇºÜ¤·¤Æ¤¤¤Þ¤¹ (¤½¤·¤Æ
           FreeBSD ¤¬·¸¤ï¤ëÀëÅÁ¤Ï¡¢Ä¹¤¤ÌܤǸ«¤ë¤È FreeBSD
           ¤ËÂФ·¤Æ¤è¤¤Êý¸þ¤ØƯ¤¯¤È»×¤Ã¤Æ¤¤¤Þ¤¹)¡£
           »ä¤¿¤Á¤Ï¾¦ÍÑ¥½¥Õ¥È¥¦¥§¥¢¥Ù¥ó¥À¤Ë¡¢
           ¤³¤³¤ÇÀ½ÉʤòÀëÅÁ¤·¤Æ¤â¤é¤¦¤³¤È¤ò˾¤ó¤Ç¤¤¤Þ¤¹¡£¾Ü¤·¤¯¤Ï¡¢
           <ulink url="http://www.FreeBSD.org/commercial/commercial.html"
                  >¾¦ÍÑ¥½¥Õ¥È¥¦¥§¥¢¥Ù¥ó¥ÀÍ÷¤Î¥Ú¡¼¥¸</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
       </note>
 
     <qandaset>
       <qandaentry>
         <question id="officesuite">
           <para>FreeBSD ÍѤΥª¥Õ¥£¥¹¥¹¥¤¡¼¥È¤Ï¤É¤³¤ÇÆþ¼ê¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
 	  <itemizedlist>
   	    <listitem>
               <para><ulink url="http://www.wccdrom.com">BSDi</ulink>
                 ¤Ï FreeBSD ¥Í¥¤¥Æ¥£¥ÖÈǤΠ<ulink
                 url="http://www.vistasource.com">VistaSource</ulink>
                 ApplixWare 5 ¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£</para>
 
               <para>ApplixWare ¤Ï¡¢¹ë²Ú¤Çµ¡Ç½ËþºÜ¤Î FreeBSD ¸þ¤±¤Î
                 ¾¦ÍÑ¥ª¥Õ¥£¥¹¥¹¥¤¡¼¥È¤Ç¡¢¥ï¡¼¥É¥×¥í¥»¥Ã¥µ¡¢É½·×»»¡¢
                 ¥×¥ì¥¼¥ó¥Æ¡¼¥·¥ç¥ó¥½¥Õ¥È¥¦¥§¥¢¡¢¥Ù¥¯¥¿ÉÁ²è¥½¥Õ¥È¥¦¥§¥¢¡¢
                 ¤½¤Î¾¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ò·¤¨¤Æ¤¤¤Þ¤¹¡£</para>
 
               <para>FreeBSD ÈǤΠApplixWare ¤Î¹ØÆþ¤Ï <ulink
                 url="http://www.wccdrom.com/titles/freebsd/applix.phtml">
                 ¤³¤Á¤é</ulink>¤«¤é¤É¤¦¤¾¡£</para>
   	    </listitem>
 
             <listitem>
               <para>Linux ÈǤΠ<ulink
                 url="http://www.sun.com/staroffice">StarOffice</ulink>
                 ¤Ï FreeBSD ¤Ç´°àú¤ËÆ°ºî¤·¤Þ¤¹¡£Linux ÈǤΠStarOffice
                 ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤â¤Ã¤È¤â´Êñ¤ÊÊýË¡¤Ï¡¢<ulink
                 url="../handbook/ports.html">FreeBSD Ports
                   ¥³¥ì¥¯¥·¥ç¥ó</ulink>¤òÍøÍѤ¹¤ë¤³¤È¤Ç¤¹¡£
                 ¤Þ¤¿¡¢¥ª¡¼¥×¥ó¥½¡¼¥¹¤Î
                 <ulink url="http://www.openoffice.org">OpenOffice</ulink>
                 ¤â¾­Íè¤Î¥Ð¡¼¥¸¥ç¥ó¤ÇÆ°ºî¤¹¤ë¤Ç¤·¤ç¤¦¡£</para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="motif">
           <para>FreeBSD ÍѤΠMotif ¤Ï¤É¤¦¤ä¤Ã¤¿¤é¼ê¤ËÆþ¤ê¤Þ¤¹¤«</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ÍѤÎÎ÷²ÁÈÇ ELF Motif 2.1.20 (i386 ÈÇ¡¢Alpha ÈÇ)
             ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï<link linkend="apps2go">Apps2go</link> ¤«¤é
             ¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£<anchor id="apps2go"/>
           </para>
 
           <para>
             ¤³¤ÎÀ½Éʤˤϡ¢¡Ö³«È¯¼ÔÈÇ (development edition)¡× ¤È¡¢
             ¤è¤ê°Â²Á¤Ê¡Ö¥é¥ó¥¿¥¤¥àÈÇ (runtime edition)¡×
             ¤ÎÆó¤Ä¤ÎÈǤ¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤é¤ÎÀ½Éʤϰʲ¼¤Îʪ¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
             <itemizedlist>
               <listitem>
                 <para>OSF/Motif manager¡¢xmbind¡¢panner¡¢wsm¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>uil¡¢mrm¡¢xm¡¢xmcxx¡¢¥¤¥ó¥¯¥ë¡¼¥É¥Õ¥¡¥¤¥ë¤ä Imake
                   ¥Õ¥¡¥¤¥ë¤È¤¤¤Ã¤¿³«È¯¼Ô¸þ¤±¥­¥Ã¥È
                 </para>
               </listitem>
 
               <listitem>
                 <para>FreeBSD 3.0 °Ê¹ß¤ÇÍøÍѤǤ­¤ë ELF ÈÇ¥¹¥¿¥Æ¥£¥Ã¥¯¥é¥¤¥Ö¥é¥ê¡¢
                   ¤ª¤è¤Ó¥À¥¤¥Ê¥ß¥Ã¥¯¥é¥¤¥Ö¥é¥ê
                 </para>
               </listitem>
 
               <listitem>
                 <para>¥Ç¥â¥ó¥¹¥È¥ì¡¼¥·¥ç¥ó¥×¥í¥°¥é¥à
                 </para>
               </listitem>
             </itemizedlist>
 
           <para>
             Ãíʸ¤¹¤ëºÝ¤Ë¤Ï FreeBSD ÍѤΠMotif ¤Ç¤¢¤ë¤³¤È¤ò¤­¤Á¤ó¤È
             ³Îǧ¤·¤Æ¤¯¤À¤µ¤¤ (¤¢¤Ê¤¿¤ÎÍߤ·¤¤¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤ò»ØÄꤹ¤ë¤Î¤â
             ˺¤ì¤Ê¤¤¤Ç¤¯¤À¤µ¤¤!)¡£NetBSD ¤ä OpenBSD ÍѤΠMotif ¤â¤Þ¤¿¡¢
             <emphasis>Apps2go</emphasis>¤«¤éÈÎÇ䤵¤ì¤Æ¤¤¤Þ¤¹¡£¸½ºß¡¢FTP ¤Ë¤è¤ë
             ¥À¥¦¥ó¥í¡¼¥É¤Î¤ßÍøÍѲÄǽ¤Ç¤¹¡£
           </para>
 
             <variablelist>
               <varlistentry>
                 <term>¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï</term>
                 <listitem>
                   <para><ulink url="http://www.apps2go.com/">Apps2go WWW page</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>Ì䤤¹ç¤ï¤»¤Ï</term>
                 <listitem>
                   <para><ulink url="mailto:sales@apps2go.com">Sales</ulink> ¤Þ¤¿¤Ï
                     <ulink url="mailto:support@apps2go.com">Support</ulink> ÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¡£</para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>¤â¤·¤¯¤Ï</term>
                 <listitem>
                   <para>phone (817) 431 8775  or +1 817 431-8775</para>
                 </listitem>
               </varlistentry>
             </variablelist>
 
           <para>
             ¾¤Î FreeBSD ÍÑ Motif 2.1 (ELF ÈÇ¡¢a.out ÈÇ) ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï
             <link linkend="metrox">Metro Link</link> ¤«¤é¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>¤³¤ÎÀ½Éʤϰʲ¼¤Îʪ¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
             <itemizedlist>
               <listitem>
                 <para>OSF/Motif manager¡¢xmbind¡¢panner¡¢wsm¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>uil¡¢mrm¡¢xm¡¢xmcxx¡¢¥¤¥ó¥¯¥ë¡¼¥É¥Õ¥¡¥¤¥ë¤ä Imake
                   ¥Õ¥¡¥¤¥ë¤È¤¤¤Ã¤¿³«È¯¼Ô¸þ¤±¥­¥Ã¥È
                 </para>
               </listitem>
 
               <listitem>
                 <para>¥¹¥¿¥Æ¥£¥Ã¥¯¥é¥¤¥Ö¥é¥ê¡¢¤ª¤è¤Ó¥À¥¤¥Ê¥ß¥Ã¥¯¥é¥¤¥Ö¥é¥ê¡£
                   (FreeBSD 3.0 °Ê¹ß¤ÇÍøÍѤǤ­¤ë ELF ÈǤ«¡¢
                   FreeBSD 2.2.8 °ÊÁ°¤ÇÍøÍѤǤ­¤ë a.out ÈǤò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤)
                 </para>
               </listitem>
 
               <listitem>
                 <para>¥Ç¥â¥ó¥¹¥È¥ì¡¼¥·¥ç¥ó¥×¥í¥°¥é¥à
                 </para>
               </listitem>
 
               <listitem>
                 <para>À°·ÁºÑ¤ß¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸</para>
               </listitem>
             </itemizedlist>
 
           <para>
             Ãíʸ¤¹¤ëºÝ¤Ë¤Ï FreeBSD ÍѤΠMotif ¤Ç¤¢¤ë¤³¤È¤ò¤­¤Á¤ó¤È
             ³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£Linux ÍѤΠMotif ¤â <emphasis>Metro Link</emphasis>
             ¤«¤éÈÎÇ䤵¤ì¤Æ¤¤¤Þ¤¹¡£¸½ºß¡¢CDROM ¤ª¤è¤Ó FTP
             ¤Ë¤è¤ë¥À¥¦¥ó¥í¡¼¥É¤¬ÍøÍѲÄǽ¤Ç¤¹¡£
           </para>
 
           <para>
             FreeBSD ÍѤΠa.out ÈÇ Motif 2.0 ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï
             <link linkend="xig">Xi Graphics</link> ¤«¤é
             ¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ÎÀ½Éʤˤϰʲ¼¤Îʪ¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
             <itemizedlist>
               <listitem>
                 <para>OSF/Motif manager¡¢xmbind¡¢panner¡¢wsm¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>uil¡¢mrm¡¢xm¡¢xmcxx¡¢¥¤¥ó¥¯¥ë¡¼¥É¥Õ¥¡¥¤¥ë¤ä Imake
                   ¥Õ¥¡¥¤¥ë¤È¤¤¤Ã¤¿³«È¯¼Ô¸þ¤±¥­¥Ã¥È
                 </para>
               </listitem>
 
               <listitem>
                 <para>FreeBSD 2.2.8 °ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤ÇÍøÍѤǤ­¤ë¥¹¥¿¥Æ¥£¥Ã¥¯¥é¥¤¥Ö¥é¥ê¡¢
                   ¤ª¤è¤Ó¥À¥¤¥Ê¥ß¥Ã¥¯¥é¥¤¥Ö¥é¥ê
                 </para>
               </listitem>
 
               <listitem>
                 <para>¥Ç¥â¥ó¥¹¥È¥ì¡¼¥·¥ç¥ó¥×¥í¥°¥é¥à
                 </para>
               </listitem>
 
               <listitem>
                 <para>À°·ÁºÑ¤ß¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸</para>
               </listitem>
             </itemizedlist>
 
           <para>
             Ãíʸ¤¹¤ëºÝ¤Ë¤Ï FreeBSD ÍѤΠMotif ¤Ç¤¢¤ë¤³¤È¤ò¤­¤Á¤ó¤È
             ³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£BSDI ¤ä Linux ÍѤΠMotif ¤â¤Þ¤¿¡¢<emphasis>Xi Graphics</emphasis>
             ¤«¤éÈÎÇ䤵¤ì¤Æ¤¤¤Þ¤¹¡£¸½ºß¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯ 4ËçÁȤǤ¹¤¬¡¢
             ¾­ÍèŪ¤Ë¤Ï CDE ¤Î¤è¤¦¤ËÅý¹ç¤µ¤ì¤¿ CD ¤ËÊѤï¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cde">
           <para>FreeBSD ÍѤΠCDE ¤Ï¤É¤¦¤ä¤Ã¤¿¤é¼ê¤ËÆþ¤ê¤Þ¤¹¤«</para>
         </question>
 
         <answer>
           <para>°ÊÁ°
             <link linkend="xig">Xi Graphics</link> ¤è¤ê FreeBSD ÍѤΠCDE ¤¬
             ÈÎÇ䤵¤ì¤Æ¤¤¤Þ¤·¤¿¤¬¡¢¸½ºß¤Ï´û¤ËÈÎÇ䤬½ªÎ»¤·¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para><ulink url="http://www.kde.org/">KDE</ulink>
             ¿¤¯¤ÎÅÀ¤Ç CDE ¤ÈÎà»÷¤·¤Æ¤¤¤ë¥ª¡¼¥×¥ó¥½¡¼¥¹¤Î X11 ¥Ç¥¹¥¯¥È¥Ã¥×´Ä¶­¤Ç¤¹¡£
             <ulink url="http://www.xfce.org/">xfce</ulink> ¤Î
             ¥ë¥Ã¥¯ &amp; ¥Õ¥£¡¼¥ë (ÌõÃí: ³°´Ñ¤äÁàºîÊýË¡¤Î¤³¤È) ¤âµ¤¤ËÆþ¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£
             KDE¡¢xfce ¤Ï¡¢¤¤¤º¤ì¤â
             <ulink url="http://www.FreeBSD.org/ports/">FreeBSD Ports Collection</ulink>
             ¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="commercial-xserver">
           <para>¹âµ¡Ç½¤Ê¾¦ÍÑ X ¥µ¡¼¥Ð¤Ã¤Æ¤¢¤ë¤ó¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¤Ï¤¤¡¢<ulink url="http://www.xig.com/">Xi Graphics</ulink> ¤È
             <ulink url="http://www.metrolink.com/">Metro Link</ulink>
             ¤«¤é¡¢FreeBSD ¤Û¤« Intel ¥Ù¡¼¥¹¤Î¥·¥¹¥Æ¥à¤ÇÆ°ºî¤¹¤ë
             Accelerated-X ¤È¤¤¤¦À½Éʤ¬ÈÎÇ䤵¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             Metro Link ¤Ï¡¢FreeBSD ¤Î¥Ñ¥Ã¥±¡¼¥¸Áàºî¥Ä¡¼¥ë¤òÍøÍѤ¹¤ë¤³¤È¤Ç
             ÍưפËÀßÄ꤬¹Ô¤Ê¤¨¤ë¤Û¤«¡¢¿ô¿¤¯¤Î¥Ó¥Ç¥ª¥Ü¡¼¥É¤ò¥µ¥Ý¡¼¥È¤·¤¿
             ¹âµ¡Ç½¤Ê X ¥µ¡¼¥Ð¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£ÇÛÉۤϥХ¤¥Ê¥ê·Á¼°¤Î¤ß¤Ç¡¢
             FTP ¤¬ÍøÍѲÄǽ¤Ç¤¹¡£¤â¤Á¤í¤ó¡¢¤È¤Æ¤â°Â²Á ($39) ¤Ë¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             <anchor id="metrox"/>
           </para>
 
           <para>
             ¤Þ¤¿¡¢Metro Link ¤Ï ELF ÈÇ¡¢a.out ÈǤΠFreeBSD ÍÑ Motif
             ¤âÈÎÇ䤷¤Æ¤¤¤Þ¤¹ (Á°¤ò»²¾È)¡£
           </para>
 
             <variablelist>
               <varlistentry><term>¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï</term>
                 <listitem>
                   <para><ulink url="http://www.metrolink.com/">Metro Link WWW page</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry><term>Ì䤤¹ç¤ï¤»¤Ï</term>
                 <listitem>
                   <para><ulink url="mailto:sales@metrolink.com">Sales</ulink>
                     ¤Þ¤¿¤Ï
                     <ulink url="mailto:tech@metrolink.com">Support</ulink> ÅŻҥ᡼¥ë¥¢¥É¥ì¥¹</para>
                 </listitem>
               </varlistentry>
 
               <varlistentry><term>¤â¤·¤¯¤Ï</term>
                 <listitem>
                   <para>phone (954) 938-0283  or +1 954 938-0283</para>
                 </listitem>
               </varlistentry>
             </variablelist>
 
           <para>
             Xi Graphics ¤¬Ä󶡤·¤Æ¤¤¤ë¹âÀ­Ç½¤Ê X ¥µ¡¼¥Ð¤Ï³Ú¤ËÀßÄê¤ò¹Ô¤Ê¤¨¤ë¤Û¤«¡¢
             ¿ô¿¤¯¤Î¥Ó¥Ç¥ª¥Ü¡¼¥É
             ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£¥µ¡¼¥Ð¤Ï¥Ð¥¤¥Ê¥ê¤Î¤ß¤¬´Þ¤Þ¤ì¤Þ¤¹¡£
             FreeBSD ÍÑ¤È Linux ÍѤÎÅý¹ç¤µ¤ì¤¿¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ËÆþ¤Ã¤Æ¤¤¤Þ¤¹¡£
             Xi Graphics ¤Ï Laptop ¥µ¥Ý¡¼¥È¤ËÆò½¤·¤¿¹âÀ­Ç½ X ¥µ¡¼¥Ð¤âÄ󶡤·¤Æ¤¤¤Þ¤¹¡£
             <anchor id="xig"/>
           </para>
 
           <para>
             ¥Ð¡¼¥¸¥ç¥ó 5.0 ¤Î¡Ö¸ß´¹¥Ç¥â¡×¤¬ÌµÎÁ¤ÇÆþ¼ê¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¤Þ¤¿ Xi Graphics ¤Ï FreeBSD ÍѤΠMotif ¤È CDE ¤âÈÎÇ䤷¤Æ¤¤¤Þ¤¹ (Á°¤ò»²¾È)¡£
           </para>
 
             <variablelist>
               <varlistentry>
                 <term>¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï</term>
                 <listitem>
                   <para><ulink url="http://www.xig.com/">Xi Graphics WWW page</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>Ì䤤¹ç¤»¤Ï</term>
                 <listitem>
                   <para><ulink url="mailto:sales@xig.com">Sales</ulink> ¤Þ¤¿¤Ï
                     <ulink url="mailto:support@xig.com">Support</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>¤â¤·¤¯¤Ï</term>
                 <listitem>
                   <para>phone (800) 946 7433  or +1 303 298-7478.</para>
                 </listitem>
               </varlistentry>
             </variablelist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="database-systems">
           <para>FreeBSD ÍѤΥǡ¼¥¿¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Ï¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¤â¤Á¤í¤ó¤Ç¤¹¡£FreeBSD ¤Î¥¦¥§¥Ö¥µ¥¤¥È¤Ë¤¢¤ë
             <ulink url="http://www.FreeBSD.org/commercial/software_bycat.html#CATEGORY_DATABASE">
               ¾¦ÍÑ¥Ù¥ó¥À¡¼</ulink> ¤È¤¤¤¦¥»¥¯¥·¥ç¥ó¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤Þ¤¿¡¢FreeBSD Ports Collection
             ¤Î<ulink url="http://www.FreeBSD.org/ports/databases.html">¥Ç¡¼¥¿¥Ù¡¼¥¹</ulink>¤Î¥»¥¯¥·¥ç¥ó¤â»²¹Í¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="oracle-support">
           <para>Oracle ¤ò FreeBSD ¾å¤ÇÆ°¤«¤¹¤³¤È¤Ï¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Ï¤¤¡£Linux ÈÇ Oracle ¤ò FreeBSD ¤Ç¥»¥Ã¥È¥¢¥Ã¥×¤¹¤ë¤¿¤á¤ÎÊýË¡¤Ï¡¢
             ¼¡¤Ë¼¨¤¹¥Ú¡¼¥¸¤Ë¾Ü¤·¤¯½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
             <itemizedlist>
               <listitem>
                 <para><ulink url="http://www.scc.nl/~marcel/howto-oracle.html">http://www.scc.nl/~marcel/howto-oracle.html</ulink></para>
               </listitem>
 
               <listitem>
                 <para><ulink url="http://www.lf.net/lf/pi/oracle/install-linux-oracle-on-freebsd">http://www.lf.net/lf/pi/oracle/install-linux-oracle-on-freebsd</ulink></para>
               </listitem>
             </itemizedlist>
         </answer>
       </qandaentry>
     </qandaset>
 </chapter>
 
   <chapter id="applications">
     <title>¥æ¡¼¥¶¥¢¥×¥ê¥±¡¼¥·¥ç¥ó</title>
 
     <para>
       <emphasis>Ìõ:
         »³²¼ ½ß <email>junkun@esys.tsukuba.ac.jp</email>¡¢
         &a.jp.shou;¡¢
         1997 ǯ 11 ·î 8 Æü</emphasis>
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="user-apps">
           <para>¤½¤¦¤¤¤¦¥æ¡¼¥¶¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ï¤É¤³¤Ë¤¢¤ë¤Î?</para>
         </question>
 
         <answer>
           <para>FreeBSD¤Ë°Ü¿¢¤µ¤ì¤¿¥½¥Õ¥È¥¦¥§¥¢¥Ñ¥Ã¥±¡¼¥¸¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             <ulink url="http://www.FreeBSD.org/ports/">FreeBSD Ports Collection
               ¤Î¥Ú¡¼¥¸</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
             ¤³¤Î¥ê¥¹¥È¤Ë¤Ï¸½ºß 3400 ¤ò±Û¤¨¤ë¹àÌܤ¬¤¢¤ê¡¢
             ¤·¤«¤âËèÆü¹¹¿·¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥Ú¡¼¥¸¤ò¤³¤Þ¤á¤Ëˬ¤ì¤ë¤«¡¢
             <literal>freebsd-announce</literal><link linkend="mailing">
               ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</link>¤ò¹ØÆɤ¹¤ë¤È¡¢
             ¿·¤·¤¯Æþ¤Ã¤¿ ports ¤òÄê´üŪ¤Ë¥Á¥§¥Ã¥¯¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ÂçÉôʬ¤Î ports ¤Ï 2.2 ¤È 3.x ¤ª¤è¤Ó 4.x ¥Ö¥é¥ó¥Á¤ÇÍøÍѤǤ­¤ë¤Ï¤º¤Ç¤¹¡£
             ¿¤¯¤Ï 2.1.x ·Ï¤Î¥·¥¹¥Æ¥à¤Ç¤âƱÍͤËÆ°ºî¤¹¤ë¤Ç¤·¤ç¤¦¡£
             FreeBSD ¤Î¥ê¥ê¡¼¥¹¤¬½Ð¤ëÅ٤ˡ¢¤½¤Î¥ê¥ê¡¼¥¹¤Î»þÅÀ¤Ç¤Î ports ¥Ä¥ê¡¼¤Î
             ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤¬»£¤é¤ì¡¢<filename>ports/</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤Ë
             Ǽ¤á¤é¤ì¤ë¤³¤È¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¤Þ¤¿¡¢<quote>package</quote>
             ¤È¤¤¤¦¹Í¤¨¤âºÎÍѤµ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ï´ðËÜŪ¤Ë¤Ï
             gzip ¤Ç°µ½Ì¤µ¤ì¤¿¥Ð¥¤¥Ê¥ê¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Ë¡¢
             ¥¤¥ó¥¹¥È¡¼¥ë»þ¤Ë´Ä¶­¤Ë¹ç¤ï¤»¤¿ºî¶È¤¬É¬Íפˤʤ俾ì¹ç¡¢
             ¹Ô¤¦µ¡Ç½¤ò¿¾¯ÉÕ¤±²Ã¤¨¤¿¤â¤Î¤Ç¤¹¡£
             package ¤ò»È¤¨¤Ð¡¢¤É¤Î¤è¤¦¤Ê¥Õ¥¡¥¤¥ë¤¬ÇÛÉÛʪ¤È¤·¤Æ´Þ¤Þ¤ì¤Æ¤¤¤ë¤«¡¢
             ¤È¸À¤Ã¤¿ºÙ¤«¤¤»öÊÁ¤Ë¤¤¤Á¤¤¤ÁÈѤ蘆¤ì¤ë¤³¤È¤Ê¤¯¡¢
             ´Êñ¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤ä¥¢¥ó¥¤¥ó¥¹¥È¡¼¥ë¤ò·«¤êÊÖ¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¤¤ package ¤¬¤¢¤ë¤Ê¤é¡¢
             <filename>/stand/sysinstall</filename>¤Î¡¢
             ¡Ö¥¤¥ó¥¹¥È¡¼¥ë¸å¤Î FreeBSD ¤ÎÀßÄê¤ò¹Ô¤¦¡×¤Î²¼¤Ë¤¢¤ë
             package ¤Î¥¤¥ó¥¹¥È¡¼¥ë¥á¥Ë¥å¡¼¤ò»È¤¦¤«¡¢
             package ¤Î¥Õ¥¡¥¤¥ë̾¤ò»ØÄꤷ¤Æ
             &man.pkg.add.1; ¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
             package ¤Î¥Õ¥¡¥¤¥ë̾¤Ë¤Ï¡¢
             Ä̾ïËöÈø¤Ë <filename>.tgz</filename> ¤¬¤Ä¤¤¤Æ¤¤¤Þ¤¹¡£
             CDROM ¤ò¤´»ÈÍѤÎÊý¤Ï¡¢CD ¤Î
             <filename>packages/All</filename>
             ¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤½¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤òÍøÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤Þ¤¿¡¢°Ê²¼¤Î¾ì½ê¤«¤é¡¢
             FreeBSD ¤Î³Æ¼ï¥Ð¡¼¥¸¥ç¥ó¤Ë¤¢¤ï¤»¤¿ package ¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ë
             ¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
           </para>
 
             <variablelist>
               <varlistentry>
                 <term>2.2.8-RELEASE/2.2.8-STABLE ÍÑ</term>
                 <listitem>
                   <para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>3.X-RELEASE/3.X-STABLE ÍÑ</term>
                 <listitem>
                   <para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term> 4.X-RELEASE/4-STABLE ÍÑ</term>
                 <listitem>
                   <para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>5.X-CURRENT ÍÑ</term>
 
                 <listitem>
                   <para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current</ulink></para>
                 </listitem>
               </varlistentry>
 
             </variablelist>
 
           <para>¤ª¶á¤¯¤Î¥ß¥é¡¼¥µ¥¤¥È¤â¤´ÍøÍѤ¯¤À¤µ¤¤¡£</para>
 
           <para>
             ¿·¤·¤¤ ports ¤¬Â³¡¹¤ÈÄɲ䵤ì¤Æ¤¤¤ë¾õÂ֤ʤΤǡ¢¤¹¤Ù¤Æ¤Î ports ¤Ë
             Âбþ¤¹¤ë package ¤¬Â¸ºß¤¹¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¤³¤È¤ò³Ð¤¨¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£
             Äê´üŪ¤Ë <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</ulink>
             ¥Þ¥¹¥¿¡¼¥µ¥¤¥È¤òˬ¤ì¤Æ¡¢¤É¤Î¤è¤¦¤Ê
             package ¤¬ÍøÍѤǤ­¤ë¤Î¤«¥Á¥§¥Ã¥¯¤¹¤ë¤Î¤âÎɤ¤¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="minimal-sh">
           <para>¤Ê¤¼ <command>/bin/sh</command> ¤Ï¤³¤ó¤Ê¤ËÄ㵡ǽ¤Ê¤Î¤Ç¤¹¤«?
             ¤É¤¦¤·¤Æ <command>bash</command> ¤ä¾¤Î¥·¥§¥ë¤òºÎÍѤ·¤Ê¤¤¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>¤½¤ì¤Ï¡¢POSIX ¤¬¤½¤Î¤è¤¦¤Ê¥·¥§¥ë¤¬¤¢¤ë¤³¤È¤òµ¬Äꤷ¤Æ¤¤¤ë¤«¤é¤Ç¤¹¡£</para>
 
           <para>
             ¤â¤Ã¤È¹þ¤ßÆþ¤Ã¤¿²óÅú:
             ¿¤¯¤Î¥æ¡¼¥¶¤Ï¡¢Â¿¤¯¤Î¥·¥¹¥Æ¥à¤ÇƱ¤¸¤è¤¦¤ËÆ°ºî¤Ç¤­¤ë¥·¥§¥ë¥¹¥¯¥ê¥×¥È¤ò½ñ¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤¬¡¢POSIX ¤Ç¥·¥§¥ë¤ä¥æ¡¼¥Æ¥£¥ê¥Æ¥£¥³¥Þ¥ó¥É¤¬ºÙ¤¯µ¬Äꤵ¤ì¤Æ¤¤¤ëÍýͳ¤Ç¤¹¡£
             ¤Û¤È¤ó¤É¤¹¤Ù¤Æ¤Î¥¹¥¯¥ê¥×¥È¤Ï Bourne shell ¤Ç½ñ¤«¤ì¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢
             ¤½¤ì¤Ï¡¢¿ô¿¤¯¤Î½ÅÍ×¤Ê¥×¥í¥°¥é¥ß¥ó¥°¥¤¥ó¥¿¥Õ¥§¥¤¥¹ (&man.make.1;¡¢
             &man.system.3;¡¢&man.popen.3;¡¢¤ä Perl ¤ä Tcl Åù¤ÎÎà»÷¤Î
             ¹â¿å½à¥¹¥¯¥ê¥×¥È¸À¸ì) ¤¬¡¢¥³¥Þ¥ó¥É¤Î²ò¼á¤Ë Bourne shell ¤ò»È¤¦¤«¤é¤Ç¤¹¡£
             ¤³¤Î¤è¤¦¤Ë Bourne shell ¤¬¶Ë¤á¤ÆÉÑÈˤˤ«¤Ä¹­ÈϰϤǻȤï¤ì¤Æ¤¤¤ë¤¿¤á¡¢
             ÁÇÁ᤯µ¯Æ°¤Ç¤­¤Æ³Î¼Â¤ËÆ°ºî¤·¡¢¥á¥â¥ê¤ò¾¯¤·¤·¤«¾ÃÈñ¤·¤Ê¤¤¤È¤¤¤¦¤³¤È¤¬
             ½ÅÍפˤʤê¤Þ¤¹¡£</para>
 
           <para>
             ´û¸¤Î¼ÂÁõ¤Ï¡¢
             »ä¤¿¤Á¤Ë²Äǽ¤Ê¸Â¤ê¤³¤ì¤é¤Î¿¤¯¤ÎÍ×µá¤òƱ»þ¤ËËþ­¤¹¤ë¤³¤È¤¬¤Ç¤­¤ëºÇÎɤΤâ¤Î¤Ç¤¹¡£
             <command>/bin/sh</command> ¤ò¾®¤µ¤¤¤Þ¤Þ¤ËÊݤĤ¿¤á¡¢
             »ä¤¿¤Á¤Ï¾¤Î¥·¥§¥ë¤¬»ý¤ÄÍÍ¡¹¤ÊÊØÍø¤Êµ¡Ç½¤òÄ󶡤·¤Æ¤¤¤Þ¤»¤ó¡£
             Ports ¥³¥ì¥¯¥·¥ç¥ó¤¬ bash ¤ä scsh¡¢tcsh¡¢zsh ¤Ê¤É¤Î
             ¿µ¡Ç½¤Ê¥·¥§¥ë¤ò´Þ¤ó¤Ç¤¤¤ë¤«¤é¤Ç¤¹ (¤³¤ì¤é¤Î¥·¥§¥ë¤¹¤Ù¤Æ¤Î
             ¥á¥â¥ê»ÈÍѾõ¶·¤Ï¡¢<command>ps -u</command> ¤Î <quote>VSZ</quote> ¤ä
             <quote>RSS</quote> ¤Î¹Ô¤Ç¡¢¤¢¤Ê¤¿¼«¿È¤¬³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹)¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-libcso30">
           <para>libc.so.3.0 ¤Ï¤É¤³¤Ë¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 2.1.x ¤Î¥·¥¹¥Æ¥à¤Ç 2.2 °Ê¹ßÍѤÎ
             package ¤òÆ°¤«¤½¤¦¤È¤·¤Æ¤¤¤Þ¤¹¤Í?
             Á°¤Î¥»¥¯¥·¥ç¥ó¤òÆɤó¤Ç¡¢¥·¥¹¥Æ¥à¤Ë¹ç¤Ã¤¿Àµ¤·¤¤
             port/package ¤òÆþ¼ê¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-libcso40">
           <para><literal>Error: can't find libc.so.4.0</literal>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬É½¼¨¤µ¤ì¤ë¤Î¤Ç¤¹¤¬¡£</para>
         </question>
 
         <answer>
           <para>²¿¤«¤Î¼ê°ã¤¤¤Ç¡¢4.X ¤È 5.X ¤Î¥·¥¹¥Æ¥àÍÑ package ¤ò¥À¥¦¥ó¥í¡¼¥É¤·¡¢
             FreeBSD 2.X¡¢¤â¤·¤¯¤Ï 3.X ¤Î¥·¥¹¥Æ¥à¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤·¤Þ¤Ã¤¿¤Î¤Ç¤·¤ç¤¦¡£
             Âбþ¤¹¤ëÀµ¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤Î package ¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="emul">
           <para>386/486SX ¤Î¥Þ¥·¥ó¤Ç ghostscript ¤òÆ°¤«¤¹¤È¥¨¥é¡¼¤¬¤Ç¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             ¤¢¤Ê¤¿¤Î¥Þ¥·¥ó¤Ë¤Ï¿ôÃͱ黻¥×¥í¥»¥Ã¥µ¤¬ÅëºÜ¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¤Í?
             ¥«¡¼¥Í¥ë¤Ë¥³¥×¥í¥»¥Ã¥µ¤ÎÂå¤ï¤ê¤È¤Ê¤ë¿ôÃͱ黻¥¨¥ß¥å¥ì¡¼¥¿¤òÄɲ乤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             °Ê²¼¤Î¥ª¥×¥·¥ç¥ó¤ò¥«¡¼¥Í¥ë¤Î¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤ËÄɲ䷤ơ¢
             ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
             <programlisting>options GPL_MATH_EMULATE</programlisting>
 
             <note>
               <para>¤³¤Î¥ª¥×¥·¥ç¥ó¤òÄɲ乤ë¾ì¹ç¡¢
                 <literal>MATH_EMULATE</literal>
                 ¤Î¹Ô¤òºï½ü¤·¤Æ¤¯¤À¤µ¤¤¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sco-socksys">
           <para>SCO/iBCS2 ¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ò¼Â¹Ô¤¹¤ë¤È¡¢
             <literal>socksys</literal> ¤ÇÍî¤Á¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
             (FreeBSD 3.0 ¤È¤½¤ì°ÊÁ°¤Î¤ß)</para>
         </question>
 
         <answer>
           <para>
             ¤Þ¤ººÇ½é¤Ë
             <filename>/etc/sysconfig</filename> (¤Þ¤¿¤Ï
             <filename>/etc/rc.conf</filename>, &man.rc.conf.5; »²¾È)
             ¤ÎºÇ¸å¤Î¥»¥¯¥·¥ç¥ó¤òÊÔ½¸¤·¡¢
             °Ê²¼¤ÎÊÑ¿ô¤ò <literal>YES</literal> ¤Ëľ¤·¤Þ¤¹¡£
           </para>
 
           <programlisting># Set to YES if you want ibcs2 (SCO) emulation loaded at startup
 ibcs2=NO</programlisting>
 
           <para>
             ¤³¤ì¤Ç¥·¥¹¥Æ¥à¤Îµ¯Æ°»þ¤Ë
             ibcs2
             ¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤¬Æɤ߹þ¤Þ¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¼¡¤Ë /compat/ibcs2/dev/
             ¤ò°Ê²¼¤Î¤è¤¦¤ËÊÔ½¸¤·¤Þ¤¹¡£
           </para>
 
           <screen>lrwxr-xr-x  1 root  wheel         9 Oct 15 22:20 X0R@ -&gt; /dev/null
 lrwxr-xr-x  1 root  wheel         7 Oct 15 22:20 nfsd@ -&gt; socksys
 -rw-rw-r--  1 root  wheel         0 Oct 28 12:02 null
 lrwxr-xr-x  1 root  wheel         9 Oct 15 22:20 socksys@ -&gt; /dev/null
 crw-rw-rw-  1 root  wheel   41,   1 Oct 15 22:14 spx</screen>
 
           <para>
             open ¤ä close ¤Î½èÍý¤Ï¡¢
             socksys ¤«¤é
             <devicename>/dev/null</devicename> (&man.null.4; »²¾È)
             ¤Ø¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤òÄ¥¤ë¤³¤È¤ÇÂåÍѤ·¤Þ¤¹¡£
             »Ä¤ê¤Î½èÍý¤Ï¡¢-CURRENT ¤ËÆþ¤Ã¤Æ¤¤¤ë¥³¡¼¥É¤¬Ã´Åö¤·¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤Ï°ÊÁ°¤Î¤â¤Î¤è¤ê ¤º¤Ã¤È¥¹¥Ã¥­¥ê¤·¤¿ÊýË¡¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="configure-inn">
           <para>INN (¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥Ë¥å¡¼¥¹) ¤ÎÀßÄêÊýË¡¤Ï?</para>
         </question>
 
         <answer>
           <para>inn ¤Î package ¤ä port ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¤¢¤È¤Ë
             <ulink url="http://www.cis.ohio-state.edu/~barr/INN.html">Dave Barr's
               INN Page</ulink> ¤ò¸«¤Æ¤ß¤Þ¤·¤ç¤¦¡£½é¿´¼Ô¸þ¤±¤Î INN FAQ ¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ms-frontpage">
           <para>¤É¤Î¥Ð¡¼¥¸¥ç¥ó¤Î Microsoft FrontPage ¤ò¼ê¤ËÆþ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
           <answer>
           <para>
             ¥ë¡¼¥¯¡¢ports ¤ò»È¤¦¤Î¤À!
             ¥Ñ¥Ã¥Á½èÍýºÑ¤ß¤Î Apache ¤¬ ports ¥Ä¥ê¡¼¤«¤éÆþ¼ê¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="java">
           <para>FreeBSD ¤Ï Java ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¤Ï¤¤¡£
             <ulink url="http://www.FreeBSD.org/java/">http://www.FreeBSD.org/java/</ulink>
             ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
             <ulink url="../java/">ÆüËܸìÌõ</ulink>
             ¤â¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ports-3x">
           <para>3.x-STABLE ¤òºÜ¤»¤Æ¤¤¤ë¥Þ¥·¥ó¤Ç port
             ¤¬¥³¥ó¥Ñ¥¤¥ë¤Ç¤­¤Ê¤¤¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£¤½¤ì¤Ï¤É¤¦¤·¤Æ¤Ç¤¹¤«?
           </para>
         </question>
 
         <answer>
           <para>
             ¤â¤·¡¢¤½¤Î»þÅÀ¤Î -CURRENT ¤« -STABLE
             ¤ËÈæ¤Ù¤Æ¤º¤Ã¤È¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤Î FreeBSD ¤òÍøÍѤ·¤Æ¤¤¤ë¤Ê¤é¡¢
             <ulink url="http://www.FreeBSD.org/ports/">http://www.FreeBSD.org/ports/</ulink>
             ¤Ë¤¢¤ë ports ¥¢¥Ã¥×¥°¥ì¡¼¥É¥­¥Ã¥È¤¬É¬ÍפǤ¹¡£
             ºÇ¿·¤Î FreeBSD ¤òÍøÍѤ·¤Æ¤¤¤ë¤Î¤ËȯÀ¸¤¹¤ë¾ì¹ç¤Ï¤ª¤½¤é¤¯¡¢
             -CURRENT ¤Ç¤ÏÀµ¾ï¤Ê¤Î¤Ë -STABLE ¤Ç¤Ï¤¦¤Þ¤¯Æ°¤«¤Ê¤¯¤Ê¤ë¤è¤¦¤ÊÊѹ¹¤¬¤½¤Î
             port ¤ËÂФ·¤Æ¹Ô¤Ê¤ï¤ì¡¢¼õÍý¤µ¤ì¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦¡£
             ports ¥³¥ì¥¯¥·¥ç¥ó¤Ï -CURRENT ¤È -STABLE¡¢
             ξÊý¤Î¥Ö¥é¥ó¥Á¤ÇÆ°¤«¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤â¤Î¤Ç¤¹¤Î¤Ç¡¢
             ¤â¤·¤½¤ì¤òȯ¸«¤·¤¿¤é &man.send-pr.1;
             ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¥Ð¥°¥ì¥Ý¡¼¥È¤ÎÄó½Ð¤ò¤ª´ê¤¤¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="find-ldso">
           <para>ld.so ¤Ï¤É¤³¤Ë¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>3.1-R °Ê¹ß¤Ê¤É¤Î Elf ²½¤µ¤ì¤¿¥Þ¥·¥ó¤Ç Netscape Navigator ¤Ê¤É¤Î
             aout ·Á¼°¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤òÆ°¤«¤¹¤È¤­¤Ë¤Ï¡¢
             <filename>/usr/libexec/ld.so</filename> ¤È
             aout ¥é¥¤¥Ö¥é¥ê¤Î¥Õ¥¡¥¤¥ë¤¬É¬ÍפǤ¹¡£
             ¤½¤ì¤é¤ÏÇÛÉÛʪ¤Î <literal>compat22</literal> ¤ËǼ¤á¤é¤ì¤Æ¤¤¤Þ¤¹¡£
             <filename>/stand/sysinstall</filename> ¤ä
             <filename>compat22</filename> ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥êÆâ¤Î
             <filename>install.sh</filename> ¤ò»È¤Ã¤Æ
             <literal>compat22</literal>
             ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¹ç¤ï¤»¤Æ 3.1-R ¤È 3.2-R ¤Î ERRATA ¤â¤ªÆɤߤ¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ports-update">
            <para>¥½¡¼¥¹¥³¡¼¥É¤ò¹¹¿·¤·¤Þ¤·¤¿¡£¤µ¤Æ¡¢¥¤¥ó¥¹¥È¡¼¥ëºÑ¤ß¤Î
              ports ¤ò¹¹¿·¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>»ÄÇ°¤Ê¤¬¤é¡¢¥¤¥ó¥¹¥È¡¼¥ëºÑ¤ß¤Î ports ¤ò¹¹¿·¤¹¤ë´Êñ¤Ê
             ÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£<command>pkg_version</command> ¥³¥Þ¥ó¥É¤ò
             ÍѤ¤¤Æ ports ¥Ä¥ê¡¼Ãæ¤Î¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤Ë¹¹¿·¤¹¤ë
             ¥¹¥¯¥ê¥×¥È¤ò¼¡¤Î¤è¤¦¤ËÀ¸À®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>pkg_version <option>-c</option> > <replaceable>/tmp/myscript</replaceable></userinput></screen>
 
           <para>½ÐÎϤµ¤ì¤¿¥¹¥¯¥ê¥×¥È¤ò»È¤¦Á°¤Ë¡¢¼ê¤Ç
             ÊÔ½¸<emphasis>¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó</emphasis>¡£¸½ºß¤Î¥Ð¡¼¥¸¥ç¥ó¤Î
             <command>pkg_version</command> ¤Ç¤Ï¡¢¥¹¥¯¥ê¥×¥È¤ÎÀèƬ¤Ë
             <command>exit</command> ¤òÁÞÆþ¤·¤Æ¶¯À©¤·¤Æ¤¤¤Þ¤¹¡£</para>
 
           <para>¥¹¥¯¥ê¥×¥È¤Î½ÐÎϤˤϡ¢¹¹¿·¤µ¤ì¤¿ packages ¤Ë°Í¸¤¹¤ë
             packages ¤¬µ­ºÜ¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢Êݸ¤·¤Æ¤ª¤­¤Þ¤·¤ç¤¦¡£¤³¤ì¤é¤â
             ¤ä¤Ï¤ê¹¹¿·¤¹¤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£Ä̾¹¹¿·¤¬
             ɬÍפȤʤë¤Î¤Ï¡¢¶¦Í­¥é¥¤¥Ö¥é¥ê¤Î¥Ð¡¼¥¸¥ç¥ó¤¬ÊѲ½¤·¡¢
             ¤½¤Î¥é¥¤¥Ö¥é¥ê¤òÍøÍѤ·¤Æ¤¤¤ë ports ¤¬¿·¤·¤¤¥é¥¤¥Ö¥é¥ê¤òÍѤ¤¤ë¤¿¤á¤Ë
             ºÆ¹½ÃÛ¤¹¤ëɬÍפ¬¤¢¤ë¾ì¹ç¤Ç¤¹¡£</para>
 
           <para>¥·¥¹¥Æ¥à¤¬¾ï»þ²ÔÆ°¤·¤Æ¤¤¤ë¤Ê¤é¤Ð¡¢
             <filename>/etc/periodic.conf</filename> ¤Ë
             <literal>weekly_status_pkg_enable="YES"</literal> ¤ò
             ÀßÄꤷ¤Æ¡¢&man.periodic.8; ¥·¥¹¥Æ¥à¤Ë¤è¤Ã¤ÆËè½µ¹¹¿·¤¬É¬Í×¤Ê ports
             ¤Î°ìÍ÷¤òÀ¸À®¤Ç¤­¤Þ¤¹¡£</para>
         </answer>
       </qandaentry>
     </qandaset>
 </chapter>
 
   <chapter id="kernelconfig">
     <title>¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó</title>
 
     <para>
       <emphasis>Ìõ:
         &a.jp.kiroh;¡¢
         1997 ǯ 11 ·î 10 Æü
       </emphasis>
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="make-kernel">
           <para>¥«¡¼¥Í¥ë¤ò¥«¥¹¥¿¥Þ¥¤¥º¤·¤¿¤¤¤ó¤Ç¤¹¤¬¡¢Æñ¤·¤¤¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             Á´Á³Æñ¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£
             <ulink url="../handbook/kernelconfig.html">¥«¡¼¥Í¥ë¤ÎºÆ¹½ÃÛ</ulink>¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <note>
               <para>¤¦¤Þ¤¯Æ°ºî¤¹¤ë¥«¡¼¥Í¥ë¤¬¤Ç¤­¤¿¤é¡¢
                 ÆüÉÕÆþ¤ê¤Î¥«¡¼¥Í¥ë¤Î¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò
                 <filename>kernel.<replaceable>YYMMDD</replaceable></filename>
                 ¤Î¤è¤¦¤ËºîÀ®¤¹¤ë¤³¤È¤ò¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
                 ¤³¤¦¤·¤Æ¤ª¤±¤Ð¡¢¼¡¤Ë¥«¡¼¥Í¥ë¤Î¹½ÃÛ¤ò¤ä¤Ã¤Æ¤¦¤Þ¤¯¤¤¤«¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤Æ¤â¡¢
                 <filename>kernel.GENERIC</filename> ¤Ë¤ï¤¶¤ï¤¶Ìá¤ëɬÍפ¬¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£
                 ¤³¤ì¤Ï¡¢GENERIC ¥«¡¼¥Í¥ë¤Ç¥µ¥Ý¡¼¥È¤µ¤ì¤Ê¤¤¥Ç¥Ð¥¤¥¹¤«¤éµ¯Æ°¤·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
                 Æä˽ÅÍפǤ¹¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-hw-float">
           <para><literal>_hw_float</literal>
             ¤¬Ìµ¤¤¤Î¤Ç¡¢¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë¤¬¤¦¤Þ¤¯¤¤¤­¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             ¿ä¬¤Ç¤¹¤¬¡¢¿ôÃͱ黻¥³¥×¥í¥»¥Ã¥µ¤ò»ý¤Ã¤Æ¤Ê¤¤¤«¤é¤È»×¤Ã¤Æ¡¢
             <devicename>npx0</devicename> (&man.npx.4; »²¾È)
             ¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤«¤éºï½ü¤·¤Æ¤·¤Þ¤Ã¤¿¤Î¤Ç¤Ï¤Ê¤¤¤Ç¤·¤ç¤¦¤«?
             <devicename>npx0</devicename> ¤Ï<emphasis>ɬ¿Ü</emphasis>¤Ç¤¹¡£
             ¥³¥×¥í¥»¥Ã¥µ¤¬¤Ê¤¯¤Æ¤â¡¢<devicename>npx0</devicename>
             ¥Ç¥Ð¥¤¥¹¤Ïºï½ü¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="why-kernel-big">
           <para>¤ï¤¿¤·¤Î¥«¡¼¥Í¥ë¤Ï¤É¤¦¤·¤Æ¤³¤ó¤Ê¤ËÂ礭¤¤ (10MB °Ê¾å)
             ¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>¤³¤ì¤Ï<emphasis>¥Ç¥Ð¥Ã¥°¥â¡¼¥É</emphasis>¤Ç¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤·¤Æ¤¤¤ë¤³¤È¤¬¸¶°ø¤Ç¤¹¡£
             ¥Ç¥Ð¥Ã¥°¥â¡¼¥É¤Ç¹½ÃÛ¤µ¤ì¤¿¥«¡¼¥Í¥ë¤Ï¡¢
             ¥Ç¥Ð¥Ã¥°¤ËÍѤ¤¤é¤ì¤ëËÄÂç¤Ê¥·¥ó¥Ü¥ë¾ðÊó¤ò´Þ¤ó¤Ç¤¤¤ë¤¿¤á¡¢
             ¥«¡¼¥Í¥ë¤Î¥µ¥¤¥º¤¬Èó¾ï¤ËÂ礭¤¯¤Ê¤ê¤Þ¤¹¡£
             ¤¿¤À¤· FreeBSD 3.0 ¤È¤½¤ì°Ê¹ß¤Î¥·¥¹¥Æ¥à¤Î¾ì¹ç¤Ï
             ¥«¡¼¥Í¥ë¤Î¥µ¥¤¥º¤Ï¾®¤µ¤¯¤Ê¤ê¤Þ¤¹¤·¡¢
             ¥Ç¥Ð¥Ã¥°¥«¡¼¥Í¥ë¤ò¼Â¹Ô¤¹¤ë»þ¤Î¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤ÎÄã²¼¤â¤¢¤ê¤Þ¤»¤ó¡£
             ¤Þ¤¿¡¢¤½¤Î¥«¡¼¥Í¥ë¤Ï¥·¥¹¥Æ¥à¤¬¥Ñ¥Ë¥Ã¥¯¤·¤¿¾ì¹ç¤ËÍ­ÍѤǤ¹¡£</para>
 
           <para>¤·¤«¤·¡¢ÍÆÎ̤µ¤Ê¥Ç¥£¥¹¥¯¤Ç¥·¥¹¥Æ¥à¤ò±¿ÍѤ·¤Æ¤¤¤¿¤ê¡¢
             ñ¤Ë¥Ç¥Ð¥Ã¥°¥«¡¼¥Í¥ë¤ò¼Â¹Ô¤·¤¿¤¯¤Ê¤¤¾ì¹ç¤Ï¡¢
             °Ê²¼¤ÎξÊý¤¬Åö¤Æ¤Ï¤Þ¤Ã¤Æ¤¤¤ë¤«¤É¤¦¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <itemizedlist>
             <listitem>
               <para>¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤Î¹Ô¤¬½ñ¤«¤ì¤Æ¤¤¤Ê¤¤¤³¤È¡£</para>
 
               <programlisting>makeoptions DEBUG=-g</programlisting>
             </listitem>
 
             <listitem>
               <para><command>config</command> ¤ò¼Â¹Ô¤¹¤ëºÝ¡¢
                 <option>-g</option> ¥ª¥×¥·¥ç¥ó¤òÉÕ¤±¤Æ¤¤¤Ê¤¤¤³¤È¡£</para>
             </listitem>
           </itemizedlist>
 
           <para>¾å¤Ë½ñ¤«¤ì¤¿»ØÄê¤ÏξÊý¤È¤â¥«¡¼¥Í¥ë¤ò¥Ç¥Ð¥Ã¥°¥â¡¼¥É¤Ç¹½ÃÛ¤¹¤ë¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
             ¾å¤Î¼ê½ç¤ò½¾¤Ã¤Æ¤¤¤ë¸Â¤ê¡¢¥«¡¼¥Í¥ë¤òÉáÄ̤˹½ÃÛ¤·¤Æ¥µ¥¤¥º¤Î¾®¤µ¤Ê¥«¡¼¥Í¥ë¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤½¤Î¾ì¹ç¤Î¥«¡¼¥Í¥ë¥µ¥¤¥º¤Ï¡¢¤ª¤è¤½ 1.5MB ¤«¤é 2MB ÄøÅ٤ˤʤê¤Þ¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multiport-serial-interrupts">
           <para>
             ¥Þ¥ë¥Á¥Ý¡¼¥È¥·¥ê¥¢¥ë¤Î¥³¡¼¥É¤Ç³ä¤ê¹þ¤ß¤¬¾×Æͤ·¤Æ¤¤¤Þ¤¹¡£
           </para>
         </question>
 
         <answer>
           <para>
             ¥Þ¥ë¥Á¥Ý¡¼¥È¥·¥ê¥¢¥ë¤ò
             ¥µ¥Ý¡¼¥È¤¹¤ë¥³¡¼¥É¤ò´Þ¤ó¤À¥«¡¼¥Í¥ë¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤è¤¦¤È¤¹¤ë¤È¡¢
             ºÇ½é¤Î¥Ý¡¼¥È¤À¤±¸¡½Ð¤µ¤ì¡¢
             »Ä¤ê¤Î¥Ý¡¼¥È¤Ï³ä¤ê¹þ¤ß¤Î¶¥¹ç¤Î¤¿¤á¥¹¥­¥Ã¥×¤µ¤ì¤¿¤È¸À¤ï¤ì¤Þ¤¹¡£
             ¤É¤¦¤ä¤Ã¤¿¤é¤¤¤¤¤Ç¤·¤ç¤¦¤«?
           </para>
 
           <para>
             ¤³¤³¤Ç¤ÎÌäÂê¤Ï¡¢FreeBSD
             ¤Ë¤Ï¥Ï¡¼¥É¥¦¥§¥¢¤Þ¤¿¤Ï¥½¥Õ¥È¥¦¥§¥¢¤Î¶¥¹ç¤Ë¤è¤ê¡¢
             ¥«¡¼¥Í¥ë¤¬¥¯¥é¥Ã¥·¥å¤¹¤ë¤Î¤òËɤ°¥³¡¼¥É¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¤È¤¤¤¦ÅÀ¤Ç¤¹¡£
             ²ò·è¤¹¤ë¤Ë¤Ï¡¢ºÇ½é¤Î¥Ý¡¼¥È¤Ë¤À¤± IRQ ¤ÎÀßÄê¤ò½ñ¤­¡¢
             »Ä¤ê¤Ï IRQ ¤ÎÀßÄê¤òºï½ü¤·¤Þ¤¹¡£
             °Ê²¼¤ËÎã¤ò¼¨¤·¤Þ¤¹¡£
           </para>
 
           <programlisting># Multiport high-speed serial line - 16550 UARTS
 #
 device sio2 at isa? port 0x2a0 tty irq 5 flags 0x501 vector siointr
 device sio3 at isa? port 0x2a8 tty flags 0x501 vector siointr
 device sio4 at isa? port 0x2b0 tty flags 0x501 vector siointr
 device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="generic-kernel-build-failure">
           <para>¥«¡¼¥Í¥ë¤ò¹½Ãۤˤ¤¤Ä¤â¼ºÇÔ¤·¤Þ¤¹¡£
             GENERIC ¥«¡¼¥Í¥ë¤â¹½ÃۤǤ­¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>¤µ¤Þ¤¶¤Þ¤ÊÍýͳ¤¬¹Í¤¨¤é¤ì¤Þ¤¹¡£°Ê²¼¡¢½ç¤ËÎóµ­¤·¤Þ¤¹¡£</para>
 
           <itemizedlist>
             <listitem>
               <para>¤¢¤Ê¤¿¤Ï¿·¤·¤¤
                 <command>make buildkernel</command> ¤ä
                 <command>make installkernel</command>
                 ¥¿¡¼¥²¥Ã¥È¤ò»È¤ï¤º¡¢
                 ¸½ºßÁö¤Ã¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤ò¹½ÃÛ¤·¤¿»þ¤È°Û¤Ê¤ë¥½¡¼¥¹¥Ä¥ê¡¼¤ò
                 ¹½ÃÛ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë (¤¿¤È¤¨¤Ð¡¢4.0-RELEASE ¤Î¥·¥¹¥Æ¥à¾å¤Ç
                 4.3-RELEASE ¤ò¹½ÃÛ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë) ¤Î¤Ç¤Ï¤Ê¤¤¤Ç¤·¤ç¤¦¤«?
                 ¤â¤·¥·¥¹¥Æ¥à¤ò¥¢¥Ã¥×¥°¥ì¡¼¥É¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤Î¤Ê¤é¡¢
                 <filename>/usr/src/UPDATING</filename> ¥Õ¥¡¥¤¥ë¤ò
                 <quote>¶¦Ä̹àÌÜ (COMMON ITEMS)</quote>
                 Àá¤ËÃí°Õ¤·¤Ê¤¬¤éºÇ¸å¤Þ¤Ç¤ªÆɤߤ¯¤À¤µ¤¤¡£</para>
             </listitem>
 
             <listitem>
               <para>¤¢¤Ê¤¿¤Ï¿·¤·¤¤ <command>make buildkernel</command> ¤ä
                 <command>make installkernel</command> ¥¿¡¼¥²¥Ã¥È¤ò
                 »È¤Ã¤Æ¤¤¤ë¤Î¤Ë¤â´Ø¤ï¤é¤º¡¢
                 <command>make buildworld</command>
                 ¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤Ê¤¤¤Î¤Ç¤Ï¤Ê¤¤¤Ç¤·¤ç¤¦¤«?
                 <command>make buildkernel</command> ¥¿¡¼¥²¥Ã¥È¤Ï¡¢
                 <command>make buildworld</command>
                 ¥¿¡¼¥²¥Ã¥È¤Ë¤è¤Ã¤Æºî¤é¤ì¤ë¥Õ¥¡¥¤¥ë¤Ë°Í¸¤·¤Æ¤¤¤Þ¤¹
                 ¤½¤Î¤¿¤á¡¢<command>make buildkernel</command>
                 ¤¬Àµ¾ï¤Ë½ªÎ»¤¹¤ë¤¿¤á¤Ë¤Ï
                 <command>make buildworld</command>
                 ¥¿¡¼¥²¥Ã¥È¤¬Àµ¾ï¤Ë´°Î»¤·¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
             </listitem>
 
             <listitem>
               <para>¹½ÃÛ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤Î¤¬
                 <link linkend="stable">FreeBSD-STABLE</link>
                 ¤À¤Ã¤¿¤È¤·¤Æ¤â¡¢¤¢¤Ê¤¿¤¬Æþ¼ê¤·¤¿¥½¡¼¥¹¥Ä¥ê¡¼¤¬²¿¤é¤«¤ÎÍýͳ¤Ç
                 ½ñ¤­´¹¤ï¤Ã¤¿¤ê¡¢²õ¤ì¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë¤Î¤«¤âÃΤì¤Þ¤»¤ó¡£
                 <link linkend="stable">FreeBSD-STABLE</link>
                 ¤Ï¤Û¤È¤ó¤É¤Î¾ì¹ç¡¢¤­¤Á¤ó¤È¹½ÃۤǤ­¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢
                 ³Î¼Â¤Ë¹½ÃÛ²Äǽ¤Ç¤¢¤ë¤³¤È¤¬Êݾڤµ¤ì¤Æ¤¤¤ë¤Î¤Ï
                 ¥ê¥ê¡¼¥¹ÈǤÀ¤±¤Ç¤¹¡£°ìÅÙ¥½¡¼¥¹¥Ä¥ê¡¼¤òºÆ¼èÆÀ¤·¤Æ¡¢
                 ÌäÂ꤬²ò·è¤·¤Ê¤¤¤«¤É¤¦¤«»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
                 ¤Þ¤¿¡¢¤¢¤ë¥µ¡¼¥Ð¤«¤é¼èÆÀ¤·¤¿»þ¤ËÌäÂ꤬ȯÀ¸¤·¤¿¤é¡¢
                 Ê̤Υµ¡¼¥Ð¤ò»î¤¹¤Î¤â¸ú²Ì¤¬¤¢¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£</para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="admin">
     <title>¥·¥¹¥Æ¥à´ÉÍý</title>
 
     <para>
       <emphasis>Ìõ:
         ¤Ë¤·¤« <email>nishika@cheerful.com</email>¡¢
         1997 ǯ 11 ·î 12 Æü</emphasis>
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="startup-config-files">
           <para>¥·¥¹¥Æ¥à¥¹¥¿¡¼¥È¥¢¥Ã¥×¥Õ¥¡¥¤¥ë¤Ï¤É¤³¤Ë¤¢¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 2.0.5R ¤«¤é 2.2.1R ¤Þ¤Ç¤Ï¡¢
             ¥×¥é¥¤¥Þ¥ê¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ï
             <filename>/etc/sysconfig</filename> ¤Ë¤¢¤ê¤Þ¤¹¡£
             ¥ª¥×¥·¥ç¥ó¤Ï¤¹¤Ù¤Æ¤³¤Î¥Õ¥¡¥¤¥ë¤ÇÀßÄꤵ¤ì¡¢Â¾¤Î
             <filename>/etc/rc</filename> (&man.rc.8; »²¾È) ¤ª¤è¤Ó
             <filename>/etc/netstart</filename> ¤È¤¤¤Ã¤¿
             ¥Õ¥¡¥¤¥ë¤Ï¤³¤ì¤òÆɤ߹þ¤à¤À¤±¤Ç¤¹¡£
           </para>
 
           <para>
             ¥Õ¥¡¥¤¥ë <filename>/etc/sysconfig</filename>
             ¤ò¸«¤Æ¡¢¥·¥¹¥Æ¥à¤ËŬ¹ç¤¹¤ë¤è¤¦¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤³¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢
             ¤½¤ì¤¾¤ì¤Î¾ì½ê¤Ë²¿¤ò½ñ¤±¤Ð¤¤¤¤¤Î¤«¤òɽ¤¹¥³¥á¥ó¥È¤¬¤¿¤¯¤µ¤ó½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             FreeBSD 2.2.2 ¤«¤é 3.0 ¤Þ¤Ç¤Î¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
             <filename>/etc/sysconfig</filename> ¤Ï¡¢
             ¤è¤êʬ¤ê¤ä¤¹¤¤Ì¾Á°¤Î
             &man.rc.conf.5;
             ¤Ë²þ̾¤µ¤ì¡¢¤½¤ì¤Ë½¾¤Ã¤Æ½ñ¼°¤â¤¤¤¯¤Ö¤ó²þ¤á¤é¤ì¤Æ¤¤¤Þ¤¹¡£
             <filename>/etc/netstart</filename> ¤â
             <filename>/etc/rc.network</filename> ¤Ë²þ̾¤µ¤ì¡¢
             Á´Éô¤Î¥Õ¥¡¥¤¥ë¤ò
             <command>cp /usr/src/etc/rc* /etc</command>
             ¤Ç°ìÅ٤˥³¥Ô¡¼¤¹¤ë¤³¤È¤¬½ÐÍè¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>FreeBSD 3.1 ¤È¤½¤ì°Ê¹ß¤Ç¤Ï¡¢
             <filename>/etc/rc.conf</filename> ¤¬
             <filename>/etc/defaults/rc.conf</filename> ¤Ë°ÜÆ°¤·¤Þ¤·¤¿¡£
             <emphasis>¤³¤Î¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó!</emphasis>
             Âå¤ï¤ê¤Ë¡¢
             <filename>/etc/defaults/rc.conf</filename>
             ¤ÎÃæ¤ÇÊѤ¨¤¿¤¤¥¨¥ó¥È¥ê¤Î¹Ô¤ò
             <filename>/etc/rc.conf</filename> ¤Ë¥³¥Ô¡¼¤·¡¢
             ¤½¤³¤ÇÊѹ¹¤¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>¤¿¤È¤¨¤Ð named ¤òµ¯Æ°¤·¤¿¤¤¤È¤·¤Þ¤·¤ç¤¦¡£
             FreeBSD 3.1 ¤«¤½¤ì°Ê¹ß¤Î¥·¥¹¥Æ¥à¤Ç FreeBSD ÉÕ°¤Î DNS
             ¥µ¡¼¥Ð¤òµ¯Æ°¤¹¤ë¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤¹¤ë¤À¤±¤Ç¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>echo named_enable="YES" &gt;&gt;
               /etc/rc.conf</userinput></screen>
 
           <para>FreeBSD 3.1 ¤«¤½¤ì°Ê¹ß¤Ç¥í¡¼¥«¥ë¥µ¡¼¥Ó¥¹¤òµ¯Æ°¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
             <filename>/usr/local/etc/rc.d</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥·¥§¥ë¥¹¥¯¥ê¥×¥È¤òÃÖ¤­¤Þ¤¹¡£
             ¥·¥§¥ë¥¹¥¯¥ê¥×¥È¤Ïµ¯Æ°²Äǽ¤ËÀßÄꤷ¡¢¥Õ¥¡¥¤¥ë̾¤¬ .sh ¤Ç½ª¤ï¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             FreeBSD 3.0 ¤È¤½¤ì°ÊÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï¡¢
             <filename>/etc/rc.local</filename> ¤òÊÔ½¸¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>¥Õ¥¡¥¤¥ë <filename>/etc/rc.serial</filename>
             ¤Ï¥·¥ê¥¢¥ë¥Ý¡¼¥È¤Î½é´ü²½
             (¤¿¤È¤¨¤Ð¥Ý¡¼¥È¤ÎÀßÄê¤ò¸ÇÄꤷ¤¿¤êÅù¡¹)
             ¤Î¤¿¤á¤Ë¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>¥Õ¥¡¥¤¥ë <filename>/etc/rc.i386</filename> ¤Ï iBCS2
             ¥¨¥ß¥å¥ì¡¼¥·¥ç¥ó¤Î¤è¤¦¤Ê
             Intel ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¸ÇÍ­¤ÎÀßÄê¤ä¡¢
             PC ¥·¥¹¥Æ¥à¥³¥ó¥½¡¼¥ëÀßÄê¤Î¤¿¤á¤Ë¤¢¤ê¤Þ¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="adding-users">
           <para>´Êñ¤Ë¥æ¡¼¥¶¤òÄɲ乤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤¤¤¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             &man.adduser.8; ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
             ¤Þ¤¿¡¢&man.pw.8; ¥³¥Þ¥ó¥É¤òÍѤ¤¤ë¤³¤È¤Ç¡¢¤µ¤é¤ËºÙ¤«¤¤Áàºî¤¬²Äǽ¤Ç¤¹¡£
           </para>
 
           <para>
             ¥æ¡¼¥¶¤òºï½ü¤¹¤ë¤Ë¤Ï &man.rmuser.8; ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
             ·«¤êÊÖ¤·¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢&man.pw.8; ¤Ç¤â¹½¤¤¤Þ¤»¤ó¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="removable-drives">
           <para>¿·¤·¤¤¥ê¥à¡¼¥Ð¥Ö¥ë¥É¥é¥¤¥Ö¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢¤É¤¦¤ä¤Ã¤Æ»È¤¦¤Î?</para>
         </question>
 
         <answer>
           <para>
             ¤½¤Î¥ê¥à¡¼¥Ð¥Ö¥ë¥É¥é¥¤¥Ö¤¬ ZIP ¤Ç¤¢¤ì EZ drive ¤Ç¤¢¤ì
             (¤¢¤ë¤¤¤Ï¤â¤·¤½¤¦¤¤¤¦É÷¤Ë»È¤¤¤¿¤¤¤Î¤Ê¤é¡¢¥Õ¥í¥Ã¥Ô¡¼¤Ç¤¢¤ì)¡¢
             ¤Þ¤¿¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ç¤¢¤ì¡¢°ìö¥·¥¹¥Æ¥à¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æǧ¼±¤µ¤ì¡¢
             ¥«¡¼¥È¥ê¥Ã¥¸¡¢¥Õ¥í¥Ã¥Ô¡¼Åù¡¹¤¬ÁÞÆþ¤µ¤ì¤Æ¤¤¤ì¤Ð¡¢
             ¤³¤È¤Ï¤É¤Î¥Ç¥Ð¥¤¥¹¤Ç¤âÁ´¤¯Æ±¤¸¤è¤¦¤Ë¿Ê¤ß¤Þ¤¹¡£
           </para>
 
           <para><anchor id="disklabel"/>
               (¤³¤Î¥»¥¯¥·¥ç¥ó¤Ï<ulink url="http://www.vmunix.com/mark/FreeBSD/ZIP-FAQ.html">Mark Mayo's ZIP FAQ</ulink> ¤Ë´ð¤Å¤¤¤Æ¤¤¤Þ¤¹)
           </para>
 
           <para>
             ZIP ¥É¥é¥¤¥Ö¤ä¥Õ¥í¥Ã¥Ô¡¼¤Ç¡¢¤¹¤Ç¤Ë DOS ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç
             ¥Õ¥©¡¼¥Þ¥Ã¥È¤·¤Æ¤¢¤ë¾ì¹ç¡¢¼¡¤Î¥³¥Þ¥ó¥É¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤³¤ì¤Ï¥Õ¥í¥Ã¥Ô¡¼¤Î¾ì¹ç¤Ç¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>mount -t msdos /dev/fd0c /floppy</userinput></screen>
 
           <para>½Ð²Ù»þ¤ÎÀßÄê¤Î ZIP ¥Ç¥£¥¹¥¯¤Ç¤Ï¤³¤¦¤Ç¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>mount -t msdos /dev/da2s4 /zip</userinput></screen>
 
           <para>
             ¤½¤Î¾¤Î¥Ç¥£¥¹¥¯¤Ë´Ø¤·¤Æ¤Ï¡¢&man.fdisk.8; ¤ä
             <filename>/stand/sysinstall</filename> ¤ò»È¤Ã¤Æ¡¢
             ¤É¤Î¤è¤¦¤Ë¥ì¥¤¥¢¥¦¥È¤µ¤ì¤Æ¤¤¤ë¤«³Î¤«¤á¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             °Ê¹ß¤Ï ZIP ¥É¥é¥¤¥Ö¤¬ 3 ÈÖÌܤΠSCSI ¥Ç¥£¥¹¥¯¤Ç¡¢
             da2 ¤Èǧ¼±¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤ÎÎã¤Ç¤¹¡£
           </para>
 
           <para>
             ¾¿Í¤È¶¦Í­¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¥Õ¥í¥Ã¥Ô¡¼¤ä¥ê¥à¡¼¥Ð¥Ö¥ë¥Ç¥£¥¹¥¯
             ¤Ç¤Ê¤±¤ì¤Ð¡¢BSD ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºÜ¤»¤Æ¤·¤Þ¤¦¤Î¤¬Îɤ¤¹Í¤¨¤Ç¤·¤ç¤¦¡£
             ¥í¥ó¥°¥Õ¥¡¥¤¥ë̾¤â¥µ¥Ý¡¼¥È¤µ¤ì¡¢¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤Ï¾¯¤Ê¤¯¤È¤â
             2 Çܤϸþ¾å¤·¤Þ¤¹¤·¡¢¤ª¤Þ¤±¤Ë¤º¤Ã¤È°ÂÄꤷ¤Æ¤¤¤Þ¤¹¡£
             ¤Þ¤ººÇ½é¤Ë¡¢DOS ¥ì¥Ù¥ë¤Ç¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó <filename>/</filename>
             ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò̵¸ú¤Ë¤·¤Æ¤ª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£»ÈÍѤ¹¤ë¤Î¤Ï
             <command>fdisk</command> ¤Ç¤â
             <filename>/stand/sysinstall</filename> ¤Ç¤â·ë¹½¤Ç¤¹¡£
             Ê£¿ô¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤òÆþ¤ì¤ë¤³¤È¤ò¹Íθ¤¹¤ë
             ɬÍפ¬¤Ê¤¤¤è¤¦¤ÊÍÆÎ̤µ¤Ê¥É¥é¥¤¥Ö¤Î¾ì¹ç¤Ï¡¢
             ¼¡¤Î¤è¤¦¤Ë <acronym>FAT</acronym> ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë (¥¹¥é¥¤¥¹)
             Á´ÂΤòÈô¤Ð¤·¤Æ¡¢BSD
             ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥óÀßÄê¤ò¹Ô¤¦¤À¤±¤ÇÎɤ¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/rda2 count=2</userinput>
 &prompt.root; <userinput>disklabel -Brw da2 auto</userinput></screen>
 
           <para>
             Ê£¿ô¤Î BSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¤Ä¤¯¤ë¾ì¹ç¡¢
             <command>disklabel</command> ¤«
             <filename>/stand/sysinstall</filename> ¤ò»È¤¤¤Þ¤¹¡£
             ¸ÇÄê¥Ç¥£¥¹¥¯¾å¤Ë¥¹¥ï¥Ã¥×Îΰè¤ò²Ã¤¨¤ë¾ì¹ç¡¢
             ¤½¤¦¤¤¤¦¤³¤È¤ò¤·¤¿¤¤¤È»×¤¦¤Î¤Ï¤â¤Ã¤È¤â¤Ç¤¹¤¬¡¢
             ZIP ¤Î¤è¤¦¤Ê¥ê¥à¡¼¥Ð¥Ö¥ë¥É¥é¥¤¥Ö¤Î¾å¤Ç¤Ï¤½¤¦¤¤¤¦¹Í¤¨¤ÏÉÔŬÀÚ
             ¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ºÇ¸å¤Ë¡¢¿·¤·¤¤¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¤Ä¤¯¤ê¤Þ¤¹¡£¥Ç¥£¥¹¥¯Á´ÂΤò»ÈÍѤ¹¤ë
             ZIP ¥É¥é¥¤¥Ö¤Î¾ì¹ç¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>newfs /dev/rda2c</userinput></screen>
 
           <para>¼¡¤Ë¥Þ¥¦¥ó¥È¤·¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>mount /dev/da2c /zip</userinput></screen>
 
           <para>¤Þ¤¿¡¢¼¡¤Î¤è¤¦¤Ê¹Ô¤ò
             <filename>/etc/fstab</filename> (&man.fstab.5; »²¾È)
             ¤ËÆþ¤ì¤Æ¤ª¤¯¤Î¤âÎɤ¤¹Í¤¨¤Ç¤·¤ç¤¦¡£
             <command>mount /zip</command>
             ¤ÈÆþÎϤ¹¤ë¤À¤±¤Ç¥Þ¥¦¥ó¥È¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>/dev/da2c /zip ffs rw,noauto 0 0</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="root-not-found-cron-errors">
           <para>¼«Ê¬¤Î crontab ¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¤¿¸å
             <errorname>root: not found</errorname>
             ¤Î¤è¤¦¤Ê¥á¥Ã¥»¡¼¥¸¤¬±ä¡¹¤Èɽ¼¨¤µ¤ì¤ë¤Î¤Ç¤¹¤¬¡¢
             ¤³¤ì¤Ï¤Ê¤¼¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¤³¤ì¤ÏÄ̾¥·¥¹¥Æ¥à crontab (<filename>/etc/crontab</filename>)
             ¤òÊÔ½¸¤·¡¢&man.crontab.1; ¤ò»È¤Ã¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¾ì¹ç¤Ëµ¯¤³¤ê¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>crontab /etc/crontab</userinput></screen>
 
           <para>¤³¤ÎÊýË¡¤ÏÀµ¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£
             ¥·¥¹¥Æ¥à crontab ¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï &man.crontab.1;
             ¤¬¹¹¿·¤¹¤ë³Æ¥æ¡¼¥¶¤Î crontab ¤È¤Ï°Û¤Ê¤ê¤Þ¤¹
             (¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎÁê°ãÅÀ¤Î¾ÜºÙ¤Ï &man.crontab.5;
             ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹)¡£</para>
 
           <para>
             ¤â¤·¤³¤Î¤è¤¦¤ÊÁàºî¤ò¤·¤Æ¤·¤Þ¤Ã¤¿¤Ê¤é¡¢
             ¤¢¤é¤¿¤Ê crontab ¤Ï¸í¤Ã¤¿¥Õ¥©¡¼¥Þ¥Ã¥È¤Î
             <filename>/etc/crontab</filename>
             ¤Î¥³¥Ô¡¼¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë¤«¤é¤Ç¤¹¡£
             °Ê²¼¤Î¥³¥Þ¥ó¥É¤Çºï½ü¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>crontab -r</userinput></screen>
 
           <para>
             º£ÅÙ <filename>/etc/crontab</filename> ¤òÊÔ½¸¤¹¤ë»þ¤Ï¡¢
             ¤½¤ÎÊѹ¹¤ò &man.cron.8; ¤ËÅÁ¤¨¤ë¤è¤¦¤ÊÁàºî¤ò¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
             &man.cron.8; ¤Ï¡¢¼«Æ°Åª¤Ë¤½¤ÎÊѹ¹¤òǧ¼±¤¹¤ë¤«¤é¤Ç¤¹¡£</para>
 
           <para>
             ¤â¤·¤¢¤Ê¤¿¤¬²¿¤«¤ò°ìÆü°ì²ó¡¢¤¢¤ë¤¤¤Ï°ì½µ´Ö¤ä°ì¥ö·î¤Ë°ì²ó¤À¤±
             ¼Â¹Ô¤µ¤»¤¿¤¤¤Ê¤é¡¢¥·¥§¥ë¥¹¥¯¥ê¥×¥È¤ò
             <filename>/usr/local/etc/periodic</filename> ¤ËÄɲä·¡¢
             &man.periodic.8; ¥³¥Þ¥ó¥É¤Ë¥·¥¹¥Æ¥à¤Î cron ¥¹¥±¥¸¥å¡¼¥ë¤«¤é
             ¾¤ÎÄê´üŪ¤Ê¥·¥¹¥Æ¥à¤Î¥¿¥¹¥¯¤È¤È¤â¤Ë
             ¼Â¹Ô¤µ¤»¤¿¤Û¤¦¤¬Îɤ¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>¤³¤Î¥¨¥é¡¼¤Î¼ÂºÝ¤Î¸¶°ø¤Ï¡¢¥·¥¹¥Æ¥à crontab ¤Ë¤Ï
             ¤É¤Î¥æ¡¼¥¶¸¢¸Â¤Ç¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë¤«¤ò»ØÄꤹ¤ë;ʬ¤Ê¥Õ¥£¡¼¥ë¥É¤¬¤¢¤ë¤³¤È¤Ë¤è¤ë¤â¤Î¤Ç¤¹¡£
             FreeBSD ¤ËźÉÕ¤µ¤ì¤Æ¤¤¤ëɸ½à¤Î¥·¥¹¥Æ¥à crontab ¤Ë¤Ï¡¢
             ¤¹¤Ù¤Æ¤Î¥¨¥ó¥È¥ê¤Ë <username>root</username> ¤¬½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤³¤Î crontab ¤¬ <username>root</username> ¥æ¡¼¥¶¤Î crontab
             (¥·¥¹¥Æ¥à crontab ¤È¤Ï <emphasis>°Û¤Ê¤ê¤Þ¤¹</emphasis>)
             ¤È¤·¤Æ»È¤ï¤ì¤¿¾ì¹ç¡¢&man.cron.8; ¤Ï <literal>root</literal>
             ¤ò¼Â¹Ô¤¹¤ë¥³¥Þ¥ó¥É¤ÎºÇ½é¤Îñ¸ì¤À¤Èǧ¼±¤·¤Þ¤¹¤¬¡¢
             ¤½¤Î¤è¤¦¤Ê¥³¥Þ¥ó¥É¤Ï¸ºß¤·¤Ê¤¤¤Î¤Ç¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="su-wheel-group">
           <para>&man.su.1; ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ
             <username>root</username> ¤Ë¤Ê¤í¤¦¤È¤¹¤ë¤È¡¢
             su ¤¬ <errorname>you are not in the correct group to
             su root</errorname> ¤È·Ù¹ð¤·¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>¤³¤ì¤Ï¡¢¥»¥­¥å¥ê¥Æ¥£¾å¤Îµ¡Ç½¤Ç¤¹¡£su ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ
             <username>root</username> (¤Þ¤¿¤Ï¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¸¢¸Â¤ò»ý¤Ä
             ¾¤Î¥¢¥«¥¦¥ó¥È) ¤Ë¤Ê¤ë¤Ë¤Ï¡¢<groupname>wheel</groupname>
             ¥°¥ë¡¼¥×¤Ë½ê°¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤³¤Îµ¡Ç½¤¬¤Ê¤¤¤È¡¢
             ¥·¥¹¥Æ¥à¤Ë¥¢¥«¥¦¥ó¥È¤¬¤¢¤Ã¤Æ <username>root</username> ¤Î
             ¥Ñ¥¹¥ï¡¼¥É¤ò¸«¤Ä¤±¤µ¤¨¤¹¤ì¤Ð¡¢Ã¯¤Ç¤â¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¸¢¸Â¤Ç
             ¥·¥¹¥Æ¥à¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤Æ¤·¤Þ¤¤¤Þ¤¹¡£¤³¤Îµ¡Ç½¤¬¤¢¤ë¾ì¹ç¤Ï¡¢
             ɬ¤º¤·¤â¤½¤¦¤Ï¤Ê¤ê¤Þ¤»¤ó¡£<groupname>wheel</groupname> ¥°¥ë¡¼¥×¤Ë
             ½ê°¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢&man.su.1; ¤¬¥Ñ¥¹¥ï¡¼¥É¤ÎÆþÎϤ¹¤é
             µñÈݤ¹¤ë¤«¤é¤Ç¤¹¡£</para>
 
           <para>狼¤¬ <username>root</username> ¤Ë su ¤Ç¤­¤ë¤è¤¦¤Ë
             ¤¹¤ë¤Ë¤Ï¡¢¤½¤Î¿Í¤ò <groupname>wheel</groupname> ¥°¥ë¡¼¥×¤ËÄɲ䷤Ƥ¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="rcconf-readonly">
           <para><filename>rc.conf</filename> ¤ä¤½¤Î¾¤Î
             ¥¹¥¿¡¼¥È¥¢¥Ã¥×¥Õ¥¡¥¤¥ë¤ò½ñ¤­´Ö°ã¤¨¤Æ¤·¤Þ¤¤¤Þ¤·¤¿¡£
             ¤·¤«¤â¤½¤Î¤¿¤á¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥ê¡¼¥É¥ª¥ó¥ê¡¼¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤Æ¤¤¤Æ
             ÊÔ½¸¤¬¤Ç¤­¤Þ¤»¤ó¡£¤É¤¦¤¹¤ì¤Ð¤¤¤¤¤Ç¤¹¤«?</para>
         </question>
 
         <answer><para>
             ¥·¥§¥ë¤Î¥Ñ¥¹Ì¾¤òÆþÎϤ¹¤ë¥×¥í¥ó¥×¥È¤¬É½¼¨¤µ¤ì¤¿¤È¤­¤Ë¡¢
             ñ¤Ë <literal>ENTER</literal> ¤ò²¡¤·¡¢<command>mount /</command> ¤ò
             ¼Â¹Ô¤·¤Æ¤½¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºÆ¥Þ¥¦¥ó¥È¤µ¤»¤Þ¤¹¡£
             ¤Þ¤¿¡¢¤ªµ¤¤ËÆþ¤ê¤Î¥¨¥Ç¥£¥¿¤¬¤¢¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò
             ¥Þ¥¦¥ó¥È¤¹¤ë¤¿¤á¤Ë <command>mount -a -t ufs</command> ¤ò
             ¤¹¤ëɬÍפ¬¤¢¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£¤¢¤Ê¤¿¤Î¤ªµ¤¤ËÆþ¤ê¤Î¥¨¥Ç¥£¥¿¤¬
             ¥Í¥Ã¥È¥ï¡¼¥¯¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ë¤¢¤ë¾ì¹ç¤Ï¡¢
             ¥Í¥Ã¥È¥ï¡¼¥¯¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Þ¥¦¥ó¥È¤¹¤ëÁ°¤Ë¥Í¥Ã¥È¥ï¡¼¥¯¤ò
             ¼êÆ°¤ÇÀßÄꤹ¤ë¤«¡¢&man.ed.1; ¤Î¤è¤¦¤Ê¥í¡¼¥«¥ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¤¢¤ë
             ¥¨¥Ç¥£¥¿¤ò»È¤¦¤«¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
           <para>&man.vi.1; ¤ä &man.emacs.1; ¤ÎÍͤʥե륹¥¯¥ê¡¼¥ó¥¨¥Ç¥£¥¿¤ò
             »È¤¦¤Ä¤â¤ê¤Ê¤é <command>export TERM=cons25</command> ¤È
             ¤ä¤Ã¤Æ¥¨¥Ç¥£¥¿¤¬ &man.termcap.5; ¥Ç¡¼¥¿¥Ù¡¼¥¹¤«¤éÀµ¤·¤¤
             ¥Ç¡¼¥¿¤òÆɤ߼è¤ì¤ë¤è¤¦¤Ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
           <para>¤³¤ì¤ò¹Ô¤Ã¤¿¤¢¤È¤Ï¤¤¤Ä¤â¤ÈƱÍÍ¡¢
             <filename>/etc/rc.conf</filename>
             ¤òÊÔ½¸¤·¤Æ´Ö°ã¤¤¤òÄûÀµ¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¥«¡¼¥Í¥ëµ¯Æ°¥á¥Ã¥»¡¼¥¸¤Îľ¸å¤Ëɽ¼¨¤µ¤ì¤¿¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Ë¤Ï¡¢
             ÌäÂê¤Îµ¯¤³¤Ã¤¿¥Õ¥¡¥¤¥ëÆâ¤Ç¤Î¹ÔÈÖ¹æ¤òɽ¼¨¤µ¤ì¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mount-dos">
           <para>¤É¤Î¤è¤¦¤Ë¤·¤¿¤é DOS ¤Î³ÈÄ¥¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¥Þ¥¦¥ó¥È¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             DOS ³ÈÄ¥¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ï¡¢
             ¤¹¤Ù¤Æ¤Î´ðËܥѡ¼¥Æ¥£¥·¥ç¥ó¤Î¸å¤Ëǧ¼±¤µ¤ì¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢2ÂæÌܤΠSCSI¥É¥é¥¤¥Ö¤Î³ÈÄ¥¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë
             <quote>E</quote>
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤¬¤¢¤ë¤È¤·¤Þ¤¹¤È¡¢
             ¤³¤ì¤Ï <filename>/dev</filename>
             ¤Ë¡Ö¥¹¥é¥¤¥¹ 5 ¡×¤Î¥¹¥Ú¥·¥ã¥ë¥Õ¥¡¥¤¥ë¤òºî¤ëɬÍפ¬¤¢¤ê¡¢
             <filename>/dev/da1s5</filename>
             ¤È¤·¤Æ¥Þ¥¦¥ó¥È¤µ¤ì¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV da1s5</userinput>
 &prompt.root; <userinput>mount -t msdos /dev/da1s5 /dos/e</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mount-foreign-fs">
           <para>¾¤Î¥·¥¹¥Æ¥à¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò FreeBSD ¤Ç¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             <literal>Digital UNIX</literal>:
             UFS CDROM ¤ÏľÀÜ FreeBSD ¤Ç¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             Digital UNIX ¤ä¤½¤ì°Ê³°¤Î¥·¥¹¥Æ¥à¤Î¥µ¥Ý¡¼¥È¤¹¤ë
             UFS ¤Î¥Ç¥£¥¹¥¯¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤Ï¤â¤Ã¤ÈÊ£»¨¤Ê¤³¤È¤Ç¡¢
             ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ç¥£¥¹¥¯¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¾ÜºÙ¤Ë°Í¸¤·¤Þ¤¹¡£
           </para>
 
           <para>
             <literal>Linux</literal>:
             2.2 °Ê¹ß¤Ï <literal>ext2fs</literal> ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£
             ¾Ü¤·¤¯¤Ï¡¢&man.mount.ext2fs.8; ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             <literal>NT</literal>:
             FreeBSD ÍѤÎÆɤߤÀ¤·¤Î¤ß²Äǽ¤Ê NTFS ¥É¥é¥¤¥Ð¤¬¤¢¤ê¤Þ¤¹¡£
             ¾Ü¤·¤¯¤Ï¡¢Mark Ovens »á¤Ë¤è¤Ã¤Æ½ñ¤«¤ì¤¿¥Á¥å¡¼¥È¥ê¥¢¥ë
             <ulink url="http://ukug.uk.freebsd.org/~mark/ntfs_install.html">http://ukug.uk.freebsd.org/~mark/ntfs_install.html</ulink>
             ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤³¤ÎÌäÂê¤Ë¤Ä¤¤¤Æ¾¤Î¾ðÊ󤬤¢¤ì¤Ð¡¢Â¾¤Î¿Í¤«¤é´¶¼Õ¤µ¤ì¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nt-bootloader">
           <para>¤É¤Î¤è¤¦¤Ë¤·¤¿¤é FreeBSD ¤ò NT ¥í¡¼¥À¡¼¤«¤éµ¯Æ°¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤³¤Î¼ê½ç¤Ï 2.2.x ¤È (µ¯Æ°¤¬ 3 ¤Ä¤Î¥¹¥Æ¡¼¥¸¤Ëʬ¤«¤ì¤Æ¤¤¤ë) 3.x
             ¤Î¥·¥¹¥Æ¥à¤È¤Ç¿¾¯°Û¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             FreeBSD ¤Î¥Í¥¤¥Æ¥£¥Ö¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ÎºÇ½é¤Î¥»¥¯¥¿¤ò¥Õ¥¡¥¤¥ë¤Ë¤·¤Æ
             DOS/NT ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¾å¤ËÃÖ¤¯¤È¤¤¤¦²è´üŪ¤Ê¥¢¥¤¥Ç¥£¥¢¤¬¤¢¤ê¤Þ¤¹¡£
             ¥Õ¥¡¥¤¥ë̾¤ò
             <filename>c:\bootsect.bsd</filename> (<filename>c:\bootsect.dos</filename>
             ¤«¤é¤ÎȯÁۤǤ¹) ¤È¤·¤¿¤È¤·¤Þ¤¹¡£
             <filename>c:\boot.ini</filename>¥Õ¥¡¥¤¥ë¤ò¼¡¤Î¤è¤¦¤ËÊÔ½¸¤·¤Þ¤¹¡£
           </para>
 
           <programlisting>[boot loader]
 timeout=30
 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
 [operating systems]
 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT"
 C:\BOOTSECT.BSD="FreeBSD"
 C:\="DOS"</programlisting>
 
           <para>
             ¤³¤Î¼ê½ç¤Ï¡¢ÍøÍѤ·¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤¬ 2.2.x ¤Ç¤¢¤ê¡¢DOS¡¢NT¡¢FreeBSD
             ¤¢¤ë¤¤¤Ï¤½¤Î¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬¤¹¤Ù¤Æ¡¢
             <emphasis>Ʊ¤¸</emphasis>¥Ç¥£¥¹¥¯¤Î¤½¤ì¤¾¤ì¤Î
             fdisk ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤³¤È¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ÎÎã¤Ï¡¢DOS ¤È NT ¤òºÇ½é¤Î fdisk ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë¤ª¤­¡¢
             FreeBSD ¤Ï 2 ÈÖÌܤˤª¤¤¤¿¥·¥¹¥Æ¥à¤Ç³Îǧ¤·¤Æ¤¤¤Þ¤¹¡£
             ¤Þ¤¿¡¢FreeBSD ¤Ï MBR ¤ò»È¤ï¤º¤Ë¡¢
             ¥Í¥¤¥Æ¥£¥Ö¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤«¤éµ¯Æ°¤¹¤ë¤è¤¦¤ËÀßÄꤷ¤Æ¤¢¤ê¤Þ¤¹
             (ÌõÃí: FreeBSD ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ç¡¢¥Ö¡¼¥È¥Þ¥Í¥¸¥ã¤ò»È¤ï¤º¤Ëɸ½à
             MBR ¤ò»È¤¦¾ì¹ç¤ËÁêÅö¤·¤Þ¤¹)¡£
           </para>
 
           <para>
             (¤â¤· NTFS ¤ËÊÑ´¹¤·¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë¤Ê¤é)DOS
             ¥Õ¥©¡¼¥Þ¥Ã¥È¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤« FAT
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò <filename>/mnt</filename> ¤Ë DOS
             ¥Þ¥¦¥ó¥È¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>dd if=/dev/rda0a of=/mnt/bootsect.bsd bs=512 count=1</userinput></screen>
 
           <para>
             ºÆµ¯Æ°¤·¤Æ DOS ¤« NT ¤ËÀÚÂؤ¨¤Þ¤¹¡£NTFS ¥æ¡¼¥¶¤Ï
             <filename>bootsect.bsd</filename> ¤ä
             <filename>bootsect.lnx</filename> ¤ò¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤«¤é
             <filename>C:\</filename>
             ¤Ø¥³¥Ô¡¼¤·¤Þ¤¹¡£
             <filename>boot.ini</filename>
             ¤Î¥Õ¥¡¥¤¥ë°À­ (¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó) ¤ÎÊѹ¹¤ò°Ê²¼¤Î¤è¤¦¤Ë¹Ô¤Ê¤¤¤Þ¤¹¡£
           </para>
 
           <screen><prompt>&gt;</prompt> <userinput>attrib -s -r c:\boot.ini</userinput></screen>
 
           <para>
             ¾å¤ÎÎã¤Î
             <filename>boot.ini</filename> ¤Ç¼¨¤·¤¿¤è¤¦¤ÊÀµ¤·¤¤¥¨¥ó¥È¥ê¤ò²Ã¤¨¡¢
             ¥Õ¥¡¥¤¥ë°À­¤ò¸µ¤ËÌᤷ¤Þ¤¹¡£
           </para>
 
           <screen><prompt>&gt;</prompt> <userinput>attrib +s +r c:\boot.ini</userinput></screen>
 
           <para>
             FreeBSD ¤¬ MBR ¤«¤éµ¯Æ°¤¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢
             ¤½¤ì¤¾¤ì¤Î¥Í¥¤¥Æ¥£¥Ö¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤«¤éµ¯Æ°¤¹¤ë¤è¤¦¤ËÀßÄꤷ¤¿¸å¤Ç¡¢
             DOS ¤«¤é <command>fdisk</command>
             ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¸µ¤ËÌᤷ¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             FreeBSD 3.X ¤Ë¤ª¤±¤ë¼ê½ç¤Ï¡¢¤³¤ì¤è¤ê¤¤¤¯¤Ö¤ó´Êñ¤Ç¤¹¡£
           </para>
 
           <para>
             FreeBSD ¤¬ NT µ¯Æ°¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤È¤·¤ÆƱ¤¸¥Ç¥£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
             <filename>/boot/boot1</filename> ¤òñ½ã¤Ë
             <filename>C:\BOOTSECT.BSD</filename> ¤Ø¥³¥Ô¡¼¤·¤Þ¤¹¡£
             ¤â¤· FreeBSD ¤¬°Û¤Ê¤Ã¤¿¥Ç¥£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
             <filename>/boot/boot1</filename> ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¤Î¤Ç¡¢
             <filename>/boot/boot0</filename> ¤¬É¬ÍפǤ¹¡£
 
             <warning>
               <para>¤³¤³¤Ç <filename>/boot/boot1</filename> ¤ÎÂå¤ï¤ê¤Ë
                 <filename>/boot/boot0</filename> ¤ò¥³¥Ô¡¼¤¹¤ë¤è¤¦¤Ê¤³¤È¤ò¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó!
                 ¤½¤¦¤¹¤ë¤È¡¢¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤ò¾å½ñ¤­¤·¤Æ¤·¤Þ¤¤¡¢
                 ¥³¥ó¥Ô¥å¡¼¥¿¤¬µ¯Æ°¤Ç¤­¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£</para>
             </warning>
           </para>
 
           <para><filename>/boot/boot0</filename> ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤Ë¤Ï¡¢
             sysinstall ¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤òÍøÍѤ¹¤ë¤«¤É¤¦¤«¿Ò¤Í¤é¤ì¤ë²èÌ̤Ç
             FreeBSD ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤òÁªÂò¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             <filename>/boot/boot0</filename>
             ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ëÉôʬ¤Ï NULL ʸ»ú¤ÇËä¤á¤é¤ì¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢
             sysinstall ¤Ï <filename>/boot/boot0</filename> ¤ò MBR
             ¤Ë¥³¥Ô¡¼¤¹¤ëÁ°¤Ë¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤ò¤­¤Á¤ó¤È¥³¥Ô¡¼¤·¤Æ¤¯¤ì¤ë¤«¤é¤Ç¤¹¡£</para>
 
           <para>FreeBSD ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ÏºÇ¸å¤Ëµ¯Æ°¤·¤¿ OS ¤òµ­Ï¿¤¹¤ë¤¿¤á¤Ë
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤ÎºÇ¸å¤Ëµ¯Æ°¤·¤¿ OS
             ¤Î¥¨¥ó¥È¥ê¤Ë¤¢¤ë¥¢¥¯¥Æ¥£¥Ö¥Õ¥é¥°¤ò¥»¥Ã¥È¤·¡¢512 ¥Ð¥¤¥ÈÁ´ÂΤò MBR ¤Ë½ñ¤­Ìᤷ¤Þ¤¹¡£
             ¤³¤ì¤Ï <filename>/boot/boot0</filename> ¤ò
             <filename>C:\BOOTSECT.BSD</filename> ¤Ë¥³¥Ô¡¼¤·¡¢
             ¥¨¥ó¥È¥ê¤Î°ì¤Ä¤Ë¥¢¥¯¥Æ¥£¥Ö¥Õ¥é¥°¤ò¥»¥Ã¥È¤·¤Æ¶õ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤ò MBR
             ¤Ë½ñ¤­¹þ¤à¤³¤È¤ÈƱ¤¸¤Ç¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="lilo-bootloader">
           <para>FreeBSD ¤È Linux ¤ò LILO ¤«¤éµ¯Æ°¤¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤È Linux ¤¬Æ±¤¸¥Ç¥£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢
             ñ¤Ë Linux °Ê³°¤Î OS ¤òµ¯Æ°¤¹¤ë¤¿¤á¤Î LILO ¤Î¥¤¥ó¥¹¥È¡¼¥ë¼ê½ç¤Ë
             ½¾¤¨¤Ð¤¤¤¤¤À¤±¤Ç¤¹¡£Èó¾ï¤Ë´Êñ¤Ë¤Ç¤Ï¤¢¤ê¤Þ¤¹¤¬¡¢µ­¤·¤Æ¤ß¤Þ¤·¤ç¤¦¡£
           </para>
 
           <para>
             Linux ¤òµ¯Æ°¤·¡¢<filename>/etc/lilo.conf</filename>
             ¤Ë°Ê²¼¤Î¹Ô¤ò²Ã¤¨¤Æ
             ¤¯¤À¤µ¤¤¡£</para>
 
             <programlisting>other=/dev/hda2
         table=/dev/hda
         label=FreeBSD</programlisting>
 
           <para>
             (¾åµ­¤Î¼ê½ç¤Ï FreeBSD ¤Î¥¹¥é¥¤¥¹¤¬ Linux ¤«¤é
             <devicename>/dev/hda2</devicename>
             ¤È¤¤¤¦Ì¾Á°¤Ç¸«¤¨¤Æ¤¤¤ë¤È²¾Äꤷ¤Æ¤¤¤Þ¤¹¡£
             ¤¢¤Ê¤¿¤ÎÀßÄê¤Ë¤¢¤ï¤»¤Æ¤¯¤À¤µ¤¤)
             ¤½¤Î¸å¡¢<command>lilo</command> ¤ò
             <username>root</username>
             ¤Ç¼Â¹Ô¤¹¤ì¤Ð´°Î»¤Ç¤¹¡£
           </para>
 
           <para>
             FreeBSD ¤¬Ê̤Υǥ£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤Î¤Ê¤é¡¢
             LILO ¤Î¥¨¥ó¥È¥ê¤Ë
             <literal>loader=/boot/chain.b</literal>
             ¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£¤¿¤È¤¨¤Ð¡¢¤³¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>other=/dev/dab4
         table=/dev/dab
         loader=/boot/chain.b
         label=FreeBSD</programlisting>
 
           <para>
             ¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï¡¢Æó¤ÄÌܤΥǥ£¥¹¥¯¤òÀµ¤·¤¯µ¯Æ°¤¹¤ë¤¿¤á¤Ë FreeBSD
             ¥Ö¡¼¥È¥í¡¼¥À¤Ë BIOS ¥É¥é¥¤¥ÖÈÖ¹æ¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ¤¿¤È¤¨¤Ð¡¢FreeBSD SCSI ¥Ç¥£¥¹¥¯¤¬ BIOS ¤Ë¤è¤Ã¤Æ
             BIOS ¥Ç¥£¥¹¥¯ 1 ¤È¤·¤Æǧ¼±¤µ¤ì¤ë¤Î¤Ê¤é¡¢
             FreeBSD ¤Î¥Ö¡¼¥È¥í¡¼¥À¤Î¥×¥í¥ó¥×¥È¤Ç¡¢¼¡¤Î¤è¤¦¤Ë»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 
             <screen><prompt>Boot:</prompt> <userinput>1:da(0,a)/kernel</userinput></screen>
           </para>
 
           <para>
             FreeBSD 2.2.5 ¤ä¤½¤ì°Ê¹ß¤ÎÈǤǤϡ¢&man.boot.8; ¤òÀßÄꤹ¤ì¤Ð
             µ¯Æ°»þ¤Ë¾åµ­¤Î¤³¤È¤¬¼«Æ°Åª¤Ë¹Ô¤¨¤Þ¤¹¡£
           </para>
 
           <para>
             <ulink url="http://sunsite.unc.edu/LDP/HOWTO/mini/Linux+FreeBSD.html">Linux+FreeBSD
               mini-HOWTO</ulink> ¤¬ FreeBSD ¤È Linux
             ¤È¤òÁê¸ß¤Ë»È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Î¤è¤¤»²¹Í»ñÎÁ¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="booteasy-loader">
           <para>FreeBSD ¤È Linux ¤ò BootEasy ¤«¤éµ¯Æ°¤¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             LILO ¤ò¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥ì¥³¡¼¥É (MBR) ¤Ç¤Ï¤Ê¤¯
             Linux ¤Îµ¯Æ°¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤³¤ì¤Ç BootEasy ¤«¤é
             LILO ¤òµ¯Æ°¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             Windows95 ¤È Linux ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
             ¤¤¤º¤ì¤Ë¤»¤è¸å¼Ô¤ÎÊý¤¬¤ª¤¹¤¹¤á¤Ç¤¹¡£
             Windows95 ¤òºÆ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëɬÍפˤ«¤é¤ì¤¿¤È¤­¡¢
             Linux ¤òµ¯Æ°²Äǽ¤ËÌ᤹¼ê³¤­¤¬´Êñ¤Ç¤¹¤à¤«¤é¤Ç¤¹
             (Windows95 ¤ÏÊжþ¤Ê¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ç¡¢
             ¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥ì¥³¡¼¥É (MBR) ¤«¤é¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤òÄɤ¤Ê§¤Ã¤Æ¤·¤Þ¤¦¤Î¤Ç¤¹)¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dangerously-dedicated">
           <para>¡Ö´í¸±³Ð¸ç¤ÎÀìÍÑ (dangerously dedicated) ¥Ç¥£¥¹¥¯¡×¤Ï·ò¹¯¤Ë°­¤¤¤Î?</para>
         </question>
 
         <answer>
           <para><anchor id="dedicate"/>
               ¥¤¥ó¥¹¥È¡¼¥ëºî¶ÈÃæ¡¢
               ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÀÚ¤ëºÝ¤Ë
               2 ¤Ä¤ÎÊýË¡¤òÁª¤Ö¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
               ¥Ç¥Õ¥©¥ë¥È¤ÎÊýË¡¤Ç¤Ï¡¢fdisk ¤Î¥Æ¡¼¥Ö¥ë¥¨¥ó¥È¥ê (FreeBSD
               ¤Ç¤Ï¥¹¥é¥¤¥¹¤È¸Æ¤Ð¤ì¤ë) ¤ò»È¤Ã¤Æ¡¢
               ¼«¿È¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë FreeBSD ¤Î¥¹¥é¥¤¥¹¤ò¡¢
               Ʊ¤¸¥Þ¥·¥ó¤Î¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤È¸ß´¹À­¤Î¤¢¤ë·Á¤Ë¤·¤Þ¤¹¡£
               ¤½¤ì¤ËÉտ路¤Æ¡¢¥Ö¡¼¥È¥»¥ì¥¯¥¿¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ì¤Ð¡¢
               ¥Ç¥£¥¹¥¯¾å¤Î»ÈÍѲÄǽ¤Ê¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤òÀÚ¤êÂؤ¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
               ¤â¤¦°ì¤Ä¤ÎÊýË¡¤Ï¥Ç¥£¥¹¥¯¤¹¤Ù¤Æ¤ò FreeBSD ¤Ç»È¤¦¤È¤¤¤¦¤â¤Î¤Ç¡¢
               ¤³¤Î¾ì¹ç¤Û¤«¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤È¤Î¸ß´¹À­¤ò¹Íθ¤·¤Ê¤¤¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤Ç¤Ï¡¢¤Ê¤¼¤³¤ì¤¬ ¡Ö´í¸±³Ð¸ç¤Î¡×¤È¸À¤ï¤ì¤ë¤Î¤Ç¤·¤ç¤¦?
             ¤³¤Î¥â¡¼¥É¤Î¥Ç¥£¥¹¥¯¤¬¡¢Ä̾ï¤Î PC ¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤¬Í­¸ú¤Ê fdisk
             ¥Æ¡¼¥Ö¥ë¤È¸«¤Ê¤¹¾ðÊó¤ò»ý¤Ã¤Æ¤¤¤Ê¤¤¤«¤é¤Ç¤¹¡£
             ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Î½ÐÍèÇ¡²¿¤Ë¤è¤ê¤Þ¤¹¤¬¡¢
             ¤½¤Î¤è¤¦¤Ê¥Ç¥£¥¹¥¯¤òȯ¸«¤·¤¿¤È¤­¡¢
             ·Ù¹ð¤ò½Ð¤¹¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£¤Þ¤¿¡¢¤â¤Ã¤È°­¤¤¾ì¹ç¡¢
             ³Îǧ¤âÄ̹ð¤â¤Ê¤·¤Ë
             BSD ¤Î¥Ö¡¼¥È¥¹¥È¥é¥Ã¥×¤Ë¥À¥á¡¼¥¸¤òÍ¿¤¨¤ë¤â¤Î¤â¤¢¤ë¤Ç¤·¤ç¤¦¡£
             ¤µ¤é¤Ë¤Ï¡¢¡Ö´í¸±³Ð¸ç¤Î¡×¥Ç¥£¥¹¥¯¥ì¥¤¥¢¥¦¥È¤Ï¿¿ô¤Î BIOS¡¢
             AWARD (¤¿¤È¤¨¤Ð HP Netserver ¤ä Micronics ¥·¥¹¥Æ¥à¡¢
             ¾¿¿ô¤Ç»ÈÍѤµ¤ì¤Æ¤¤¤¿) ¤ä
             Symbios/NCR (¿Íµ¤¤Î¤¢¤ëSCSI ¥³¥ó¥È¥í¡¼¥é 53C8xx
             ÍÑ) ¤Ê¤É¤òº®Í𤵤»¤ë¤³¤È¤¬Ê¬¤«¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤Ï´°Á´¤Ê¥ê¥¹¥È¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¾¤Ë¤â¤Þ¤À¤Þ¤À¤¢¤ê¤Þ¤¹¡£¤³¤Îº®Íð¤ÎÃû¸õ¤Ï¡¢
             µ¯Æ°»þ¤Ë¥·¥¹¥Æ¥à¤¬¥í¥Ã¥¯¤¹¤ë¤È¤¤¤¦¤À¤±¤Ç¤Ê¤¯¡¢
             FreeBSD ¤Î¥Ö¡¼¥È¥¹¥È¥é¥Ã¥×¤¬¼«Ê¬¼«¿È¤ò¸«¤Ä¤±¤é¤ì¤Ê¤¤¤¿¤á¤Ëɽ¼¨¤¹¤ë
             <quote>read error</quote>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤Ê¤É¤Ë¤â¸½¤ì¤ë¤³¤È¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¤½¤â¤½¤â¤¤¤Ã¤¿¤¤¤Ê¤¼¤³¤Î¥â¡¼¥É¤¬¤¢¤ë¤Î¤Ç¤·¤ç¤¦¤«?
             ¤³¤ì¤Ï¤ï¤º¤«¤Ë¿ô¥­¥í¥Ð¥¤¥È¤Î¥Ç¥£¥¹¥¯ÍÆÎ̤òÀáÌ󤹤ë¤Î¤ß¤Ç¤¢¤ê¡¢
             ¿·µ¬¥¤¥ó¥¹¥È¡¼¥ë¤Ç¼ÂºÝ¤ËÌäÂê¤òÀ¸¤º¤ë¤Î¤Ç¤¹¡£
             ¡Ö´í¸±³Ð¸ç¤Î¡×¥â¡¼¥É¤Îµ¯¸»¤Ï¿·¤·¤¤ FreeBSD ¥¤¥ó¥¹¥È¡¼¥é¤Ç¤Î¡¢
             BIOS ¤«¤é¸«¤¨¤ë¥Ç¥£¥¹¥¯¤Î
             ¡Ö¥¸¥ª¥á¥È¥ê¡×¤ÎÃͤȥǥ£¥¹¥¯¼«¿È¤È¤ÎÀ°¹çÀ­¤È¤¤¤¦¡¢
             ¤â¤Ã¤È¤â°ìÈÌŪ¤ÊÌäÂê¤Î¤Ò¤È¤Ä¤ò²óÈò¤·¤¿¤¤¤È¤¤¤¦Í׵᤬Çطʤˤ¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¡Ö¥¸¥ª¥á¥È¥ê¡×¤Ï»þÂåÃÙ¤ì¤Î³µÇ°¤Ç¤¹¤¬¡¢
             ̤¤À¤Ë PC BIOS ¤È¥Ç¥£¥¹¥¯¤Ø¤ÎÁê¸ßºîÍѤÎÃæ³Ë¤ò¤Ê¤·¤Æ¤¤¤Þ¤¹¡£
             FreeBSD ¤Î¥¤¥ó¥¹¥È¡¼¥é¤¬¥¹¥é¥¤¥¹¤òºî¤ë»þ¡¢
             ¥Ç¥£¥¹¥¯¾å¤Î¥¹¥é¥¤¥¹¤ò BIOS ¤¬¸«¤Ä¤±¤é¤ì¤ë¤è¤¦¤Ë¡¢
             ¥¹¥é¥¤¥¹°ÌÃÖ¤ò¥Ç¥£¥¹¥¯¾å¤Ëµ­Ï¿¤·¤Þ¤¹¡£¤½¤ì¤¬¸í¤Ã¤Æ¤¤¤ì¤Ð¡¢
             µ¯Æ°¤Ç¤­¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¡Ö´í¸±³Ð¸ç¤Î¡×¥â¡¼¥É¤Ï¤³¤ì¤ò¡¢
             ÌäÂê¤òñ½ã¤Ë¤¹¤ë¤³¤È¤Ç²óÈò¤·¤è¤¦¤È¤·¤Þ¤¹¡£
             ¾õ¶·¤Ë¤è¤Ã¤Æ¤Ï¤³¤ì¤Ç¤¦¤Þ¤¯¤¤¤­¤Þ¤¹¡£
             ¤·¤«¤·¼¡Á±¤Îºö¤È¤·¤Æ»È¤ï¤ì¤Æ¤¤¤ë¤Ë²á¤®¤Þ¤»¤ó¡£
             ¤³¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤â¤Ã¤ÈÎɤ¤ÊýË¡¤Ï¤¤¤¯¤é¤Ç¤â¤¢¤ë¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¤Ç¤Ï¡¢
             ¥¤¥ó¥¹¥È¡¼¥ë»þ¤Ë¡Ö´í¸±³Ð¸ç¤ÎÀìÍѡץ⡼¥É¤¬É¬Íפˤʤë
             ¾õ¶·¤ò²óÈò¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Î¤Ç¤·¤ç¤¦¤«?
             ¤Þ¤º BIOS ¤¬Êó¹ð¤¹¤ë¥Ç¥£¥¹¥¯¤Î¥¸¥ª¥á¥È¥ê¤ÎÃͤò³Ð¤¨¤Æ¤ª¤¯¤³¤È¤«¤é¤Ï¤¸¤á¤Þ¤·¤ç¤¦¡£
             <quote>boot:</quote>
             ¥×¥í¥ó¥×¥È¤Ç <quote><option>-v</option></quote>
             ¤ò»ØÄꤹ¤ë¤«¡¢¥í¡¼¥À¤Ç
             <quote>boot -v</quote>
             ¤È»ØÄꤷ¤Æ¡¢
             µ¯Æ°»þ¤Ë¥«¡¼¥Í¥ë¤Ë¤³¤ÎÃͤòɽ¼¨¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¥¤¥ó¥¹¥È¡¼¥é¤¬µ¯Æ°¤¹¤ëľÁ°¤Ë¡¢
             ¥«¡¼¥Í¥ë¤¬¥¸¥ª¥á¥È¥êÃͤΥꥹ¥È¤òɽ¼¨¤¹¤ë¤Ç¤·¤ç¤¦¡£
             ¥Ñ¥Ë¥Ã¥¯¤òµ¯¤³¤µ¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£
             ¥¤¥ó¥¹¥È¡¼¥é¤¬µ¯Æ°¤¹¤ë¤Î¤òÂÔ¤Á¡¢
             µÕ¥¹¥¯¥í¡¼¥ë¤Ç¤µ¤«¤Î¤Ü¤Ã¤ÆÃͤò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ÉáÄÌ¤Ï BIOS
             ¥Ç¥£¥¹¥¯¥æ¥Ë¥Ã¥ÈÈÖ¹æ¤Ï¡¢
             FreeBSD ¤¬¥Ç¥£¥¹¥¯¤ò¸¡½Ð¤¹¤ë½ç½ø¤ÈƱÍͤǤ¢¤ê¡¢
             ºÇ½é¤Ë IDE¡¢¼¡¤Ë SCSI ¤È¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Ç¥£¥¹¥¯¤ò¥¹¥é¥¤¥·¥ó¥°¤¹¤ëºÝ¤Ë¡¢
             FDISK ¤Î²èÌ̤Çɽ¼¨¤µ¤ì¤ë¥Ç¥£¥¹¥¯¤Î¥¸¥ª¥á¥È¥ê¤¬Àµ¤·¤¤¤³¤È (BIOS
             ¤ÎÊÖ¤¹ÃͤȰìÃפ·¤Æ¤¤¤ë¤«) ¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
             Ëü°ì°Û¤Ê¤Ã¤Æ¤¤¤¿¤é <quote><userinput>g</userinput></quote>
             ¤ò²¡¤·¤Æ½¤Àµ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¥Ç¥£¥¹¥¯¤Ë¤Þ¤Ã¤¿¤¯¤Ê¤Ë¤â¤Ê¤¤¾ì¹ç¤ä¡¢
             ¾¤Î¥·¥¹¥Æ¥à¤«¤é»ý¤Ã¤Æ¤­¤¿¥Ç¥£¥¹¥¯¤Î¾ì¹ç¤Ï
             ¤³¤ì¤ò¹Ô¤Ê¤¦É¬Íפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ¤³¤ì¤Ï¤½¤Î¥Ç¥£¥¹¥¯¤«¤éµ¯Æ°¤µ¤»¤è¤¦¤È¤·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Î¤ß¡¢
             ÌäÂê¤Ë¤Ê¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
             FreeBSD ¤Ï¤½¤Î¥Ç¥£¥¹¥¯¤ò¤¦¤Þ¤¤¶ñ¹ç¤¤¤Ë¾¤Î¥Ç¥£¥¹¥¯¤È¶èÊ̤·¤Æ¤¯¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Ç¥£¥¹¥¯¤Î¥¸¥ª¥á¥È¥ê¤Ë¤Ä¤¤¤Æ BIOS ¤È FreeBSD
             ´Ö¤Ç°ìÃפµ¤»¤ë¤³¤È¤¬¤Ç¤­¤¿¤é¡¢¤³¤ÎÌäÂê¤Ï¤Û¤Ü²ò·è¤·¤¿¤È»×¤Ã¤Æ¤è¤¤¤Ç¤·¤ç¤¦¡£
             ¤½¤·¤Æ¤â¤Ï¤ä¡Ö´í¸±³Ð¸ç¤ÎÀìÍѡץ⡼¥É¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£
             ¤·¤«¤·¡¢¤Þ¤Àµ¯Æ°»þ¤Ë¶²ÉݤÎ
             <quote>read error</quote>
             ¥á¥Ã¥»¡¼¥¸¤¬½Ð¤ë¤è¤¦¤Ç¤¢¤ì¤Ð¡¢
             ¤ªµ§¤ê¤òÊû¤²¤Æ¿·¤·¤¤¥Ç¥£¥¹¥¯¤òÇ㤤¤Þ¤·¤ç¤¦¡£
             ¤â¤¦¼º¤¦¤â¤Î¤Ï²¿¤â¤¢¤ê¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¡Ö´í¸±³Ð¸ç¤ÎÀìÍѥǥ£¥¹¥¯¡×¤òÄ̾ï¤Î PC
             ¤Ç¤Î»ÈÍÑË¡¤ËÌ᤹¤Ë¤Ï¡¢
             ¸¶Â§¤È¤·¤Æ 2 ¤ÄÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£1 ¤Ä¤Ï½½Ê¬¤Ê NULL
             ¥Ð¥¤¥È¤ò MBR ¤Ë½ñ¤­¹þ¤ó¤Ç¡¢
             ¤­¤¿¤ë¤Ù¤­¥¤¥ó¥¹¥È¡¼¥é¤Ë¥Ç¥£¥¹¥¯¤Ï¤Þ¤Ã¤µ¤é¤À¤È»×¤¤¹þ¤Þ¤»¤ëÊýË¡¤Ç¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢¤³¤ó¤Ê´¶¤¸¤Ç¤¹¡£
 
             <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/rda0 count=15</userinput></screen>
           </para>
 
           <para>
             ¤Þ¤¿¡¢¥Þ¥Ë¥å¥¢¥ë¤Ë¤Ï½ñ¤«¤ì¤Æ¤¤¤Ê¤¤ DOS ¤Î¡Öµ¡Ç½¡×
 
             <screen><prompt>&gt;</prompt> <userinput>fdisk /mbr</userinput></screen>
 
               ¤Ï¡¢BSD ¥Ö¡¼¥È¥¹¥È¥é¥Ã¥×¤òÄɤ¤Ê§¤Ã¤Æ¤¯¤ì¤ë¾å¤Ë¡¢
             ¿·¤·¤¤¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥ì¥³¡¼¥É¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤ì¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="add-swap-space">
           <para>¤É¤Î¤è¤¦¤Ë¤·¤¿¤é¥¹¥ï¥Ã¥×Îΰè¤òÁý¤ä¤»¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¥µ¥¤¥º¤òÁý¤ä¤¹¤Î¤¬ºÇÎɤÎÊýË¡¤Ç¤¹¤¬¡¢
             Ê̤Υǥ£¥¹¥¯¤òÄɲ䷤ʤ¯¤ÆºÑ¤à¤È¤¤¤¦ÍøÅÀ¤Î¤¢¤ëÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£
             ·Ð¸³¤«¤éÆÀ¤¿°ìÈÌŪ¤ÊÊýË¡¤Ï¥á¥¤¥ó¥á¥â¥ê¤Î 2ÇÜÄøÅ٤Υ¹¥ï¥Ã¥×Îΰè¤ò
             ¤È¤ë¤È¤¤¤¦¤â¤Î¤Ç¤¹¡£¤·¤«¤·¤´¤¯¾®¤µ¤Ê¥á¥¤¥ó¥á¥â¥ê¤·¤«¤Ê¤¤¾ì¹ç¤Ï¡¢
             ¤½¤ì°Ê¾å¤Î¥¹¥ï¥Ã¥×¤ò¹½À®¤·¤¿¤¤¤È»×¤¦¤Ç¤·¤ç¤¦¡£¤Þ¤¿¡¢¾­Íè¤Î¥á¥â¥ê¤Î
             ¥¢¥Ã¥×¥°¥ì¡¼¥É¤ËÈ÷¤¨¡¢¸å¤Ç¥¹¥ï¥Ã¥×¤Î¹½À®¤òÊѹ¹¤¹¤ëɬÍפ¬¤Ê¤¤¤è¤¦¤Ë
             ½½Ê¬¤Ê¥¹¥ï¥Ã¥×¤ò¹½À®¤·¤Æ¤ª¤¯¤³¤È¤ÏÎɤ¤¹Í¤¨¤Ç¤¹¡£
           </para>
 
           <para>
             ¥¹¥ï¥Ã¥×¤òÊ̤Υǥ£¥¹¥¯¾å¤ËÄɲ乤뤳¤È¤Ï¡¢Ã±½ã¤ËƱ¤¸¥Ç¥£¥¹¥¯¾å
             ¤Ë¥¹¥ï¥Ã¥×¤òÄɲ乤ë¾ì¹ç¤è¤ê¤â¹â®¤ËÆ°ºî¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
             Îã¤Ëµó¤²¤ì¤Ð¡¢¤¢¤ë¥Ç¥£¥¹¥¯¾å¤Î¥½¡¼¥¹¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤¤¤ë¤È¤·¤Æ¡¢
             ¥¹¥ï¥Ã¥×¤¬Ê̤Υǥ£¥¹¥¯¾å¤Ëºî¤é¤ì¤Æ¤¤¤ì¤Ð¡¢¤³¤ì¤é¤¬Æ±¤¸¥Ç¥£¥¹¥¯¾å
             ¤Ë¤¢¤ë¾ì¹ç¤è¤ê¤âÃÇÁ³Â®¤¤¤Ç¤¹¡£SCSI ¥Ç¥£¥¹¥¯¤Î¾ì¹ç¤ÏÆäˤ½¤¦¤À¤È¸À¤¨¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Ç¥£¥¹¥¯¤¬Ê£¿ô¤¢¤ë¾ì¹ç¡¢¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò³Æ¥Ç¥£¥¹¥¯¤Ë
             ºî¤ë¤è¤¦¤Ë¹½À®¤¹¤ë¤È¡¢»ÈÍÑÃæ¤Î¥Ç¥£¥¹¥¯¾å¤Ë¥¹¥ï¥Ã¥×¤òÃÖ¤¤¤¿¤È¤·¤Æ¤â¡¢
             Ä̾ï¤Î¾ì¹ç¤ÏÍ­±×¤Ç¤¹¡£°ìÈÌŪ¤Ë¡¢¥·¥¹¥Æ¥à¤Ë¤¢¤ë¹â®¤Ê¥Ç¥£¥¹¥¯¤Ë¤Ï
             ¥¹¥ï¥Ã¥×¤òºî¤ë¤è¤¦¤Ë¤¹¤Ù¤­¤Ç¤·¤ç¤¦¡£
             FreeBSD ¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¥¤¥ó¥¿¡¼¥ê¡¼¥Ö¤Ê¥¹¥ï¥Ã¥×¥Ç¥Ð¥¤¥¹¤ò 4¤Ä¤Þ¤Ç
             ¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£Ê£¿ô¤Î¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¹½À®¤¹¤ëºÝ¤Ë¡¢
             ÉáÄ̤Ϥ½¤ì¤é¤òÂçÂÎƱ¤¸¤¯¤é¤¤¤ÎÂ礭¤µ¤Ë¤·¤Æºî¤ê¤¿¤¤¤È¤³¤í¤Ç¤¹¤¬¡¢
             ¥«¡¼¥Í¥ë¤Î¥³¥¢¥À¥ó¥×¤ò¼è¤ë¤Î¤ËÅԹ礬Îɤ¤¤è¤¦¤Ë¥á¥¤¥ó¤Î
             ¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÂ礭¤á¤Ë¤È¤ë¿Í¤â¤¤¤Þ¤¹¡£
             ¥á¥¤¥ó¤Î¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ï¥«¡¼¥Í¥ë¤Î¥³¥¢¤¬¤È¤ì¤ë¤è¤¦¤Ë
             ºÇÄã¤Ç¤â¼Â¥á¥â¥ê¤ÈƱ¤¸Â礭¤µ¤Ë¤¹¤Ù¤­¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             IDE ¥É¥é¥¤¥Ö¤ÏƱ»þ¤ËƱ¤¸¥Á¥ã¥Í¥ë¾å¤ÎÊ£¿ô¤Î¥É¥é¥¤¥Ö¤Ë¤Ï
             ¥¢¥¯¥»¥¹¤Ç¤­¤Þ¤»¤ó (FreeBSD ¤Ï mode 4 ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Ê¤¤¤Î¤Ç¡¢
             ¤¹¤Ù¤Æ¤Î IDE ¥Ç¥£¥¹¥¯ I/O ¤Ï <quote>programmed</quote> ¤Ç¤¹)¡£
             IDE ¤Î¾ì¹ç¤Ç¤¢¤Ã¤Æ¤â¤ä¤Ï¤ê¡¢¥¹¥ï¥Ã¥×¤òÊ̤Υϡ¼¥É¥Ç¥£¥¹¥¯¾å¤Ë
             ºîÀ®¤¹¤ë¤³¤È¤ò¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
             ¥É¥é¥¤¥Ö¤Ï¼Â¤Ë°Â¤¤¤â¤Î¤Ç¤¹¡¢¿´ÇÛ¤¹¤ë¤À¤±ÌµÂ̤Ǥ¹¡£
           </para>
 
           <para>
             NFS ±Û¤·¤Ë¥¹¥ï¥Ã¥Ô¥ó¥°¤µ¤»¤ëÊýË¡¤Ï¡¢
             ¥¹¥ï¥Ã¥×ÍÑ¤Î¥í¡¼¥«¥ë¥Ç¥£¥¹¥¯¤¬Ìµ¤¤¾ì¹ç¤Ë¤Î¤ß¿ä¾©¤µ¤ì¤Þ¤¹¡£
             NFS ±Û¤·¤Î¥¹¥ï¥Ã¥Ô¥ó¥°¤ÏÃÙ¤¯¡¢FreeBSD 4.x ¤è¤êÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï
             ¸úΨ¤¬°­¤¤¤Î¤Ç¤¹¤¬¡¢4.0 °Ê¹ß¤Ç¤Ï¤½¤ì¤Ê¤ê¤Ë¹â®¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¤½¤¦¤Ï¤¤¤Ã¤Æ¤â¡¢ÍøÍѤǤ­¤ë¥Í¥Ã¥È¥ï¡¼¥¯¤ÎÂÀ¤µ¤ËÀ©¸Â¤µ¤ì¤Þ¤¹¤·¡¢
             NFS ¥µ¡¼¥Ð¤Ë;·×¤ÊÉé²Ù¤¬¤«¤«¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ì¤Ï 64MB¤Î vn-swap ¤òºî¤ëÎã¤Ç¤¹ (¤³¤³¤Ç¤Ï
             <filename>/usr/swap0</filename>
             ¤È¤·¤Þ¤¹¤¬¡¢¤â¤Á¤í¤ó¹¥¤­¤Ê̾Á°¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹)¡£
           </para>
 
           <para>
             ¥«¡¼¥Í¥ë¤¬¼¡¤Î¹Ô¤ò´Þ¤à¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤«¤é¹½À®¤µ¤ì¤Æ¤¤¤ë¤«¤ò
             ³Îǧ¤·¤Þ¤¹¡£GENERIC ¥«¡¼¥Í¥ë¤Ë¤Ï¡¢¤³¤Î¹Ô¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <programlisting>pseudo-device   vn 1   #Vnode driver (turns a file into a device)</programlisting>
 
           <orderedlist>
             <listitem>
               <para>vn ¥Ç¥Ð¥¤¥¹¤òºî¤ê¤Þ¤¹</para>
               <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh ./MAKEDEV vn0</userinput></screen>
 
             </listitem>
 
             <listitem>
               <para>¥¹¥ï¥Ã¥×¥Õ¥¡¥¤¥ë¤òºî¤ê¤Þ¤¹
                 (<filename>/usr/swap0</filename>)</para>
               <screen>&prompt.root; <userinput>dd if=/dev/zero of=/usr/swap0 bs=1024k count=64</userinput></screen>
             </listitem>
 
             <listitem>
               <para>¥¹¥ï¥Ã¥×¥Õ¥¡¥¤¥ë¤ËŬÀڤʥѡ¼¥ß¥Ã¥·¥ç¥ó¤òÀßÄꤷ¤Þ¤¹</para>
               <screen>&prompt.root; <userinput>chmod 0600 /usr/swap0</userinput></screen>
             </listitem>
 
             <listitem>
               <para><filename>/etc/rc.conf</filename>
                 ¤Ç¥¹¥ï¥Ã¥×¥Õ¥¡¥¤¥ë¤òÍ­¸ú²½¤µ¤»¤Þ¤¹</para>
               <programlisting>swapfile="/usr/swap0"   # Set to name of swapfile if aux swapfile desired.</programlisting>
             </listitem>
 
             <listitem>
               <para>¥Þ¥·¥ó¤òºÆµ¯Æ°¤·¤Þ¤¹</para>
             </listitem>
           </orderedlist>
 
           <para>
             ¥¹¥ï¥Ã¥×¥Õ¥¡¥¤¥ë¤ò¤¹¤°¤ËÍ­¸ú²½¤µ¤»¤¿¤¤¤Î¤Ê¤é°Ê²¼¤Î¤è¤¦¤Ë¥¿¥¤¥×¤·¤Þ¤¹¡£
           </para>
             <screen>&prompt.root; <userinput>vnconfig -e /dev/vn0b /usr/swap0 swap</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="printer-setup">
           <para>¥×¥ê¥ó¥¿¤Î¥»¥Ã¥È¥¢¥Ã¥×¤ÇÌäÂ꤬¤¢¤ê¤Þ¤¹</para>
         </question>
 
         <answer>
           <para>¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¥×¥ê¥ó¥¿¤ÎÉôʬ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
             õ¤·¤Æ¤¤¤ëÌäÂê¤Î¤Û¤È¤ó¤É¤¬½ñ¤«¤ì¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£
             <ulink url="../handbook/printing.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡Ö¥×¥ê¥ó¥¿¤ÎÍøÍÑ¡×</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>¥×¥ê¥ó¥¿¤Ë¤è¤Ã¤Æ¤Ï¡¢°õºþ¤¹¤ë¤Î¤Ë¥Û¥¹¥È¦¤Ë¥É¥é¥¤¥Ð¤¬
             ɬÍפǤ¹¡£¤³¤ì¤é <quote>WinPrinters</quote> ¤È¸Æ¤Ð¤ì¤ë¤â¤Î¤Ï¡¢
             ÁǤΠFreeBSD ¤Ç¤Ï»È¤¨¤Þ¤»¤ó¡£DOS ¤ä Windows NT 4.0 ¤ÇÆ°ºî¤·¤Ê¤¤
             ¤Ê¤é¡¢¤½¤Î¥×¥ê¥ó¥¿¤Ï¤ª¤½¤é¤¯ WinPrinter ¤Ç¤·¤ç¤¦¡£
             ¤¿¤À¤·¡¢Í£°ì¤Î´õ˾¤¬»Ä¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             <filename>ports/print/pnm2ppa</filename> ¤Î port ¤¬
             Âбþ¤·¤Æ¤¤¤ë¤«¤É¤¦¤«³Îǧ¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£<ulink
             url="http://www.freebsd.org/cgi/url.cgi?ports/print/pnm2ppa/pkg-descr">
             ¥Ñ¥Ã¥±¡¼¥¸¤ÎÀâÌÀ</ulink>¤Ë¤Ï¤³¤¦½ñ¤¤¤Æ¤¢¤ê¤Þ¤¹¡£</para>
 
           <blockquote>
             <para>¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤Ï PPA (printer performance
               architecture) ¥×¥í¥È¥³¥ë¤Î½ÐÎϤò¹Ô¤¤¤Þ¤¹¡£¤³¤Î¥×¥í¥È¥³¥ë
               ¤Ï HP ¤Î "Windows ÀìÍÑ" ¥×¥ê¥ó¥¿¤Î°ìÉô¤Ë»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
               ¤½¤Î¤Ê¤«¤Ë¤Ï¡¢HP Deskjet 820C ¥·¥ê¡¼¥º¡¢HP DeskJet 720
               ¥·¥ê¡¼¥º¡¢¤ª¤è¤Ó HP DeskJet 1000 ¥·¥ê¡¼¥º¤¬¤¢¤ê¤Þ¤¹¡£(ά)</para>
 
             <para>WWW: <ulink
               url="http://pnm2ppa.sourceforge.net/">http://pnm2ppa.sourceforge.net/</ulink></para>
           </blockquote>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="keyboard-mappings">
           <para>»ä¤Î¥·¥¹¥Æ¥à¤Î¥­¡¼¥Ü¡¼¥É¥Þ¥Ã¥Ô¥ó¥°¤Ï´Ö°ã¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             <command>kbdcontrol</command> ¥×¥í¥°¥é¥à¤Ï¡¢
             ¥­¡¼¥Ü¡¼¥É¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤à¤¿¤á¤Î¥ª¥×¥·¥ç¥ó¤òÈ÷¤¨¤Æ¤¤¤Þ¤¹¡£
             <filename>/usr/share/syscons/keymaps</filename>
             ¤Î²¼¤Ë¤¿¤¯¤µ¤ó¤Î¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤¬¤¢¤ê¤Þ¤¹¡£
             ¥·¥¹¥Æ¥à¤Ë´ØÏ¢¤Î¤¢¤ë¤â¤Î¤ò°ì¤ÄÁª¤ó¤Ç¡¢¥í¡¼¥É¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>kbdcontrol -l uk.iso</userinput></screen>
 
           <para>
             <filename>/usr/share/syscons/keymaps</filename>
             ¤È³ÈÄ¥»Ò
             <filename>.kbd</filename> ¤Ï¡¢¤É¤Á¤é¤â
             &man.kbdcontrol.1;
             ¤Ë¤è¤Ã¤Æ»ÈÍѤµ¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ì¤Ï <filename>/etc/sysconfig</filename> (¤Þ¤¿¤Ï
             &man.rc.conf.5;)
             Ãæ¤ÇÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤³¤Î¥Õ¥¡¥¤¥ëÃæ¤Ë¤¢¤ë¤½¤ì¤¾¤ì¤Î¥³¥á¥ó¥È¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             FreeBSD 2.0.5R
             ¤ä¤½¤ì°Ê¹ß¤ÎÈǤǤϡ¢
             ¥Æ¥­¥¹¥È¥Õ¥©¥ó¥È¤ä¥­¡¼¥Ü¡¼¥É¥Þ¥Ã¥Ô¥ó¥°¤Ë´Ø·¸¤Î¤¢¤ë¤â¤Î¤Ï¤¹¤Ù¤Æ¡¢
             <filename>/usr/share/examples/syscons</filename>
             ¤ÎÃæ¤Ë¤ª¤µ¤á¤é¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>¸½ºß°Ê²¼¤Î¥Þ¥Ã¥Ô¥ó¥°¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
             <itemizedlist>
               <listitem>
                 <para>Belgian ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>Brazilian 275 keyboard Codepage 850</para>
               </listitem>
 
               <listitem>
                 <para>Brazilian 275 keyboard ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>Danish Codepage 865</para>
               </listitem>
 
               <listitem>
                 <para>Danish ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>French ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>German Codepage 850 </para>
               </listitem>
 
               <listitem>
                 <para>German ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>Italian ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>Japanese 106</para>
               </listitem>
 
               <listitem>
                 <para>Japanese 106x</para>
               </listitem>
 
               <listitem>
                 <para>Latin American</para>
               </listitem>
 
               <listitem>
                 <para>Norwegian ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>Polish ISO-8859-2 (programmer's)</para>
               </listitem>
 
               <listitem>
                 <para>Russian Codepage 866 (alternative)</para>
               </listitem>
 
               <listitem>
                 <para>Russian koi8-r (shift)</para>
               </listitem>
 
               <listitem>
                 <para>Russian koi8-r</para>
               </listitem>
 
               <listitem>
                 <para>Spanish ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>Swedish Codepage 850</para>
               </listitem>
 
               <listitem>
                 <para>Swedish ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>Swiss-German ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>United Kingdom Codepage 850</para>
               </listitem>
 
               <listitem>
                 <para>United Kingdom ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>United States of America ISO-8859-1</para>
               </listitem>
 
               <listitem>
                 <para>United States of America dvorak</para>
               </listitem>
 
               <listitem>
                 <para>United States of America dvorakx</para>
               </listitem>
 
             </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="pnp-resources">
           <para>µ¯Æ°»þ¤Ë¡¢<errorname>unknown: &lt;PNP0303&gt; can't
               assign resources</errorname> ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬É½¼¨¤µ¤ì¤ë¤Î¤Ç¤¹¤¬?</para>
         </question>
 
         <answer>
           <para>°Ê²¼¤Ï¡¢freebsd-current ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ø¤ÎÅê¹Æ¤«¤é¤Î
             È´¿è¤Ç¤¹¡£</para>
 
           <blockquote>
             <attribution>&a.wollman;, 2001 ǯ 4 ·î 24 Æü</attribution>
 
             <para><quote>can't assign resources</quote> ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤Ï¡¢
               ¤½¤Î¥Ç¥Ð¥¤¥¹¤¬¥ì¥¬¥·¡¼ ISA ¥Ç¥Ð¥¤¥¹¤Ç¡¢PnP ¤ò°Õ¼±¤·¤Æ¤¤¤Ê¤¤
               ¥É¥é¥¤¥Ð¤¬¥«¡¼¥Í¥ë¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
               ¤³¤ì¤Ë¤Ï¡¢¥­¡¼¥Ü¡¼¥É¥³¥ó¥È¥í¡¼¥é¡¢¥×¥í¥°¥é¥à²Äǽ¤Ê
               ³ä¤ê¹þ¤ßÀ©¸æ IC ¤ä¤½¤Î¾¤µ¤Þ¤¶¤Þ¤Êɸ½àŪ¤Ê¥Ç¥Ð¥¤¥¹¤¬
               ¤¢¤ê¤Þ¤¹¡£¥ê¥½¡¼¥¹¤¬³ä¤êÅö¤Æ¤é¤ì¤Ê¤¤¤Î¤Ï¡¢´û¤Ë¤½¤Î¥¢¥É¥ì¥¹¤ò
               »È¤Ã¤Æ¤¤¤ë¥É¥é¥¤¥Ð¤¬¤¢¤ë¤«¤é¤Ç¤¹¡£</para>
           </blockquote>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="user-quotas">
           <para>¥æ¡¼¥¶¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿¤¬Àµ¾ï¤ËÆ°ºî¤·¤Æ¤¤¤Ê¤¤¤è¤¦¤Ç¤¹¡£</para>
         </question>
 
         <answer>
             <orderedlist>
               <listitem>
                 <para><quote><filename>/</filename></quote>
                   ¤Ë¤Ï¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿¤òÀßÄꤷ¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£</para>
               </listitem>
 
               <listitem>
                 <para>
                   ¥¯¥©¡¼¥¿¥Õ¥¡¥¤¥ë¤¬ÃÖ¤«¤ì¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ë
                   ¥¯¥©¡¼¥¿¥Õ¥¡¥¤¥ë¤òÃÖ¤¯¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
                 </para>
 
                 <informaltable frame="none">
                   <tgroup cols="2">
                     <thead>
                       <row>
                         <entry>Filesystem</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 id="inappropriate-ccd">
           <para>¤ï¤¿¤·¤Î ccd ¤Ï¡¢
             ²¿¤¬Å¬¹ç¤·¤Æ¤¤¤Ê¤¤ (Inappropriate) ¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>¼¡¤Î¤è¤¦¤Ê¾É¾õ¤¬¸½¤ì¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>ccdconfig -C</userinput>
 ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format</screen>
 
           <para>
             Ä̾盧¤Î¸½¾Ý¤Ï¥¿¥¤¥×¤ò¡Ö̤»ÈÍÑ (unused)¡×¤Î¤Þ¤ÞÊü¤Ã¤Æ¤ª¤«¤ì¤¿
             <literal>c</literal>
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¤Ä¤Ê¤²¤è¤¦¤È¤·¤¿¾ì¹ç¤Ë¸½¤ì¤Þ¤¹¡£ccd ¥É¥é¥¤¥Ð¤Ï
             FS_BSDFFS
             ¥¿¥¤¥×¤ò¥Ù¡¼¥¹¤È¤¹¤ë¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÍ׵ᤷ¤Þ¤¹¡£
             ¤Ä¤Ê¤²¤è¤¦¤È¤·¤Æ¤¤¤ë¥Ç¥£¥¹¥¯¤Î¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òÊÔ½¸¤·¤Æ¡¢
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¥¿¥¤¥×¤ò <literal>4.2BSD</literal>
             ¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ccd-disklabel">
           <para>¤É¤¦¤·¤Æ¤ï¤¿¤·¤Î ccd ¤Î¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>¼¡¤Î¤è¤¦¤Ê¾É¾õ¤¬¸½¤ì¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>disklabel ccd0</userinput>
 (it prints something sensible here, so let's try to edit it)
 &prompt.root; <userinput>disklabel -e ccd0</userinput>
 (edit, save, quit)
 disklabel: ioctl DIOCWDINFO: No disk label on disk;
 use "disklabel -r" to install initial label</screen>
 
           <para>
             ¤³¤ì¤Ï ccd ¤«¤éÊÖ¤µ¤ì¤ë¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤¬¡¢
             ¼Â¤Ï¥Ç¥£¥¹¥¯¾å¤Ë¤Ï¤Ê¤¤¤Þ¤Ã¤¿¤¯¤Îµ¶¤Î¾ðÊó¤À¤«¤é¤Ç¤¹¡£
             ¤³¤ì¤òÌÀ¼¨Åª¤Ë½ñ¤­Ä¾¤¹¤³¤È¤ÇÌäÂê¤ò²ò¾Ã¤Ç¤­¤Þ¤¹¡¢
             ¤½¤ì¤Ë¤Ï¡¢¤Ä¤®¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>disklabel ccd0 &gt; /tmp/disklabel.tmp</userinput>
 &prompt.root; <userinput>disklabel -Rr ccd0 /tmp/disklabel.tmp</userinput>
 &prompt.root; <userinput>disklabel -e ccd0</userinput>
 (this will work now)</screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sysv-ipc">
           <para>FreeBSD ¤Ï System V ¤Î IPC ¥×¥ê¥ß¥Æ¥£¥Ö¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Ï¤¤¡£
             FreeBSD ¤Ï System-V ¥¹¥¿¥¤¥ë¤Î IPC ¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£
             ¶¦Í­¥á¥â¥ê¡¢¥á¥Ã¥»¡¼¥¸¡¢¥»¥Þ¥Õ¥©¤¬´Þ¤Þ¤ì¤Þ¤¹¡£
             °Ê²¼¤Î¹Ô¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤Ë²Ã¤¨¤ë¤È¡¢
             ¥µ¥Ý¡¼¥È¤¬Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>options    SYSVSHM          # enable shared memory
 options    SYSVSEM          # enable for semaphores
 options    SYSVMSG          # enable for messaging</programlisting>
 
             <note>
               <para>FreeBSD 3.2 ¤È¤½¤ì°Ê¹ß¤Ç¤Ï¡¢
                 ¤³¤ì¤é¤Î¥ª¥×¥·¥ç¥ó¤¬¤¢¤é¤«¤¸¤á <emphasis>GENERIC</emphasis>
                 ¥«¡¼¥Í¥ë¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢
                 ¤¢¤Ê¤¿¤Î¥·¥¹¥Æ¥à¤Ë¤Ï¤¹¤Ç¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
             </note>
 
         <para>¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="uucpmail">
           <para>UUCP ¤Ç¥á¡¼¥ë¤òÇÛÁ÷¤¹¤ë¤Ë¤Ï sendmail ¤ò¤É¤¦»È¤¨¤Ð¤è¤¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤ËÉÕ°¤·¤Æ¤¤¤ë sendmail ¤Ï¡¢
             ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤ËľÀܤĤʤ¬¤Ã¤Æ¤¤¤ë¥µ¥¤¥È¤Ë¤¢¤ï¤»¤ÆÀßÄꤷ¤Æ¤¢¤ê¤Þ¤¹¡£
             UUCP ·Ðͳ¤Ç mail ¤ò¸ò´¹¤·¤¿¤¤¾ì¹ç¤Ë¤Ï sendmail
             ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò²þ¤á¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
           </para>
 
           <para>
             <filename>/etc/sendmail.cf</filename>
             ¤ò¼«Ê¬¤Î¼ê¤Ç²þ¤¤¹¤ë¤Î¤Ï½ã¿è¼çµÁ¼Ô¤Î¤ä¤ë¤è¤¦¤Ê»ö¤Ç¤¹¡£
             sendmail ¤Î version 8 ¤Ï &man.m4.1;
             ¤Î¤è¤¦¤Ê¥×¥ê¥×¥í¥»¥Ã¥µ¤òÄ̤·¤ÆÀßÄê¥Õ¥¡¥¤¥ë¤òÀ¸À®¤¹¤ë¿·¤·¤¤¥¢¥×¥í¡¼¥Á¤ò¼è¤Ã¤Æ¤ª¤ê¡¢
             ¤è¤êÃê¾Ý²½¤µ¤ì¤¿¥ì¥Ù¥ë¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¤Þ¤¹¡£
             <filename>/usr/src/usr.sbin/sendmail/cf</filename>
             ¥Ç¥£¥ì¥¯¥È¥ê¤ÎÃæ¤Ë¤¢¤ëÀßÄê¥Õ¥¡¥¤¥ë¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤â¤·¤¹¤Ù¤Æ¤Î¥½¡¼¥¹¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë¤Ï sendmail
             ¤ÎÀßÄê¥Ä¡¼¥ë¤Ï¡¢Ê̤Πtar ¥Õ¥¡¥¤¥ë¤Ë¤Þ¤È¤á¤Æ¤¢¤ê¤Þ¤¹¡£CD-ROM ¤¬
             mount ¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
 
           <screen>&prompt.root; <userinput>cd /cdrom/src</userinput>
 &prompt.root; <userinput>cat scontrib.?? | tar xzf - -C /usr/src contrib/sendmail</userinput></screen>
 
           <para>
             ¤³¤ì¤Ï¤¿¤Ã¤¿¿ô 100Kbyte ¤Ç¤¹¤«¤é¿´Çۤʤ¤¤Ç¤·¤ç¤¦¡£
             <filename>cf</filename>
             ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë <filename>README</filename>
             ¤Ë¡¢m4 ¤Ç¤ÎÀßÄê¤Î´ðËÜŪ¤ÊÀâÌÀ¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             UUCP ¤Ç¤ÎÇÛÁ÷¤Î¤¿¤á¤Ë¤Ï¡¢<literal>mailertable</literal> ¤ò»ÈÍѤ¹¤ì¤Ð
             ¤è¤¤¤Ç¤·¤ç¤¦¡£¤³¤ì¤Ë¤è¤Ã¤Æ¡¢sendmail
             ¤¬ÇÛÁ÷Êý¼°¤ò·èÄꤹ¤ë¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò
             ºîÀ®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>¤Þ¤º¤Ï¤¸¤á¤Ë¡¢
             <filename>.mc</filename> ¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             <filename>/usr/src/usr.sbin/sendmail/cf/cf</filename> ¤È¤¤¤¦¥Ç¥£¥ì¥¯¥È¥ê¤¬¡¢
             ¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤òºîÀ®¤¹¤ë¾ì½ê¤Ç¤¹¡£´û¤Ë¤¤¤¯¤Ä¤«Î㤬¤¢¤ë¤È»×¤¤¤Þ¤¹¡£
             ¤³¤ì¤«¤éºîÀ®¤¹¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°¤ò <filename>foo.mc</filename> ¤È¤¹¤ë¤È¡¢
             <filename>sendmail.cf</filename> ¤òµá¤á¤Æ¤¤¤ë¤è¤¦¤Ê·Á¼°¤ËÊÑ´¹¤¹¤ë¤Ë¤Ï¡¢
             ¼¡¤Î¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <screen>&prompt.root; <userinput>cd /usr/src/usr.sbin/sendmail/cf/cf</userinput>
 &prompt.root; <userinput>make foo.cf</userinput>
 &prompt.root; <userinput>cp foo.cf /etc/sendmail.cf</userinput></screen>
 
           <para>
             ɸ½àŪ¤Ê
             <filename>.mc</filename> ¥Õ¥¡¥¤¥ë¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>include(`../m4/cf.m4')
 VERSIONID(`<replaceable>Your version number</replaceable>')
 OSTYPE(bsd4.4)
 
 FEATURE(nodns)
 FEATURE(nocanonify)
 FEATURE(mailertable)
 
 define(`UUCP_RELAY', <replaceable>your.uucp.relay</replaceable>)
 define(`UUCP_MAX_SIZE', 200000)
 
 MAILER(local)
 MAILER(smtp)
 MAILER(uucp)
 
 Cw    <replaceable>your.alias.host.name</replaceable>
 Cw    <replaceable>youruucpnodename.UUCP</replaceable></programlisting>
 
           <para>
             <literal>nodns</literal> ¤È
             <literal>nocanonify</literal> ¤È¤¤¤¦»ØÄê¤ò¤¹¤ë¤³¤È¤Ç¡¢
             mail ¤ÎÇÛÁ÷¤Ë DNS ¤ò»ÈÍѤ·¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£
             <literal>UUCP_RELAY</literal> ¤È¤¤¤¦
             ¹Ô¤Ë´Ø¤·¤Æ¤Ï¡¢
             ¤¢¤ëÍýͳ¤«¤éɬÍפǤ¹¤¬¤½¤ì¤Ïʹ¤«¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£
             .UUCP ¤Ç½ª¤ï¤ë²¾Áۥɥᥤ¥ó¤ò½èÍý¤¹¤ë¤³¤È¤Î¤Ç¤­¤ë¥¤¥ó¥¿¡¼¥Í¥Ã¥È¾å¤Ç¤Î
             ¥Û¥¹¥È̾¤ò¤³¤³¤Ë½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£Ä̾ï¤Ï¡¢ISP ¤Î mail ¥ê¥ì¡¼¥Û¥¹¥È¤ò
             ½ñ¤¯¤³¤È¤Ë¤Ê¤ë¤È»×¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ì¤¬½ªÎ»¤·¤¿¤é¡¢¼¡¤Ë
             <filename>/etc/mailertable</filename>
             ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤¬É¬ÍפǤ¹¡£É¸½àŪ¤ÊÎã¤Ï¼¡¤Î¤È¤ª¤ê¤Ç¤¹¡£
           </para>
 
 <programlisting>#
 # makemap hash /etc/mailertable.db &lt; /etc/mailertable
 #
 horus.interface-business.de   uucp-dom:horus
 .interface-business.de        uucp-dom:if-bus
 interface-business.de         uucp-dom:if-bus
 .heep.sax.de                  smtp8:%1
 horus.UUCP                    uucp-dom:horus
 if-bus.UUCP                   uucp-dom:if-bus
 .                             uucp-dom:</programlisting>
 
 
           <para>
             ¸«¤ì¤Ðʬ¤«¤ë¤è¤¦¤Ë¡¢¤³¤ì¤Ï¼Âºß¤¹¤ëÀßÄê¤Î¥Õ¥¡¥¤¥ë¤Ç¤¹¡£¤Ï¤¸¤á¤Î
             3 ¹Ô¤Ï¥É¥á¥¤¥ó̾¤Ç»ØÄꤵ¤ì¤¿¥á¡¼¥ë¤¬ default ¤Î·ÐÏ©¤ÇÇÛÁ÷¤µ¤ì¤º¤Ë¡¢
             ¡Ö¶áÆ»¡×¤¹¤ë¤¿¤á¤Ë UUCP ¤ÇÎÙ¤ê¤Î¥µ¥¤¥È¤ËÁ÷¤ë¤¿¤á¤ÎÆÃÊ̤ʾõ¶·¤ò
             ½èÍý¤¹¤ë¤â¤Î¤Ç¤¹¡£
             ¼¡¤Î¹Ô¤Ï Ethernet ¤Ç¤Ä¤Ê¤¬¤Ã¤Æ¤¤¤ë¥í¡¼¥«¥ë¤Î¥É¥á¥¤¥ó¤ËÂФ·¤Æ¤Ï
             SMTP ¤ÇÁ÷¤ë¤¿¤á¤ÎÀßÄê¤Ç¤¹¡£
             ºÇ¸å¤Ë¡¢UUCP ¤Ç¤ÎÎÙ¤ê¤Î¥µ¥¤¥È¤¬ .UUCP ¤Ç½ª¤ï¤ë²¾Áۥɥᥤ¥ó¤Î½ñ¼°¤Ç
             »ØÄꤵ¤ì¤Æ¤ª¤ê¡¢default ¤Î rule ¤ò
             <literal><replaceable>uucp-neighbour</replaceable>!<replaceable>
             recipient</replaceable></literal>
             ¤Ç¾å½ñ¤­¤¹¤ë¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£°ìÈֺǸå¤Î¹Ô¤Ï¤¤¤Ä¤â¥É¥Ã¥È¤ò°ì¤Ä½ñ¤­¤Þ¤¹¡£
             ¤³¤ì¤Ï¡¢¤³¤³¤Þ¤Ç¤Î¹Ô¤Ç¥Þ¥Ã¥Á¤·¤Ê¤«¤Ã¤¿¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤Ë¥Þ¥Ã¥Á¤·¡¢
             ¤³¤Î¥µ¥¤¥È¤«¤éÀ¤³¦¤Ë¸þ¤±¤Æ½Ð¤Æ¤¤¤¯¤¿¤á¤Î mail gateway ¤Ë UUCP
             ¤ÇÇÛÁ÷¤¹¤ë¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
             <literal>uucp-dom:</literal> ¤Ë³¤±¤Æ½ñ¤«¤ì¤Æ¤¤¤ë¥Î¡¼¥É̾¤Ï¡¢
             <literal>uuname</literal> ¥³¥Þ¥ó¥É¤Ç»ØÄꤹ¤ë¤³¤È¤Ë¤è¤Ã¤Æ UUCP
             ¤ÇľÀÜÇÛÁ÷¤µ¤ì¤ëÀµ¤·¤¤¥Î¡¼¥É̾¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ºÇ¸å¤Ë¡¢¤³¤Î¥Õ¥¡¥¤¥ë¤Ï»ÈÍѤ¹¤ëÁ°¤Ë DBM ¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¤Ë
             ÊÑ´¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤ò¹Ô¤Ê¤¦¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ï mailertable
             ¤ÎºÇ½é¤Î¥³¥á¥ó¥È¤Ë½ñ¤¤¤Æ¤¢¤ê¤Þ¤¹¡£mailertable ¤òÊѹ¹¤·¤¿»þ¤Ë¤Ï¡¢
             ɬ¤º¤³¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ºÇ¸å¤Î¥Ò¥ó¥È¤Ç¤¹: ¤â¤·ÆÃÄê¤Î¥á¡¼¥ëÇÛÁ÷¤¬¤¦¤Þ¤¯ºîÆ°¤¹¤ë¤«¤É¤¦¤«
             ³Î¤«¤á¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢sendmail ¤Î<option>-bt</option> ¥ª¥×¥·¥ç¥ó¤ò
             »ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£¤³¤Î¥ª¥×¥·¥ç¥ó¤Ë¤è¤Ã¤Æ sendmail ¤Ï
             <emphasis>¥¢¥É¥ì¥¹¥Æ¥¹¥È¥â¡¼¥É</emphasis>¤Çµ¯Æ°¤·¤Þ¤¹¡£
             <literal>0</literal>
             ¤Î¸å¤ËÇÛÁ÷¤·¤¿¤¤¥¢¥É¥ì¥¹¤ò½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£ºÇ¸å¤Î¹Ô¤Ë¡¢¼ÂºÝ¤Ë»ÈÍѤµ¤ì¤ë
             mail agent¡¢¤³¤Î mail agent ¤ÇÁ÷¤é¤ì¤ëÁ÷¿®Àè¤Î¥Û¥¹¥È¡¢¤½¤·¤Æ
             (¿ʬÊÑ´¹¤µ¤ì¤Æ¤¤¤ë) ¥¢¥É¥ì¥¹¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£¤³¤Î¥â¡¼¥É¤òÈ´¤±¤ë¤Ë¤Ï
             Control-D ¤ò²¡¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.user; <userinput>sendmail -bt</userinput>
 ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
 Enter &lt;ruleset&gt; &lt;address&gt;
 <prompt>&gt;</prompt> <userinput>0 foo@interface-business.de</userinput>
 rewrite: ruleset  0   input: foo @ interface-business . de
 ...
 rewrite: ruleset  0 returns: $# uucp-dom $@ if-bus $: foo \
 &lt; @ interface-business . de &gt;
 <prompt>&gt;</prompt> <userinput>^D</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ispmail">
           <para>¥À¥¤¥¢¥ë¥¢¥Ã¥×¤Ç¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤ËÀܳ¤¹¤ë´Ä¶­¤Ç¥á¡¼¥ë¤ò¥»¥Ã¥È¥¢¥Ã¥×¤¹¤ë¤Ë¤Ï¤É¤¦¤ä¤ë¤Î?</para></question>
 
         <answer>
           <para>
             ÀÅŪ¤Ë IP ¥¢¥É¥ì¥¹¤¬³ä¤êÅö¤Æ¤é¤ì¤ë¾ì¹ç¤Ï¡¢
             ¥Ç¥Õ¥©¥ë¥È¤Î¾õÂÖ¤òÊѹ¹¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
             ³ä¤êÅö¤Æ¤é¤ì¤¿Ì¾Á°¤ò¥Û¥¹¥È¥Í¡¼¥à¤È
             ¤¹¤ë¤À¤±¤Ç¡¢sendmail ¤¬¸å¤Î¤³¤È¤ò°ú¤­¼õ¤±¤Æ¤¯¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             ¥À¥¤¥¢¥ë¥¢¥Ã¥× <application>ppp</application> ¤ò
             ¥¤¥ó¥¿¡¼¥Í¥Ã¥ÈÀܳ¤Ë»ÈÍѤ·¡¢Æ°Åª¤Ë IP ¥¢¥É¥ì¥¹¤¬³ä¤êÅö¤Æ¤é¤ì¤ë¾ì¹ç¤Ï¡¢
             ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥µ¡¼¥Ó¥¹¥×¥í¥Ð¥¤¥À (ISP)
             ¤Î¥á¡¼¥ë¥µ¡¼¥Ð¤Ë¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤¬¤¢¤ë¤Ï¤º¤Ç¤¹¡£
             ISP ¤Î¥É¥á¥¤¥ó¤¬
             <hostid role="domainname">myISP.com</hostid>
             ¤Ç¡¢¤¢¤Ê¤¿¤Î¥æ¡¼¥¶Ì¾¤¬
             <username>user</username> ¤À¤È²¾Äꤷ¤Þ¤¹¡£
             ¤Þ¤¿¡¢¤¢¤Ê¤¿¤¬¼«Ê¬¤Î¥Þ¥·¥ó¤ò <hostid role="fqdn">bsd.home</hostid>
             ¤È¸Æ¤ó¤Ç¤ª¤ê¡¢ISP ¤¬
             <hostid role="fqdn">relay.myISP.com</hostid>
             ¤ò¥á¡¼¥ë¥ê¥ì¡¼¤È¤·¤Æ»ÈÍѤǤ­¤ë¤È¸À¤Ã¤Æ¤¤¤ë¤È¤·¤Þ¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤«¤é¥á¡¼¥ë¤ò¼è¤Ã¤Æ¤¯¤ë¤¿¤á¤Ë¤Ï¡¢
             ²ó¼ý (retrieval) ¥¨¡¼¥¸¥§¥ó¥È¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             <application>Fetchmail</application>
             ¤Ï¿¼ï¿Íͤʥץí¥È¥³¥ë¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤Î¤Ç¤ª´«¤á¤Ç¤¹¡£
             ISP ¤¬»ÈÍѤ·¤Æ¤¤¤ë¤Î¤Ï¡¢ÂçÄñ POP3 ¥×¥í¥È¥³¥ë¤Ç¤¹¡£
             ¥æ¡¼¥¶ ppp ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢
             <filename>/etc/ppp/ppp.linkup</filename>
             ¤Ë°Ê²¼¤Î¤è¤¦¤Ëµ­½Ò¤¹¤ë¤È¡¢
             ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤ÈÀܳ¤¬´°Î»¤·¤¿»þÅÀ¤Ç¼«Æ°Åª¤Ë¥á¡¼¥ë¤ò¼èÆÀ¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>MYADDR:
         !bg su user -c fetchmail</programlisting>
 
 
           <para>
             ¥í¡¼¥«¥ë¤Ç¤Ê¤¤¥¢¥«¥¦¥ó¥È¤Ë¥á¡¼¥ë¤òÇÛÁ÷¤¹¤ë¤Î¤Ë
             sendmail ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç (¸å½Ò)¡¢
             ¾å¤Ë¼¨¤·¤¿¥¨¥ó¥È¥ê¤Î¸å¤Ë
           </para>
 
 <programlisting>        !bg su user -c "sendmail -q"</programlisting>
 
           <para>
             ¤òµ­½Ò¤·¤Þ¤¹¡£¤³¤ì¤Ï¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤¬³ÎΩ¤·¤¿¤é¤¹¤°¤Ë
             <application>sendmail</application> ¤Ëί¤Ã¤Æ¤¤¤ë
             mailqueue ¤ò¶¯À©Åª¤Ë½èÍý¤µ¤»¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ÎÎã¤Ç¤Ï¡¢<username>user</username> ¤¬
             <hostid role="fqdn">bsd.home</hostid> ¤Ë¥¢¥«¥¦¥ó¥È¤ò»ý¤Á¡¢
             <hostid role="fqdn">bsd.home</hostid> ¾å¤Î
             <username>user</username>
             ¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ë¡¢°Ê²¼¤Î¤è¤¦¤Ê
             <filename>.fetchmailrc</filename>
             ¥Õ¥¡¥¤¥ë¤¬¤Ä¤¯¤é¤ì¤Æ¤¤¤ë¤³¤È¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <programlisting>poll myISP.com protocol pop3 fetchall pass MySecret;</programlisting>
 
           <para>
             ¸À¤¦¤Þ¤Ç¤â¤Ê¤¯¡¢¤³¤Î¥Õ¥¡¥¤¥ë¤Ï
             <username>user</username>
             °Ê³°¤Î¥æ¡¼¥¶¤¬Æɤळ¤È¤¬½ÐÍè¤Ê¤¤¤è¤¦¤Ë¤·¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
             ÆâÍƤ˥ѥ¹¥ï¡¼¥É <literal>MySecret</literal>
             ¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¤«¤é¤Ç¤¹¡£
           </para>
 
           <para>
             Àµ¤·¤¤
             <literal>from:</literal>
             ¥Ø¥Ã¥À¤ò¤Ä¤±¤Æ¥á¡¼¥ë¤òÁ÷¤ë¤¿¤á¤Ë¤Ï¡¢
             <application>sendmail</application> ¤Ë
             <literal>user@bsd.home</literal> ¤Ç¤Ï¤Ê¤¯
             <literal>user@myISP.com</literal>
             ¤ò»ÈÍѤ¹¤ë¤è¤¦¶µ¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¥á¡¼¥ë¤ò¤è¤êÁ᤯žÁ÷¤¹¤ë¤¿¤á¤Ë¡¢¤¹¤Ù¤Æ¤Î¥á¡¼¥ë¤ò
             <hostid role="fqdn">relay.myISP.com</hostid>
             ¤ØÁ÷¤ë¤è¤¦¤Ë <application>sendmail</application> ¤Ë
             »Ø¼¨¤·¤Æ¤ª¤¯¤Î¤âÎɤ¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¾å¤ÎÍ×·ï¤òËþ¤¿¤¹¤Ë¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ê <filename>.mc</filename>
             ¥Õ¥¡¥¤¥ë¤¬Å¬¤·¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <programlisting>VERSIONID(`bsd.home.mc version 1.0')
 OSTYPE(bsd4.4)dnl
 FEATURE(nouucp)dnl
 MAILER(local)dnl
 MAILER(smtp)dnl
 Cwlocalhost
 Cwbsd.home
 MASQUERADE_AS(`myISP.com')dnl
 FEATURE(allmasquerade)dnl
 FEATURE(masquerade_envelope)dnl
 FEATURE(nocanonify)dnl
 FEATURE(nodns)dnl
 define(`SMART_HOST', `relay.myISP.com')
 Dmbsd.home
 define(`confDOMAIN_NAME',`bsd.home')dnl
 define(`confDELIVERY_MODE', `deferred')dnl</programlisting>
 
           <para>
             <filename>.mc</filename> ¥Õ¥¡¥¤¥ë¤«¤é
             <filename>sendmail.cf</filename> ¤Ø¤ÎÊÑ´¹ÊýË¡¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             Á°¤Î¥»¥¯¥·¥ç¥ó¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤. sendmail.cf ¤ò¹¹¿·¤·¤¿¸å¤Ë
             <application>sendmail</application> ¤ò¥ê¥¹¥¿¡¼¥È¤¹¤ë¤Î¤â¤ªËº¤ì¤Ê¤¯¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="toor-account">
           <para>¤³¤Î UID ¤¬ 0 ¤Î <username>toor</username> ¤È¤¤¤¦
             ¥¢¥«¥¦¥ó¥È¤È¤Ï²¿¤Ç¤¹¤«? ´í¸±¤Ë¤µ¤é¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>¿´ÇÛ̵ÍѤǤ¹¡£<username>toor</username> ¤Ï
             <quote>ÂåÂؤÎ</quote> ¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¡¼¥¢¥«¥¦¥ó¥È¤Ç¤¹
             (toor ¤Ï root ¤òµÕ¤ËÄ֤俤â¤Î¤Ç¤¹)¡£
             °ÊÁ°¤Ï¡¢&man.bash.1; ¥·¥§¥ë¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤¿»þ¤Ë
             ºîÀ®¤µ¤ì¤Æ¤¤¤Þ¤·¤¿¤¬¡¢¸½ºß¤Ïɸ½à¤ÇºîÀ®¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤³¤Î¥æ¡¼¥¶¡¼¤¬ºîÀ®¤µ¤ì¤ë¤Î¤Ï¡¢
             ¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¤¬Èóɸ½à¤Î¥·¥§¥ë¤ò»È¤¦¾ì¹ç¤òÁÛÄꤷ¤Æ¤ª¤ê¡¢
             <username>root</username>
             ¤Îɸ½à¤Î¥·¥§¥ë¤òÊѹ¹¤·¤Ê¤¯¤Æ¤â¤è¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ´ðËÜÇÛÉۤ˴ޤޤì¤Æ¤¤¤Ê¤¤¥·¥§¥ë
             (¤¿¤È¤¨¤Ð ports ¤ä packages ¤«¤é¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤ë¥·¥§¥ë)
             ¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¤ÏÊ̤Υե¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¸ºß¤¹¤ë
             ²ÄǽÀ­¤Î¤¢¤ë <filename>/usr/local/bin</filename> ¤Ë
             ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤ë¤³¤È¤¬Â¿¤¤¤Î¤Ç¡¢¤³¤ì¤Ï½ÅÍפǤ¹¡£
             <username>root</username> ¤Î¥·¥§¥ë¤¬
             <filename>/usr/local/bin</filename> ¤Ë¤¢¤ê¡¢
             <filename>/usr</filename>
             (¤Þ¤¿¤Ï¡¢<filename>/usr/local/bin</filename>
             ¤¬¤¢¤ë¤¤¤º¤ì¤«¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à)
             ¤¬²¿¤é¤«¤ÎÍýͳ¤Ç¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤Ê¤¤¤È¤¹¤ë¤È¡¢
             <username>root</username> ¤ÏÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Ë
             ¥í¥°¥¤¥ó¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó (¥·¥ó¥°¥ë¥æ¡¼¥¶¡¼¥â¡¼¥É¤ÇºÆµ¯Æ°¤¹¤ì¤Ð¡¢
             ¥·¥§¥ë¤Î¥Ñ¥¹¤ÎÆþÎϤòÂ¥¤µ¤ì¤ë¤Î¤Ç¤¹¤¬)¡£</para>
 
           <para><username>toor</username> ¤òÆü¡¹¤Î root ¤Î»Å»ö¤ò
             Èóɸ½à¤Î¥·¥§¥ë¤Ç¹Ô¤¦¤¿¤á¤Ë»È¤¤¡¢<username>root</username> ¤Ï
             ¥·¥ó¥°¥ë¥æ¡¼¥¶¡¼¥â¡¼¥É¤ä¶ÛµÞ»þ¤Î¤¿¤á¤Ë¡¢É¸½à¤Î¥·¥§¥ë¤Î¤Þ¤Þ¤Ë
             ¤·¤Æ¤¤¤ë¿Í¤¬¤¤¤Þ¤¹¡£²¿¤â¤·¤Ê¤±¤ì¤Ð¡¢¥Ñ¥¹¥ï¡¼¥É¤ò̵¸ú¤Ë¤·¤Æ¤¢¤ë¤Î¤Ç
             <username>toor</username> ¤Ç¤Ï¥í¥°¥¤¥ó¤Ç¤­¤Þ¤»¤ó¡£
             »È¤¤¤¿¤¤¤Ê¤é¡¢<username>root</username> ¤Ç¥í¥°¥¤¥ó¤·¤Æ <username>toor</username> ¤Î
             ¥Ñ¥¹¥ï¡¼¥É¤òÀßÄꤷ¤Þ¤·¤ç¤¦¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="forgot-root-pw">
           <para>¤·¤Þ¤Ã¤¿! root ¤Î¥Ñ¥¹¥ï¡¼¥É¤ò˺¤ì¤Æ¤·¤Þ¤Ã¤¿!</para>
         </question>
 
         <answer>
           <para>
             ¹²¤Æ¤Ê¤¤¤Ç¤¯¤À¤µ¤¤! ñ¤Ë¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¡¢
             ¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤Ë°Ü¤ë¤¿¤á¤Ë <prompt>Boot:</prompt>
             ¤Èɽ¼¨¤µ¤ì¤ë¥×¥í¥ó¥×¥È¤Ç <userinput>boot -s</userinput>
             ¤ÈÆþÎϤ·¤Æ¤¯¤À¤µ¤¤
             (FreeBSD ¤Î 3.2 ¤è¤êÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï
             <userinput>-s</userinput>¤È¤Ê¤ê¤Þ¤¹)¡£
             ¤É¤Î¥·¥§¥ë¤ò»È¤¦¤Î¤«¤È¤¤¤¦¼ÁÌä¤Ë¤Ï¡¢ENTER
             ¥­¡¼¤ò²¡¤·¤Æ¤¯¤À¤µ¤¤¡£&prompt.root;
             ¤Ë°Ü¤ë¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£
             <command>mount -u /</command> ¤ÈÆþÎϤ·¤Æ
             ¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÆɤ߽ñ¤­¤òºÆ¥Þ¥¦¥ó¥È¤·¡¢
             <command>mount -a</command> ¤ÈÆþÎϤ·¤Æ¡¢
             ¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Þ¥¦¥ó¥È¤·Ä¾¤·¤¿¸å¡¢
             <command>passwd root</command>
             ¤ÈÆþÎϤ·¤Æ <username>root</username>
             ¤Î¥Ñ¥¹¥ï¡¼¥É¤òÀßÄꤷľ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤Î¸å¡¢<command>exit</command>
             ¤ÈÆþÎϤ¹¤ì¤Ð¡¢µ¯Æ°¤¬Â³¤±¤é¤ì¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="CAD-reboot">
           <para>
             <keycap>Control</keycap>-<keycap>Alt</keycap>-<keycap>Delete</keycap>
             ¤Ç¥·¥¹¥Æ¥à¤¬ºÆµ¯Æ°¤·¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤¤¤¤?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 2.2.7-RELEASE °Ê¹ß¤Ç syscons (¥Ç¥Õ¥©¥ë¥È¤Î¥³¥ó¥½¡¼¥ë¥É¥é¥¤¥Ð)
             ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢¼¡¤Î¹Ô¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤ËÄɲä·¤Æ
             ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¡¢¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>options SC_DISABLE_REBOOT</programlisting>
 
           <para>
             FreeBSD 2.2.5-RELEASE °Ê¹ß¤Ç PCVT ¥³¥ó¥½¡¼¥ë¥É¥é¥¤¥Ð¤ò»ÈÍѤ·¤Æ¤¤¤ë
             ¾ì¹ç¤Ë¤Ï¡¢Æ±Íͤ˼¡¤Î¹Ô¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤ËÄɲä·¤Æ
             ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¡¢¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>options PCVT_CTRL_ALT_DEL</programlisting>
 
           <para>
             ¾å¤Ë¤¢¤²¤¿¤â¤Î¤è¤ê¤â¸Å¤¤ FreeBSD ¤Î¾ì¹ç¡¢
             ¸½ºß¥³¥ó¥½¡¼¥ë¤¬»ÈÍѤ·¤Æ¤¤¤ë¥­¡¼¥Þ¥Ã¥×¤òÊÔ½¸¤·¡¢
             ¥­¡¼¥ï¡¼¥É
             <literal>boot</literal> ¤ò
             <literal>nop</literal> ¤Ë½ñ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£
             <filename>/usr/share/syscons/keymaps/us.iso.kbd</filename>
             ¤Ë¤¢¤ê¤Þ¤¹¡£
             ¤½¤ÎÊѹ¹¤òÈ¿±Ç¤µ¤»¤è¤¦¤È¤·¤Æ¡¢
             ¤³¤Î¥­¡¼¥Þ¥Ã¥×¤Î¥í¡¼¥É¤òÌÀ¼¨Åª¤Ë¹Ô¤Ê¤¦¤¿¤á¤Ë¡¢
             <filename>/etc/rc.conf</filename> ¤ò¼Â¹Ô¤¹¤Ù¤­¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ¤â¤Á¤í¤ó¾¤Î¹ñ¤Î¥­¡¼¥Þ¥Ã¥×¤ò»È¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
             Âå¤ï¤ê¤Ë¤½¤Î¥­¡¼¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dos-to-unix-txt">
           <para>DOS ¤Î¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤ò UNIX
             ¤Î¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤ËÀ°·Á¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤¤¤¤?</para>
         </question>
 
         <answer>
           <para>
             ñ¤Ë¼¡¤Î perl ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.user; <userinput>perl -i.bak -npe 's/\r\n/\n/g' file ...</userinput></screen>
 
 
           <para>
             file
             ¤ÎÉôʬ¤Ë¤Ï½èÍý¤¹¤ë¥Õ¥¡¥¤¥ë¤ò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
             À°·Á¸å¤Î¥Õ¥¡¥¤¥ë¤Ï¸µ¤Î¥Õ¥¡¥¤¥ë̾¤ÇºîÀ®¤µ¤ì¡¢
             À°·ÁÁ°¤Î¥Õ¥¡¥¤¥ë¤Ï¥Ð¥Ã¥¯¥¢¥Ã¥×¤È¤·¤Æ¸µ¤Î
             ¥Õ¥¡¥¤¥ë̾¤ÎËöÈø¤Ë³ÈÄ¥»Ò
             <filename>.bak</filename> ¤Î¤Ä¤±¤é¤ì¤¿Ì¾Á°¤ÇºîÀ®¤µ¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             ¤¢¤ë¤¤¤Ï
             &man.tr.1;
             ¥³¥Þ¥ó¥É¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.user; <userinput>tr -d '\r' &lt; <replaceable>dos-text-file</replaceable> &gt; <replaceable>unix-file</replaceable></userinput></screen>
 
           <para>
             <replaceable>dos-text-file</replaceable> ¤Ï
             DOS ·Á¼°¤Î¥Æ¥¹¥È¥Õ¥¡¥¤¥ë¡¢
             <replaceable>unix-file</replaceable>
             ¤Ë¤ÏÊÑ´¹¤µ¤ì¤¿½ÐÎϤ¬³ÊǼ¤µ¤ì¤Þ¤¹¡£
             perl ¤ò»È¤¦¤è¤ê¤Û¤ó¤Î¤Á¤ç¤Ã¤Ô¤ê®¤¯¤Ê¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="kill-by-name">
           <para>̾Á°¤Ç»ØÄꤷ¤Æ¥×¥í¥»¥¹¤Ë¥·¥°¥Ê¥ë¤òÁ÷¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤¤¤¤?</para>
         </question>
 
         <answer>
           <para>
             &man.killall.1;
             ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="root-acl">
           <para>su ¤¬ not in <username>root</username>'s ACL
             ¤È¸À¤Ã¤Æ»ä¤òǺ¤Þ¤»¤ë¤Î¤Ï¤Ê¤¼?</para>
         </question>
 
         <answer>
           <para>Kerberos ¤Îǧ¾Ú¥·¥¹¥Æ¥à¤«¤é¤¯¤ë¥¨¥é¡¼¤Ç¤¹¡£
             ¤³¤ÎÌäÂê¤ÏÃ×̿Ū¤Ê¤â¤Î¤Ç¤Ï¤Ê¤¯¡¢
             ¤¦¤Ã¤È¤ª¤·¤¤¤È¤¤¤Ã¤¿¤â¤Î¤Ç¤¹¡£
             <command>su</command> ¤Ë <option>-K</option>
             ¥ª¥×¥·¥ç¥ó¤ò¤Ä¤±¤Æµ¯Æ°¤¹¤ë¤«¡¢
             ¼¡¤Î¼ÁÌä¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ëÊýË¡¤Ç Kerberos
             ¤ò¥¢¥ó¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="uninstall-kerberos">
           <para>Kerberos ¤ò¥¢¥ó¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤¤¤¤¤Î?</para>
         </question>
 
         <answer>
           <para>
             ¥·¥¹¥Æ¥à¤«¤é Kerberos ¤òºï½ü¤¹¤ë¤Ë¤Ï¡¢
             ¤¢¤Ê¤¿¤ÎÆ°¤«¤·¤Æ¤¤¤ë¥ê¥ê¡¼¥¹¤Î
             bin ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤òºÆ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤â¤· CDROM ¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤Ê¤é¡¢
             ¤½¤Î CDROM ¤ò¥Þ¥¦¥ó¥È (¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤Ï
             <filename>/cdrom</filename> ¤È²¾Äê) ¤·¤Æ¡¢
             ¼¡¤Î¤è¤¦¤ËÆþÎϤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>cd /cdrom/bin</userinput>
 &prompt.root; <userinput>./install.sh</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="add-pty">
           <para>µ¿»÷¥¿¡¼¥ß¥Ê¥ë¤òÄɲ乤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             telnet¡¢ssh¡¢X¡¢screen ¤ò¤¿¤¯¤µ¤óÍøÍѤµ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢
             µ¿»÷¥¿¡¼¥ß¥Ê¥ë¤¬Â­¤ê¤Ê¤¯¤Ê¤Ã¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤òÁý¤ä¤¹¤Ë¤Ï¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
             <procedure>
               <step>
                 <para>
                   ¼¡¤Î¹Ô¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤ËÄɲä·¤Æ
 
                   <programlisting>pseudo-device pty 256</programlisting>
 
                   ¿·¤¿¤Ë¥«¡¼¥Í¥ë¤òºî¤ê¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
                 </para>
               </step>
 
               <step>
                 <para>
                   ¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ
 
                   <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV pty{1,2,3,4,5,6,7}</userinput></screen>
 
                   ¿·¤¿¤Ê¥¿¡¼¥ß¥Ê¥ëÍѤΠ256 ¸Ä¤Î¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤òºî¤ê¤Þ¤¹¡£
                 </para>
               </step>
 
               <step>
                 <para>
                   <filename>/etc/ttys</filename> ¤òÊÔ½¸¤·
                   256 ¸Ä¤Î¥¿¡¼¥ß¥Ê¥ë¤´¤È¤ÎÄêµÁ¤òÄɲä·¤Þ¤¹¡£
                   ´û¸¤Î¥¨¥ó¥È¥ê¡¼¤Î·Á¼°¤Ë¤¢¤ï¤»¤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£
                   ¤¿¤È¤¨¤Ð¤³¤ó¤Ê´¶¤¸¤Ç¤¹¡£
                 </para>
 
                   <programlisting>ttyqc none network</programlisting>
 
                 <para>
                   Àµµ¬É½¸½¤ò»È¤Ã¤¿»ØÄê¤Ï
                   <literal>tty[pqrsPQRS][0-9a-v]</literal>
                   ¤È¤Ê¤ê¤Þ¤¹¡£
                 </para>
               </step>
 
               <step>
                 <para>
                   ¿·¤·¤¤¥«¡¼¥Í¥ë¤Ç¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤¹¤ë¤È´°Î»¤Ç¤¹¡£
                 </para>
               </step>
             </procedure>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="create-snd0">
           <para>
             <devicename>snd0</devicename>
             ¥Ç¥Ð¥¤¥¹¤òºîÀ®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó!</para>
         </question>
 
         <answer>
           <para><devicename>snd</devicename> ¤È¤¤¤¦¥Ç¥Ð¥¤¥¹¤Ï¸ºß¤·¤Þ¤»¤ó¡£
             ¤³¤Î̾Á°¤Ï¡¢FreeBSD
             ¥µ¥¦¥ó¥É¥É¥é¥¤¥Ð¤Ë¤è¤Ã¤ÆºîÀ®¤µ¤ì¤ë¤µ¤Þ¤¶¤Þ¤Ê¥Ç¥Ð¥¤¥¹¡¢
             <devicename>mixer</devicename> ¤ä
             <devicename>sequencer</devicename>¡¢
             <devicename>dsp</devicename>
             ¤Ê¤É¤òÁí¾Î¤·¤¿¤â¤Î¤Ç¤¹¡£
           </para>
 
           <para>¤³¤ì¤é¤Î¥Ç¥Ð¥¤¥¹¤òºîÀ®¤¹¤ë¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV snd0</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="reread-rc">
           <para>ºÆµ¯Æ°¤»¤º¤Ë¤â¤¦°ìÅÙ
             <filename>/etc/rc.conf</filename>
             ¤òÆɤ߹þ¤ó¤Ç
             <filename>/etc/rc</filename>
             ¤ò³«»Ï¤µ¤»¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             ¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤Ë°Ü¹Ô¤·¤Æ¡¢
             ¥Þ¥ë¥Á¥æ¡¼¥¶¥â¡¼¥É¤ËÌá¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¥³¥ó¥½¡¼¥ë¤Ç¼¡¤Î¤è¤¦¤Ë¼Â¹Ô¤·¤Þ¤¹¡£
 
             <screen>&prompt.root; <userinput>shutdown now</userinput><emphasis>(Ãí: <option>-r</option> ¤ä <option>-h</option> ¤ÏÉÕ¤±¤Þ¤»¤ó)</emphasis>
 &prompt.root; <userinput>return</userinput>
 &prompt.root; <userinput>exit</userinput></screen>
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sandbox">
           <para>º½¾ì (sandbox) ¤È¤Ï²¿¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para><quote>º½¾ì (Sandbox)</quote> ¤È¤Ï¥»¥­¥å¥ê¥Æ¥£ÍѸì¤Î°ì¤Ä¤Ç¡¢
             ¼¡¤ÎÆó¤Ä¤Î°ÕÌ£¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
             <itemizedlist>
               <listitem>
                 <para>
                   °ì¤ÄÌܤϡ¢¡Ö²¾ÁÛŪ¤Ê¡ØËÉÊɡ٤ǰϤޤì¤Æ¤¤¤ë¥×¥í¥»¥¹¡×¤Ç¤¹¡£
                   ¤½¤Î¡ØËÉÊɡ٤ϡ¢¤½¤Î¥×¥í¥»¥¹¤Ë¿¯Æþ¤·¤¿Âè»°¼Ô¤¬¡¢
                   ¤µ¤é¤Ë¥·¥¹¥Æ¥à¤Î¹­¤¤ÈϰϤ˱ƶÁ¤òÍ¿¤¨¤ë¤³¤È¤òËɤ°¤è¤¦¤ËÀ߷פµ¤ì¤Þ¤¹¡£
                 </para>
 
                 <para>
                   ¤³¤Î¥×¥í¥»¥¹¤Î¿¶Éñ¤¤¤Ï¡¢¡ØËÉÊÉ¡Ù¤ÎÃæ¤À¤±¤ËÀ©¸Â¤µ¤ì¤ë¡¢¤Èɽ¸½¤Ç¤­¤Þ¤¹¡£
                   ¤Ä¤Þ¤ê¡¢¤³¤Î¥×¥í¥»¥¹¤Ë¤ª¤¤¤Æ¡¢¡ØËÉÊÉ¡Ù¤ò±Û¤¨¤ë¤è¤¦¤Ê¥³¡¼¥É¤Î¼Â¹Ô¤Ï
                   ¤Ç¤­¤Ê¤¤¤È¤¤¤¦°ÕÌ£¤Ç¤¹¡£¤½¤Î¤¿¤á¡¢¥³¡¼¥É¤Î¼Â¹Ô¤Ë¤ª¤±¤ë¥»¥­¥å¥ê¥Æ¥£¤Ï
                   ³Î¤«¤Ê¤â¤Î¤Ç¤¢¤ë¤ÈÊݾڤǤ­¡¢¼Â¹Ô¤Î¾ÜºÙ¤ÊÄÉÀפò¹Ô¤Ê¤¦É¬ÍפϤʤ¯¤Ê¤ê¤Þ¤¹¡£
                 </para>
 
                 <para>
                   ¤½¤Î¡ØËÉÊɡ٤Ȥϡ¢¤¿¤È¤¨¤Ð¥æ¡¼¥¶ ID ¤¬¤½¤ì¤Ë¤¢¤¿¤ë¤Ç¤·¤ç¤¦¡£
                   ¤³¤ÎÄêµÁ¤Ï¡¢security(7) ¤ä named(8) ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ÇÍѤ¤¤é¤ì¤Æ¤¤¤Þ¤¹¡£
                 </para>
 
                 <para>
                   <literal>ntalk</literal>
                   ¥µ¡¼¥Ó¥¹ (/etc/inetd.conf
                   »²¾È¤Î¤³¤È) ¤òÎã¤Ë¤È¤Ã¤Æ¤ß¤Þ¤¹¡£
                   ¤³¤Î¥µ¡¼¥Ó¥¹¤Ï¤«¤Ä¤Æ¡¢¼Â¹Ô»þ¤Î ¥æ¡¼¥¶ ID ¤È¤·¤Æ
                   root
                   ¤òÍѤ¤¤Æ¤¤¤Þ¤·¤¿¤¬¡¢¸½ºß¤Ç¤Ï
                   tty
                   ¤È¤¤¤¦¥æ¡¼¥¶ ID ¤ÇÆ°ºî¤·¤Þ¤¹¡£
                   ¥æ¡¼¥¶
                   tty ¤Ï¡¢
                   ntalk ¤ò·Ðͳ¤·¤Æ¥·¥¹¥Æ¥à¤Î¿¯Æþ¤ËÀ®¸ù¤·¤¿Âè»°¼Ô¤¬
                   ¤½¤Î¥æ¡¼¥¶ ID °Ê¾å¤Î¸¢¸Â¤òÆÀ¤ë¤³¤È¤ò¡¢
                   ¤è¤ê°ìÁغ¤Æñ¤Ë¤¹¤ë¤¿¤á¤ËÀ߷פµ¤ì¤¿º½¾ì (sandbox) ¤Ê¤Î¤Ç¤¹¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   Æó¤ÄÌܤϡ֥·¥ß¥å¥ì¡¼¥È¤µ¤ì¤¿¥Þ¥·¥ó¤ÎÆ⦤Ǽ¹Ԥµ¤ì¤ë¥×¥í¥»¥¹¡×¤Î¤³¤È¤Ç¡¢
                   ¤³¤Á¤é¤Ï¤è¤êÃæ³ËŪ¤Ç¤¹¡£
                   ÉáÄ̤˹ͤ¨¤ì¤Ð¡¢¤¢¤ë¥×¥í¥»¥¹¤Ë¿¯Æþ¤¹¤ë¤³¤È¤¬¤Ç¤­¤ëÂè»°¼Ô¤Ï¡¢
                   ¥Þ¥·¥ó¤Î¤è¤ê¹­¤¤ÈϰϤˤ⿯Æþ¤Ç¤­¤ë¤È¿®¤¸¤ë¤â¤Î¤Ê¤Î¤Ç¤¹¤¬¡¢
                   ¤³¤Î¼ï¤Î¥×¥í¥»¥¹¤Î¾ì¹ç¡¢¤½¤ì¤Ï¼ÂºÝ¤Ë¤Ï¥·¥ß¥å¥ì¡¼¥È¤µ¤ì¤¿¥Þ¥·¥ó¤Ë
                   ¿¯Æþ¤·¤¿¤À¤±¤Ê¤Î¤Ç¡¢¸½¼Â¤Î¥Ç¡¼¥¿¤òÊѹ¹¤¹¤ë¤³¤È¤Ï²¿°ì¤Ä¤Ç¤­¤Þ¤»¤ó¡£
                 </para>
 
                 <para>
                   ¤³¤ì¤ò¼Â¸½¤¹¤ë¤¿¤á¤ÎºÇ¤â¹­¤¯ÍѤ¤¤é¤ì¤Æ¤¤¤ëÊýË¡¤Ï¡¢
                   ¥·¥ß¥å¥ì¡¼¥È¤µ¤ì¤¿´Ä¶­¤ò¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¹½ÃÛ¤·¡¢
                   ¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë chroot ¤·¤Æ¡¢¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ç
                   ¥×¥í¥»¥¹¤ò¼Â¹Ô¤¹¤ë¤³¤È (¤Ä¤Þ¤ê¡¢¤½¤Î¥×¥í¥»¥¹¤Ë¤È¤Ã¤Æ
                   <filename>/</filename> ¤Ï
                   ¥·¥¹¥Æ¥à¤Î¼ÂºÝ¤Î¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê
                   <filename>/</filename> ¤Ç¤Ï¤Ê¤¯¡¢
                   chroot ¤µ¤ì¤¿¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ò»Ø¤¹) ¤Ç¤¹¡£
                 </para>
 
                 <para>
                   ¹­¤¯ÍѤ¤¤é¤ì¤Æ¤¤¤ë¤â¤¦°ì¤Ä¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£
                   ¤½¤ì¤Ï¡¢´û¤Ë¸ºß¤·¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò
                   Æɤ߹þ¤ßÀìÍÑ (read-only) ¤Ç¥Þ¥¦¥ó¥È¤·¡¢¤½¤Î¾å¤Ë¡¢¤¢¤ë¥×¥í¥»¥¹¤ËÂФ·¤Æ
                   ¤½¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬½ñ¤­¹þ¤ß²Äǽ¤Ç¤¢¤ë¤è¤¦¤Ë¸«¤»¤ë¤è¤¦¤Ê¡¢
                   ¤â¤¦°ì¤Ä¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÁؤòÍÑ°Õ¤¹¤ë¤â¤Î¤Ç¤¹¡£¤¹¤ë¤È¡¢
                   ¤½¤Î¥×¥í¥»¥¹¤Ï¥Õ¥¡¥¤¥ë¤ò½ñ¤­¹þ¤à¤³¤È¤¬¤Ç¤­¤ë¤Èǧ¼±¤·¡¢
                   ¼ÂºÝ¤Ë½ñ¤­¹þ¤à¤³¤È¤¬¤Ç¤­¤ë¤Î¤â¤½¤ÎÆÃÄê¤Î¥×¥í¥»¥¹¤À¤±
                   - ¥·¥¹¥Æ¥à¤Ë¤¢¤ë¾¤Î¥×¥í¥»¥¹¤Ï½ñ¤­¹þ¤á¤Ê¤¤¤Î¤ËÂФ·¤Æ -
                   ¤Ç¤¢¤ë¤È¤¤¤¦¾õ¶·¤ò¼Â¸½¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
                 </para>
 
                 <para>
                   ¤³¤Î¼ï¤Îº½¾ì (sandbox) ¤Ï¡¢
                   ¤½¤ÎÈó¾ï¤ËÆ©²áŪ¤ÊÀ­¼Á¤ò»È¤Ã¤Æ¡¢¥æ¡¼¥¶ (¤â¤·¤¯¤Ï¿¯Æþ¼Ô) ¤¬
                   ¤½¤Î»ö¼Â¤Ëµ¤ÉÕ¤«¤Ê¤¤¤è¤¦¤Ë¼Â¸½¤µ¤ì¤Þ¤¹¡£
                 </para>
               </listitem>
             </itemizedlist>
 
           <para>
             UNIX ¤Ï¡¢ÆâÉôŪ¤ËÆó¤Ä¤Îº½¾ì (sandbox) ¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£
             °ì¤Ä¤Ï¥×¥í¥»¥¹¥ì¥Ù¥ë¤Î¤â¤Î¡¢¤â¤¦°ì¤Ä¤Ï¥æ¡¼¥¶ ID ¥ì¥Ù¥ë¤Î¤â¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             UNIX ¥×¥í¥»¥¹¤Ï¤¹¤Ù¤Æ¡¢Â¾¤Î UNIX ¥×¥í¥»¥¹¤«¤é´°Á´¤Ë³ÖÎ¥¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤É¤Î¥×¥í¥»¥¹¤â¡¢Â¾¤Î¥×¥í¥»¥¹¤Î¥¢¥É¥ì¥¹¶õ´Ö¤òÊѹ¹¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
             ¤³¤ì¤Ï¡¢¤¢¤ë¥×¥í¥»¥¹¤¬Â¾¤Î¥×¥í¥»¥¹¤Î¥¢¥É¥ì¥¹¶õ´Ö¤ò¾å½ñ¤­¤Ç¤­¤ë¤è¤¦¤Ê¡¢
             ¥¯¥é¥Ã¥·¥å¤Ë¤Ä¤Ê¤¬¤ë¹Ô°Ù¤¬Íưפ˼¸½¤Ç¤­¤ë Windows ¤È¤ÏÁ´¤¯°Û¤Ê¤ë¤â¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             UNIX ¥×¥í¥»¥¹¤Ï¡¢ÆÃÄê¤Î¥æ¡¼¥¶ ID ¤¬½êÍ­¤·¤Þ¤¹¡£
             ¤â¤·¡¢¼Â¹Ô¼Ô¤Î¥æ¡¼¥¶ ID ¤¬ <username>root</username>
             ¥æ¡¼¥¶¤Î¤â¤Î¤Ç¤Ê¤±¤ì¤Ð¡¢
             ¥æ¡¼¥¶ ID ¤Ï¡¢Â¾¤Î¥æ¡¼¥¶¤¬½êÍ­¤¹¤ë¥×¥í¥»¥¹¤«¤é
             ¤½¤Î¥×¥í¥»¥¹¤ò¼é¤ëµ¡Ç½¤ò²Ì¤¿¤¹¤ï¤±¤Ç¤¹¡£
             ¤Þ¤¿¡¢¤½¤Î¥æ¡¼¥¶ ID ¤Ï¡¢¥Ç¥£¥¹¥¯¾å¤Ë¤¢¤ë¥Ç¡¼¥¿¤ò
             Êݸ¤ë¤Î¤Ë¤â»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="securelevel">
           <para>¥»¥­¥å¥¢¥ì¥Ù¥ë (securelevel) ¤Ã¤Æ²¿¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¥»¥­¥å¥¢¥ì¥Ù¥ë¤È¤Ï¥«¡¼¥Í¥ë¤Ë¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë¥»¥­¥å¥ê¥Æ¥£µ¡¹½¤Î°ì¤Ä¤Ç¤¹¡£
             ´Êñ¤Ë¸À¤¦¤È¡¢¥«¡¼¥Í¥ë¤Ï¥»¥­¥å¥¢¥ì¥Ù¥ë¤¬Àµ¤ÎÃͤλþ¤Ë¡¢
             ¤¢¤ëÆÃÄê¤ÎÁàºî¤òÀ©¸Â¤·¤Þ¤¹¡£¤³¤ÎÀ©¸Â¤Ï¡¢¤¿¤È¤¨¥¹¡¼¥Ñ¥æ¡¼¥¶
             (<username>root</username> ¤Î¤³¤È) ¤Ç¤¢¤Ã¤Æ¤âÎã³°¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¤³¤Îʸ¤ò½ñ¤¤¤Æ¤¤¤ë»þÅÀ¤Ç¤Ï¡¢
             ¥»¥­¥å¥¢¥ì¥Ù¥ëµ¡¹½¤ò»È¤Ã¤Æ°Ê²¼¤Î¤è¤¦¤ÊÁàºî¤òÀ©¸Â¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
           <itemizedlist>
             <listitem>
               <para>
                 <literal>schg</literal> (system immutable flag)
                 ¤Î¤è¤¦¤Ê¥Õ¥¡¥¤¥ë¥Õ¥é¥°¤ÎÊѹ¹</para>
             </listitem>
 
             <listitem>
               <para><devicename>/dev/mem</devicename> ¤ª¤è¤Ó
                 <devicename>/dev/kmem</devicename>
                 ·Ðͳ¤Ç¤Î¥«¡¼¥Í¥ë¥á¥â¥ê¤Ø¤Î½ñ¤­¹þ¤ß</para>
             </listitem>
 
             <listitem>
               <para>¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤Î¥í¡¼¥É</para>
             </listitem>
 
             <listitem>
               <para>&man.ipfirewall.4; ¥ë¡¼¥ë¤ÎÊѹ¹</para>
             </listitem>
           </itemizedlist>
 
           <para>²ÔƯÃæ¤Î¥·¥¹¥Æ¥à¤Ç¥»¥­¥å¥¢¥ì¥Ù¥ë¤Î¾õÂÖ¤ò¥Á¥§¥Ã¥¯¤¹¤ë¤Ë¤Ï¡¢
             ¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
 
           <para>½ÐÎϤˤϡ¢&man.sysctl.8; ÊÑ¿ô (º£¤Î¾ì¹ç¤Ï
             <varname>kern.securelevel</varname>) ¤È¿ô»ú¤¬¸½¤ì¤Þ¤¹¡£
             ¿ô»ú¤¬¸½ºß¤Î¥»¥­¥å¥¢¥ì¥Ù¥ë¤ÎÃͤǤ¹¡£
             ¤³¤ì¤¬¤â¤·Àµ¤ÎÃͤʤ顢
             ²¿¤é¤«¤Î¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ë¤è¤ëÀ©¸Â¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
 
           <para>¥·¥¹¥Æ¥à²ÔƯÃæ¤Ë¥»¥­¥å¥¢¥ì¥Ù¥ë¤ò²¼¤²¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
             ¤³¤ì¤Ï¡¢¤½¤ì¤ò²Äǽ¤Ë¤¹¤ë¤È¥»¥­¥å¥¢¥ì¥Ù¥ë¤Î°ÕÌ£¤¬¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¦¤«¤é¤Ç¤¹¡£
             ¥»¥­¥å¥¢¥ì¥Ù¥ë¤¬Àµ¤ÎÃͤǤʤ¤¤³¤È¤òÍ׵᤹¤ëÁàºî
             (¤¿¤È¤¨¤Ð <maketarget>installworld</maketarget> ¤äÆüÉÕ¤ÎÊѹ¹¤Ê¤É)
             ¤ò¹Ô¤Ê¤¦É¬Íפ¬¤¢¤ë¾ì¹ç¤Ï¡¢<filename>/etc/rc.conf</filename>
             ¤Ë¤¢¤ë¥»¥­¥å¥¢¥ì¥Ù¥ë¤ÎÀßÄê (<varname>kern_securelevel</varname> ¤È
             <varname>kern_securelevel_enable</varname> ¤È¤¤¤¦ÊÑ¿ô)
             ¤òÊѹ¹¤·¤ÆºÆµ¯Æ°¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ë´Ø¤¹¤ë¾Ü¤·¤¤¾ðÊó¤ä¡¢
             ³Æ¥ì¥Ù¥ë¤Ç¼Â¸½¤µ¤ì¤ëµ¡Ç½¤Ë´Ø¤·¤Æ¤Ï
             &man.init.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
             <warning>
               <para>¥»¥­¥å¥¢¥ì¥Ù¥ë¤ÏËüǽ¤È¤¤¤¦¤ï¤±¤Ç¤Ï¤Ê¤¯¡¢
                 ¼åÅÀ¤â¿ô¿¤¯Â¸ºß¤·¤Þ¤¹¡£¤Þ¤¿¡¢¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï¡¢
                 ¥»¥­¥å¥ê¥Æ¥£¤òÄã²¼¤µ¤»¤Æ¤·¤Þ¤¦¤³¤È¤â¤¢¤ê¤Þ¤¹¡£</para>
 
               <para>ºÇ¤âÂ礭¤ÊÌäÂê¤Î°ì¤Ä¤Ë¡¢
                 ¥»¥­¥å¥¢¥ì¥Ù¥ë¤Îµ¡Ç½¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢
                 µ¯Æ°½èÍý¤Ç¥»¥­¥å¥¢¥ì¥Ù¥ë¤¬ÀßÄꤵ¤ì¤ë¤Þ¤Ç¤Ë»È¤ï¤ì¤ë¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò
                 Êݸ¤ëɬÍפ¬¤¢¤ë¤È¤¤¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
                 ¤â¤·¹¶·â¼Ô¤¬¡¢¥·¥¹¥Æ¥à¤¬¥»¥­¥å¥¢¥ì¥Ù¥ë¤òÀßÄꤹ¤ëÁ°¤Ë¥³¡¼¥É¤ò¼Â¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤È¤·¤¿¤é¡¢
                 ¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ë¤è¤ëÊݸî¤Ï̵°ÕÌ£¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹
                 (µ¯Æ°»þ¤Ë¤ÏÄ㤤¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ç¤·¤«¼Â¹Ô¤Ç¤­¤Ê¤¤½èÍý¤ò¹Ô¤Ê¤¦É¬Íפ¬¤¢¤ë¤¿¤á¡¢
                 ¥»¥­¥å¥¢¥ì¥Ù¥ë¤ÎÀßÄê¤Ï¡¢µ¯Æ°½èÍý¤ÎºÇ¸å¤ÎÊý¤Ç¹Ô¤Ê¤ï¤ì¤Þ¤¹)¡£
                 µ¯Æ°½èÍý¤Ç»È¤ï¤ì¤ë¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤òÊݸ¤ë¤³¤È¤Ïµ»½ÑŪ¤ËÉÔ²Äǽ¤Ç¤¹¡£
                 ¤â¤·¤½¤¦¤Ç¤­¤¿¤È¤·¤Æ¤â¡¢¥·¥¹¥Æ¥à¤ÎÊݼé¤Ï¤Þ¤µ¤Ë°­Ì´¤È¤Ê¤ë¤Ç¤·¤ç¤¦¡£
                 ÀßÄê¥Õ¥¡¥¤¥ë°ì¤Ä½ñ¤­´¹¤¨¤ë¤Î¤Ë¤â¡¢
                 ¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤ËÀÚÂؤ¨¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¯¤Ê¤ë¤Î¤Ç¤¹¤«¤é¡£
               </para>
 
               <para>°Ê¾å¤ÇÀâÌÀ¤·¤¿ÆâÍƤ䤽¤Î¾¤ÎÅÀ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
                 ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ç¤âÎɤ¯ÏÃÂê¤Ë¤Î¤Ü¤ê¤Þ¤¹¡£
                 µÄÏÀ¤Î¤è¤¦¤¹¤ò<ulink url="http://www.FreeBSD.org/search/">¤³¤Î¥Ú¡¼¥¸</ulink>¤«¤é¸¡º÷¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
                 ¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ï¡¢
                 ¤¤¤º¤ì¤è¤êγÅ٤κ٤«¤¤µ¡¹½¤Ë¤È¤Ã¤ÆÂå¤ï¤ë¤À¤í¤¦¤È¹Í¤¨¤Æ¤¤¤ë¿Í¡¹¤â¤¤¤Þ¤¹¤¬¡¢
                 ¤½¤ÎÅÀ¤Ë¤Ä¤¤¤Æ¤Ï¤Þ¤ÀÉÔÆ©ÌÀ¤Ê¤Þ¤Þ¤Ç¤¹¡£
               </para>
 
               <para>¤É¤¦¤«Ãí°Õ¤¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
             </warning>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="user-floppymount">
           <para>¥Õ¥í¥Ã¥Ô¡¼¤ä CDROM ¤ä¾¤Î¥ê¥à¡¼¥Ð¥Ö¥ë¥á¥Ç¥£¥¢¤Î¥Þ¥¦¥ó¥È¤ò°ìÈ̥桼¥¶¡¼¤Ëµö²Ä¤¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             °ìÈ̥桼¥¶¡¼¤Ç¤â¥Ç¥Ð¥¤¥¹¤ò¥Þ¥¦¥ó¥È¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¼ê½ç¤Ï¼¡¤Î¤È¤ª¤ê¤Ç¤¹¡£
           </para>
 
           <procedure>
             <step>
               <para><username>root</username>
                 ¤Ë¤Ê¤Ã¤Æ¡¢
                 sysctl ÊÑ¿ô¤Ç¤¢¤ë
                 <varname>vfs.usermount</varname> ¤ò
                 <literal>1</literal> ¤ËÀßÄꤷ¤Þ¤¹¡£
               </para>
 
                 <screen>&prompt.root; <userinput>sysctl -w vfs.usermount=1</userinput></screen>
             </step>
 
             <step>
               <para><username>root</username>
                 ¤Ë¤Ê¤Ã¤Æ¡¢
                 ¥ê¥à¡¼¥Ð¥Ö¥ë¥á¥Ç¥£¥¢¤Ë´ØÏ¢¤¹¤ë¥Ö¥í¥Ã¥¯¥Ç¥Ð¥¤¥¹¤ËŬÀڤʥѡ¼¥ß¥Ã¥·¥ç¥ó¤òÀßÄꤷ¤Þ¤¹¡£
               </para>
 
               <para>
                 Îã¤È¤·¤Æ¡¢ºÇ½é¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥Ð¥¤¥¹¤ò¥æ¡¼¥¶¡¼¤¬¥Þ¥¦¥ó¥È¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢
                 ¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
               </para>
 
               <screen>&prompt.root; <userinput>chmod 666 /dev/fd0</userinput></screen>
               <para>
                 <groupname>operator</groupname> ¥°¥ë¡¼¥×¤Ë½ê°¤¹¤ë¥æ¡¼¥¶¤¬
                 CDROM ¥É¥é¥¤¥Ö¤ò¥Þ¥¦¥ó¥È¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï
                 °Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
               </para>
 
               <screen>&prompt.root; <userinput>chgrp operator /dev/cd0c</userinput>
 &prompt.root; <userinput>chmod 640 /dev/cd0c</userinput></screen>
             </step>
 
             <step>
               <para>
                 ºÇ¸å¤Ë <literal>vfs.usermount=1</literal> ¤È¤¤¤¦¹Ô¤ò
                 <filename>/etc/sysctl.conf</filename> ¥Õ¥¡¥¤¥ë¤ËÄɲä·¡¢
                 ¥Ö¡¼¥È»þ¤Ë¥»¥Ã¥È¤µ¤ì¤ë¤è¤¦¤Ë¤·¤Æ¤ª¤­¤Þ¤¹¡£
               </para>
             </step>
 
           </procedure>
 
           <para>
             ¤³¤ì¤Ç¡¢¤¹¤Ù¤Æ¤Î¥æ¡¼¥¶¤Ï
             ¥Õ¥í¥Ã¥Ô¡¼ <devicename>/dev/fd0</devicename> ¤ò
             ¼«¿È¤Î½êÍ­¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ø¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
 &prompt.user; <userinput>mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
 
           <para>
             ¤³¤ì¤Ç¡¢<groupname>operator</groupname> ¥°¥ë¡¼¥×¤Ë½ê°¤¹¤ë¥æ¡¼¥¶¤Ï
             CDROM <devicename>/dev/cd0c</devicename> ¤ò
             ¼«¿È¤Î½êÍ­¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ø¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
 &prompt.user; <userinput>mount -t msdos /dev/cd0c ~/my-mount-point</userinput>
 </screen>
 
           <para>¥Ç¥Ð¥¤¥¹¤Î¥¢¥ó¥Þ¥¦¥ó¥È¤Ï´Êñ¤Ç¤¹¡£</para>
 
           <screen>&prompt.user; <userinput>umount ~/my-mount-point</userinput></screen>
 
           <para>
             ¤·¤«¤·¡¢
             <varname>vfs.usermount</varname>
             ¤òÍ­¸ú¤Ë¤¹¤ë¤³¤È¤Ï¡¢¥»¥­¥å¥ê¥Æ¥£¾å¤è¤¤¤³¤È¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             MSDOS ·Á¼°¤Î¥á¥Ç¥£¥¢¤Ë¥¢¥¯¥»¥¹¤Ë¤Ï¡¢Ports ¥³¥ì¥¯¥·¥ç¥ó¤Ë¤¢¤ë
             ¥Ñ¥Ã¥±¡¼¥¸
             <ulink url="http://www.freebsd.org/cgi/ports.cgi?query=%5Emtools-&amp;stype=name">mtools</ulink>
             ¤ò»ÈÍѤ·¤¿Êý¤¬¤è¤¤¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="new-huge-disk">
           <para>¥·¥¹¥Æ¥à¤ò¿·¤·¤¤µðÂç¥Ç¥£¥¹¥¯¤Ø°Ü¤¹¤Ë¤Ï¤É¤¦¤¹¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>°ìÈÖÎɤ¤¤Î¤Ï¿·¤·¤¤¥Ç¥£¥¹¥¯¤Ë OS ¤òºÆ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¡¢
             ¤½¤ì¤«¤é¥æ¡¼¥¶¥Ç¡¼¥¿¤ò°Ü¤¹¤³¤È¤Ç¤¹¡£Æäˤ¢¤Ê¤¿¤¬ -stable ¤ò
             Ê£¿ô¤Î¥ê¥ê¡¼¥¹¤ò¸Ù¤¤¤ÇÄɤ¤³Ý¤±¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¤³¤ÎÊýË¡¤ò¤ª¤¹¤¹¤á¤·¤Þ¤¹¡£
             ¤¢¤Ê¤¿¤Ï &man.boot0cfg.8; ¤ò»È¤¦¤³¤È¤Ç booteasy ¤òξÊý¤Î
             ¥Ç¥£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¡¢¿·¤·¤¤ÇÛÃÖ¤ÇËþ­¤·¤Æ¤¤¤ë´Ö
             ¥Ç¥å¥¢¥ë¥Ö¡¼¥È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤ò¹Ô¤Ã¤¿¤¢¤È¥Ç¡¼¥¿¤ò°Ü¤¹
             ÊýË¡¤òõ¤¹¤Ê¤é¼¡¤ÎÃÊÍî¤ÏÆɤßÈô¤Ð¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>²¿¤â¤Ê¤¤¥Ç¥£¥¹¥¯¤Ø¥¤¥ó¥¹¥È¡¼¥ë¤·¤Ê¤¤¤³¤È¤Ë·è¤á¤¿¤Ê¤é¤Ð
             <filename>/stand/sysinstall</filename>¡¢¤Ê¤ê &man.fdisk.8;
             ¤È &man.disklabel.8; ¤Ê¤ê¤ò»È¤Ã¤Æ¿·¤·¤¤¥Ç¥£¥¹¥¯¤Ë
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤È¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òºî¤é¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤Þ¤¿ &man.boot0cfg.8; ¤Ç booteasy ¤òξÊý¤Î¥Ç¥£¥¹¥¯¤Ë
             ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¡¢¥³¥Ô¡¼¤Îºî¶È¤¬½ª¤ï¤Ã¤¿¤¢¤È¤Ë
             ¸Å¤¤¥·¥¹¥Æ¥à¤«¤é¤Ç¤â¿·¤·¤¤¥Ç¥£¥¹¥¯¤«¤é¤Ç¤âµ¯Æ°¤Ç¤­¤ë¤è¤¦¤Ë
             ¤·¤Æ¤ª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£¤³¤Îºî¶È¤Î¾ÜºÙ¤Ï <ulink
             url="http://www.freebsd.org/tutorials/formatting-media/index.html">formatting-media
             tutorial</ulink> ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>¿·¤·¤¤¥Ç¥£¥¹¥¯¤ÎΩ¤Á¾å¤²¤¬½ª¤ï¤Ã¤Æ¥Ç¡¼¥¿¤Î°ÜÆ°¤ò
             ÂԤĤФ«¤ê¤Ë¤Ê¤ê¤Þ¤·¤¿¡£¤·¤«¤·Èᤷ¤¤¤«¤Ê¡¢Ìµ°Ç¤ä¤¿¤é¤È
             ¥³¥Ô¡¼¤¹¤ì¤Ð¤¤¤¤¤È¤¤¤¦¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë
             (<filename>/dev</filename>) ¤ä¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Ê¤É¤Ï
             ¼ºÇԤθµ¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤ì¤é¤òÍý²ò¤¹¤ë¥Ä¡¼¥ë¡¢¤¹¤Ê¤ï¤Á
             &man.dump.8; ¤ä &man.tar.1; Åù¤ò»È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
             ¥Ç¡¼¥¿¤Î°Üž¤Ï¥·¥ó¥°¥ë¥æ¡¼¥¶¤Ç¹Ô¤¦¤³¤È¤ò¤ª´«¤á¤·¤Þ¤¹¤¬¡¢
             ÀäÂФȸÀ¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£</para>
 
           <para>¤¢¤Ê¤¿¤Ï &man.dump.8; ¤È &man.restore.8; °Ê³°¤Î¤â¤Î¤Ç
             root ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò°Ü¹Ô¤·¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
             &man.tar.1; ¥³¥Þ¥ó¥É¤Ç¤â¤¿¤Ö¤ó¤¦¤Þ¤¯¹Ô¤¯¤Ç¤·¤ç¤¦¤¬¡¢
             ¤ä¤é¤Ê¤¤¤Û¤¦¤¬¤¤¤¤¤Ç¤·¤ç¤¦¡£¥Ñ¡¼¥Æ¥£¥·¥ç¥ó°ì¤Ä¤ò
             ¤â¤¦°ì¤Ä¤Î¤«¤é¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë°Ü¤¹¤È¤­¤Ï
             &man.dump.8; ¤È &man.restore.8; »È¤¦¤Ù¤­¤Ç¤¹¡£
             ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¥Ç¡¼¥¿¤ò¿·¤·¤¤¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë°Ü¤¹¤Î¤Ë
             dump ¤ò»È¤¦¤ä¤êÊý¤Ï°Ê²¼¤ÎÄ̤ê¤Ç¤¹¡£</para>
 
           <procedure>
             <step>
               <para>¿·¤·¤¤¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë newfs ¤ò¤«¤±¤ë¡£</para>
             </step>
 
             <step>
               <para>¤½¤ì¤ò»ÃÄêŪ¤Ê¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤Ë¥Þ¥¦¥ó¥È¤¹¤ë¡£</para>
             </step>
 
             <step>
               <para>¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë cd¡£</para>
             </step>
 
             <step>
               <para>¸Å¤¤¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò dump ¤·¡¢
                 ¤½¤Î½ÐÎϤò¥Ñ¥¤¥×¤Ç¿·¤·¤¤Êý¤Ø¡£</para>
             </step>
           </procedure>
 
           <para>¤¿¤È¤¨¤Ð root ¤ò
             <devicename>/dev/ad1s1a</devicename> ¤Ø¡¢»ÃÄêŪ¤Ê¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤ò
             <filename>/mnt</filename> ¤È¤·¤Æ°Ü¤½¤¦¤È¤¹¤ë¤È°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
 &prompt.root; <userinput>mount /dev/ad1s1a</userinput>
 &prompt.root; <userinput>cd /mnt</userinput>
 &prompt.root; <userinput>dump 0uaf - / | restore xf -</userinput></screen>
 
 
           <para>¤â¤·¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¹½À®¤òÊѤ¨¤è¤¦¤È»×¤Ã¤Æ¤¤¤ë¤Ê¤é -
             ¤Ä¤Þ¤ê°ì¤Ä¤À¤Ã¤¿¤â¤Î¤òÆó¤Ä¤Ë¤·¤¿¤êÆó¤Ä¤À¤Ã¤¿¤â¤Î¤ò¤¯¤Ã¤Ä¤±¤¿¤ê
             ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤Ê¤é¡¢¼«Á°¤Ç¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê°Ê²¼¤Î¤¹¤Ù¤Æ¤ò
             ¿·¤·¤¤¾ì½ê¤Ø°Ü¤¹É¬Íפ¬½Ð¤Æ¤¯¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£&man.dump.8; ¤Ï
             ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËƯ¤¯¤Î¤Ç¤³¤ÎÌÜŪ¤Ë¤Ï»È¤¨¤Þ¤»¤ó¡£¤³¤Î¾ì¹ç¤Ï
             &man.tar.1; ¤ò»È¤¤¤Þ¤¹¡£°ìÈÌ¤Ë <filename>/old</filename> ¤«¤é
             <filename>/new</filename> ¤Ø¤Î°ÜÆ°¤Ï  &man.tar.1; ¤Ç
             °Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>(cd /old; tar cf - .) | (cd /new; tar xpf -)</userinput></screen>
 
           <para><filename>/old</filename> ¤Ë¾¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬
             ¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤Æ¡¢¤½¤Î¥Ç¡¼¥¿¤Î°ÜÆ°¤Þ¤Ç¤Ï¹Í¤¨¤Æ¤Ê¤¤¤Ê¤é¤Ð
             ºÇ½é¤Î &man.tar.1; ¤Ë 'l' ¥Õ¥é¥°¤òÄɲä·¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>(cd /old; tar clf - .) | (cd /new; tar xpf -).</userinput></screen>
 
           <para>&man.tar.1; ¤Î¤«¤ï¤ê¤Ë &man.cpio.1; ¤ä &man.pax.1;,
             cpdup (ports/sysutils/cpdup) Åù¤ò
             »È¤Ã¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£</para>
          </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="release-candidate">
           <para>
             ¥·¥¹¥Æ¥à¤òºÇ¿·¤Î -STABLE ¤Ë¥¢¥Ã¥×¥Ç¡¼¥È¤·¤è¤¦¤È¤·¤¿¤Î¤Ç¤¹¤¬
             -RC ¤ä -BETA ¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤·¤¿! ²¿¤¬µ¯¤³¤Ã¤¿¤Î¤Ç¤¹¤«?
           </para>
         </question>
 
         <answer>
           <para>
             û¤¤Åú¤¨: ¤¿¤À¤Î̾Á°¤Ç¤¹¡£RC ¤Ï
             <quote>¥ê¥ê¡¼¥¹¸õÊä (Release Candidate)</quote> ¤Ë
             ͳÍ褹¤ë¤â¤Î¤Ç¡¢¥ê¥ê¡¼¥¹¤¬´Ö¶á¤Ç¤¢¤ë¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
             ¤Þ¤¿¡¢FreeBSD ¤Ë¤ª¤±¤ë -BETA ¤ÏÄ̾
             ¥ê¥ê¡¼¥¹Á°¤Î¥³¡¼¥É¥Õ¥ê¡¼¥º´ü´Ö¤ËÆþ¤Ã¤Æ¤¤¤ë¤È¤¤¤¦°ÕÌ£¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             Ť¤Åú¤¨: FreeBSD ¤Ï¤½¤Î¥ê¥ê¡¼¥¹¤ò 2 ¥ö½ê¤¢¤ë¤¦¤Á¤Î
             °ìÊý¤«¤éÇÉÀ¸¤µ¤»¤Þ¤¹¡£3.0-RELEASE ¤ä 4.0-RELEASE ¤ÎÍͤÊ
             (0 ¤Î¥Þ¥¤¥Ê¡¼ÈÖ¹æ¤ò»ý¤Ä) ¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤Ï¡¢°ìÈÌ¤Ë <link
             linkend="current">-CURRENT</link> ¤È¸Æ¤Ð¤ì¤ë
             ³«È¯ÈǤÎή¤ì¤«¤éʬ´ô¤µ¤»¤é¤ì¤Æ¤Ç¤­¤Þ¤¹¡£3.1-RELEASE ¤ä
             4.2-RELEASE ¤Ê¤É¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ï¥¢¥¯¥Æ¥£¥Ö¤Ê
             <link linkend="stable">-STABLE</link> ¥Ö¥é¥ó¥Á (»Þ) ¤Î
             ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ç¤·¤¿¡£
             4.3-RELEASE ¤«¤é¤Ï¡¢¥ê¥ê¡¼¥¹Ëè¤Ë¥Ö¥é¥ó¥Á¤¬ºîÀ®¤µ¤ì¤ë¤è¤¦¤Ë
             ¤Ê¤ê¤Þ¤·¤¿¡£¤â¤Î¤¹¤´¤¯ÊݼéŪ¤Ê³«È¯Â®ÅÙ (¼ç¤Ë¥»¥­¥å¥ê¥Æ¥£
             ´«¹ð¤Î¤ß) ¤òµá¤á¤Æ¤¤¤ë¿Í¤Ï¡¢¤³¤Î¥Ö¥é¥ó¥Á¤òÄÉÀפ¹¤ë¤È
             ¤è¤¤¤Ç¤·¤ç¤¦¡£</para>
 
           <para>
             ¥ê¥ê¡¼¥¹¤òºî¤ë»þ¤Ë¤Ê¤ë¤È¤½¤ì¤òʬ´ô¤µ¤»¤ë¥Ö¥é¥ó¥Á¤Ï
             ÆÃÄê¤Î¥×¥í¥»¥¹¤ØÆÍÆþ¤·¤Þ¤¹¡£¤½¤Î¥×¥í¥»¥¹¤Î°ì¤Ä¤Ï
             ¥³¡¼¥É¥Õ¥ê¡¼¥º (¥³¡¼¥É¤ÎÅà·ë) ¤Ç¤¹¡£¥³¡¼¥É¥Õ¥ê¡¼¥º¤¬
             »Ï¤Þ¤ë¤È¡¢¤½¤Î¥Ö¥é¥ó¥Á¤Î̾Á°¤¬¥ê¥ê¡¼¥¹¤Ë¤Ê¤í¤¦¤È¤·¤Æ¤¤¤ë¤³¤È¤ò
             È¿±Ç¤¹¤ë¤â¤Î¤ËÊѤ¨¤é¤ì¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢4.0-STABLE ¤È
             ¸Æ¤Ð¤ì¤Æ¤¤¤¿¥Ö¥é¥ó¥Á¤Ï̾Á°¤¬ 4.1-BETA ¤Ø¤È
             ÊѤ¨¤é¤ì¡¢¥³¡¼¥É¥Õ¥ê¡¼¥º¤È¥ê¥ê¡¼¥¹Á°¤Î¥Æ¥¹¥È¤¬
             »Ï¤Þ¤Ã¤¿¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
             ¥Ð¥°¤Î½¤Àµ¤Ï¥ê¥ê¡¼¥¹¤Î°ìÉô¤È¤·¤Æ¥³¥ß¥Ã¥È¤µ¤ì¤Þ¤¹¡£
             ¥½¡¼¥¹¥³¡¼¥É¤¬¥ê¥ê¡¼¥¹¤Î·Á¤ò¼è¤Ã¤¿¤Ê¤é̾Á°¤¬ 4.1-RC ¤Ø¤È
             ÊѤ¨¤é¤ì¡¢¤½¤ì¤«¤é¥ê¥ê¡¼¥¹¤¬ºî¤é¤ì¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
             ¤Ò¤È¤¿¤Ó RC ¤Î¥¹¥Æ¡¼¥¸¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¦¤È¡¢È¯¸«¤µ¤ì¤¿
             ¤â¤Ã¤È¤âÃ×̿Ū¤Ê¥Ð¥°¤Î½¤Àµ¤·¤«¤Ç¤­¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£
             ¤Ò¤È¤¿¤Ó¥ê¥ê¡¼¥¹¤¬ (¤³¤ÎÎã¤Ç¤Ï 4.1-RELEASE) ºî¤é¤ì¤ì¤Ð¡¢
             ¤½¤Î¥Ö¥é¥ó¥Á¤Ï 4.1-STABLE ¤È²þ̾¤µ¤ì¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="kernel-chflag-failure">
           <para>¿·¤·¤¤¥«¡¼¥Í¥ë¤òÆþ¤ì¤è¤¦¤È¤·¤¿¤Î¤Ç¤¹¤¬¡¢
             chflags ¤Ë¼ºÇÔ¤·¤Þ¤¹¡£¤É¤¦¤¹¤ì¤ÐÎɤ¤¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>´Êñ¤Ê²óÅú:
             ¿ʬ¡¢¥»¥­¥å¥¢¥ì¥Ù¥ë¤¬ 0 ¤è¤êÂ礭¤¯¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦¡£
             ľÀÜ¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤ÇºÆµ¯Æ°¤·¤Æ¡¢
             ¥«¡¼¥Í¥ë¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>¾Ü¤·¤¤²óÅú:
             FreeBSD ¤Ç¤Ï¡¢¥»¥­¥å¥¢¥ì¥Ù¥ë¤¬ 0 ¤è¤êÂ礭¤¤¾ì¹ç¡¢
             ¥·¥¹¥Æ¥à¥Õ¥é¥°¤ÎÊѹ¹¤¬¶Ø»ß¤µ¤ì¤Þ¤¹¡£
             ¸½ºß¤Î¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ï¡¢¼¡¤Î¥³¥Þ¥ó¥É¤ò»È¤Ã¤ÆÄ´¤Ù¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
 
           <para>¥»¥­¥å¥¢¥ì¥Ù¥ë¤ò²¼¤²¤ëÁàºî¤Ï¡¢¤Ç¤­¤Ê¤¤¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¤½¤Î¤¿¤á¡¢¥«¡¼¥Í¥ë¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤Ë¤Ï¡¢
             ¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤Çµ¯Æ°¤¹¤ë¤«¡¢<filename>/etc/rc.conf</filename>
             ¤Î¥»¥­¥å¥ê¥Æ¥£ÀßÄê¤òÊѹ¹¤·¤ÆºÆµ¯Æ°¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¥»¥­¥å¥¢¥ì¥Ù¥ë¤Î¾ÜºÙ¤Ï &man.init.8; ¤ò¡¢
             rc.conf ¤Î¾ÜºÙ¤Ï <filename>/etc/defaults/rc.conf</filename> ¤ª¤è¤Ó¡¢
             &man.rc.conf.5; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="kernel-securelevel-time">
           <para>¥·¥¹¥Æ¥à¤Î»þ¹ï¤ò 1 ÉðʾåÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤Î¤Ç¤¹!
             ¤É¤¦¤¹¤ì¤ÐÎɤ¤¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>´Êñ¤Ê²óÅú:
             ¿ʬ¡¢¥»¥­¥å¥¢¥ì¥Ù¥ë¤¬ 1 ¤è¤êÂ礭¤¯¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦¡£
             ľÀÜ¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤ÇºÆµ¯Æ°¤·¤Æ¡¢
             »þ¹ï¤ÎÊѹ¹¤ò¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>¾Ü¤·¤¤²óÅú:
             FreeBSD ¤Ç¤Ï¡¢¥»¥­¥å¥¢¥ì¥Ù¥ë¤¬ 1 ¤è¤êÂ礭¤¤¾ì¹ç¡¢
             1 Éðʾå¤Î»þ¹ïÊѹ¹¤¬¶Ø»ß¤µ¤ì¤Þ¤¹¡£
             ¸½ºß¤Î¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ï¡¢¼¡¤Î¥³¥Þ¥ó¥É¤ò»È¤Ã¤ÆÄ´¤Ù¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
 
           <para>¥»¥­¥å¥¢¥ì¥Ù¥ë¤ò²¼¤²¤ëÁàºî¤Ï¡¢¤Ç¤­¤Ê¤¤¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¤½¤Î¤¿¤á¡¢¥·¥¹¥Æ¥à¤Î»þ¹ï¤òÊѹ¹¤¹¤ë¤Ë¤Ï¡¢
             ¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤Çµ¯Æ°¤¹¤ë¤«¡¢<filename>/etc/rc.conf</filename>
             ¤Î¥»¥­¥å¥ê¥Æ¥£ÀßÄê¤òÊѹ¹¤·¤ÆºÆµ¯Æ°¤¹¤ëɬÍפФ¢¤ê¤Þ¤¹¡£
             ¥»¥­¥å¥¢¥ì¥Ù¥ë¤Î¾ÜºÙ¤Ï &man.init.8; ¤ò¡¢
             rc.conf ¤Î¾ÜºÙ¤Ï <filename>/etc/defaults/rc.conf</filename> ¤ª¤è¤Ó¡¢
             &man.rc.conf.5; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="statd-mem-leak">
           <para>&man.rpc.statd.8; ¤Ë¥á¥â¥ê¥ê¡¼¥¯¤ò¸«¤Ä¤±¤Þ¤·¤¿!
             ¥á¥â¥ê¤ò 256 ¥á¥¬¥Ð¥¤¥È¤â»È¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>¤¤¤¤¤¨¡£¤½¤ì¤Ï¥á¥â¥ê¥ê¡¼¥¯¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤·¡¢
             256 ¥á¥¬¥Ð¥¤¥È¤Î¥á¥â¥ê¤ò»È¤Ã¤Æ¤¤¤ë¡¢¤È¤¤¤¦¤³¤È¤Ç¤â¤¢¤ê¤Þ¤»¤ó¡£
             ¤ª¤½¤é¤¯ (¤Û¤È¤ó¤É¤Î¾ì¹ç)¡¢
             ½èÍý¤ËÅԹ礬Îɤ¤¤è¤¦¤ËÈó¾ï¤Ë¤¿¤¯¤µ¤ó¤ÎÎ̤Υá¥â¥ê¤ò
             ¤½¤Î¥×¥í¥»¥¹¤Î¥¢¥É¥ì¥¹¶õ´Ö¤Ë¥Þ¥Ã¥Ô¥ó¥°¤·¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦¡£
             µ»½ÑŪ¤Ê¸«ÃϤ«¤é¹Í¤¨¤Æ¤â¡¢¤³¤ì¤ÏÂ礭¤Ê³²¤¬¤¢¤ë¤³¤È¤Ç¤Ï¤Ê¤¯¡¢
             ñ¤Ë &man.top.1; ¤ä &man.ps.1; ¤È¤¤¤Ã¤¿¥Ä¡¼¥ë¤Îɽ¼¨¤Ë±Æ¶Á¤¬¤¢¤ëÄøÅ٤Ǥ¹¡£
           </para>
 
           <!-- hrs/2001/03/01: possible typo? generious - generous -->
           <para>&man.rpc.statd.8; ¤Ï¡¢(<filename>/var</filename> ¤Ë¤¢¤ë)
             ¥¹¥Æ¡¼¥¿¥¹¥Õ¥¡¥¤¥ë¤ò¼«Ê¬¤Î¥¢¥É¥ì¥¹¶õ´Ö¤Ë¥Þ¥Ã¥Ô¥ó¥°¤·¤Þ¤¹¡£
             ¥Þ¥Ã¥Ô¥ó¥°¤Ï¡¢¸å¤ÇÂ礭¤Ê¶õ´Ö¤¬É¬Íפˤʤä¿»þ¤ËºÆ¥Þ¥Ã¥Ô¥ó¥°¤·¤Ê¤¤¤ÇºÑ¤à¤è¤¦¡¢
             Èó¾ï¤ËÂ礭¤Ê¥µ¥¤¥º¤ò»ØÄꤷ¤Æ¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£
             ¤³¤ì¤Ï¡¢¥½¡¼¥¹¥³¡¼¥É¤Ë´Þ¤Þ¤ì¤ë &man.mmap.2;
             ´Ø¿ô¤Î¥Þ¥Ã¥Ô¥ó¥°Ä¹¤ò¼¨¤¹°ú¿ô¤Ë
             <literal>0x10000000</literal> ¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¤³¤È¤«¤é¤âʬ¤«¤ê¤Þ¤¹¡£
             ¤³¤Î¿ô»ú¤¬ IA32 ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Î»ý¤Ä¥¢¥É¥ì¥¹¥¹¥Ú¡¼¥¹Á´ÂΤÎ
             16 ʬ¤Î 1¡¢¤¹¤Ê¤ï¤Á¡¢¤Á¤ç¤¦¤É 256 ¥á¥¬¥Ð¥¤¥È¤ËÁêÅö¤¹¤ë¤Î¤Ç¤¹¡£</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="x">
     <title>X Window System ¤È²¾ÁÛ¥³¥ó¥½¡¼¥ë</title>
 
     <para>
       <emphasis>Ìõ:
         &a.motoyuki;
         1997 ǯ 11 ·î 13 Æü</emphasis>
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="running-X">
           <para>X ¤òÆ°¤«¤·¤¿¤¤¤Î¤Ç¤¹¤¬¡¢¤É¤¦¤¹¤ì¤Ð¤¤¤¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤â¤Ã¤È¤â´Êñ¤ÊÊýË¡¤Ï FreeBSD ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤ÎºÝ¤Ë
             X ¤òÆ°¤«¤¹¤³¤È¤ò»ØÄꤹ¤ë¤À¤±¤Ç¤¹¡£
           </para>
 
           <para>¤½¤ì¤«¤é <command>xf86config</command>
             ¥Ä¡¼¥ë¤Î¥É¥­¥å¥á¥ó¥È¤òÆɤó¤Ç¤³¤ì¤Ë½¾¤Ã¤Æ¤¯¤À¤µ¤¤¡£
             ¤³¤Î¥Ä¡¼¥ë¤Ï¤¢¤Ê¤¿¤Î¥°¥é¥Õ¥£¥Ã¥¯¥«¡¼¥É¤ä¥Þ¥¦¥¹¤Ê¤É¤Ë¹ç¤ï¤»¤Æ
             XFree86(tm) ¤ÎÀßÄê¤ò¹Ô¤¦¤Î¤ò½õ¤±¤Æ¤¯¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             Xaccel ¥µ¡¼¥Ð¡¼¤Ë¤Ä¤¤¤ÆÄ´¤Ù¤Æ¤ß¤ë¤Î¤â¤¤¤¤¤Ç¤·¤ç¤¦¡£
             ¾Ü¤·¤¯¤Ï <link linkend="xig">Xi Graphics ¤Ë¤Ä¤¤¤Æ</link> ¤«
             <link linkend="metrox">Metro Link</link> ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="running-X-securelevels">
           <para>X ¤ò<emphasis>¼Â¹Ô¤·¤è¤¦¤È</emphasis>¤·¤Æ
             <command>startx</command>
             ¤ÈÆþÎϤ·¤¿¤Î¤Ç¤¹¤¬¡¢
             <errorname>KDENABIO failed (Operation not permitted)</errorname>
             ¤È¤¤¤¦¥¨¥é¡¼¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£
             ²¿¤«¤ª¤«¤·¤Ê¤³¤È¤ò¤ä¤Ã¤Æ¤·¤Þ¤Ã¤¿¤ó¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>¤¢¤Ê¤¿¤Î¥·¥¹¥Æ¥à¤Ï¹â¤¤¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ç±¿ÍѤµ¤ì¤Æ¤¤¤Þ¤¹¤Í?
             ¼Â¤Ï¡¢¹â¤¤¥»¥­¥å¥¢¥ì¥Ù¥ë¤Ç X ¤òµ¯Æ°¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Ê¤¤¤Î¤Ç¤¹¡£
             ¤É¤¦¤·¤Æ¤Ê¤Î¤«¤Ë¤Ä¤¤¤Æ¤Ï¡¢&man.init.8;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
           <para>¤Ç¤Ï¡¢Âå¤ï¤ê¤Ë¤É¤¦¤¹¤ì¤ÐÎɤ¤¤Î¤«¤ªÅú¤¨¤·¤Þ¤·¤ç¤¦¡£
             ´ðËÜŪ¤Ë 2 ¤Ä¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£
             °ì¤Ä¤Ï¥»¥­¥å¥¢¥ì¥Ù¥ë¤ò 0 ¤Ë¤¹¤ë (Ä̾¤³¤ì¤Ï
             <filename>/etc/rc.conf</filename> ¤Ç»ØÄꤷ¤Þ¤¹) ¤³¤È¡¢
             ¤â¤¦°ì¤Ä¤Ïµ¯Æ°»þ (¥»¥­¥å¥¢¥ì¥Ù¥ë¤ò¾å¤²¤ëÁ°) ¤Ë
               &man.xdm.1; ¤ò¼Â¹Ô¤¹¤ë¤«¤Ç¤¹¡£</para>
 
           <para>µ¯Æ°»þ¤Ë &man.xdm.1; ¤ò¼Â¹Ô¤¹¤ëÊýË¡¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             <xref linkend="xdm-boot"/> ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="x-and-moused">
           <para>»ä¤Î¥Þ¥¦¥¹¤Ï¤Ê¤¼ X ¤ÇÆ°¤«¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>syscons (¥Ç¥Õ¥©¥ë¥È¤Î¥³¥ó¥½¡¼¥ë¥É¥é¥¤¥Ð) ¤ò»È¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
             ¤½¤ì¤¾¤ì¤Î²¾ÁÛ¥¹¥¯¥ê¡¼¥ó¤Ç¥Þ¥¦¥¹¥Ý¥¤¥ó¥¿¡¼¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤è¤¦¤Ë
             FreeBSD ¤òÀßÄê¤Ç¤­¤Þ¤¹¡£X ¤Ç¤Î¥Þ¥¦¥¹¤Î¾×ÆͤòÈò¤±¤ë¤¿¤á¤Ë¡¢syscons ¤Ï
             <devicename>/dev/sysmouse</devicename>
             ¤È¤¤¤¦²¾ÁۥǥХ¤¥¹¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             ËÜʪ¤Î¥Þ¥¦¥¹¥Ç¥Ð¥¤¥¹¤«¤éÆþÎϤµ¤ì¤¿¤¹¤Ù¤Æ¤Î¥Þ¥¦¥¹¤Î¥¤¥Ù¥ó¥È¤Ï¡¢
             moused ¤ò·Ðͳ¤·¤Æ sysmouse ¥Ç¥Ð¥¤¥¹¤Ø½ÐÎϤµ¤ì¤Þ¤¹¡£
             °ì¤Ä°Ê¾å¤Î²¾ÁÛ¥³¥ó¥½¡¼¥ë¤È X ¤Î
             <emphasis>ξÊý¤Ç</emphasis> ¥Þ¥¦¥¹¤ò»È¤¤¤¿¤¤¾ì¹ç¡¢
             <xref linkend="moused" remap="another section"/>
             ¤ò»²¾È¤·¤Æ moused ¤òÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤½¤·¤Æ¡¢<filename>/etc/XF86Config</filename> ¤òÊÔ½¸¤·¡¢
             ¼¡¤Î¤è¤¦¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <programlisting>Section         Pointer
 Protocol        "SysMouse"
 Device          "/dev/sysmouse"
 .....</programlisting>
 
           <para>
             ¾å¤ÎÎã¤Ï¡¢XFree86 3.3.2 °Ê¹ß¤Î¾ì¹ç¤ÎÎã¤Ç¤¹¡£
             ¤½¤ì¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
             <emphasis>Protocol</emphasis> ¤È¤¤¤¦Éôʬ¤ò
             <emphasis>MouseSystems</emphasis> ¤ÈÃÖ¤­´¹¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             X ¤Ç <devicename>/dev/mouse</devicename>
             ¤ò»È¤¦¤Î¤ò¹¥¤à¿Í¤â¤¤¤Þ¤¹¡£
             ¤³¤Î¾ì¹ç¤Ï¡¢
             <devicename>/dev/mouse</devicename>
             ¤ò
             <devicename>/dev/sysmouse</devicename> (&man.sysmouse.4; »²¾È)
             ¤Ë¥ê¥ó¥¯¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>rm -f mouse</userinput>
 &prompt.root; <userinput>ln -s sysmouse mouse</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="x-and-wheel">
           <para>¤ï¤¿¤·¤Î¥Þ¥¦¥¹¤Ë¤Ï¥Û¥¤¡¼¥ëµ¡Ç½¤¬ÉÕ¤¤¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢X ¤Ç»È¤¦¤³¤È¤Ï¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¤Ï¤¤¡¢¤â¤Á¤í¤ó»È¤¨¤Þ¤¹¤¬¡¢¤½¤Î¤¿¤á¤Ë¤Ï
             X ¥¯¥é¥¤¥¢¥ó¥È¥×¥í¥°¥é¥à¤òŬÀÚ¤ËÀßÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             <ulink url="http://www.inria.fr/koala/colas/mouse-wheel-scroll/">Colas Nahaboo
               »á¤Î¥¦¥§¥Ö¥Ú¡¼¥¸(http://www.inria.fr/koala/colas/mouse-wheel-scroll/)</ulink>
             ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>
             <application>imwheel</application>
             ¤È¤¤¤¦¥×¥í¥°¥é¥à¤ò»È¤¦¾ì¹ç¤Ï¡¢
             ¼¡¤Î¤è¤¦¤Ê´Êñ¤Ê¼ê½ç¤Ë¤·¤¿¤¬¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <orderedlist>
             <listitem>
               <para>¥Û¥¤¡¼¥ë¥¤¥Ù¥ó¥È¤ÎÊÑ´¹</para>
 
               <para>
                 <application>imwheel</application> ¤Ï¡¢
                 ¥Þ¥¦¥¹¤Î¥Ü¥¿¥ó 4¡¢¥Ü¥¿¥ó 5 ¤ò¥­¡¼²¡²¼¥¤¥Ù¥ó¥È¤ËÊÑ´¹¤¹¤ë¥×¥í¥°¥é¥à¤Ç¤¹¡£
                 ¤½¤Î¤¿¤á¥Û¥¤¡¼¥ë¥Þ¥¦¥¹¤ÇÍøÍѤ¹¤ë¤Ë¤Ï¡¢¥Þ¥¦¥¹¥Û¥¤¡¼¥ë¤Î¥¤¥Ù¥ó¥È¤ò¥Ü¥¿¥ó 4¡¢
                 ¥Ü¥¿¥ó 5 ¤Î¥¤¥Ù¥ó¥È¤ËÊÑ´¹¤¹¤ë¥Þ¥¦¥¹¥É¥é¥¤¥Ð¤òÍøÍѤ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
                 ¤³¤ÎÊÑ´¹¤ò¹Ô¤Ê¤¦¤Ë¤ÏÆó¤Ä¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£
                 °ì¤Ä¤Ï &man.moused.8;
                 ¤Ç¹Ô¤Ê¤¦ÊýË¡¡¢Æó¤Ä¤á¤Ï X ¥µ¡¼¥Ð¼«¿È¤ËÊÑ´¹¤ò¹Ô¤Ê¤ï¤»¤ëÊýË¡¤Ç¤¹¡£
               </para>
 
               <orderedlist>
                 <listitem>
                   <para>¥Û¥¤¡¼¥ë¥¤¥Ù¥ó¥È¤ÎÊÑ´¹¤Ë &man.moused.8; ¤ò»È¤¦</para>
 
                   <para>
                     &man.moused.8; ¤Ë¥¤¥Ù¥ó¥È¤òÊÑ´¹¤µ¤»¤ë¤Ë¤Ï¡¢
                     &man.moused.8; µ¯Æ°»þ¤Ë¥ª¥×¥·¥ç¥ó
                     <option>-z 4</option> ¤òÄɲä·¤Þ¤¹¡£
                     ¤¿¤È¤¨¤Ð¡¢ÉáÃÊ &man.moused.8; ¤ò
                     <command>moused -p /dev/psm0</command>
                     ¤È¤·¤Æµ¯Æ°¤·¤Æ¤¤¤ë¤Ê¤é¡¢¤½¤ÎÂå¤ï¤ê¤Ë
                     <command>moused -p /dev/psm0 -z 4</command>
                     ¤È¤·¤Þ¤¹¡£
                     ¤â¤·¡¢
                     <filename>/etc/rc.conf</filename>
                     ¤ò»È¤Ã¤Æ¼«Æ°Åª¤Ëµ¯Æ°¤¹¤ë¤è¤¦¤ËÀßÄꤷ¤Æ¤¤¤ë¤Ê¤é¡¢
                     <filename>/etc/rc.conf</filename>
                     ¤ÎÃæ¤Î
                     <varname>moused_flags</varname> ¤È¤¤¤¦ÊÑ¿ô¤Ë
                     <option>-z 4</option> ¤òÄɲ乤ë¤À¤±¤Ç¤¹¡£
                   </para>
 
                   <para>
                     ¤½¤·¤Æ¡¢5 ¥Ü¥¿¥ó¥Þ¥¦¥¹¤ò»È¤¦¤³¤È¤ò
                     X ¥µ¡¼¥Ð¤ËÅÁ¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
                     ¤³¤ì¤ò¹Ô¤Ê¤¦¤Ë¤Ï
                     <filename>/etc/XF86Config</filename> ¤Î
                     <quote>Pointer</quote> ¥»¥¯¥·¥ç¥ó¤Ë
                     <literal>Buttons 5</literal> ¤È¤¤¤¦¹Ô¤òÄɲ乤ë¤À¤±¤Ç¤¹¡£
                     ¤½¤¦¤¹¤ë¤È
                     <filename>/etc/XF86Config</filename> ¤Î
                     <quote>Pointer</quote> ¤Ï¡¢
                     ¤¿¤È¤¨¤Ð¼¡¤Î¤è¤¦¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
                   </para>
 
                   <example>
                     <title>moused ¤Ë¤è¤ëÊÑ´¹¤òÍøÍѤ·¤Æ¥Û¥¤¡¼¥ë¥Þ¥¦¥¹¤ò
                       »ÈÍѤ¹¤ë¤¿¤á¤Î XFree86 3.3.x ·ÏÎó¤Î XF86Config ¤Î
                       <quote>Pointer</quote> ¥»¥¯¥·¥ç¥ó¤ÎÀßÄêÎã</title>
 
                     <programlisting>Section "Pointer"
    Protocol        "SysMouse"
    Device          "/dev/sysmouse"
    Buttons         5
 EndSection</programlisting>
                   </example>
 
                   <example>
                     <title>¼«Æ°Åª¤Ê¥×¥í¥È¥³¥ëǧ¼±µ¡Ç½¤ª¤è¤Ó¥Ü¥¿¥óÇÛÃÖÊÑ´¹µ¡Ç½¤ò
                       ÍøÍѤ·¡¢¥Û¥¤¡¼¥ë¥Þ¥¦¥¹¤ò»ÈÍѤ¹¤ë¤¿¤á¤Î XFree86 4.x ·ÏÎó¤Î
                       XF86Config ¤Î <quote>InputDevice</quote> ¥»¥¯¥·¥ç¥ó¤ÎÀßÄêÎã</title>
 
                     <programlisting>Section "InputDevice"
    Identifier      "Mouse1"
    Driver          "mouse"
    Option          "Protocol" "auto"
    Option          "Device" "/dev/psm0"
    Option          "Buttons" "5"
    Option          "ZAxisMapping" "4 5"
 EndSection</programlisting>
                   </example>
 
                   <example>
                     <title>¥Û¥¤¡¼¥ë¥Þ¥¦¥¹¤Ç Emacs ¾å¤Ç¤Î¥Ú¡¼¥¸¥¹¥¯¥í¡¼¥ë¤ò
                       ¹Ô¤¦¤¿¤á¤Î <quote>.emacs</quote> ¤ÎÀßÄêÎã</title>
                     <programlisting>;; wheel mouse
 (global-set-key [mouse-4] 'scroll-down)
 (global-set-key [mouse-5] 'scroll-up)</programlisting>
                   </example>
                 </listitem>
 
                 <listitem>
                   <para>X ¥µ¡¼¥Ð¤ò»È¤Ã¤¿¥Û¥¤¡¼¥ë¥¤¥Ù¥ó¥È¤ÎÊÑ´¹</para>
 
                   <para>
                     &man.moused.8; ¤òµ¯Æ°¤·¤Æ¤¤¤Ê¤«¤Ã¤¿¤ê¡¢
                     ¥Û¥¤¡¼¥ë¥¤¥Ù¥ó¥È¤ÎÊÑ´¹¤Ë &man.moused.8;
                     ¤òµ¯Æ°¤·¤¿¤¯¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢¤½¤ÎÂå¤ï¤ê¤Ë
                     X ¥µ¡¼¥Ð¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
                     ¤³¤ì¤Ë¤Ï¡¢<filename>/etc/XF86Config</filename>
                     ¥Õ¥¡¥¤¥ë¤ò½ñ¤­´¹¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
                     ¤Þ¤ººÇ½é¤ËɬÍפʤΤϡ¢
                     ¥Þ¥¦¥¹¤¬¤É¤Î¥×¥í¥È¥³¥ë¤ò»È¤Ã¤Æ¤¤¤ë¤Î¤«¤ò³Îǧ¤¹¤ë¤³¤È¤Ç¤¹¡£
                     ¤Û¤È¤ó¤É¤Î¥Û¥¤¡¼¥ë¥Þ¥¦¥¹¤Ï
                     <quote>IntelliMouse</quote>
                     ¥×¥í¥È¥³¥ë¤ò»ÈÍѤ·¤Æ¤¤¤Þ¤¹¤¬¡¢
                     XFree86 ¥µ¡¼¥Ð¤Ï¤½¤Î¾¤Î¥×¥í¥È¥³¥ë¡¢
                     ¤¿¤È¤¨¤Ð
                     Logitech MouseMan+ ¥Þ¥¦¥¹¤¬ÍøÍѤ·¤Æ¤¤¤ë
                     <quote>MouseManPlusPS/2</quote>
                     ¥×¥í¥È¥³¥ë¤Ê¤É¤â¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
                     »ÈÍѤµ¤ì¤Æ¤¤¤ë¥×¥í¥È¥³¥ë¤¬³Îǧ¤Ç¤­¤¿¤é
                     <quote>Pointer</quote> ¥»¥¯¥·¥ç¥ó¤Ë
                     <varname>Protocol</varname> ¤Î¹Ô¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
                   </para>
 
                   <para>
                     ¤Ä¤®¤Ë¡¢
                     ¥Û¥¤¡¼¥ë¤Î¥¹¥¯¥í¡¼¥ë¥¤¥Ù¥ó¥È¤ò¥Þ¥¦¥¹¥Ü¥¿¥ó 4¡¢
                     ¥Þ¥¦¥¹¥Ü¥¿¥ó 5 ¤Ë³ä¤êÅö¤Æ¤ë¤³¤È¤ò X ¥µ¡¼¥Ð¤ËÅÁ¤¨¤Þ¤¹¡£
                     ¤³¤ì¤ò¹Ô¤Ê¤¦¤Ë¤Ï
                     <varname>ZAxisMapping</varname>
                     ¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤ·¤Þ¤¹¡£
                   </para>
 
                   <para>
                     ¤¿¤È¤¨¤Ð¡¢&man.moused.8; ¤¬µ¯Æ°¤·¤Æ¤¤¤Ê¤¤¾õÂ֤ǡ¢
                     PS/2 ¥Þ¥¦¥¹¥Ý¡¼¥È¤Ë IntelliMouse ¤¬Àܳ¤µ¤ì¤Æ¤¤¤ë¤È¤·¤¿¤é
                     <filename>/etc/XF86Config</filename>
                     ¤Ï¤ª¤½¤é¤¯¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
                   </para>
 
                   <example>
                     <title>
                       X ¥µ¡¼¥Ð¤Ë¤è¤ëÊÑ´¹¤òÍøÍѤ·¤Æ¥Û¥¤¡¼¥ë¥Þ¥¦¥¹¤ò»ÈÍѤ¹¤ë¤¿¤á¤Î
                       XF86Config ¤Î <quote>Pointer</quote> ¥»¥¯¥·¥ç¥ó¤ÎÀßÄêÎã</title>
 
                     <programlisting>Section "Pointer"
    Protocol        "IntelliMouse"
    Device          "/dev/psm0"
    ZAxisMapping    4 5
 EndSection</programlisting>
                   </example>
                 </listitem>
               </orderedlist>
             </listitem>
 
             <listitem>
               <para><application>imwheel</application> ¤Î¥¤¥ó¥¹¥È¡¼¥ë</para>
 
               <para>
                 ¤µ¤Æ¡¢¤Ä¤®¤Ë Ports Collection ¤«¤é
                 <application>imwheel</application> ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
                 ¤³¤ì¤¬¤¢¤ë¤Î¤Ï <filename>x11</filename> ¥«¥Æ¥´¥ê¤Ç¤¹¡£
                 ¤³¤Î¥×¥í¥°¥é¥à¤Ï¡¢
                 ¥Þ¥¦¥¹¥¤¥Ù¥ó¥È¤ò¥­¡¼¥Ü¡¼¥É¥¤¥Ù¥ó¥È¤ËÊÑ´¹¤·¤Þ¤¹¡£
                 ¤¿¤È¤¨¤Ð¡¢¥Þ¥¦¥¹¥Û¥¤¡¼¥ë¤òÁ°¤Ë²ó¤·¤¿»þ¡¢
                 <application>imwheel</application> ¤Ï <keycap>PageUp</keycap>
                 ¤ò¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¥×¥í¥°¥é¥à¤ËÁ÷¤ë¤è¤¦¤ÊÆ°ºî¤ò¤¹¤ë¤ï¤±¤Ç¤¹¡£
                 <application>Imwheel</application>
                 ¤Ï¥Û¥¤¡¼¥ë¥¤¥Ù¥ó¥È¤È¥­¡¼¥Ü¡¼¥É²¡²¼¤ÎÂбþ¤òÀßÄê¥Õ¥¡¥¤¥ë¤ò»È¤Ã¤ÆÀßÄꤹ¤ë¤¿¤á¡¢
                 ¥¢¥×¥ê¥±¡¼¥·¥ç¥óËè¤Ë°Û¤Ê¤ëÂбþ¤ò»ý¤¿¤»¤ë¤³¤È¤â²Äǽ¤Ç¤¹¡£
                 <application>imwheel</application> ¤Î¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ï
                 <filename>/usr/X11R6/etc/imwheelrc</filename>
                 ¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£
                 ¤³¤ì¤ò <filename>~/.imwheelrc</filename> ¤Ë¥³¥Ô¡¼¤·¤ÆÊÔ½¸¤·¡¢
                 ¤ª¹¥¤­¤Ê¤è¤¦¤Ë <application>imwheel</application>
                 ¤ÇÍøÍѤ·¤¿¤¤¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ÎÀßÄê¤ò¥«¥¹¥¿¥Þ¥¤¥º¤·¤Æ¤¯¤À¤µ¤¤¡£
                 ÀßÄê¥Õ¥¡¥¤¥ë¤Î½ñ¼°¤Ï &man.imwheel.1; ¤ËÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para><application>Emacs</application> ¤Ç
                 <application>Imwheel</application> ¤ò»È¤¦¤è¤¦¤ËÀßÄꤹ¤ë
                 (<emphasis>ɬ¿Ü¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó</emphasis>)</para>
 
               <para>
                 <application>emacs</application> ¤ä
                 <application>Xemacs</application>
                 ¤ÇÍøÍѤ¹¤ë¤Ë¤Ï¡¢
                 <filename>~/.emacs</filename> ¤Ë¤¤¤¯¤é¤«½ñ¤­²Ã¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
                 <application>emacs</application> ¤Î¾ì¹ç¤Ï¼¡¤ÎÉôʬ¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
               </para>
 
               <example>
                 <title><application>Imwheel</application> ¤òÍøÍѤ¹¤ë¤¿¤á¤Î
                   <application>Emacs</application> ¤ÎÀßÄêÎã</title>
 
                 <programlisting>;;; For imwheel
 (setq imwheel-scroll-interval 3)
 (defun imwheel-scroll-down-some-lines ()
   (interactive)
   (scroll-down imwheel-scroll-interval))
 (defun imwheel-scroll-up-some-lines ()
   (interactive)
   (scroll-up imwheel-scroll-interval))
 (global-set-key [?\M-\C-\)] 'imwheel-scroll-up-some-lines)
 (global-set-key [?\M-\C-\(] 'imwheel-scroll-down-some-lines)
 ;;; end imwheel section</programlisting>
               </example>
 
               <para>
                 <application>Xemacs</application> ¤Î¾ì¹ç¤Ï
                 <filename>~/.emacs</filename> ¤Ë¼¡¤ÎÉôʬ¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
               </para>
 
               <example>
                 <title><application>Imwheel</application> ¤òÍøÍѤ¹¤ë¤¿¤á¤Î
                   <application>XEmacs</application> ¤ÎÀßÄêÎã</title>
 
                 <programlisting>;;; For imwheel
 (setq imwheel-scroll-interval 3)
 (defun imwheel-scroll-down-some-lines ()
   (interactive)
   (scroll-down imwheel-scroll-interval))
 (defun imwheel-scroll-up-some-lines ()
   (interactive)
   (scroll-up imwheel-scroll-interval))
 (define-key global-map [(control meta \))] 'imwheel-scroll-up-some-lines)
 (define-key global-map [(control meta \()] 'imwheel-scroll-down-some-lines)
 ;;; end imwheel section</programlisting>
               </example>
             </listitem>
 
             <listitem>
               <para><application>Imwheel</application> ¤Î¼Â¹Ô</para>
 
               <para>
                 ¥¤¥ó¥¹¥È¡¼¥ë¤¬´°Î»¤·¤Æ¤¤¤ì¤Ð¡¢Ã±¤Ë xterm (ÌõÃí:
                 ÆüËܸì´Ä¶­¤Ç¹­¤¯»È¤ï¤ì¤Æ¤¤¤ë kterm ¤Ç¤â¹½¤¤¤Þ¤»¤ó) ¤«¤é
                 <command>imwheel</command> ¤òÆþÎϤ¹¤ë¤À¤±¤Çµ¯Æ°¤Ç¤­¤Þ¤¹¡£
                 µ¯Æ°¤¹¤ë¤È¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤ÇÆ°ºî¤·¡¢¤¹¤°¤ËÍøÍѤǤ­¤Þ¤¹¡£
                 <application>imwheel</application> ¤ò¤¤¤Ä¤â»È¤¦¤è¤¦¤ËÀßÄꤹ¤ë¤Ë¤Ï¡¢
                 <filename>.xinitrc</filename> ¤«
                 <filename>.xsession</filename> ¤Î¥Õ¥¡¥¤¥ë¤Ë¤½¤Î¤Þ¤Þ¥³¥Þ¥ó¥É¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
                 <application>imwheel</application> ¤¬ PID
                 ¥Õ¥¡¥¤¥ë¤Ë´Ø¤¹¤ë·Ù¹ð¤òɽ¼¨¤¹¤ë¤«¤âÃΤì¤Þ¤»¤ó¤¬¡¢
                 ̵»ë¤·¤Æ¤â´í¸±¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤³¤Î·Ù¹ð¤¬°ÕÌ£¤ò»ý¤Ä¤Î¤Ï¡¢
                 Linux ÈǤΠ<application>imwheel</application> ¤À¤±¤Ç¤¹¡£
               </para>
             </listitem>
           </orderedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="window-menu-weird">
           <para>X ¤Î¥á¥Ë¥å¡¼¤ä¥À¥¤¥¢¥í¥°¥Ü¥Ã¥¯¥¹¤¬¤¦¤Þ¤¯Æ°¤­¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             Num Lock ¥­¡¼¤ò¥ª¥Õ¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>Num Lock ¥­¡¼¤¬¥Ç¥Õ¥©¥ë¥È¤Çµ¯Æ°»þ¤Ë¥ª¥ó¤Ë¤Ê¤ë¾ì¹ç¤Ï¡¢
             <filename>XF86Config</filename> ¥Õ¥¡¥¤¥ë¤Î
             <literal>Keyboard</literal>
             ¥»¥¯¥·¥ç¥ó¤Ë°Ê²¼¤Î¹Ô¤ò²Ã¤¨¤Æ¤â¤¤¤¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <programlisting># Let the server do the NumLock processing.  This should only be
 # required when using pre-R6 clients
     ServerNumLock</programlisting>
 
             <note>
               <title>ÌõÃí</title>
               <para>
                 ¤³¤ÎÌäÂê¤Ï XFree86 3.2 °Ê¹ß¤Ç¤Ï²ò·è¤·¤Æ¤¤¤Þ¤¹¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="virtual-console">
           <para>²¾ÁÛ¥³¥ó¥½¡¼¥ë¤È¤Ï²¿¤Ç¤¹¤«? ¤É¤¦¤ä¤Ã¤¿¤é»È¤¨¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ²¾ÁÛ¥³¥ó¥½¡¼¥ë¤Ï¡¢´Êñ¤Ë¤¤¤¦¤È¡¢¥Í¥Ã¥È¥ï¡¼¥¯¤ä X
             ¤òÆ°¤«¤¹¤Ê¤É¤ÎÊ£»¨¤Ê¤³¤È¤ò¹Ô¤Ê¤ï¤º¤Ë¡¢
             ¤¤¤¯¤Ä¤«¤Î¥»¥Ã¥·¥ç¥ó¤òƱ»þ¤Ë¹Ô¤Ê¤¦¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <para>
             ¥·¥¹¥Æ¥à¤Î¥¹¥¿¡¼¥È»þ¤Ë¤Ï¡¢
             µ¯Æ°¥á¥Ã¥»¡¼¥¸¤¬½Ð¤¿¸å¤Ë login
             ¥×¥í¥ó¥×¥È¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£¤½¤³¤Ç
             ¥í¥°¥¤¥ó̾¤È¥Ñ¥¹¥ï¡¼¥É¤òÆþÎϤ¹¤ë¤È
             1 ÈÖÌܤβ¾ÁÛ¥³¥ó¥½¡¼¥ë¾å¤Ç»Å»ö (¤¢¤ë¤¤¤ÏÍ·¤Ó) ¤ò»Ï¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¾¤Î¥»¥Ã¥·¥ç¥ó¤ò»Ï¤á¤¿¤¤¾ì¹ç¤â¤¢¤ë¤Ç¤·¤ç¤¦¡£
             ¤½¤ì¤ÏÆ°¤«¤·¤Æ¤¤¤ë¥×¥í¥°¥é¥à¤Î¥É¥­¥å¥á¥ó¥È¤ò¸«¤¿¤ê¡¢
             FTP ¤ÎžÁ÷¤¬½ª¤ï¤ë¤Þ¤ÇÂԤĴ֡¢
             ¥á¡¼¥ë¤òÆɤ⤦¤È¤·¤¿¤ê¤¹¤ë¤³¤È¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             <keycap>Alt</keycap>-<keycap>F2</keycap>
             ¤ò²¡¤¹ (<keycap>Alt</keycap> ¥­¡¼¤ò²¡¤·¤Ê¤¬¤é
             <keycap>F2</keycap> ¥­¡¼¤ò²¡¤¹) ¤È¡¢
             2 ÈÖÌܤΡֲ¾ÁÛ¥³¥ó¥½¡¼¥ë¡×¤Ç
             ¥í¥°¥¤¥ó¥×¥í¥ó¥×¥È¤¬ÂÔµ¡¤·¤Æ¤¤¤ë¤³¤È¤¬¤ï¤«¤ê¤Þ¤¹¡£
             ºÇ½é¤Î¥»¥Ã¥·¥ç¥ó¤ËÌá¤ê¤¿¤¤¤È¤­¤Ï
             <keycap>Alt</keycap>-<keycap>F1</keycap> ¤ò²¡¤·¤Þ¤¹¡£
           </para>
 
           <para>
             ɸ½à¤Î FreeBSD¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤Ï¡¢
             3 Ëç (3.3-RELEASE ¤Ç¤Ï 8 Ëç) ¤Î²¾ÁÛ¥³¥ó¥½¡¼¥ë¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Æ¡¢
             <keycap>Alt</keycap>-<keycap>F1</keycap>¡¢
             <keycap>Alt</keycap>-<keycap>F2</keycap>¡¢
             <keycap>Alt</keycap>-<keycap>F3</keycap>
             ¤Ç²¾ÁÛ¥³¥ó¥½¡¼¥ë´Ö¤ÎÀÚÂؤ¨¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¤è¤ê¿¤¯¤Î²¾ÁÛ¥³¥ó¥½¡¼¥ë¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢
             <filename>/etc/ttys</filename> (&man.ttys.5; »²¾È)
             ¤òÊÔ½¸¤·¤Æ
             <quote>Virtual terminals</quote>
             ¤Î¥³¥á¥ó¥È¹Ô¤Î¸å¤Ë
             <devicename>ttyv4</devicename>
             ¤«¤é
             <devicename>ttyvc</devicename>
             ¤Î¼êÁ°¤Þ¤Ç¤Î¥¨¥ó¥È¥ê¤ò²Ã¤¨¤Þ¤¹
             (°Ê²¼¤ÎÎã¤ÏÀèƬ¤Ë¤Ï¶õÇò¤ÏÆþ¤ê¤Þ¤»¤ó)¡£
           </para>
 
           <programlisting># /etc/ttys ¤Ë¤Ï ttyv3 ¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç
 # "off" ¤ò "on" ¤ËÊѹ¹¤·¤Þ¤¹¡£
 ttyv3   "/usr/libexec/getty Pc"         cons25  on secure
 ttyv4   "/usr/libexec/getty Pc"         cons25  on secure
 ttyv5   "/usr/libexec/getty Pc"         cons25  on secure
 ttyv6   "/usr/libexec/getty Pc"         cons25  on secure
 ttyv7   "/usr/libexec/getty Pc"         cons25  on secure
 ttyv8   "/usr/libexec/getty Pc"         cons25  on secure
 ttyv9   "/usr/libexec/getty Pc"         cons25  on secure
 ttyva   "/usr/libexec/getty Pc"         cons25  on secure
 ttyvb   "/usr/libexec/getty Pc"         cons25  on secure</programlisting>
 
           <para>
             ¿¤¯¤¹¤ë¤«¾¯¤Ê¤¯¤¹¤ë¤«¤Ï¤¢¤Ê¤¿¤Î¼«Í³¤Ç¤¹¡£
             ¤è¤ê¿¤¯¤Î²¾ÁÛ¥¿¡¼¥ß¥Ê¥ë¤ò»È¤¦¤È¤è¤ê¿¤¯¤Î¥ê¥½¡¼¥¹¤ò»È¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
             8MB °Ê²¼¤Î¥á¥â¥ê¤·¤«¤Ê¤¤¾ì¹ç¤Ï¤³¤ì¤Ï½ÅÍפÊÌäÂê¤Ç¤¹¡£
             ¤â¤·É¬Íפ¬¤¢¤ì¤Ð
             <literal>secure</literal> ¤ò
             <literal>insecure</literal>
             ¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
             <important>
               <para>X ¤ò»È¤¤¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢
                 ºÇÄã°ì¤Ä¤Î²¾ÁÛ¥¿¡¼¥ß¥Ê¥ë (¤Î¥¨¥ó¥È¥ê) ¤ò»È¤ï¤º¤Ë»Ä¤·¤Æ¤ª¤¯¤«¡¢
                 off ¤Ë¤·¤Æ¤ª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
                 ¤Ä¤Þ¤ê¡¢12 ¸Ä¤Î
                 <keycap>Alt</keycap>-¥Õ¥¡¥ó¥¯¥·¥ç¥ó¥­¡¼¤¹¤Ù¤Æ¤Ç¥í¥°¥¤¥ó¥×¥í¥ó¥×¥È¤ò
                 ½Ð¤·¤¿¤¤¤Î¤Ê¤é¤Ð¡¢
                 »ÄÇ°¤Ê¤¬¤é X ¤ÏÍøÍѤǤ­¤Ê¤¤¤È¤¤¤¦¤³¤È¤Ç¤¹¡£
                 Ʊ¤¸¥Þ¥·¥ó¤Ç X ¥µ¡¼¥Ð¡¼¤âÆ°¤«¤·¤¿¤¤¤Î¤Ê¤é¤Ð
                 11 ¸Ä¤·¤«»È¤¨¤Þ¤»¤ó¡£
               </para>
             </important>
 
           <para>
             ²¾ÁÛ¥³¥ó¥½¡¼¥ë¤ò̵¸ú¤Ë¤¹¤ë¤â¤Ã¤È¤â´Êñ¤ÊÊýË¡¤Ï¡¢
             ¥³¥ó¥½¡¼¥ë¤ò
             off ¤Ë¤¹¤ë¤³¤È¤Ç¤¹¡£
             ¤¿¤È¤¨¤Ð 12 ¸Ä¤¹¤Ù¤Æ¤Î¥¿¡¼¥ß¥Ê¥ë¤ò³ä¤êÅö¤Æ¤Æ¤¤¤ë¾õÂÖ¤Ç
             X ¤òÆ°¤«¤·¤¿¤¤¤È¤­¤Ï¡¢
             ²¾ÁÛ¥¿¡¼¥ß¥Ê¥ë 12 ¤òÊѹ¹¤·¤Þ¤¹¡£
           </para>
 
           <programlisting>ttyvb   "/usr/libexec/getty Pc"         cons25  on secure</programlisting>
 
           <para>
             ¤³¤ì¤ò¼¡¤Î¤è¤¦¤ËÊѹ¹¤·¤Þ¤¹¡£
           </para>
 
           <programlisting>ttyvb   "/usr/libexec/getty Pc"         cons25  off secure</programlisting>
 
           <para>
             ¥­¡¼¥Ü¡¼¥É¤Ë¥Õ¥¡¥ó¥¯¥·¥ç¥ó¥­¡¼¤¬ 10 ¸Ä¤·¤«¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢
             ¼¡¤Î¤è¤¦¤ËÀßÄꤷ¤Þ¤¹¡£
           </para>
 
           <programlisting>ttyv9   "/usr/libexec/getty Pc"         cons25  off secure
 ttyva   "/usr/libexec/getty Pc"         cons25  off secure
 ttyvb   "/usr/libexec/getty Pc"         cons25  off secure</programlisting>
 
           <para>
             (¤³¤ì¤é¤Î¹Ô¤ò¾Ã¤¹¤À¤±¤Ç¤â¤¤¤¤¤Ç¤¹¡£)
           </para>
 
           <para>
             <filename>/etc/ttys</filename>
             ¤òÊÔ½¸¤·¤¿¤é¡¢
             ¼¡¤Ï½½Ê¬¤Ê¿ô¤Î²¾ÁÛ¥¿¡¼¥ß¥Ê¥ë¥Ç¥Ð¥¤¥¹¤òºî¤é¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
             ¤â¤Ã¤È¤â´Êñ¤ÊÊýË¡¤ò¼¨¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV vty12</userinput><emphasis> (12 ¸Ä¤Î¥Ç¥Ð¥¤¥¹¤ò¤Ä¤¯¤ë¾ì¹ç)</emphasis></screen>
 
           <para>
             ¤µ¤Æ¡¢²¾ÁÛ¥³¥ó¥½¡¼¥ë¤òÍ­¸ú¤Ë¤¹¤ë¤â¤Ã¤È¤â´Êñ (¤½¤·¤Æ³Î¼Â) ¤ÊÊýË¡¤Ï¡¢
             ºÆµ¯Æ°¤¹¤ë¤³¤È¤Ç¤¹¡£¤·¤«¤·¡¢ºÆµ¯Æ°¤·¤¿¤¯¤Ê¤¤¾ì¹ç¤Ï¡¢
             X ¥¦¥£¥ó¥É¥¦¥·¥¹¥Æ¥à¤ò½ªÎ»¤µ¤»¤Æ¼¡¤ÎÆâÍƤò
             (<username>root</username>¸¢¸Â¤Ç) ¼Â¹Ô¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
 
           <para>
             ½ÅÍפÊÅÀ¤Ï¡¢
             ¤³¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ëÁ°¤Ë X
             ¥¦¥£¥ó¥É¥¦¥·¥¹¥Æ¥à¤ò´°Á´¤Ë½ªÎ»¤µ¤»¤Æ¤ª¤¯¤³¤È¤Ç¤¹¡£
             ¤â¤·¤½¤¦¤·¤Ê¤¤¤È <command>kill</command>
             ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤¿¸å¡¢
             ¥·¥¹¥Æ¥à¤Ï¤ª¤½¤é¤¯¥Ï¥ó¥°¥¢¥Ã¥×¤¹¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="vty-from-x">
           <para>X ¤«¤é²¾ÁÛ¥³¥ó¥½¡¼¥ë¤ËÀÚÂؤ¨¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ²¾ÁÛ¥³¥ó¥½¡¼¥ë¤ØÌá¤ë¤Ë¤Ï
             <keycombo action="simul">
               <keycap>Ctrl</keycap>
               <keycap>Alt</keycap>
               <keycap>F<replaceable>n</replaceable></keycap>
             </keycombo> ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
             ºÇ½é¤Î²¾ÁÛ¥³¥ó¥½¡¼¥ë¤Ø¤Ï
             <keycombo action="simul">
               <keycap>Ctrl</keycap>
               <keycap>Alt</keycap>
               <keycap>F1</keycap>
             </keycombo> ¤ÇÌá¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Æ¥­¥¹¥È¥³¥ó¥½¡¼¥ë¤Ø°Ü¤Ã¤¿¸å¤Ï¡¢¤½¤ÎÃæ¤Ç°ÜÆ°¤¹¤ë¤Î¤Ë
             º£Å٤Ϥ¤¤Ä¤â¤É¤ª¤ê
             <keycombo action="simul">
               <keycap>Alt</keycap>
               <keycap>F<replaceable>n</replaceable></keycap>
             </keycombo> ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             X ¤Î¥»¥Ã¥·¥ç¥ó¤ØÌá¤ë¤Ë¤Ï X ¤ÎÁö¤Ã¤Æ¤¤¤ë²¾ÁÛ¥³¥ó¥½¡¼¥ë¤Ø
             ÀÚ¤êÂؤ¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤â¤·¤¢¤Ê¤¿¤¬ X ¤ò¥³¥Þ¥ó¥É¥é¥¤¥ó¤«¤é
             ¼Â¹Ô¤·¤Æ¤¤¤¿¤Î¤Ç¤¢¤ì¤Ð (¤¿¤È¤¨¤Ð <command>startx</command>
             ¤ò»È¤¦) X ¤Î¥»¥Ã¥·¥ç¥ó¤Ï¤½¤ì¤ò¼Â¹Ô¤·¤¿¥Æ¥­¥¹¥È¥³¥ó¥½¡¼¥ë¤Ç¤Ï¤Ê¤¯
             ºÇ½é¤Î»È¤ï¤ì¤Æ¤¤¤Ê¤¤²¾ÁÛ¥³¥ó¥½¡¼¥ë¤Ë³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£
             ¤¢¤Ê¤¿¤¬²¾ÁÛüËö¤ò 8 ¸ÄÍÑ°Õ¤·¤Æ¤¤¤ë¾ì¹ç¤Ï X ¤ò 9 ÈÖÌܤÎ
             ¥³¥ó¥½¡¼¥ë¤Ë¤¤¤ë¤Ï¤º¤Ç¡¢
             <keycombo action="simul">
               <keycap>Alt</keycap>
               <keycap>F9</keycap>
             </keycombo> ¤ò»È¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
             <note>
               <title>ÌõÃí</title>
               <para>
                 X ¤ËÌá¤ë¤Ë¤Ï¡¢
                 3 Ëç¤Î²¾ÁÛ¥³¥ó¥½¡¼¥ë¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï
                 <keycap>Alt</keycap>-<keycap>F4</keycap> ¤Ç¤¹¡£
                 Í­¸ú¤Ê²¾ÁÛ¥³¥ó¥½¡¼¥ë¤Î¿ô +1 ¤Î¥Õ¥¡¥ó¥¯¥·¥ç¥ó¥­¡¼¤Î
                 °ÌÃÖ¤Ë X ¤¬³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="xdm-boot">
           <para>XDM ¤òµ¯Æ°»þ¤Ëµ¯Æ°¤µ¤»¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             <ulink url="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=xdm">xdm</ulink>
             ¤Îµ¯Æ°ÊýË¡¤Ë¤Ä¤¤¤Æ¤ÏÆó¤Ä¤ÎήÇɤ¬¤¢¤ê¤Þ¤¹¡£
             °ìÊý¤ÎήÇɤǤÏÄ󶡤µ¤ì¤¿Îã¤ò»ÈÍѤ·¤Æ xdm ¤ò
             <filename>/etc/ttys</filename> (&man.ttys.5; »²¾È)
             ¤«¤éµ¯Æ°¤·¡¢¤â¤¦°ìÊý¤ÎήÇÉ¤Ç¤Ï xdm ¤òñ¤Ë
             <filename>rc.local</filename> (&man.rc.8; »²¾È)
             ¤Þ¤¿¤Ï <filename>/usr/local/etc/rc.d</filename> ¤Ë¤ª¤¤¤¿
             <filename>X.sh</filename> ¥¹¥¯¥ê¥×¥È¤«¤éµ¯Æ°¤·¤Þ¤¹¡£
             ¤É¤Á¤é¤âÀµ¤·¤¯¡¢ÊÒÊý¤¬Æ°ºî¤·¤Ê¤¤¾ì¹ç¤Ï¡¢¤â¤¦ÊÒÊý¤¬Æ°ºî¤¹¤ë¤Ç¤·¤ç¤¦¡£
             ¤É¤Á¤é¤â¾ì¹ç¤Ç¤â·ë²Ì¤ÏƱ¤¸¤Ç¤¢¤ê¡¢X ¤Ï¥°¥é¥Õ¥£¥«¥ë¤Ê
             <prompt>login:</prompt> ¥×¥í¥ó¥×¥È¤òɽ¼¨¤·¤Þ¤¹¡£
           </para>
 
           <para>
             <filename>ttys</filename> ¤òÍøÍѤ¹¤ëÊýË¡¤ÎÍøÅÀ¤Ï¡¢
             ¤É¤Î <acronym>vty</acronym> ¤Ç X ¤¬µ¯Æ°¤·¤¿¤«¤Îµ­Ï¿¤¬»Ä¤»¤ë¤³¤È¤È¡¢
             ¥í¥°¥¢¥¦¥È»þ¤Ë X ¥µ¡¼¥Ð¤òºÆµ¯Æ°¤¹¤ëÀÕǤ¤ò
             init ¤Ë²¡¤·¤Ä¤±¤ë¤³¤È¤¬¤Ç¤­¤ë¤³¤È¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             <filename>rc.local</filename> ¤«¤é¥í¡¼¥É¤µ¤ì¤ë¾ì¹ç¡¢
             <command>xdm</command> ¤Ï°ú¿ô¤ò»ý¤¿¤º¤Ë
             (¤¹¤Ê¤ï¤Á¡¢¥Ç¡¼¥â¥ó¤È¤·¤Æ) µ¯Æ°¤·¤Þ¤¹¡£
             <command>xdm</command> ¤Ï <command>getty</command>
             ¤¬µ¯Æ°¤·¤¿¸å¤Ë¥í¡¼¥É¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤½¤¦¤Ç¤Ê¤¤¤È¡¢<command>xdm</command> ¤Ï <command>getty</command>
             ¤È¾×Æͤ·¡¢¥³¥ó¥½¡¼¥ë¤ò¥í¥Ã¥¯¥¢¥¦¥È¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
             ¤³¤ÎÌäÂê¤ËÂн褹¤ëºÇÁ±¤ÎÊýË¡¤Ï¡¢
             µ¯Æ°¥¹¥¯¥ê¥×¥È (ÌõÃí: <filename>rc.local</filename>
             ¤Î¤³¤È) ¤Ç 10 ÉäۤɤΠ<command>sleep</command> ¤ò¼Â¹Ô¤µ¤»¡¢
             ¤½¤Î¸å¤Ë <command>xdm</command> ¤ò¥í¡¼¥É¤¹¤ë¤³¤È¤Ç¤¹¡£
           </para>
 
           <para>
             <filename>/etc/ttys</filename> ¤«¤é
             <command>xdm</command> ¤òµ¯Æ°¤µ¤»¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
             <command>xdm</command> ¤È <command>getty</command>
             ¤¬¾×Æͤ¹¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ÎÌäÂê¤ò²óÈò¤¹¤ë¤Ë¤Ï¡¢<filename>/usr/X11R6/lib/X11/xdm/Xservers</filename> ¤Ë
             <literal>vt</literal> ÈÖ¹æ¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>:0 local /usr/X11R6/bin/X vt4</programlisting>
 
           <para>¾å¤ÎÎã¤Ï¡¢<devicename>/dev/ttyv3</devicename> ¤ò
             X ¥µ¡¼¥Ð¤ËÂбþ¤µ¤»¤Þ¤¹¡£ÈÖ¹æ¤Ï 1 ¤«¤é»Ï¤Þ¤ê¤Þ¤¹¤Î¤ÇÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
             X ¥µ¡¼¥Ð¤Ï
             <acronym>vty</acronym> ¤ò 1 ¤«¤é¿ô¤¨¤Þ¤¹¤¬¡¢
             FreeBSD ¥«¡¼¥Í¥ë¤Ï
             <acronym>vty</acronym> ¤ò 0 ¤«¤é¿ô¤¨¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="xconsole-failure">
           <para><command>xconsole</command> ¤òÆ°¤«¤½¤¦¤È¤¹¤ë¤È
             <quote><computeroutput>Couldn't open console</computeroutput></quote>
             ¤È¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£</para>
         </question>
 
         <answer>
           <para>
             <application>X</application> ¤ò <command>startx</command>
             ¤Çµ¯Æ°¤·¤Þ¤¹¤È¡¢<devicename>/dev/console</devicename> ¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤Ï
             <emphasis>Êѹ¹¤Ç¤­¤Ê¤¤</emphasis>¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢
             <command>xterm -C</command> ¤ä <command>xconsole</command>
             ¤ÏÆ°¤­¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤³¤ì¤Ï¥³¥ó¥½¡¼¥ë¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤¬¡¢
             ɸ½à¤Ç¤Ï¤½¤Î¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤«¤é¤Ç¤¹¡£
             ¥Þ¥ë¥Á¥æ¡¼¥¶¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
             ¥æ¡¼¥¶¤Îï¤â¤¬¥·¥¹¥Æ¥à¥³¥ó¥½¡¼¥ë¤Ë½ñ¤­¹þ¤à¤³¤È¤¬²Äǽ¤Ç¤¢¤ëɬÍפÏɬ¤º¤·¤â¤¢¤ê¤Þ¤»¤ó¡£
             <acronym>VTY</acronym>
             ¤ò»È¤¤Ä¾ÀÜ¥Þ¥·¥ó¤Ë¥í¥°¥¤¥ó¤¹¤ë¥æ¡¼¥¶¤Î¤¿¤á¤Ë¡¢
             ¤³¤Î¤è¤¦¤ÊÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Ë
             &man.fbtab.5;
             ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             Í×ÅÀ¤ò½Ò¤Ù¤ë¤È¡¢¼¡¤Î¤è¤¦¤Ê·Á¼°¤Î¹Ô¤ò
             <filename>/etc/fbtab</filename> (&man.fbtab.5; »²¾È) ¤Ë²Ã¤¨¤Þ¤¹¡£
           </para>
 
           <programlisting>/dev/ttyv0 0600 /dev/console</programlisting>
 
           <para>
             ¤½¤¦¤¹¤ë¤È¡¢
             <devicename>/dev/ttyv0</devicename> ¤«¤é¥í¥°¥¤¥ó¤·¤¿¥æ¡¼¥¶¤¬
             ¥³¥ó¥½¡¼¥ë¤ò½êÍ­¤¹¤ë¤³¤È¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="xfree86-root">
           <para>¤ï¤¿¤·¤Ï¤¤¤Ä¤â XFree86 ¤ò°ìÈ̥桼¥¶¤«¤éµ¯Æ°¤·¤Æ¤¤¤¿¤Î¤Ç¤¹¤¬¡¢
             ºÇ¶á¤Ë¤Ê¤Ã¤Æ <username>root</username> ¥æ¡¼¥¶¤Ç¤Ê¤±¤ì¤Ð¤Ê
             ¤é¤Ê¤¤¤È¸À¤ï¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£</para>
         </question>
 
         <answer>
           <para>¤¹¤Ù¤Æ¤Î X ¥µ¡¼¥Ð¤Ï¡¢
             ¥Ó¥Ç¥ª¥Ï¡¼¥É¥¦¥§¥¢¤ËľÀÜ¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë <username>root</username>
             ¥æ¡¼¥¶¤Ç¼Â¹Ô¤µ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤Î XFree86 (&lt;= 3.3.6) ¤Ë´Þ¤Þ¤ì¤ë¤¹¤Ù¤Æ¤Î¥µ¡¼¥Ð¤Ï¡¢
             ¼«Æ°Åª¤Ë <username>root</username> ¸¢¸Â¤Ç¼Â¹Ô¤µ¤ì¤ë¤è¤¦¤Ë
             (<username>root</username> ¥æ¡¼¥¶¤Ë setuid
             ¤µ¤ì¤Æ) ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£
             X ¥µ¡¼¥Ð¤ÏÂ礭¤¯Ê£»¨¤Ê¥×¥í¥°¥é¥à¤Ç¤¢¤ê¡¢
             ¤³¤ì¤ÏÌÀ¤é¤«¤Ë¥»¥­¥å¥ê¥Æ¥£¤ò´í¸±¤Ë»¯¤¹Í×°ø¤È¤Ê¤ê¤Þ¤¹¡£
             ¤½¤Î¤¿¤á¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤Î XFree86 ¤Ç¤Ï¡¢
             ¥µ¡¼¥Ð¤ò <username>root</username> ¥æ¡¼¥¶¤Ë setuid
             ¤·¤Ê¤¤¤Ç¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£</para>
 
           <para>X ¥µ¡¼¥Ð¤ò root ¥æ¡¼¥¶¤ÇÆ°¤«¤¹¤È¤¤¤¦¤Î¤Ï¡¢
             ÌÀ¤é¤«¤Ë¥»¥­¥å¥ê¥Æ¥£Åª¤ËÉÔŬÅö¤Ç¼õ¤±Æþ¤ì¤é¤ì¤Ê¤¤¤³¤È¤Ç¤¹¡£
             X ¤ò°ìÈ̥桼¥¶¤Ç¼Â¹Ô¤¹¤ë¤Ë¤Ï¡¢Æó¤Ä¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£
             °ì¤Ä¤Ï <command>xdm</command> ¤ä¡¢¤½¤Î¾¤Î¥Ç¥£¥¹¥×¥ì¥¤¥Þ¥Í¡¼¥¸¥ã
             (¤¿¤È¤¨¤Ð <command>kdm</command> ¤Ê¤É) ¤ò»È¤¦¤³¤È¡¢
             ¤â¤¦°ì¤Ä¤Ï <command>Xwrapper</command> ¤ò»È¤¦¤³¤È¤Ç¤¹¡£
           </para>
 
           <para><command>xdm</command> ¤Ï¡¢
             ¥°¥é¥Õ¥£¥«¥ë¤Ê¥í¥°¥¤¥ó²èÌ̤ò°·¤¦¥Ç¡¼¥â¥ó¤Ç¤¹¡£
             Ä̾µ¯Æ°»þ¤Ë¼Â¹Ô¤µ¤ì¡¢
             ³Æ¥æ¡¼¥¶¤Îǧ¾Ú¤È¥æ¡¼¥¶¥»¥·¥ç¥ó¤ò³«»Ï¤µ¤»¤ëµ¡Ç½¤ò¼Â¸½¤·¤Þ¤¹¡£
             ´ðËÜŪ¤Ë¡¢<command>getty</command> ¤È <command>login</command>
             ¤Î¥°¥é¥Õ¥£¥Ã¥¯ÈÇ¡¢¤È¹Í¤¨¤ÆÎɤ¤¤Ç¤·¤ç¤¦¡£
             <command>xdm</command> ¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             <ulink url="http://www.xfree86.org/support.html">XFree86
               ´ØϢʸ½ñ</ulink> ¤ª¤è¤Ó
             <link linkend="xdm-boot">FAQ ¹àÌÜ</link>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
 
           <para><command>Xwrapper</command> ¤È¤Ï¡¢X ¥µ¡¼¥ÐÍѤΥé¥Ã¥Ñ
             (wrapper) ¤Î¤³¤È¤Ç¤¹¡£
             ¤³¤ì¤ÏɬÍפʥ»¥­¥å¥ê¥Æ¥£¤ò³ÎÊݤ·¤Ä¤Ä¡¢°ìÈ̥桼¥¶¤¬ X
             ¥µ¡¼¥Ð¤ò¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ë¤·¤¿¾®¤µ¤Ê¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ç¡¢
             ¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¿ô¤ÎÀµÅöÀ­¥Á¥§¥Ã¥¯¤ò¹Ô¤Ê¤¤¡¢
             ¤½¤ì¤òÄ̲᤹¤ì¤ÐŬÀÚ¤Ê X ¥µ¡¼¥Ð¤òµ¯Æ°¤·¤Þ¤¹¡£
             ²¿¤é¤«¤ÎÍýͳ¤Ç¥Ç¥£¥¹¥×¥ì¥¤¥Þ¥Í¡¼¥¸¥ã¤ò»È¤¤¤¿¤¯¤Ê¤¤¾ì¹ç¤Ë
             ¤³¤ì¤ò»È¤¦¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£
             Ports Collection Á´ÂΤò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¤¤ì¤Ð¡¢
             <filename>/usr/ports/x11/wrapper</filename>
             ¤Ë¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ps2-x">
           <para>»ä¤Î PS/2 ¥Þ¥¦¥¹¤Ï X ¥¦¥£¥ó¥É¥¦¥·¥¹¥Æ¥à¾å¤Ç¤¦¤Þ¤¯Æ°¤­¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             ¤¢¤Ê¤¿¤Î¥Þ¥¦¥¹¤È¥Þ¥¦¥¹¥É¥é¥¤¥Ð¤¬¤¦¤Þ¤¯Æ±´ü¤·¤Æ¤¤¤Ê¤¤¤«¤é¤«¤â¤·¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             FreeBSD 2.2.5 ¤Þ¤Ç¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢X ¤«¤é²¾ÁÛ¥¿¡¼¥ß¥Ê¥ë¤ØÀÚÂؤ¨¤Æ¡¢
             ¤Þ¤¿ X ¤ØÌá¤ë¤ÈºÆƱ´ü¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ¤³¤ÎÌäÂ꤬¤è¤¯µ¯¤­¤ë¤è¤¦¤Ç¤¢¤ì¤Ð¡¢¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó
             ¥Õ¥¡¥¤¥ë¤Ë¼¡¤Î¥ª¥×¥·¥ç¥ó¤ò½ñ¤¤¤Æ¥«¡¼¥Í¥ë¤òºÆ¹½À®¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>options PSM_CHECKSYNC</programlisting>
 
           <para>
             ¤â¤·¡¢¥«¡¼¥Í¥ë¤ÎºÆ¹½ÃÛ¤ò¹Ô¤Ê¤Ã¤¿¤³¤È¤¬¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢
             <link linkend="make-kernel">¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤¹¤ë</link>¤Î¹à¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ë¤è¤ê¡¢
             ¥Þ¥¦¥¹¤È¥É¥é¥¤¥Ð¤ÎƱ´ü¤ÇÌäÂ꤬µ¯¤­¤ë²ÄǽÀ­¤Ï¾¯¤Ê¤¯¤Ê¤ë¤Ç¤·¤ç¤¦¡£
             ¤â¤·¤½¤ì¤Ç¤â¤³¤ÎÌäÂ꤬µ¯¤­¤ë¤è¤¦¤Ê¤é¤Ð¡¢
             ºÆƱ´ü¤µ¤»¤ë¤Ë¤Ï¥Þ¥¦¥¹¤òÆ°¤«¤µ¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤ª¤¤¤Æ
             ¥Þ¥¦¥¹¥Ü¥¿¥ó¤Î¤É¤ì¤«¤ò²¡¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï»ÄÇ°¤Ê¤¬¤é¤¹¤Ù¤Æ¤Î¥·¥¹¥Æ¥à¤ÇƯ¤¯¤ï¤±¤Ç¤Ï¤Ê¤¯¡¢
             ¤Þ¤¿¡¢PS/2 ¥Þ¥¦¥¹¥Ý¡¼¥È¤Ë¤Ä¤Ê¤¬¤ì¤Æ¤¤¤ë¤Î¤¬
             ¥¿¥Ã¥× (tap) µ¡Ç½¤ò»ý¤Ä ¥¢¥ë¥×¥¹¼ÒÀ½ GlidePoint ¥Ç¥Ð¥¤¥¹¤Î¾ì¹ç¡¢
             ¥¿¥Ã¥×µ¡Ç½¤¬Ìµ¸ú¤È¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             FreeBSD 2.2.6 °Ê¹ß¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
             Ʊ´ü¤Î¥Á¥§¥Ã¥¯ÊýË¡¤¬¾¯¤·²þÁ±¤µ¤ì¤¿¤Î¤Çɸ½à¤ÇÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             GlidePoint ¤Ç¤â¤¦¤Þ¤¯Æ¯¤­¤Þ¤¹ (Ʊ´ü¥Á¥§¥Ã¥¯¤¬É¸½à¤Îµ¡Ç½¤Ë¤Ê¤Ã¤¿¤Î¤Ç
             <literal>PSM_CHECKSYNC</literal>
             ¥ª¥×¥·¥ç¥ó¤Ï¤³¤ì¤é¤Î¥Ð¡¼¥¸¥ç¥ó¤«¤é¤Ïºï½ü¤µ¤ì¤Þ¤·¤¿)¡£
             ¤·¤«¤·¤Ê¤¬¤é¡¢
             ¤Þ¤ì¤Ë¥É¥é¥¤¥Ð¤¬´Ö°ã¤Ã¤Æ (ÌõÃí:
             ÌäÂ꤬¤Ê¤¤¤Î¤Ë) Ʊ´ü¤Ë´Ø¤·¤ÆÌäÂ꤬¤¢¤ë¤ÈÊó¹ð¤·¡¢¥«¡¼¥Í¥ë¤«¤é
           </para>
 
           <programlisting>psmintr: out of sync (xxxx != yyyy)</programlisting>
 
           <para>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬½ÐÎϤµ¤ì¤Æ¡¢¥Þ¥¦¥¹¤¬Àµ¤·¤¯Æ°ºî¤·¤Æ¤¤¤Ê¤¤¤è¤¦¤Ë¸«¤¨¤ë
             ¤³¤È¤¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤â¤·¤³¤Î¤è¤¦¤Ê¤³¤È¤¬µ¯¤³¤ë¾ì¹ç¤Ë¤Ï¡¢PS/2 ¥Þ¥¦¥¹¥É¥é¥¤¥Ð¤Î¥Õ¥é¥°¤Ë
             0x100 ¤ò»ØÄꤷ¤ÆƱ´ü¥Á¥§¥Ã¥¯¤ò̵¸ú¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£¥·¥¹¥Æ¥à¤Îµ¯Æ°»þ¤Ë
             <quote><option>-c</option></quote>
             µ¯Æ°¥ª¥×¥·¥ç¥ó¤òÍ¿¤¨¤Æ
             <emphasis>UserConfig</emphasis> ¤ËÆþ¤ê¤Þ¤¹¡£
           </para>
 
           <screen>boot: <userinput>-c</userinput></screen>
           <screen><prompt>boot:</prompt> <userinput><option>-c</option></userinput></screen>
 
           <para>
             <emphasis>UserConfig</emphasis>
             ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ç°Ê²¼¤Î¤è¤¦¤ËÆþÎϤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>UserConfig&gt; <userinput>flags psm0 0x100</userinput>
 UserConfig&gt; <userinput>quit</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ps2-mousesystems">
           <para>MouseSystems ¤Î PS/2 ¥Þ¥¦¥¹¤¬¤¦¤Þ¤¯Æ°¤­¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             MouseSystems ¤Î PS/2 ¥Þ¥¦¥¹¤Î¤¢¤ë¥â¥Ç¥ë¤Ï¡¢
             ¹â²òÁüÅ٥⡼¥É¤Î¾ì¹ç¤Ë¤Î¤ßÀµ¤·¤¯Æ°ºî¤¹¤ë¤È¤¤¤¦¤³¤È¤¬Êó¹ð¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤½¤ì°Ê³°¤Î¥â¡¼¥É¤Ç¤Ï¡¢
             ¥Þ¥¦¥¹¥«¡¼¥½¥ë¤¬¤·¤ç¤Ã¤Á¤å¤¦¥¹¥¯¥ê¡¼¥óº¸¾å¤Ë¹Ô¤Ã¤Æ¤·¤Þ¤¦¤«¤â¤·¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             »ÄÇ°¤Ê¤¬¤é FreeBSD 2.0.X ¤ä 2.1.X ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
             ¤³¤ÎÌäÂê¤ò²ò·è¤¹¤ëÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             2.2 ¤«¤é 2.2.5 ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
             °Ê²¼¤Î¥Ñ¥Ã¥Á¤ò
             <filename>/sys/i386/isa/psm.c</filename>
             ¤ËŬÍѤ·¥«¡¼¥Í¥ë¤ÎºÆ¹½ÃÛ¤ò¹Ô¤Ê¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤â¤·¡¢¥«¡¼¥Í¥ë¤ÎºÆ¹½ÃÛ¤ò¹Ô¤Ê¤Ã¤¿¤³¤È¤¬¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢
             <link linkend="make-kernel">¥«¡¼¥Í¥ë¤Î¹½ÃÛ</link>¤Î¹à¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>@@ -766,6 +766,8 @@
      if (verbose &gt;= 2)
          log(LOG_DEBUG, "psm%d: SET_DEFAULTS return code:%04x\n",
              unit, i);
 +    set_mouse_resolution(sc-&gt;kbdc, PSMD_RES_HIGH);
 +
  #if 0
      set_mouse_scaling(sc-&gt;kbdc);    /* 1:1 scaling */
      set_mouse_mode(sc-&gt;kbdc);               /* stream mode */</programlisting>
 
 
           <para>
             FreeBSD 2.2.6 °Ê¹ß¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
             PS/2 ¥Þ¥¦¥¹¥É¥é¥¤¥Ð¤Î¥Õ¥é¥°¤Ë
             0x04 ¤ò»ØÄꤷ¤Æ¥Þ¥¦¥¹¤ò¹â²òÁüÅ٥⡼¥É¤Ë¤·¤Þ¤¹¡£
             ¥·¥¹¥Æ¥à¤Îµ¯Æ°»þ¤Ë
             <option>-c</option>
             µ¯Æ°¥ª¥×¥·¥ç¥ó¤òÍ¿¤¨¤Æ
             <emphasis>UserConfig</emphasis> ¤ËÆþ¤ê¤Þ¤¹¡£
           </para>
 
 
           <screen>boot: <userinput>-c</userinput></screen>
 
           <para>
             <emphasis>UserConfig</emphasis>
             ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ç°Ê²¼¤Î¤è¤¦¤ËÆþÎϤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>UserConfig&gt; <userinput>flags psm0 0x04</userinput>
 UserConfig&gt; <userinput>quit</userinput></screen>
 
           <para>
             ¥Þ¥¦¥¹¤Ë´Ø¤¹¤ëÉÔ¶ñ¹ç¤Î¾¤Î¸¶°ø¤Î²ÄǽÀ­¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             ľÁ°¤Î¥»¥¯¥·¥ç¥ó¤â¸«¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="imake-tmpl">
           <para>X ¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ò¹½ÃÛ¤¹¤ë»þ¤Ë¡¢
             <computeroutput>imake can't find <filename>Imake.tmpl</filename></computeroutput>
             ¤È¤Ê¤ê¤Þ¤¹¡£¤É¤³¤Ë¤¢¤ë¤Î¤Ç¤·¤ç¤¦¤«?
           </para>
         </question>
 
         <answer>
           <para>
             <filename>Imake.tmpl</filename> ¤Ï
             X ¤Îɸ½à¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¹½Ãۥġ¼¥ë¤Ç¤¢¤ë Imake ¥Ñ¥Ã¥±¡¼¥¸¤Î°ìÉô¤Ç¤¹¡£
             <filename>Imake.tmpl</filename> ¤Ï¡¢
             X ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¹½ÃÛ¤ËɬÍפÊ¿¤¯¤Î¥Ø¥Ã¥À¥Õ¥¡¥¤¥ë¤ÈƱÍͤˡ¢
             X ¤Î¥×¥í¥°¥é¥à¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
             <command>sysinstall</command> ¤ò»È¤¦¤«¡¢
             ¼êÆ°¤Ç X ¤Î¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤«¤é¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mouse-button-reverse">
           <para>¥Þ¥¦¥¹¤Î¥Ü¥¿¥ó¤òÆþ¤ìÂؤ¨¤ëÊýË¡¤Ï¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             <filename>.xinitrc</filename> ¤«
             <filename>.xsession</filename> ¤Ç
           </para>
 
             <programlisting><command>xmodmap</command> <option>-e "pointer = 3 2 1"</option></programlisting>
 
           <para>
             ¤È¤¤¤¦¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="install-splash">
           <para>¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ï¤É¤¦¤¹¤ë¤Î¤Ç¤¹¤«¡£
             ¤É¤³¤Ç¸«¤Ä¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 3.1 ¤Î¥ê¥ê¡¼¥¹Ä¾Á°¤Ë¡¢µ¯Æ°¥á¥Ã¥»¡¼¥¸¤Îɽ¼¨´ü´Ö¤Ë
             ¤¤¤ï¤æ¤ë &quot;¥¹¥×¥é¥Ã¥·¥å&quot;
             ¥¹¥¯¥ê¡¼¥ó¤òɽ¼¨¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤ë¿·¤·¤¤µ¡Ç½¤¬Äɲ䵤ì¤Þ¤·¤¿¡£
             ¤¤¤Þ¤Î¤È¤³¤í¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤Ï
             256 ¿§¤Î¥Ó¥Ã¥È¥Þ¥Ã¥× (<filename>*.BMP</filename>) ¤«
             ZSoft PCX (<filename>*.PCX</filename>) ¥Õ¥¡¥¤¥ë¤Ç¤¹¡£
             ¤½¤ì¤Ë²Ã¤¨¤Æ¡¢É¸½à¤Î <acronym>VGA</acronym> ¥¢¥À¥×¥¿¤Ç¤ÎÆ°ºî¤µ¤»¤ë¤Ë¤Ï
             320x200 °Ê²¼¤Î²òÁüÅ٤Ǥ¢¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¥«¡¼¥Í¥ë¤Ë <acronym>VESA</acronym>
             ¥µ¥Ý¡¼¥È¤òÄɲ乤ì¤Ð 1024x768
             ¤Þ¤Ç¤Î¤è¤êÂ礭¤¤¥Ó¥Ã¥È¥Þ¥Ã¥×¤ò»ÈÍѤǤ­¤Þ¤¹¡£
             <acronym>VESA</acronym> ¥µ¥Ý¡¼¥È¤òÍ­¸ú²½¤¹¤ë¤Ë¤Ï¤Þ¤º¡¢
             ¥«¡¼¥Í¥ë¤¬
             <literal>VM86</literal>
             ¥«¡¼¥Í¥ë¥ª¥×¥·¥ç¥ó¤È¤È¤â¤Ë¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
             <acronym>VESA</acronym> ¥µ¥Ý¡¼¥È¤½¤Î¤â¤Î¤Ï
             <literal>VESA</literal> ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ª¥×¥·¥ç¥ó
             ¤Ë¤è¤Ã¤ÆľÀÜ¥«¡¼¥Í¥ëÃæ¤Ë¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤«¡¢
             µ¯Æ°»þ¤Ë <acronym>VESA</acronym> kld
             ¥â¥¸¥å¡¼¥ë¤òÆɤ߹þ¤Þ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤ò»È¤¦¤Ë¤Ï¡¢
             FreeBSD
             ¤Îµ¯Æ°¥×¥í¥»¥¹¤ò¥³¥ó¥È¥í¡¼¥ë¤¹¤ë¥¹¥¿¡¼¥È¥¢¥Ã¥×¥Õ¥¡¥¤¥ë¤ò½ñ¤­´¹¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ï FreeBSD 3.2 ¤Î¥ê¥ê¡¼¥¹°ÊÁ°¤ËÊѹ¹¤µ¤ì¤Þ¤·¤¿¤Î¤Ç¡¢
             ¸½ºß¤Ï¡¢¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤òÆɤ߹þ¤àÊýË¡¤¬Æó¤Ä¤¢¤ê¤Þ¤¹¡£
           </para>
 
             <itemizedlist>
               <listitem>
                 <para>FreeBSD 3.1 ¤Î¾ì¹ç</para>
 
                 <para>
                   ¤Þ¤ººÇ½é¤Î¥¹¥Æ¥Ã¥×¤Ï¡¢
                   ¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤Î¥Ó¥Ã¥È¥Þ¥Ã¥×ÈǤòõ¤·¤Æ¤¯¤ë¤³¤È¤Ç¤¹¡£
                   3.1-RELEASE ¤Ç¤Ï Windows
                   ¤Î¥Ó¥Ã¥È¥Þ¥Ã¥×·Á¼°¤Î¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤À¤±¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
                   ¤ªË¾¤ß¤Î¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤ò¸«¤Ä¤±¤¿¤Ê¤é¡¢¤½¤ì¤ò
                   <filename>/boot/splash.bmp</filename>
                   ¤Ë¥³¥Ô¡¼¤·¤Þ¤¹¡£¼¡¤Ë¡¢¤³¤ì¤é¤Î¹Ô¤¬½ñ¤«¤ì¤¿
                   <filename>/boot/loader.rc</filename>
                   ¥Õ¥¡¥¤¥ë¤¬É¬ÍפǤ¹¡£
                 </para>
 
                 <programlisting>load kernel
 load -t splash_image_data /boot/splash.bmp
 load splash_bmp
 autoboot</programlisting>
               </listitem>
 
               <listitem>
                 <para>FreeBSD 3.2 °Ê¹ß¤Î¾ì¹ç</para>
 
                 <para>PCX ·Á¼°¤Î¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤Î¥µ¥Ý¡¼¥È¤¬Äɲ䵤ì¤ë¤ÈƱ»þ¤Ë¡¢
                   FreeBSD 3.2 ¤Ë¤Ïµ¯Æ°¥×¥í¥»¥¹¤òÀßÄꤹ¤ë¡¢
                   ¤è¤êÀöÎý¤µ¤ì¤¿ÊýË¡¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
                   ¤â¤·¤ªË¾¤ß¤Ê¤é¡¢¾å¤Ë¼¨¤·¤¿
                   FreeBSD 3.1 ÍѤÎÊýË¡¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
                   ¤â¤·¤½¤¦¤·¤¿¤¯¤Æ¡¢¤«¤Ä PCX ·Á¼°¤ò»È¤¤¤¿¤¤¤Ê¤é¡¢
                   <literal>splash_bmp</literal> ¤ò
                   <literal>splash_pcx</literal> ¤ÈÆɤߴ¹¤¨¤Æ¤¯¤À¤µ¤¤¡£
                   ¤½¤¦¤Ç¤Ï¤Ê¤¯¤Æ¡¢¿·¤·¤¤µ¯Æ°ÀßÄêÊýË¡¤ò»È¤¦¤Î¤Ê¤é¡¢
                   ¼¡¤Î¿ô¹Ô¤¬½ñ¤«¤ì¤¿ <filename>/boot/loader.rc</filename>
                   ¥Õ¥¡¥¤¥ë¤È¡¢</para>
 
                 <programlisting>include /boot/loader.4th
 start</programlisting>
 
                 <para>
                   ¼¡¤Î¿ô¹Ô¤¬´Þ¤Þ¤ì¤¿
                   <filename>/boot/loader.conf</filename>
                   ¥Õ¥¡¥¤¥ë¤òºî¤ë¤³¤È¤¬É¬ÍפǤ¹¡£
                 </para>
 
                 <programlisting>splash_bmp_load="YES"
 bitmap_load="YES"</programlisting>
 
                 <para>
                   ¤³¤ÎÎã¤Ç¤Ï¡¢¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤È¤·¤Æ
                   <filename>/boot/splash.bmp</filename>
                   ¤ò»È¤¦¤³¤È¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£PCX ·Á¼°¤Î¥Õ¥¡¥¤¥ë¤ò»È¤¦¾ì¹ç¤Ë¤Ï¡¢
                   ¤½¤Î¥Õ¥¡¥¤¥ë¤ò <filename>/boot/splash.pcx</filename> ¤Ë¥³¥Ô¡¼¤·¤Æ¡¢
                   ¾å¤Ç¼¨¤·¤¿¤è¤¦¤Ë
                   <filename>/boot/loader.rc</filename> ¤òºî¤ê¤Þ¤¹¡£
                   ¤½¤·¤Æ¡¢¼¡¤ÎÆâÍƤÎ
                   <filename>/boot/loader.conf</filename>
                   ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤òºî¤Ã¤Æ¤¯¤À¤µ¤¤¡£
                 </para>
 
                 <programlisting>splash_pcx_load="YES"
 bitmap_load="YES"
 bitmap_name="/boot/splash.pcx"</programlisting>
               </listitem>
             </itemizedlist>
 
           <para>
             ¤µ¤Æ¡¢¤¢¤È¤Ï¥¹¥×¥é¥Ã¥·¥å¥¹¥¯¥ê¡¼¥ó¤òÍÑ°Õ¤¹¤ë¤À¤±¤Ç¤¹¡£
             ¤½¤ì¤Ë¤Ï <ulink url="http://www.baldwin.cx/splash/">http://www.baldwin.cx/splash/</ulink>
             ¤Î¥®¥ã¥é¥ê¡¼¤ò¥µ¡¼¥Õ¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="windows-keys">
           <para>X ¤Ç Windows(tm) ¥­¡¼¤ò»È¤¦¤³¤È¤Ï¤Ç¤­¤ë¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Ï¤¤¡¢¤â¤Á¤í¤ó¡£
             ¤É¤¦¤¤¤¦Æ°ºî¤ò¤¹¤ë¤«¤Ë¤Ä¤¤¤ÆÄêµÁ¤¹¤ë¤Ë¤Ï &man.xmodmap.1; ¤ò»È¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ɸ½àŪ¤Ê &quot;Windows(tm)&quot; ¥­¡¼¥Ü¡¼¥É¤Î¾ì¹ç¡¢
             Âбþ¤¹¤ë¥­¡¼¥³¡¼¥É¤Ï 3 ¼ïÎढ¤ê¤Þ¤¹¡£
           </para>
 
           <itemizedlist>
             <listitem>
               <para>115 - º¸¤Î Ctrl ¤È Alt ¤Î´Ö¤Ë¤¢¤ë Windows(tm) ¥­¡¼</para>
             </listitem>
 
             <listitem>
               <para>116 - ±¦¤Î Alt ¤È Gr ¤Î´Ö¤Ë¤¢¤ë Windows(tm) ¥­¡¼</para>
             </listitem>
 
             <listitem>
               <para>117 - ±¦¤Î Ctrl ¤Îº¸Î٤ˤ¢¤ë¥á¥Ë¥å¡¼¥­¡¼</para>
             </listitem>
           </itemizedlist>
 
           <para>
             º¸¤Ë¤¢¤ë Windows(tm) ¥­¡¼¤ò²¡¤¹¤È¥«¥ó¥Þµ­¹æ¤¬ÆþÎϤµ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢
             ¤³¤ó¤ÊÉ÷¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>xmodmap -e "keycode 115 = comma"</userinput></screen>
 
           <para>
             ÀßÄê¤òÈ¿±Ç¤µ¤»¤ë¤Ë¤Ï¡¢¤ª¤½¤é¤¯¥¦¥£¥ó¥É¥¦¥Þ¥Í¡¼¥¸¥ã¤òºÆµ¯Æ°¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             Windows(tm) ¥­¡¼¤Î¥­¡¼¥Þ¥Ã¥×¤ò X µ¯Æ°»þ¤ËËè²ó¡¢
             ¼«Æ°Åª¤ËÍ­¸ú²½¤¹¤ë¤Ë¤Ï <command>xmodmap</command> ¥³¥Þ¥ó¥É¤ò
             <filename>~/.xinitrc</filename> ¤ËÄɲ乤뤫¡¢
             ¤â¤·¤¯¤Ï¤ª¤¹¤¹¤á¤Ç¤­¤ëÊýË¡¤È¤·¤Æ
             <filename>~/.xmodmaprc</filename> ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Æ¡¢
             ¤½¤Î¥Õ¥¡¥¤¥ë¤Î°ì¹Ô°ì¹Ô¤Ë <command>xmodmap</command>
             ¤Î¥ª¥×¥·¥ç¥ó¤òµ­½Ò¤·¡¢¼¡¤Î°ì¹Ô
           </para>
 
           <programlisting>xmodmap $HOME/.xmodmaprc</programlisting>
 
           <para>¤ò <filename>~/.xinitrc</filename>
             ¤ËÄɲ乤ë¤È¤¤¤¦ÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>
             ¤¿¤È¤¨¤Ð¡¢Àè¤Û¤É¤¢¤²¤¿»°¤Ä¤Î¥­¡¼¤ò F13¡¢F14¡¢F15 ¤Ë³ä¤êÅö¤Æ¤ë¤È¤·¤Þ¤¹¡£
             ¤³¤¦¤·¤Æ¤ª¤±¤Ð¡¢¸å¤Û¤É¼¨¤¹¤è¤¦¤Ë¡¢¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ä
             ¥¦¥£¥ó¥É¥¦¥Þ¥Í¡¼¥¸¥ã¤ÎÊØÍø¤Êµ¡Ç½¤ò
             ¤½¤Î»°¤Ä¤Î¥­¡¼¤Ë´Êñ¤Ë³ä¤êÅö¤Æ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤¦¤¹¤ë¤Ë¤Ï¡¢¼¡¤ÎÆâÍƤò <filename>~/.xmodmaprc</filename>
             ¤ËÄɲä·¤Þ¤¹¡£
           </para>
 
           <programlisting>keycode 115 = F13
 keycode 116 = F14
 keycode 117 = F15</programlisting>
 
           <para>
             ¤¿¤È¤¨¤Ð <command>fvwm2</command> ¤ò»È¤Ã¤Æ¤¤¤¿¤é¡¢
             F13 ¤ò¥«¡¼¥½¥ë²¼¤Î¥¦¥£¥ó¥É¥¦¤Î¥¢¥¤¥³¥ó²½¡¢
             F14 ¤ò¥¦¥£¥ó¥É¥¦¤ÎÁ°ÌÌ/ÇØÌ̲½¡¢
             F15 ¤ò¡¢¤¢¤¿¤«¤â¥Ç¥¹¥¯¥È¥Ã¥×¤Ë¥«¡¼¥½¥ë¤¬Â¸ºß¤·¤Ê¤¤¤«¤Î¤è¤¦¤Ë¡¢
             ¥á¥¤¥ó¥ï¡¼¥¯¥¹¥Ú¡¼¥¹ (¥¢¥×¥ê¥±¡¼¥·¥ç¥ó)
             ¤Î¥á¥Ë¥å¡¼¤ò¸Æ¤Ó½Ð¤»¤ëµ¡Ç½¤Ë³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£
             ºÇ¸å¤Îµ¡Ç½¤Ï¡¢¤½¤Î¥Ç¥¹¥¯¥È¥Ã¥×¤¬¤Þ¤Ã¤¿¤¯¸«¤¨¤Ê¤¤¤È¤­¤ËÊØÍø¤Ç¤¹¡£
             (¤Þ¤¿¡¢¥­¡¼¥È¥Ã¥×¤Î¥í¥´¤Ë¤â¤Ô¤Ã¤¿¤ê¤Ç¤¹)
             <!-- hrs/2000/03/10: need refine translation -->
           </para>
 
           <para>
             <filename>~/.fvwmrc</filename> ¤Î¼¡¤Î¥¨¥ó¥È¥ê¤Ï¡¢Á°½Ò¤Î
             ÀßÄê¤ò¼Â¸½¤·¤Þ¤¹¡£
           </para>
 
           <programlisting>Key F13        FTIWS    A        Iconify
 Key F14        FTIWS    A        RaiseLower
 Key F15        A        A        Menu Workplace Nop</programlisting>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="networking">
     <title>¥Í¥Ã¥È¥ï¡¼¥­¥ó¥°</title>
 
     <para>
       <emphasis>Ìõ:
         &a.jp.arimura;¡¢
         &a.jp.shou;¡¢
         ¤Ë¤·¤« <email>nishika@cheerful.com</email>¡¢
         &a.jp.kiroh;¡¢
         1998 ǯ 10 ·î 4 Æü</emphasis>
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="diskless-booting">
           <para><quote>¥Ç¥£¥¹¥¯¥ì¥¹¥Ö¡¼¥È (diskless boot)</quote>
             ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¤É¤³¤ÇÆÀ¤é¤ì¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para><quote>¥Ç¥£¥¹¥¯¥ì¥¹¥Ö¡¼¥È (diskless boot)</quote>
             ¤È¤¤¤¦¤Î¤Ï¡¢FreeBSD ¤¬¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Çµ¯Æ°¤·¡¢
             ɬÍפʥե¡¥¤¥ë¤ò¼«Ê¬¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ç¤Ï¤Ê¤¯¤Æ¥µ¡¼¥Ð¤«¤éÆɤ߹þ¤à¤â¤Î¤Ç¤¹¡£
             ¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï
             <ulink url="../handbook/diskless.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡Ö¥Ç¥£¥¹¥¯¥ì¥¹¥Ö¡¼¥È¡×</ulink>¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="router">
           <para>
             FreeBSD ¤ò¥Í¥Ã¥È¥ï¡¼¥¯¤Î¥ë¡¼¥¿ (router) ¤È¤·¤Æ»ÈÍѤ¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤¹¤«?
           </para>
         </question>
 
         <answer>
           <para>
             ¥¤¥ó¥¿¡¼¥Í¥Ã¥Èɸ½à¤ä¤³¤ì¤Þ¤Ç¤Î¤è¤¤·Ð¸³¤Ë¤è¤Ã¤Æ»ØŦ¤µ¤ì¤Æ¤¤¤ëÄ̤ꡢ
             FreeBSD ¤Ïɸ½à¤Ç¤Ï¥Ñ¥±¥Ã¥È¤òžÁ÷ (forward) ¤¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤Þ¤»¤ó¡£
             ¤·¤«¤·¡¢
             &man.rc.conf.5;
             ¤ÎÃæ¤Ç¼¡¤ÎÊÑ¿ô¤ÎÃͤò
             <literal>YES</literal>
             ¤È¤¹¤ë»ö¤Ë¤è¤Ã¤Æ¤³¤Îµ¡Ç½¤òÍ­¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <programlisting>gateway_enable=YES          # Set to YES if this host will be a gateway</programlisting>
 
           <para>
             ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ë¤è¤Ã¤Æ
             &man.sysctl.8;
             ¤ÎÊÑ¿ô
             <varname>net.inet.ip.forwarding</varname> ¤¬
             <literal>1</literal> ¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤Û¤È¤ó¤É¤Î¾ì¹ç¡¢
             ¥ë¡¼¥¿¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤òƱ¤¸¥Í¥Ã¥È¥ï¡¼¥¯¤Î¾¤Î·×»»µ¡Åù¤ËÃΤ餻¤ë¤¿¤á¤Ë¡¢
             ·ÐÏ©À©¸æ¤Î¤¿¤á¤Î¥×¥í¥»¥¹¤òÁö¤é¤»¤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£
             FreeBSD ¤Ë¤Ï BSD ¤Îɸ½à·ÐÏ©À©¸æ¥Ç¡¼¥â¥ó¤Ç¤¢¤ë
             &man.routed.8;
             ¤¬ÉÕ°¤·¤Æ¤¤¤Þ¤¹¤¬¡¢¤è¤êÊ£»¨¤Ê¾õ¶·¤ËÂн褹¤ë¤¿¤á¤Ë¤Ï
             <application>GaTeD</application>(<ulink url="http://www.gated.org/">http://www.gated.org/</ulink>
             ¤«¤éÆþ¼ê²Äǽ) ¤ò»ÈÍѤ¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
             3_5Alpha7 ¤Ë¤ª¤¤¤Æ FreeBSD ¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             Ãí°Õ¤·¤Æ¤Û¤·¤¤¤Î¤Ï¡¢FreeBSD ¤ò¤³¤Î¤è¤¦¤Ë¤·¤Æ»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ç¤â¡¢
             ¥ë¡¼¥¿¤Ë´Ø¤¹¤ë¥¤¥ó¥¿¡¼¥Í¥Ã¥Èɸ½à¤ÎɬÍ×¾ò·ï¤ò´°Á´¤Ë¤ÏËþ¤¿¤·¤Æ¤¤¤Ê¤¤
             ¤È¤¤¤¦¤³¤È¤Ç¤¹¡£¤·¤«¤·¡¢ÉáÄ̤˻ÈÍѤ¹¤ë¾ì¹ç¤Ë¤Ï¤Û¤È¤ó¤ÉÌäÂꤢ¤ê¤Þ¤»¤ó¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="win95-connection">
           <para>Win95 ¤ÎÁö¤Ã¤Æ¤¤¤ë¥Þ¥·¥ó¤ò¡¢FreeBSD ·Ðͳ¤Ç¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤ËÀܳ¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             Ä̾¤³¤Î¼ÁÌ䤬½Ð¤Æ¤¯¤ë¾õ¶·¤Ï¼«Âð¤ËÆóÂæ¤Î PC ¤¬¤¢¤ê¡¢°ìÂæ¤Ç¤Ï
             FreeBSD ¤¬¡¢¤â¤¦°ìÂæ¤Ç¤Ï Win95 ¤¬Áö¤Ã¤Æ¤¤¤ë¤è¤¦¤Ê¾ì¹ç¤Ç¤¹¡£
             ¤³¤³¤Ç¤ä¤í¤¦¤È¤·¤Æ¤¤¤¦»ö¤Ï FreeBSD ¤ÎÁö¤Ã¤Æ¤¤¤ë·×»»µ¡¤ò¥¤¥ó¥¿¡¼¥Í¥Ã¥È
             ¤ËÀܳ¤·¡¢Win95 ¤ÎÁö¤Ã¤Æ¤¤¤ë¥Þ¥·¥ó¤«¤é¤Ï FreeBSD
             ¤ÎÁö¤Ã¤Æ¤¤¤ë¥Þ¥·¥ó¤ò·Ðͳ¤·¤ÆÀܳ¤ò¹Ô¤Ê¤¦»ö¤Ç¤¹¡£
             ¤³¤ì¤ÏÆó¤ÄÁ°¤Î¼ÁÌä¤ÎÆÃÊ̤ʾì¹ç¤ËÁêÅö¤·¤Þ¤¹¡£
           </para>
 
           <para>¡Ä¤Ç¡¢Åú¤¨¤Ï¡Ö¤Ï¤¤¡×¤Ç¤¹¡£
             FreeBSD 3.x ¤Î¥æ¡¼¥¶¥â¡¼¥É ppp ¤Ë¤Ï <option>-nat</option>
             ¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£
             <application>ppp</application> ¤ò <option>-nat</option>
             ¥ª¥×¥·¥ç¥óÉÕ¤­¤Çµ¯Æ°¤·¡¢
             <filename>/etc/rc.conf</filename> ¤Ë¤¢¤ë
             <literal>gateway_enable</literal> ¤ò
             <emphasis>YES</emphasis> ¤ËÀßÄꤷ¤Þ¤¹¡£
             ¤½¤·¤Æ Windows ¥Þ¥·¥ó¤òÀµ¤·¤¯ÀßÄꤹ¤ì¤Ð¡¢
             ¤­¤Á¤ó¤ÈÆ°ºî¤¹¤ë¤Ç¤·¤ç¤¦¡£</para>
 
           <para>
             ÀßÄê¤Ë´Ø¤¹¤ë¤µ¤é¤Ë¾Ü¤·¤¤¾ðÊó¤Ï¡¢
             Steve Sims »á¤Ë¤è¤ë
             <ulink url="http://www.FreeBSD.org/tutorials/ppp/index.html">Pedantic
               PPP Primer</ulink> ¤Ë¤¢¤ê¤Þ¤¹¡£</para>
 
           <para>¥«¡¼¥Í¥ë¥â¡¼¥É ppp ¤òÍøÍѤ¹¤ë¾ì¹ç¤ä¡¢
             ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤È¤Î¥¤¡¼¥µ¥Í¥Ã¥ÈÀܳ¤¬ÍøÍѤǤ­¤ë¾ì¹ç¤Ï¡¢
             <command>natd</command> ¤òÍøÍѤ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤Î FAQ ¤Î <link linkend="natd">natd</link>
             ¤Î¥»¥¯¥·¥ç¥ó¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="latest-bind">
           <para>ISC ¤«¤é¥ê¥ê¡¼¥¹¤µ¤ì¤Æ¤¤¤ë BIND ¤ÎºÇ¿·ÈǤϥ³¥ó¥Ñ¥¤¥ë¤Ç¤­¤Ê¤¤¤ó¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             BIND ¤ÎÇÛÉÛʪ¤È FreeBSD ¤È¤Ç¤Ï
             <filename>cdefs.h</filename>
             ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤ÎÃæ¤Ç¥Ç¡¼¥¿·¿¤ÎÌ·½â¤¬¤¢¤ê¤Þ¤¹¡£
             <filename>compat/include/sys/cdefs.h</filename>
             ¤òºï½ü¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="slip-ppp-support">
           <para>FreeBSD ¤Ç <acronym>SLIP</acronym> ¤È
             <acronym>PPP</acronym> ¤Ï»È¤¨¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             »È¤¨¤Þ¤¹¡£FreeBSD ¤òÍѤ¤¤Æ¾¤Î¥µ¥¤¥È¤ËÀܳ¤¹¤ë¾ì¹ç¤Ë¤Ï¡¢
             &man.slattach.8;¡¢&man.sliplogin.8;¡¢&man.ppp.8; ¤½¤·¤Æ
             &man.pppd.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
             &man.ppp.8; ¤È &man.pppd.8; ¤Ï¡¢
             <acronym>PPP</acronym> ¤Î¥µ¡¼¥Ð¡¢¥¯¥é¥¤¥¢¥ó¥ÈξÊý¤Îµ¡Ç½¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¤½¤Î°ìÊý¤Ç¡¢&man.sliplogin.8; ¤Ï
             <acronym>SLIP</acronym> ¤Î¥µ¡¼¥ÐÀìÍѤǡ¢
             &man.slattach.8; ¤Ï
             <acronym>SLIP</acronym> ¤Î¥¯¥é¥¤¥¢¥ó¥ÈÀìÍѤǤ¹¡£
           </para>
 
           <para>¤³¤ì¤é¤ò»È¤¦¤¿¤á¤Î¤µ¤é¤Ê¤ë¾ðÊó¤Ë¤Ä¤¤¤Æ¤Ï¡¢<ulink
             url="../handbook/ppp-and-slip.html">¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î PPP ¤È
             SLIP ¤Î¾Ï</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
 
           <para>
             ¡Ö¥·¥§¥ë¥¢¥«¥¦¥ó¥È¡×¤òÄ̤¸¤Æ¤Î¤ß¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Ø¥¢¥¯¥»¥¹²Äǽ¤Ê¾ì¹ç¡¢
             <application>slirp</application>
             package ¤ß¤¿¤¤¤Ê¤â¤Î¤¬Íߤ·¤¯¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤Í¡£
             ¤³¤ì¤ò»È¤¨¤Ð¡¢¥í¡¼¥«¥ë¥Þ¥·¥ó¤«¤éľÀÜ <acronym>ftp</acronym>
             ¤ä <acronym>http</acronym>
             ¤Î¤è¤¦¤Ê¥µ¡¼¥Ó¥¹¤Ë (¸ÂÄêŪ¤Ç¤Ï¤¢¤ê¤Þ¤¹¤¬) ¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="natd">
           <para>FreeBSD ¤Ï <acronym>NAT</acronym> ¤«
             <acronym>IP</acronym> ¥Þ¥¹¥«¥ì¡¼¥É¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤«?
           </para>
         </question>
 
         <answer>
           <para>
             ¥í¡¼¥«¥ë¤Ê¥µ¥Ö¥Í¥Ã¥È (°ìÂæ°Ê¾å¤Î¥í¡¼¥«¥ë¥Þ¥·¥ó) ¤ò»ý¤Ã¤Æ¤¤¤ë¤¬¡¢
             ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥×¥í¥Ð¥¤¥À¤«¤é 1 ¤Ä¤·¤« <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤Î³ä¤êÅö¤Æ¤ò¼õ¤±¤Æ¤¤¤Ê¤¤¾ì¹ç (¤Þ¤¿¤Ï <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤òưŪ¤Ë³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤ë¾ì¹ç¤Ç¤â)¡¢
             &man.natd.8;
             ¥×¥í¥°¥é¥à¤ò»È¤¤¤¿¤¯¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤Í¡£
             <literal>natd</literal> ¤ò»È¤¨¤Ð¡¢
             1 ¤Ä¤·¤« <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤ò»ý¤Ã¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ç¤â¡¢
             ¥µ¥Ö¥Í¥Ã¥ÈÁ´ÂΤò¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤ËÀܳ¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             &man.ppp.8;
             ¤âƱÍͤε¡Ç½¤ò»ý¤Ã¤Æ¤ª¤ê¡¢<option>-nat</option>
             ¥¹¥¤¥Ã¥Á¤ÇÍ­¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤É¤Á¤é¤Î¾ì¹ç¤â
             alias ¥é¥¤¥Ö¥é¥ê (&man.libalias.3;) ¤¬»È¤ï¤ì¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="create-dev-net">
           <para><devicename>/dev/ed0</devicename>
             ¥Ç¥Ð¥¤¥¹¤òºîÀ®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>Berkeley UNIX ¤Ë¤ª¤±¤ë¥Í¥Ã¥È¥ï¡¼¥¯¤Î¹½À®¤Ë¤ª¤¤¤Æ¡¢
             ¥Í¥Ã¥È¥ï¡¼¥¯¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ï¥«¡¼¥Í¥ë¥³¡¼¥É¤«¤é¤Î¤ß¡¢
             ľÀܤ¢¤Ä¤«¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤è¤ê¾Ü¤·¤¯ÃΤꤿ¤¤¾ì¹ç¤Ï¡¢
             <filename>/etc/rc.network</filename>
             ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤ä¡¢
             ¤³¤Î¥Õ¥¡¥¤¥ë¤ÎÃæ¤Ë½ñ¤¤¤Æ¤¢¤ë¡¢
             ¤µ¤Þ¤¶¤Þ¤Ê¥×¥í¥°¥é¥à¤Ë¤Ä¤¤¤Æ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤ì¤Ç¤â¤Þ¤Àʬ¤«¤é¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢
             ¾¤Î BSD ·Ï¤Î OS ¤Î¥Í¥Ã¥È¥ï¡¼¥¯´ÉÍý¤Ë¤Ä¤¤¤Æ¤ÎËܤòÆɤà¤Ù¤­¤Ç¤·¤ç¤¦¡£
             ¤´¤¯¾¯¤·¤ÎÎã³°¤ò¤Î¤¾¤¤¤Æ¤Ï¡¢FreeBSD ¤Î¥Í¥Ã¥È¥ï¡¼¥¯´ÉÍý¤Ï SunOS 4.0
             ¤ä Ultrix ¤È´ðËÜŪ¤ËƱ¤¸¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ethernet-aliases">
           <para>Ethernet ¥¢¥É¥ì¥¹¤Î¥¨¥¤¥ê¥¢¥¹ (alias) ¤Ï¤É¤Î¤è¤¦¤Ë¤·¤ÆÀßÄê¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             &man.ifconfig.8;
             ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ë
             <literal>netmask 0xffffffff</literal>
             ¤òÄɲ䷤ơ¢¼¡¤Î¤è¤¦¤Ë½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>ifconfig ed0 alias 204.141.95.2 netmask 0xffffffff</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="port-3c503">
           <para>3C503 ¤Ç¾¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥Ý¡¼¥È¤ò»ÈÍѤ¹¤ë¤Ë¤Ï¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð¤è¤¤¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¾¤Î¥Ý¡¼¥È¤ò»ÈÍѤ·¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢
             &man.ifconfig.8;
             ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ë¥Ñ¥é¥á¡¼¥¿¤òÄɲ䷤ʤ±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï
             <literal>link0</literal>
             ¤¬ÍѤ¤¤é¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             BNC ¤Î¤«¤ï¤ê¤Ë
             AUI ¥Ý¡¼¥È¤ò»ÈÍѤ·¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢
             <literal>link2</literal>
             ¤È¤¤¤¦¥Ñ¥é¥á¡¼¥¿¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
             ¤³¤ì¤é¤Î¥Õ¥é¥°¤Ï¡¢
             <filename>/etc/rc.conf</filename> (&man.rc.conf.5; »²¾È)
             ¤Ë¤¢¤ë ifconfig_*
             ¤ÎÊÑ¿ô¤ò»È¤Ã¤Æ»ØÄꤵ¤ì¤ë¤Ï¤º¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nfs">
           <para>FreeBSD ¤È¤Î´Ö¤Ç NFS ¤¬¤¦¤Þ¤¯¤Ç¤­¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             PC ÍѤΥͥåȥ¥¯¥«¡¼¥É¤Ë¤è¤Ã¤Æ¤Ï¡¢
             NFS ¤Î¤è¤¦¤Ê¡¢
             ¥Í¥Ã¥È¥ï¡¼¥¯¤ò¹ó»È¤¹¤ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ë¤ª¤¤¤ÆÌäÂê¤òµ¯¤³¤¹¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ÎÅÀ¤Ë´Ø¤·¤Æ¤Ï
             <ulink url="../handbook/nfs.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡ÖNFS¡×</ulink>¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nfs-linux">
           <para>²¿¸Î Linux ¤Î¥Ç¥£¥¹¥¯¤ò NFS
             ¥Þ¥¦¥ó¥È¤Ç¤­¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             Linux ¤Î NFS
             ¤Î¥³¡¼¥É¤Ë¤Ï¡¢
             µö²Ä¤µ¤ì¤¿¥Ý¡¼¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤·¤«¼õ¤±¤Ä¤±¤Ê¤¤¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
             °Ê²¼¤ò»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
            <screen>&prompt.root; <userinput>mount -o -P linuxbox:/blah /mnt</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nfs-sun">
           <para>²¿¸Î Sun ¤Î¥Ç¥£¥¹¥¯¤ò NFS
             ¥Þ¥¦¥ó¥È¤Ç¤­¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             SunOS 4.X ¤¬Áö¤Ã¤Æ¤¤¤ë Sun Workstation ¤Ï¡¢
             µö²Ä¤µ¤ì¤¿¥Ý¡¼¥È¤«¤é¤Î¥Þ¥¦¥ó¥ÈÍ׵ᤷ¤«¼õ¤±¤Ä¤±¤Þ¤»¤ó¡£
             °Ê²¼¤ò»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>mount -o -P sunbox:/blah /mnt</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="exports-errors">
           <para><command>mountd</command> ¤«¤é
             <quote>can't change attributes</quote>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬¤º¤Ã¤È½Ð³¤±¤Æ¤¤¤Æ¡¢
             FreeBSD ¤Î NFS ¥µ¡¼¥Ð¤Ç¤Ï
             <quote>bad exports list</quote>
             ¤Èɽ¼¨¤µ¤ì¤Þ¤¹¡£¤³¤ì¤Ï²¿¤¬¸¶°ø¤Ê¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>ºÇ¤âÎɤ¯¤¢¤ëÌäÂê¤Ï¡¢&man.exports.5;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î°Ê²¼¤ÎÉôʬ¤òÀµ¤·¤¯Íý²ò¤·¤Æ¤¤¤Ê¤¤¤³¤È¤Ç¤¹¡£</para>
 
           <blockquote>
             <para>¤³¤Î¥Õ¥¡¥¤¥ë¤Î³Æ¹Ô (# ¤Ç¤Ï¤¸¤Þ¤ë¥³¥á¥ó¥È¹Ô¤ò½ü¤¯) ¤Ï¡¢
               NFS ¥µ¡¼¥Ð¤Î¥í¡¼¥«¥ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¸ºß¤¹¤ë¡¢
               ¾¤Î¥Û¥¹¥È¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤ë¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È (Ê£¿ô²Ä) ¤È¡¢
               ¤½¤ì¤ËÂФ¹¤ë¥¨¥¯¥¹¥Ý¡¼¥È¥Õ¥é¥°¤ò»ØÄꤷ¤Þ¤¹¡£
               ÆÃÄê¤Î¥¨¥¯¥¹¥Ý¡¼¥ÈÀè¥Û¥¹¥È¤ª¤è¤Ó¡¢
               ¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤ËŬÍѤµ¤ì¤ë¥Ç¥Õ¥©¥ë¥È¥¨¥ó¥È¥ê¤ÏξÊý¤È¤â¡¢
               ¥µ¡¼¥Ð¤Î³Æ¥í¡¼¥«¥ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ·¤Æ°ì²ó¤À¤±¤·¤«»ØÄê¤Ç¤­¤Þ¤»¤ó¡£</para>
           </blockquote>
 
           <para>¤µ¤Æ¡¢¤¢¤ê¤¬¤Á¤Ê´Ö°ã¤¤¤ò¤´Í÷¤Ë¤Ê¤ì¤Ð¤Ï¤Ã¤­¤ê¤¹¤ë¤Ç¤·¤ç¤¦¡£
             ¤â¤· <filename>/usr</filename>
             °Ê²¼¤¬Ã±°ì¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤¢¤ë (¤Ä¤Þ¤ê
             <filename>/usr</filename> ¤Ë²¿¤â¥Þ¥¦¥ó¥È¤µ¤ì¤Ê¤¤) ¾ì¹ç¡¢
             ¼¡¤Î exports ¥ê¥¹¥È¤ÏÀµ¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£</para>
 
           <programlisting>/usr/src   client
 /usr/ports client</programlisting>
 
           <para>°ì¤Ä¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ·¤Æ°À­¤Î»ØÄ꤬Æó¹Ô¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             <filename>/usr</filename> ¤ÏƱ¤¸¥Û¥¹¥È
             <hostid>client</hostid> ¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤Þ¤¹¤«¤é¡¢
             Àµ¤·¤¤½ñ¤­Êý¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
 
           <programlisting>/usr/src /usr/ports  client</programlisting>
 
           <para>¤â¤¦°ìÅ٥ޥ˥奢¥ë¥Ú¡¼¥¸¤Îʸ¾Ï¤ò³Îǧ¤¹¤ë¤È¡¢
             ¤¢¤ë¥Û¥¹¥È¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤ë³Æ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°À­¤Ï
             ¤¹¤Ù¤Æ°ì¹Ô¤Ë½ñ¤«¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡¢¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹
             (¤³¤³¤Ç¤Ï¡¢¡Ö¥¢¥¯¥»¥¹²Äǽ¤Ê¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¡×
             ¤â°ì¤Ä¤ÎÆÈΩ¤·¤¿¥Û¥¹¥È¤È¤·¤Æ°·¤ï¤ì¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤)¡£
             ¤³¤Î¤³¤È¤Ï¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤ë¤¿¤á¤Ë
             ´ñ̯¤Ê½ñ¼°¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¸¶°ø¤Ë¤â¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢
             ¤Û¤È¤ó¤É¤Î¿Í¤Ë¤È¤Ã¤Æ¡¢¤³¤ì¤ÏÌäÂê¤Ë¤Ï¤Ê¤é¤Ê¤¤¤Ç¤·¤ç¤¦¡£</para>
 
           <para>¼¡¤Ë¼¨¤¹¤Î¤Ï¡¢Í­¸ú¤Ê exports ¥ê¥¹¥È¤ÎÎã¤Ç¤¹¡£
             ¤³¤³¤Ç¤Ï¡¢<filename>/usr</filename> ¤È
             <filename>/exports</filename>
             ¤¬¥í¡¼¥«¥ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤¹¡£</para>
 
           <programlisting># Export src and ports to client01 and client02, but only
 # client01 has root privileges on it
 /usr/src /usr/ports -maproot=0    client01
 /usr/src /usr/ports               client02
 # The "client" machines have root and can mount anywhere
 # up /exports. The world can mount /exports/obj read-only
 /exports -alldirs -maproot=0      client01 client02
 /exports/obj -ro</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-nextstep">
           <para>PPP ¤Ç NeXTStep
             ¤ËÀܳ¤¹¤ëºÝ¤ËÌäÂ꤬¤¢¤ë¤Î¤Ç¤¹¤¬¡£
           </para>
         </question>
 
         <answer>
           <para>
             <filename>/etc/rc.conf</filename> (&man.rc.conf.5; »²¾È)
             ¤ÎÃæ¤Ç¼¡¤ÎÊÑ¿ô¤ò NO ¤Ë¤·¤Æ¡¢
             TCP extension ¤ò̵¸ú¤Ë¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>tcp_extensions=NO</programlisting>
 
           <para>
             Xylogic ¤Î Annex ¤âƱÍͤÎÌäÂ꤬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢
             Annex ·Ðͳ¤Ç PPP
             ¤ò¹Ô¤Ê¤¦¾ì¹ç¤Ë¤â¤³¤ÎÊѹ¹¤ò¹Ô¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ip-multicast">
           <para>IP
             ¥Þ¥ë¥Á¥­¥ã¥¹¥È (multicast) ¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD 2.0 ¤«¤½¤ì°Ê¹ß¤Ç¤Ï¡¢
             ɸ½à¤Î¾õÂ֤Ǵ°Á´¤Ë¥Þ¥ë¥Á¥­¥ã¥¹¥È¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£
             ¸½ºß»ÈÍѤ·¤Æ¤¤¤ë·×»»µ¡¤ò¥Þ¥ë¥Á¥­¥ã¥¹¥È¤Î¥ë¡¼¥¿ (router) ¤È¤·¤Æ»ÈÍѤ¹¤ë¤Ë¤Ï¡¢
             <literal>MROUTING</literal>
             ¤È¤¤¤¦¥ª¥×¥·¥ç¥ó¤òÄêµÁ¤·¤¿¥«¡¼¥Í¥ë¤òºî¤Ã¤¿¤¦¤¨¤Ç¡¢
             <command>mrouted</command>
             ¤òÁö¤é¤»¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£2.2 ¤«¤½¤ì°Ê¹ß¤Î FreeBSD ¤Ê¤é¤Ð¡¢
             <filename>/etc/rc.conf</filename>
             ¤Ç¥Õ¥é¥°
             <literal>mrouted_enable</literal> ¤ò
             <literal>YES</literal> ¤Ë¥»¥Ã¥È¤·¤Æ¤ª¤¯¤³¤È¤Ç¡¢
             µ¯Æ°»þ¤Ë <command>mrouted</command>
             ¤òµ¯Æ°¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             MBONE
             ÍѤΥġ¼¥ë¤Ï ports Æâ¤ÎÀìÍѤΥ«¥Æ¥´¥ê¡¼ mbone
             ¤Ë¤¢¤ê¤Þ¤¹¡£
             <command>vic</command> ¤ä
             <command>vat</command>
             ¤È¤¤¤Ã¤¿²ñµÄÍѤΥġ¼¥ë¤òõ¤·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
             ¤³¤Î¾ì½ê¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¾Ü¤·¤¤¾ðÊó¤Ï
             <ulink url="http://www.mbone.com/">Mbone Information Web</ulink>
             ¤Ë¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dec-pci-chipset">
           <para>
             DEC
             ¤Î PCI ¥Á¥Ã¥×¥»¥Ã¥È¤òÍѤ¤¤Æ¤¤¤ë¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤Ë¤Ï¡¢
             ¤É¤Î¤è¤¦¤Êʪ¤¬¤¢¤ê¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             <ulink url="mailto:gfoster@driver.nsta.org">Glen Foster
               »á</ulink>¤Ë¤è¤ë°ìÍ÷¤Ë¡¢
             ºÇ¶á¤ÎÀ½ÉʤòÄɲä·¤¿¤â¤Î¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹¡£
           </para>
 
           <programlisting>Vendor          Model
 ----------------------------------------------
 ASUS            PCI-L101-TB
 Accton          ENI1203
 Cogent          EM960PCI
 Compex          ENET32-PCI
 D-Link          DE-530
 Dayna           DP1203, DP2100
 DEC             DE435, DE450
 Danpex          EN-9400P3
 JCIS            Condor JC1260
 Linksys         EtherPCI
 Mylex           LNP101
 SMC             EtherPower 10/100 (Model 9332)
 SMC             EtherPower (Model 8432)
 TopWare         TE-3500P
 Znyx            (2.2.X) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
                 (3.X) ZX345Q, ZX346Q, ZX348Q, ZX412Q, ZX414, ZX442,
                       ZX444, ZX474, ZX478, ZX212, ZX214 (10mbps/hd)</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="fqdn-hosts">
           <para>
             ²¿¸Î¼«Ê¬¤Î¥µ¥¤¥È¤Î¥Û¥¹¥È¤ËÂФ·¤Æ FQDN
             ¤ò»ÈÍѤ¹¤ëɬÍפ¬¤¢¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¼ÂºÝ¤Ë¤Ï¤½¤Î¥Û¥¹¥È¤ÏÊ̤Υɥᥤ¥ó¤Ë¤¢¤ë¤Î¤Ç¤Ï¤Ê¤¤¤Ç¤¹¤«¡£
             ¤¿¤È¤¨¤Ð¡¢foo.bar.edu
             ¤È¤¤¤¦¥É¥á¥¤¥ó¤ÎÃ椫¤é¡¢
             <hostid role="domainname">bar.edu</hostid> ¥É¥á¥¤¥ó¤Ë¤¢¤ë
             <hostid>mumble</hostid>
             ¤È¤¤¤¦¥Û¥¹¥È¤ò»ØÄꤷ¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢
             <hostid>mumble</hostid>
             ¤À¤±¤Ç¤Ï¥À¥á¤Ç¡¢
             <hostid role="domainname">mumble.bar.edu</hostid>
             ¤È¤¤¤¦ FQDN (fully-qualified domain name)
             ¤Ç»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ÅÁÅýŪ¤Ë¡¢BSD ¤Î
             BIND ¤Î¥ê¥¾¥ë¥Ð (resolver) ¤Ç¤Ï¤³¤Î¤è¤¦¤Ê»ö¤Ï²Äǽ¤Ç¤·¤¿¤¬¡¢
             FreeBSD ¤ËÆþ¤Ã¤Æ¤¤¤ë
             <application>bind</application> (&man.named.8; »²¾È)
             ¤Î¸½ºß¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
             ¼«Ê¬°Ê³°¤Î¥É¥á¥¤¥ó¤ËÂФ·¤Æ FQDN
             ¤Ç¤Ê¤¤ÊÌ̾¤ò¼«Æ°Åª¤Ë¤Ä¤±¤Æ¤¯¤ì¤ë¤è¤¦¤Ê»ö¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¤·¤¿¤¬¤Ã¤Æ <hostid>mumble</hostid> ¤È¤¤¤¦¥Û¥¹¥È̾¤Ï¡¢
             <hostid role="fqdn">mumble.foo.bar.edu</hostid>
             ¤È¤¤¤¦Ì¾Á°¤«¡¢¤â¤·¤¯¤Ï root
             ¥É¥á¥¤¥óÆâ¤Ë¤¢¤ë¾ì¹ç¤Ë¤·¤«Å¬ÍѤµ¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤³¤ì¤Ï¡¢
             <hostid role="fqdn">mumble.bar.edu</hostid> ¤È
             <hostid role="domainname">mumble.edu</hostid>
             ¤È¤¤¤¦¤³¤È¤Ê¤Ã¤¿¥É¥á¥¤¥ó̾¤ËÂФ·¤Æ¥Û¥¹¥È̾¤Î¥µ¡¼¥Á¤¬¹Ô¤Ê¤ï¤ì¤Æ¤¤¤¿
             °ÊÁ°¤Î¿¶¤ëÉñ¤¤¤È¤Ï°Û¤Ê¤Ã¤¿¤â¤Î¤Ç¤¹¡£¤³¤Î¤è¤¦¤Ê»ö¤¬°­¤¤Îã¤â¤·¤¯¤Ï
             ¥»¥­¥å¥ê¥Æ¥£¥Û¡¼¥ë¤È¤ß¤Ê¤µ¤ì¤ëÍýͳ¤Ë¤Ä¤¤¤Æ¤Ï
             RFC 1535 ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             <filename>/etc/resolv.conf</filename> ¥Õ¥¡¥¤¥ë
             (&man.resolv.conf.5; »²¾È)
             ¤ÎÃæ¤Ç
           </para>
 
             <programlisting>domain foo.bar.edu</programlisting>
 
           <para>
             ¤È½ñ¤¤¤Æ¤¢¤ë¹Ô¤ò¡¢
 
             <hostid>search foo.bar.edu bar.edu</hostid>
 
             ¤Î¤è¤¦¤Ë½ñ¤­¤«¤¨¤ë¤³¤È¤Ç¡¢¾å¤Î¤è¤¦¤Ê»ö¤¬¤Ç¤­¤Þ¤¹¡£¤·¤«¤·¡¢
             RFC 1535 ¤Ë¤¢¤ë¤è¤¦¤Ë¡¢
             ¸¡º÷½ç½ø¤¬¡ÖÆâÉô (local) ¤È³°Éô (public) ¤Î´ÉÍý¤Î¶­³¦¡×¤ò¤Þ¤¿¤¬¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="network-permission-denied">
           <para>¤¹¤Ù¤Æ¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤ÎÁàºî¤ËÂФ·¤Æ
             <literal>Permission denied</literal>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬É½¼¨¤µ¤ì¤ë¤Î¤Ç¤¹¤¬¡£</para>
         </question>
 
         <answer>
           <para>
             <literal>IPFIREWALL</literal>
             ¥ª¥×¥·¥ç¥ó¤òÉÕ¤±¤Æ¥«¡¼¥Í¥ë¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤¿¾ì¹ç¤Ë¤Ï¡¢
             2.1-STABLE ¤Î³«È¯¤ÎÅÓÃ椫¤éÊѹ¹¤Ë¤Ê¤Ã¤¿ 2.1.7R ¤Îɸ½àŪ¤ÊÊý¿Ë¤È¤·¤Æ¡¢
             ÌÀ¼¨Åª¤Ëµö²Ä¤µ¤ì¤Æ¤¤¤Ê¤¤¤¹¤Ù¤Æ¤Î¥Ñ¥±¥Ã¥È¤ÏÍî¤È¤µ¤ì¤ëÀßÄê
             ¤Ë¤Ê¤Ã¤Æ¤¤¤ë»ö¤ò³Ð¤¨¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤â¤·¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤ÎÀßÄê¤ò´Ö°ã¤¨¤¿¾ì¹ç¤Ë¥Í¥Ã¥È¥ï¡¼¥¯¤ÎÁàºî¤¬ºÆ¤Ó¤Ç¤­¤ë
             ¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢<username>root</username>
             ¤Ç¥í¥°¥¤¥ó¤·¤Æ¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
          <screen>&prompt.root; <userinput>ipfw add 65534 allow all from any to any</userinput></screen>
 
           <para>
             <filename>/etc/rc.conf</filename> ¤Ë
             <literal>firewall_type='open'</literal>
             ¤òÄɲ䷤Ƥâ¤è¤¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             FreeBSD ¤Î¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤ÎÀßÄê¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤Ï
             <ulink url="../handbook/firewalls.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡Ö¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¡×</ulink>¤Ë¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ipfw-overhead">
           <para>IPFW ¤Î¥ª¡¼¥Ð¥Ø¥Ã¥É¤Ï¤É¤Î¤¯¤é¤¤¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ÎÅú¤¨¤Ï¡¢
             »È¤Ã¤Æ¤¤¤ë¥ë¡¼¥ë¥»¥Ã¥È¤È¥×¥í¥»¥Ã¥µ¤Î¥¹¥Ô¡¼¥É¤Ë¤è¤Ã¤Æ¤Û¤È¤ó¤É·è¤Þ¤ê¤Þ¤¹¡£
             ¥¤¡¼¥µ¥Í¥Ã¥È¤ËÂФ·¤Æ¾¯¤·¤Î¥ë¡¼¥ë¥»¥Ã¥È¤À¤±¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
             ¤Û¤È¤ó¤É¤½¤Î±Æ¶Á¤Ï̵»ë¤Ç¤­¤ëÄøÅ٤Ǥ¹¡£
             ¼ÂºÝ¤Î¬ÄêÃͤò¸«¤Ê¤¤¤ÈËþ­¤Ç¤­¤Ê¤¤Êý¡¹¤Î¤¿¤á¤Ë¡¢
             ¼ÂºÝ¤Î¬Äê·ë²Ì¤ò¤ª¸«¤»¤·¤Þ¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¼¡¤Î¬Äê¤Ï 486-66 (ÌõÃí: Intel ¼ÒÀ½ CPU i486¡¢66MHz ¤Î¤³¤È) ¾å¤Ç
             2.2.5-STABLE ¤ò»ÈÍѤ·¤Æ¹Ô¤Ê¤ï¤ì¤Þ¤·¤¿¡£
             IPFW ¤ÏÊѹ¹¤¬²Ã¤¨¤é¤ì¤Æ¡¢<literal>ip_fw_chk</literal>
             ¥ë¡¼¥Á¥óÆâ¤Ç¤«¤«¤ë»þ´Ö¤ò
             ¬Äꤷ¤Æ 1000
             ¥Ñ¥±¥Ã¥ÈËè¤Ë·ë²Ì¤ò¥³¥ó¥½¡¼¥ë¤Ëɽ¼¨¤¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¤½¤ì¤¾¤ì 1000 ¤º¤Ä¤Î¥ë¡¼¥ë¤¬Æþ¤Ã¤Æ¤¤¤ë 2
             ¤Ä¤Î¥ë¡¼¥ë¥»¥Ã¥È¤Ç¥Æ¥¹¥È¤¬¹Ô¤Ê¤ï¤ì¤Þ¤·¤¿¡£
             ¤Ò¤È¤ÄÌܤΥ롼¥ë¥»¥Ã¥È¤ÏºÇ°­¤Î¥±¡¼¥¹¤ò¸«¤ë¤¿¤á¤Ë
           </para>
 
             <programlisting>ipfw add deny tcp from any to any 55555</programlisting>
 
           <para>
             ¤È¤¤¤¦¥ë¡¼¥ë¤ò·«¤êÊÖ¤·¤¿¤â¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             IPFW ¤Î¥Ñ¥±¥Ã¥È¥Á¥§¥Ã¥¯¥ë¡¼¥Á¥ó¤Ï¡¢
             ¥Ñ¥±¥Ã¥È¤¬ (¥Ý¡¼¥ÈÈÖ¹æ¤Î¤»¤¤¤Ç) ¤³¤Î¥ë¡¼¥ë¤Ë¥Þ¥Ã¥Á¤·¤Ê¤¤¤³¤È¤¬¤ï¤«¤ë¤Þ¤Ç¤Ë¡¢
             ²¿ÅÙ¤â¼Â¹Ô¤µ¤ì¤Þ¤¹¡£¤½¤Î¤¿¤á¡¢¤³¤ì¤ÏºÇ°­¤Î¥±¡¼¥¹¤ò¼¨¤·¤Þ¤¹¡£
             ¤³¤Î¥ë¡¼¥ë¤ò 999 ¸Ä·«¤êÊÖ¤·Ê¤٤¿¸å¤Ë
           </para>
 
             <programlisting>allow ip from any to any</programlisting>
 
           <para>
             ¤¬½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             2¤ÄÌܤΥ롼¥ë¥»¥Ã¥È¤Ï¡¢¤Ê¤ë¤Ù¤¯Á᤯¥Á¥§¥Ã¥¯¤¬½ªÎ»¤¹¤ë¤è¤¦¤Ë½ñ¤«¤ì¤¿¤â¤Î¤Ç¤¹¡£
           </para>
 
             <programlisting>ipfw add deny ip from 1.2.3.4 to 1.2.3.4</programlisting>
 
           <para>
             ¤³¤Î¥ë¡¼¥ë¤Ç¤Ï¡¢È¯¿®¸µ¤Î IP ¥¢¥É¥ì¥¹¤¬¥Þ¥Ã¥Á¤·¤Ê¤¤¤Î¤Ç¡¢
             ¥Á¥§¥Ã¥¯¤Ï¤¹¤°¤Ë½ªÎ»¤·¤Þ¤¹¡£¾å¤Î¥ë¡¼¥ë¥»¥Ã¥È¤È¤ª¤Ê¤¸¤è¤¦¤Ë¡¢
             1000 ¸ÄÌܤΥ롼¥ë¤Ï
           </para>
 
             <programlisting>allow ip from any to any</programlisting>
 
           <para>
             ¤Ç¤¹¡£
           </para>
 
           <para>
             1 ¤ÄÌܤΥ롼¥ë¥»¥Ã¥È¤Î¾ì¹ç¡¢
             ¥Ñ¥±¥Ã¥È¤¢¤¿¤ê¤Î¥ª¡¼¥Ð¥Ø¥Ã¥É¤Ï¤ª¤è¤½
             2.703ms/packet¡¢
             ¤³¤ì¤Ï¤À¤¤¤¿¤¤ 1 ¤Ä¤Î¥ë¡¼¥ë¤¢¤¿¤ê 2.7
             ¥Þ¥¤¥¯¥íÉ䫤«¤Ã¤Æ¤¤¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¤·¤¿¤¬¤Ã¤Æ¡¢
             ¤³¤Î¥ë¡¼¥ë¤Ë¤ª¤±¤ë¥Ñ¥±¥Ã¥È½èÍý»þ´Ö¤ÎÍýÏÀŪ¤Ê¸Â³¦¤Ï¡¢
             ËèÉÃÌó 370 ¥Ñ¥±¥Ã¥È¤Ç¤¹¡£
             10Mbps ¤Î¥¤¡¼¥µ¥Í¥Ã¥È¤Ç 1500 ¥Ð¥¤¥È°Ê²¼¤Î¥Ñ¥±¥Ã¥È¥µ¥¤¥º¤ò²¾Äꤹ¤ë¤È¡¢
             ¥Ð¥ó¥ÉÉý¤ÎÍøÍѸúΨ¤Ï 55.5% ¤¬¸Â³¦¤È¤Ê¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             2 ¤ÄÌܤΥ롼¥ë¥»¥Ã¥È¤Ç¤Ï¡¢¤½¤ì¤¾¤ì¤Î¥Ñ¥±¥Ã¥È¤¬¤ª¤è¤½
             1.172ms¤Ç½èÍý¤µ¤ì¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢
             ¤À¤¤¤¿¤¤ 1 ¤Ä¤Î¥ë¡¼¥ë¤¢¤¿¤ê 1.2
             ¥Þ¥¤¥¯¥íÉ䫤«¤Ã¤Æ¤¤¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¥Ñ¥±¥Ã¥È½èÍý»þ´Ö¤ÎÍýÏÀŪ¤Ê¸Â³¦¤Ï¡¢
             ËèÉÃÌó 853 ¥Ñ¥±¥Ã¥È¤È¤Ê¤ê¤Þ¤¹¤Î¤Ç¡¢
             10Mbps Ethernet ¤Î¥Ð¥ó¥ÉÉý¤ò»È¤¤Àڤ뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤Î¥Æ¥¹¥È¤Ç¤Î¥ë¡¼¥ë¿ô¤Ï¿²á¤®¤ë¤¿¤á¡¢
             ¼ÂºÝ¤Ë»ÈÍѤ¹¤ëºÝ¤Î·ë²Ì¤òÈ¿±Ç¤·¤Æ¤¤¤ëÌõ¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¤³¤ì¤é¤Ï¾å¤Ë¼¨¤·¤¿¿ôÃͤò½Ð¤¹¤¿¤á¤À¤±¤ËÍѤ¤¤é¤ì¤¿¤â¤Î¤Ç¤¹¡£
             ¸úΨ¤ÎÎɤ¤¥ë¡¼¥ë¥»¥Ã¥È¤òºî¤ë¤¿¤á¤Ë¤Ï¡¢
             ¼¡¤Î¤è¤¦¤Ê»ö¤ò¹Í¤¨¤Æ¤ª¤±¤Ð¤è¤¤¤Ç¤·¤ç¤¦¡£
           </para>
 
             <itemizedlist>
               <listitem>
                 <para>
                   ¡Ö³ÎÄꤷ¤Æ¤¤¤ë¡×¥ë¡¼¥ë¤ÏÀèƬ¤ÎÊý¤Ë»ý¤Ã¤Æ¤­¤Æ¤¯¤À¤µ¤¤¡£
                   ¤³¤ì¤Ï¡¢Â¿¿ô¤Î TCP ¤Î¥È¥é¥Õ¥£¥Ã¥¯¤¬¤³¤Î¥ë¡¼¥ë¤Ç½èÍý¤µ¤ì¤ë¤¿¤á¤Ç¤¹¡£
                   ¤½¤·¤Æ¤³¤Î¥ë¡¼¥ë¤ÎÁ°¤Ë¤Ï
                   <literal>allow tcp</literal>
                   ¤È¤¤¤¦µ­½Ò¤òÃÖ¤«¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   Îɤ¯»È¤ï¤ì¤ë¥ë¡¼¥ë¤ò¡¢¤¢¤Þ¤êÎɤ¯»È¤ï¤ì¤Ê¤¤¥ë¡¼¥ë¤è¤ê¤â
                   Á°¤ÎÊý¤Ë (¤â¤Á¤í¤ó<emphasis>¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Îµö²ÄÀßÄê¤òÊѤ¨¤Ê¤¤ÈϰϤÇ</emphasis>)
                   »ý¤Ã¤Æ¤­¤Æ¤¯¤À¤µ¤¤¡£
                   <command>ipfw -a l</command> ¤Î¤è¤¦¤·¤Æ¥Ñ¥±¥Ã¥È¿ô¤ÎÅý·×¤ò¼è¤ë¤³¤È¤Ç¡¢
                   ¤É¤Î¥ë¡¼¥ë¤¬ºÇ¤â¤è¤¯»È¤ï¤ì¤Æ¤¤¤ë¤«¤òÄ´¤Ù¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
                 </para>
               </listitem>
             </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ipfw-fwd">
           <para>&man.ipfw.8; <quote>fwd</quote>
             ¥ë¡¼¥ë¤ò»È¤Ã¤Æ¾¤Î¥Þ¥·¥ó¤Ë¥µ¡¼¥Ó¥¹¤ò¥ê¥À¥¤¥ì¥¯¥È¤·¤¿¤Î¤Ç¤¹¤¬¡¢
             ¤¦¤Þ¤¯Æ°¤¤¤Æ¤¯¤ì¤Ê¤¤¤è¤¦¤Ç¤¹¡£¤É¤¦¤·¤Æ¤Ê¤ó¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>¤ª¤½¤é¤¯¡¢¤¢¤Ê¤¿¤¬´üÂÔ¤·¤Æ¤¤¤ëÆ°ºî¤È¤Ï¡¢
             ñ¤Ê¤ë¥Ñ¥±¥Ã¥ÈžÁ÷¤Ç¤Ï¤Ê¤¯¥Í¥Ã¥È¥ï¡¼¥¯¥¢¥É¥ì¥¹ÊÑ´¹ (NAT)
             ¤È¸Æ¤Ð¤ì¤ë¤â¤Î¤À¤«¤é¤Ç¤·¤ç¤¦¡£
             <quote>fwd</quote> ¥ë¡¼¥ë¤Ïʸ»ú¤É¤ª¤ê¡¢ËÜÅö¤ËžÁ÷¤·¤«¹Ô¤Ê¤¤¤Þ¤»¤ó¡£
             ¥Ñ¥±¥Ã¥È¤ÎÃæ¿È¤Ë¤Ä¤¤¤Æ¤Ï°ìÀÚ¼ê¤ò²Ã¤¨¤Ê¤¤¤Î¤Ç¤¹¡£
             ¤½¤Î¤¿¤á¡¢¼¡¤Î¤è¤¦¤Ê¥ë¡¼¥ë¤òÀßÄꤷ¤¿¤È¤¹¤ë¤È¡¢
           </para>
 
           <screen>01000 fwd <replaceable>10.0.0.1</replaceable> from any to <replaceable>foo 21</replaceable></screen>
 
           <para>°¸À襢¥É¥ì¥¹¤Ë <replaceable>foo</replaceable> ¤È½ñ¤«¤ì¤¿¥Ñ¥±¥Ã¥È¤¬
             ¤³¤Î¥ë¡¼¥ë¤òÀßÄꤷ¤¿¥Þ¥·¥ó¤ËÅþÃ夷¤¿¾ì¹ç¡¢¤½¤Î¥Ñ¥±¥Ã¥È¤Ï
             <replaceable>10.0.0.1</replaceable> ¤ËžÁ÷¤µ¤ì¤Þ¤¹¤¬¡¢°¸À襢¥É¥ì¥¹¤Ï
             <replaceable>foo</replaceable> ¤Î¤Þ¤Þ¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¤Ä¤Þ¤ê¡¢¥Ñ¥±¥Ã¥È¤Ë°¸À襢¥É¥ì¥¹¤¬ <replaceable>10.0.0.1</replaceable>
             ¤Ë½ñ¤­´¹¤¨¤é¤ì¤ë¤È¤¤¤¦¤³¤È¤Ï<emphasis>¤¢¤ê¤Þ¤»¤ó</emphasis>¡£
             ¼«Ê¬°¸¤Ç¤Ê¤¤¥Ñ¥±¥Ã¥È¤ò¼õ¤±¤È¤Ã¤¿¥Þ¥·¥ó¤Ï¡¢
             ¤ª¤½¤é¤¯¤Û¤È¤ó¤É¤Î¾ì¹ç¡¢¤½¤Î¥Ñ¥±¥Ã¥È¤òÇË´þ¤¹¤ë¤È»×¤¤¤Þ¤¹¡£
             ¤½¤Î¤¿¤á <quote>fwd</quote> ¥ë¡¼¥ë¤Ï¡¢
             ¤½¤Î¥ë¡¼¥ë¤ò½ñ¤¤¤¿¥æ¡¼¥¶¤¬°Õ¿Þ¤·¤¿¤è¤¦¤Ë¤ÏÆ°¤«¤Ê¤¤¤³¤È¤¬Îɤ¯¤¢¤ê¤Þ¤¹¡£
             ¤³¤ÎÆ°ºî¤Ï¥Ð¥°¤Ç¤Ï¤Ê¤¯¡¢»ÅÍͤʤΤǤ¹¡£</para>
 
           <para>¥µ¡¼¥Ó¥¹¤ÎžÁ÷¤ò¤­¤Á¤ó¤ÈÆ°ºî¤µ¤»¤ëÊýË¡¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             <link linkend="service-redirect">¥µ¡¼¥Ó¥¹¤Î¥ê¥À¥¤¥ì¥¯¥È¤Ë´Ø¤¹¤ë
               FAQ</link> ¤ä &man.natd.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¡¢
             <ulink url="../ports/">Ports Collection</ulink>
             ¤Ë¤¤¤¯¤Ä¤«´Þ¤Þ¤ì¤Æ¤¤¤ë¥Ý¡¼¥ÈžÁ÷¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ê¤É¤ò¤´Í÷¤Ë¤Ê¤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="service-redirect">
           <para>¥µ¡¼¥Ó¥¹Í×µá¤ò¾¤Î¥Þ¥·¥ó¤Ë¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             FTP ¤Ê¤É¤Î¥µ¡¼¥Ó¥¹¤Î¥ê¥¯¥¨¥¹¥È¤Ï¡¢<quote>socket</quote>
             ¥Ñ¥Ã¥±¡¼¥¸¤òÍøÍѤ·¤Æ¥ê¥À¥¤¥ì¥¯¥È¤Ç¤­¤Þ¤¹¡£
             <quote>socket</quote>
             ¥Ñ¥Ã¥±¡¼¥¸¤Ï ports ¤Î
             <filename>sysutils</filename>
             ¥«¥Æ¥´¥ê¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
             (<filename>/etc/inet.conf</filename>¤Ë½ñ¤«¤ì¤Æ¤¤¤ë)
             ¥³¥Þ¥ó¥É¹Ô¤ò¡¢¼¡¤Î¤è¤¦¤Ë <quote>socket</quote> ¤ò¸Æ¤Ö¤è¤¦¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
         </para>
 
           <programlisting>ftp stream tcp nowait nobody /usr/local/bin/socket socket ftp.foo.com ftp</programlisting>
 
           <para>
             ¤³¤³¤Ç
             <replaceable>ftp.foo.com</replaceable>
             ¤Ï¥ê¥À¥¤¥ì¥¯¥ÈÀè¤Î¥Û¥¹¥È̾¡¢
             ¹Ô¤ÎºÇ¸å¤Î
             <replaceable>ftp</replaceable> ¤Ï¥Ý¡¼¥È̾¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bandwidth-mgr-tool">
           <para>¥Ð¥ó¥ÉÉý¤Î´ÉÍý¤ò¹Ô¤Ê¤¨¤ë¥Ä¡¼¥ë¤Ï¤É¤³¤Ç¼ê¤ËÆþ¤ì¤é¤ì¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ÍѤΥХó¥ÉÉý´ÉÍý¥Ä¡¼¥ë¤Ë¤Ï¡¢ÌµÎÁ¤Ç¼ê¤ËÆþ¤ì¤é¤ì¤ë
             <ulink url="http://www.csl.sony.co.jp/person/kjc/programs.html">ALTQ</ulink> ¤È¡¢
             <ulink url="http://www.etinc.com/">Emerging Technologies</ulink>
             ¤«¤éÆþ¼ê¤Ç¤­¤ë Bandwidth Manager
             ¤È¤¤¤¦»ÔÈΤΤâ¤Î¤Î 2 ¼ïÎब¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="extra-named-port">
 	  <para>BIND (<command>named</command>) ¤¬¡¢53 È֥ݡ¼¥È¤Î¤Û¤«¤Ë
 	    Â礭¤ÊÈÖ¹æ¤Î¥Ý¡¼¥È¤Ç¼õ¤±ÉÕ¤±¤Æ¤¤¤Þ¤¹¡£»ä¤Î¥Û¥¹¥È¤Ï
 	    ¾è¤Ã¼è¤é¤ì¤¿¤Î¤Ç¤·¤ç¤¦¤«¡£</para>
 	</question>
 
 	<answer>
 	  <para>¤ª¤½¤é¤¯°ã¤¤¤Þ¤¹¡£FreeBSD 3.0 °Ê¹ß¤Ç¤Ï¡¢³°¸þ¤±¤ÎÌä¹ç¤»¤Ë
 	    ¥é¥ó¥À¥à¤ÊÂ礭¤ÊÈÖ¹æ¤Î¥Ý¡¼¥È¤òÍѤ¤¤ë¥Ð¡¼¥¸¥ç¥ó¤Î BIND ¤ò
 	    ÍѤ¤¤Æ¤¤¤Þ¤¹¡£¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤òÄ̤¹¤¿¤á¡¢¤Þ¤¿¤Ï¤¢¤Ê¤¿¤Î
 	    µ¤Ê¬¤Ç¡¢³°¸þ¤­¤ÎÌä¹ç¤»¤ò 53 È֥ݡ¼¥È¤«¤é¹Ô¤¤¤¿¤¤¤Ê¤é¤Ð¡¢
 	    <filename>/etc/namedb/named.conf</filename> ¤Ë¼¡¤Î¤è¤¦¤Ë
 	    ÀßÄꤷ¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <programlisting>options {
         query-source address * port 53;
 };</programlisting>
 
 	  <para>¹¹¤Ë¸ÂÄꤷ¤¿¤±¤ì¤Ð¡¢<literal>*</literal> ¤òñ°ì¤Î IP
 	    ¥¢¥É¥ì¥¹¤ËÃÖ¤­´¹¤¨¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£</para>
 
 	  <para>¤½¤ì¤Ï¤È¤â¤«¤¯¡¢¤ª¤á¤Ç¤È¤¦¤´¤µ¤¤¤Þ¤¹¡£
 	    <command>sockstat</command> ¤Î½ÐÎϤò¸«¤Æ¡¢¤ª¤«¤·¤Ê¸½¾Ý¤Ë
 	    ÃíÌܤ¹¤ë¤Î¤Ï¤è¤¤½¬´·¤Ç¤¹¡£</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bpf-not-configured">
           <para>¤Ê¤¼ <quote><computeroutput>/dev/bpf0: device not configured</computeroutput></quote>
             ¤¬½Ð¤ë¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             ¥Ð¡¼¥¯¥ì¡¼¥Ñ¥±¥Ã¥È¥Õ¥£¥ë¥¿ (&man.bpf.4;)
             ¥É¥é¥¤¥Ð¤Ï¡¢¤½¤ì¤òÍøÍѤ¹¤ë¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ëÁ°¤ËÍ­¸ú¤Ë¤·¤Æ¤ª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
             ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤Ë¡¢¼¡¤Î¤è¤¦¤ËÄɲ䷤ƥ«¡¼¥Í¥ë¤ÎºÆ¹½ÃÛ¤ò¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>pseudo-device bpfilter		# Berkeley Packet Filter</programlisting>
 
           <para>
             ¤½¤·¤ÆºÆµ¯Æ°¤·¤Æ¤«¤é¡¢¼¡¤Ë¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤òºîÀ®¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤Ï¡¢¼¡¤Î¤è¤¦¤ËÆþÎϤ·¡¢<filename>/dev</filename> ¤òÊѹ¹¤¹¤ë¤³¤È¤Ç¹Ô¤Ê¤¤¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>sh MAKEDEV bpf0</userinput></screen>
 
           <para>
             ¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤ÎºîÀ®¤Î¾ÜºÙ¤Ï¡¢
             <ulink url="../handbook/kernelconfig-nodes.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡Ö¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¡×</ulink>¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mount-smb-share">
           <para>Linux ¤Î smbmount ¤Î¤è¤¦¤Ë¡¢
             ¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Î Windows
             ¥Þ¥·¥ó¤Î¥Ç¥£¥¹¥¯¤ò¥Þ¥¦¥ó¥È¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤¿¤éÎɤ¤¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>Ports Collection ¤Ë´Þ¤Þ¤ì¤ë
             <application>sharity light</application> ¥Ñ¥Ã¥±¡¼¥¸¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡¢</para>
           <!-- XXX update for bp's SMBFS in CURRENT, when it is imported! -->
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="icmp-response-bw-limit">
           <para><quote>icmp-response bandwidth limit 300/200 pps</quote>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬¥í¥°¥Õ¥¡¥¤¥ë¤Ë¸½¤ì¤ë¤Î¤Ç¤¹¤¬¡¢
             ¤É¤¦¤¤¤¦¤³¤È¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>¤³¤ì¤Ï¡¢¥«¡¼¥Í¥ë¼«¿È¤«¤é¡ÖICMP ¤ä TCP ¤Î¥ê¥»¥Ã¥È (RST)
             ±þÅú¤ò¡¢ÂÅÅö¤Ê¿ô¤è¤ê¤â¿¤¯Á÷¤Ã¤Æ¤¤¤ë¡×¤È¤¤¤¦¤³¤È¤ò¡¢
             ¤¢¤Ê¤¿¤ËÅÁ¤¨¤ë¥á¥Ã¥»¡¼¥¸¤Ç¤¹¡£
             ICMP ±þÅú¤ÏÎɤ¯¡¢»È¤ï¤ì¤Æ¤¤¤Ê¤¤ UDP
             ¥Ý¡¼¥È¤ËÀܳ¤·¤è¤¦¤È¤·¤¿·ë²Ì¤È¤·¤ÆÀ¸À®¤µ¤ì¤Þ¤¹¡£
             ¤Þ¤¿¡¢TCP ¥ê¥»¥Ã¥È¤Ï¥ª¡¼¥×¥ó¤µ¤ì¤Æ¤¤¤Ê¤¤ TCP
             ¥Ý¡¼¥È¤ËÀܳ¤·¤è¤¦¤È¤·¤¿·ë²Ì¤È¤·¤ÆÀ¸À®¤µ¤ì¤Þ¤¹¡£
             ¤½¤Î¾¡¢¤³¤ì¤é¤Î¥á¥Ã¥»¡¼¥¸¤¬É½¼¨¤µ¤ì¤ë¸¶°ø¤È¤Ê¤ë¾õ¶·¤È¤·¤Æ¡¢
             °Ê²¼¤Î¤è¤¦¤Ê¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <itemizedlist>
             <listitem>
               <para>(ÆÃÄê¤Î¥»¥­¥å¥ê¥Æ¥£¾å¤Î¼åÅÀ¤ò°­ÍѤ·¤è¤¦¤È¤¹¤ë¹¶·â¤Ç¤Ï¤Ê¤¯)
                 ËÄÂç¤Ê¿ô¤Î¥Ñ¥±¥Ã¥È¤ò»È¤Ã¤¿¶¯°ú¤Ê¥µ¡¼¥Ó¥¹Ë¸³² (DoS) ¹¶·â¡£</para>
             </listitem>
 
             <listitem>
               <para>(°ìÉô¤Î¥¦¥§¥ë¥Î¥¦¥ó¥Ý¡¼¥È¤òÁÀ¤Ã¤¿¤â¤Î¤Ç¤Ï¤Ê¤¯)
                 Èó¾ï¤Ë¹­¤¤ÈϰϤΥݡ¼¥È¤ËÀܳ¤ò»î¤ß¤ë¥Ý¡¼¥È¥¹¥­¥ã¥ó¡£</para>
             </listitem>
           </itemizedlist>
 
           <para>¥á¥Ã¥»¡¼¥¸Ãæ¤ÎºÇ½é¤Î¿ô»ú¤Ï¡¢
             ¾å¸Â¤òÀßÄꤷ¤Ê¤«¤Ã¤¿¾ì¹ç¤Ë¥«¡¼¥Í¥ë¤¬Á÷¤Ã¤Æ¤¤¤¿¤Ç¤¢¤í¤¦¥Ñ¥±¥Ã¥È¤Î¿ô¤ò¼¨¤·¡¢
             ÆóÈÖÌܤοô»ú¤Ï¡¢¥Ñ¥±¥Ã¥È¿ô¤Î¾å¸ÂÃͤò¼¨¤·¤Þ¤¹¡£
             ¤³¤Î¾å¸ÂÃͤÏ
             <varname>net.inet.icmp.icmplim</varname> ¤È¤¤¤¦
             sysctl ÊÑ¿ô¤ò»È¤¦¤³¤È¤Ç¡¢°Ê²¼¤Î¤è¤¦¤ËÊѹ¹²Äǽ¤Ç¤¹¡£
             ¤³¤³¤Ç¤Ï¾å¸Â¤ò 1 É䢤¿¤ê¤Î¥Ñ¥±¥Ã¥È¿ô¤Ç
             <literal>300</literal> ¤Ë¤·¤Æ¤¤¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>sysctl -w net.inet.icmp.icmplim=300</userinput></screen>
 
           <para>¥«¡¼¥Í¥ë¤Î±þÅúÀ©¸Â¤ò̵¸ú¤Ë¤»¤º¡¢
             ¥í¥°¥Õ¥¡¥¤¥ëÃæ¤Î¥á¥Ã¥»¡¼¥¸¤À¤±¤òÍÞÀ©¤·¤¿¤¤¾ì¹ç¡¢
             <varname>net.inet.icmp.icmplim_output</varname> sysctl
             ÊÑ¿ô¤ò¼¡¤Î¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ç½ÐÎϤò»ß¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
           <screen>&prompt.root; <userinput>sysctl -w net.inet.icmp.icmplim_output=0</userinput></screen>
 
           <para>ºÇ¸å¤Ë¡¢¤â¤·±þÅúÀ©¸Â¤ò̵¸ú¤Ë¤·¤¿¤¤¾ì¹ç¤Ï¡¢
             <varname>net.inet.icmp.icmplim</varname> sysctl ÊÑ¿ô¤Ë
             (¾å¤ÎÎã¤Î¤è¤¦¤Ë¤·¤Æ) <literal>0</literal>
             ¤òÀßÄꤹ¤ë¤³¤È¤Ç¼Â¸½¤Ç¤­¤Þ¤¹¡£
             ¤¿¤À¤·±þÅúÀ©¸Â¤ò̵¸ú²½¤¹¤ë¤Î¤Ï¡¢¾åµ­¤ÎÍýͳ¤«¤é¤ª¤¹¤¹¤á¤·¤Þ¤»¤ó¡£</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="ppp">
     <title>PPP</title>
 
     <qandaset>
       <qandaentry>
         <question id="userppp">
           <para><command>ppp</command> ¤¬Æ°¤­¤Þ¤»¤ó¡£¤É¤³¤ò´Ö°ã¤¨¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>
             ¤Þ¤º
             &man.ppp.8;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¤È¡¢
             <ulink url="../handbook/ppp-and-slip.html#USERPPP">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡ÖPPP¡×</ulink>¤òÆɤó¤Ç¤ß¤Þ¤·¤ç¤¦¡£
             ¼¡¤Ë¡¢
           </para>
 
             <programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting>
 
           <para>
             ¤È¤¤¤¦Ì¿Îá¤ò <application>ppp</application>
             ¤Î¥³¥Þ¥ó¥É¥×¥í¥ó¥×¥È¤ËÂФ·¤ÆÂǤÁ¹þ¤à¤«¡¢
             ÀßÄê¥Õ¥¡¥¤¥ë
             <filename>/etc/ppp/ppp.conf</filename>
             ¤Ë²Ã¤¨¤Æ (<literal>default</literal>
             ¥»¥¯¥·¥ç¥ó¤ÎÀèƬ¤Ë²Ã¤¨¤ë¤Î¤¬°ìÈÖÎɤ¤¤Ç¤·¤ç¤¦)
             ¥í¥°¤òÍ­¸ú¤Ë¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤ÎºÝ¡¢
             <filename>/etc/syslog.conf</filename> (&man.syslog.conf.5; »²¾È)
             ¤Ë
           </para>
 
             <programlisting>!ppp
 *.*              /var/log/ppp.log</programlisting>
 
           <para>
             ¤È½ñ¤«¤ì¤¿¹Ô¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¤«¡¢¤Þ¤¿¡¢
             <filename>/var/log/ppp.log</filename>
             ¤¬Â¸ºß¤·¤Æ¤¤¤ë¤«¤É¤¦¤«³Î¤«¤á¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£
             ¤µ¤Æ¡¢¤³¤ì¤Ç²¿¤¬µ¯¤­¤Æ¤¤¤ë¤Î¤«Æͤ­»ß¤á¤ë¤¿¤á¤Ë¡¢
             ¥í¥°¥Õ¥¡¥¤¥ë¤«¤é¤¿¤¯¤µ¤ó¤Î¾ðÊó¤òÆÀ¤é¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
             ¥í¥°¤ËÌõ¤Îʬ¤é¤Ê¤¤Éôʬ¤¬¤¢¤Ã¤Æ¤â¿´ÇÛ¤´ÌµÍÑ¡£
             ¤¢¤Ê¤¿¤¬½õ¤±¤òµá¤á¤¿Ã¯¤«¤Ë¤È¤Ã¤Æ¤Ï¡¢
             ¤½¤ÎÉôʬ¤¬°ÕÌ£¤ò¤Ê¤¹¾ì¹ç¤¬¤¢¤ë¤Î¤Ç¤¹¡£
           </para>
 
             <note>
               <title>ÌõÃí</title>
               <para>
                 ¥í¥°¤Î¼èÆÀ¤Ë syslog ¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤¿¤Î¤Ï
                 2.2.5 °Ê¹ß¤«¤é¤Ç¤¹¡£
               </para>
             </note>
 
           <para>
             »ÈÍÑÃæ¤Î <command>ppp</command> ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç
             <quote><literal>set log</literal></quote>
             Ì¿Îá¤ò²ò¼á¤·¤Ê¤¤¾ì¹ç¤Ï¡¢<ulink url="http://people.FreeBSD.org/~brian/">ºÇ¿·ÈÇ</ulink>¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤Ù¤­¤Ç¤¹¡£
             FreeBSD ¤Î 2.1.5 °Ê¹ß¤Ç¥Ó¥ë¥É¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-hangs">
           <para><command>ppp</command> ¤ò¼Â¹Ô¤¹¤ë¤È¥Ï¥ó¥°¤·¤Þ¤¹</para>
         </question>
 
         <answer>
           <para>
             ¥Û¥¹¥È̾¤Î²ò·è¤¬¤¦¤Þ¤¯¤¤¤Ã¤Æ¤¤¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¡£¤Þ¤º¡¢
             ¥ê¥¾¥ë¥Ð (resolver) ¤¬
             <filename>/etc/hosts</filename>¤ò»²¾È¤¹¤ë¤è¤¦¤Ë¡¢
             <filename>/etc/host.conf</filename>
             ¤ÎºÇ½é¤Î¹Ô¤Ë
             <literal>host</literal>
             ¤È½ñ¤­¹þ¤ó¤Ç¤¯¤À¤µ¤¤¡£
             ¤Ä¤®¤Ë¡¢<filename>/etc/hosts</filename>
             ¤Ë»ÈÍѤ·¤Æ¤¤¤ë¥Þ¥·¥ó¤Î¥¨¥ó¥È¥ê¤ò½ñ¤­²Ã¤¨¤Þ¤¹¡£
             ¥í¡¼¥«¥ë¤Ç¥Í¥Ã¥È¥ï¡¼¥¯¤ò»ÈÍѤ·¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ï¡¢
             <literal>localhost</literal>
             ¤Î¹Ô¤ò°Ê²¼¤Î¤è¤¦¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>127.0.0.1      foo.bar.com foo localhost</programlisting>
 
           <para>
             »ÈÍѤ·¤Æ¤¤¤ë¥Û¥¹¥È¤Î¥¨¥ó¥È¥ê¤òÄɲ䷤Ƥ⤫¤Þ¤¤¤Þ¤»¤ó¡£
             ¾ÜºÙ¤Ï´ØÏ¢¤¹¤ë¥Þ¥ó¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-nodial-auto">
           <para><command>ppp</command> ¤¬
             <option>-auto</option> ¥â¡¼¥É¤Ç¥À¥¤¥¢¥ë¤·¤Æ¤¯¤ì¤Ê¤¤</para>
         </question>
 
         <answer>
           <para>
             ¤Þ¤ººÇ½é¤Ë¡¢¥Ç¥Õ¥©¥ë¥È¥ë¡¼¥È¤¬³ÎΩ¤·¤Æ¤¤¤ë¤«¤É¤¦¤«¥Á¥§¥Ã¥¯¤·¤Æ¤¯¤À¤µ¤¤¡£
             <command>netstat -rn</command> (&man.netstat.1; »²¾È)
             ¤ò¼Â¹Ô¤¹¤ë¤È¡¢°Ê²¼¤Î¤è¤¦¤Ê¾ðÊó¤¬É½¼¨¤µ¤ì¤ë¤Ï¤º¤Ç¤¹¡£
           </para>
 
           <screen>Destination        Gateway            Flags     Refs     Use     Netif Expire
 default            10.0.0.2           UGSc        0        0      tun0
 10.0.0.2           10.0.0.1           UH          0        0      tun0</screen>
 
           <para>
             ¤³¤ì¤Ï¤¢¤Ê¤¿¤¬¥Ï¥ó¥É¥Ö¥Ã¥¯¤ä¥Þ¥Ë¥å¥¢¥ë¡¢
             <filename>ppp.conf.sample</filename>
             ¤ÎÃæ¤Ç½Ð¤Æ¤¯¤ë¥¢¥É¥ì¥¹¤ò»ÈÍѤ·¤Æ¤¤¤ë¤È²¾Äꤷ¤¿¾ì¹ç¤ÎÎã¤Ç¤¹¡£
             ¥Ç¥Õ¥©¥ë¥È¥ë¡¼¥È¤¬³ÎΩ¤·¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
             <filename>ppp.conf</filename>
             ¤ÎÃæ¤Î
             <literal>HISADDR</literal>
             ¤¬Íý²ò¤Ç¤­¤Ê¤¤¡¢
             ¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤Î
             &man.ppp.8;
             ¤¬Áö¤Ã¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
             FreeBSD 2.2.5 ¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤ËÉÕ°¤·¤Æ¤¤¤¿
             <application>ppp</application>
             ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢
           </para>
 
             <programlisting>add 0 0 HISADDR</programlisting>
 
           <para>
             ¤È½ñ¤«¤ì¤¿¹Ô¤ò°Ê²¼¤Î¤è¤¦¤Ë½¤Àµ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
             <programlisting>add 0 0 10.0.0.2</programlisting>
 
           <para>
             <command>netstat -rn</command>
             ¤Ç¥Ç¥Õ¥©¥ë¥È¥ë¡¼¥È¤Î¾ðÊó¤¬É½¼¨¤µ¤ì¤Ê¤¤¾ì¹ç¡¢¤â¤¦°ì¤Ä¡¢
             <filename>/etc/rc.conf</filename> (&man.rc.conf.5; »²¾È) (2.2.2
             ¤è¤êÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï
             <filename>/etc/sysconfig</filename>
             ¤È¸Æ¤Ð¤ì¤Æ¤¤¤Þ¤·¤¿) ¤ÎÃæ¤Ç¥Ç¥Õ¥©¥ë¥È¤Î¥ë¡¼¥¿¤ò¸í¤Ã¤ÆÀßÄꤷ¡¢
             <filename>ppp.conf</filename> ¤«¤é
           </para>
 
             <programlisting>delete ALL</programlisting>
 
           <para>
             ¤Î¹Ô¤ò¤¦¤Ã¤«¤ê¾Ã¤·¤Æ¤·¤Þ¤Ã¤¿²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤Î¾ì¹ç¤Ï¡¢
             <ulink url="../handbook/ppp-and-slip.html#USERPPP-FINAL">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡Ö¥·¥¹¥Æ¥à¤ÎºÇ½ªÀßÄê¡×</ulink>¤Î¹à¤òÆɤßľ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="no-route-to-host">
           <para><quote><computeroutput>No route to host</computeroutput></quote>
             ¤È¤Ï¤É¤¦¤¤¤¦°ÕÌ£¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤³¤Î¥¨¥é¡¼¤ÏÄ̾
             <filename>/etc/ppp/ppp.linkup</filename>
             ¤Ë°Ê²¼¤Î¤è¤¦¤Ê¥»¥¯¥·¥ç¥ó¤¬Ìµ¤¤¾ì¹ç¤Ëµ¯¤³¤ê¤Þ¤¹¡£
           </para>
 
             <programlisting>MYADDR:
   delete ALL
   add 0 0 HISADDR</programlisting>
 
           <para>
             ¤³¤ì¤ÏưŪ <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢
             ¤Þ¤¿¤Ï¥²¡¼¥È¥¦¥§¥¤¤Î¥¢¥É¥ì¥¹¤òÃΤé¤Ê¤¤¾ì¹ç¤Ë¤Î¤ßɬÍפÊÀßÄê¤Ç¤¹¡£
             ¥¤¥ó¥¿¥é¥¯¥Æ¥£¥Ö¥â¡¼¥É¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢
             <emphasis>¥Ñ¥±¥Ã¥È¥â¡¼¥É</emphasis>¤ËÆþ¤Ã¤¿¸å¤Ç (¥×¥í¥ó¥×¥È¤¬
             <acronym>PPP</acronym>
             ¤ÈÂçʸ»ú¤ËÊѤï¤Ã¤¿¤é¥Ñ¥±¥Ã¥È¥â¡¼¥É¤ËÆþ¤Ã¤¿¤·¤ë¤·¤Ç¤¹)¡¢
             °Ê²¼¤ÎÌ¿Îá¤òÆþÎϤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>delete ALL
 add 0 0 HISADDR</screen>
 
           <para>
             ¾Ü¤·¤¤¾ðÊó¤Ë¤Ä¤¤¤Æ¤Ï¡¢
             <ulink url="../handbook/ppp-and-slip.html#USERPPP-DYNAMICIP">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡ÖPPP ¤ÈưŪ IP ÀßÄê¡×</ulink>¤Î¹à¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="connection-threeminutedrop">
           <para>3 ʬ¤Û¤É·Ð¤Ä¤ÈÀܳ¤¬ÀÚ¤ì¤Æ¤·¤Þ¤¦</para>
         </question>
 
         <answer>
           <para>
             <command>ppp</command>
             ¤Î¥¿¥¤¥à¥¢¥¦¥È¤Ï ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï 3 ʬ¤Ç¤¹¡£
             ¤³¤ì¤Ï
           </para>
 
           <programlisting>set timeout <replaceable>NNN</replaceable></programlisting>
 
           <para>
             ¤È¤¤¤¦Ì¿Îá¤Ë¤è¤Ã¤ÆÄ´À°¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             <replaceable>NNN</replaceable> ¤Ë¤Ï¡¢
             Àܳ¤¬ÀÚ¤ì¤ë¤Þ¤Ç¤Î¥¢¥¤¥É¥ë»þ´Ö¤¬Éÿô¤ÇÆþ¤ê¤Þ¤¹¡£
             <replaceable>NNN</replaceable> ¤¬ 0 ¤Î¾ì¹ç¡¢
             ¥¿¥¤¥à¥¢¥¦¥È¤Ë¤è¤ëÀÚÃǤϵ¯¤³¤ê¤Þ¤»¤ó¡£
             ¤³¤Î¥³¥Þ¥ó¥É¤Ï <filename>ppp.conf</filename>
             ¤ËÆþ¤ì¤ë¤³¤È¤â¡¢
             ¥¤¥ó¥¿¥é¥¯¥Æ¥£¥Ö¥â¡¼¥É¤Ç¥×¥í¥ó¥×¥È¤«¤éÆþÎϤ¹¤ë¤³¤È¤â
             ¤Ç¤­¤Þ¤¹¡£
             ¥½¥±¥Ã¥È¤òÍѤ¤¤ë
             &man.telnet.1; ¤« &man.pppctl.8; ¤ò»ÈÍѤ·¡¢
             <application>ppp</application>
             ¥µ¡¼¥Ð¤ËÀܳ¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢
             ²óÀþ¤¬¥¢¥¯¥Æ¥£¥Ö¤Ê´Ö¤Ë¸ÂÄꤷ¤Æ¥¿¥¤¥à¥¢¥¦¥È¤Î»þ´Ö¤òÄ´À°¤¹¤ë¤³¤È¤â²Äǽ¤Ç¤¹¡£
           </para>
 
             <note>
               <title>ÌõÃí</title>
               <para>
                 <command>pppctl</command> ¤Ï 2.2.5R ¤«¤é¤Ç¤¹¡£
               </para>
             </note>
 
           <para>
             ¾Ü¤·¤¤¾ðÊó¤Ï
             &man.ppp.8;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-drop-heavy-load">
           <para>Éé²Ù¤¬¹â¤¤¤ÈÀܳ¤¬ÀÚ¤ì¤Æ¤·¤Þ¤¦</para>
         </question>
 
         <answer>
           <para>
             Link Quality Reporting (LQR) ¤ÎÀßÄê¤ò¹Ô¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢
             ¥Þ¥·¥ó¤ÈÀܳÀè¤Î´Ö¤ÇÈó¾ï¤Ë¤¿¤¯¤µ¤ó¤Î <acronym>LQR</acronym>
             ¥Ñ¥±¥Ã¥È¤¬¼º¤ï¤ì¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£·ë²Ì¤È¤·¤Æ
             <command>ppp</command> ¤Ï²óÀþ¤Î¶ñ¹ç¤¤¤¬°­¤¤¤È¹Í¤¨¡¢
             ²óÀþ¤òÀÚÃǤ¹¤ë¤Î¤Ç¤¹¡£2.2.5 ¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Î FreeBSD ¤Ç¤Ï
             <acronym>LQR</acronym>
             ¤Ï¥Ç¥Õ¥©¥ë¥È¤ÇÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¸½ºß¤Ç¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¾õÂÖ¤Ç̵¸ú¤Ç¤¹¡£
             <acronym>LQR</acronym>
             ¤Ï°Ê²¼¤ÎÌ¿Îá¤Ç̵¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <programlisting>disable lqr</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-drop-random">
           <para>Àܳ¤¬¥é¥ó¥À¥à¤ËÀÚ¤ì¤Æ¤·¤Þ¤¦</para>
         </question>
 
         <answer>
           <para>
             ¥Î¥¤¥º¤Î¿¤¤²óÀþ¡¢¤¢¤ë¤¤¤ÏÂÔ¤Áµ¡Ç½ÉÕ¤­¤Î²óÀþ¤Ç¤Ï¡¢
             »þ¡¹¥â¥Ç¥à¤¬ (¸í¤Ã¤Æ) ¥­¥ã¥ê¥¢¤ò¼º¤Ã¤¿¤È»×¤¤¹þ¤ß¡¢
             ²óÀþ¤¬ÀÚÃǤµ¤ì¤Æ¤·¤Þ¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             Âç¿¿ô¤Î¥â¥Ç¥à¤Ç¤Ï¡¢
             °ì»þŪ¤Ê¥­¥ã¥ê¥¢¤ÎÁÓ¼º¤ò¤É¤ì¤¯¤é¤¤¤Î»þ´Ö¤Ç¸¡½Ð¤¹¤ë¤«¤ò¡¢
             ÀßÄê¤Ç·è¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð USR Sportster ¤Ç¤Ï¡¢S10 ¥ì¥¸¥¹¥¿
             ¤ÎÃͤò 10 Çܤ·¤¿Éÿô¤¬¤½¤ÎÃͤˤʤê¤Þ¤¹¡£
             ¤³¤Î¾ì¹ç¡¢¥â¥Ç¥à¤ò¤â¤Ã¤È¤Î¤ó¤Ó¤ê²°¤µ¤ó¤Ë¤¹¤ë¤Ë¤Ï¡¢
             dial ¹Ô¤Ë¼¡¤Î¤è¤¦¤Êʸ»úÎó¤ò²Ã¤¨¤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <programlisting>set dial "...... ATS10=10 OK ......"</programlisting>
 
           <para>
             ¾Ü¤·¤¯¤Ï¤ª»È¤¤¤Î¥â¥Ç¥à¤Î¥Þ¥Ë¥å¥¢¥ë¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-hangs-random">
           <para>Àܳ¤¬ÉÔµ¬Â§¤Ë¥Ï¥ó¥°¥¢¥Ã¥×¤·¤Æ¤·¤Þ¤¦</para>
         </question>
 
         <answer>
           <para>
             ¤¿¤¯¤µ¤ó¤Î¿Í¤¬¡¢¸¶°øÉÔÌÀ¤Î¥Ï¥ó¥°¥¢¥Ã¥×¤ò·Ð¸³¤·¤Æ¤¤¤Þ¤¹¡£
             ¸¡¾Ú¤Î¤¿¤á¤ËɬÍפʤΤϡ¢¤Þ¤º¤É¤Á¤é¦¤Î¥ê¥ó¥¯¤Ç¤½¤ì¤¬µ¯¤³¤Ã¤Æ¤¤¤ë¤«¡¢
             ¤È¤¤¤¦¤³¤È¤Ç¤¹¡£
           </para>
 
           <para>
             ³°ÉôÀܳ·¿¥â¥Ç¥à¤òÍøÍѤ·¤Æ¤¤¤ë¤Ê¤é¡¢
             ñ¤Ë <command>ping</command> ¤ò»È¤¦¤³¤È¤Ç¡¢
             ¥Ç¡¼¥¿¤òÁ÷¿®¤¹¤ë¤È¤­¤Ë <acronym>TD</acronym>
             ¥é¥ó¥×¤¬ÅÀÅô¤¹¤ë¤«¤É¤¦¤«¤ò³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤â¤·¡¢<acronym>TD</acronym> ¥é¥ó¥×¤¬ÅÀÅô¤·¤Æ¡¢
             <acronym>RD</acronym> ¥é¥ó¥×¤¬ÅÀÅô¤·¤Ê¤±¤ì¤Ð¡¢
             ÌäÂê¤Ï²óÀþ¤Î¸þ¤³¤¦Â¦¤Ë¤¢¤ê¤Þ¤¹¡£<acronym>TD</acronym> ¤¬ÅÀÅô¤·¤Ê¤±¤ì¤Ð¡¢
             ÌäÂê¤Ï²óÀþ¤Î¤³¤Á¤é¦¤Ç¤¹¡£Æ⢷¿¥â¥Ç¥à¤Î¾ì¹ç¡¢
             <filename>ppp.conf</filename> ¥Õ¥¡¥¤¥ë¤Ë
             <command>set server</command> ¥³¥Þ¥ó¥É¤òÆþ¤ì¤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£
             ²óÀþ¤¬ÀÚÃǤµ¤ì¤¿¤È¤­¡¢<command>pppctl</command>
             ¤ò»È¤Ã¤Æ <command>ppp</command>
             ¤ËÀܳ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤Î¤È¤­¡¢
             ¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤¬µÞ¤ËÉüµì (¿ÇÃÇ¥½¥±¥Ã¥È¤Ø¤Î¥¢¥¯¥»¥¹¤Ç¡¢
             <command>ppp</command> ¤¬Éü³è¤·¤Þ¤¹) ¤¹¤ë¤«¡¢
             ¤â¤·¤¯¤ÏÀܳ¼«ÂΤ¬Á´¤¯¤Ç¤­¤Ê¤¤ (¤¿¤À¤·¡¢
             <command>ppp</command>
             µ¯Æ°»þ¤Ë <command>set socket</command>
             ¥³¥Þ¥ó¥É¤¬¤Á¤ã¤ó¤È¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¤È¤·¤Þ¤¹) ¤È¤·¤¿¤é¡¢
             ÌäÂê¤Ï²óÀþ¤Î¤³¤Á¤é¦¤Ç¤¹¡£
             ¤â¤·¡¢Àܳ²Äǽ¤Ç¡¢¤«¤Ä¾õ¶·¤¬ÊѲ½¤·¤Ê¤±¤ì¤Ð¡¢
             <command>set log local async</command>
             ¤ò»È¤Ã¤Æ¥í¡¼¥«¥ëÈóƱ´ü¥í¥° (async logging) ¤òÍ­¸ú¤Ë¤·¡¢
             <command>ping</command>
             ¤ò¾¤Î¥¦¥£¥ó¥É¥¦¤«¥¿¡¼¥ß¥Ê¥ë¤«¤é»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
             ÈóƱ´ü¥í¥°¤Ë¤Ï¡¢¤³¤Á¤é¦¤Î¥ê¥ó¥¯¤ÎÁ÷¼õ¿®¥Ç¡¼¥¿¤¬µ­Ï¿¤µ¤ì¤Þ¤¹¡£
             ¤â¤·¡¢¥Ç¡¼¥¿¤¬Á÷¿®¤µ¤ì¤¿¤Ë¤â¤«¤«¤ï¤é¤ºÊ֤äÆÍè¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢
             ÌäÂê¤Ï²óÀþ¤Î¸þ¤³¤¦Â¦¤Ë¤¢¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ÌäÂ꤬²óÀþ¤Î¤É¤Á¤é¦¤«¤Ë¤¢¤ë¤³¤È¤¬Ê¬¤«¤Ã¤¿¤é¡¢
             ¤Ä¤®¤ÎÆó¤Ä¤Î²ÄǽÀ­¤¬¹Í¤¨¤é¤ì¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-remote-not-responding">
           <para>²óÀþ¤Î¸þ¤³¤¦Â¦¤Ç¤ÎÈ¿±þ¤¬¤Ê¤¤</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤ËÂнè¤Ç¤­¤ë¤³¤È¤Ï¤Û¤È¤ó¤É¤¢¤ê¤Þ¤»¤ó¡£ÂçÉôʬ¤Î ISP
             ¤Ï¡¢Microsoft ¼ÒÀ½ OS °Ê³°¤ÎÍøÍѼԤËÂФ·¤Æ¤Î¥µ¥Ý¡¼¥È¤òµñÈݤ¹¤ë¤Ç¤·¤ç¤¦¡£
             <filename>ppp.conf</filename> ¥Õ¥¡¥¤¥ë¤ÎÃæ¤Ë
             <literal>enable lqr</literal>
             ¤òµ­½Ò¤¹¤ë¤³¤È¤Ç
             <command>ppp</command>
             ¤¬²óÀþ¤Î¸þ¤³¤¦Â¦¤ÇȯÀ¸¤¹¤ëÀÚÃǤò¸¡½Ð¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢
             ¤³¤Î¸¡½Ð¤ÏÈæ³ÓŪÃÙ¤¤¤¿¤á¡¢¤¢¤Þ¤êÌò¤ËΩ¤Á¤Þ¤»¤ó¡£¤Þ¤¿¡¢¤¢¤Ê¤¿¤Ï
             user-ppp ¤òÍøÍѤ·¤Æ¤¤¤ë¤³¤È¤ò
             ISP ¤ËÃΤé¤ì¤¿¤¯¤Ê¤¤¤È»×¤¦¤«¤âÃΤì¤Þ¤»¤ó¤Í¡£
           </para>
 
           <para>
             ¤Þ¤ººÇ½é¤Ë¡¢¤³¤Á¤é¦¤Î°µ½Ìµ¡Ç½¤ò¤¹¤Ù¤Æ̵¸ú¤Ë¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤ì¤Ë¤Ï¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤ò¤Ä¤®¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <programlisting>disable pred1 deflate deflate24 protocomp acfcomp shortseq vj
 deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
 
           <para>
             ¤½¤·¤ÆºÆÀܳ¤·¡¢Êѹ¹Á°¤ÈƱ¤¸¤è¤¦¤ËÄÌ¿®¤Ç¤­¤ë¤³¤È¤ò³Îǧ¤·¤Þ¤¹¡£
             ¤â¤·¤³¤ì¤Ë¤è¤Ã¤Æ¾õ¶·¤¬²þÁ±¤µ¤ì¤ë¤«¡¢´°Á´¤Ë²ò·è¤·¤¿¤é¡¢
             (¾å¤ÎÀßÄê¤Î¤¦¤Á) ¤É¤ÎÀßÄê¤Ç¾õ¶·¤¬ÊѲ½¤·¤¿¤Î¤«¤ò¡¢
             ¿§¡¹¤ÊÁȹ礻¤Ç»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£¤³¤ì¤Ï¡¢ISP
             ¤ËÌ䤤¹ç¤ï¤»¤ò¹Ô¤Ê¤¦¤È¤­¤ÎÍ­¸ú¤Ê¾ðÊó¤È¤Ê¤ê¤Þ¤¹ (¤¿¤À¤·¡¢
             ¤¢¤Ê¤¿¤¬ Microsoft
             ¼ÒÀ½Éʰʳ°¤Î¤â¤Î¤òÍøÍѤ·¤Æ¤¤¤ë¤³¤È¤âÌÀ¤é¤«¤Ë¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¤¬)¡£
           </para>
 
           <para>
             ISP ¤ËÌ䤤¹ç¤ï¤»¤ò¹Ô¤Ê¤¦Á°¤Ë¡¢¤³¤Á¤é¦¤ÎÈóƱ´ü¥í¥°¤òÍ­¸ú¤Ë¤·¤Æ¡¢
             Àܳ¤¬¥Ï¥ó¥°¥¢¥Ã¥×¤¹¤ë¤Þ¤ÇÂԤäƤ¯¤À¤µ¤¤¡£¤³¤Îºî¶È¤Ï¡¢
             Èó¾ï¤Ë¿¤¯¤Î¥Ç¥£¥¹¥¯¶õ´Ö¤ò¾ÃÈñ¤¹¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£
             ¶½Ì£¤ÎÂоݤȤʤäƤ¤¤ë¤Î¤Ï¡¢ÄÌ¿®¥Ý¡¼¥È¤«¤éºÇ¸å¤ËÆɤ߹þ¤Þ¤ì¤¿¥Ç¡¼¥¿¤Ç¤¹¡£
             ¤½¤ì¤ÏÄ̾ï <acronym>ASCII</acronym> ¥Ç¡¼¥¿¤Ç¡¢
             ÌäÂêÅÀ¤Î¾ÜºÙ (<quote><computeroutput>Memory fault, core dump</computeroutput></quote> ¤Ê¤É) ¤¬
             µ­ºÜ¤µ¤ì¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ²óÀþ¤Î¸þ¤³¤¦Â¦¤ÇÄÌ¿®¥í¥°¤ò´Æ»ë¤¹¤ë¤³¤È¤Ï²Äǽ¤Ê¤Ï¤º¤Ç¤¹¤Î¤Ç¡¢
             ÀÚÃǤ¬È¯À¸¤·¤¿»þ¡¢ISP ¤ÎÂбþ¤¬¹¥°ÕŪ¤Ê¤é¤Ð
             ¤É¤¦¤·¤Æ ISP ¦¤ÇÌäÂ꤬ȯÀ¸¤·¤¿¤Î¤«¤³¤Á¤é¤ËÅÁ¤¨¤Æ¤¯¤ì¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£
             <email>brian@Awfulhak.org</email>
             ¤Þ¤Ç¾ÜºÙ¤òÁ÷¤Ã¤Æĺ¤¯¤«¡¢ISP
             ¤ËľÀÜ»ä¤ËÏ¢Íí¤¹¤ë¤è¤¦¤ËÅÁ¤¨¤Æ²¼¤µ¤Ã¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-hung">
           <para><command>ppp</command> ¤¬¥Ï¥ó¥°¥¢¥Ã¥×¤¹¤ë</para>
         </question>
 
         <answer>
           <para>
             ¥Ù¥¹¥È¤ÊÊýË¡¤Ï¡¢
             <literal>CFLAGS+=-g</literal> ¤È
             <literal>STRIP=</literal> ¤ò
             <command>ppp</command> ¤Î
             <filename>Makefile</filename>
             ¤ËÄɲ䷤ơ¢
             <command>ppp</command> ¤òºÆ¹½ÃÛ¤·¡¢
             ¤½¤·¤Æ
             <literal>make clean &amp;&amp; make &amp;&amp; make install</literal>
             ¤ò¹Ô¤Ê¤¦¤³¤È¤Ç¤¹¡£
             <command>ppp</command> ¤¬¥Ï¥ó¥°¥¢¥Ã¥×¤·¤¿»þ¡¢
             <literal>ps ajxww | fgrep ppp</literal> ¤ò»È¤Ã¤Æ
             <command>ppp</command>
             ¤Î¥×¥í¥»¥¹ ID ¤òÄ´¤Ù¡¢
             <literal>gdb ppp PID</literal> ¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
             <command>gdb</command>
             ¤Î¥×¥í¥ó¥×¥È¤«¤é¡¢
             <command>bt</command>
             ¤ò»È¤Ã¤Æ¥¹¥¿¥Ã¥¯¤ò¥È¥ì¡¼¥¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¥¹¥¿¥Ã¥¯¥È¥ì¡¼¥¹¤Î·ë²Ì¤Ï¡¢<email>brian@Awfulhak.org</email>
             ¤Þ¤ÇÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-loginok-thennothing">
           <para><computeroutput>Login OK!</computeroutput>
             ¤Î¥á¥Ã¥»¡¼¥¸¤¬½Ð¤¿¸å¡¢²¿¤âµ¯¤³¤é¤Ê¤¤</para>
         </question>
 
         <answer>
           <para>
             2.2.5 ¤è¤êÁ°¤Î¥ê¥ê¡¼¥¹¤Î FreeBSD ¤Ç¤Ï¡¢
             &man.ppp.8;
             ¤Ï¥ê¥ó¥¯¤¬³ÎΩ¤·¤¿¸å¡¢ÀܳÀ褬 <acronym>Line Control Protocol (LCP)</acronym>
             ¤òȯ¿®¤¹¤ë¤Î¤òÂÔ¤Á¤Þ¤¹¡£¤·¤«¤·¡¢Â¿¤¯¤Î <acronym>ISP</acronym>
             ¤Ç¤Ï¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò¼«Ê¬¤«¤é¤Ïµ¯¤³¤µ¤º¡¢
             ¥¯¥é¥¤¥¢¥ó¥È¤¬µ¯¤³¤¹¤Î¤òÂԤäƤ¤¤Þ¤¹¡£
             <application>ppp</application> ¤Ë¶¯À©Åª¤Ë
             <acronym>LCP</acronym> ¤òȯ¿®¤µ¤»¤ë¤Ë¤Ï¡¢
             ¼¡¤ÎÌ¿Îá¤ò»È¤¤¤Þ¤¹¡£
           </para>
 
             <programlisting>set openmode active</programlisting>
 
             <note>
               <para>
                 ξÊý¤Î¦¤¬¥Í¥´¥¸¥§¡¼¥·¥ç¥ó¤òµ¯¤³¤·¤Æ¤â¡¢
                 ÂçÄñ¤Î¾ì¹ç¤Ï²¿¤ÎÌäÂê¤â¤¢¤ê¤Þ¤»¤ó¡£
                 ¤Ç¤¹¤«¤é¡¢¸½ºß¤Ç¤Ï openmode
                 ¤Ï¥Ç¥Õ¥©¥ë¥È¤ÇÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
                 ¼¡¤Î¥»¥¯¥·¥ç¥ó¤Ç¤³¤ì¤¬<emphasis>ÌäÂê¤Ë¤Ê¤ë¾ì¹ç</emphasis>¤òÀâÌÀ¤·¤Þ¤¹¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-same-magic">
           <para>¤Ç¤â¤Þ¤À <quote><computeroutput>magic is the same</computeroutput></quote>
             ¤È¤¤¤¦¥¨¥é¡¼¤¬½Ð¤ë</para>
         </question>
 
         <answer>
           <para>
             »þÀÞ¡¢Àܳľ¸å¤Î¥í¥°¤Ë
             <quote><computeroutput>magic is the same</computeroutput></quote>
             ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬¤¢¤é¤ï¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤Î¥á¥Ã¥»¡¼¥¸¤¬¤¢¤é¤ï¤ì¤Æ¤â²¿¤âµ¯¤­¤Ê¤¤¾ì¹ç¤â¤¢¤ê¤Þ¤¹¤·¡¢
             ¤É¤Á¤é¤«¤Î¦¤¬Àܳ¤òÀڤäƤ·¤Þ¤¦¾ì¹ç¤â¤¢¤ê¤Þ¤¹¡£
             <command>ppp</command> ¤Î¼ÂÁõ¤Î¿¤¯¤Ï¤³¤ÎÌäÂê¤ËÂбþ¤Ç¤­¤Æ¤ª¤é¤º¡¢
             ¤½¤Î¾ì¹ç¤Ë¤Ï¤Á¤ã¤ó¤È link ¤¬¾å¤¬¤Ã¤Æ¤¤¤ë¾õÂ֤Ǥ¢¤Ã¤Æ¤â¡¢
             <command>ppp</command> ¤¬ºÇ½ªÅª¤Ë¤¢¤­¤é¤á¤Æ¤·¤Þ¤¤¡¢
             Àܳ¤òÀÚ¤ë¤Þ¤ÇÀßÄê¤Î¥ê¥¯¥¨¥¹¥È¤¬·«¤êÊÖ¤·Á÷¤é¤ì¡¢
             ÀßÄ꤬¹Ô¤ï¤ì¤¿¤È¤¤¤¦ÄÌÃΤ¬¥í¥°¥Õ¥¡¥¤¥ë¤Ë»Ä¤ë¤È»×¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ì¤ÏÄ̾
             ¥Ç¥£¥¹¥¯¥¢¥¯¥»¥¹¤ÎÃÙ¤¤¥µ¡¼¥Ð¥Þ¥·¥ó¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤Ç
             <command>getty</command> ¤¬À¸¤­¤Æ¤¤¤Æ¡¢
             <command>ppp</command> ¤¬¥í¥°¥¤¥ó¥¹¥¯¥ê¥×¥È¤«¡¢
             ¥í¥°¥¤¥óľ¸å¤Ëµ¯Æ°¤µ¤ì¤¿¥×¥í¥°¥é¥à¤«¤é¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ëµ¯¤³¤ê¤Þ¤¹¡£
             <command>slirp</command>
             ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤ËƱÍͤξɾõ¤¬¸«¤é¤ì¤¿¤È¤¤¤¦Êó¹ð¤â¤¢¤ê¤Þ¤¹¡£
             ¸¶°ø¤Ï
             <command>getty</command> ¤Î½ªÎ»¤µ¤ì¤ë¤Þ¤Ç¤È¡¢
             <command>ppp</command> ¤¬¼Â¹Ô¤µ¤ì¡¢
             ¥¯¥é¥¤¥¢¥ó¥È¦¤Î
             <command>ppp</command> ¤¬
             <acronym>Line Control Protocol (LCP)</acronym>
             ¤òÁ÷¤ê»Ï¤á¤ë¤Þ¤Ç¤Î¥¿¥¤¥ß¥ó¥°¤Ë¤¢¤ê¤Þ¤¹¡£
             ¥µ¡¼¥Ð¦¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤Ç
             <literal>ECHO</literal>
             ¤¬Í­¸ú¤Ê¤Þ¤Þ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¡¢
             ¥¯¥é¥¤¥¢¥ó¥È¦¤Î
             <command>ppp</command>
             ¤Ë¥Ñ¥±¥Ã¥È¤¬¡ÖÈ¿¼Í¡×¤·¤Æ¤·¤Þ¤¦¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             <acronym>LCP</acronym>
             ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î°ìÉô¤È¤·¤Æ¡¢
             ¥ê¥ó¥¯¤Îξ¥µ¥¤¥É¤Ç
             magic number ¤òÄê¤á¤Æ¡¢
             ¡ÖÈ¿¼Í¡×¤¬µ¯¤­¤Æ¤¤¤Ê¤¤¤«¤É¤¦¤«³Î¤«¤á¤ëºî¶È¤¬¤¢¤ê¤Þ¤¹¡£
             µ¬Ìó¤Ç¤Ï¡¢ÀܳÁê¼ê¤¬¤³¤Á¤é¤ÈƱ¤¸ magic number ¤òÄ󼨤·¤Æ¤­¤¿¤é¡¢
             <acronym>NAK</acronym> ¤òÁ÷¤Ã¤Æ¿·¤·¤¤
             magic number ¤òÁªÂò¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤ÈÄê¤á¤Æ¤¤¤Þ¤¹¡£
             ¤³¤Îºî¶È¤Î´Ö¡¢¥µ¡¼¥Ð¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤Î
             <literal>ECHO</literal> ¤¬¤º¤Ã¤ÈÍ­¸ú¤Ë¤Ê¤Ã¤¿¤Þ¤Þ¤Ê¤Î¤Ç¡¢
             ¥¯¥é¥¤¥¢¥ó¥È¦¤Î <command>ppp</command>
             ¤Ï <acronym>LCP</acronym> ¥Ñ¥±¥Ã¥È¤òÁ÷¤ê¡¢
             ¥Ñ¥±¥Ã¥È¤¬È¿¼Í¤·¤ÆÁ´¤¯Æ±¤¸ magic number
             ¤¬Á÷¤é¤ì¤Æ¤¯¤ë¤Î¤ò¸«¤Ä¤±¡¢
             ¤½¤ì¤ËÂФ·¤Æ <acronym>NAK</acronym>
             ¤òÁ÷¤ë¤Î¤Ç¤¹¡£°ìÊý <acronym>NAK</acronym>
             ¼«ÂΤâ (¤³¤ì¤Ï <command>ppp</command>
             ¤¬ magic number
             ¤òÊѹ¹¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Ê¤¤¤³¤È¤ò°ÕÌ£¤·¤Æ¤¤¤Þ¤¹) È¿¼Í¤·¤Æ¤¯¤ë¤Î¤Ç¡¢
             ·ë²Ì¤È¤·¤Æ magic number ¤¬¿ô¤¨¤­¤ì¤Ê¤¤¤Û¤ÉÊѹ¹¤µ¤ì¡¢
             ¤½¤Î¤¹¤Ù¤Æ¤¬¥µ¡¼¥Ð¤Î <acronym>tty</acronym>
             ¥Ð¥Ã¥Õ¥¡¤ÎÃæ¤ËÀѤ߽Ťʤ뤳¤È¤Ë¤Ê¤ë¤Î¤Ç¤¹¡£
             ¥µ¡¼¥Ð¤Ç¥¹¥¿¡¼¥È¤·¤¿ <command>ppp</command>
             ¤Ï¡¢¤¹¤°¤Ë magic number ¤Ç¤¢¤Õ¤ì¤«¤¨¤Ã¤Æ¤·¤Þ¤¤¡¢
             <acronym>LCP</acronym>
             ¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò½½Ê¬¤Ë¹Ô¤Ã¤¿¤â¤Î¤ÈȽÃǤ·¤Æ¡¢
             ¤µ¤Ã¤µ¤ÈÀܳ¤òÀڤäƤ·¤Þ¤¤¤Þ¤¹¡£
             °ìÊý¡¢
             ¥¯¥é¥¤¥¢¥ó¥È¦¤ÏÈ¿¼Í¤¬µ¢¤Ã¤Æ¤³¤Ê¤¯¤Ê¤Ã¤¿¤Î¤ÇËþ­¤·¤Þ¤¹¤¬¡¢
             ¤½¤ì¤â¥µ¡¼¥Ð¤¬Àܳ¤òÀڤ俤³¤È¤òÃΤë¤Þ¤Ç¤Ç¤¹¡£
           </para>
 
           <para>
             ¤³¤Î»öÂ֤ϡ¢°Ê²¼¤Î¹Ô¤ò
             <filename>ppp.conf</filename>
             ¤ÎÃæ¤Ë½ñ¤¤¤Æ¡¢
             Áê¼ê¤¬¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò³«»Ï¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë»ö¤Ë¤è¤Ã¤Æ²óÈò¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <programlisting>set openmode passive</programlisting>
 
           <para>
             ¤³¤ì¤Ç <command>ppp</command> ¤Ï¥µ¡¼¥Ð¤¬
             <acronym>LCP</acronym>
             ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤òµ¯¤³¤¹¤Î¤òÂԤĤ褦¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¤·¤«¤·¡¢
             ¼«Ê¬¤«¤é¤Ï·è¤·¤Æ¥Í¥´¥¸¥§¡¼¥·¥ç¥ó¤òµ¯¤³¤µ¤Ê¤¤¥µ¡¼¥Ð¤â¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ¤â¤·¤³¤Î¾õ¶·¤ËÁø¶ø¤·¤¿¾ì¹ç¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>set openmode active 3</programlisting>
 
           <para>
             ¤³¤ì¤Ë¤è¤Ã¤Æ <command>ppp</command> ¤Ï 3 ÉôÖ
             passive ¥â¡¼¥É¤ò³¤±¤¿¸å¤Ç¡¢
             <acronym>LCP</acronym> ¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ê»Ï¤á¤Þ¤¹¡£
             ¤³¤Î´Ö¤ËÁê¼ê¤¬¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ê»Ï¤á¤¿¾ì¹ç¤Ë¤Ï
             3 ÉôÖÂÔ¤¿¤º¤Ë¤³¤Î¥ê¥¯¥¨¥¹¥È¤Ë¨ºÂ¤Ë±þÅú¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-lcp-constant">
           <para>Àܳ¤¬ÀÚ¤ì¤ë¤Þ¤Ç <acronym>LCP</acronym>
             ¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤¬Â³¤¯¤Î¤Ç¤¹¤¬¡£</para>
         </question>
 
         <answer>
           <para>
             ¸½ºß¤Î <application>ppp</application> ¤Ï¡¢¤Þ¤À
             <acronym>LCP</acronym> ¤ä
             <acronym>CCP</acronym>¡¢
             <acronym>IPCP</acronym>
             ¤ÎÊÖ»ö¤¬¡¢
             ¸µ¤Î¥ê¥¯¥¨¥¹¥È¤ÈÏ¢·È¤·¤Æ¤¯¤ì¤ëµ¡Ç½¤¬¤­¤Á¤ó¤È¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£
             ¤½¤Î·ë²Ì¡¢¤¢¤ë
             <application>ppp</application>
             ¤Î¼ÂÁõ¤¬Áê¼ê¤è¤ê¤â 6 ÉðʾåÃÙ¤¤¾ì¹ç¤Ë¤Ï¡¢
             <acronym>LCP</acronym> ÀßÄê¤Î¥ê¥¯¥¨¥¹¥È¤ò¤µ¤é¤Ë 2 ²óÁ÷¤ê¤Þ¤¹¡£
             ¤³¤ì¤ÏÃ×̿Ū¤Êʪ¤Ç¤¹¡£
           </para>
 
           <para>
             <hostid>A</hostid> ¤È <hostid>B</hostid>¤È¤¤¤¦
             2 ¤Ä¤Î¼ÂÁõ¤ò¹Í¤¨¤Æ¤ß¤Þ¤·¤ç¤¦¡£
             <hostid>A</hostid> ¤¬Àܳ¤Îľ¸å¤Ë
             <acronym>LCP</acronym> ¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ê¡¢
             °ìÊý <hostid>B</hostid> ¤ÎÊý¤Ï¥¹¥¿¡¼¥È¤¹¤ë¤Î¤Ë
             7 É䫤«¤Ã¤¿¤È¤·¤Þ¤¹¡£<hostid>B</hostid> ¤¬¥¹¥¿¡¼¥È¤¹¤ë»þ¤Ë¤Ï
             <hostid>A</hostid> ¤Ï <acronym>LCP</acronym>
             ¥ê¥¯¥¨¥¹¥È¤ò 3 ²óÁ÷¤Ã¤Æ¤·¤Þ¤Ã¤Æ¤¤¤Þ¤¹¡£
             Á°¤ÎÀá¤Ç½Ò¤Ù¤¿ magic number ¤ÎÌäÂ꤬µ¯¤­¤Ê¤¤¤è¤¦¡¢
             <literal>ECHO</literal> ¤Ï <literal>off</literal> ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£
             <hostid>B</hostid> ¤Ï <acronym>REQ</acronym> ¤òÁ÷¤ê¤Þ¤¹¡£
             ¤¹¤ë¤È¤³¤ì¤Ï <hostid>A</hostid> ¤Î <acronym>REQ</acronym> ¤Î¤¦¤Á¡¢
             ºÇ½é¤Îʪ¤ËÂФ¹¤ë <acronym>ACK</acronym> ¤È¤Ê¤ê¤Þ¤¹¡£
             ·ë²Ì¤È¤·¤Æ¡¢<hostid>A</hostid>
             ¤Ï <acronym>OPENED</acronym>
             ¤Î¾õÂÖ¤ËÆþ¤ê¡¢
             <hostid>B</hostid>
             ¤ËÂФ·¤Æ (ºÇ½é¤Î) <acronym>ACK</acronym> ¤òÁ÷¤ê¤Þ¤¹¡£
             ¤½¤Î¤¦¤Á¤Ë
             <hostid>B</hostid> ¤Ï¡¢<hostid>B</hostid>
             ¤¬¥¹¥¿¡¼¥È¤¹¤ëÁ°¤Ë
             <hostid>A</hostid>
             ¤«¤éÁ÷¤é¤ì¤¿¤â¤¦ 2 ¤Ä¤Î
             <acronym>REQ</acronym> ¤ËÂФ¹¤ë
             <acronym>ACK</acronym> ¤òÁ÷¤êÊÖ¤·¤Þ¤¹¡£
             <hostid>B</hostid> ¤Ï <hostid>A</hostid>
             ¤«¤é¤ÎºÇ½é¤Î
             <acronym>ACK</acronym> ¤ò¼õ¤±¼è¤ê
             <acronym>OPENED</acronym> ¤Î¾õÂÖ¤ËÆþ¤ê¤Þ¤¹¡£
             <hostid>A</hostid> ¤Ï <hostid>B</hostid> ¤«¤é¤Î
             2 ¤ÄÌܤΠ<acronym>ACK</acronym>
             ¤ò¼õ¤±¼è¤ê¤Þ¤¹¤Î¤Ç¡¢
             <acronym>REQ-SENT</acronym>¤Î¾õÂÖ¤ËÌá¤ê¡¢
             ¤µ¤é¤Ë¡¢RFC ¤Î¤È¤ª¤ê¤Ë (4 ¤ÄÌܤÎ) <acronym>REQ</acronym>
             ¤òÁ÷¤ê¤Þ¤¹¡£¤½¤·¤Æ 3 ¤ÄÌܤÎ
             <acronym>ACK</acronym>
             ¤ò¼õ¤±¼è¤Ã¤Æ
             <acronym>OPENED</acronym> ¾õÂÖ¤ËÆþ¤ê¤Þ¤¹¡£
             °ìÊý¡¢<hostid>B</hostid> ¤Ï <hostid>A</hostid>
             ¤«¤é¤Î 4 ¤ÄÌܤÎ
             <acronym>REQ</acronym>
             ¤ò¼õ¤±¼è¤ê¤Þ¤¹¤Î¤Ç¡¢
             <acronym>ACK-SENT</acronym>
             ¤Î¾õÂÖ¤ËÆþ¤ê¡¢2 ¤ÄÌܤÎ
             <acronym>REQ</acronym>
             ¤È 4 ¤ÄÌܤÎ
             <acronym>ACK</acronym> ¤ò
             RFC ¤Î¤È¤ª¤ê¤ËÁ÷¤ê¤Þ¤¹¡£
             <hostid>A</hostid>¤Ï¡¢
             <acronym>REQ</acronym>
             ¤ò¼õ¤±¤È¤ë¤È
             <acronym>REQ-SENT</acronym>
             ¤Î¾õÂ֤ˤʤꡢ¤µ¤é¤Ë
             <acronym>REQ</acronym>
             ¤òÁ÷¤ê¤Þ¤¹¡£
             ¤½¤·¤Æ¤¹¤°¤Ë
             <acronym>ACK</acronym> ¤ò¼õ¤±¼è¤Ã¤Æ
             <acronym>OPENED</acronym>
             ¤Î¾õÂÖ¤ËÆþ¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ì¤¬¡¢ÊÒÊý¤Î
             <command>ppp</command>
             ¤¬¤¢¤­¤é¤á¤Æ¤·¤Þ¤¦¤Þ¤Ç³¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¤³¤ì¤ò²óÈò¤¹¤ëºÇ¤âÎɤ¤ÊýË¡¤Ï¡¢
             ÊÒÊý¤ò
             <literal>passive</literal>
             ¥â¡¼¥É¤ËÀßÄꤹ¤ë¡¢
             ¤¹¤Ê¤ï¤ÁÈ¿ÂЦ¤¬¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò³«»Ï¤¹¤ë¤Þ¤ÇÂԤĤ褦¤Ë¤¹¤ë»ö¤Ç¤¹¡£
             ¤³¤ì¤Ï¡¢
           </para>
 
             <programlisting>set openmode passive</programlisting>
 
           <para>
             ¤È¤¤¤¦¥³¥Þ¥ó¥É¤Ç¤Ç¤­¤Þ¤¹¡£
             ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ïµ¤¤òÉÕ¤±¤Æ»È¤ï¤Ê¤¤¤È¤¤¤±¤Þ¤»¤ó¡£¤µ¤é¤Ë
           </para>
 
             <programlisting>set stopped <replaceable>N</replaceable></programlisting>
 
           <para>
             ¤È¤¤¤¦¥³¥Þ¥ó¥É¤òÄɲ䷤ơ¢
             <application>ppp</application> ¤¬¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤¬³«»Ï¤¹¤ë¤Þ¤ÇÂÔ¤Ä
             ºÇÂç¤Î»þ´Ö¤òÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£¤â¤·¤¯¤Ï¡¢
           </para>
 
             <programlisting>set openmode active <replaceable>N</replaceable></programlisting>
 
           <para>
             ¤È¤¤¤¦¥³¥Þ¥ó¥É (¤³¤³¤Ç¡¢
             <replaceable>N</replaceable>
             ¤Ï¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤¬»Ï¤Þ¤ë¤Þ¤ÇÂԤĻþ´Ö) ¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
             ¾Ü¤·¤¯¤Ï¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-lockups">
           <para>ppp ¤¬Àܳľ¸å¤Ë¸Ç¤Þ¤Ã¤Æ¤·¤Þ¤¦</para>
         </question>
 
         <answer>
           <para>
             2.2.5 ¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Î FreeBSD ¤Ç¤Ï¡¢<application>ppp</application>
             ¤¬ Predictor1 °µ½Ì¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò¸í¤Ã¤Æ²ò¼á¤·¤Æ¡¢
             Àܳľ¸å¤Ë¥ê¥ó¥¯¤ò̵¸ú¤Ë¤·¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤Ïξ¥µ¥¤¥É¤¬°Û¤Ê¤ë
             <acronym>Compression Control Protocols (CCP)</acronym>
             ¤ò»È¤Ã¤Æ¥Í¥´¥¸¥§¡¼¥·¥ç¥ó¤ò¹Ô¤Ã¤¿¾ì¹ç¤Ë¤Î¤ßȯÀ¸¤·¤Þ¤¹¡£
             ¤³¤ÎÌäÂê¤Ï¸½ºß¤Ï²ò·è¤·¤Æ¤¤¤Þ¤¹¤¬¡¢¤¢¤Ê¤¿¤ÎÁö¤é¤»¤Æ¤¤¤ë
             <application>ppp</application>
             ¤Î¥Ð¡¼¥¸¥ç¥ó¤¬¸Å¤¤¾ì¹ç¤Ç¤â¡¢¼¡¤ÎÌ¿Îá¤Ç²ò·è¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
           <programlisting>disable pred1</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-shell-test-lockup">
           <para><command>ppp</command> ¤ÎÆâÉô¤Ç¥·¥§¥ë¤òµ¯Æ°¤·¤è¤¦¤È¤¹¤ë¤È¸Ç¤Þ¤Ã¤Æ¤·¤Þ¤¦</para>
         </question>
 
         <answer>
           <para>
             <command>shell</command> ¤¢¤ë¤¤¤Ï
             <command>!</command>
             ¥³¥Þ¥ó¥É¤ò»ÈÍѤ¹¤ë¤È¡¢
             <application>ppp</application>
             ¤Ï¥·¥§¥ë¤òµ¯Æ°¤· (²¿¤«°ú¿ô¤òÅϤ·¤¿¾ì¹ç¤Ï¡¢
             <application>ppp</application>
             ¤Ï°ú¿ô¤â¼Â¹Ô¤·¤Þ¤¹)¡¢
             ¥³¥Þ¥ó¥É¤¬½ªÎ»¤¹¤ë¤Þ¤Ç½èÍý¤òÃæÃǤ·¤Þ¤¹¡£
             ¥³¥Þ¥ó¥É¤ò¼Â¹ÔÃæ¤Ë <application>ppp</application>
             ¤Î¥ê¥ó¥¯¤ò»È¤ª¤¦¤È¤¹¤ë¤È¡¢
             ¥ê¥ó¥¯¤¬¸Ç¤Þ¤Ã¤Æ¤¤¤ë¤è¤¦¤Ë¸«¤¨¤Þ¤¹¤¬¡¢
             ¤³¤ì¤Ï <application>ppp</application> ¤¬¥³¥Þ¥ó¥É¤Î½ªÎ»¤òÂԤäƤ¤¤ë¤«¤é¤Ç¤¹¡£
           </para>
 
           <para>
             ¤³¤Î¤è¤¦¤Ê¾ì¹ç¤Ï¡¢Âå¤ï¤ê¤Ë
             <command>!bg</command>
             ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
             Í¿¤¨¤é¤ì¤¿¥³¥Þ¥ó¥É¤¬¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ç¼Â¹Ô¤µ¤ì¤ë¤Î¤Ç¡¢
             <command>ppp</command>
             ¤Ï¥ê¥ó¥¯¤Ë´Ø¤¹¤ë¥µ¡¼¥Ó¥¹¤ò·Ñ³¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-nullmodem">
           <para>¥Ì¥ë¥â¥Ç¥à¥±¡¼¥Ö¥ë¤ò»ÈÍѤ·¤Æ¤¤¤ë¤È¤­¡¢
             <command>ppp</command> ¤¬½ªÎ»¤·¤Ê¤¤</para>
         </question>
 
         <answer>
           <para>
             ¥Ì¥ë¥â¥Ç¥à¥±¡¼¥Ö¥ë¤ò»ÈÍѤ·¤ÆľÀÜÀܳ¤·¤Æ¤¤¤ë¾ì¹ç¡¢
             <application>ppp</application>
             ¤Ï¼«Æ°Åª¤Ë¤ÏÀܳ¤Î½ªÎ»¤òÃΤ뤳¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£
             ¤³¤ì¤Ï¥Ì¥ë¥â¥Ç¥à¥·¥ê¥¢¥ë¥±¡¼¥Ö¥ë¤ÎÇÛÀþ¤Ëµ¯°ø¤·¤Æ¤¤¤Þ¤¹¡£
             ¤³¤Î¼ï¤ÎÀܳ·ÁÂÖ¤òÍѤ¤¤ë¾ì¹ç¤Ï¡¢
             °Ê²¼¤ÎÌ¿Îá¤òÍѤ¤¤Æ <acronym>LQR</acronym>
             ¤ò¾ï¤ËÍ­¸ú¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>enable lqr</programlisting>
 
           <para>
             ¤³¤¦¤¹¤ë¤È¡¢ÀܳÀ褬¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò¹Ô¤¦¾ì¹ç¡¢¥Ç¥Õ¥©¥ë¥È¤Ç
             <acronym>LQR</acronym> ¤Î»ÈÍѤò¼õ¤±Æþ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-auto-noreasondial">
           <para><command>ppp</command> ¤ò
             <option>-auto</option> ¥â¡¼¥É¤ÇÆ°¤«¤¹¤È¡¢
             ¾¡¼ê¤Ë¥À¥¤¥¢¥ë¤¹¤ë¤³¤È¤¬¤¢¤ë</para>
         </question>
 
         <answer>
           <para>
             <application>ppp</application>
             ¤¬»×¤¤¤â¤·¤Ê¤¤¤È¤­¤Ë¥À¥¤¥¢¥ë¤ò»Ï¤á¤ë¾ì¹ç¡¢¤½¤Î¸¶°ø¤òÆͤ­»ß¤á¡¢
             ËɻߤΤ¿¤á¤Ë¥À¥¤¥ä¥ë¥Õ¥£¥ë¥¿ (dfilters) ¤ò¤«¤±¤Æ¤ä¤ë
             ɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¸¶°ø¤òÆͤ­»ß¤á¤ë¤¿¤á¤Ë¤Ï¡¢°Ê²¼¤ÎÌ¿Îá¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>set log +tcp/ip</programlisting>
 
           <para>
             ¤³¤ì¤ÇÀܳ¤òÄ̲᤹¤ë¤¹¤Ù¤Æ¤Î¥È¥é¥Õ¥£¥Ã¥¯¤ò¥í¥°¤Ë»Ä¤¹¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
             ¼¡¤ËÆÍÁ³²óÀþ¤¬¤Ä¤Ê¤¬¤Ã¤¿¤È¤­¤Î¥í¥°¤Î¥¿¥¤¥à¥¹¥¿¥ó¥×¤ò¤¿¤É¤ì¤Ð¡¢
             ¸¶°ø¤òÆͤ­»ß¤á¤ë¤³¤È¤¬¤Ç¤­¤ë¤Ï¤º¤Ç¤¹¡£
           </para>
 
           <para>
             ¸¶°ø¤¬¤ï¤«¤Ã¤¿¤é¡¢¼¡¤Ë¡¢¤³¤Î¤è¤¦¤Ê¾õ¶·¤Ç¤Ï¥À¥¤¥ä¥ë¤¬µ¯¤³¤é¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤·¤ç¤¦¡£
             Ä̾¤³¤Î¼ê¤ÎÌäÂê¤Ï¡¢<acronym>DNS</acronym>
             ¤Ç̾Á°¤Î²ò·è¤ò¤·¤è¤¦¤È¤·¤¿¤¿¤á¤Ëµ¯¤³¤ê¤Þ¤¹¡£
             <acronym>DNS</acronym> ¤Ë¤è¤ë̾Á°¤Î²ò·è¤Ë¤è¤Ã¤Æ¡¢
             Àܳ¤¬¹Ô¤ï¤ì¤ë¤Î¤òËɻߤ¹¤ë¤Ë¤Ï¡¢
             ¼¡¤Î¤è¤¦¤Ê¼êÃʤòÍѤ¤¤Þ¤¹ (¤³¤ì¤Ï <application>ppp</application>
             ¤Î´û¤Ë³ÎΩ¤·¤¿Àܳ¤Ë´Ø¤·¤Æ¥Ñ¥±¥Ã¥È¤Î¥Õ¥£¥ë¥¿¥ê¥ó¥°¤ò¤¹¤ë¤â¤Î¤Ç¤Ï<emphasis>¤¢¤ê¤Þ¤»¤ó</emphasis>)¡£
           </para>
 
           <programlisting>set dfilter 1 deny udp src eq 53
 set dfilter 2 deny udp dst eq 53
 set dfilter 3 permit 0/0 0/0</programlisting>
 
           <para>
             ¤³¤ì¤Ï¥Ç¥Þ¥ó¥É¥À¥¤¥ä¥ëµ¡Ç½¤ËÌäÂê¤òÀ¸¤¸¤µ¤»¤ë¤¿¤á¡¢
             ¾ï¤ËŬÀڤǤ¢¤ë¤È¤Ï¤«¤®¤ê¤Þ¤»¤ó¡£
             ¤Û¤È¤ó¤É¤Î¥×¥í¥°¥é¥à¤Ï¾¤Î¥Í¥Ã¥È¥ï¡¼¥¯´ØÏ¢¤Î½èÍý¤ò¹Ô¤Ê¤¦Á°¤Ë
             <acronym>DNS</acronym>
             ¤Ø¤ÎÌ䤤¹ç¤ï¤»¤¬É¬Íפˤʤê¤Þ¤¹¡£
           </para>
 
           <para>
             <acronym>DNS</acronym> ¤Î¾ì¹ç¤Ï¡¢
             ²¿¤¬¼ÂºÝ¤Ë¥Û¥¹¥È̾¤ò¸¡º÷¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤Î¤«¤òÆͤ­»ß¤á¤ë¤Ù¤­¤Ç¤·¤ç¤¦¡£
             ÂçÄñ¤Î¾ì¹ç¤Ï¡¢
             &man.sendmail.8;
             ¤¬ÈȿͤǤ¹¡£
             ÀßÄê¥Õ¥¡¥¤¥ë¤Ç sendmail ¤¬
             <acronym>DNS</acronym> ¤ËÌ䤤¹ç¤ï¤»¤Ê¤¤¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤«³Îǧ¤¹¤Ù¤­¤Ç¤¹¡£
             ¼«Ê¬ÍѤÎÀßÄê¥Õ¥¡¥¤¥ë¤òºîÀ®¤¹¤ë¤¿¤á¤Î¾Ü¤·¤¤ÊýË¡¤Ï¡¢
             <link linkend="ispmail">¥á¡¼¥ë¤ÎÀßÄê</link> ¤Î¹à¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
             ¤Þ¤¿¤Ï¡¢
             <filename>.mc</filename>
             ¥Õ¥¡¥¤¥ë¤Ë¼¡¤Î¤è¤¦¤Ê¹Ô¤òÄɲ䷤Ƥâ¤è¤¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <programlisting>define(`confDELIVERY_MODE', `d')dnl</programlisting>
 
           <para>
             ¤³¤Î¹Ô¤òÄɲ乤ë¤È¡¢sendmail
             ¤Ï¥á¡¼¥ë¥­¥å¡¼¤ò½èÍý¤¹¤ë (Ä̾ï
             sendmail ¤Ï 30 ʬ¤´¤È¤Ë¥­¥å¡¼¤ò½èÍý¤¹¤ë¤è¤¦¡¢
             <quote><option>-bd -q30m</option></quote>
             ¤È¤¤¤¦¥ª¥×¥·¥ç¥ó¤òÉÕ¤±¤Æµ¯Æ°¤µ¤ì¤Þ¤¹) ¤Þ¤Ç¤«¡¢
             ¤Þ¤¿¤Ï (¿ʬ <filename>ppp.linkup</filename> ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤ÎÃæ¤Ç)
             <quote><command>sendmail -q</command></quote>
             ¤È¤¤¤¦¥³¥Þ¥ó¥É¤¬¼Â¹Ô¤µ¤ì¤ë¤Þ¤Ç¡¢
             ¤¹¤Ù¤Æ¤Î¥á¡¼¥ë¤ò¥­¥å¡¼¤Ëί¤á¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
             <note>
               <title>ÌõÃí</title>
               <para>
                 <quote><command>sendmail -q</command></quote>
                 ¤Ï¤½¤Î»þÅÀ¤Î¥á¡¼¥ë¥­¥å¡¼¤ÎÆâÍƤò½èÍý¤·¤Æ½ªÎ»¤·¤Þ¤¹¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ccp-errors">
           <para><acronym>CCP</acronym>
             ¥¨¥é¡¼¤È¤Ï¤É¤¦¤¤¤¦°ÕÌ£¤Ç¤¹¤«</para>
         </question>
 
         <answer>
           <para>
             ¥í¥°¥Õ¥¡¥¤¥ëÃæ¤Î°Ê²¼¤Î¥¨¥é¡¼¤Ï¡¢
           </para>
 
             <programlisting>CCP: CcpSendConfigReq
 CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
 
           <para>
             ¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Ë¤ª¤¤¤Æ <command>ppp</command> ¤Ï
             Predictor1 °µ½Ì¤òÍѤ¤¤ë¤Ù¤¯¼çÄ¥¤·¤¿¤Î¤ËÂФ·¤Æ¡¢
             ÀܳÀè¤Ï°µ½Ì¤ò»ÈÍѤ·¤Ê¤¤¤³¤È¤ò¼çÄ¥¤·¤¿¾ì¹ç¤Ëµ¯¤³¤ê¤Þ¤¹¡£
             ¤³¤Î¥á¥Ã¥»¡¼¥¸¤Ë¤Ï²¿¤Î³²¤â¤¢¤ê¤Þ¤»¤ó¤¬¡¢
             ½Ð¤ë¤Î¤¬·ù¤Ê¤é¡¢°Ê²¼¤ÎÌ¿Îá¤òÍѤ¤¤Æ¤³¤Á¤é¦¤Ç¤â
             Predictor1 °µ½Ì¤ò̵¸ú¤Ë¤¹¤ë¤³¤È¤ÇÂбþ¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <programlisting>disable pred1</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-lockup-ioerrors">
           <para>¥Õ¥¡¥¤¥ëžÁ÷¤ÎÅÓÃæ¤Ç¡¢<command>ppp</command> ¤¬
             IO ¥¨¥é¡¼¤ò½Ð¤·¤Æ¸Ç¤Þ¤Ã¤Æ¤·¤Þ¤¦</para>
         </question>
 
         <answer>
 
           <para>
             FreeBSD 2.2.2 °ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Î <devicename>tun</devicename>
             ¥É¥é¥¤¥Ð¤Ë¤Ï¡¢<devicename>tun</devicename>
             ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Î <acronym>MTU</acronym>
             ¤Î¥µ¥¤¥º¤è¤êÂ礭¤Ê¥Ñ¥±¥Ã¥È¤ò¼õ¤±¼è¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤È¤¤¤¦¥Ð¥°¤¬¤¢¤ê¤Þ¤·¤¿¡£
             <acronym>MTU</acronym>
             ¤Î¥µ¥¤¥º¤è¤êÂ礭¤Ê¥Ñ¥±¥Ã¥È¤ò¼õ¤±ÉÕ¤±¤ë¤È IO ¥¨¥é¡¼¤¬µ¯¤³¤ê¡¢
             <command>syslogd</command> ·Ðͳ¤Çµ­Ï¿¤µ¤ì¤ë¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             <command>ppp</command> ¤Î»ÅÍͤǤϡ¢
             <acronym>LCP</acronym>
             ¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò¹Ô¤¦¾ì¹ç¤ò´Þ¤à<emphasis>¤É¤Î¤è¤¦¤Ê¾ì¹ç¤Ç¤â</emphasis>ºÇÄã
             1500 ¥ª¥¯¥Æ¥Ã¥È¤Î
             Maximum Receive Unit (<acronym>MRU</acronym>)
             ¤ò¼õ¤±Æþ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤Ç¤¹¤«¤é¡¢<acronym>MTU</acronym> ¤ò
             1500 °Ê²¼¤ËÀßÄꤷ¤¿¾ì¹ç¤Ç¤â¡¢ISP ¤Ï¤½¤ì¤Ë´Ø·¸¤Ê¤¯
             1500 ¤ÎÂ礭¤µ¤Î¥Ñ¥±¥Ã¥È¤òÁ÷¤Ã¤Æ¤¯¤ë¤Ç¤·¤ç¤¦¡£
             ¤½¤·¤Æ¤³¤Î¥¤¥±¤Æ¤Ê¤¤µ¡Ç½¤Ë¤Ö¤Á¤¢¤¿¤Ã¤Æ¡¢
             ¥ê¥ó¥¯¤¬¸Ç¤Þ¤ë¤Î¤òÌܤˤ¹¤ë¤³¤È¤Ë¤Ê¤ë¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             FreeBSD 2.2.2 °ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢<acronym>MTU</acronym>
             ¤ò·è¤·¤Æ 1500 ¤è¤ê¾®¤µ¤¯¤·¤Ê¤¤¤³¤È¤Ç¡¢
             ¤³¤ÎÌäÂê¤ò²óÈò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-connectionspeed">
           <para>¤É¤¦¤·¤Æ <command>ppp</command>
             ¤ÏÀܳ®ÅÙ¤ò¥í¥°¤Ë»Ä¤µ¤Ê¤¤¤ó¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>
             ¥â¥Ç¥à¤È¤Î¡Ö¤ä¤ê¼è¤ê¡×¤¹¤Ù¤Æ¤Î¹Ô¤ò¥í¥°¤Ë»Ä¤¹¤Ë¤Ï¡¢
             °Ê²¼¤Î¤è¤¦¤Ë¤·¤ÆÀܳ®ÅÙ¤Î¥í¥°¤ÎÍ­¸ú²½¤ò¹Ô¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>set log +connect</programlisting>
 
           <para>¤³¤ì¤Ï
             &man.ppp.8;
             ¤ËºÇ¸å¤Ë¤¯¤ë¤³¤È¤¬Í׵ᤵ¤ì¤Æ¤¤¤ë
             <quote><literal>expect</literal></quote>
             ¤È¤¤¤¦Ê¸»úÎ󤬤¯¤ë¤Þ¤Ç¤Î¤¹¤Ù¤Æ¤Î¤â¤Î¤ò¥í¥°¤Ëµ­Ï¿¤µ¤»¤Þ¤¹¡£
           </para>
 
           <para>
             Àܳ®ÅÙ¤Ï¥í¥°¤Ë¤È¤ê¤¿¤¤¤±¤ì¤É¡¢<acronym>PAP</acronym>
             ¤ä <acronym>CHAP</acronym>
             ¤ò»È¤Ã¤Æ¤¤¤ë (¤½¤Î·ë²Ì¡¢¥À¥¤¥ä¥ë¥¹¥¯¥ê¥×¥ÈÃæ¤Î
             <literal>CONNECT</literal>
             °Ê¹ß¤ËÁ´¤¯¡Ö¤ä¤ê¤È¤ê¡×¤ò¹Ô¤ï¤Ê¤¤ -
             <quote><literal>set login</literal></quote>
             ¥¹¥¯¥ê¥×¥È¤Ë¤Ï²¿¤â½ñ¤«¤Ê¤¤) ¤Î¤Ç¤¢¤ì¤Ð¡¢
             <application>ppp</application> ¤Ë
             <quote><literal>expect</literal></quote>
             ¤ò´Þ¤ó¤À <literal>CONNECT</literal>
             ¹Ô¤¹¤Ù¤Æ¤¬¤¯¤ë¤Þ¤ÇÂÔ¤¿¤»¤ë¤è¤¦¤Ë¤·¤Ê¤¤¤È¤¤¤±¤Þ¤»¤ó¡¢
             °Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 4 \"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n"</programlisting>
 
           <para>
             ¤³¤³¤Ç¡¢<literal>CONNECT</literal> ¤ò¼õ¿®¤·¤Æ¤«¤é¡¢
             ²¿¤âÁ÷¤é¤º¡¢Éüµ¢²þ¹Ô (linefeed) ¤òÂԤäƤ¤¤Þ¤¹¡¢
             <application>ppp</application> ¤Ë <literal>CONNECT</literal>
             ¤Î±þÅú¤¹¤Ù¤Æ¤òÆɤ߹þ¤Þ¤»¤Æ¤¤¤ë¤ï¤±¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-ignores-backslash">
           <para>»ä¤Î <literal>chat</literal> ¥¹¥¯¥ê¥×¥È¤Ç¤Ï
             <quote><literal>\</literal></quote>
             ¤È¤¤¤¦Ê¸»ú¤ò <command>PPP</command> ¤¬²ò¼á¤·¤Æ¤¯¤ì¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             <command>PPP</command> ¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤à¤È¤­¤Ë¡¢
             <literal>set phone "123 456 789"</literal>
             ¤Î¤è¤¦¤Êʸ»úÎó¤òÀµ¤·¤¯²ò¼á¤·¡¢
             Èֹ椬¼ÂºÝ¤Ë<emphasis>1 ¤Ä¤Î</emphasis>°ú¿ô¤Ç¤¢¤ë¤ÈÍý²ò¤·¤Þ¤¹¡£
             <quote>&quot;</quote>
             ¤È¤¤¤¦Ê¸»ú¤ò»ØÄꤹ¤ë¤Ë¤Ï¡¢¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å (backslash;
             <quote><literal>\</literal></quote>) ¤Ç¥¨¥¹¥±¡¼¥×¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
           </para>
 
           <para>
             <literal>chat</literal> ¤Î³Æ°ú¿ô¤¬²ò¼á¤µ¤ì¤ë¤È¤­¤Ë¤Ï¡¢
             <quote><literal>\P</literal></quote>
             ¤ä
             <quote><literal>\T</literal></quote>
             ¤Î¤è¤¦¤ÊÆÃÊ̤ʥ¨¥¹¥±¡¼¥×¥·¡¼¥±¥ó¥¹ (¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸»²¾È¤Î¤³¤È) ¤ò¸«ÉÕ¤±¤ë¤¿¤á¤Ë¡¢
             ¤â¤¦ 1 ²ó¡¢»ú¶ç²òÀϤò¹Ô¤¤¤Þ¤¹¡£
             ¤³¤Î¤è¤¦¤Ë»ú¶ç²òÀÏ¤Ï 2 ²ó·«¤êÊÖ¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢
             Àµ¤·¤¤²ó¿ô¤À¤±¥¨¥¹¥±¡¼¥×½èÍý¤ò¹Ô¤ï¤Ê¤¤¤È¤¤¤±¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¥â¥Ç¥à¤Ë¤¿¤È¤¨¤Ð <quote><literal>\</literal></quote>
             ¤Î¤è¤¦¤Êʸ»ú¤òÁ÷¤ê¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢
             ¼¡¤Î¤è¤¦¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
           <programlisting>set dial "\"\" ATZ OK-ATZ-OK AT\\\\X OK"</programlisting>
 
           <para>
             ¼ÂºÝ¤Ë¥â¥Ç¥à¤ËÁ÷¤é¤ì¤ëʸ»úÎó¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>ATZ
 OK
 AT\X
 OK</programlisting>
 
           <para>
             ¾¤ÎÎã¤Ç¤¹¤È
           </para>
 
             <programlisting>set phone 1234567
               set dial "\"\" ATZ OK ATDT\\T"</programlisting>
 
           <para>
             ¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
             <programlisting>ATZ
 OK
 ATDT1234567</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-segfault-nocore">
           <para><command>ppp</command> ¤¬
             <computeroutput>segmentation fault</computeroutput> ¤Ë¤Ê¤ë¤Î¤Ç¤¹¤¬¡¢
             <filename>ppp.core</filename> ¥Õ¥¡¥¤¥ë¤¬¤¢¤ê¤Þ¤»¤ó</para>
         </question>
 
         <answer>
           <para>
             <application>ppp</application> (¤ä¾¤Î¥×¥í¥°¥é¥à) ¤Ï·è¤·¤Æ
             core ¤òÅǤ¤¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
             <application>ppp</application>
             ¤Ï¼Â¸ú uid ¤¬ 0 ¤ÇÆ°¤¤¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢
             ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ï <application>ppp</application>
             ¤ò½ªÎ»¤µ¤»¤ëÁ°¤Ë¥Ç¥£¥¹¥¯¤Ë core ¥¤¥á¡¼¥¸¤ò½ñ¤­¹þ¤ß¤Þ¤»¤ó¡£
             ¤·¤«¤· <application>ppp</application>
             ¤Ï¼ÂºÝ¤Ë¤Ï¥»¥°¥á¥ó¥Æ¡¼¥·¥ç¥ó°ãÈ¿¤ä¡¢
             ¾¤Î core ¤òÅǤ¯¸¶°ø¤È¤Ê¤ë¤è¤¦¤Ê¥·¥°¥Ê¥ë¤Ë¤è¤Ã¤Æ½ªÎ»¤·¤Æ¤ª¤ê¡¢
             <emphasis>¤µ¤é¤Ë</emphasis>ºÇ¿·¤Î¥Ð¡¼¥¸¥ç¥ó
             (¤³¤Î¥»¥¯¥·¥ç¥ó¤Î»Ï¤á¤ò¸«¤Æ¤¯¤À¤µ¤¤)
             ¤ò»ÈÍѤ·¤Æ¤¤¤ë¤Ê¤é¤Ð¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.user; <userinput>tar xfz ppp-*.src.tar.gz</userinput>
 &prompt.user; <userinput>cd ppp*/ppp</userinput>
 &prompt.user; <userinput>echo STRIP= &gt;&gt;Makefile</userinput>
 &prompt.user; <userinput>echo CFLAGS+=-g &gt;&gt;Makefile</userinput>
 &prompt.user; <userinput>make clean all</userinput>
 &prompt.user; <userinput>su</userinput>
 &prompt.root; <userinput>make install</userinput>
 &prompt.root; <userinput>chmod 555 /usr/sbin/ppp</userinput></screen>
 
           <para>
             ¤³¤ì¤Ç¥Ç¥Ð¥Ã¥°²Äǽ¤Ê¥Ð¡¼¥¸¥ç¥ó¤Î
             <application>ppp</application> ¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£
             <username>root</username> ¤Ç
             <application>ppp</application> ¤ò¼Â¹Ô¤·¡¢
             ¤¹¤Ù¤Æ¤ÎÆø¢¤¬Ìµ¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤è¤¦¤Ë¤¹¤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£
             <application>ppp</application> ¤ò¼Â¹Ô¤¹¤ë»þ¤Ë¤Ï¡¢
             ¥«¥ì¥ó¥È¥Ç¥£¥ì¥¯¥È¥ê¤¬ <command>make</command>
             ¤·¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¢¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤³¤ì¤Ç¡¢<application>ppp</application>
             ¤¬¥»¥°¥á¥ó¥Æ¡¼¥·¥ç¥óÎã³°¤ò¼õ¤±¼è¤Ã¤¿¤È¤­¤Ë¤Ï
             <filename>ppp.core</filename>
             ¤È¤¤¤¦Ì¾Á°¤Î
             core ¥Õ¥¡¥¤¥ë¤òÅǤ¯¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£core ¤¬
             ÅǤ«¤ì¤¿¤é¼¡¤Î¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.user; <userinput>su</userinput>
 &prompt.root; <userinput>gdb /usr/sbin/ppp ppp.core</userinput>
 <prompt>(gdb)</prompt> <userinput>bt</userinput>
 .....
 <prompt>(gdb)</prompt> <userinput>f 0</userinput>
 ....
 <prompt>(gdb)</prompt> <userinput>i args</userinput>
 ....
 <prompt>(gdb)</prompt> <userinput>l</userinput>
 .....</screen>
 
           <para>
             ¼ÁÌ䤹¤ëºÝ¤Ë¤Ï¡¢¤³¤ì¤é¤¹¤Ù¤Æ¤Î¾ðÊó¤òÄ󶡤·¤Æ¡¢
             ÌäÂêÅÀ¤ÎʬÀϤ¬¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             <command>gdb</command>
             ¤Î»È¤¤Êý¤Ë´·¤ì¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢¼ÂºÝ¤Ë dump
             ¤Î¸¶°ø¤È¤Ê¤Ã¤¿Íýͳ¤ä¤½¤Î¥¢¥É¥ì¥¹¡¢
             ´ØÏ¢¤·¤¿ÊÑ¿ô¤ÎÃͤʤɤâÄ´¤Ù¤ë»ö¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-autodialprocess-noconnect">
           <para>auto ¥â¡¼¥É¤Ç¥À¥¤¥¢¥ë¤ò¤¹¤ë¤è¤¦¤Ê¥×¥í¥»¥¹¤¬Àܳ¤µ¤ì¤Ê¤¤¡£
           </para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Ï <application>ppp</application>
             ¤¬¥í¡¼¥«¥ë¦¤Î <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤ò¡¢
             ưŪ¤ËÄÌ¿®Áê¼ê¤È¸ò¾Ä¤¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë»þ¤ËȯÀ¸¤¹¤ëÎɤ¯ÃΤé¤ì¤¿¾ã³²¤Ç¤·¤¿¡£
             ºÇ¿·¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
             ¤³¤ÎÌäÂê¤Ï½¤Àµ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             <literal>iface</literal>
             ¤ò¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤«¤é¸¡º÷¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤³¤ì¤Ï¡¢ºÇ½é¤Î¥×¥í¥°¥é¥à¤¬
             &man.connect.2;
             ¤ò¸Æ¤Ó½Ð¤·¤¿»þ¡¢<devicename>tun</devicename>
             ¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Î <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤¬¡¢
             ¥½¥±¥Ã¥È¤Î½ªÃ¼¤Ë³ä¤êÅö¤Æ¤é¤ì¤Æ¤·¤Þ¤¦¤È¤¤¤¦ÌäÂê¤Ç¤¹¡£
             ¥«¡¼¥Í¥ë¤Ï¡¢
             ³°¤Ø½Ð¤Æ¤¤¤¯ºÇ½é¤Î¥Ñ¥±¥Ã¥È¤òºî¤ê¡¢¤½¤ì¤ò <devicename>tun</devicename>
             ¥Ç¥Ð¥¤¥¹¤Ø½ñ¤­¹þ¤ß¤Þ¤¹¡£
             ¤½¤·¤Æ <application>ppp</application> ¤Ï¡¢
             ¤½¤Î¥Ñ¥±¥Ã¥È¤òÆɤ߹þ¤ó¤ÇÀܳ¤ò³ÎΩ¤·¤Þ¤¹¡£
             <application>ppp</application>
             ¤ÏưŪ¤Ë <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤ò³ä¤êÅö¤Æ¤ë¤¿¤á¡¢
             ¤â¤·¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Î¥¢¥É¥ì¥¹¤¬ÊѲ½¤·¤Æ¤·¤Þ¤¦¤È¡¢
             ºÇ½é¤Ë³ä¤êÅö¤Æ¤é¤ì¤¿¥½¥±¥Ã¥È½ªÃ¼¤Î <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤Ï̵¸ú¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
             ¤½¤Î¤¿¤á¡¢¤½¤ì°Ê¹ßÁê¼ê¤ËÁ÷¤é¤ì¤ë¤¹¤Ù¤Æ¤Î¥Ñ¥±¥Ã¥È¤ÏÄ̾
             Áê¼ê¤ËÆϤ¯¤³¤È¤Ï¤Ê¤¤¤Ç¤·¤ç¤¦¡£¤â¤·²¾¤ËÆϤ¤¤¿¤È¤·¤Æ¤â¡¢
             ´û¤Ë¤³¤Á¤é¤Î <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤ÏÊѹ¹¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢
             ¤É¤ó¤ÊÈ¿±þ¤âºÇ½é¤Î¥Þ¥·¥ó¤Ë¤ÏÌá¤Ã¤Æ¤­¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤³¤ÎÌäÂê¤ËÂн褹¤ëÍýÏÀŪ¤ÊÊýË¡¤¬¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹¡£¤â¤·²Äǽ¤Ê¤é¡¢
             Áê¼ê¤¬ºÆÅÙ¡¢Æ±¤¸ <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤ò³ä¤êÅö¤Æ¤Æ¤¯¤ì¤ë¤³¤È¤¬°ìÈ֤Ǥ¹ <literal>:-)</literal>
             <application>ppp</application>
             ¤Î¸½ºß¤Î¥Ð¡¼¥¸¥ç¥ó¤Ï¤³¤ì¤ò¹Ô¤Ê¤¤¤Þ¤¹¤¬¡¢
             ¾¤Î¤Û¤È¤ó¤É¤Î¼ÂÁõ¤Ï¤½¤¦¤¤¤Ã¤¿Æ°ºî¤ò¤·¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ²æ¡¹¤Î¦¤«¤éÂнè¤Ç¤­¤ëºÇ¤â´Êñ¤ÊÊýË¡¤Ï¡¢<devicename>tun</devicename>
             ¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Î
             <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤ò¸ÇÄꤹ¤ë»ö¤Ç¤¹¡£¤Þ¤¿¤½¤Î¤«¤ï¤ê¤Ë¡¢
             ³°¤Ë½Ð¤Æ¤¤¤¯¥Ñ¥±¥Ã¥È¤òÊѹ¹¤·¤Æ¡¢
             ȯ¿®¸µ <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤ò¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Î <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤«¤é¡¢¸ò¾Ä¤Ë¤è¤Ã¤ÆÆÀ¤é¤ì¤¿ <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤Ë¡¢
             Ŭµ¹½ñ¤­¤«¤¨¤ë»ö¤Ë¤è¤Ã¤Æ¤âÂнè¤Ç¤­¤Þ¤¹¡£
             ¤³¤ì¤Ï¡¢´ðËÜŪ¤Ë
             <application>ppp</application> ¤ÎºÇ¿·¥Ð¡¼¥¸¥ç¥ó¤Ë¤¢¤ë <literal>iface-alias</literal>
             ¥ª¥×¥·¥ç¥ó¤¬¹Ô¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤ÈƱ¤¸¤Ç¤¹
             (&man.libalias.3;
             ¤ª¤è¤Ó¡¢<application>ppp</application> ¤Î <option>-nat</option>
             ¥¹¥¤¥Ã¥Á¤Ë¤â´Ø·¸¤·¤Þ¤¹)¡£¤½¤ì¤Ï¡¢°ÊÁ°¤Î <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤ò¤¹¤Ù¤Æ´ÉÍý¤·¡¢
             ¤½¤ì¤é¤òºÇ¸å¤Î¸ò¾Ä¤Ë¤è¤Ã¤ÆÆÀ¤é¤ì¤¿ <acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤ËÂФ·¤Æ NAT µ¡Ç½¤òÍ­¸ú²½¤·¤Þ¤¹¡£</para>
 
           <para>
             ¤â¤¦ 1 ¤Ä¤Î (¤ª¤½¤é¤¯ºÇ¤â¿®Íê¤Ç¤­¤ë) ÊýË¡¤Ï¡¢bind ¤µ¤ì¤¿
             ¤¹¤Ù¤Æ¤Î¥½¥±¥Ã¥È¤Î <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤ò¡¢
             °Û¤Ê¤ë¤â¤Î¤ËÊѹ¹¤Ç¤­¤ë¥·¥¹¥Æ¥à¥³¡¼¥ë¤ò¼ÂÁõ¤¹¤ë¤³¤È¤Ç¤¹¡£
             <application>ppp</application>¤Ï¡¢
             ¿·¤·¤¤ <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤¬³ä¤êÅö¤Æ¤é¤ì¤¿»þ¡¢
             ¤³¤Î¥·¥¹¥Æ¥à¥³¡¼¥ë¤òÍѤ¤¤Æ¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¥×¥í¥°¥é¥à¤Ë¤¢¤ë¡¢
             ¤¹¤Ù¤Æ¤Î¥½¥±¥Ã¥È¤ò½ñ¤­¤«¤¨¤Æ¤ä¤ë¤ï¤±¤Ç¤¹¡£
             Ʊ¤¸¥·¥¹¥Æ¥à¥³¡¼¥ë¤¬¡¢<acronym>DHCP</acronym> ¥¯¥é¥¤¥¢¥ó¥È¤¬ÍøÍѤ¹¤ë¥½¥±¥Ã¥È¤ò
             ¶¯À©Åª¤ËºÆ bind ¤¹¤ë¤Î¤Ë¤â»È¤¦¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             3 ¤ÄÌܤÎÊýË¡¤Ï¡¢<acronym>IP</acronym>
             ¥¢¥É¥ì¥¹¤ò»ØÄꤷ¤Ê¤¤¤Ç¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤òÍøÍѤǤ­¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ç¤¹¡£
             ³°¤Ë½Ð¤Æ¤¤¤¯¥Ñ¥±¥Ã¥È¤Ï¡¢ºÇ½é¤Î <literal>SIOCAIFADDR</literal>
             ioctl ¤Î´°Î»¤Þ¤Ç¡¢
             255.255.255.255 ¤È¤¤¤¦ <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤¬Í¿¤¨¤é¤ì¤Þ¤¹¡£
             ¤³¤ì¤Ë¤è¤Ã¤Æ¡¢¥½¥±¥Ã¥È¤Ï¾ï¤Ë bind ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ȯ¿®¸µ <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤òÊѹ¹¤¹¤ë¤Î¤Ï
             <application>ppp</application> ¤Î»Å»ö¤Ç¤¹¡£¤¿¤À¤·¡¢
             ¤½¤ì¤Ïȯ¿®¸µ <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤¬
             255.255.255.255 ¤Ë¤Ê¤Ã¤Æ¤¤¤Æ¡¢<acronym>IP</acronym> ¥¢¥É¥ì¥¹¤È
             <acronym>IP</acronym> ¥Á¥§¥Ã¥¯¥µ¥à¤òÊѹ¹¤¹¤ëɬÍפ¬¤¢¤ë¾ì¹ç¤À¤±¤Ç¤¹¡£
             ¤³¤ì¤Ï¡¢¥«¡¼¥Í¥ë¤¬ÉÔŬÀÚ¤ËÀßÄꤵ¤ì¤¿¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Ø¤Ï
             °Û¾ï¤Ê¥Ñ¥±¥Ã¥È¤òÁ÷½Ð¤·¤è¤¦¤È¤¹¤ë¤³¤È¤òÍøÍѤ·¤Æ¡¢¤Ê¤Ë¤«Â¾¤Î
             »ÅÁȤߤ¬Á̵ÚŪ¤Ë½¤Àµ¤ò¹Ô¤Ã¤Æ¤¯¤ì¤ë¤³¤È¤òÁ°Äó¤Ë¤·¤Æ¤¤¤ë¡¢
             ³ä¤êÀڤä¿ÊýË¡¤Ç¤Ï¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-nat-games">
           <para>²¿¸Î¤Û¤È¤ó¤É¤Î¥²¡¼¥à¤¬
             <option>-nat</option> ¥¹¥¤¥Ã¥ÁÉÕ¤­¤À¤ÈÆ°¤«¤Ê¤¤¤ó¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             <!--
             <note>
               <title>ÌõÃí</title>
               <para>
                 ¤³¤ÎÌäÂê¤Ïº´Æ£ ½ß°ì¤µ¤óºî¤Î <acronym>NAT</acronym>
                 ¥Ñ¥Ã¥Á¤ò»È¤Ã¤Æ¤â²ò·è¤Ç¤­¤Þ¤¹¡£
                 <ulink url="http://www2a.biglobe.ne.jp/~junichi/freebsd/lowtech/nat.html">NAT on iij-ppp</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
               </para>
             </note>
             -->
 
             libalias ¤ò»È¤Ã¤Æ¤¤¤ë»þ¤Ë¥²¡¼¥à¤Ê¤É¤ÎÎà¤Î¤â¤Î¤¬Æ°ºî¤·¤Ê¤¤Íýͳ¤Ï¡¢
             ³°Â¦¤Ë¤¢¤ë¥Þ¥·¥ó¤¬Àܳ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤«¡¢Æ⦤ˤ¢¤ë¥Þ¥·¥ó¤Ë
             (;·×¤Ê) UDP ¥Ñ¥±¥Ã¥È¤òÁ÷¿®¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤«¤é¤Ç¤¹¡£
             Æ⦤Υޥ·¥ó¤Ë¤³¤ì¤é¤Î¥Ñ¥±¥Ã¥È¤òÁ÷¤ë¤Ù¤­¤«¤Ë¤Ä¤¤¤Æ¡¢
             NAT ¥½¥Õ¥È¥¦¥§¥¢¤Ï´ØÃΤ·¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤¦¤Þ¤¯Æ°¤«¤¹¤¿¤á¤Ë¤Ï¡¢
             ¼Â¹ÔÃæ¤Î¤â¤Î¤¬ÌäÂê¤ÎȯÀ¸¤·¤Æ¤¤¤ë¥½¥Õ¥È¥¦¥§¥¢¤À¤±¤Ç¤¢¤ë¤«¤ò³Îǧ¤·¡¢
             ¥²¡¼¥È¥¦¥§¥¤¤Î <devicename>tun</devicename> ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ËÂФ·¤Æ
             <command>tcpdump</command> ¤ò¼Â¹Ô¤¹¤ë¤«¡¢
             ¥²¡¼¥È¥¦¥§¥¤¾å¤Ç <command>ppp</command> ¤Î
             <acronym>TCP</acronym>/<acronym>IP</acronym>
             ¥í¥°µ­Ï¿¤òÍ­¸ú²½ (<quote><literal>set log
               +tcp/ip</literal></quote>) ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
           <para>
             ¹Ôµ·¤Î°­¤¤¥½¥Õ¥È¥¦¥§¥¢¤òµ¯Æ°¤¹¤ëºÝ¤Ë¡¢
             ¥²¡¼¥È¥¦¥§¥¤¥Þ¥·¥ó¤òÄ̲᤹¤ë¥Ñ¥±¥Ã¥È¤ò´Æ»ë¤¹¤Ù¤­¤Ç¤¹¡£
             ³°Â¦¤«¤é²¿¤«¥Ñ¥±¥Ã¥È¤¬Ìá¤Ã¤Æ¤­¤¿»þ¤Ë¡¢
             ¤½¤Î¥Ñ¥±¥Ã¥È¤ÏÇË´þ¤µ¤ì¤ë¤Ç¤·¤ç¤¦ (¤½¤ì¤¬ÌäÂê¤Ê¤Î¤Ç¤¹)¡£
             ¤³¤ì¤é¤Î¥Ñ¥±¥Ã¥È¤Î¥Ý¡¼¥ÈÈÖ¹æ¤ËÃí°Õ¤·¤Æ¡¢
             ¤½¤Î¹Ôµ·¤Î°­¤¤¥½¥Õ¥È¥¦¥§¥¢¤òÄä»ß¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤³¤ì¤ò¿ô²ó·«¤êÊÖ¤·¤Æ¥Ý¡¼¥ÈÈֹ椬¾ï¤ËƱ¤¸¤Ç¤¢¤ë¤«¤ò³Îǧ¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
             Ʊ¤¸¤Ç¤¢¤Ã¤¿¾ì¹ç¤Ï¡¢
             <filename>/etc/ppp/ppp.conf</filename>
             ¤ÎŬÀڤʥ»¥¯¥·¥ç¥ó¤Ë¼¡¤Î¹Ô¤òÆþ¤ì¤ë¤È¡¢
             ¤½¤Î¥½¥Õ¥È¥¦¥§¥¢¤ÏÆ°ºî¤¹¤ë¤è¤¦¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
           </para>
 
           <programlisting>nat <replaceable>port</replaceable> <replaceable>proto</replaceable> <replaceable>internalmachine</replaceable>:<replaceable>port</replaceable> <replaceable>port</replaceable></programlisting>
 
           <para>
             ¤³¤³¤Ç <replaceable>proto</replaceable> ¤Ï
             <literal>tcp</literal> ¤« <literal>udp</literal> ¤Ç¤¢¤ê¡¢
             <replaceable>internalmachine</replaceable>
             ¤Ï¥Ñ¥±¥Ã¥È¤òÁ÷¤ê¤¿¤¤¥Þ¥·¥ó¡¢¤½¤·¤Æ
             <replaceable>port</replaceable>
             ¤Ï¥Ñ¥±¥Ã¥È¤ÎÁ÷¿®Àè¤Î¥Ý¡¼¥ÈÈÖ¹æ¤Ç¤¹¡£
           </para>
 
           <para>
             ¾åµ­¤Î¥³¥Þ¥ó¥É¤òÊѹ¹¤»¤º¤Ë¡¢
             ¾¤Î¥Þ¥·¥ó¾å¤Ç¤½¤Î¥½¥Õ¥È¥¦¥§¥¢¤ò»ÈÍѤǤ­¤ë¤è¤¦¤Ë¤Ï¤·¤¿¤¯¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             ¤½¤·¤ÆƱ»þ¤ËÆó¤Ä¤ÎÆâÉô¤Î¥Þ¥·¥ó¾å¤Ç¤½¤Î¥½¥Õ¥È¥¦¥§¥¢¤ò¼Â¹Ô¤¹¤ë¤³¤È¤Ï¡¢
             ¤³¤Î¼ÁÌä¤ÎÈϰϤòĶ¤¨¤Æ¤¤¤Þ¤¹¡£·ë¶É¡¢³°Â¦¤ÎÀ¤³¦¤«¤é¤Ï¡¢
             ÆâÉô¥Í¥Ã¥È¥ï¡¼¥¯Á´ÂΤ¬¤¿¤À°ì¤Ä¤Î¥Þ¥·¥ó¤È¤·¤Æ¸«¤¨¤ë¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¥Ý¡¼¥ÈÈֹ椬¾ï¤ËƱ¤¸¤È¤Ï¸Â¤é¤Ê¤¤¾ì¹ç¡¢¤µ¤é¤Ë»°¤Ä¤Î¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <orderedlist>
             <listitem>
               <para>
                 libalias ¤Ç¥µ¥Ý¡¼¥È¤¹¤ë¤è¤¦¤Ë¤·¡¢·ë²Ì¤òÁ÷¤êÉÕ¤±¤ë¡£
                 ÆÃÄê¤Î¾ì¹ç¤ÎÎã¤Ï <filename>/usr/src/lib/libalias/alias_*.c</filename>
                 ¤Ë¤¢¤ê¤Þ¤¹ (<filename>alias_ftp.c</filename>
                 ¤ÏÎɤ¤¥×¥í¥È¥¿¥¤¥×¤Ç¤¹)¡£¤³¤ì¤Ë¤ÏÄ̾³°¸þ¤­¤ÎÆÃÄê¤Î¥Ñ¥±¥Ã¥È¤òÆɤߡ¢
                 ÆâÉô¤Î·×»»µ¡¤Î¤¢¤ëÆÃÄê¤Î¥Ý¡¼¥È¤Ø¤ÎÀܳ¤ò³«»Ï¤¹¤ë¤è¤¦¤ÊÌ¿Î᤬¡¢
                 ³°Éô¤Î·×»»µ¡ÂФ·¤ÆÁ÷¤é¤ì¤Æ¤¤¤ë¤³¤È¤ò¸«Ê¬¤±¡¢
                 ¸å³¤Î¥Ñ¥±¥Ã¥È¤¬¤É¤³¤Ë¹Ô¤±¤Ð¤¤¤¤¤Î¤«¤¬Ê¬¤«¤ë¤è¤¦¤Ë¡¢
                 ¥¨¥¤¥ê¥¢¥¹¥Æ¡¼¥Ö¥ëÃæ¤Î
                 <quote><replaceable>route</replaceable></quote>
                 ¤ÎÉôʬ¤òÀßÄꤹ¤ë¡¢¤È¤¤¤¦ºî¶È¤¬´Þ¤Þ¤ì¤Þ¤¹¡£
               </para>
 
               <para>
                 ¤³¤ì¤ÏºÇ¤âÆñ¤·¤¤ÊýË¡¤Ç¤¹¤¬¡¢ºÇ¤âÎɤ¤ÊýË¡¤Ç¤â¤¢¤ê¤Þ¤¹¤·¡¢¥½¥Õ¥È¥¦¥§¥¢¤¬
                 Ê£¿ô¤Î·×»»µ¡¤ÇÆ°¤¯¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>¥×¥í¥­¥· (proxy) ¤ò»È¤¦¡£¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤¬¡¢¤¿¤È¤¨¤Ð socks5
                 ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤«¡¢(cvsup ¤Î¤è¤¦¤Ë) <quote>passive</quote>
                 ¥ª¥×¥·¥ç¥ó¤ò»ý¤Ã¤Æ¤¤¤ë¤È¤³¤ÎÊýË¡¤¬»È¤¨¤Þ¤¹¡£
                 <quote>passive</quote>
                 ¤È¤ÏÁê¼ê¦¤Î¤Û¤¦¤«¤éÀܳ¤òµá¤á¤Æ¤¯¤ë¤³¤È¤òÈò¤±¤ë¤¿¤á¤Ë¤¢¤ë¥ª¥×¥·¥ç¥ó¤Ç¤¹¡£
               </para>
             </listitem>
 
             <listitem>
               <para>
                 <quote><literal>nat addr</literal></quote>
                 ¤ò»È¤Ã¤Æ¤Ê¤ó¤Ç¤â¤«¤ó¤Ç¤âÆâÉô¤Î·×»»µ¡¤Ë¸þ¤±¤Æή¤·¤Æ¤·¤Þ¤¦¡£
                 ¤³¤ì¤Ï¤Á¤ç¤Ã¤È̵ÍýÌðÍý¤Ê²ò·èË¡¤Ç¤¹¡£
               </para>
             </listitem>
           </orderedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="useful-port-numbers">
           <para>Í­ÍѤʥݡ¼¥ÈÈÖ¹æ¤Î¥ê¥¹¥È¤Ï¤¢¤ê¤Þ¤»¤ó¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Þ¤À½ÐÍè¤Æ¤¤¤Þ¤»¤ó¡£¤·¤«¤·¡¢
             ¤³¤ì¤Ï (´Ø¿´¤ò»ý¤Ã¤Æ失¤ë¤Ê¤é¤Ð) ¤½¤¦¤¤¤Ã¤¿¥ê¥¹¥È¤Ë¤·¤Æ¤¤¤¯Í½Äê¤Ç¤¹¡£
             ¤½¤ì¤¾¤ì¤ÎÎã¤Ë¤¢¤ë
             <replaceable>internal</replaceable> ¤Ï¡¢
             ¥²¡¼¥à¤ÇÍ·¤Ö¥Þ¥·¥ó¤Î <acronym>IP</acronym> ¥¢¥É¥ì¥¹¤ËÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
 
           <para>
             <variablelist>
               <varlistentry>
                 <term>Asheron's Call</term>
 
                 <listitem>
                   <programlisting>nat port udp <replaceable>internal</replaceable>:65000 65000</programlisting>
 
                   <para>¼êÆ°¤Ç¥²¡¼¥à¤Î¥Ý¡¼¥ÈÈÖ¹æ¤ò 65000 ¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
                     ¥Þ¥·¥ó¤¬Ê£¿ô¤¢¤ë¾ì¹ç¤Ï¡¢¤½¤ì¤¾¤ì¤Î¥Þ¥·¥ó¤Ë½ÅÊ£¤·¤Ê¤¤¥Ý¡¼¥ÈÈÖ¹æ (¤Ä¤Þ¤ê
                     65001¡¢65002 ¤Ê¤É) ¤òÀßÄꤷ¡¢¤½¤ÎÀßÄꤴ¤È¤Ë
                     <literal>nat port</literal> ¤Î¹Ô¤òÄɲä·¤Þ¤¹¡£</para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>Half Life</term>
                 <listitem>
                   <programlisting>nat port udp <replaceable>internal</replaceable>:27005 27015</programlisting>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>PCAnywhere 8.0</term>
                 <listitem>
                   <programlisting>nat port udp <replaceable>internal</replaceable>:5632 5632
 nat port tcp <replaceable>internal</replaceable>:5631 5631</programlisting>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>Quake</term>
                 <listitem>
                   <programlisting>nat port udp <replaceable>internal</replaceable>:6112 6112</programlisting>
 
                   <para>¤³¤Î¤è¤¦¤ËÀßÄꤹ¤ëÂå¤ï¤ê¤Ë¡¢
                     <ulink url="http://www.battle.net/support/proxy/">www.battle.net</ulink>
                     ¤Ç Quake ¤Î¥×¥í¥­¥· (proxy) ¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¤«Ä´¤Ù¤Æ¤â¤¤¤¤¤Ç¤·¤ç¤¦¡£
                   </para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>Quake2</term>
                 <listitem>
                   <programlisting>alias port udp <replaceable>internal</replaceable>:27901 27910</programlisting>
 
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>Red Alert</term>
                 <listitem>
                   <programlisting>nat port udp <replaceable>internal</replaceable>:8675 8675
 nat port udp <replaceable>internal</replaceable>:5009 5009</programlisting>
                 </listitem>
               </varlistentry>
 
             </variablelist>
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="fcs-errors">
           <para><acronym>FCS</acronym> ¥¨¥é¡¼¤Ã¤Æ²¿?</para>
         </question>
 
         <answer>
           <para>
             <acronym>FCS</acronym> ¤È¤Ï
             <literal>F</literal>rame <literal>C</literal>heck <literal>S</literal>equence
 	    (¥Õ¥ì¡¼¥à¥Á¥§¥Ã¥¯¥·¡¼¥±¥ó¥¹) ¤Îά¤Ç¤¹¡£
             ¸Ä¡¹¤Î <application>ppp</application> ¥Ñ¥±¥Ã¥È¤Ë¤Ï¡¢
             Á÷¼õ¿®¤¹¤ë¥Ç¡¼¥¿¤¬Àµ¤·¤¤¤«¤òÄ´¤Ù¤ë¤¿¤á¤Î¥Á¥§¥Ã¥¯¥µ¥à¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¼õ¿®¤·¤¿¥Ñ¥±¥Ã¥È¤Î <acronym>FCS</acronym> ¤¬Àµ¤·¤¯¤Ê¤¤¾ì¹ç¤Ï¡¢¤½¤Î¥Ñ¥±¥Ã¥È¤ÏÇÑ´þ¤µ¤ì¡¢
             <acronym>HDLC</acronym> <acronym>FCS</acronym> ¥«¥¦¥ó¥È¤¬Áý¤ä¤µ¤ì¤Þ¤¹¡£
             <acronym>HDLC</acronym> ¥¨¥é¡¼¤Î¿ô¤Ï¡¢
             <command>show hdlc</command>
             ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æɽ¼¨¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             ¥ê¥ó¥¯¤ÎÉʼÁ¤¬°­¤«¤Ã¤¿¤ê¡¢
             ¥·¥ê¥¢¥ë¥É¥é¥¤¥Ð¤¬¥Ñ¥±¥Ã¥È¤ò¼è¤ê¤³¤Ü¤·¤Æ¤¤¤¿¤ê¤¹¤ë¤È¡¢
             <acronym>FCS</acronym> ¥¨¥é¡¼¤¬¤¿¤Ó¤¿¤ÓȯÀ¸¤·¤Þ¤¹¡£
             <acronym>FCS</acronym> ¥¨¥é¡¼¤Ï¡¢
             °µ½Ì¥×¥í¥È¥³¥ë¤Î®ÅÙÄã²¼¤Î¸¶°ø¤Ë¤Ï¤Ê¤ê¤Þ¤¹¤¬¡¢
             Æä˿´ÇÛ¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
             ³°ÉÕ¤±¥â¥Ç¥à¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
             ¥±¡¼¥Ö¥ë¤¬¤Á¤ã¤ó¤È¥·¡¼¥ë¥É¤µ¤ì¤Æ¤¤¤ë¤«¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¡¢
             <acronym>FCS</acronym> ¥¨¥é¡¼¤Î¸¶°ø¤È¤Ê¤ë¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             Àܳľ¸å¤«¤é¥ê¥ó¥¯¤¬¥Õ¥ê¡¼¥º¤·¡¢ÂçÎ̤Î
             <acronym>FCS</acronym> ¥¨¥é¡¼¤¬È¯À¸¤¹¤ë¾ì¹ç¤Ï¡¢
             ¥ê¥ó¥¯¤¬ 8 ¥Ó¥Ã¥È¥¯¥ê¡¼¥ó¤Ç¤Ê¤¤²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
             ¥½¥Õ¥È¥¦¥§¥¢¥Õ¥í¡¼À©¸æ (XON/XOFF)
             ¤¬»È¤ï¤ì¤Æ¤¤¤Ê¤¤¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤É¤¦¤·¤Æ¤â¥½¥Õ¥È¥¦¥§¥¢¥Õ¥í¡¼À©¸æ¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¾ì¹ç¤Ï¡¢
             <literal>set accmap 0x000a0000</literal> ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¡¢
             <application>ppp</application> ¤Ë
             <literal>^Q</literal> ¤È
             <literal>^S</literal> ¤ò¥¨¥¹¥±¡¼¥×¤µ¤»¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¥ê¥â¡¼¥È¥Û¥¹¥È¤¬ <acronym>PPP</acronym>
             ¥×¥í¥È¥³¥ë¤ò»ÈÍѤ·¤Æ¤Ê¤¤¾ì¹ç¤â¡¢ÂçÎ̤Î
             <acronym>FCS</acronym> ¥¨¥é¡¼¤¬È¯À¸¤·¤Þ¤¹¡£
             ¤³¤Î¾ì¹ç¤Ï¥í¥°¤ò¤È¤ê¤Ê¤¬¤é<emphasis>ÈóƱ´ü</emphasis>¤ÇÀܳ¤·¡¢
             ¥í¥°¥¤¥ó¥×¥í¥ó¥×¥È¤ä¥·¥§¥ë¥×¥í¥ó¥×¥È¤¬Á÷¤é¤ì¤ÆÍè¤Æ¤¤¤Ê¤¤¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¥í¥°¥Õ¥¡¥¤¥ë¤Ë¥ê¥ó¥¯¤ò½ªÎ»¤·¤¿¸¶°ø¤È¤Ê¤ë¤è¤¦¤Êµ­Ï¿¤¬¤Ê¤¤¾ì¹ç¤Ï¡¢
             ¥ê¥â¡¼¥È¥Û¥¹¥È (¥×¥í¥Ð¥¤¥À?) ¤Î´ÉÍý¼Ô¤Ë¡¢
             ¥»¥Ã¥·¥ç¥ó¤ò½ªÎ»¤µ¤ì¤¿Íýͳ¤ò¿Ò¤Í¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry id="PPPoEwithNAT">
         <question id="macos-win98-pppoe-freeze">
           <para>¥²¡¼¥È¥¦¥§¥¤¤Ç PPPoE ¤ò¼Â¹Ô¤¹¤ë¤È MacOS ¤ä
             Windows 98 ¤È¤ÎÀܳ¤¬¥Õ¥ê¡¼¥º¤·¤Æ¤·¤Þ¤¦¤Î¤Ç¤¹¤¬¡¢
             ¤³¤ì¤Ï¤Ê¤¼¤Ê¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             Michael Wozniak <email>mwozniak@netcom.ca</email>
             »á¤¬¡¢¤³¤Î¸½¾Ý¤Ë´Ø¤·¤ÆÀâÌÀ¤·¤Æ¤¯¤ì¤Þ¤·¤¿¡£
             ¤Þ¤¿¡¢Dan Flemming <email>danflemming@mac.com</email>
             »á¤Ï MacOS ¤Ç¤Î²ò·èºö¤òÄ󶡤·¤Æ¤¯¤ì¤Þ¤·¤¿¡£
             ¾ðÊó¤ÎÄ󶡤˴¶¼Õ¤·¤Þ¤¹¡£
           </para>
 
           <para>¤³¤ì¤Ï¡¢¤¤¤ï¤æ¤ë¡Ö¥Ö¥é¥Ã¥¯¥Û¡¼¥ë¥ë¡¼¥¿ (Black Hole router)¡×¤Ë¸¶°ø¤¬¤¢¤ê¤Þ¤¹¡£
             Windows 98 ¤È MacOS (¤ª¤è¤Ó¡¢¤ª¤½¤é¤¯Â¾¤Î Microsoft ¼ÒÀ½ OS) ¤Î TCP ¥Ñ¥±¥Ã¥ÈÁ÷½Ð¤Ï¡¢
             PPPoE ¤Î¥Õ¥ì¡¼¥à (Ethernet ¤Î MTU ¤Ïɸ½à¤Ç
             1500) ¤ËÆþ¤é¤Ê¤¤¤è¤¦¤ÊÂ礭¤Ê¥»¥°¥á¥ó¥È¥µ¥¤¥º¤òÍ׵ᤷ¤Þ¤¹¡£
             <emphasis>¤½¤·¤Æ¤µ¤é¤Ë</emphasis>ʬ³ä¶Ø»ß (<quote>don't fragment</quote>)
 	    ¥Õ¥é¥°¥Ó¥Ã¥È¤ò (TCP ¥Ñ¥±¥Ã¥È¤Ë¥Ç¥Õ¥©¥ë¥È¤Ç) ¥»¥Ã¥È¤¹¤ë¤Î¤Ç¤¹¤¬¡¢
             Telco ¤Î¥ë¡¼¥¿¤Ï¡¢Ê¬³ä¤¬É¬¿Ü ("must fragment") ¤Ç¤¢¤ë¤³¤È¤ò¼¨¤¹
             ICMP ¥á¥Ã¥»¡¼¥¸¤ò¡¢Àܳ¤·¤è¤¦¤È¤¹¤ë¥¦¥§¥Ö¥µ¥¤¥È¤ËÂФ·¤ÆÁ÷½Ð¤·¤Þ¤»¤ó
             (¤Ä¤Þ¤ê¡¢¥ë¡¼¥¿¤ÏÀµ¤·¤¯ ICMP ¥Ñ¥±¥Ã¥È¤òÁ÷½Ð¤·¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢
             ¥¦¥§¥Ö¥µ¥¤¥È¤Î¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤¬¤½¤ì¤òÍî¤È¤·¤Æ¤¤¤ë¤Î¤Ç¤¹)¡£
             ¤½¤Î¤¿¤á¥¦¥§¥Ö¥µ¡¼¥Ð¤¬ PPPoE Àܳ¤ËÂФ·¤ÆÂ礭¤¹¤®¤ë¥Õ¥ì¡¼¥à¤òÁ÷½Ð¤¹¤ë¤È
             Telco ¤Î¥ë¡¼¥¿¤Ï¤½¤Î¥Õ¥ì¡¼¥à¤ò¼Î¤Æ¤Æ¤·¤Þ¤¤¡¢
             ¸«¤è¤¦¤È¤·¤¿¥Ú¡¼¥¸¤¬É½¼¨¤µ¤ì¤Ê¤¤¤È¤¤¤¦¾É¾õ¤¬¸½¤ï¤ì¤Þ¤¹
             (MSS ¤è¤ê¾®¤µ¤¤¥Ú¡¼¥¸¤ä²èÁü¤Ïɽ¼¨¤µ¤ì¤Þ¤¹)¡£
             ¤Û¤È¤ó¤É¤Î Telco PPPoE ÀßÄê¤Ï¡¢É¸½à¤Ç¤³¤Î¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤è¤¦¤Ç¤¹¡£
             (¤¢¤¢¡¢Èà¤é¤¬¥ë¡¼¥Æ¥£¥ó¥°¥×¥í¥°¥é¥à¤Îºî¤êÊý¤òÍý²ò¤·¤Æ¤µ¤¨¤¤¤ì¤Ð¡Ä)¡£
           </para>
 
           <para>
             °ì¤Ä¤Î²ò·èË¡¤Ï¡¢Windows 95/98 ¥Þ¥·¥ó¤Ç regedit ¤ò»È¤¤¡¢
             ¼¡¤Î¥ì¥¸¥¹¥È¥ê¥¨¥ó¥È¥ê¤òÄɲ乤뤳¤È¤Ç¤¹¡£
           </para>
 
           <programlisting>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000\MaxMTU</programlisting>
 
           <para>
             ¥ì¥¸¥¹¥È¥ê¥¨¥ó¥È¥ê¤Ï¡¢<quote>1450</quote> ¤ÎÃÍ
             (¤â¤Ã¤ÈÀµ³Î¤Ë¸À¤¦¤È¡¢TCP ¥Ñ¥±¥Ã¥È¤ò PPPoE ¥Õ¥ì¡¼¥à¤Ë´°Á´¤ËŬ¹ç¤µ¤»¤ë¤Ë¤Ï
             <quote>1464</quote> ¤Ç¤¢¤ë¤Ù¤­¤Ç¤Ç¤¹¤¬¡¢
             <quote>1450</quote> ¤È¤¹¤ë¤È¡¢¸½¤ï¤ì¤ë²ÄǽÀ­¤¬¤¢¤ë¾¤Î IP
             ¥×¥í¥È¥³¥ë¤ËÂФ·¤Æ¥¨¥é¡¼¥Þ¡¼¥¸¥ó¤ò³ÎÊݤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹)
             ¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤Î¥ì¥¸¥¹¥È¥ê¥­¡¼¤Ï¡¢Windows2000 ¤Ç
             <literal>Tcpip\Parameters\Interfaces\<replaceable>ID for adapter</replaceable>\MTU</literal>
             ¤Ë°Ü¤µ¤ì¤¿¤È¤¤¤¦Êó¹ð¤¬¤¢¤ê¤Þ¤·¤¿¡£
           </para>
 
           <para>
             FreeBSD/NAT/PPPoE ¥ë¡¼¥¿¤È¶¦Â¸¤µ¤»¤ë¤¿¤á¤Ë Windoze ¤Î MTU
             ¤òÊѹ¹¤¹¤ëÊýË¡¤Ë´Ø¤¹¤ë¾ÜºÙ¤Ï¡¢
             <ulink url="http://search.support.microsoft.com/kb">Microsoft Knowledge
             Base</ulink> ¤Ë¤¢¤ë¡¢
             ÈÖ¹æ <quote>Q158474 - Windows TCPIP Registry Entries</quote>¡¢
             ¤ª¤è¤ÓÈÖ¹æ
             <quote>Q120642 - TCPIP &amp; NBT Configuration Parameters for Windows NT</quote>
             ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>»ÄÇ°¤Ê¤³¤È¤Ë¡¢MacOS ¤Ë¤Ï
             TCP/IP ÀßÄê¤òÊѹ¹¤¹¤ëÊýË¡¤¬¤¢¤ê¤Þ¤»¤ó¡£
             ¤·¤«¤·¡¢<ulink url="http://www.softworks.com/">Sustainable Softworks ¼Ò</ulink>
             ¤¬ÈÎÇ䤷¤Æ¤¤¤ë OTAdvancedTuner (OT ¤Ï OpenTransport ¤È¤¤¤¦
             MacOS ¤Î TCP/IP ¥¹¥¿¥Ã¥¯¤Î̾Á°¤Î¤³¤È) ¤Î¤è¤¦¤Ê¾¦ÍÑ¥½¥Õ¥È¥¦¥§¥¢¤¬Â¸ºß¤·¤Þ¤¹¡£
             ¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤Ï¡¢¥æ¡¼¥¶¤«¤é TCP/IP ÀßÄê¤ÎÊѹ¹¤ò¹Ô¤Ê¤¦¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£
             MacOS NAT ¥æ¡¼¥¶¤Ï¥É¥í¥Ã¥×¥À¥¦¥ó¥á¥Ë¥å¡¼¤«¤é
             <literal>ip_interface_MTU</literal> ¤òÁªÂò¤·¡¢
             ¥Ü¥Ã¥¯¥¹¤Ë¤¢¤ë <literal>1500</literal> ¤ÎÂå¤ï¤ê¤Ë
             <literal>1450</literal> ¤òÆþÎϤ·¡¢
             <literal>Save as Auto Configure</literal> ¤ÎÎ٤Υܥ寥¹¤ò¥¯¥ê¥Ã¥¯¤·¤Æ
             <literal>Make Active</literal> ¤ò¥¯¥ê¥Ã¥¯¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para><application>ppp</application> ¤ÎºÇ¿·ÈÇ
             (2.3 ¤«¤½¤ì°Ê¹ß) ¤Ë¤Ï¡¢¼«Æ°Åª¤Ë MSS ¤òŬÀÚ¤ÊÃͤËÄ´À᤹¤ë
             <command>enable tcpmssfixup</command> ¥³¥Þ¥ó¥É¤¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤Îµ¡Ç½¤Ïɸ½à¤ÇÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¤â¤·µì¥Ð¡¼¥¸¥ç¥ó¤Î <application>ppp</application>
             ¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¾õ¶·¤Ë¤¢¤ë¤Ê¤é¡¢
             <application>tcpmssd</application> ¤Î port
             ¤ò¤´Í÷¤Ë¤Ê¤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="desperation">
           <para>¤É¤ì¤Ë¤âÅö¤Æ¤Ï¤Þ¤é¤Ê¤¤! ¤É¤¦¤·¤¿¤é¤¤¤¤¤Î?</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Þ¤Ç¤Î¤¹¤Ù¤Æ¤Î¼ÁÌä¤ËÅö¤Æ¤Ï¤Þ¤é¤Ê¤¤¾ì¹ç¡¢ÀßÄê¥Õ¥¡¥¤¥ë¡¢
             <application>ppp</application>
             ¤Î¼Â¹ÔÊýË¡¡¢¥í¥°¥Õ¥¡¥¤¥ë¤Î³ºÅöÉôʬ¤È
             <command>netstat -rn</command>
             ¥³¥Þ¥ó¥É¤Î½ÐÎÏ (ÀܳÁ°¤ÈÀܳ¸å) ¤ò´Þ¤à¡¢
             ¤¢¤Ê¤¿¤Î»ý¤Ã¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¾ðÊó¤ò
             &a.questions;
             ¤ä
             <ulink url="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</ulink>
             ¥Ë¥å¡¼¥¹¥°¥ë¡¼¥×¤ØÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£Ã¯¤«¤¬¤¢¤Ê¤¿¤òÀµ¤·¤¤Êý¸þ¤ØƳ¤¤¤Æ¤¯¤ì¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="serial">
     <title>¥·¥ê¥¢¥ëÀܳ</title>
 
     <para>
       <emphasis>Ìõ:
         °ìµÜ μ <email>ryo@azusa.shinshu-u.ac.jp</email>¡¢
         1997 ǯ 11 ·î 16 Æü</emphasis>
     </para>
 
     <para>
       ¤³¤Î¥»¥¯¥·¥ç¥ó¤Ç¤Ï¡¢FreeBSD ¤Ç¥·¥ê¥¢¥ëÀܳ¤ò¤¹¤ë»þ¤Î°ìÈÌŪ¤Ê¼ÁÌä¤ËÅú¤¨¤Þ¤¹¡£
       <acronym>PPP</acronym> ¤ª¤è¤Ó
       <acronym>SLIP</acronym> ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
       <xref linkend="networking" remap="¥Í¥Ã¥È¥ï¡¼¥­¥ó¥°"/>¤Î¥»¥¯¥·¥ç¥ó¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="found-serial">
           <para>¤É¤¦¤ä¤Ã¤¿¤é FreeBSD ¤¬¥·¥ê¥¢¥ë¥Ý¡¼¥È¤òǧ¼±¤·¤¿¤³¤È¤òÃΤë»ö¤¬¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             FreeBSD ¤Î¥«¡¼¥Í¥ë¤¬µ¯Æ°¤¹¤ë»þ¡¢¥«¡¼¥Í¥ë¤Ï¤½¤ÎÀßÄê¤Ë¤·¤¿¤¬¤Ã¤Æ¡¢
             ¥·¥¹¥Æ¥à¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤ò¸¡½Ð¤·¤Þ¤¹¡£µ¯Æ°»þ¤Ëɽ¼¨¤µ¤ì¤ë¥á¥Ã¥»¡¼¥¸¤ò¤è¤¯´Ñ»¡¤¹¤ë¤«¡¢
             µ¯Æ°¸å¤Ë¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë»ö¤Ë¤è¤Ã¤Æ³Îǧ¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <screen>dmesg | grep sio</screen>
 
           <para>¤³¤³¤Ë¾å¤Ëµó¤²¤¿¥³¥Þ¥ó¥É¤Î½ÐÎÏÎã¤ò¼¨¤·¤Þ¤¹¡£</para>
 
           <screen>sio0 at 0x3f8-0x3ff irq 4 on isa
 sio0: type 16550A
 sio1 at 0x2f8-0x2ff irq 3 on isa
 sio1: type 16550A</screen>
 
           <para>
             ¤³¤ì¤Ï¡¢Æó¤Ä¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£1 ÈÖÌܤϡ¢
             irq ¤¬ 4 ¤Ç <literal>0x3f8</literal> ¤Î¥Ý¡¼¥È¥¢¥É¥ì¥¹¤ò»ÈÍѤ·¤Æ¤¤¤Þ¤¹¡£
             ¤½¤·¤Æ¡¢16550A-type UART ¥Á¥Ã¥×¤¬Â¸ºß¤·¤Þ¤¹¡£
             2 ÈÖÌܤϡ¢Æ±¤¸¥Á¥Ã¥×¤ò»È¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢
             irq ¤Ï 3 ¤Ç¡¢<literal>0x2f8</literal>
             ¤Î¥Ý¡¼¥È¥¢¥É¥ì¥¹¤ò»ÈÍѤ·¤Æ¤¤¤Þ¤¹¡£Æ⢤Υâ¥Ç¥à¥«¡¼¥É¤Ï¡¢
             Ä̾ï¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤ÈƱ¤¸¤è¤¦¤Ë°·¤ï¤ì¤Þ¤¹¤¬¡¢
             ¾ï»þ¥·¥ê¥¢¥ë¥Ý¡¼¥È¤Ë¥â¥Ç¥à¤¬Àܳ¤µ¤ì¤Æ¤¤¤ë¤È¤¤¤¦ÅÀ¤Ç°Û¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             GENERIC ¥«¡¼¥Í¥ë¤Ï¡¢¾å¤ÎÎã¤ÈƱ¤¸ irq
             ¤È¥Ý¡¼¥È¥¢¥É¥ì¥¹¤ÎÀßÄê¤ÎÆó¤Ä¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤é¤ÎÀßÄ꤬¤¢¤Ê¤¿¤Î¥·¥¹¥Æ¥à¤Ë¹ç¤ï¤Ê¤¤¾ì¹ç¡¢
             ¤Þ¤¿¤Ï¥â¥Ç¥à¥«¡¼¥É¤òÄɲä·¤¿¾ì¹ç¤ä¥«¡¼¥Í¥ë¤ÎÀßÄê°Ê¾å¤Ë¥·¥ê¥¢¥ë¥Ý¡¼¥È¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
             ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¾Ü¤·¤¯¤Ï¡¢
             <link linkend="make-kernel">¥«¡¼¥Í¥ë¤Î¹½ÃÛ</link>¤Î¹à¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="found-modem">
           <para>
             ¤É¤¦¤ä¤Ã¤¿¤é FreeBSD ¤¬¥â¥Ç¥à¥«¡¼¥É¤òǧ¼±¤·¤¿¤³¤È¤òÃΤ뤳¤È¤¬¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             Á°¤Î¼ÁÌä¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-tty0X">
           <para>FreeBSD 2.0.5 ¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤·¤¿¤é
 	    <devicename>tty0<replaceable>X</replaceable></devicename>
             ¤¬¸«¤Ä¤«¤é¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤¿¤Î¤Ç¤¹¤¬</para>
         </question>
 
         <answer>
           <para>¿´ÇÛ¤¢¤ê¤Þ¤»¤ó¡£
 	    <devicename>ttyd<replaceable>X</replaceable></devicename>
 	    ¤ËÅý¹ç¤µ¤ì¤Þ¤·¤¿¡£
             ¤¿¤À¡¢¸Å¤¤ÀßÄê¥Õ¥¡¥¤¥ë¤Î¤¹¤Ù¤Æ¤ò¹¹¿·¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="access-serial-ports">
           <para>¤É¤¦¤ä¤Ã¤¿¤é FreeBSD ¤Ç¥·¥ê¥¢¥ë¥Ý¡¼¥È¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             3 ÈÖÌܤΥݡ¼¥È
             <devicename>sio2</devicename> (&man.sio.4; ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£DOS
             ¤Ç¤Ï¡¢<devicename>COM3</devicename> ¤È¸Æ¤Ð¤ì¤Þ¤¹¡£) ¤Ë¤Ï¡¢
             ¥À¥¤¥ä¥ë¥¢¥¦¥È¥Ç¥Ð¥¤¥¹¤È¤·¤Æ¤Ï <devicename>/dev/cuaa2</devicename>¡¢
             ¥À¥¤¥ä¥ë¥¤¥ó¥Ç¥Ð¥¤¥¹¤È¤·¤Æ <devicename>/dev/ttyd2</devicename> ¤¬¤¢¤ê¤Þ¤¹¡£
             ¤½¤ì¤Ç¤Ï¤³¤Îξ¼Ô¤Ë¤Ï¤É¤Î¤è¤¦¤Ê°ã¤¤¤¬¤¢¤ë¤Î¤Ç¤·¤ç¤¦¤«?
           </para>
 
           <para>
             ¤Þ¤º¡¢¥À¥¤¥ä¥ë¥¤¥ó¤Î»þ¤Ë¤Ï
             <devicename>ttyd<replaceable>X</replaceable></devicename>
 	    ¤ò»È¤¤¤Þ¤¹¡£
             <devicename>/dev/ttyd<replaceable>X</replaceable></devicename>
             ¤ò¥Ö¥í¥Ã¥­¥ó¥°¥â¡¼¥É¤Ç¥ª¡¼¥×¥ó¤¹¤ë¤È¡¢¥×¥í¥»¥¹¤ÏÂбþ¤¹¤ë
             <devicename>cuaa<replaceable>X</replaceable></devicename>
             ¥Ç¥Ð¥¤¥¹¤¬¥¤¥ó¥¢¥¯¥Æ¥£¥Ö¤Ë¤Ê¤ë¤Î¤òÂÔ¤Á¤Þ¤¹¡£
             ¼¡¤Ë <acronym>CD</acronym> ¿®¹æ¤¬¥¢¥¯¥Æ¥£¥Ö¤Ë¤Ê¤ë¤Î¤òÂÔ¤Á¤Þ¤¹¡£
             <devicename>cuaa<replaceable>X</replaceable></devicename>
             ¥Ç¥Ð¥¤¥¹¤ò¥ª¡¼¥×¥ó¤¹¤ë¤È¡¢¥·¥ê¥¢¥ë¥Ý¡¼¥È¤¬
             <devicename>ttyd<replaceable>X</replaceable></devicename>
             ¥Ç¥Ð¥¤¥¹¤Ë¤è¤Ã¤Æ¤¹¤Ç¤Ë»È¤ï¤ì¤Æ¤¤¤Ê¤¤¤«¤É¤¦¤«¤ò³Îǧ¤·¤Þ¤¹¡£
             ¤â¤·¤³¤Î¥Ý¡¼¥È¤¬»ÈÍѲÄǽ¤Ç¤¢¤ì¤Ð¡¢¥Ý¡¼¥È¤Î»ÈÍѸ¢¤ò
             <devicename>ttyd<replaceable>X</replaceable></devicename>
             ¤«¤é¡ÖÃ¥¤¤¼è¤ë¡×¤Î¤Ç¤¹¡£¤Þ¤¿¡¢
             <devicename>cuaa<replaceable>X</replaceable></devicename>
             ¥Ç¥Ð¥¤¥¹¤Ï <acronym>CD</acronym> ¿®¹æ¤ò´Æ»ë¤·¤Þ¤»¤ó¡£
             ¤³¤Î»ÅÁȤߤȼ«Æ°±þÅú¥â¥Ç¥à¤Ë¤è¤Ã¤Æ¡¢
             ¥ê¥â¡¼¥È¥æ¡¼¥¶¡¼¤ò¥í¥°¥¤¥ó¤µ¤»¤¿¤ê¡¢
             Ʊ¤¸¥â¥Ç¥à¤Ç¥À¥¤¥ä¥ë¥¢¥¦¥È¤·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¡¢
             ¥·¥¹¥Æ¥à¤Î¤¢¤é¤æ¤ë¥È¥é¥Ö¥ë¤ÎÌÌÅݤò¸«¤ë¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="enable-multiport-serial">
           <para>¥Þ¥ë¥Á¥Ý¡¼¥È¥·¥ê¥¢¥ë¥«¡¼¥É¤ò¥µ¥Ý¡¼¥È¤µ¤»¤ë¤Ë¤Ï¤É¤¦¤·¤¿¤é¤è¤¤¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             ·«¤êÊÖ¤·¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢
             <link linkend="make-kernel">¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó</link>¤Î¥»¥¯¥·¥ç¥ó¤Ç¤Ï¡¢
             ¤¢¤Ê¤¿¤Î¥«¡¼¥Í¥ë¤ÎÀßÄê¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤¬ÆÀ¤é¤ì¤ë¤Ç¤·¤ç¤¦¡£
             ¥Þ¥ë¥Á¥Ý¡¼¥È¥·¥ê¥¢¥ë¥«¡¼¥É¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢¥«¡¼¥Í¥ë¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ë¡¢
             ¥«¡¼¥É¤Î»ý¤Ä¤½¤ì¤¾¤ì¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤ËÂбþ¤¹¤ë
             &man.sio.4;
             ¤Î¹Ô¤òµ­½Ò¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤·¤«¤·¡¢
             irq ¤È¥Ù¥¯¥¿¥¢¥É¥ì¥¹¤Ï°ì¤Ä¤Î¥¨¥ó¥È¥ê¤Ë¤Î¤ßµ­½Ò¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¥«¡¼¥É¾å¤Î¤¹¤Ù¤Æ¤Î¥Ý¡¼¥È¤Ï°ì¤Ä¤Î irq ¤ò¶¦Í­¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             °ì´ÓÀ­¤ò»ý¤¿¤»¤ë¤¿¤á¤Ë¤â¡¢
             ºÇ¸å¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È¤Î½ê¤Ç irq ¤ò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
             ¤Þ¤¿¡¢<literal>COM_MULTIPORT</literal> ¥ª¥×¥·¥ç¥ó¤âÉÕ¤±¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¼¡¤Ë¼¨¤¹Îã¤Ï¡¢AST ¤Î 4 ¥Ý¡¼¥È¥·¥ê¥¢¥ë¥«¡¼¥É¤ò irq 7 ¤ÇÀßÄꤷ¤¿¤â¤Î¤Ç¤¹¡£
           </para>
 
           <programlisting>options "COM_MULTIPORT"
 device sio4 at isa? port 0x2a0 tty flags 0x781
 device sio5 at isa? port 0x2a8 tty flags 0x781
 device sio6 at isa? port 0x2b0 tty flags 0x781
 device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlisting>
 
           <para>
             ¤³¤Î¥Õ¥é¥°¤Ï¥Þ¥¹¥¿¥Ý¡¼¥È¤¬¥Þ¥¤¥Ê¡¼ÈÖ¹æ 7
             (<literal>0x700</literal>) ¤ò»ý¤Ã¤Æ¤¤¤Æ¡¢
             ¸¡½Ð»þ¤Î¿ÇÃǵ¡Ç½¤òÍ­¸ú¤Ë¤· (<literal>0x080</literal>)¡¢
             ¤½¤·¤Æ¤¹¤Ù¤Æ¤Î¥Ý¡¼¥È¤Ç irq
             ¤ò¶¦Í­¤¹¤ë (<literal>0x001</literal>) ¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multiport-serial-share-irq">
           <para>FreeBSD ¤ÇÊ£¿ô¤Î¥Þ¥ë¥Á¥Ý¡¼¥È¥·¥ê¥¢¥ë¥«¡¼¥É´Ö¤Ç
             irq ¤ò¶¦Í­¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¸½ºß¤Î¤È¤³¤í¤Ï¤Ç¤­¤Þ¤»¤ó¡£¤½¤ì¤¾¤ì¤Î¥«¡¼¥ÉËè¤Ë°Û¤Ê¤Ã¤¿ irq
             ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="default-serial-params">
           <para>
             ¥Ý¡¼¥È¤Ë¥Ç¥Õ¥©¥ë¥È¤Î¥Ñ¥é¥á¡¼¥¿¤òÀßÄꤹ¤ë»ö¤Ï½ÐÍè¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para><devicename>ttyd<replaceable>X</replaceable></devicename>
 	    ¥Ç¥Ð¥¤¥¹ (¤Þ¤¿¤Ï
             <devicename>cuaa<replaceable>X</replaceable></devicename>
             ¥Ç¥Ð¥¤¥¹) ¤Ï¡¢
             ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¤¿¤á¤Ë¥ª¡¼¥×¥ó¤¹¤ëɸ½àŪ¤Ê¥Ç¥Ð¥¤¥¹¤Ç¤¹¡£
             ¥×¥í¥»¥¹¤¬¤½¤Î¥Ý¡¼¥È¤ò¥ª¡¼¥×¥ó¤¹¤ë»þ¡¢
             ¥×¥í¥»¥¹¤Ï¥Ç¥Õ¥©¥ë¥È¤ÎüËö I/O ÀßÄê¤ò¼èÆÀ¤·¤Þ¤¹¡£
             ¤³¤ì¤é¤ÎÀßÄê¤Ï¼¡¤Î¥³¥Þ¥ó¥É¤Ç³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <programlisting>stty -a -f /dev/ttyd1</programlisting>
 
           <para>
             ¤³¤Î¥Ç¥Ð¥¤¥¹¤ËÂФ¹¤ëÀßÄê¤òÊѹ¹¤·¤¿¾ì¹ç¡¢
             ¤½¤ÎÀßÄê¤Ï¥Ç¥Ð¥¤¥¹¤ò¥¯¥í¡¼¥º¤¹¤ë¤Þ¤ÇÍ­¸ú¤Ç¤¹¡£
             ¥Ç¥Ð¥¤¥¹¤òºÆ¥ª¡¼¥×¥ó¤·¤¿¾ì¹ç¡¢¤½¤ì¤é¤ÎÀßÄê¤Ï¥Ç¥Õ¥©¥ë¥È¤ËÌá¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
             ¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤ËÊѹ¹¤ò²Ã¤¨¤ë¤¿¤á¤Ë¡¢
             ¡Ö½é´üÀßÄê¡×¥Ç¥Ð¥¤¥¹¤ò¥ª¡¼¥×¥ó¤·¡¢
             ÀßÄê¤ò½¤Àµ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢<acronym>CLOCAL</acronym> ¥â¡¼¥É¡¢8 ¥Ó¥Ã¥È¡¢
             <acronym>XON/XOFF</acronym>
             ¥Õ¥í¡¼À©¸æ¤È¤¤¤¦ÀßÄê¤ò
             <devicename>ttyd5</devicename>
             ¤Î¥Ç¥Õ¥©¥ë¥È¤Ë¤·¤¿¤¤¾ì¹ç¡¢¼¡¤Î¤è¤¦¤Ë¹Ô¤Ê¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>stty -f /dev/ttyid5 clocal cs8 ixon ixoff</programlisting>
 
           <para>
             ¤³¤ÎÀßÄê¤ò¹Ô¤Ê¤¦¤¿¤á¤Î¥³¥Þ¥ó¥É¤òµ­½Ò¤¹¤ë¤Î¤ËŬÀڤʥե¡¥¤¥ë¤Ï¡¢
             <filename>/etc/rc.serial</filename> ¤Ç¤¹¡£
             ¤³¤ì¤Ç¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤¬
             <devicename>ttyd5</devicename> ¤ò¥ª¡¼¥×¥ó¤·¤¿»þ¤Ë¡¢
             ¤³¤ì¤é¤ÎÀßÄê¤ò¥Ç¥Õ¥©¥ë¥È¤Ç¼èÆÀ¤·¤Þ¤¹¡£
             ¤·¤«¤·¡¢¤³¤¦¤¤¤Ã¤¿¥ê¥ó¥¯¤Ë¤è¤ëÀßÄê¤ÏÊѹ¹²Äǽ¤Ç¤¹¡£
           </para>
 
           <para>
             ¡ÖÀßÄê¸ÇÄê¡×¥Ç¥Ð¥¤¥¹¤òÄ´À°¤·¤Æ¤ä¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢
             ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ë¤è¤ëÀßÄê¤ÎÊѹ¹¤ò¶Ø»ß¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢<devicename>ttyd5</devicename>
             ¤ÎÄÌ¿®Â®ÅÙ¤ò 57600bps
             ¤Ë¸ÇÄꤹ¤ë¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¹Ô¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
 
           <para>
             ¤³¤ì¤Ë¤è¤ê¡¢¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ï <devicename>ttyd5</devicename>
             ¤ò¥ª¡¼¥×¥ó¤·¡¢¥Ý¡¼¥È¤ÎÄÌ¿®Â®ÅÙ¤òÊѹ¹¤·¤è¤¦¤È¤·¤Þ¤¹¤¬¡¢
             ÄÌ¿®Â®ÅÙ¤Ï 57600bps ¤Î¤Þ¤Þ¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
           <para>
             ÅöÁ³¤Î¤³¤È¤Ê¤¬¤é¡¢½é´üÀßÄê¥Ç¥Ð¥¤¥¹¤ª¤è¤Ó¡¢ÀßÄê¸ÇÄê¥Ç¥Ð¥¤¥¹¤Ï
             <username>root</username> ¤Î¤ß¤¬½ñ¤­¹þ¤ß¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤·¤«¤·¡¢&man.MAKEDEV.8;
             ¥¹¥¯¥ê¥×¥È¤Ï¥Ç¥Ð¥¤¥¹¥¨¥ó¥È¥ê¤òºîÀ®¤¹¤ë»þ¤Ë¡¢
             ¤³¤Î¤è¤¦¤ÊÀßÄê¤Ï<emphasis>¹Ô¤¤¤Þ¤»¤ó</emphasis>¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="enable-dialup">
           <para>¤É¤Î¤è¤¦¤Ë¤·¤¿¤é¥â¥Ç¥à·Ðͳ¤Ç¥À¥¤¥ä¥ë¥¢¥Ã¥×¥í¥°¥¤¥ó¤¬¤Ç¤­¤ë¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Ä¤Þ¤ê¡¢¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥µ¡¼¥Ó¥¹¥×¥í¥Ð¥¤¥À¡¼¤Ë¤Ê¤ê¤¿¤¤¤Î¤Ç¤¹¤Í¡£
             ¤½¤ì¤Ë¤Ï¤Þ¤º¡¢1 Âæ¤Ê¤¤¤·Ê£¿ô¤Î¼«Æ°±þÅú¥â¥Ç¥à¤¬É¬ÍפǤ¹¡£
             ¥â¥Ç¥à¤Ë¤Ï¡¢¥­¥ã¥ê¥¢¡¼¤ò¸¡½Ð¤·¤¿»þ¤Ë¤Ï
             <acronym>CD</acronym> ¿®¹æ¤ò½ÐÎϤ·¡¢
             ¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤Ë¤Ï½ÐÎϤ·¤Ê¤¤¤³¤È¤¬É¬ÍפȤµ¤ì¤Þ¤¹¡£
             ¤Þ¤¿ <acronym>DTR</acronym> ¿®¹æ¤¬
             on ¤«¤é off ¤Ë¤Ê¤Ã¤¿»þ¤Ë¤Ï¡¢
             ÅÅÏòóÀþ¤òÀÚÃǤ·¡¢¥â¥Ç¥à¼«¿È¤ò¥ê¥»¥Ã¥È¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤ª¤½¤é¤¯¡¢<acronym>RTS/CTS</acronym> ¥Õ¥í¡¼À©¸æ¤ò»È¤¦¤«¡¢
             ¥í¡¼¥«¥ë¥Õ¥í¡¼À©¸æ¤ò¤Þ¤Ã¤¿¤¯»È¤ï¤Ê¤¤¤«¤Î¤É¤Á¤é¤«¤Ç¤·¤ç¤¦¡£
             ºÇ¸å¤Ë¡¢¥³¥ó¥Ô¥å¡¼¥¿¤È¥â¥Ç¥à¤Î´Ö¤Ï¸ÇÄê®Å٤Ǥʤ±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤¿¤À¡¢(¥À¥¤¥ä¥ë¥¢¥Ã¥×¤Îȯ¸Æ¼Ô¤ËÂФ·¤Æ¿ÆÀڤǤ¢¤ë¤¿¤á¤Ë¤Ï¡¢
             ) ¤³¤Á¤é¤Î¥â¥Ç¥à¤ÈÁê¼ê¦¤Î¥â¥Ç¥à¤Î´Ö¤Î®ÅÙ¤ò¡¢
             ¥â¥Ç¥à´Ö¤Ç¼«Æ°Ä´À°¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤Ù¤­¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             ¿¤¯¤¢¤ë¥Ø¥¤¥º¥³¥Þ¥ó¥É¸ß´¹¥â¥Ç¥à¤ËÂФ·¤Æ¡¢¼¡¤Î¥³¥Þ¥ó¥É¤Ï¤³¤ì¤é¤ÎÀßÄê¤ò¹Ô¤Ê¤¤¡¢
             ¤½¤ÎÀßÄê¤òÉÔ´øȯÀ­¥á¥â¥ê¡¼¤ËÊݸ¤·¤Þ¤¹¡£
           </para>
 
           <programlisting>AT&amp;C1&amp;D3&amp;K3&amp;Q6S0=1&amp;W</programlisting>
 
           <para>
             MS-DOS ¤Î¥¿¡¼¥ß¥Ê¥ë¥×¥í¥°¥é¥à¤ËÍê¤é¤º¤Ë AT ¥³¥Þ¥ó¥É¤òÁ÷½Ð¤¹¤ë¤Ë¤Ï¡¢
             <link linkend="direct-at">¡ÖAT
               ¥³¥Þ¥ó¥É¤òÆþÎϤ¹¤ë¤Ë¤Ï¡×</link>¤Î¥»¥¯¥·¥ç¥ó¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¼¡¤Ë¡¢¥â¥Ç¥àÍѤΥ¨¥ó¥È¥ê¤ò
             <filename>/etc/ttys</filename> (&man.ttys.5; »²¾È)
             ¤ËºîÀ®¤·¤Þ¤·¤ç¤¦¡£
             ¤³¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢
             ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬¥í¥°¥¤¥ó¤òÂԤäƤ¤¤ë¤¹¤Ù¤Æ¤Î¥Ý¡¼¥È¤¬µ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             °Ê²¼¤Î¤è¤¦¤Ê¹Ô¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>ttyd1 "/usr/libexec/getty std.57600" dialup on insecure</programlisting>
 
           <para>
             ¤³¤Î¹Ô¤Ï¡¢2 ÈÖÌܤΥ·¥ê¥¢¥ë¥Ý¡¼¥È
             (<devicename>/dev/ttyd1</devicename>) ¤Ë¤Ï¡¢
             57600bps ¤ÎÄÌ¿®Â®Å٤ǥΥó¥Ñ¥ê¥Æ¥£ (<literal>std.57600</literal>:
             ¤³¤ì¤Ï
             <filename>/etc/gettytab</filename>
             ¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£&man.gettytab.5; »²¾È)
             ¤Î¥â¥Ç¥à¤¬Àܳ¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£
             ¤³¤Î¥Ý¡¼¥È¤ÎüËö¥¿¥¤¥×¤Ï <literal>dialup</literal> ¤Ç¤¹¡£
             ¤Þ¤¿¤³¤Î¥Ý¡¼¥È¤Ï¡¢<literal>on</literal>
             ¤¹¤Ê¤ï¤Á¥í¥°¥¤¥ó²Äǽ¤Ç¤¢¤ê¡¢<literal>insecure</literal> ¤Ç¤¹¡£
             ¤³¤ì¤Ï <username>root</username>
             ¤¬¤³¤Î¥Ý¡¼¥È¤«¤éľÀÜ¥í¥°¥¤¥ó¤¹¤ë¤Î¤Ï¡¢
             µö²Ä¤µ¤ì¤Æ¤¤¤Ê¤¤¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
             ¤³¤Î¤è¤¦¤Ê¥À¥¤¥ä¥ë¥¤¥ó¥Ý¡¼¥È¤ËÂФ·¤Æ¤Ï¡¢
             <devicename>ttyd<replaceable>X</replaceable></devicename>
             ¤Î¥¨¥ó¥È¥ê¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤³¤ì¤¬°ìÈÌŪ¤Ê¡¢¥¿¡¼¥ß¥Ê¥ë¥¿¥¤¥×¤È¤·¤Æ <literal>dialup</literal>
             ¤ò»È¤¦ÊýË¡¤Ç¤¹¡£Â¿¤¯¤Î¥æ¡¼¥¶¡¼¤Ï¡¢
             <filename>.profile</filename> ¤ä
             <filename>.login</filename> ¤Ç¡¢
             ¥í¥°¥¤¥ó»þ¤ÎüËö¥¿¥¤¥×¤¬
             <literal>dialup</literal> ¤Ç¤¢¤Ã¤¿¾ì¹ç¤Ë¤Ï¡¢
             ¼ÂºÝ¤ÎüËö¥¿¥¤¥×¤ò¥æ¡¼¥¶¡¼¤ËÌ䤤¹ç¤ï¤»¤ë¤è¤¦¤ËÀßÄꤷ¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ÎÎã¤Ï¡¢¥Ý¡¼¥È¤¬ <literal>insecure</literal>
             ¤Ç¤·¤¿¡£¤³¤Î¥Ý¡¼¥È¤Ç <username>root</username> ¤Ë¤Ê¤ë¤Ë¤Ï¡¢
             °ìÈ̥桼¥¶¡¼¤È¤·¤Æ¥í¥°¥¤¥ó¤·¡¢¤½¤ì¤«¤é
             <quote><ulink url="http://www.FreeBSD.org/cgi/man.cgi?su">su</ulink></quote> ¤ò»È¤Ã¤Æ
             <username>root</username> ¤Ë¤Ê¤Ã¤Æ¤¯¤À¤µ¤¤¡£
             ¤â¤·¡¢<literal>secure</literal>
             ¤ò»ØÄꤷ¤¿¤Ê¤é¤Ð¡¢
             ľÀÜ <username>root</username> ¤¬¤½¤Î¥Ý¡¼¥È¤«¤é¥í¥°¥¤¥ó¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             <filename>/etc/ttys</filename>
             ¤ËÊѹ¹¤ò²Ã¤¨¤¿¸å¤Ï¡¢<acronym>HUP</acronym> ¥·¥°¥Ê¥ë (SIGHUP) ¤ò
             &man.init.8;
             ¥×¥í¥»¥¹¤ËÁ÷¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
 
           <para>
             ¤³¤ÎÁàºî¤Ï <command>init</command> ¥×¥í¥»¥¹¤Ë
             <filename>/etc/ttys</filename>
             ¤òºÆÆɤ߹þ¤ß¤µ¤»¤Þ¤¹¡£
             ¤³¤ì¤Ë¤è¤ê¡¢init ¥×¥í¥»¥¹¤Ï
             <command>getty</command> ¥×¥í¥»¥¹¤ò¤¹¤Ù¤Æ¤Î
             <literal>on</literal>
             ¤È¤Ê¤Ã¤Æ¤¤¤ë¥Ý¡¼¥È¤Ëµ¯Æ°¤µ¤»¤Þ¤¹¡£
             ¼¡¤Î¤è¤¦¤Ë¤·¤Æ¡¢¥Ý¡¼¥È¤¬¥í¥°¥¤¥ó²Äǽ¤«¤òÃΤ뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.user; <userinput>ps -ax | grep '[t]tyd1'</userinput></screen>
 
           <para>
             ¥í¥°¥¤¥ó²Äǽ¤Ç¤¢¤ì¤Ð¡¢¼¡¤Î¤è¤¦¤Ê½ÐÎϤ¬ÆÀ¤é¤ì¤ë¤Ï¤º¤Ç¤¹¡£
           </para>
 
           <screen>747 ??  I      0:00.04 /usr/libexec/getty std.57600 ttyd1</screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dumb-terminal">
           <para>¥À¥à¥¿¡¼¥ß¥Ê¥ë¤ò FreeBSD ¥Þ¥·¥ó¤ËÀܳ¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤¿¤é¤è¤¤¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤â¤·¡¢Â¾¤Î¥³¥ó¥Ô¥å¡¼¥¿¡¼¤ò FreeBSD ¤ÎüËö¤È¤·¤ÆÀܳ¤·¤¿¤¤¤Î¤Ê¤é¤Ð¡¢
             ¤ª¸ß¤¤¤Î¥·¥ê¥¢¥ë¥Ý¡¼¥È´Ö¤ò¤Ä¤Ê¤°¥Ì¥ë¥â¥Ç¥à¥±¡¼¥Ö¥ë
             (ÌõÃí: ¥ê¥Ð¡¼¥¹¥±¡¼¥Ö¥ë¤â¤·¤¯¤Ï¥¯¥í¥¹¥±¡¼¥Ö¥ë¤È¤â¸Æ¤Ð¤ì¤Þ¤¹)
             ¤òÍÑ°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤â¤·¡¢´ûÀ½¤ÎüËö¤ò»È¤¦¾ì¹ç¤Ï¡¢ÉÕ°¤¹¤ë¥Þ¥Ë¥å¥¢¥ë¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤½¤·¤Æ¡¢<filename>/etc/ttys</filename> (&man.ttys.5; »²¾È)
             ¤ò¾å¤ÈƱ¤¸¤è¤¦¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤¿¤È¤¨¤Ð¡¢WYSE-50 ¤È¤¤¤¦Ã¼Ëö¤ò 5 ÈÖÌܤΥݡ¼¥È¤ËÀܳ¤¹¤ë¤Ê¤é¤Ð¡¢
             ¼¡¤Î¤è¤¦¤Ê¥¨¥ó¥È¥ê¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>ttyd4 "/usr/libexec/getty std.38400" wyse50 on secure</programlisting>
 
           <para>
             ¤³¤ÎÎã¤Ï¡¢<devicename>/dev/ttyd4</devicename> ¥Ý¡¼¥È¤Ë¥Î¥ó¥Ñ¥ê¥Æ¥£¡¢
             üËö¥¿¥¤¥×¤¬ wyse50¡¢ÄÌ¿®Â®ÅÙ¤¬
             38400bps (<literal>std.38400</literal>: ¤³¤ÎÀßÄê¤Ï¡¢
             <filename>/etc/gettytab</filename>
             ¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£&man.gettytab.5; »²¾È) ¤ÎüËö¤¬Â¸ºß¤·¤Æ¤ª¤ê¡¢
             <username>root</username>
             ¤Î¥í¥°¥¤¥ó¤¬µö²Ä¤µ¤ì¤Æ¤¤¤ë (<literal>secure</literal>) ¤Ç¤¢¤ë¤³¤È¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cannot-tip">
           <para>¤É¤¦¤·¤Æ <command>tip</command> ¤ä
             <command>cu</command> ¤¬Æ°¤«¤Ê¤¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤ª¤½¤é¤¯¤¢¤Ê¤¿¤Î¥·¥¹¥Æ¥à¤Ç¤Ï
             &man.tip.1; ¤ä &man.cu.1; ¤Ï
             <username>uucp</username> ¥æ¡¼¥¶¡¼¤«¡¢
             <groupname>dialer</groupname> ¥°¥ë¡¼¥×¤Ë¤è¤Ã¤Æ¤Î¤ß¼Â¹Ô²Äǽ¤Ê¤Î¤Ç¤·¤ç¤¦¡£
             <groupname>dialer</groupname> ¥°¥ë¡¼¥×¤Ï¡¢
             ¥â¥Ç¥à¤ä¥ê¥â¡¼¥È¥·¥¹¥Æ¥à¤Ë¥¢¥¯¥»¥¹¤¹¤ë¥æ¡¼¥¶¡¼¤ò´ÉÍý¤¹¤ë¤¿¤á¤Ë¡¢
             »ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤½¤ì¤Ë¤Ï¡¢<filename>/etc/group</filename>
             ¥Õ¥¡¥¤¥ë¤Î <groupname>dialer</groupname>
             ¥°¥ë¡¼¥×¤Ë¤¢¤Ê¤¿¼«¿È¤òÄɲ䷤Ƥ¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤½¤¦¤¹¤ëÂå¤ï¤ê¤Ë¡¢¼¡¤Î¤è¤¦¤Ë¥¿¥¤¥×¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢
             ¤¢¤Ê¤¿¤Î¥·¥¹¥Æ¥à¤ÎÁ´¥æ¡¼¥¶¡¼¤¬
             <command>tip</command> ¤ä
             <command>cu</command>
             ¤ò¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>chmod 4511 /usr/bin/cu</userinput>
 &prompt.root; <userinput>chmod 4511 /usr/bin/tip</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="hayes-unsupported">
           <para>»ä¤Î Hayes ¥â¥Ç¥à¤Ï¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Ê¤¤¤Î¤Ç¤¹¤¬¡¢
             ¤É¤¦¤·¤¿¤é¤¤¤¤¤Î¤Ç¤·¤ç¤¦¤«¡£</para>
         </question>
 
         <answer>
           <para>
             ¼ÂºÝ¡¢
             &man.tip.1;
             ¤Î¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ï¸Å¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¤¹¤Ç¤Ë¡¢Hayes ¥À¥¤¥¢¥é¤¬¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
             <filename>/etc/remote</filename>
             ¥Õ¥¡¥¤¥ë (&man.remote.5; »²¾È) ¤Ç¡¢
             <quote><literal>at=hayes</literal></quote>
             ¤È»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             Hayes ¥É¥é¥¤¥Ð¤Ï¡¢ºÇ¶á¤Î¥â¥Ç¥à¤Î¿·¤·¤¤µ¡Ç½¤Ç¤¢¤ë¡¢
             <literal>BUSY</literal>¡¢
             <literal>NO DIALTONE</literal>¡¢
             <literal>CONNECT 115200</literal>
             ¤Ê¤É¤Î¥á¥Ã¥»¡¼¥¸¤òǧ¼±¤Ç¤­¤ë¤Û¤É¸­¤¯¤Ï¤Ê¤¯¡¢
             ñ¤Ëº®Íð¤òµ¯¤³¤¹¤À¤±¤Ç¤¹¡£
             &man.tip.1;
             ¤ò»È¤¦¾ì¹ç¤Ë¤Ï (<literal>ATX0&amp;W</literal>¤È¤¹¤ë¤Ê¤É¤·¤Æ)¡¢
             ¤³¤ì¤é¤Î¥á¥Ã¥»¡¼¥¸¤òɽ¼¨¤µ¤»¤Ê¤¤¤è¤¦¤Ë¤·¤Ê¤¯¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤Þ¤¿¡¢<literal>tip</literal> ¤Î¥À¥¤¥ä¥ë¤Î¥¿¥¤¥à¥¢¥¦¥È¤Ï 60 ÉäǤ¹¡£
             ¥â¥Ç¥à¤Î¥¿¥¤¥à¥¢¥¦¥ÈÀßÄê¤Ï¤½¤ì¤è¤êû¤¯¤¹¤Ù¤­¤Ç¤¢¤ê¡¢
             ¤½¤¦¤·¤Ê¤¤¤È <literal>tip</literal>
             ¤ÏÄÌ¿®¤ËÌäÂ꤬¤¢¤ë¤ÈȽÃǤ¹¤ë¤Ç¤·¤ç¤¦¡£
             <literal>ATS7=45&amp;W</literal> ¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¼ÂºÝ¡¢¥Ç¥Õ¥©¥ë¥È¤Î
             <literal>tip</literal> ¤Ï Hayes
             ¤Î´°Á´¤Ê¥µ¥Ý¡¼¥È¤ò¤·¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ²ò·èÊýË¡¤Ï <filename>/usr/src/usr.bin/tip/tip</filename>
             ¤Î²¼¤Î <filename>tipconf.h</filename> ¤òÊѹ¹¤¹¤ë¤³¤È¤Ç¤¹¡£
             ¤â¤Á¤í¤ó¡¢¤³¤ì¤Ë¤Ï¥½¡¼¥¹ÇÛÉÛ¥Õ¥¡¥¤¥ë¤¬É¬ÍפǤ¹¡£
           </para>
 
           <para>
             <quote><literal>#define HAYES 0</literal></quote>
             ¤Èµ­½Ò¤µ¤ì¤Æ¤¤¤ë¹Ô¤ò
             <quote><literal>#define HAYES1</literal></quote> ¤ÈÊѹ¹¤·¡¢¤½¤·¤Æ
             <quote><command>make</command></quote> ¤È
             <quote><command>make install</command></quote>
             ¤ò¼Â¹Ô¤·¤Þ¤¹¡£¤³¤ì¤Ç¤¦¤Þ¤¯Æ°ºî¤¹¤ë¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="direct-at">
           <para>¤³¤ì¤é¤Î AT ¥³¥Þ¥ó¥É¤òÆþÎϤ¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             <filename>/etc/remote</filename>
             ¥Õ¥¡¥¤¥ë (&man.remote.5; »²¾È) ¤ÎÃæ¤Ç
             <quote>direct</quote> ¥¨¥ó¥È¥ê¤òºî¤ê¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¥â¥Ç¥à¤¬ 1 ÈÖÌܤΥ·¥ê¥¢¥ë¥Ý¡¼¥È¤Ç¤¢¤ë
             <devicename>/dev/cuaa0</devicename>¤ËÀܳ¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢
             ¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
           <programlisting>cuaa0:dv=/dev/cuaa0:br#19200:pa=none</programlisting>
 
           <para>
             ¥â¥Ç¥à¤¬¥µ¥Ý¡¼¥È¤¹¤ëºÇÂç¤Î bps ¥ì¡¼¥È¤ò
             <literal>br</literal> ¥Õ¥£¡¼¥ë¥É¤Ë»È¤¤¤Þ¤¹¡£
             ¤½¤·¤Æ <command>tip <devicename>cuaa0</devicename></command> (&man.tip.1; »²¾È)
             ¤ò¼Â¹Ô¤¹¤ë¤È¡¢¥â¥Ç¥à¤¬ÍøÍѤǤ­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             <devicename>/dev/cuaa0</devicename>¤¬¥·¥¹¥Æ¥à¤Ë¸ºß¤·¤Ê¤¤¾ì¹ç¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV cuaa0</userinput></screen>
 
           <para>
             ¤Þ¤¿¤Ï <username>root</username>
             ¤Ë¤Ê¤Ã¤Æ°Ê²¼¤Î¤è¤¦¤Ë cu ¤ò»È¤¤¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
 
           <para><replaceable>line</replaceable>
             ¤Ë¤Ï¥·¥ê¥¢¥ë¥Ý¡¼¥È (¤¿¤È¤¨¤Ð
             <devicename>/dev/cuaa0</devicename>)¤ò»ØÄꤷ¤Þ¤¹¡£
             ¤½¤·¤Æ <replaceable>speed</replaceable>
             ¤Ë¤ÏÀܳ¤¹¤ë®ÅÙ (¤¿¤È¤¨¤Ð
             <literal>57600</literal>) ¤ò»ØÄꤷ¤Þ¤¹¡£
             ¤½¤Î¸å AT ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤¿¤é¡¢
             <literal>~.</literal>
             ¤ÈÆþÎϤ¹¤ì¤Ð½ªÎ»¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="gt-failure">
           <para>pn µ¡Ç½¤Î <literal>&lt;@&gt;</literal> µ­¹æ¤¬»È¤¨¤Þ¤»¤ó!</para>
         </question>
 
         <answer>
           <para>ÅÅÏÃÈÖ¹æ (pn) µ¡Ç½¤ÎÃæ¤Ç¤Î
             <literal>&lt;@&gt;</literal> µ­¹æ¤Ï¡¢
             <command>tip</command> ¤Ë
             <filename>/etc/phones</filename>
             ¤Ë¤¢¤ëÅÅÏÃÈÖ¹æ¤ò»²¾È¤¹¤ë¤è¤¦¤ËÅÁ¤¨¤Þ¤¹¡£¤·¤«¤·
             <literal>&lt;@&gt;</literal> ¤Îʸ»ú¤Ï
             <filename>/etc/remote</filename>
             ¤Î¤è¤¦¤ÊÀßÄê¥Õ¥¡¥¤¥ë¤ÎÃæ¤Ç¤ÏÆüìʸ»ú¤È¤Ê¤ê¤Þ¤¹¡£
             ¤½¤³¤Ç¡¢¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤ò»È¤Ã¤Æ¥¨¥¹¥±¡¼¥×¤ò¹Ô¤¤¤Þ¤¹¡£
           </para>
 
           <programlisting>pn=\@</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dial-command-line">
           <para>¥³¥Þ¥ó¥É¥é¥¤¥ó¤«¤éÅÅÏÃÈÖ¹æ¤ò»ØÄꤹ¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             <quote><literal>generic</literal></quote>
             ¥¨¥ó¥È¥ê¤È¸Æ¤Ð¤ì¤ë¤â¤Î¤ò
             <filename>/etc/remote</filename> ¥Õ¥¡¥¤¥ë
             (&man.remote.5; »²¾È) ¤ËÄɲä·¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
           <programlisting>tip115200|Dial any phone number at 115200 bps:\
 :dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du:
 tip57600|Dial any phone number at 57600 bps:\
 :dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du:</programlisting>
 
 
           <para>
             ¤½¤·¤Æ
             <quote><command>tip -115200 5551234</command></quote>
             ¤Î¤è¤¦¤ËÍøÍѤǤ­¤Þ¤¹¡£
             &man.tip.1; ¤è¤ê &man.cu.1; ¤ò»È¤¤¤¿¤¤¾ì¹ç¡¢
             <command>cu</command> ¤Î
             <literal>generic</literal> ¥¨¥ó¥È¥ê¤ò»È¤¤¤Þ¤¹¡£
           </para>
 
           <programlisting>cu115200|Use cu to dial any number at 115200bps:\
 :dv=/dev/cuaa1:br#57600:at=hayes:pa=none:du:</programlisting>
 
           <para>
             ¤½¤·¤Æ <quote><command>cu 5551234 -s 115200</command></quote>
             ¤È¼Â¹Ô¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="set-bps">
           <para>Ëè²ó bps ¥ì¡¼¥È¤òÆþÎϤ·¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¤«?</para>
         </question>
 
         <answer>
           <para>
             <literal>tip1200</literal> ¤ä
             <literal>cu1200</literal> ÍѤΥ¨¥ó¥È¥ê¤òµ­½Ò¤·¡¢
             ŬÀÚ¤ÊÄÌ¿®Â®ÅÙ¤ò <literal>br</literal>
             ¥Õ¥£¡¼¥ë¥É¤ËÀßÄꤷ¤Þ¤¹¡£
             &man.tip.1; ¤Ï
             1200bps ¤¬Àµ¤·¤¤¥Ç¥Õ¥©¥ë¥ÈÃͤǤ¢¤ë¤È¤ß¤Ê¤¹¤Î¤Ç¡¢
             <quote><literal>tip1200</literal></quote> ¥¨¥ó¥È¥ê¤ò»²¾È¤·¤Þ¤¹¡£
             ¤â¤Á¤í¤ó 1200bps ¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="terminal-server">
           <para>¥¿¡¼¥ß¥Ê¥ë¥µ¡¼¥Ð¤ò·Ðͳ¤·¤ÆÊ£¿ô¤Î¥Û¥¹¥È¤Ø¥¢¥¯¥»¥¹¤·¤¿¤¤¤Î¤Ç¤¹¤¬¡£</para>
         </question>
 
         <answer>
           <para>
             Ëè²óÀܳ¤µ¤ì¤ë¤Î¤òÂԤäÆ
             <quote><userinput>CONNECT &lt;<replaceable>host</replaceable>&gt;</userinput></quote>
             ¤ÈÆþÎϤ¹¤ë¤«¤ï¤ê¤Ë¡¢
             <command>tip</command> ¤Î
             <literal>cm</literal> µ¡Ç½¤ò»È¤¤¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢<filename>/etc/remote</filename> (&man.remote.5; »²¾È)
             ¤Ë¼¡¤Î¤è¤¦¤Ê¥¨¥ó¥È¥ê¤òÄɲä·¤Þ¤¹¡£
           </para>
 
 
           <programlisting>pain|pain.deep13.com|Forrester's machine:\
 	:cm=CONNECT pain\n:tc=deep13:
 muffin|muffin.deep13.com|Frank's machine:\
 	:cm=CONNECT muffin\n:tc=deep13:
 deep13:Gizmonics Institute terminal server:\
 	:dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
 
           <para>
             ¤³¤ì¤Ç¡¢<quote><command>tip <hostid>pain</hostid></command></quote>
             ¤ä <quote><command>tip <hostid>muffin</hostid></command></quote>
             ¤È¼Â¹Ô¤¹¤ë¤È
             <hostid>pain</hostid> ¤ä
             <hostid>muffin</hostid> ¤Î¥Û¥¹¥È¤ËÀܳ¤¹¤ë¤³¤È¤¬¤Ç¤­¡¢
             <quote><command>tip <hostid>deep13</hostid></command></quote>
             ¤ò¼Â¹Ô¤¹¤ë¤È¥¿¡¼¥ß¥Ê¥ë¥µ¡¼¥Ð¤ËÀܳ¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tip-multiline">
           <para>
             <command>tip</command>
             ¤ò»È¤Ã¤Æ¤½¤ì¤¾¤ì¤Î¥µ¥¤¥È¤ÎÊ£¿ô¤Î²óÀþ¤ËÀܳ¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤ÏÂç³Ø¤ËÅÅÏòóÀþ¤¬¤¤¤¯¤Ä¤«¤¢¤Ã¤Æ¡¢
             ¿ôÀé¿Í¤Î³ØÀ¸¤¬Àܳ¤·¤è¤¦¤È¤¹¤ë¾ì¹ç¤Ë¤è¤¯¤¢¤ëÌäÂê¤Ç¤¹¡£
           </para>
 
           <para>
             ¤¢¤Ê¤¿¤ÎÂç³Ø¤Î¥¨¥ó¥È¥ê¤ò
             <filename>/etc/remote</filename>
             ¥Õ¥¡¥¤¥ë (&man.remote.5; »²¾È) ¤ËºîÀ®¤·¤Æ¡¢
             <literal>pn</literal> ¤Î¥Õ¥£¡¼¥ë¥É¤Ë¤Ï
             <literal>&lt;\@&gt;</literal> ¤ò»È¤¤¤Þ¤¹¡£
           </para>
 
           <programlisting>big-university:\
 :pn=\@:tc=dialout
 dialout:\
 :dv=/dev/cuaa3:br#9600:at=courier:du:pa=none:</programlisting>
 
 
           <para>
             ¤½¤·¤Æ
             <filename>/etc/phones</filename> ¥Õ¥¡¥¤¥ë
             (&man.phones.5; »²¾È) ¤ËÂç³Ø¤ÎÅÅÏÃÈÖ¹æ¤Î°ìÍ÷¤ò½ñ¤­¤Þ¤¹¡£
           </para>
 
 
           <programlisting>big-university 5551111
 big-university 5551112
 big-university 5551113
 big-university 5551114</programlisting>
 
 
           <para>
             &man.tip.1;
             ¤Ï°ìÏ¢¤ÎÅÅÏÃÈÖ¹æ¤ò¾å¤«¤é½ç¤Ë»î¤ß¤Æ¡¢
             ºÇ½ªÅª¤ËÀܳ¤Ç¤­¤Ê¤±¤ì¤Ð¤¢¤­¤é¤á¤Þ¤¹¡£¥ê¥È¥é¥¤¤ò³¤±¤µ¤»¤¿¤¤¾ì¹ç¤Ï¡¢
             <command>tip</command> ¤ò
             while ¥ë¡¼¥×¤ËÆþ¤ì¤Æ¼Â¹Ô¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multi-controlp">
           <para><keycap>CTRL</keycap>+<keycap>P</keycap> ¤ò
             1 ²óÁ÷¤ë¤¿¤á¤Ë 2 ÅÙ²¡¤¹É¬Íפ¬¤¢¤ë¤Î¤Ï¤Ê¤¼?</para>
         </question>
 
         <answer>
           <para><keycap>CTRL</keycap>+<keycap>P</keycap>
             ¤ÏÄ̾ï¡Ö¶¯À© (force)¡×ʸ»ú¤Ç¤¢¤ê¡¢
             &man.tip.1;
             ¤Ë¼¡¤Îʸ»ú¤¬¥ê¥Æ¥é¥ë¥Ç¡¼¥¿¤Ç¤¢¤ë¤³¤È¤òÅÁ¤¨¤Þ¤¹¡£
             ¶¯À©Ê¸»ú¤Ï¡ÖÊÑ¿ô¤ÎÀßÄê¡×¤ò°ÕÌ£¤¹¤ë
             <literal>~s</literal> ¥¨¥¹¥±¡¼¥×¤Ë¤è¤Ã¤Æ¡¢
             ¾¤Îʸ»ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             <quote><literal>~sforce=<replaceable>&lt;single-char&gt;</replaceable></literal></quote>
             ¤ÈÆþÎϤ·¤Æ²þ¹Ô¤·¤Þ¤¹¡£
             <replaceable>&lt;single-char&gt;</replaceable> ¤Ï¡¢Ç¤°Õ¤Î 1 ¥Ð¥¤¥Èʸ»ú¤Ç¤¹¡£
             <replaceable>&lt;single-char&gt;</replaceable> ¤ò¾Êά¤¹¤ë¤È
             <literal>NUL</literal> ʸ»ú¤Ë¤Ê¤ê¡¢
             ¤³¤ì¤Ï <keycap>CTRL</keycap>+<keycap>2</keycap> ¤ä
             <keycap>CTRL</keycap>+<keycap>SPACE</keycap>
             ¤ò²¡¤·¤Æ¤âÆþÎϤǤ­¤Þ¤¹¡£
             ¤¤¤¯¤Ä¤«¤Î¥¿¡¼¥ß¥Ê¥ë¥µ¡¼¥Ð¤Ç»È¤ï¤ì¤Æ¤¤¤ë¤Î¤ò¸«¤¿¤À¤±¤Ç¤¹¤¬¡¢
             <replaceable>&lt;single-char&gt;</replaceable> ¤Ë
             <keycap>SHIFT</keycap>+<keycap>CTRL</keycap>+<keycap>6</keycap>
             ¤Ë³ä¤êÅö¤Æ¤ë¤Î¤â¤è¤¤¤Ç¤·¤ç¤¦¡£
           </para>
 
           <para>
             <filename>$HOME/.tiprc</filename> ¤Ë¼¡¤Î¤è¤¦¤ËÄêµÁ¤¹¤ë¤³¤È¤Ç¡¢
             Ǥ°Õ¤Îʸ»ú¤ò¶¯À©Ê¸»ú¤È¤·¤ÆÍøÍѤǤ­¤Þ¤¹¡£
           </para>
 
           <programlisting>force=<replaceable>&lt;single-char&gt;</replaceable></programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="uppercase">
           <para>ÂǤÁ¹þ¤ó¤Àʸ»ú¤¬ÆÍÁ³¤¹¤Ù¤ÆÂçʸ»ú¤Ë¤Ê¤ê¤Þ¤·¤¿??</para>
         </question>
 
         <answer>
           <para>
             <keycap>CTRL</keycap>+<keycap>A</keycap>
             ¤ò²¡¤·¤Æ¤·¤Þ¤¤¡¢<keycap>caps-lock</keycap>
             ¥­¡¼¤¬²õ¤ì¤Æ¤¤¤ë¾ì¹ç¤Î¤¿¤á¤ËÀ߷פµ¤ì¤¿
             &man.tip.1;
             ¤Î <quote>raise character</quote> ¥â¡¼¥É¤ËÆþ¤Ã¤¿¤Î¤Ç¤·¤ç¤¦¡£
             ´û¤Ë½Ò¤Ù¤¿ <literal>~s</literal> ¤ò»È¤Ã¤Æ¡¢
             <quote>raisechar</quote> ¤ò¤è¤êŬÀÚ¤ÊÃͤËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤â¤·¤³¤ì¤éξÊý¤Îµ¡Ç½¤ò»ÈÍѤ·¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢
             ¶¯À©Ê¸»ú¤ÈƱ¤¸ÀßÄê¤Ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
           </para>
 
           <para>
             °Ê²¼¤Ï <keycap>CTRL</keycap>+<keycap>2</keycap> ¤ä
             <keycap>CTRL</keycap>+<keycap>A</keycap>
             ¤Ê¤É¤òÉÑÈˤ˻Ȥ¦É¬ÍפΤ¢¤ë Emacs ¥æ¡¼¥¶¤Ë¤¦¤Ã¤Æ¤Ä¤±¤Î
             <filename>.tiprc</filename> ¥Õ¥¡¥¤¥ë¤Î¥µ¥ó¥×¥ë¤Ç¤¹¡£
           </para>
 
           <programlisting>force=^^
 raisechar=^^</programlisting>
 
           <para>
             <literal>^</literal> ¤Ï
             <keycap>SHIFT</keycap>+<keycap>CTRL</keycap>+<keycap>6</keycap> ¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tip-filetransfer">
           <para><command>tip</command> ¤Ç¥Õ¥¡¥¤¥ë¤òžÁ÷¤¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             ¤â¤·Â¾¤Î UNIX ¤Î¥·¥¹¥Æ¥à¤ÈÀܳ¤·¤Æ¤¤¤ë¤Ê¤é¡¢
             <literal>~p</literal> (Á÷¿®) ¤ä
             <literal>~t</literal> (¼õ¿®) ¤Ç¥Õ¥¡¥¤¥ë¤ÎÁ÷¼õ¿®¤¬¤Ç¤­¤Þ¤¹¡£
             ¤³¤ì¤é¤Î¥³¥Þ¥ó¥É¤Ï¡¢Áê¼ê¤Î¥·¥¹¥Æ¥à¤Î¾å¤Ç
             &man.cat.1; ¤ä &man.echo.1;
             ¤ò¼Â¹Ô¤¹¤ë¤³¤È¤ÇÁ÷¼õ¿®¤ò¤·¤Þ¤¹¡£½ñ¼°¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
           </para>
 
 
           <programlisting>~p <replaceable>&lt;¥í¡¼¥«¥ë¤Î¥Õ¥¡¥¤¥ë̾&gt;</replaceable> <replaceable>[&lt;¥ê¥â¡¼¥È¤Î¥Õ¥¡¥¤¥ë̾&gt;]</replaceable>
 ~t <replaceable>&lt;¥ê¥â¡¼¥È¤Î¥Õ¥¡¥¤¥ë̾&gt;</replaceable> <replaceable>[&lt;¥í¡¼¥«¥ë¤Î¥Õ¥¡¥¤¥ë̾&gt;]</replaceable></programlisting>
 
 
           <para>
             ¤³¤ÎÊýË¡¤Ç¤Ï¥¨¥é¡¼¥Á¥§¥Ã¥¯¤ò¹Ô¤¤¤Þ¤»¤ó¤Î¤Ç¡¢
             zmodem ¤Ê¤É¤Î¾¤Î¥×¥í¥È¥³¥ë¤ò»È¤Ã¤¿Êý¤¬¤è¤¤¤Ç¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="zmodem-tip">
           <para><application>tip</application> ¤«¤é zmodem ¤ò¼Â¹Ô¤¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             ¤Þ¤º»Ï¤á¤Ë¡¢FreeBSD Ports
             Collection ¤«¤é zmodem ¥×¥í¥°¥é¥à¤Î¤¤¤º¤ì¤«
             (<application>lrzsz</application>¤È <application>rzsz</application>
             ¤Î¡¢ÄÌ¿®¥«¥Æ¥´¥ê¡¼¤Î2 ¤Ä¤Î¥×¥í¥°¥é¥à¤Î¤É¤Á¤é¤«) ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Õ¥¡¥¤¥ë¤ò¼õ¿®¤¹¤ë¤Ë¤Ï¡¢¥ê¥â¡¼¥È¦¤ÇÁ÷¿®¥×¥í¥°¥é¥à¤òµ¯Æ°¤·¤Þ¤¹¡£
             ¤½¤·¤Æ¡¢<keycap>Enter</keycap> ¥­¡¼¤ò²¡¤·¤Æ¤«¤é
             <quote><literal>~C rz</literal></quote>
             (lrzsz ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¾ì¹ç¤Ï
             <quote><literal>~C lrz</literal></quote>) ¤ÈÆþÎϤ¹¤ë¤È¡¢
             ¥í¡¼¥«¥ë¦¤Ø¤Î¥Õ¥¡¥¤¥ë¤Î¼õ¿®¤¬»Ï¤Þ¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¥Õ¥¡¥¤¥ë¤òÁ÷¿®¤¹¤ë¤Ë¤Ï¡¢¥ê¥â¡¼¥È¦¤Ç¼õ¿®¥×¥í¥°¥é¥à¤òµ¯Æ°¤·¤Þ¤¹¡£
             ¤½¤·¤Æ¡¢<keycap>Enter</keycap> ¥­¡¼¤ò²¡¤·¤Æ¤«¤é
             <quote><literal>~C sz <replaceable>&lt;files&gt;</replaceable></literal></quote>
             (lrzsz ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¾ì¹ç¤Ï
             <quote><literal>~C lsz
               <replaceable>&lt;files&gt;</replaceable></literal></quote>)
             ¤ÈÆþÎϤ¹¤ë¤È¡¢¥ê¥â¡¼¥È¦¤Ø¤Î¥Õ¥¡¥¤¥ë¤ÎÁ÷¿®¤¬»Ï¤Þ¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cannot-find-serial">
           <para>ÀßÄ꤬Àµ¤·¤¤¤Î¤Ë¤â¤«¤«¤ï¤é¤º¡¢FreeBSD ¤¬¥·¥ê¥¢¥ë¥Ý¡¼¥È¤ò¸«ÉÕ¤±¤é¤ì¤Þ¤»¤ó¡£</para>
         </question>
 
         <answer>
           <para>
             ¥Þ¥¶¡¼¥Ü¡¼¥É¤ä¥·¥ê¥¢¥ë¥«¡¼¥É¤¬ Acer ¤Î UART ¥Á¥Ã¥×¤ò»È¤Ã¤¿Êª¤Î¾ì¹ç¡¢
             FreeBSD ¤Î <devicename>sio</devicename> ¥É¥é¥¤¥Ð¤Ç¤ÏÀµ¤·¤¯¸¡½Ð¤¹¤ë»ö¤¬½ÐÍè¤Þ¤»¤ó¡£
             ¤³¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
             <ulink url="http://www.lemis.com/serial-port-patch.html">www.lemis.com</ulink>
             ¤«¤é¥Ñ¥Ã¥Á¤òÆþ¼ê¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="misc">
     <title>¤½¤Î¾¤Î¼ÁÌä</title>
 
     <para>
       <emphasis>Ìõ:
         &a.jp.yoshiaki;¡¢
         &a.jp.sugimura;¡¢
         Ê¡´Ö ¹¯¹° <email>yasuf@big.or.jp</email>¡¢
         1997 ǯ 11 ·î 10 Æü - 1999 ǯ 5 ·î 8 Æü</emphasis>
     </para>
 
 
     <qandaset>
       <qandaentry>
         <question id="more-swap">
           <para>FreeBSD ¤Ï Linux ¤è¤ê¿¤¯¤Î¥¹¥ï¥Ã¥×Îΰè¤ò¾ÃÈñ¤¹¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¼ÂºÝ¤Ë¤Ï¤½¤¦¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             FreeBSD ¤Ï Linux ¤è¤ê¤â¥¹¥ï¥Ã¥×¤ò¿¤¯»È¤Ã¤Æ¤¤¤ë¤è¤¦¤Ë¸«¤¨¤ë¤À¤±¤Ç¤¹¡£
             ¤³¤ÎÅÀ¤Ë¤ª¤±¤ë FreeBSD ¤È Linux ¤Î¼ç¤Ê°ã¤¤¤Ï¡¢
             FreeBSD ¤Ï¤è¤ê¿¤¯¤Î¥á¥¤¥ó¥á¥â¥ê¤òÍ­¸úÍøÍѤǤ­¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¡¢
             ´°Á´¤Ë¥¢¥¤¥É¥ë¤Ë¤Ê¤Ã¤¿¤â¤Î¤ä¥á¥¤¥ó¥á¥â¥ê¾å¤Î»È¤ï¤ì¤Ê¤¯¤Ê¤Ã¤¿¥Ú¡¼¥¸¤ò¡¢
             ¥¹¥ï¥Ã¥×¤Ë¤¢¤é¤«¤¸¤áÀѶËŪ¤Ë°ÜÆ°¤·¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£
             Linux ¤Ç¤Ï¡¢
             ºÇ¸å¤Î¼êÃʤȤ·¤Æ¥Ú¡¼¥¸¤ò¥¹¥ï¥Ã¥×¤Ë°ÜÆ°¤µ¤»¤ë¤À¤±¤È¤¤¤¦·¹¸þ¤¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤Î¥¹¥ï¥Ã¥×¤Î»È¤¤Êý¤Ï¡¢
             ¥á¥¤¥ó¥á¥â¥ê¤ò¤è¤ê¸ú²ÌŪ¤Ë»ÈÍѤ¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¥Ð¥é¥ó¥¹¤¬Êݤ¿¤ì¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             FreeBSD ¤Ï¤³¤Î¤è¤¦¤Ê¾õ¶·¤Ç¤ÏÀè¼êºö¤ò¼è¤ê¤Þ¤¹¤¬¡¢
             ¥·¥¹¥Æ¥à¤¬ËÜÅö¤Ë¶õ¤­¾õÂ֤λþ¤Ë¡¢
             Íýͳ¤â̵¤¯¥Ú¡¼¥¸¤ò¥¹¥ï¥Ã¥×¤·¤è¤¦¤È·è¤á¤ë¤³¤È¤Ï¤Ê¤¤¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤·¤¿¤¬¤Ã¤Æ¡¢
             ÌëÃæ¤Ë»È¤ï¤º¤Ë¤ª¤¤¤¿¥·¥¹¥Æ¥à¤¬Ä«µ¯¤­¤¿¤È¤­¡¢
             ¤¹¤Ù¤Æ¥Ú¡¼¥¸¥¢¥¦¥È¤µ¤ì¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È¤Ï¤Ê¤¤¤Î¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="top-freemem">
           <para>¤Û¤È¤ó¤É¥×¥í¥°¥é¥à¤Ï¼Â¹Ô¤µ¤ì¤Æ¤¤¤Ê¤¤¤Î¤Ë¡¢
               ¤É¤¦¤·¤Æ &man.top.1; ¤ÏÈó¾ï¤Ë¾¯¤Ê¤¤ free memory ¤òÊó¹ð¤¹¤ë¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>´Êñ¤Ë¸À¤¨¤Ð¡¢free memory
             ¤È¤Ï̵Â̤ˤʤäƤ¤¤ë¥á¥â¥ê¤Î¤³¤È¤À¤«¤é¤Ç¤¹¡£
             ¥×¥í¥°¥é¥à¤¬³ÎÊݤ·¤Æ¤¤¤ë¥á¥â¥ê°Ê³°¤Î¤¹¤Ù¤Æ¤Î¥á¥â¥ê¤Ï¡¢
             FreeBSD ¥«¡¼¥Í¥ëÆâ¤Ç¥Ç¥£¥¹¥¯¥­¥ã¥Ã¥·¥å¤È¤·¤ÆÍøÍѤµ¤ì¤Þ¤¹¡£
             ¤³¤ÎÃÍ¤Ï &man.top.1; ¤Ë¤ª¤¤¤Æ
             <literal>Inact</literal>¡¢
             <literal>Cache</literal>
             <literal>Buf</literal> ¤È¤·¤Æɽ¼¨¤µ¤ì¡¢
             ¤½¤ì¤¾¤ì¤Ï°Û¤Ê¤ë¥¨¡¼¥¸¥ó¥°¥ì¥Ù¥ë
             (ÌõÃí: ¥Ç¡¼¥¿¤¬¤É¤ì¤À¤±¸Å¤¤¤«¤ò¼¨¤¹É¾²ÁÃÍ)
             ¤Ç¥­¥ã¥Ã¥·¥å¤µ¤ì¤¿Á´¥Ç¡¼¥¿¤òɽ¤·¤Þ¤¹¡£
             ¥Ç¡¼¥¿¤¬¥­¥ã¥Ã¥·¥å¤µ¤ì¤ë¤È¸À¤¦¤Î¤Ï¡¢
             ºÇ¶á¥¢¥¯¥»¥¹¤µ¤ì¤¿¥Ç¡¼¥¿¤Ç¤¢¤ì¤Ð¡¢
             ºÆÅÙ¤½¤Î¥Ç¡¼¥¿¤ò¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë¥·¥¹¥Æ¥à¤¬ÃÙ¤¤¥Ç¥£¥¹¥¯¤Ë¥¢¥¯¥»¥¹¤¹¤ëɬÍפ¬¤Ê¤¤¡¢
             ¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
             ¤½¤Î¤¿¤á¡¢Á´ÂΤΥѥե©¡¼¥Þ¥ó¥¹¤¬¸þ¾å¤·¤Þ¤¹¡£
             °ìÈÌŪ¤Ë¡¢&man.top.1; ¤Çɽ¼¨¤µ¤ì¤ë
             <literal>Free</literal> ¥á¥â¥ê¤¬¾®¤µ¤¤Ãͤò¼¨¤¹¤³¤È¤ÏÎɤ¤¤³¤È¤Ç¡¢
             ¼«Í³¤Ë»È¤¨¤ë¥á¥â¥ê¤Î»ÄÎ̤¬<emphasis>ËÜÅö¤Ë</emphasis>¾¯¤Ê¤¤¡¢
             ¤È¤¤¤¦¤³¤È¤òɽ¤·¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="aout-elf">
           <para>FreeBSD ¤Î¼Â¹Ô¥Õ¥©¡¼¥Þ¥Ã¥È¤Î a.out¡¢ELF
             ¤È¤Ï¤É¤Î¤è¤¦¤Ê¤â¤Î¤Ç¤¹¤«?
             ¤Þ¤¿¡¢a.out¡¢ELF ¤ò»È¤¦Íýͳ¤Ï²¿¤Ç¤·¤ç¤¦?</para></question>
 
         <answer>
           <para>
             FreeBSD ¤¬²¿¸Î ELF
             ¥Õ¥©¡¼¥Þ¥Ã¥È¤òÍøÍѤ·¤Æ¤¤¤ë¤Î¤«¤òÍý²ò¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
             ¤Þ¤º UNIX¤Ë¤ª¤¤¤Æ¸½ºß¡ÖÍ¥Àª¡×¤Ê
             3 ¼ïÎà¤Î¼Â¹Ô¥Õ¥©¡¼¥Þ¥Ã¥È¤Ë¤Ä¤¤¤Æ
             ¤¤¤¯¤é¤«ÃΤäƤª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
             <note>
               <para>FreeBSD 3.x ¤è¤êÁ°¤Î FreeBSD ¤Ç¤Ï a.out
                 ¥Õ¥©¡¼¥Þ¥Ã¥È¤¬»È¤ï¤ì¤Æ¤¤¤Þ¤·¤¿¡£</para>
             </note>
 
 
           <itemizedlist>
             <listitem>
               <para>&man.a.out.5;</para>
 
                 <para>
                   ºÇ¤â¸Å¤¯ ¡Öͳ½ïÀµ¤·¤¤¡× unix ¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥©¡¼¥Þ¥Ã¥È¤Ç¤¹¡£
                   ¥Þ¥¸¥Ã¥¯¥Ê¥ó¥Ð¤ò´Þ¤àû¤¯¤Æ¥³¥ó¥Ñ¥¯¥È¤Ê¥Ø¥Ã¥À¤¬ÀèƬ¤Ë¤¢¤ê¡¢
                   ¤³¤ì¤¬¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎÆÃħ¤È¤µ¤ì¤Æ¤¤¤Þ¤¹
                   (&man.a.out.5; ¤Ë¾ÜºÙ¤ÊÆâÍƤ¬¤¢¤ê¤Þ¤¹)¡£
                   ¥í¡¼¥É¤µ¤ì¤ë 3¼ïÎà¤Î¥»¥°¥á¥ó¥È¡¢
                   <literal>.text</literal>¡¢
                   <literal>.data</literal>¡¢
                   <literal>.bss</literal>
                   ¤È²Ã¤¨¤Æ¥·¥ó¥Ü¥ë¥Æ¡¼¥Ö¥ë¤Èʸ»úÎó¥Æ¡¼¥Ö¥ë¤ò´Þ¤ß¤Þ¤¹¡£
                 </para>
             </listitem>
 
             <listitem>
               <para><acronym>COFF</acronym></para>
                 <para>
                   SVR3 ¤Î¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥©¡¼¥Þ¥Ã¥È¤Ç¤¹¡£
                   ¥Ø¥Ã¥À¤Ïñ°ì¤Î¥»¥¯¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤«¤éÀ®¤ê¡¢
                   <literal>.text</literal>¡¢
                   <literal>.data</literal>¡¢
                   <literal>.bss</literal>
                   ¥»¥¯¥·¥ç¥ó°Ê³°¤ÎÉôʬ¤ò»ý¤Ä¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
                 </para>
             </listitem>
 
             <listitem>
               <para><acronym>ELF</acronym></para>
                 <para>
                   <acronym>COFF</acronym>¤Î¸å·Ñ¤Ç¤¹¡£Ê£¿ô¤Î¥»¥¯¥·¥ç¥ó¤ò¥µ¥Ý¡¼¥È¤·¡¢32-bit
                   ¤È 64-bit¤Î¤¤¤º¤ì¤ÎÃͤâ²Äǽ¤Ç¤¹¡£Â礭¤Ê·çÅÀ¤Î°ì¤Ä¤Ï¡¢<acronym>ELF</acronym>
                   ¤Ï¤½¤ì¤¾¤ì¤Î¥·¥¹¥Æ¥à¥¢¡¼¥­¥Æ¥¯¥Á¥ãËè¤Ëñ°ì¤Î <acronym>ABI</acronym>
                   ¤Î¤ß¤¬Â¸ºß¤¹¤ë¤È¤¤¤¦²¾Äê¤ÇÀ߷פµ¤ì¤Æ¤¤¤ë¤³¤È¤Ç¤¹¡£
                   ¤³¤Î²¾Äê¤Ï¤Þ¤Ã¤¿¤¯Àµ¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£
                   ¾¦ÍѤΠSYSV ¤ÎÀ¤³¦¤Ç¤µ¤¨¤½¤¦¤Ç¤¹ (¾¯¤Ê¤¯¤È¤â SVR4¡¢
                   Solaris¡¢SCO ¤Î 3¼ïÎà¤Î ABI ¤¬¤¢¤ê¤Þ¤¹)¡£
                 </para>
 
                 <para>
                   FreeBSD ¤Ï¤³¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Î»î¤ß¤È¤·¤Æ¡¢
                   ´ûÃΤΠ<acronym>ELF</acronym>
                   ¼Â¹Ô¥Õ¥¡¥¤¥ë¤Ë <acronym>ABI</acronym> ¤Ë±þ¤¸¤¿¾ðÊó¤ò
                   <emphasis>½ñ¤­²Ã¤¨¤ë</emphasis>¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£
                   ¾Ü¤·¤¯¤Ï &man.brandelf.1;
                   ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
                 </para>
             </listitem>
           </itemizedlist>
 
           <para>
             FreeBSD ¤ÏÅÁÅýŪ¤ÊΩ¾ì¤ò¤È¤ê¡¢¿ô¿¤¯¤ÎÀ¤Âå¤Î BSD
             ¤Î¥ê¥ê¡¼¥¹¤Ç»î¤µ¤ì¡¢¼Â¾Ú¤µ¤ì¤Æ¤­¤¿
             &man.a.out.5;
             ¥Õ¥©¡¼¥Þ¥Ã¥È¤òÅÁÅýŪ¤Ë»ÈÍѤ·¤Æ¤¤¤Þ¤¹¡£
             ¤¤¤Ä¤«¤Ï FreeBSD ¥·¥¹¥Æ¥à¤Ç¥Í¥¤¥Æ¥£¥Ö
             <acronym>ELF</acronym> ¥Ð¥¤¥Ê¥ê¤òºî¤ê¡¢
             ¼Â¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢
             ½é´ü¤Îº¢ FreeBSD
             ¤Ç¤Ï <acronym>ELF</acronym>
             ¤ò¥Ç¥Õ¥©¥ë¥È¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤ËÊѹ¹¤¹¤ë¤È¤¤¤¦Æ°¤­¤Ï
             ¤¢¤ê¤Þ¤»¤ó¤Ç¤·¤¿¡£¤Ê¤¼¤Ç¤·¤ç¤¦¤«?
             ¤È¤³¤í¤Ç Linux ¤Ë¤ª¤¤¤Æ¤Ï¡¢
             <acronym>ELF</acronym> ¤Ø¤Î¶ìÄˤò¤È¤â¤Ê¤Ã¤¿Êѹ¹¤Ï¡¢
             ¤½¤Î»þ¤Ë <filename>a.out</filename>
             ¼Â¹Ô¥Õ¥©¡¼¥Þ¥Ã¥È¤«¤éƨ¤ì¤¿¤È¤¤¤¦¤è¤ê¤Ï¡¢
             ¥¸¥ã¥ó¥×¥Æ¡¼¥Ö¥ë¥Ù¡¼¥¹¤Î¶¦Í­¥é¥¤¥Ö¥é¥ê¤Î¥á¥«¥Ë¥º¥à¤Î½ÀÆðÀ­¤ÎÄ㤵¤«¤é¤ÎæµÑ¤Ç¤·¤¿¡£
             ¤³¤ì¤Ï¥Ù¥ó¥À¤ä³«È¯¼ÔÁ´ÂΤˤȤäơ¢
             ¶¦Í­¥é¥¤¥Ö¥é¥ê¤ÎºîÀ®¤¬Èó¾ï¤ËÆñ¤·¤«¤Ã¤¿¸¶°ø¤Ç¤·¤¿¡£
             <acronym>ELF</acronym>
             ¤Î¥Ä¡¼¥ë¤Ë¤Ï¶¦Í­¥é¥¤¥Ö¥é¥ê¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤â¤Î¤¬Ä󶡤µ¤ì¤Æ¤ª¤ê¡¢
             ¤Þ¤¿¤¤¤º¤ì¤Ë¤»¤è°ìÈÌŪ¤Ë¡Ö¿ÊÊâ¡×¤·¤Æ¤¤¤ë¤È¹Í¤¨¤é¤ì¤Þ¤¹¡£
             ¤³¤Î¤¿¤á°Ü¹Ô¤Î¥³¥¹¥È¤ÏɬÍפʤâ¤Î¤È¤·¤ÆÍÆǧ¤µ¤ì¡¢
             °Ü¹Ô¤Ï¹Ô¤Ê¤ï¤ì¤Þ¤·¤¿¡£
           </para>
 
           <para>
             FreeBSD ¤Î¾ì¹ç¤Ï¡¢¶¦Í­¥é¥¤¥Ö¥é¥ê¤Î¥á¥«¥Ë¥º¥à¤Ï Sun ¤Î
             <application>SunOS</application> ·Á¼°¤Î¶¦Í­¥é¥¤¥Ö¥é¥ê¤Î
             ¥á¥«¥Ë¥º¥à¤Ë¶Ë¤á¤Æ¶á¤¤¤â¤Î¤Ë¤Ê¤Ã¤Æ¤¤¤Æ¡¢
             Èó¾ï¤Ë»È¤¤¤ä¤¹¤¤¤â¤Î¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             ¤·¤«¤·¤Ê¤¬¤é¡¢FreeBSD ¤Ç¤Ï 3.0 ¤«¤é <acronym>ELF</acronym>
             ¥Ð¥¤¥Ê¥ê¤ò¥Ç¥Õ¥©¥ë¥È¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤È¤·¤Æ¸ø¼°¤Ë¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             a.out ¼Â¹Ô¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï¤è¤¤¤â¤Î¤ò»äã¤ËÄ󶡤·¤Æ¤¯¤ì¤Æ¤¤¤ë¤â¤Î¤Î¡¢
             »ä¤¿¤Á¤Î»È¤Ã¤Æ¤¤¤ë¥³¥ó¥Ñ¥¤¥é¤Îºî¼Ô¤Ç¤¢¤ë GNU ¤Î¿Í¡¹¤Ï
             a.out ¥Õ¥©¡¼¥Þ¥Ã¥È¤Î¥µ¥Ý¡¼¥È¤ò¤ä¤á¤Æ¤·¤Þ¤Ã¤¿¤Î¤Ç¤·¤¿¡£
             ¤³¤Î¤³¤È¤Ï¡¢
             »ä¤¿¤Á¤ËÊ̥С¼¥¸¥ç¥ó¤Î¥³¥ó¥Ñ¥¤¥é¤È¥ê¥ó¥«¤òÊݼ餹¤ë¤³¤È¤ò;µ·¤Ê¤¯¤µ¤ì¤ë¤³¤È¤È¤Ê¤ê¡¢
             ºÇ¿·¤Î GNU ³«È¯¤ÎÅØÎϤˤè¤ë²¸·Ã¤«¤é±ó¤¶¤«¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¤½¤Î¾å¡¢ISO C++ ¤Î¡¢
             ¤È¤¯¤Ë¥³¥ó¥¹¥È¥é¥¯¥¿¤ä¥Ç¥¹¥È¥é¥¯¥¿¤¬¤é¤ß¤ÎÍ×µá¤â¤¢¤Ã¤Æ¡¢º£¸å¤Î
             FreeBSD ¤Î¥ê¥ê¡¼¥¹¤Ç¥Í¥¤¥Æ¥£¥Ö¤Î <acronym>ELF</acronym>
             ¤Î¥µ¥Ý¡¼¥È¤µ¤ì¤ëÊý¸þ¤Ø¤ÈÏ䬿ʤó¤Ç¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="binary-formats">
           <para>¤½¤ì¤Ë¤·¤Æ¤â¡¢¤Ê¤¼¤½¤ó¤Ê¤Ë¿¤¯¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤¬¤¢¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤â¤¦¤ª¤Ü¤í¤²¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤¿°Å¤¤²áµî¤Ë¡¢Ã±½ã¤Ê¥Ï¡¼¥É¥¦¥§¥¢¤¬¤¢¤ê¤Þ¤·¤¿¡£
             ¤³¤Îñ½ã¤Ê¥Ï¡¼¥É¥¦¥§¥¢¤Ï¡¢Ã±½ã¤Ç¾®¤µ¤Ê¥·¥¹¥Æ¥à¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤·¤¿¡£
             a.out ¤Ï¤³¤Îñ½ã¤Ê¥·¥¹¥Æ¥à (PDP-11)
             ¤Ç¤Îºî¶È¤ò¹Ô¤Ê¤¦¥Ð¥¤¥Ê¥ê¤È¤·¤Æ´°Á´¤ËŬ¤·¤¿¤â¤Î¤À¤Ã¤¿¤Î¤Ç¤¹¡£
             ¿Í¡¹¤Ï¤³¤Îñ½ã¤Ê¥·¥¹¥Æ¥à¤«¤é UNIX ¤ò°Ü¿¢¤¹¤ëºÝ¤Ë¡¢a.out
             ¥Õ¥©¡¼¥Þ¥Ã¥È¤ò¤½¤Î¤Þ¤Þ»È¤¤¤Þ¤·¤¿¡£¤È¤¤¤¦¤Î¤Ï
             Motorola 68k¡¢VAXen¡¢
             ¤È¤¤¤Ã¤¿¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ø¤Î UNIX ¤Î½é´ü¤Î°Ü¿¢¤Ç¤Ï¤³¤ì¤Ç½½Ê¬¤À¤Ã¤¿¤«¤é¤Ç¤¹¡£
           </para>
 
           <para>
             ¤ä¤¬¤Æ¤¢¤ëÁïÌÀ¤Ê¥¨¥ó¥¸¥Ë¥¢¤¬¡¢
             ¥½¥Õ¥È¥¦¥§¥¢¤Ç¤Á¤ç¤Ã¤È¤·¤¿¥È¥ê¥Ã¥¯¤ò»È¤¦¤³¤È¤ò·è¤á¤Þ¤·¤¿¡£
             Èà¤Ï¤¤¤¯¤Ä¤«¤Î¥²¡¼¥È¤òºï¤ê¼è¤Ã¤Æ
             CPU ¤Î¥³¥¢¤ò¤è¤ê®¤¯Áö¤é¤»¤ë¤³¤È¤¬¤Ç¤­¤¿¤Î¤Ç¤¹¡£
             ¤³¤ì¤Ï¿·¤·¤¤¼ïÎà¤Î¥Ï¡¼¥É¥¦¥§¥¢ (º£Æü¤Ç¤Ï <acronym>RISC</acronym>
             ¤È¤·¤ÆÃΤé¤ì¤Æ¤¤¤Þ¤¹) ¤ÇÆ°¤¤¤¿¤Î¤Ç¤¹¡£
             a.out ¤Ï¤³¤Î¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤ÏŬ¤·¤Æ¤¤¤Ê¤«¤Ã¤¿¤Î¤Ç¡¢
             ¤³¤Î¥Ï¡¼¥É¥¦¥§¥¢¾å¤Ç¿¤¯¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤¬¡¢
             ¸ÂÄꤵ¤ì¤¿Ã±½ã¤Ê a.out
             ¥Õ¥©¡¼¥Þ¥Ã¥È¤Ç¤Î¤â¤Î¤è¤ê¤â¤è¤êÎɤ¤¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤ò½Ð¤¹¤³¤È¤òÌܻؤ·¤Æ³«È¯¤µ¤ì¤¿¤Î¤Ç¤¹¡£
             <acronym>COFF</acronym>¡¢<acronym>ECOFF</acronym>¡¢
             ¤½¤·¤Æ¤¤¤¯¤Ä¤«¤Îͭ̾¤Ç¤Ê¤¤¥Õ¥©¡¼¥Þ¥Ã¥È¤¬
             <acronym>ELF</acronym> ¤¬É¸½à¤Ë¤Ê¤ëÁ°¤Ë³«È¯¤µ¤ì¡¢
             ¤½¤ì¤é¤Î¸Â³¦¤¬Ãµµá¤µ¤ì¤¿¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¤µ¤é¤Ë¡¢¥×¥í¥°¥é¥à¥µ¥¤¥º¤ÏµðÂç¤Ë¤Ê¤ê¡¢
             ¥Ç¥£¥¹¥¯ (¤ª¤è¤ÓʪÍý¥á¥â¥ê) ¤Ï°ÍÁ³¤È¤·¤ÆÁêÂÐŪ¤Ë¾®¤µ¤«¤Ã¤¿¤¿¤á¡¢
             ¶¦Íѥ饤¥Ö¥é¥ê¤Î¥³¥ó¥»¥×¥È¤¬ÃÂÀ¸¤·¤Þ¤·¤¿¡£
             ¤Þ¤¿¡¢VM ¥·¥¹¥Æ¥à¤Ï¤è¤êÊ£»¨¤Ê¤â¤Î¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
             ¤³¤ì¤é¤Î¸Ä¡¹¤Î¿ÊÊâ¤Ï a.out ¥Õ¥©¡¼¥Þ¥Ã¥È¤ò»ÈÍѤ·¤Æ¿ë¤²¤é¤ì¤Þ¤·¤¿¤¬¡¢
             ¤½¤ÎÍ­ÍÑÀ­¤Ï¿·¤·¤¤µ¡Ç½¤È¤È¤â¤Ë¤É¤ó¤É¤ó¹­¤¬¤Ã¤Æ¤­¤Þ¤·¤¿¡£
             ¤³¤ì¤é¤Ë²Ã¤¨¡¢¼Â¹Ô»þ¤ËɬÍפʤâ¤Î¤òưŪ¤Ë¥í¡¼¥É¤¹¤ë¡¢
             ¤Þ¤¿¤Ï½é´ü²½¥³¡¼¥É¤Î¼Â¹Ô¸å¤Ë¥×¥í¥°¥é¥à¤Î°ìÉô¤òÇË´þ¤·¡¢
             ¥³¥¢¥á¥â¥ê¤ª¤è¤Ó¥¹¥ï¥Ã¥×¶õ´Ö¤òÀáÌ󤹤ë¤È¤¤¤¦Í×˾¤¬¹â¤Þ¤ê¤Þ¤·¤¿¡£
             ¥×¥í¥°¥é¥ß¥ó¥°¸À¸ì¤Ï¤µ¤é¤ËÊ£»¨¤Ë¤Ê¤ê¡¢<literal>main</literal>
             ´Ø¿ô¤ÎÁ°¤Ë¼«Æ°Åª¤Ë¥³¡¼¥ë¤µ¤ì¤ë¥³¡¼¥É¤ÎÍ×˾¤¬¹â¤Þ¤ê¤Þ¤·¤¿¡£
             ¿¤¯¤Îµ¡Ç½³ÈÄ¥¤¬¹Ô¤Ê¤ï¤ì¡¢a.out
             ¥Õ¥©¡¼¥Þ¥Ã¥È¤¬¤³¤ì¤é¤¹¤Ù¤Æ¤ò¼Â¸½¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¡¢
             ¤½¤ì¤é¤Ï¤·¤Ð¤é¤¯¤Ï´ðËÜŪ¤ËÆ°ºî¤·¤Æ¤¤¤Þ¤·¤¿¡£
             ¤ä¤¬¤Æ¡¢a.out ¤Ï¥³¡¼¥É¤Ç¤Î¥ª¡¼¥Ð¥Ø¥Ã¥É¤ÈÊ£»¨¤µ¤òÁýÂ礵¤»¤º¤Ë¡¢
             ¤³¤ì¤é¤ÎÌäÂꤹ¤Ù¤Æ¤ò½èÍý¤¹¤ë¤³¤È¤Ë̵Íý¤¬¤Ç¤Æ¤­¤Þ¤·¤¿¡£
             °ìÊý¡¢<acronym>ELF</acronym> ¤Ï¤³¤ì¤é¤ÎÌäÂê¤Î¿¤¯¤ò²ò·è¤·¤Þ¤¹¤¬¡¢
             ¸½¾õ²ÔƯ¤·¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤«¤é¤ÎÀÚÂؤ¨¤ÏÌñ²ð¤Ê¤â¤Î¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
             ¤½¤Î¤¿¤á <acronym>ELF</acronym> ¤Ï¡¢a.out ¤Î¤Þ¤Þ¤Ç¤¤¤ë¤³¤È¤¬
             <acronym>ELF</acronym>
             ¤Ø¤Î°Ü¹Ô¤è¤ê¤â¤â¤Ã¤ÈÌñ²ð¤Ê¤â¤Î¤Ë¤Ê¤ë¤Þ¤ÇÂÔ¤ÄɬÍפ¬¤¢¤ê¤Þ¤·¤¿¡£
           </para>
 
           <para>
             ¤·¤«¤·»þ¤¬·Ð¤Ä¤Ë¤Ä¤ì¡¢FreeBSD
             ¤Î¥Ó¥ë¥É¥Ä¡¼¥ë¤Î¸µ¤È¤Ê¤Ã¤¿¥Ä¡¼¥ë·² (Æä˥¢¥»¥ó¥Ö¥é¤È¥í¡¼¥À) ¤È
             FreeBSD ¤Î¥Ó¥ë¥É¥Ä¡¼¥ë·²¤Ï°Û¤Ê¤Ã¤¿¿Ê²½¤Î·ÐÏ©¤ò¤¿¤É¤ê¤Þ¤·¤¿¡£
             FreeBSD ¤Î¥Ä¥ê¡¼¤Ç¤Ï¡¢¶¦Í­¥é¥¤¥Ö¥é¥ê¤¬Äɲ䵤졢
             ¥Ð¥°¥Õ¥£¥Ã¥¯¥¹¤â¹Ô¤ï¤ì¤Þ¤·¤¿¡£
             ¤â¤È¤â¤È¤Î¥Ä¡¼¥ë·²¤òºîÀ®¤·¤¿ GNU ¤Î¿Í¤¿¤Á¤Ï¡¢¥×¥í¥°¥é¥à¤ò½ñ¤­Ä¾¤·¡¢
             ¥¯¥í¥¹¥³¥ó¥Ñ¥¤¥é¤Î¥µ¥Ý¡¼¥È¡¢
             °Û¤Ê¤ë¥Õ¥©¡¼¥Þ¥Ã¥È¤òǤ°Õ¤Ë¼è¤ê¹þ¤àµ¡Ç½¤Ê¤É¤òÄɲ䷤Ƥ¤¤­¤Þ¤·¤¿¡£
             ¿¤¯¤Î¿Í¡¹¤¬ FreeBSD
             ¤ò¥¿¡¼¥²¥Ã¥È¤È¤·¤¿¥¯¥í¥¹¥³¥ó¥Ñ¥¤¥é¤Î¹½ÃÛ¤ò»î¤ß¤Þ¤·¤¿¤¬¡¢
             FreeBSD ¤Î»È¤Ã¤Æ¤¤¤ë <command>as</command> ¤È
             <command>ld</command>
             ¤Î¸Å¤¤¥×¥í¥°¥é¥à¥³¡¼¥É¤Ï¥¯¥í¥¹¥³¥ó¥Ñ¥¤¥ë¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤ª¤é¤º¡¢
             ¤¦¤Þ¤¯¤¤¤­¤Þ¤»¤ó¤Ç¤·¤¿¡£
             ¿·¤·¤¤ GNU ¤Î¥Ä¡¼¥ë·² (binutils) ¤Ï¡¢
             ¥¯¥í¥¹¥³¥ó¥Ñ¥¤¥ë¡¢¶¦Í­¥é¥¤¥Ö¥é¥ê¡¢C++
             ³ÈÄ¥¤Ê¤É¤Îµ¡Ç½¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             ¤µ¤é¤Ë¿ô¿¤¯¤Î¥Ù¥ó¥À¤¬
             <acronym>ELF</acronym> ¥Ð¥¤¥Ê¥ê¤ò¥ê¥ê¡¼¥¹¤·¤Æ¤¤¤Þ¤¹¡£
             FreeBSD ¤Ë¤È¤Ã¤Æ <acronym>ELF</acronym>
             ¥Ð¥¤¥Ê¥ê¤¬¼Â¹Ô¤Ç¤­¤ë¤³¤È¤Ï¡¢
             Èó¾ï¤Ë¥á¥ê¥Ã¥È¤¬¤¢¤ê¤Þ¤¹¡£<acronym>ELF</acronym> ¥Ð¥¤¥Ê¥ê¤¬
             FreeBSD ¤ÇÆ°¤¯¤Î¤Ê¤é¡¢a.out
             ¤òÆ°¤«¤¹¤Î¤Ë¼ê´Ö¤ò¤«¤±¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¤Í¡£
             Ť¤´ÖÃé¼Â¤Ë¤è¤¯Æ¯¤¤¤¿Ï·¤¤¤¿ÇϤϡ¢
             ¤½¤í¤½¤íËÒÁðÃϤǵ٤ޤ»¤Æ¤¢¤²¤Þ¤·¤ç¤¦¡£
           </para>
 
           <para>
             <acronym>ELF</acronym> ¤Ï a.out ¤ËÈæ¤Ù¤Æ¤è¤êɽ¸½ÎϤ¬¤¢¤ê¡¢
             ¥Ù¡¼¥¹¤Î¥·¥¹¥Æ¥à¤ËÂФ·¤Æ¤è¤êÉý¹­¤¤³ÈÄ¥À­¤òÄ󶡤Ǥ­¤Þ¤¹¡£
             <acronym>ELF</acronym> ÍѤΥġ¼¥ë¤Ï¤è¤ê¤è¤¯Êݼ餵¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤Þ¤¿Â¿¤¯¤Î¿Í¤Ë¤È¤Ã¤Æ½ÅÍפʥ¯¥í¥¹¥³¥ó¥Ñ¥¤¥ë¤â¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
             <acronym>ELF</acronym> ¤Î¼Â¹Ô®Å٤ϡ¢¤Û¤ó¤Î¾¯¤· a.out ¤è¤êÃÙ¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢
             ¼ÂºÝ¤Ë®Å٤κ¹¤ò¤Ï¤«¤ë¤Î¤Ïº¤Æñ¤Ç¤·¤ç¤¦¡£
             <acronym>ELF</acronym> ¤È a.out ¤Î´Ö¤Ë¤Ï¡¢¥Ú¡¼¥¸¥Þ¥Ã¥Ô¥ó¥°¡¢
             ½é´ü²½¥³¡¼¥É¤Î½èÍý¤Ê¤É¿¤¯¤Î°ã¤¤¤¬¤¢¤ê¤Þ¤¹¤¬¡¢
             ¤È¤ê¤¿¤Æ¤Æ½ÅÍפʤâ¤Î¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤·¤«¤·°ã¤¤¤¬¤¢¤ë¤Î¤Ï³Î¤«¤Ç¤¹¡£¤Û¤É¤Ê¤¯¡¢
             GENERIC ¥«¡¼¥Í¥ë¤«¤é a.out ¤Î¥µ¥Ý¡¼¥È¤¬³°¤µ¤ì¤Þ¤¹¡£
             a.out ¤Î¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ëɬÍ×À­¤¬¤Ê¤¯¤Ê¤ì¤Ð¡¢
             ºÇ½ªÅª¤Ë a.out ¤Î¥µ¥Ý¡¼¥È¤Ï¥«¡¼¥Í¥ë¤«¤éºï½ü¤µ¤ì¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="chmod-symlinks">
           <para>¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Îµö²Ä°À­¤ò
             <command>chmod</command> ¤ÇÊѤ¨¤é¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Ïµö²Ä°À­¤ò»ý¤Á¤Þ¤»¤ó¡£
             ¤Þ¤¿ &man.chmod.1; ¤Î¥Ç¥Õ¥©¥ë¥ÈÆ°ºî¤Ï¡¢
             ¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò¤¿¤É¤Ã¤Æ¥ê¥ó¥¯Àè¤Î¥Õ¥¡¥¤¥ë¤Îµö²Ä°À­¤òÊѹ¹¤¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤»¤ó¡£
             ¤½¤Î¤¿¤á¡¢
             <filename>foo</filename> ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤¬¤¢¤ê¡¢
             ¤³¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯
             <filename>bar</filename> ¤¬¤¢¤Ã¤¿¤È¤¹¤ë¤È¡¢
             °Ê²¼¤Î¥³¥Þ¥ó¥É¤Ï¾ï¤ËÀ®¸ù¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.user; <userinput>chmod g-w bar</userinput></screen>
 
           <para>¤·¤«¤·¤³¤Î¾ì¹ç¡¢<filename>foo</filename> ¤Îµö²Ä°À­¤ÏÊѹ¹¤µ¤ì¤Þ¤»¤ó¡£</para>
 
           <para>
             ¤³¤Î¾ì¹ç¡¢<quote><option>-H</option></quote> ¤«
             <quote><option>-L</option></quote> ¤Î¤É¤Á¤é¤«¤Î¥ª¥×¥·¥ç¥ó¤ò
             <quote><option>-R</option></quote> ¤ÈƱ»þ¤Ë»È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
             &man.chmod.1; ¤È &man.symlink.7;
             ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë¤Ï¤â¤Ã¤È¾Ü¤·¤¤¾ðÊ󤬤¢¤ê¤Þ¤¹¡£
           </para>
 
             <warning>
               <para>
                 <quote><option>-R</option></quote> ¥ª¥×¥·¥ç¥ó¤Ï<emphasis>ºÆµ¢Åª¤Ë</emphasis>
                 &man.chmod.1;
                 ¤ò¼Â¹Ô¤·¤Þ¤¹¡£¥Ç¥£¥ì¥¯¥È¥ê¤ä¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò
                 <command>chmod</command> ¤¹¤ë¾ì¹ç¤Ïµ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£
                 ¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Ç»²¾È¤µ¤ì¤Æ¤¤¤ëñ°ì¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤òÊѹ¹¤·¤¿¤¤¾ì¹ç¤Ï¡¢
                 &man.chmod.1;
                 ¤ò¥ª¥×¥·¥ç¥ó¤ò¤Ä¤±¤º¤Ë¡¢
                 ¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Î̾Á°¤Î¸å¤í¤Ë¥¹¥é¥Ã¥·¥å (<quote><filename>/</filename></quote>)
                 ¤ò¤Ä¤±¤Æ»È¤¤¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢<quote><filename>foo</filename></quote>
                 ¤¬¥Ç¥£¥ì¥¯¥È¥ê <quote><filename>bar</filename></quote>
                 ¤Ø¤Î¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Ç¤¢¤ë¾ì¹ç¡¢
                 <quote><filename>foo</filename></quote>
                 (¼ÂºÝ¤Ë¤Ï <quote><filename>bar</filename></quote>)
                 ¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤òÊѹ¹¤·¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢¤³¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
               </para>
 
               <screen>&prompt.user; <userinput>chmod 555 foo/</userinput></screen>
 
               <para>
                 ¸å¤í¤Ë¥¹¥é¥Ã¥·¥å¤ò¤Ä¤±¤ë¤È¡¢
                 &man.chmod.1; ¤Ï¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯
                 <quote><filename>foo</filename></quote>
                 ¤òÄɤ¤¤«¤±¤Æ¥Ç¥£¥ì¥¯¥È¥ê
                 <quote><filename>bar</filename></quote>
                 ¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤òÊѹ¹¤·¤Þ¤¹¡£
               </para>
             </warning>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="login-8char">
           <para>¥í¥°¥¤¥ó̾¤¬<emphasis>¤¤¤Þ¤À¤Ë</emphasis>
             8 ʸ»ú¤ËÀ©¸Â¤µ¤ì¤Æ¤¤¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             <literal>UT_NAMESIZE</literal>
             ¤òÊѹ¹¤·¤Æ¥·¥¹¥Æ¥àÁ´ÂΤòºî¤êľ¤»¤Ð½½Ê¬¤Ç¡¢
             ¤½¤ì¤À¤±¤Ç¤¦¤Þ¤¯¤¤¤¯¤À¤í¤¦¤È¤¢¤Ê¤¿¤Ï¹Í¤¨¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
             »ÄÇ°¤Ê¤¬¤é¿¤¯¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ä¥æ¡¼¥Æ¥£¥ê¥Æ¥£ (¥·¥¹¥Æ¥à¥Ä¡¼¥ë¤â´Þ¤á¤Æ) ¤Ï¡¢
             ¾®¤µ¤Ê¿ôÃͤò¹½Â¤ÂΤä¥Ð¥Ã¥Õ¥¡¤Ê¤É¤Ë»È¤Ã¤Æ¤¤¤Þ¤¹ (ɬ¤º¤·¤â
             <quote>8</quote> ¤ä <quote>9</quote> ¤Ç¤Ï¤Ê¤¯¡¢
             <quote>15</quote> ¤ä <quote>20</quote> ¤Ê¤É¤ÎÊѤä¿Ãͤò»È¤¦¤â¤Î¤â¤¢¤ê¤Þ¤¹)¡£
             (¸ÇÄêĹ¤Î¥ì¥³¡¼¥É¤ò´üÂÔ¤¹¤ë¤È¤³¤í¤Ç²ÄÊÑĹ¥ì¥³¡¼¥É¤Ë¤Ê¤ë¤¿¤á¡¢
             ) Âæ̵¤·¤Ë¤Ê¤Ã¤¿¥í¥°¥Õ¥¡¥¤¥ë¤òÆÀ¤ë¤³¤È¤Ë¤Ê¤ë¤È¤¤¤¦¤³¤È¤À¤±¤Ç¤Ê¤¯¡¢
             Sun ¤Î <acronym>NIS</acronym>
             ¤Î¥¯¥é¥¤¥¢¥ó¥È¤Î¾ì¹ç¤ÏÌäÂ꤬µ¯¤­¤Þ¤¹¤·¡¢Â¾¤Î UNIX
             ¥·¥¹¥Æ¥à¤È¤Î´ØÏ¢¤Ë¤ª¤¤¤Æ¤³¤ì¤é°Ê³°¤ÎÌäÂê¤âµ¯¤­¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ¤·¤«¤·¡¢FreeBSD 3.0 °Ê¹ß¤Ç¤Ï 16 ʸ»ú¤È¤Ê¤ê¡¢
             ¿¤¯¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Î¥Ï¡¼¥É¥³¡¼¥É¤µ¤ì¤¿Ì¾Á°¤ÎŤµ¤ÎÌäÂê¤â²ò·è¤µ¤ì¤Þ¤¹¡£
             ¼ÂºÝ¤Ë¤Ï¥·¥¹¥Æ¥à¤Î¤¢¤Þ¤ê¤Ë¿¤¯¤ÎÉôʬ¤ò½¤Àµ¤¹¤ë¤¿¤á¤Ë¡¢
             3.0 ¤Ë¤Ê¤ë¤Þ¤Ç¤ÏÊѹ¹¤¬¹Ô¤ï¤ì¤Þ¤»¤ó¤Ç¤·¤¿¡£
           </para>
 
           <para>
             ¤½¤ì°ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢¤³¤ì¤é¤ÎÌäÂ꤬µ¯¤³¤Ã¤¿¾ì¹ç¤Ë¡¢
             ÌäÂê¤ò¼«Ê¬¼«¿È¤Çȯ¸«¤·¡¢²ò·è¤Ç¤­¤ë¤³¤È¤ËÀäÂÐŪ¤Ê¼«¿®¤¬¤¢¤ë¾ì¹ç¤Ï
             <filename>/usr/include/utmp.h</filename> ¤òÊÔ½¸¤·¡¢
             <literal>UT_NAMESIZE</literal> ¤ÎÊѹ¹¤Ë¤·¤¿¤¬¤Ã¤Æ¡¢
             Ť¤¥æ¡¼¥¶Ì¾¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             ¤Þ¤¿¡¢
             <literal>UT_NAMESIZE</literal> ¤ÎÊѹ¹¤È°ìÃפ¹¤ë¤è¤¦¤Ë
             <filename>/usr/include/sys/param.h</filename> ¤Î
             <literal>MAXLOGNAME</literal> ¹¹¿·¤·¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
             ºÇ¸å¤Ë¡¢¥½¡¼¥¹¤«¤é¥Ó¥ë¥É¤¹¤ë¾ì¹ç¤Ï
             <filename>/usr/include</filename>
             ¤òËè²ó¥¢¥Ã¥×¥Ç¡¼¥È¤¹¤ëɬÍפ¬¤¢¤ë¤³¤È¤ò˺¤ì¤Ê¤¤¤è¤¦¤Ë!
             <filename>/usr/src/..</filename> ¾å¤Î¥Õ¥¡¥¤¥ë¤òÊѹ¹¤·¤Æ¤ª¤¤¤ÆÃÖ¤­´¹¤¨¤Þ¤·¤ç¤¦¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dos-binaries">
           <para>FreeBSD ¾å¤Ç DOS ¤Î¥Ð¥¤¥Ê¥ê¤òÆ°¤«¤¹¤³¤È¤Ï¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Ï¤¤¡¢FreeBSD 3.0 ¤«¤é¤Ï¡¢
             Åý¹ç¤È²þÎɤ¬½Å¤Í¤é¤ì¤¿ BSDI ¤Î <application>doscmd</application>
             DOS ¥¨¥ß¥å¥ì¡¼¥·¥ç¥ó¥µ¥Ö¥·¥¹¥Æ¥à¤ò»È¤Ã¤Æ¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
             º£¤Ê¤ªÂ³¤±¤é¤ì¤Æ¤¤¤ë¤³¤ÎÅØÎϤ˶½Ì£¤ò»ý¤Ã¤Æ»²²Ã¤·¤Æ¤¤¤¿¤À¤±¤ë¤Ê¤é¡¢
             &a.emulation;
             ¤Ø¥á¡¼¥ë¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>FreeBSD 3.0 °ÊÁ°¤Î¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
             <application>pcemu</application>
             ¤È¤¤¤¦¹ªÌ¯¤Ê¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤¬ FreeBSD Ports Collection ¤Ë¤¢¤ê¡¢
             8088 ¤Î¥¨¥ß¥å¥ì¡¼¥·¥ç¥ó¤È DOS
             ¤Î¥Æ¥­¥¹¥È¥â¡¼¥É¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤òÆ°¤«¤¹¤Ë½½Ê¬¤Ê
             BIOS ¥µ¡¼¥Ó¥¹¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£¤³¤ì¤Ï X ¥¦¥£¥ó¥É¥¦¥·¥¹¥Æ¥à¤¬É¬ÍפǤ¹ (XFree86
             ¤È¤·¤ÆÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹)¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="free-account">
           <para>¤É¤³¤Ç̵ÎÁ¤Î FreeBSD ¤Î¥¢¥«¥¦¥ó¥È¤ò¼èÆÀ¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>FreeBSD ¤Ï¤¤¤º¤ì¤Î¥µ¡¼¥Ð¡¼¤Ë¤â¥¢¥¯¥»¥¹¤ò³«Êü¤·¤Æ¤¤¤Þ¤»¤ó¤¬¡¢
             Unix ¥·¥¹¥Æ¥à¤Ø¤Î¼«Í³¤Ê¥¢¥¯¥»¥¹¤òÄ󶡤·¤Æ¤¤¤ë¤È¤³¤í¤¬¤¢¤ê¤Þ¤¹¡£
             ÈñÍѤϤޤÁ¤Þ¤Á¤Ç¡¢¸ÂÄꤵ¤ì¤¿¥µ¡¼¥Ó¥¹¤¬ÍøÍѤǤ­¤Þ¤¹¡£</para>
 
           <para>M-Net ¤È¤·¤Æ¤âÃΤé¤ì¤ë <ulink
             url="http://www.arbornet.org/">Arbornet, Inc</ulink> ¤Ï
             1983 ǯ¤«¤é Unix ¥·¥¹¥Æ¥à¤Ø¤Î¥¢¥¯¥»¥¹¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£
             System III ¤¬Æ°ºî¤¹¤ë Altos ¤Ë»Ï¤Þ¤ê¡¢1991 ǯ¤Ë¤Ï
             BSD/OS ¤Ë°Ü¹Ô¤·¤Þ¤·¤¿¡£2000 ǯ 6 ·î¤Ë¤Ï¡¢ºÆ¤Ó FreeBSD ¤Ë
             °Ü¹Ô¤·¤Æ¤¤¤Þ¤¹¡£M-Net ¤Ë¤Ï SSH ¤Þ¤¿¤Ï telnet ·Ðͳ¤Ç
             ¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤¬¤Ç¤­¡¢FreeBSD ¥½¥Õ¥È¥¦¥§¥¢°ì¼°¤¬
             ÍøÍѤǤ­¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£¤¿¤À¤·¡¢¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤Ï
             ²ñ°÷¤È¡¢Èó±ÄÍøÁÈ¿¥¤È¤·¤Æ±¿±Ä¤µ¤ì¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤Ë´óÉÕ¤ò¤¹¤ë
             ¸å±ç¼Ô¤ËÀ©¸Â¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤Þ¤¿¡¢M-Net ¤Ï·Ç¼¨ÈÄ¥·¥¹¥Æ¥à¤È
             ÁÐÊý¸þ¥Á¥ã¥Ã¥È¤âÄ󶡤·¤Æ¤¤¤Þ¤¹¡£</para>
 
           <para><ulink url="http://www.grex.org/">Grex</ulink> ¤Ï¡¢
             ·Ç¼¨ÈÄ¥·¥¹¥Æ¥à¤ÈÁÐÊý¸þ¥Á¥ã¥Ã¥È¥½¥Õ¥È¥¦¥§¥¢¤¬Æ±¤¸¤Ç¤¢¤ë¤³¤È¤â´Þ¤á¡¢
             M-Net ¤È¤è¤¯»÷¤¿¥µ¥¤¥È¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£¤·¤«¤·¡¢
             ¥Þ¥·¥ó¤Ï Sun 4M ¤Ç¡¢SunOS ¤¬Æ°ºî¤·¤Æ¤¤¤Þ¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sup-define">
           <para><quote><acronym>sup</acronym></quote> ¤È¤Ï²¿¤Ç¡¢
             ¤É¤Î¤è¤¦¤Ë¤·¤Æ»È¤¦¤â¤Î¤Ê¤Î¤Ç¤·¤ç¤¦¤«?</para>
         </question>
 
         <answer>
           <para>
             <ulink url="http://www.FreeBSD.org/cgi/ports.cgi?^sup">SUP</ulink>
             ¤È¤Ï¡¢¥½¥Õ¥È¥¦¥§¥¢¥¢¥Ã¥×¥Ç¡¼¥È¥×¥í¥È¥³¥ë (Software Update Protocol) ¤Ç
             ¥«¡¼¥Í¥®¡¼¥á¥í¥óÂç³Ø (CMU) ¤Ç³«È¯¥Ä¥ê¡¼¤ÎƱ´ü¤Î¤¿¤á¤Ë³«È¯¤µ¤ì¤Þ¤·¤¿¡£
             »ä¤¿¤Á¤ÎÃæ¿´³«È¯¥Ä¥ê¡¼¤ò¥ê¥â¡¼¥È¥µ¥¤¥È¤ÇƱ´ü¤µ¤»¤ë¤¿¤á¤Ë»È¤Ã¤Æ¤¤¤Þ¤·¤¿¡£
           </para>
 
           <para>
             SUP ¤Ï¥Ð¥ó¥ÉÉý¤òϲÈñ¤·¤Þ¤¹¤Î¤Ç¡¢º£¤Ï»È¤Ã¤Æ¤¤¤Þ¤»¤ó¡£
             ¥½¡¼¥¹¥³¡¼¥É¤Î¥¢¥Ã¥×¥Ç¡¼¥È¤Î¸½ºß¤Î¤ª¤¹¤¹¤á¤ÎÊýË¡¤Ï
             <ulink url="../handbook/synching.html#CVSUP">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡ÖCVSup¡×</ulink>¤Ë¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="very-very-cool">
           <para>FreeBSD ¤ò¥¯¡¼¥ë¤Ë»È¤¦¤Ë¤Ï?</para>
           <para>
             FreeBSD ¤òÆ°¤«¤¹»þ¤Ë²¹ÅÙ¬Äê¤ò¹Ô¤Ê¤Ã¤¿¿Í¤Ï¤¤¤Þ¤¹¤«? Linux
             ¤Ï dos ¤è¤ê¤â²¹ÅÙ¤¬²¼¤¬¤ë¤È¤¤¤¦¤³¤È¤ÏÃΤäƤ¤¤Þ¤¹¤¬¡¢FreeBSD
             ¤Ë¤Ä¤¤¤Æ¤Ï¤³¤Î¤è¤¦¤Ê¤³¤È¤Ë¿¨¤ì¤¿¤â¤Î¤ò¸«¤¿¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¼ÂºÝÇ®¤¯¤Ê¤Ã¤Æ¤¤¤ë¤è¤¦¤Ë¸«¤¨¤Þ¤¹¡£
           </para>
         </question>
 
         <answer>
           <para>
             ¤¤¤¤¤¨¡£
             »ä¤¿¤Á¤Ï 250 ¥Þ¥¤¥¯¥í¥°¥é¥à¤Î LSD-25
             ¤ò¤¢¤é¤«¤¸¤áÍ¿¤¨¤Æ¤ª¤¤¤¿¥Ü¥é¥ó¥Æ¥£¥¢¤ËÂФ¹¤ë¡¢
             Ìܱ£¤·Ì£³Ð¥Æ¥¹¥È¤òÂçÎ̤˹ԤʤäƤ¤¤Þ¤¹¡£
             35% ¤Î¥Ü¥é¥ó¥Æ¥£¥¢¤Ï FreeBSD
             ¤Ï¥ª¥ì¥ó¥¸¤Î¤è¤¦¤ÊÌ£¤¬¤¹¤ë¤È¸À¤Ã¤Æ¤¤¤ë¤Î¤ËÂФ·¡¢
             Linux ¤Ï»ç±ì¤Î¤è¤¦¤ÊÌ£¤ï¤¤¤¬¤¢¤ë¤È¸À¤Ã¤Æ¤¤¤ë¿Í¤â¤¤¤Þ¤¹¡£
             ξÊý¤Î¥°¥ë¡¼¥×¤È¤â²¹ÅÙ¤ÎÉÔ°ìÃפˤĤ¤¤Æ¤Ï²¿¤â¿¨¤ì¤Æ¤¤¤Þ¤»¤ó¡£
             ¤³¤ÎÄ´ºº¤Ç¡¢Èó¾ï¤Ë¿¤¯¤Î¥Ü¥é¥ó¥Æ¥£¥¢¤¬¥Æ¥¹¥È¤ò¹Ô¤Ê¤Ã¤¿Éô²°¤«¤éÉԻ׵Ĥ½¤¦¤Ë½Ð¤Æ¤­¤Æ¡¢
             ¤³¤Î¤è¤¦¤Ê¤ª¤«¤·¤Ê·ë²Ì¤ò¼¨¤·¤¿¤³¤È¤Ë»ä¤¿¤Á¤ÏÅöÏǤµ¤»¤é¤ì¤Þ¤·¤¿¡£
             »ä¤¿¤Á¤Ï¡¢¤Û¤È¤ó¤É¤Î¥Ü¥é¥ó¥Æ¥£¥¢¤Ï Apple
             ¤Ë¤¤¤ÆÈà¤é¤ÎºÇ¿·¤Î¡Ö°ú¤Ã¤«¤¤¤ÆÆ÷¤¤¤ò¤«¤°¡×GUI
             ¤ò»È¤Ã¤Æ¤¤¤ë¤Î¤Ç¤Ï¤Ê¤¤¤«¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£
             »ä¤¿¤Á¤Ï´ñ̯¤Ê¸Å¤¤»Å»ö¤ò¤·¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦!
           </para>
 
           <para>
             ¿¿ÌÌÌܤ˸À¤¦¤È¡¢FreeBSD ¤ä Linux ¤Ï¶¦¤Ë
             <quote><acronym>HLT</acronym></quote> (Ää»ß)
             Ì¿Îá¤ò¥·¥¹¥Æ¥à¤Î¥¢¥¤¥É¥ë (idle) »þ¤Ë»È¤¤¡¢
             ¥¨¥Í¥ë¥®¡¼¤Î¾ÃÈñ¤ò²¡¤¨¤Æ¤¤¤Þ¤¹¤Î¤ÇÇ®¤ÎȯÀ¸¤â¾¯¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£
             ¤Þ¤¿¡¢<acronym>APM (advanced power management)</acronym>
             ¤òÀßÄꤷ¤Æ¤¢¤ë¤Ê¤é FreeBSD ¤Ï <acronym>CPU</acronym>
             ¤ò¥í¡¼¥Ñ¥ï¡¼¥â¡¼¥É¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="letmeoutofhere">
           <para>狼¤¬»ä¤Î¥á¥â¥ê¥«¡¼¥É¤ò¤Ò¤Ã¤«¤¤¤Æ¤¤¤ë¤Î¤Ç¤¹¤«??</para>
           <para>
             FreeBSD¤Ç¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë¤ò¤·¤Æ¤¤¤ë»þ¡¢
             ¥á¥â¥ê¤«¤é°ú¤Ã¤«¤¤¤Æ¤¤¤ë¤è¤¦¤Ê´ñ̯¤Ê²»¤¬Ê¹¤³¤¨¤ë¤è¤¦¤Ê¤³¤È¤Ï¤¢¤ë¤Î¤Ç¤·¤ç¤¦¤«?
             ¥³¥ó¥Ñ¥¤¥ë¤ò¤·¤Æ¤¤¤ë»þ (¤¢¤ë¤¤¤Ïµ¯Æ°»þ¤Ë¥Õ¥í¥Ã¥Ô¥É¥é¥¤¥Ö¤òǧ¼±¤·¤¿¸å¤Îû¤¤´Ö¤Ê¤É)¡¢
             ´ñ̯¤Ê°ú¤Ã¤«¤¯¤è¤¦¤Ê²»¤¬¥á¥â¥ê¥«¡¼¥É¤Î¤¢¤¿¤ê¤«¤éʹ¤³¤¨¤Æ¤­¤Þ¤¹¡£
           </para>
         </question>
 
         <answer>
           <para>
             ¤½¤ÎÄ̤ê! BSD ¤Îʸ½ñ¤Ë¤ÏÎɤ¯¡¢¥Ç¡¼¥â¥ó (daemon) ¤È¤¤¤¦¸ÀÍÕ¤¬½Ð¤Æ¤­¤Þ¤¹¡£
             ¤Û¤È¤ó¤É¤Î¿Í¤ÏÃΤé¤Ê¤¤¤Î¤Ç¤¹¤¬¡¢
             ¥Ç¡¼¥â¥ó¤È¤Ï¡¢¤¢¤Ê¤¿¤Î¥³¥ó¥Ô¥å¡¼¥¿¤ò°Í¤êÂå¤È¤¹¤ë¡¢
             ½ã¿è¤ÇÈóʪ¼ÁŪ¤Ê¸ºß¤Î¤³¤È¤Ç¤¹¡£
             ¥á¥â¥ê¤«¤éʹ¤³¤¨¤ë¤Ò¤Ã¤«¤¯¤è¤¦¤Ê²»¤Ï¡¢
             ¤µ¤Þ¤¶¤Þ¤¢¤ë¥·¥¹¥Æ¥à´ÉÍý¥¿¥¹¥¯¤Î°·¤¤¤ò¤¤¤«¤ËºÇÁ±¤Ê¤â¤Î¤Ë¤¹¤ë¤«¡¢
             ¤È¤¤¤Ã¤¿¤³¤È¤ò·è¤á¤ë¤È¤­¤Ë¥Ç¡¼¥â¥ó¤¿¤Á¤¬¸ò¤ï¤¹¡¢
             ¤«¤ó¹â¤¤¤µ¤µ¤ä¤­À¼¤Ê¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ¤³¤Î»¨²»¤¬Ê¹¤³¤¨¤¿¤È¤­¡¢DOS ¤«¤é
             <quote><command>fdisk /mbr</command></quote>
             ¤È¤¤¤¦¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ì¤Ð¡¢
             ¤¦¤Þ¤¯¥Ç¡¼¥â¥ó¤òÄɤ¤½Ð¤¹¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£
             ¤Ç¤â¡¢¥Ç¡¼¥â¥ó¤Ï¤½¤ì¤Ë»õ¸þ¤«¤Ã¤Æ <command>fdisk</command>
             ¤Î¼Â¹Ô¤ò¤ä¤á¤µ¤»¤è¤¦¤È¤¹¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£
             ¤â¤·¡¢¤½¤ì¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¤È¤­¤Ë¥¹¥Ô¡¼¥«¤Ê¤é¥Ó¥ë ¥²¥¤¥Ä (Bill
             Gates) ¤Î°­Ëâ¤Î¤µ¤µ¤ä¤­¤¬Ê¹¤³¤¨¤Æ¤­¤¿¤é¡¢
             ¤¹¤°¤ËΩ¤Á¾å¤¬¤Ã¤Æƨ¤²¤Æ¤¯¤À¤µ¤¤¡£·è¤·¤Æ¿¶¤êÊ֤äƤϤ¤¤±¤Þ¤»¤ó!
             BSD ¤Î¥Ç¡¼¥â¥ó¤¿¤Á¤¬²¡¤¨¹þ¤ó¤Ç¤¤¤¿ÁлҤΥǡ¼¥â¥ó¡¢DOS ¤È Windows ¤¬²òÊü¤µ¤ì¡¢
             ¤¢¤Ê¤¿¤Îº²¤ò±Ê±ó¤ÎÇËÌǤØƳ¤³¤¦¤È¥Þ¥·¥ó¤òºÆ¤Ó»ÙÇÛ¤·¤Æ¤·¤Þ¤¦¤³¤È¤Ç¤·¤ç¤¦¡£
             ¤½¤ì¤òÃΤ俺£¤ä¡¢Áª¤Ù¤È¸À¤ï¤ì¤¿¤é¡¢
             ¤à¤·¤í¤Ò¤Ã¤«¤­²»¤Ë´·¤ì¤ëÊý¤òÁª¤Ö¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤«?
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="define-MFC">
           <para>&quot;MFC&quot; ¤È¤Ï¤É¤¦¤¤¤¦°ÕÌ£¤Ç¤¹¤«</para>
         </question>
 
         <answer>
           <para>
             <acronym>MFC</acronym> ¤È¤Ï¡¢
             ¡ÖCURRENT ¤È¤Î¹çή (Merged From -CURRENT)¡×¤ÎƬʸ»ú¤ò¤È¤Ã¤¿¤â¤Î¤Ç¤¹¡£
             <acronym>CVS</acronym> ¥í¥°¤Ç
             -CURRENT ¤«¤é
             -STABLE ¥Ö¥é¥ó¥Á¤Ø¤Î¹çή¤ò¼¨¤·¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="define-BSD">
           <para>&quot;BSD&quot; ¤È¤Ï¤É¤¦¤¤¤¦°ÕÌ£¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤³¤Î¸ÀÍդϡ¢Ãç´Ö¤¦¤Á¤À¤±¤Ëʬ¤«¤ë±£¸ì¤Ç²¿¤È¤«¤È¤¤¤¦°ÕÌ£¤Ç¤¹¡£
             ʸ»ú¤É¤ª¤ê¤ËÌõ¤¹¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¤¬¡¢
             BSD ¤ÎÌõ¤Ï¡ÖF1 ¤Î¥ì¡¼¥·¥ó¥°¥Á¡¼¥à¡×¤«¡Ö¥Ú¥ó¥®¥ó¤Ï¤ª¤¤¤·¤¤¥¹¥Ê¥Ã¥¯¡×¡¢
             ¤¢¤ë¤¤¤Ï¡Ö²¶¤¿¤Á¤ã
             Linux ¤è¤êÞ¯Íî¤ÏÍø¤¤¤Æ¤ë¤¼¡×¤È¤«¤½¤Î¤Ø¤ó¤À¤È¸À¤Ã¤Æ¤ª¤±¤Ð¤ª¤Ã¤±¡¼¤Ç¤·¤ç¤¦¡£
             <literal>:-)</literal>
           </para>
 
           <para>
             ¾éÃ̤Ϥµ¤Æ¤ª¤­¡¢BSD ¤È¤Ï¡¢Berkeley
             CSRG (¥³¥ó¥Ô¥å¡¼¥¿¥·¥¹¥Æ¥àɾµÄ²ñ) ¤¬Èà¤é¤Î
             UNIX ¤ÎÇÛÉÛ·ÁÂÖ¤Î̾Á°¤È¤·¤ÆÅö»þÁª¤ó¤À
             &quot;Berkeley Software Distribution&quot;
             ¤Îά¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="define-repocopy">
           <para>¥ê¥Ý¥¸¥È¥ê¡¦¥³¥Ô¡¼ (repo-copy)
             ¤È¤Ï°ìÂβ¿¤Î¤³¤È¤Ç¤·¤ç¤¦?</para>
         </question>
 
         <answer>
           <para>repo-copy (<quote>repository copy</quote> ¤Îά) ¤È¤Ï¡¢
             CVS ¥ê¥Ý¥¸¥È¥ê¤ÎÃæ¤ÇľÀÜ¥Õ¥¡¥¤¥ë¤ò¥³¥Ô¡¼¤¹¤ë¤³¤È¤ò¼¨¤¹ÍѸì¤Ç¤¹¡£</para>
 
           <para>repo-copy ¤ò¹Ô¤Ê¤ï¤Ê¤¤¾ì¹ç¤ò¹Í¤¨¤Þ¤¹¡£
             ¥ê¥Ý¥¸¥È¥ê¤ÎÃæ¤Î°Û¤Ê¤ë¾ì½ê¤Ë¥Õ¥¡¥¤¥ë¤ò¥³¥Ô¡¼¤·¤¿¤ê¡¢
             °ÜÆ°¤·¤¿¤ê¤¹¤ëɬÍ×À­¤¬À¸¤¸¤ë¤È¡¢¥³¥ß¥Ã¥¿¡¼¤Ï
             ¥Õ¥¡¥¤¥ë¤ò¿·¤·¤¤¾ì½ê¤ËÃÖ¤¯¤¿¤á¤Ë <command>cvs add</command> ¤ò¡¢
             ¤½¤·¤Æ¸Å¤¤¥Õ¥¡¥¤¥ë¤¬ºï½ü¤µ¤ì¤ë¾ì¹ç¤Ï¡¢¸Å¤¤¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ
             <command>cvs rm</command> ¤ò¼Â¹Ô¤¹¤ë¤Ç¤·¤ç¤¦¡£</para>
 
           <para>¤³¤ÎÊýË¡¤Î·çÅÀ¤Ï¡¢¥Õ¥¡¥¤¥ë¤ÎÊѹ¹ÍúÎò
             (¤¿¤È¤¨¤Ð CVS ¥í¥°¤Î¥¨¥ó¥È¥ê) ¤¬¿·¤·¤¤¾ì½ê¤Ë¥³¥Ô¡¼¤µ¤ì¤Ê¤¤¤³¤È¤Ç¤¹¡£
             FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ç¤Ï¤³¤ÎÊѹ¹ÍúÎò¤ò¤È¤Æ¤âÍ­ÍѤʤâ¤Î¤À¤È¹Í¤¨¤Æ¤¤¤ë¤¿¤á¡¢
             Á°½Ò¤ÎÊýË¡¤ÎÂå¤ï¤ê¤Ë¥ê¥Ý¥¸¥È¥ê¥³¥Ô¡¼¤¬Îɤ¯ÍѤ¤¤é¤ì¤Þ¤¹¡£
             ¤³¤ÎÁàºî¤Ï <command>cvs</command> ¥×¥í¥°¥é¥à¤òÍøÍѤ¹¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢
             ¥ê¥Ý¥¸¥È¥ê¤Î´ÉÍýôÅö¼Ô¤¬¥ê¥Ý¥¸¥È¥ê¤ÎÃæ¤Ç¥Õ¥¡¥¤¥ë¤òľÀÜ¥³¥Ô¡¼¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bikeshed-painting">
           <para>¤Ê¤ó¤Ç¥Ð¥¤¥¯¾®²° (bikeshed) ¤Î¿§¤Ë¤Þ¤Çµ¤¤ò»È¤ï¤Ê¤±¤ì¤Ð¤¤¤±¤Ê¤¤¤ó¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>°ì¸À¤Ç¸À¤Ã¤Æ¤·¤Þ¤¨¤Ð¡¢¤½¤¦¤¹¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ¤â¤¦¾¯¤·¾Ü¤·¤¯ÀâÌÀ¤·¤Þ¤·¤ç¤¦¡£
             ¤¿¤È¤¨¤Ð¡¢¤¢¤Ê¤¿¤¬¥Ð¥¤¥¯¾®²°¤ò·ú¤Æ¤ëµ»½Ñ¤ò»ý¤Ã¤Æ¤¤¤¿¤È¤·¤Þ¤¹¡£
             ¤·¤«¤·¤½¤ì¤Ï¡¢ÅÉ¤í¤¦¤È¤·¤Æ¤¤¤ë¿§¤¬µ¤¤ËÆþ¤é¤Ê¤¤¤«¤é¤È¸À¤Ã¤Æ¡¢
             ¾¿Í¤¬¥Ð¥¤¥¯¾®²°¤ò·ú¤Æ¤è¤¦¤È¤·¤Æ¤¤¤ë¤Î¤ò»ß¤á¤ÆÎɤ¤Íýͳ¤Ë¤Ï¤Ê¤ê¤Þ¤»¤ó¤è¤Í¡£
             ¤³¤ì¤Ï¡¢¼«Ê¬¤Î¹ÔÆ°¤Ë¤Ä¤¤¤Æ½½Ê¬¤ÊÍý²ò¤ò»ý¤Ã¤Æ¤¤¤ë¤Ê¤é¡¢
             ¤¢¤Ê¤¿¤ÏºÙ¤«¤Êµ¡Ç½¤¹¤Ù¤Æ¤Ë¤ï¤¿¤Ã¤ÆµÄÏÀ¤¹¤ëɬÍפϤʤ¤¤³¤È¤ò¼¨¤¹ÈæÓȤǤ¹¡£
             ¤¢¤ëÊѹ¹¤Ë¤è¤Ã¤Æ»º¤ß½Ð¤µ¤ì¤ë¥Î¥¤¥º¤ÎÁíÎ̤ϡ¢
             ¤½¤ÎÊѹ¹¤ÎÊ£»¨¤µ¤ËÈ¿ÈæÎ㤹¤ë¤Î¤À¤È¸À¤Ã¤Æ¤¤¤ë¿Íã¤â¤¤¤Þ¤¹¡£</para>
 
           <para>¤µ¤é¤Ë¾Ü¤·¤¯¡¢´°Á´¤Ê²óÅú¤ò¾Ò²ð¤·¤Þ¤·¤ç¤¦¡£
             Poul-Henning Kamp ¤Ï¡¢
             ¡Ö&man.sleep.1; ¤Ïʬ¿ô¤ÎÉÿô¤ò°ú¿ô¤È¤·¤Æ¼è¤ë¤Ù¤­¤«¡×¤È¤¤¤¦
             Èó¾ï¤ËŤ¤µÄÏÀ¤Î¸å¤Ç¡¢
             <quote><ulink url="http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=506636+517178+/usr/local/www/db/text/1999/freebsd-hackers/19991003.freebsd-hackers">A bike shed (any colour will do) on greener
             grass...</ulink></quote>
             ¤È¤¤¤¦¥¿¥¤¥È¥ë¤ÎĹʸ¤òÅê¹Æ¤·¤Þ¤·¤¿¡£
             ´Ø·¸¤Î¤¢¤ëÉôʬ¤À¤±¤ò°Ê²¼¤Ë·ÇºÜ¤·¤Þ¤¹¡£</para>
 
           <blockquote>
             <attribution>1999 ǯ 10 ·î 2 Æü  freebsd-hackers ¤Ë¤Æ
               Poul-Henning Kamp</attribution>
 
             <para>
               <quote>¤³¤Î¥Ð¥¤¥¯¾®²°¡¢¤É¤¦¤À¤í¤¦?</quote>
               狼¤¬¤¿¤º¤Í¤Þ¤·¤¿¡£
             </para>
 
             <para>
               Ť¤¡Ä¤È¤¤¤¦¤«¡¢¤à¤·¤í¸Å¤¤Ïäˤʤê¤Þ¤¹¤¬¡¢
               Ãæ¿È¤Ï¤ï¤ê¤È´Êñ¤ÊÏäǤ¹¡£¥Ñ¡¼¥­¥ó¥½¥ó
               (C. Northcote Parkinson) ¤Ï 1960 ǯÂå½éƬ¤Ë
               <quote>¥Ñ¡¼¥­¥ó¥½¥ó¤Îˡ§</quote> ¤È¸Æ¤Ð¤ì¤ëËܤò½ñ¤­¤Þ¤·¤¿¡£
               ¤³¤ÎÃæ¤Ë¤Ï¤µ¤Þ¤¶¤Þ¤Ê·Ð±Ä¤ÎÎϳؤ˴ؤ¹¤ëƶ»¡¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
             </para>
 
             <para>[ ¤³¤ÎËܤ˴ؤ¹¤ë²òÀ⤬¤¢¤Ã¤¿¤¬¾Êά ]</para>
 
             <para>¥Ð¥¤¥¯¾®²°¤Ë´ØÏ¢¤¹¤ëÎã¤È¤·¤Æ¡¢
               ¤â¤¦°ì¤Ä¤Î½ÅÍפʹ½À®Í×ÁǤȤʤäƤ¤¤ë¤Î¤Ï¸¶»ÒÎÏȯÅŽê¤Ç¤¹¡£
               ¤³¤ÎËܤÎǯÂ夬¤ï¤«¤ê¤Þ¤¹¤Í¡£</para>
 
             <para>¥Ñ¡¼¥­¥ó¥½¥ó¤Ï¡¢¤¢¤Ê¤¿¤¬½ÅÌò²ñ¤Ë½ÐÀʤ·¤Æ
               ¿ôÉ´Ëü¤«¤é¿ô10²¯¥É¥ëµ¬ÌϤ趻ÒÎÏȯÅŽê¤Î·úÀߤξµÇ§¤òÆÀ¤ë
               ¤³¤È¤Ï¤Ç¤­¤ë¤Ç¤·¤ç¤¦¤¬¡¢¤¢¤Ê¤¿¤¬·ú¤Æ¤¿¤¤¤Î¤¬¥Ð¥¤¥¯¾®²°¤Ê¤é¤Ð¡¢
               ½ª¤ï¤ê¤Ê¤­µÄÏÀ¤Ë´¬¤­¹þ¤Þ¤ì¤ë¤À¤í¤¦¤È¸À¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
 
             <para>¥Ñ¡¼¥­¥ó¥½¥ó¤Ï¤³¤Î¤è¤¦¤ËÀâÌÀ¤·¤Æ¤¤¤Þ¤¹¡£
               ¤³¤ì¤Ï¸¶È¯¤¬Í¾¤ê¤ËµðÂç¤Ç¹â²Á¤ÇÊ£»¨¤Ê¤Î¤Çï¤â¤³¤ì¤ò°ì¼ê¤Ë°®¤ë¤³¤È¤¬¤Ç¤­¤º¡¢
               ¤½¤ì¤ò»î¤ß¤ë¤¯¤é¤¤¤Ê¤é¤à¤·¤í¡¢¼ê¤¬½Ð¤»¤Ê¤¯¤Ê¤ëÁ°¤Ë
               ¾¤Î狼¤¬¤¹¤Ù¤Æ¤ò¾ÜºÙ¤Ë¥Á¥§¥Ã¥¯¤¹¤ë¤³¤È¤ò
               °ú¤­¼õ¤±¤ë¤³¤È¤ËÍê¤ë¤Î¤Ç¤¹¡£
               ¥ê¥Á¥ã¡¼¥É¡¦¥Õ¥¡¥¤¥ó¥Þ¥ó (Richard P. Feynmann) ¤Ï¡¢
               ¥í¥¹¥¢¥é¥â¥¹¤Ç¤³¤Î¼ê¤Î½ÅÍפʷи³¤ò²¿Å٤⸫¤Æ¤­¤¿¤ÈËܤ˽ñ¤¤¤Æ¤¤¤Þ¤¹¡£
             </para>
 
             <para>°ìÊý¤Ç¥Ð¥¤¥¯¾®²°¤Î¾ì¹ç¤Ï¡¢Ã¯¤Ç¤â½µËö¤Ë¤³¤ì¤òºî¤ê¾å¤²¤ë¤³¤È¤¬¤Ç¤­¡¢
               ¤·¤«¤â TV ¤Î»î¹ç¤ò¸«¤ë»þ´Ö¤¬¤¢¤Þ¤ë¤Û¤É¤Ç¤¹¡£
               ¤Ê¤Î¤Ç¡¢¤É¤ó¤Ê¤Ë½àÈ÷¤¬À°¤¨¤Æ¤¢¤Ã¤Æ¡¢¤É¤ó¤Ê¤Ë·×²è¤¬½çÅö¤Ç¤¢¤Ã¤¿¤È¤·¤Æ¤â¡¢
               ¤ï¤¿¤·¤Ï»Å»ö¤ò¤ä¤Ã¤Æ¤¤¤ë¤è¡¢
               ¤ï¤¿¤·¤ÏÃí°Õ¤òʧ¤Ã¤Æ¤¤¤ë¤è¡¢¤½¤·¤Æ
               ¤ï¤¿¤·¤Ï<emphasis>¤³¤³</emphasis>¤Ë¤¤¤ë¤è¡¢
               ¤È¤¤¤¦¤³¤È¤ò¼¨¤½¤¦¤È¤¹¤ë¿Í¤¬É¬¤º¸½¤ì¤Þ¤¹¡£</para>
 
             <para>¥Ç¥ó¥Þ¡¼¥¯¤Ç¤Ï¤³¤ì¤ò¡Ö»ØÌæ¤ò¤Ä¤±¤ë¡×¤È¸Æ¤ó¤Ç¤¤¤Þ¤¹¡£
               ¤³¤ì¤Ï¸Ä¿ÍŪ¤Ê¥×¥é¥¤¥É¤ä̾À¼¤òµá¤á¡¢
               ¤¢¤ë¾ì½ê¤ò»Ø¤·¼¨¤·¤Æ¡Ö¤³¤³! ¤³¤³¤Ï<emphasis>²¶</emphasis>¤¬
               ¤ä¤Ã¤¿¤ó¤À¤¼¡Á¡×¤È¤¤¤¦¤è¤¦¤Ê¤â¤Î¤Ç¤¹¡£
               ¤³¤ì¤ÏÀ¯¼£²È¤Ë¸«¤é¤ì¤ë¶¯¤¤ÆÃħ¤Ç¤¹¤¬¡¢
               ¤½¤Î¾¤Î¤Û¤È¤ó¤É¤Î¿Í¤â¤³¤¦¤¤¤¦É÷¤Ë¿¶Éñ¤¦²ÄǽÀ­¤Ï¤¢¤ë¤Î¤Ç¤¹¡£
               À¸´¥¤­¤Î¥»¥á¥ó¥È¤Ë¤Ä¤±¤é¤ì¤¿Â­ÀפΤ³¤È¤ò¹Í¤¨¤ì¤Ð¤ªÊ¬¤«¤ê¤Ç¤·¤ç¤¦¡£</para>
           </blockquote>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="changing-lightbulbs">
           <para>¤Ò¤È¤Ä¤ÎÅŵå¤ò¼è¤êÂؤ¨¤ë¤Î¤Ë¡¢²¿¿Í¤Î FreeBSD ¥Ï¥Ã¥«¡¼¤¬É¬Í×?</para>
         </question>
 
         <answer>
           <para>
             1,172¿Í¤Ç¤¹¡£
           </para>
 
           <itemizedlist>
             <listitem>
               <para>Åŵ夬¾Ã¤¨¤Æ¤¤¤ë¤È -CURRENT ¤Çʸ¶ç¤ò¸À¤¦¤Î¤Ë 23 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>ÀßÄê¾å¤ÎÌäÂê¤Ç -questions ¤ÇÏäò¤¹¤Ù¤­¤³¤È¤Ë¤Ä¤¤¤ÆÁû¤°¤Î¤Ë 4 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¤½¤ì¤ò send-pr (ÌõÃí: ¾ã³²Êó¹ð) ¤¹¤ë¤Î¤Ë 3
                 ¿Í (¤½¤Î¤¦¤Á¤Î¤Ò¤È¤Ä¤Ï´Ö°ã¤Ã¤Æ doc ¥«¥Æ¥´¥ê¤ËÁ÷¤ê¤Ä¤±¤é¤ì¤¿¤¦¤¨¤Ë¡¢
                 ÆâÍƤ¬¡Ö°Å¤¯¤Ê¤Ã¤¿¡×¤È¤¤¤¦¤À¤±¤Î¤â¤Î)¡£</para>
             </listitem>
             <listitem>
               <para>buildworld ¤ò¼ºÇÔ¤µ¤»¡¢5 ʬ¸å¤Ë¤Ï¸µ¤ËÌᤵ¤ì¤ë¤è¤¦¤ÊÅŵå¤ò
                 ¥Æ¥¹¥È¤â¤»¤º¤Ë¥³¥ß¥Ã¥È¤¹¤ë¤Î¤Ë 1 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>send-pr ¤·¤¿¿Í¤Ë¡¢¥Ñ¥Ã¥Á¤¬´Þ¤Þ¤ì¤Æ¤¤¤Ê¤¤¤È¡Ö¤¤¤Á¤ã¤â¤ó¡×¤òÉÕ¤±¤ë¤Î¤Ë
                 8 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>buildworld ¤¬¼ºÇÔ¤¹¤ë¤Èʸ¶ç¤ò¸À¤¦¤Î¤Ë 5 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¼«Ê¬¤Î¤È¤³¤í¤Ç¤Ï¤Á¤ã¤ó¤ÈÆ°¤¯¡¢
                 cvsup ¤·¤¿¥¿¥¤¥ß¥ó¥°¤¬°­¤«¤Ã¤¿¤ó¤À¤í¤¦¤ÈÅú¤¨¤ë¤Î¤Ë 31 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¿·¤·¤¤Åŵå¤Î¤¿¤á¤Î¥Ñ¥Ã¥Á¤ò -hackers ¤ËÅꤲ¤ë¤Î¤Ë 1 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¼«Ê¬¤Ï 3 ǯ¤âÁ°¤Ë¥Ñ¥Ã¥Á¤òºî¤Ã¤¿¤¬¡¢¤½¤ì¤ò -CURRENT
                 ¤ËÅꤲ¤¿¤È¤­¤Ë¤Ï̵»ë¤µ¤ì¤¿¤À¤±¤À¤Ã¤¿¡¢
                 ¼«Ê¬¤Ï send-pr ¤Î¥·¥¹¥Æ¥à¤Ë¤Ï·ù¤Ê·Ð¸³¤¬¤¢¤ë¤È (¤ª¤Þ¤±¤Ë¡¢
                 Äó°Æ¤µ¤ì¤¿¿·¤·¤¤Åŵå¤Ë¤Ï½ÀÆðÀ­¤¬Ìµ¤¤¤È¤Þ¤Ç) ʸ¶ç¤ò¸À¤¦¤Î¤Ë 1 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>Åŵ夬´ðËÜ¥·¥¹¥Æ¥à¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Ê¤¤¡¢
                 committer ¤Ï¥³¥ß¥å¥Ë¥Æ¥£¤Î°Õ¸«¤òʹ¤¯¤³¤È̵¤·¤Ë¤³¤ó¤Ê¤³¤È¤ò¤¹¤ë¸¢Íø¤Ï̵¤¤¤È¶«¤Ó¡¢
                 ¡Ö¤³¤ó¤Ê¤È¤­¤Ë -core ¤Ï²¿¤ò¤ä¤Ã¤Æ¤ë¤ó¤À!?¡×¤È¤ï¤á¤­¤Á¤é¤¹¤Î¤Ë 37 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¼«Å¾¼ÖÃÖ¤­¾ì¤Î¿§¤Ëʸ¶ç¤ò¸À¤¦¤Î¤Ë 200 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¥Ñ¥Ã¥Á¤¬ &man.style.9; °ãÈ¿¤À¤È»ØŦ¤¹¤ë¤Î¤Ë 3 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>Äó°Æ¤µ¤ì¤¿¿·¤·¤¤Åŵå¤Ï GPL ¤Î²¼¤Ë¤¢¤ë¤Èʸ¶ç¤ò¸À¤¦¤Î¤Ë 70 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>GPL ¤È BSD ¥é¥¤¥»¥ó¥¹¤È MIT ¥é¥¤¥»¥ó¥¹¤È NPL ¤È¡¢
                 Ë¿ FSF ÁÏΩ¼Ô¤é¤Î¸Ä¿ÍŪ¤Ê·ò¹¯Ë¡¤ÎÍ¥°ÌÀ­¤Ë¤Ä¤¤¤Æ¤ÎÏÀÁè¤òÀï¤ï¤¹¤Î¤Ë 586 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¥¹¥ì¥Ã¥É¤Î¤¢¤Á¤³¤Á¤Î»Þ¤ò -chat ¤ä -advocacy ¤Ë°ÜÆ°¤¹¤ë¤Î¤Ë 7 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>Äó°Æ¤µ¤ì¤¿Åŵå¤ò¡¢¸Å¤¤¤Î¤è¤ê¤º¤Ã¤ÈÇö°Å¤¤¤Î¤Ë¥³¥ß¥Ã¥È¤·¤Æ¤·¤Þ¤¦¤Î¤Ë 1 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>FreeBSD ¤ËÇö°Å¤¤Åŵå¤òÉÕ¤±¤ë¤¯¤é¤¤¤Ê¤é¿¿¤Ã°Å¤Î¤Û¤¦¤¬¤Þ¤·¤À¤È¤¤¤¦¡¢
                 ¥³¥ß¥Ã¥È¥á¥Ã¥»¡¼¥¸¤Ø¤ÎÀ¨¤Þ¤¸¤¤ÈóÆñ¤ÎÍò¤Ë¤è¤Ã¤Æ¡¢
                 ¤½¤ì¤ò¸µ¤ËÌ᤹¤Î¤Ë 2 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>Çö°Å¤¤Åŵ夬Ģ¾Ã¤·¤Ë¤µ¤ì¤¿¤³¤È¤ËÂФ·¤Æ¤É¤Ê¤êÀ¼¤Ç¸ýÏÀ¤·¡¢
                 -core ¤ÎÀ¼ÌÀ¤òÍ׵᤹¤ë¤Î¤Ë 46 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¤â¤· FreeBSD ¤ò¤¿¤Þ¤´¤Ã¤Á¤Ë°Ü¿¢¤¹¤ë¤³¤È¤Ë¤Ê¤Ã¤¿¤È¤­¤ËÅԹ礬¤¤¤¤¤è¤¦¤Ë¡¢
                 ¤â¤Ã¤È¾®¤µ¤ÊÅŵå¤òÍ׵᤹¤ë¤Î¤Ë 11 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>-hackers ¤È -chat ¤Î S/NÈæ¤Ëʸ¶ç¤ò¸À¤¤¡¢
                 ¹³µÄ¤Î¤¿¤á¹ÖÆɤò¼è¤ê¤ä¤á¤ë¤Î¤Ë 73 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¡Öunsubscribe¡×¡Ö¤É¤¦¤ä¤Ã¤¿¤é¹ÖÆɤò¤ä¤á¤é¤ì¤ë¤ó¤Ç¤¹¤«?¡×
                 ¡Ö¤³¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤«¤é¤ï¤¿¤·¤ò³°¤·¤Æ¤¯¤À¤µ¤¤¡×¤È¤¤¤Ã¤¿
                 ¥á¥Ã¥»¡¼¥¸¤ò¡¢Îã¤Î¥Õ¥Ã¥¿¤ò¤¯¤Ã¤Ä¤±¤ÆÅê¹Æ¤¹¤ë¤Î¤Ë 13 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¤ß¤ó¤Ê¤¬·ãÏÀ¤òÀï¤ï¤»¤ë¤Î¤ËË»¤¬¤·¤¯¤Æµ¤ÉÕ¤«¤Ê¤¤´Ö¤Ë¡¢
                 ºî¶ÈÃæ¤ÎÅŵå¤ò¥³¥ß¥Ã¥È¤¹¤ë¤Î¤Ë 1 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¿·¤·¤¤Åŵå¤Ï TenDRA ¤ò»È¤Ã¤Æ¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤¿¾ì¹ç¤Ë 0.364%
                 ¤âÌÀ¤ë¤¯¤Ê¤ë (¤¿¤À¤·Åŵå¤òΩÊýÂΤˤ·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤)¡¢
                 ¤À¤«¤é FreeBSD ¤Ï EGCS ¤«¤é TenDRA ¤ËÊѤ¨¤ë¤Ù¤­¤À¤È»ØŦ¤¹¤ë¤Î¤Ë 31 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¿·¤·¤¤Åŵå¤ÏÈþ¤·¤µ¤Ë·ç¤±¤Æ¤¤¤ë¤Èʸ¶ç¤ò¸À¤¦¤Î¤Ë 1 ¿Í¡£</para>
             </listitem>
             <listitem>
               <para>¡ÖMFC ¤Ã¤Æ²¿¤Ç¤¹¤«?¡×¤Èʹ¤¯¤Î¤Ë 9 ¿Í (send-pr ¤·¤¿¿Í¤â´Þ¤à)¡£</para>
             </listitem>
             <listitem>
               <para>Åŵ夬¼è¤êÂؤ¨¤é¤ì¤Æ¤«¤é
                 2 ½µ´Ö¤â¾Ã¤¨¤Ã¤Ñ¤Ê¤·¤À¤Èʸ¶ç¤ò¸À¤¦¤Î¤Ë 57 ¿Í¡£</para>
             </listitem>
           </itemizedlist>
 
             <note>
             <title>&a.nik; ¤Ë¤è¤ëÄɵ­</title>
               <para>
                 ¤³¤ì¤Ë¤ÏÇú¾Ð¤·¤Þ¤·¤¿¡£
               </para>
               <para>
                 ¤½¤ì¤«¤é¤ï¤¿¤·¤Ï¹Í¤¨¤Þ¤·¤¿¡£
                 ¡Ö¤Á¤ç¤Ã¤ÈÂԤƤè? ¤³¤Î¥ê¥¹¥È¤Î¤É¤³¤«¤Ë¡¢
                 ¡Ø¤³¤ì¤òʸ½ñ¤Ë¤Þ¤È¤á¤ë¤Î¤Ë 1¿Í¡Ù¤È¤¤¤¦¤Î¤¬¤¢¤Ã¤Æ¤â¤¤¤¤¤ó¤¸¤ã¤Ê¤¤¤«?¡×
               </para>
               <para>
                 ¤½¤ì¤«¤é¤ï¤¿¤·¤Ï¸ç¤ê¤ò³«¤¤¤¿¤Î¤Ç¤¹ <literal>:-)</literal>
               </para>
             </note>
 
             <para><emphasis>¤³¤Î¹àÌܤÎÃøºî¸¢¤Ï
               Copyright (c) 1999 &a.des; ¤Ë¤¢¤ê¤Þ¤¹¡£
               ̵ÃǤǻÈÍѤ·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£</emphasis>
           </para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="hackers">
     <title>¤Þ¤¸¤á¤Ê FreeBSD ¥Ï¥Ã¥«¡¼¤À¤±¤ÎÏÃÂê</title>
 
     <para>
       <emphasis>Ìõ:
         &a.iwasaki;¡¢
         1997 ǯ 11 ·î 8 Æü</emphasis>
     </para>
 
     <qandaset>
       <qandaentry>
         <question id="define-snap-release">
           <para>SNAP ¤È¤« RELEASE ¤È¤«¤Ï²¿?</para>
         </question>
 
         <answer>
           <para>¸½ºß¡¢FreeBSD ¤Î
             <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS ¥ê¥Ý¥¸¥È¥ê</ulink>
             ¤Ë¤Ï¡¢»°¤Ä¤Î¥¢¥¯¥Æ¥£¥Ö/½à¥¢¥¯¥Æ¥£¥Ö¤Ê¥Ö¥é¥ó¥Á¤¬¤¢¤ê¤Þ¤¹
             (¥¢¥¯¥Æ¥£¥Ö¤Ê³«È¯¥Ö¥é¥ó¥Á¤Ï»°¤Ä¤·¤«Â¸ºß¤·¤Ê¤¤¤¿¤á¡¢
             ¤ª¤½¤é¤¯ RELENG_2 ¥Ö¥é¥ó¥Á¤ÎÊѹ¹¤Ïǯ¤Ë 2 ²ó¤À¤±¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦)¡£</para>
 
             <itemizedlist>
               <listitem>
                 <para>
                   <literal>RELENG_2_2</literal>
                   Ä̾Π<emphasis>2.2-STABLE</emphasis>
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   <literal>RELENG_3</literal>
                   Ä̾Π<emphasis>3.X-STABLE</emphasis>
                 </para>
               </listitem>
 
               <listitem>
                 <para>
                   <literal>RELENG_4</literal>
                   Ä̾Π<emphasis>4-STABLE</emphasis></para>
               </listitem>
 
               <listitem>
                 <para><acronym>HEAD</acronym>
                   Ä̾Π<option>-CURRENT</option> ¤¢¤ë¤¤¤Ï
                   <emphasis>5.0-CURRENT</emphasis></para>
               </listitem>
 
             </itemizedlist>
 
           <para>
             <acronym>HEAD</acronym>
             ¤Ï¾¤ÎÆó¤Ä¤È°ã¤Ã¤Æ¡¢
             ¼ÂºÝ¤Î¥Ö¥é¥ó¥Á¥¿¥°¤Ç¤Ï¤Ê¤¯¡¢
             <emphasis>¡Öcurrent¡¢
               ʬ´ô¤·¤Æ¤¤¤Ê¤¤³«È¯ËÜή¡×</emphasis>¤Î¤¿¤á¤Îñ¤Ê¤ë¥·¥ó¥Ü¥ê¥Ã¥¯¤ÊÄê¿ô¤Ç¤¹¡£
             »ä¤¿¤Á¤Ï¤³¤ì¤ò <literal>-CURRENT</literal> ¤È¸Æ¤ó¤Ç¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             ¸½ºß¡¢
             <quote>-CURRENT</quote> ¤Ï 5.0 ¤Î³«È¯ËÜή¤Ç¤¢¤ê¡¢
             <literal>4.0-STABLE</literal> ¥Ö¥é¥ó¥Á¡¢
             ¤Ä¤Þ¤ê <literal>RELENG_4</literal> ¤Ï
             2000 ǯ 3 ·î¤Ë
             <quote>-CURRENT</quote> ¤«¤éʬ´ô¤·¤Æ¤¤¤Þ¤¹¡£
           </para>
 
           <para>
             <literal>2.2-STABLE</literal> ¥Ö¥é¥ó¥Á¡¢
             <literal>RELENG_2_2</literal> ¤Ï
             1996 ǯ 11 ·î¤Ë <quote>-CURRENT</quote> ¤«¤éʬ´ô¤·¤Þ¤·¤¿¡£
             ¤³¤ì¤ÏÊݼ餬´°Á´¤Ë½ªÎ»¤·¤Æ¤¤¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="custrel">
           <para>¼«Ê¬ÍѤΥ«¥¹¥¿¥à¥ê¥ê¡¼¥¹¤ò¹½ÃÛ¤¹¤ë¤Ë¤Ï?</para>
         </question>
 
         <answer>
           <para>
             ¥ê¥ê¡¼¥¹¤ò¹½ÃÛ¤¹¤ë¤Ë¤Ï»°¤Ä¤Î¤³¤È¤¬É¬ÍפǤ¹¡£¤Þ¤º¡¢
             &man.vn.4;
             ¥É¥é¥¤¥Ð¤¬ÁȤ߹þ¤Þ¤ì¤¿¥«¡¼¥Í¥ë¤ò¼Â¹Ô¤µ¤»¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             °Ê²¼¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤ËÄɲä·¡¢
             ¥«¡¼¥Í¥ë¤òºî¤êľ¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>pseudo-device vn         #Vnode driver (turns a file into a device)</programlisting>
           <para>
             ¼¡¤Ë¡¢CVS ¥ê¥Ý¥¸¥È¥êÁ´ÂΤò¼ê¸µ¤Ë¤ª¤¤¤Æ¤ª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤ì¤òÆþ¼ê¤¹¤ë¤Ë¤Ï
             <ulink url="../handbook/synching.html#CVSUP">CVSUP</ulink>
             ¤¬»ÈÍѤǤ­¤Þ¤¹¤¬¡¢supfile ¤Ç release ¤Î̾¾Î¤ò cvs ¤Ë¤·¤Æ
             ¾¤Î¥¿¥°¤ä date ¥Õ¥£¡¼¥ë¥É¤òºï½ü¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <programlisting>*default prefix=/home/ncvs
 *default base=/a
 *default host=cvsup.FreeBSD.org
 *default release=cvs
 *default delete compress use-rel-suffix
 
 ## Main Source Tree
 src-all
 src-eBones
 src-secure
 
 # Other stuff
 ports-all
 www
 doc-all</programlisting>
 
           <para>
             ¤½¤·¤Æ <command>cvsup -g supfile</command> ¤ò¼Â¹Ô¤·¤Æ¼«Ê¬¤Î¥Þ¥·¥ó¤Ë
             CVS ¥ê¥Ý¥¸¥È¥êÁ´ÂΤò¥³¥Ô¡¼¤·¤Þ¤¹¡Ä¡£
           </para>
 
           <para>
             ºÇ¸å¤Ë¡¢¥Ó¥ë¥ÉÍѤˤ«¤Ê¤ê¤Î¶õ¤­Îΰè¤òÍÑ°Õ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ò <filename>/some/big/filesystem</filename> ¤È¤·¤Æ¡¢
             ¾å¤ÎÎã¤Ç CVS ¥ê¥Ý¥¸¥È¥ê¤ò <filename>/home/ncvs</filename> ¤ËÃÖ¤¤¤¿¤â¤Î¤È¤¹¤ë¤È¡¢
             °Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ¥ê¥ê¡¼¥¹¤ò¹½ÃÛ¤·¤Þ¤¹¡£
           </para>
 
           <screen>&prompt.root; <userinput>setenv CVSROOT /home/ncvs</userinput>
  # or export CVSROOT=/home/ncvs
 &prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make buildworld</userinput>
 &prompt.root; <userinput>cd /usr/src/release</userinput>
 &prompt.root; <userinput>make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release</userinput>
       </screen>
 
         <note>
           <para>¤¿¤À¤·¡¢¤¹¤Ç¤Ë <filename>/usr/obj</filename>
             °Ê²¼¤Ë¹½ÃÛʪ¤¬Â¸ºß¤·¤Æ¤¤¤ë¤Ê¤é¡¢buildworld
             ¤ÎɬÍפÏ<emphasis>¤¢¤ê¤Þ¤»¤ó</emphasis>¡£</para>
         </note>
 
           <para>
             ½èÍý¤¬½ªÎ»¤¹¤ë¤È¡¢
             ¥ê¥ê¡¼¥¹Á´ÂΤ¬ <filename>/some/big/filesystem/release</filename>
             ¤Ë¹½ÃÛ¤µ¤ì¡¢´°Á´¤Ê <acronym>FTP</acronym> ¥¤¥ó¥¹¥È¡¼¥ëÍѤÎÇÛÉÛʪ¤¬
             <filename>/some/big/filesystem/release/R/ftp</filename> ¤ËºîÀ®¤µ¤ì¤Þ¤¹¡£
             -current °Ê³°¤Î³«È¯¥Ö¥é¥ó¥Á¤Î SNAP ¤ò¼«Ê¬¤Ç¹½ÃÛ¤·¤¿¤¤¾ì¹ç¤Ï¡¢
             <literal>RELEASETAG=SOMETAG</literal>
             ¤ò¾å¤Î <command>make release</command> ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤ËÄɲä·¤Þ¤¹¡£
             ¤¿¤È¤¨¤Ð¡¢<literal>RELEASETAG=RELENG_2_2</literal>
             ¤È¤¹¤ë¤ÈºÇ¿·¤Î 2.2-STABLE snapshot ¤¬¹½ÃÛ¤µ¤ì¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="custom-install-disks">
           <para>¥«¥¹¥¿¥à¤Î¥¤¥ó¥¹¥È¡¼¥ë¥Ç¥£¥¹¥¯¤òºî¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤¤¤¤¤Î¤Ç¤¹¤«? </para>
         </question>
 
         <answer>
           <para>
             <filename>/usr/src/release/Makefile</filename>
             ¤Î¤¤¤í¤¤¤í¤Ê¥¿¡¼¥²¥Ã¥È¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¥Ç¥£¥¹¥¯¡¢
             ¥½¡¼¥¹¡¢¥Ð¥¤¥Ê¥ê¥¢¡¼¥«¥¤¥Ö¤òºî¤ë´°Á´¤Ê½èÍý¤ò¼«Æ°Åª¤Ë¹Ô¤Ê¤¦¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             <filename>Makefile</filename> ¤Ë½½Ê¬¤Ê¾ðÊ󤬤¢¤ê¤Þ¤¹¡£
             ¤·¤«¤·¡¢¼Â¹Ô¤Ë¤Ï <quote>make world</quote> ¤¬É¬Íפǡ¢
             ¿¤¯¤Î»þ´Ö¤È¥Ç¥£¥¹¥¯¤ÎÍÆÎ̤¬É¬ÍפǤ¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="makeworld-clobbers">
           <para><quote>make world</quote>
             ¤ò¹Ô¤Ê¤¦¤È´û¸¤Î¥Ð¥¤¥Ê¥ê¤ò¾å½ñ¤­¤·¤Æ¤·¤Þ¤¦¤Î¤Ç¤¹¤¬¡£</para>
         </question>
 
         <answer>
           <para>¤¨¤¨¡¢¤½¤ì¤¬°ìÈÌŪ¤Ê¹Í¤¨Êý¤Ç¤¹¡£Ì¾Á°¤¬¼¨¤·¤Æ¤¤¤ë¤è¤¦¤Ë
             <quote>make world</quote>
             ¤Ï¤¹¤Ù¤Æ¤Î¥·¥¹¥Æ¥à¤Î¥Ð¥¤¥Ê¥ê¤òºÇ½é¤«¤éºî¤êľ¤·¤Þ¤¹¤Î¤Ç¡¢·ë²Ì¤È¤·¤Æ¡¢
             ¥¯¥ê¡¼¥ó¤Ç°ì´ÓÀ­¤Î¤¢¤ë´Ä¶­¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹
             (¤³¤ì¤¬¤½¤ì¤À¤±Ä¹¤¤»þ´Ö¤¬¤«¤«¤ëÍýͳ¤Ç¤¹)¡£
           </para>
 
           <para>
             ´Ä¶­ÊÑ¿ô <literal>DESTDIR</literal> ¤ò
             <quote><command>make world</command></quote> ¤ä
             <quote><command>make install</command></quote>
             ¤ò¼Â¹Ô¤¹¤ë»þ¤ËÄêµÁ¤·¤Æ¤ª¤¯¤È¡¢¿·¤·¤¯ºî¤é¤ì¤¿¥Ð¥¤¥Ê¥ê¤Ï
             <literal>${DESTDIR}</literal>¤ò <username>root</username>
             ¤È¤ß¤Ê¤·¤¿¥Ç¥£¥ì¥¯¥È¥ê¥Ä¥ê¡¼¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£
             ¤¢¤ë¤Ç¤¿¤é¤á¤Ê¶¦Í­¥é¥¤¥Ö¥é¥ê¤ÎÊѹ¹¤ä¥×¥í¥°¥é¥à¤ÎºÆ¹½Ãۤˤè¤Ã¤Æ
             <quote><command>make world</command></quote>
             ¤Ï¼ºÇÔ¤¹¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bus-speed-defaulted">
           <para>¥·¥¹¥Æ¥àµ¯Æ°»þ¤Ë
             <quote>(<computeroutput>bus speed defaulted</computeroutput>)</quote> ¤È¥á¥Ã¥»¡¼¥¸¤¬½Ð¤Þ¤¹¡£
           </para>
         </question>
 
         <answer>
           <para>
             Adaptec ¤Î 1542 SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤Ï¡¢
             ¥æ¡¼¥¶¤¬¥½¥Õ¥È¥¦¥§¥¢Åª¤Ë¥Ð¥¹¥¢¥¯¥»¥¹Â®ÅÙ¤ÎÀßÄê¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             °ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Î 1542 ¥É¥é¥¤¥Ð¤Ï¡¢
             »ÈÍѲÄǽ¤ÊºÇÂç¤Î®ÅÙ¤òµá¤á¤Æ¥¢¥À¥×¥¿¤ò¤½¤ÎÀßÄê¤Ë¤·¤è¤¦¤È¤·¤Þ¤·¤¿¡£
             ¤³¤ì¤ÏÆÃÄê¤Î¥æ¡¼¥¶¤Î¥·¥¹¥Æ¥à¤Ç¤ÏÌäÂ꤬¤¢¤ë»ö¤¬¤ï¤«¤ê¡¢
             ¸½ºß¤Ç¤Ï¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ª¥×¥·¥ç¥ó¤Ë
             <quote><symbol>TUNE_1542</symbol></quote> ¤¬²Ã¤¨¤é¤ì¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤ò»ÈÍѤ¹¤ë¤È¡¢¤³¤ì¤¬Æ¯¤¯¥·¥¹¥Æ¥à¤Ç¤Ï¥Ç¥£¥¹¥¯¤¬Â®¤¯¤Ê¤ê¤Þ¤¹¤¬¡¢
             ¥Ç¡¼¥¿¤Î¾×Æͤ¬µ¯¤­¤Æ®¤¯¤Ï¤Ê¤é¤Ê¤¤¥·¥¹¥Æ¥à¤â¤¢¤ë¤Ç¤·¤ç¤¦
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ctm">
           <para>¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥¢¥¯¥»¥¹¤ËÀ©¸Â¤¬¤¢¤Ã¤Æ¤â current ¤òÄɤ¤¤«¤±¤é¤ì¤Þ¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¤Ï¤¤¡¢
             <ulink url="../handbook/synching.html#CTM">CTM
               ¥·¥¹¥Æ¥à</ulink>¤ò»È¤Ã¤Æ¡¢
             ¥½¡¼¥¹¥Ä¥ê¡¼Á´ÂΤΥÀ¥¦¥ó¥í¡¼¥É¤ò<emphasis>¹Ô¤Ê¤ï¤º</emphasis>¤ËÄɤ¤¤«¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="split-240k">
           <para>¤É¤Î¤è¤¦¤Ë¤·¤ÆÇÛÉÛ¥Õ¥¡¥¤¥ë¤ò 240KB
             ¤Ëʬ³ä¤·¤Æ¤¤¤ë¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             Èæ³ÓŪ¿·¤·¤¤ BSD ¥Ù¡¼¥¹¤Î¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
             <command>split</command> ¤ËǤ°Õ¤Î¥Ð¥¤¥È¶­³¦¤Çʬ³ä¤¹¤ë
             <quote><option>-b</option></quote> ¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             °Ê²¼¤Ï <filename>/usr/src/Makefile</filename> ¤«¤é¤ÎÎã¤Ç¤¹¡£
           </para>
 
           <programlisting>bin-tarball:
               (cd ${DISTDIR}; \
               tar cf - . \
               gzip --no-name -9 -c | \
               split -b 240640 - \
               ${RELEASEDIR}/tarballs/bindist/bin_tgz.)</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="submitting-kernel-extensions">
           <para>»ä¤Ï¥«¡¼¥Í¥ë¤Ë³ÈÄ¥¤ò¹Ô¤Ê¤¤¤Þ¤·¤¿¡£
             ï¤ËÁ÷¤ì¤Ð¤¤¤¤¤Ç¤¹¤«? </para></question>
 
         <answer>
           <para>
             <ulink url="../handbook/contrib.html">FreeBSD
               ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î¡ÖFreeBSD ¤Ø¤Î¹×¸¥¡×</ulink>¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤¢¤Ê¤¿¤Î¥¢¥¤¥Ç¥£¥¢¤Ë´¶¼Õ¤·¤Þ¤¹!
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="pnp-initialize">
           <para><acronym>PnP</acronym> <acronym>ISA</acronym>
             ¥«¡¼¥É¤Î¸¡½Ð¤È½é´ü²½¤Ï¤É¤Î¤è¤¦¤Ë¹Ô¤Ê¤¦¤Î¤Ç¤¹¤«? </para>
         </question>
 
         <answer>
           <para>
             <ulink url="mailto:uhclem@nemesis.lonestar.org">Frank Durda IV »á</ulink> ¤è¤ê:
           </para>
 
           <blockquote>
             <para>
               Í×ÅÀ¤Ï¡¢¥Û¥¹¥È¤¬Ç§¼±¤µ¤ì¤Æ¤¤¤Ê¤¤¥Ü¡¼¥É¤òõ¤¹»þ¤Ë¡¢¤¹¤Ù¤Æ¤Î
               PnP ¥Ü¡¼¥É¤¬±þÅú¤¹¤ë¤³¤È¤Î¤Ç¤­¤ë¾¯¿ô¤Î I/O
               ¥Ý¡¼¥È¤¬¤¢¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£
               ¤½¤ì¤Ë¤è¤ê¡¢PnP ¥×¥í¡¼¥Ö¥ë¡¼¥Á¥ó¤¬³«»Ï¤·¤¿¤È¤­¡¢PnP
               ¥Ü¡¼¥É¤¬Â¸ºß¤¹¤ë¤Ê¤é¡¢¤¹¤Ù¤Æ¤Î PnP ¥Ü¡¼¥É¤Ï¼«Ê¬¤Î¥â¥Ç¥ëÈÖ¹æ¤òÊÖ¤·¤Þ¤¹¡£
               ¤½¤Î¥Ý¡¼¥È¤ò I/O read ¤¹¤ë¤È¥×¥í¡¼¥Ö¥ë¡¼¥Á¥ó¤ÏÌ䤤¤ËÂФ¹¤ë¥ï¥¤¥¢¡¼¥É-OR
               ¤µ¤ì¤¿ <quote>yes</quote> ¤òÆÀ¤Þ¤¹¡£¤³¤Î¾ì¹ç¤Ï
               ¾¯¤Ê¤¯¤È¤â 1 ¥Ó¥Ã¥È¤¬ ON ¤Ë¤Ê¤ê¤Þ¤¹¡£
               ¤½¤·¤Æ¡¢¥×¥í¡¼¥Ö¥ë¡¼¥Á¥ó¤Ï¥â¥Ç¥ë ID (Microsoft/Intel
               ¤Ë¤è¤Ã¤Æ³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤Þ¤¹)¤¬ X ¤è¤ê¾®¤µ¤¤¥Ü¡¼¥É¤ò
               <quote>¥ª¥Õ¥é¥¤¥ó</quote> ¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
               ¤³¤ÎÁàºî¤ò¹Ô¤Ê¤¤¡¢Ì䤤¹ç¤ï¤»¤Ë±þÅú¤·¤Æ¤¤¤ë¥Ü¡¼¥É¤¬¤Þ¤À
               »Ä¤Ã¤Æ¤¤¤ë¤«¤É¤¦¤«¤òÄ´¤Ù¤Þ¤¹¡£
               ¤â¤· <quote><literal>0</literal></quote> ¤¬Ê֤äƤ¯¤ë¤Ê¤é X
               ¤è¤êÂ礭¤Ê ID ¤ò»ý¤Ä¥Ü¡¼¥É¤Ï¤Ê¤¤¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
               º£ÅÙ¤Ï <quote>X</quote>
               ¤è¤ê¤â¾®¤µ¤ÊÃͤò»ý¤Ä¥Ü¡¼¥É¤Ë¤Ä¤¤¤ÆÌ䤤¹ç¤ï¤»¤Þ¤¹¡£
               ¤â¤·¤¢¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
               ¥×¥í¡¼¥Ö¥ë¡¼¥Á¥ó¤Ï¥â¥Ç¥ëÈֹ椬 X ¤è¤ê¾®¤µ¤¤¤³¤È¤òÃΤê¤Þ¤¹¡£
               º£Å٤ϡ¢X-(limit/4)
               ¤è¤êÂ礭¤ÊÃͤò»ý¤Ä¥Ü¡¼¥É¤ò¥ª¥Õ¥é¥¤¥ó¤Ë¤·¤ÆÌ䤤¹ç¤ï¤»¤ò·«¤êÊÖ¤·¤Þ¤¹¡£
               ¤³¤Î ID ¤ÎÈϰϤˤè¤ë½à¥Ð¥¤¥Ê¥ê¥µ¡¼¥Á¤ò½½Ê¬·«¤êÊÖ¤¹¤³¤È¤Ë¤è¤ê¡¢
               ¥×¥í¡¼¥Ö¥ë¡¼¥Á¥ó¤Ï¥Þ¥·¥ó¤Ë¸ºß¤¹¤ë¤¹¤Ù¤Æ¤Î
               PnP ¥Ü¡¼¥É¤ÎÃͤòºÇ½ªÅª¤ËÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤½¤Î·«¤êÊÖ¤·¤Î²ó¿ô¤Ï
               2^64 ¤è¤ê¤Ï¤ë¤«¤Ë¾¯¤Ê¤¤²ó¿ô¤Ç¤¹¡£
             </para>
 
             <para>
               ID ¤ÏÆó¤Ä¤Î 32-bit (¤Ä¤Þ¤ê 64bit) ¥Õ¥£¡¼¥ë¥É + 8 bit
               ¥Á¥§¥Ã¥¯¥µ¥à¤«¤é¤Ê¤ê¤Þ¤¹¡£ºÇ½é¤Î 32 bits ¤Ï¥Ù¥ó¥À¤Î¼±Ê̻ҤǤ¹¡£
               ¤³¤ì¤Ï¸øɽ¤µ¤ì¤Æ¤Ï¤¤¤Þ¤»¤ó¤¬¡¢
               Ʊ°ì¤Î¥Ù¥ó¥À¤«¤é¶¡µë¤µ¤ì¤Æ¤¤¤ë°Û¤Ê¤ë¥¿¥¤¥×¤Î¥Ü¡¼¥É¤Ç¤Ï°Û¤Ê¤ë
               32-bit ¥Ù¥ó¥À ID ¤ò»ý¤Ä¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¹Í¤¨¤é¤ì¤Þ¤¹¡£
               À½Â¤¸µ¤òÆÃÄꤹ¤ë¤À¤±¤Î¤¿¤á¤Ë 32-bit
               ¤Ï¤¤¤¯¤é¤«²á¾ê¤Ç¤¹¡£
             </para>
 
             <para>
               ²¼°Ì¤Î 32-bit ¤Ï¥·¥ê¥¢¥ëÈֹ桢
               ¥¤¡¼¥µ¥Í¥Ã¥È¥¢¥É¥ì¥¹¤Ê¤É¤Î¥Ü¡¼¥É¤òÆÃÄꤹ¤ë¤â¤Î¤Ç¤¹¡£
               ¥Ù¥ó¥À¤Ï¾å°Ì 32 bits ¤¬°Û¤Ê¤Ã¤Æ¤¤¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢
               ²¼°Ì 32-bit ¤¬Æ±°ì¤Ç¤¢¤ë 2ËçÌܤΥܡ¼¥É¤òÀ½Â¤¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
               ¤·¤¿¤¬¤Ã¤Æ¡¢Æ±¤¸¥¿¥¤¥×¤ÎÊ£¿ô¤Î¥Ü¡¼¥É¤ò¥Þ¥·¥ó¤Ë¤¤¤ì¤ë¤³¤È¤¬¤Ç¤­¡¢
               ¤³¤Î¾ì¹ç¤Ç¤â 64-bit
               Á´ÂΤǤϥæ¥Ë¡¼¥¯¤Ç¤¹¡£
             </para>
 
             <para>
               32-bit ¤Î¥Õ¥£¡¼¥ë¥É¤Ï¤¹¤Ù¤Æ¤ò 0 ¤Ë¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
               ¤³¤ì¤Ï½é´ü²½¤Î¥Ð¥¤¥Ê¥ê¥µ¡¼¥Á¤Î´Ö¥ï¥¤¥¢¡¼¥É-OR
               ¤Ë¤è¤Ã¤Æ 0 ¤Ç¤Ï¤Ê¤¤
               ¥Ó¥Ã¥È¤ò»²¾È¤¹¤ë¤«¤é¤Ç¤¹¡£
             </para>
 
             <para>
               ¥·¥¹¥Æ¥à¤¬¤¹¤Ù¤Æ¤Î¥Ü¡¼¥É¤ÎÍ¿¤¨¤é¤ì¤¿ ID ¤òǧ¼±¤¹¤ë¤È¡¢
               ¤½¤ì¤¾¤ì¤Î¥Ü¡¼¥É¤ËÂбþ¤·¤¿½èÍý¤ò°ì¤Ä¤º¤Ä (Ʊ°ì¤Î
               I/O ¥Ý¡¼¥È¤òÄ̤·¤Æ) ¹Ô¤Ê¤¤¤Þ¤¹¡£
               ¤½¤·¤Æ¡¢ÍøÍѤǤ­¤ë³ä¤ê¹þ¤ß¤ÎÁªÂò¤Ê¤É¤Î¥Ü¡¼¥É¤¬É¬ÍפȤ¹¤ë¥ê¥½¡¼¥¹¤ò¸¡½Ð¤·¤Þ¤¹¡£
               ¤¹¤Ù¤Æ¤Î¥Ü¡¼¥É¤Ë¤Ä¤¤¤Æ¤³¤Î¾ðÊó¤ò½¸¤á¤Þ¤¹¡£
             </para>
 
             <para>
               ¤³¤Î¾ðÊó¤Ï¥Ï¡¼¥É¥Ç¥£¥¹¥¯¾å¤Î ECU ¥Õ¥¡¥¤¥ë¤Ê¤É¤Î¾ðÊó¤È¤Þ¤È¤á¤é¤ì¡¢
               ¥Þ¥¶¡¼¥Ü¡¼¥É¤Î BIOS ¤Ë¤â·ë¹ç¤µ¤ì¤Þ¤¹¡£
               ¥Þ¥¶¡¼¥Ü¡¼¥É¾å¤Î¥Ï¡¼¥É¥¦¥§¥¢¤Ø¤Î ECU ¤È
               BIOS PnP ¤Î¥µ¥Ý¡¼¥È¤ÏÄ̾ï¤ÏÅý¹ç¤µ¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢
               ¼þÊÕµ¡´ï¤Ë¤Ä¤¤¤Æ¤Ï¿¿¤Î PnP¤Ç¤¢¤ë¤È¤Ï¤¤¤¨¤Þ¤»¤ó¡£
               ¤·¤«¤·¡¢BIOS ¤Î¾ðÊó¤Ë ECU ¤Î¾ðÊó¤ò²Ã¤¨¤ÆÄ´ºº¤¹¤ë¤³¤È¤Ç¡¢
               ¥×¥í¡¼¥Ö¥ë¡¼¥Á¥ó¤Ï PnP
               ¥Ç¥Ð¥¤¥¹¤¬ºÆÇÛÃ֤Ǥ­¤Ê¤¯¤Ê¤ë¤³¤È¤òÈò¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
             </para>
 
             <para>
               ¤½¤ì¤«¤é¡¢ºÆÅÙ PnP ¥Ç¥Ð¥¤¥¹¤Ë¥¢¥¯¥»¥¹¤·¡¢I/O¡¢DMA¡¢IRQ¡¢
               ¥á¥â¥ê¥Þ¥Ã¥×¥¢¥É¥ì¥¹¤ÎÀßÄê¤ò¤·¤Þ¤¹¡£
               ¥Ç¥Ð¥¤¥¹¤Ï¤³¤Î¥¢¥É¥ì¥¹¤Ë¸«¤¨¤ë¤è¤¦¤Ë¤Ê¤ê¡¢
               ¼¡¤ËºÆµ¯Æ°¤¹¤ë¤Þ¤Ç¤³¤Î°ÌÃÖ¤òÀê¤á¤Þ¤¹¡£¤·¤«¤·¡¢
               ¤¢¤Ê¤¿¤Î˾¤à»þ¤Ë°ÜÆ°¤µ¤»¤ë¤³¤È¤¬ÉÔ²Äǽ¤Ç¤¢¤ë¡¢
               ¤È¤¤¤Ã¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             </para>
 
             <para>
               °Ê¾å¤ÎÏäǤÏÂ礭¤¯Ã±½ã²½¤ò¤·¤Æ¤¢¤ê¤Þ¤¹¤¬¡¢
               ´ðËÜŪ¤Ê¹Í¤¨Êý¤ÏÆÀ¤é¤ì¤¿¤Ç¤·¤ç¤¦¡£
             </para>
 
             <para>
               ¥Þ¥¤¥¯¥í¥½¥Õ¥È¤Ï¡¢¥Ü¡¼¥É¤Î¥í¥¸¥Ã¥¯¤¬ÂÐΩ¤¹¤ë
               I/O ¥µ¥¤¥¯¥ë¤Ç¤Ï¥Ç¥³¡¼¥É¤·¤Æ¤¤¤Ê¤¤ (ÌõÃí:
               ¤ª¤½¤é¤¯ read »þ¤·¤«¥Ç¥³¡¼¥É¤µ¤ì¤Æ¤¤¤º
               write »þ¤Ï¥Ý¡¼¥È¤¬¶õ¤¤¤Æ¤¤¤ë¤È¤¤¤¦°ÕÌ£¤Ç¤·¤ç¤¦)¡¢
               ¥×¥é¥¤¥Þ¥ê¥×¥ê¥ó¥¿¤Î¥¹¥Æ¡¼¥¿¥¹¥Ý¡¼¥È¤Î¤¤¤¯¤Ä¤«¤ò PnP
               ¤Î¤¿¤á¤ËÀêÍ­¤·¤Þ¤·¤¿¡£
               »ä¤Ï½é´ü¤Î PnP ¤ÎÄó°Æ¥ì¥Ó¥å¡¼»þ¤Ë IBM
               ½ãÀµ¤Î¥×¥ê¥ó¥¿¥Ü¡¼¥É¤Ç¥¹¥Æ¡¼¥¿¥¹¥Ý¡¼¥È¤Î write
               ¤Î¥Ç¥³¡¼¥É¤¬¤µ¤ì¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È¤Ëµ¤¤¬¤Ä¤­¤Þ¤·¤¿¤¬¡¢
               MS ¤Ï <quote>tough (´è¸Ç¡¢ÉÔ±¿¡¢ÌµË¡¤Ê)</quote>
               ¤È¸À¤Ã¤Æ¤¤¤Þ¤¹¡£
               ¤½¤·¤Æ¥×¥ê¥ó¥¿¤Î¥¹¥Æ¡¼¥¿¥¹¥Ý¡¼¥È¤Ø¥¢¥É¥ì¥¹¤ÎÀßÄê¤Î¤¿¤á¤Ë
               write ¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£¤Þ¤¿¡¢
               ¤½¤Î¥¢¥É¥ì¥¹ + <literal>0x800</literal> ¤È
               read ¤Î¤¿¤á¤Î 3ÈÖÌܤΠI/O ¥Ý¡¼¥È¤¬
               <literal>0x200</literal> ¤«¤é
               <literal>0x3ff</literal> ¤Î´Ö¤Î¤É¤³¤«¤ËÃÖ¤«¤ì¤ë¤Ç¤·¤ç¤¦¡£
             </para>
           </blockquote>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="architectures">
           <para>FreeBSD ¤Ï¡¢Â¾¤Î¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤ò¥µ¥Ý¡¼¥È¤·¤Ê¤¤¤ó¤Ç¤¹¤«? </para>
         </question>
 
         <answer>
           <para>
             ¤¤¤¯¤Ä¤«¤Î¥°¥ë¡¼¥×¤Î¿Í¡¹¤¬¡¢FreeBSD
             ¤Î¾¤Î¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ø¤Î°Ü¿¢¤Ë´Ø¿´¤ò¼¨¤·¤Æ¤ª¤ê¡¢
             FreeBSD/AXP (ALPHA) ¤Ï¤³¤ì¤é¤ÎÀ®²Ì¤È¤·¤Æ¤Ï¤È¤Æ¤âÀ®¸ù¤·¤¿¤â¤Î¤Î°ì¤Ä¤Ç¤¹¡£
             FreeBSD/AXP ¤Ï¸½ºß
             <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/alpha/">ftp://ftp.FreeBSD.org/pub/FreeBSD/alpha</ulink>
             ¤«¤éÆþ¼ê¤Ç¤­¤Þ¤¹¡£
             ALPHA ¤Ø¤Î°Ü¿¢ÈǤ¬¸½ºßÆ°¤¯µ¡¼ï¤ÏÁý¤¨¤Ä¤Ä¤¢¤ê¡¢
             ¤½¤ÎÃæ¤Ë¤Ï AlphaStation¡¢AXPpci¡¢PC164¡¢Miata ¤½¤·¤Æ Multia
             ¤È¤¤¤Ã¤¿¥â¥Ç¥ë¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
             ¸½¾õ¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤òÆÀ¤ë¤Ë¤Ï
             <email>freebsd-alpha@FreeBSD.org</email><link linkend="mailing">¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</link>¤Ë»²²Ã¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¤½¤Î¾¤Ë FreeBSD ¤Î SPARC ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ø¤Î°Ü¿¢¤¬¤¢¤ê¤Þ¤¹¡£
             ¥×¥í¥¸¥§¥¯¥È¤Ø¤Î»²²Ã¤Ë¶½Ì£¤¬¤¢¤ëÊý¤Ï
             <email>freebsd-sparc@FreeBSD.org</email><link linkend="mailing">¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</link>
             ¤Ë»²²Ã¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¿Ê¹ÔÃæ¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Î¥ê¥¹¥È¤Ë¤â¤Ã¤È¤âºÇ¶áÄɲ䵤줿¤Î¤¬
             IA-64 ¤È PowerPC¤Ç¤¹¡£¾ÜºÙ¤Ï
             <email>freebsd-ia64@FreeBSD.org</email> ¤ª¤è¤Ó/¤¢¤ë¤¤¤Ï
             <email>freebsd-ppc@FreeBSD.org</email><link
             linkend="mailing">¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</link>¤Ë»²²Ã¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¿·¤·¤¤¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ë´Ø¤¹¤ë°ìÈÌŪ¤ÊµÄÏÀ¤Ë¤Ä¤¤¤Æ¤Ï
             ¿·¤·¤¤¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ë´Ø¤¹¤ë°ìÈÌŪ¤ÊµÄÏÀ¤Ë¤Ä¤¤¤Æ¤Ï
             <email>freebsd-platforms@FreeBSD.org</email><link linkend="mailing">¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</link>
             ¤Ø»²²Ã¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="major-numbers">
           <para>¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤ò³«È¯¤·¤¿¤Î¤Ç¡¢¥á¥¸¥ã¡¼Èֹ椬Íߤ·¤¤¤Î¤Ç¤¹¤¬¡£</para>
         </question>
 
         <answer>
           <para>
             ¤³¤ì¤Ï¡¢³«È¯¤·¤¿¥É¥é¥¤¥Ð¤ò¸ø³«¤¹¤ë¤«¤É¤¦¤«¤Ë°Í¸¤·¤Þ¤¹¡£
             ¸ø³«¤¹¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢¥É¥é¥¤¥Ð¤Î¥½¡¼¥¹¥³¡¼¥É¡¢
             <filename>files.i386</filename> ¤ÎÊѹ¹¡¢
             ¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤Î¥µ¥ó¥×¥ë¡¢
             ¥Ç¥Ð¥¤¥¹¤¬»È¤¦¥¹¥Ú¥·¥ã¥ë¥Õ¥¡¥¤¥ë¤òºîÀ®¤¹¤ë
             &man.MAKEDEV.8;
             ¤Î¥³¡¼¥É¤ò»ä¤¿¤Á¤ËÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
             ¸ø³«¤¹¤ë¤Ä¤â¤ê¤¬¤Ê¤¤¾ì¹ç¡¢¥é¥¤¥»¥ó¥¹¤ÎÌäÂê¤Ë¤è¤ê¸ø³«¤Ç¤­¤Ê¤¤¾ì¹ç¤Ï¡¢
             ¥­¥ã¥é¥¯¥¿¥á¥¸¥ã¡¼ÈÖ¹æ 32 ¤ª¤è¤Ó¡¢
             ¥Ö¥í¥Ã¥¯¥á¥¸¥ã¡¼ÈÖ¹æ 8 ¤¬¤³¤Î¤è¤¦¤ÊÌÜŪ¤Î¤¿¤á¤ËͽÌ󤵤ì¤Æ¤¤¤Þ¤¹¡£
             ¤³¤ì¤é¤ÎÈÖ¹æ¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
             ¤É¤Á¤é¤Î¾ì¹ç¤Ç¤¢¤ì¡¢¥É¥é¥¤¥Ð¤Ë´Ø¤¹¤ë¾ðÊó¤ò
             &a.hackers;
             ¤Ëή¤·¤Æ失¤ë¤È½õ¤«¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="alternate-directory-layout">
           <para>ÂåÂؤΥǥ£¥ì¥¯¥È¥êÇÛÃ֥ݥꥷ¡¼</para>
         </question>
 
         <answer>
           <para>
             ¸½ºß»È¤ï¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ÎÇÛÃ֥ݥꥷ¡¼¤Ï¡¢
             »ä¤¬ 1983 ǯ¤Ë½ñ¤¤¤¿¤â¤Î¤«¤éÁ´¤¯Êѹ¹¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£
             »ä¤ÏÅö½é¤ÎÇÛÃ֥ݥꥷ¡¼¤ò¡¢¥ª¥ê¥¸¥Ê¥ë¤Î fast filesystem ¤Î¤¿¤á¤Ë½ñ¤­¡¢
             ¤Þ¤Ã¤¿¤¯²þÄꤷ¤Æ¤¤¤Þ¤»¤ó¡£
             ¤³¤Î¥Ý¥ê¥·¡¼¤Ï¥·¥ê¥ó¥À¥°¥ë¡¼¥×¤ò»È¤¤¿Ô¤¯¤¹¤Î¤òËɤ°¤Ë¤Ï¤¦¤Þ¤¯¤¤¤­¤Þ¤·¤¿¤¬¡¢
             ¤ªµ¤¤Å¤­¤ÎÊý¤â¤¤¤ëÄ̤ê find ¤ÎÆ°ºî¤Ë¤ÏÉÔŬÀڤǤ¹¡£
             ¤Û¤È¤ó¤É¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÆâÍƤϡ¢
             ¿¼¤µÍ¥À踡º÷ (ftw ¤È¤â¸Æ¤Ð¤ì¤Þ¤¹) ¤Ë¤è¤Ã¤Æºî¤é¤ì¤¿¥¢¡¼¥«¥¤¥Ö¤«¤é¡¢
             Ãê½Ð (restore) ¤·¤ÆºîÀ®¤µ¤ì¤Þ¤¹¡£¤³¤ÎºÝ¡¢
             ¥Ç¥£¥ì¥¯¥È¥ê¤Ï¡¢¥·¥ê¥ó¥À¥°¥ë¡¼¥×¤Ë¤Þ¤¿¤¬¤Ã¤ÆÇÛÃÖ¤µ¤ì¡¢
             °Ê¹ß¤Î¿¼¤µÍ¥À踡º÷¤ò¹Ô¤¦¤Ë¤Ï¡¢
             ¹Í¤¨ÆÀ¤ë¸Â¤êºÇ°­¤Î¾õÂ֤ˤʤê¤Þ¤¹¡£
             ¤â¤·ºîÀ®¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ÎÁí¿ô¤¬¤ï¤«¤Ã¤Æ¤¤¤ì¤Ð¡¢
             ²ò·èÊýË¡¤Ï¤¢¤ê¤Þ¤¹¡£(Áí¿ô/¥·¥ê¥ó¥À¥°¥ë¡¼¥×¿ô) ¸Ä¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ò¡¢
             ¥·¥ê¥ó¥À¥°¥ë¡¼¥×¤´¤È¤Ë¤Þ¤È¤á¤ÆºîÀ®¤¹¤ì¤ÐÎɤ¤¤Î¤Ç¤¹¡£
             ¤â¤Á¤í¤óºÇŬ¤Ê¥Ç¥£¥ì¥¯¥È¥êÇÛÃ֤ˤʤë¤è¤¦¤Ë¡¢
             Áí¿ô¤òͽ¬¤¹¤ëÊýË¡¤ò¹Í¤¨¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤·¤«¤·²¾¤Ë¥·¥ê¥ó¥À¥°¥ë¡¼¥×¤¢¤¿¤ê¤Î¥Ç¥£¥ì¥¯¥È¥ê¿ô¤ò
             10 ¤¯¤é¤¤¤Î¾®¤µ¤Ê¿ô¤Ë¸ÇÄꤷ¤Æ¤·¤Þ¤Ã¤¿¤È¤·¤Æ¤â¡¢
             ÂçÉý¤Ê²þÁ±¤¬Ë¾¤á¤ë¤Ç¤·¤ç¤¦¡£
             ¤³¤Î¥Ý¥ê¥·¡¼¤òÍѤ¤¤ë¤Ù¤­¥ê¥¹¥È¥¢ºî¶È¤ò¡¢Ä̾ï¤Îºî¶È
             (¤ª¤½¤é¤¯´û¸¤Î¥Ý¥ê¥·¡¼¤ò»ÈÍѤ·¤¿¤Û¤¦¤¬Îɤ¤¤Ç¤·¤ç¤¦)
             ¤ò¶èÊ̤¹¤ë¤Ë¤Ï¡¢
             10 Éô֤δ֤˺îÀ®¤µ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤òºÇÂç
             10 ¸Ä¤Þ¤Ç¤Þ¤È¤á¤Æñ°ì¤Î¥·¥ê¥ó¥À¥°¥ë¡¼¥×¤Ë½ñ¤­¹þ¤à¤È¤¤¤¦¼ê½ç¤¬»È¤¨¤ë¤Ç¤·¤ç¤¦¡£
             ¤È¤Ë¤«¤¯»ä¤Î·ëÏÀ¤Ï¡¢¤½¤í¤½¤í¼Â¸³¤ò»Ï¤á¤Æ¸«¤ë»þ´ü¤À¤í¤¦¤È¤¤¤¦¤³¤È¤Ç¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="kernel-panic-troubleshooting">
           <para>¥«¡¼¥Í¥ë¥Ñ¥Ë¥Ã¥¯¤òºÇÂç¸Â¤ËÍøÍѤ¹¤ë</para>
         </question>
 
         <answer>
             <note>
               <para>
                 ¤³¤ÎÀá¤Ï¡¢freebsd-current <link linkend="mailing">¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</link>¤Ë
                 &a.wpaul; »á¤¬Åê¹Æ¤·¤¿¥á¡¼¥ë¤ò¡¢
                 &a.des; »á¤¬¹»Àµ¤·¡¢[] Æâ¤Î¥³¥á¥ó¥È¤òÄɲ䷤ưúÍѤ·¤¿¤â¤Î¤Ç¤¹¡£
               </para>
             </note>
 
           <programlisting>From: Bill Paul &lt;wpaul@skynet.ctr.columbia.edu&gt;
 Subject: Re: the fs fun never stops
 To: ben@rosengart.com
 Date: Sun, 20 Sep 1998 15:22:50 -0400 (EDT)
 Cc: current@FreeBSD.ORG</programlisting>
 
           <para><emphasis>[&lt;ben@rosengart.com&gt; ¤¬°Ê²¼¤Î¥Ñ¥Ë¥Ã¥¯¥á¥Ã¥»¡¼¥¸¤òÅê¹Æ¤·¤Þ¤·¤¿¡£]</emphasis></para>
 
           <programlisting>&gt; Fatal trap 12: page fault while in kernel mode
 &gt; fault virtual address   = 0x40
 &gt; fault code              = supervisor read, page not present
 &gt; instruction pointer     = 0x8:0xf014a7e5
                                 ^^^^^^^^^^
 &gt; stack pointer           = 0x10:0xf4ed6f24
 &gt; frame pointer           = 0x10:0xf4ed6f28
 &gt; code segment            = base 0x0, limit 0xfffff, type 0x1b
 &gt;                         = DPL 0, pres 1, def32 1, gran 1
 &gt; processor eflags        = interrupt enabled, resume, IOPL = 0
 &gt; current process         = 80 (mount)
 &gt; interrupt mask          =
 &gt; trap number             = 12
 &gt; panic: page fault</programlisting>
 
           <para>
             ¤³¤Î¤è¤¦¤Ê¥á¥Ã¥»¡¼¥¸¤¬É½¼¨¤µ¤ì¤¿¾ì¹ç¡¢ÌäÂ꤬µ¯¤­¤ë¾õ¶·¤ò³Îǧ¤·¤Æ¡¢
             ¾ðÊó¤òÁ÷¤ë¤À¤±¤Ç¤Ï½½Ê¬¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
             ²¼Àþ¤ò¤Ä¤±¤¿Ì¿Îá¥Ý¥¤¥ó¥¿ÃͤϽÅÍפÊÃͤǤ¹¤¬¡¢
             »ÄÇ°¤Ê¤¬¤é¤³¤ÎÃͤϹ½À®¤Ë°Í¸¤·¤Þ¤¹¡£¤Ä¤Þ¤ê¡¢
             ¤³¤ÎÃͤϻȤäƤ¤¤ë¥«¡¼¥Í¥ë¤Î¥¤¥á¡¼¥¸¤Ë°Í¸¤¹¤ë¤Î¤Ç¤¹¡£
             ¤â¤·¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ê¤É¤Î GENERIC ¥«¡¼¥Í¥ë¤ò»È¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
             ¾¤Î¿Í´Ö¤¬ÌäÂê¤Î¤¢¤ë´Ø¿ô¤Ë¤Ä¤¤¤ÆÄÉ»î¤ò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢
             ¥«¥¹¥¿¥Þ¥¤¥º¤µ¤ì¤¿¥«¡¼¥Í¥ë¤Î¾ì¹ç¤Ï¡¢
             »È¤Ã¤Æ¤¤¤ëËܿͤˤ·¤«ÌäÂê¤Îµ¯¤³¤Ã¤¿¾ì½ê¤ÏÆÃÄê¤Ç¤­¤Ê¤¤¤Î¤Ç¤¹¡£
           </para>
 
           <para>
             ²¿¤ò¤¹¤ì¤ÐÎɤ¤¤Î¤Ç¤·¤ç¤¦?
           </para>
 
             <procedure>
               <step>
                 <para>
                   Ì¿Îá¥Ý¥¤¥ó¥¿Ãͤò¥á¥â¤·¤Þ¤¹¡£
                   <literal>0x8:</literal> ¤È¤¤¤¦Éôʬ¤Ïº£²óɬÍפ¢¤ê¤Þ¤»¤ó¡£
                   ɬÍ×¤Ê¤Î¤Ï <literal>0xf0xxxxxx</literal> ¤È¤¤¤¦Éôʬ¤Ç¤¹¡£
                 </para>
               </step>
 
               <step>
                 <para>
                   ¥·¥¹¥Æ¥à¤¬ºÆµ¯Æ°¤·¤¿¤é¡¢°Ê²¼¤ÎÁàºî¤ò¹Ô¤¤¤Þ¤¹¡£
 
                   <screen>&prompt.user; <userinput>nm -n /kernel.that.caused.the.panic | grep f0xxxxxx</userinput></screen>
 
                   ¤³¤³¤Ç¡¢<literal>f0xxxxxx</literal> ¤ÏÌ¿Îá¥Ý¥¤¥ó¥¿ÃͤǤ¹¡£
                   ¥«¡¼¥Í¥ë¥·¥ó¥Ü¥ë¤Î¥Æ¡¼¥Ö¥ë¤Ï´Ø¿ô¤Î¥¨¥ó¥È¥ê¥Ý¥¤¥ó¥È¤ò´Þ¤ß¡¢
                   Ì¿Îá¥Ý¥¤¥ó¥¿Ãͤϡ¢´Ø¿ôÆâÉô¤Î¤¢¤ëÅÀ¤Ç¤¢¤êºÇ½é¤ÎÅÀ¤Ç¤Ï¤Ê¤¤¤¿¤á¡¢
                   ¤³¤ÎÁàºî¤ò¹Ô¤Ã¤Æ¤â´°Á´¤Ë°ìÃפ¹¤ë¤â¤Î¤¬É½¼¨¤µ¤ì¤Ê¤¤¾ì¹ç¤â¤¢¤ê¤Þ¤¹¡£
                   ¤³¤Î¾ì¹ç¤Ï¡¢
                   ºÇ¸å¤Î·å¤ò¾Ê¤¤¤Æ¤â¤¦¤¤¤Á¤É¤ä¤Ã¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
                   ¤³¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
 
                   <screen>&prompt.user; <userinput>nm -n /kernel.that.caused.the.panic | grep f0xxxxx</userinput></screen>
 
                   ¤³¤ì¤Ç¤â°ìÃפ·¤Ê¤¤¾ì¹ç¤Ï¡¢
                   ·å¤ò¸º¤é¤·¤Ê¤¬¤é²¿¤é¤«¤Î½ÐÎϤ¬¤¢¤ë¤Þ¤Ç·«¤êÊÖ¤·¤Æ¤¯¤À¤µ¤¤¡£
                   ²¿¤«½ÐÎϤµ¤ì¤¿¤é¡¢
                   ¤½¤ì¤¬¥«¡¼¥Í¥ë¥Ñ¥Ë¥Ã¥¯¤ò°ú¤­µ¯¤³¤·¤¿²ÄǽÀ­¤Î¤¢¤ë´Ø¿ô¤Î¥ê¥¹¥È¤Ç¤¹¡£
                   ¤³¤ì¤Ï¡¢ÌäÂêÅÀ¤ò¸«ÉÕ¤±¤ëÀµ³Î¤ÊÊýË¡¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢²¿¤â¤Ê¤¤¤è¤ê¤Þ¤·¤Ç¤¹¡£
                 </para>
               </step>
             </procedure>
 
           <para>
             ¤³¤Î¤è¤¦¤Ê¥Ñ¥Ë¥Ã¥¯¥á¥Ã¥»¡¼¥¸¤òÅê¹Æ¤·¤Æ¤¤¤ë¿Í¤Ï¤è¤¯¸«³Ý¤±¤Þ¤¹¤¬¡¢
             ¤³¤Î¤è¤¦¤Ë¡¢Ì¿Îá¥Ý¥¤¥ó¥¿Ãͤò¡¢
             ¥«¡¼¥Í¥ë¥·¥ó¥Ü¥ë¥Æ¡¼¥Ö¥ë¤ÎÃæ¤Î´Ø¿ô¤È¤Ä¤­¹ç¤ï¤»¤ÆÄ´¤Ù¤Æ¤¤¤ë¿Í¤Ï¤Þ¤ì¤Ç¤¹¡£
           </para>
 
           <para>
             ¥Ñ¥Ë¥Ã¥¯¤Î¸¶°ø¤òÆͤ­»ß¤á¤ëºÇÎɤÎÊýË¡¤Ï¡¢¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤ò¤È¤ê¡¢
             &man.gdb.1; ¤Ç¥¹¥¿¥Ã¥¯¥È¥ì¡¼¥¹¤ò¹Ô¤¦¤³¤È¤Ç¤¹¡£
           </para>
 
           <para>
             ¤É¤Ã¤Á¤Ë¤·¤í¡¢»ä¤ÏÉáÄ̰ʲ¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£
           </para>
 
             <procedure>
               <step>
                 <para>
                   ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤òºî¤ê¤Þ¤¹¡£
                   ¥«¡¼¥Í¥ë¥Ç¥Ð¥Ã¥¬¤¬É¬Íפ½¤¦¤Ç¤¢¤ì¤Ð
                   <literal>options 'DDB'</literal>
                   ¤ò²Ã¤¨¤Æ¤âÎɤ¤¤Ç¤¹ (»ä¤Ï±Êµ×¥ë¡¼¥×¤¬µ¯¤³¤Ã¤Æ¤¤¤½¤¦¤Ê¾ì¹ç¤Ë¡¢
                   ¥Ö¥ì¡¼¥¯¥Ý¥¤¥ó¥È¤òÀßÄꤹ¤ë¤Î¤Ë»È¤Ã¤Æ¤¤¤Þ¤¹)¡£
                 </para>
               </step>
 
               <step>
                 <para>
                   <command>config -g KERNELCONFIG</command>
                   ¤È¤·¤Æ¥Ó¥ë¥É¥Ç¥£¥ì¥¯¥È¥ê¤òÀßÄꤷ¤Þ¤¹¡£
                 </para>
               </step>
 
               <step>
                 <para>
                   <command>cd /sys/compile/KERNELCONFIG; make</command> ¤ò¼Â¹Ô¤·¤Þ¤¹¡£
                 </para>
               </step>
 
               <step>
                 <para>¥«¡¼¥Í¥ë¤Î¥³¥ó¥Ñ¥¤¥ë¤¬½ªÎ»¤¹¤ë¤Î¤òÂÔ¤Á¤Þ¤¹¡£</para>
               </step>
 
               <step>
                 <para><command>make install</command> ¤ò¼Â¹Ô¤·¤Þ¤¹¡£</para>
               </step>
 
               <step>
                 <para>ºÆµ¯Æ°¤·¤Þ¤¹¡£</para>
               </step>
             </procedure>
 
           <para>
               &man.make.1; ¥×¥í¥»¥¹¤Ï£²¤Ä¤Î¥«¡¼¥Í¥ë¡¢
             <filename>kernel</filename> ¤È
             <filename>kernel.debug</filename> ¤ò¥Ó¥ë¥É¤·¤Þ¤¹¡£
             <filename>kernel</filename> ¤Ï <filename>/kernel</filename>
             ¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¡¢
             <filename>kernel.debug</filename> ¤Ï &man.gdb.1;
             ¤Î¥Ç¥Ð¥Ã¥°ÍÑ¥·¥ó¥Ü¥ë¾ðÊó¤ò¼è¤ê½Ð¤¹¤¿¤á¤ËÍøÍѤµ¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             ³Î¼Â¤Ë¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤ò¤È¤ë¤Ë¤Ï¡¢<filename>/etc/rc.conf</filename>
             ¤òÊÔ½¸¤·¤Æ <literal>dumpdev</literal>
             ¤ò»ÈÍѤ·¤Æ¤¤¤ë¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¤³¤¦¤¹¤ë¤È &man.rc.8; ¥¹¥¯¥ê¥×¥È¤«¤é
             &man.dumpon.8; ¥³¥Þ¥ó¥É¤¬¼Â¹Ô¤µ¤ì¡¢
             ¥¯¥é¥Ã¥·¥å¥À¥ó¥×µ¡Ç½¤¬Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¼êÆ°¤Ç &man.dumpon.8; ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¡£
             ¥Ñ¥Ë¥Ã¥¯¤Î¸å¡¢¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤Ï &man.savecore.8;
             ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¼è¤ê½Ð¤¹¤³¤È ¤¬¤Ç¤­¤Þ¤¹¡£
             <literal>dumpdev</literal> ¤¬
             <filename>/etc/rc.conf</filename> ¤ÇÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢
             &man.rc.8; ¥¹¥¯¥ê¥×¥È¤«¤é
             &man.savecore.8; ¤¬¼«Æ°Åª¤Ë¼Â¹Ô¤µ¤ì¡¢¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤ò
             <filename>/var/crash</filename> ¤ËÊݸ¤·¤Þ¤¹¡£
            </para>
 
             <note>
               <para>FreeBSD ¤Î¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤Î¥µ¥¤¥º¤Ï¡¢
                 ¤Õ¤Ä¤¦ÊªÍý¥á¥â¥ê¥µ¥¤¥º¤ÈƱ¤¸¤Ç¤¹¡£
                 ¤Ä¤Þ¤ê 64MB ¤Î¥á¥â¥ê¤òÀѤó¤Ç¤¤¤ì¤Ð¡¢
                 64MB ¤Î¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤¬À¸À®¤µ¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
                 <filename>/var/crash</filename>
                 ¤Ë½½Ê¬¤Ê¶õ¤­ÍÆÎ̤¬¤¢¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£¼êÆ°¤Ç
                 &man.savecore.8; ¤ò¼Â¹Ô¤¹¤ì¤Ð¡¢
                 ¤â¤Ã¤È¶õ¤­ÍÆÎ̤Τ¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤òÊݸ¤Ç¤­¤Þ¤¹¡£
                 <literal>options MAXMEM=(foo)</literal>
                 ¤È¤¤¤¦¹Ô¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤ËÄɲ乤뤳¤È¤Ç¡¢
                 ¥«¡¼¥Í¥ë¤Î¥á¥â¥ê»ÈÍÑÎ̤òÀ©¸Â¤Ç¤­¤Þ¤¹¡£
                 ¤¿¤È¤¨¤Ð 128MB ¤Î¥á¥â¥ê¤¬¤¢¤ë¾ì¹ç¤â¡¢
                 ¥«¡¼¥Í¥ë¤Î¥á¥â¥ê»ÈÍÑÎ̤ò 16MB
                 ¤ËÀ©¸Â¤·¡¢¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤Î¥µ¥¤¥º¤â
                 128MB ¤Ç¤Ï¤Ê¤¯ 16MB ¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
               </para>
             </note>
 
           <para>
             ¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤ò¼è¤ê½Ð¤»¤¿¤é¡¢
             °Ê²¼¤Î¤è¤¦¤Ë &man.gdb.1;
             ¤ò»È¤Ã¤Æ¥¹¥¿¥Ã¥¯¥È¥ì¡¼¥¹¤ò¤È¤ê¤Þ¤¹¡£
           </para>
 
 
           <screen>&prompt.user; <userinput>gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0</userinput>
 <prompt>(gdb)</prompt> <userinput>where</userinput></screen>
 
 
           <para>
             ɬÍפʾðÊó¤¬ 1 ²èÌ̤˼ý¤Þ¤é¤Ê¤¤¤³¤È¤â¿¤¤¤Î¤Ç¡¢¤Ç¤­¤ì¤Ð
             &man.script.1; ¤ò»È¤Ã¤Æ½ÐÎϤòµ­Ï¿¤·¤Þ¤¹¡£
             strip ¤·¤Æ¤¤¤Ê¤¤¥«¡¼¥Í¥ë¥¤¥á¡¼¥¸¤ò»È¤¦¤³¤È¤Ç¡¢
             ¤¹¤Ù¤Æ¤Î¥Ç¥Ð¥Ã¥°¥·¥ó¥Ü¥ë¤¬»²¾È¤Ç¤­¡¢
             ¥Ñ¥Ë¥Ã¥¯¤ÎȯÀ¸¤·¤¿¥«¡¼¥Í¥ë¤Î¥½¡¼¥¹¥³¡¼¥É¤Î¹Ô¤¬É½¼¨¤µ¤ì¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£
             Ä̾Àµ³Î¤Ê¥¯¥é¥Ã¥·¥å¤Ø¤Î²áÄø¤òÄÉÀפ¹¤ë¤Ë¤Ï¡¢
             ½ÐÎϤòºÇ¸å¤Î¹Ô¤«¤éµÕÊý¸þ¤ËÆɤޤʤ±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
             ¤Þ¤¿ &man.gdb.1; ¤ò»È¤Ã¤Æ¡¢
             ÊÑ¿ô¤ä¹½Â¤ÂΤÎÆâÍƤòɽ¼¨¤µ¤»¡¢
             ¥¯¥é¥Ã¥·¥å¤·¤¿»þ¤Î¥·¥¹¥Æ¥à¤Î¾õÂÖ¤òÄ´¤Ù¤é¤ì¤Þ¤¹¡£
           </para>
 
           <para>
             ¤â¤·¤¢¤Ê¤¿¤¬¥Ç¥Ð¥Ã¥°¶¸¤Ç¡¢Æ±»þ¤ËÊ̤Υ³¥ó¥Ô¥å¡¼¥¿¤òÍøÍѤǤ­¤ë´Ä¶­¤Ë¤¢¤ì¤Ð¡¢
             &man.gdb.1; ¤ò¥ê¥â¡¼¥È¥Ç¥Ð¥Ã¥°¤Ë»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
             ¥ê¥â¡¼¥È¥Ç¥Ð¥Ã¥°¤ò»È¤¦¤È¡¢¤¢¤ë¥³¥ó¥Ô¥å¡¼¥¿¾å¤Î
             &man.gdb.1; ¤ò»È¤Ã¤Æ¡¢
             Ê̤Υ³¥ó¥Ô¥å¡¼¥¿¤Î¥«¡¼¥Í¥ë¤ò¥Ç¥Ð¥Ã¥°¤Ç¤­¤Þ¤¹¡£
             ¥Ö¥ì¡¼¥¯¥Ý¥¤¥ó¥È¤ÎÀßÄê¡¢¥«¡¼¥Í¥ë¥³¡¼¥É¤Î¥¹¥Æ¥Ã¥×¼Â¹Ô¤Ê¤É¡¢
             ¤Õ¤Ä¤¦¤Î¥×¥í¥°¥é¥à¤Î¥Ç¥Ð¥Ã¥°¤ÈÊѤï¤ê¤Þ¤»¤ó¡£
             ¥³¥ó¥Ô¥å¡¼¥¿¤ò 2 Âæʤ٤ƥǥХå°¤¹¤ë¥Á¥ã¥ó¥¹¤Ë¤Ï¤Ê¤«¤Ê¤«·Ã¤Þ¤ì¤Ê¤¤¤Î¤Ç¡¢
             »ä¤Ï¤Þ¤À¥ê¥â¡¼¥È¥Ç¥Ð¥Ã¥°¤ò»î¤·¤¿¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
           </para>
 
             <note>
               <title>Bill ¤Ë¤è¤ëÄɵ­</title>
               <para>
                 DDB ¤òÍ­¸ú¤Ë¤·¤Æ¤¤¤Æ¥«¡¼¥Í¥ë¤¬¥Ç¥Ð¥Ã¥¬¤Ë
                 Íî¤Á¤¿¤é¡¢ddb ¤Î¥×¥í¥ó¥×¥È¤Ç &quot;<command>panic</command>&quot;
                 ¤ÈÆþÎϤ¹¤ì¤Ð¡¢¶¯À©Åª¤Ë¥Ñ¥Ë¥Ã¥¯¤òµ¯¤³¤·¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
                 ¥Ñ¥Ë¥Ã¥¯¤ÎÅÓÃæ¤Ç¡¢ºÆ¤Ó¥Ç¥Ð¥Ã¥¬¤ËÍî¤Á¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢
                 &quot;<command>continue</command>&quot;
                 ¤ÈÆþÎϤ¹¤ì¤Ð¡¢
                 ¥¯¥é¥Ã¥·¥å¥À¥ó¥×¤òºÇ¸å¤Þ¤Ç¼Â¹Ô¤µ¤»¤é¤ì¤Þ¤¹¡£
               </para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dlsym-failure">
           <para><function>dlsym()</function> ¤¬ ELF ¼Â¹Ô·Á¼°¤Ç¤ÏÆ°ºî¤·¤Ê¤¯¤Ê¤ê¤Þ¤¹!</para>
         </question>
 
         <answer>
           <para>
             <acronym>ELF</acronym> ¤Î¥Ä¡¼¥ëÎà¤Ï¡¢
             ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¼Â¹Ô·Á¼°¤ÎÃæ¤ËÄêµÁ¤µ¤ì¤Æ¤¤¤ë¥·¥ó¥Ü¥ë¤ò¡¢
             ¥À¥¤¥Ê¥ß¥Ã¥¯¥ê¥ó¥«¤«¤é¸«¤¨¤ë¤è¤¦¤Ë¤Ï¤·¤Þ¤»¤ó¡£
             ¤³¤Î¤¿¤á¡¢<function>dlopen(NULL, flags)</function>
             ¤ò¸Æ¤Ó½Ð¤·¤ÆÆÀ¤é¤ì¤¿¥Ï¥ó¥É¥ë¤ËÂФ·¤Æ¡¢
             <function>dlsym()</function> ¤Çõº÷¤ò¹Ô¤Ã¤Æ¤â¡¢
             ¤³¤¦¤¤¤Ã¤¿¥·¥ó¥Ü¥ë¤ò¸«¤Ä¤±¤é¤ì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤â¤·¡¢¤¢¤Ê¤¿¤¬¥×¥í¥»¥¹¤ÎÃæ¿´¤Ë¤¢¤¿¤ë¼Â¹Ô·Á¼°¤ÎÃæ¤Ë¤¢¤ë¥·¥ó¥Ü¥ë¤òõº÷¤·¤¿¤±¤ì¤Ð¡¢
             ELF ¥ê¥ó¥« (&man.ld.1;) ¤Ë
             <option>-export-dynamic</option>
             ¥ª¥×¥·¥ç¥ó¤òÉÕ¤±¤Æ¼Â¹Ô·Á¼°¤ò¥ê¥ó¥¯¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="change-kernel-address-space">
           <para>¥«¡¼¥Í¥ë¥¢¥É¥ì¥¹¶õ´Ö¤òÂ礭¤¯¤·¤¿¤ê¡¢
             ¾®¤µ¤¯¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤¿¤éÎɤ¤¤Î¤Ç¤¹¤«?</para>
         </question>
 
         <answer>
           <para>
             ¥«¡¼¥Í¥ë¥¢¥É¥ì¥¹¶õ´Ö¤Ï¡¢FreeBSD 3.X ¾å¤Ç
             256MB¡¢FreeBSD 4.X ¾å¤Ç 1GB ¤¬¥Ç¥Õ¥©¥ë¥È¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
             Éé²Ù¤Î¹â¤¤¥Í¥Ã¥È¥ï¡¼¥¯¥µ¡¼¥Ð (¤¿¤È¤¨¤ÐÂ礭¤Ê FTP¡¢HTTP ¥µ¡¼¥Ð)
             ¤ò±¿ÍѤ¹¤ë¾ì¹ç¤Ï¡¢256MB ¤Ç¤Ï­¤ê¤Ê¤¤¤³¤È¤Ëµ¤ÉÕ¤¯¤«¤âÃΤì¤Þ¤»¤ó¡£
           </para>
 
           <para>
             ¤Ç¤Ï¡¢¥¢¥É¥ì¥¹¶õ´Ö¤òÂ礭¤¯¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤¿¤éÎɤ¤¤Î¤Ç¤·¤ç¤¦¤«?
             ¤½¤ì¤Ë¤Ï¡¢Æó¤Ä¤ÎÃʳ¬¤òƧ¤ß¤Þ¤¹¡£¤Þ¤º¡¢
             ¤è¤êÂ礭¤¤¥¢¥É¥ì¥¹¶õ´Ö¤ò³ä¤êÅö¤Æ¤ë¤³¤È¤ò¥«¡¼¥Í¥ë¤ËÃΤ餻¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
             ¼¡¤Ë¡¢¥«¡¼¥Í¥ë¤Ï¥¢¥É¥ì¥¹¶õ´Ö¤ÎÀèƬ¤Ë¥í¡¼¥É¤µ¤ì¤ë¤¿¤á¡¢
             ¥¢¥É¥ì¥¹¤ÎÀèƬ¤¬Å·°æ
             (ÌõÃí:¥«¡¼¥Í¥ë¥¢¥É¥ì¥¹¶õ´Ö¤ÎºÇ²¼Ã¼¥¢¥É¥ì¥¹¤Î¤³¤È) ¤È
             ¤Ö¤Ä¤«¤ë¤³¤È¤Î¤Ê¤¤¤è¤¦¤Ë¡¢¥í¡¼¥É¥¢¥É¥ì¥¹¤òº£¤Þ¤Ç¤è¤êÄã°Ì¤ËÀßÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
           </para>
 
           <para>
             ºÇ½é¤ÎÃʳ¬¤Ï¡¢<filename>src/sys/i386/include/pmap.h</filename> ¤Ë¤¢¤ë
             <literal>NKPDE</literal> ¤ÎÃͤòÁý²Ã¤µ¤»¤ë¤³¤È¤Ç¹Ô¤Ê¤¤¤Þ¤¹¡£
             ¤³¤³¤Ë 1GB ¤Î¥¢¥É¥ì¥¹¶õ´Ö¤Ë¤¹¤ë¤¿¤á¤Ë¡¢¤É¤Î¤è¤¦¤Ë¤¹¤ì¤ÐÎɤ¤¤«¤ò¼¨¤·¤Þ¤¹¡£
           </para>
 
 <programlisting>#ifndef NKPDE
 #ifdef SMP
 #define NKPDE                   254     /* addressable number of page tables/pde's */
 #else
 #define NKPDE                   255     /* addressable number of page tables/pde's */
 #endif  /* SMP */
 #endif</programlisting>
 
           <para>
             Àµ³Î¤Ê <literal>NKPDE</literal> ¤ÎÃͤò·×»»¤¹¤ë¤Ë¤Ï¡¢
             ˾¤ß¤Î¥¢¥É¥ì¥¹¶õ´Ö¤ÎÂ礭¤µ (¥á¥¬¥Ð¥¤¥Èñ°Ì) ¤ò 4 ¤Ç³ä¤Ã¤Æ¡¢
             ¤½¤ì¤«¤éñ°ì¥×¥í¥»¥Ã¥µ (UP) ¤Ê¤é 1¡¢SMP ¤Ê¤é 2 ¤ò°ú¤­»»¤·¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <para>
             ¼¡¤ÎÃʳ¬¤ò¹Ô¤Ê¤¦¤Ë¤Ï¡¢¥í¡¼¥É¥¢¥É¥ì¥¹¤òÀµ³Î¤Ë·×»»¤¹¤ë¤³¤È¤¬É¬ÍפǤ¹¡£
             ñ½ã¤Ë¡¢¥¢¥É¥ì¥¹¶õ´Ö¤ÎÂ礭¤µ
             (¥Ð¥¤¥Èñ°Ì) ¤ò 0x100100000 ¤«¤é°ú¤­»»¤·¤Æ¤¯¤À¤µ¤¤¡£
             1GB ¥¢¥É¥ì¥¹¶õ´Ö¤Î¾ì¹ç¡¢¤½¤Î·ë²Ì¤Ï 0xc0100000 ¤Ë¤Ê¤ê¤Þ¤¹¡£
             ¤½¤·¤Æ¡¢<filename>src/sys/i386/conf/Makefile.i386</filename> ¤Ë¤¢¤ë
             <symbol>LOAD_ADDRESS</symbol> ¤Ë¡¢º£·×»»¤·¤¿ÃͤòÆþ¤ì¤Þ¤¹¡£¤Þ¤¿¡¢¼¡¤Î¤è¤¦¤Ë
             <filename>src/sys/i386/conf/kernel.script</filename>
             ¤Î¥»¥¯¥·¥ç¥ó¤Î»Ï¤á¤ÎÊý¤Ë¤¢¤ë¥í¥±¡¼¥·¥ç¥ó¥«¥¦¥ó¥¿¤Ë¤âƱ¤¸ÃͤòÆþ¤ì¤Æ¤¯¤À¤µ¤¤¡£
           </para>
 
           <programlisting>OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386")
 OUTPUT_ARCH(i386)
 ENTRY(btext)
 SEARCH_DIR(/usr/lib); SEARCH_DIR(/usr/obj/elf/home/src/tmp/usr/i386-unknown-freebsdelf/lib);
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
   . = 0xc0100000 + SIZEOF_HEADERS;
   .interp     : { *(.interp)    }</programlisting>
 
           <para>
             ¤½¤ì¤¬´°Î»¤·¤¿¤é¡¢<command>config</command> ¤·Ä¾¤·¤Æ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£
             ¤ª¤½¤é¤¯¡¢&man.ps.1;¡¢&man.top.1;
             ¤Ê¤É¤ËÉÔ¶ñ¹ç¤¬½Ð¤ë¤Ç¤·¤ç¤¦¡£
             ¤½¤ì¤é¤òÀµ¾ï¤Ë¤¹¤ë¤¿¤á¤Ë¡¢<command>make world</command>
             (¤â¤·¤¯¤Ï¡¢Êѹ¹¤·¤¿ <filename>pmap.h</filename> ¤ò
             <filename>/usr/include/vm/</filename> ¤Ë¥³¥Ô¡¼¤·¤¿¸å¤Ë¡¢
             <filename>libkvm</filename>¡¢
             <command>ps</command> ¤ª¤è¤Ó <command>top</command>
             ¤ò¼êÆ°¤ÇºÆ¹½ÃÛ¤¹¤ë¤³¤È) ¤ò¹Ô¤Ê¤¦¤Ù¤­¤Ç¤¹¡£
           </para>
 
             <note>
               <para>¥«¡¼¥Í¥ë¥¢¥É¥ì¥¹¶õ´Ö¤ÎÂ礭¤µ¤Ï¡¢4MB ¤ÎÇÜ¿ô¤Ç¤¢¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
             </note>
 
             <note>
               <title>&a.dg; »á¤Ë¤è¤ëÊä­</title>
               <para>
                 ¥«¡¼¥Í¥ë¥¢¥É¥ì¥¹¶õ´Ö¤Ï 2 ¤Î¾è¿ô¤Ç¤¢¤ëɬÍפ¬¤¢¤ë¤È»×¤¤¤Þ¤¹¤¬¡¢
                 ¤½¤ì¤¬³Î¤«¤Ê¤³¤È¤«¤É¤¦¤«¤Ï¤Ï¤Ã¤­¤ê¤·¤Æ¤¤¤Þ¤»¤ó¡£
                 ÀΤε¯Æ°¥³¡¼¥É¤Ë¤Ï¡¢Îɤ¯¹â°Ì¥¢¥É¥ì¥¹¥Ó¥Ã¥È¤Î¥È¥ê¥Ã¥¯¤¬»È¤ï¤ì¤Æ¤¤¤¿¤¿¤á¡¢
                 ¾¯¤Ê¤¯¤È¤â 256MB ¤ÎγÅ٤Ǥ¢¤ë¤³¤È¤¬ÁÛÄꤵ¤ì¤Æ¤¤¤¿¤È»×¤¤¤Þ¤¹¡£
               </para>
             </note>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="acknowledgments">
     <title>¼Õ¼­</title>
 
     <para>
       <emphasis>Ìõ:
         &a.jp.y-koga;¡¢
         1997 ǯ 11 ·î 10 Æü</emphasis>
     </para>
 
     <blockquote>
       <attribution>FreeBSD Core Team</attribution>
       <para>
         ¤³¤Î FAQ ¤Ë¤Ä¤¤¤ÆÌäÂê¤ò¸«¤Ä¤±¤¿¤ê¡¢²¿¤«ÅÐÏ¿¤·¤¿¤¤¾ì¹ç¤Ï¡¢
         &a.faq; ¤Þ¤Ç¥á¡¼¥ë¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
         ¥Õ¥£¡¼¥É¥Ð¥Ã¥¯¤·¤Æ¤¯¤ì¤ë¤ß¤Ê¤µ¤ó¤Ë¤Ï´¶¼Õ´¶¼Õ¤Ê¤Î¤Ç¤¹¡£
         ¤ß¤Ê¤µ¤ó¤Ë¼êÅÁ¤Ã¤Æ¤â¤é¤ï¤Ê¤¤¤È¤³¤Î FAQ ¤Ï¤è¤¯¤Ê¤ê¤Þ¤»¤ó¤«¤é!
       </para>
     </blockquote>
 
       <variablelist>
         <varlistentry><term>&a.jkh;</term>
           <listitem>
             <para>¤¿¤Þ¤Ëµ¯¤³¤¹ FAQ ¤ÎʤÙÂؤ¨¤ä¹¹¿·¤Îȯºî</para>
           </listitem>
         </varlistentry>
 
         <varlistentry><term>&a.dwhite;</term>
           <listitem>
             <para>freebsd-questions ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ç¤ÎµÁ̳¤òĶ¤¨¤¿¥µ¡¼¥Ó¥¹</para>
           </listitem>
         </varlistentry>
 
         <varlistentry><term>&a.joerg;</term>
           <listitem>
             <para>Usenet (NetNews) ¤Ç¤ÎµÁ̳¤òĶ¤¨¤¿¥µ¡¼¥Ó¥¹</para>
           </listitem>
         </varlistentry>
 
         <varlistentry><term>&a.wollman;</term>
           <listitem>
             <para>¥Í¥Ã¥È¥ï¡¼¥¯Àá¤Î¼¹É®¤Èʸ½ñÀ°·Á</para>
           </listitem>
         </varlistentry>
 
         <varlistentry><term>Jim Lowe</term>
           <listitem>
             <para>¥Þ¥ë¥Á¥­¥ã¥¹¥È¤Ë¤Ä¤¤¤Æ</para>
           </listitem>
         </varlistentry>
 
         <varlistentry><term>&a.pds;</term>
           <listitem>
             <para>FreeBSD FAQ ¥¿¥¤¥Ô¥ó¥°µ¡³£ÅÛÎì</para>
           </listitem>
         </varlistentry>
 
         <varlistentry><term>FreeBSD ¥Á¡¼¥à</term>
           <listitem>
             <para>ÉÔÊ¿¤ò¸À¤Ã¤¿¤ê¡¢¤¦¤á¤¤¤¿¤ê¡¢¾ðÊóÄ󶡤·¤Æ¤¯¤ì¤¿¤ê</para>
           </listitem>
         </varlistentry>
       </variablelist>
 
     <para>
       ¤¢¤È¡¢È´¤±¤Æ¤·¤Þ¤Ã¤¿Â¾¤ÎÊý¡¹¤ËÂФ·¤Æ¡¢¼Õºá¤È¿´¤«¤é¤Î´¶¼Õ¤òÊû¤²¤Þ¤¹!
     </para>
   </chapter>
 
   <chapter id="jcontrib">
     <title>FreeBSD FAQ ÆüËܸ첽¤Ë¤Ä¤¤¤Æ</title>
 
     <para>
       FreeBSD ÆüËܸì¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È¤Ï¡¢
       FreeBSD ´Ø·¸¤ÎÆüËܸìʸ½ñ¤¬¾¯¤Ê¤¤¤³¤È¤òò¤¤¤¿¿ô¿Í¤Î
       FreeBSD ¥æ¡¼¥¶¤ÎÄ󾧤ˤè¤Ã¤Æ 1996 ǯ 2 ·î 26 Æü¤Ë¥¹¥¿¡¼¥È¤·¡¢
       FreeBSD ÆüËܸì¥Ï¥ó¥É¥Ö¥Ã¥¯¤ÎºîÀ®¤ò¤Ï¤¸¤á¤È¤·¤¿³èÆ°¤ò¹Ô¤Ê¤Ã¤Æ¤­¤Þ¤·¤¿¡£
       FreeBSD FAQ ¤ÎÆüËܸ첽¤Ë¤Ä¤¤¤Æ¤Ï¥ª¥ê¥¸¥Ê¥ë¤ÎËÝÌõºî¶È¤À¤±¤Ç¤Ê¤¯¡¢
       ÆüËܹñÆâ¤Ë¸ÇÍ­¤ÎÏÃÂê¤Ë¤Ä¤¤¤Æ¤â¹­¤¯¾ðÊó¤ò½¸¤á¡¢
       ÆüËܤΠFreeBSD ¥æ¡¼¥¶¤Ë¤È¤Ã¤Æ¿¿¤ËÍ­±×¤Ê¥É¥­¥å¥á¥ó¥È¤òÄ󶡤·¤è¤¦¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£
       ¥ª¥ê¥¸¥Ê¥ë¤Î FAQ ¤ÏÆüËè¤Ë¹¹¿·¤µ¤ì¤Æ¤ª¤ê¡¢
       »ä¤¿¤Á¤â¤Þ¤¿¤³¤ì¤ËÄɤ¤ÉÕ¤¯¤¿¤á¤Ëºî¶È¤ò³¤±¤Æ¤¤¤­¤Þ¤¹¡£¤â¤Á¤í¤ó¡¢¿·¤·¤¤¥á¥ó¥Ð¤âÂç´¿·Þ¤Ç¤¹¡£
       ÆüËܸìËÝÌõÈǤˤĤ¤¤Æ¡¢²¿¤«¤ªµ¤¤Å¤­¤ÎÅÀ¤¬¤¢¤ê¤Þ¤·¤¿¤é¡¢
       &a.jp.doc-jp;
       ¤Þ¤Ç¤´Ï¢Íí¤¯¤À¤µ¤¤¡£
       ¤Þ¤¿¡¢¤â¤·»ä¤¿¤Á¤Îºî¶È¤ò¼êÅÁ¤Ã¤Æ¤¯¤ì¤ë¤Ê¤é¡¢
       <ulink url="http://www.jp.FreeBSD.org/doc-jp/">FreeBSD
         ÆüËܸì¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È¤Î¥Ú¡¼¥¸</ulink>¤ò¤´Í÷¤Î¾å¡¢À§È󻲲䷤Ƥ¯¤À¤µ¤¤¡£
     </para>
 
     <bridgehead renderas="sect2">ËÝÌõ¼Ô (¸Þ½½²»½ç)</bridgehead>
 
     <itemizedlist>
       <listitem><para>&a.jp.arimura;</para></listitem>
       <listitem><para>°ìµÜ μ <email>ryo@azusa.shinshu-u.ac.jp</email></para></listitem>
       <listitem><para>&a.iwasaki;</para></listitem>
       <listitem><para>&a.jp.yoshiaki;</para></listitem>
       <listitem><para>&a.kuriyama;</para></listitem>
       <listitem><para>&a.jp.y-koga;</para></listitem>
       <listitem><para>&a.motoyuki;</para></listitem>
       <listitem><para>&a.jp.sugimura;</para></listitem>
       <listitem><para>&a.jp.nakai;</para></listitem>
       <listitem><para>¤Ë¤·¤« <email>nishika@cheerful.com</email></para></listitem>
       <listitem><para>&a.hanai;</para></listitem>
       <listitem><para>&a.jp.kiroh;</para></listitem>
       <listitem><para>&a.jp.shou;</para></listitem>
       <listitem><para>Ê¡´Ö ¹¯¹° <email>yasuf@big.or.jp</email></para></listitem>
       <listitem><para>&a.jp.mrt;</para></listitem>
       <listitem><para>»³²¼ ½ß <email>junkun@esys.tsukuba.ac.jp</email></para></listitem>
     </itemizedlist>
 
     <bridgehead renderas="sect2">ººÆÉ¼Ô (¸Þ½½²»½ç)</bridgehead>
 
     <itemizedlist>
       <listitem><para>&a.asami;</para></listitem>
       <listitem><para>&a.iwasaki;</para></listitem>
       <listitem><para>&a.jp.yoshiaki;</para></listitem>
       <listitem><para>Â綶 ·ò <email>ohashi@mickey.ai.kyutech.ac.jp</email></para></listitem>
       <listitem><para>&a.kuriyama;</para></listitem>
       <listitem><para>&a.motoyuki;</para></listitem>
       <listitem><para>&a.jp.saeki;</para></listitem>
       <listitem><para>&a.jp.sugimura;</para></listitem>
       <listitem><para>&a.hanai;</para></listitem>
       <listitem><para>&a.jp.nao;</para></listitem>
       <listitem><para>&a.jp.kiroh;</para></listitem>
       <listitem><para>&a.jp.hino;</para></listitem>
       <listitem><para>ÛØ»³  Âî <email>shiyama@intercity.or.jp</email></para></listitem>
       <listitem><para>&a.jp.shou;</para></listitem>
       <listitem><para>&a.jp.mrt;</para></listitem>
       <listitem><para>¼ã°æ  µ×»Ë <email>earth@hokuto7.or.jp</email></para></listitem>
     </itemizedlist>
 
     <bridgehead renderas="sect2">ºî¶È´Ä¶­À°È÷ (¸Þ½½²»½ç)</bridgehead>
 
     <itemizedlist>
       <listitem><para>°ìµÜ μ <email>ryo@azusa.shinshu-u.ac.jp</email></para></listitem>
       <listitem><para>&a.jp.iwasaki;</para></listitem>
       <listitem><para>&a.jp.simokawa;</para></listitem>
       <listitem><para>ÎëÌÚ  ½¨¹¬ <email>hideyuki@jp.FreeBSD.org</email></para></listitem>
     </itemizedlist>
 
   </chapter>
 
   <bibliography id="bibliography">
     <title>Í­ÍѤʽñÀÒ</title>
 
     <biblioentry id="biblio-44sysman">
       <biblioset relation="book">
         <title>4.4BSD System Manager's Manual</title>
 
         <corpauthor>Computer Systems Research Group, University of
           California, Berkeley</corpauthor>
 
         <publisher>
           <publishername>O'Reilly and Associates</publishername>
         </publisher>
 
         <edition>1st Edition</edition>
 
         <pubdate>June 1994</pubdate>
 
         <pagenums>804 pages</pagenums>
 
         <isbn>ISBN 1-56592-080-5</isbn>
       </biblioset>
     </biblioentry>
 
     <biblioentry id="biblio-44userman">
       <biblioset relation="book">
         <title>4.4BSD User's Reference Manual</title>
         <corpauthor>Computer Systems Research Group, University of
           California, Berkeley</corpauthor>
 
         <publisher>
           <publishername>O'Reilly and Associates</publishername>
         </publisher>
 
         <edition>1st Edition</edition>
 
         <pubdate>June 1994</pubdate>
 
         <pagenums>905 pages</pagenums>
 
         <isbn>ISBN 1-56592-075-9</isbn>
       </biblioset>
     </biblioentry>
 
     <biblioentry id="biblio-44suppman">
       <biblioset relation="book">
         <title>4.4BSD User's Supplementary Documents</title>
 
         <corpauthor>Computer Systems Research Group, University of
           California, Berkeley</corpauthor>
 
         <publisher>
           <publishername>O'Reilly and Associates</publishername>
         </publisher>
 
         <edition>1st Edition</edition>
 
        <pubdate>June 1994</pubdate>
 
         <pagenums>712 pages</pagenums>
 
         <isbn>ISBN 1-56592-076-7</isbn>
       </biblioset>
     </biblioentry>
 
     <biblioentry id="biblio-44progman">
       <biblioset relation="book">
         <title>4.4BSD Programmer's Reference Manual</title>
 
         <corpauthor>Computer Systems Research Group, University of
          California, Berkeley</corpauthor>
 
         <publisher>
           <publishername>O'Reilly and Associates</publishername>
         </publisher>
 
         <edition>1st Edition</edition>
         <pubdate>June 1994</pubdate>
 
         <pagenums>866 pages</pagenums>
 
         <isbn>ISBN 1-56592-078-3</isbn>
       </biblioset>
     </biblioentry>
 
     <biblioentry id="biblio-44progsupp">
       <biblioset relation="book">
         <title>4.4BSD Programmer's Supplementary Documents</title>
 
         <corpauthor>Computer Systems Research Group, University of
           California, Berkeley</corpauthor>
 
         <publisher>
           <publishername>O'Reilly and Associates</publishername>
         </publisher>
 
         <edition>1st Edition</edition>
 
         <pubdate>June 1994</pubdate>
 
         <pagenums>596 pages</pagenums>
 
         <isbn>ISBN 1-56592-079-1</isbn>
       </biblioset>
     </biblioentry>
 
     <biblioentry id="biblio-44kernel">
       <biblioset relation="book">
         <title>The Design and Implementation of the 4.4BSD Operating System</title>
 
         <authorgroup>
           <author>
             <firstname>M. K.</firstname>
 
             <surname>McKusick</surname>
           </author>
 
           <author>
             <firstname>Kirk</firstname>
 
             <surname>Marshall</surname>
           </author>
 
           <author>
             <firstname>Keith</firstname>
 
             <surname>Bostic</surname>
           </author>
 
           <author>
             <firstname>Michael J</firstname>
 
             <surname>Karels</surname>
           </author>
 
           <author>
             <firstname>John</firstname>
 
             <surname>Quarterman</surname>
           </author>
         </authorgroup>
 
         <publisher>
           <publishername>Addison-Wesley</publishername>
 
           <address>
             <city>Reading</city>
             <state>MA</state>
           </address>
         </publisher>
 
         <pubdate>1996</pubdate>
 
         <isbn>ISBN 0-201-54979-4</isbn>
       </biblioset>
     </biblioentry>
 
     <biblioentry id="biblio-nemeth3rd">
       <biblioset relation="book">
         <title>Unix System Administration Handbook</title>
 
         <authorgroup>
           <author>
             <firstname>Evi</firstname>
 
             <surname>Nemeth</surname>
           </author>
 
           <author>
             <firstname>Garth</firstname>
 
             <surname>Snyder</surname>
           </author>
 
           <author>
             <firstname>Scott</firstname>
 
             <surname>Seebass</surname>
           </author>
 
           <author>
             <firstname>Trent R.</firstname>
 
             <surname>Hein</surname>
           </author>
 
           <author>
             <firstname>John</firstname>
 
             <surname>Quarterman</surname>
           </author>
         </authorgroup>
 
         <publisher>
           <publishername>Prentice-Hall</publishername>
         </publisher>
 
         <edition>3rd edition</edition>
 
         <pubdate>2000</pubdate>
 
         <isbn>ISBN 0-13-020601-6</isbn>
       </biblioset>
     </biblioentry>
 
     <biblioentry id="lehey3rd">
       <biblioset relation="book">
         <title>The Complete FreeBSD</title>
 
         <author>
           <firstname>Greg</firstname>
 
           <surname>Lehey</surname>
         </author>
 
         <publisher>
           <publishername>Walnut Creek</publishername>
         </publisher>
 
         <edition>3rd edition</edition>
 
         <pubdate>June 1999</pubdate>
 
         <pagenums>773 pages</pagenums>
 
         <isbn>ISBN 1-57176-246-9</isbn>
       </biblioset>
     </biblioentry>
 
     <biblioentry id="biblio-mckusick-1">
       <abbrev>McKusick et al, 1994</abbrev>
 
       <biblioset relation="manual">
         <title>Berkeley Software Architecture Manual, 4.4BSD
           Edition</title>
 
         <authorgroup>
           <author>
             <firstname>M. K.</firstname>
 
             <surname>McKusick</surname>
           </author>
 
           <author>
             <firstname>M. J.</firstname>
 
             <surname>Karels</surname>
           </author>
 
           <author>
             <firstname>S. J.</firstname>
 
             <surname>Leffler</surname>
           </author>
 
           <author>
             <firstname>W. N.</firstname>
 
             <surname>Joy</surname>
           </author>
 
           <author>
             <firstname>R. S.</firstname>
 
             <surname>Faber</surname>
           </author>
         </authorgroup>
 
         <pagenums>5:1-42</pagenums>
       </biblioset>
     </biblioentry>
   </bibliography>
 </book>
diff --git a/ja_JP.eucJP/books/handbook/disks/chapter.xml b/ja_JP.eucJP/books/handbook/disks/chapter.xml
index 3b2928c5eb..f92e6884be 100644
--- a/ja_JP.eucJP/books/handbook/disks/chapter.xml
+++ b/ja_JP.eucJP/books/handbook/disks/chapter.xml
@@ -1,3340 +1,3333 @@
 <?xml version="1.0" encoding="euc-jp"?>
 <!--
      The FreeBSD Documentation Project
      The FreeBSD Japanese Documentation Project
 
      Original revision: 1.190
      $FreeBSD$
 -->
 
 <chapter id="disks">
   <title>¥¹¥È¥ì¡¼¥¸</title>
 
   <sect1 id="disks-synopsis">
     <title>¤³¤Î¾Ï¤Ç¤Ï</title>
 
     <para>¤³¤Î¾Ï¤Ç¤Ï¡¢FreeBSD ¤Ë¤ª¤±¤ë¥Ç¥£¥¹¥¯¤Î»ÈÍÑÊýË¡¤òÀâÌÀ¤·¤Þ¤¹¡£
       ¤³¤ì¤Ë¤Ï¥á¥â¥ê¥Ç¥£¥¹¥¯¡¢¥Í¥Ã¥È¥ï¡¼¥¯¤ËÀܳ¤µ¤ì¤¿¥Ç¥£¥¹¥¯¡¢
       ¤ª¤è¤Óɸ½àŪ¤Ê SCSI/IDE µ­²±¥Ç¥Ð¥¤¥¹¤¬´Þ¤Þ¤ì¤Þ¤¹¡£</para>
 
     <para>¤³¤Î¾Ï¤Ç¤Ï¡¢°Ê²¼¤ÎʬÌî¤Ë¤Ä¤¤¤ÆÀâÌÀ¤·¤Þ¤¹¡£</para>
 
     <itemizedlist>
       <listitem><para>ʪÍý¥Ç¥£¥¹¥¯¾å¤Î¥Ç¡¼¥¿¹½À®
 	¤Ë¤Ä¤¤¤Æµ­½Ò¤¹¤ë¤¿¤á¤Ë FreeBSD ¤¬»ÈÍѤ¹¤ëÍѸì
 	(¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ª¤è¤Ó¥¹¥é¥¤¥¹) </para>
       </listitem>
       <listitem><para>¥·¥¹¥Æ¥à¤Ë¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤òÄɲ乤ëÊýË¡</para>
       </listitem>
       <listitem><para>¥á¥â¥ê¥Ç¥£¥¹¥¯¤Î¤è¤¦¤Ê²¾ÁÛ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÀßÄꤹ¤ëÊýË¡</para></listitem>
       <listitem>
 	<para>»ÈÍѤǤ­¤ë¥Ç¥£¥¹¥¯ÍÆÎ̤òÀ©¸Â¤¹¤ë¤¿¤á¤Ë¥¯¥©¡¼¥¿¤òÀßÄꤹ¤ëÊýË¡</para>
       </listitem>
       <listitem>
 	<para>¹¶·â¼Ô¤«¤éÊݸ¤ë¤¿¤á¤Ë¥Ç¥£¥¹¥¯¤ò°Å¹æ²½¤¹¤ëÊýË¡</para>
       </listitem>
       <listitem>
 	<para>FreeBSD ¤Ç CD ¤ä DVD ¤òºîÀ®¤¹¤ëÊýË¡</para>
       </listitem>
       <listitem>
 	<para>¥Ð¥Ã¥¯¥¢¥Ã¥×¤Î¤¿¤á¤Î¤µ¤Þ¤¶¤Þ¤Êµ­²±¥á¥Ç¥£¥¢¥ª¥×¥·¥ç¥ó</para>
       </listitem>
       <listitem>
 	<para>FreeBSD ¤ÇÍøÍѤǤ­¤ë¥Ð¥Ã¥¯¥¢¥Ã¥×¥×¥í¥°¥é¥à¤Î»ÈÍÑÊýË¡</para>
       </listitem>
       <listitem>
 	<para>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ëÊýË¡</para>
       </listitem>
       <listitem>
 	<para>¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤È¤Ï²¿¤«¡¢¤½¤·¤Æ¤½¤ì¤ò¸ú²ÌŪ¤Ë»ÈÍѤ¹¤ëÊýË¡</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="disks-naming">
     <title>¥Ç¥Ð¥¤¥¹Ì¾</title>
 
     <para>°Ê²¼¤Ï¡¢FreeBSD ¤ÇÂбþ¤·¤Æ¤¤¤ëʪÍýµ­²±¥Ç¥Ð¥¤¥¹¤È¤½¤ì¤ËÂбþ¤¹¤ë¥Ç¥Ð¥¤¥¹Ì¾¤Î¥ê¥¹¥È¤Ç¤¹¡£</para>
 
     <table id="disk-naming-physical-table">
       <title>ʪÍý¥Ç¥£¥¹¥¯¤Ø¤Î̾Á°ÉÕ¤±</title>
 
       <tgroup cols="2">
 	<thead>
 	  <row>
 	    <entry>¥É¥é¥¤¥Ö¤Î¼ïÎà</entry>
 	    <entry>¥É¥é¥¤¥Ö¤Î¥Ç¥Ð¥¤¥¹Ì¾</entry>
 	  </row>
 	</thead>
 	<tbody>
 	  <row>
 	    <entry>IDE ¥Ï¡¼¥É¥É¥é¥¤¥Ö</entry>
 	    <entry><literal>ad</literal></entry>
 	  </row>
 	  <row>
 	    <entry>IDE CD-ROM ¥É¥é¥¤¥Ö</entry>
 	    <entry><literal>acd</literal></entry>
 	  </row>
 	  <row>
 	    <entry>SCSI ¥Ï¡¼¥É¥É¥é¥¤¥Ö¤ª¤è¤Ó USB ÂçÍÆÎ̵­²±¥Ç¥Ð¥¤¥¹</entry>
 	    <entry><literal>da</literal></entry>
 	  </row>
 	  <row>
 	    <entry>SCSI CD-ROM ¥É¥é¥¤¥Ö</entry>
 	    <entry><literal>cd</literal></entry>
 	  </row>
 	  <row>
 	    <entry>¤½¤Î¾¤ÎÈóɸ½àŪ CD-ROM ¥É¥é¥¤¥Ö</entry>
 	    <entry>¥ß¥Ä¥ß CD-ROM ¤Ï <literal>mcd</literal>,
 	      Sony CD-ROM ¤Ï <literal>scd</literal>,
 	      ¾¾²¼/¥Ñ¥Ê¥½¥Ë¥Ã¥¯ CD-ROM ¤Ï <literal>matcd</literal>
-	      <footnote>
-		<para>&man.matcd.4; ¥É¥é¥¤¥Ð¤Ï 2002 ǯ 10 ·î 5 Æü¤Ë
-		  FreeBSD&nbsp;4.X ¥Ö¥é¥ó¥Á¤«¤éºï½ü¤µ¤ì¤Þ¤·¤¿¡£
-		  ¤Þ¤¿¡¢FreeBSD&nbsp;5.0 ¤ª¤è¤Ó 5.1 ¥ê¥ê¡¼¥¹¤Ë¤Ï¸ºß¤·¤Þ¤»¤ó¤¬¡¢
-		  2003 ǯ 6 ·î 16 Æü¤Ë
-		  FreeBSD&nbsp;5.X ¥Ö¥é¥ó¥Á¤ËÉüµ¢¤·¤Þ¤·¤¿¡£</para>
-	      </footnote>
 	    </entry>
 	  </row>
 	  <row>
 	    <entry>¥Õ¥í¥Ã¥Ô¡¼¥É¥é¥¤¥Ö</entry>
 	    <entry><literal>fd</literal></entry>
 	  </row>
 	  <row>
 	    <entry>SCSI ¥Æ¡¼¥×¥É¥é¥¤¥Ö</entry>
 	    <entry><literal>sa</literal></entry>
 	  </row>
 	  <row>
 	    <entry>IDE ¥Æ¡¼¥×¥É¥é¥¤¥Ö</entry>
 	    <entry><literal>ast</literal></entry>
 	  </row>
 	  <row>
 	    <entry>¥Õ¥é¥Ã¥·¥å¥É¥é¥¤¥Ö</entry>
 	    <entry>&diskonchip; ¥Õ¥é¥Ã¥·¥å¥Ç¥Ð¥¤¥¹¤Ï
 	      <literal>fla</literal></entry>
 	  </row>
 	  <row>
 	    <entry>RAID ¥É¥é¥¤¥Ö</entry>
 	    <entry>&adaptec; AdvancedRAID ¤Ï <literal>aacd</literal>, &mylex;
 	      ¤Ï <literal>mlxd</literal> ¤ª¤è¤Ó <literal>mlyd</literal>,
 	      AMI &megaraid; ¤Ï <literal>amrd</literal>,
 	      Compaq Smart RAID ¤Ï <literal>idad</literal>,
 	      &tm.3ware; RAID ¤Ï<literal>twed</literal></entry>
 	  </row>
 	</tbody>
       </tgroup>
     </table>
   </sect1>
 
   <sect1 id="disks-adding">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>David</firstname>
 	  <surname>O'Brien</surname>
 	  <contrib>¸¶ºî: </contrib>
 	</author>
       </authorgroup>
       <!-- 26 Apr 1998 -->
     </sect1info>
 
     <title>¥Ç¥£¥¹¥¯¤ÎÄɲÃ</title>
 
     <indexterm>
       <primary>¥Ç¥£¥¹¥¯</primary>
       <secondary>ÄɲÃ</secondary>
     </indexterm>
 
     <para>¸½ºß°ì¤Ä¤·¤«¥É¥é¥¤¥Ö¤¬¤Ê¤¤·×»»µ¡¤Ë¿·¤·¤¯ SCSI
       ¥Ç¥£¥¹¥¯¤òÄɲä·¤¿¤¤¤È¤·¤Þ¤·¤ç¤¦¡£¤Þ¤º¥³¥ó¥Ô¥å¡¼¥¿¤ÎÅŸ»¤òÀڤꡢ
       ¥³¥ó¥Ô¥å¡¼¥¿¤ä¥³¥ó¥È¥í¡¼¥é¡¢
       ¥É¥é¥¤¥Ö¤ÎÀ½Â¤¸µ¤ÎÀâÌÀ½ñ¤Ë½¾¤Ã¤Æ¥É¥é¥¤¥Ö¤ò¼è¤êÉÕ¤±¤Þ¤¹¡£
       ¤³¤Î¤¢¤¿¤ê¤Î¼ê½ç¤ÏÈó¾ï¤Ë¿´ô¤Ë¤ï¤¿¤ë¤¿¤á¡¢
       ¾ÜºÙ¤Ï¤³¤Îʸ½ñ¤ÎÈϰϳ°¤Ç¤¹¡£</para>
 
     <para><username>root</username> ¥æ¡¼¥¶¤Ç¥í¥°¥¤¥ó¤·¤Þ¤¹¡£
       ¥É¥é¥¤¥Ö¤Î¼è¤êÉÕ¤±¸å¤Ï <filename>/var/run/dmesg.boot</filename>
       ¤òÄ´¤Ù¤Æ¿·¤·¤¤¥Ç¥£¥¹¥¯¤¬¸«¤Ä¤«¤Ã¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤ª¤­¤Þ¤¹¡£
       ¤³¤ÎÎã¤Ç¤Ï¡¢¿·¤·¤¯ÉÕ¤±¤¿¥É¥é¥¤¥Ö¤Ï <filename>da1</filename> ¤Ç¡¢
       ²æ¡¹¤Ï¤½¤ì¤ò <filename>/1</filename> ¤Ë¥Þ¥¦¥ó¥È¤·¤¿¤¤¤È¤·¤Þ¤·¤ç¤¦
       (¤â¤· IDE ¥É¥é¥¤¥Ö¤òÉÕ¤±¤è¤¦¤È¤·¤Æ¤¤¤ë¤Î¤Ê¤é¡¢¥Ç¥Ð¥¤¥¹Ì¾¤Ï
       4.0 °ÊÁ°¤Î¥·¥¹¥Æ¥à¤Ç¤Ï <filename>wd1</filename>, ¤Û¤È¤ó¤É¤Î 4.x
       ¥·¥¹¥Æ¥à¤Ç¤Ï <filename>ad1</filename> ¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦)¡£</para>
 
     <indexterm><primary>¥Ñ¡¼¥Æ¥£¥·¥ç¥ó</primary></indexterm>
     <indexterm><primary>¥¹¥é¥¤¥¹</primary></indexterm>
     <indexterm><primary><command>fdisk</command></primary></indexterm>
 
     <para>FreeBSD ¤Ï IBM-PC ¸ß´¹¤Î¥³¥ó¥Ô¥å¡¼¥¿¤ÇÆ°¤¯¤¿¤á¡¢
       PC BIOS ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¹Íθ¤ËÆþ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
       ¤³¤ì¤Ï½¾Íè¤Î BSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤È¤Ï°Û¤Ê¤ê¤Þ¤¹¡£PC ¥Ç¥£¥¹¥¯¤Ï 4 ¤Ä¤Þ¤Ç¤Î
       BIOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥¨¥ó¥È¥ê¤ò»ý¤Ä¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
       ¤â¤·¤½¤Î¥Ç¥£¥¹¥¯¤òËÜÅö¤Ë FreeBSD ÀìÍѤˤ·¤¿¤¤¾ì¹ç¤Ë¤Ï
       <emphasis>ÀìÍÑ</emphasis> ¥â¡¼¥É¤ÇÍѤ¤¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
       ¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢FreeBSD ¤Ï PC BIOS
       ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¤É¤ì¤«°ì¤Ä¤ÎÃæ¤ËÆþ¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
       FreeBSD ¤Ç¤Ï¡¢½¾Íè¤Î BSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Èº®Í𤷤ʤ¤¤è¤¦¤Ë
       PC BIOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¤³¤È¤ò<emphasis>¥¹¥é¥¤¥¹</emphasis>¤È¸Æ¤Ó¤Þ¤¹¡£
       ¤Þ¤¿¡¢Ê̤ΠOS ¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤¿¥³¥ó¥Ô¥å¡¼¥¿¤Ç»È¤ï¤ì¤Æ¤¤¤¿¤¬
       FreeBSD ÀìÍѤˤ¹¤ë¥Ç¥£¥¹¥¯¾å¤Ç¤â¥¹¥é¥¤¥¹¤òÍѤ¤¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
       ¤³¤ì¤Ï¡¢Â¾¤Î OS ¤Î <command>fdisk</command>
       ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤òº®Í𤵤»¤Ê¤¤¤¿¤á¤Ç¤¹¡£</para>
 
     <para>¥¹¥é¥¤¥¹¤Î¾ì¹ç¡¢¥É¥é¥¤¥Ö¤Ï <filename>/dev/da1s1e</filename>
       ¤È¤·¤Æ²Ã¤¨¤é¤ì¤ë¤Ç¤·¤ç¤¦¡£¤³¤ì¤Ï¡¢SCSI ¥Ç¥£¥¹¥¯¤Ç¥æ¥Ë¥Ã¥ÈÈÖ¹æ¤Ï 1
       (Æó¤Ä¤á¤Î SCSI ¥Ç¥£¥¹¥¯), ¥¹¥é¥¤¥¹¤Ï 1 (PC BIOS ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤¬ 1) ¤Ç
       BSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó <filename>e</filename>, ¤ÈÆɤߤޤ¹¡£
       ÀìÍѥǥ£¥¹¥¯¤Î¾ì¹ç¤À¤Èñ½ã¤Ë <filename>/dev/da1e</filename>
       ¤È¤·¤Æ²Ã¤¨¤é¤ì¤ë¤Ç¤·¤ç¤¦¡£</para>
 
     <sect2>
       <title>&man.sysinstall.8; ¤ÎÍøÍÑ</title>
 
       <indexterm>
 	<primary><application>sysinstall</application></primary>
 	<secondary>¥Ç¥£¥¹¥¯¤ÎÄɲÃ</secondary>
       </indexterm>
       <indexterm><primary>su</primary></indexterm>
 
       <procedure>
 	<step>
 	  <title><application>sysinstall</application> ¤ÎÁàºî</title>
 
 	  <para><command>sysinstall</command> ¤Î»È¤¤°×¤¤¥á¥Ë¥å¡¼¤òÍøÍѤ·¤Æ¡¢
 	    ¿·¤·¤¤¥Ç¥£¥¹¥¯¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥óʬ¤±¤ä¥é¥Ù¥ëÉÕ¤±¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	    <username>root</username> ¥æ¡¼¥¶¤Ç¥í¥°¥¤¥ó¤¹¤ë¤«
 	    <command>su</command> ¥³¥Þ¥ó¥É¤òÍѤ¤¤ë¤«¤·¤Æ root ¸¢¸Â¤ò¼èÆÀ¤·¤Þ¤¹¡£
 	    <command>/stand/sysinstall</command> ¤ò¼Â¹Ô¤·¤Æ <literal>Configure</literal>
 	    ¥á¥Ë¥å¡¼¤ËÆþ¤ê¤Þ¤¹¡£<literal>FreeBSD Configuration Menu</literal>
 	    ¤ÎÃæ¤Ç¥¹¥¯¥í¡¼¥ë¥À¥¦¥ó¤·¤Æ <literal>Fdisk</literal>
 	    ¤Î¹àÌܤòÁª¤Ó¤Þ¤¹¡£</para>
 	</step>
 
 	<step>
 	  <title><application>fdisk</application> ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥¨¥Ç¥£¥¿</title>
 	  <para><application>fdisk</application> ¤Ç¤Ï¡¢¥Ç¥£¥¹¥¯Á´ÂΤò
 	    FreeBSD ¤Ç»È¤¦¤¿¤á¤Ë <userinput>A</userinput> ¤òÆþÎϤ·¤Þ¤¹¡£
 	    <quote>remain cooperative with any future possible operating systems</quote>
 	    ¤Èʹ¤«¤ì¤¿¤é <literal>YES</literal> ¤ÈÅú¤¨¤Þ¤¹¡£
 	    <userinput>W</userinput> ¤ÇÊѹ¹¤ò¥Ç¥£¥¹¥¯¤Ë½ñ¤­¹þ¤ß¤Þ¤¹¡£¤³¤³¤Ç
 	    <userinput>q</userinput> ¤ÈÆþÎϤ·¤Æ FDISK ¥¨¥Ç¥£¥¿¤òÈ´¤±¤Þ¤¹¡£
 	    ¼¡¤Ë¥Þ¥¹¥¿¥Ö¡¼¥È¥ì¥³¡¼¥É¤Ë¤Ä¤¤¤Æʹ¤«¤ì¤Þ¤¹¡£
 	    ¤³¤³¤Ç¤Ï´û¤ËÆ°¤¤¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤Ë¥Ç¥£¥¹¥¯¤òÄɲ䷤褦¤È¤·¤Æ¤¤¤ë¤Î¤Ç
 	    <literal>None</literal> ¤òÁª¤Ó¤Þ¤¹¡£</para>
 	</step>
 
 	<step>
 	  <title>¥Ç¥£¥¹¥¯¥é¥Ù¥ë¥¨¥Ç¥£¥¿</title>
 	  <indexterm><primary>BSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó</primary></indexterm>
 
 	  <para>¼¡¤Ë <application>sysinstall</application> ¤ò½ªÎ»¤·¡¢
 	    ¤â¤¦°ìÅÙµ¯Æ°¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£Æ±¤¸¼ê½ç¤òƧ¤ó¤Çº£ÅÙ¤Ï
 	    <literal>Label</literal> ¥ª¥×¥·¥ç¥ó¤òÁªÂò¤·¡¢
 	    <literal>Disk Label Editor</literal> ¤ËÆþ¤ê¤Þ¤¹¡£
 	    ¤³¤³¤Ç¤Ï½¾Íè¤Î BSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºîÀ®¤·¤Þ¤¹¡£
 	    °ì¤Ä¤Î¥Ç¥£¥¹¥¯¤Ï <literal>a</literal> ¤«¤é <literal>h</literal> ¤Þ¤Ç¤Î¥é¥Ù¥ë¤¬¤Ä¤¤¤¿ºÇÂç
 	    8 ¤Ä¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò»ý¤Ä¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	    ¤¤¤¯¤Ä¤«¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥é¥Ù¥ë¤ÏÆÃÊ̤ÊÍÑÅÓ¤ËÍѤ¤¤é¤ì¤Þ¤¹¡£
 	    <literal>a</literal> ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ï¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó
 	    (<filename>/</filename>) ¤Ç¤¹¡£¤·¤¿¤¬¤Ã¤Æ¡¢¥·¥¹¥Æ¥à¥Ç¥£¥¹¥¯
 	    (¤Ä¤Þ¤êµ¯Æ°¥Ç¥£¥¹¥¯) ¤Î¤ß¤Ë <literal>a</literal>
 	    ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤¬¤¢¤ë¤Ù¤­¤Ç¤¹¡£<literal>b</literal>
 	    ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ï¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ËÍѤ¤¤é¤ì¡¢
 	    Ê£¿ô¤Î¥Ç¥£¥¹¥¯¤Ë¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºî¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	    <literal>c</literal> ¤ÏÀìÍѥ⡼¥É¤Ë¤ª¤±¤ë¥Ç¥£¥¹¥¯Á´ÂΡ¢
 	    ¤â¤·¤¯¤Ï¥¹¥é¥¤¥¹¥â¡¼¥É¤Ë¤ª¤±¤ë¥¹¥é¥¤¥¹Á´ÂΤò»Ø¤·¤Þ¤¹¡£
 	    ¾¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ÏÈÆÍÑŪ¤ËÍѤ¤¤é¤ì¤Þ¤¹¡£</para>
 
 	  <para><application>sysinstall</application> ¤Î¥é¥Ù¥ë¥¨¥Ç¥£¥¿
 	    ¤Ï¡¢¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ç¤â¥¹¥ï¥Ã¥×¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ç¤â¤Ê¤¤¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë¤Ï¡¢<literal>e</literal>
 	    ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºÎÍѤ·¤è¤¦¤È¤·¤Þ¤¹¡£¥é¥Ù¥ë¥¨¥Ç¥£¥¿¤Ç¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤Ë¤Ï
 	    <userinput>C</userinput> ¤òÆþÎϤ·¤Æ¤¯¤À¤µ¤¤¡£
 	    FS (¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à) ¤«¥¹¥ï¥Ã¥×¤«¤òʹ¤«¤ì¤¿¤é
 	    <literal>FS</literal> ¤òÁª¤Ó¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È
 	    (¤¿¤È¤¨¤Ð <filename>/mnt</filename>) ¤òÆþÎϤ·¤Þ¤¹¡£
 	    ¥¤¥ó¥¹¥È¡¼¥ë¸å¤Î¥â¡¼¥É¤Ç¥Ç¥£¥¹¥¯¤òÄɲ乤ë¾ì¹ç¡¢
 	    <application>sysinstall</application> ¤Ï
 	    <filename>/etc/fstab</filename> ¤Ë¥¨¥ó¥È¥ê¤òÄɲ䷤ʤ¤¤¿¤á¡¢
 	    ¤³¤³¤Ç»ØÄꤹ¤ë¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤Ï¤½¤ì¤Û¤É½ÅÍפǤϤ¢¤ê¤Þ¤»¤ó¡£</para>
 
 	  <para>¤µ¤Æ¡¢¥Ç¥£¥¹¥¯¤Ë¿·¤·¤¤¥é¥Ù¥ë¤ò½ñ¤­¹þ¤ß¡¢
 	    ¤½¤³¤Ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºî¤ë½àÈ÷¤¬À°¤¤¤Þ¤·¤¿¡£Áá®
 	    <command>W</command> ¤òᤤ¤Æ¼Â¹Ô¤·¤Þ¤·¤ç¤¦¡£
 	    <application>sysinstall</application> ¤«¤é¤Î¡¢
 	    ¿·¤·¤¤¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¥Þ¥¦¥ó¥È¤Ç¤­¤Ê¤¤¡¢
 	    ¤È¤¤¤¦¥¨¥é¡¼¤Ï̵»ë¤·¤Æ¤¯¤À¤µ¤¤¡£Label Editor ¤«¤éÈ´¤±¡¢
 	    <application>sysinstall</application> ¤ò½ªÎ»¤·¤Þ¤¹¡£</para>
 	</step>
 
 	<step>
 	  <title>½ªÎ»</title>
 
 	  <para>ºÇ¸å¤Ë <filename>/etc/fstab</filename> ¤òÊÔ½¸¤·¡¢
 	    ¿·¤·¤¤¥Ç¥£¥¹¥¯¤Î¥¨¥ó¥È¥ê¤òÄɲä·¤Þ¤¹¡£</para>
 	</step>
       </procedure>
     </sect2>
 
     <sect2>
       <title>¥³¥Þ¥ó¥É¥é¥¤¥ó¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ÎÍøÍÑ</title>
 
       <sect3>
 	<title>¥¹¥é¥¤¥¹¤ÎÍøÍÑ</title>
 
 	<para>¤³¤Î¥»¥Ã¥È¥¢¥Ã¥×ÊýË¡¤Ç¤Ï¡¢
 	  ¤¹¤Ç¤Ë¥³¥ó¥Ô¥å¡¼¥¿¤Ë¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤Æ¤â
 	  Àµ¤·¤¯¶¨Ä´Æ°ºî¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¡¢Â¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î
 	  <command>fdisk</command> ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤òº®Í𤵤»¤ë¤³¤È¤â¤¢¤ê¤Þ¤»¤ó¡£
 	  ¿·¤·¤¤¥Ç¥£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¾ì¹ç¤Ï¡¢
 	  ¤³¤ÎÊýË¡¤òÍѤ¤¤ë¤³¤È¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
 	  ¸å½Ò¤¹¤ë <literal>ÀìÍѥ⡼¥É</literal> ¤Ï¡¢
 	  ¤½¤¦¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤Íýͳ¤¬¤¢¤ë»þ¤Ë¤Î¤ß¡¢
 	  ÍøÍѤ¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
 &prompt.root; <userinput>fdisk -BI da1</userinput> # ¿·¤·¤¤¥Ç¥£¥¹¥¯¤Î½é´ü²½
 &prompt.root; <userinput>disklabel -B -w -r da1s1 auto</userinput> # ¥Ç¥£¥¹¥¯¤Ë¥é¥Ù¥ë¤òÉÕ¤±¤ë
 &prompt.root; <userinput>disklabel -e da1s1</userinput> # ºîÀ®¤·¤¿¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òÊÔ½¸¤·¡¢¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÄɲ乤ë
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>newfs /dev/da1s1e</userinput> # ºîÀ®¤·¤¿¤¹¤Ù¤Æ¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ËÂФ·¤Æ¤³¤ì¤ò·«¤êÊÖ¤¹
 &prompt.root; <userinput>mount /dev/da1s1e /1</userinput> # ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¥Þ¥¦¥ó¥È¤¹¤ë
 &prompt.root; <userinput>vi /etc/fstab</userinput> # <filename>/etc/fstab</filename> ¤ËŬÀڤʥ¨¥ó¥È¥ê¤òÄɲ乤ë</screen>
 
 	<para>IDE ¥Ç¥£¥¹¥¯¤ò»È¤¦¾ì¹ç¤Ï <filename>da</filename> ¤ÎÉôʬ¤ò
 	  <filename>ad</filename> ¤È¤·¤Þ¤¹¡£4.X ¤è¤êÁ°¤Î¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
 	  (ÌõÃí: <filename>ad</filename> ¤Ç¤Ï¤Ê¤¯)
 	  <filename>wd</filename> ¤È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
       </sect3>
 
       <sect3>
 	<title>ÀìÍѥ⡼¥É</title>
 	<indexterm><primary>OS/2</primary></indexterm>
 
 	<para>¿·¤·¤¤¥É¥é¥¤¥Ö¤ò¾¤Î OS ¤È¶¦Í­¤·¤Ê¤¤¾ì¹ç¤Ë¤Ï
 	  <literal>ÀìÍÑ</literal> ¥â¡¼¥É¤òÍѤ¤¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
 	  ¤³¤Î¥â¡¼¥É¤Ï¥Þ¥¤¥¯¥í¥½¥Õ¥È¤Î OS
 	  ¤òº®Í𤵤»¤ë¤³¤È¤ò²±¤¨¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤
 	  (¤·¤«¤·¡¢¤½¤ì¤é¤Ë¤è¤Ã¤Æ²õ¤µ¤ì¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó)¡£ °ìÊý¡¢IBM ¤Î &os2;
 	  ¤Ï¤É¤ó¤Ê¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ç¤â¸«¤Ä¤±¤¿¤éÍý²ò¤Ç¤­¤Ê¤¯¤Æ¤â
 	  <quote>ÀìÍ­</quote> ¤·¤Þ¤¹¡£</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
 &prompt.root; <userinput>disklabel -Brw da1 auto</userinput>
 &prompt.root; <userinput>disklabel -e da1</userinput> # `e' ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ÎºîÀ®
 &prompt.root; <userinput>newfs -d0 /dev/da1e</userinput>
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>vi /etc/fstab</userinput> # /dev/da1e ¥¨¥ó¥È¥ê¤ÎÄɲÃ
 &prompt.root; <userinput>mount /1</userinput></screen>
 
 	<para>¤â¤¦°ì¤Ä¤ÎÊýË¡¤Ï¼¡¤ÎÄ̤ꡣ</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 count=2</userinput>
 &prompt.root; <userinput>disklabel /dev/da1 | disklabel -BrR da1 /dev/stdin</userinput>
 &prompt.root; <userinput>newfs /dev/da1e</userinput>
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>vi /etc/fstab</userinput> # /dev/da1e ¥¨¥ó¥È¥ê¤ÎÄɲÃ
 &prompt.root; <userinput>mount /1</userinput></screen>
 
 	<note><para>&os;&nbsp;5.1-RELEASE ¤«¤é¡¢½¾Íè¤Î &man.disklabel.8;
 	    ¥×¥í¥°¥é¥à¤Ï &man.bsdlabel.8;
 	    ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ËÃÖ¤­´¹¤¨¤é¤ì¤Þ¤·¤¿¡£&man.bsdlabel.8; ¤Ç¤Ï¡¢
 	    »ÈÍѤµ¤ì¤Æ¤¤¤Ê¤¤¿ô¿¤¯¤Î¥ª¥×¥·¥ç¥ó¤ä¥Ñ¥é¥á¥¿¤¬ºï½ü¤µ¤ì¤Þ¤·¤¿¡£
 	    ¤¿¤È¤¨¤Ð <option>-r</option> ¥ª¥×¥·¥ç¥ó¤Ï &man.bsdlabel.8;
 	    ¤Ç¤Ï¼è¤ê½ü¤«¤ì¤Þ¤·¤¿¡£¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï &man.bsdlabel.8;
 	    ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para></note>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="raid">
     <title>RAID</title>
 
     <sect2 id="raid-soft">
       <title>¥½¥Õ¥È¥¦¥§¥¢ RAID</title>
 
       <sect3 id="ccd">
 	<sect3info>
 	  <authorgroup>
 	    <author>
 	      <firstname>Christopher</firstname>
 	      <surname>Shumway</surname>
 	      <contrib>¸¶ºî: </contrib>
 	    </author>
 	  </authorgroup>
 	  <authorgroup>
 	    <author>
 	      <firstname>Jim</firstname>
 	      <surname>Brown</surname>
 	      <contrib>²þÄû: </contrib>
 	    </author>
 	  </authorgroup>
 	</sect3info>
 
 	<title>Concatenated Disk Driver (CCD) ¤ÎÀßÄê</title>
 
 	<indexterm>
 	  <primary>RAID</primary>
 	  <secondary>¥½¥Õ¥È¥¦¥§¥¢</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>RAID</primary>
 	  <secondary>CCD</secondary>
 	</indexterm>
 
 	<para>ÂçÍÆÎ̵­Ï¿¤Ë´Ø¤¹¤ë²ò·èË¡¤òÁªÂò¤¹¤ëºÝ¤Ë¤â¤Ã¤È¤â½Å»ë¤¹¤Ù¤­Í×ÁǤϡ¢
 	  ®ÅÙ¡¢¿®ÍêÀ­¡¢¤½¤·¤ÆÈñÍѤǤ¹¡£
 	  »°¤Ä¤òƱ»þ¤Ë¥Ð¥é¥ó¥¹¤è¤¯¼Â¸½¤¹¤ë¤³¤È¤Ïµ©¤Ç¤¹¡£
 	  Ä̾®¤¯¤Æ¿®ÍêÀ­¤Î¤¢¤ëÂçÍÆÎ̵­Ï¿ÁõÃ֤Ϲâ²Á¤Ç¤¢¤ê¡¢
 	  ÈñÍѤòÍÞ¤¨¤è¤¦¤È¤¹¤ë¤È®ÅÙ¤Þ¤¿¤Ï¿®ÍêÀ­¤Î¤É¤Á¤é¤«¤¬µ¾À·¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
 
 	<para>¤³¤³¤ÇÎã¤Ë¤¢¤²¤ë¥·¥¹¥Æ¥à¤ÎÀ߷פˤª¤¤¤Æ¤Ï¡¢
 	  ÈñÍѤ¬ºÇ¤â½ÅÍפÊÍ×ÁǤȤ·¤Æ¡¢¼¡¤Ë®ÅÙ¡¢ºÇ¸å¤Ë¿®ÍêÀ­¤¬ÁªÂò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
 	  ¤³¤Î¥·¥¹¥Æ¥à¤Ç¤Î¥Ç¡¼¥¿Å¾Á÷®Å٤Ϸë¶É¤Î¤È¤³¤í¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤è¤Ã¤ÆÀ©¸Â¤µ¤ì¤Þ¤¹¡£
 	  ¿®ÍêÀ­¤ÏÂçÊѽÅÍפǤ¹¡£¤¿¤À¤·¡¢°Ê²¼¤ÇÀâÌÀ¤¹¤ë CCD ¥É¥é¥¤¥Ö¤Ï¡¢
 	  ¥Ç¡¼¥¿¼«ÂΤϤ¹¤Ç¤Ë CD-R ¤Ë´°Á´¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤·¤Æ¤¢¤ë¤â¤Î
 	  (¤·¤¿¤¬¤Ã¤Æ¸ò´¹¤Ï´Êñ¤Ë¤Ç¤­¤Þ¤¹)
 	  ¤Î¡¢¥ª¥ó¥é¥¤¥ó¥Ç¡¼¥¿¤ÎÌò³ä¤ò¤µ¤»¤Æ¤¤¤Þ¤¹¡£</para>
 
 	<para>¤¢¤Ê¤¿¼«¿È¤ÎÍ×µá»ö¹à¤ò·èÄꤹ¤ë¤³¤È¤Ï¡¢
 	  ÂçÍÆÎ̵­Ï¿¤Ë´Ø¤¹¤ë²ò·èË¡¤òÁªÂò¤¹¤ë¤³¤È¤ÎºÇ½é¤ÎÃʳ¬¤Ç¤¹¡£
 	  ¤â¤·¤¢¤Ê¤¿¤ÎÍ×µá»ö¹à¤¬ÈñÍѤè¤ê®ÅÙ¤Þ¤¿¤Ï¿®ÍêÀ­¤òÍ¥À褹¤ë¤Ê¤é¡¢
 	  ²ò·èË¡¤Ï¤³¤Î¥·¥¹¥Æ¥à¤È¤Ï°ã¤¦¤â¤Î¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£</para>
 
 	<sect4 id="ccd-installhw">
 	  <title>¥Ï¡¼¥É¥¦¥§¥¢¤Î¥¤¥ó¥¹¥È¡¼¥ë</title>
 
 	  <para>IDE ¥·¥¹¥Æ¥à¥Ç¥£¥¹¥¯¤Ë²Ã¤¨¤Æ¡¢Western Digital À½¤Î
 	    30GB, 5400RPM ¤Î IDE ¥Ç¥£¥¹¥¯»°Âæ¤ò»È¤Ã¤Æ¡¢
 	    °Ê²¼¤ËÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤ÊÌó 90GB ¤Î¥ª¥ó¥é¥¤¥ó¥¹¥È¥ì¡¼¥¸¤È¤Ê¤ë
 	    CCD ¥Ç¥£¥¹¥¯¤òºîÀ®¤·¤Þ¤·¤¿¡£³Æ IDE ¥Ç¥£¥¹¥¯¤¬¤½¤ì¤¾¤ì¤Î
 	    IDE ¥³¥ó¥È¥í¡¼¥é¤È¥±¡¼¥Ö¥ë¤ò¤â¤Ã¤Æ¤¤¤ë¤³¤È¤¬ÍýÁÛŪ¤Ç¤¹¤¬¡¢
 	    ÈñÍѤòºÇÄã¸Â¤Ë¤¹¤ë¤¿¤á¤Ë¡¢
 	    IDE ¥³¥ó¥È¥í¡¼¥é¤òÄɲ䷤Ƥ¤¤Þ¤»¤ó¡£¤½¤ÎÂå¤ï¤ê¡¢¤½¤ì¤¾¤ì¤Î IDE
 	    ¥³¥ó¥È¥í¡¼¥é¤¬¥Þ¥¹¥¿¥Ç¥Ð¥¤¥¹¤ò°ì¤Ä¡¢
 	    ¥¹¥ì¡¼¥Ö¥Ç¥Ð¥¤¥¹¤ò°ì¤Ä»ý¤Ä¤è¤¦¤Ë¡¢
 	    ¥Ç¥£¥¹¥¯¤Ï¥¸¥ã¥ó¥Ñ¤ò»È¤Ã¤ÆÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
 	  <para>ºÆµ¯Æ°¤ÎºÝ¤Ë¡¢¥·¥¹¥Æ¥à BIOS
 	    ¤¬Àܳ¤µ¤ì¤¿¥Ç¥£¥¹¥¯¤ò¼«Æ°Åª¤Ë¸¡½Ð¤¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Þ¤·¤¿¡£
 	    ¤è¤ê½ÅÍפʤ³¤È¤Ï¡¢FreeBSD ¤¬ºÆµ¯Æ°¤ÎºÝ¤Ë¤½¤ì¤é¤ò¸¡½Ð¤¹¤ë¤³¤È¤Ç¤¹¡£</para>
 
 	  <programlisting>ad0: 19574MB &lt;WDC WD205BA&gt; [39770/16/63] at ata0-master UDMA33
 ad1: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata0-slave UDMA33
 ad2: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-master UDMA33
 ad3: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-slave UDMA33</programlisting>
 
  	  <note><para>FreeBSD ¤¬¥Ç¥£¥¹¥¯¤ò¤¹¤Ù¤Æ¸¡½Ð¤·¤Ê¤¤¤È¤­¤Ï¡¢
 	      ¥¸¥ã¥ó¥Ñ¤òÀµ¤·¤¯ÀßÄꤷ¤Æ¤¢¤ë¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£Â¿¤¯¤Î IDE
 	      ¥É¥é¥¤¥Ö¤Ï <quote>¥±¡¼¥Ö¥ë¥»¥ì¥¯¥È</quote>
 	      ¥¸¥ã¥ó¥Ñ¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£
 	      ¤³¤ì¤Ï¥Þ¥¹¥¿/¥¹¥ì¡¼¥Ö¤Î´Ø·¸¤òÀßÄꤹ¤ë¥¸¥ã¥ó¥Ñ¤Ç¤Ï
 	      <emphasis>¤¢¤ê¤Þ¤»¤ó</emphasis>¡£¥É¥é¥¤¥Ö¤Îʸ½ñ¤ò»²¾È¤·¤Æ¡¢
 	      Àµ¤·¤¤¥¸¥ã¥ó¥ÑÀßÄê¤ò¸«¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£</para></note>
 
 	  <para>¼¡¤Ë¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ìÉôʬ¤È¤·¤Æ¡¢
 	    ¤½¤ì¤é¤ò¤É¤Î¤è¤¦¤ËÀܳ¤¹¤ë¤Î¤«¤ò¹Íθ¤·¤Þ¤¹¡£&man.vinum.8;
 	    <!-- Furukawa:2004/1/8
 	    should be refer this after creating vinum/chapter.xml
 	    (<xref linkend="vinum-vinum"/>)
 	    -->
 	    ¤ª¤è¤Ó &man.ccd.4;
 	    ¤ÎξÊý¤ò¸¡Æ¤¤¹¤Ù¤­¤Ç¤·¤ç¤¦¡£¤³¤ÎÀßÄê¤Ç¤Ï¡¢&man.ccd.4;
 	    ¤òÁªÂò¤·¤Þ¤·¤¿¡£</para>
 	</sect4>
 
 	<sect4 id="ccd-setup">
 	  <title>CCD ¤ÎÀßÄê</title>
 
 	  <para>&man.ccd.4; ¥É¥é¥¤¥Ð¤Ï¡¢¤¤¤¯¤Ä¤«¤ÎƱ¤¸¥Ç¥£¥¹¥¯¤ò»È¤Ã¤Æ¡¢
 	    °ì¤Ä¤ÎÏÀÍýŪ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÏ¢·ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	    &man.ccd.4; ¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢¥«¡¼¥Í¥ë¤¬ &man.ccd.4;
 	    ¤ËÂбþ¤·¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	    ¼¡¤Î¹Ô¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥®¥å¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤ËÄɲ䷤ơ¢
 	    ¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¡¢ºÆ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <programlisting>pseudo-device   ccd     4</programlisting>
 
 	  <para>5.X ¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
 	    ¾åµ­¤ÎÂå¤ï¤ê¤Ë¼¡¤Î¹Ô¤òÄɲ䷤ʤ±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
 	  <programlisting>device   ccd</programlisting>
 
 	  <note><para>FreeBSD&nbsp;5.X ¤Ç¤Ï &man.ccd.4;
 	      ¥Ç¥Ð¥¤¥¹¤Î¿ô¤ò»ØÄꤹ¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£&man.ccd.4;
 	      ¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Ï¼«¸ÊÊ£À½¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿ &mdash;
 	      ¿·¤·¤¤¥Ç¥Ð¥¤¥¹¥¤¥ó¥¹¥¿¥ó¥¹¤Ï¡¢
 	      ɬÍפ˱þ¤¸¤Æ¤½¤ÎÅÔÅÙ¼«Æ°Åª¤ËºîÀ®¤µ¤ì¤Þ¤¹¡£</para></note>
 
 	  <para>FreeBSD 3.0 °Ê¹ß¤Ç¤Ï¡¢
 	    ¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤òÆɤ߹þ¤ó¤Ç
 	    &man.ccd.4; ¤ËÂбþ¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£</para>
 
 	  <para>&man.ccd.4; ¤òÀßÄꤹ¤ë¤¿¤á¤Ë¡¢¤Þ¤º &man.disklabel.8;
 	    ¤ò»ÈÍѤ·¤Æ¥Ç¥£¥¹¥¯¤Ë¥é¥Ù¥ë¤ò½ñ¤­¹þ¤Þ¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
 	  <programlisting>disklabel -r -w ad1 auto
 disklabel -r -w ad2 auto
 disklabel -r -w ad3 auto</programlisting>
 
 	  <para>¤³¤Î¥³¥Þ¥ó¥É¤Ï¥Ç¥£¥¹¥¯Á´ÂΤò¼¨¤¹
 	    <devicename>ad1c</devicename>,
 	    <devicename>ad2c</devicename> ¤ª¤è¤Ó
 	    <devicename>ad3c</devicename> ¤ËÂФ¹¤ë¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òºîÀ®¤·¤Þ¤¹¡£</para>
 
 	  <note><para>&os;&nbsp;5.1-RELEASE ¤«¤é¡¢½¾Íè¤Î &man.disklabel.8;
 	      ¥×¥í¥°¥é¥à¤Ï &man.bsdlabel.8;
 	      ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ËÃÖ¤­´¹¤¨¤é¤ì¤Þ¤·¤¿¡£&man.bsdlabel.8; ¤Ç¤Ï¡¢
 	      »ÈÍѤµ¤ì¤Æ¤¤¤Ê¤¤¿ô¿¤¯¤Î¥ª¥×¥·¥ç¥ó¤ä¥Ñ¥é¥á¥¿¤¬ºï½ü¤µ¤ì¤Þ¤·¤¿¡£
 	      ¤¿¤È¤¨¤Ð <option>-r</option> ¥ª¥×¥·¥ç¥ó¤Ï &man.bsdlabel.8;
 	      ¤Ç¤Ï¼è¤ê½ü¤«¤ì¤Þ¤·¤¿¡£¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï &man.bsdlabel.8;
 	      ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para></note>
 
 	  <para>¼¡¤Ë¡¢¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤Î¥¿¥¤¥×¤òÊѹ¹¤·¤Þ¤¹¡£
 	    &man.disklabel.8; ¤ò»ÈÍѤ·¤Æ¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òÊÔ½¸¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <programlisting>disklabel -e ad1
 disklabel -e ad2
 disklabel -e ad3</programlisting>
 
 	  <para>¤³¤Î¥³¥Þ¥ó¥É¤Ï <envar>EDITOR</envar>
 	    ´Ä¶­ÊÑ¿ô¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¥¨¥Ç¥£¥¿ (°ìÈÌŪ¤Ë¤Ï &man.vi.1;)
 	    ¤Ç¤½¤ì¤¾¤ì¤Î¥Ç¥£¥¹¥¯¤Î¸½ºß¤Î¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤ò³«¤­¤Þ¤¹¡£</para>
 
 	  <para>Êѹ¹¤µ¤ì¤Æ¤¤¤Ê¤¤¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
 
 	  <programlisting>8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)</programlisting>
 
 	  <para>&man.ccd.4; ¤Ç»ÈÍѤ¹¤ë <literal>e</literal>
 	    ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºîÀ®¤·¤Þ¤¹¡£Ä̾ï¤Ç¤Ï <literal>c</literal>
 	    ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¹Ô¤ò¥³¥Ô¡¼¤¹¤ì¤ÐÎɤ¤¤Ç¤·¤ç¤¦¡£¤·¤«¤·¡¢
 	    <option>fstype</option> ¤Ï <userinput>4.2BSD</userinput>
 	    ¤Ç¤Ê¤±¤ì¤Ð <emphasis>¤Ê¤ê¤Þ¤»¤ó</emphasis>¡£
 	    ¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£</para>
 
 	  <programlisting>8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)
   e: 60074784        0    4.2BSD        0     0     0   # (Cyl.    0 - 59597)</programlisting>
 	</sect4>
 
 	<sect4 id="ccd-buildingfs">
 	  <title>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¹½ÃÛ</title>
 
 	  <para><devicename>ccd0c</devicename>
 	    ¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤Ï¤Þ¤À¸ºß¤·¤Æ¤¤¤Ê¤¤¤«¤âÃΤì¤Þ¤»¤ó¡£
 	    ¤½¤Î¤È¤­¤Ï¡¢¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤ÆºîÀ®¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <programlisting>cd /dev
 sh MAKEDEV ccd0</programlisting>
 
 	  <note><para>FreeBSD 5.0 ¤Ç¤Ï &man.devfs.5; ¤¬
 	      <filename>/dev</filename> °Ê²¼¤Î¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤ò¼«Æ°Åª¤Ë´ÉÍý¤¹¤ë¤Î¤Ç¡¢
 	      <command>MAKEDEV</command>¤ò»ÈÍѤ¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£</para></note>
 
 	  <para>¤¹¤Ù¤Æ¤Î¥Ç¥£¥¹¥¯¤Ë¥é¥Ù¥ë¤ò½ñ¤­¹þ¤ó¤À¤Î¤Ç¡¢
 	    &man.ccd.4; ¤ò¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£
 	    ¤³¤ì¤ò¹Ô¤¦¤¿¤á¤Ë¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ê¥ª¥×¥·¥ç¥ó¤Ç
 	    &man.ccdconfig.8; ¤ò»È¤¤¤Þ¤¹¡£</para>
 
 	  <programlisting>ccdconfig ccd0<co id="co-ccd-dev"/> 32<co id="co-ccd-interleave"/> 0<co id="co-ccd-flags"/> /dev/ad1e<co id="co-ccd-devs"/> /dev/ad2e /dev/ad3e</programlisting>
 
 	  <para>³Æ¥ª¥×¥·¥ç¥ó¤Î»ÈÍÑË¡¤È°ÕÌ£¤Ï°Ê²¼¤ÎÄ̤ê¤Ç¤¹¡£</para>
 
 	  <calloutlist>
 	    <callout arearefs="co-ccd-dev">
 	      <para>°ìÈÖÌܤΰú¿ô¤ÏÀßÄꤹ¤ë¥Ç¥Ð¥¤¥¹¤Ç¤¹¡£¤³¤ÎÎã¤Î¾ì¹ç¤Ï
 		<devicename>/dev/ccd0c</devicename> ¤Ç¤¹¡£
 		<filename>/dev/</filename> ¤ÎÉôʬ¤Ï¥ª¥×¥·¥ç¥ó¤Ç¤¹¡£</para>
 	    </callout>
 
 	    <callout arearefs="co-ccd-interleave">
 	      <para>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ¹¤ë¥¤¥ó¥¿¥ê¡¼¥Ö¤Ç¤¹¡£¥¤¥ó¥¿¥ê¡¼¥Ö¤Ï¡¢
 		¥Ç¥£¥¹¥¯¥Ö¥í¥Ã¥¯Æâ¤Î¥¹¥È¥é¥¤¥×¥µ¥¤¥º¤òÄêµÁ¤·¤Þ¤¹¡£
 		¥Ç¥£¥¹¥¯¥Ö¥í¥Ã¥¯¤ÏÄ̾ï 512 ¥Ð¥¤¥È¤Ç¤¹¡£¤·¤¿¤¬¤Ã¤Æ 32
 		¥¤¥ó¥¿¥ê¡¼¥Ö¤Ï 16,384 ¥Ð¥¤¥È¤È¤Ê¤ê¤Þ¤¹¡£</para>
 	    </callout>
 
 	    <callout arearefs="co-ccd-flags">
 	      <para>¤³¤ì¤Ï &man.ccdconfig.8; ¤ËÂФ¹¤ë¥Õ¥é¥°¤Ç¤¹¡£
 		¥É¥é¥¤¥Ö¥ß¥é¡¼¥ê¥ó¥°¤òÍ­¸ú¤Ë¤·¤¿¤¤¾ì¹ç¡¢
 		¤³¤³¤Ë¥Õ¥é¥°¤ò»ØÄꤷ¤Þ¤¹¡£
 		¤³¤ÎÀßÄê¤Ç¤Ï &man.ccd.4; ¤ËÂФ¹¤ë¥ß¥é¡¼¥ê¥ó¥°¤ÏÄ󶡤·¤Þ¤»¤ó¤Î¤Ç¡¢
 		0 (¥¼¥í) ¤ò»ØÄꤷ¤Æ¤¤¤Þ¤¹¡£</para>
 	    </callout>
 
 	    <callout arearefs="co-ccd-devs">
 	      <para>¤³¤Î &man.ccdconfig.8; ¤ËÂФ¹¤ëºÇ¸å¤Î°ú¿ô¤Ï¡¢
 		¥¢¥ì¥¤Æâ¤ËÃÖ¤¯¥Ç¥Ð¥¤¥¹¤Ç¤¹¡£
 		¤½¤ì¤¾¤ì¤Î¥Ç¥Ð¥¤¥¹¤ËÂФ¹¤ë´°Á´¤Ê¥Ñ¥¹Ì¾¤ò»ÈÍѤ·¤Þ¤¹¡£</para>
 	    </callout>
 	  </calloutlist>
 
 	  <para>&man.ccdconfig.8; ¤ò¼Â¹Ô¤¹¤ë¤È &man.ccd.4; ¤¬ÀßÄꤵ¤ì¤Þ¤¹¡£
 	    ¤³¤ì¤Ç¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¹¡£
 	    ¥ª¥×¥·¥ç¥ó¤Ë¤Ä¤¤¤Æ &man.newfs.8; ¤ò»²¾È¤¹¤ë¤«¡¢
 	    ¼¡¤Î¤è¤¦¤Ë¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <programlisting>newfs /dev/ccd0c</programlisting>
 	</sect4>
 
 	<sect4 id="ccd-auto">
 	  <title>¼«Æ°Åª¤ËÀßÄꤹ¤ë</title>
 
 	  <para>°ìÈÌŪ¤Ë¡¢ºÆµ¯Æ°¤¹¤ë¤¿¤Ó¤Ë &man.ccd.4;
 	    ¤ò¥Þ¥¦¥ó¥È¤·¤¿¤¤¤È»×¤¦¤Ç¤·¤ç¤¦¡£¤³¤ì¤ò¹Ô¤¦¤¿¤á¤Ë¡¢
 	    ¤Þ¤ºÀßÄê¤ò¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¼¡¤Î¥³¥Þ¥ó¥É¤òÍѤ¤¤Æ¡¢
 	    ¸½ºß¤ÎÀßÄê¤ò <filename>/etc/ccd.conf</filename> ¤Ë½ñ¤­½Ð¤·¤Þ¤¹¡£</para>
 
 	  <programlisting>ccdconfig -g &gt; /etc/ccd.conf</programlisting>
 
 	  <para><filename>/etc/ccd.conf</filename> ¤¬Â¸ºß¤¹¤ë¤È¡¢
 	    ºÆµ¯Æ°¤ÎºÝ¤Ë <command>/etc/rc</command> ¥¹¥¯¥ê¥×¥È¤¬
 	    <command>ccdconfig -C</command> ¤ò¼Â¹Ô¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢
 	    &man.ccd.4; ¤Ï¼«Æ°Åª¤ËÀßÄꤵ¤ì¤¿¸å¡¢¥Þ¥¦¥ó¥È¤µ¤ì¤Þ¤¹¡£</para>
 
 	  <note><para>¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤Çµ¯Æ°¤·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
 	      &man.ccd.4; ¤ò &man.mount.8; ¤¹¤ëÁ°¤Ë¡¢
 	      ¥¢¥ì¥¤¤òÀßÄꤹ¤ë¤¿¤á¤Ë¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
 	    <programlisting>ccdconfig -C</programlisting>
 	  </note>
 
 	  <para>¼«Æ°Åª¤Ë &man.ccd.4; ¤ò¥Þ¥¦¥ó¥È¤¹¤ë¤Ë¤Ï¡¢
 	    <filename>/etc/fstab</filename> ¤Ë &man.ccd.4;
 	    ¤Î¥¨¥ó¥È¥êÄɲä·¤Þ¤¹¡£¤³¤Î¤è¤¦¤ËÀßÄꤹ¤ë¤Èµ¯Æ°»þ¤Ë¥Þ¥¦¥ó¥È¤µ¤ì¤Þ¤¹¡£</para>
 
 	  <programlisting>/dev/ccd0c              /media       ufs     rw      2       2</programlisting>
 	</sect4>
       </sect3>
 
       <sect3 id="vinum">
 	<title>Vinum ¥Ü¥ê¥å¡¼¥à¥Þ¥Í¡¼¥¸¥ã</title>
 	<indexterm>
 	  <primary>RAID</primary>
 	  <secondary>¥½¥Õ¥È¥¦¥§¥¢</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>RAID</primary>
 	  <secondary>Vinum</secondary>
 	</indexterm>
 
 	<para>Vinum ¥Ü¥ê¥å¡¼¥à¥Þ¥Í¡¼¥¸¥ã¤Ï¡¢
 	  ²¾Áۥǥ£¥¹¥¯¥É¥é¥¤¥Ö¤ò¼ÂÁõ¤·¤¿¥Ö¥í¥Ã¥¯¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Ç¤¹¡£
 	  Vinum ¤Ï¡¢¥Ç¥£¥¹¥¯¥Ï¡¼¥É¥¦¥§¥¢¤ò¥Ö¥í¥Ã¥¯¥Ç¥Ð¥¤¥¹¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤«¤é
 	  ʬΥ¤·¡¢¥Ç¡¼¥¿¤òÇÛÃÖ¤·¤Þ¤¹¡£
 	  ¤½¤Î·ë²Ì¡¢¥Ç¥£¥¹¥¯µ­²±ÁõÃÖ¤ò½¾Íè¤Î¥¹¥é¥¤¥¹¤Ç°·¤¦¤Î¤ÈÈæ³Ó¤·¤Æ¡¢
 	  ½ÀÆðÀ­¡¢À­Ç½¤ª¤è¤Ó¿®ÍêÀ­¤¬¸þ¾å¤·¤Æ¤¤¤Þ¤¹¡£
 	  &man.vinum.8; ¤Ï RAID-0, RAID-1 ¤ª¤è¤Ó RAID-5 ¥â¥Ç¥ë¡¢
 	  ¤½¤·¤Æ¤½¤ì¤¾¤ì¤ÎÁȹ礻¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£</para>
 
 	<para>&man.vinum.8; ¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï Vinum ¥Ü¥ê¥å¡¼¥à¥Þ¥Í¥¸¥ã
 	  <!-- Furukawa:2004/1/8
 	  should be refer this after creating vinum/chapter.xml
 	  <xref linkend="vinum-vinum"/>
 	  -->
 	  ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
       </sect3>
     </sect2>
 
     <sect2 id="raid-hard">
       <title>¥Ï¡¼¥É¥¦¥§¥¢ RAID</title>
       <indexterm>
 	<primary>RAID</primary>
 	<secondary>¥Ï¡¼¥É¥¦¥§¥¢</secondary>
       </indexterm>
 
       <para>FreeBSD ¤Ï¡¢¤µ¤Þ¤¶¤Þ¤Ê¥Ï¡¼¥É¥¦¥§¥¢ <acronym>RAID</acronym>
 	¥³¥ó¥È¥í¡¼¥é¤Ë¤âÂбþ¤·¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤é¤Î¥Ç¥Ð¥¤¥¹¤Ï¥¢¥ì¥¤¤òÀ©¸æ¤¹¤ë¤¿¤á¤Î
 	ÆÃÊ̤ʥ½¥Õ¥È¥¦¥§¥¢¤ò FreeBSD ¤ÇɬÍפ¹¤ë¤³¤È¤Ê¤¯¡¢
 	<acronym>RAID</acronym> ¥µ¥Ö¥·¥¹¥Æ¥à¤òÀ©¸æ¤·¤Þ¤¹¡£</para>
 
       <para>¥«¡¼¥É¾å¤Î <acronym>BIOS</acronym> ¤ò»ÈÍѤ·¤Æ¡¢
 	¥«¡¼¥É¤Ï¤½¤ì¼«¿È¤Ç¥Ç¥£¥¹¥¯Áàºî¤Î¤Û¤È¤ó¤É¤òÀ©¸æ¤·¤Þ¤¹¡£°Ê²¼¤Ï
 	<acronym>Promise IDE RAID</acronym>
 	¥³¥ó¥È¥í¡¼¥é¤ò»ÈÍѤ·¤¿ÀßÄê¤Î´Êñ¤ÊÀâÌÀ¤Ç¤¹¡£
 	¤³¤Î¥«¡¼¥É¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¡¢¥·¥¹¥Æ¥à¤¬µ¯Æ°¤·¤¿¤È¤­¤Ë¤Ï¡¢
 	¾ðÊó¤ÎÆþÎϤòÂ¥¤¹¥×¥í¥ó¥×¥È¤òɽ¼¨¤·¤Þ¤¹¡£
 	»Ø¼¨¤Ë¤·¤¿¤¬¤Ã¤Æ¥«¡¼¥É¤ÎÀßÄê²èÌ̤˿ʤó¤Ç¤¯¤À¤µ¤¤¡£
 	Àܳ¤µ¤ì¤¿¥É¥é¥¤¥Ö¤òÁȤ߹ç¤ï¤»¤ë¤è¤¦¤ËÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	ÀßÄê¸å¡¢¥Ç¥£¥¹¥¯¤Ï FreeBSD ¤ËÂФ·¤Æñ°ì¤Î¥É¥é¥¤¥Ö¤Î¤è¤¦¤Ë¸«¤¨¤Þ¤¹¡£
 	¾¤Î <acronym>RAID</acronym> ¥ì¥Ù¥ë¤ÏŬµ¹ÀßÄê¤Ç¤­¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2>
       <title>ATA RAID1 ¥¢¥ì¥¤¤ÎºÆ¹½ÃÛ</title>
 
       <para>FreeBSD ¤Ï¥¢¥ì¥¤Æâ¤Î¾ã³²¥Ç¥£¥¹¥¯¤òÆ°ºîÃæ¤Ë¸ò´¹¤Ç¤­¤Þ¤¹¡£
 	¤¿¤À¤·¡¢ºÆµ¯Æ°Á°¤Ë¤½¤ì¤ò¸¡ÃΤ·¤Æ¤¤¤ë¤³¤È¤¬É¬ÍפǤ¹¡£</para>
 
       <para><filename>/var/log/messages</filename> ¤Þ¤¿¤Ï &man.dmesg.8;
 	¤Î½ÐÎϤ˼¡¤Î¤è¤¦¤Ê¹Ô¤¬¤¢¤ë¤Ç¤·¤ç¤¦¡£</para>
 
       <programlisting>ad6 on monster1 suffered a hard error.
 ad6: READ command timeout tag=0 serv=0 - resetting
 ad6: trying fallback to PIO mode
 ata3: resetting devices .. done
 ad6: hard error reading fsbn 1116119 of 0-7 (ad6 bn 1116119; cn 1107 tn 4 sn 11) status=59 error=40
 ar0: WARNING - mirror lost</programlisting>
 
       <para>&man.atacontrol.8; ¤ò»ÈÍѤ·¤Æ¾ÜºÙ¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£</para>
 
       <screen>&prompt.root; <userinput>atacontrol list</userinput>
 ATA channel 0:
 	Master:      no device present
 	Slave:   acd0 &lt;HL-DT-ST CD-ROM GCR-8520B/1.00&gt; ATA/ATAPI rev 0
 
 ATA channel 1:
 	Master:      no device present
 	Slave:       no device present
 
 ATA channel 2:
 	Master:  ad4 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
 	Slave:       no device present
 
 ATA channel 3:
 	Master:  ad6 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
 	Slave:       no device present
 
 &prompt.root; <userinput>atacontrol status ar0</userinput>
 ar0: ATA RAID1 subdisks: ad4 ad6 status: DEGRADED</screen>
 
       <procedure>
 	<step>
 	  <para>¥Ç¥£¥¹¥¯¤ò°ÂÁ´¤Ë¼è¤ê³°¤¹¤¿¤á¤Ë¡¢
 	    ¤Þ¤º¥¢¥ì¥¤¤«¤éÀÚ¤êÎ¥¤·¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol detach 3</userinput></screen>
 	</step>
 
 	<step>
 	  <para>¥Ç¥£¥¹¥¯¤ò¼è¤ê³°¤·¤Þ¤¹¡£</para>
 	</step>
 
 	<step>
 	  <para>¥¹¥Ú¥¢¤Î¥Ç¥£¥¹¥¯¤ò¼è¤êÉÕ¤±¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol attach 3</userinput>
 Master:  ad6 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
 Slave:   no device present</screen>
 	</step>
 
 	<step>
 	  <para>¥¢¥ì¥¤¤òºÆ¹½ÃÛ¤·¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol rebuild ar0</userinput></screen>
 	</step>
 
 	<step>
 	  <para>ºÆ¹½ÃÛ¥³¥Þ¥ó¥É¤Ï´°Î»¤¹¤ë¤Þ¤Ç¾¤ÎÁàºî¤ò¼õ¤±ÉÕ¤±¤Þ¤»¤ó¡£¤·¤«¤·¡¢
 	    ¤â¤¦°ì¤ÄÊ̤Υ¿¡¼¥ß¥Ê¥ë¤ò
 	    (<keycombo action="simul"><keycap>Alt</keycap>
 	    <keycap>F<replaceable>n</replaceable></keycap></keycombo>
 	    ¤ò²¡¤·¤Æ) ³«¤­¡¢
 	    ¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë¤È¿Ê¹Ô¾õÂÖ¤ò³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>dmesg | tail -10</userinput>
 [output removed]
 ad6: removed from configuration
 ad6: deleted from ar0 disk1
 ad6: inserted into ar0 disk1 as spare
 
 &prompt.root; <userinput>atacontrol status ar0</userinput>
 ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed</screen>
 	</step>
 
 	<step>
 	  <para>Áàºî¤¬´°Î»¤¹¤ë¤Þ¤Ç¤ªÂÔ¤Á¤¯¤À¤µ¤¤¡£</para>
 	</step>
       </procedure>
     </sect2>
   </sect1>
 
   <sect1 id="creating-cds">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Mike</firstname>
 	  <surname>Meyer</surname>
 	  <contrib>´ó¹Æ: </contrib>
 	  <!-- mwm@mired.org -->
 	</author>
       </authorgroup>
       <!-- Apr 2001 -->
     </sect1info>
 
     <title>¸÷¥á¥Ç¥£¥¢ (CD &amp; DVD) ¤ÎºîÀ®¤È»ÈÍÑ</title>
     <indexterm>
       <primary>CDROM</primary>
       <secondary>ºîÀ®</secondary>
     </indexterm>
 
     <sect2>
       <title>¤Ï¤¸¤á¤Ë</title>
 
       <para>CD ¤Ï¾¤Î°ìÈÌŪ¤Ê¥Ç¥£¥¹¥¯¤È°Û¤Ê¤ëÍÍ¡¹¤ÊÆÃħ¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£
 	¤½¤â¤½¤â¥æ¡¼¥¶¤¬½ñ¤­¹þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£
 	¤Þ¤¿ÃÙ±ä¤Ê¤·¤ÇϢ³Ū¤ËÆɤ߽Ф»¤ë¤è¤¦¤Ë¡¢
 	¥È¥é¥Ã¥¯´Ö¤ò¥Ø¥Ã¥É¤¬°ÜÆ°¤·¤Ê¤¤¤Ç¤¹¤à¤è¤¦¤Ë¥Ç¥¶¥¤¥ó¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
 	¤µ¤é¤Ë¤³¤Î¥µ¥¤¥º¤Î¥á¥Ç¥£¥¢¤ÎÃæ¤Ç¤Ï¥·¥¹¥Æ¥à¤ò¤Þ¤¿¤°¥Ç¡¼¥¿¤Î
 	°ÜÆ°¤¬Èæ³ÓŪ´Êñ¤Ç¤â¤¢¤ê¤Þ¤¹¡£</para>
 
       <para>CD ¤Ï¥È¥é¥Ã¥¯¤Î³µÇ°¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢
 	¤³¤ì¤Ï¥Ç¡¼¥¿¤òϢ³Ū¤ËÆɤ߽Ф¹¤¿¤á¤Î¤â¤Î¤Ç¤¢¤Ã¤Æ¥Ç¥£¥¹¥¯¤ÎʪÍýÆÃÀ­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
 	FreeBSD ¤Ç CD ¤òºîÀ®¤¹¤ë¤Ë¤Ï¡¢¤Þ¤º CD
 	¤Î¥È¥é¥Ã¥¯¤È¤Ê¤ë¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë¤òÍÑ°Õ¤·¡¢
 	¤½¤Î¥È¥é¥Ã¥¯¤ò CD ¤Ë½ñ¤­¹þ¤ß¤Þ¤¹¡£</para>
 
       <indexterm><primary>ISO 9660</primary></indexterm>
       <indexterm>
 	<primary>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</primary>
 	<secondary>ISO 9660</secondary>
       </indexterm>
       <para>ISO 9660 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï¤³¤ÎÍͤʺ¹°Û¤ò°·¤¦¤Ù¤¯À߷פµ¤ì¤Þ¤·¤¿¡£
 	¤½¤Î·ë²Ì¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï°ìÈÌŪ¤Ë»ÈÍѤ¹¤ë¤Î¤Ëº¹¤·¤Ä¤«¤¨¤Ê¤¤ÄøÅÙ¤Ë
 	À©¸Â¤µ¤ì¤Æɸ½à²½¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¹¬¤¤¤Ê¤³¤È¤Ë¡¢ISO 9660
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¤Ï³ÈÄ¥µ¡¹½¤¬Ä󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£Å¬Àڤ˽ñ¤«¤ì¤¿ CD ¤Ï¡¢
 	³ÈÄ¥µ¡¹½¤ËÂбþ¤·¤¿¥·¥¹¥Æ¥à¤Ç¤Ï³ÈÄ¥¤òÍøÍѤ·¤Æ¡¢¤½¤¦¤Ç¤Ê¤¤¥·¥¹¥Æ¥à¤Ç¤Ï
 	³ÈÄ¥µ¡¹½¤ò»ÈÍѤ·¤Ê¤¤ÈϰϤÇÆ°ºî¤¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
       <indexterm>
 	<primary><filename role="package">sysutils/mkisofs</filename></primary>
       </indexterm>
       <para><filename role="package">sysutils/mkisofs</filename> ¥×¥í¥°¥é¥à¤Ï
 	ISO 9660 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò´Þ¤à¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë¤òºîÀ®¤¹¤ë¤Î¤Ë»È¤ï¤ì¤Þ¤¹¡£
 	¤³¤ì¤Ë¤ÏÍÍ¡¹¤Ê³ÈÄ¥¤ò¥µ¥Ý¡¼¥È¤¹¤ë¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¡¢
 	°Ê²¼¤ÇÀâÌÀ¤·¤Þ¤¹¡£ ¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤Ï¡¢ports ¤Î
 	<filename role="package">sysutils/mkisofs</filename>
 	¤«¤é¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <indexterm>
 	<primary>CD ¥é¥¤¥¿</primary>
 	<secondary>ATAPI</secondary>
       </indexterm>
 
       <para>CD ¤Ë½ñ¤­¹þ¤à¤¿¤á¤Î¥Ä¡¼¥ë¤Ï¡¢¤ª»È¤¤¤Î CD ¥é¥¤¥¿¤¬ ATAPI
 	Àܳ¤«Èݤ«¤Ë¤â°Í¸¤·¤Þ¤¹¡£ATAPI CD ¥é¥¤¥¿¤Ê¤é¡¢¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î°ìÉô¤Ç¤¢¤ë
 	<command><link linkend="burncd">burncd</link></command>
 	¥×¥í¥°¥é¥à¤ò»È¤¤¤Þ¤¹¡£SCSI ¤ä USB ¤Î CD ¥é¥¤¥¿¤Ê¤é¡¢ports ¤Î
 	<filename role="package">sysutils/cdrecord</filename>
 	¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ
 	<command><link linkend="cdrecord">cdrecord</link></command>
 	¥×¥í¥°¥é¥à¤ò»È¤¦¤Ù¤­¤Ç¤·¤ç¤¦¡£</para>
 
       <para><command>burncd</command>
 	¤¬Âбþ¤·¤Æ¤¤¤ë¥É¥é¥¤¥Ö¤Ï¸ÂÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£
 	¥É¥é¥¤¥Ö¤¬Âбþ¤µ¤ì¤Æ¤¤¤ë¤«¤É¤¦¤«¤ò³Îǧ¤¹¤ë¤Ë¤Ï¡¢
 	<ulink url="http://www.freebsd.dk/ata/">CD-R/RW supported
 	  drives</ulink> ¤Ë¤¢¤ë°ìÍ÷¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£</para>
 
       <note>
 	<indexterm>
 	  <primary>CD ¥é¥¤¥¿</primary>
 	  <secondary>ATAPI/CAM ¥É¥é¥¤¥Ð</secondary>
 	</indexterm>
 	<para>&os;&nbsp;5.X ¤Þ¤¿¤Ï &os;&nbsp;4.8-RELEASE
 	  °Ê¹ß¤Î¥Ð¡¼¥¸¥ç¥ó¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢
 	  <link linkend="atapicam">ATAPI/CAM ¥â¥¸¥å¡¼¥ë</link> ¤ò»ÈÍѤ¹¤ë¤È
 	  ATAPI ¥Ï¡¼¥É¥¦¥§¥¢¾å¤Ç SCSI ¥É¥é¥¤¥ÖÍѤÎ
 	  <command><link linkend="cdrecord">cdrecord</link></command>
 	  ¤ª¤è¤Ó¾¤Î¥Ä¡¼¥ë¤ò»ÈÍѤǤ­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
       </note>
     </sect2>
 
     <sect2 id="mkisofs">
       <title>mkisofs</title>
 
       <para><filename role="package">sysutils/mkisofs</filename> ¤Ï &unix;
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î̾Á°¶õ´Ö¤Ë¤ª¤±¤ë¥Ç¥£¥ì¥¯¥È¥ê¥Ä¥ê¡¼¤Î¥¤¥á¡¼¥¸¤È¤·¤Æ
 	ISO 9660 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤·¤Þ¤¹¡£
 	ºÇ¤â´Êñ¤Ê»È¤¤Êý¤Ï°Ê²¼¤ÎÄ̤ê¤Ç¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>mkisofs -o <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
 
       <indexterm>
 	<primary>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</primary>
 	<secondary>ISO 9660</secondary>
       </indexterm>
 
       <para>¤³¤Î¥³¥Þ¥ó¥É¤Ï <replaceable>/path/to/tree</replaceable>
 	°Ê²¼¤Î¥Ç¥£¥ì¥¯¥È¥ê¥Ä¥ê¡¼¤Î¥³¥Ô¡¼¤Ç¤¢¤ë ISO 9660
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò´Þ¤ó¤À <replaceable>imagefile.iso</replaceable>
 	¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Þ¤¹¡£¤³¤Î²áÄø¤Ë¤ª¤¤¤Æ¡¢¥Õ¥¡¥¤¥ë̾¤Ïɸ½àŪ¤Ê ISO 9660
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÀ©¸Â¤ËŬ¹ç¤¹¤ë¤è¤¦¤Ê¥Õ¥¡¥¤¥ë̾¤ËÂбþ¤Å¤±¤é¤ì¡¢
 	ISO ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¥Õ¥¡¥¤¥ë̾¤òʸ»ú²½¤Ç¤­¤Ê¤¤¥Õ¥¡¥¤¥ë¤Ï½ü³°¤µ¤ì¤Þ¤¹¡£</para>
 
       <indexterm>
 	<primary>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</primary>
 	<secondary>HFS</secondary>
       </indexterm>
       <indexterm>
 	<primary>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</primary>
 	<secondary>Joliet</secondary>
       </indexterm>
 
       <para>¤³¤ÎÀ©¸Â¤ò²óÈò¤¹¤ë¤¿¤á¤ËÍøÍѤǤ­¤ë¥ª¥×¥·¥ç¥ó¤Ï¤¤¤¯¤Ä¤â¤¢¤ê¤Þ¤¹¡£
 	ÆÃ¤Ë <option>-R</option> ¥ª¥×¥·¥ç¥ó¤Ï &unix; ¥·¥¹¥Æ¥à¤Çɸ½àŪ¤Ê Rock Ridge
 	³ÈÄ¥¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£<option>-J</option> ¥ª¥×¥·¥ç¥ó¤Ï Microsoft
 	¤Î¥·¥¹¥Æ¥à¤Çɸ½àŪ¤Ê Joliet ³ÈÄ¥¤òÍ­¸ú¤Ë¤·¡¢
 	<option>-hfs</option> ¥ª¥×¥·¥ç¥ó¤Ï &macos; ¤Ç»ÈÍѤµ¤ì¤Æ¤¤¤ë
 	HFS ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£</para>
 
       <para>FreeBSD ¤Ç¤·¤«»È¤ï¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢<option>-U</option>
 	¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë¤È¤¢¤é¤æ¤ë¥Õ¥¡¥¤¥ë̾À©¸Â¤ò̵¸ú¤Ë¤Ç¤­¤Þ¤¹¡£
 	¤µ¤é¤Ë <option>-R</option> ¥ª¥×¥·¥ç¥ó¤È¤È¤â¤Ë»È¤¦¤³¤È¤Ç
 	FreeBSD ¤ÈƱ°ì¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¤¥á¡¼¥¸¤òºîÀ®¤Ç¤­¤Þ¤¹¤¬¡¢
 	¤³¤ì¤Ï ISO 9660 ɸ½à¤Î¿¤¯¤ò̵»ë¤·¤Æ¤¤¤Þ¤¹¡£</para>
 
       <indexterm>
 	<primary>CDROM</primary>
 	<secondary>¥Ö¡¼¥¿¥Ö¥ë (µ¯Æ°²Äǽ¤Ê) CDROM ¤ÎºîÀ®</secondary>
       </indexterm>
       <para>°ìÈÌŪ¤Ë»È¤ï¤ì¤ëºÇ¸å¤Î¥ª¥×¥·¥ç¥ó¤Ï <option>-b</option> ¥ª¥×¥·¥ç¥ó¤Ç¤¹¡£
 	¤³¤ì¤Ï <quote>El Torito</quote>	¥Ö¡¼¥¿¥Ö¥ë CD
 	¤òºîÀ®¤¹¤ë¤Î¤Ë»È¤¦µ¯Æ°¥¤¥á¡¼¥¸¤Î¤¢¤ê¤«¤ò»ØÄꤷ¤Þ¤¹¡£
 	¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï°ú¿ô¤È¤·¤Æµ¯Æ°¥¤¥á¡¼¥¸¤Ø¤Î¥Ñ¥¹¤ò¡¢
 	CD ¤Ë½ñ¤­¹þ¤Þ¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¥Ä¥ê¡¼¤ÎĺÅÀ¤«¤é¤ÎÁêÂаÌÃ֤Ǽè¤ê¤Þ¤¹¡£
 	¤·¤¿¤¬¤Ã¤Æ <filename>/tmp/myboot</filename> ¤¬¥Ö¡¼¥È²Äǽ¤Ê
 	FreeBSD ¥·¥¹¥Æ¥à¤Ç <filename>/tmp/myboot/boot/cdboot</filename>
 	¤Ë¥Ö¡¼¥È¥¤¥á¡¼¥¸¤¬¤¢¤ë¤Ê¤é¤Ð¡¢°Ê²¼¤Î¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ç ISO 9660
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¤¥á¡¼¥¸¤ò <filename>/tmp/bootable.iso</filename>
 	¤ËºîÀ®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>mkisofs -U -R -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot</userinput></screen>
 
       <para>¤³¤Î¸å¡¢¥«¡¼¥Í¥ë¤Ç <devicename>vn</devicename> (FreeBSD&nbsp;4.X)
 	¤Þ¤¿¤Ï <devicename>md</devicename> (FreeBSD&nbsp;5.X)
 	¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>vnconfig -e vn0c /tmp/bootable.iso</userinput>
 &prompt.root; <userinput>mount -t cd9660 /dev/vn0c /mnt</userinput></screen>
 
       <para>FreeBSD&nbsp;4.X ¤ª¤è¤Ó FreeBSD&nbsp;5.X ¤ËÂФ·¤Æ¤Ï°Ê²¼¤ÎÄ̤ê¤Ç¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>mdconfig -a -t vnode -f /tmp/bootable.iso -u 0</userinput>
 &prompt.root; <userinput>mount -t cd9660 /dev/md0 /mnt</userinput></screen>
 
       <para><filename>/mnt</filename> ¤È
 	<filename>/tmp/myboot</filename> ¤¬Æ±°ì¤«¤É¤¦¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
     <para><filename role="package">sysutils/mkisofs</filename>
       ¤Ë¤ÏµóÆ°¤òºÙ¤«¤¯À©¸æ¤¹¤ë¤¿¤á¤Ë¾¤Ë¤â¤¿¤¯¤µ¤ó¤Î¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£
       Æäˡ¢ISO 9660
       ¥ì¥¤¥¢¥¦¥È¤ÎÊѹ¹¤ä Joliet ¤ª¤è¤Ó HFS ¥Ç¥£¥¹¥¯ºîÀ®¤Ê¤É¤Î
       ¾ÜºÙ¤Ï &man.mkisofs.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
     </sect2>
 
     <sect2 id="burncd">
       <title>burncd</title>
       <indexterm>
 	<primary>CDROM</primary>
 	<secondary>½ñ¤­¹þ¤ß</secondary>
       </indexterm>
       <para>¤¢¤Ê¤¿¤¬»ý¤Ã¤Æ¤¤¤ë¤Î¤¬ ATAPI CD ¥é¥¤¥¿¤Ê¤é¡¢CD ¤Ë ISO
 	¥¤¥á¡¼¥¸¤ò½ñ¤­¹þ¤à¤¿¤á¤Ë <command>burncd</command> ¥³¥Þ¥ó¥É¤¬»È¤¨¤Þ¤¹¡£
 	<command>burncd</command> ¤Ï¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î°ìÉô¤Ç
 	<filename>/usr/sbin/burncd</filename> ¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
 	»È¤¤Êý¤Ï¤È¤Æ¤âñ½ã¤Ç¥ª¥×¥·¥ç¥ó¤â¾¯¤·¤·¤«¤¢¤ê¤Þ¤»¤ó¡£</para>
 
       <screen>&prompt.root; <userinput>burncd -f <replaceable>cddevice</replaceable> data <replaceable>imagefile.iso</replaceable> fixate</userinput></screen>
 
       <para>°Ê¾å¤Î¥³¥Þ¥ó¥É¤Ï <replaceable>imagefile.iso</replaceable>
 	¤Î¥³¥Ô¡¼¤ò <replaceable>cddevice</replaceable> ¤Ë½ñ¤­¹þ¤ß¤Þ¤¹¡£
 	¥Ç¥Õ¥©¥ë¥È¤Î¥Ç¥Ð¥¤¥¹¤Ï <filename>/dev/acd0c</filename> ¤Ç¤¹¡£
 	½ñ¤­¹þ¤ß®ÅÙ¤äÁàºî´°Î»¸å¤Ë CD ¤ò¼«Æ°Åª¤Ë¼è¤ê½Ð¤¹ÊýË¡¡¢
 	¥ª¡¼¥Ç¥£¥ª¥Ç¡¼¥¿¤Î½ñ¤­¹þ¤ß¤Ê¤É¤Î¥ª¥×¥·¥ç¥ó¤Ë¤Ä¤¤¤Æ¤Ï &man.burncd.8;
 	¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£</para>
     </sect2>
 
     <sect2 id="cdrecord">
       <title>cdrecord</title>
 
       <para>¤¢¤Ê¤¿¤¬»ý¤Ã¤Æ¤¤¤ë CD ¥é¥¤¥¿¤¬ ATAPI ¤Ç¤Ï¤Ê¤±¤ì¤Ð¡¢
 	CD ¤ò½ñ¤­¹þ¤à¤Î¤Ë <command>cdrecord</command> ¤ò»È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
 	<command>cdrecord</command> ¤Ï¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î°ìÉô¤Ç¤Ï¤Ê¤¯¡¢
 	<filename role="package">sysutils/cdrtools</filename> ¤Î port ¤Þ¤¿¤Ï
 	ŬÀÚ¤Ê package ¤òÍøÍѤ·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
 	¤Ê¤ª¡¢¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤òÊѹ¹¤¹¤ë¤È¥Ð¥¤¥Ê¥ê¤ËÌ·½â¤¬È¯À¸¤·¡¢
 	<quote>¥³¡¼¥¹¥¿¡¼</quote> ¤òºî¤Ã¤Æ¤·¤Þ¤¦¤ª¤½¤ì¤¬¤¢¤ê¤Þ¤¹¡£
 	¤·¤¿¤¬¤Ã¤Æ¡¢¥·¥¹¥Æ¥à¤ò¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ëÅ٤ˤ³¤Î port ¤âºî¤êľ¤¹¤«¡¢
 	¤¢¤ë¤¤¤Ï<link
 	linkend="stable">FreeBSD ¤Î°ÂÄêÈǤòÄɤ¤¤«¤±¤Æ¤¤¤ë</link>¤Î¤Ê¤é¤Ð¡¢
 	¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤¬ÍøÍѤǤ­¤ë¤è¤¦¤Ë¤Ê¤Ã¤¿»þ¤Ë ports
 	¤ò¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
       <para><command>cdrecord</command> ¤Ë¤Ï¤¿¤¯¤µ¤ó¤Î¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¤¬¡¢
 	´ðËÜŪ¤Ê»È¤¤Êý¤Ï <command>burncd</command> ¤è¤ê¤â¤µ¤é¤Ë´Êñ¤Ç¤¹¡£
 	ISO 9660 ¥¤¥á¡¼¥¸¤ò½ñ¤­¹þ¤à¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>cdrecord dev=<replaceable>device</replaceable> <replaceable>imagefile.iso</replaceable></userinput></screen>
 
       <para><command>cdrecord</command> ¤Î¥È¥ê¥Ã¥­¡¼¤ÊÉôʬ¤Ï¡¢»ÈÍѤ¹¤ë
 	<option>dev</option> ¤ò¸«¤Ä¤±¤ë¤È¤³¤í¤Ë¤¢¤ê¤Þ¤¹¡£
 	ŬÀÚ¤ÊÀßÄê¤ò¸«¤Ä¤±¤ë¤¿¤á¤Ë¤Ï <command>cdrecord</command> ¤Î
 	<option>-scanbus</option> ¥Õ¥é¥°¤ò»È¤¤¤Þ¤¹¡£
 	¤¿¤È¤¨¤Ð¡¢°Ê²¼¤Î¤è¤¦¤Ê·ë²Ì¤¬½ÐÎϤµ¤ì¤ë¤Ç¤·¤ç¤¦¡£</para>
 
       <indexterm>
 	<primary>CDROM</primary>
 	<secondary>½ñ¤­¹þ¤ß</secondary>
       </indexterm>
       <screen>&prompt.root; <userinput>cdrecord -scanbus</userinput>
 Cdrecord 1.9 (i386-unknown-freebsd4.2) Copyright (C) 1995-2000 J&ouml;rg Schilling
 Using libscg version 'schily-0.1'
 scsibus0:
         0,0,0     0) 'SEAGATE ' 'ST39236LW       ' '0004' Disk
         0,1,0     1) 'SEAGATE ' 'ST39173W        ' '5958' Disk
         0,2,0     2) *
         0,3,0     3) 'iomega  ' 'jaz 1GB         ' 'J.86' Removable Disk
         0,4,0     4) 'NEC     ' 'CD-ROM DRIVE:466' '1.26' Removable CD-ROM
         0,5,0     5) *
         0,6,0     6) *
         0,7,0     7) *
 scsibus1:
         1,0,0   100) *
         1,1,0   101) *
         1,2,0   102) *
         1,3,0   103) *
         1,4,0   104) *
         1,5,0   105) 'YAMAHA  ' 'CRW4260         ' '1.0q' Removable CD-ROM
         1,6,0   106) 'ARTEC   ' 'AM12S           ' '1.06' Scanner
         1,7,0   107) *</screen>
 
       <para>¥ê¥¹¥È¤Ë¤¢¤ë¥Ç¥Ð¥¤¥¹¤ËÂФ¹¤ëŬÀÚ¤Ê <option>dev</option>
 	¤ÎÃͤ¬¤³¤³¤Ë¼¨¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤¢¤Ê¤¿¤Î CD ¥é¥¤¥¿¤ò¤³¤Î¥ê¥¹¥È¤«¤é¸«¤Ä¤±¡¢
 	¥«¥ó¥Þ¤Ç¶èÀÚ¤é¤ì¤¿ 3 ¤Ä¤Î¿ôÃͤò <option>dev</option>
 	¤ÎÃͤȤ·¤Æ»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£¤³¤ÎÎã¤Ç¤Ï CRW ¥Ç¥Ð¥¤¥¹¤Ï 1,5,0
 	¤Ê¤Î¤Ç¡¢Å¬ÀÚ¤ÊÆþÎÏ¤Ï <option>dev=1,5,0</option> ¤È¤Ê¤ê¤Þ¤¹¡£
 	ÃͤòÌÀ¼¨¤¹¤ë¤â¤Ã¤È´Êñ¤ÊÊýË¡¤â¤¢¤ê¤Þ¤¹¡£¾ÜºÙ¤Ï &man.cdrecord.1;
 	¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£¤½¤³¤Ë¤Ï¥ª¡¼¥Ç¥£¥ª¥È¥é¥Ã¥¯¤ò½ñ¤­¹þ¤àÊýË¡¤ä¡¢
 	½ñ¤­¹þ¤ß®ÅÙ¤½¤Î¾¤òÁàºî¤¹¤ëÊýË¡¤â½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2 id="duplicating-audiocds">
       <title>¥ª¡¼¥Ç¥£¥ª CD ¤ÎÊ£À½</title>
 
       <para>CD ¤«¤é¥ª¡¼¥Ç¥£¥ª¥Ç¡¼¥¿¤òϢ³¤·¤¿¥Õ¥¡¥¤¥ë¤ËŸ³«¤·¡¢¥Ö¥é¥ó¥¯ CD
 	¤Ë¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤ò½ñ¤­¹þ¤à¤³¤È¤Ç¡¢¥ª¡¼¥Ç¥£¥ª CD
 	¤òÊ£À½¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	¤³¤Î¼ê½ç¤Ï ATAPI ¤ª¤è¤Ó SCSI ¥É¥é¥¤¥Ö¤Î´Ö¤Ç¾¯¤·°Û¤Ê¤ê¤Þ¤¹¡£</para>
 
       <procedure>
 	<title>SCSI ¥É¥é¥¤¥Ö</title>
 
 	<step>
 	  <para><command>cdda2wav</command> ¤ò»ÈÍѤ·¤Æ¥ª¡¼¥Ç¥£¥ª¤òŸ³«¤·¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.user; <userinput>cdda2wav -v255 -D2,0 -B -Owav</userinput></screen>
 	</step>
 
 	<step>
 	  <para><command>cdrecord</command> ¤ò»ÈÍѤ·¤Æ
 	    <filename>.wav</filename> ¥Õ¥¡¥¤¥ë¤Ë½ñ¤­½Ð¤·¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.user; <userinput>cdrecord -v dev=<replaceable>2,0</replaceable> -dao -useinfo  *.wav</userinput></screen>
 
 	  <para><xref linkend="cdrecord"/> ¤ËÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë
 	    <replaceable>2.0</replaceable>
 	    ¤¬Å¬Àڤ˻ØÄꤵ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Î¤«¤á¤Æ¤¯¤À¤µ¤¤¡£</para>
 	</step>
       </procedure>
 
       <procedure>
 	<title>ATAPI ¥É¥é¥¤¥Ö</title>
 
 	<step>
 	  <para>ATAPI CD ¥É¥é¥¤¥Ð¤Ç¤Ï¡¢¤½¤ì¤¾¤ì¤Î¥È¥é¥Ã¥¯¤ò
 	    <filename>/dev/acd<replaceable>d</replaceable>t<replaceable>nn</replaceable></filename> ¤Î¤è¤¦¤ËÍøÍѤǤ­¤Þ¤¹¡£
 	    ¤³¤³¤Ç <replaceable>d</replaceable> ¤Ï¥É¥é¥¤¥ÖÈÖ¹æ¤Ç¤¢¤ê¡¢
 	    <replaceable>nn</replaceable> ¤ÏÆó·å½½¿Ê¤Î¥È¥é¥Ã¥¯ÈÖ¹æ¤Ç¤¹¡£
 	    °ì·å¤Î¾ì¹ç 0 ¤òÁ°¤ËÉղ乤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	    ¤·¤¿¤¬¤Ã¤Æ¡¢°ìÈÖÌܤΥǥ£¥¹¥¯¤Î°ìÈÖÌܤΥȥé¥Ã¥¯¤Ï
 	    <filename>/dev/acd0t01</filename>¡¢ÆóÈÖÌܤΥȥé¥Ã¥¯¤Ï
 	    <filename>/dev/acd0t02</filename>¡¢»°ÈÖÌܤΥȥé¥Ã¥¯¤Ï
 	    <filename>/dev/acd0t03</filename> ¤Ê¤É¤È¤Ê¤ê¤Þ¤¹¡£</para>
 
 	  <para>ŬÀڤʥǥХ¤¥¹¥Õ¥¡¥¤¥ë¤¬ <filename>/dev</filename>
 	    ¤Ë¸ºß¤¹¤ë¤³¤È¤ò³Î¤«¤á¤Æ¤¯¤À¤µ¤¤¡£
 	    ¸ºß¤·¤Ê¤±¤ì¤Ð¡¢¤¿¤È¤¨¤Ð¼¡¤Î¤è¤¦¤Ë¤·¤ÆºîÀ®¤·¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV acd0t99</userinput></screen>
 
 	  <note><para>FreeBSD 5.0 ¤Ç¤Ï &man.devfs.5; ¤¬
 	      <filename>/dev</filename> ¤Ë¥¨¥ó¥È¥ê¤ò¼«Æ°Åª¤ËºîÀ®¡¢
 	      ´ÉÍý¤¹¤ë¤Î¤Ç¡¢<command>MAKEDEV</command>
 	      ¤ò»ÈÍѤ¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£</para></note>
 	</step>
 
 	<step>
 	  <para>&man.dd.1; ¤ò»ÈÍѤ·¤Æ³Æ¥È¥é¥Ã¥¯¤òŸ³«¤·¤Þ¤¹¡£
 	    ¥Õ¥¡¥¤¥ë¤òŸ³«¤¹¤ëºÝ¡¢¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤ò»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
 	  <screen>&prompt.root; <userinput>dd if=/dev/acd0t01 of=track1.cdr bs=2352</userinput>
 &prompt.root; <userinput>dd if=/dev/acd0t02 of=track2.cdr bs=2352</userinput>
 ...</screen>
 	</step>
 
 	<step>
 	  <para><command>burncd</command> ¤ò»ÈÍѤ·¤Æ¡¢
 	    Ÿ³«¤·¤¿¥Õ¥¡¥¤¥ë¤ò¥Ç¥£¥¹¥¯¤Ë½ñ¤­¹þ¤ß¤Þ¤¹¡£
 	    ¤³¤ì¤é¤¬¥ª¡¼¥Ç¥£¥ª¥Õ¥¡¥¤¥ë¤Ç¤¢¤ë¤³¤È¡¢
 	    ¤½¤·¤Æ½ñ¤­¹þ¤ß¤¬½ªÎ»¤·¤¿¤È¤­¤Ë <command>burncd</command>
 	    ¤¬¥Ç¥£¥¹¥¯¤ò¸ÇÄê (fixate) ¤¹¤ë¤³¤È¤òÌÀ¼¨¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
 	  <screen>&prompt.root; <userinput>burncd -f <replaceable>/dev/acd0c</replaceable> audio track1.cdr track2.cdr <replaceable>...</replaceable> fixate</userinput></screen>
 	</step>
       </procedure>
     </sect2>
 
     <sect2 id="imaging-cd">
       <title>¥Ç¡¼¥¿ CD ¤ÎÊ£À½</title>
 
       <para>¥Ç¡¼¥¿ CD ¤ò¡¢<filename role="package">sysutils/mkisofs</filename>
 	¤òÍѤ¤¤ÆºîÀ®¤µ¤ì¤¿¥¤¥á¡¼¥¸¥Õ¥¡¥¤¥ë¤Èµ¡Ç½Åª¤ËÅù²Á¤Ê¥¤¥á¡¼¥¸¥Õ¥¡¥¤¥ë¤Ë¥³¥Ô¡¼¤Ç¤­¤Þ¤¹¡£
 	¤³¤ì¤ò»ÈÍѤ·¤Æ¡¢¤¹¤Ù¤Æ¤Î¥Ç¡¼¥¿ CD ¤òÊ£À½¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	¤³¤³¤Ç¤ÎÎã¤Ï CDROM ¥Ç¥Ð¥¤¥¹¤¬ <devicename>acd0</devicename>
 	¤Ç¤¢¤ë¤È¤·¤Æ¤¤¤Þ¤¹¡£¤¢¤Ê¤¿¤Î CDROM ¥Ç¥Ð¥¤¥¹¤ËÆɤßÂؤ¨¤Æ¤¯¤À¤µ¤¤¡£
 	CDROM ¤Î¾ì¹ç¤Ë¤Ï¡¢¥Ñ¡¼¥Æ¥£¥·¥ç¥óÁ´ÂΤޤ¿¤Ï¥Ç¥£¥¹¥¯Á´ÂÎ
 	¤ò»ØÄꤹ¤ë¤¿¤á¤Ë <literal>c</literal>
 	¤ò¥Ç¥Ð¥¤¥¹Ì¾¤Î¸å¤ËÄɲ䷤ʤ±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
       <screen>&prompt.root; <userinput>dd if=/dev/acd0c of=file.iso bs=2048</userinput></screen>
 
       <para>¤³¤ì¤Ç¥Ç¥£¥¹¥¯¥¤¥á¡¼¥¸¤ò¼è¤ê½Ð¤¹¤³¤È¤¬¤Ç¤­¤Þ¤·¤¿¡£
 	¤¹¤Ç¤ËÀâÌÀ¤·¤¿ÊýË¡¤òÍѤ¤¤Æ CD ¤Ë½ñ¤­¹þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2 id="mounting-cd">
       <title>¥Ç¡¼¥¿ CD ¤Î»ÈÍÑ</title>
 
       <para>¤µ¤Æ¡¢É¸½àŪ¤Ê¥Ç¡¼¥¿ CDROM ¤òºîÀ®¤·¤¿¤Î¤Ç¡¢
 	¤ª¤½¤é¤¯¼¡¤Ï¤½¤ì¤ò¥Þ¥¦¥ó¥È¤·¤Æ¥Ç¡¼¥¿¤òÆɤ߽Ф·¤¿¤¤¤È»×¤¦¤Ç¤·¤ç¤¦¡£
 	¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï &man.mount.8; ¤Ï¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¿¥¤¥×¤ò
 	<literal>ufs</literal> ¤È¤·¤Æ¤¤¤Þ¤¹¡£
 	¼¡¤Î¤è¤¦¤Ë¼Â¹Ô¤·¤è¤¦¤È¤¹¤ë¤È¡¢</para>
 
       <screen>&prompt.root; <userinput>mount /dev/cd0c /mnt</userinput></screen>
 
       <para><errorname>Incorrect super block</errorname>
 	¤È¤¤¤¦¥¨¥é¡¼¤¬ÊÖ¤µ¤ì¤Æ¥Þ¥¦¥ó¥È¤Ç¤­¤Ê¤¤¤Ç¤·¤ç¤¦¡£
 	CDROM ¤Ï <literal>UFS</literal> ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤Ï¤Ê¤¤¤¿¤á¤Ë¡¢
 	¤³¤Î¤è¤¦¤Ê¼ê½ç¤Ç¥Þ¥¦¥ó¥È¤·¤è¤¦¤¹¤ë¤È¼ºÇÔ¤·¤Þ¤¹¡£
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¿¥¤¥×¤¬ <literal>ISO9660</literal> ¤Ç¤¢¤ë¤È
 	&man.mount.8; ¤Ë¶µ¤¨¤µ¤¨¤¹¤ì¤Ð¡¢¤¹¤Ù¤Æ¤Ï¤¦¤Þ¤¯Æ°ºî¤·¤Þ¤¹¡£
 	&man.mount.8; ¤Ë <option>-t cd9660</option>
 	¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤³¤È¤Ç¤³¤ì¤ò¹Ô¤¤¤Þ¤¹¡£
 	¤¿¤È¤¨¤Ð <devicename>/dev/cd0c</devicename> ¤Î CDROM ¥Ç¥Ð¥¤¥¹¤ò
 	<filename>/mnt</filename> ¤Ë¥Þ¥¦¥ó¥È¤·¤¿¤¤¾ì¹ç¤Ï¡¢
 	°Ê²¼¤Î¤è¤¦¤Ë¼Â¹Ô¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0c /mnt</userinput></screen>
 
       <para>»ÈÍѤ·¤Æ¤¤¤ë CDROM ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ë¤è¤Ã¤Æ¤Ï¡¢
 	¥Ç¥Ð¥¤¥¹Ì¾
 	(¤³¤ÎÎã¤Ç¤Ï <devicename>/dev/cd0c</devicename>)
 	¤¬°Û¤Ê¤ë¤«¤â¤·¤ì¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
 	¤Þ¤¿¡¢<option>-t cd9660</option> ¥ª¥×¥·¥ç¥ó¤Ï¡¢Ã±¤Ë
 	&man.mount.cd9660.8; ¤ò¼Â¹Ô¤·¤Þ¤¹¡£
 	¤³¤ÎÎã¤ò°Ê²¼¤Î¤è¤¦¤Ëû½Ì¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>mount_cd9660 /dev/cd0c /mnt</userinput></screen>
 
       <para>°ìÈÌŪ¤Ë¤³¤ÎÊýË¡¤Ç¤Ï¡¢¤¹¤Ù¤Æ¤Î¥á¡¼¥«¤Î ¥Ç¡¼¥¿ CDROM
 	¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤·¤«¤·¤Ê¤¬¤é¡¢ÆÃÄê¤Î ISO 9660
 	³ÈÄ¥¤¬»Ü¤µ¤ì¤¿¥Ç¥£¥¹¥¯¤Ç¤Ï´ñ̯¤ÊÆ°ºî¤ò¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
 	¤¿¤È¤¨¤Ð Joliet ¥Ç¥£¥¹¥¯¤Ï¡¢
 	¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë̾¤ò 2 ¥Ð¥¤¥È¤Î Unicode ʸ»ú¤Ç³ÊǼ¤·¤Þ¤¹¡£
 	FreeBSD ¥«¡¼¥Í¥ë¤Ï (¤Þ¤À) Unicode ¤òÍý²ò¤Ç¤­¤Ê¤¤¤Î¤Ç¡¢
 	Èó±Ñ¸ìʸ»ú¤Ï¥¯¥¨¥¹¥Á¥ç¥ó¥Þ¡¼¥¯¤Çɽ¼¨¤µ¤ì¤Þ¤¹
 	(FreeBSD 4.3 °Ê¹ß¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢CD9660 ¥É¥é¥¤¥Ð¤Ë¤ÏŬÀÚ¤Ê Unicode
 	ÊÑ´¹É½¤òÆɤ߹þ¤à¤¿¤á¤ÎµÞ¤´¤·¤é¤¨¤Î¥Õ¥Ã¥¯¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
 	¤¤¤¯¤Ä¤«¤Î¶¦Ä̤Υ¨¥ó¥³¡¼¥É¤ËÂФ¹¤ë¥â¥¸¥å¡¼¥ë¤Ï
 	<filename role="package">sysutils/cd9660_unicode</filename> port
 	¤«¤éÍøÍѲÄǽ¤Ç¤¹)¡£</para>
 
       <para>CDROM ¤ò¥Þ¥¦¥ó¥È¤·¤è¤¦¤È¤¹¤ë»þ¤Ë¡¢
 	<errorname>Device not configured</errorname>
 	¤Èɽ¼¨¤µ¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¤³¤ì¤Ï¡¢¥Ç¥£¥¹¥¯¤¬¥È¥ì¡¼¤Ë¤Ê¤¤¤È
 	CDROM ¥É¥é¥¤¥Ö¤¬È½ÃǤ·¤Æ¤¤¤ë¤«¡¢
 	¥É¥é¥¤¥Ö¤¬¥Ð¥¹¾å¤Ëǧ¼±¤Ç¤­¤Ê¤¤¤³¤È¤òÄ̾ï°ÕÌ£¤·¤Þ¤¹¡£
 	¥Ç¥£¥¹¥¯¤¬ÁÞÆþ¤µ¤ì¤¿¤³¤È¤ò CDROM ¥É¥é¥¤¥Ö¤¬Ç§¼±¤¹¤ë¤Ë¤Ï¿ôÉ䫤«¤ê¤Þ¤¹¤Î¤Ç¡¢
 	¿ÉÊú¶¯¤¯ÂԤäƤ¯¤À¤µ¤¤¡£</para>
 
       <para>¥Ð¥¹¤Î¥ê¥»¥Ã¥È¤ËÊÖÅú¤¹¤ë¤¿¤á¤Î¥¿¥¤¥à¥¢¥¦¥È¤¬Ã»¤¤¤¿¤á¤Ë¡¢»þ¡¹ SCSI
 	CDROM ¤Ïǧ¼±¤Ë¼ºÇÔ¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£SCSI CDROM ¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
 	¼¡¤Î¥ª¥×¥·¥ç¥ó¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥®¥å¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤ËÄɲ䷤ơ¢
 	<link linkend="kernelconfig-building">¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤</link>¡£</para>
 
       <programlisting>options SCSI_DELAY=15000</programlisting>
 
       <para>¤³¤ì¤è¤ê¡¢SCSI ¥Ð¥¹¤òµ¯Æ°»þ¤Ë 15 ÉôÖÄä»ß¤µ¤»¤Æ¡¢
 	CDROM ¥É¥é¥¤¥Ö¤¬¥Ð¥¹¥ê¥»¥Ã¥È¤Ë±þÅú¤¹¤ëµ¡²ñ¤òÍ¿¤¨¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2 id="rawdata-cd">
       <title>Raw ¥Ç¡¼¥¿ CD ¤Î½ñ¤­¹þ¤ß</title>
 
       <para>ISO 9660 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤³¤È̵¤¯¡¢
 	¥Õ¥¡¥¤¥ë¤òľÀÜ CD ¤Ë½ñ¤­¹þ¤à¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
 	¤³¤ÎÊýË¡¤ò¥Ð¥Ã¥¯¥¢¥Ã¥×ÌÜŪ¤Ë»ÈÍѤ·¤Æ¤¤¤ë¿Í¤â¤¤¤Þ¤¹¡£
 	¤³¤ì¤Ï¡¢É¸½à CD ¤ò½ñ¤­¹þ¤à¤è¤ê¤â¤µ¤é¤Ë®¤¯¼Â¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>burncd -f /dev/acd1c -s 12 data archive.tar.gz fixate</userinput></screen>
 
       <para>¤³¤Î¤è¤¦¤Ë CD ¤Ë½ñ¤­¹þ¤Þ¤ì¤¿¥Ç¡¼¥¿¤ò¼èÆÀ¤¹¤ë¤Ë¤Ï¡¢
 	raw ¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤«¤é¥Ç¡¼¥¿¤òÆɤ߹þ¤Þ¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
       <screen>&prompt.root; <userinput>tar xzvf /dev/acd1c</userinput></screen>
 
       <para>¤³¤Î¥Ç¥£¥¹¥¯¤òÄ̾ï¤Î CDROM ¤È¤·¤Æ¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
 	¤³¤Î¤è¤¦¤Ê CDROM ¤Ï FreeBSD ¤ò½ü¤¤¤Æ¡¢
 	¾¤Î¤¹¤Ù¤Æ¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ç¤ÏÆɤ߹þ¤à¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
 	CD ¤ò¥Þ¥¦¥ó¥È¤·¤¿¤¤¤«¡¢
 	¤½¤Î¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤È¥Ç¡¼¥¿¤ò¶¦Í­¤·¤¿¤¤¾ì¹ç¤Ï¡¢
 	¾åµ­¤ËÀâÌÀ¤·¤¿¤è¤¦¤Ë
 	<filename role="package">sysutils/mkisofs</filename>
 	¤ò»ÈÍѤ·¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£</para>
     </sect2>
 
     <sect2 id="atapicam">
       <title>ATAPI/CAM ¥É¥é¥¤¥Ð¤Î»ÈÍÑ</title>
 
       <indexterm>
 	<primary>CD ¥é¥¤¥¿</primary>
 	<secondary>ATAPI/CAM ¥É¥é¥¤¥Ð</secondary>
       </indexterm>
 
       <para>¤³¤Î¥É¥é¥¤¥Ð¤Ï¡¢ATAPI ¥Ç¥Ð¥¤¥¹ (CD-ROM, CD-RW, DVD ¥É¥é¥¤¥Ö¤Ê¤É)
 	¤Ø SCSI ¥µ¥Ö¥·¥¹¥Æ¥à¤òÄ̤¸¤Æ¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£
 	¤³¤ì¤Ë¤è¤ê¡¢<filename role="package">sysutils/cdrdao</filename> ¤Þ¤¿¤Ï
 	&man.cdrecord.1; ¤Î¤è¤¦¤Ê¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤¬»ÈÍѤǤ­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
 
       <para>¤³¤Î¥É¥é¥¤¥Ð¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢
 	¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥®¥å¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë¼¡¤Î¹Ô¤òÄɲ乤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
       <programlisting>device atapicam
 device scbus
 device cd
 device pass</programlisting>
 
       <para>¼¡¤Î¹Ô¤â¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥®¥å¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤ËɬÍפǤ¹¡£</para>
 
       <programlisting>device ata
 device atapicd</programlisting>
 
       <para>ξÊý¤¬¤¹¤Ç¤Ë¸ºß¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
       <para>¤½¤ì¤«¤éºÆ¹½ÃÛ¤·¡¢¿·¤·¤¤¥«¡¼¥Í¥ë¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢
 	¥³¥ó¥Ô¥å¡¼¥¿¤òºÆµ¯Æ°¤·¤Þ¤¹¡£
 	µ¯Æ°¥×¥í¥»¥¹Ãæ¤Ë¥Ç¥£¥¹¥¯¥é¥¤¥¿¤Ï°Ê²¼¤Î¤è¤¦¤Ëɽ¼¨¤µ¤ì¤ë¤Ç¤·¤ç¤¦¡£</para>
 
       <screen>acd0: CD-RW &lt;MATSHITA CD-RW/DVD-ROM UJDA740&gt; at ata1-master PIO4
 cd0 at ata1 bus 0 target 0 lun 0
 cd0: &lt;MATSHITA CDRW/DVD UJDA740 1.00&gt; Removable CD-ROM SCSI-0 device
 cd0: 16.000MB/s transfers
 cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed</screen>
 
       <para>¥É¥é¥¤¥Ö¤Ï <filename>/dev/cd0</filename>
 	¥Ç¥Ð¥¤¥¹¤òÄ̤¸¤Æ¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤¬²Äǽ¤È¤Ê¤ê¤Þ¤¹¡£
 	¤¿¤È¤¨¤Ð¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Æ CD-ROM ¤ò <filename>/mnt</filename>
 	¤Ë¥Þ¥¦¥ó¥È¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>mount -t cd9660 <replaceable>/dev/cd0c</replaceable> /mnt</userinput></screen>
 
       <para><username>root</username> ¸¢¸Â¤Ç¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¡¢
 	¥é¥¤¥¿¤Î SCSI ¥¢¥É¥ì¥¹¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>camcontrol devlist</userinput>
 &lt;MATSHITA CDRW/DVD UJDA740 1.00&gt;   at scbus1 target 0 lun 0 (pass0,cd0)</screen>
 
       <para>¤·¤¿¤¬¤Ã¤Æ¡¢<literal>1,0,0</literal> ¤¬ &man.cdrecord.1;
 	¤ª¤è¤Ó¤½¤Î¾¤Î SCSI ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ç»ÈÍѤ¹¤ë SCSI ¥¢¥É¥ì¥¹¤Ç¤¹¡£</para>
 
       <para>ATAPI/CAM ¤ª¤è¤Ó SCSI ¥·¥¹¥Æ¥à¤Î¾ÜºÙ¤Ï &man.atapicam.4; ¤ª¤è¤Ó
 	&man.cam.4; ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
     </sect2>
   </sect1>
 
   <sect1 id="floppies">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Julio</firstname>
 	  <surname>Merino</surname>
 	  <contrib>¸¶ºî: </contrib>
 	</author>
       </authorgroup>
       <!-- 24 Dec 2001 -->
       <authorgroup>
 	<author>
 	  <firstname>Martin</firstname>
 	  <surname>Karlsson</surname>
 	  <contrib>²þÄû: </contrib>
 	</author>
       </authorgroup>
       <!-- 27 Apr 2003 -->
     </sect1info>
 
     <title>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ÎºîÀ®¤È»ÈÍÑ</title>
 
     <para>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë¥Ç¡¼¥¿¤ò³ÊǼ¤¹¤ë¤³¤È¤Ï¤·¤Ð¤·¤ÐÌò¤Ë¤¿¤Á¤Þ¤¹¡£
       ¤¿¤È¤¨¤Ð¡¢¤¢¤ë¿Í¤¬Â¾¤Î¥ê¥à¡¼¥Ð¥Ö¥ëµ­Ï¿¥á¥Ç¥£¥¢¤ò²¿¤â»ý¤Ã¤Æ¤¤¤Ê¤¤¤È¤­¤ä¡¢
       ¾®¤µ¤Ê¥Ç¡¼¥¿¤ò¾¤Î¥³¥ó¥Ô¥å¡¼¥¿¤Ë°ÜÆ°¤µ¤»¤ëɬÍפ¬¤¢¤ë¤È¤­¤Ç¤¹¡£</para>
 
     <para>¤³¤ÎÀá¤Ç¤Ï¡¢FreeBSD ¤Ë¤ª¤±¤ë¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Î»ÈÍÑÊýË¡¤òÀâÌÀ¤·¤Þ¤¹¡£
       ¼ç¤Ë 3.5 ¥¤¥ó¥Á¤Î DOS ¥Õ¥í¥Ã¥Ô¡¼¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤ÈÁàºîÊýË¡¤ò°·¤¤¤Þ¤¹¤¬¡¢
       ¾¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Î·Á¼°¤Ë¤Ä¤¤¤Æ¤â³µÇ°¤Ï»÷¤Æ¤¤¤Þ¤¹¡£</para>
 
     <sect2>
       <title>¥Õ¥í¥Ã¥Ô¡¼¤Î¥Õ¥©¡¼¥Þ¥Ã¥È</title>
 
       <sect3>
 	<title>¥Ç¥Ð¥¤¥¹</title>
 
 	<para>¾¤Î¥Ç¥Ð¥¤¥¹¤ÈƱÍͤˡ¢¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ï
 	  <filename>/dev</filename> ¤Ë¤¢¤ë¥¨¥ó¥È¥ê¤òÄ̤¸¤Æ¥¢¥¯¥»¥¹¤µ¤ì¤Þ¤¹¡£4.X
 	  ¤ª¤è¤Ó¤½¤ì°ÊÁ°¤Î¥ê¥ê¡¼¥¹¤Ë¤ª¤¤¤Æ raw
 	  ¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤Ë¤Ï
 	  <filename>/dev/fd<replaceable>N</replaceable></filename>
 	  ¤Þ¤¿¤Ï <filename>/dev/fd<replaceable>NX</replaceable></filename>
 	  ¤ò»ÈÍѤ·¤Þ¤¹¡£<replaceable>N</replaceable> ¤Ï¥É¥é¥¤¥ÖÈÖ¹æ¤òɽ¤·¡¢
 	  ÂçÄñ¤Ï 0 ¤Ç¤¹¡£<replaceable>X</replaceable> ¤Ïʸ»ú¤òɽ¤·¤Þ¤¹¡£</para>
 
 	<para>5.0 ¤ª¤è¤Ó¤½¤ì°Ê¹ß¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï¡¢Ã±¤Ë
 	  <filename>/dev/fd<replaceable>N</replaceable></filename> ¤ò»ÈÍѤ·¤Þ¤¹¡£</para>
 
 	<sect4>
 	  <title>4.X ¤ª¤è¤Ó¤½¤ì°ÊÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Î¥Ç¥£¥¹¥¯¥µ¥¤¥º</title>
 
 	  <para><filename>/dev/fd<replaceable>N</replaceable>.<replaceable>size</replaceable></filename> ¤È¤¤¤¦¥Ç¥Ð¥¤¥¹¤â¤¢¤ê¤Þ¤¹¡£
 	    <replaceable>size</replaceable>
 	    ¤Ï¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Î¥µ¥¤¥º¤ò¥­¥í¥Ð¥¤¥È¤Ç¼¨¤·¤¿¤â¤Î¤Ç¤¹¡£
 	    ¤³¤ì¤é¤Î¥¨¥ó¥È¥ê¤ÏÄã¥ì¥Ù¥ë¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎºÝ¤Ë¡¢
 	    ¥Ç¥£¥¹¥¯¥µ¥¤¥º¤ò·èÄꤹ¤ë¤Î¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£
 	    1440kB ¤Ï°Ê²¼¤ÎÎã¤Ç»ÈÍѤµ¤ì¤ë¥µ¥¤¥º¤Ç¤¹¡£</para>
 
 	  <para>»þ¡¹ <filename>/dev</filename> ²¼¤Î¥¨¥ó¥È¥ê¤Ï (ºÆ)
 	    ºîÀ®¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¼¡¤Î¥³¥Þ¥ó¥É¤Ç¤³¤ì¤ò¹Ô¤¤¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>cd /dev &amp;&amp; ./MAKEDEV "fd*"</userinput></screen>
 	</sect4>
 
 	<sect4>
 	  <title>5.X ¤ª¤è¤Ó¤½¤ì°Ê¹ß¤Î¥ê¥ê¡¼¥¹¤Ç¤Î¥Ç¥£¥¹¥¯¥µ¥¤¥º</title>
 
 	  <para>FreeBSD 5.0 ¤Ç¤Ï &man.devfs.5; ¤¬
 	    <filename>/dev</filename> Æâ¤Î¥¨¥ó¥È¥ê¤ò¼«Æ°Åª¤Ë´ÉÍý¤¹¤ë¤Î¤Ç¡¢
 	    <command>MAKEDEV</command>¤ò»ÈÍѤ¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£</para>
 
 	  <para>½ê˾¤Î¥Ç¥£¥¹¥¯¥µ¥¤¥º¤Ï &man.fdformat.1; ¤Ë <option>-f</option>
 	    ¥Õ¥é¥°¤òÄ̤·¤ÆÅϤµ¤ì¤Þ¤¹¡£Âбþ¤·¤Æ¤¤¤ë¥µ¥¤¥º¤Ï &man.fdcontrol.8;
 	    ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë·ÇºÜ¤µ¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢ºÇÎɤËÆ°ºî¤¹¤ë¤Î¤Ï
 	    1440kB ¤À¤È½õ¸À¤·¤Æ¤ª¤­¤Þ¤¹¡£</para>
 	</sect4>
       </sect3>
 
       <sect3>
 	<title>¥Õ¥©¡¼¥Þ¥Ã¥È</title>
 
 	<para>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ï¡¢
 	  »ÈÍÑÁ°¤ËÄã¥ì¥Ù¥ë¥Õ¥©¡¼¥Þ¥Ã¥È¤ò¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	  Ä̾¥Ù¥ó¥À¤ÏÄã¥ì¥Ù¥ë¥Õ¥©¡¼¥Þ¥Ã¥ÈºÑ¤ß¤Î¥Ç¥£¥¹¥¯¤ò½Ð²Ù¤·¤Æ¤¤¤Þ¤¹¤¬¡¢
 	  ¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï¥á¥Ç¥£¥¢¤ÎÉʼÁ¤ò³Îǧ¤¹¤ë¤è¤¤ÊýË¡¤Ç¤¹¡£
 	  ¤è¤êÂ礭¤Ê (¤Þ¤¿¤Ï¾®¤µ¤Ê) ¥Ç¥£¥¹¥¯¥µ¥¤¥º¤Ë¤¹¤ë¤³¤È¤â²Äǽ¤Ç¤¹¤¬¡¢
 	  ¤Û¤È¤ó¤É¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Î¥µ¥¤¥º¤Ï 1440kB ¤ÇÆ°ºî¤¹¤ë¤è¤¦¤ËÀ߷פµ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
 	<para>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤òÄã¥ì¥Ù¥ë¥Õ¥©¡¼¥Þ¥Ã¥È¤¹¤ë¤Ë¤Ï
 	  &man.fdformat.1; ¤ò»ÈÍѤ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	  ¤³¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ï°ú¿ô¤È¤·¤Æ¥Ç¥Ð¥¤¥¹Ì¾¤ò»ØÄꤷ¤Þ¤¹¡£</para>
 
 	<para>¥Ç¥£¥¹¥¯¤¬Îɹ¥¤«¤¢¤ë¤¤¤ÏÉÔÎɤǤ¢¤ë¤«¤ò·èÄꤹ¤ë¤Î¤ËÌòΩ¤Ä¤Î¤Ç¡¢
 	  ¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò¤¹¤Ù¤Æ¥á¥â¤Ë¼è¤Ã¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	<sect4>
 	  <title>4.X °ÊÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Î¥Õ¥©¡¼¥Þ¥Ã¥È</title>
 
 	  <para><filename>/dev/fd<replaceable>N</replaceable>.<replaceable>size</replaceable></filename> ¥Ç¥Ð¥¤¥¹¤ò»È¤Ã¤Æ¥Õ¥í¥Ã¥Ô¡¼¤ò¥Õ¥©¡¼¥Þ¥Ã¥È¤·¤Þ¤¹¡£
 	    ¿·¤·¤¤ 3.5 ¥¤¥ó¥Á¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ò¥É¥é¥¤¥Ö¤ËÁÞÆþ¤·¡¢
 	    °Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <screen>&prompt.root; <userinput>/usr/sbin/fdformat /dev/fd0.1440</userinput></screen>
 	</sect4>
 
 	<sect4>
 	  <title>5.0 °Ê¹ß¤Î¥ê¥ê¡¼¥¹¤Ç¤Î¥Õ¥©¡¼¥Þ¥Ã¥È</title>
 
 	  <para><filename>/dev/fd<replaceable>N</replaceable></filename>
 	    ¥Ç¥Ð¥¤¥¹¤ò»ÈÍѤ·¤Æ¥Õ¥í¥Ã¥Ô¡¼¤ò¥Õ¥©¡¼¥Þ¥Ã¥È¤·¤Þ¤¹¡£
 	    ¿·¤·¤¤ 3.5 ¥¤¥ó¥Á¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ò¥É¥é¥¤¥Ö¤ËÁÞÆþ¤·¡¢
 	    °Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <screen>&prompt.root; <userinput>/usr/sbin/fdformat -f 1440 /dev/fd0</userinput></screen>
 	</sect4>
       </sect3>
     </sect2>
 
     <sect2>
       <title>¥Ç¥£¥¹¥¯¥é¥Ù¥ë</title>
 
       <para>¥Ç¥£¥¹¥¯¤òÄã¥ì¥Ù¥ë¥Õ¥©¡¼¥Þ¥Ã¥È¤·¤¿¤é¡¢
 	¼¡¤Ë¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òºîÀ®¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤Ï¸å¤ÇÇË´þ¤µ¤ì¤Þ¤¹¤¬¡¢
 	¥·¥¹¥Æ¥à¤¬¥Ç¥£¥¹¥¯¤Î¥µ¥¤¥º¤È¥¸¥ª¥á¥È¥ê¤ò·èÄꤹ¤ë¤Î¤ËɬÍפˤʤê¤Þ¤¹¡£</para>
 
       <para>¿·¤·¤¤¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤Ï¥Ç¥£¥¹¥¯Á´ÂΤò°ú¤­·Ñ¤®¡¢
 	¥Õ¥í¥Ã¥Ô¡¼¤Î¥¸¥ª¥á¥È¥ê¤Ë´Ø¤¹¤ëŬÀڤʾðÊó¤Î¤¹¤Ù¤Æ¤¬´Þ¤Þ¤ì¤Þ¤¹¡£
 	¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤ËÂФ¹¤ë¥¸¥ª¥á¥È¥ê¤ÎÃͤÏ
 	<filename>/etc/disktab</filename> ¤Ë·ÇºÜ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
       <para>¼¡¤Î¤è¤¦¤Ë &man.disklabel.8; ¤ò¼Â¹Ô¤Ç¤­¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>/sbin/disklabel -B -r -w /dev/fd0 fd1440</userinput></screen>
 
       <note><para>&os;&nbsp;5.1-RELEASE ¤«¤é¡¢½¾Íè¤Î &man.disklabel.8;
 	  ¥×¥í¥°¥é¥à¤Ï &man.bsdlabel.8;
 	  ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ËÃÖ¤­´¹¤¨¤é¤ì¤Þ¤·¤¿¡£&man.bsdlabel.8; ¤Ç¤Ï¡¢
 	  »ÈÍѤµ¤ì¤Æ¤¤¤Ê¤¤¥ª¥×¥·¥ç¥ó¤ª¤è¤Ó¥Ñ¥é¥á¥¿¤Î¿ô¿¤¯¤¬ºï½ü¤µ¤ì¤Þ¤·¤¿¡£
 	  ¤¿¤È¤¨¤Ð <option>-r</option> ¥ª¥×¥·¥ç¥ó¤Ï &man.bsdlabel.8;
 	  ¤Ç¤Ï¼è¤ê½ü¤«¤ì¤Þ¤·¤¿¡£¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï &man.bsdlabel.8;
 	  ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para></note>
     </sect2>
 
     <sect2>
       <title>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</title>
 
       <para>¤³¤ì¤Ç¥Õ¥í¥Ã¥Ô¡¼¤ò¹â¥ì¥Ù¥ë¥Õ¥©¡¼¥Þ¥Ã¥È¤¹¤ë½àÈ÷¤¬¤Ç¤­¤Þ¤·¤¿¡£¤³¤ì¤Ï
 	FreeBSD ¤¬¥Ç¥£¥¹¥¯¤òÆɤ߽ñ¤­¤¹¤ë¿·¤·¤¤¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤·¤Þ¤¹¡£
 	¿·¤·¤¤¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤È¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤ÏÇË´þ¤µ¤ì¤Þ¤¹¡£
 	¤·¤¿¤¬¤Ã¤Æ¡¢¥Ç¥£¥¹¥¯¤òºÆ¥Õ¥©¡¼¥Þ¥Ã¥È¤¹¤ë¤È¤­¤Ë¤Ï¡¢
 	¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òºÆºîÀ®¤·¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
       <para>¥Õ¥í¥Ã¥Ô¡¼¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¤Ï UFS ¤Þ¤¿¤Ï FAT ¤ò»ÈÍѤǤ­¤Þ¤¹¡£
 	¥Õ¥í¥Ã¥Ô¡¼¤ËÂФ·¤Æ¤Ï FAT ¤¬°ìÈÌŪ¤Ë¤è¤ê¤è¤¤ÁªÂò¤Ç¤¹¡£</para>
 
       <para>¥Õ¥í¥Ã¥Ô¡¼¾å¤Ë¿·¤·¤¤¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤Ë¤Ï¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>/sbin/newfs_msdos /dev/fd0</userinput></screen>
 
       <para>¤³¤ì¤Ç¥Ç¥£¥¹¥¯¤¬»ÈÍѤǤ­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£</para>
     </sect2>
 
     <sect2>
       <title>¥Õ¥í¥Ã¥Ô¡¼¤Î»ÈÍÑ</title>
 
       <para>¥Õ¥í¥Ã¥Ô¡¼¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¡¢&man.mount.msdos.8;
 	(4.X °ÊÁ°¤Î¥ê¥ê¡¼¥¹) ¤Þ¤¿¤Ï &man.mount.msdosfs.8;
 	(5.0 °Ê¸å¤Î¥ê¥ê¡¼¥¹) ¤òÍѤ¤¤Æ¥Þ¥¦¥ó¥È¤·¤Þ¤¹¡£
 	Ports Collection ¤«¤é
 	<filename role="package">emulators/mtools</filename>
 	¤ò»ÈÍѤ¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£</para>
     </sect2>
   </sect1>
 
   <sect1 id="backups-tapebackups">
     <title>¥Ç¡¼¥¿¥Æ¡¼¥×¤ÎºîÀ®¤È»ÈÍÑ</title>
 
     <indexterm><primary>¥Æ¡¼¥×¥á¥Ç¥£¥¢</primary></indexterm>
     <para>°ìÈÌŪ¤Ê¥Æ¡¼¥×¥á¥Ç¥£¥¢¤Ë¤Ï 4mm, 8mm, QIC, ¥ß¥Ë¥«¡¼¥È¥ê¥Ã¥¸¡¢
       DLT ¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
     <sect2 id="backups-tapebackups-4mm">
       <title>4mm (DDS: Digital Data Storage)</title>
 
       <indexterm>
 	<primary>¥Æ¡¼¥×¥á¥Ç¥£¥¢</primary>
 	<secondary>DDS (4mm) ¥Æ¡¼¥×</secondary>
       </indexterm>
       <indexterm>
 	<primary>¥Æ¡¼¥×¥á¥Ç¥£¥¢</primary>
 	<secondary>QIC ¥Æ¡¼¥×</secondary>
       </indexterm>
       <para>4mm ¥Æ¡¼¥×¤Ï¥ï¡¼¥¯¥¹¥Æ¡¼¥·¥ç¥ó¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¥á¥Ç¥£¥¢¤È¤·¤Æ
 	QIC ¤Ë¼è¤Ã¤ÆÂå¤ï¤ê¤Ä¤Ä¤¢¤ê¤Þ¤¹¡£¤³¤Î·¹¸þ¤Ï
 	QIC ¥É¥é¥¤¥Ö¤Î¼çÍפʥ᡼¥«¤Ç¤¢¤Ã¤¿ Archive ¤ò Conner ¤¬Çã¼ý¤·
 	QIC ¥É¥é¥¤¥Ö¤ÎÀ½Â¤¤òÃæ»ß¤·¤¿¤³¤È¤Ç²Ã®¤·¤Þ¤·¤¿¡£
 	4mm ¥É¥é¥¤¥Ö¤Ï¾®·¿¤ÇÀŤ«¤Ç¤¹¤¬ 8mm
 	¥É¥é¥¤¥Ö¤¬»ý¤Ã¤Æ¤¤¤ë¿®ÍêÀ­¤Û¤É¡¢¤½¤ÎɾȽ¤ÏÎɤ¯¤¢¤ê¤Þ¤»¤ó¡£
 	¤Þ¤¿¡¢4mm ¥«¡¼¥È¥ê¥Ã¥¸¤Ï 8mm ¥«¡¼¥È¥ê¥Ã¥¸¤è¤ê¤â°Â²Á¤Ç¾®·¿
 	(3 x 2 x 0.5 ¥¤¥ó¥Á¡¢76 x 51 x 12 mm) ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
 	¤¿¤À¤·¡¢8mm ¤ÈƱÍͤˡ¢4mm ¤Î¥Ø¥Ã¥É¤Ï¥Ø¥ê¥«¥ë¥¹¥­¥ã¥óÊý¼°
 	(ÌõÃí: VTR ¤ÈƱÍͤβóž¥Ø¥Ã¥É¤ò»È¤¦Êý¼°)
 	¤òºÎÍѤ·¤Æ¤¤¤ë¤¿¤á¡¢Èæ³ÓŪ¼÷Ì¿¤¬Ã»¤¤¤Ç¤¹¡£</para>
 
       <para>¥É¥é¥¤¥Ö¤Î¥Ç¡¼¥¿¥¹¥ë¡¼¥×¥Ã¥È¤Ï¡¢150&nbsp;kB/s ¤«¤é
 	ºÇÂç¤Ç 500&nbsp;kB/s ÄøÅ٤Ǥ¹¡£	¥Ç¡¼¥¿ÍÆÎÌ¤Ï 1.3&nbsp;GB ¤«¤é
 	2.0&nbsp;GB ¤Ç¤¹¡£
 	¥É¥é¥¤¥Ö¤Î¤Û¤È¤ó¤É¤ÇÍøÍѲÄǽ¤Ê¥Ï¡¼¥É¥¦¥§¥¢°µ½Ì¤ò»ÈÍѤ¹¤ë¤È¡¢
 	ÍÆÎ̤¬Ìó 2&nbsp;Çܤˤʤê¤Þ¤¹¡£
 	¥Þ¥ë¥Á¥É¥é¥¤¥Ö¥Æ¡¼¥×¥é¥¤¥Ö¥é¥ê¥æ¥Ë¥Ã¥È¤Ï 1&nbsp;¤Ä¤ÎãþÂΤË
 	6&nbsp;¤Ä¤Î¥É¥é¥¤¥Ö¤ò¼ýÍƲÄǽ¤Ç¡¢¼«Æ°Åª¤Ë¥Æ¡¼¥×¤Î¸ò´¹¤¬¤Ç¤­¤Þ¤¹¡£
 	¥é¥¤¥Ö¥é¥ê¤ÎÍÆÎÌ¤Ï 240&nbsp;GB ¤Ë㤷¤Þ¤¹¡£</para>
 
       <para>¸½ºß¤Î DDS-3 ɸ½à¤Ï 12&nbsp;GB (°µ½Ì»þ 24&nbsp;GB)
 	¤Þ¤Ç¤Î¥Æ¡¼¥×ÍÆÎ̤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£</para>
 
       <para>8mm ¥É¥é¥¤¥Ö¤ÈƱÍͤË
 	4mm ¥É¥é¥¤¥Ö¤Ï¥Ø¥ê¥«¥ë¥¹¥­¥ã¥ó¤ò»ÈÍѤ·¤Þ¤¹¡£
 	¥Ø¥ê¥«¥ë¥¹¥­¥ã¥óÊý¼°¤ÎÍøÅÀ¤ª¤è¤Ó·çÅÀ¤Ï¤¹¤Ù¤Æ 4mm ¤ª¤è¤Ó 8mm
 	¥É¥é¥¤¥Ö¤ÎξÊý¤ËÅö¤Æ¤Ï¤Þ¤ê¤Þ¤¹¡£</para>
 
       <para>¥Æ¡¼¥×¤Ï 2,000 ²ó¤Î¥Ñ¥¹¤¢¤ë¤¤¤Ï
 	100 ²ó¥Õ¥ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤·¤¿¸å¤Ë¤Ï¸ò´¹¤¹¤ë¤Ù¤­¤Ç¤¹¡£</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-8mm">
       <title>8mm (Exabyte)</title>
       <indexterm>
 	<primary>¥Æ¡¼¥×¥á¥Ç¥£¥¢</primary>
 	<secondary>Exabyte (8mm) ¥Æ¡¼¥×</secondary>
       </indexterm>
 
       <para>8mm ¥Æ¡¼¥×¤Ï SCSI
 	¥Æ¡¼¥×¥É¥é¥¤¥Ö¤È¤·¤ÆºÇ¤â¤è¤¯»È¤ï¤ì¤Æ¤¤¤ë¤â¤Î¤Ç¡¢
 	¥Ç¡¼¥¿¸ò´¹ÍѤȤ·¤ÆºÇÎɤÎÁªÂò¤Ç¤¹¡£¤Û¤È¤ó¤É¤Î¥µ¥¤¥È¤Ë¤Ï Exabyte
 	2&nbsp;GB 8mm ¥Æ¡¼¥×¥É¥é¥¤¥Ö¤¬¤¢¤ë¤Ç¤·¤ç¤¦¡£8mm
 	¥É¥é¥¤¥Ö¤Ï¿®ÍêÀ­¤¬¹â¤¯¡¢»È¤¤¤ä¤¹¤¯¡¢ÀŤ«¤Ç¤¹¡£
 	¥«¡¼¥È¥ê¥Ã¥¸¤Ï°Â²Á¤Ç¾®·¿¤Ç¤¹
 	(4.8 x 3.3 x 0.6 ¥¤¥ó¥Á¡¢122 x 84 x 15 mm)¡£8mm
 	¥Æ¡¼¥×¤Î·çÅÀ¤Ï¡¢¥Æ¡¼¥×¤È¥Ø¥Ã¥É¤ÎÁêÂÐŪ¤Ê®ÅÙ¤¬¹â®¤Ê¤¿¤á¤Ë¡¢
 	Èæ³ÓŪ¥Ø¥Ã¥É¤È¥Æ¡¼¥×¤Î¼÷Ì¿¤¬Ã»¤¤¤³¤È¤Ç¤¹¡£</para>
 
       <para>¥Ç¡¼¥¿¥¹¥ë¡¼¥×¥Ã¥È¤Ï 250&nbsp;kB/s ¤«¤é 500&nbsp;kB/s
 	ÄøÅ٤Ǥ¹¡£¥Ç¡¼¥¿ÍÆÎÌ¤Ï 300&nbsp;MB ¤«¤é 7&nbsp;GB ¤Ç¤¹¡£
 	¤Û¤È¤ó¤É¤Î¥É¥é¥¤¥Ö¤ÇÍøÍѲÄǽ¤Ê¥Ï¡¼¥É¥¦¥§¥¢°µ½Ì¤òÍøÍѤ¹¤ë¤È¡¢
 	ÍÆÎ̤¬Ìó 2&nbsp;Çܤˤʤê¤Þ¤¹¡£
 	¤³¤ì¤é¤Î¥É¥é¥¤¥Ö¤Ï¡¢Ã±°ì¤Î¥æ¥Ë¥Ã¥È¤«¤é
 	6&nbsp;¤Ä¤Î¥É¥é¥¤¥Ö¤È 120
 	ËܤΥơ¼¥×¤ò°ì¤Ä¤ÎãþÂΤ˼ýÍƤ·¤¿¥Þ¥ë¥Á¥É¥é¥¤¥Ö¥Æ¡¼¥×¥é¥¤¥Ö¥é¥ê¤Þ¤ÇÍøÍѲÄǽ¤Ç¤¹¡£
 	¥Æ¡¼¥×¤Ï¥æ¥Ë¥Ã¥È¤Ë¤è¤Ã¤Æ¼«Æ°Åª¤Ë¼è¤ê´¹¤¨¤é¤ì¤Þ¤¹¡£
 	¥é¥¤¥Ö¥é¥ê¤ÎÍÆÎÌ¤Ï 840&nbsp;GB °Ê¾å¤Ë㤷¤Þ¤¹¡£</para>
 
       <para>Exabyte ¤Î <quote>Mammoth</quote>
 	¥â¥Ç¥ë¤Ï¥Æ¡¼¥× 1&nbsp;Ëܤ¢¤¿¤ê 12&nbsp;GB
 	(°µ½Ì»þ 24&nbsp;GB) ¤ËÂбþ¤·¡¢
 	½¾Íè¤Î¥Æ¡¼¥×¥É¥é¥¤¥Ö¤ÈÈæ¤ÙÈñÍѤÏÌó 2&nbsp;Çܤˤʤê¤Þ¤¹¡£</para>
 
       <para>¥Ç¡¼¥¿¤Ï¥Ø¥ê¥«¥ë¥¹¥­¥ã¥ó¤òÍѤ¤¤Æ¥Æ¡¼¥×¤Ëµ­Ï¿¤µ¤ì¤Þ¤¹¡£
 	¥Ø¥Ã¥À¤Ï¥á¥Ç¥£¥¢¤ËÂФ·¤Æ¤¢¤ë·¹¤­ (Ìó 6 ÅÙ) ¤ËÇÛÃÖ¤µ¤ì¤Þ¤¹¡£
 	¥Æ¡¼¥×¤Ï¥Ø¥Ã¥É¤Î¤¢¤ë±ßÅû¤Î¼þ¤Î 270 Å٤ˤ錄¤Ã¤ÆÀÜ¿¨¤·¤Þ¤¹¡£
 	¥Æ¡¼¥×¤¬±ßÅûÌ̤òÁö¹Ô¤¹¤ë´Ö¡¢±ßÅû¤Ï²óž¤·¤Æ¤¤¤Þ¤¹¡£
 	¤³¤Î·ë²Ì¡¢¹âÌ©Å٤Υǡ¼¥¿¤Î¤Ä¤Þ¤Ã¤¿¥È¥é¥Ã¥¯¤Ï¡¢
 	¶¹¤¤´Ö³Ö¤Ç¥Æ¡¼¥×¤Î¾åü¤È²¼Ã¼¤Î´Ö¤ò¼Ð¤á¤Ë²£ÀÚ¤ê¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-qic">
       <title>QIC</title>
       <indexterm>
 	<primary>¥Æ¡¼¥×¥á¥Ç¥£¥¢</primary>
 	<secondary>QIC-150</secondary>
       </indexterm>
 
       <para>QIC-150 ¥Æ¡¼¥×¤È¥É¥é¥¤¥Ö¤Ï¡¢
 	¤ª¤½¤é¤¯ºÇ¤â°ìÈÌŪ¤Ë»È¤ï¤ì¤Æ¤¤¤ë¥É¥é¥¤¥Ö¤È¥á¥Ç¥£¥¢¤Ç¤·¤ç¤¦¡£
 	QIC ¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ï <quote>¸½¼ÂŪ¤Ê</quote>
 	¥Ð¥Ã¥¯¥¢¥Ã¥×¥É¥é¥¤¥Ö¤È¤·¤Æ¤ÏºÇ¤â¹â²Á¤Ç¤Ê¤¤¤â¤Î¤Ç¤¹¡£
 	·çÅÀ¤Ï¥á¥Ç¥£¥¢¤Î¥³¥¹¥È¤Ç¤¹¡£QIC ¥Æ¡¼¥×¤Ï 8mm ¤ä 4mm ¥Æ¡¼¥×¤ÈÈæ³Ó¤·¤Æ
 	GB ¤¢¤¿¤ê¤Î¥Ç¡¼¥¿¤ÎÊݸ¤Ç 5 Çܤۤɹâ²Á¤Ç¤¹¡£
 	¤·¤«¤·¡¢¤¢¤Ê¤¿¤ÎɬÍפȤ¹¤ëÎ̤¬È¾¥À¡¼¥¹Äø¤Î¥Æ¡¼¥×¤Ç½½Ê¬¤Ç¤¢¤ì¤Ð¡¢
 	QIC ¤ÏÀµ¤·¤¤ÁªÂò¤«¤â¤·¤ì¤Þ¤»¤ó¡£QIC ¤Ï
 	<emphasis>ºÇ¤â</emphasis>°ìÈÌŪ¤Ê¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ç¤¹¡£
 	¤¹¤Ù¤Æ¤Î¥µ¥¤¥È¤Ë QIC ¥É¥é¥¤¥Ö¤Î¤É¤ì¤«¤ÎÍÆÎ̤Τâ¤Î¤¬¤¢¤ê¤Þ¤¹¡£ÌäÂê¤Ï¡¢
 	QIC ¤ÏƱ¤¸¤è¤¦¤Ê¥Æ¡¼¥× (¤Þ¤Ã¤¿¤¯Æ±¤¸¾ì¹ç¤â¤¢¤ë)
 	¤Ë¿Íͤʵ­Ï¿Ì©ÅÙ¤¬¤¢¤ë¤³¤È¤Ç¤¹¡£QIC ¥É¥é¥¤¥Ö¤ÏÀŤ«¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
 	¤³¤ì¤é¤Î¥É¥é¥¤¥Ö¤Ï¥Ç¡¼¥¿µ­Ï¿¤ò³«»Ï¤¹¤ëÁ°¤Ë²»¤ò¤¿¤Æ¤Æ¥·¡¼¥¯¤·¤Þ¤¹¤·¡¢
 	¥ê¡¼¥É¡¢¥é¥¤¥È¡¢¥·¡¼¥¯¤Î»þ¤Ë¤Ï¤Ã¤­¤ê¤Èʹ¤³¤¨¤ë²»¤ò½Ð¤·¤Þ¤¹¡£
 	QIC ¥Æ¡¼¥×¤ÎÂ礭¤µ¤Ï (6 x 4 x 0.7 ¥¤¥ó¥Á¡¢152 x 102 x 17 mm) ¤Ç¤¹¡£
 	1/4 ¥¤¥ó¥ÁÉý¤Î¥Æ¡¼¥×¤â»ÈÍѤ·¤Æ¤¤¤ë
 	<link linkend="backups-tapebackups-mini">¥ß¥Ë¥«¡¼¥È¥ê¥Ã¥¸</link>
 	¤ÏÊ̤˵ÄÏÀ¤·¤Þ¤¹¡£¥Æ¡¼¥×¥é¥¤¥Ö¥é¥ê¤ä¥Á¥§¥ó¥¸¥ã¤Ï¤¢¤ê¤Þ¤»¤ó¡£</para>
 
       <para>¥Ç¡¼¥¿¥¹¥ë¡¼¥×¥Ã¥È¤Ï ~1500&nbsp;kB/s ¤«¤é ~5000&nbsp;kB/s
 	ÄøÅ٤Ǥ¹¡£¥Ç¡¼¥¿ÍÆÎÌ¤Ï 400&nbsp;MB ¤«¤é 150&nbsp;GB ¤Ç¤¹¡£
 	¥Ï¡¼¥É¥¦¥§¥¢°µ½Ì¤¬ºÇ¶á¤Î¥É¥é¥¤¥Ö¤Î¿¤¯¤ÇÍøÍѤǤ­¤Þ¤¹¡£
 	QIC ¥É¥é¥¤¥Ö¤Ï DAT ¥É¥é¥¤¥Ö¤ËÃÖ¤­´¹¤¨¤é¤ì¤Ä¤Ä¤¢¤ê¡¢
 	¤¢¤Þ¤êÉÑÈˤˤϻÈÍѤµ¤ì¤Ê¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
 
       <para>¥Ç¡¼¥¿¤ÏÊ£¿ô¤Î¥È¥é¥Ã¥¯¤Ëʬ¤«¤ì¤Æ¥Æ¡¼¥×¤Ëµ­Ï¿¤µ¤ì¤Þ¤¹¡£
 	¥È¥é¥Ã¥¯¤Ï¥Æ¡¼¥×¥á¥Ç¥£¥¢¤ÎŤµÊý¸þ¤Î°ìü¤«¤é¤â¤¦°ìÊý¤Îü¤Þ¤Ç¤Ç¤¹
 	(ÌõÃí: 1 ¥È¥é¥Ã¥¯¤Î read/write ¤¬½ª¤ï¤ë¤È¥Æ¡¼¥×¤ÎÁö¹ÔÊý¸þ¤òȿž¤µ¤»
 	¼¡¤Î¥È¥é¥Ã¥¯¤Î read/write ¤ò¹Ô¤¤¤Þ¤¹)¡£¥È¥é¥Ã¥¯¤Î¿ô¤È¡¢
 	¤½¤ì¤ËÂбþ¤¹¤ë¥È¥é¥Ã¥¯¤ÎÉý¤Ï¥Æ¡¼¥×¤ÎÍÆÎ̤ˤè¤Ã¤ÆÊѤï¤ê¤Þ¤¹¡£
 	¤¹¤Ù¤Æ¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢
 	ºÇ¶á¤Î¥É¥é¥¤¥Ö¤Ï¤Û¤È¤ó¤É¡¢¾¯¤Ê¤¯¤È¤âÆɤ߽Ф·¤Ë¤Ä¤¤¤Æ¤Ï
 	(¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï½ñ¤­¹þ¤ß¤â) ²¼°Ì¸ß´¹À­¤¬¤¢¤ê¤Þ¤¹¡£
 	QIC ¤Ï¥Ç¡¼¥¿¤Î°ÂÁ´À­¤Ë¤Ä¤¤¤Æ¤Ï¤è¤¤¤È¤¤¤ï¤ì¤Æ¤¤¤Þ¤¹
 	(¥Ø¥ê¥«¥ë¥¹¥­¥ã¥ó¥É¥é¥¤¥Ö¤ËÈæ¤Ù¤Æµ¡¹½¤Ïñ½ã¤Ç¤è¤ê¾æÉפǤ¹)¡£</para>
 
       <para>¥Æ¡¼¥×¤Ï 5000 ²ó¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤Ç¼÷Ì¿¤È¤Ê¤ë¤Ç¤·¤ç¤¦¡£</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-mini">
       <title>XXX* ¥ß¥Ë¥«¡¼¥È¥ê¥Ã¥¸</title>
 
       <para></para>
     </sect2>
 
     <sect2 id="backups-tapebackups-dlt">
       <title>DLT</title>
       <indexterm>
 	<primary>¥Æ¡¼¥×¥á¥Ç¥£¥¢</primary>
 	<secondary>DLT</secondary>
       </indexterm>
 
       <para>DLT	¤Ï¤³¤³¤Ë¼¨¤·¤¿¥É¥é¥¤¥Ö¤Î¥¿¥¤¥×¤ÎÃæ¤ÇºÇ¹â®¤Î¥Ç¡¼¥¿Å¾Á÷¥ì¡¼¥È¤òȯ´ø¤·¤Þ¤¹¡£
 	1/2 ¥¤¥ó¥Á (12.5mm) ¥Æ¡¼¥×¤¬Ã±¥ê¡¼¥ë¤Î¥«¡¼¥È¥ê¥Ã¥¸
 	(4 x 4 x 1 ¥¤¥ó¥Á¡¢100 x 100 x 25 mm) ¤ËÆþ¤Ã¤Æ¤¤¤Þ¤¹¡£
 	¥«¡¼¥È¥ê¥Ã¥¸¤Î¤Ò¤È¤Ä¤Î¦ÌÌÁ´ÂΤ¬¥¹¥¤¥ó¥°¥²¡¼¥È¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
 	¥É¥é¥¤¥Ö¤Îµ¡¹½¤¬¤³¤Î¥²¡¼¥È¤ò³«¤±¡¢¥Æ¡¼¥×¥ê¡¼¥À¤ò°ú¤­½Ð¤·¤Þ¤¹¡£
 	¥Æ¡¼¥×¥ê¡¼¥À¤Ë¤ÏÂʱ߷Á¤Î·ê¤¬¤¢¤ê¡¢
 	¥É¥é¥¤¥Ö¤¬¥Æ¡¼¥×¤ò <quote>°ú¤Ã³Ý¤±¤ë</quote> ¤Î¤Ë»È¤¤¤Þ¤¹¡£
 	´¬¤­¼è¤ê¤Î¤¿¤á¤Î¥ê¡¼¥ë¤Ï¥É¥é¥¤¥Ö¤ÎÃæ¤Ë¤¢¤ê¤Þ¤¹¡£
 	¤³¤³¤Ëµó¤²¤¿Â¾¤Î¥«¡¼¥È¥ê¥Ã¥¸¤Ï¤¹¤Ù¤Æ
 	(9 ¥È¥é¥Ã¥¯¥Æ¡¼¥×¤ÏÍ£°ì¤ÎÎã³°¤Ç¤¹)
 	Á÷¤ê½Ð¤·¥ê¡¼¥ë¤È´¬¤­¼è¤ê¥ê¡¼¥ë¤ÎξÊý¤¬¥«¡¼¥È¥ê¥Ã¥¸¤ÎÃæ¤Ë¤¢¤ê¤Þ¤¹¡£</para>
 
       <para>¥Ç¡¼¥¿¥¹¥ë¡¼¥×¥Ã¥È¤ÏÌó 1.5&nbsp;MB/s ¤Ç¡¢4mm, 8mm, QIC
 	¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Î 3&nbsp;ÇܤǤ¹¡£¥Ç¡¼¥¿ÍÆÎ̤Ïñ°ì¤Î¥É¥é¥¤¥Ö¤Ç
 	10&nbsp;GB ¤«¤é 20&nbsp;GB ¤ÎÈϰϤǤ¹¡£¥Þ¥ë¥Á¥Æ¡¼¥×¥Á¥§¥ó¥¸¥ã¡¢
 	¥Þ¥ë¥Á¥Æ¡¼¥×¥É¥é¥¤¥Ö¡¢5 ¤«¤é 900&nbsp;´¬¤Î¥Æ¡¼¥×¤ò 1 ¤«¤é
 	20 ¥É¥é¥¤¥Ö¤Ç°·¤¦¥Þ¥ë¥Á¥É¥é¥¤¥Ö¥Æ¡¼¥×¥é¥¤¥Ö¥é¥ê¤¬¤¢¤ê¡¢
 	50&nbsp;GB ¤«¤é 9&nbsp;TB ¤ÎÍÆÎ̤¬ÆÀ¤é¤ì¤Þ¤¹¡£</para>
 
       <para>°µ½Ì¤Ë¤è¤Ã¤Æ¡¢DLT Type IV ¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï
 	70&nbsp;GB ¤Þ¤Ç¤ÎÍÆÎ̤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£</para>
 
       <para>¥Ç¡¼¥¿¤Ï (QIC¥Æ¡¼¥×¤Î¤è¤¦¤Ë)
 	¥Æ¡¼¥×¤ÎÁö¹ÔÊý¸þ¤ÈÊ¿¹Ô¤ËÊ£¿ô¤¢¤ë¥È¥é¥Ã¥¯¤Øµ­Ï¿¤µ¤ì¤Þ¤¹¡£
 	2&nbsp;¤Ä¤Î¥È¥é¥Ã¥¯¤ËƱ»þ½ñ¤­¹þ¤ß¤ò¹Ô¤¤¤Þ¤¹¡£
 	read/write ¥Ø¥Ã¥É¤Î¼÷Ì¿¤ÏÈæ³ÓŪŤ¤¤È¸À¤¨¤Þ¤¹¡£
 	¥Æ¡¼¥×¤ÎÁö¹Ô¤¬»ß¤Þ¤ì¤Ð¥Ø¥Ã¥É¤È¥Æ¡¼¥×¤Î´Ö¤ÎÁêÂб¿Æ°¤Ï̵¤¤¤«¤é¤Ç¤¹¡£</para>
     </sect2>
 
     <sect2>
       <title id="backups-tapebackups-ait">AIT</title>
       <indexterm>
 	<primary>¥Æ¡¼¥×¥á¥Ç¥£¥¢</primary>
 	<secondary>AIT</secondary>
       </indexterm>
 
       <para>AIT ¤Ï¡¢Sony ¤¬È¯É½¤·¤¿¿·¤·¤¤¥Õ¥©¡¼¥Þ¥Ã¥È¤Ç¡¢
         ¥Æ¡¼¥× 1&nbsp;Ëܤ¢¤¿¤ê 50&nbsp;GB (°µ½Ì»þ) ¤Þ¤Ç³ÊǼ¤Ç¤­¤Þ¤¹¡£
 	¥Æ¡¼¥×¤Ë¤Ï¥á¥â¥ê¥Á¥Ã¥×¤¬ÅëºÜ¤µ¤ì¤Æ¤ª¤ê¡¢
 	¥Æ¡¼¥×¤ÎÆâÍƤκ÷°ú¾ðÊó¤òÊÝ»ý¤·¤Æ¤¤¤Þ¤¹¡£
 	¾¤Î¥Æ¡¼¥×¤Ç¤Ï¥Æ¡¼¥×¾å¤Î¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ¤òÇÄ°®¤¹¤ë¤Î¤Ë¿ôʬɬÍפȤ¹¤ë¤Î¤Ç¤¹¤¬¡¢
 	¤³¤Î¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ç¤Ïº÷°ú¾ðÊó¤òÆɤó¤Çľ¤Á¤Ë·èÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	<application>SAMS:Alexandria</application>
         ¤Î¤è¤¦¤Ê¥½¥Õ¥È¥¦¥§¥¢¤Ï¡¢40 ¤òĶ¤¨¤ë
         ATI ¥Æ¡¼¥×¥é¥¤¥Ö¥é¥ê¤òÁàºî¤Ç¤­¤ë¤Î¤Ï¤â¤Á¤í¤ó¤Î¤³¤È¡¢
 	¥Æ¡¼¥×¤Î¥á¥â¥ê¥Á¥Ã¥×¤ÈľÀÜÄÌ¿®¤·¤Æ¡¢¥¹¥¯¥ê¡¼¥ó¤ËÆâÍƤòɽ¼¨¤·¡¢
 	¤É¤Î¥Õ¥¡¥¤¥ë¤¬¤É¤Î¥Æ¡¼¥×¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤µ¤ì¤¿¤«¤òÄ´¤Ù¤Æ¡¢
 	Àµ¤·¤¤¥Æ¡¼¥×¤ò¸«¤Ä¤±¡¢Æɤ߹þ¤ß¡¢
 	¥Æ¡¼¥×¤«¤é¥Ç¡¼¥¿¤òÉü¸µ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <para>¤³¤Î¤è¤¦¤Ê¥é¥¤¥Ö¥é¥ê¤ÏÂçÂÎ $20,000 ¤¯¤é¤¤¤¹¤ë¤Î¤Ç¡¢
 	°¦¹¥²È¤¬¹ØÆþ¤Ç¤­¤ë²Á³ÊÂÓ¤«¤é¤Ï³°¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2>
       <title>¿·ÉʤΥơ¼¥×¤ò½é¤á¤Æ»È¤¦¾ì¹ç</title>
 
       <para>Á´¤¯¿·Éʤζõ¥Æ¡¼¥×¤òÆɤ⤦¤È¤·¤¿¤ê½ñ¤­¹þ¤â¤¦¤È¤¹¤ë¤È¡¢
 	½èÍý¤Ï¼ºÇÔ¤¹¤ë¤Ç¤·¤ç¤¦¡£
 	¼¡¤Î¤è¤¦¤Ê¥á¥Ã¥»¡¼¥¸¤¬¥³¥ó¥½¡¼¥ë¤Ë½ÐÎϤµ¤ì¤ë¤Ç¤·¤ç¤¦¡£</para>
 
       <screen>sa0(ncr1:4:0): NOT READY asc:4,1
 sa0(ncr1:4:0):  Logical unit is in process of becoming ready</screen>
 
       <para>¥Æ¡¼¥×¤Ë¼±ÊÌ¥Ö¥í¥Ã¥¯ (Identifier Block:block number 0)
 	¤¬¤¢¤ê¤Þ¤»¤ó¡£QIC-525 ɸ½à¤òºÎÍѤ·¤¿¤¹¤Ù¤Æ¤Î QIC
 	¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ï¼±ÊÌ¥Ö¥í¥Ã¥¯¤ò¥Æ¡¼¥×¤Ë½ñ¤­¹þ¤ß¤Þ¤¹¡£
 	2 ¤Ä¤Î²ò·èÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para><command>mt fsf 1</command>
 	      ¤Ë¤è¤ê¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ï¥Æ¡¼¥×¤Ë¼±ÊÌ¥Ö¥í¥Ã¥¯¤ò½ñ¤­¹þ¤ß¤Þ¤¹¡£</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>¥Õ¥í¥ó¥È¥Ñ¥Í¥ë¤Î¥Ü¥¿¥ó¤ò²¡¤·¤Æ¥Æ¡¼¥×¤ò¼è¤ê½Ð¤·¤Þ¤¹¡£</para>
 
 	    <para>ºÆ¤Ó¥Æ¡¼¥×¤òÁÞÆþ¤·¡¢¥Ç¡¼¥¿¤ò¥Æ¡¼¥×¤Ë <command>dump</command>
 	      ¤·¤Þ¤¹¡£</para>
 
 	    <para><command>dump</command> ¤Ï
 	      <errorname>DUMP: End of tape detected</errorname> ¤ÈÊó¹ð¤·¡¢
 	      ¥³¥ó¥½¡¼¥ë¤Ë¤Ï
 	      <errorname>HARDWARE FAILURE info:280 asc:80,96</errorname>
 	      ¤Èɽ¼¨¤µ¤ì¤ë¤Ç¤·¤ç¤¦¡£</para>
 
 	    <para><command>mt rewind</command> ¤ò»È¤Ã¤Æ¥Æ¡¼¥×¤ò´¬Ìᤷ¤Þ¤¹¡£</para>
 
 	    <para>¼¡¤«¤é¤Ï¥Æ¡¼¥×¤ÎÁàºî¤Ï¤¦¤Þ¤¯¤¤¤¯¤Ç¤·¤ç¤¦¡£</para>
 	  </listitem>
 	</itemizedlist>
     </sect2>
   </sect1>
 
   <sect1 id="backups-floppybackups">
     <title>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ø¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×</title>
 
     <sect2 id="floppies-using">
       <title>¥Ç¡¼¥¿¤ò¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¤Î¤Ë¥Õ¥í¥Ã¥Ô¡¼¤Ï»È¤¨¤Þ¤¹¤«?</title>
       <indexterm><primary>¥Ð¥Ã¥¯¥¢¥Ã¥×¥Õ¥í¥Ã¥Ô¡¼</primary></indexterm>
       <indexterm><primary>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯</primary></indexterm>
 
       <para>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ï°Ê²¼¤ÎÍýͳ¤Ë¤è¤Ã¤Æ¡¢
 	¼ÂºÝ¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¤Ä¤¯¤ë¤¿¤á¤ÎŬÀڤʥá¥Ç¥£¥¢¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>¥á¥Ç¥£¥¢¤Î¿®ÍêÀ­¤¬ (ÆäËĹ´ü´Ö¤Î¾ì¹ç) Ä㤤¡£</para>
 	</listitem>
 
 	<listitem>
 	  <para>¥Ð¥Ã¥¯¥¢¥Ã¥×¤È¥ê¥¹¥È¥¢¤¬¤È¤Æ¤âÃÙ¤¤¡£</para>
 	</listitem>
 
 	<listitem>
 	  <para>ÍÆÎ̤¬Èó¾ï¤Ë¾®¤µ¤¤
 	    (1 ¥À¡¼¥¹¤«¤½¤³¤é¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë
 	    ¥Ï¡¼¥É¥Ç¥£¥¹¥¯Á´ÂΤò¥Ð¥Ã¥¯¥¢¥Ã¥×¤·¤Æ¤¤¤¿»þÂå¤Ï¡¢
 	    ¤Ï¤ë¤«±ó¤¯¤Ë²á¤®µî¤ê¤Þ¤·¤¿)¡£</para>
 	</listitem>
       </itemizedlist>
 
       <para>¤·¤«¤·¤Ê¤¬¤é¡¢¥Ç¡¼¥¿¤ò¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¾¤Î¼êÃʤ¬¤Ê¤¤¤Î¤Ê¤é¡¢
 	¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¼è¤é¤Ê¤¤¤è¤ê¤â¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ò»È¤¦Êý¤¬¤Þ¤·¤Ç¤·¤ç¤¦¡£</para>
 
       <para>¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ò»ÈÍѤ»¤¶¤ë¤òÆÀ¤Ê¤¤¤È¤­¤Ï¡¢
 	ÉʼÁ¤Î¤è¤¤¥Ç¥£¥¹¥¯¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
 	»ö̳½ê¤Î¤½¤ÎÊդ˿ôǯž¤¬¤Ã¤Æ¤¤¤¿¥Õ¥í¥Ã¥Ô¡¼¤Ï»È¤ï¤Ê¤¤Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£
 	ɾȽ¤Î¤è¤¤¥á¡¼¥«¤Î¿·¤·¤¤¥Ç¥£¥¹¥¯¤ò»ÈÍѤ¹¤ë¤³¤È¤¬ÍýÁۤǤ¹¡£</para>
     </sect2>
 
     <sect2 id="floppies-creating">
       <title>¤½¤ì¤Ç¤Ï¤É¤¦¤ä¤Ã¤Æ¥Ç¡¼¥¿¤ò¥Õ¥í¥Ã¥Ô¡¼¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¤Î¤Ç¤¹¤«?</title>
 
       <para>¥Õ¥í¥Ã¥Ô¡¼¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ëºÇ¤â¤è¤¤ÊýË¡¤Ï¡¢
 	<option>-M</option> (¥Þ¥ë¥Á¥Ü¥ê¥å¡¼¥à) ¥ª¥×¥·¥ç¥óÉÕ¤­¤Ç
 	&man.tar.1; ¥³¥Þ¥ó¥É¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¤¹¡£¤³¤ì¤Ç¡¢
 	Ê£¿ô¤Î¥Õ¥í¥Ã¥Ô¡¼¤Ë¤ï¤¿¤Ã¤Æ¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¤³¤È¤¬²Äǽ¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
 
       <para>¥«¥ì¥ó¥È¥Ç¥£¥ì¥¯¥È¥ê¤È¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥êÆâ¤Î¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¤Ë¤Ï¡¢
 	°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò (<username>root</username> ¸¢¸Â¤Ç)
 	»ÈÍѤ·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>tar Mcvf /dev/fd0 *</userinput></screen>
 
       <para>1 ËçÌܤΥեí¥Ã¥Ô¡¼¤¬°ìÇդˤʤë¤È¡¢
 	&man.tar.1; ¤Ï¼¡¤Î¥Ü¥ê¥å¡¼¥à¤òÁÞÆþ¤¹¤ë¤è¤¦¤ËÍ׵ᤷ¤Þ¤¹
 	(&man.tar.1; ¤Ï¤µ¤Þ¤¶¤Þ¤Ê¥á¥Ç¥£¥¢¤ò°·¤¨¤ë¤Î¤Ç¡¢
 	¥Ü¥ê¥å¡¼¥à¤Èɽ¼¨¤·¤Þ¤¹¡£¤³¤Îʸ̮¤Ç¤Ï¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Î¤³¤È¤Ç¤¹)¡£</para>
 
       <screen>Prepare volume #2 for /dev/fd0 and hit return:</screen>
 
       <para>»ØÄꤷ¤¿¥Õ¥¡¥¤¥ë¤¬¤¹¤Ù¤ÆÊݸ¤µ¤ì¤ë¤Þ¤Ç
 	(¥Ü¥ê¥å¡¼¥àÈÖ¹æ¤òÁý¤ä¤·¤Ê¤¬¤é) ¤³¤ì¤¬·«¤êÊÖ¤µ¤ì¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2 id="floppies-compress">
       <title>¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò°µ½Ì¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¤«?</title>
       <indexterm>
 	<primary><command>tar</command></primary>
       </indexterm>
       <indexterm>
 	<primary><command>gzip</command></primary>
       </indexterm>
       <indexterm><primary>°µ½Ì</primary></indexterm>
 
       <para>»ÄÇ°¤Ê¤³¤È¤Ë &man.tar.1; ¤Ï¥Þ¥ë¥Á¥Ü¥ê¥å¡¼¥à¥¢¡¼¥«¥¤¥Ö¤ËÂФ·¤Æ¡¢
 	<option>-z</option> ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£
 	¤â¤Á¤í¤ó¡¢¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò &man.gzip.1; ¤Ç°µ½Ì¤·¡¢
 	¤½¤ì¤é¤ò &man.tar.1; ¤òÍѤ¤¤Æ¥Õ¥í¥Ã¥Ô¡¼¤ËÊݸ¤·¤Æ¡¢
 	¤½¤ì¤«¤éºÆ¤Ó &man.gunzip.1; ¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2 id="floppies-restoring">
       <title>¤É¤Î¤è¤¦¤Ë¤·¤Æ¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¥ê¥¹¥È¥¢¤·¤¿¤é¤¤¤¤¤Î¤Ç¤·¤ç¤¦¤«?</title>
 
       <para>¤¹¤Ù¤Æ¤Î¥¢¡¼¥«¥¤¥Ö¤ò¥ê¥¹¥È¥¢¤¹¤ë¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>tar Mxvf /dev/fd0</userinput></screen>
 
       <para>ÆÃÄê¤Î¥Õ¥¡¥¤¥ë¤À¤±¤ò¥ê¥¹¥È¥¢¤¹¤ë¤Ë¤Ï 2 ¤Ä¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£
 	1 ¤ÄÌܤϡ¢1 ËçÌܤΥեí¥Ã¥Ô¡¼¤òÍѤ¤¤Æ°Ê²¼¤Î¤è¤¦¤Ë¤¹¤ë¤â¤Î¤Ç¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>tar Mxvf /dev/fd0 <replaceable>filename</replaceable></userinput></screen>
 
       <para>&man.tar.1; ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ï¡¢
 	ɬÍפʥե¡¥¤¥ë¤ò¸«¤Ä¤±¤ë¤Þ¤Ç¼¡¤Î¥Ç¥£¥¹¥¯¤òÁÞÆþ¤¹¤ë¤è¤¦¤ËÍ׵ᤷ¤Þ¤¹¡£</para>
 
       <para>¤â¤¦ 1 ¤Ä¤Ï¡¢
 	ɬÍפʥե¡¥¤¥ë¤¬¤É¤Î¥Õ¥í¥Ã¥Ô¡¼¤ËÊݸ¤µ¤ì¤Æ¤¤¤ë¤«Ê¬¤«¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢
 	¤½¤Î¥Õ¥í¥Ã¥Ô¡¼¤òÁÞÆþ¤·¤Æ¾åµ­¤ÈƱ¤¸¥³¥Þ¥ó¥É¤ò»ÈÍѤ¹¤ë¤À¤±¤Ç¤â¤è¤¤¤Ç¤¹¡£
 	¤¢¤ë¥Õ¥í¥Ã¥Ô¡¼¾å¤Ë¤¢¤ë 1 ÈÖÌܤΥե¡¥¤¥ë¤¬¡¢
 	¤½¤ÎÁ°¤Î¥Õ¥í¥Ã¥Ô¡¼¤«¤é³¤¤¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
 	¤½¤Î¥Õ¥¡¥¤¥ë¤Î¥ê¥¹¥È¥¢¤òÍ׵ᤷ¤Æ¤¤¤Ê¤¯¤Æ¤â &man.tar.1;
 	¤Ï¤½¤ì¤ò¥ê¥¹¥È¥¢¤Ç¤­¤Ê¤¤¤È·Ù¹ð¤¹¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤!</para>
     </sect2>
   </sect1>
 
   <sect1 id="backup-basics">
     <title>¥Ð¥Ã¥¯¥¢¥Ã¥×¤Î´ðËÜ</title>
 
     <para>¼ç¤Ê¥Ð¥Ã¥¯¥¢¥Ã¥×¥×¥í¥°¥é¥à¤Ï
       &man.dump.8;, &man.tar.1;, &man.cpio.1; ¤Î»°¤Ä¤Ç¤¹¡£</para>
 
     <sect2>
       <title>¥À¥ó¥×¤È¥ê¥¹¥È¥¢</title>
       <indexterm>
 	<primary>¥Ð¥Ã¥¯¥¢¥Ã¥×¥½¥Õ¥È¥¦¥§¥¢</primary>
 	<secondary>¥À¥ó¥× / ¥ê¥¹¥È¥¢</secondary>
       </indexterm>
       <indexterm><primary><command>dump</command></primary></indexterm>
       <indexterm><primary><command>restore</command></primary></indexterm>
 
       <para>ÅÁÅýŪ¤Ê &unix; ¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¥×¥í¥°¥é¥à¤Ï
 	<command>dump</command> ¤È <command>restore</command> ¤Ç¤¹¡£
 	¤³¤ì¤é¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¤è¤Ã¤ÆºîÀ®¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¡¢¥ê¥ó¥¯¡¢
 	¥Ç¥£¥ì¥¯¥È¥ê¤È¤¤¤Ã¤¿Ãê¾Ý¤Î²¼°Ì¤Ë¤¢¤ë¡¢
 	¥Ç¥£¥¹¥¯¥Ö¥í¥Ã¥¯¤Î½¸¹ç¤È¤·¤Æ¥É¥é¥¤¥Ö¤òÁàºî¤·¤Þ¤¹¡£
 	<command>dump</command>
 	¤Ï¥Ç¥Ð¥¤¥¹¾å¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àÁ´ÂΤò¥Ð¥Ã¥¯¥¢¥Ã¥×¤·¤Þ¤¹¡£
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ìÉôʬ¤À¤±¡¢
 	¤Þ¤¿¤ÏÆó¤Ä°Ê¾å¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¤ï¤¿¤ë¥Ç¥£¥ì¥¯¥È¥ê¥Ä¥ê¡¼¤ò¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
 	<command>dump</command>
 	¤Ï¥Õ¥¡¥¤¥ë¤ª¤è¤Ó¥Ç¥£¥ì¥¯¥È¥ê¤ò¥Æ¡¼¥×¤Ë½ñ¤­¹þ¤Þ¤º¤Ë¡¢
 	¥Õ¥¡¥¤¥ë¤ª¤è¤Ó¥Ç¥£¥ì¥¯¥È¥ê¤ò´Þ¤ó¤À raw ¥Ç¡¼¥¿¥Ö¥í¥Ã¥¯¤ò½ñ¤­¹þ¤ß¤Þ¤¹¡£</para>
 
       <note><para>¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê¤Ç <command>dump</command>
 	¤ò»È¤Ã¤¿¾ì¹ç¡¢
 	<filename>/home</filename>, <filename>/usr</filename>
 	¤Ê¤É¡¢Â¾¤Î¿¤¯¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ï¥Ð¥Ã¥¯¥¢¥Ã¥×¤µ¤ì¤Þ¤»¤ó¡£
 	¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ÏÄ̾
 	¾¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ø¤Î¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤Ç¤¢¤Ã¤¿¤ê¡¢
 	¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤È¤Ê¤Ã¤Æ¤¤¤ë¤¿¤á¤Ç¤¹¡£</para></note>
 
       <para><command>dump</command> ¤Ë¤Ï AT&amp;T UNIX ¤Î¥Ð¡¼¥¸¥ç¥ó 6
 	(¤ª¤è¤½ 1975 ǯ) ¤Î½é´ü¤«¤é»Ä¤Ã¤Æ¤¤¤ëÊʤ¬¤¢¤ê¤Þ¤¹¡£
 	¥Ç¥Õ¥©¥ë¥È¤Î¥Ñ¥é¥á¥¿¤Ï¡¢¸½ºßÍøÍѲÄǽ¤Ê¹âÌ©ÅÙ¥á¥Ç¥£¥¢
 	(ºÇÂç 62,182 ftpi) ¤Ç¤Ï¤Ê¤¯¡¢9 ¥È¥é¥Ã¥¯¥Æ¡¼¥× (6250 bpi)
 	¤ËºÇŬ¤ÊÃͤȤʤäƤ¤¤Þ¤¹¡£
 	¸½ºß¤Î¥Æ¡¼¥×¥É¥é¥¤¥Ö¤ÎÍÆÎ̤òÍøÍѤ¹¤ë¤¿¤á¤Ë¡¢
 	¤³¤ì¤é¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤò¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ç¾å½ñ¤­¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
       <indexterm><primary><filename>.rhosts</filename></primary></indexterm>
       <para><command>rdump</command> ¤È <command>rrestore</command>
 	¤òÍѤ¤¤Æ¾¤Î¥³¥ó¥Ô¥å¡¼¥¿¤ËÀܳ¤µ¤ì¤Æ¤¤¤ë¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ë¥Í¥Ã¥È¥ï¡¼¥¯·Ðͳ¤Ç¥Ç¡¼¥¿¤ò¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¤³¤È¤â²Äǽ¤Ç¤¹¡£
 	¤É¤Á¤é¤Î¥×¥í¥°¥é¥à¤â¥ê¥â¡¼¥È¤Î¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë
 	<command>rcmd</command> ¤ª¤è¤Ó <command>ruserok</command>
 	¤Ë°Í¸¤·¤Æ¤¤¤Þ¤¹¡£
 	¤·¤¿¤¬¤Ã¤Æ¡¢¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¼Â¹Ô¤¹¤ë¥æ¡¼¥¶¤¬¥ê¥â¡¼¥È¥³¥ó¥Ô¥å¡¼¥¿¤Î
 	<filename>.rhosts</filename> ¥Õ¥¡¥¤¥ë¤Ë½ñ¤«¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
 	<command>rdump</command> ¤ª¤è¤Ó <command>rrestore</command>
 	¤Î°ú¿ô¤Ï¥ê¥â¡¼¥È¥³¥ó¥Ô¥å¡¼¥¿¤ËŬÀڤʤâ¤Î¤òÍѤ¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
 	FreeBSD ¥³¥ó¥Ô¥å¡¼¥¿¤«¤é <hostid>komodo</hostid> ¤È¸Æ¤Ð¤ì¤ë Sun
 	¤ËÀܳ¤µ¤ì¤Æ¤¤¤ë Exabyte ¥Æ¡¼¥×¤Ø <command>rdump</command>
 	¤¹¤ë¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nsa8 /dev/da0a 2>&amp;1</userinput></screen>
 
       <para>Ãí°Õ: <filename>.rhosts</filename>
 	ǧ¾Ú¤òµö²Ä¤¹¤ë¤³¤È¤Ë¤Ï¡¢¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤¹¤ë°ÅÌۤβ¾Ä꤬¤¢¤ê¤Þ¤¹¡£
 	¤¢¤Ê¤¿¤ÎÃÖ¤«¤ì¤Æ¤¤¤ë¾õ¶·¤òÃí°Õ¿¼¤¯Ä´¤Ù¤Æ¤¯¤À¤µ¤¤¡£</para>
 
       <para><command>ssh</command> ±Û¤·¤Ë
 	<command>dump</command> ¤È <command>restore</command>
 	¤ò¤è¤ê°ÂÁ´¤Ê·Á¤Ç»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£</para>
 
       <example>
 	<title><application>ssh</application> ±Û¤·¤Î
 	  <command>dump</command> ¤ÎÍøÍÑ</title>
 
 	<screen>&prompt.root; <userinput>/sbin/dump -0uan -f - /usr | gzip -2 | ssh1 -c blowfish \
           targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz</userinput></screen>
       </example>
 
       <para>¤Þ¤¿¤Ï¡¢´Ä¶­ÊÑ¿ô <envar>RSH</envar> ¤òÀßÄꤷ¤Æ¡¢
 	<command>dump</command> ¤ÎÁȤ߹þ¤ßµ¡Ç½¤òÍøÍѤ¹¤ë¡£</para>
 
       <example>
 	<title><envar>RSH</envar> ¤òÀßÄꤷ¤¿ <application>ssh</application> ±Û¤·¤Î <command>dump</command> ¤òÍøÍÑ</title>
 
 	<screen>&prompt.root; <userinput>RSH=/usr/bin/ssh /sbin/dump -0uan -f targetuser@targetmachine.example.com:/dev/sa0</userinput></screen>
 
       </example>
 
     </sect2>
 
     <sect2>
       <title><command>tar</command></title>
       <indexterm>
 	<primary>¥Ð¥Ã¥¯¥¢¥Ã¥×¥½¥Õ¥È¥¦¥§¥¢</primary>
 	<secondary><command>tar</command></secondary>
       </indexterm>
 
       <para>&man.tar.1; ¤Ï AT&amp;T UNIX ¤Î ¥Ð¡¼¥¸¥ç¥ó 6 (1975 ǯ¤´¤í)
 	¤Ë¤Þ¤ÇÁ̤뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£<command>tar</command>
 	¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤È¶¨Ä´¤·¤ÆÆ°ºî¤·¡¢
 	¥Õ¥¡¥¤¥ë¤È¥Ç¥£¥ì¥¯¥È¥ê¤ò¥Æ¡¼¥×¤Ë½ñ¤­¹þ¤ß¤Þ¤¹¡£<command>tar</command>
 	¤Ï &man.cpio.1;
 	¤Ç»ÈÍѲÄǽ¤Ê¥Õ¥ë¥ì¥ó¥¸¤Î¥ª¥×¥·¥ç¥ó¤Ë¤ÏÂбþ¤·¤Æ¤¤¤Þ¤»¤ó¤¬¡¢
 	<command>tar</command> ¤Ë¤Ï <command>cpio</command>
 	¤¬»ÈÍѤ¹¤ë¤è¤¦¤Ê´ñ̯¤Ê¥³¥Þ¥ó¥É¥Ñ¥¤¥×¥é¥¤¥ó¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£</para>
 
       <indexterm><primary><command>tar</command></primary></indexterm>
       <para><command>tar</command>
 	¤Î¿¤¯¤ÎÈǤϥͥåȥ¥¯·Ðͳ¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤Ë¤ÏÂбþ¤·¤Æ¤¤¤Þ¤»¤ó¡£
 	FreeBSD ¤¬»ÈÍѤ·¤Æ¤¤¤ë GNU ÈǤΠ<command>tar</command> ¤Ï¡¢
 	<command>rdump</command>
 	¤ÈƱ¤¸¹½Ê¸¤Ç¥ê¥â¡¼¥È¥Ç¥Ð¥¤¥¹¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£
 	<hostid>komodo</hostid> ¤È¸Æ¤Ð¤ì¤ë Sun ¤ËÀܳ¤µ¤ì¤¿ Exabyte
 	¥Æ¡¼¥×¥É¥é¥¤¥Ö¤ËÂФ·¤Æ <command>tar</command>
 	¤ò¼Â¹Ô¤¹¤ë¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>/usr/bin/tar cf komodo:/dev/nsa8 . 2>&amp;1</userinput></screen>
 
       <para>¥ê¥â¡¼¥È¥Ç¥Ð¥¤¥¹¤ËÂбþ¤·¤Æ¤¤¤Ê¤¤ÈǤËÂФ·¤Æ¤Ï¡¢¥Ñ¥¤¥×¥é¥¤¥ó¤È
 	<command>rsh</command>
 	¤ò»ÈÍѤ·¤Æ¥ê¥â¡¼¥È¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ë¥Ç¡¼¥¿¤òÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>tar cf - . | rsh <replaceable>hostname</replaceable> dd of=<replaceable>tape-device</replaceable> obs=20b</userinput></screen>
 
       <para>¥Í¥Ã¥È¥ï¡¼¥¯¤ò±Û¤¨¤¿¥Ð¥Ã¥¯¥¢¥Ã¥×¤Î¥»¥­¥å¥ê¥Æ¥£¤ò·üÇ°¤·¤Æ¤¤¤ë¤Ê¤é¡¢
 	<command>rsh</command> ¤ÎÂå¤ï¤ê¤Ë <command>ssh</command>
 	¤ò»È¤¦¤Ù¤­¤Ç¤¹¡£</para>
     </sect2>
 
     <sect2>
       <title><command>cpio</command></title>
       <indexterm>
 	<primary>¥Ð¥Ã¥¯¥¢¥Ã¥×¥½¥Õ¥È¥¦¥§¥¢</primary>
 	<secondary><command>cpio</command></secondary>
       </indexterm>
 
       <para>&man.cpio.1; ¤ÏËÜÍè &unix;
 	¥Õ¥¡¥¤¥ë¤ò¼§µ¤¥á¥Ç¥£¥¢¤Ç¸ò´¹¤¹¤ë¤¿¤á¤Î¥×¥í¥°¥é¥à¤Ç¤¹¡£
 	<command>cpio</command> ¤Ï¥Ð¥¤¥È¥¹¥ï¥Ã¥Ô¥ó¥°¡¢
 	¿¤¯¤Î°Û¤Ê¤ë¥¢¡¼¥«¥¤¥Ö¥Õ¥©¡¼¥Þ¥Ã¥È¤Î½ñ¤­¹þ¤ß¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê
 	(¤½¤ì°Ê³°¤Ë¤â¿¿ô¤Î¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹)¡¢
 	¥Ñ¥¤¥×¤Ç¾¤Î¥×¥í¥°¥é¥à¤Ë¥Ç¡¼¥¿¤òÅϤ¹¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
 	¤³¤ÎºÇ¸å¤Ë¤¢¤²¤¿ÆÃħ¤¬¡¢<command>cpio</command>
 	¤ò¥¤¥ó¥¹¥È¡¼¥ë¥á¥Ç¥£¥¢¤È¤·¤Æ¤ÏÍ¥¤ì¤¿ÁªÂò»è¤Ë¤·¤Æ¤¤¤Þ¤¹¡£
 	<command>cpio</command>
 	¤Ï¥Ç¥£¥ì¥¯¥È¥ê¥Ä¥ê¡¼¤Îõº÷¤Îµ¡Ç½¤Ï¤Ê¤¯¡¢¥Õ¥¡¥¤¥ë¥ê¥¹¥È¤Ï
 	<filename>stdin</filename> ¤«¤é¤ÎÆþÎϤǤʤ¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£</para>
       <indexterm><primary><command>cpio</command></primary></indexterm>
 
       <para><command>cpio</command>
 	¤Ï¥Í¥Ã¥È¥ï¡¼¥¯·Ðͳ¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤Ë¤ÏÂбþ¤·¤Æ¤¤¤Þ¤»¤ó¡£
 	°Ê²¼¤Î¤è¤¦¤Ë¥Ñ¥¤¥×¥é¥¤¥ó¤È <command>rsh</command>
 	¤òÍѤ¤¤Æ¥ê¥â¡¼¥È¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ë¥Ç¡¼¥¿¤òÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>for f in <replaceable>directory_list; do</replaceable></userinput>
 <userinput>find $f &gt;&gt; backup.list</userinput>
 <userinput>done</userinput>
 &prompt.root; <userinput>cpio -v -o --format=newc &lt; backup.list | ssh <replaceable>user</replaceable>@<replaceable>host</replaceable> "cat &gt; <replaceable>backup_device</replaceable>"</userinput></screen>
 
       <para><replaceable>directory_list</replaceable>
 	¤Ï¥Ð¥Ã¥¯¥¢¥Ã¥×¤·¤¿¤¤¥Ç¥£¥ì¥¯¥È¥ê¤Î¥ê¥¹¥È¤Ç¡¢
 	<replaceable>user</replaceable>@<replaceable>host</replaceable>
 	¤Ï¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¼Â¹Ô¤·¤¿¤¤¥æ¡¼¥¶¤È¥Û¥¹¥È̾¤ÎÁȤǤ¢¤ê¡¢
 	<replaceable>backup_device</replaceable>
 	¤Ï¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò½ñ¤­¹þ¤ß¤¿¤¤¥Ç¥Ð¥¤¥¹¤Ç¤¹
 	(¤¿¤È¤¨¤Ð <filename>/dev/nsa0</filename>)¡£</para>
     </sect2>
 
     <sect2>
       <title><command>pax</command></title>
       <indexterm>
 	<primary>¥Ð¥Ã¥¯¥¢¥Ã¥×¥½¥Õ¥È¥¦¥§¥¢</primary>
 	<secondary><command>pax</command></secondary>
       </indexterm>
       <indexterm><primary><command>pax</command></primary></indexterm>
       <indexterm><primary>POSIX</primary></indexterm>
       <indexterm><primary>IEEE</primary></indexterm>
 
       <para>&man.pax.1; ¤Ï <command>tar</command> ¤È
 	<command>cpio</command>	¤ËÂФ¹¤ë IEEE/&posix;
 	¤Î²óÅú¤Ç¤¹¡£Ä¹Ç¯¤Î´Ö¡¢¤µ¤Þ¤¶¤Þ¤ÊÈǤÎ
 	<command>tar</command> ¤È <command>cpio</command>
 	¤Ï¸ß¤¤¤Ë¤ï¤º¤«¤ËÈó¸ß´¹¤Ë¤Ê¤Ã¤Æ¤­¤Æ¤¤¤Þ¤·¤¿¡£
 	¤½¤ì¤é¤ò¤·¤é¤ßÄÙ¤·¤Ëɸ½à²½¤¹¤ëÂå¤ï¤ê¤Ë¡¢&posix;
 	¤Ï¿·¤·¤¤¥¢¡¼¥«¥¤¥Ö¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤òºî¤ê¤Þ¤·¤¿¡£
 	<command>pax</command>
 	¤Ï¡¢¤¤¤¯¤Ä¤â¤Î <command>cpio</command> ¤ä
 	<command>tar</command>
 	¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎÆɤ߽ñ¤­¤ËÂбþ¤·¤è¤¦¤È»î¤ß¤Æ¤¤¤ë¤Û¤«¡¢
 	ÀìÍѤ˿·¤·¤¤¥Õ¥©¡¼¥Þ¥Ã¥È¤ò³«È¯¤·¤Þ¤·¤¿¡£
 	¥³¥Þ¥ó¥É·²¤Ï <command>tar</command> ¤è¤ê¤â
 	<command>cpio</command> ¤ÎÊý¤Ë¤¤¤¯¤Ö¤ó»÷¤Æ¤¤¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2 id="backups-programs-amanda">
       <title><application>Amanda</application></title>
       <indexterm>
 	<primary>¥Ð¥Ã¥¯¥¢¥Ã¥×¥½¥Õ¥È¥¦¥§¥¢</primary>
 	<secondary><application>Amanda</application></secondary>
       </indexterm>
       <indexterm><primary><application>Amanda</application></primary></indexterm>
 
       <!-- Remove link until <port> tag is available -->
       <para><application>Amanda</application> (Advanced Maryland
 	Network Disk Archiver) ¤Ïñ°ì¤Î¥×¥í¥°¥é¥à¤Ç¤Ï¤Ê¤¯¡¢
 	¥¯¥é¥¤¥¢¥ó¥È/¥µ¡¼¥Ð·¿¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¥·¥¹¥Æ¥à¤Ç¤¹¡£
 	<application>Amanda</application> ¥µ¡¼¥Ð¤Ï¡¢
 	<application>Amanda</application> ¥¯¥é¥¤¥¢¥ó¥È¤òÍ­¤¹¤ë
 	¥Í¥Ã¥È¥ï¡¼¥¯¤ËÀܳ¤µ¤ì¤¿¥³¥ó¥Ô¥å¡¼¥¿¤«¤é¥Ç¡¼¥¿¤ò¼õ¤±¼è¤ê¡¢
 	È÷¤¨ÉÕ¤±¤é¤ì¤¿¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤·¤Þ¤¹¡£
 	¤¤¤¯¤Ä¤â¤ÎÂçÍÆÎ̥ǥ£¥¹¥¯¤òÈ÷¤¨¤¿¥µ¥¤¥È¤Ç¤Î¶¦Ä̤ÎÌäÂê¤Ï¡¢
 	¥Ç¡¼¥¿¥Ç¥£¥ì¥¯¥È¥ê¤ò¥Æ¡¼¥×¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¤Î¤Ë»þ´Ö¤¬¤«¤«¤ê¤¹¤®¤ë¤³¤È¤Ç¤¹¡£
 	<application>Amanda</application> ¤Ï¤³¤ÎÌäÂê¤ò²ò·è¤·¤Þ¤¹¡£
 	<application>Amanda</application> ¤Ï
 	<quote>¥Û¡¼¥ë¥Ç¥£¥ó¥°¥Ç¥£¥¹¥¯</quote> ¤ò»ÈÍѤ·¤Æ¡¢
 	Ʊ»þ¤ËÊ£¿ô¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¹Ô¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	<application>Amanda</application> ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ë¤«¤«¤ì¤¿¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Õ¥ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤òÆÃÄê¤Î´Ö³Ö¤Ç¤È¤ë¤¿¤á¤Ë
 	<quote>¥¢¡¼¥«¥¤¥Ö¥»¥Ã¥È</quote> ¤È¸Æ¤Ð¤ì¤ë¥Æ¡¼¥×¥°¥ë¡¼¥×¤òºîÀ®¤·¤Þ¤¹¡£
 	<quote>¥¢¡¼¥«¥¤¥Ö¥»¥Ã¥È</quote> ¤Ë¤Ï
 	Ìë´Ö¤ËºîÀ®¤µ¤ì¤ë¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÁýʬ (¤Þ¤¿¤Ïº¹Ê¬)
 	¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤â´Þ¤Þ¤ì¤Þ¤¹¡£
 	¾ã³²¤¬µ¯¤­¤¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥ê¥¹¥È¥¢¤Ë¤Ï¡¢
 	ºÇ¤â¿·¤·¤¤¥Õ¥ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤ÈÁýʬ¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤¬É¬ÍפǤ¹¡£</para>
 
       <para>ÀßÄê¥Õ¥¡¥¤¥ë¤Ç¤Ï¡¢¥Ð¥Ã¥¯¥¢¥Ã¥×¤ÎÀ©¸æ¤È
 	<application>Amanda</application>
 	¤Ë¤è¤ë¥Í¥Ã¥È¥ï¡¼¥¯¥È¥é¥Õ¥£¥Ã¥¯Î̤òÀßÄꤷ¤Þ¤¹¡£
 	<application>Amanda</application>
 	¤Ï¾åµ­¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¥×¥í¥°¥é¥à¤Î¤¤¤º¤ì¤«¤ò»È¤Ã¤Æ¥Ç¡¼¥¿¤ò¥Æ¡¼¥×¤Ë½ñ¤­¹þ¤ß¤Þ¤¹¡£
 	<application>Amanda</application> ¤Ï port ¤Þ¤¿¤Ï package
 	¤È¤·¤ÆÍøÍѲÄǽ¤Ç¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£</para>
     </sect2>
 
     <sect2>
       <title>²¿¤â¤·¤Ê¤¤</title>
 
       <para><quote>²¿¤â¤·¤Ê¤¤</quote>
 	¤È¤¤¤¦¤Î¤Ï¥³¥ó¥Ô¥å¡¼¥¿¤Î¥×¥í¥°¥é¥à¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢
 	¥Ð¥Ã¥¯¥¢¥Ã¥×¤ÎÀïά¤È¤·¤ÆºÇ¤â¹­¤¯ºÎÍѤµ¤ì¤Æ¤¤¤Þ¤¹¡£
 	¤³¤ì¤Ë¤Ï½é´üÅê»ñ¤¬É¬Íפ¢¤ê¤Þ¤»¤ó¡£
 	½¾¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¥Ð¥Ã¥¯¥¢¥Ã¥×¥¹¥±¥¸¥å¡¼¥ë¤â¤¢¤ê¤Þ¤»¤ó¡£
 	¤¿¤À²¿¤â¤·¤Ê¤¤¤À¤±¤Ç¤¹¡£¥Ç¡¼¥¿¤Ë²¿¤«µ¯¤­¤¿¤é¶ì¾Ð¤¤¤·¤ÆÂѤ¨¤Æ¤¯¤À¤µ¤¤!</para>
 
       <para>¤¢¤Ê¤¿¤Ë¤È¤Ã¤Æ»þ´Ö¤ä¥Ç¡¼¥¿¤Î²ÁÃͤ¬¾¯¤Ê¤¤¤«¡¢
 	¤¢¤ë¤¤¤Ï¤Þ¤Ã¤¿¤¯¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð <quote>²¿¤â¤·¤Ê¤¤</quote>
 	¤Î¤Ï¤¢¤Ê¤¿¤Î¥³¥ó¥Ô¥å¡¼¥¿¤ËºÇ¤âŬ¤·¤¿¥Ð¥Ã¥¯¥¢¥Ã¥×¥×¥í¥°¥é¥à¤Ç¤·¤ç¤¦¡£
 	¤·¤«¤·Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£&unix; ¤ÏÊØÍø¤Ê¥Ä¡¼¥ë¤Ç¤¹¡£
 	6&nbsp;¥ö·î¤â»ÈÍѤ·¤Æ¤¤¤ì¤Ð¡¢
 	¤¢¤Ê¤¿¤Ë¤È¤Ã¤Æ²ÁÃͤΤ¢¤ë¥Õ¥¡¥¤¥ë¤Î»³¤¬½ÐÍè¾å¤¬¤Ã¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£</para>
 
       <para><quote>²¿¤â¤·¤Ê¤¤</quote>
 	¤³¤È¤Ï¥³¥ó¥Ô¥å¡¼¥¿¤¬Æ±¤¸¤â¤Î¤ò¤â¤¦°ìÅÙºî¤êľ¤¹¤³¤È¤Î¤Ç¤­¤ë
 	<filename>/usr/obj</filename>
 	¤ä¤½¤Î¾¤Î¥Ç¥£¥ì¥¯¥È¥ê¥Ä¥ê¡¼¤Ë¤Ä¤¤¤Æ¤ÏŬÀڤʥХ寥¢¥Ã¥×ÊýË¡¤Ç¤¹¡£
 	°ìÎã¤È¤·¤Æ¡¢¤³¤Î¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î HTML ÈÇ ¤Þ¤¿¤Ï &postscript;
 	ÈǤò¹½À®¤¹¤ë¥Õ¥¡¥¤¥ë¤¬¤¢¤ê¤Þ¤¹¡£
 	¤³¤ì¤é¤Îʸ½ñ·Á¼°¤Ï SGML ¥Õ¥¡¥¤¥ë¤«¤éºîÀ®¤µ¤ì¤¿¤â¤Î¤Ç¤¹¡£
 	HTML ¤Þ¤¿¤Ï &postscript; ¥Õ¥¡¥¤¥ë¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£
 	SGML ¥Õ¥¡¥¤¥ë¤ÏÄê´üŪ¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2>
       <title>¤É¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¥×¥í¥°¥é¥à¤¬ºÇŬ¤Ç¤¹¤«?</title>
       <indexterm>
 	<primary>LISA</primary>
       </indexterm>
 
       <para>&man.dump.8; ¤Ç¤¹¡£<emphasis>°Ê¾å¡£</emphasis>
 	Elizabeth D. Zwicky
 	¤Ï¤³¤³¤Ç¸¡Æ¤¤·¤¿¥×¥í¥°¥é¥à¤¹¤Ù¤Æ¤Ë¤Ä¤¤¤Æ¹éÌäŪ¤Ê¥Æ¥¹¥È¤ò¹Ô¤¤¤Þ¤·¤¿¡£
 	¤¹¤Ù¤Æ¤Î¥Ç¡¼¥¿¤È &unix;
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¾õÂÖ¤¹¤Ù¤Æ¤òÊݸ¤¹¤ë¤Î¤ËºÇŬ¤Ê¤Î¤Ï¡¢ÌÀ¤é¤«¤Ë
 	<command>dump</command> ¤Ç¤¹¡£
 	Elizabeth ¤Ï¿¼ï¿ÍͤÎÆðۤʾõÂÖ
 	(¤¤¤¯¤Ä¤«¤Ï¤¢¤Þ¤êÄÁ¤·¤¯¤Ê¤¤¤â¤Î¤â¤¢¤ê¤Þ¤¹)
 	¤ò´Þ¤à¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤·¡¢
 	¤½¤ì¤é¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤È¥ê¥¹¥È¥¢¤ò¹Ô¤Ã¤Æ¡¢
 	¤½¤ì¤¾¤ì¤Î¥×¥í¥°¥é¥à¤Î¥Æ¥¹¥È¤ò¹Ô¤¤¤Þ¤·¤¿¡£ÆðۤʾõÂ֤Ȥϡ¢
 	¥Û¡¼¥ë¤¬¤¢¤ë¥Õ¥¡¥¤¥ë¡¢¥Û¡¼¥ë¤È¥Ì¥ë¥Ö¥í¥Ã¥¯¤¬¤¢¤ë¥Õ¥¡¥¤¥ë¡¢
 	´ñ̯¤Êʸ»ú¤ò¥Õ¥¡¥¤¥ë̾¤Ë»ý¤Ä¥Õ¥¡¥¤¥ë¡¢Æɤ߼è¤êÉԲġ¢
 	½ñ¤­¹þ¤ßÉԲĤΥե¡¥¤¥ë¡¢¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë¡¢
 	¥Ð¥Ã¥¯¥¢¥Ã¥×Ãæ¤Î¥Õ¥¡¥¤¥ë¤Î¥µ¥¤¥ºÊѹ¹¡¢
 	¥Ð¥Ã¥¯¥¢¥Ã¥×Ãæ¤Î¥Õ¥¡¥¤¥ë¤ÎºîÀ®¤ª¤è¤Óºï½ü¡¢¤Ê¤É¤Ç¤¹¡£
 	Èà½÷¤Ï 1991 ǯ 10 ·î¤Î LISA V ¤Ç·ë²Ì¤òȯɽ¤·¤Æ¤¤¤Þ¤¹¡£
 	<ulink url="http://berdmann.dyndns.org/zwicky/testdump.doc.html">torture-testing Backup and Archive Programs</ulink>
 	¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
     </sect2>
 
     <sect2>
       <title>¶ÛµÞ»þ¤Î¥ê¥¹¥È¥¢¼ê½ç</title>
 
       <sect3>
 	<title>»´»ö¤¬µ¯¤­¤ëÁ°¤Ë</title>
 
 	<para>ȯÀ¸¤¹¤ë²ÄǽÀ­¤¬¤¢¤ë¤É¤Î¤è¤¦¤Ê»´»ö¤ËÂФ·¤Æ¤â¡¢
 	  È÷¤¨¤ë¤Î¤ËɬÍפʼê½ç¤Ï°Ê²¼¤Î 4 ¥¹¥Æ¥Ã¥×¤À¤±¤Ç¤¹¡£</para>
 	<indexterm>
 	  <primary><command>disklabel</command></primary>
 	</indexterm>
 
 	<para>ºÇ½é¤Ë¡¢
 	  ³Æ¥Ç¥£¥¹¥¯¤Î¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ë
 	  (<filename>/etc/fstab</filename>)¡¢
 	  ¥Ö¡¼¥È¥á¥Ã¥»¡¼¥¸Á´ÂΤò¤½¤ì¤¾¤ì 2 Ë示¤Ä°õºþ¤·¤Þ¤¹
 	  (¤¿¤È¤¨¤Ð <command>disklabel da0 | lpr</command>)¡£</para>
 
 	<indexterm><primary>fix-it ¥Õ¥í¥Ã¥Ô¡¼</primary></indexterm>
 	<para>2 ÈÖÌܤˡ¢¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤È fix-it ¥Õ¥í¥Ã¥Ô¡¼
 	  (<filename>boot.flp</filename> ¤ª¤è¤Ó <filename>fixit.flp</filename>)
 	  ¤Ë¤½¤Î¥·¥¹¥Æ¥à¤Î¥Ç¥Ð¥¤¥¹¤¬¤¹¤Ù¤Æ´Þ¤Þ¤ì¤Æ¤¤¤ë¤«³Îǧ¤·¤Þ¤¹¡£
 	  ºÇ¤â´Êñ¤Ë³Îǧ¤¹¤ëÊýË¡¤Ï¡¢¥Õ¥í¥Ã¥Ô¡¼¤ò¥É¥é¥¤¥Ö¤ËÆþ¤ì¤Æ¥Þ¥·¥ó¤ò¥ê¥Ö¡¼¥È¤·¤Æ¥Ö¡¼¥È¥á¥Ã¥»¡¼¥¸¤ò³Îǧ¤¹¤ë¤³¤È¤Ç¤¹¡£
 	  ¤¢¤Ê¤¿¤Î¥·¥¹¥Æ¥à¤Î¥Ç¥Ð¥¤¥¹¤Î¤¹¤Ù¤Æ¤¬´Þ¤Þ¤ì¡¢
 	  µ¡Ç½¤·¤Æ¤¤¤ì¤Ð 3 ÈÖÌܤμê½ç¤Ë¿Ê¤ó¤Ç¤¯¤À¤µ¤¤¡£</para>
 
 	<para>¤µ¤â¤Ê¤±¤ì¤Ð¡¢
 	  ¤½¤Î¥·¥¹¥Æ¥à¤Î¤¹¤Ù¤Æ¤Î¥Ç¥£¥¹¥¯¤ò¥Þ¥¦¥ó¥È¤Ç¤­¡¢
 	  ¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ë¤â¥¢¥¯¥»¥¹¤Ç¤­¤ë¥«¡¼¥Í¥ë¤òÈ÷¤¨¤¿
 	  ¥«¥¹¥¿¥à¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤ò 2 ËçºîÀ®¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	  ¤³¤ì¤é¤Î¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë¤Ï <command>fdisk</command>,
 	  <command>disklabel</command>, <command>newfs</command>,
 	  <command>mount</command>
 	  ¤È¡¢ÍøÍѤ¹¤ë¥Ð¥Ã¥¯¥¢¥Ã¥×¥×¥í¥°¥é¥à¤¬Æþ¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
 	  ¤³¤ì¤é¤Î¥×¥í¥°¥é¥à¤Ï¥¹¥¿¥Æ¥£¥Ã¥¯¥ê¥ó¥¯¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
 	  <command>dump</command> ¤ò»ÈÍѤ¹¤ë¤Î¤Ê¤é¡¢¤³¤Î¥Õ¥í¥Ã¥Ô¡¼¤Ë¤Ï
 	  <command>restore</command> ¤â´Þ¤Þ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
 	<para>3 ÈÖÌܤˡ¢Äê´üŪ¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×¤òºîÀ®¤·¤Þ¤¹¡£
 	  ºÇ¸å¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤Î¸å¤Ç¹Ô¤ï¤ì¤¿Êѹ¹¤Ï¡¢²óÉü¤Ç¤­¤º¤Ë¼º¤ï¤ì¤Þ¤¹¡£
 	  ¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×¤Ë¥é¥¤¥È¥×¥í¥Æ¥¯¥È¤ò»Ü¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	<para>4 ÈÖÌܤˡ¢¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯
 	  (<filename>boot.flp</filename> ¤È
 	  <filename>fixit.flp</filename>¡¢
 	  ¤«¡¢Âè 2 Ãʳ¬¤ÇºîÀ®¤·¤¿
 	  2 Ëç¤Î¥«¥¹¥¿¥à¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Î¤É¤Á¤é¤«)
 	  ¤ª¤è¤Ó¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×¤Î¥Æ¥¹¥È¤ò¤·¤Þ¤¹¡£
 	  ¼ê½ç¤Î¥á¥â¤òºî¤ê¤Þ¤·¤ç¤¦¡£
 	  ¤³¤Î¥á¥â¤Ï¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¡¢°õºþ¤·¤¿»æ¡¢
 	  ¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×¤È°ì½ï¤ËÊݸ¤·¤Æ¤ª¤­¤Þ¤¹¡£
 	  ¥ê¥¹¥È¥¢¤ò¹Ô¤¦¤È¤­¤Ë¤Ï¡¢
 	  ¤³¤Î¥á¥â¤¬¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×¤ò²õ¤¹¤Î¤òËɤ°¤¯¤é¤¤¼è¤êÍ𤷤Ƥ¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó
 	  (¤É¤Î¤è¤¦¤Ë?
 	  <command>tar xvf /dev/sa0</command> ¤ÎÂå¤ï¤ê¤Ë¡¢¤¦¤Ã¤«¤ê
 	  <command>tar cvf /dev/sa0</command>
 	  ¤ÈÆþÎϤ·¤Æ¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×¤ò¾å½ñ¤­¤·¤Æ¤·¤Þ¤¦¤«¤â¤·¤ì¤Þ¤»¤ó)¡£</para>
 
 	<note>
 	  <title>ÌõÃí</title>
 	  <para>¾å½ñ¤­¤Ï¥é¥¤¥È¥×¥í¥Æ¥¯¥È¤ò¤·¤Æ¤ª¤±¤ÐËɤ²¤Þ¤¹¤¬¡¢
 	    ²¿¤é¤«¤Î¸¶°ø¤Ç¥×¥í¥Æ¥¯¥È¤¬¤Ï¤º¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
 	    ¤Á¤Ê¤ß¤ËÌõ¼Ô¤Î·Ð¸³¤«¤é¸À¤¨¤Ð¡¢
 	    ¾å¤Î¤è¤¦¤Ê¥ß¥¹¥¿¥¤¥×¤Ï·ë¹½µ¯¤­¤Þ¤¹¡£</para>
 	</note>
 
 	<para>°ÂÁ´À­¤òÁý¤¹¤¿¤á¤Ë¡¢Ëè²ó¡¢
 	  ¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤òºîÀ®¤·¡¢
 	  2&nbsp;´¬¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×¤ò¼è¤ê¤Þ¤¹¡£
 	  °ìÊý¤òÎ¥¤ì¤¿¾ì½ê¤ËÊݴɤ·¤Þ¤¹¡£
 	  Î¥¤ì¤¿¾ì½ê¤ÏƱ¤¸»ö̳½ê¤Î·úʪ¤ÎÃϲ¼¼¼¤Ç¤Ï¤¤¤±¤Þ¤»¤ó¡£
 	  À¤³¦ËÇ°×¥»¥ó¥¿¡¼¥Ó¥ë¤Ë¤¢¤Ã¤¿¿ô¿¤¯¤Î²ñ¼Ò¤Ï¡¢
 	  ¶ì¤¤·Ð¸³¤Ë¤è¤ê¤³¤Î¶µ·±¤òÆÀ¤Þ¤·¤¿¡£Î¥¤ì¤¿¾ì½ê¤È¤Ï¡¢
 	  ¥³¥ó¥Ô¥å¡¼¥¿¤ä¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤«¤é½½Ê¬¤Êµ÷Î¥¤ò¼è¤Ã¤Æ
 	  ʪÍýŪ¤ËʬΥ¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
 	<example>
 	  <title>¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤òºîÀ®¤¹¤ë¥¹¥¯¥ê¥×¥È</title>
 
 	  <programlisting><![CDATA[#!/bin/sh
 #
 # create a restore floppy
 #
 # format the floppy
 #
 PATH=/bin:/sbin:/usr/sbin:/usr/bin
 
 fdformat -q fd0
 if [ $? -ne 0 ]
 then
 	 echo "Bad floppy, please use a new one"
 	 exit 1
 fi
 
 # place boot blocks on the floppy
 #
 disklabel -w -B /dev/fd0c fd1440
 
 #
 # newfs the one and only partition
 #
 newfs -t 2 -u 18 -l 1 -c 40 -i 5120 -m 5 -o space /dev/fd0a
 
 #
 # mount the new floppy
 #
 mount /dev/fd0a /mnt
 
 #
 # create required directories
 #
 mkdir /mnt/dev
 mkdir /mnt/bin
 mkdir /mnt/sbin
 mkdir /mnt/etc
 mkdir /mnt/root
 mkdir /mnt/mnt			# for the root partition
 mkdir /mnt/tmp
 mkdir /mnt/var
 
 #
 # populate the directories
 #
 if [ ! -x /sys/compile/MINI/kernel ]
 then
 	 cat << EOM
 The MINI kernel does not exist, please create one.
 Here is an example config file:
 #
 # MINI - A kernel to get FreeBSD onto a disk.
 #
 machine         "i386"
 cpu             "I486_CPU"
 ident           MINI
 maxusers        5
 
 options         INET                    # needed for _tcp _icmpstat _ipstat
                                         #            _udpstat _tcpstat _udb
 options         FFS                     #Berkeley Fast File System
 options         FAT_CURSOR              #block cursor in syscons or pccons
 options         SCSI_DELAY=15           #Be pessimistic about Joe SCSI device
 options         NCONS=2                 #1 virtual consoles
 options         USERCONFIG              #Allow user configuration with -c XXX
 
 config          kernel	root on da0 swap on da0 and da1 dumps on da0
 
 device          isa0
 device          pci0
 
 device          fdc0	at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
 device          fd0	at fdc0 drive 0
 
 device          ncr0
 
 device          scbus0
 
 device          sc0	at isa? port "IO_KBD" tty irq 1 vector scintr
 device          npx0	at isa? port "IO_NPX" irq 13 vector npxintr
 
 device          da0
 device          da1
 device          da2
 
 device          sa0
 
 pseudo-device   loop            # required by INET
 pseudo-device   gzip            # Exec gzipped a.out's
 EOM
 	 exit 1
 fi
 
 cp -f /sys/compile/MINI/kernel /mnt
 
 gzip -c -best /sbin/init > /mnt/sbin/init
 gzip -c -best /sbin/fsck > /mnt/sbin/fsck
 gzip -c -best /sbin/mount > /mnt/sbin/mount
 gzip -c -best /sbin/halt > /mnt/sbin/halt
 gzip -c -best /sbin/restore > /mnt/sbin/restore
 
 gzip -c -best /bin/sh > /mnt/bin/sh
 gzip -c -best /bin/sync > /mnt/bin/sync
 
 cp /root/.profile /mnt/root
 
 cp -f /dev/MAKEDEV /mnt/dev
 chmod 755 /mnt/dev/MAKEDEV
 
 chmod 500 /mnt/sbin/init
 chmod 555 /mnt/sbin/fsck /mnt/sbin/mount /mnt/sbin/halt
 chmod 555 /mnt/bin/sh /mnt/bin/sync
 chmod 6555 /mnt/sbin/restore
 
 #
 # create the devices nodes
 #
 cd /mnt/dev
 ./MAKEDEV std
 ./MAKEDEV da0
 ./MAKEDEV da1
 ./MAKEDEV da2
 ./MAKEDEV sa0
 ./MAKEDEV pty0
 cd /
 
 #
 # create minimum file system table
 #
 cat &gt; /mnt/etc/fstab &lt;&lt;EOM
 /dev/fd0a    /    ufs    rw  1  1
 EOM
 
 #
 # create minimum passwd file
 #
 cat > /mnt/etc/passwd <<EOM
 root:*:0:0:Charlie &:/root:/bin/sh
 EOM
 
 cat > /mnt/etc/master.passwd <<EOM
 root::0:0::0:0:Charlie &:/root:/bin/sh
 EOM
 
 chmod 600 /mnt/etc/master.passwd
 chmod 644 /mnt/etc/passwd
 /usr/sbin/pwd_mkdb -d/mnt/etc /mnt/etc/master.passwd
 
 #
 # umount the floppy and inform the user
 #
 /sbin/umount /mnt
 echo "The floppy has been unmounted and is now ready."]]></programlisting>
         </example>
       </sect3>
 
       <sect3>
 	<title>»´»ö¤Î¸å¤Ï</title>
 
 	<para>½ÅÍפÊÌäÂê¤Ï¡¢¥Ï¡¼¥É¥¦¥§¥¢¤¬À¸¤­»Ä¤Ã¤¿¤«¤É¤¦¤«¤Ç¤¹¡£
 	  Äê´üŪ¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¼è¤Ã¤Æ¤¤¤ì¤Ð¡¢
 	  ¥½¥Õ¥È¥¦¥§¥¢¤Ë¤Ä¤¤¤Æ¿´ÇÛ¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£</para>
 
 	<para>¥Ï¡¼¥É¥¦¥§¥¢¤Ë¾ã³²¤¬¤¢¤ì¤Ð¡¢
 	  ¥³¥ó¥Ô¥å¡¼¥¿¤ò»ÈÍѤ¹¤ëÁ°¤Ë¤½¤ÎÉôÉʤò¸ò´¹¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	<para>¥Ï¡¼¥É¥¦¥§¥¢¤ËÌäÂ̵꤬¤±¤ì¤Ð¡¢¥Õ¥í¥Ã¥Ô¡¼¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
 	  ¥«¥¹¥¿¥à¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ò»ÈÍѤ·¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢
 	  ¥·¥ó¥°¥ë¥æ¡¼¥¶¥â¡¼¥É¤Ç¥Ö¡¼¥È¤·¤Æ (<prompt>boot:</prompt>
 	  ¥×¥í¥ó¥×¥È¤Ç <literal>-s</literal> ¤òÆþÎϤ·¤Þ¤¹)¡¢
 	  ¼¡¤ÎÃÊÍî¤ÏÈô¤Ð¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	<para><filename>boot.flp</filename> ¤È <filename>fixit.flp</filename>
 	  ¤ò»ÈÍѤ·¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¤³¤Î¤Þ¤ÞÆɤ߿ʤá¤Æ¤¯¤À¤µ¤¤¡£
 	  <filename>boot.flp</filename>
 	  ¥Õ¥í¥Ã¥Ô¡¼¤ò¥Õ¥í¥Ã¥Ô¡¼¥É¥é¥¤¥Ö¤ËÆþ¤ì¤Æ¡¢
 	  ¥³¥ó¥Ô¥å¡¼¥¿¤òµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£
 	  ËÜÍè¤Î¥¤¥ó¥¹¥È¡¼¥ë¥á¥Ë¥å¡¼¤¬²èÌ̤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£
 	  <literal>Fixit--Repair mode with CDROM or floppy.</literal>
 	  ¥ª¥×¥·¥ç¥ó¤òÁªÂò¤·¤Þ¤¹¡£»Ø¼¨¤µ¤ì¤¿Ä̤ê
 	  <filename>fixit.flp</filename> ¤ò¤¤¤ì¤Æ¤¯¤À¤µ¤¤¡£
 	  <command>restore</command> ¤È¤½¤Î¾ɬÍפȤʤë¥×¥í¥°¥é¥à¤Ï
 	  <filename>/mnt2/stand</filename> ¤Ë¤¢¤ê¤Þ¤¹¡£</para>
 
 	<para>¤½¤·¤Æ¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò°ì¤Ä¤º¤Ä²óÉü¤·¤Þ¤¹¡£</para>
 
 	<indexterm>
 	  <primary><command>mount</command></primary>
 	</indexterm>
 	<indexterm><primary>root ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó</primary></indexterm>
 	<indexterm>
 	  <primary><command>disklabel</command></primary>
 	</indexterm>
 	<indexterm>
 	  <primary><command>newfs</command></primary>
 	</indexterm>
 	<para>ºÇ½é¤Î¥Ç¥£¥¹¥¯¤Î¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò <command>mount</command>
 	  ¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤ (¤¿¤È¤¨¤Ð <command>mount /dev/da0a /mnt</command>)¡£
 	  ¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤¬Ç˲õ¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢<command>disklabel</command>
 	  ¤òÍѤ¤¤Æ¤¢¤é¤«¤¸¤á°õºþ¤·¤ÆÊݸ¤·¤Æ¤ª¤¤¤¿Ä̤ê¤Ë¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºî¤êľ¤·¡¢¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤òºîÀ®¤·¤Æ¤¯¤À¤µ¤¤¡£
 	  <command>newfs</command> ¤ò»ÈÍѤ·¤Æ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºî¤êľ¤·¤Þ¤¹¡£
 	  ¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÆɤ߽ñ¤­²Äǽ¤Ë¥Þ¥¦¥ó¥È¤·Ä¾¤·¤Þ¤¹
 	  (<command>mount -u -o rw /mnt</command>)¡£
 	  ¥Ð¥Ã¥¯¥¢¥Ã¥×¥×¥í¥°¥é¥à¤È¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×¤ò»ÈÍѤ·¤Æ¡¢
 	  ¤³¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ç¡¼¥¿¤ò²óÉü¤·¤Þ¤¹
 	  (¤¿¤È¤¨¤Ð <command>restore vrf /dev/sa0</command>)¡£
 	  ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥¢¥ó¥Þ¥¦¥ó¥È¤·¤Þ¤¹
 	  (¤¿¤È¤¨¤Ð <command>umount /mnt</command>)¡£
 	  ¾ã³²¤ò¼õ¤±¤¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤½¤ì¤¾¤ì¤Ë¤Ä¤¤¤Æ·«¤êÊÖ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	<para>¥·¥¹¥Æ¥à¤¬Æ°¤­½Ð¤·¤¿¤é¡¢
 	  ¿·¤·¤¤¥Æ¡¼¥×¤Ë¥Ç¡¼¥¿¤ò¥Ð¥Ã¥¯¥¢¥Ã¥×¤·¤Æ¤¯¤À¤µ¤¤¡£
 	  ¤É¤Î¤è¤¦¤ÊÍýͳ¤ÇºÆ¤Ó»ö¸Î¤¬µ¯¤­¤¿¤ê¡¢¥Ç¡¼¥¿¤¬¼º¤ï¤ì¤ë¤«¤ï¤«¤ê¤Þ¤»¤ó¡£
 	  ¤³¤ì¤Ë¿ô»þ´Ö¤òÈñ¤¹¤³¤È¤Ç¡¢¸å¡¹¤ÎºÒÆñ¤«¤éµß¤ï¤ì¤Þ¤¹¡£</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="disks-virtual">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>ºÆ¹½À®¤ª¤è¤ÓÄɵ­: </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>¥Í¥Ã¥È¥ï¡¼¥¯¡¢¥á¥â¥ê¡¢¤½¤·¤Æ¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</title>
     <indexterm><primary>²¾Áۥǥ£¥¹¥¯</primary></indexterm>
     <indexterm>
       <primary>¥Ç¥£¥¹¥¯</primary>
       <secondary>²¾ÁÛ</secondary>
     </indexterm>
 
     <para>FreeBSD ¤Ë¤Ï¥Õ¥í¥Ã¥Ô¡¼¤ä CD,
       ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ê¤É¤Î¼ê¸µ¤Î·×»»µ¡¤Ë¼è¤êÉÕ¤±¤¿¥Ç¥£¥¹¥¯¤Î¾¤Ë¡¢
       Ê̤ηÁÂ֤Υǥ£¥¹¥¯¡¢<firstterm>²¾Áۥǥ£¥¹¥¯</firstterm>¡¢¤â¤¢¤ê¤Þ¤¹¡£</para>
 
     <indexterm><primary>NFS</primary></indexterm>
     <indexterm><primary>Coda</primary></indexterm>
     <indexterm>
       <primary>¥Ç¥£¥¹¥¯</primary>
       <secondary>¥á¥â¥ê</secondary>
     </indexterm>
 
     <para>¤³¤ì¤Ë¤Ï¡¢<link linkend="network-nfs">Network File System</link>
       ¤Î¤è¤¦¤Ê¥Í¥Ã¥È¥ï¡¼¥¯¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ä Coda,
       ¥á¥â¥ê¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ª¤è¤Ó¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
     <para>²ÔƯ¤µ¤»¤Æ¤¤¤ë FreeBSD ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ë¤è¤Ã¤Æ¡¢
       ¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¤ª¤è¤Ó¥á¥â¥ê¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤·¤¿¤êÁàºî¤¹¤ë¤¿¤á¤Ë¡¢°Û¤Ê¤ë¥Ä¡¼¥ë¤ò»ÈÍѤ·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤Ç¤·¤ç¤¦¡£</para>
 
     <note>
       <para>FreeBSD&nbsp;4.X ¤Î»ÈÍѼԤÏɬÍפʥǥХ¤¥¹¤òºîÀ®¤¹¤ë¤¿¤á¤Ë
 	&man.MAKEDEV.8; ¤ò»ÈÍѤ·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤Ç¤·¤ç¤¦¡£FreeBSD&nbsp;5.0
 	°Ê¹ß¤Ç¤Ï¡¢&man.devfs.5; ¤¬¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤ò¼«Æ°Åª¤Ë³ä¤êÅö¤Æ¤Æ¤¯¤ì¤ë¤Î¤Ç¡¢
 	»ÈÍѼԤ¬°Õ¼±¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£</para>
     </note>
 
     <sect2 id="disks-vnconfig">
       <title>FreeBSD&nbsp;4.X ¤Ç¥Õ¥¡¥¤¥ëÃæ¤Ë¹½ÃÛ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</title>
       <indexterm>
 	<primary>¥Ç¥£¥¹¥¯</primary>
 	<secondary>¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹ (4.X)</secondary>
       </indexterm>
 
       <para>&man.vnconfig.8;
 	¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ò»È¤¨¤Ðµ¼»÷¥Ç¥£¥¹¥¯¥Ç¥Ð¥¤¥¹¤òÀßÄꤷ¡¢
 	Í­¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	<firstterm>vnode</firstterm> ¤È¤Ï¥Õ¥¡¥¤¥ë¤ÎÆâÉôŪ¤Êɽ¸½ÊýË¡¤Ç¤¢¤ê¡¢
 	¥Õ¥¡¥¤¥ë¤Ë´Ø¤¹¤ëÁàºî¤ÎÃæ¿´¤È¤Ê¤ë¤â¤Î¤Ç¤¹¡£¤Ä¤Þ¤ê¡¢&man.vnconfig.8;
 	¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÀ¸À®¤·¤¿¤êÁàºî¤·¤¿¤ê¤¹¤ë¤¿¤á¤Ë¥Õ¥¡¥¤¥ë¤òÍѤ¤¤ë¤Î¤Ç¤¹¡£
 	°ì¤ÄÎã¤òµó¤²¤ë¤È¡¢
 	¥Õ¥¡¥¤¥ë¤Ë¼ý¤á¤é¤ì¤¿¥Õ¥í¥Ã¥Ô¡¼¤ä CD-ROM ¤Î¥¤¥á¡¼¥¸¤ò¥Þ¥¦¥ó¥È¤¹¤ë¤¿¤á¤ËÍѤ¤¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <para>&man.vnconfig.8; ¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢
 	¥«¡¼¥Í¥ë¤¬ &man.vn.4; ¥Ç¥Ð¥¤¥¹¤ËÂбþ¤·¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	¤½¤¦¤Ç¤Ê¤±¤ì¤Ð¡¢¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥®¥å¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë
 	¼¡¤Î¹Ô¤òÄɲ䷤ƥ«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¡¢¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
       <programlisting>pseudo-device vn</programlisting>
 
       <para>´û¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¤¥á¡¼¥¸¤Î¥Þ¥¦¥ó¥È</para>
 
       <example>
 	<title>FreeBSD&nbsp;4.X ¤Ç¤Î vnconfig ¤òÍѤ¤¤¿´û¸¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¤¥á¡¼¥¸¤Î¥Þ¥¦¥ó¥È</title>
 
 	<screen>&prompt.root; <userinput>vnconfig vn<replaceable>0</replaceable> <replaceable>diskimage</replaceable></userinput>
 &prompt.root; <userinput>mount /dev/vn<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput></screen>
       </example>
 
       <para>&man.vnconfig.8; ¤òÍѤ¤¤¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¤¥á¡¼¥¸¤Î¿·µ¬ºîÀ®</para>
 
       <example>
 	<title><command>vnconfig</command> ¤òÍѤ¤¤¿¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¥Ç¥£¥¹¥¯¤Î¿·µ¬ºîÀ®</title>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>newimage</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput>
 5120+0 records in
 5120+0 records out
 &prompt.root; <userinput>vnconfig -s labels -c vn<replaceable>0</replaceable> <replaceable>newimage</replaceable></userinput>
 &prompt.root; <userinput>disklabel -r -w vn<replaceable>0</replaceable> auto</userinput>
 &prompt.root; <userinput>newfs vn<replaceable>0</replaceable>c</userinput>
 Warning: 2048 sector(s) in last cylinder unallocated
 /dev/vn0c:     10240 sectors in 3 cylinders of 1 tracks, 4096 sectors
         5.0MB in 1 cyl groups (16 c/g, 32.00MB/g, 1280 i/g)
 super-block backups (for fsck -b #) at:
  32
 &prompt.root; <userinput>mount /dev/vn<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 /dev/vn0c        4927        1     4532     0%    /mnt</screen>
       </example>
     </sect2>
 
     <sect2 id="disks-mdconfig">
       <title>FreeBSD&nbsp;5.X ¤Ç¥Õ¥¡¥¤¥ëÃæ¤Ë¹½ÃÛ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</title>
       <indexterm>
 	<primary>¥Ç¥£¥¹¥¯</primary>
 	<secondary>¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹ (5.X)</secondary>
       </indexterm>
 
       <para>&man.mdconfig.8; ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ï FreeBSD&nbsp;5.X ¤Ë¤ª¤¤¤Æ
 	¥á¥â¥ê¥Ç¥£¥¹¥¯ (&man.md.4;) ¤òÀßÄꤷ¡¢Í­¸ú¤Ë¤¹¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£
 	&man.mdconfig.8; ¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï &man.md.4; ¥â¥¸¥å¡¼¥ë¤òÆɤ߹þ¤à¤«¡¢
 	¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥®¥å¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë &man.md.4;
 	¥Ç¥Ð¥¤¥¹¤òÄɲ䷤ƥ«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¡¢¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
       <programlisting>device md</programlisting>
 
       <para>&man.mdconfig.8; ¥³¥Þ¥ó¥É¤Ï¡¢
 	»°¤Ä¤Î¥¿¥¤¥×¤Î¥á¥â¥ê¥Ù¡¼¥¹²¾Áۥǥ£¥¹¥¯¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£
 	&man.malloc.9; ¤òÍѤ¤¤Æ³ä¤êÅö¤Æ¤é¤ì¤¿¥á¥â¥ê¥Ç¥£¥¹¥¯¡¢
 	¥Õ¥¡¥¤¥ë¤ò¥Ù¡¼¥¹¤Ë¤·¤¿¥á¥â¥ê¥Ç¥£¥¹¥¯¡¢
 	¤ª¤è¤Ó¥¹¥ï¥Ã¥×Îΰè¤ò¥Ù¡¼¥¹¤Ë¤·¤¿¥á¥â¥ê¥Ç¥£¥¹¥¯¤Ç¤¹¡£
 	ÁÛÄꤵ¤ì¤ë»ÈÍÑË¡¤Ï¡¢¥Õ¥¡¥¤¥ëÆâ¤ËÊÝ»ý¤µ¤ì¤¿¥Õ¥í¥Ã¥Ô¡¼¥¤¥á¡¼¥¸¤Þ¤¿¤Ï
 	CD ¥¤¥á¡¼¥¸¤ò¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤Ç¤¹¡£</para>
 
       <para>´û¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¤¥á¡¼¥¸¤Î¥Þ¥¦¥ó¥È</para>
 
       <example>
 	<title>FreeBSD&nbsp;5.X ¤Ç¤Î <command>mdconfig</command> ¤òÍѤ¤¤¿´û¸¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¤¥á¡¼¥¸¤Î¥Þ¥¦¥ó¥È</title>
 
 	<screen>&prompt.root; <userinput>mdconfig -a -t vnode -f <replaceable>diskimage</replaceable> -u <replaceable>0</replaceable></userinput>
 &prompt.root; <userinput>mount /dev/md<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput></screen>
       </example>
 
       <para>&man.mdconfig.8; ¤òÍѤ¤¤¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¤¥á¡¼¥¸¤Î¿·µ¬ºîÀ®</para>
 
       <example>
 	<title><command>mdconfig</command> ¤òÍѤ¤¤¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¤¥á¡¼¥¸¤Î¿·µ¬ºîÀ®</title>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>newimage</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput>
 5120+0 records in
 5120+0 records out
 &prompt.root; <userinput>mdconfig -a -t vnode -f <replaceable>newimage</replaceable> -u <replaceable>0</replaceable></userinput>
 &prompt.root; <userinput>disklabel -r -w md<replaceable>0</replaceable> auto</userinput>
 &prompt.root; <userinput>newfs md<replaceable>0</replaceable>c</userinput>
 /dev/md0c: 5.0MB (10240 sectors) block size 16384, fragment size 2048
 	using 4 cylinder groups of 1.27MB, 81 blks, 256 inodes.
 super-block backups (for fsck -b #) at:
  32, 2624, 5216, 7808
 &prompt.root; <userinput>mount /dev/md<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 /dev/md0c        4846        2     4458     0%    /mnt</screen>
       </example>
 
       <para><option>-u</option> ¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤Æ
 	¥æ¥Ë¥Ã¥ÈÈÖ¹æ¤ò»ØÄꤷ¤Ê¤¤¾ì¹ç¡¢&man.mdconfig.8;
 	¤Ï̤»ÈÍѤΥǥХ¤¥¹¤ò¼«Æ°Åª¤ËÁªÂò¤¹¤ë¤¿¤á¤Ë
 	&man.md.4; ¥Ç¥Ð¥¤¥¹¤Î auto-unit µ¡Ç½¤ò»ÈÍѤ·¤Þ¤¹¡£
 	³ä¤êÅö¤Æ¤é¤ì¤¿¥æ¥Ë¥Ã¥È¤Î̾Á°¤Ï <devicename>md4</devicename>
 	¤Î¤è¤¦¤Ëɸ½à½ÐÎϤ˽ÐÎϤµ¤ì¤Þ¤¹¡£&man.mdconfig.8;
 	¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
       <note><para>&os;&nbsp;5.1-RELEASE ¤«¤é¡¢½¾Íè¤Î &man.disklabel.8;
 	  ¥×¥í¥°¥é¥à¤Ï &man.bsdlabel.8;
 	  ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ËÃÖ¤­´¹¤¨¤é¤ì¤Þ¤·¤¿¡£&man.bsdlabel.8; ¤Ç¤Ï¡¢
 	  »ÈÍѤµ¤ì¤Æ¤¤¤Ê¤¤¥ª¥×¥·¥ç¥ó¤ª¤è¤Ó¥Ñ¥é¥á¥¿¤Î¿ô¿¤¯¤¬ºï½ü¤µ¤ì¤Þ¤·¤¿¡£
 	  ¤¿¤È¤¨¤Ð <option>-r</option> ¥ª¥×¥·¥ç¥ó¤Ï &man.bsdlabel.8;
 	  ¤Ç¤Ï¼è¤ê½ü¤«¤ì¤Þ¤·¤¿¡£¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï &man.bsdlabel.8;
 	  ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para></note>
 
       <para>&man.mdconfig.8; ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ÏÂçÊÑÌò¤ËΩ¤Á¤Þ¤¹¤¬¡¢
 	¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤¿¤á¤Ë¡¢
 	¿¤¯¤Î¥³¥Þ¥ó¥É¤ÎÆþÎϤ¬É¬ÍפȤʤê¤Þ¤¹¡£FreeBSD&nbsp;5.0 ¤Ç¤Ï
 	&man.mdmfs.8; ¤È¸Æ¤Ð¤ì¤ë¥Ä¡¼¥ë¤âÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥×¥í¥°¥é¥à¤Ï
 	&man.mdconfig.8; ¤òÍѤ¤¤Æ &man.md.4; ¥Ç¥£¥¹¥¯¤òÀßÄꤷ¡¢&man.newfs.8;
 	¤òÍѤ¤¤Æ UFS ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤·¡¢&man.mount.8;
 	¤òÍѤ¤¤Æ¥Þ¥¦¥ó¥È¤·¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢¾åµ­¤ÈƱ¤¸¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤·¡¢
 	¥Þ¥¦¥ó¥È¤·¤¿¤¤¾ì¹ç¤Ï¡¢²¼µ­¤Î¤è¤¦¤ËÆþÎϤ¹¤ë¤À¤±¤Ç¤¹¡£</para>
 
       <example>
 	<title><command>mdmfs</command> ¤òÍѤ¤¤¿¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¥Ç¥£¥¹¥¯¤ÎÀßÄê¤È¥Þ¥¦¥ó¥È</title>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>newimage</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput>
 5120+0 records in
 5120+0 records out
 &prompt.root; <userinput>mdmfs -F <replaceable>newimage</replaceable> -s <replaceable>5</replaceable>m md<replaceable>0</replaceable> <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md0        4846    2  4458     0%    /mnt</screen>
       </example>
 
       <para>¥æ¥Ë¥Ã¥ÈÈÖ¹æ¤ò»ØÄꤻ¤º¤Ë <option>md</option>
 	¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤ·¤¿¾ì¹ç¡¢&man.mdmfs.8;
 	¤Ï̤»ÈÍѤΥǥХ¤¥¹¤ò¼«Æ°Åª¤ËÁªÂò¤¹¤ë¤¿¤á¤Ë &man.md.4; ¥Ç¥Ð¥¤¥¹¤Î
 	auto-unit µ¡Ç½¤ò»ÈÍѤ·¤Þ¤¹¡£&man.mdmfs.8;
 	¤Ë¤Ä¤¤¤Æ¤Î¾ÜºÙ¤Ï¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
     </sect2>
 
     <sect2 id="disks-md-freebsd4">
       <title>FreeBSD&nbsp;4.X ¤Ç¤Î¥á¥â¥ê¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</title>
       <indexterm>
 	<primary>¥Ç¥£¥¹¥¯</primary>
 	<secondary>¥á¥â¥ê¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à (4.X)</secondary>
       </indexterm>
 
       <para>&man.md.4; ¥É¥é¥¤¥Ð¤Ï FreeBSD&nbsp;4.X
 	¤Ë¤ª¤¤¤Æ¥á¥â¥ê¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤¿¤á¤Ëñ½ã¤Ç¸ú²ÌŪ¤Ê¼êÃʤǤ¹¡£
 	¥á¥â¥ê¤ò³ä¤êÅö¤Æ¤ë¤¿¤á¤Ë &man.malloc.9; ´Ø¿ô¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£</para>
 
       <para>&man.vnconfig.8; ¤òÍѤ¤¤ÆºîÀ®¤·¤¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÎã¤Ë¼è¤ë¤È¡¢
 	°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <example>
 	<title>FreeBSD&nbsp;4.X ¤Ç¤Î md ¥á¥â¥ê¥Ç¥£¥¹¥¯</title>
 
 	<screen>&prompt.root; <userinput>dd if=<replaceable>newimage</replaceable> of=/dev/md<replaceable>0</replaceable></userinput>
 5120+0 records in
 5120+0 records out
 &prompt.root; <userinput>mount /dev/md<replaceable>0c</replaceable> <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 /dev/md0c        4927        1     4532     0%    /mnt</screen>
       </example>
 
       <para>¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï &man.md.4; ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
     </sect2>
 
     <sect2 id="disks-md-freebsd5">
       <title>FreeBSD&nbsp;5.X ¤Ç¤Î¥á¥â¥ê¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</title>
       <indexterm>
 	<primary>¥Ç¥£¥¹¥¯</primary>
 	<secondary>¥á¥â¥ê¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à (5.X)</secondary>
       </indexterm>
 
       <para>¥á¥â¥ê¥Ù¡¼¥¹¤ª¤è¤Ó¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ·¤Æ¤â
 	Ʊ¤¸¥Ä¡¼¥ë (&man.mdconfig.8; ¤Þ¤¿¤Ï &man.mdmfs.8;) ¤ò»ÈÍѤǤ­¤Þ¤¹¡£
 	¥á¥â¥ê¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ¹¤ëµ­²±Îΰè¤Ï
 	&man.malloc.9; ´Ø¿ô¤òÍѤ¤¤Æ³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£</para>
 
       <example>
 	<title><command>mdconfig</command> ¤òÍѤ¤¤¿¥á¥â¥ê¥Ù¡¼¥¹¥Ç¥£¥¹¥¯¤Î¿·µ¬ºîÀ®</title>
 
 	<screen>&prompt.root; <userinput>mdconfig -a -t malloc -s <replaceable>5</replaceable>m -u <replaceable>1</replaceable></userinput>
 &prompt.root; <userinput>newfs -U md<replaceable>1</replaceable></userinput>
 /dev/md1: 5.0MB (10240 sectors) block size 16384, fragment size 2048
 	using 4 cylinder groups of 1.27MB, 81 blks, 256 inodes.
 	with soft updates
 super-block backups (for fsck -b #) at:
  32, 2624, 5216, 7808
 &prompt.root; <userinput>mount /dev/md<replaceable>1</replaceable> <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md1        4846    2  4458     0%    /mnt</screen>
       </example>
 
       <example>
 	<title><command>mdmfs</command> ¤òÍѤ¤¤¿¥á¥â¥ê¥Ù¡¼¥¹¥Ç¥£¥¹¥¯¤Î¿·µ¬ºîÀ®</title>
 	<screen>&prompt.root; <userinput>mdmfs -M -s <replaceable>5</replaceable>m md<replaceable>2</replaceable> <replaceable>/mnt</replaceable></userinput>
 &prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput>
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md2        4846    2  4458     0%    /mnt</screen>
       </example>
 
       <para>&man.mdconfig.8; ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Î <option>malloc</option> ¤ò
 	<option>swap</option> ¤ËÃÖ¤­´¹¤¨¤ë¤³¤È¤Ç¡¢&man.malloc.9;
 	´Ø¿ô¤Ë¤è¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò»ÈÍѤ¹¤ëÂå¤ï¤ê¤Ë
 	¥¹¥ï¥Ã¥×Îΰè¤ò»ÈÍѤ¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï &man.mdmfs.8;
 	¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ï¥¹¥ï¥Ã¥×¥Ù¡¼¥¹¤Î¥Ç¥£¥¹¥¯¤òºîÀ®¤·¤Þ¤¹
 	(<option>-M</option> ¤Ê¤·)¡£¾ÜºÙ¤Ï &man.mdconfig.8; ¤ª¤è¤Ó
 	&man.mdmfs.8; ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
     </sect2>
 
     <sect2>
       <title>¥·¥¹¥Æ¥à¤«¤é¥á¥â¥ê¥Ç¥£¥¹¥¯¤òÀÚ¤êÎ¥¤¹</title>
       <indexterm>
 	<primary>¥Ç¥£¥¹¥¯</primary>
 	<secondary>¥á¥â¥ê¥Ç¥£¥¹¥¯¤ÎÀÚ¤êÎ¥¤·</secondary>
       </indexterm>
 
       <para>¥á¥â¥ê¥Ù¡¼¥¹¤Þ¤¿¤Ï¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬»ÈÍѤµ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
 	¤¹¤Ù¤Æ¤Î¥ê¥½¡¼¥¹¤ò¥·¥¹¥Æ¥à¤Ë³«Êü¤¹¤ë¤Ù¤­¤Ç¤¹¡£
 	¤Ï¤¸¤á¤Ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥¢¥ó¥Þ¥¦¥ó¥È¤·¤Þ¤¹¡£
 	¼¡¤Ë¥·¥¹¥Æ¥à¤«¤é¥Ç¥£¥¹¥¯¤òÀÚ¤êÎ¥¤·¡¢¥ê¥½¡¼¥¹¤ò³«Êü¤¹¤ë¤¿¤á¤Ë
 	&man.mdconfig.8; ¤ò»ÈÍѤ·¤Þ¤¹¡£</para>
 
       <para>¤¿¤È¤¨¤Ð <filename>/dev/md4</filename> ¤Ë¤è¤Ã¤Æ»ÈÍѤµ¤ì¤¿¤¹¤Ù¤Æ¤Î¥ê¥½¡¼¥¹¤òÀÚ¤êÎ¥¤·¡¢³«Êü¤¹¤ë¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>mdconfig -d -u <replaceable>4</replaceable></userinput></screen>
 
       <para><command>mdconfig -l</command> ¥³¥Þ¥ó¥É¤ò»ÈÍѤ¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢
 	ÀßÄꤵ¤ì¤¿ &man.md.4; ¥Ç¥Ð¥¤¥¹¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤òɽ¼¨¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¹¡£</para>
 
       <para>FreeBSD&nbsp;4.X ¤Ç¤Ï &man.vnconfig.8; ¤Ï¥Ç¥Ð¥¤¥¹¤òÀÚ¤êÎ¥¤¹¤Î¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£¤¿¤È¤¨¤Ð <filename>/dev/vn4</filename> ¤Ë¤è¤Ã¤Æ»ÈÍѤµ¤ì¤¿¤¹¤Ù¤Æ¤Î¥ê¥½¡¼¥¹¤òÀÚ¤êÎ¥¤·¡¢³«Êü¤¹¤ë¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>vnconfig -u vn<replaceable>4</replaceable></userinput></screen>
     </sect2>
   </sect1>
 
   <sect1 id="snapshots">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>´ó¹Æ: </contrib>
 	</author>
       </authorgroup>
       <!-- 15 JUL 2002 -->
     </sect1info>
 
     <title>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È</title>
 
     <indexterm>
       <primary>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à</primary>
       <secondary>¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È</secondary>
     </indexterm>
 
     <para>FreeBSD&nbsp;5.0 ¤Ï
       Soft Updates
       <!-- Furukawa:2004/1/8
       should be refer this after updating config/chapter.xml
       <link linkend="soft-updates">Soft Updates</link>
       -->
       ¤È¶¨Ä´¤¹¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤È¤¤¤¦¿·¤·¤¤µ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£</para>
 
     <para>¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ï»ØÄꤷ¤¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¤¥á¡¼¥¸¤òºîÀ®¤·¡¢
       ¤Þ¤¿¡¢¥Õ¥¡¥¤¥ë¤È¤·¤Æ°·¤¦¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
       ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¥Õ¥¡¥¤¥ë¤Ï¥¢¥¯¥·¥ç¥ó¤¬¼Â¹Ô¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àÆâ¤ÇºîÀ®¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
       ¤Þ¤¿¡¢¥æ¡¼¥¶¤Ï°ì¤Ä¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¢¤¿¤ê 20
       ¤Þ¤Ç¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤òºîÀ®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
       Í­¸ú¤Ê¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ï¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯Æâ¤Ëµ­Ï¿¤µ¤ì¤ë¤Î¤Ç¡¢
       ¥ê¥Ö¡¼¥È¤·¤Æ¤«¤é±Ê³Ū¤Ë¥¢¥ó¥Þ¥¦¥ó¥È¤ª¤è¤Ó¥ê¥Þ¥¦¥ó¥È¤òµ­Ï¿¤·¤Þ¤¹¡£
       ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤¬É¬Í×̵¤¯¤Ê¤Ã¤¿¤È¤­¤Ï¡¢
       ɸ½à¤Î &man.rm.1; ¥³¥Þ¥ó¥É¤òÍѤ¤¤Æºï½ü¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
       ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ï¤É¤ó¤Ê½çÈ֤Ǻï½ü¤·¤Æ¤â¤è¤¤¤Î¤Ç¤¹¤¬¡¢
       ¤½¤Î¾¤Î¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤¬³«Êü¤µ¤ì¤¿¥Ö¥í¥Ã¥¯¤Î¤¦¤Á¤¤¤¯¤é¤«¤ò¤ª¤½¤é¤¯É¬ÍפȤ¹¤ë¤Î¤Ç¡¢
       »ÈÍѤµ¤ì¤Æ¤¤¤¿¤¹¤Ù¤Æ¤Î¥¹¥Ú¡¼¥¹¤òÆÀ¤é¤ì¤ë¤È¤Ï¸Â¤ê¤Þ¤»¤ó¡£</para>
 
     <para>½é¤á¤Æ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤òºîÀ®¤¹¤ë¤È¡¢<username>root</username>
       ¤Ç¤µ¤¨¤â½ñ¤­¹þ¤á¤Ê¤¤¤è¤¦¤Ë <option>schg</option>
       ¥Õ¥é¥° (&man.chflags.1; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¾È) ¤¬ÀßÄꤵ¤ì¤Þ¤¹¡£
       &man.unlink.1; ¥³¥Þ¥ó¥É¤Ï¡¢¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ë <option>schg</option>
       ¥Õ¥é¥°¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Æ¤â¤½¤ì¤é¤òºï½ü¤¹¤ë¤³¤È¤Î¤Ç¤­¤ëÎã³°¤Ç¤¹¡£
       ¤·¤¿¤¬¤Ã¤Æ¡¢¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¥Õ¥¡¥¤¥ë¤òºï½ü¤¹¤ëÁ°¤Ë¡¢
       <option>schg</option> ¥Õ¥é¥°¤ò¥¯¥ê¥¢¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£</para>
 
     <para>¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ï &man.mount.8; ¥³¥Þ¥ó¥É¤òÍѤ¤¤ÆºîÀ®¤µ¤ì¤Þ¤¹¡£
       <filename>/var</filename> ¤Î¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò
       <filename>/var/snapshot/snap</filename> ¤ËºîÀ®¤·¤¿¤¤¤È¤­¤Ï¡¢
       °Ê²¼¤Î¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Þ¤¹¡£</para>
 
     <screen>&prompt.root; <userinput>mount -u -o snapshot /var/snapshot/snap /var</userinput></screen>
 
     <para>¤Þ¤¿¡¢¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤òºîÀ®¤¹¤ë¤Î¤Ë &man.mksnap.ffs.8;
       ¤â»È¤¨¤Þ¤¹¡£</para>
     <screen>&prompt.root; <userinput>mksnap_ffs /var /var/snapshot/snap</userinput></screen>
 
     <para>¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ë¤Ï¤¤¤¯¤Ä¤«¤ÎÍøÍÑË¡¤¬¤¢¤ê¤Þ¤¹¡£</para>
 
     <itemizedlist>
       <listitem>
 	<para>¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò¥Ð¥Ã¥¯¥¢¥Ã¥×ÌÜŪ¤Ë»ÈÍѤ¹¤ë´ÉÍý¼Ô¤â¤¤¤Þ¤¹¡£
 	  ¤Ê¤¼¤Ê¤é¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ï CD ¤ä¥Æ¡¼¥×¤ËžÁ÷¤Ç¤­¤ë¤«¤é¤Ç¤¹¡£</para>
       </listitem>
 
       <listitem>
 	<para>¥Õ¥¡¥¤¥ë¤Î´°Á´À­¤ò¸¡¾Ú¤¹¤ë¤¿¤á¤Ë¡¢
 	  &man.fsck.8; ¤ò¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ë¼Â¹Ô¤·¤Æ¤â¤è¤¤¤Ç¤·¤ç¤¦¡£
 	  ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò¥Þ¥¦¥ó¥È¤·¤¿¤È¤­¤Ë¤½¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥¯¥ê¡¼¥ó¤Ç¤¢¤Ã¤¿¤È¤¹¤ë¤È¡¢
 	  ¤½¤Î¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò¥Þ¥¦¥ó¥È¤¹¤ë¤È¤­¤Ï¤¤¤Ä¤Ç¤â¥¯¥ê¡¼¥ó¤Ê
 	  (¤½¤·¤ÆÊѹ¹¤Î¤Ê¤¤) ·ë²Ì¤òÆÀ¤ë¤Ç¤·¤ç¤¦¡£
 	  ¤³¤ì¤ÏËܼÁŪ¤Ë¤Ï ¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É &man.fsck.8; ¤¬¹Ô¤¦¤³¤È¤Ç¤¹¡£</para>
       </listitem>
 
       <listitem>
 	<para>¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¾å¤Ç &man.dump.8; ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ò¼Â¹Ô¤¹¤ë¤È¡¢
 	  ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤È¥¿¥¤¥à¥¹¥¿¥ó¥×¤¬°ìÃפ¹¤ë¥À¥ó¥×¤¬ÊÖ¤µ¤ì¤ë¤Ç¤·¤ç¤¦¡£
 	  &man.dump.8; ¤Ï <option>-L</option> ¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢
 	  °ì¤Ä¤Î¥³¥Þ¥ó¥É¤Ç¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò¤È¤ê¡¢¥À¥ó¥×¥¤¥á¡¼¥¸¤òºîÀ®¤·¤Æ¡¢¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤òºï½ü¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¹¡£</para>
       </listitem>
 
       <listitem>
 	<para>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î <quote>Åà·ë¤µ¤ì¤¿</quote> ¥¤¥á¡¼¥¸¤È¤·¤Æ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò
 	  &man.mount.8; ¤·¤Þ¤¹¡£
 	  <filename>/var/snapshot/snap</filename> ¤Î¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤ò
 	  &man.mount.8; ¤¹¤ë¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
 	<screen>&prompt.root; <userinput>mdconfig -a -t vnode -f /var/snapshot/snap -u 4</userinput>
 &prompt.root; <userinput>mount -r /dev/md4 /mnt</userinput></screen>
 
       </listitem>
     </itemizedlist>
 
     <para>¤³¤ì¤Ç <filename>/mnt</filename> ¤Ë¥Þ¥¦¥ó¥È¤·¤¿
       Åà·ë¾õÂ֤Π<filename>/var</filename> ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¹½Â¤¤òõº÷¤Ç¤­¤Þ¤¹¡£
       ¤¹¤Ù¤Æ¤¬¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤¬ºîÀ®¤µ¤ì¤¿»þ¤ÈƱ¤¸¾õÂ֤ˤʤë¤Ï¤º¤Ç¤¹¡£¤¿¤À¤·¡¢
       °ÊÁ°¤ËºîÀ®¤µ¤ì¤¿¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤¬¥µ¥¤¥º 0 ¤Î¥Õ¥¡¥¤¥ë¤È¤·¤Æ¸½¤ì¤ë¤³¤È¤¬Í£°ì¤ÎÎã³°¤Ç¤¹¡£
       ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Î»ÈÍѤò½ª¤¨¤¿¾ì¹ç¡¢°Ê²¼¤Î¤è¤¦¤Ë¥¢¥ó¥Þ¥¦¥ó¥È¤Ç¤­¤Þ¤¹¡£</para>
 
     <screen>&prompt.root; <userinput>umount /mnt</userinput>
 &prompt.root; <userinput>mdconfig -d -u 4</userinput></screen>
 
     <para><option>softupdates</option>
       ¤ª¤è¤Ó¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¤Ë´Ø¤¹¤ë¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
       <ulink url="http://www.mckusick.com/">http://www.mckusick.com/</ulink>
       ¤Ë¤¢¤ë Marshall Kirk McKusick ¤Î¥¦¥§¥Ö¥µ¥¤¥È¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
       ¤³¤³¤Ë¤Ïµ»½ÑŪ¤ÊÏÀʸ¤â¤¢¤ê¤Þ¤¹¡£</para>
   </sect1>
 
   <sect1 id="quotas">
     <title>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¯¥©¡¼¥¿</title>
     <indexterm>
       <primary>¥¢¥«¥¦¥ó¥Æ¥£¥ó¥°</primary>
       <secondary>¥Ç¥£¥¹¥¯Îΰè</secondary>
     </indexterm>
     <indexterm><primary>¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿</primary></indexterm>
 
     <para>¥¯¥©¡¼¥¿¤Ï OS ¤Î»ý¤Ã¤Æ¤¤¤ë¥ª¥×¥·¥ç¥Ê¥ë¤Êµ¡Ç½¤Ç¤¢¤ê¡¢
       ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àËè¤Ë¥æ¡¼¥¶¤ä¥°¥ë¡¼¥×¤Î¥á¥ó¥Ð¤¬»ÈÍѤ¹¤ë¥Ç¥£¥¹¥¯ÍÆÎ̤ä¥Õ¥¡¥¤¥ë¤Î¿ô¤òÀ©¸Â¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
       ¤³¤Îµ¡Ç½¤Ï¡¢¤¢¤ë¥æ¡¼¥¶¤ä¥°¥ë¡¼¥×¤Ë³ä¤êÅö¤Æ¤é¤ì¤ë¥ê¥½¡¼¥¹¤ÎÎ̤òÀ©¸Â¤¹¤ë¤³¤È¤¬Ë¾¤Þ¤·¤¤¤è¤¦¤Ê¥¿¥¤¥à¥·¥§¥¢¥ê¥ó¥°¥·¥¹¥Æ¥à¤Ë¤ª¤¤¤Æ¤è¤¯ÍѤ¤¤é¤ì¤Þ¤¹¡£
       ¤³¤Îµ¡Ç½¤òÍѤ¤¤ë¤³¤È¤Ë¤è¤Ã¤Æ»ÈÍѲÄǽ¤Ê¥Ç¥£¥¹¥¯ÍÆÎ̤ÎÁ´¤Æ¤ò°ì¿Í¤Î¥æ¡¼¥¶¤ä¥æ¡¼¥¶¤Î¥°¥ë¡¼¥×¤¬»È¤Ã¤Æ¤·¤Þ¤¦¤³¤È¤òËɤ°¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
     <sect2>
       <title>¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿¤ò»È¤¦¤¿¤á¤Î¥·¥¹¥Æ¥àÀßÄê</title>
 
       <para>¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿¤ÎÀßÄê¤ò»Ï¤á¤ëÁ°¤Ë¡¢
 	¤Þ¤º¤Ï¥«¡¼¥Í¥ë¤Ë¥¯¥©¡¼¥¿¤¬ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Þ¤·¤ç¤¦¡£
 	¥«¡¼¥Í¥ë¤Î¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë¼¡¤Î¹Ô¤òÆþ¤ì¤Þ¤¹¡£</para>
 
       <programlisting>options QUOTA</programlisting>
 
       <para>ɸ½à¤Î <filename>GENERIC</filename> ¥«¡¼¥Í¥ë¤Ç¤Ï¡¢
 	¤³¤Îµ¡Ç½¤ÏÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤»¤ó¤Î¤Ç¡¢
 	¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿¤òÍøÍѤ¹¤ë¤¿¤á¤Ë¤Ï¾åµ­¤òÀßÄê¸å¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤·¤Ê¤ª¤·¡¢
 	ºîÀ®¤µ¤ì¤¿¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£
 	¥«¡¼¥Í¥ë¤Î¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¤Ë´Ø¤·¤Æ¤Ï
 	<xref linkend="kernelconfig"/> ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
 
       <para>¼¡¤Ë <filename>/etc/rc.conf</filename>
 	¤Ç¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿¤òÍ­¸ú¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	¼¡¤Î¹Ô¤ò²Ã¤¨¤Þ¤·¤ç¤¦¡£</para>
 
       <programlisting>enable_quotas="YES"</programlisting>
       <indexterm>
 	<primary>¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿</primary>
 	<secondary>¥Á¥§¥Ã¥¯</secondary>
       </indexterm>
 
       <para>µ¯Æ°»þ¤ÎÆ°ºî¤ò¤µ¤é¤ËºÙ¤«¤¯¥³¥ó¥È¥í¡¼¥ë¤¹¤ë¤¿¤á¤Ë¤â¤¦°ì¤ÄÀßÄêÍѤÎÊÑ¿ô¤¬¤¢¤ê¤Þ¤¹¡£
 	Ä̾µ¯Æ°»þ¤Ë¤Ï &man.quotacheck.8;
 	¤Ë¤è¤ê¤½¤ì¤¾¤ì¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¯¥©¡¼¥¿¤ÎÀ°¹çÀ­¤¬¥Á¥§¥Ã¥¯¤µ¤ì¤Þ¤¹¡£
 	&man.quotacheck.8; ¤ÎÌò³ä¤Ï¡¢
 	¥¯¥©¡¼¥¿¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Ç¡¼¥¿¤¬Àµ¤·¤¯¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î¥Ç¡¼¥¿¤òÈ¿±Ç¤·¤Æ¤¤¤ë¤«³Îǧ¤¹¤ë¤³¤È¤Ç¤¹¡£
 	¤³¤ì¤Ï¤«¤Ê¤ê»þ´Ö¤ò¿©¤¦½èÍý¤Ç¤¢¤ê¡¢
 	µ¯Æ°¤Ë¤«¤«¤ë»þ´Ö¤ËÂ礭¤Ê±Æ¶Á¤òµÚ¤Ü¤·¤Þ¤¹¡£
 	¤³¤Î¥¹¥Æ¥Ã¥×¤ò¤È¤Ð¤·¤¿¤¤¿Í¤Î¤¿¤á¤Ë
 	<filename>/etc/rc.conf</filename> ¤Ë¼¡¤ÎÊÑ¿ô¤¬ÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
       <programlisting>check_quotas="NO"</programlisting>
 
       <para>¤â¤· 3.2-RELEASE ¤è¤ê¤âÁ°¤Î FreeBSD
 	¤ò»È¤Ã¤Æ¤¤¤ë¤Ê¤é¤ÐÀßÄê¤Ï¤â¤Ã¤Èñ½ã¤Ç¡¢°ì¤Ä¤ÎÊÑ¿ô¤Î¤ß¤Ç¤¹¡£
 	¼¡¤Î¹Ô¤ò <filename>/etc/rc.conf</filename> ¤ÇÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£</para>
 
       <programlisting>check_quotas="YES"</programlisting>
 
       <para>ºÇ¸å¤Ë¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àËè¤Ë¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿¤òÍ­¸ú¤Ë¤¹¤ë¤¿¤á¤Ë
 	<filename>/etc/fstab</filename> ¤òÊÔ½¸¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	¤³¤³¤Ç¥æ¡¼¥¶¤â¤·¤¯¤Ï¥°¥ë¡¼¥×¡¢
 	¤¢¤ë¤¤¤Ï¤½¤ÎξÊý¤Ë¥¯¥©¡¼¥¿¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤ë¤Î¤Ç¤¹¡£</para>
 
       <para>¤¢¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ë¥æ¡¼¥¶Ëè¤Î¥¯¥©¡¼¥¿¤òÍ­¸ú¤Ë¤¹¤ë¾ì¹ç¤Ë¤Ï¡¢
 	<filename>/etc/fstab</filename>
 	Ãæ¤Ç¥¯¥©¡¼¥¿¤òÍ­¸ú¤Ë¤·¤¿¤¤¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥¨¥ó¥È¥ê¤Î¥ª¥×¥·¥ç¥óÉô¤Ë
 	<option>userquota</option> ¤ò²Ã¤¨¤Þ¤¹¡£
 	Î㤨¤Ð¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
 
       <programlisting>/dev/da1s2g   /home    ufs rw,userquota 1 2</programlisting>
 
       <para>ƱÍͤˡ¢¥°¥ë¡¼¥×¥¯¥©¡¼¥¿¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï
 	<option>userquota</option> ¥­¡¼¥ï¡¼¥É¤ÎÂå¤ï¤ê¤Ë
 	<option>groupquota</option> ¤òÍѤ¤¤Þ¤¹¡£
 	¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤ÎξÊý¤Î¥¯¥©¡¼¥¿¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£</para>
 
       <programlisting>/dev/da1s2g    /home    ufs rw,userquota,groupquota 1 2</programlisting>
 
       <para>¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢
 	¥¯¥©¡¼¥¿¥Õ¥¡¥¤¥ë¤Ï¤½¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê¤Ë
 	¥æ¡¼¥¶ÍÑ¡¢¥°¥ë¡¼¥×ÍѤ½¤ì¤¾¤ì
 	<filename>quota.user</filename>, <filename>quota.group</filename>
 	¤È¤¤¤¦Ì¾Á°¤ÇÃÖ¤«¤ì¤Þ¤¹¡£¤µ¤é¤Ë¾Ü¤·¤¤¾ðÊó¤Ï &man.fstab.5;
 	¤ò¤´Í÷¤¯¤À¤µ¤¤¡£&man.fstab.5;
 	¥Þ¥Ë¥å¥¢¥ë¤Ë¤ÏÊ̤ξì½ê¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤ë¤È½ñ¤¤¤Æ¤Ï¤¢¤ê¤Þ¤¹¤¬¡¢
 	¤¢¤Þ¤ê´«¤á¤é¤ì¤Þ¤»¤ó¡£¤Ê¤¼¤Ê¤é¡¢
 	ÍÍ¡¹¤Ê¥¯¥©¡¼¥¿´Ø·¸¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤¬¤½¤ì¤Ë¤¦¤Þ¤¯Âнè¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤¤¤¿¤á¤Ç¤¹¡£</para>
 
       <para>¤³¤Î»þÅÀ¤Ç¡¢
 	°ìÅÙ¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¤Æ¿·¤·¤¤¥«¡¼¥Í¥ë¤ÇΩ¤Á¾å¤²¤Þ¤·¤ç¤¦¡£
 	<filename>/etc/rc</filename> ¤¬¼«Æ°Åª¤ËŬÅö¤Ê¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¡¢
 	<filename>/etc/fstab</filename>
 	¤ÇÍ­¸ú¤Ë¤·¤¿Á´¤Æ¤Î¥¯¥©¡¼¥¿ÍѤ˽é´ü¥Õ¥¡¥¤¥ë¤òºî¤Ã¤Æ¤¯¤ì¤Þ¤¹¡£
 	½¾¤Ã¤Æ¡¢¶õ¤Î¥¯¥©¡¼¥¿¥Õ¥¡¥¤¥ë¤ò¼ê¤Çºî¤ëɬÍפϰìÀÚ¤¢¤ê¤Þ¤»¤ó¡£</para>
 
       <para>Ä̾ï¤Î±¿ÍÑ¤Ç¤Ï &man.quotacheck.8; ¤ä
 	&man.quotaon.8;, &man.quotaoff.8;
 	¤È¤¤¤Ã¤¿¥³¥Þ¥ó¥É¤ò¼ê¤ÇÆ°¤«¤¹É¬ÍפϤʤ¤¤Î¤Ç¤¹¤¬¡¢
 	´·¤ì¤ë¤¿¤á¤Ë¤â¤³¤ì¤é¤Î¥Þ¥Ë¥å¥¢¥ë¤ÏÆɤó¤Ç¤ª¤­¤Þ¤·¤ç¤¦¡£</para>
     </sect2>
 
     <sect2>
       <title>¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤ÎÀßÄê</title>
       <indexterm>
 	<primary>¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿</primary>
 	<secondary>À©¸Â</secondary>
       </indexterm>
 
       <para>°ìö¥¯¥©¡¼¥¿¤òÍ­¸ú¤Ë¤·¤¿¤éËÜÅö¤ËÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤Î¤«³Îǧ¤·¤Æ¤ª¤­¤Þ¤·¤ç¤¦¡£´Êñ¤ÊÊýË¡¤Ï¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë¤³¤È¤Ç¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>quota -v</userinput></screen>
 
       <para>¥Ç¥£¥¹¥¯¤Î»ÈÍѾõ¶·¤È¡¢¥¯¥©¡¼¥¿¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤¬°ì¹Ô¤Ë¤Þ¤È¤á¤Æ½ÐÎϤµ¤ì¤ë¤Ç¤·¤ç¤¦¡£</para>
 
       <para>¤µ¤¢¡¢&man.edquota.8; ¤Ç¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤òÀßÄꤹ¤ë½àÈ÷¤¬¤Ç¤­¤Þ¤·¤¿¡£</para>
 
       <para>¥æ¡¼¥¶¤ä¥°¥ë¡¼¥×¤¬»ÈÍѤǤ­¤ë¥Ç¥£¥¹¥¯ÍÆÎ̤äºîÀ®¤Ç¤­¤ë¥Õ¥¡¥¤¥ë¤Î¿ô¤ËÀ©¸Â¤ò¤«¤±¤ë¤Ë¤Ï¤¤¤¯¤Ä¤«¤Î¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£³ä¤êÅö¤Æ¥Ç¥£¥¹¥¯ÍÆÎ̤òÀ©¸Â
 	(¥Ö¥í¥Ã¥¯¥¯¥©¡¼¥¿) ¤¹¤ë¤³¤È¤â¥Õ¥¡¥¤¥ë¿ô¤òÀ©¸Â (inode ¥¯¥©¡¼¥¿)
 	¤¹¤ë¤³¤È¤â¡¢Î¾¼Ô¤òÁȤ߹ç¤ï¤»¤ë¤³¤È¤â¤Ç¤­¤ë¤Î¤Ç¤¹¡£
 	¤³¤ì¤é¤ÎÀ©¸Â¤Ï¤½¤ì¤¾¤ì¤µ¤é¤ËÆó¤Ä¤Î¥«¥Æ¥´¥ê¡¢
 	¥Ï¡¼¥É¥ê¥ß¥Ã¥È¤È¥½¥Õ¥È¥ê¥ß¥Ã¥È¡¢¤Ëʬ¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <indexterm><primary>¥Ï¡¼¥É¥ê¥ß¥Ã¥È</primary></indexterm>
       <para>¥Ï¡¼¥É¥ê¥ß¥Ã¥È¤ò±Û¤¨¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
 	¤¢¤ë¥æ¡¼¥¶¤¬°ìö¥Ï¡¼¥É¥ê¥ß¥Ã¥È¤Ë¤¿¤Ã¤·¤¿¾ì¹ç¡¢
 	¤½¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤Ï¤½¤ì°Ê¾å¤Î³ä¤êÅö¤Æ¤Ï˾¤á¤Þ¤»¤ó¡£
 	Î㤨¤Ð¤¢¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ë
 	500 ¥Ö¥í¥Ã¥¯¤Î¥Ï¡¼¥É¥ê¥ß¥Ã¥È¤¬ÀßÄꤵ¤ì¤Æ¤ª¤ê¸½ºß
 	490 ¥Ö¥í¥Ã¥¯¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢¤µ¤é¤Ë 10 ¥Ö¥í¥Ã¥¯¤·¤«»È¤¨¤Ê¤¤¤Î¤Ç¤¹¡£
 	11 ¥Ö¥í¥Ã¥¯¤ò»È¤ª¤¦¤È¤¹¤ë¤È¼ºÇÔ¤·¤Þ¤¹¡£</para>
 
       <indexterm><primary>¥½¥Õ¥È¥ê¥ß¥Ã¥È</primary></indexterm>
       <para>°ìÊý¡¢
 	¥½¥Õ¥È¥ê¥ß¥Ã¥È¤Ï¤¢¤ë¸Â¤é¤ì¤¿»þ´ÖÆâ¤Ç¤¢¤ì¤Ð±Û¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	¤³¤Î»þ´Ö¤Ïͱͽ´ü´Ö¤È¤·¤ÆÃΤé¤ì¤Æ¤ª¤ê¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï 1 ½µ´Ö¤Ç¤¹¡£
 	¤¢¤ë¥æ¡¼¥¶¤¬¼«Ê¬¤Î¥½¥Õ¥È¥ê¥ß¥Ã¥È¤òͱͽ´ü´Ö¤è¤ê¤âŤ¤´Ö±Û¤¨¤Æ¤¤¤ë¤È¥½¥Õ¥È¥ê¥ß¥Ã¥È¤Ï¥Ï¡¼¥É¥ê¥ß¥Ã¥È¤ËÊѤï¤ê¡¢¤½¤ì°Ê¾å»ÈÍѤ¹¤ë¤³¤È¤Ï¤Ç¤­¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£
 	¥æ¡¼¥¶¤¬¥½¥Õ¥È¥ê¥ß¥Ã¥È¤è¤ê¤â¸º¤é¤»¤Ðͱͽ´ü´Ö¤Ï¥ê¥»¥Ã¥È¤µ¤ì¤Þ¤¹¡£</para>
 
       <para>°Ê²¼¤Ï &man.edquota.8;
 	¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤¿»þ¤Ë¸«¤ë¤³¤È¤Ë¤Ê¤ë¤Ç¤¢¤í¤¦Îã¤Ç¤¹¡£
 	&man.edquota.8; ¥³¥Þ¥ó¥É¤¬µ¯Æ°¤µ¤ì¤ë¤È´Ä¶­ÊÑ¿ô
 	<envar>EDITOR</envar> ¤Ç»ØÄꤵ¤ì¤ë¥¨¥Ç¥£¥¿¤ËÆþ¤ê¤Þ¤¹¡£
 	<envar>EDITOR</envar> ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë¤Ï
 	<application>vi</application> ¤¬µ¯Æ°¤µ¤ì¤Þ¤¹¡£
 	¤³¤³¤Ç¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤òÊÔ½¸¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>edquota -u test</userinput></screen>
 
       <programlisting>Quotas for user test:
 /usr: blocks in use: 65, limits (soft = 50, hard = 75)
         inodes in use: 7, limits (soft = 50, hard = 60)
 /usr/var: blocks in use: 0, limits (soft = 50, hard = 75)
         inodes in use: 0, limits (soft = 50, hard = 60)</programlisting>
 
       <para>Ä̾¥¯¥©¡¼¥¿¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àËè¤Ë 2 ¹Ô¤¢¤ê¤Þ¤¹¡£
 	°ì¤Ä¤Ï¥Ö¥í¥Ã¥¯¥ê¥ß¥Ã¥ÈÍѤǤ⤦°ì¤Ä¤Ï inode ¥ê¥ß¥Ã¥ÈÍѤǤ¹¡£
 	¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤òÊѹ¹¤·¤¿¤¤¤È¤³¤í¤ò½ñ¤­ÊѤ¨¤ë¤À¤±¤Ç¤«¤Þ¤¤¤Þ¤»¤ó¡£
 	¤¿¤È¤¨¤Ð¤³¤Î¥æ¡¼¥¶¤Î¥Ö¥í¥Ã¥¯¥ê¥ß¥Ã¥È¤ò¡¢¥½¥Õ¥È¥ê¥ß¥Ã¥È¤Ï 50 ¤«¤é 500
 	¤Ø¡¢¥Ï¡¼¥É¥ê¥ß¥Ã¥È¤Ï 75 ¤«¤é 600 ¤ËÊѹ¹¤¹¤ë¾ì¹ç¡¢</para>
 
       <programlisting>/usr: blocks in use: 65, limits (soft = 50, hard = 75)</programlisting>
 
       <para>¤«¤é</para>
 
       <programlisting> /usr: blocks in use: 65, limits (soft = 500, hard = 600)</programlisting>
 
       <para>¤Ø½ñ¤­´¹¤¨¤Þ¤¹¡£¿·¤·¤¤¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤Ï¥¨¥Ç¥£¥¿¤ò½ªÎ»¤¹¤ì¤ÐÀßÄꤵ¤ì¤Þ¤¹¡£</para>
 
       <para>¤¢¤ëÈϰϤΠUID
 	¤ËÂФ·¤Æ¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤òÀßÄꤷ¤¿¤¤¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¤¬¡¢¤³¤Î¤è¤¦¤Ê»þ¤Ë¤Ï
 	&man.edquota.8; ¥³¥Þ¥ó¥É¤Î <option>-p</option>
 	¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¤¤¤¤¤Ç¤·¤ç¤¦¡£¤Þ¤º¡¢
 	¤¢¤ë¥æ¡¼¥¶¤Ë³ä¤êÅö¤Æ¤¿¤¤¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤òÀßÄꤷ¡¢¼¡¤Ë
 	<command>edquota -p protouser startuid-enduid</command>
 	¤ò¼Â¹Ô¤¹¤ë¤Î¤Ç¤¹¡£Î㤨¤Ð¥æ¡¼¥¶ <username>test</username>
 	¤Ë¤ªË¾¤ß¤Î¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤¬ÉÕ¤¤¤Æ¤¤¤ë¤È¤·¤Þ¤·¤ç¤¦¡£
 	¼¡¤Î¥³¥Þ¥ó¥É¤Ë¤è¤ê 10,000 ¤«¤é 19,999 ¤Î´Ö¤Î UID
 	¤ËÂФ·¤ÆƱ¤¸¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤òÉÕ¤±¤ë¤³¤È¤¬¤Ç¤­¤ë¤Î¤Ç¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>edquota -p test 10000-19999</userinput></screen>
 
       <para>¤µ¤é¤Ë¾Ü¤·¤¤¤³¤È¤Ï &man.edquota.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</para>
     </sect2>
 
     <sect2>
       <title>¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤È¥Ç¥£¥¹¥¯»ÈÍѾõ¶·¤Î¥Á¥§¥Ã¥¯</title>
       <indexterm>
 	<primary>¥Ç¥£¥¹¥¯¥¯¥©¡¼¥¿</primary>
 	<secondary>¥Á¥§¥Ã¥¯</secondary>
       </indexterm>
 
       <para>&man.quota.1; ¤Þ¤¿¤Ï &man.repquota.8;
 	¤È¤¤¤Ã¤¿¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤ä¥Ç¥£¥¹¥¯¤ÎÍøÍѾõ¶·¤ò³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	&man.quota.1; ¥³¥Þ¥ó¥É¤Ï¸Ä¡¹¤Î¥æ¡¼¥¶¤ä¥°¥ë¡¼¥×¤Î¥¯¥©¡¼¥¿¤ä¥Ç¥£¥¹¥¯ÍøÍѾõ¶·¤ò³Îǧ¤¹¤ë¤Î¤Ë»È¤¨¤Þ¤¹¡£
 	¥æ¡¼¥¶¤Ï¼«¿È¤Î¥¯¥©¡¼¥¿¡¢¤½¤·¤Æ½ê°¤¹¤ë¥°¥ë¡¼¥×¤Î¥°¥ë¡¼¥×¤Î¤ß³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¤Î¤ß¤¬Â¾¤Î¥æ¡¼¥¶¤ä½ê°¤·¤Æ¤¤¤Ê¤¤¥°¥ë¡¼¥×¤Î¥¯¥©¡¼¥¿¤ÈÍøÍѾõ¶·¤ò¸«¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
 	&man.repquota.8; ¥³¥Þ¥ó¥É¤ò»È¤¦¤È¡¢¥¯¥©¡¼¥¿¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àÍѤÎÁ´¤Æ¤Î¥¯¥©¡¼¥¿¤ä¥Ç¥£¥¹¥¯ÍÆÎ̤Υµ¥Þ¥ê¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <para>°Ê²¼¤ÏÆó¤Ä¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¥¯¥©¡¼¥¿À©¸Â¤¬¤«¤±¤é¤ì¤Æ¤¤¤ë¥æ¡¼¥¶¤ËÂФ¹¤ë<command>quota -v</command> ¥³¥Þ¥ó¥É¤Î½ÐÎÏÎã¤Ç¤¹¡£</para>
 
       <programlisting>Disk quotas for user test (uid 1002):
      Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
            /usr      65*     50      75   5days       7      50      60
        /usr/var       0      50      75               0      50      60</programlisting>
 
       <indexterm><primary>ͱͽ´ü´Ö</primary></indexterm>
       <para>¾å¤ÎÎã¤Ç¡¢<filename>/usr</filename>
 	¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ç¤Ï¤³¤Î¥æ¡¼¥¶¤Ï¸½ºß
 	50 ¥Ö¥í¥Ã¥¯¤È¤¤¤¦¥½¥Õ¥È¥ê¥ß¥Ã¥È¤ò 15 ¥Ö¥í¥Ã¥¯¥ª¡¼¥Ð¡¼¤·
 	5 Æü´Ö¤Îͱͽ´ü´Ö¤¬»Ä¤Ã¤Æ¤¤¤Þ¤¹¡£¥¢¥¹¥¿¥ê¥¹¥¯ <literal>*</literal>
 	¤Ï¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤ò±Û¤¨¤Æ¤¤¤ë¥æ¡¼¥¶¤ò¼¨¤·¤Æ¤¤¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
       <para>Ä̾¤½¤Î¥æ¡¼¥¶¤¬Á´¤¯»È¤Ã¤Æ¤¤¤Ê¤¤¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï¡¢
 	¥¯¥©¡¼¥¿¥ê¥ß¥Ã¥È¤¬ÉÕ¤±¤é¤ì¤Æ¤¤¤ë¤È¤·¤Æ¤â
 	&man.quota.1; ¥³¥Þ¥ó¥É¤Î½ÐÎϤˤϸ½¤ï¤ì¤Þ¤»¤ó¡£
 	<option>-v</option> ¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤ì¤Ð¤½¤Î¤è¤¦¤Ê¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¡¢
 	¾å¤ÎÎã¤Ç¤Ï <filename>/usr/var</filename>¡¢
 	¤òɽ¼¨¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
     </sect2>
 
     <sect2>
       <title>NFS ¾å¤Î ¥¯¥©¡¼¥¿</title>
       <indexterm><primary>NFS</primary></indexterm>
 
       <para>¥¯¥©¡¼¥¿¤Ï NFS ¥µ¡¼¥Ð¾å¤Î¥¯¥©¡¼¥¿¥µ¥Ö¥·¥¹¥Æ¥à¤Ë¤è¤ê¼Â¹Ô¤µ¤ì¤Þ¤¹¡£
 	&man.rpc.rquotad.8; ¥Ç¡¼¥â¥ó¤Ë¤è¤ê¡¢NFS ¥¯¥é¥¤¥¢¥ó¥È¾å¤Î &man.quota.1;
 	¥³¥Þ¥ó¥É¤Ï¾ðÊó¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¡¢¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¾å¤Î¥æ¡¼¥¶¤¬¼«Ê¬¤Î¥¯¥©¡¼¥¿¤ÎÅý·×¤ò¸«¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
 
       <para><filename>/etc/inetd.conf</filename> ¤Ë¤ª¤¤¤Æ°Ê²¼¤Î¤è¤¦¤Ë
 	<command>rpc.rquotad</command> ¤òÍ­¸ú¤Ë¤·¤Þ¤·¤ç¤¦¡£</para>
 
       <programlisting>rquotad/1      dgram rpc/udp wait root /usr/libexec/rpc.rquotad rpc.rquotad</programlisting>
 
       <para>¤½¤·¤Æ°Ê²¼¤Î¤è¤¦¤Ë <command>inetd</command> ¤òºÆµ¯Æ°¤·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>kill -HUP `cat /var/run/inetd.pid`</userinput></screen>
     </sect2>
   </sect1>
 
   <sect1 id="disks-encrypting">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Lucky</firstname>
 	  <surname>Green</surname>
 	  <contrib>´ó¹Æ: </contrib>
 	  <affiliation>
 	    <address><email>shamrock@cypherpunks.to</email></address>
 	  </affiliation>
 	</author>
       </authorgroup>
       <!-- 11 MARCH 2003 -->
     </sect1info>
 
     <title>¥Ç¥£¥¹¥¯¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î°Å¹æ²½</title>
     <indexterm>
       <primary>¥Ç¥£¥¹¥¯</primary>
       <secondary>°Å¹æ²½</secondary></indexterm>
 
     <para>FreeBSD
       ¤Ï̵µö²Ä¤Î¥Ç¡¼¥¿¥¢¥¯¥»¥¹¤ËÂФ¹¤ëÍ¥¤ì¤¿¥ª¥ó¥é¥¤¥óÊݸǽ¤òÄ󶡤·¤Þ¤¹¡£
       ¥Õ¥¡¥¤¥ë¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤ª¤è¤Ó¶¯À©Åª¥¢¥¯¥»¥¹¥³¥ó¥È¥í¡¼¥ë
       (MAC: Mandatory Access Control)
       (Mandatory Access Control (MAC) ¤ò»²¾È)
       <!-- Furukawa:2004/1/8
       should be refer this after updating security/chapter.xml
       (<xref linkend="mac"/> ¤ò»²¾È)
       -->
       ¤Ï¡¢¥³¥ó¥Ô¥å¡¼¥¿¤¬Æ°ºîÃæ¤Ç¡¢OS ¤¬¼Â¹ÔÃæ¤Ç¤¢¤ë¤È¤­¤Ë¡¢
       ̵µö²Ä¤ÎÂè»°¼Ô¤¬¥Ç¡¼¥¿¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤Î¤òËɤ°¤³¤È¤ËÌòΩ¤Á¤Þ¤¹¡£
       ¤·¤«¤·¤Ê¤¬¤é¡¢¹¶·â¼Ô¤¬¥³¥ó¥Ô¥å¡¼¥¿¤ËʪÍýŪ¤Ë¥¢¥¯¥»¥¹¤·¡¢
       µ¡Ì©¥Ç¡¼¥¿¤ò¥³¥Ô¡¼¤·Ê¬ÀϤ¹¤ë¤¿¤á¤Ë¥³¥ó¥Ô¥å¡¼¥¿¤Î¥Ï¡¼¥É¥É¥é¥¤¥Ö¤òÊ̤Υ·¥¹¥Æ¥à¤Ë°ÜÆ°¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤ì¤Ð¡¢
       OS ¤Ë¤è¤Ã¤Æ¶¯²½¤µ¤ì¤¿µö²Ä°À­¤Ï°ÕÌ£¤ò¤Ê¤µ¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£</para>
 
     <para>¹¶·â¼Ô¤¬ÅŸ»¤ÎÍî¤Á¤¿¥³¥ó¥Ô¥å¡¼¥¿¤ä
       ¥Ï¡¼¥É¥É¥é¥¤¥Ö¤ò¼ê¤Ë¤¤¤ì¤ë¼êÃʤˤ«¤«¤ï¤é¤º¡¢
       <application>GEOM ¥Ù¡¼¥¹¤Î¥Ç¥£¥¹¥¯°Å¹æ²½ (gbde: GEOM Based Disk Encryption)</application>
       ¤Ï¡¢Ãø¤·¤¤»ñ¸»¤ò»ý¤ÁËܵ¤¤Ç¹¶·â¤ò»Å³Ý¤±¤ë¤Ä¤â¤ê¤Ç¤ä¤Ã¤Æ¤­¤¿¹¶·â¼Ô¤«¤é¤µ¤¨¤â¥³¥ó¥Ô¥å¡¼¥¿¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ë¤¢¤ë¥Ç¡¼¥¿¤òÊݸ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
       ¸Ä¡¹¤Î¥Õ¥¡¥¤¥ë¤À¤±¤ò°Å¹æ²½¤¹¤ëÈѤ路¤¤ÊýË¡¤È°Û¤Ê¤ê¡¢
       <application>gbde</application>
       ¤ÏÁ´¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÆ©²áŪ¤Ë°Å¹æ²½¤·¤Þ¤¹¡£
       ʿʸ¥Æ¥­¥¹¥È¤Ï·è¤·¤Æ¥Ï¡¼¥É¥É¥é¥¤¥Ö¤Î¥×¥é¥Ã¥¿¤Ë´Ø·¸¤·¤Þ¤»¤ó¡£</para>
 
     <sect2>
       <title>¥«¡¼¥Í¥ë¤Ç gbde ¤òÍ­¸ú¤Ë¤¹¤ë</title>
 
       <procedure>
 	<step>
 	  <title><username>root</username> ¤Ë¤Ê¤ë</title>
 
 	  <para><application>gbde</application>
 	    ¤ÎÀßÄê¤ò¤¹¤ë¤Ë¤Ï¥¹¡¼¥Ñ¥æ¡¼¥¶¤Î¸¢¸Â¤¬É¬Íפˤʤê¤Þ¤¹¡£
 	    °Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¡¢
 	    <username>root</username> ¤Ë¤Ê¤Ã¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <screen>&prompt.user; <userinput>su -</userinput>
 Password:</screen>
 	</step>
 
 	<step>
 	  <title>¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ð¡¼¥¸¥ç¥ó¤ò³Î¤«¤á¤ë</title>
 
 	  <para>&man.gbde.4; ¤¬Æ°ºî¤¹¤ë¤Ë¤Ï FreeBSD 5.0 °Ê¹ß¤¬É¬ÍפǤ¹¡£
 	    °Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¡¢
 	    ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ð¡¼¥¸¥ç¥ó¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <screen>&prompt.root; <userinput>uname -r</userinput>
 5.0-RELEASE</screen>
 	</step>
 
 	<step>
 	  <title>¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥®¥å¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë &man.gbde.4;
 	    Âбþ¤òÄɲ乤ë</title>
 
 	  <para>¤ª¹¥¤ß¤Î¥Æ¥­¥¹¥È¥¨¥Ç¥£¥¿¤ò»ÈÍѤ·¤Æ¡¢
 	    °Ê²¼¤Î¹Ô¤ò¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥®¥å¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ë²Ã¤¨¤Þ¤¹¡£</para>
 
 	  <para><literal>options GEOM_BDE</literal></para>
 
 	  <para>FreeBSD ¥«¡¼¥Í¥ë¤òÀßÄê¡¢ºÆ¥³¥ó¥Ñ¥¤¥ë¡¢¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
 	    ¤³¤Î¼ê½ç¤Ï <xref linkend="kernelconfig"/> ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
 	  <para>¿·¤·¤¤¥«¡¼¥Í¥ë¤ÇºÆµ¯Æ°¤·¤Þ¤¹¡£</para>
 	</step>
       </procedure>
     </sect2>
 
     <sect2>
       <title>°Å¹æ²½¤µ¤ì¤¿¥Ï¡¼¥É¥É¥é¥¤¥Ö¤Î½àÈ÷</title>
 
       <para>°Ê²¼¤ÎÎã¤Ç¤Ï¡¢¥·¥¹¥Æ¥à¤Ë¿·¤·¤¤¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤òÄɲ䷤褦¤È¤·¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥·¥¹¥Æ¥à¤Ïñ°ì¤Î°Å¹æ²½¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÊÝ»ý¤¹¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
 	¤³¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ï <filename>/private</filename>
 	¤È¤·¤Æ¥Þ¥¦¥ó¥È¤µ¤ì¤Þ¤¹¡£<application>gbde</application> ¤Ï
 	<filename>/home</filename> ¤ª¤è¤Ó <filename>/var/mail</filename>
 	¤ò°Å¹æ²½¤¹¤ë¤Î¤Ë¤â»ÈÍѤǤ­¤Þ¤¹¤¬¡¢
 	¤è¤êÊ£»¨¤Ê»Ø¼¨¤òɬÍפȤʤë¤Î¤Ç¤³¤Î²òÀâ¤ÎÈÏáƤò±Û¤¨¤Æ¤¤¤Þ¤¹¡£</para>
 
       <procedure>
 	<step>
 	  <title>¿·¤·¤¤¥Ï¡¼¥É¥É¥é¥¤¥Ö¤òÄɲ乤ë</title>
 
 	  <para><xref linkend="disks-adding"/> ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ëÄ̤ê¤Ë¿·¤·¤¤¥É¥é¥¤¥Ö¤ò¥·¥¹¥Æ¥à¤ËÀßÃÖ¤·¤Þ¤¹¡£
 	    ¤³¤ÎÎã¤Ç¤Ï¡¢¿·¤·¤¤¥Ï¡¼¥É¥É¥é¥¤¥Ö¤Ï
 	    <devicename>/dev/ad4s1c</devicename> ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë
 	    ²Ã¤¨¤é¤ì¤¿¤â¤Î¤È¤·¤Þ¤¹¡£
 	    <devicename>/dev/ad0s1<replaceable>*</replaceable></devicename>
 	    ¥Ç¥Ð¥¤¥¹¤Ï¡¢¤³¤ÎÎã¤Î¥·¥¹¥Æ¥à¾å¤Ë¸ºß¤¹¤ëɸ½àŪ¤Ê
 	    FreeBSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òɽ¤·¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>ls /dev/ad*</userinput>
 /dev/ad0        /dev/ad0s1b     /dev/ad0s1e     /dev/ad4s1
 /dev/ad0s1      /dev/ad0s1c     /dev/ad0s1f     /dev/ad4s1c
 /dev/ad0s1a     /dev/ad0s1d     /dev/ad4</screen>
 	</step>
 
 	<step>
 	  <title>gbde ¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤òÊÝ»ý¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤òºîÀ®¤¹¤ë</title>
 
 	  <screen>&prompt.root; <userinput>mkdir /etc/gbde</userinput></screen>
 
 	  <para><application>gbde</application> ¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢
 	    °Å¹æ²½¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤Î¤ËɬÍפȤʤë¾ðÊ󤬳ÊǼ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
 	    ¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Ë¥¢¥¯¥»¥¹¤·¤Ê¤¤¾ì¹ç¡¢
 	    <application>gbde</application> ¤Ï
 	    ËÄÂç¤Ê¼êÆ°¤Ë¤è¤ë²ðºß¤Ê¤·¤Ë¤Ï (¥½¥Õ¥È¥¦¥§¥¢¤ÏÂбþ¤·¤Æ¤¤¤Þ¤»¤ó)¡¢°Å¹æ²½¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë´Þ¤Þ¤ì¤ë¥Ç¡¼¥¿¤ò²òÆɤ¹¤ë¤³¤È¤Ï¤Ç¤­¤Ê¤¤¤Ç¤·¤ç¤¦¡£
 	    ¤½¤ì¤¾¤ì¤Î°Å¹æ²½¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ÏÊÌ¡¹¤Î¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤ò»ÈÍѤ·¤Þ¤¹¡£</para>
 	</step>
 
 	<step>
 	  <title>gbde ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò½é´ü²½¤¹¤ë</title>
 
 	  <para><application>gbde</application>
 	    ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ï»ÈÍѤ¹¤ëÁ°¤Ë½é´ü²½¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
 	    ¤³¤Î½é´ü²½¤Ï°ìÅÙ¤À¤±¼Â¹Ô¤µ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c</userinput></screen>
 
 	  <para>¥¨¥Ç¥£¥¿¤¬³«¤¯¤Î¤Ç¡¢
 	    ¥Æ¥ó¥×¥ì¡¼¥È¤ò¤â¤È¤Ë¤µ¤Þ¤¶¤Þ¤Ê¥ª¥×¥·¥ç¥ó¤òÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
 	    UFS1 ¤Þ¤¿¤Ï UFS2 ¤Ç»ÈÍѤ¹¤ë¤Ë¤Ï¡¢sector_size ¤ò
 	    2048 ¤ËÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£</para>
 
 	  <programlisting>$<!-- This is not the space you are looking
 for-->FreeBSD: src/sbin/gbde/template.txt,v 1.1 2002/10/20 11:16:13 phk Exp $
 #
 # Sector size is the smallest unit of data which can be read or written.
 # Making it too small decreases performance and decreases available space.
 # Making it too large may prevent filesystems from working.  512 is the
 # minimum and always safe.  For UFS, use the fragment size
 #
 sector_size     =       2048
 [...]
 </programlisting>
 
 	  <para>&man.gbde.8;
 	    ¤Ï¥Ç¡¼¥¿¤òÊݸ¤ë¤Î¤Ë»ÈÍѤ¹¤ë¥Ñ¥¹¥Õ¥ì¡¼¥º¤òÆóÅÙ¿Ò¤Þ¤¹¡£
 	    ¥Ñ¥¹¥Õ¥ì¡¼¥º¤Ï¤½¤ì¤¾¤ìƱ¤¸¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
 	    ¥Ç¡¼¥¿¤òÊݸ¤ë <application>gbde</application> ¤ÎǽÎϤϡ¢
 	    ¤¢¤Ê¤¿¤¬ÁªÂò¤·¤¿¥Ñ¥¹¥Õ¥ì¡¼¥º¤ÎÉʼÁ¤Ë´°Á´¤Ë°Í¸¤·¤Þ¤¹¡£
 	    <footnote>
 	      <para>µ­²±¤¹¤ë¤Î¤¬´Êñ¤Ç¡¢
 		°ÂÁ´¤Ê¥Ñ¥¹¥Õ¥ì¡¼¥º¤òÁªÂò¤¹¤ëÊýË¡¤Ë¤Ä¤¤¤Æ¤Ï¡¢
 		<ulink url="http://world.std.com/~reinhold/diceware.html">
 		  Diceware Passphrase</ulink>
 		¥¦¥§¥Ö¥µ¥¤¥È¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para></footnote></para>
 
 	  <para><command>gbde init</command> ¥³¥Þ¥ó¥É¤Ï
 	    <application>gbde</application>
 	    ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ËÂФ¹¤ë¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Þ¤¹¡£¤³¤ÎÎã¤Ç¤Ï
 	    <filename>/etc/gbde/ad4s1c</filename> ¤Ë³ÊǼ¤µ¤ì¤Þ¤¹¡£</para>
 
 	  <caution>
 	    <para><application>gbde</application> ¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Ï¡¢
 	      ¤¹¤Ù¤Æ¤Î°Å¹æ²½¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ÎÆâÍƤȤȤâ¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤µ¤ì¤Ê¤±¤ì¤Ð <emphasis>¤Ê¤ê¤Þ¤»¤ó</emphasis>¡£
 	      ¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤À¤±¤òºï½ü¤·¤Æ¤¤¤ë´Ö¡¢
 	      ¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Ê¤·¤Ç¤Ï¿®Ç°¤Î¸Ç¤¤¹¶·â¼Ô¤¬
 	      <application>gbde</application>
 	      ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò²òÆɤ¹¤ë¤³¤È¤òËɤ°¤³¤È¤¬¤Ç¤­¤Ê¤¤°ìÊý¤Ç¡¢
 	      ÀµÅö¤Ê½êÍ­¼Ô¤Ï¡¢&man.gbde.8; ¤ª¤è¤Ó¤³¤ÎÀ߷׼Ԥˤޤ俤¯»Ù»ý¤µ¤ì¤Ê¤¤ËÄÂç¤ÊÎ̤κî¶È¤Ê¤·¤Ë¤Ï¡¢
 	      °Å¹æ²½¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¾å¤Î¥Ç¡¼¥¿¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤Ç¤·¤ç¤¦¡£</para>
 	  </caution>
 	</step>
 
 	<step>
 	  <title>¥«¡¼¥Í¥ë¤Ë°Å¹æ²½¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÀܳ¤¹¤ë</title>
 
 	  <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c</userinput></screen>
 
 	  <para>°Å¹æ²½¤µ¤ì¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò½é´ü²½¤¹¤ëºÝ¤ËÁªÂò¤·¤¿¥Ñ¥¹¥Õ¥ì¡¼¥º¤òÆþÎϤ¹¤ë¤è¤¦¤Ëµá¤á¤é¤ì¤Þ¤¹¡£
 	    ¿·¤·¤¤°Å¹æ²½¥Ç¥Ð¥¤¥¹¤Ï <filename>/dev</filename> ¤Ë
 	    <filename>/dev/device_name.bde</filename>
 	    ¤È¤·¤Æ¸½¤ì¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>ls /dev/ad*</userinput>
 /dev/ad0        /dev/ad0s1b     /dev/ad0s1e     /dev/ad4s1
 /dev/ad0s1      /dev/ad0s1c     /dev/ad0s1f     /dev/ad4s1c
 /dev/ad0s1a     /dev/ad0s1d     /dev/ad4        /dev/ad4s1c.bde</screen>
 	</step>
 
 	<step>
 	  <title>°Å¹æ²½¥Ç¥Ð¥¤¥¹¾å¤Ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë</title>
 
 	  <para>¥«¡¼¥Í¥ë¤Ë°Å¹æ²½¥Ç¥Ð¥¤¥¹¤¬Àܳ¤µ¤ì¤ë¤È¡¢
 	    ¥Ç¥Ð¥¤¥¹¾å¤Ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤Ç¤­¤Þ¤¹¡£
 	    °Å¹æ²½¥Ç¥Ð¥¤¥¹¾å¤Ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤Ë¤Ï &man.newfs.8;
 	    ¤ò»ÈÍѤ·¤Þ¤¹¡£½¾Íè¤Î UFS1 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç½é´ü²½¤¹¤ë¤è¤ê¡¢
 	    ¿·¤·¤¤ UFS2 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç½é´ü²½¤·¤¿Êý¤¬¹â®¤Ê¤Î¤Ç¡¢
 	    <option>-O2</option> ¥ª¥×¥·¥ç¥ó¤È¤È¤â¤Ë &man.newfs.8;
 	    ¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
 
 	  <note><para>&os;&nbsp;5.1-RELEASE °Ê¹ß¤Ç¤Ï¡¢<option>-O2</option>
 	      ¥ª¥×¥·¥ç¥ó¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤¹¡£</para></note>
 
 	  <screen>&prompt.root; <userinput>newfs -U -O2 /dev/ad4s1c.bde</userinput></screen>
 
 	  <note>
 	    <para>&man.newfs.8; ¤Ï¡¢¥Ç¥Ð¥¤¥¹Ì¾¤Ë
 	      <filename><replaceable>*</replaceable>.bde</filename>
 	      ³ÈÄ¥»Ò¤Ë¤è¤Ã¤Æǧ¼±¤µ¤ì¤ë¡¢
 	      Àܳ¤µ¤ì¤¿ <application>gbde</application>
 	      ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ËÂФ·¤Æ¼Â¹Ô¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 	  </note>
 	</step>
 
 	<step>
 	  <title>°Å¹æ²½¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¥Þ¥¦¥ó¥È¤¹¤ë</title>
 
 	  <para>°Å¹æ²½¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ¹¤ë¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤òºîÀ®¤·¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>mkdir /private</userinput></screen>
 
 	  <para>°Å¹æ²½¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Þ¥¦¥ó¥È¤·¤Þ¤¹¡£</para>
 
 	  <screen>&prompt.root; <userinput>mount /dev/ad4s1c.bde /private</userinput></screen>
 	</step>
 
 	<step>
 	  <title>°Å¹æ²½¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬ÍøÍѲÄǽ¤«³Î¤«¤á¤ë</title>
 
 	  <para>¤³¤ì¤Ç°Å¹æ²½¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï &man.df.1; ¤Ç¸«¤ë¤³¤È¤¬¤Ç¤­¡¢
 	    ÍøÍѤ¹¤ë½àÈ÷¤¬¤Ç¤­¤Þ¤·¤¿¡£</para>
 
 	  <screen>&prompt.user; <userinput>df -H</userinput>
 Filesystem        Size   Used  Avail Capacity  Mounted on
 /dev/ad0s1a      1037M    72M   883M     8%    /
 /devfs            1.0K   1.0K     0B   100%    /dev
 /dev/ad0s1f       8.1G    55K   7.5G     0%    /home
 /dev/ad0s1e      1037M   1.1M   953M     0%    /tmp
 /dev/ad0s1d       6.1G   1.9G   3.7G    35%    /usr
 /dev/ad4s1c.bde   150G   4.1K   138G     0%    /private</screen>
 	</step>
       </procedure>
     </sect2>
 
     <sect2>
       <title>¸ºß¤¹¤ë°Å¹æ²½¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Þ¥¦¥ó¥È¤¹¤ë</title>
 
       <para>¥·¥¹¥Æ¥à¤òµ¯Æ°¤¹¤ëÅ٤ˡ¢¤¹¤Ù¤Æ¤Î°Å¹æ²½¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï
 	»ÈÍÑÁ°¤Ë¥«¡¼¥Í¥ë¤ËÀܳ¤·¡¢
 	¥¨¥é¡¼¤Î̵ͭ¤ò¥Á¥§¥Ã¥¯¤·¡¢¥Þ¥¦¥ó¥È¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
 	ɬÍפʥ³¥Þ¥ó¥É¤Ï <username>root</username>
 	¥æ¡¼¥¶¤È¤·¤Æ¼Â¹Ô¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
       <procedure>
 	<step>
 	  <title>¥«¡¼¥Í¥ë¤Ë gbde ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÀܳ¤¹¤ë</title>
 
 	  <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c</userinput></screen>
 
 	  <para>¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î°Å¹æ²½¤ò½é´ü²½¤¹¤ëºÝ¤ËÁªÂò¤·¤¿¥Ñ¥¹¥Õ¥ì¡¼¥º¤òÆþÎϤ¹¤ë¤è¤¦¤Ëµá¤á¤é¤ì¤ë¤Ç¤·¤ç¤¦¡£</para>
 	</step>
 
 	<step>
 	  <title>¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¨¥é¡¼¤ò¥Á¥§¥Ã¥¯¤¹¤ë</title>
 
 	  <para>°Å¹æ²½¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¼«Æ°Åª¤Ë¥Þ¥¦¥ó¥È¤¹¤ë¤¿¤á¤Ë
 	    <filename>/etc/fstab</filename> ¤ËÀßÄê¤ò·ÇºÜ¤¹¤ë¤³¤È¤Ï¤Þ¤À¤Ç¤­¤Ê¤¤¤¿¤á¡¢
 	    ¥Þ¥¦¥ó¥È¤¹¤ëÁ°¤Ë &man.fsck.8; ¤ò¼Â¹Ô¤·¤Æ¡¢
 	    ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¨¥é¡¼¤ò¥Á¥§¥Ã¥¯¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
 
 	  <screen>&prompt.root; <userinput>fsck -p -t ffs /dev/ad4s1c.bde</userinput></screen>
 	</step>
 
 	<step>
 	  <title>°Å¹æ²½¥Õ¥¡¥¤¥ë¤ò¥Þ¥¦¥ó¥È¤¹¤ë</title>
 
 	  <screen>&prompt.root; <userinput>mount /dev/ad4s1c.bde /private</userinput></screen>
 
 	  <para>¤³¤ì¤Ç°Å¹æ²½¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬ÍøÍѤǤ­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£</para>
 	</step>
       </procedure>
 
       <sect3>
 	<title>°Å¹æ²½¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¼«Æ°Åª¤Ë¥Þ¥¦¥ó¥È¤¹¤ë</title>
 
 	<para>¥¹¥¯¥ê¥×¥È¤òºîÀ®¤·¤Æ¡¢°Å¹æ²½¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¼«Æ°Åª¤ËÀܳ¡¢
 	  ¥Á¥§¥Ã¥¯¡¢¥Þ¥¦¥ó¥È¤¹¤ë¤³¤È¤Ï²Äǽ¤Ç¤¹¡£¤·¤«¤·¤Ê¤¬¤é¡¢
 	  °ÂÁ´¾å¤ÎÍýͳ¤Ë¤è¤ê¥¹¥¯¥ê¥×¥È¤Ë &man.gbde.8;
 	  ¥Ñ¥¹¥ï¡¼¥É¤ò´Þ¤á¤ë¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤½¤ÎÂå¤ï¤ê¤Ë¡¢¥³¥ó¥½¡¼¥ë¤Þ¤¿¤Ï
 	  &man.ssh.1; ¤Ë¤è¤ëÀܳ¤«¤é¥Ñ¥¹¥ï¡¼¥É¤òÆþÎϤ¹¤ë¤è¤¦¤Ê¥¹¥¯¥ê¥×¥È¤¬¼êÆ°¤Ç¼Â¹Ô¤µ¤ì¤ë¤³¤È¤¬¿ä¾©¤µ¤ì¤Þ¤¹¡£</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>gbde ¤¬ºÎÍѤ·¤¿°Å¹æ¤ÎÊݸî</title>
 
       <para>&man.gbde.8; ¤Ï 128bit AES ¤Î
 	CBC ¥â¡¼¥É¤ò»ÈÍѤ·¤Æ¥»¥¯¥¿¥Ú¥¤¥í¡¼¥É¤ò°Å¹æ²½¤·¤Þ¤¹¡£
 	¥Ç¥£¥¹¥¯¾å¤Î¤½¤ì¤¾¤ì¤Î¥»¥¯¥¿¤Ï°Û¤Ê¤ë AES ¸°¤Ç°Å¹æ²½¤µ¤ì¤Þ¤¹¡£
 	¥»¥¯¥¿¸°¤¬¥æ¡¼¥¶¤¬ÆþÎϤ·¤¿¥Ñ¥¹¥Õ¥ì¡¼¥º¤«¤é¤É¤Î¤è¤¦¤ËƳ¤­½Ð¤µ¤ì¤ë¤«¤ò´Þ¤á¡¢
 	<application>gbde</application> ¤Î°Å¹æ¼êË¡¤ÎÀ߷פˤĤ¤¤Æ¤Î¾ÜºÙ¤Ï¡¢
 	&man.gbde.4; ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
     </sect2>
 
     <sect2>
       <title>¸ß´¹À­¤Ë´Ø¤¹¤ëÌäÂê</title>
 
       <para>&man.sysinstall.8; ¤Ï
 	<application>gbde</application> °Å¹æ²½¥Ç¥Ð¥¤¥¹¤È¸ß´¹À­¤¬¤¢¤ê¤Þ¤»¤ó¡£
 	&man.sysinstall.8; ¤ò¼Â¹Ô¤¹¤ëÁ°¤Ë
 	<devicename><replaceable>*</replaceable>.bde</devicename>
 	¥Ç¥Ð¥¤¥¹¤Ï¤¹¤Ù¤Æ¥«¡¼¥Í¥ë¤«¤éÀÚÃǤµ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
 	¤½¤¦¤·¤Ê¤¤¤È¡¢&man.sysinstall.8; ¤¬½é¤á¤Ë¥Ç¥Ð¥¤¥¹¤òÁöºº¤¹¤ëºÝ¤Ë¥¯¥é¥Ã¥·¥å¤·¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£
 	°Å¹æ²½¥Ç¥Ð¥¤¥¹¤òÀÚÃǤ¹¤ë¤Ë¤Ï¡¢°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Þ¤¹¡£</para>
 
       <screen>&prompt.root; <userinput>gbde detach /dev/ad4s1c</userinput></screen>
 
     </sect2>
   </sect1>
 </chapter>
diff --git a/ja_JP.eucJP/htdocs/java/install.xml b/ja_JP.eucJP/htdocs/java/install.xml
index 169cf65de5..495e423f91 100644
--- a/ja_JP.eucJP/htdocs/java/install.xml
+++ b/ja_JP.eucJP/htdocs/java/install.xml
@@ -1,75 +1,62 @@
 <?xml version="1.0" encoding="euc-jp"?>
 <!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
 "http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [
 <!ENTITY title "FreeBSD &java; Project: How To Install">
 <!-- $FreeBSD$ -->
 <!-- The FreeBSD Japanese Documentation Project -->
-<!-- Original revision: 1.17 -->
+<!-- Original revision: r42154 -->
 ]>
 <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.developers">
     <table border="0">
       <tr>
           <td>
 	    <p>FreeBSD ¤Ë Java ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤Ë¤¢¤¿¤Ã¤Æ¡¢
 	      ¤É¤Î Java ³«È¯¥­¥Ã¥È¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤«Áª¤ó¤Ç¤¯¤À¤µ¤¤¡£</p>
           </td>
       </tr>
       <tr>
           <td>
 	    <h3><a name="openjdk">FreeBSD ¤Î OpenJDK</a></h3>
 
 	    <p>OpenJDK ¤Î FreeBSD ¥Í¥¤¥Æ¥£¥Ö¤Ê port ¤Ç¤¹¡£</p>
 
 	    <p><code>cd /usr/ports/java/openjdk16<br/>
               make install clean</code></p>
           </td>
       </tr>
-      <tr>
-          <td>
-	    <h3><a name="jdk">Oracle ¼Ò¤Ë¤è¤ë FreeBSD ÍѤΠJDK</a></h3>
-
-	    <p>¤³¤ì¤Ï Java FreeBSD °Ü¿¢¥×¥í¥¸¥§¥¯¥È¤Ë¤è¤ëÀ®²Ì¤Ç¤¹¡£
-	      ¥×¥í¥¸¥§¥¯¥È¤¬ºîÀ®¤·¤¿¥Ñ¥Ã¥Á¥»¥Ã¥È¤È
-	      Oracle ¤¬¸ø³«¤·¤¿ JDK ¤Î¥½¡¼¥¹¥³¡¼¥É¤ò»ÈÍѤ·¤Æ¡¢
-	      FreeBSD ¥Í¥¤¥Æ¥£¥Ö¤Ê JDK ¤ò¹½ÃÛ¤·¤Þ¤¹¡£</p>
-
-	    <p><code>cd /usr/ports/java/jdk16<br/>
-              make install clean</code></p>
-          </td>
-      </tr>
       <tr>
           <td>
 	    <h3><a name="linux-sun-jdk">Oracle ¼Ò¤Ë¤è¤ë Linux ÍÑ JDK</a></h3>
 
 	    <p>¤³¤Î port ¤Ï¡¢Oracle ¼Ò¤¬
 	      Linux ÍѤ˹½ÃÛ¤·¤¿ Java ³«È¯¥­¥Ã¥È¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
 	      FreeBSD ¤Î Linux ¸ß´¹µ¡Ç½¤ò»ÈÍѤ·¤ÆÆ°ºî¤·¤Þ¤¹¡£</p>
 
 	    <p><code>cd /usr/ports/java/linux-sun-jdk16<br/>
               make install clean</code></p>
           </td>
       </tr>
       <tr>
           <td>
             <p><b>Note:</b>
 	      ¥é¥¤¥»¥ó¥¹¥Ý¥ê¥·¤Î¤¿¤á¤Ë¡¢
 	      FreeBSD ¤Î Oracle JDK ¥Ð¥¤¥Ê¥ê¤òÇÛÉÛ¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
               ¤Þ¤¿¡¢¸Ä¿ÍŪ¤Ê»ÈÍѤΤߤ¬µö²Ä¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
               ¥½¡¼¥¹¥³¡¼¥É¤È FreeBSD ÍѤΥѥåÁ¥»¥Ã¥È¤ò
               ¼êÆ°¤Ç¼èÆÀ¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤Î¤âƱ¤¸Íýͳ¤Ç¤¹¡£</p>
 
             <p>²¿¤«¤¦¤Þ¤¯¤¤¤«¤Ê¤¤¤³¤È¤¬¤¢¤Ã¤¿¤é
               <a href="../../doc/ja_JP.eucJP/books/handbook/ports.html">FreeBSD Handbook ¤Î
                 &quot;¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¥¤¥ó¥¹¥È¡¼¥ë&quot; ¤Î¾Ï</a> ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£</p>
           </td>
         </tr>
     </table>
   </body>
 </html>
diff --git a/ja_JP.eucJP/htdocs/ports/references.xml b/ja_JP.eucJP/htdocs/ports/references.xml
index 4de5e7d9dd..f02b7ddd96 100644
--- a/ja_JP.eucJP/htdocs/ports/references.xml
+++ b/ja_JP.eucJP/htdocs/ports/references.xml
@@ -1,97 +1,97 @@
 <?xml version="1.0" encoding="euc-jp"?>
 <!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
 "http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [
 <!ENTITY title 'FreeBSD Ports -- ¤½¤Î¾¤Î¾ðÊó'>
 <!ENTITY % ports.ent SYSTEM "ports.ent">
 %ports.ent;
 <!ENTITY email 'ports'>
 %statistics.ent;
 ]>
 <!-- The FreeBSD Japanese Documentation Project -->
-<!-- Original revision: 1.5 -->
+<!-- Original revision: r42153 -->
 
 <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.ports">
 
 &searchform;
 
 <hr/>
 
 <p>ports ¤ä packages ¤Ë¤Ä¤¤¤Æ¤â¤¦¾¯¤·¾Ü¤·¤¯ÃΤꤿ¤¤¾ì¹ç¤Ë¤Ï¡¢
   <a href="&enbase;/doc/ja_JP.eucJP/books/handbook/index.html">
   FreeBSD ¥Ï¥ó¥É¥Ö¥Ã¥¯</a> ¤Î
   <a href="&enbase;/doc/ja_JP.eucJP/books/handbook/ports.html">
   ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¥¤¥ó¥¹¥È¡¼¥ë - packages ¤È ports</a> ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
 </p>
 
 <p>¿·¤·¤¤ ports ¤òºî¤Ã¤¿¤ê ports ¤ò´ÉÍý¤¹¤ë¤¿¤á¤Î°ì¼¡¾ðÊó¤Ë¤Ä¤¤¤Æ¤Ï¡¢
   <a href="&enbase;/doc/ja_JP.eucJP/books/porters-handbook/index.html">
   port ºîÀ®¼Ô¤Î¤¿¤á¤Î¥Ï¥ó¥É¥Ö¥Ã¥¯</a> ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
   <a href="&enbase;/doc/en_US.ISO8859-1/books/porters-handbook/keeping-up.html">
   Keeping Up</a> ¤Ë¤â¾ðÊ󤬤¢¤ê¤Þ¤¹¡£
   ²¼µ­¤Î¥È¥Ô¥Ã¥¯¤Î¾ÜºÙ¤ä¡¢¤â¤Ã¤ÈÄ´¤Ù¤ë¤¿¤á¤Î¾ðÊó¤â´Þ¤ó¤Ç¤¤¤Þ¤¹¡£
 </p>
 
 <p>°Ê²¼¤Ë¤âÍ­ÍѤʾðÊ󤬤¢¤ê¤Þ¤¹¡£</p>
 
 <ul>
   <li><a href="http://docs.FreeBSD.org/mail/current/freebsd-ports.html">
     FreeBSD ports ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</a> ¤Î¥¢¡¼¥«¥¤¥Ö¡£
   </li>
 
   <li><a href="&enbase;/doc/en_US.ISO8859-1/articles/contributing-ports/index.html">
     FreeBSD Ports Collection ¤Ø¤Î¹×¸¥</a>
   </li>
 
   <li>
     <a href="http://www.FreshPorts.org">FreshPorts.org</a> ¤Ï¡¢
     ¸Ä¡¹¤Î ports ¤Ë¤Ä¤¤¤Æ¡¢
     ¸½ºß¤Î¥Ð¡¼¥¸¥ç¥ó¡¢ºÇ¸å¤Î¥Á¥§¥Ã¥¯¥¤¥ó¡¢¤ª¤è¤Ó¡¢Â¾¤ÎÍ­ÍѤÊÅý·×¤Ê¤É¡¢
     ¾ÜºÙ¤Ê¾ðÊó¤òÆÀ¤ë¤¿¤á¤ÎÍ­ÍѤʥġ¼¥ë¤Ç¤¹¡£
     ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ò¹ØÆɤ·¤Æ¡¢¤ªµ¤¤ËÆþ¤ê¤Î ports ¤ÎºÇ¿·¤Î¾ðÊó¤òÆÀ¤Æ¤¯¤À¤µ¤¤¡£
   </li>
 
 <!--
   <li>
     <a href="&enbase;/ports/growth/status.png">¶Ã°ÛŪ¤Ê®Å٤Ǥ½¤Î¿ô¤òÁý¤·¤Æ¤­¤¿</a>
     Ports Collection ¤Î¥°¥é¥Õ¡£
   </li>
 -->
 
   <li>
     <a href="&enbase;/cgi/man.cgi?query=ftp"><tt>ftp</tt></a>,
     <a href="&enbase;/cgi/man.cgi?query=pkg_add"><tt>pkg_add</tt></a> ¤ª¤è¤Ó
     <a href="&enbase;/cgi/man.cgi?query=ports"><tt>ports</tt></a> ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¡£
   </li>
 
   <li>
     <a href="http://pointyhat.FreeBSD.org">ports ¤ª¤è¤Ó packages ¥Ó¥ë¥É¥¯¥é¥¹¥¿</a>¡£
   </li>
 
   <li>
     <a href="&enbase;/portmgr/">Ports Management Team</a> (portmgr) ¥Ú¡¼¥¸¡£
   </li>
 
   <li>
-    <a href="http://cvsweb.FreeBSD.org">
+    <a href="http://svnweb.FreeBSD.org">
     ¥½¡¼¥¹¥ê¥Ý¥¸¥È¥ê¤Î¥¦¥§¥Ö¥¤¥ó¥¿¥Õ¥§¡¼¥¹</a> ¤ò»È¤¤¡¢¥½¡¼¥¹¥ê¥Ý¥¸¥È¥ê¤ò±ÜÍ÷¤Ç¤­¤Þ¤¹¡£
     port ¥·¥¹¥Æ¥àÁ´ÂΤ˱ƶÁ¤¹¤ë¤è¤¦¤ÊÊѹ¹¤Ï¡¢
-    <a href="http://cvsweb.FreeBSD.org/ports/CHANGES">CHANGES</a>
+    <a href="http://svnweb.FreeBSD.org/ports/head/CHANGES?view=markup">CHANGES</a>
     ¥Õ¥¡¥¤¥ë¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
     ¤¢¤ëÆÃÄê¤Î ports ¤Ë±Æ¶Á¤¹¤ë¤è¤¦¤ÊÊѹ¹¤Ï¡¢
-    <a href="http://cvsweb.FreeBSD.org/ports/UPDATING">UPDATING</a>
+    <a href="http://svnweb.FreeBSD.org/ports/head/UPDATING?view=markup">UPDATING</a>
     ¥Õ¥¡¥¤¥ë¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
     ¤·¤«¤·¤Ê¤¬¤é¡¢¤¹¤Ù¤Æ¤ÎÅú¤¨¤Ï
-    <a href="http://cvsweb.FreeBSD.org/ports/Mk/bsd.port.mk">
+    <a href="http://svnweb.FreeBSD.org/ports/head/Mk/bsd.port.mk?view=markup">
     bsd.port.mk</a> ¤Î¥½¡¼¥¹¥³¡¼¥É¡¢
     ¤ª¤è¤Ó´ØÏ¢¥Õ¥¡¥¤¥ë¤òÆɤळ¤È¤Ç³Î¼Â¤ËÆÀ¤é¤ì¤ë¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£
   </li>
 </ul>
 
 </body>
 </html>
diff --git a/pl_PL.ISO8859-2/books/handbook/install/chapter.xml b/pl_PL.ISO8859-2/books/handbook/install/chapter.xml
index d3bac689a7..511862cb9c 100644
--- a/pl_PL.ISO8859-2/books/handbook/install/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/install/chapter.xml
@@ -1,5367 +1,5361 @@
 <?xml version="1.0" encoding="iso-8859-2"?>
 <!--
      The FreeBSD Polish Documentation Project
 
      $FreeBSD$
      Original revision: 1.338
 -->
 
 <chapter id="install">
   <chapterinfo>
     <authorgroup>
       <author>
         <firstname>Jim</firstname>
 	<surname>Mock</surname>
         <contrib>Rozdzia³ przebudowa³ i czê¶ciowo napisa³
           od nowa </contrib>
       </author>
     </authorgroup>
 
     <authorgroup>
       <author>
 	<firstname>Randy</firstname>
 	<surname>Pratt</surname>
         <contrib>Omówienie sysinstall, zrzuty ekranów i inne
           fragmenty przygotowa³ </contrib>
       </author>
     </authorgroup>
     <!-- January 2000 -->
     <authorgroup>
       <author>
         <firstname>Micha³</firstname>
         <surname>Wojciechowski</surname>
         <contrib>T³umaczy³ </contrib>
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>Instalacja FreeBSD</title>
 
   <sect1 id="install-synopsis">
     <title>Streszczenie</title>
 
     <indexterm><primary>instalacja</primary></indexterm>
 
     <para>Wraz z FreeBSD rozpowszechniany jest prosty w u¿yciu program
       instalacyjny, dzia³aj±cy w trybie tekstowym, o nazwie
       <application>sysinstall</application>.  Jest on domy¶lnym
       programem instalacyjnym FreeBSD, jednak¿e dystrybutorzy
       systemu mog± zast±piæ go w³asnym odpowiednikiem.  W niniejszym
       rozdziale zawarto opis instalacji FreeBSD przy pomocy
       <application>sysinstall</application>.</para>
 
     <para>Po przeczytaniu rozdzia³u bêdziemy wiedzieæ:</para>
 
     <itemizedlist>
       <listitem>
         <para>W jaki sposób tworzy siê dyskietki instalacyjne FreeBSD.</para>
       </listitem>
 
       <listitem>
         <para>Jak FreeBSD odwo³uje siê do dysku i jak go dzieli.</para>
       </listitem>
 
       <listitem>
         <para>Jak uruchamia siê <application>sysinstall</application>.</para>
       </listitem>
 
       <listitem>
         <para>Jakie pytania zadaje <application>sysinstall</application>,
           o co w nich chodzi i jak na nie odpowiedzieæ.</para>
       </listitem>
     </itemizedlist>
 
     <para>Przed przeczytaniem rozdzia³u powinni¶my:</para>
 
     <itemizedlist>
       <listitem>
         <para>Zapoznaæ siê z list± obs³ugiwanego sprzêtu do³±czon± do
           instalowanej wersji FreeBSD, by upewniæ siê, ¿e posiadany sprzêt
           bêdzie dzia³aæ.</para>
       </listitem>
     </itemizedlist>
 
     <note>
       <para>Opis instalacji dotyczy generalnie komputerów opartych na
         architekturze &i386; (<quote>zgodny z PC</quote>). W stosownych
         przypadkach podawane bêd± informacje odnosz±ce siê do innych platform
         (na przyk³ad Alpha). Pomimo starañ o utrzymanie niniejszego opisu aktualnym,
         mo¿liwe jest zaistnienie drobnych ró¿nic pomiêdzy instalatorem a zawarto¶ci±
         tego rozdzia³u. Zaleca siê, aby traktowaæ niniejszy teksty jako ogólny przewodnik,
         ni¿ raczej dos³owny podrêcznik instalacji.</para>
     </note>
 
   </sect1>
 
   <sect1 id="install-pre">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Cezary</firstname>
           <surname>Morga</surname>
           <contrib>Przek³ad uzupe³ni³ </contrib>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>Czynno¶ci wstêpne</title>
 
     <sect2 id="install-inventory">
       <title>Rozpoznanie komponentów komputera</title>
 
       <para>Przed instalacj± FreeBSD powinni¶my zapoznaæ siê z komponentami
         naszego komputera. W czasie instalacji FreeBSD poka¿e listê urz±dzeñ
         (dyski, karty sieciowe, napêdy CD-ROM, itd.) wraz z informacjami o
         producentach i numerach modeli. FreeBSD postara siê tak¿e ustaliæ
         prawid³ow± konfiguracjê ka¿dego z nich, m.in. ustawienia przerwañ
         IRQ i portów we/wy. Ze wzglêdu na <quote>kaprysy</quote> pecetowego sprzêtu mo¿e
         siê okazaæ, ¿e konfiguracja wykryta przez FreeBSD nie jest w pe³ni
         prawid³owa i trzeba bêdzie samodzielnie j± poprawiæ.</para>
 
       <para>Je¿eli na komputerze jest ju¿ zainstalowany inny system operacyjny,
         na przyk³ad &windows; lub Linux, warto jest skorzystaæ z dostêpnych
         w nim narzêdzi do sprawdzenia bie¿±cej konfiguracji sprzêtowej.
         Kiedy zupe³nie nie wiadomo jak skonfigurowana powinna byæ dana karta,
         wymagane informacje mog± znajdowaæ siê bezpo¶rednio na niej samej.
         Czêsto spotykane numery przerwañ IRQ to 3, 5 i 7, a adresy portów
         we/wy s± zwykle zapisywane w postaci liczb szesnastkowych,
         na przyk³ad 0x330.</para>
 
       <para>Zalecamy by zebrane informacje wydrukowaæ lub zapisaæ na
         kartce przed rozpoczêciem instalacji FreeBSD.  Mo¿na je zestawiæ
         w postaci tabeli, np.:</para>
 
       <table pgwide="1" frame="none">
         <title>Przyk³adowa lista urz±dzeñ</title>
 
 	<tgroup cols="4">
           <colspec colwidth="2*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="4*"/>
 	  <thead>
 	    <row>
               <entry>Nazwa urz±dzenia</entry>
 
 	      <entry>IRQ</entry>
 
               <entry>Port(y) we/wy</entry>
 
               <entry>Uwagi</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
               <entry>Pierwszy dysk twardy</entry>
 
 	      <entry>brak</entry>
 
 	      <entry>brak</entry>
 
               <entry>40&nbsp;GB, firmy Seagate, IDE 1 master</entry>
 	    </row>
 
 	    <row>
 	      <entry>CDROM</entry>
 
 	      <entry>brak</entry>
 
 	      <entry>brak</entry>
 
               <entry>IDE 1 slave</entry>
 	    </row>
 
 	    <row>
               <entry>Drugi dysk twardy</entry>
 
 	      <entry>brak</entry>
 
 	      <entry>brak</entry>
 
               <entry>20&nbsp;GB, firmy IBM, IDE 2 master</entry>
 	    </row>
 
 	    <row>
               <entry>Kontroler IDE</entry>
 
 	      <entry>14</entry>
 
 	      <entry>0x1f0</entry>
 
 	      <entry></entry>
 	    </row>
 
 	    <row>
               <entry>Karta sieciowa</entry>
 
 	      <entry>brak</entry>
 
 	      <entry>brak</entry>
 
 	      <entry>&intel; 10/100</entry>
 	    </row>
 
 	    <row>
 	      <entry>Modem</entry>
 
 	      <entry>brak</entry>
 
 	      <entry>brak</entry>
 
 	      <entry>&tm.3com; 56K faxmodem na COM1</entry>
 	    </row>
 
 	    <row>
 	      <entry>&hellip;</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
     </sect2>
 
     <sect2>
       <title>Przygotowanie kopii danych</title>
 
       <para>Je¶li komputer, na którym bêdzie przeprowadzana instalacja
         zawiera cenne dane, powinni¶my koniecznie przygotowaæ ich kopiê
         zapasow±, oraz sprawdziæ stan tych¿e kopii przed instalacj± FreeBSD.
         Podczas instalacji kilkakrotnie pojawi siê pro¶ba o potwierdzenie
         przed zapisaniem czegokolwiek na dysku, jednak gdy ju¿ siê to
         rozpocznie, nie bêdzie mo¿liwo¶ci odwrotu.</para>
     </sect2>
 
     <sect2 id="install-where">
       <title>Wybór miejsca dla FreeBSD</title>
 
       <para>Je¿eli masz zamiar przeznaczyæ ca³y dysk na FreeBSD, to omawiane
         poni¿ej zagadnienia nie bêd± ciê dotyczyæ &mdash; mo¿esz pomin±æ
         tê czê¶æ.</para>
 
       <para>W przypadku, gdy zamierzamy zainstalowaæ FreeBSD obok
         innych systemów operacyjnych, warto zapoznaæ siê z podstawowymi
         informacjami o sposobie przechowywania danych na dysku.</para>
 
       <sect3 id="install-where-i386">
         <title>Uk³ad dysku w systemach &i386;</title>
 
       <para>Dysk komputera typu PC mo¿na podzieliæ na oddzielne porcje,
         zwane <firstterm>partycjami</firstterm>. Komputery PC potrafi±
         obs³u¿yæ maksymalnie cztery partycje na jednym dysku. Partycje
         te nazywane s± <firstterm>partycjami podstawowymi</firstterm>.
         W celu ominiêcia tego ograniczenia i umo¿liwienia stworzenia
         wiêkszej liczby partycji, wymy¶lono nowy typ partycji -
         <firstterm>partycje rozszerzone</firstterm>. Na dysku mo¿e
         znajdowaæ siê tylko jedna taka partycja. Natomiast wewn±trz
         niej mo¿na utworzyæ specjalne partycje, zwane
         <firstterm>partycjami logicznymi</firstterm>.</para>
 
       <para>Wszystkie partycje posiadaj± w³asny <firstterm>identyfikator
           partycji</firstterm>, tj. numer okre¶laj±cy typ przechowywanych
         na niej danych. Partycje FreeBSD oznaczone s± identyfikatorem
         <literal>165</literal>.</para>
 
       <para>Ka¿dy ze stosowanych systemów operacyjnych identyfikuje partycje
         w okre¶lony sposób. Dla przyk³adu, DOS i jego nastêpcy, w tym &windows;,
         przypisuj± ka¿dej partycji podstawowej i logicznej <firstterm>literê
           dysku</firstterm>, zaczynaj±c od <devicename>C:</devicename>.</para>
 
       <para>FreeBSD musi byæ zainstalowane na partycji podstawowej.
         Wszystkie w³asne dane, w tym pliki tworzone przez u¿ytkowników,
         mo¿e przechowywaæ na jednej partycji. Jednak¿e, je¶li masz do
         dyspozycji kilka dysków, mo¿esz utworzyæ partycjê FreeBSD na ka¿dym
         z nich b±d¼ jedynie na wybranych. Tym nie mniej na potrzeb
         instalacji wymagane jest posiadanie jednej partycji. Mo¿e to byæ
         ¶wie¿o utworzona, pusta partycja, lub te¿ partycja zawieraj±ca dane,
         które nie s± ju¿ potrzebne.</para>
 
       <para>W przypadku, gdy wszystkie dostêpne partycje na dysku s±
         ju¿ wykorzystywane, bêdziesz musia³ zwolniæ jedn± z nich, korzystaj±c
         z narzêdzi dostêpnych w wykorzystywanym systemie operacyjnym (np.
         <command>fdisk</command> w DOS lub &windows;).</para>
 
       <para>Je¶li dysponujesz woln± partycj±, mo¿esz j± wykorzystaæ.
         Mo¿e siê jednak okazaæ, ¿e zajdzie potrzeba zmniejszenia rozmiarów
         niektórych z pozosta³ych partycji.</para>
 
       <para>Minimalna instalacja FreeBSD zajmuje jedynie 100&nbsp;MB miejsca
         na dysku. Jest to jednak¿e <emphasis>bardzo</emphasis> minimalna
         instalacja, praktycznie nie pozostawiaj±ca miejsca na pliki u¿ytkowników.
         Zdecydowanie bardziej realnym minimum jest 250&nbsp;MB, o ile nie
         planujemy wykorzystania ¶rodowiska graficznego, b±d¼ co najmniej
         350&nbsp;MB z graficznym interfejsem. Instalowanie wielu dodatkowych
         programów wymaga wiêcej wolnego miejsca na dysku.</para>
 
       <para>W celu przygotowania miejsca dla FreeBSD mo¿na wykorzystaæ
         narzêdzia komercyjne pokroju <application>&partitionmagic;</application>
         b±d¼ darmowe jak <application>GParted</application>.
         Dwa darmowe programy s³u¿±ce do tego samego celu, tj.
         <application>FIPS</application> i <application>PResizer</application>,
         dostêpne s± na p³ycie CD w katalogu <filename>tools</filename>.
         W tym samym katalogu znajduje siê równie¿ ich dokumentacja. Zarówno
         <application>FIPS</application>, <application>PResizer</application>
         jak i <application>&partitionmagic;</application> potrafi± rozszerzaæ
         partycje typu <acronym>FAT16</acronym> i <acronym>FAT32</acronym>
         &mdash; wykorzystywane w &ms-dos; a¿ po &windows; ME. System plików
         <acronym>NTFS</acronym> potrafi± obs³ugiwaæ
         <application>&partitionmagic;</application> i
         <application>GParted</application>.</para>
 
       <warning>
         <para> Niew³a¶ciwe korzystanie z tych narzêdzi mo¿e doprowadziæ
           do utraty danych. Przed ich zastosowaniem nale¿y siê upewniæ,
           ¿e przygotowali¶my aktualne kopie zapasowe.</para>
       </warning>
 
       <example>
         <title>Wykorzystanie niezmienionej istniej±cej partycji</title>
 
         <para>Przyjmijmy, ¿e mamy do dyspozycji komputer wyposa¿ony w
           dysk o pojemno¶ci 4&nbsp;GB, z zainstalowanym systemem &windows;.
           Dysk jest podzielony na dwie czê¶ci oznaczone literami
           <devicename>C:</devicename> i <devicename>D:</devicename>,
           o rozmiarze 2&nbsp;GB ka¿da. Na <devicename>C:</devicename>
           mamy 1&nbsp;GB danych, a na <devicename>D:</devicename> 0,5&nbsp;GB
           danych.</para>
 
         <para>Mamy wiêc dysk o dwóch partycjach, z których ka¿da
           oznaczona jest liter± dysku. Mo¿emy skopiowaæ dane z
           <devicename>D:</devicename> na <devicename>C:</devicename>,
           dziêki czemu druga partycja stanie siê wolna i bêdzie mo¿na
           zainstalowaæ na niej FreeBSD.</para>
       </example>
 
       <example>
         <title>Zmniejszenie istniej±cej partycji</title>
 
         <para>Przyjmijmy tym razem, ¿e na dysku o pojemno¶ci 4&nbsp;GB
           zainstalowany jest system &windows; na jednej du¿ej partycji.
           Partycja dostêpna jest jako dysk <devicename>C:</devicename>
           o rozmiarze 4&nbsp;GB. Mamy na nim 1,5&nbsp;GB danych
           i chcieliby¶my udostêpniæ dla FreeBSD 2&nbsp;GB.</para>
 
         <para>Mo¿emy wybraæ jedno z poni¿szych rozwi±zañ:</para>
 
 	<orderedlist>
 	  <listitem>
             <para>Przygotowaæ kopiê danych, nastêpnie na nowo zainstalowaæ
               &windows;, tworz±c podczas instalacji partycjê o rozmiarze
               2&nbsp;GB.</para>
 	  </listitem>
 
 	  <listitem>
             <para>Skorzystaæ z jednego ze wspomnianych wcze¶niej narzêdzi,
               np. <application>&partitionmagic;</application>, w celu
               zmniejszenia rozmiaru partycji &windows;.</para>
 	  </listitem>
 	</orderedlist>
       </example>
 
       </sect3>
 
       <sect3>
         <title>Uk³ad dysku Alpha</title>
 
 	<indexterm><primary>Alpha</primary></indexterm>
 
         <para>W przypadku architektury Alpha na FreeBSD
           trzeba bêdzie przeznaczyæ ca³y dysk. Nie ma obecnie
           mo¿liwo¶ci wspólnego korzystania z dysku przez kilka
           systemów operacyjnych. W zale¿no¶ci od konkretnego
           modelu komputera Alpha, mo¿emy wykorzystaæ dysk SCSI
           lub IDE, o ile komputer umo¿liwia za³adowanie z niego
           systemu operacyjnego.</para>
 
         <para>Zgodnie z konwencj± stosowan± w podrêcznikach
           Digital / Compaq wszystkie polecenia SRM pisane s± wielkimi
           literami. SRM nie rozró¿nia ma³ych i du¿ych liter.</para>
 
         <para>By wy¶wietliæ nazwy i rodzaje zainstalowanych
           w komputerze dysków, pos³ugujemy siê poleceniem
           <literal>SHOW DEVICE</literal> w konsoli SRM:</para>
 
 	<screen>&gt;&gt;&gt;<userinput>SHOW DEVICE</userinput>
 dka0.0.0.4.0               DKA0           TOSHIBA CD-ROM XM-57  3476
 dkc0.0.0.1009.0            DKC0                       RZ1BB-BS  0658
 dkc100.1.0.1009.0          DKC100             SEAGATE ST34501W  0015
 dva0.0.0.0.1               DVA0
 ewa0.0.0.3.0               EWA0              00-00-F8-75-6D-01
 pkc0.7.0.1009.0            PKC0                  SCSI Bus ID 7  5.27
 pqa0.0.0.4.0               PQA0                       PCI EIDE
 pqb0.0.1.4.0               PQB0                       PCI EIDE</screen>
 
 	<para>Powy¿szy przyk³ad pochodzi z komputera Digital Personal
           Workstation 433au i pokazuje trzy dyski. Pierwszym z nich
           jest CDROM opisany nazw± <devicename>DKA0</devicename>,
           natomiast dwa pozosta³e to twarde dyski o nazwach
           <devicename>DKC0</devicename>
           i <devicename>DKC100</devicename>.</para>
 
         <para>Dyski o nazwach typu <devicename>DKx</devicename> s± dyskami
           SCSI. Dla przyk³adu <devicename>DKA100</devicename> oznacza dysk
           SCSI o identyfikatorze 1 na pierwszej szynie SCSI (A), natomiast
           <devicename>DKC300</devicename> oznacza dysk o identyfikatorze 3
           na trzeciej szynie SCSI (C). Nazwa <devicename>
 	  PKx</devicename> oznacza kontroler SCSI. Jak pokazuje przyk³ad
           z <literal>SHOW DEVICE</literal>, napêdy CDROM SCSI traktowane
           s± tak samo jak dyski twarde SCSI.</para>
 
         <para>Nazwy dysków IDE maj± postaæ <devicename>DQx</devicename>,
           a nazwa <devicename>PQx</devicename> oznacza kontroler IDE.</para>
 
       </sect3>
     </sect2>
 
     <sect2>
       <title>Zbieranie informacji o konfiguracji sieci</title>
 
       <para>Je¶li podczas instalacji bêdziemy korzystaæ z po³±czenia
         z sieci± (np. FreeBSD instalowane bêdzie z serwera FTP lub
         serwera NFS), bêdziemy musieli znaæ konfiguracjê sieci.
         W trakcie instalacji pojawi siê pro¶ba o wpisanie tej konfiguracji,
         by umo¿liwiæ FreeBSD po³±czenie siê z sieci± i kontynuowanie
         instalacji.</para>
 
       <sect3>
         <title>Po³±czenie z sieci± Ethernet lub przez modem kablowy/DSL</title>
 
         <para>W przypadku komputera pod³±czonego do sieci Ethernet
           lub po³±czonego z Internetem przez modem kablowy lub DSL,
           potrzebne bêd± nastêpuj±ce informacje:</para>
 
 	<orderedlist>
 	  <listitem>
 	    <para>Adres IP</para>
 	  </listitem>
 
 	  <listitem>
             <para>Adres IP domy¶nej bramy</para>
 	  </listitem>
 
 	  <listitem>
             <para>Nazwa stacji</para>
 	  </listitem>
 
 	  <listitem>
             <para>Adresy IP serwerów DNS</para>
 	  </listitem>
 
 	  <listitem>
             <para>Maska podsieci</para>
 	  </listitem>
 	</orderedlist>
 
         <para>Informacje te mo¿emy uzyskaæ od administratora systemu
           lub dostawcy us³ug sieciowych. Mo¿e siê okazaæ, ¿e konfiguracja
           odbywa siê automatycznie, przy u¿yciu <firstterm>DHCP</firstterm>.
           Je¶li tak jest, nale¿y o tym fakcie pamiêtaæ.</para>
       </sect3>
 
       <sect3>
         <title>Po³±czenie przez modem</title>
 
         <para>Instalacja FreeBSD przez Internet mo¿liwa jest tak¿e
           w przypadku po³±czenia modemowego, jednak¿e bêdzie to
           trwa³o bardzo d³ugo.</para>
 
         <para>Niezbêdne informacje:</para>
 
 	<orderedlist>
 	  <listitem>
             <para>Numer telefonu do dostawcy us³ug internetowych</para>
 	  </listitem>
 
 	  <listitem>
             <para>Numer portu COM, do którego pod³±czony jest modem</para>
 	  </listitem>
 
 	  <listitem>
             <para>Nazwa u¿ytkownika i has³o konta u dostawcy us³ug</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
     </sect2>
     <sect2>
       <title>Sprawdzenie erraty FreeBSD</title>
 
       <para>W pracy nad FreeBSD podejmowane s± wszelkie starania, aby
         ka¿de wydanie FreeBSD by³o jak najbardziej niezawodne, jednak¿e
         od czasu do czasu zdarzaj± siê b³êdy. W pewnych bardzo rzadkich
         przypadkach mog± mieæ one wp³yw na proces instalacji systemu.
         B³êdy te po wykryciu i naprawieniu s± opisywane w erracie zamieszczonej
         na stronie <ulink
           url="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">FreeBSD
           Errata</ulink> (ang.). Przed instalacj± warto jest sprawdziæ, czy w erracie
         nie wspomniano o problemach, które mog± zak³óciæ instalacjê.</para>
 
       <para>Informacje o wszystkich wydaniach systemu, jak równie¿ erraty
         do ka¿dego z nich, znale¼æ mo¿na na
         <ulink url="&url.base;/index.html">stronie WWW
           FreeBSD</ulink> w czê¶ci po¶wiêconej <ulink
 	url="&url.base;/releases/index.html">wydaniom</ulink>.</para>
     </sect2>
 
     <sect2>
       <title>Pozyskanie plików instalacyjnych FreeBSD</title>
 
       <para>Pliki potrzebne do rozpoczêcia instalacji systemu
         mog± pochodziæ z jednego z wymienionych poni¿ej
         ¼róde³:</para>
 
       <itemizedlist>
         <title>No¶niki lokalne</title>
 
 	<listitem>
           <para>P³yta CDROM lub DVD</para>
 	</listitem>
 
 	<listitem>
           <para>Partycja DOS-owa na tym samym komputerze</para>
 	</listitem>
 
 	<listitem>
           <para>Pamiêæ ta¶mowa QIC lub SCSI</para>
 	</listitem>
 
 	<listitem>
           <para>Dyskietki</para>
 	</listitem>
       </itemizedlist>
 
       <itemizedlist>
         <title>Sieæ</title>
 
 	<listitem>
           <para>Serwer FTP, tak¿e przez firewall lub proxy
             HTTP, zale¿nie od potrzeb</para>
 	</listitem>
 
 	<listitem>
           <para>Serwer NFS</para>
 	</listitem>
 
 	<listitem>
           <para>Dedykowane po³±czenie równoleg³e lub szeregowe</para>
 	</listitem>
       </itemizedlist>
 
       <para>Posiadaj±c FreeBSD na CD lub DVD, mamy ju¿ wszystko,
         co potrzeba, mo¿emy zatem przej¶æ do nastêpnej czê¶ci
 	(<xref linkend="install-floppies"/>).</para>
 
       <para>Je¶li nie mamy plików instalacyjnych FreeBSD,
         <xref linkend="install-diff-media"/>
         zawiera opis instalacji FreeBSD z dowolnego z wymienionych
         wcze¶niej ¼róde³. Nastêpnie powróæmy do
 	<xref linkend="install-floppies"/>.</para>
     </sect2>
 
     <sect2 id="install-floppies">
       <title>Przygotowanie dyskietek do instalacji</title>
 
       <para>Instalacja FreeBSD rozpoczyna siê uruchomieniem programu
         instalacyjnego podczas startu komputera &mdash; nie jest to
         program, który mo¿na uruchomiæ w innym systemie operacyjnym.
         Zwykle przy uruchamianiu komputera ³adowany jest system
         zainstalowany na dysku twardym, jednak mo¿na tak¿e uruchomiæ
         system z dyskietki <quote>startowej</quote>. Do tego celu
         mo¿e tak¿e pos³u¿yæ CDROM, je¶li komputer daje tak± mo¿liwo¶æ.</para>
 
       <tip>
         <para>Je¶li posiadamy FreeBSD na p³ytach CDROM lub DVD
           (kupionych lub przygotowanych samodzielnie), a nasz komputer
           pozwala na uruchomienie z p³yty (zwykle dziêki ustawieniu
           opcji BIOS-u zwanej <quote>Boot Order</quote> lub podobnej),
           mo¿emy nie czytaæ niniejszej czê¶ci. P³yty CDROM i DVD
           zawieraj±ce FreeBSD mog± byæ u¿yte jako dyski startowe bez
           dodatkowego przygotowania.</para>
       </tip>
 
       <para>By utworzyæ zestaw dyskietek startowych, nale¿y:</para>
 
       <procedure>
 	<step>
           <title>Zdobyæ obrazy dyskietek startowych</title>
 
           <para>Dyskietki startowe znale¼æ mo¿na w¶ród plików
             instalacyjnych w katalogu <filename>floppies/</filename>
             b±d¼ pobraæ z serwera
             <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>&lt;arch&gt;</replaceable>/<replaceable>&lt;version&gt;</replaceable>-RELEASE/floppies/</literal>
             zamieniaj±c odpowiednio <replaceable>&lt;arch&gt;</replaceable>
             i <replaceable>&lt;wersja&gt;</replaceable>
             w³a¶ciw± architektur± naszego sprzêtu i wybran± wersj±
             FreeBSD. Przyk³adowo, obrazy dyskietek dla
             &os;&nbsp;&rel.current;-RELEASE na architekturê &i386; dostêpne
             s± pod adresem <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/"></ulink>.</para>
 
           <para>Obrazy dyskietek maj± rozszerzenie <filename>.flp</filename>.
             Katalog <filename>floppies/</filename> zawiera kilka ró¿nych obrazów,
             a to, które z nich bêd± potrzebne, zale¿y od wersji FreeBSD, która
             bêdzie instalowana, a czasem równie¿ od sprzêtu na którym system ma
             byæ zainstalowany. Z regu³y potrzebne bêd± trzy dyskietki
             <filename>boot.flp</filename>,
             <filename>kern1.flp</filename> i
 	    <filename>kern2.flp</filename>. Warto jednak dla pewno¶ci
             przeczytaæ znajduj±cy siê w tym samym katalogu plik
             <filename>README.TXT</filename>.</para>
 
           <note><para>Systemy ga³êzi 5.X starsze od &os;&nbsp;5.3 mog± wymagaæ
               dodatkowych sterowników urz±dzeñ. Znale¼æ je mo¿na w obrazie
               dyskietki <filename>drivers.flp</filename>.</para></note>
 
 	  <important>
             <para>Pobieraj±c pliki przez FTP nale¿y koniecznie u¿ywaæ
               <emphasis>trybu binarnego</emphasis>. Wiadomo jest, ¿e w
               niektórych przegl±darkach stosowany jest tryb <emphasis>tekstowy</emphasis>
               (zwany te¿ <emphasis>ASCII</emphasis>), przez co dyskietki startowe
               mog± siê okazaæ niezdatne do u¿ycia.</para>
 	  </important>
 	</step>
 
 	<step>
           <title>Przygotowaæ dyskietki startowe</title>
 
           <para>Dla ka¿dego pliku z obrazem przygotowujemy jedn± dyskietkê.
             Dyskietki nie mog± byæ w jakikolwiek sposób uszkodzone.
             Najprostszym sposobem samodzielnego sprawdzenia, czy dyskietka
             nie jest wadliwa, jest jej sformatowanie. Nie powinni¶my ufaæ
             dyskietkom formatowanym fabrycznie. Narzêdzie formatuj±ce
             dostêpne w systemie &windows; nie poinformuje o istnieniu
             uszkodzonych bloków, po prostu oznaczy je jako
             <quote>uszkodzone</quote> i zignoruje. Zaleca siê u¿ywanie
             fabrycznie nowych dyskietek.</para>
 
 	  <important>
             <para>Gdy podczas instalacji FreeBSD program instalacyjny
               wska¿e b³±d, zastygnie lub zachowa siê w dziwny sposób,
               jednymi z pierwszych podejrzanych powinny byæ dyskietki.
               Trzeba wówczas nagraæ pliki obrazów na inne dyskietki
               i spróbowaæ ponownie.</para>
 	  </important>
 	</step>
 
 	<step>
           <title>Nagraæ pliki obrazów na dyskietki</title>
 
           <para>Pliki <filename>.flp</filename> nie s± zwyczajnymi
             plikami, które mo¿na nagraæ na dyskietkê. S± natomiast
             obrazami ca³kowitej zawarto¶ci dyskietek. Oznacza to,
             ¿e <emphasis>nie mo¿na</emphasis> zapisaæ tych plików
             po prostu kopiuj±c z jednego dysku na drugi. Skorzystamy
             ze specjalnego oprogramowania, by bezpo¶rednio zapisaæ
             obrazy na dyskietkach.</para>
 
 	  <indexterm><primary>DOS</primary></indexterm>
           <para>Je¶li dyskietki nagrywamy na komputerze z
             &ms-dos;/&windows;, to mo¿emy skorzystaæ z do³±czonego
             do FreeBSD narzêdzia <command>fdimage</command>.</para>
 
           <para>W przypadku, gdy wykorzystujemy obrazy dyskietek z
             p³yty CDROM dostêpnego jako dysk <devicename>E:</devicename>,
             pos³u¿ymy siê poleceniem:</para>
 
 	  <screen><prompt>E:\&gt;</prompt> <userinput>tools\fdimage floppies\kern.flp A:</userinput></screen>
 
           <para>Powtarzamy je dla ka¿dego z plików <filename>.flp</filename>,
             za ka¿dym razem zmieniaj±c dyskietkê. Najlepiej jest te¿ napisaæ
             na dyskietce nazwê skopiowanego na ni± pliku. Powy¿sze polecenie
             mo¿e potrzebowaæ pewnych modyfikacji, w zale¿no¶ci od miejsca,
             w którym znajduj± siê pliki <filename>.flp</filename>. Je¿eli nie
             dysponujemy p³yt± CD, mo¿emy pobraæ <command>fdimage</command>
             z <ulink
 	    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">katalogu
               <filename class="directory">tools</filename></ulink>
             na serwerze FTP FreeBSD.</para>
 
           <para>Je¿eli natomiast dyskietki nagrywamy w systemie uniksowym
             (na przyk³ad w innym FreeBSD), do zapisania plików obrazów
             na dyskietkach mo¿emy wykorzystaæ polecenie &man.dd.1;.
             We FreeBSD wpisaliby¶my:</para>
 
 	  <screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput></screen>
 
           <para>W systemie FreeBSD <filename>/dev/fd0</filename> odpowiada
             pierwszej stacji dyskietek (napêdowi <devicename>A:</devicename>).
             <filename>/dev/fd1</filename> odpowiada³oby <devicename>B:</devicename>
             i tak dalej. W innych odmianach systemów &unix; mog± byæ stosowane inne nazwy
             stacji dyskietek, konieczne mo¿e wiêc byæ zapoznanie siê z dokumentacj±
             danego systemu.</para>
 	</step>
       </procedure>
 
       <para>W tej chwili jeste¶my ju¿ przygotowani do instalacji FreeBSD.</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-start">
     <title>Rozpoczêcie instalacji</title>
 
     <important>
       <para> Z za³o¿enia, podczas instalacji dane na dysku
         (lub dyskach) nie ulegn± ¿adnym zmianom przed pojawieniem
         siê nastêpuj±cego komunikatu:</para>
 
       <literallayout class="monospaced">Last Chance: Are you SURE you want continue the installation?
 
 If you're running this on a disk with data you wish to save then WE
 STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding!
 
 We can take no responsibility for lost disk contents!</literallayout>
 
       <para>Instalacjê mo¿na przerwaæ w dowolnej chwili przed powy¿szym
         ostrze¿eniem, maj±c pewno¶æ, ¿e dane na dysku pozostaj± nietkniête.
         Je¶li bêdziemy siê obawiaæ, ¿e co¶ niew³a¶ciwie skonfigurowali¶my,
         mo¿emy po prostu wy³±czyæ komputer i nic z³ego siê nie stanie.</para>
     </important>
 
     <sect2 id="install-starting">
       <title>Uruchomienie komputera</title>
 
       <sect3 id="install-starting-i386">
         <title>Uruchomienie &i386;</title>
 
       <procedure>
 	<step>
           <para>Na pocz±tku komputer powinien byæ wy³±czony.</para>
 	</step>
 
 	<step>
           <para>W³±czamy komputer. Po chwili powinna pojawiæ siê mo¿liwo¶æ
             przej¶cia do menu systemowego, lub BIOS-u, najczê¶ciej poprzez
             naci¶niêcie klawisza <keycap>F2</keycap>, <keycap>F10</keycap>,
             <keycap>Del</keycap> b±d¼ <keycombo action="simul">
               <keycap>Alt</keycap>
               <keycap>S</keycap>
 	    </keycombo>. Wciskamy odpowiedni klawisz zgodnie z informacj±
             na ekranie. Niekiedy komputer podczas uruchamiania pokazuje jaki¶
             obrazek. Zwykle wciskaj±c <keycap>Esc</keycap> mo¿emy pozbyæ siê
             obrazka, aby mieæ mo¿liwo¶æ przeczytania komunikatów.</para>
 	</step>
 
 	<step>
           <para>W¶ród opcji odnajdujemy tê, która decyduje o kolejno¶ci
             ³adowania systemu z poszczególnych urz±dzeñ. Zwykle ma ona postaæ
             listy urz±dzeñ, takich jak <literal>Floppy</literal>, <literal>CDROM</literal>,
 	    <literal>First Hard Disk</literal>, itd.</para>
 
           <para>Je¿eli wcze¶niej przygotowali¶my dyskietki startowe,
             wybieramy stacjê dyskietek. Je¶li natomiast korzystamy
             z p³yty CD, wybieramy w³a¶nie CDROM. W±tpliwo¶ci mo¿emy
             rozstrzygn±æ zagl±daj±c do instrukcji do³±czonej do
             komputera i jego p³yty g³ównej.</para>
 
           <para>Wprowadzone zmiany musz± byæ zapisane przed
             opuszczeniem menu systemowego. Komputer powinien
             ponownie siê uruchomiæ.</para>
 	</step>
 
 	<step>
           <para>Je¿eli korzystamy z dyskietek startowych, o których
             traktuje <xref linkend="install-floppies"/>, to jedna z nich
               bêdzie pierwsz± dyskietk± startow±, najprawdopodobniej
               bêdzie to dyskietka zawieraj±ca <filename>kern.flp</filename>.
               J± w³a¶nie wk³adamy do stacji.</para>
 
             <para>W przypadku korzystania z p³yty CD wystarczy
               po prostu w³±czyæ komputer i w³o¿yæ p³ytê do napêdu.</para>
 
             <para>Je¿eli komputer uruchomi siê jak zwykle i za³aduje
               ju¿ zainstalowany system operacyjny, mo¿e to oznaczaæ, ¿e:</para>
 
 	  <orderedlist>
 	    <listitem>
               <para>Dyskietka lub p³yta zosta³y w³o¿one za pó¼no.
                 Powinni¶my spróbowaæ uruchomiæ komputer bez wyjmowania
                 dyskietki b±d¼ p³yty.</para>
 	    </listitem>
 
 	    <listitem>
               <para>Zmiany w ustawieniach BIOS-u nie zadzia³a³y prawid³owo.
                 Spróbujmy wprowadziæ je ponownie, a¿ do osi±gniêcia
                 zamierzonego efektu.</para>
 	    </listitem>
 
 	    <listitem>
               <para>Nasza wersja BIOS-u nie pozwala na uruchomienie
                 systemu z wybranego no¶nika.</para>
 	    </listitem>
 	</orderedlist>
 	</step>
 
 	<step>
           <para>Rozpocznie siê ³adowanie FreeBSD. Podczas ³adowania
             z p³yty CD pojawi siê tekst podobny do poni¿szego (pominiêto
             informacje o wersji)::</para>
 
 	  <screen>Verifying DMI Pool Data ........
 Boot from ATAPI CD-ROM :
  1. FD 2.88MB  System Type-(00)
 Uncompressing ... done
 
 BTX loader 1.00 BTX version is 1.01
 Console: internal video/keyboard
 BIOS drive A: is disk0
 BIOS drive B: is disk1
 BIOS drive C: is disk2
 BIOS drive D: is disk3
 BIOS 639kB/261120kB available memory
 
 FreeBSD/i386 bootstrap loader, Revision 0.8
 
 /kernel text=0x277391 data=0x3268c+0x332a8 |
 
 |
 Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [kernel] in 9 seconds... _</screen>
 
 	  <para>Natomiast ³aduj±c z dyskietki, zobaczymy tekst w rodzaju
             (pominiêto informacje o wersji):</para>
 
 	  <screen>Verifying DMI Pool Data ........
 
 BTX loader 1.00  BTX version is 1.01
 Console: internal video/keyboard
 BIOS drive A: is disk0
 BIOS drive C: is disk1
 BIOS 639kB/261120kB available memory
 
 FreeBSD/i386 bootstrap loader, Revision 0.8
 
 /kernel text=0x277391 data=0x3268c+0x332a8 |
 
 Please insert MFS root floppy and press enter:</screen>
 
 	  <para>Postêpuj±c zgodnie z instrukcj± na ekranie,
             wyjmujemy dyskietkê <filename>kern.flp</filename>,
             wk³adamy <filename>mfsroot.flp</filename> i naciskamy
             <keycap>Enter</keycap>. We &os;&nbsp;5.3 i pó¼niejszych
             dostêpne s± równie¿ inne dyskietki opisane w <link linkend="install-floppies">poprzednim
             podrozdziale</link>. Nale¿y uruchomiæ system z pierwszej
             dyskietki, nastêpnie wk³adaæ kolejne zgodnie z pojawiaj±cymi
             siê komunikatami.</para>
 	</step>
 
 	<step>
           <para>Niezale¿nie, czy uruchamiamy komputer z dyskietki
             czy z p³yty, podczas ³adowania ujrzymy komunikat:</para>
 
 	  <screen>Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [kernel] in 9 seconds... _</screen>
 
 	  <para>Albo czekamy dziesiêæ sekund, albo wciskamy <keycap>Enter</keycap>.</para>
 	</step>
       </procedure>
 
       </sect3>
       <sect3>
         <title>Uruchomienie Alpha</title>
 
 	<indexterm><primary>Alpha</primary></indexterm>
 
       <procedure>
 	<step>
           <para>Na pocz±tku komputer powinien byæ wy³±czony.</para>
 	</step>
 
 	<step>
           <para>W³±czamy komputer i czekamy na znak zachêty boot monitora.</para>
         </step>
 
 	<step>
           <para>Je¿eli korzystamy z dyskietek startowych opisanych w
             <xref linkend="install-floppies"/>, to jedna z nich bêdzie
             pierwsz± dyskietk± startow±, najprawdopodobniej bêdzie to
             dyskietka zawieraj±ca <filename>kern.flp</filename>.
             J± w³a¶nie wk³adamy do stacji i wpisujemy nastêpuj±ce
             polecenie, aby uruchomiæ komputer z dyskietki (zmieniaj±c
             nazwê napêdu dyskietek, je¿eli bêdzie to konieczne):</para>
 
 	  <screen>&gt;&gt;&gt;<userinput>BOOT DVA0 -FLAGS '' -FILE ''</userinput></screen>
 
           <para>W przypadku korzystania z p³yty CD, wk³adamy
             j± do napêdu i rozpoczynamy instalacjê wpisuj±c
             nastêpuj±ce polecenie (wstawiaj±c inn± nazwê napêdu
             CDROM, je¿eli bêdzie to konieczne):</para>
 
           <screen>&gt;&gt;&gt;<userinput>BOOT DKA0 -FLAGS '' -FILE ''</userinput></screen>
 	</step>
 
 	<step>
           <para>Rozpocznie siê ³adowanie FreeBSD. Podczas ³adowania
             z dyskietki, zobaczymy tekst w rodzaju:</para>
 
 	  <screen>Please insert MFS root floppy and press enter:</screen>
 
           <para>Postêpuj±c zgodnie z instrukcj± na ekranie, wyjmujemy
             dyskietkê <filename>kern.flp</filename>, wk³adamy
             <filename>mfsroot.flp</filename> i naciskamy
             <keycap>Enter</keycap>.</para>
 	</step>
 
 	<step>
           <para>Niezale¿nie, czy uruchamiamy komputer z dyskietki
             czy z p³yty, podczas ³adowania ujrzymy komunikat:</para>
 
 	  <screen>Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [kernel] in 9 seconds... _</screen>
 
 	  <para>Czekamy dziesiêæ sekund, albo wciskamy <keycap>Enter</keycap>.
             Przejdziemy do menu konfiguracyjnego j±dra.</para>
 	</step>
       </procedure>
 
       </sect3>
 
     </sect2>
 
     <sect2 id="view-probe">
       <title>Przegl±danie wyników rozpoznania urz±dzeñ</title>
 
       <para>Kilkaset ostatnio wy¶wietlonych na ekranie linii
         jest zapisywanych i mo¿na je przegl±daæ.</para>
 
       <para>By przejrzeæ bufor, naciskamy <keycap>Scroll Lock</keycap>.
         W³±czamy w ten sposób tryb przewijania ekranu. Mo¿na teraz
         przegl±daæ wyniki rozpoznania urz±dzeñ przy u¿yciu klawiszy
         kursora, lub <keycap>PageUp</keycap> i <keycap>PageDown</keycap>.
         Tryb przewijania wy³±cza siê wciskaj±c ponownie
         <keycap>Scroll Lock</keycap>.</para>
 
       <para>Zróbmy to, aby przejrzeæ tekst, który zosta³ przewiniêty
         poza ekran, gdy j±dro dokonywa³o rozpoznawania urz±dzeñ.
         Tekst bêdzie mieæ tre¶æ podobn± do przedstawionej na
         <xref linkend="install-dev-probe"/>, jednak¿e dok³adna tre¶æ
           zale¿y od zainstalowanych w komputerze urz±dzeñ.</para>
 
       <figure id="install-dev-probe">
         <title>Przyk³ad wyników rozpoznania urz±dzeñ</title>
 
 	<screen>avail memory = 253050880 (247120K bytes)
 Preloaded elf kernel "kernel" at 0xc0817000.
 Preloaded mfs_root "/mfsroot" at 0xc0817084.
 md0: Preloaded image &lt;/mfsroot&gt; 4423680 bytes at 0xc03ddcd4
 
 md1: Malloc disk
 Using $PIR table, 4 entries at 0xc00fde60
 npx0: &lt;math processor&gt; on motherboard
 npx0: INT 16 interface
 pcib0: &lt;Host to PCI bridge&gt; on motherboard
 pci0: &lt;PCI bus&gt; on pcib0
 pcib1:&lt;VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge&gt; at device 1.0 on pci0
 pci1: &lt;PCI bus&gt; on pcib1
 pci1: &lt;Matrox MGA G200 AGP graphics accelerator&gt; at 0.0 irq 11
 isab0: &lt;VIA 82C586 PCI-ISA bridge&gt; at device 7.0 on pci0
 isa0: &lt;iSA bus&gt; on isab0
 atapci0: &lt;VIA 82C586 ATA33 controller&gt; port 0xe000-0xe00f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0 &lt;VIA 83C572 USB controller&gt; port 0xe400-0xe41f irq 10 at device 7.2 on pci
 0
 usb0: &lt;VIA 83572 USB controller&gt; on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr1
 uhub0: 2 ports with 2 removable, self powered
 pci0: &lt;unknown card&gt; (vendor=0x1106, dev=0x3040) at 7.3
 dc0: &lt;ADMtek AN985 10/100BaseTX&gt; port 0xe800-0xe8ff mem 0xdb000000-0xeb0003ff ir
 q 11 at device 8.0 on pci0
 dc0: Ethernet address: 00:04:5a:74:6b:b5
 miibus0: &lt;MII bus&gt; on dc0
 ukphy0: &lt;Generic IEEE 802.3u media interface&gt; on miibus0
 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 ed0: &lt;NE2000 PCI Ethernet (RealTek 8029)&gt; port 0xec00-0xec1f irq 9 at device 10.
 0 on pci0
 ed0 address 52:54:05:de:73:1b, type NE2000 (16 bit)
 isa0: too many dependant configs (8)
 isa0: unexpected small tag 14
 orm0: &lt;Option ROM&gt; at iomem 0xc0000-0xc7fff on isa0
 fdc0: &lt;NEC 72065B or clone&gt; at port 0x3f0-0x3f5,0x3f7 irq 6 drq2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: &lt;1440-KB 3.5" drive&gt; on fdc0 drive 0
 atkbdc0: &lt;Keyboard controller (i8042)&gt; at port 0x60,0x64 on isa0
 atkbd0: &lt;AT Keyboard&gt; flags 0x1 irq1 on atkbdc0
 kbd0 at atkbd0
 psm0: &lt;PS/2 Mouse&gt; irq 12 on atkbdc0
 psm0: model Generic PS/@ mouse, device ID 0
 vga0: &lt;Generic ISA VGA&gt; at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: &lt;System console&gt; at flags 0x100 on isa0
 sc0: VGA &lt;16 virtual consoles, flags=0x300&gt;
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: &lt;Parallel port&gt; at port 0x378-0x37f irq 7 on isa0
 pppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/15 bytes threshold
 plip0: &lt;PLIP network interface&gt; on ppbus0
 ad0: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata0-master UDMA33
 acd0: CD-RW &lt;LITE-ON LTR-1210B&gt; at ata1-slave PIO4
 Mounting root from ufs:/dev/md0c
 /stand/sysinstall running as init on vty0</screen>
       </figure>
 
       <para>Warto jest uwa¿nie przejrzeæ wyniki, by mieæ pewno¶æ,
         ¿e wszystkie spodziewane urz±dzenia zosta³y wykryte. Brak
         urz±dzenia na li¶cie oznacza, ¿e nie zosta³o ono wykryte.
         Je¶li sterownik wymaga³ skonfigurowania IRQ i adresu portu,
         to powinni¶my sprawdziæ, czy prawid³owo je wpisali¶my.</para>
 
       <para>Je¶li trzeba bêdzie zmieniæ ustawienia rozpoznawania
         urz±dzeñ, mo¿emy ³atwo opu¶ciæ program <application>sysinstall</application>
         i zacz±æ od nowa. Dziêki temu mo¿na równie¿ lepiej poznaæ ca³y proces.</para>
 
       <figure id="sysinstall-exit">
         <title>Wyj¶cie z sysinstall</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/sysinstall-exit"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Korzystaj±c z klawiszy kursora, wybieramy z g³ównego menu
         <guimenuitem>Exit Install</guimenuitem>. Uka¿e siê nastêpuj±cy
         komunikat:</para>
 
 
       <screen>                      User Confirmation Requested
          Are you sure you wish to exit? The system will reboot
            (be sure to remove any floppies from the drives).
 
                             [ Yes ]    No</screen>
 
       <para>Instalacja ponownie zacznie siê od pocz±tku,
         je¶li wybierzemy &gui.yes;, pozostawiaj±c p³ytê
         CD w napêdzie.</para>
 
       <para>Je¶li instalujemy z dyskietek, przed ponownym
         uruchomieniem komputera powinni¶my wyj±æ dyskietkê
         <filename>mfsroot.flp</filename> i w³o¿yæ
         <filename>kern.flp</filename>.</para>
     </sect2>
   </sect1>
 
   <sect1 id="using-sysinstall">
     <title>Wprowadzenie do sysinstall</title>
 
     <para><application>Sysinstall</application> jest aplikacj±
       instalacyjn± przygotowan± w ramach Projektu FreeBSD. Jest
       to program konsolowy podzielony na szereg pomniejszych menu
       i ekranów, s³u¿±cych do konfiguracji i zarz±dzania procesem
       instalacji.</para>
 
     <para>Menu <application>sysinstall</application> obs³ugiwane
       jest klawiszami kursora, klawiszem <keycap>Enter</keycap>,
       <keycap>Spacj±</keycap> i innymi. Dok³adny opis dzia³ania
       poszczególnych klawiszy znale¼æ mo¿na w czê¶ci po¶wiêconej
       pos³ugiwaniu siê <application>sysinstall</application>.</para>
 
     <para>Dostêp do tych informacji mo¿liwy jest poprzez pod¶wietlenie
       pozycji <guimenuitem>Usage</guimenuitem> i wybranie przycisku
       <guibutton>[Select]</guibutton>, a nastêpnie wci¶niêcie klawisza
       <keycap>Enter</keycap>, zgodnie z <xref
       linkend="sysinstall-main3"/>.</para>
 
     <para>Wy¶wietlone zostan± zostan± wskazówki odno¶nie pos³ugiwania
       siê systemem menu. Po ich przeczytaniu powrót do g³ównego menu
       mo¿liwy jest poprzez naci¶niêcie klawisza <keycap>Enter</keycap>.</para>
 
     <figure id="sysinstall-main3">
       <title>Wy¶wietlenie z g³ównego menu instrukcji obs³ugi sysinstall</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="install/main1"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
     <sect2 id="select-doc">
       <title>Menu dokumentacji</title>
 
       <para>Korzystaj±c z klawiszy kursora, w g³ównym menu wybieramy
         <guimenuitem>Doc</guimenuitem> i wciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="main-doc">
         <title>Wybór menu dokumentacji</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-doc"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Spowoduje to wy¶wietlenie menu dokumentacji.</para>
 
       <figure id="docmenu1">
         <title>Menu dokumentacji sysinstall</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/docmenu1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Warto przeczytaæ dostêpne tu dokumenty.</para>
 
       <para>By wy¶wietliæ konkretny dokument, wybieramy go
         klawiszami kursora, a nastêpnie wciskamy <keycap>Enter</keycap>.
         Po przeczytaniu klawiszem <keycap>Enter</keycap> mo¿emy powróciæ
         do menu dokumentacji.</para>
 
       <para>Do g³ównego menu instalacji powracamy wybieraj±c
         klawiszami kursora <guimenuitem>Exit</guimenuitem>,
         a nastêpnie wciskaj±c <keycap>Enter</keycap>.</para>
     </sect2>
 
     <sect2 id="keymap">
       <title>Menu mapowania klawiatury</title>
 
       <para>Aby zmieniæ mapowanie klawiatury klawiszami kursora
         wybieramy z menu pozycjê <guimenuitem>Keymap</guimenuitem>
         i wciskamy <keycap>Enter</keycap>. Zmiana mapowania klawiatury
         wymagana jest jedynie gdy u¿ywamy klawiatury innej ni¿
         standardowej amerykañskiej.</para>
 
       <figure id="sysinstall-keymap">
         <title>G³ówne menu sysinstall</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-keymap"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Wyboru mapowania klawiatury dokonujemy poprzez wskazanie
         odpowiedniej pozycji z listy przy pomocy klawiszy kursora,
         oraz wci¶niêcie <keycap>Spacji</keycap>. Ponowne naci¶niêcie
         <keycap>Spacji</keycap> cofa wybór. Po wybraniu odpowiedniego
         mapowania wskazujemy klawiszami kursora &gui.ok; i wciskamy
         <keycap>Enter</keycap>.</para>
 
       <para>Na poni¿szym rysunku przedstawiona jest tylko czê¶æ listy.
         Wybranie &gui.cancel; spowoduje przyjêcie domy¶lnego mapowania
         klawiatury i powrót do g³ównego menu.</para>
 
       <figure id="sysinstall-keymap-menu">
         <title>Menu mapowania klawiatury</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/keymap"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
     </sect2>
 
     <sect2 id="viewsetoptions">
       <title>Ekran opcji instalacji</title>
 
     <para>Wybieramy <guimenuitem>Options</guimenuitem>
       i naciskamy <keycap>Enter</keycap>.</para>
 
     <figure id="sysinstall-options">
       <title>G³ówne menu sysinstall</title>
 
       <mediaobject>
         <imageobject>
 	  <imagedata fileref="install/main-options"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
       <figure id="options">
         <title>Opcje sysinstall</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/options"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Warto¶ci domy¶lne s± zwykle odpowiednie dla wiêkszo¶ci
         u¿ytkowników i nie ma potrzeby ich zmiany. Nazwa wydania
         mo¿e byæ inna w zale¿no¶ci od instalowanej wersji
         systemu.</para>
 
       <para>Po wybraniu jednej z opcji, na dole ekranu uka¿e siê
         jej opis pod¶wietlony na niebiesko. Opcja <guimenuitem>Use Defaults</guimenuitem>
         (u¿yj domy¶lnych) przywraca wszystkim opcjom warto¶ci
         domy¶lne.</para>
 
       <para>Naciskaj±c <keycap>F1</keycap> przechodzimy do ekranu
         pomocy, gdzie mo¿emy przeczytaæ o poszczególnych opcjach.</para>
 
       <para>Naciskaj±c <keycap>Q</keycap> powracamy do g³ównego menu.</para>
     </sect2>
 
     <sect2 id="start-install">
       <title>Rozpoczêcie instalacji standardowej</title>
 
       <para>Instalacja standardowa zalecana jest dla wszystkich
         zaczynaj±cych sw± przygodê z FreeBSD, b±d¼ w ogóle z systemem
         &unix;. Klawiszami kursora wybieramy <guimenuitem>Standard</guimenuitem>
         i wciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="sysinstall-standard">
         <title>Rozpoczêcie instalacji standardowej</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-std"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 id="install-steps">
     <title>Przydzia³ miejsca na dysku</title>
 
     <para>Zaczynamy od przydzielenia FreeBSD przestrzeni dyskowej,
       oraz oznaczenia tej przestrzeni w taki sposób, by
       <application>sysinstall</application> móg³ j± przygotowaæ.
       Do tego potrzebna nam bêdzie wiedza na temat sposobu, w jaki
       FreeBSD znajduje informacje zapisane na dysku.</para>
 
     <sect2 id="install-drive-bios-numbering">
       <title>Kolejno¶æ dysków w BIOS-ie</title>
 
       <para>Przed instalacj± i konfiguracj± FreeBSD powinni¶my
         zapoznaæ siê z pewnym wa¿nym zagadnieniem, szczególnie
         istotnym dla posiadaczy dwóch lub wiêcej twardych dysków.</para>
 
       <indexterm><primary>DOS</primary></indexterm>
       <indexterm><primary>Microsoft Windows</primary></indexterm>
       <para>W komputerze typu PC wyposa¿onym w zale¿ny od BIOS-u system
         operacyjny, jak na przyk³ad &ms-dos; lub &microsoft.windows;,
         BIOS mo¿e zmieniæ rzeczywist± kolejno¶æ dysków, a system operacyjny
         tê zmianê zaakceptuje. Dziêki temu system mo¿e zostaæ uruchomiony
         z dysku innego ni¿ tzw. <quote>primary master</quote>. Jest to
         szczególnie wygodne dla tych u¿ytkowników, którzy za najprostsz±
         i najtañsz± metodê tworzenia kopii zapasowej uwa¿aj± kupno identycznego
         drugiego twardego dysku i kopiowanie zawarto¶ci pierwszego dysku przy
         u¿yciu <application><trademark class="registered">Ghost</trademark></application>
         lub <application>XCOPY</application>. W przypadku uszkodzenia pierwszego
         dysku, ataku wirusa lub awarii systemu operacyjnego, dane mog± byæ z ³atwo¶ci±
         odzyskane poprzez zamianê logicznej kolejno¶ci dysków w BIOS-ie. To tak,
         jakby zamieniæ przewody dysków, ale bez konieczno¶ci otwierania obudowy.</para>
 
       <indexterm><primary>SCSI</primary></indexterm>
       <indexterm><primary>BIOS</primary></indexterm>
       <para>Dro¿sze maszyny wyposa¿one w kontrolery SCSI maj± czêsto rozszerzenia
         BIOS-u pozwalaj±ce zamieniaæ kolejno¶æ dysków SCSI na podobnej zasadzie,
         obs³uguj±c do siedmiu dysków.</para>
 
       <para>U¿ytkowników przyzwyczajonych do korzystania z tego typu
         rozwi±zañ mo¿e spotkaæ niespodzianka, gdy we FreeBSD rezultaty
         odbiegaj± od oczekiwañ. FreeBSD nie korzysta z BIOS-u, jak
         równie¿ nie zna <quote>logicznej kolejno¶ci dysków BIOS-u</quote>.
         W efekcie mo¿e to prowadziæ do k³opotliwych sytuacji, szczególnie
         wtedy, gdy dyski s± identyczne pod wzglêdem geometrii, oraz zawieraj±
         takie same dane.</para>
 
       <para>Planuj±c u¿ywanie FreeBSD, powinni¶my ustawiæ w BIOS-ie
         rzeczywist± kolejno¶æ dysków przed instalacj± systemu, i tê
         kolejno¶æ pozostawiæ. Je¶li chcemy koniecznie zamieniæ dyski,
         to mo¿emy to zrobiæ sprzêtowo, otwieraj±c obudowê i zamieniaj±c
         odpowiednie zworki i przewody.</para>
 
       <sidebar>
         <title>Fragment z Archiwum Wyj±tkowych Przygód Bolka i Lolka:</title>
 
         <para>Bolek ma przygotowaæ dla Lolka komputer z FreeBSD. Bolek
           montuje jeden dysk SCSI jako urz±dzenie SCSI zero, i instaluje
           na nim FreeBSD.</para>
 
         <para>Lolek zaczyna korzystaæ z systemu, ale po kilku dniach zauwa¿a,
           ¿e dysk SCSI zg³asza liczne b³êdy, wiêc zawiadamia o tym Bolka.</para>
 
         <para>Po kolejnych kilku dniach Bolek postanawia rozwi±zaæ problem,
           wiêc bierze ze <quote>sk³adzika</quote> taki sam dysk SCSI.
           Kontrola powierzchni dysku wykazuje, ¿e dysk dzia³a prawid³owo,
           wiêc Bolek pod³±cza go jako czwarte urz±dzenie SCSI i wykonuje
           kopiê dysku zerowego na dysk czwarty. Poniewa¿ dysk jest pod³±czony
           i dzia³a jak nale¿y, Bolek stwierdza, ¿e mo¿na zacz±æ go u¿ywaæ, wiêc
           wykorzystuj±c mo¿liwo¶ci BIOS-u SCSI zmienia kolejno¶æ dysków w taki
           sposób, by system uruchamiany by³ z czwartego urz±dzenia SCSI. FreeBSD
           uruchamia siê i dzia³a jak nale¿y.</para>
 
         <para>Lolek korzysta z systemu przez jaki¶ czas, nastêpnie wspólnie z
           Bolkiem postanawiaj± spróbowaæ czego¶ nowego &mdash; zainstalowaæ
           nowsz± wersjê FreeBSD. Bolek wymontowuje dysk SCSI zero, poniewa¿
           dzia³a³ kiepsko, i zastêpuje go kolejnym identycznym dyskiem ze
           <quote>sk³adzika</quote>. Bolek instaluje now± wersjê FreeBSD
           na nowym dysku SCSI korzystaj±c z czarodziejskich dyskietek
           instalacyjnych Lolka. Instalacja przebiega prawid³owo.</para>
 
         <para>Lolek u¿ywa nowej wersji FreeBSD przez parê dni i stwierdza,
           ¿e mo¿na zacz±æ korzystaæ z niej w pracy. Wcze¶niej jednak
           trzeba bêdzie skopiowaæ wszystkie dane ze starej wersji. Lolek
           pod³±cza wiêc czwarty dysk SCSI (naj¶wie¿sz± kopiê starej wersji
           FreeBSD). Lolek stwierdza jednak z niepokojem, ¿e na dysku nie ma
           ¶ladu po jego cennych danych.</para>
 
         <para>Gdzie siê one podzia³y?</para>
 
         <para>Gdy Bolek sporz±dzi³ kopiê dysku zerowego na dysku czwartym,
           dysk czwarty sta³ siê <quote>klonem</quote>. Zmieniaj±c kolejno¶æ
           dysków w BIOS-ie SCSI aby móc uruchamiaæ system z dysku czwartego,
           Bolek sam siebie wprowadza³ w b³±d. FreeBSD wci±¿ dzia³a³o na dysku
           zerowym. Zmiana w BIOS-ie powoduje, ¿e czê¶æ kodu uruchamiaj±cego
           FreeBSD jest rzeczywi¶cie ³adowana z dysku wskazanego w BIOS-ie,
           lecz kiedy pa³eczkê przejmuj± sterowniki j±dra FreeBSD, kolejno¶æ
           dysków BIOS-u przestaje obowi±zywaæ, a FreeBSD przechodzi z powrotem
           na rzeczywist± kolejno¶æ. W opowiadanej historyjce system nadal
           dzia³a³ na dysku zerowym, i tam w³a¶nie znajdowa³y siê cenne dane
           Lolka, a nie na dysku czwartym. Choæ wydawa³o siê, ¿e system dzia³a
           na dysku czwartym, by³o to tylko z³udzenie.</para>
 
         <para>Z przyjemno¶ci± oznajmiamy, i¿ ani jeden bajt cennych danych
           nie zgin±³ ani nie zosta³ w inny sposób skrzywdzony podczas naszych
           badañ nad opisanym zjawiskiem. Stary dysk SCSI zero zosta³ odnaleziony
           i cenne dane wróci³y do Lolka (Bolek z kolei przekona³ siê,
           ¿e niczego nie mo¿na byæ pewnym).</para>
 
         <para>W opowie¶ci udzia³ wziê³y dyski SCSI, jednak¿e w przypadku
           dysków IDE sytuacja wygl±da³aby tak samo.</para>
       </sidebar>
     </sect2>
 
     <sect2 id="main-fdisk">
       <title>Tworzenie segmentów za pomoc± programu FDisk</title>
 
       <note>
         <para>Dokonywane tutaj zmiany nie zostan± zapisane na dysku.
           Je¿eli bêdziemy podejrzewaæ, ¿e co¶ zrobili¶my ¼le, mo¿emy
           wybraæ w menu wyj¶cie z programu <application>sysinstall</application>
           i spróbowaæ jeszcze raz od pocz±tku, b±d¼ wcisn±æ <keycap>U</keycap>
           by skorzystaæ z opcji <guimenuitem>Undo</guimenuitem> (cofnij).
           W ostateczno¶ci, je¿eli ca³kiem stracimy orientacjê, mo¿emy
           po prostu wy³±czyæ komputer.</para>
       </note>
 
       <para>Po wybraniu standardowej instalacji w <application>sysinstall</application>
         zostanie wy¶wietlony nastêpuj±cy komunikat:</para>
 
       <screen>                                 Message
  In the next menu, you will need to set up a DOS-style ("fdisk")
  partitioning scheme for your hard disk. If you simply wish to devote
  all disk space to FreeBSD (overwriting anything else that might be on
  the disk(s) selected) then use the (A)ll command to select the default
  partitioning scheme followed by a (Q)uit. If you wish to allocate only
  free space to FreeBSD, move to a partition marked "unused" and use the
  (C)reate command.
                                 [  OK  ]
 
                       [ Press enter or space ]</screen>
 
       <para>Zgodnie z poleceniem naciskamy <keycap>Enter</keycap>.
         Zobaczymy teraz listê twardych dysków znalezionych przez j±dro
         podczas rozpoznawania urz±dzeñ. <xref linkend="sysinstall-fdisk-drive1"/>
         przedstawia przyk³ad komputera z dwoma dyskami IDE, o nazwach
         <devicename>ad0</devicename> i <devicename>ad2</devicename>.</para>
 
       <figure id="sysinstall-fdisk-drive1">
         <title>Wybór dysku FDisk-a</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-drive1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Mo¿na siê zastanawiaæ, dlaczego na li¶cie brakuje
         <devicename>ad1</devicename>. Co spowodowa³o, ¿e zosta³ pominiêty?</para>
 
       <para>Przyjmijmy przyk³adowo, ¿e mamy dwa dyski IDE, jeden jako master
         na pierwszym kontrolerze IDE, drugi jako master na drugim kontrolerze
         IDE. Gdyby we FreeBSD zosta³y one ponumerowane w takiej kolejno¶ci,
         w jakiej zosta³y wykryte, czyli <devicename>ad0</devicename> i
 	<devicename>ad1</devicename>, wszystko dzia³a³oby jak nale¿y.</para>
 
       <para>Gdyby¶my jednak zainstalowali potem jeszcze jeden dysk,
         jako slave na pierwszym kontrolerze IDE, to ten w³a¶nie dysk
         zosta³by nowym <devicename>ad1</devicename>, a wcze¶niejszy
         <devicename>ad1</devicename> zmieni³by siê w <devicename>ad2</devicename>.
         Poniewa¿ systemy plików odnajdywane s± wed³ug nazw urz±dzeñ
         (np. <devicename>ad1s1a</devicename>), mog³oby siê nagle okazaæ,
         ¿e niektóre systemy plików nie dzia³aj± poprawnie.
         Aby to poprawiæ, musieliby¶my zmieniæ konfiguracjê systemu.</para>
 
       <para>Aby zapobiec takim sytuacjom, j±dro FreeBSD mo¿e byæ skonfigurowane
         tak, by przydzielaæ dyskom IDE numery zgodne z ich rzeczywistym
         umiejscowieniem, niezale¿nie od kolejno¶ci wykrywania. Tym sposobem
         dysk pod³±czony jako master na drugim kontrolerze IDE <emphasis>zawsze</emphasis>
         bêdzie mieæ nazwê <devicename>ad2</devicename>, nawet w sytuacji,
         gdy <devicename>ad0</devicename> i <devicename>ad1</devicename>
         nie s± w ogóle obecne.</para>
 
       <para>J±dro FreeBSD domy¶lnie skonfigurowane jest w³a¶nie w ten
         sposób, dlatego te¿ na ekranie mamy <devicename>ad0</devicename> i
 	<devicename>ad2</devicename>. Komputer, z którego ten rysunek pochodzi,
         mia³ dwa dyski IDE pod³±czone jako master do obu kontrolerów IDE,
         nie mia³ natomiast dysków pod³±czonych jako slave.</para>
 
       <para>Wybieramy dysk, na którym chcemy zainstalowaæ FreeBSD
         i wybieramy &gui.ok;. Zostanie uruchomiony <application>FDisk</application>,
         pokazuj±c na ekranie obraz podobny do <xref linkend="sysinstall-fdisk1"/>.</para>
 
       <para>Ekran <application>FDisk</application>-a podzielony jest na
         trzy czê¶ci.</para>
 
       <para>Czê¶æ pierwsza, obejmuj±ca pierwsze dwie linie ekranu, zawiera
         informacje o wybranym dysku, w tym jego oznaczenie we FreeBSD,
         geometriê oraz ca³kowity rozmiar dysku.k.</para>
 
       <para>Druga czê¶æ pokazuje informacje o istniej±cych na dysku
         segmentach: gdzie siê one zaczynaj± oraz koñcz±, jaki jest
         ich rozmiar, jaka nazwa zosta³a im nadana przez FreeBSD
         ich opis oraz typ. Na rysunku przyk³adowym widaæ dwa
         niewielkie nieu¿ywane segmenty, obecne ze wzglêdu na stosowany
         w architekturze PC podzia³ dysku. Prócz tego widaæ du¿y segment
         <acronym>FAT</acronym>, który prawie na pewno jest dyskiem
         <devicename>C:</devicename> w &ms-dos; / &windows;, oraz segment
         rozszerzony, zawieraj±cy byæ mo¿e dyski &ms-dos; / &windows;
         oznaczone kolejnymi literami.</para>
 
       <para>W trzeciej czê¶ci znajduje siê lista dostêpnych w
         <application>FDisk</application>-u poleceñ.</para>
 
       <figure id="sysinstall-fdisk1">
         <title>Uk³ad partycji w FDisk-u przed zmianami</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-edit1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Dalej postêpowaæ bêdziemy w zale¿no¶ci od tego, jak
         chcemy podzieliæ nasz dysk na segmenty.</para>
 
       <para>Je¿eli chcemy, by FreeBSD zajê³o ca³y dysk (co wi±¿e
         siê z usuniêciem z niego wszelkich innych danych, gdy
         potwierdzimy to w <application>sysinstall</application>
         na pó¼niejszym etapie instalacji), naciskamy <keycap>A</keycap>,
         co odpowiada opcji <guimenuitem>Use Entire Disk</guimenuitem>
         (wykorzystaj ca³y dysk). Istniej±ce segmenty zostan± usuniête,
         a w ich miejsce pojawi siê ma³y obszar opisany jako <literal>unused</literal>
         (nieu¿ywany; znów jest to nastêpstwem pecetowego uk³adu dysku),
         oraz du¿y segment przeznaczony dla FreeBSD. Je¿eli decydujemy
         siê na tê opcjê, powinni¶my w nastêpnej kolejno¶ci wskazaæ
         nowoutworzony segment FreeBSD przy u¿yciu klawiszy kursora
         i wcisn±æ <keycap>S</keycap>, by umo¿liwiæ ³adowanie systemu
         z tego segmentu. Ekran bêdzie wygl±daæ podobnie do przedstawionego
         na <xref linkend="sysinstall-fdisk2"/>. Zwróæmy uwagê na literê
         <literal>A</literal> w kolumnie Flags, oznacza ona, ¿e segment
         jest <emphasis>aktywny</emphasis> i bêdzie z niego ³adowany
         system.</para>
 
       <para>Je¶li chcemy usun±æ istniej±cy segment by zwolniæ miejsce
         dla FreeBSD, wskazujemy segment korzystaj±c z klawiszy kursora
         i naciskamy <keycap>D</keycap>. Nastêpnie mo¿emy nacisn±æ
         <keycap>C</keycap> i w odpowiedzi na pytanie o rozmiar segmentu,
         który chcemy utworzyæ, wpisaæ odpowiedni± warto¶æ i wcisn±æ
         <keycap>Enter</keycap>. Warto¶æ domy¶lna stanowi najwiêkszy
         mo¿liwy rozmiar segmentu, czyli np. woln± przestrzeñ na dysku
         b±d¼ ca³± pojemno¶æ dysku twardego.</para>
 
       <para>Wolne miejsce dla FreeBSD mogli¶my tak¿e przygotowaæ wcze¶niej
         (na przyk³ad przy u¿yciu programu
         <application>&partitionmagic;</application>), w takim wypadku po
         prostu wciskamy <keycap>C</keycap> by utworzyæ nowy segment.
         W tym przypadku równie¿ zostaniemy zapytani o rozmiar segmentu,
         który zamierzamy stworzyæ.</para>
 
       <figure id="sysinstall-fdisk2">
         <title>Partycja w FDisk-u obejmuj±ca ca³y dysk</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-edit2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Na koniec naciskamy <keycap>Q</keycap>. Dokonane zmiany
         zostan± zapamiêtane przez <application>sysinstall</application>,
         ale nie bêd± jeszcze zapisane na dysku.</para>
     </sect2>
 
     <sect2 id="bootmgr">
       <title>Instalacja programu ³aduj±cego</title>
 
       <para>W kolejnym kroku instalacji bêdziemy mieæ mo¿liwo¶æ
         zainstalowania programu ³aduj±cego (ang. boot manager).
         Mówi±c ogólnie, powinni¶my instalowaæ program ³aduj±cy
         FreeBSD je¿eli:</para>
 
       <itemizedlist>
 	<listitem>
           <para>Mamy dwa lub wiêcej dysków, a FreeBSD instalujemy
             na dysku innym ni¿ pierwszy.</para>
 	</listitem>
 
 	<listitem>
           <para>Instalujemy FreeBSD obok innego systemu operacyjnego
             na tym samym dysku, i chcemy mieæ mo¿liwo¶æ wybrania
             systemu operacyjnego podczas uruchamiania komputera.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Je¶li FreeBSD bêdzie jedynym systemem operacyjnym na
         danym komputerze i zostanie zainstalowany na pierwszym dysku
         twardym, wówczas wystarczy wykorzystaæ
         <guimenuitem>Standardowy</guimenuitem> program ³aduj±cy. Natomiast
         je¶li wykorzystujemy ju¿ inny program potrafi±cy uruchomiæ FreeBSD
         powinny¶my wybraæ opcjê <guimenuitem>None</guimenuitem> (¿aden).</para>
 
       <para>Dokonany wybór potwierdzamy naciskaj±c <keycap>Enter</keycap>.</para>
 
       <figure id="sysinstall-bootmgr">
         <title>Wybór programu ³aduj±cego w sysinstall</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/boot-mgr"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Ekran pomocy, wy¶wietlany po naci¶niêciu <keycap>F1</keycap>,
         opisuje problemy z jakimi mo¿na siê spotkaæ, gdy planuje siê mieæ
         kilka systemów operacyjnych na jednym dysku.</para>
     </sect2>
 
     <sect2>
       <title>Tworzenie segmentów na innym dysku</title>
 
       <para>Je¿eli mamy wiêcej dysków, po wyborze programu
         ³aduj±cego ponownie uka¿e siê ekran wyboru dysku.
         Chc±c zainstalowaæ FreeBSD na kilku dyskach, wybieramy
         tutaj kolejny dysk i ponownie korzystaj±c z programu
         <application>FDisk</application> tworzymy na nim
         segmenty.</para>
 
       <important>
         <para>Je¶li instalujemy FreeBSD na innym dysku ni¿ pierwszy,
           wówczas program ³aduj±cy FreeBSD musi zostaæ zainstalowany
           na obydwu dyskach.</para>
       </important>
 
       <figure id="sysinstall-fdisk-drive2">
         <title>Zakoñczenie wyboru dysku</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-drive2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawisz <keycap>Tab</keycap> prze³±cza pomiêdzy ostatnio
         wybranym dyskiem oraz przyciskami &gui.ok;, i
 	&gui.cancel;.</para>
 
       <para>Wciskamy <keycap>Tab</keycap> jeden raz, by wybraæ
         &gui.ok;, nastêpnie naciskamy <keycap>Enter</keycap>
         aby przej¶æ do kolejnego etapu instalacji.</para>
     </sect2>
 
     <sect2 id="bsdlabeleditor">
       <title>Tworzenie partycji z wykorzystaniem
 	<application>Disklabel</application></title>
 
       <para>W nowoutworzonych segmentach musimy stworzyæ kilka partycji.
         Pamiêtajmy, ¿e ka¿da partycja oznaczona jest liter± od
         <literal>a</literal> do <literal>h</literal>, a partycje
         <literal>b</literal>, <literal>c</literal> i <literal>d</literal>
         rz±dz± siê specjalnymi zasadami, których nale¿y przestrzegaæ.</para>
 
       <para>Niektóre aplikacje mog± skorzystaæ na stosowaniu okre¶lonych
         schematów podzia³u na partycje, szczególnie, gdy partycje roz³o¿one
         s± na kilku dyskach. Na razie jednak, poniewa¿ jest to nasza pierwsza
         instalacja FreeBSD, nie powinni¶my zbytnio przejmowaæ siê podzia³em
         dysku na partycje. Wa¿niejszym jest, by¶my zainstalowali FreeBSD
         i zaczêli siê uczyæ, jak go u¿ywaæ. Kiedy ju¿ nabierzemy pewnej
         wprawy, mo¿emy zainstalowaæ system ponownie i zmieniæ sposób
         podzia³u na partycje.</para>
 
       <para>Poni¿szy schemat przedstawia cztery partycje &mdash; jedn± dla
         przestrzeni wymiany, oraz trzy dla systemów plików.</para>
 
       <table frame="none" pgwide="1">
         <title>Uk³ad partycji pierwszego dysku</title>
 
 	<tgroup cols="4">
           <colspec colwidth="1*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="4*"/>
 
 	  <thead>
 	    <row>
 	      <entry>Partycja</entry>
 
 	      <entry>System plików</entry>
 
 	      <entry>Rozmiar</entry>
 
 	      <entry>Opis</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><literal>a</literal></entry>
 
 	      <entry><filename>/</filename></entry>
 
 	      <entry>100&nbsp;MB</entry>
 
               <entry>Bêdzie to g³ówny system plików. Wszystkie inne systemy
                 plików bêd± zamontowane gdzie¶ wewn±trz niego. 100&nbsp;MB
                 jest do¶æ rozs±dnym rozmiarem dla tego celu. Nie bêdzie tu
                 przechowywane zbyt wiele danych, zwykle po instalacji FreeBSD
                 umieszcza tu oko³o 40&nbsp;MB danych. Pozosta³e miejsce jest dla
                 danych tymczasowych, oraz s³u¿y jako zapas, gdyby kolejne wersje
                 FreeBSD potrzebowa³y wiêcej miejsca w <filename>/</filename>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>b</literal></entry>
 
 	      <entry>brak</entry>
 
 	      <entry>2-3 x RAM</entry>
 
               <entry><para>Partycja ta s³u¿y jako przestrzeñ wymiany. Wybór jej
                   odpowiedniego rozmiaru nie jest spraw± banaln±. Mo¿emy przyj±æ,
                   ¿e przestrzeñ wymiany powinna byæ dwu- lub trzykrotnie wiêksza
                   ni¿ ilo¶æ pamiêci fizycznej (RAM). Prócz tego powinni¶my mieæ
                   co najmniej 64&nbsp;MB przestrzeni wymiany, wiêc je¿eli nasz
                   komputer ma mniej ni¿ 32&nbsp;MB pamiêci, ustawmy rozmiar
                   przestrzeni wymiany na 64&nbsp;MB.</para><para>
 
                   Je¶li dysponujemy kilkoma dyskami, mo¿emy na ka¿dym z nich
                   umie¶ciæ przestrzeñ wymiany. FreeBSD bêdzie w procesie wymiany
                   wykorzystywaæ ka¿dy z dysków, dziêki czemu wymiana bêdzie siê
                   odbywaæ szybciej. W takim przypadku przyjmujemy ca³kowity
                   rozmiar potrzebnej przestrzeni wymiany (np. 128&nbsp;MB)
                   i dzielimy go przez liczbê posiadanych dysków (np. dwa dyski),
                   otrzymuj±c w wyniku rozmiar przestrzeni wymiany dla jednego dysku.
                   W naszym przyk³adzie bêdzie to 64&nbsp;MB na ka¿dy dysk.</para></entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>e</literal></entry>
 
 	      <entry><filename>/var</filename></entry>
 
 	      <entry>50&nbsp;MB</entry>
 
               <entry>W katalogu <filename>/var</filename> przechowywane s± pliki
                 o zmiennych rozmiarach; pliki dzienników systemowych i inne pliki
                 administracyjne. Podczas codziennej pracy FreeBSD na wielu z tych
                 plików dokonywane s± czêste operacje odczytu lub zapisu. Dziêki
                 umieszczeniu ich w oddzielnym systemie plików FreeBSD mo¿e dokonaæ
                 optymalizacji dostêpu do nich, nie wywieraj±c jednocze¶nie wp³ywu
                 na inne pliki, do których dostêp przebiega inaczej.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>f</literal></entry>
 
 	      <entry><filename>/usr</filename></entry>
 
 	      <entry>Reszta dysku</entry>
 
               <entry>Inne pliki bêd± zwykle przechowywane w katalogu
                 <filename>/usr</filename> i jego podkatalogach.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>Je¿eli instalujemy FreeBSD na dwóch lub wiêcej dyskach, musimy
         utworzyæ partycje tak¿e w innych przygotowanych segmentach. Naj³atwiej
         jest po prostu przygotowaæ na ka¿dym z kolejnych dysków dwie partycje,
         jedn± na przestrzeñ wymiany, drug± na system plików.</para>
 
       <table frame="none" pgwide="1">
         <title>Uk³ad partycji dla kolejnych dysków</title>
 
 	<tgroup cols="4">
           <colspec colwidth="1*"/>
           <colspec colwidth="1*"/>
           <colspec colwidth="2*"/>
           <colspec colwidth="3*"/>
 
 	  <thead>
 	    <row>
 	      <entry>Partycja</entry>
 
 	      <entry>System plików</entry>
 
 	      <entry>Rozmiar</entry>
 
 	      <entry>Opis</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><literal>b</literal></entry>
 
 	      <entry>brak</entry>
 
               <entry>Patrz: opis</entry>
 
               <entry>Jak ju¿ powiedzieli¶my, przestrzeñ wymiany mo¿emy
                 dzieliæ miêdzy kilka dysków. Mimo, i¿ mamy do dyspozycji
                 partycjê <literal>a</literal>, zgodnie z obowi±zuj±c±
                 konwencj± przestrzeñ wymiany powinna znajdowaæ siê na
                 partycji <literal>b</literal>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>e</literal></entry>
 
 	      <entry>/dysk<replaceable>n</replaceable></entry>
 
               <entry>Reszta dysku</entry>
 
               <entry>Pozosta³a czê¶æ dysku zajmowana jest przez jedn±
                 du¿± partycjê. Mog³aby to z powodzeniem byæ partycja
                 <literal>a</literal>, zamiast <literal>e</literal>.
                 Przyjêto jednak, ¿e partycja <literal>a</literal>
                 zarezerwowana jest dla g³ównego systemu plików (<filename>/</filename>).
                 Nie ma przymusu stosowania tej zasady, jednak
                 <application>sysinstall</application> jej przestrzega,
                 dobrze wiêc jest j± stosowaæ dla zachowania porz±dku
                 podczas instalacji. System plików mo¿emy zamontowaæ
                 w dowolnym miejscu, w przyk³adzie zaproponowano
                 <filename>/dysk<replaceable>n</replaceable></filename>,
                 gdzie <replaceable>n</replaceable> jest kolejnym numerem
                 ka¿dego dysku. Mo¿na jednak wybraæ inne nazewnictwo wed³ug
                 uznania..</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>Po podjêciu decyzji jak ma wygl±daæ uk³ad partycji, pora wprowadziæ
         go w ¿ycie u¿ywaj±c <application>sysinstall</application>. Na ekranie
         uka¿e siê nastêpuj±cy komunikat:</para>
 
       <screen>                                 Message
  Now, you need to create BSD partitions inside of the fdisk
  partition(s) just created. If you have a reasonable amount of disk
  space (200MB or more) and don't have any special requirements, simply
  use the (A)uto command to allocate space automatically. If you have
  more specific needs or just don't care for the layout chosen by
  (A)uto, press F1 for more information on manual layout.
 
                                 [  OK  ]
                           [ Press enter or space ]</screen>
 
       <para>Naciskamy <keycap>Enter</keycap> by przej¶æ do edytora partycji
         FreeBSD, zwanego <application>Disklabel</application>.</para>
 
       <para><xref linkend="sysinstall-label"/> przedstawia ekran zaraz po
         uruchomieniu <application>Disklabel</application>. Jest on podzielony
         na trzy czê¶ci.</para>
 
       <para>W kilku pierwszych wierszach widoczna jest nazwa wybranego
         aktualnie dysku, oraz nazwa segmentu, w którym tworzymy partycje
         (<application>Disklabel</application> u¿ywa tutaj nazwy
         <literal>Partition name</literal>, czyli nazwa partycji,
         a nie nazwa segmentu). Jest tu równie¿ zawarta informacja o
         rozmiarze wolnej przestrzeni wewn±trz segmentu, czyli przestrzeni
         nie przydzielonej jeszcze partycjom.</para>
 
       <para>¦rodek ekranu zajmuje lista utworzonych partycji, wraz
         z nazwami przechowywanych na nich systemów plików, ich rozmiarami
         oraz pewnymi opcjami zwi±zanymi z tworzeniem systemu plików.</para>
 
       <para>W dolnej czê¶ci przedstawiona jest lista dostêpnych w
         <application>Disklabel</application> poleceñ.</para>
 
       <figure id="sysinstall-label">
         <title>Edytor Disklabel</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-ed1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para><application>Disklabel</application> potrafi automatycznie
         utworzyæ partycje i nadaæ im domy¶lne rozmiary. Wypróbujmy tê
         mo¿liwo¶æ naciskaj±c <keycap>A</keycap>. Na ekranie uka¿e
         siê obraz podobny do <xref linkend="sysinstall-label2"/>.
         Ustawienia automatyczne mog± byæ w³a¶ciwe lub nie, w zale¿no¶ci
         od rozmiaru dysku. Nie ma to jednak wiêkszego znaczenia, poniewa¿
         nie trzeba ich koniecznie akceptowaæ.</para>
 
 	<note>
           <para>Katalog <filename>/tmp</filename> jest domy¶lnie umieszczany
             na w³asnej partycji, zamiast byæ czê¶ci± partycji <filename>/</filename>.
             Dziêki temu mo¿na unikn±æ zape³nienia partycji <filename>/</filename>
             plikami tymczasowymi.</para>
 	</note>
 
       <figure id="sysinstall-label2">
         <title>Edytor disklabel z automatycznymi ustawieniami</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-auto"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>By usun±æ zaproponowane partycje i zast±piæ je utworzonymi
         w³asnorêcznie, wybieramy klawiszami kursora pierwsz± partycjê
         i naciskamy <keycap>D</keycap>. Tak samo postêpujemy z pozosta³ymi
         partycjami.</para>
 
       <para>Teraz, aby stworzyæ pierwsz± partycjê (<literal>a</literal>,
         zamontowan± jako <filename>/</filename>), wybieramy informacje
         o dysku w górnej czê¶ci ekranu i wciskamy <keycap>C</keycap>.
         Pojawi siê okienko z pytaniem o rozmiar nowej partycji
         (<xref linkend="sysinstall-label-add"/>). Wybrany rozmiar podaæ
         mo¿emy w blokach, albo w wygodniejszej formie w postaci liczby
         megabajtów, gigabajtów lub cylindrów, odpowiednio z przyrostkiem
         <literal>M</literal>, <literal>G</literal> lub
         <literal>C</literal>.</para>
 
       <note><para>Pocz±wszy od FreeBSD&nbsp;5.X u¿ytkownicy mog±: wybraæ
           system plików <acronym>UFS2</acronym> (domy¶lny system we &os;&nbsp;5.1
           i pó¼niejszych) wykorzystuj±c opcjê <literal>Custom Newfs</literal>
           (<keycap>Z</keycap>), tworzyæ partycje za pomoc± <literal>Auto Defaults</literal>
           i modyfikowaæ przy pomocy <literal>Custom Newfs</literal> b±d¼ dodaæ opcjê
           <option>-O 2</option> podczas normalnego procesu tworzenia partycji.
           Wykorzystuj±c opcjê <literal>Custom Newfs</literal> musimy pamiêtaæ
           by dodaæ flagê <option>-U</option> (SoftUpdates)!</para></note>
 
       <figure id="sysinstall-label-add">
         <title>Wolne miejsce dla g³ównej partycji</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Wybieraj±c domy¶lnie zaproponowany rozmiar utworzymy
         partycjê obejmuj±c± pozosta³e miejsce w segmencie. Je¿eli
         zamierzamy stworzyæ partycje o takich rozmiarach, jak
         wcze¶niej opisywali¶my, wówczas kasujemy zaproponowan±
         warto¶æ klawiszem <keycap>Backspace</keycap>, i wpisujemy
         64M, <xref linkend="sysinstall-label-add2"/>. Nastêpnie
         wybieramy &gui.ok;.</para>
 
       <figure id="sysinstall-label-add2">
         <title>Zmiana rozmiaru g³ównej partycji</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Po wybraniu rozmiaru partycji pojawi siê pytanie, czy
         partycja zawieraæ bêdzie system plików, czy przestrzeñ wymiany.
         Okienko z tym pytaniem pokazane jest na <xref linkend="sysinstall-label-type"/>.
         Pierwsza partycja zawieraæ bêdzie system plików, wybieramy wiêc
         <guimenuitem>FS</guimenuitem> i naciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="sysinstall-label-type">
         <title>Wybór typu g³ównej partycji</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-fs"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Poniewa¿ na partycji znajdowaæ siê bêdzie system plików,
         <application>Disklabel</application> musi wiedzieæ, gdzie bêdzie
         on zamontowany. <xref linkend="sysinstall-label-mount"/> przedstawia
         okienko z pro¶b± o podanie tej informacji. G³ówny system plików
         montowany jest jako <filename>/</filename>, wpisujemy wiêc
         <filename>/</filename> i wciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="sysinstall-label-mount">
         <title>Wybór miejsca montowania g³ównego systemu plików</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Na ekranie pojawi siê informacja o nowo utworzonej partycji.
         Powinni¶my teraz powtórzyæ ca³± procedurê dla kolejnych partycji.
         Tworz±c partycjê wymiany nie bêdziemy pytani o miejsce jej zamontowania,
         poniewa¿ partycje wymiany nie s± montowane. Gdy bêdziemy tworzyæ
         ostatni± partycjê, <filename>/usr</filename>, mo¿emy przyj±æ
         proponowany rozmiar domy¶lny, aby przeznaczyæ na tê partycjê
         resztê segmentu.</para>
 
       <para>Ostatecznie ekran edytora Disklabel bêdzie wygl±daæ podobnie do
         <xref linkend="sysinstall-label4"/>, choæ wybrane przez nas warto¶ci
         mog± byæ inne. By zakoñczyæ pracê z Disklabel, wciskamy
         <keycap>Q</keycap>.</para>
 
       <figure id="sysinstall-label4">
         <title>Edytor Disklabel</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-ed2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 id="install-choosing">
     <title>Wybór sk³adników instalacji</title>
 
     <sect2 id="distset">
       <title>Wybór zestawu komponentów</title>
 
       <para>Decyzja o tym, jaki zestaw komponentów zainstalujemy,
         zale¿y w du¿ej mierze od planowanych zastosowañ systemu
         i ilo¶ci wolnego miejsca na dysku. Dostêpne warianty
         pozwalaj± zarówno na instalacjê najmniejszej konfiguracji,
         jak i na instalacjê wszystkiego. Pocz±tkuj±cy u¿ytkownicy
         systemów &unix; i FreeBSD powinni wybraæ jeden z przygotowanych
         wariantów. Dla bardziej do¶wiadczonych u¿ytkowników istnieje
         mo¿liwo¶æ u³o¿enia w³asnego zestawu komponentów.</para>
 
       <para>Wiêcej informacji o zestawach komponentów i ich zawarto¶ci
         mo¿emy uzyskaæ naciskaj±c <keycap>F1</keycap>. Po przejrzeniu
         tych informacji naciskamy <keycap>Enter</keycap>, aby powróciæ
         do menu wyboru komponentów.</para>
 
       <para>Je¶li planujemy korzystaæ z graficznego interfejsu u¿ytkownika
         powinni¶my wybraæ jeden z zestawów o nazwie rozpoczynaj±cej siê
         liter± <literal>X</literal>. Po instalacji zajmiemy siê konfigurowaniem
         serwera graficznego i wyborem mened¿era okien. Szczegó³owe informacje
         na ten temat zawiera rozdzia³ <xref linkend="x11"/>.</para>
 
       <para>To, która wersja systemu X11 jest domy¶lnie instalowana,
         zale¿y od instalowanej wersji &os;. Wydania wcze¶niejsze od 5.3
         domy¶lnie instaluj± <application>&xfree86;&nbsp;4.X</application>.
         Natomiast &os;&nbsp;5.3 i pó¼niejsze instaluj±
         <application>&xorg;</application>.</para>
 
       <para>Je¿eli planujemy samodzielne kompilowanie j±dra, powinni¶my
         wybraæ wariant zawieraj±cy kod ¼ród³owy. <xref linkend="kernelconfig"/>
         zawiera informacje, dlaczego powinno siê budowaæ niestandardowe
         j±dro i jak to zrobiæ.</para>
 
       <para>Oczywi¶cie najbardziej wszechstronny jest system zawieraj±cy
         wszystkie komponenty. Je¶li mamy wystarczaj±co du¿o miejsca na dysku,
         wybieramy klawiszami kursora <guimenuitem>All</guimenuitem>,
         <xref linkend="distribution-set1"/>, i naciskamy <keycap>Enter</keycap>.
         Je¿eli jednak miejsca na dysku mog³oby nie wystarczyæ, wybierzmy wariant
         najlepiej odpowiadaj±cy obecnym potrzebom. Kolejne komponenty mog± byæ
         dodawane po zainstalowaniu systemu.</para>
 
       <figure id="distribution-set1">
         <title>Wybór komponentów</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/dist-set"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
 
     <sect2 id="portscol">
       <title>Instalacja kolekcji portów</title>
 
       <para>Po wyborze komponentów bêdziemy mieæ mo¿liwo¶æ zainstalowania
         kolekcji portów FreeBSD. Kolekcja portów umo¿liwia ³atwe
         i wygodne instalowanie oprogramowania. Nie zawiera ona kodów
         ¼ród³owych programów. W sk³ad kolekcji portów wchodz± pliki
         umo¿liwiaj±ce automatyczne pobieranie programów, oraz ich
         kompilowanie i instalowanie. <xref linkend="ports"/> opisuje
         sposób korzystanie z kolekcji portów.</para>
 
       <para>Program instalacyjny nie sprawdza, czy mamy odpowiednio
         du¿o wolnego miejsca na dysku. Kolekcjê portów powinni¶my
         instalowaæ tylko pod warunkiem, ¿e miejsca faktycznie wystarczy.
         We FreeBSD &rel.current; kolekcja zajmuje oko³o
         &ports.size;.</para>
 
 <screen>                         User Confirmation Requested
  Would you like to install the FreeBSD ports collection?
 
  This will give you ready access to over &os.numports; ported software packages,
  at a cost of around &ports.size; of disk space when "clean" and possibly much
  more than that if a lot of the distribution tarballs are loaded
  (unless you have the extra CDs from a FreeBSD CD/DVD distribution
  available and can mount it on /cdrom, in which case this is far less
  of a problem).
 
  The Ports Collection is a very valuable resource and well worth having
  on your /usr partition, so it is advisable to say Yes to this option.
 
  For more information on the Ports Collection &amp; the latest ports,
  visit:
      http://www.FreeBSD.org/ports
 
                               [ Yes ]     No</screen>
 
       <para>Klawiszami kursora wybieramy &gui.yes;, aby zainstalowaæ kolekcjê
         portów, lub &gui.no;, by z niej zrezygnowaæ. Wybór zatwierdzamy
         klawiszem <keycap>Enter</keycap>. Ponownie pojawi siê menu wyboru
         komponentów.</para>
 
       <figure id="distribution-set2">
         <title>Zatwierdzenie wybranych komponentów</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/dist-set2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Je¿eli odpowiadaj± nam wybrane komponenty, przy pomocy
         klawiszy kursora wybieramy <guimenuitem>Exit</guimenuitem>,
         zaznaczamy &gui.ok;  i naciskamy <keycap>Enter</keycap>,
         przechodz±c do kolejnego etapu instalacji.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="install-media">
     <title>Wybór no¶nika instalacji</title>
 
     <para>W przypadku, gdy instalujemy z p³yty CD b±d¼ DVD,
       klawiszami kursora wybieramy pozycjê
       <guimenuitem>Install from a FreeBSD CD/DVD</guimenuitem>
       (instalacja z CD/DVD). Upewniwszy siê, ¿e zaznaczone jest
       &gui.ok;, naciskamy <keycap>Enter</keycap> przechodz±c
       do nastêpnego etapu instalacji.</para>
 
     <para>Je¿eli stosujemy inn± metodê instalacji, wybieramy
       odpowiedni± pozycjê i postêpujemy zgodnie ze wskazówkami.</para>
 
     <para>Klawiszem <keycap>F1</keycap> mo¿emy w³±czyæ pomoc.
       Do menu wyboru no¶nika powracamy naciskaj±c
       <keycap>Enter</keycap>.</para>
 
     <figure id="choose-media">
       <title>Wybór no¶nika instalacji</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="install/media"/>
 	</imageobject>
       </mediaobject>
     </figure>
 
     <note>
       <title>Tryby instalacji przez FTP</title>
 
       <indexterm>
 	<primary>instalacja</primary>
 	<secondary>sieæ</secondary>
 	<tertiary>FTP</tertiary>
       </indexterm>
 
       <para>Mo¿na wybraæ jeden z trzech trybów instalacji
         przez FTP: aktywne FTP, pasywne FTP lub po¶rednio
         przez HTTP proxy.</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>Aktywne FTP: <guimenuitem>Install from an FTP
 	      server</guimenuitem></term>
 
 	  <listitem>
             <para>Wybór tego wariantu spowoduje, ¿e przesy³anie
               danych przez FTP odbywaæ siê bêdzie w trybie
               <quote>aktywnym</quote>. Nie zadzia³a to w przypadku
               transmisji przez zaporê ogniow±, ale bêdzie
               wspó³pracowaæ ze starszymi serwerami FTP nie
               obs³uguj±cymi trybu pasywnego. Je¶li po³±czenie
               pasywne (wybierane domy¶lnie) nie zadzia³a,
               spróbujmy aktywnego!</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Pasywne FTP: <guimenuitem>Install from an FTP server through a
 	      firewall</guimenuitem></term>
 
 	  <listitem>
 	    <indexterm>
 	      <primary>FTP</primary>
 	      <secondary>tryb pasywny</secondary>
 	    </indexterm>
 
             <para>Opcja ta informuje <application>sysinstall</application>,
               ¿e przesy³anie danych przez FTP odbywaæ siê bêdzie w trybie
               <quote>pasywnym</quote>. Pozwoli to na po³±czenie poprzez
               zaporê ogniow±, która nie zezwala na po³±czenia z zewn±trz
               z portami o przypadkowych numerach.
 	    </para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>FTP przez proxy HTTP: <guimenuitem>Install from an FTP server
 	      through a http proxy</guimenuitem></term>
 
 	  <listitem>
 	    <indexterm>
 	      <primary>FTP</primary>
 	      <secondary>przez proxy HTTP</secondary>
 	    </indexterm>
 
             <para>Ten wariant instruuje <application>sysinstall</application>
               do wykorzystania protoko³u HTTP (podobnie jak przegl±darka
               stron WWW) do po³±czenia siê z serwerem proxy po¶rednicz±cym
               w transmisji przez FTP. Serwer po¶rednicz±cy przetwarza ¿±dania
               i przesy³a je do serwera FTP. Dziêki temu mo¿liwe jest po³±czenie
               poprzez zaporê ogniow± nie zezwalaj±c± na ¿adne po³±czenia
               FTP, oferuj±c± jednak HTTP proxy. W takiej sytuacji, poza
               adresem serwera FTP, bêdziemy musieli podaæ tak¿e adres
               serwera proxy.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>Korzystaj±c z po¶rednicz±cego serwera FTP proxy, zwykle
         podajemy nazwê serwera docelowego jako czê¶æ nazwy u¿ytkownika,
         po znaku <quote>@</quote>. Serwer proxy <quote>udaje</quote>
         wówczas serwer docelowy. Za³ó¿my, dla przyk³adu, ¿e chcemy
         zainstalowaæ system z <hostid role="fqdn">ftp.FreeBSD.org</hostid>,
         za po¶rednictwem serwera proxy FTP <hostid role="fqdn">foo.example.com</hostid>,
         nas³uchuj±cego na porcie 1024.</para>
 
       <para>W takiej sytuacji przechodzimy do menu opcji, jako nazwê
         u¿ytkownika FTP wpisujemy <literal>ftp@ftp.FreeBSD.org</literal>,
         a jako has³o podajemy nasz adres email. Jako no¶nik instalacji
         wybieramy FTP (lub pasywne FTP, je¿eli umo¿liwia to serwer proxy),
         a jako URL wpisujemy
 	<literal>ftp://foo.example.com:1234/pub/FreeBSD</literal>.</para>
 
       <para>Ze wzglêdu na to, ¿e <filename>/pub/FreeBSD</filename>
         z <hostid role="fqdn">ftp.FreeBSD.org</hostid> jest udostêpnione
         na serwerze proxy <hostid role="fqdn">foo.example.com</hostid>,
         mo¿emy w³a¶nie z <emphasis>tego</emphasis> serwera dokonaæ
         instalacji (poniewa¿ zajmie siê on pobraniem odpowiednich plików
         z <hostid role="fqdn">ftp.FreeBSD.org</hostid>).</para>
     </note>
   </sect1>
 
   <sect1 id="install-final-warning">
     <title>Przyst±pienie do instalacji</title>
 
     <para>Mo¿emy teraz rozpocz±æ w³a¶ciw± instalacjê, a zarazem
       mamy ostatni± szansê na rezygnacjê z instalacji bez zmiany
       zawarto¶ci dysku twardego.</para>
 
     <screen>                       User Confirmation Requested
  Last Chance! Are you SURE you want to continue the installation?
 
  If you're running this on a disk with data you wish to save then WE
  STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding!
 
  We can take no responsibility for lost disk contents!
 
                              [ Yes ]    No</screen>
 
     <para>Wybieramy &gui.yes; i wciskamy
       <keycap>Enter</keycap>, by rozpocz±æ instalacjê.</para>
 
     <para>Czas trwania instalacji zale¿y od wybranych komponentów,
       u¿ywanego no¶nika instalacji oraz prêdko¶ci komputera. Szereg
       komunikatów informowaæ bêdzie o przebiegu procesu instalacji.</para>
 
     <para>Po zakoñczeniu instalacji wy¶wietlony zostanie
       nastêpuj±cy komunikat:</para>
 
     <screen>                               Message
 
 Congratulations! You now have FreeBSD installed on your system.
 
 We will now move on to the final configuration questions.
 For any option you do not wish to configure, simply select No.
 
 If you wish to re-enter this utility after the system is up, you may
 do so by typing: /stand/sysinstall .
 
                                  [ OK ]
 
                       [  Press enter to continue  ]</screen>
 
     <para>Po naci¶niêciu klawisza <keycap>Enter</keycap>
       zajmiemy siê przygotowaniem wstêpnej konfiguracji systemu.</para>
 
     <para>Je¶li wybierzemy &gui.no; i naci¶niemy
       <keycap>Enter</keycap> instalacja zostanie przerwana,
       bez dokonywania jakichkolwiek zmian. Pojawi siê komunikat
       o tre¶ci:</para>
 
     <screen>                                Message
 Installation complete with some errors.  You may wish to scroll
 through the debugging messages on VTY1 with the scroll-lock feature.
 You can also choose "No" at the next prompt and go back into the
 installation menus to retry whichever operations have failed.
 
                                  [ OK ]</screen>
 
     <para>Powy¿szy komunikat pojawia siê, poniewa¿ nic nie zosta³o
       zainstalowane. Naciskaj±c <keycap>Enter</keycap> mo¿emy powróciæ
       do g³ównego menu i opu¶ciæ program instalacyjny.</para>
   </sect1>
 
   <sect1 id="install-post">
     <title>Po instalacji</title>
 
     <para>Po pomy¶lnie zakoñczonej instalacji zajmiemy siê
       wstêpn± konfiguracj± systemu. Wszelkich zmian w ustawieniach
       mo¿emy dokonaæ przed uruchomieniem nowo zainstalowanego systemu
       FreeBSD lub te¿ po zakoñczeniu instalacji, korzystaj±c z
       <command>sysinstall</command> (we &os; starszych ni¿ 5.2
       <command>/stand/sysinstall</command>) i jego opcji
       <guimenuitem>Configure</guimenuitem>.</para>
 
     <sect2 id="inst-network-dev">
       <title>Konfiguracja urz±dzeñ sieciowych</title>
 
       <para>Je¶li wcze¶niej skonfigurowali¶my PPP na potrzeby
         instalacji przez FTP, konfiguracja urz±dzeñ sieciowych
         zostanie pominiêta. Bêdziemy mogli zaj±æ siê ni±
         pó¼niej.</para>
 
       <para>Szczegó³owe informacje na temat sieci lokalnych
         (LAN) oraz konfiguracji FreeBSD w roli bramy lub rutera
         znale¼æ mo¿na w rozdziale <link
           linkend="advanced-networking">Zaawansowana konfiguracja
           sieciowa</link>.</para>
 
       <screen>                      User Confirmation Requested
    Would you like to configure any Ethernet or SLIP/PPP network devices?
 
                              [ Yes ]   No</screen>
 
       <para>Je¶li chcemy skonfigurowaæ urz±dzenie sieciowe,
         wybieramy &gui.yes; i wciskamy <keycap>Enter</keycap>.
         W przeciwnym wypadku wybieramy &gui.no;.</para>
 
       <figure id="ed-config1">
         <title>Wybór karty Ethernet</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ed0-conf"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawiszami kursora wybieramy interfejs, który bêdziemy
         konfigurowaæ i wciskamy <keycap>Enter</keycap>.</para>
 
       <screen>                      User Confirmation Requested
        Do you want to try IPv6 configuration of the interface?
 
                               Yes   [ No ]</screen>
 
       <para>Dla przyk³adu, w sieci lokalnej w zupe³no¶ci wystarcza obecny
         protokó³ Internetu (<acronym>IPv4</acronym>), wybieramy wiêc klawiszami
         kursora &gui.no; i naciskamy <keycap>Enter</keycap>.</para>
 
       <para>Je¶li chcemy wypróbowaæ nowy protokó³ Internetu (<acronym>IPv6</acronym>),
         wybieramy &gui.yes; i naciskamy <keycap>Enter</keycap>. Przez chwilê bêdzie
         siê odbywaæ poszukiwanie serwerów <acronym>RA</acronym>.</para>
 
       <screen>                             User Confirmation Requested
         Do you want to try DHCP configuration of the interface?
 
                               Yes   [ No ]</screen>
 
       <para>Je¿eli nie wykorzystujemy DHCP (Dynamic Host Configuration Protocol),
         wybieramy klawiszami kursora &gui.no; i wciskamy
         <keycap>Enter</keycap>.</para>
 
       <para>Wybranie &gui.yes; spowoduje uruchomienie <application>dhclient</application>
         i je¶li wszystko przebiegnie prawid³owo, konfiguracja sieci zostanie rozpoznana
         automatycznie. <xref linkend="network-dhcp"/> zawiera szczegó³owe informacje
         na ten temat.</para>
 
       <para>Przedstawiony poni¿ej ekran konfiguracji sieci (Network Configuration)
         przedstawia konfiguracjê karty sieciowej komputera, który bêdzie s³u¿y³
         jako brama w sieci lokalnej.</para>
 
       <figure id="ed-config2">
         <title>Konfiguracja interfejsu ed0</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ed0-conf2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawiszem <keycap>Tab</keycap> wybieramy poszczególne pola, w których
         wpisujemy odpowiednie informacje:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>Host (stacja)</term>
 
 	  <listitem>
             <para>Pe³na nazwa stacji, w powy¿szym przyk³adzie
               <hostid role="fqdn">k6-2.example.com</hostid>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Domain (domena)</term>
 
 	  <listitem>
             <para>Nazwa domeny, do której nale¿y stacja, w przyk³adzie jest to
               <hostid role="domainname">example.com</hostid>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>IPv4 Gateway (brama IPv4)</term>
 
 	  <listitem>
 	    <para>Adres IP stacji przekazuj±cej pakiety do odbiorców spoza
               sieci lokalnej. Musi byæ podany, je¶li komputer jest wêz³em
               w sieci. Je¿eli komputer pe³ni rolê bramy do Internetu w sieci
               lokalnej, pole to nale¿y <emphasis>pozostawiæ puste</emphasis>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
           <term>Name server (serwer nazw)</term>
 
 	  <listitem>
             <para>Adres IP lokalnego serwera DNS. W przyk³adowej sieci
               lokalnej nie ma serwera DNS, wpisany wiêc zosta³ adres serwera DNS
               dostawcy Internetu (<hostid role="ipaddr">208.163.10.2</hostid>).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
           <term>IPv4 address (adres IPv4)</term>
 
 	  <listitem>
             <para>W przyk³adzie temu interfejsowi przypisano adres
 	      <hostid role="ipaddr">192.168.0.1</hostid>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
           <term>Netmask (maska podsieci)</term>
 
 	  <listitem>
             <para>W sieci lokalnej u¿yty zosta³ dla przyk³adu blok
               adresów klasy C
               (<hostid role="ipaddr">192.168.0.0</hostid> -
 	      <hostid role="ipaddr">192.168.0.255</hostid>).
               Maska podsieci jest mask± sieci klasy C
 	      (<hostid role="netmask">255.255.255.0</hostid>).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
           <term>Extra options to ifconfig (dodatkowe opcje dla ifconfig)</term>
 
 	  <listitem>
             <para>Tu wpisywane s± dodatkowe opcje dla <command>ifconfig</command>
               charakterystyczne dla interfejsu. W pokazanym przyk³adzie nie by³o
               takowych opcji.</para>
 	  </listitem>
 	</varlistentry>
 
       </variablelist>
 
       <para>Gdy konfiguracja bêdzie gotowa, klawiszem <keycap>Tab</keycap>
         wybieramy &gui.ok; i naciskamy <keycap>Enter</keycap>.</para>
 
 
       <screen>                      User Confirmation Requested
         Would you like to Bring Up the ed0 interface right now?
 
                              [ Yes ]   No</screen>
 
       <para>Je¶li wybierzemy &gui.yes; i wci¶niemy
         <keycap>Enter</keycap>, komputer zostanie aktywowany
         do pracy w sieci.</para>
     </sect2>
 
     <sect2 id="gateway">
       <title>Konfiguracja bramy</title>
 
       <screen>                       User Confirmation Requested
        Do you want this machine to function as a network gateway?
 
                               [ Yes ]    No</screen>
 
       <para>Je¶li komputer bêdzie w sieci lokalnej pe³niæ rolê bramy,
         czyli bêdzie przekazywaæ pakiety pomiêdzy innymi komputerami,
         wybieramy opcjê &gui.yes; i naciskamy <keycap>Enter</keycap>.
         Je¿eli natomiast komputer bêdzie wêz³em w sieci, wybieramy
         &gui.no; i równie¿ wciskamy <keycap>Enter</keycap>.</para>
     </sect2>
 
     <sect2 id="inetd-services">
       <title>Konfiguracja us³ug internetowych</title>
 
       <screen>                      User Confirmation Requested
 Do you want to configure inetd and the network services that it provides?
 
                                Yes   [ No ]</screen>
 
       <para>Wybranie &gui.no; spowoduje, ¿e wiele us³ug (jak np.
         <application>telnetd</application>) bêd± wy³±czone. Oznacza
         to, ¿e zdalni u¿ytkownicy nie bêd± mogli po³±czyæ siê z naszym
         komputerem za pomoc± <application>telnetu</application>.  U¿ytkownicy
         lokalni bêd± natomiast mogli ³±czyæ siê z odleg³ymi komputerami
         korzystaj±c z <application>telnetu</application>.</para>
 
       <para>Us³ugi mo¿emy w³±czyæ po zainstalowaniu systemu, aby to zrobiæ,
         modyfikujemy plik <filename>/etc/inetd.conf</filename> za pomoc±
         edytora tekstu. Wiêcej informacji znale¼æ mo¿na w Sekcji 25.2.1.
 	<xref linkend="network-inetd-overview"/>.</para>
 
       <para>Je¶li woleliby¶my skonfigurowaæ us³ugi internetowe podczas
         instalacji, wybieramy &gui.yes;. Zostaniemy poproszeni o dodatkowe
         potwierdzenie:</para>
 
       <screen>                      User Confirmation Requested
 The Internet Super Server (inetd) allows a number of simple Internet
 services to be enabled, including finger, ftp and telnetd.  Enabling
 these services may increase risk of security problems by increasing
 the exposure of your system.
 
 With this in mind, do you wish to enable inetd?
 
                              [ Yes ]   No</screen>
 
       <para>Wybieramy &gui.yes;, by przej¶æ dalej.</para>
 
       <screen>                      User Confirmation Requested
 inetd(8) relies on its configuration file, /etc/inetd.conf, to determine
 which of its Internet services will be available.  The default FreeBSD
 inetd.conf(5) leaves all services disabled by default, so they must be
 specifically enabled in the configuration file before they will
 function, even once inetd(8) is enabled.  Note that services for
 IPv6 must be separately enabled from IPv4 services.
 
 Select [Yes] now to invoke an editor on /etc/inetd.conf, or [No] to
 use the current settings.
 
                              [ Yes ]   No</screen>
 
       <para>Wybranie &gui.yes; pozwoli na w³±czanie poszczególnych
         us³ug poprzez usuniêcie znaku <literal>#</literal> na pocz±tku
         w³a¶ciwego wiersza.</para>
 
       <figure id="inetd-edit">
         <title>Modyfikacja <filename>inetd.conf</filename></title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/edit-inetd-conf"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Gdy w³±czymy wybrane us³ugi, naciskamy <keycap>Esc</keycap>
         by przej¶æ do menu, w którym bêdziemy mogli zakoñczyæ
         modyfikowanie pliku i zapisaæ zmiany.</para>
 
     </sect2>
 
     <sect2 id="ftpanon">
       <title>Anonimowe FTP</title>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>anonimowe</secondary>
       </indexterm>
 
       <screen>                      User Confirmation Requested
  Do you want to have anonymous FTP access to this machine?
 
                               Yes    [ No ]</screen>
 
       <sect3 id="deny-anon">
         <title>Wy³±czenie anonimowego FTP</title>
 
         <para>Wybranie zaznaczonego domy¶lnie &gui.no; pozwoli na dostêp
           do komputera poprzez FTP tylko tym u¿ytkownikom, którzy maj±
           w³asne konta chronione has³em.</para>
       </sect3>
 
       <sect3 id="ftpallow">
         <title>W³±czenie anonimowego FTP</title>
 
         <para>W³±czenie anonimowego FTP oznacza, ¿e ka¿dy bêdzie
           móg³ uzyskaæ dostêp do komputera. Zanim siê na to zdecydujemy,
           powinni¶my byæ ¶wiadomi niebezpieczeñstwa, które siê z tym
           wi±¿e. <xref linkend="security"/> zawiera wiêcej informacji
           na temat bezpieczeñstwa.</para>
 
         <para>Aby w³±czyæ anonimowe FTP, klawiszami kursora wybieramy
           &gui.yes; i naciskamy <keycap>Enter</keycap>.
           Ekran bêdzie wygl±daæ jak na poni¿szym rysunku (lub podobnie):</para>
 
 	<figure id="anon-ftp2">
           <title>Domy¶lne ustawienia anonimowego FTP</title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/ftp-anon1"/>
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
         <para>Mo¿emy nacisn±æ <keycap>F1</keycap>, by uzyskaæ pomoc:</para>
 
 	<screen>This screen allows you to configure the anonymous FTP user.
 
 The following configuration values are editable:
 
 UID:     The user ID you wish to assign to the anonymous FTP user.
          All files uploaded will be owned by this ID.
 
 Group:   Which group you wish the anonymous FTP user to be in.
 
 Comment: String describing this user in /etc/passwd
 
 
 FTP Root Directory:
 
         Where files available for anonymous FTP will be kept.
 
 Upload subdirectory:
 
         Where files uploaded by anonymous FTP users will go.</screen>
 
 	<para>G³ówny katalog ftp jest domy¶lnie umieszczany
           w <filename>/var</filename>. Je¿eli nie mamy tam
           wystarczaj±co du¿o miejsca dla przewidywanych potrzeb
           FTP, mo¿emy wybraæ w zamian katalog <filename>/usr</filename>,
           jako g³ówny katalog FTP (FTP Root Directory) wpisuj±c
 	  <filename>/usr/ftp</filename>.</para>
 
         <para>Po wybraniu odpowiadaj±cych nam ustawieñ naciskamy
 	  <keycap>Enter</keycap>.</para>
 
 	<screen>                          User Confirmation Requested
          Create a welcome message file for anonymous FTP users?
 
                               [ Yes ]    No</screen>
 
 	<para>Je¿eli wybierzemy &gui.yes; i wci¶niemy
           <keycap>Enter</keycap>, automatycznie zostanie
           uruchomiony edytor, w którym bêdziemy mogli napisaæ
           komunikat powitalny dla u¿ytkowników anonimowego
           FTP.</para>
 
 	<figure id="anon-ftp4">
           <title>Edycja komunikatu powitalnego FTP</title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/ftp-anon2"/>
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
         <para>U¿ywanym tutaj edytorem tekstu jest <command>ee</command>.
           Postêpuj±c zgodnie z przedstawionymi na ekranie wskazówkami
           mo¿emy wprowadziæ tre¶æ komunikatu, lub te¿ mo¿emy zrobiæ to pó¼niej,
           korzystaj±c z dowolnego edytora. W tym celu warto jest zapisaæ nazwê
           i lokalizacjê pliku pokazywan± na dole ekranu.</para>
 
         <para>Gdy naci¶niemy <keycap>Esc</keycap> pokazane zostanie menu
           z domy¶lnie zaznaczon± opcj± <guimenuitem>a) leave editor</guimenuitem>.
           (opuszczenie edytora). Wybieramy j± naciskaj±c
 	  <keycap>Enter</keycap>. Ponowne naci¶niêcie
 	  <keycap>Enter</keycap> spowoduje zapisanie zmian je¶li jakich¶
           dokonali¶my.</para>
       </sect3>
     </sect2>
 
     <sect2 id="nfsconf">
       <title>Konfiguracja sieciowych us³ug plikowych</title>
 
       <para>Sieciowe us³ugi plikowe (Network File Services - NFS)
         pozwalaj± na wspó³dzielony dostêp do plików przez sieæ.
         Komputer mo¿emy skonfigurowaæ jako serwer, klient, lub oba
         naraz. Wiêcej informacji na ten temat mo¿na znale¼æ w
         <xref linkend="network-nfs"/>.</para>
 
       <sect3 id="nsf-server-options">
         <title>Serwer NFS</title>
 
 	<screen>                       User Confirmation Requested
  Do you want to configure this machine as an NFS server?
 
                               Yes    [ No ]</screen>
 
 	<para>Je¶li nie zamierzamy korzystaæ z serwera NFS,
           wybieramy &gui.no; i wciskamy
 	  <keycap>Enter</keycap>.</para>
 
         <para>W przeciwnym wypadku, gdy wybierzemy &gui.yes;, zostanie
           pokazany komunikat o konieczno¶ci stworzenia pliku
 	  <filename>exports</filename>.</para>
 
 	<screen>                               Message
 Operating as an NFS server means that you must first configure an
 /etc/exports file to indicate which hosts are allowed certain kinds of
 access to your local filesystems.
 Press [Enter] now to invoke an editor on /etc/exports
                                [ OK ]</screen>
 
 	<para>Naciskamy <keycap>Enter</keycap>.  Zostanie uruchomiony
           edytor tekstu, w którym bêdziemy mogli przygotowaæ plik
 	  <filename>exports</filename>.</para>
 
 	<figure id="nfs-server-edit">
 	  <title>Edycja pliku <filename>exports</filename></title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/nfs-server-edit"/>
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
         <para>Zgodnie ze wskazówkami dopisujemy udostêpniane systemy
           plików. Mo¿emy tak¿e zrobiæ to pó¼niej, korzystaj±c
           z preferowanego przez nas edytora tekstu. W tym celu warto
           zapisaæ sobie pokazywan± na dole ekranu nazwê i lokalizacjê
           pliku.</para>
 
         <para>Gdy naci¶niemy <keycap>Esc</keycap>, pokazane zostanie menu
           z domy¶lnie zaznaczon± opcj±
           <guimenuitem>a) leave editor</guimenuitem> (opuszczenie edytora).
           Wybieramy j± naciskaj±c <keycap>Enter</keycap>.</para>
       </sect3>
 
       <sect3 id="nfs-client-options">
 	<title>Klient NFS</title>
 
 	<para>Instalacja klienta NFS pozwoli naszemu komputerowi ³±czyæ siê z serwerami NFS.</para>
 
 	<screen>                       User Confirmation Requested
  Do you want to configure this machine as an NFS client?
 
                               Yes   [ No ]</screen>
 
 	<para>Wybieramy klawiszami kursora &gui.yes; lub
 	  &gui.no; zale¿enie od podjêtej decyzji, po czym
           naciskamy <keycap>Enter</keycap>.</para>
       </sect3>
     </sect2>
 
     <sect2 id="securityprofile">
       <title>Profil zabezpieczeñ</title>
 
       <para><quote>Profil zabezpieczeñ</quote> to zestaw opcji
         konfiguracyjnych, maj±cy zapewniæ okre¶lony poziom
         bezpieczeñstwa poprzez w³±czenie i wy³±czenie pewnych
         programów i ustawieñ. Im surowszy profil zabezpieczeñ,
         tym mniej programów bêdzie domy¶lnie uruchamianych.
         Odpowiada to jednej z podstawowych zasad bezpieczeñstwa:
         nale¿y wy³±czaæ wszystko, co nie musi byæ w³±czone.</para>
 
       <para>Pamiêtajmy, ¿e profil zabezpieczeñ to tylko domy¶lne
         ustawienia. Poszczególne programy mo¿na w³±czaæ i wy³±czaæ
         ju¿ po zainstalowaniu FreeBSD, poprzez modyfikacjê lub dodanie
         odpowiednich wpisów w pliku <filename>/etc/rc.conf</filename>.
         Dalsze informacje na ten temat znale¼æ mo¿na w dokumentacji
         systemowej &man.rc.conf.5;.</para>
 
       <para>Poni¿sza tabela pokazuje, jaki jest efekt stosowania
         ka¿dego z profili zabezpieczeñ. Kolumny odpowiadaj± profilom,
         które mo¿na wybraæ, natomiast w kolejnych wierszach wymienione
         s± poszczególne programy lub funkcje w³±czone lub wy³±czone
         w danym profilu.</para>
 
       <table>
         <title>Dostêpne profile zabezpieczeñ</title>
 
 	<tgroup cols="3">
 	  <thead>
 	    <row>
 	      <entry></entry>
 
 	      <entry>Extreme</entry>
 
 	      <entry>Medium</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 
 	    <row>
 	      <entry>&man.sendmail.8;</entry>
 
 	      <entry>NIE</entry>
 
 	      <entry>TAK</entry>
 	    </row>
 
 	    <row>
 	      <entry>&man.sshd.8;</entry>
 
 	      <entry>NIE</entry>
 
 	      <entry>TAK</entry>
 	    </row>
 
 	    <row>
 	      <entry>&man.portmap.8;</entry>
 
 	      <entry>NIE</entry>
 
-	      <entry>MO¯E
-		<footnote>
-                  <para>Portmapper jest w³±czony, je¶li na wcze¶niejszym
+	      <entry>MO¯E (Portmapper jest w³±czony, je¶li na wcze¶niejszym
                     etapie instalacji komputer zosta³ skonfigurowany jako
-                    klient lub serwer NFS.</para>
-		</footnote>
+                    klient lub serwer NFS.)
 	      </entry>
 	    </row>
 
 	    <row>
 	      <entry>serwer NFS</entry>
 
 	      <entry>NIE</entry>
 
 	      <entry>TAK</entry>
 	    </row>
 
 	    <row>
 	      <entry>&man.securelevel.8;</entry>
 
-	      <entry>TAK
-		<footnote>
-                  <para>Wybieraj±c profil zabezpieczeñ, który
+	      <entry>TAK (Wybieraj±c profil zabezpieczeñ, który
                     powoduje ustawienie securelevel
                     na <quote>Extreme</quote> lub <quote>High</quote>,
                     powinni¶my pamiêtaæ o konsekwencjach. Warto przeczytaæ
                     dokumentacjê systemow± &man.init.8; i zwróciæ szczególn±
                     uwagê na znaczenie poziomów bezpieczeñstwa, by unikn±æ
-                    pó¼niejszych k³opotów!</para>
-		</footnote>
+                    pó¼niejszych k³opotów!)
 	      </entry>
 
 	      <entry>NIE</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <screen>                       User Confirmation Requested
  Do you want to select a default security profile for this host (select
  No for "medium" security)?
 
                             [ Yes ]    No</screen>
 
       <para>Je¿eli wybierzemy &gui.no; i naci¶niemy
         <keycap>Enter</keycap>, zostanie ustawiony ¶redni profil
         zabezpieczeñ.</para>
 
       <para>Chc±c wybraæ inny profil zabezpieczeñ, wybieramy &gui.yes;
         i wciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="security-profile">
         <title>Opcje profilu zabezpieczeñ</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/security"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Aby uzyskaæ pomoc, wciskamy <keycap>F1</keycap>. Naciskaj±c
         <keycap>Enter</keycap> wracamy do menu.</para>
 
       <para>Klawiszami kursora wybieramy <guimenuitem>Medium</guimenuitem>,
         chyba, ¿e jeste¶my pewni, ¿e bêdziemy potrzebowaæ innego poziomu
         bezpieczeñstwa. Wskazujemy nastêpnie
         &gui.ok; i wciskamy
 	<keycap>Enter</keycap>.</para>
 
       <para>Zostanie wy¶wietlony komunikat potwierdzaj±cy wybór profilu
         zabezpieczeñ.</para>
 
       <screen>                                 Message
 
 Moderate security settings have been selected.
 
 Sendmail and SSHd have been enabled, securelevels are
 disabled, and NFS server setting have been left intact.
 PLEASE NIETE that this still does not save you from having
 to properly secure your system in other ways or exercise
 due diligence in your administration, this simply picks
 a standard set of out-of-box defaults to start with.
 
 To change any of these settings later, edit /etc/rc.conf
 
                                   [OK]</screen>
 
       <screen>                                 Message
 
 Extreme security settings have been selected.
 
 Sendmail, SSHd, and NFS services have been disabled, and
 securelevels have been enabled.
 PLEASE NIETE that this still does not save you from having
 to properly secure your system in other ways or exercise
 due diligence in your administration, this simply picks
 a more secure set of out-of-box defaults to start with.
 
 To change any of these settings later, edit /etc/rc.conf
 
                                   [OK]</screen>
 
       <para>Naciskamy <keycap>Enter</keycap>, aby przej¶æ
         do kolejnego etapu konfiguracji.</para>
 
       <warning>
         <para> Profil zabezpieczeñ nie jest cudownym lekarstwem!
           Nawet, je¶li wybrali¶my najbardziej bezpieczny profil,
           musimy na bie¿±co interesowaæ siê sprawami bezpieczeñstwa
           systemu, czytaj±c po¶wiêcone im listy dyskusyjne
           (<xref linkend="eresources-mail"/>),, stosuj±c
           dobre has³a i przestrzegaj±c ogólnych zasad bezpieczeñstwa.
           Profil jest tylko wygodnym sposobem na przygotowanie
           podstawowych zabezpieczeñ.</para>
       </warning>
 
     </sect2>
 
     <sect2 id="console">
       <title>Ustawienia konsoli systemowej</title>
 
       <para>Kilka opcji s³u¿y do konfiguracji konsoli systemowej.</para>
 
       <screen>                      User Confirmation Requested
        Would you like to customize your system console settings?
 
                               [ Yes ]  No</screen>
 
       <para>Aby zobaczyæ i zmieniæ ustawienia, wybieramy
         &gui.yes; i wciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="saver-options">
         <title>Opcje konfiguracji konsoli systemowej</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Czêsto stosowan± opcj± jest wygaszacz ekranu (screen saver).
         Klawiszami kursora wybieramy <guimenuitem>Saver</guimenuitem>
         i naciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="saver-select">
         <title>Opcje wygaszacza ekranu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Za pomoc± klawiszy kursora wybieramy odpowiadaj±cy nam
         wygaszacz i wciskamy <keycap>Enter</keycap>.  Ponownie pojawi
         siê menu konfiguracji konsoli systemowej.</para>
 
       <para>Przyjmowany domy¶lnie przedzia³ czasu wynosi 300 sekund.
         Aby go zmieniæ, ponownie wybieramy <guimenuitem>Saver</guimenuitem>.
         W menu opcji wygaszacza ekranu klawiszami kursora wybieramy
         <guimenuitem>Timeout</guimenuitem> i naciskamy <keycap>Enter</keycap>.
         Pojawi siê okienko:</para>
 
       <figure id="saver-timeout">
         <title>Limit czasu wygaszacza ekranu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Warto¶æ mo¿emy zmieniæ, po czym wybieramy &gui.ok;
         i wciskamy <keycap>Enter</keycap>, by wróciæ do menu
         konfiguracji konsoli.</para>
 
       <figure id="saver-exit">
         <title>Zakoñczenie konfiguracji konsoli</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver4"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Wybieramy <guimenuitem>Exit</guimenuitem> i naciskamy
         <keycap>Enter</keycap>, przechodz±c do kolejnego etapu
         konfiguracji.</para>
     </sect2>
 
     <sect2 id="timezone">
       <title>Ustawienia strefy czasowej</title>
 
       <para>Dziêki ustawieniu strefy czasowej komputer bêdzie móg³
         automatycznie ustawiaæ zegar w przypadku zmiany czasu,
         jak równie¿ bêdzie prawid³owo wykonywaæ inne czynno¶ci
         zwi±zane ze stref± czasow±.</para>
 
       <para>W przyk³adzie mamy do czynienia z komputerem
         znajduj±cym siê we wschodniej strefie czasowej Stanów
         Zjednoczonych. Rzeczywiste ustawienia bêd± zale¿eæ
         od naszego po³o¿enia geograficznego.</para>
 
       <screen>                      User Confirmation Requested
           Would you like to set this machine's time zone now?
 
                             [ Yes ]   No</screen>
 
       <para>By ustawiæ strefê czasow±, wybieramy &gui.yes;
         i naciskamy <keycap>Enter</keycap>.</para>
 
       <screen>                       User Confirmation Requested
  Is this machine's CMOS clock set to UTC? If it is set to local time
  or you don't know, please choose NIE here!
 
                               Yes   [ No ]</screen>
 
       <para>Wybieramy &gui.yes; lub &gui.no;,
         w zale¿no¶ci od ustawienia zegara komputera, nastêpnie
         wciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="set-timezone-region">
         <title>Wybór regionu geograficznego</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawiszami kursora wybieramy odpowiedni region,
         po czym naciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="set-timezone-country">
         <title>Wybór kraju</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Przy u¿yciu klawiszy kursora wybieramy odpowiedni kraj
         i naciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="set-timezone-locality">
         <title>Wybór strefy czasowej</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawiszami kursora wybieramy w³a¶ciw± strefê czasow±
         i wciskamy <keycap>Enter</keycap>.</para>
 
       <screen>                            Confirmation
             Does the abbreviation 'EDT' look reasonable?
 
                             [ Yes ]   No</screen>
 
       <para>Zostaniemy zapytani, czy skrót nazwy strefy
         czasowej jest prawid³owy. Je¶li tak, naciskamy
         <keycap>Enter</keycap> i przechodzimy do kolejnego
         etapu konfiguracji.</para>
     </sect2>
 
     <sect2 id="linuxcomp">
       <title>Kompatybilno¶æ z Linuksem</title>
 
       <screen>                      User Confirmation Requested
           Would you like to enable Linux binary compatibility?
 
                             [ Yes ]   No</screen>
 
       <para>Wybranie &gui.yes; i naci¶niêcie
         <keycap>Enter</keycap> pozwoli uruchamiaæ programy
         linuksowe we FreeBSD. Program instalacyjny do³±czy
         pakiety obs³uguj±ce kompatybilno¶æ z Linuksem.</para>
 
       <para>Je¶li instalujemy system przez FTP, komputer bêdzie
         potrzebowaæ ³±czno¶ci z Internetem. Mo¿e siê zdarzyæ,
         ¿e na serwerze ftp bêdzie brakowa³o pewnych sk³adników,
         na przyk³ad obs³uguj±cych kompatybilno¶æ z Linuksem.
         Mo¿na je jednak zainstalowaæ pó¼niej.</para>
     </sect2>
 
     <sect2 id="mouse">
       <title>Ustawienia myszki</title>
 
       <para>Pos³uguj±c siê 3-przyciskow± myszk± bêdziemy mogli wycinaæ
         i wklejaæ tekst na konsoli i w uruchamianych programach. Je¶li
         nasza myszka ma dwa przyciski, po instalacji zajrzyjmy do dokumentacji
         systemowej &man.moused.8;, gdzie opisana zosta³a emulacja trzech
         przycisków. W naszym przyk³adzie konfigurujemy myszkê nie pod³±czon±
         przez USB (np. przez z³±cze PS/2 lub port COM)::</para>
 
       <screen>                      User Confirmation Requested
          Does this system have a non-USB mouse attached to it?
 
                             [ Yes ]    No </screen>
 
       <para>Wybieramy &gui.no;, je¶li myszka pod³±czona jest
         przez USB, lub &gui.yes; w przeciwnym wypadku i
         naciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="mouse-protocol">
         <title>Opcja wyboru protoko³u myszki</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawiszami kursora wskazujemy <guimenuitem>Type</guimenuitem>
         i naciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="set-mouse-protocol">
         <title>Wybór protoko³u myszki</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Myszka u¿ywana w przyk³adzie jest typu PS/2, wybrano
         wiêc domy¶ln± opcjê <guimenuitem>Auto</guimenuitem>.
         Inny protokó³ wybieramy wskazuj±c odpowiedni± opcjê klawiszami
         kursora. Upewniwszy siê, ¿e &gui.ok; jest zaznaczone, naciskamy
         <keycap>Enter</keycap> i wracamy do poprzedniego menu.</para>
 
       <figure id="config-mouse-port">
         <title>Konfiguracja portu myszki</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Za pomoc± klawiszy kursora wybieramy <guimenuitem>Port</guimenuitem>
         i wciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="set-mouse-port">
         <title>Wybór portu myszki</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse4"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Poniewa¿ przyk³adowa myszka jest typu PS/2, zaznaczona
         zosta³a domy¶lna opcja <guimenuitem>PS/2</guimenuitem>.
         Klawiszami kursora mo¿emy wybraæ port, nastêpnie naciskamy
         <keycap>Enter</keycap>.</para>
 
       <figure id="test-daemon">
         <title>W³±czenie demona myszki</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse5"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Na koniec wybieramy <guimenuitem>Enable</guimenuitem>
         i naciskamy <keycap>Enter</keycap> by w³±czyæ
         demona myszki i go przetestowaæ.</para>
 
 
       <figure id="test-mouse-daemon">
         <title>Testowanie demona myszki</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse6"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Nastêpnie musimy poruszyæ myszk± i sprawdziæ czy
         kursor porusza siê we w³a¶ciwy sposób po ekranie.
         Je¶li tak to wybieramy &gui.yes; i wciskamy <keycap>Enter</keycap>.
         Je¶li nie myszka nie zosta³a w³a¶ciwie skonfigurowana &mdash;
         wybieramy &gui.no; i próbujemy innych ustawieñ myszy.</para>
 
       <para>Wybieramy <guimenuitem>Exit</guimenuitem> i wciskamy
         <keycap>Enter</keycap>, by zakoñczyæ ten etap
         konfiguracji.</para>
     </sect2>
 
     <sect2 id="network-services">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>Tom</firstname>
             <surname>Rhodes</surname>
             <contrib>Napisa³ </contrib>
           </author>
         </authorgroup>
       </sect2info>
       <title>Konfiguracja dodatkowych us³ug sieciowych</title>
 
       <para>Konfiguracja us³ug sieciowych mo¿e byæ nu¿±cym zadaniem
 	dla pocz±tkuj±cych u¿ytkowników, szczególnie je¶li brak im
         wiedzy w tym zakresie. Mo¿liwo¶æ pracy w sieci - tak¿e w Internecie -
 	jest kluczowym elementem wszystkich wspó³czesnych systemów
 	operacyjnych, w tym równie¿ &os;. St±d te¿ jest bardzo
 	pomocnym mieæ pojêcie o mo¿liwo¶ciach pracy w sieci jakie oferuje &os;.
 	Poznanie tych jego mo¿liwo¶ci ju¿ w trakcie instalacji pozwoli
 	u¿ytkownikom zrozumieæ ró¿ne aspekty funkcjonowania
         us³ug sieciowych.</para>
 
       <para>Us³ugi sieciowe s± programami potrafi±cymi przyjmowaæ dane
         z dowolnej lokalizacji w sieci.  Dlatego w³a¶nie dok³adanych jest
         wiele starañ, by zagwarantowaæ, ¿e programy te nie uczyni± nic
         <quote>szkodliwego</quote>.  Niestety, programi¶ci nie s±
         doskonali.  W przesz³o¶ci zdarza³y siê sytuacje, w których
         atakuj±cy wykorzystywali b³êdy w oprogramowaniu by wyrz±dziæ
         szkodê systemowi.  St±d te¿ jest bardzo istotnym by w³±czaæ
         tylko te us³ugi sieciowe, które s± nam potrzebne. Je¶li nie
         jeste¶my pewni, najlepiej jest nie w³±czaæ danej us³ugi nim
         nie dowiemy siê czy rzeczywi¶cie jej potrzebujemy. Zawsze mo¿emy
         j± aktywowaæ pó¼niej uruchamiaj±c ponownie
         <application>sysinstall</application> b±d¼ edytuj±c plik
         <filename>/etc/rc.conf</filename>.</para>
 
       <para>Wybranie opcji <guimenu>Networking</guimenu> spowoduje wy¶wietlenie
         menu zbli¿onego do poni¿szego:</para>
 
       <figure id="network-configuration">
 	<title>Najwy¿szy poziom konfiguracji sieci</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/net-config-menu1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Pierwsz± z dostêpnych opcji - <guimenuitem>Interfaces</guimenuitem> -
         opisuje bli¿ej <xref linkend="inst-network-dev"/>, dlatego te¿ mo¿emy
         j± teraz pomin±æ.</para>
 
       <para>Wybór opcji <guimenuitem>AMD</guimenuitem> w³±czy wsparcie dla
         narzêdzia automatycznego montowania BSD (ang. Automatic Mount Utility).
         Opcja ta najczê¶ciej jest wykorzystywana z protoko³em
         <acronym>NFS</acronym> (patrz poni¿ej) do automatycznego montowania
         zdalnych systemów plików. Nie wymaga dodatkowej konfiguracji.</para>
 
       <para>Kolejn± opcj± jest <guimenuitem>AMD Flags</guimenuitem>.
         Po jej wybraniu pojawi siê menu, gdzie nale¿y wprowadziæ specyficzne
         flagi AMD. Menu zawiera ju¿ domy¶lne warto¶ci:</para>
 
       <screen>-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map</screen>
 
       <para>Flaga <option>-a</option> okre¶la domy¶lny punkt montowania,
         w tym wypadku <filename>/.amd_mnt</filename>.  Flaga <option>-l</option>
         definiuje domy¶lny plik <filename>log</filename> dziennika systemowego;
         je¶li w systemie wykorzystywany jest demon <literal>syslogd</literal>,
         wówczas wszystkie komunikaty bêd± wysy³ane w³a¶nie do niego.  Katalog
         <filename class="directory">/host</filename> jest wykorzystywany do
         montowania systemów plików wyeksportowanych ze zdalnej maszyny, podczas
         gdy katalog <filename class="directory">/net</filename> do
         montowania systemów plików z adresu <acronym>IP</acronym>.
         Plik <filename>/etc/amd.map</filename> zawiera domy¶lne warto¶ci
         flag dla zasobów eksportowanych przez <acronym>AMD</acronym>.</para>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>anonimowe</secondary>
       </indexterm>
 
       <para>Wybór opcji <guimenuitem>Anon FTP</guimenuitem> zezwala na anonimowe
         po³±czenia <acronym>FTP</acronym>, tym samym tworz±c z naszego komputera
         anonimowy serwer <acronym>FTP</acronym>. Nale¿y mieæ jednak ¶wiadomo¶æ
         niebezpieczeñstw jakie poci±ga za sob± taka konfiguracja. Po wybraniu
         tej opcji pojawi siê kolejne okienko wyja¶niaj±ce zwi±zane z ni±
         niebezpieczeñstwa oraz umo¿liwiaj±ce szczegó³ow± konfiguracjê.</para>
 
       <para>Menu <guimenuitem>Gateway</guimenuitem> pozwala skonfigurowaæ
         nasz± maszynê jako bramê, co zosta³o opisane wcze¶niej. Mo¿e byæ
         równie¿ wykorzystane do wy³±czenia tej opcji je¶li przypadkowo
         zosta³a ona aktywowana w trakcie instalacji.</para>
 
       <para>Opcja <guimenuitem>Inetd</guimenuitem> pozwala skonfigurowaæ
         b±d¼ ca³kowicie wy³±czyæ demonona &man.inetd.8;, który równie¿
         zosta³ opisany wcze¶niej.</para>
 
       <para>Opcja <guimenuitem>Mail</guimenuitem> wykorzystywana jest do
         konfiguracji domy¶lnego systemowego serwera poczty <acronym>MTA</acronym>
         (ang. Mail Transfer Agent). Wybór tej opcji spowoduje wy¶wietlenie
         nastêpuj±cego menu:</para>
 
       <figure id="mta-selection">
 	<title>Wybór domy¶lnego MTA</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mta-main"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>W menu tym mamy mo¿liwo¶æ wyboru, który <acronym>MTA</acronym>
         zostanie zainstalowany jako domy¶lny.  W praktyce
         <acronym>MTA</acronym> nie jest niczym wiêcej jak serwerem,
         który dostarcza pocztê elektroniczn± do u¿ytkowników lokalnego
         systemu b±d¼ wysy³a j± do Internetu.</para>
 
       <para>Wybór opcji <guimenuitem>Sendmail</guimenuitem> spowoduje
         instalacjê popularnego serwera <application>sendmail</application>.
         Serwer ten jest domy¶lnym serwerem we &os;. Opcja <guimenuitem>Sendmail
           local</guimenuitem> równie¿ spowoduje wybór <application>sendmail</application>
         jako domy¶lnego <acronym>MTA</acronym>, jednak¿e bez mo¿liwo¶ci odbierania
         poczty przychodz±cej z Internetu. Pozosta³e opcje <guimenuitem>Postfix</guimenuitem>
         i <guimenuitem>Exim</guimenuitem> daj± efekt analogiczny do
         <guimenuitem>Sendmail</guimenuitem> &mdash; obydwa rozwi±zania dostarczaj± pocztê.
         Tym nie mniej, niektórzy u¿ytkownicy preferuj± te serwery jako alternatywê dla
         <acronym>MTA</acronym> <application>sendmail</application>.</para>
 
       <para>Po wybraniu <acronym>MTA</acronym>, b±d¼ pominiêciu tego kroku, pojawi siê
         ponownie okno konfiguracji sieci z kolejn± opcj±: <guimenuitem>NFS
         client</guimenuitem>.</para>
 
       <para>Opcja <guimenuitem>NFS client</guimenuitem> pozwala skonfigurowaæ
         system do komunikacji z serwerem za pomoc± <acronym>NFS</acronym>.
         Serwer <acronym>NFS</acronym> udostêpnia systemy plików innym maszynom
         w sieci za pomoc± protoko³u <acronym>NFS</acronym>. Je¶li nasza maszyna
         nie bêdzie pracowa³a w sieci mo¿na t± opcjê pomin±æ. System mo¿e pó¼niej
         wymagaæ dalszej konfiguracji. <xref linkend="network-nfs"/> zawiera
         szczegó³owe informacje o konfiguracji klienta i serwera
         <acronym>NFS</acronym>.</para>
 
       <para>Poni¿ej znajduje siê opcja <guimenuitem>NFS server</guimenuitem>
         umo¿liwiaj±ca skonfigurowanie systemu jako serwer <acronym>NFS</acronym>.
         Dodatkowo konfiguruje ona wymagane parametry dla us³ug <acronym>RPC</acronym>.
         <acronym>RPC</acronym> koordynuje po³±czenia pomiêdzy maszynami
         i programami.</para>
 
       <para>Kolejna opcja to <guimenuitem>Ntpdate</guimenuitem>, odpowiadaj±ca za
         synchronizacjê czasu systemowego. Po wybraniu jej pojawi siê nastêpuj±ce
         menu:</para>
 
       <figure id="Ntpdate-config">
         <title>Konfiguracja ntpdate</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ntp-config"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Z menu wybieramy najbli¿szy nam serwer.  Wybór pobliskiego serwera gwarantuje
         dok³adniejsz± synchronizacjê czasu, z uwagi na fakt, ¿e w komunikacji z bardziej oddalony
         serwerem mog± wystêpowaæ wiêksze opó¼nienia.</para>
 
       <para>Kolejnym elementem jest wybór <acronym>PCNFSD</acronym>.  Opcja ta zainstaluje
         <filename role="package">net/pcnfsd</filename> z Kolekcji portów.  Jest to przydatne
         narzêdzie umo¿liwiaj±ce uwierzytelnianie NFS systemom operacyjnym, które same nie potrafi± siê
         uwierzytelniæ, jak np. &ms-dos;.</para>
 
       <para>Przewijaj±c w dó³ pojawi± siê kolejne opcje:</para>
 
       <figure id="Network-configuration-cont">
         <title>Najni¿szy poziom konfiguracji sieci</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/net-config-menu2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Programy &man.rpcbind.8;, &man.rpc.statd.8; i &man.rpc.lockd.8; wykorzystywane s±
         przy po³±czeniach <acronym>RPC</acronym> (Remote Procedure Call).  <command>rpcbind</command>
         zarz±dza komunikacj± pomiêdzy serwerem <acronym>NFS</acronym> i klientami, tym samym jest wymagany
         do poprawnego funkcjonowania serwera <acronym>NFS</acronym>.  Demon <application>rpc.statd</application>
         wykorzystywany jest do komunikacji z innymi demonami <application>rpc.statd</application> w sieci,
         w celu monitorowania stanu maszyn, na których one pracuj±. Uzyskane w ten sposób informacje
         przechowywane s± z regu³y w pliku <filename>/var/db/statd.status</filename>.  Kolejnym elementem
         jest <guimenuitem>rpc.lockd</guimenuitem>, który udostêpnia us³ugi blokowania plików.
         Z regu³y, wykorzystywany jest w parze z <application>rpc.statd</application> do ¶ledzenia,
         które maszyny wymagaj± blokowania i jak czêsto.  O ile dwie ostatnie us³ugi s± idealne
         do debugowania, nie s± one wymagane do poprawnego dzia³ania serwera <acronym>NFS</acronym>.</para>
 
       <para>Kolejnym elementem na li¶cie jest demon rutowania - <guimenuitem>Routed</guimenuitem>.
         &man.routed.8; zarz±dza tablicami rutingu sieci, wyszukuje rutery multicast i udostêpnia
         na ¿±danie kopiê tablic rutingu ka¿dej maszynie w sieci.  Wykorzystywany jest on z regu³y
         na komputerach pracuj±cych jako bramy dla sieci lokalnej.  Po jego wybraniu pojawi siê dodatkowe
         menu, w którym nale¿y okre¶liæ jego domy¶ln± lokalizacjê.  Warto¶æ domy¶lna jest zdefiniowana
         i zostanie wybrana po naci¶niêciu klawisza <keycap>Enter</keycap>.  Nastêpnie pojawi siê kolejne
         menu, tym razem w celu ustawienia flag. Domy¶ln± jest <option>-q</option> i powinna pojawiæ
         siê na ekranie.</para>
 
       <para>Kolejn± opcj± jest <guimenuitem>Rwhod</guimenuitem>, której wybór w³±czy demona
         &man.rwhod.8; w trakcie uruchamiania systemu.  <command>rwhod</command> jest narzêdziem, które
         regularnie rozsy³a w sieci komunikaty systemowe b±d¼ - w trybie <quote>konsumenta</quote>
         - zbiera je.  Wiêcej informacji dostêpnych jest w podrêcznikach systemowych &man.ruptime.1;
         i &man.rwho.1;.</para>
 
       <para>Przedostatnim elementem na li¶cie jest demon &man.sshd.8;. Jest to serwer
         <application>OpenSSH</application>, którego wykorzystanie jest zalecane w zamiast
         <application>telnet</application>u czy serwerów <acronym>FTP</acronym>.  Serwer
         <application>sshd</application> jest wykorzystywany do zestawiania bezpiecznego
         po³±czenia pomiêdzy dwoma maszynami wykorzystuj±c po³±czenia szyfrowane.</para>
 
       <para>Ostatni± na li¶cie jest opcja Rozszerzeñ <acronym>TCP</acronym> (<guimenuitem>TCP
           Extensions</guimenuitem>).  W³±czenie jej umo¿liwia korzystanie z rozszerzeñ
         <acronym>TCP</acronym> zdefiniowanych w <acronym>RFC</acronym>&nbsp;1323
         i <acronym>RFC</acronym>&nbsp;1644.  O ile na wielu komputerach pozwoli to
         na przyspieszenie komunikacji, o tyle mo¿e równie¿ spowodowaæ odrzucanie
         niektórych po³±czeñ.  Stosowanie tej opcji nie jest zalecane dla serwerów,
         chod¼ mo¿e siê okazaæ korzystne dla stacji roboczych.</para>
 
       <para>Skoñczywszy konfiguracjê us³ug sieciowych mo¿emy przewin±æ do samej góry ekranu,
         do opcji <guimenuitem>Exit</guimenuitem> i przej¶æ do kolejnej czê¶ci konfiguracji.</para>
 
     </sect2>
 
     <sect2 id="x-server">
       <title>Konfiguracja serwera X</title>
 
       <note>
 	<para>Pocz±wszy od wersji &os;&nbsp;5.3-RELEASE, opcje konfiguracji
           serwera X zosta³y usuniête z <application>sysinstall</application>.
           Serwer X musimy zainstalowaæ i skonfigurowaæ po skoñczonej instalacji
           systemu. <xref linkend="x11"/> zawiera szczegó³owe informacje odno¶nie
           instalacji i konfiguracji serwera X.  Je¶li nie instalujemy wersji
           wcze¶niejszej ni¿ &os;&nbsp;5.3-RELEASE, mo¿emy pomi±æ t± sekcjê.</para>
       </note>
 
       <para>Chc±c korzystaæ z graficznego interfejsu u¿ytkownika w rodzaju
         <application>KDE</application>, <application>GNIEME</application>
         lub innego, trzeba skonfigurowaæ serwer X.</para>
 
       <note>
         <para>By uruchomiæ <application>&xfree86;</application> z poziomu
           u¿ytkownika innego ni¿ <username>root</username>, nale¿y zainstalowaæ
           <filename role="package">x11/wrapper</filename>.  Jest on instalowany
           domy¶lnie we FreeBSD&nbsp;4.7 i pó¼niejszych.  W przypadku wcze¶niejszych
           wersji mo¿na go zainstalowaæ z menu wyboru pakietów.</para>
       </note>
 
       <para>Aby sprawdziæ, czy nasza karta graficzna jest obs³ugiwana, mo¿emy
         zajrzeæ na stronê WWW
 	<ulink url="http://www.xfree86.org/">&xfree86;</ulink>.</para>
 
       <screen>                      User Confirmation Requested
         Would you like to configure your X server at this time?
 
                             [ Yes ]   No</screen>
 
       <warning>
         <para> Nale¿y koniecznie znaæ dane techniczne monitora i karty graficznej.
           Nieprawid³owe ustawienia mog± spowodowaæ uszkodzenie sprzêtu.  Je¶li nie
           dysponujemy tymi danymi, wybierzmy &gui.no; i przyst±pmy do konfiguracji
           serwera X po zainstalowaniu systemu, gdy ju¿ zaopatrzymy siê w niezbêdne
           dane.  Do tego celu mo¿emy wykorzystaæ <command>sysinstall</command>
           (<command>/stand/sysinstall</command> we &os; starszych ni¿ 5.2),
           wybieraj±c <guimenuitem>Configure</guimenuitem>, a nastêpnie
           <guimenuitem>XFree86</guimenuitem>.
 	</para>
       </warning>
 
       <para>Je¶li mamy dane techniczne karty graficznej i monitora,
         wybieramy &gui.yes; i wciskamy <keycap>Enter</keycap>,
         rozpoczynaj±c konfiguracjê serwera X.</para>
 
       <figure id="xserver2">
         <title>Wybór metody konfiguracji</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/xf86setup"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Serwer X mo¿na konfigurowaæ na kilka sposobów.
         Wybieramy jedn± z metod przy pomocy klawiszy kursora
         i naciskamy <keycap>Enter</keycap>.  Pamiêtajmy o uwa¿nym
         czytaniu wszelkich poleceñ pojawiaj±cych siê na ekranie.</para>
 
       <para>Wybór <application>xf86cfg</application> i
         <application>xf86cfg -textmode</application> mo¿e spowodowaæ,
         ¿e ekran stanie siê ciemny, a uruchomienie mo¿e zaj±æ kilka sekund.
         B±d¼my cierpliwi.</para>
 
 
       <para>W poni¿szym przyk³adzie przedstawione bêdzie korzystanie z programu
         konfiguracyjnego <application>xf86config</application>.  Wybierane przez
         nas opcje zale¿eæ bêd± od wyposa¿enia naszego komputera, bêd± siê wiêc
         zapewne ró¿niæ od opcji pokazanych w przyk³adzie:</para>
 
       <screen>                                Message
  You have configured and been running the mouse daemon.
  Choose "/dev/sysmouse" as the mouse port and "SysMouse" or
  "MouseSystems" as the mouse protocol in the X configuration utility.
 
                                  [ OK ]
 
                       [ Press enter to continue ]</screen>
 
       <para>Komunikat ten informuje o wykryciu skonfigurowanego wcze¶niej
         demona myszki. Naciskamy <keycap>Enter</keycap>,
         by przej¶æ dalej.</para>
 
       <para>Po uruchomieniu, <application>xf86config</application> wy¶wietli
         krótkie wprowadzenie:</para>
 
       <screen>This program will create a basic XF86Config file, based on menu selections you
 make.
 
 The XF86Config file usually resides in /usr/X11R6/etc/X11 or /etc/X11. A sample
 XF86Config file is supplied with XFree86; it is configured for a standard
 VGA card and monitor with 640x480 resolution. This program will ask for a
 pathname when it is ready to write the file.
 
 You can either take the sample XF86Config as a base and edit it for your
 configuration, or let this program produce a base XF86Config file for your
 configuration and fine-tune it.
 
 Before continuing with this program, make sure you know what video card
 you have, and preferably also the chipset it uses and the amount of video
 memory on your video card. SuperProbe may be able to help with this.
 
 Press enter to continue, or ctrl-c to abort.</screen>
 
       <para>Po naci¶niêciu <keycap>Enter</keycap> przejdziemy do konfiguracji myszki.
         Pamiêtajmy, by uwa¿nie czytaæ polecenia i wybraæ w³a¶ciwy protokó³ myszki
         <quote>Mouse Systems</quote> i port myszki <filename>/dev/sysmouse</filename>,
         nawet je¶li w przyk³adzie wybierana jest myszka PS/2.</para>
 
       <screen>First specify a mouse protocol type. Choose one from the following list:
 
  1.  Microsoft compatible (2-button protocol)
  2.  Mouse Systems (3-button protocol) &amp; FreeBSD moused protocol
  3.  Bus Mouse
  4.  PS/2 Mouse
  5.  Logitech Mouse (serial, old type, Logitech protocol)
  6.  Logitech MouseMan (Microsoft compatible)
  7.  MM Series
  8.  MM HitTablet
  9.  Microsoft IntelliMouse
 
 If you have a two-button mouse, it is most likely of type 1, and if you have
 a three-button mouse, it can probably support both protocol 1 and 2. There are
 two main varieties of the latter type: mice with a switch to select the
 protocol, and mice that default to 1 and require a button to be held at
 boot-time to select protocol 2. Some mice can be convinced to do 2 by sending
 a special sequence to the serial port (see the ClearDTR/ClearRTS options).
 
 Enter a protocol number: 2
 
 You have selected a Mouse Systems protocol mouse. If your mouse is normally
 in Microsoft-compatible mode, enabling the ClearDTR and ClearRTS options
 may cause it to switch to Mouse Systems mode when the server starts.
 
 Please answer the following question with either 'y' or 'n'.
 Do you want to enable ClearDTR and ClearRTS? n
 
 You have selected a three-button mouse protocol. It is recommended that you
 do not enable Emulate3Buttons, unless the third button doesn't work.
 
 Please answer the following question with either 'y' or 'n'.
 Do you want to enable Emulate3Buttons? y
 
 Now give the full device name that the mouse is connected to, for example
 /dev/tty00. Just pressing enter will use the default, /dev/mouse.
 On FreeBSD, the default is /dev/sysmouse.
 
 Mouse device: /dev/sysmouse</screen>
 
       <para>Kolejnym krokiem jest konfiguracja klawiatury.  W przyk³adzie
         wybrana zosta³a typowa klawiatura o 101 klawiszach.  Jako wariant
         nazwy mo¿emy wybraæ dowoln± nazwê, lub po prostu nacisn±æ <keycap>Enter</keycap>,
         akceptuj±c proponowan± nazwê domy¶ln±.</para>
 
       <screen>Please select one of the following keyboard types that is the better
 description of your keyboard. If nothing really matches,
 choose 1 (Generic 101-key PC)
 
   1  Generic 101-key PC
   2  Generic 102-key (Intl) PC
   3  Generic 104-key PC
   4  Generic 105-key (Intl) PC
   5  Dell 101-key PC
   6  Everex STEPnote
   7  Keytronic FlexPro
   8  Microsoft Natural
   9  Northgate OmniKey 101
  10  Winbook Model XP5
  11  Japanese 106-key
  12  PC-98xx Series
  13  Brazilian ABNT2
  14  HP Internet
  15  Logitech iTouch
  16  Logitech Cordless Desktop Pro
  17  Logitech Internet Keyboard
  18  Logitech Internet Navigator Keyboard
  19  Compaq Internet
  20  Microsoft Natural Pro
  21  Genius Comfy KB-16M
  22  IBM Rapid Access
  23  IBM Rapid Access II
  24  Chicony Internet Keyboard
  25  Dell Internet Keyboard
 
 Enter a number to choose the keyboard.
 
 1
 
 
 Please select the layout corresponding to your keyboard
 
 
   1  U.S. English
   2  U.S. English w/ ISO9995-3
   3  U.S. English w/ deadkeys
   4  Albanian
   5  Arabic
   6  Armenian
   7  Azerbaidjani
   8  Belarusian
   9  Belgian
  10  Bengali
  11  Brazilian
  12  Bulgarian
  13  Burmese
  14  Canadian
  15  Croatian
  16  Czech
  17  Czech (qwerty)
  18  Danish
 
 Enter a number to choose the country.
 Press enter for the next page
 
 1
 
 
 Please enter a variant name for 'us' layout. Or just press enter
 for default variant
 
 us
 
 
 Please answer the following question with either 'y' or 'n'.
 Do you want to select additional XKB options (group switcher,
 group indicator, etc.)? n</screen>
 
       <para>Nastêpnie przystêpujemy do konfiguracji monitora.  Pamiêtajmy,
         by nie przekroczyæ dopuszczalnych warto¶ci czêstotliwo¶ci, poniewa¿ mo¿e
         to spowodowaæ uszkodzenie monitora.  W razie jakichkolwiek w±tpliwo¶ci,
         od³ó¿my konfiguracjê monitora do czasu, gdy bêdziemy ju¿ mieæ niezbêdne
         informacje.</para>
 
       <screen>Now we want to set the specifications of the monitor. The two critical
 parameters are the vertical refresh rate, which is the rate at which the
 whole screen is refreshed, and most importantly the horizontal sync rate,
 which is the rate at which scanlines are displayed.
 
 The valid range for horizontal sync and vertical sync should be documented
 in the manual of your monitor. If in doubt, check the monitor database
 /usr/X11R6/lib/X11/doc/Monitors to see if your monitor is there.
 
 Press enter to continue, or ctrl-c to abort.
 
 
 
 You must indicate the horizontal sync range of your monitor. You can either
 select one of the predefined ranges below that correspond to industry-
 standard monitor types, or give a specific range.
 
 It is VERY IMPORTANT that you do not specify a monitor type with a horizontal
 sync range that is beyond the capabilities of your monitor. If in doubt,
 choose a conservative setting.
 
     hsync in kHz; monitor type with characteristic modes
  1  31.5; Standard VGA, 640x480 @ 60 Hz
  2  31.5 - 35.1; Super VGA, 800x600 @ 56 Hz
  3  31.5, 35.5; 8514 Compatible, 1024x768 @ 87 Hz interlaced (no 800x600)
  4  31.5, 35.15, 35.5; Super VGA, 1024x768 @ 87 Hz interlaced, 800x600 @ 56 Hz
  5  31.5 - 37.9; Extended Super VGA, 800x600 @ 60 Hz, 640x480 @ 72 Hz
  6  31.5 - 48.5; Non-Interlaced SVGA, 1024x768 @ 60 Hz, 800x600 @ 72 Hz
  7  31.5 - 57.0; High Frequency SVGA, 1024x768 @ 70 Hz
  8  31.5 - 64.3; Monitor that can do 1280x1024 @ 60 Hz
  9  31.5 - 79.0; Monitor that can do 1280x1024 @ 74 Hz
 10  31.5 - 82.0; Monitor that can do 1280x1024 @ 76 Hz
 11  Enter your own horizontal sync range
 
 Enter your choice (1-11): 6
 
 You must indicate the vertical sync range of your monitor. You can either
 select one of the predefined ranges below that correspond to industry-
 standard monitor types, or give a specific range. For interlaced modes,
 the number that counts is the high one (e.g. 87 Hz rather than 43 Hz).
 
  1  50-70
  2  50-90
  3  50-100
  4  40-150
  5  Enter your own vertical sync range
 
 Enter your choice: 2
 
 You must now enter a few identification/description strings, namely an
 identifier, a vendor name, and a model name. Just pressing enter will fill
 in default names.
 
 The strings are free-form, spaces are allowed.
 Enter an identifier for your monitor definition: Hitachi</screen>
 
       <para>W kolejnym etapie wybieramy z listy sterownik karty
         graficznej.  Je¶li przewijaj±c listê niechc±cy ominiemy
         nasz± kartê, naciskajmy dalej <keycap>Enter</keycap>, a lista
         zostanie powtórzona.  W przyk³adzie pokazujemy tylko fragment
         listy:</para>
 
       <screen>Now we must configure video card specific settings. At this point you can
 choose to make a selection out of a database of video card definitions.
 Because there can be variation in Ramdacs and clock generators even
 between cards of the same model, it is not sensible to blindly copy
 the settings (e.g. a Device section). For this reason, after you make a
 selection, you will still be asked about the components of the card, with
 the settings from the chosen database entry presented as a strong hint.
 
 The database entries include information about the chipset, what driver to
 run, the Ramdac and ClockChip, and comments that will be included in the
 Device section. However, a lot of definitions only hint about what driver
 to run (based on the chipset the card uses) and are untested.
 
 If you can't find your card in the database, there's nothing to worry about.
 You should only choose a database entry that is exactly the same model as
 your card; choosing one that looks similar is just a bad idea (e.g. a
 GemStone Snail 64 may be as different from a GemStone Snail 64+ in terms of
 hardware as can be).
 
 Do you want to look at the card database? y
 
 
 
 288  Matrox Millennium G200 8MB                        mgag200
 289  Matrox Millennium G200 SD 16MB                    mgag200
 290  Matrox Millennium G200 SD 4MB                     mgag200
 291  Matrox Millennium G200 SD 8MB                     mgag200
 292  Matrox Millennium G400                            mgag400
 293  Matrox Millennium II 16MB                         mga2164w
 294  Matrox Millennium II 4MB                          mga2164w
 295  Matrox Millennium II 8MB                          mga2164w
 296  Matrox Mystique                                   mga1064sg
 297  Matrox Mystique G200 16MB                         mgag200
 298  Matrox Mystique G200 4MB                          mgag200
 299  Matrox Mystique G200 8MB                          mgag200
 300  Matrox Productiva G100 4MB                        mgag100
 301  Matrox Productiva G100 8MB                        mgag100
 302  MediaGX                                           mediagx
 303  MediaVision Proaxcel 128                          ET6000
 304  Mirage Z-128                                      ET6000
 305  Miro CRYSTAL VRX                                  Verite 1000
 
 Enter a number to choose the corresponding card definition.
 Press enter for the next page, q to continue configuration.
 
 288
 
 Your selected card definition:
 
 Identifier: Matrox Millennium G200 8MB
 Chipset:    mgag200
 Driver:     mga
 Do NIET probe clocks or use any Clocks line.
 
 Press enter to continue, or ctrl-c to abort.
 
 
 
 Now you must give information about your video card. This will be used for
 the "Device" section of your video card in XF86Config.
 
 You must indicate how much video memory you have. It is probably a good
 idea to use the same approximate amount as that detected by the server you
 intend to use. If you encounter problems that are due to the used server
 not supporting the amount memory you have (e.g. ATI Mach64 is limited to
 1024K with the SVGA server), specify the maximum amount supported by the
 server.
 
 How much video memory do you have on your video card:
 
  1  256K
  2  512K
  3  1024K
  4  2048K
  5  4096K
  6  Other
 
 Enter your choice: 6
 
 Amount of video memory in Kbytes: 8192
 
 You must now enter a few identification/description strings, namely an
 identifier, a vendor name, and a model name. Just pressing enter will fill
 in default names (possibly from a card definition).
 
 Your card definition is Matrox Millennium G200 8MB.
 
 The strings are free-form, spaces are allowed.
 Enter an identifier for your video card definition:</screen>
 
       <para>Nastêpnie wybieramy tryby graficzne dla preferowanych rozdzielczo¶ci.
         Najczê¶ciej u¿ywane s± tryby 640x480, 800x600 i 1024x768, wybór zale¿y
         jednak od mo¿liwo¶ci karty graficznej, rozmiarów monitora i oczekiwanej
         wygody pracy.  Gdy bêdziemy wybieraæ g³êbiê koloru, wybierzmy najwy¿sz±
         warto¶æ, któr± obs³uguje karta.</para>
 
       <screen>For each depth, a list of modes (resolutions) is defined. The default
 resolution that the server will start-up with will be the first listed
 mode that can be supported by the monitor and card.
 Currently it is set to:
 
 "640x480" "800x600" "1024x768" "1280x1024" for 8-bit
 "640x480" "800x600" "1024x768" "1280x1024" for 16-bit
 "640x480" "800x600" "1024x768" "1280x1024" for 24-bit
 
 Modes that cannot be supported due to monitor or clock constraints will
 be automatically skipped by the server.
 
  1  Change the modes for 8-bit (256 colors)
  2  Change the modes for 16-bit (32K/64K colors)
  3  Change the modes for 24-bit (24-bit color)
  4  The modes are OK, continue.
 
 Enter your choice: 2
 
 Select modes from the following list:
 
  1  "640x400"
  2  "640x480"
  3  "800x600"
  4  "1024x768"
  5  "1280x1024"
  6  "320x200"
  7  "320x240"
  8  "400x300"
  9  "1152x864"
  a  "1600x1200"
  b  "1800x1400"
  c  "512x384"
 
 Please type the digits corresponding to the modes that you want to select.
 For example, 432 selects "1024x768" "800x600" "640x480", with a
 default mode of 1024x768.
 
 Which modes? 432
 
 You can have a virtual screen (desktop), which is screen area that is larger
 than the physical screen and which is panned by moving the mouse to the edge
 of the screen. If you don't want virtual desktop at a certain resolution,
 you cannot have modes listed that are larger. Each color depth can have a
 differently-sized virtual screen
 
 Please answer the following question with either 'y' or 'n'.
 Do you want a virtual screen that is larger than the physical screen? n
 
 
 
 For each depth, a list of modes (resolutions) is defined. The default
 resolution that the server will start-up with will be the first listed
 mode that can be supported by the monitor and card.
 Currently it is set to:
 
 "640x480" "800x600" "1024x768" "1280x1024" for 8-bit
 "1024x768" "800x600" "640x480" for 16-bit
 "640x480" "800x600" "1024x768" "1280x1024" for 24-bit
 
 Modes that cannot be supported due to monitor or clock constraints will
 be automatically skipped by the server.
 
  1  Change the modes for 8-bit (256 colors)
  2  Change the modes for 16-bit (32K/64K colors)
  3  Change the modes for 24-bit (24-bit color)
  4  The modes are OK, continue.
 
 Enter your choice: 4
 
 
 
 Please specify which color depth you want to use by default:
 
   1  1 bit (monochrome)
   2  4 bits (16 colors)
   3  8 bits (256 colors)
   4  16 bits (65536 colors)
   5  24 bits (16 million colors)
 
 Enter a number to choose the default depth.
 
 4</screen>
 
       <para>Przygotowan± konfiguracjê nale¿y zachowaæ.  Upewnijmy siê, ¿e konfiguracja
         zostanie zapisana w pliku o nazwie <filename>/etc/X11/XF86Config</filename>.</para>
 
       <screen>I am going to write the XF86Config file now. Make sure you don't accidently
 overwrite a previously configured one.
 
 Shall I write it to /etc/X11/XF86Config? y</screen>
 
       <para>Je¶li z jakich¶ przyczyn konfiguracja nie powiedzie siê, mo¿emy zacz±æ
         j± od pocz±tku, wybieraj±c &gui.yes;, gdy pojawi siê nastêpuj±cy
         komunikat:</para>
 
       <screen>          User Confirmation Requested
 The XFree86 configuration process seems to have
 failed.  Would you like to try again?
 
              [ Yes ]         No</screen>
 
       <para>Je¿eli konfiguracja <application>&xfree86;</application> sprawia
         problemy, wybierzmy &gui.no; i naci¶nijmy <keycap>Enter</keycap>,
         by kontynuowaæ instalacjê.  Po jej zakoñczeniu bêdziemy mogli uruchomiæ
         program konfiguracyjny poleceniem <command>xf86cfg -textmode</command>
         lub <command>xf86config</command>, wydanym jako <username>root</username>.
         <xref linkend="x11"/> prezentuje inn± metodê konfiguracji
         <application>&xfree86;</application> . Je¶li zdecydujemy siê pomin±æ na
         razie konfiguracjê <application>&xfree86;</application>, kolejnym krokiem
         bêdzie wybór pakietów.</para>
 
       <para>Domy¶lnie serwer X mo¿e zostaæ unicestwiony kombinacj± klawiszy
         <keycombo action='simul'><keycap>Ctrl</keycap><keycap>Alt</keycap>
 	<keycap>Backspace</keycap></keycombo>.  Mo¿emy z niej skorzystaæ,
         je¶li co¶ jest nie w porz±dku z ustawieniami serwera i chcemy unikn±æ
         uszkodzenia sprzêtu.</para>
 
       <para>Podczas pracy serwera X mo¿na zmieniaæ tryb graficzny, u¿ywaj±c
         kombinacji klawiszy
 	<keycombo action='simul'>
 	  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>+</keycap>
 	</keycombo> lub
 	<keycombo action='simul'>
 	  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>-</keycap>
 	</keycombo>.</para>
 
       <para>Po zakoñczeniu instalacji mo¿na wyregulowaæ wysoko¶æ, szeroko¶æ
         i po³o¿enie obrazu przy u¿yciu <application>xvidtune</application>,
         po uruchomieniu <application>&xfree86;</application>.</para>
 
       <para>Zwracajmy uwagê na ostrze¿enia o mo¿liwo¶ci uszkodzenia sprzêtu
         poprzez niew³a¶ciwe ustawienia.  Nie róbmy niczego, czego nie jeste¶my
         pewni.  Zamiast u¿ywaæ xvidtune, mo¿emy dostroiæ ekran X Window korzystaj±c
         z regulatorów monitora.  Mog± siê pojawiæ pewne ró¿nice w wy¶wietlaniu obrazu
         przy powraceniu do trybu tekstowego, lepsze to jednak ni¿ uszkodzenie
         sprzêtu.</para>
 
       <para>Przed dokonaniem jakichkolwiek zmian zapoznajmy siê z dokumentacj±
         &man.xvidtune.1;.</para>
 
       <para>Je¿eli konfiguracja <application>&xfree86;</application> przebieg³a pomy¶lnie,
         przejdziemy do kolejnego etapu, w którym wybierzemy mened¿era okien.</para>
     </sect2>
 
     <sect2 id="default-desktop">
       <title>Wybór mened¿era okien</title>
 
       <note>
         <para>Pocz±wszy od wersji &os;&nbsp;5.3-RELEASE, opcje wyboru
           ¶rodowiska graficznego zosta³y usuniête z <application>sysinstall</application>.
           Musimy je skonfigurowaæ po skoñczonej instalacji
           systemu. <xref linkend="x11"/> zawiera szczegó³owe informacje odno¶nie
             instalacji i konfiguracji ¶rodowiska graficznego.  Je¶li nie instalujemy wersji
           wcze¶niejszej ni¿ &os;&nbsp;5.3-RELEASE, mo¿emy pomi±æ t± sekcjê.</para>
       </note>
 
       <para>Dostepnych jest wiele ró¿nych mened¿erów okien, poczynaj±c od najprostszych,
         zapewniaj±cych jedynie podstawowe funkcje, do rozbudowanych ¶rodowisk
         wyposa¿onych w poka¼ny zestaw oprogramowania.  Niektórym wystarczy nieznaczna
         przestrzeñ na dysku i niewiele pamiêci, inne natomiast mog± mieæ znacznie
         wiêksze wymagania.  Dobrze jest wypróbowaæ kilka ró¿nych mened¿erów
         i wybraæ spo¶ród nich ten, który najbardziej nam odpowiada.  S± one dostêpne
         w Kolekcji portów lub w postaci pakietów, mo¿na je wiêc instalowaæ po
         zainstalowaniu systemu.</para>
 
       <para>Mo¿emy wybraæ jeden z popularnych mened¿erów okien i zainstalowaæ
         go jako domy¶lny.  Dziêki temu bêdziemy mieæ mo¿liwo¶æ uruchomienia
         go zaraz po zakoñczeniu instalacji.</para>
 
       <figure id="x-desktop">
         <title>Wybór domy¶lnego mened¿era okien</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/desktop"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawiszami kursora wybieramy jedn± z opcji i wciskamy
         <keycap>Enter</keycap>.  Wybrany mened¿er okien zostanie
         zainstalowany.</para>
     </sect2>
 
     <sect2 id="packages">
     <title>Instalacja pakietów</title>
 
     <para>Pakiety to skompilowane programy, które mo¿na w ³atwy sposób instalowaæ.</para>
 
       <para>W poni¿szym przyk³adzie pokazana jest instalacja jednego pakietu.
         Mo¿emy oczywi¶cie zainstalowaæ wiêcej pakietów.  Gdy system bêdzie
         ju¿ zainstalowany, kolejne pakiety bêdzie mo¿na dodawaæ przy u¿yciu
         <command>sysinstall</command> (<command>/stand/sysinstall</command>
 	w wersjach &os; wcze¶niejszych ni¿ 5.2).</para>
 
       <screen>                     User Confirmation Requested
  The FreeBSD package collection is a collection of hundreds of
  ready-to-run applications, from text editors to games to WEB servers
  and more. Would you like to browse the collection now?
 
                             [ Yes ]   No</screen>
 
       <para>Je¶li wybierzemy &gui.yes; i naci¶niemy <keycap>Enter</keycap>,
         przejdziemy do ekranu wyboru pakietów:</para>
 
       <figure id="package-category">
         <title>Wybór kategorii pakietów</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-cat"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>W danej chwili dostêpne do instalacji s± jedynie pakiety
         z bie¿±cego no¶nika.</para>
 
       <para>Mo¿emy wybraæ jedn± z kategorii pakietów albo
         <guimenuitem>All</guimenuitem>, by wy¶wietlone zosta³y wszystkie
         dostêpne pakiety.  Wybran± opcjê wskazujemy przy u¿yciu klawiszy
         kursora i wciskamy <keycap>Enter</keycap>.</para>
 
       <para>Pokazana zostanie lista pakietów dostêpnych w wybranej kategorii:</para>
 
       <figure id="package-select">
         <title>Wybór pakietów</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-sel"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Dla przyk³adu zaznaczona zosta³a pow³oka <application>bash</application>.
         Mo¿emy wybraæ tyle pakietów, ile nam siê podoba, zaznaczaj±c ka¿dy z nich
         <keycap>Space</keycap>.  Krótki opis pakietu wy¶wietlany jest w lewym dolnym
         rogu ekranu.</para>
 
       <para>Klawiszem <keycap>Tab</keycap> mo¿emy prze³±czaæ siê miêdzy ostatnio
         wybranym pakietem, przyciskami &gui.ok; i &gui.cancel;.</para>
 
       <para>Po zaznaczeniu wszystkich wybranych pakietów naciskamy <keycap>Tab</keycap>,
         by zaznaczyæ &gui.ok; i naciskamy <keycap>Enter</keycap>, powracaj±c w ten sposób
         do menu wyboru pakietów.</para>
 
       <para>Do prze³±czania siê miêdzy &gui.ok; i &gui.cancel; mog± równie¿ s³u¿yæ klawisze
         kursora.  Za ich pomoc± mo¿emy wybraæ &gui.ok;, a nastêpnie nacisn±æ
         <keycap>Enter</keycap>, by wróciæ do menu wyboru pakietów.</para>
 
       <figure id="package-install">
         <title>Rozpoczêcie instalacji pakietów</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-install"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawiszami kursora i <keycap>Tab</keycap> wybieramy <guibutton>[&nbsp;Install&nbsp;]</guibutton>
         i wciskamy <keycap>Enter</keycap>.  Pojawi siê pro¶ba o potwierdzenie chêci
         zainstalowania pakietów:</para>
 
       <figure id="package-install-confirm">
         <title>Potwierdzenie instalacji pakietów</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-confirm"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Gdy wybierzemy &gui.ok; i naci¶niemy <keycap>Enter</keycap>, rozpocznie siê
         instalacja pakietów.  A¿ do jej zakoñczenia bêd± pokazywane komunikaty o przebiegu
         instalacji.  Je¿eli pojawi± siê informacje o jakichkolwiek problemach,
         zanotujmy je.</para>
 
       <para>Po zainstalowaniu pakietów wracamy do konfiguracji systemu. Nawet je¶li nie wybrali¶my
         ¿adnych pakietów i chcemy wróciæ do koñcowej konfiguracji wybieramy
         opcjê <guibutton>Install</guibutton>.</para>
     </sect2>
 
     <sect2 id="addusers">
       <title>Dodawanie u¿ytkowników i grup</title>
 
       <para>Powinni¶my za³o¿yæ przynajmniej jedno konto u¿ytkownika, by móc korzystaæ
         z systemu nie bêd±c zalogowanym jako <username>root</username>.  G³ówna partycja
         jest zwykle niewielka, wiêc korzystanie z aplikacji jako <username>root</username>
         mo¿e j± szybko zape³niæ.  Inny powód wymieniony zosta³ w poni¿szym
         komunikacie:</para>
 
       <screen>                     User Confirmation Requested
  Would you like to add any initial user accounts to the system? Adding
  at least one account for yourself at this stage is suggested since
  working as the "root" user is dangerous (it is easy to do things which
  adversely affect the entire system).
 
                             [ Yes ]   No</screen>
 
       <para>Wybieramy &gui.yes; i naciskamy <keycap>Enter</keycap>,
         by dodaæ u¿ytkownika.</para>
 
       <figure id="add-user2">
         <title>Dodawanie u¿ytkownika</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser1"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Klawiszamy kursora wybieramy <guimenuitem>User</guimenuitem>
         (u¿ytkownik) i wciskamy <keycap>Enter</keycap>.</para>
 
       <figure id="add-user3">
         <title>Dane nowego u¿ytkownika</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser2"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Kolejne pola wybieramy klawiszem <keycap>Tab</keycap>.
         W dolnej czê¶ci ekranu pojawiaæ siê bêd± nastêpuj±ce opisy,
         pomocne przy wprowadzaniu poszczególnych danych:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>Login ID</term>
 
 	  <listitem>
             <para>Nazwa nowego u¿ytkownika (obowi±zkowa).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>UID</term>
 
 	  <listitem>
             <para>Numer bêd±cy identyfikatorem u¿ytkownika (wype³niany
               automatycznie, je¶li pole pozostanie puste).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Group</term>
 
 	  <listitem>
             <para>Nazwa podstawowej grupy u¿ytkownika (wybierana automatycznie,
               je¶li pole pozostanie puste).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Password</term>
 
 	  <listitem>
             <para>Has³o u¿ytkownika (wpisujmy je uwa¿nie!).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Full name</term>
 
 	  <listitem>
             <para>Nazwisko u¿ytkownika (komentarz).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Member groups</term>
 
 	  <listitem>
             <para>Grupy, których cz³onkiem bêdzie u¿ytkownik (czyli
               dostanie ich uprawnienia).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Home directory</term>
 
 	  <listitem>
             <para>Domowy katalog u¿ytkownika (wpisywany automatycznie,
               je¶li pole pozostanie puste).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Login shell</term>
 	  <listitem>
             <para>Pow³oka uruchamiana po zalogowaniu siê (wybierana automatycznie,
               je¶li pole pozostanie puste, np. <filename>/bin/sh</filename>).</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>W przyk³adzie pow³oka zosta³a zmieniona z <filename>/bin/sh</filename>
         na <filename>/usr/local/bin/bash</filename>, aby korzystaæ z pow³oki
         <application>bash</application> zainstalowanej wcze¶niej jako pakiet.
         Nie wpisujmy tu pow³oki, która nie istnieje, gdy¿ uniemo¿liwi to zalogowanie siê.
         Najpopularniejsz± pow³ok± w ¶wiecie BSD jest pow³oka C, czyli
         <filename>/bin/tcsh</filename>.</para>
 
       <para>U¿ytkownik zosta³ dopisany do grupy <groupname>wheel</groupname>,
         dziêki czemu bêdzie móg³ uzyskiwaæ uprawnienia u¿ytkownika
         <username>root</username>.</para>
 
       <para>Gdy skoñczymy, wybieramy &gui.ok;.  Ponownie pojawi siê menu zarz±dzania
         u¿ytkownikami i grupami:</para>
 
       <figure id="add-user4">
         <title>Wyj¶cie z menu zarz±dzania u¿ytkownikami i grupami</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser3"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>W podobny sposób mo¿emy od razu utworzyæ dodatkowe grupy,
         je¶li zajdzie taka potrzeba.  Gdy system bêdzie ju¿ zainstalowany,
         bêdziemy mogli dodawaæ grupy przy u¿yciu <command>sysinstall</command>
         (<command>/stand/sysinstall</command> w wersjach &os; starszych ni¿
 	5.2).</para>
 
       <para>Gdy skoñczymy dodawanie u¿ytkowników wybieramy klawiszami kursora
         <guimenuitem>Exit</guimenuitem> i wciskamy <keycap>Enter</keycap>,
         by kontynuowaæ instalacjê.</para>
     </sect2>
 
     <sect2 id="rootpass">
       <title>Has³o u¿ytkownika <username>root</username></title>
 
       <screen>                        Message
  Now you must set the system manager's password.
  This is the password you'll use to log in as "root".
 
                          [ OK ]
 
                [ Press enter to continue ]</screen>
 
       <para>Wciskamy <keycap>Enter</keycap>, aby ustawiæ has³o
         <username>root</username>a.</para>
 
       <para>Has³o musi byæ prawid³owo podane dwukrotnie.  Rzecz jasna,
         powinni¶my zadbaæ o to, by ³atwo odnale¼æ has³o, gdy zdarzy
         siê nam je zapomnieæ.  Zwróæmy uwagê, ¿e w trakcie wpisywania
         has³a nie pojawi± siê ¿adne znaki, nawet gwiazdki.</para>
 
       <screen>Changing local password for root.
 New password :
 Retype new password :</screen>
 
       <para>Po pomy¶lnym wprowadzeniu has³a przejdziemy do kolejnego etapu
         instalacji.</para>
     </sect2>
 
     <sect2 id="exit-inst">
       <title>Zakoñczenie instalacji</title>
 
       <para>Je¿eli bêdziemy chcieli skonfigurowaæ dodatkowe urz±dzenia sieciowe,
         lub wprowadziæ inne zmiany w konfiguracji systemu, mo¿emy to zrobiæ w tym
         w³a¶nie momencie, lub te¿ po zakoñczeniu instalacji za po¶rednictwem
         <command>sysinstall</command> (<command>/stand/sysinstall</command>
         w wersjach &os; wcze¶niejszych ni¿ 5.2).</para>
 
       <screen>                     User Confirmation Requested
  Visit the general configuration menu for a chance to set any last
  options?
 
                               Yes   [ No ]</screen>
 
       <para>Wybieramy klawiszami kursora &gui.no; i wciskamy <keycap>Enter</keycap>,
         by powróciæ do g³ównego menu instalacji.</para>
 
       <figure id="final-main">
         <title>Zakoñczenie instalacji</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mainexit"/>
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Przy pomocy klawiszy kursora wybieramy <guibutton>[X Exit Install]</guibutton>
         i naciskamy <keycap>Enter</keycap>.  Pojawi siê pro¶ba o potwierdzenie chêci
         zakoñczenia instalacji:</para>
 
       <screen>                     User Confirmation Requested
  Are you sure you wish to exit? The system will reboot (be sure to
  remove any floppies from the drives).
 
                             [ Yes ]   No</screen>
 
       <para>Wybieramy &gui.yes;. Je¿eli uruchamiali¶my komputer z dyskietki, wyjmujemy j±.
         Napêd CDROM bêdzie zablokowany a¿ do chwili, gdy komputer zacznie siê ponownie uruchamiaæ.
         Wtedy napêd zostanie odblokowany i bêdzie mo¿na wyj±æ z niego p³ytê (szybko).</para>
 
       <para>Komputer zostanie ponownie uruchomiony. Zwróæmy uwagê na ewentualne komunikaty
         o b³êdach.</para>
     </sect2>
 
     <sect2 id="freebsdboot">
       <title>Uruchamianie FreeBSD</title>
 
       <sect3 id="freebsdboot-i386">
         <title>Uruchamianie FreeBSD na komputerach &i386;</title>
 
       <para>Je¿eli wszystko przebieg³o prawid³owo, na ekranie zobaczymy
         seriê kolejno pojawiaj±cych siê komunikatów, a na koniec bêdziemy
         mogli siê zalogowaæ.  Komunikaty mo¿emy przeczytaæ naciskaj±c
         <keycap>Scroll-Lock</keycap>, nastêpnie przewijaj±c ekran klawiszami
         <keycap>PgUp</keycap> i <keycap>PgDn</keycap>.  Ponownie naciskaj±c
         <keycap>Scroll-Lock</keycap> powracamy do komunikatu logowania.</para>
 
       <para>Byæ mo¿e nie bêdziemy mogli zobaczyæ wszystkich komunikatów
         (ograniczony rozmiar bufora), jednak mo¿na je przejrzeæ po zalogowaniu
         siê, wpisuj±c <command>dmesg</command> w linii poleceñ.</para>
 
       <para>Zalogujmy siê, wpisuj±c nazwê u¿ytkownika i has³o wybrane podczas
         instalacji (w naszym przyk³adzie <username>rpratt</username>).
         Jako <username>root</username> powinni¶my logowaæ siê tylko wtedy,
         gdy jest to konieczne.</para>
 
       <para>Typowe komunikaty pokazywane podczas uruchamiania systemu
         (pominiêto informacje o wersji):</para>
 
 <screen>Copyright (c) 1992-2002 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
 
 Timecounter "i8254"  frequency 1193182 Hz
 CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU)
   Origin = "AuthenticAMD"  Id = 0x580  Stepping = 0
   Features=0x8001bf&lt;FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX&gt;
   AMD Features=0x80000800&lt;SYSCALL,3DNow!&gt;
 real memory  = 268435456 (262144K bytes)
 config&gt; di sn0
 config&gt; di lnc0
 config&gt; di le0
 config&gt; di ie0
 config&gt; di fe0
 config&gt; di cs0
 config&gt; di bt0
 config&gt; di aic0
 config&gt; di aha0
 config&gt; di adv0
 config&gt; q
 avail memory = 256311296 (250304K bytes)
 Preloaded elf kernel "kernel" at 0xc0491000.
 Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c.
 md0: Malloc disk
 Using $PIR table, 4 entries at 0xc00fde60
 npx0: &lt;math processor&gt; on motherboard
 npx0: INT 16 interface
 pcib0: &lt;Host to PCI bridge&gt; on motherboard
 pci0: &lt;PCI bus&gt; on pcib0
 pcib1: &lt;VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge&gt; at device 1.0 on pci0
 pci1: &lt;PCI bus&gt; on pcib1
 pci1: &lt;Matrox MGA G200 AGP graphics accelerator&gt; at 0.0 irq 11
 isab0: &lt;VIA 82C586 PCI-ISA bridge&gt; at device 7.0 on pci0
 isa0: &lt;ISA bus&gt; on isab0
 atapci0: &lt;VIA 82C586 ATA33 controller&gt; port 0xe000-0xe00f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0: &lt;VIA 83C572 USB controller&gt; port 0xe400-0xe41f irq 10 at device 7.2 on pci0
 usb0: &lt;VIA 83C572 USB controller&gt; on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 chip1: &lt;VIA 82C586B ACPI interface&gt; at device 7.3 on pci0
 ed0: &lt;NE2000 PCI Ethernet (RealTek 8029)&gt; port 0xe800-0xe81f irq 9 at
 device 10.0 on pci0
 ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit)
 isa0: too many dependant configs (8)
 isa0: unexpected small tag 14
 fdc0: &lt;NEC 72065B or clone&gt; at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: &lt;1440-KB 3.5" drive&gt; on fdc0 drive 0
 atkbdc0: &lt;keyboard controller (i8042)&gt; at port 0x60-0x64 on isa0
 atkbd0: &lt;AT Keyboard&gt; flags 0x1 irq 1 on atkbdc0
 kbd0 at atkbd0
 psm0: &lt;PS/2 Mouse&gt; irq 12 on atkbdc0
 psm0: model Generic PS/2 mouse, device ID 0
 vga0: &lt;Generic ISA VGA&gt; at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: &lt;System console&gt; at flags 0x1 on isa0
 sc0: VGA &lt;16 virtual consoles, flags=0x300&gt;
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: &lt;Parallel port&gt; at port 0x378-0x37f irq 7 on isa0
 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/15 bytes threshold
 ppbus0: IEEE1284 device found /NIBBLE
 Probing for PnP devices on ppbus0:
 plip0: &lt;PLIP network interface&gt; on ppbus0
 lpt0: &lt;Printer&gt; on ppbus0
 lpt0: Interrupt-driven port
 ppi0: &lt;Parallel I/O&gt; on ppbus0
 ad0: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata0-master using UDMA33
 ad2: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata1-master using UDMA33
 acd0: CDROM &lt;DELTA OTC-H101/ST3 F/W by OIPD&gt; at ata0-slave using PIO4
 Mounting root from ufs:/dev/ad0s1a
 swapon: adding /dev/ad0s1b as swap device
 Automatic boot in progress...
 /dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1a: clean, 48752 free (552 frags, 6025 blocks, 0.9% fragmentation)
 /dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1f: clean, 128997 free (21 frags, 16122 blocks, 0.0% fragmentation)
 /dev/ad0s1g: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1g: clean, 3036299 free (43175 frags, 374073 blocks, 1.3% fragmentation)
 /dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS
 /dev/ad0s1e: clean, 128193 free (17 frags, 16022 blocks, 0.0% fragmentation)
 Doing initial network setup: hostname.
 ed0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
         inet6 fe80::5054::5ff::fede:731b%ed0 prefixlen 64 tentative scopeid 0x1
         ether 52:54:05:de:73:1b
 lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; mtu 16384
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
         inet6 ::1 prefixlen 128
         inet 127.0.0.1 netmask 0xff000000
 Additional routing options: IP gateway=TAK TCP keepalive=TAK
 routing daemons:.
 additional daemons: syslogd.
 Doing additional network setup:.
 Starting final network daemons: creating ssh RSA host key
 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:
 cd:76:89:16:69:0e:d0:6e:f8:66:d0:07:26:3c:7e:2d root@k6-2.example.com
  creating ssh DSA host key
 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:
 f9:a1:a9:47:c4:ad:f9:8d:52:b8:b8:ff:8c:ad:2d:e6 root@k6-2.example.com.
 setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib
 /usr/local/lib
 a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
 starting standard daemons: inetd cron sshd usbd sendmail.
 Initial rc.i386 initialization:.
 rc.i386 configuring syscons: blank_time screensaver moused.
 Additional ABI support: linux.
 Local package initialization:.
 Additional TCP options:.
 
 FreeBSD/i386 (k6-2.example.com) (ttyv0)
 
 login: rpratt
 Password:</screen>
 
       <para>Generowanie kluczy RSA i DSA na niezbyt szybkich komputerach
         mo¿e zaj±æ nieco czasu. Dzieje siê to tylko podczas pierwszego
         uruchomienia nowo zainstalowanego systemu.  Nastêpne ³adowanie
         systemu bêdzie ju¿ odbywaæ siê szybciej.</para>
 
       <para>Je¶li skonfigurowali¶my serwer X i wybrali¶my mened¿era okien,
         mo¿emy uruchomiæ go wpisuj±c <command>startx</command>
         w linii poleceñ.</para>
 
       </sect3>
 
       <sect3>
         <title>Uruchamianie FreeBSD na komputerach Alpha</title>
 
 	<indexterm><primary>Alpha</primary></indexterm>
 
         <para>Po zakoñczeniu instalacji bêdziemy mogli uruchomiæ FreeBSD,
           wpisuj±c nastêpuj±ce polecenie w konsoli SRM:</para>
 
 	<screen>&gt;&gt;&gt;<userinput>BOOT DKC0</userinput></screen>
 
         <para>Nakazuje ono oprogramowaniu sprzêtowemu uruchomiæ system
           z okre¶lonego dysku.  By FreeBSD by³o automatycznie uruchamiane
           przy w³±czeniu komputera, wpisujemy poni¿sze polecenia:</para>
 
 	<screen><prompt>&gt;&gt;&gt;</prompt> <userinput>SET BOOT_OSFLAGS A</userinput>
 <prompt>&gt;&gt;&gt;</prompt> <userinput>SET BOOT_FILE ''</userinput>
 <prompt>&gt;&gt;&gt;</prompt> <userinput>SET BOOTDEF_DEV DKC0</userinput>
 <prompt>&gt;&gt;&gt;</prompt> <userinput>SET AUTO_ACTION BOOT</userinput></screen>
 
 	<para>Komunikaty pokazywane podczas ³adowania systemu bêd± podobne
           (choæ nie identyczne) do komunikatów pokazywanych na &i386;.</para>
       </sect3>
     </sect2>
 
     <sect2 id="shutdown">
       <title>Wy³±czanie FreeBSD</title>
 
       <para>W³a¶ciwe wy³±czenie systemu operacyjnego jest istotn± spraw±.
         Nie nale¿y po prostu wy³±czaæ komputera.  Powinni¶my najpierw uzyskaæ
         prawa administratora, wpisuj±c w linii poleceñ <command>su</command>
         i podaj±c has³o <username>root</username>a; mo¿e to zrobiæ tylko u¿ytkownik
         nale¿±cy do grupy <groupname>wheel</groupname>.  Mo¿emy tak¿e po prostu
         zalogowaæ siê jako <username>root</username>.  Nastêpnie wydajemy polecenie
         <command>shutdown -h now</command>.</para>
 
       <screen>The operating system has halted.
 Please press any key to reboot.</screen>
 
       <para>Po takim wy³±czeniu systemu i pojawieniu siê komunikatu <quote>Please press any
           key to reboot</quote> (Naci¶nij dowolny klawisz by ponownie uruchomiæ system),
         mo¿na ju¿ wy³±czyæ komputer.  Naci¶niêcie dowolnego klawisza spowoduje ponownie
         uruchomienie systemu.</para>
 
       <para>Inny sposobem ponownego uruchomienia systemu jest kombinacja klawiszy
         <keycombo action="simul">
 	  <keycap>Ctrl</keycap>
 	  <keycap>Alt</keycap>
 	  <keycap>Del</keycap>
 	</keycombo>,
         jednak w normalnych warunkach korzystanie z niej nie jest zalecane.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="install-supported-hardware">
     <title>Obs³ugiwany sprzêt</title>
 
     <indexterm><primary>sprzêt</primary></indexterm>
     <para>W obecnej chwili FreeBSD dzia³a na komputerach z magistralami
       ISA, VLB, EISA i PCI wyposa¿onych w procesory Intel, AMD, Cyrix
       lub NexGen <quote>x86</quote>, jak równie¿ na komputerach z procesorem
       Compaq Alpha. Obs³ugiwane s± tak¿e dyski IDE i ESDI, rozmaite kontrolery
       SCSI, karty PCMCIA, urz±dzenia USB oraz karty sieciowe i szeregowe.
       FreeBSD pracuje tak¿e z szyn± microchannel (MCA) firmy IBM.</para>
 
     <para>Lista obs³ugiwanych urz±dzeñ do³±czona jest do ka¿dego wydania
       FreeBSD w dokumencie FreeBSD Hardware Notes. Mo¿na go zwykle znale¼æ
       w pliku <filename>HARDWARE.TXT</filename>, umieszczonym bezpo¶rednio
       w g³ównym katalogu p³yty CDROM lub na serwerze FTP, b±d¼ w menu
       dokumentacji <application>sysinstall</application>. Na li¶cie zebrano
       urz±dzenia, które poprawnie wspó³pracuj± z FreeBSD. Kopie tej listy
       dla ró¿nych wydañ systemu i ró¿nych architektur mo¿na tak¿e znale¼æ
       na podstronie <ulink
         url="http://www.FreeBSD.org/releases/index.html">Release
       Information</ulink> na stronie WWW FreeBSD.</para>
   </sect1>
 
   <sect1 id="install-trouble">
     <title>Rozwi±zywanie problemów</title>
 
     <indexterm>
       <primary>instalacja</primary>
       <secondary>rozwi±zywanie problemów</secondary>
     </indexterm>
     <para>W tej czê¶ci opisujemy, jak radziæ sobie z podstawowymi problemami
       spotykanymi podczas instalacji. W kilku pytaniach i odpowiedziach
       omawiamy tak¿e mo¿liwo¶æ uruchamiania FreeBSD i &ms-dos; na tym samym
       komputerze.</para>
 
     <sect2>
       <title>Co robiæ, gdy co¶ pójdzie nie tak</title>
 
       <para>Ze wzglêdu na rozmaite ograniczenia architektury PC,
         rozpoznawanie urz±dzeñ mo¿e niekiedy sprawiaæ problemy. Mo¿na
         jednak spróbowaæ sobie z nimi poradziæ</para>
 
       <para>Zapoznajmy siê z dokumentem Hardware Notes, by mieæ
         pewno¶æ, ¿e nasze urz±dzenia s± obs³ugiwane przez FreeBSD.</para>
 
       <para>Je¶li wci±¿ wystêpuj± problemy, mimo, ¿e nasz sprzêt jest
         obs³ugiwany, powinni¶my ponownie uruchomiæ komputer i wybraæ opcjê
         wizualnej konfiguracji j±dra (visual kernel configuration). Bêdziemy
         mieæ mo¿liwo¶æ przejrzenia naszych urz±dzeñ i podania systemowi
         informacji o nich. J±dro uruchamiane z dyskietki startowej zak³ada,
         ¿e wiêkszo¶æ urz±dzeñ skonfigurowanych jest z fabrycznymi ustawieniami
         IRQ, portów we/wy i kana³ów DMA. Je¶li konfiguracja naszego sprzêtu
         jest odmienna, zapewne bêdziemy musieli poinformowaæ o tym FreeBSD,
         odpowiednio modyfikuj±c konfiguracjê.</para>
 
       <para>Mo¿e siê zdarzyæ, ¿e próba rozpoznania urz±dzenia nieistniej±cego
         spowoduje k³opoty z pó¼niejszym rozpoznawaniem urz±dzeñ rzeczywi¶cie
         zainstalowanych w komputerze. W takim wypadku powinni¶my wy³±czyæ
         sterowniki powoduj±ce konflikty.</para>
 
       <note>
         <para>Pewnych problemów z instalacj± mo¿na unikn±æ dziêki instalacji
           nowszego oprogramowania sprzêtowego (ang. firmware) urz±dzenia,
           zwykle p³yty g³ównej. Oprogramowanie sprzêtowe p³yty g³ównej znane
           jest pod nazw± <acronym>BIOS</acronym>. Wiêkszo¶æ producentów p³yt
           g³ównych lub komputerów umieszcza informacje o nowych wersjach
           oprogramowania na swoich stronach WWW.</para>
 
         <para>Producenci zwykle stanowczo odradzaj± instalowanie nowego
           <acronym>BIOS</acronym>-u, oprócz sytuacji, w których jest to
           uzasadnione, na przyk³ad w przypadku wykrycia powa¿nego b³êdu.
           Instalacja nowszej wersji <emphasis>mo¿e</emphasis> siê nie udaæ,
           powoduj±c trwa³e uszkodzenie uk³adu <acronym>BIOS</acronym>.</para>
         </note>
 
       <warning>
         <para>Nie nale¿y wy³±czaæ sterowników potrzebnych podczas instalacji,
           na przyk³ad sterownika ekranu (<devicename>sc0</devicename>).
           Je¿eli po zakoñczeniu konfiguracji j±dra instalacja w tajemniczy
           sposób zastyga lub przerywa pracê, zapewne usunêli¶my
           lub zmodyfikowali¶my co¶, co nie powinno byæ ruszane. Musimy ponownie
           uruchomiæ komputer i spróbowaæ jeszcze raz.</para>
       </warning>
 
       <para>Podczas konfiguracji mo¿emy:</para>
 
       <itemizedlist>
         <listitem>
           <para>Przejrzeæ listê sterowników zainstalowanych w j±drze.</para>
         </listitem>
 
         <listitem>
           <para>Wy³±czyæ sterowniki urz±dzeñ, których nie ma w komputerze.</para>
         </listitem>
 
         <listitem>
           <para>Zmieniæ ustawienia IRQ, DRQ i portów we/wy u¿ywanych
             przez sterowniki.</para>
         </listitem>
       </itemizedlist>
 
       <para>Po dostosowaniu konfiguracji j±dra do naszego sprzêtu, wpisujemy
         <command>Q</command>, by ponownie uruchomiæ komputer z nowymi
         ustawieniami. Zmiany konfiguracji s± trwa³e i bêd± obowi±zywaæ
         równie¿ po zakoñczeniu instalacji, nie bêdzie wiêc trzeba konfigurowaæ
         j±dra na nowo przy ka¿dym uruchamianiu systemu. Jest jednak bardzo
         prawdopodobne, ¿e bêdziemy chcieli zbudowaæ <link
         linkend="kernelconfig">niestandardowe j±dro</link>.</para>
     </sect2>
 
     <sect2>
       <title>Jak poradziæ sobie z istniej±cymi partycjami &ms-dos;</title>
 
       <indexterm><primary>DOS</primary></indexterm>
       <para>Wielu u¿ytkowników instaluje &os; na komputerach PC z systemem
         operacyjnym z rodziny &microsoft;. Specjalnie dla tych u¿ytkowników
         przygotowany zosta³ program <application>FIPS</application>. Narzêdzie
         to znajduje siê na p³ycie instalacyjnej w katalogu\
         <filename>tools</filename>. Mo¿na je równie¿ pobraæ z wielu <link
         linkend="mirrors">serwerów lustrzanych &os;</link>.</para>
 
       <para><application>FIPS</application> umo¿liwia podzielenie istniej±cej
         partycji &ms-dos; na dwie czê¶ci, zachowuj±c pierwotn± partycjê i pozwalaj±c
         na instalacjê &os; na wolnej drugiej czêsci. Wpierw nale¿y wykonaæ
         defragmentacjê partycji &ms-dos; za pomoc± dostêpnego w &windows;
         narzêdzia (w Eksploratorze nacisn±æ prawym przyciskiem myszki na dysku
         twardym, nastêpnie wybraæ opcjê defragmentacji dysku), albo <application>Norton
           Disk Tools</application>. Nastêpnie nale¿y uruchomiæ
         <application>FIPS</application>. Program zapyta o potrzebne mu informacje.
         Potem mo¿na ponownie uruchomiæ komputer i zainstalowaæ &os; na nowym wolnym
         segmencie. W menu <guimenuitem>Distributions</guimenuitem> mo¿na dowiedzieæ
         siê, ile miejsca na dysku bêdzie w przybli¿eniu potrzebne.</para>
 
       <para>Jest tak¿e bardzo u¿yteczny program firmy PowerQuest
         (<ulink url="http://www.powerquest.com/">http://www.powerquest.com</ulink>),
         o nazwie <application>&partitionmagic;</application>. Ma on znacznie wiêksze
         mo¿liwo¶ci ni¿ <application>FIPS</application> i stosowanie go jest zalecane,
         je¶li planuje siê czêste instalowanie i usuwanie systemów operacyjnych.
         Nie jest on jednak za darmo; je¶li &os; ma byæ zainstalowane raz na dobre,
         <application>FIPS</application> zapewne w zupe³no¶ci wystarczy.</para>
     </sect2>
 
     <sect2>
       <title>Wykorzystanie systemów plików &ms-dos; i &windows;</title>
 
       <para>W chwili obecnej &os; nie obs³uguje systemów plików skompresowanych
         za pomoc± programu <application>Double Space&trade;</application>.
         Tym samym musimy wpierw rozkompresowaæ system plików nim &os; bêdzie móg³
         odczytaæ zapisane w nim dane. Mo¿na do tego wykorzystaæ <application>Agenta
           kompresji</application> z menu <guimenuitem>Start </guimenuitem>&gt;
         <guimenuitem>Programy</guimenuitem> &gt; <guimenuitem>Narzêdzia
           systemowe</guimenuitem>.</para>
 
       <para>&os; obs³uguje systemy plików &ms-dos;. By je zamontowaæ nale¿y
         wykorzystaæ polecenie &man.mount.msdosfs.8;
         z odpowiednimi parametrami.  Typowa forma
         polecenia wygl±da nastêpuj±co:</para>
 
       <screen>&prompt.root; <userinput>mount_msdosfs /dev/ad0s1 /mnt</userinput></screen>
 
       <para>W tym przyk³adzie system plików &ms-dos; zlokalizowany jest na pierwszej
         partycji pierwszego dysku twardego. By sprawdziæ jak jest w naszym przypadku
         nale¿y sprawdziæ wynik poleceñ <command>dmesg</command> oraz
         <command>mount</command>. Powinno to pozwoliæ nam zorientowaæ siê w uk³adzie
         partycji na dysku.</para>
 
       <note><para>Rozszerzone partycje &ms-dos; odwzorowywane s± na koñcu pozosta³ych
           <quote>segmentów</quote> we &os;.  Przyk³adowo, pierwsza partycja &ms-dos;
         mo¿e znajdowaæ sie na <filename>/dev/ad0s1</filename>, partycja &os;
         na <filename>/dev/ad0s2</filename>, natomiast rozszerzona partycja &ms-dos;
         na <filename>/dev/ad0s3</filename>.  Mo¿e to byæ myl±ce na pocz±tku.</para></note>
 
       <para>Analogicznie mo¿na montowaæ partycje NTFS wykorzystuj±c polecenie
         &man.mount.ntfs.8;.</para>
     </sect2>
 
     <sect2>
       <title>Pytania u¿ytkowników komputerów Alpha</title>
 
       <indexterm><primary>Alpha</primary></indexterm>
 
       <para>Oto niektóre z najczê¶ciej zadawanych pytañ dotycz±cych
         instalowania FreeBSD na komputerach Alpha.</para>
 
       <qandaset>
 	<qandaentry>
 	  <question>
 	    <indexterm><primary>ARC</primary></indexterm>
 	    <indexterm><primary>Alpha BIOS</primary></indexterm>
 	    <indexterm><primary>SRM</primary></indexterm>
 
             <para>Czy mogê ³adowaæ system z konsoli ARC lub Alpha BIOS?</para>
 	  </question>
 
 	  <answer>
             <para>Nie. &os;, podobnie jak Compaq Tru64 i VMS, mo¿e byæ
               ³adowany tylko z konsoli SRM.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
             <para>Pomocy, brakuje mi miejsca na dysku! Czy muszê
               wszystko skasowaæ?</para>
 	  </question>
 
 	  <answer>
             <para>Niestety tak.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
             <para>Czy mo¿na montowaæ systemy plików Compaq Tru64 lub VMS?</para>
 	  </question>
 
 	  <answer>
             <para>Nie, przynajmniej na razie.</para>
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect2>
   </sect1>
 
   <sect1 id="install-advanced">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Valentino</firstname>
 	  <surname>Vaschetto</surname>
 	  <contrib>Napisa³ </contrib>
 	</author>
 	<!-- May 2001 -->
       </authorgroup>
     </sect1info>
 
     <title>Instalacja zaawansowana</title>
 
     <para>W tej czê¶ci omówiona zosta³a instalacja &os;
       w sytuacjach wyj±tkowych.</para>
 
     <sect2 id="headless-install">
       <title>Instalacja FreeBSD na komputerze bez monitora
         lub klawiatury</title>
 
       <indexterm>
         <primary>instalacja</primary>
         <secondary>bez g³owy (konsola szeregowa)</secondary>
       </indexterm>
       <indexterm><primary>konsola szeregowa</primary></indexterm>
       <para>Ten rodzaj instalacji zwany jest <quote>instalacj±
           bez g³owy</quote>, poniewa¿ komputer, na którym &os;
         bêdzie instalowane nie ma pod³±czonego monitora, lub nawet
         nie ma wyj¶cia VGA. Jak to mo¿liwe? Dziêki konsoli szeregowej.
         W roli konsoli szeregowej u¿ywa siê zwykle innego komputera,
         który pe³ni rolê ekranu i klawiatury dla pozbawionego tych
         urz±dzeñ komputera. By zainstalowaæ system t± metod±, musimy
         przygotowaæ dyskietki instalacyjne zgodnie z opisem w
         <xref  linkend="install-floppies"/>.</para>
 
       <para>By zmodyfikowaæ dyskietki do pracy z konsol± szeregow±
         nale¿y wykonaæ nastêpuj±ce kroki:</para>
 
       <procedure>
 	<step>
           <title>W³±czenie konsoli szeregowej na dyskietce startowej</title>
   	    <indexterm>
 	      <primary><command>mount</command></primary>
 	    </indexterm>
             <para>Je¶li spróbowaliby¶my uruchomiæ komputer korzystaj±c
               z utworzonych w³a¶nie dyskietek startowych, zosta³aby
               uruchomiona zwyk³a instalacja FreeBSD.  My jednak chcemy,
               by podczas instalacji u¿ywana by³a konsola szeregowa.
               By to skonfigurowaæ, montujemy dyskietkê
               <filename>kern.flp</filename> we FreeBSD przy u¿yciu
               polecenia &man.mount.8;.</para>
 
             <screen>&prompt.root; <userinput>mount /dev/fd0 /mnt</userinput></screen>
 
             <para>Po zamontowaniu dyskietki, wchodzimy do katalogu
               <filename class="directory">/mnt</filename>:</para>
 
 	    <screen>&prompt.root; <userinput>cd /mnt</userinput></screen>
 
             <para>Teraz w³±czymy na dyskietce konsolê szeregow±.
               Musimy stworzyæ plik <filename>boot.config</filename>
               zawieraj±cy wiersz <literal>/boot/loader -h</literal>.
               Jego zadaniem jest po prostu nakazanie programowi
               ³aduj±cemu system, by u¿ywa³ konsoli szeregowej.</para>
 
 	    <screen>&prompt.root; <userinput>echo "/boot/loader -h" &gt; boot.config</userinput></screen>
 
             <para>Po prawid³owym skonfigurowaniu dyskietki odmontowujemy
               j± poleceniem &man.umount.8;:</para>
 
             <screen>&prompt.root; <userinput>cd /</userinput>
 &prompt.root; <userinput>umount /mnt</userinput></screen>
 
 	    <para>Mo¿emy wyj±æ dyskietkê ze stacji dyskietek.</para>
 	  </step>
 
 	  <step>
             <title>Pod³±czenie kabla null-modem</title>
 
   	    <indexterm><primary>kabel null-modem</primary></indexterm>
             <para>Dwa komputery ³±czymy <link linkend="term-cables-null">kablem
                 null-modem</link>.  Po prostu pod³±czamy kabel do portów szeregowych
               w jednym i drugim komputerze.  <emphasis>Zwyk³y kabel szeregowy
               nie nadaje siê do tego celu</emphasis>, potrzebny jest kabel
               null-modem, poniewa¿ jego przewody s± odpowiednio
               skrzy¿owane.</para>
 	  </step>
 
 	  <step>
             <title>Uruchomienie instalacji</title>
 
             <para>Mo¿emy ju¿ uruchomiæ instalacjê. Do stacji dyskietek
               <quote>bezg³owego</quote> komputera, na którym ma byæ
               zainstalowane FreeBSD, wk³adamy dyskietkê
               <filename>kern.flp</filename> i w³±czamy komputer.</para>
 	  </step>
 
 	  <step>
             <title>Po³±czenie z <quote>bezg³owym</quote> komputerem</title>
 	    <indexterm>
 	      <primary><command>cu</command></primary>
 	    </indexterm>
             <para>Z komputerem ³±czymy siê korzystaj±c z
 	      &man.cu.1;:</para>
 
 	    <screen>&prompt.root; <userinput>cu -l /dev/cuaa0</userinput></screen>
 	  </step>
       </procedure>
 
       <para>Gotowe! Powinni¶my byæ w stanie kontrolowaæ
         <quote>bezg³owy</quote> komputer poprzez sesjê
         <command>cu</command>. Zostaniemy poproszeni
         o w³o¿enie dyskietki <filename>mfsroot.flp</filename>,
         nastepnie o wybranie typu terminala. Wybieramy kolorow±
         konsolê FreeBSD (FreeBSD color console) i kontynuujemy
         instalacjê.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="install-diff-media">
     <title>Przygotowanie w³asnego no¶nika instalacji</title>
 
     <note>
       <para>Dla uproszczenia, w niniejszej czê¶ci <quote>dysk
           FreeBSD</quote> oznaczaæ bêdzie p³ytê CDROM lub DVD
         z FreeBSD, który zakupili¶my lub przygotowali¶my
         samodzielnie.</para>
     </note>
 
     <para>Mo¿e siê zdarzyæ sytuacja, w której bêdziemy musieli
       przygotowaæ w³asny no¶nik lub ¼ród³o dla instalacji FreeBSD.
       Mo¿e to byæ no¶nik fizyczny, na przyk³ad ta¶ma, albo inne ¼ród³o
       z którego <application>sysinstall</application> bêdzie móg³ pobraæ
       pliki, na przyk³ad lokalny serwer FTP lub partycja &ms-dos;.</para>
 
     <para>Oto przyk³ad:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Mamy wiele komputerów w sieci lokalnej i jeden dysk FreeBSD.
           Chcemy przygotowaæ lokalny serwer FTP z zawarto¶ci± dysku FreeBSD,
           aby komputery mog³y z niego korzystaæ zamiast ³±czyæ siê
           z Internetem.</para>
       </listitem>
 
       <listitem>
         <para>Mamy dysk FreeBSD, jednak FreeBSD nie obs³uguje naszego napêdu
           CD/DVD. Napêd jest natomiast prawid³owo obs³ugiwany
           w &ms-dos;/&windows;. Chcemy skopiowaæ pliki instalacyjne
           FreeBSD na partycjê DOS i wykorzystaæ j± do zainstalowania
           FreeBSD.</para>
       </listitem>
 
       <listitem>
         <para>Komputer, na którym chcemy zainstalowaæ system nie ma napêdu
           CD/DVD ani karty sieciowej.  Jest inny komputer, który ma napêd
           CD/DVD lub kartê sieciow± i mo¿emy po³±czyæ siê z nim kablem
           szeregowym lub równoleg³ym.</para>
       </listitem>
 
       <listitem>
         <para>Chcemy przygotowaæ ta¶mê, przy pomocy której bêdzie mo¿na
           zainstalowaæ FreeBSD.</para>
       </listitem>
     </itemizedlist>
 
     <sect2 id="install-cdrom">
       <title>Przygotowanie p³yty instalacyjnej</title>
 
       <para>W ramach ka¿dego wydania systemu Projekt FreeBSD udostêpnia
         piêæ obrazów p³yt CD (<quote>obrazów ISO</quote>).  Je¶li dysponujemy
         nagrywark± CD, mo¿emy je nagraæ (<quote>wypaliæ</quote>) na p³ytach,
         otrzymuj±c zestaw p³yt, które mog± pos³u¿yæ do zainstalowania systemu.
         Jest to najprostszy sposób instalacji FreeBSD w przypadku, gdy mamy
         nagrywarkê i tanie po³±czenie z Internetem.</para>
 
       <procedure>
 	<step>
           <title>Pobranie obrazów ISO</title>
 
           <para>Obrazy ISO ka¿dego z wydañ systemu mo¿na pobraæ z
             <filename>ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-<replaceable>arch</replaceable>/<replaceable>version</replaceable></filename> lub z najbli¿szego serwera
             lustrzanego. W miejscu <replaceable>arch</replaceable>
             i <replaceable>version</replaceable> wstawiamy odpowiedni±
             nazwê architektury i wersjê.</para>
 
           <para>Wspomniany katalog zawiera zwykle nastêpuj±ce obrazy:</para>
 
 	  <table frame="none">
             <title>Nazwy obrazów ISO dla FreeBSD 4.<replaceable>X</replaceable>
               i ich znaczenie</title>
 
 	    <tgroup cols="2">
 	      <thead>
 		<row>
                   <entry>Nazwa pliku</entry>
 
                   <entry>Zawarto¶æ</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-miniinst.iso</filename></entry>
 
                   <entry>Wszystko, co jest potrzebne do zainstalowania FreeBSD.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc1.iso</filename></entry>
 
                   <entry>Wszystko, co jest potrzebne do zainstalowania
                     FreeBSD, i tyle dodatkowych pakietów, ile zmie¶ci³o
                     siê na p³ycie.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc2.iso</filename></entry>
 
                   <entry><quote>¯ywy system plików</quote>, u¿ywany wraz
                     z dostêpn± w <application>sysinstall</application> funkcj±
                     <quote>Repair</quote> (naprawa). Kopia drzewa CVS FreeBSD.
                     Dodatkowe pakiety o charakterze niezale¿nym.</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </table>
 
 	  <table frame="none">
             <title>Nazwy obrazów ISO dla FreeBSD 5.<replaceable>X</replaceable>
               i ich znaczenie</title>
 
 	    <tgroup cols="2">
 	      <thead>
 		<row>
                   <entry>Nazwa pliku</entry>
 
                   <entry>Zawarto¶æ</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-bootonly.iso</filename></entry>
 
                   <entry>Wszystko co jest niezbêdne by uruchomiæ j±dro
                     FreeBSD i rozpocz±æ instalacjê. Pliki instalacyjne
                     zostan± probrane z serwera FTP b±d¼ innego ¼ród³a.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-miniinst.iso</filename></entry>
 
                   <entry>Wszystko, co jest potrzebne do zainstalowania FreeBSD.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc1.iso</filename></entry>
 
                   <entry>Wszystko co jest potrzebne by zainstalowaæ &os;
                     jako <quote>¿ywy system plików</quote> u¿ywany wraz
                     z dostêpn± w <application>sysinstall</application>
                     funkcj± <quote>Repair</quote> (naprawa).</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc2.iso</filename></entry>
 
                   <entry>Dokumentacja &os; i tyle dodatkowych pakietów,
                     ile zmie¶ci³o siê na p³ycie.</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </table>
 
           <para><emphasis>Musimy</emphasis> pobraæ albo obraz ISO mini,
             albo obraz pierwszej p³yty.  Nie ma sensu pobieraæ obydwu,
             poniewa¿ obraz pierwszej p³yty zawiera wszystko to,
             co obraz mini.</para>
 
 	  <note>
             <para>Obraz ISO mini dostêpny jest tylko dla wydañ starszych
               ni¿ FreeBSD 5.4-RELEASE.</para>
 	  </note>
 
           <para>Z obrazu ISO miniinst warto jest skorzystaæ, gdy mamy
             niedrogi dostêp do Internetu. Za jego pomoc± mo¿emy zainstalowaæ
             FreeBSD, natomiast niezale¿ne oprogramowanie instalujemy przez
             Internet, przy pomocy systemu portów i pakietów (patrz:
             <xref linkend="ports"/>).</para>
 
           <para>P³ytê pierwsz± wybieramy wtedy, gdy oprócz zainstalowania
             systemu chcemy skorzystaæ z zestawu wybranych pakietów
             oprogramowania.</para>
 
 	  <para>Pozosta³e p³yty s± przydatne, lecz nie niezbêdne, szczególnie,
             gdy dysponujemy szybkim dostêpem do Internetu.</para>
 	</step>
 
 	<step>
           <title>Nagranie p³yt CD</title>
 
           <para>Pliki obrazów nale¿y nagraæ na p³yty. Je¶li zamierzamy
             robiæ to w systemie FreeBSD, informacje na ten temat znajdziemy
             w <xref linkend="creating-cds"/> (w szczególno¶ci <xref linkend="burncd"/>
             oraz <xref linkend="cdrecord"/>).</para>
 
 	  <para>Je¿eli p³yty nagrywaæ bêdziemy w innym systemie,
             do tego celu mo¿emy pos³u¿yæ siê dowolnymi dostêpnymi
             programami obs³uguj±cymi nagrywarkê p³yt CD. ISO jest
             standardowym formatem obrazu p³yt obs³ugiwanym w wielu
             aplikacjach nagrywaj±cych.</para>
 	</step>
       </procedure>
 
       <note><para>Zainteresowanych przygotowaniem w³asnych wydañ
         &os; odsy³amy do artyku³u <ulink
         url="&url.articles.releng;">Release Engineering
         </ulink>(ang.).</para></note>
 
     </sect2>
 
     <sect2 id="install-ftp">
       <title>Przygotowanie lokalnego serwera FTP z dyskiem FreeBSD</title>
 
       <indexterm>
 	<primary>instalacja</primary>
 	<secondary>sieæ</secondary>
 	<tertiary>FTP</tertiary>
       </indexterm>
 
       <para>Uk³ad plików na dysku FreeBSD jest taki sam, jak uk³ad plików
         na serwerze FTP. Dziêki temu ³atwo mo¿emy przygotowaæ lokalny
         serwer FTP, który mo¿e byæ wykorzystany przez inne komputery
         w sieci do instalacji FreeBSD.</para>
 
       <procedure>
 	<step>
           <para>Na komputerze, który bêdzie s³u¿yæ jako serwer FTP,
             umieszczamy CDROM w napêdzie i montujemy go w katalogu
             <filename>/cdrom</filename>.</para>
 
 	  <screen>&prompt.root; <userinput>mount /cdrom</userinput></screen>
 	</step>
 
 	<step>
           <para>Zak³adamy konto dla anonimowego u¿ytkownika FTP
             w <filename>/etc/passwd</filename>. Plik <filename>/etc/passwd</filename>
             modyfikujemy przy u¿yciu &man.vipw.8;. Dodajemy nastêpuj±cy
             wiersz:</para>
 
 	  <programlisting>ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
 	</step>
 
 	<step>
           <para>Na koniec upewniamy siê, ¿e us³uga FTP jest w³±czona
             w <filename>/etc/inetd.conf</filename>.</para>
 	</step>
       </procedure>
 
       <para>Od tej chwili ka¿dy, kto jest w stanie nawi±zaæ po³±czenie
         z naszym komputerem, mo¿e podczas instalacji FreeBSD wybraæ
         jako ¼ród³o serwer FTP, w menu wyboru serwera FTP wybraæ opcjê
         <quote>Other</quote> (inny) i wpisaæ
         <userinput>ftp://<replaceable>nasz.komputer</replaceable></userinput>.</para>
 
       <note>
         <para>Je¶li no¶nik, z którego uruchamiamy instalator (najczê¶ciej
           dyskietka), nie pochodzi z dok³adnie tej samej wersji co pliki
           na naszym serwerze FTP, to <application>sysinstall</application>
           nie pozwoli nam kontynuowaæ instalacji. By pomin±æ t± blokadê
           nale¿y w menu <guimenu>Options</guimenu> zmieniæ nazwê dystrybucji
           na <guimenuitem>any</guimenuitem>.</para>
       </note>
 
       <warning>
         <para> Ta metoda mo¿e byæ z powodzeniem stosowana na komputerze
           w sieci lokalnej, chronionym przez zaporê ogniow±. Udostêpnianie
           serwera FTP innym u¿ytkownikom Internetu (a nie tylko sieci
           lokalnej) nara¿a nasz komputer na ataki w³amywaczy i inne problemy.
           Decyduj±c siê na to nale¿y koniecznie przestrzegaæ zasad
           bezpieczeñstwa.</para>
       </warning>
     </sect2>
 
       <sect2>
         <title>Przygotowywanie dyskietek instalacyjnych</title>
 
       <indexterm>
 	<primary>instalacja</primary>
 	<secondary>dyskietki</secondary>
       </indexterm>
 
       <para>Je¿eli koniecznie chcemy instalowaæ system z dyskietek
         (co <emphasis>nie jest</emphasis> zalecane), na przyk³ad
         z powodu nieobs³ugiwanego urz±dzenia lub po prostu z zami³owania
         do utrudnieñ, musimy najpierw przygotowaæ dyskietki
         instalacyjne.</para>
 
 	<para>Bêdziemy potrzebowaæ co najmniej tylu dyskietek 1.44&nbsp;MB
           lub 1.2&nbsp;MB, by zmie¶ci³y siê na nich wszystkie pliki z katalogu
           <filename>bin</filename> (binarne pliki dystrybucyjne).  Je¶li dyskietki
           przygotowujemy w DOS-ie, to <emphasis>musz±</emphasis> one byæ sformatowane
           przy pomocy DOS-owego polecenia <command>FORMAT</command>.  W &windows;
           do sformatowania dyskietek mo¿emy u¿yæ Explorera (klikamy prawym przyciskiem
           myszy na stacji <devicename>A:</devicename> i wybieramy
           <quote>Format</quote>).</para>
 
         <para><emphasis>Nie ufajmy</emphasis> dyskietkom sformatowanym fabrycznie.
           Dla pewno¶ci sformatujmy je jeszcze raz samodzielnie.  W przesz³o¶ci wiele
           problemów zg³aszanych przez u¿ytkowników spowodowanych by³o korzystaniem
           z nieprawid³owo sformatowanych dyskietek, dlatego te¿ zwracamy
           na to uwagê.</para>
 
         <para>Je¿eli do przygotowania dyskietek s³u¿y nam komputer z FreeBSD,
           równie¿ powinni¶my je sformatowaæ. Dyskietki nie musz± byæ formatowane
           w DOS-owym systemie plików. Mo¿emy utworzyæ na nich system plików
           UFS, za pomoc± poleceñ <command>bsdlabel</command> i <command>newfs</command>,
           wywo³anych w nastêpuj±cy sposób (na przyk³adzie dyskietek 3.5"
           1.44&nbsp;MB):</para>
 
 	<screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
 &prompt.root; <userinput>bsdlabel -w -r fd0.1440 floppy3</userinput>
 &prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
 
 	<note>
           <para>W przypadku dyskietek 5.25" 1.2&nbsp;MB, wpisaliby¶my odpowiednio
             <literal>fd0.1200</literal> i <literal>floppy5</literal>.</para>
 	</note>
 
         <para>Po takiej operacji dyskietki bêdzie mo¿na zamontowaæ i zapisywaæ
           na nich dane tak samo, jak na innych systemach plików.</para>
 
         <para>Po sformatowaniu dyskietek nale¿y skopiowaæ na nie pliki.
           Pliki dystrybucyjne podzielone s± na kawa³ki o wygodnych rozmiarach,
           tak aby piêæ z nich mie¶ci³o siê na typowej dyskietce 1.44&nbsp;MB.
           Umie¶æmy na ka¿dej z dyskietek tyle plików, ile siê zmie¶ci,
           a¿ wszystkie pliki dystrybucyjne znajd± siê na dyskietkach. Pliki powinny
           byæ umieszczone w odpowiednim katalogu na dyskietce, np.:
           <filename>a:\bin\bin.aa</filename>,
 	  <filename>a:\bin\bin.ab</filename>, itd.</para>
 
         <para>Podczas instalacji, gdy pojawi siê ekran wyboru no¶nika (Media),
           wybieramy <guimenuitem>Floppy</guimenuitem> (dyskietki).  Dalej poprowadzi
           nas program instalacyjny.</para>
       </sect2>
 
       <sect2 id="install-msdos">
         <title>Instalacja z partycji &ms-dos;</title>
 
 	<indexterm>
 	  <primary>instalacja</primary>
 	  <secondary>z MS-DOS</secondary>
 	</indexterm>
         <para>By mo¿na by³o zainstalowaæ FreeBSD z partycji &ms-dos;, kopiujemy pliki
           dystrybucyjne do katalogu <filename>freebsd</filename> w g³ównym katalogu
           partycji - na przyk³ad <filename>c:\freebsd</filename>.  Wewn±trz tego katalogu
           musi byæ czê¶ciowo zachowana struktura katalogów p³yty CDROM lub serwera FTP,
           je¶li wiêc kopiujemy pliki z p³yty CD, dobrze jest skorzystaæ z DOS-owego
           polecenia <command>xcopy</command>.  Dla przyk³adu, poni¿sze polecenia
           przygotuj± minimaln± instalacjê FreeBSD:</para>
 
 	<screen><prompt>C:\&gt;</prompt> <userinput>md c:\freebsd</userinput>
 <prompt>C:\&gt;</prompt> <userinput>xcopy e:\bin c:\freebsd\bin\ /s</userinput>
 <prompt>C:\&gt;</prompt> <userinput>xcopy e:\manpages c:\freebsd\manpages\ /s</userinput></screen>
 
 	<para>W przyk³adzie za³o¿yli¶my, ¿e miejsce dla FreeBSD mamy na dysku
           <devicename>C:</devicename>, a napêd CDROM dostêpny jest jako dysk
           <devicename>E:</devicename>.</para>
 
         <para>Je¶li nie dysponujemy napêdem CDROM, pliki dystrybucyjne mo¿emy
           pobraæ z <ulink
 	  url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">ftp.FreeBSD.org</ulink>.
           Ka¿dy zestaw plików umieszczony jest w oddzielnym katalogu; na przyk³ad zestaw
           <emphasis>base</emphasis> znajduje siê w katalogu <ulink
 	  url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/base/">&rel.current;/base/</ulink>.</para>
 
         <para>Zestawy plików, które chcemy instalowaæ z partycji &ms-dos;
           (i dla których jest na niej odpowiednio du¿o wolnego miejsca), umieszczamy
           w katalogu <filename>c:\freebsd</filename>.  Na potrzeby instalacji minimalnej
           wystarczy zestaw  <literal>BIN</literal>.</para>
       </sect2>
 
       <sect2>
         <title>Przygotowanie ta¶my instalacyjnej</title>
 
 	<indexterm>
 	  <primary>instalacja</primary>
 	  <secondary>z ta¶my QIC/SCSI</secondary>
 	</indexterm>
         <para>Instalacja z ta¶my jest jedn± z najprostszych metod,
           obok instalacji przez FTP i instalacji z p³yty CD.
           Program instalacyjny zak³ada, ¿e ta¶ma po prostu zawiera
           pliki w postaci archiwum tar. Interesuj±ce nas pliki
           dystrybucyjne archiwizujemy na ta¶mie:</para>
 
 	<screen>&prompt.root; <userinput>cd /freebsd/distdir</userinput>
 &prompt.root; <userinput>tar cvf /dev/rwt0 dist1 ... dist2</userinput></screen>
 
 	<para>Przeprowadzaj±c instalacjê powinni¶my upewniæ siê,
           ¿e dysponujemy odpowiedni± ilo¶ci± wolnego miejsca w jakim¶
           katalogu tymczasowym (bêdziemy mieæ mo¿liwo¶æ wyboru tego
           katalogu), by pomie¶ciæ <emphasis>pe³n±</emphasis> zawarto¶æ
           przygotowanej wcze¶niej ta¶my.  Ze wzglêdu na to, ¿e dostêp do danych
           na ta¶mie nie jest swobodny, taki rodzaj instalacji bêdzie wymagaæ
           do¶æ sporej przestrzeni tymczasowej.  Mo¿na za³o¿yæ, ¿e potrzeba
           bêdzie tyle przestrzeni, ile zajmuj± dane zapisane na ta¶mie.</para>
 
 	<note>
           <para>Rozpoczynaj±c instalacjê pamiêtajmy, by ta¶ma by³a
             umieszczona w napêdzie <emphasis>przed</emphasis> uruchomieniem
             komputera z dyskietki startowej.  W przeciwnym razie napêd ta¶mowy
             mo¿e nie zostaæ wykryty podczas rozpoznawania urz±dzeñ.</para>
 	</note>
       </sect2>
 
       <sect2>
         <title>Przed instalacj± przez sieæ</title>
 
 	<indexterm>
 	  <primary>instalacja</primary>
 	  <secondary>sieæ</secondary>
 	  <tertiary>port szeregowy (SLIP lub PPP)</tertiary>
 	</indexterm>
 	<indexterm>
 	  <primary>instalacja</primary>
 	  <secondary>sieæ</secondary>
 	  <tertiary>port równoleg³y (PLIP)</tertiary>
 	</indexterm>
 	<indexterm>
 	  <primary>instalacja</primary>
 	  <secondary>sieæ</secondary>
 	  <tertiary>Ethernet</tertiary>
 	</indexterm>
         <para>S± trzy mo¿liwo¶ci instalacji przez sieæ: port szeregowy
           (SLIP lub PPP), port równoleg³y (PLIP (kabel laplink))
           lub Ethernet (typowa karta sieciowa Ethernet (tak¿e
           PCMCIA)).</para>
 
         <para>Obs³uga protoko³u SLIP jest dosyæ prymitywna i ogranicza
           siê do bezpo¶rednich po³±czeñ, jak choæby kabel ³±cz±cy komputer
           przeno¶ny z innym komputerem. Po³±czenie musi byæ bezpo¶rednie,
           poniewa¿ instalacja za po¶rednictwem SLIP nie umo¿liwia
           dzwonienia; jest to mo¿liwe w przypadku PPP, dlatego te¿ powinno
           siê u¿ywaæ PPP zamiast SLIP, o ile to mo¿liwe.</para>
 
         <para>Je¿eli korzystamy z modemu, to PPP jest najprawdopodobniej
           jedyn± mo¿liwo¶ci±. Zawczasu przygotujmy sobie informacje od dostawcy
           us³ug sieciowych, poniewa¿ bêd± nam one potrzebne na wczesnym etapie
           instalacji.</para>
 
         <para>Je¶li ³±cz±c siê z dostawc± us³ug sieciowych u¿ywamy PAP lub CHAP
           (innymi s³owy, je¶li w &windows; mo¿emy uzyskaæ po³±czenie bez korzystania
           ze skryptu), wówczas wystarczy, ¿e w linii poleceñ <application>ppp</application>
           wpiszemy <command>dial</command>. W przeciwnym razie bêdziemy musieli po³±czyæ
           siê z dostawc± us³ug sieciowych za pomoc± <quote>poleceñ AT</quote>, zale¿nych
           od typu modemu, gdy¿ do dyspozycji bêdziemy mieæ jedynie uproszczony emulator
           terminala.  Wiêcej informacji znajdziemy w po¶wiêconych user-ppp czê¶ciach
           <link linkend="userppp">Podrêcznika</link> i <ulink
             url="&url.books.faq;/ppp.html">FAQ</ulink>. Je¶li wyst±pi± problemy, mo¿emy
           pos³u¿yæ siê poleceniem <command>set log local ...</command>, by komunikaty
           by³y pokazywane na ekranie.</para>
 
         <para>Je¿eli dysponujemy bezpo¶rednim po³±czeniem z innym komputerem
           z FreeBSD (w wersji 2.0-R lub pó¼niejszej), wówczas mamy równie¿ mo¿liwo¶æ
           instalacji przez port równoleg³y.  Prêdko¶æ transmisji danych portem równoleg³ym
           jest zwykle znacznie wy¿sza ni¿ prêdko¶æ przesy³ania portem szeregowym (do
           50&nbsp;kilobajtów/sekundê), dziêki czemu instalacja przebiega szybciej.</para>
 
         <para>Najszybszym wariantem instalacji poprzez sieæ jest wykorzystanie karty
           sieciowej Ethernet.  FreeBSD obs³uguje wiêkszo¶æ popularnych kart sieciowych;
           lista obs³ugiwanych kart (wraz z ich ustawieniami) znajduje siê w dokumencie
           Hardware Notes, do³±czonym do ka¿dego wydania FreeBSD. Je¿eli korzystamy
           z karty sieciowej PCMCIA, pamiêtajmy o tym, by by³a ona w³o¿ona
           <emphasis>przed</emphasis> w³±czeniem komputera.  Niestety, jak dot±d
           FreeBSD nie obs³uguje wk³adania kart PCMCIA w trakcie instalacji.</para>
 
         <para>Bêdziemy musieli znaæ nasz adres IP, maskê podsieci, oraz nazwê
           naszego komputera.  Je¶li instalujemy za po¶rednictwem PPP i nie mamy
           statycznego adresu IP, nie musimy siê przejmowaæ, gdy¿ adres IP mo¿e
           byæ przydzielony dynamicznie przez dostawcê us³ug.  Administrator sieci
           mo¿e nam podpowiedzieæ, jakie parametry podaæ podczas konfiguracji sieci.
           Je¶li do po³±czeñ z innymi stacjami bêdziemy u¿ywaæ ich nazw, a nie adresów
           IP, to dodatkowo bêdziemy musieli znaæ adres serwera nazw i prawdopodobnie
           adres bramy (w przypadku PPP jest to adres IP dostawcy). Je¿eli mamy zamiar
           instalowaæ za po¶rednictwem FTP i proxy HTTP, bêdzie nam ponadto potrzebny
           adres proxy.  Skontaktujmy siê z administratorem sieci lub dostawc± us³ug
           sieciowych <emphasis>przed</emphasis> rozpoczêciem instalacji, je¶li nie znamy
           którego¶ z wymienionych powy¿ej adresów.</para>
 
 	<sect3>
           <title>Przed instalacj± przez NFS</title>
 
 	  <indexterm>
 	    <primary>instalacja</primary>
 	    <secondary>sieæ</secondary>
 	    <tertiary>NFS</tertiary>
 	  </indexterm>
           <para>Instalacja przez NFS jest raczej ma³o skomplikowana.  Wystarczy po prostu
             skopiowaæ wybrane pliki dystrybucyjne na serwer, nastêpnie podczas instalacji
             wybraæ NFS jako no¶nik i wskazaæ serwer.</para>
 
           <para>Je¿eli serwer wymaga stosowania <quote>uprzywilejowanego portu</quote>
             (zwykle jest tak w przypadku stacji roboczych Sun), musimy to zaznaczyæ
             w menu <guimenu>Options</guimenu> (opcja <literal>NFS Secure</literal>),
             zanim rozpoczniemy instalacjê.</para>
 
           <para>Je¶li nasza karta sieciowa jest niezbyt dobrej jako¶ci i nie grzeszy
             prêdko¶ci±, mo¿emy w³±czyæ opcjê <literal>NFS Slow</literal>.</para>
 
           <para>Instalacja przez NFS wymaga, by serwer obs³ugiwa³ montowanie
             podkatalogów, na przyk³ad je¶li katalog dystrybucyjny FreeBSD&nbsp;&rel.current;
             znajduje siê w: <filename>ziggy:/usr/archive/stuff/FreeBSD</filename>,
             to serwer <hostid>ziggy</hostid> musi umo¿liwiaæ bezpo¶rednie montowanie
             katalogu <filename>/usr/archive/stuff/FreeBSD</filename>, a nie tylko
             <filename>/usr</filename>, lub <filename>/usr/archive/stuff</filename>.</para>
 
           <para>We FreeBSD w pliku <filename>/etc/exports</filename> mo¿liwo¶æ montowania
             podkatalogów w³±cza siê opcj± <option>-alldirs</option>.  W innych serwerach
             NFS mo¿e byæ inaczej.  Je¶li otrzymujemy od serwera komunikaty o tre¶ci
             <quote>permission denied</quote> (odmowa dostêpu), prawdopodobnie jest
             to spowodowane w³a¶nie nieprawid³owym ustawieniem wspomnianej opcji.</para>
 	</sect3>
 
       </sect2>
   </sect1>
 </chapter>
diff --git a/share/pgpkeys/gavin.key b/share/pgpkeys/gavin.key
index 00a5f7f09d..f5b66c4aeb 100644
--- a/share/pgpkeys/gavin.key
+++ b/share/pgpkeys/gavin.key
@@ -1,425 +1,571 @@
 <!-- $FreeBSD$ -->
 <!--
 sh ./addkey.sh gavin A093262B;
 -->
 <programlisting xmlns="http://docbook.org/ns/docbook" role="pgpfingerprint"><![CDATA[
 pub   1024D/A093262B 2005-02-18
       Key fingerprint = 313A A79F 697D 3A5C 216A  EDF5 935D EF44 A093 262B
-uid                  Gavin Atkinson <gavin@16squared.co.uk>
 uid                  Gavin Atkinson (FreeBSD key) <gavin@FreeBSD.org>
 uid                  Gavin Atkinson (Work e-mail) <ga9@york.ac.uk>
+uid                  Gavin Atkinson <gavin@16squared.co.uk>
 uid                  Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
+uid                  Gavin Atkinson (Work e-mail) <gavin.atkinson@york.ac.uk>
 sub   2048g/58F40B3D 2005-02-18
 ]]></programlisting>
 <programlisting xmlns="http://docbook.org/ns/docbook" role="pgpkey"><![CDATA[
 -----BEGIN PGP PUBLIC KEY BLOCK-----
 
 mQGiBEIWBmcRBACSBNLMQiqMhQLXqjCfQtRveQ3hyCECyWf6dmlxLYCf5EjHrka9
 +q+spQtkYciFHDotxtCJjJvwaxO3Cxjfhssx1ZPfyezkfU98qbyem/N62Gsr1l1y
 6zJKiAgJt+sOYnBvyCADFT/2nUeRZDN9jjfPI23uZsq6xOAeUVUWsw4KuwCgr4YD
 l7f/IhL9xaRF+wdRa/MVfOcD/1jR464Mmj8PNRFn21aFHVpPE1ZOsunGv8uyjfO1
 TGyY7EThy+ZcaBSEfjHLEHKXOYuPJ1acOe70AgrBom4WjrxtGptpSwyi1lRJvt8z
 vjOWniUsNf6hInyUSMdeIyYT3BuLawlxrQ2q7SxzpU2n8zeH18HNnzsKAt+fAue7
 A8fNA/0V6E/NGGM3L2v/0S4O64ijmskGsc8MamyfRqaDv+1Zr44jY/GwXQyl1j5P
 pHEFxzFl4IfCJbUikoIBWoWT92AIZL4/mji6vZjlmUrgJ9eBTAvF0CRMS4mN9/4a
-Hit4kZ4moR/4r6PxLC7XX+QrVBoUe+oAZstOi7eCSXi5Xj2NmLQwR2F2aW4gQXRr
-aW5zb24gKEZyZWVCU0Qga2V5KSA8Z2F2aW5ARnJlZUJTRC5vcmc+iGAEExECACAF
-AkbK5pUCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRCTXe9EoJMmK0KnAJwP
-Bhj4uOdhe2cheGw/ujQz+HzNsQCghjy8yyud9WQYyY5xNLt1f6j2OMGIRgQQEQIA
-BgUCSltg3AAKCRDtytXlKjtj6YonAJ92cnZOiLvl0xQygGGBXU9FOgpHLACdEZ+g
-4NUPA0Pyieuq9okFvgA82WS0LUdhdmluIEF0a2luc29uIChXb3JrIGUtbWFpbCkg
-PGdhOUB5b3JrLmFjLnVrPohgBBMRAgAgAhsDAh4BAheABQJGyudGBgsJCAcDAgQV
+Hit4kZ4moR/4r6PxLC7XX+QrVBoUe+oAZstOi7eCSXi5Xj2NmLQtR2F2aW4gQXRr
+aW5zb24gKFdvcmsgZS1tYWlsKSA8Z2E5QHlvcmsuYWMudWs+iGAEExECACACGwMC
+HgECF4AGCwkIBwMCBBUCCAMEFgIDAQUCUA3Q4QAKCRCTXe9EoJMmK/s3AKCqP/7x
+xrRHSnCsPanX+TMJMoFrhQCeKRAm9Po+K/WPyGwSaqo85lsza0iIRgQSEQIABgUC
+QhtuoAAKCRCpnyS0ZzRRql1yAJ9dX6Q62FS0tcwewm4wBUKfrMW8GQCfViglmVSv
+r7kN+FRo5aI4vRixfCmIRgQQEQIABgUCQh6MhwAKCRAgmbZMvxVJC/fGAJ0duuRd
+/DexkVimAcGJIAv9lmcsHwCdG3s9oU/MzN4Ouy1tJ/RQHWpXQOuIRgQSEQIABgUC
+Qh+QlwAKCRBtnOWrBC4AyUIiAJ9GrGh8oboARrzt+AbQ1UFJzgcyTACg/W3ejF8X
+omhyudOrrtxuXOc5AQ6IRgQSEQIABgUCQiBoGwAKCRCSNJC+sAkIn9ZHAJ9ljXu1
+o/8bBFzhCp2L1NoR+0ntXACfemaDJBX6noUhfdq9nnW0szxEGUGInAQTAQIABgUC
+QiCIhwAKCRB0nx5vVV/IpamPA/46qGzAdm2IaFTdHZinh8V5PtAJfUyp7jJqjdUV
+ZlW+mM03xdyZM1LW0KM8E/QaJ9yD8UNYpXKJGBIZwkaG3fQ9nBdoq4RRDoej7Orj
+F9qsMJXSzQQY7ZiuVfLVfecaRVj+wlYA7qHUjU1Ah6srZBzV1roFni8wcYwXuO4t
+V9jaqYkBIgQQAQIADAUCQh+6OwUDABJ1AAAKCRCXELibyletfK1JB/0RnHte+Ui5
+iqXqABzgNk5z4xMRm68pYBAoUSEL0WDFYoySaZXFslGdufzraOkdX6vTfXsUKu4v
+SCgelcoSLp9a+ov4cUQYLSGuSshNIOmZRLFXyeO4cNto7tQKxiyg0HwP3wxJ6mtj
+oCSGpRJ48drjZ2WeLanMHHp1bz4GXC7TfK4YFRHICJVCYwGjo7cOGO9nVqnQMU9l
+otCIQ6H18pB53mUMfFhitXKaAiTgHhAMtOWk83BnFgbAfQnGIZob4J0fuc0PGhJn
+PtwmbfWeFfAf7IErOYc64H3rcwtBu6QIlc0RUvxdND8/iVxx0r9g5zKbfh+lUmA/
+xt/+FhkrzdtEiEYEExECAAYFAkIsPNcACgkQKeFPmTkbOShZDwCgvdnTa6/c5LnZ
+gosbpQhGhWToL8MAn3WEnqCQRKvcGrcq+mO9qdc1T7hDiEYEEBECAAYFAkIvFqUA
+CgkQoLS7q6lYlVUrEQCfWt1UyjuSn2CszXIRMsOHe6pdjbkAnAgvQrZaeSfSHoZO
+CYbxgpLA38KwiEYEExECAAYFAkJlGlIACgkQYgOKS92bmRDBWACgpbAYHjsbNr5O
+MWTLt4jsnvSCYkUAn2nMI/PXaXJl2cFU+rs1QzFxC08RiJwEEwECAAYFAkJlGmgA
+CgkQxSga5QRk5+X0dAP9HiO8Xwz5y7i2FER23mA8lL8yV9aE+mSYPK17Wo4NZaGG
+Pd67B9ONUtPsMfav+Gybn0pxKPlMkALPvH3t8GxIdfGUR2CTCOOChc+H0fTNJ243
+TJmRHutTZ+tZx556SC6b/B1Pll5aWIkshmwS1hvSJFlMhvTLPl4Cp71jCNMBFeqI
+RgQQEQIABgUCQnFcsAAKCRCbxLc+I60jyX32AKCWZbHBHuuaIOrhdcIR48fpkOUH
+KgCgkRTIQDhUknN/+rckw9HuOAaqOJGIRgQSEQIABgUCQqN9+AAKCRDbxu0yF8Vd
+3bepAKCHKskuYBp3w13AcPBeoaYvJ8Vj1QCglszfpx/8/TToTxEbvqBnctCfgKiI
+RgQTEQIABgUCQvkysAAKCRDtFpR/ZKGUTbBDAJ4tHs3/xALzoK5sEImKvbrEqrwp
+gACeNixZohoEuglhFB/+Y3obGj/Y9D2JASIEEAECAAwFAkLsxoMFAwASdQAACgkQ
+lxC4m8pXrXyogQf+KMMmqS9y9OdgrES5VQJsaYkdMehe5gRbQh15WMg/Dv2cqhw5
+pcHS3sOCiQdT+w8GQaszuWg/833XqDI4owCZ3xhky81VpmW8/g1dBwJf4q3BxILh
+X0k+AXpyFiSvIfRIaQDwNaGQCvsXjATHr2wIWLiHukn4Fs13Z9ePh6Qkd3I9Zd8m
+YEmHFGfOPWQXiypzKebKR90/UIc62pq7HOYDLd2YCrAgMn/+YR6yitttpCsGS1Pb
+GlvuFp7GIuPco8OwbShYGU8v1mZZ6przs0zJ87WzmqsRUNouEHJ80P+RldVHun59
+rdZzkCtuDVOlVgWSUrM0noh+srHk/fsWRLr8gokBIgQQAQIADAUCQu1swwUDABJ1
+AAAKCRCXELibyletfOtZCADHI3IwEJBZKXFwRPhAuse/kniR8Jm5jlfE1MHZ5T72
+Anhmn5IGX565TDn2tFw4zB3Tq+c0fZaKq7PboOpbexZFiqaPtC6LybsE18qc0vy0
+KRiF5Bd0Dw3zf3nPGSXvUNgjdII4kYv3QD2puxV/71Rt7Bgq2IapBF5I5mx1ABjR
+zPGF8Uqn9kBui8HRv1hGRrMQbSrpNEd9+XP1A8GpIlfebMz7OAaND2h998/YFLjG
+JsDcYQ8DWWNZjMbtxKuNORCfiNWO7TBNmn63M2kiGFpM+jDJ03B0gpq46OvLmvja
+iONwAadFzvkgSPdvAmDZopC9dGcsoKvaqXRm5sAZuZMiiEYEEBECAAYFAkL5z1QA
+CgkQ7crV5So7Y+l4FACeODO0GjIPUjNaZrvSpoVlamSPsvMAnRUgxZKcWfH7IoI1
+8/ozSeg6oLfUiQEiBBABAgAMBQJCMVDNBQMAEnUAAAoJEJcQuJvKV6188AEIAJBB
+iTAKSnCTVuwVhcKlskYbeRbkEjvakU1a56z76lyYNRE/NoBaFkz1ExsGcgkgXwiY
+Fx2gOuw7O7Zv44f3hh7uZPWP94vcrQ7ffUD7HQPKAXpc1KUR6Wsso+aCXSWZUTXZ
+GLm1mkaVRbHH3+X+kRBAulAaTw86rXiSzDXU/L1JMh4eB6EBQicpKQdg0xv3J5dB
+bvOYO78PoduMJT5tuRoyfEJ/sRhi5nRY+smVawo2LWRdunU746Kz6obbPDUzPJ6o
+p7MlN3v5f9CVM1kghCKaJMe4z78wFgySz+oho5snDL+iol+iVa3hD/Z80NF6rUXu
+WE6IGW7vzXJV4xP0lcuJASIEEAECAAwFAkJCdF8FAwASdQAACgkQlxC4m8pXrXwW
+uQf/YFO9OUW0mrI0bdz2V2h+tDlc4HQWy+eBIraWu7wl+8upB4r3HfIcAcW3OlBM
+5DduSnFn36R6LzlkLqDxKsB43H/zWvcvI7g/iC4IjMPNQT/Nz3MjjdI7K1SpjV+R
+3jU0qlyzEfbK8xo70+IuM1vWNUrJKmPAM6SKIvI/BvqsfXE+r4Cmgr61VzExam6s
+0BAW2rbz2EfE6197LQ1guCOsNbAHERja6JGpzFbTJpToXdeZ6Cds2zMzTfjEIBas
+/vfMua6ctRc6tyPWqS3EV/bj+w6iDC1TalQ8xS6NKrIPk8GSeLQrSTs4wQ3DOd0Y
+J7a9yuXoU7WSYqF2x3SIULFYRokBIgQQAQIADAUCQlQzcQUDABJ1AAAKCRCXELib
+yletfPnBB/9hWpNWfIdgMn04jzjPZWcjr14RVOS/vmLLXGBP8ZcU29sLaXp+1q7e
+LQvRWz61iuGavAW2sZArl9W5wHRVHnlLiddPNpYBG3zL5QMHzlXZXxk77cxsBbGw
+3de/VSiIG5r8nOqcP8QL8gyiZIKf9zvXLfvdCUu9/5Lb5FBvBfOeGb7MCUHbP4pF
+bwzEtDd4q29vCXdCe3FdG1urTcTzyHwf4AD8nDAndo+OQ4Ljk/LhzSwObzjFMBvR
+70f1wLtNK/mrdO6Vtd/CSo6ZlFsxwHEgHdUrIHYSCcKMHIsZtt3SYYn733VrnQDt
+hZBj8/ez8LkOZd3kciY2T422xCGk+7AYiQEiBBABAgAMBQJCZf7cBQMAEnUAAAoJ
+EJcQuJvKV618pBoH/iEd0KObc2rjg6SmeN2JvupUgqmNxg4AOnWgKaqZyFpNV6Jk
+9MRl8UYjxqb6dPKHs+LJxUP66gHObd1USeq2V4pSz2dRZKgD5+Qu4xZUiyMm9TlR
+UixGeMXZcGQ2nk0+BT/H5Ge7NCBG8g2DzvDvCdev5MCH5Ck8h/w6m7RJmBOXxRfM
+hn8TJ2PSkaGgQdYBXuwZeSgsrNwThxRol9ixKjZQovvPIUU6nP37JCHUO63PNj43
+nMqo0vP+LE0FbnM+fv+ydeclqduSBw/+THzNDEEYPJcq4czMJZ/s3HwJYAMJ2YaU
+cK9b1ga4+tDMzjj0aAlDGIYCQB7FbGtSuMINoHmJASIEEAECAAwFAkJ3JXcFAwAS
+dQAACgkQlxC4m8pXrXx3LwgAlzp+XDu2Cz6tYLOZmnqVo8f2FrwSS4RUzuVU1Bw7
+rm+4S3FlGdBzx6ukDEC31TqSd0wigwsd+xYafVoONAMsgqfAlbr/Vlxz/f8kHUtv
+ys9POFIsCj6KvO7MQMc5v6vIgnZMU9b/Wkwz9dbrOZyp84hKl5BvRNt1bhPGD+a+
+ROkc168Q6hRGTmxKtDmd7HYEArBdMIj0V6DVu5kwzULHkgG+8SXAgDEdHzdGIUNT
+riG+4gmoIRmgKcNLHWOTfV1LqPZsvT0WCmXVZTKnW8F4497cqP25t4JaWYqpOYOa
+QFsvTXrqspZC4jk1Tu9xTUkrJhUz5WLism5w924yDhMhz4kBIgQQAQIADAUCQonQ
+ywUDABJ1AAAKCRCXELibyletfKsJB/9MM2Xuwwp8w2o3E+IVvyIFC+tCJXMvoT1u
+cQEu2QZSQ8pirF/ezwoznywx4WebMQTeLudbe0lr4IMgmv/wZ1M7p5G3iOJ/Q4Ou
+wnMvMq9I4uxbNYItloYLwXcC3svLBVk9rqq+Ci22UxDuC5EYFhE8GQy8eFmuR/+M
+hGuQ5EMz9HQWegNDqvTbEhkoIMMvOixZuxUGl2cPIose+fJlosyYRZszflC08/mQ
+Um9M/d27zuI0Ii2ia1vskRAkswBwHboJwJ0w9VdcFXN2jFFhMly93f/RBEejWW4B
+zbZOqB0fPc7jmHVnfoelZPl21r7r6BaLwUxrXjdJnK1E0mHBWPt6iQEiBBABAgAM
+BQJCnO1nBQMAEnUAAAoJEJcQuJvKV6187V0H/R0YaMUQlKBfwvH0ssT9+j6wgN1Q
+pBaDMsO0HGSVdzOy4ZVTi2S2byxdvuR5vCs0E+7L+a+WVb4ZC1yhHbr1dhieNiw3
+oKMXeGDsz6fb95Xi0ku7pgF6VXR0nw+gyqt9OrEnviGnt0rxL3hcfLmd/zXQBkcH
+kDvPBkMgr1OP5V6u8SWa7m+9nhyUn9hTYPHIsQkW4gv8CL1nUAqrUS3oyrUGt13e
+0aib2H7ONO28ATvQA5XKdMMCsndgbdRCReWzWPGqQ488sGqapKGjUw2v5VuCSdjP
+yH8mb/D8uL7XhO+xjhWtV9mliCa10xX/6i619zjuhE3PiJXhrypYFCpsI2GJASIE
+EAECAAwFAkK3V8EFAwASdQAACgkQlxC4m8pXrXzBCQgAgy3Nyi/hqbxChdn5ZGqV
+3a87p8pCrbyPUoxtSvH6eYNOfXtJrqTKn6zZ5gchKIRvvf9tml94OqiBNIkyaJol
+s9Z2bKCS9CrzCtiwi3xdY2AiGsueCB0d/MFJ9FK4F8GhjPVgBPndq9f3yImellXm
+i+lrobcV7g1eo0Ace9y5eXdCndBfEQhhIK8NMGuOTYtVdrmEjbHCtJPOvJGh0wkq
+n1cPfd5G6ZE/yezc7bDBziwqnhysW18pZp1Qg+ddVCslB/RqVBqeNH4lCEqrxt1n
+W9Zs/KNGLynW/6ZsSS2q8ney+HOiicYhBk+v6K8tGxTTTNMenZpKfNp9gQ5TivRO
+t4kBIgQQAQIADAUCQtEZowUDABJ1AAAKCRCXELibyletfLTuB/0WZmXqAsWd8ze/
+m9z0T5PtYgMQ1Yv+cEeh4JXzDNuxvZLpz7nM3Q3v6mHDZECLnT5/hIkV2ma4tNV4
+wKcycgo8VISxOrbxMbXMo96HOPKiRvPfN6+E9gj0M9AswmARPHbsGMezpUKDzbu8
++NBEJAO+DJZYV1gybUMD7s4SzDx+qbfw6YbzP0EW6MXIKMtwdqHbn33lo+S7+Ens
+fTVSgHOBe5BTgx7ADSAWW/BxHgTObZx7CzJ8Uj6iv2I8OPiiD7fq8r+zaIRe3JMT
+NYfPNchIeKMf670ItD6qPkFRtp1VVYtqfjK+hZo1kBG2awHvdk9Ca8NvVy3iJ2KG
+g6xx+9Q8iQEiBBABAgAMBQJC0b+fBQMAEnUAAAoJEJcQuJvKV618CQ4H/j/tT1Ot
+grAv/4SxBl0uQAiHXFUU6ZdsgPqP6QcW2gY2+HXjRedsnP3aXTYJLZ2vYAMvm382
+BU4v4LqK9QFx+YW86nizVWG68rLAkBG3Rur62yxghZYklmg7pJP0+Rsm8kn8LXSR
+4E2G6Q9VmAfgmw6EzkOYzbgW+kVyHGSLMj9DtFAoUzwhEXJPyEBR8yZ0t/b52rVK
+/4ZgzTYrK62dOUIPoI54NgrSCBNMiGbpv+f/IFvGAgZLlhk+bIV8ODsfwEFGifHS
+5kZd0nbvcGU/q5mE8vOQXpsgEbxY0qcfpfx+IXvR9iHJ7iiKea3Ha0zaOemOKZYJ
+Nvi7y1Q5BmITw+iIRgQQEQIABgUCRGhXHQAKCRD/wPFMhMcbbh0kAJ4kkql3b0eT
+rYAyIGXQFnbH4xfFtgCgjUvnc77mkvnQkFZgOdXu4I4PgKmIRgQSEQIABgUCRgLT
+cwAKCRAWwTtft+SuksyIAKCX+/mCraHOxPXaUVCvbhCaw4WQdQCfaAcF6NIFmaj0
+bWZaee3EgPLioIOIRgQQEQIABgUCRgG2wwAKCRCpad1zbqleZwxFAKCpUzaRgoE4
+nJS/stmXMcyb6lSMcgCdHg3Yk2BMH44hUeeAmu0l3lsoSw2IRgQQEQIABgUCRgEI
+egAKCRC3zGx8mAQiqDxFAKCnINbx8eFt5t9afQiV74tpq22YSQCg7Ok+VsGBpejy
+zd1Qe0gEFl0iLQmIfAQQAQIABgUCRgEHRwAKCRDkU1D0fKgzbbGkAwCXS8GR5eV9
+jfpoR6uoyX6hddznSp2igNkvkGQf+HKJnDTJd0xttTCHDBHwQ1GlBPIC5r2DL/BY
+vUoTyhqBLAlDQbUX0CwHThf7BXFplVheRTCpra24UCjzTCuU7a1U2Y+InAQQAQIA
+BgUCRgD5ggAKCRD7x41iJ6OpTfCLA/wMlvzDm69vvXPGTspJbZwjHKlafF2AdOfI
+TXvIKa6GYYUDL84XkzOXBi/OFRMC+mGzGuwzRv7ydJ6bXue+GpEE+wVioif5ndVN
+d+MEf8d8B3rNROR+HmmaDXcfzfrOPeJT29DU5YW7kqj3aU+8WiMZjOOrZqmVLrFx
+MTp1GncOB4hGBBARAgAGBQJGAmLDAAoJEP3EfXaEwL2szmoAn2KyP10LuVj3Lqk/
+5AU/S5rYSzl7AKCNwmlcA2SPRVPL61n8bqlXdy7SIYhGBBARAgAGBQJGAnRSAAoJ
+EFE2UCdDS/Bwj0IAn2CVkwvXdo69mb/y+BQiRZy91TFdAJ4klwGRzMNvHT6NiGQO
+8+JdMKJ22YicBBABAgAGBQJGA47pAAoJEB9/qQgDWPy9r1cD/iBaDJRZzYsLxq0Y
+UHms96AoLhKPY3VWJzpqBlYAx2oWFELWZmdwtmTYa5what8kUDUkmkXt5B9Vj1fh
+xyuT4FIpdlhDQ89D4rSehoDl0Y+SLUWDHow5hLaJpraN5L7GWpBJ7JRMZGgX08cN
+d6/YWToznrJFlv+pKPFxXyp/p9yPiEYEEBECAAYFAkYKq8wACgkQITGblEwaW+Vk
+dwCguMuRh7ZcG+APg5GXDC6qLGi8OKMAnjabrWolmcn8qRkt0Zc1E5KzY5X1iF4E
+ExECAB4FAkIWCfsCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQk13vRKCTJisP
+ewCeL00JVLTC7h/7qjHT/SrbfG175G0AoJlGUIlV7NDnPs7Vl5o4HpA265iziHEE
+ExECADIFAkr4Y6orGmh0dHA6Ly93d3cucG9sbGluZ2VyLm9yZy51ay9wZ3AtcG9s
+aWN5LnR4dAAKCRBgesqFMHiP70w3AKCMIyacHDDlh02rS/BU6kMt1feUOgCTBa0A
+ys5/qNIRfPwq0LUNahbHzIhgBBMRAgAgAhsDAh4BAheABQJGyudGBgsJCAcDAgQV
 AggDBBYCAwEACgkQk13vRKCTJiuFGQCfQ2C3R35UYN+H99vAUu6473TwCJMAoJWj
-7SZDdibo6eXfhwU4u9zuhYD3iEYEEhECAAYFAkIbbqAACgkQqZ8ktGc0UapdcgCf
-XV+kOthUtLXMHsJuMAVCn6zFvBkAn1YoJZlUr6+5DfhUaOWiOL0YsXwpiEYEEBEC
-AAYFAkIejIcACgkQIJm2TL8VSQv3xgCdHbrkXfw3sZFYpgHBiSAL/ZZnLB8AnRt7
-PaFPzMzeDrstbSf0UB1qV0DriEYEEhECAAYFAkIfkJcACgkQbZzlqwQuAMlCIgCf
-RqxofKG6AEa87fgG0NVBSc4HMkwAoP1t3oxfF6JocrnTq67cblznOQEOiEYEEhEC
-AAYFAkIgaBsACgkQkjSQvrAJCJ/WRwCfZY17taP/GwRc4Qqdi9TaEftJ7VwAn3pm
-gyQV+p6FIX3avZ51tLM8RBlBiJwEEwECAAYFAkIgiIcACgkQdJ8eb1VfyKWpjwP+
-OqhswHZtiGhU3R2Yp4fFeT7QCX1Mqe4yao3VFWZVvpjNN8XcmTNS1tCjPBP0Gifc
-g/FDWKVyiRgSGcJGht30PZwXaKuEUQ6Ho+zq4xfarDCV0s0EGO2YrlXy1X3nGkVY
-/sJWAO6h1I1NQIerK2Qc1da6BZ4vMHGMF7juLVfY2qmJASIEEAECAAwFAkIfujsF
-AwASdQAACgkQlxC4m8pXrXytSQf9EZx7XvlIuYql6gAc4DZOc+MTEZuvKWAQKFEh
-C9FgxWKMkmmVxbJRnbn862jpHV+r0317FCruL0goHpXKEi6fWvqL+HFEGC0hrkrI
-TSDpmUSxV8njuHDbaO7UCsYsoNB8D98MSeprY6AkhqUSePHa42dlni2pzBx6dW8+
-Blwu03yuGBURyAiVQmMBo6O3DhjvZ1ap0DFPZaLQiEOh9fKQed5lDHxYYrVymgIk
-4B4QDLTlpPNwZxYGwH0JxiGaG+CdH7nNDxoSZz7cJm31nhXwH+yBKzmHOuB963ML
-QbukCJXNEVL8XTQ/P4lccdK/YOcym34fpVJgP8bf/hYZK83bRIhGBBMRAgAGBQJC
-LDzXAAoJECnhT5k5GzkoWQ8AoL3Z02uv3OS52YKLG6UIRoVk6C/DAJ91hJ6gkESr
-3Bq3KvpjvanXNU+4Q4hGBBARAgAGBQJCLxalAAoJEKC0u6upWJVVKxEAn1rdVMo7
-kp9grM1yETLDh3uqXY25AJwIL0K2Wnkn0h6GTgmG8YKSwN/CsIhGBBMRAgAGBQJC
-ZRpSAAoJEGIDikvdm5kQwVgAoKWwGB47Gza+TjFky7eI7J70gmJFAJ9pzCPz12ly
-ZdnBVPq7NUMxcQtPEYicBBMBAgAGBQJCZRpoAAoJEMUoGuUEZOfl9HQD/R4jvF8M
-+cu4thREdt5gPJS/MlfWhPpkmDyte1qODWWhhj3euwfTjVLT7DH2r/hsm59KcSj5
-TJACz7x97fBsSHXxlEdgkwjjgoXPh9H0zSduN0yZkR7rU2frWceeekgum/wdT5Ze
-WliJLIZsEtYb0iRZTIb0yz5eAqe9YwjTARXqiEYEEBECAAYFAkJxXLAACgkQm8S3
-PiOtI8l99gCglmWxwR7rmiDq4XXCEePH6ZDlByoAoJEUyEA4VJJzf/q3JMPR7jgG
-qjiRiEYEEhECAAYFAkKjffgACgkQ28btMhfFXd23qQCghyrJLmAad8NdwHDwXqGm
-LyfFY9UAoJbM36cf/P006E8RG76gZ3LQn4CoiEYEExECAAYFAkL5MrAACgkQ7RaU
-f2ShlE2wQwCeLR7N/8QC86CubBCJir26xKq8KYAAnjYsWaIaBLoJYRQf/mN6Gxo/
-2PQ9iQEiBBABAgAMBQJC7MaDBQMAEnUAAAoJEJcQuJvKV618qIEH/ijDJqkvcvTn
-YKxEuVUCbGmJHTHoXuYEW0IdeVjIPw79nKocOaXB0t7DgokHU/sPBkGrM7loP/N9
-16gyOKMAmd8YZMvNVaZlvP4NXQcCX+KtwcSC4V9JPgF6chYkryH0SGkA8DWhkAr7
-F4wEx69sCFi4h7pJ+BbNd2fXj4ekJHdyPWXfJmBJhxRnzj1kF4sqcynmykfdP1CH
-OtqauxzmAy3dmAqwIDJ//mEesorbbaQrBktT2xpb7haexiLj3KPDsG0oWBlPL9Zm
-Weqa87NMyfO1s5qrEVDaLhByfND/kZXVR7p+fa3Wc5Arbg1TpVYFklKzNJ6IfrKx
-5P37FkS6/IKJASIEEAECAAwFAkLtbMMFAwASdQAACgkQlxC4m8pXrXzrWQgAxyNy
-MBCQWSlxcET4QLrHv5J4kfCZuY5XxNTB2eU+9gJ4Zp+SBl+euUw59rRcOMwd06vn
-NH2Wiquz26DqW3sWRYqmj7Qui8m7BNfKnNL8tCkYheQXdA8N8395zxkl71DYI3SC
-OJGL90A9qbsVf+9UbewYKtiGqQReSOZsdQAY0czxhfFKp/ZAbovB0b9YRkazEG0q
-6TRHfflz9QPBqSJX3mzM+zgGjQ9offfP2BS4xibA3GEPA1ljWYzG7cSrjTkQn4jV
-ju0wTZp+tzNpIhhaTPowydNwdIKauOjry5r42ojjcAGnRc75IEj3bwJg2aKQvXRn
-LKCr2ql0ZubAGbmTIohGBBARAgAGBQJC+c9UAAoJEO3K1eUqO2PpeBQAnjgztBoy
-D1IzWma70qaFZWpkj7LzAJ0VIMWSnFnx+yKCNfP6M0noOqC31IkBIgQQAQIADAUC
-QjFQzQUDABJ1AAAKCRCXELibyletfPABCACQQYkwCkpwk1bsFYXCpbJGG3kW5BI7
-2pFNWues++pcmDURPzaAWhZM9RMbBnIJIF8ImBcdoDrsOzu2b+OH94Ye7mT1j/eL
-3K0O331A+x0DygF6XNSlEelrLKPmgl0lmVE12Ri5tZpGlUWxx9/l/pEQQLpQGk8P
-Oq14ksw11Py9STIeHgehAUInKSkHYNMb9yeXQW7zmDu/D6HbjCU+bbkaMnxCf7EY
-YuZ0WPrJlWsKNi1kXbp1O+Ois+qG2zw1MzyeqKezJTd7+X/QlTNZIIQimiTHuM+/
-MBYMks/qIaObJwy/oqJfolWt4Q/2fNDReq1F7lhOiBlu781yVeMT9JXLiQEiBBAB
-AgAMBQJCQnRfBQMAEnUAAAoJEJcQuJvKV618FrkH/2BTvTlFtJqyNG3c9ldofrQ5
-XOB0FsvngSK2lru8JfvLqQeK9x3yHAHFtzpQTOQ3bkpxZ9+kei85ZC6g8SrAeNx/
-81r3LyO4P4guCIzDzUE/zc9zI43SOytUqY1fkd41NKpcsxH2yvMaO9PiLjNb1jVK
-ySpjwDOkiiLyPwb6rH1xPq+ApoK+tVcxMWpurNAQFtq289hHxOtfey0NYLgjrDWw
-BxEY2uiRqcxW0yaU6F3XmegnbNszM034xCAWrP73zLmunLUXOrcj1qktxFf24/sO
-ogwtU2pUPMUujSqyD5PBkni0K0k7OMENwzndGCe2vcrl6FO1kmKhdsd0iFCxWEaJ
-ASIEEAECAAwFAkJUM3EFAwASdQAACgkQlxC4m8pXrXz5wQf/YVqTVnyHYDJ9OI84
-z2VnI69eEVTkv75iy1xgT/GXFNvbC2l6ftau3i0L0Vs+tYrhmrwFtrGQK5fVucB0
-VR55S4nXTzaWARt8y+UDB85V2V8ZO+3MbAWxsN3Xv1UoiBua/JzqnD/EC/IMomSC
-n/c71y373QlLvf+S2+RQbwXznhm+zAlB2z+KRW8MxLQ3eKtvbwl3QntxXRtbq03E
-88h8H+AA/JwwJ3aPjkOC45Py4c0sDm84xTAb0e9H9cC7TSv5q3TulbXfwkqOmZRb
-McBxIB3VKyB2EgnCjByLGbbd0mGJ+991a50A7YWQY/P3s/C5DmXd5HImNk+NtsQh
-pPuwGIkBIgQQAQIADAUCQmX+3AUDABJ1AAAKCRCXELibyletfKQaB/4hHdCjm3Nq
-44Okpnjdib7qVIKpjcYOADp1oCmqmchaTVeiZPTEZfFGI8am+nTyh7PiycVD+uoB
-zm3dVEnqtleKUs9nUWSoA+fkLuMWVIsjJvU5UVIsRnjF2XBkNp5NPgU/x+RnuzQg
-RvINg87w7wnXr+TAh+QpPIf8Opu0SZgTl8UXzIZ/Eydj0pGhoEHWAV7sGXkoLKzc
-E4cUaJfYsSo2UKL7zyFFOpz9+yQh1DutzzY+N5zKqNLz/ixNBW5zPn7/snXnJanb
-kgcP/kx8zQxBGDyXKuHMzCWf7Nx8CWADCdmGlHCvW9YGuPrQzM449GgJQxiGAkAe
-xWxrUrjCDaB5iQEiBBABAgAMBQJCdyV3BQMAEnUAAAoJEJcQuJvKV618dy8IAJc6
-flw7tgs+rWCzmZp6laPH9ha8EkuEVM7lVNQcO65vuEtxZRnQc8erpAxAt9U6kndM
-IoMLHfsWGn1aDjQDLIKnwJW6/1Zcc/3/JB1Lb8rPTzhSLAo+irzuzEDHOb+ryIJ2
-TFPW/1pMM/XW6zmcqfOISpeQb0TbdW4Txg/mvkTpHNevEOoURk5sSrQ5nex2BAKw
-XTCI9Feg1buZMM1Cx5IBvvElwIAxHR83RiFDU64hvuIJqCEZoCnDSx1jk31dS6j2
-bL09Fgpl1WUyp1vBeOPe3Kj9ubeCWlmKqTmDmkBbL0166rKWQuI5NU7vcU1JKyYV
-M+Vi4rJucPduMg4TIc+JASIEEAECAAwFAkKJ0MsFAwASdQAACgkQlxC4m8pXrXyr
-CQf/TDNl7sMKfMNqNxPiFb8iBQvrQiVzL6E9bnEBLtkGUkPKYqxf3s8KM58sMeFn
-mzEE3i7nW3tJa+CDIJr/8GdTO6eRt4jif0ODrsJzLzKvSOLsWzWCLZaGC8F3At7L
-ywVZPa6qvgottlMQ7guRGBYRPBkMvHhZrkf/jIRrkORDM/R0FnoDQ6r02xIZKCDD
-LzosWbsVBpdnDyKLHvnyZaLMmEWbM35QtPP5kFJvTP3du87iNCItomtb7JEQJLMA
-cB26CcCdMPVXXBVzdoxRYTJcvd3/0QRHo1luAc22TqgdHz3O45h1Z36HpWT5dta+
-6+gWi8FMa143SZytRNJhwVj7eokBIgQQAQIADAUCQpztZwUDABJ1AAAKCRCXELib
-yletfO1dB/0dGGjFEJSgX8Lx9LLE/fo+sIDdUKQWgzLDtBxklXczsuGVU4tktm8s
-Xb7kebwrNBPuy/mvllW+GQtcoR269XYYnjYsN6CjF3hg7M+n2/eV4tJLu6YBelV0
-dJ8PoMqrfTqxJ74hp7dK8S94XHy5nf810AZHB5A7zwZDIK9Tj+VervElmu5vvZ4c
-lJ/YU2DxyLEJFuIL/Ai9Z1AKq1Et6Mq1Brdd3tGom9h+zjTtvAE70AOVynTDArJ3
-YG3UQkXls1jxqkOPPLBqmqSho1MNr+VbgknYz8h/Jm/w/Li+14TvsY4VrVfZpYgm
-tdMV/+outfc47oRNz4iV4a8qWBQqbCNhiQEiBBABAgAMBQJCt1fBBQMAEnUAAAoJ
-EJcQuJvKV618wQkIAIMtzcov4am8QoXZ+WRqld2vO6fKQq28j1KMbUrx+nmDTn17
-Sa6kyp+s2eYHISiEb73/bZpfeDqogTSJMmiaJbPWdmygkvQq8wrYsIt8XWNgIhrL
-nggdHfzBSfRSuBfBoYz1YAT53avX98iJnpZV5ovpa6G3Fe4NXqNAHHvcuXl3Qp3Q
-XxEIYSCvDTBrjk2LVXa5hI2xwrSTzryRodMJKp9XD33eRumRP8ns3O2wwc4sKp4c
-rFtfKWadUIPnXVQrJQf0alQanjR+JQhKq8bdZ1vWbPyjRi8p1v+mbEktqvJ3svhz
-oonGIQZPr+ivLRsU00zTHp2aSnzafYEOU4r0TreJASIEEAECAAwFAkLRGaMFAwAS
-dQAACgkQlxC4m8pXrXy07gf9FmZl6gLFnfM3v5vc9E+T7WIDENWL/nBHoeCV8wzb
-sb2S6c+5zN0N7+phw2RAi50+f4SJFdpmuLTVeMCnMnIKPFSEsTq28TG1zKPehzjy
-okbz3zevhPYI9DPQLMJgETx27BjHs6VCg827vPjQRCQDvgyWWFdYMm1DA+7OEsw8
-fqm38OmG8z9BFujFyCjLcHah25995aPku/hJ7H01UoBzgXuQU4MewA0gFlvwcR4E
-zm2cewsyfFI+or9iPDj4og+36vK/s2iEXtyTEzWHzzXISHijH+u9CLQ+qj5BUbad
-VVWLan4yvoWaNZARtmsB73ZPQmvDb1ct4idihoOscfvUPIkBIgQQAQIADAUCQtG/
-nwUDABJ1AAAKCRCXELibyletfAkOB/4/7U9TrYKwL/+EsQZdLkAIh1xVFOmXbID6
-j+kHFtoGNvh140XnbJz92l02CS2dr2ADL5t/NgVOL+C6ivUBcfmFvOp4s1VhuvKy
-wJARt0bq+tssYIWWJJZoO6ST9PkbJvJJ/C10keBNhukPVZgH4JsOhM5DmM24FvpF
-chxkizI/Q7RQKFM8IRFyT8hAUfMmdLf2+dq1Sv+GYM02KyutnTlCD6COeDYK0ggT
-TIhm6b/n/yBbxgIGS5YZPmyFfDg7H8BBRonx0uZGXdJ273BlP6uZhPLzkF6bIBG8
-WNKnH6X8fiF70fYhye4oinmtx2tM2jnpjimWCTb4u8tUOQZiE8PoiEYEEBECAAYF
-AkRoVx0ACgkQ/8DxTITHG24dJACeJJKpd29Hk62AMiBl0BZ2x+MXxbYAoI1L53O+
-5pL50JBWYDnV7uCOD4CpiEYEEhECAAYFAkYC03MACgkQFsE7X7fkrpLMiACgl/v5
-gq2hzsT12lFQr24QmsOFkHUAn2gHBejSBZmo9G1mWnntxIDy4qCDiEYEEBECAAYF
-AkYBtsMACgkQqWndc26pXmcMRQCgqVM2kYKBOJyUv7LZlzHMm+pUjHIAnR4N2JNg
-TB+OIVHngJrtJd5bKEsNiEYEEBECAAYFAkYBCHoACgkQt8xsfJgEIqg8RQCgpyDW
-8fHhbebfWn0Ile+LaattmEkAoOzpPlbBgaXo8s3dUHtIBBZdIi0JiHwEEAECAAYF
-AkYBB0cACgkQ5FNQ9HyoM22xpAMAl0vBkeXlfY36aEerqMl+oXXc50qdooDZL5Bk
-H/hyiZw0yXdMbbUwhwwR8ENRpQTyAua9gy/wWL1KE8oagSwJQ0G1F9AsB04X+wVx
-aZVYXkUwqa2tuFAo80wrlO2tVNmPiJwEEAECAAYFAkYA+YIACgkQ+8eNYiejqU3w
-iwP8DJb8w5uvb71zxk7KSW2cIxypWnxdgHTnyE17yCmuhmGFAy/OF5MzlwYvzhUT
-AvphsxrsM0b+8nSem17nvhqRBPsFYqIn+Z3VTXfjBH/HfAd6zUTkfh5pmg13H836
-zj3iU9vQ1OWFu5Ko92lPvFojGYzjq2aplS6xcTE6dRp3DgeIRgQQEQIABgUCRgJi
-wwAKCRD9xH12hMC9rM5qAJ9isj9dC7lY9y6pP+QFP0ua2Es5ewCgjcJpXANkj0VT
-y+tZ/G6pV3cu0iGIRgQQEQIABgUCRgJ0UgAKCRBRNlAnQ0vwcI9CAJ9glZML13aO
-vZm/8vgUIkWcvdUxXQCeJJcBkczDbx0+jYhkDvPiXTCidtmInAQQAQIABgUCRgOO
-6QAKCRAff6kIA1j8va9XA/4gWgyUWc2LC8atGFB5rPegKC4Sj2N1Vic6agZWAMdq
-FhRC1mZncLZk2GucIWrfJFA1JJpF7eQfVY9X4ccrk+BSKXZYQ0PPQ+K0noaA5dGP
-ki1Fgx6MOYS2iaa2jeS+xlqQSeyUTGRoF9PHDXev2Fk6M56yRZb/qSjxcV8qf6fc
-j4hGBBARAgAGBQJGCqvMAAoJECExm5RMGlvlZHcAoLjLkYe2XBvgD4ORlwwuqixo
-vDijAJ42m61qJZnJ/KkZLdGXNROSs2OV9YheBBMRAgAeBQJCFgn7AhsDBgsJCAcD
-AgMVAgMDFgIBAh4BAheAAAoJEJNd70SgkyYrD3sAni9NCVS0wu4f+6ox0/0q23xt
-e+RtAKCZRlCJVezQ5z7O1ZeaOB6QNuuYs7QuR2F2aW4gQXRraW5zb24gPGdhdmlu
-LmF0a2luc29uQHVyeS55b3JrLmFjLnVrPohgBBMRAgAgBQJGyuY9AhsDBgsJCAcD
-AgQVAggDBBYCAwECHgECF4AACgkQk13vRKCTJiuoHQCfRfwTFFSxKg5ypN2pBRGp
-Wvb5IDMAn2TQqGeMthvHZcAFkqJVCbKiscn2iEYEEBECAAYFAkIejIIACgkQIJm2
-TL8VSQuodACfbcRqAIJoyqj1psar/guNQvwtLWwAn0nKhxj2RwZOJucYIDScjh/8
-a1W9iEYEEBECAAYFAkIvFp0ACgkQoLS7q6lYlVVRmQCglNB0/V/heRKmzPuxav5Z
-gpuw9iwAniR/fq7601gx+lkCQCfXPtJHOpJCiEYEEBECAAYFAkJxXKcACgkQm8S3
-PiOtI8nEYwCgkyBctkZyQ1Y+Wqea7a3V2eHV/iUAnizbQsop2GUW58PBTx4sonHl
-wyvjiEYEEBECAAYFAkL5z1QACgkQ7crV5So7Y+lL6gCeJJNstWR+gQwQf4pBmjjZ
-c090GicAn05wmdlZRuqxVhq0kPrL5DDngNdciEYEEBECAAYFAkRoVx0ACgkQ/8Dx
-TITHG27yEQCfYlLrCX6rTwSstcrJwsO2btf3vs4AoIh23MeBSJ1GTv4sWSJpfhmz
-jiqciEYEEBECAAYFAkYBCHoACgkQt8xsfJgEIqiKWwCg2lonPDhhp3zbr4QevFAw
-SS9TMLgAnjXdp9XHfa+16OPzR+BTE8iVZBdZiEYEEBECAAYFAkYBtsMACgkQqWnd
-c26pXmcxXgCgmTSWsbnWDjFLBdYsrjNxRxD3qukAni3YtvBav6svsIEfSyKMaXA+
-m1GQiEYEEBECAAYFAkYCYsMACgkQ/cR9doTAvazGVQCfU2f40VEvox62BJv/AjBz
-NONXqzkAoIajv3THHzZMkhSwZfQzV6IJWutFiEYEEBECAAYFAkYCdFIACgkQUTZQ
-J0NL8HABqQCdFHM9TVF2TCVxHMp+xrT0+7z3AxwAn1KyNLEAFUjLQWLoTHyMtHFx
-lb/SiEYEEhECAAYFAkIbbpwACgkQqZ8ktGc0UarOqQCfcIPcSUZ0AfPkjNvesfaI
-AR7sIJIAoL9IcEARdRoFRef8g3Wg31r95WdpiEYEEhECAAYFAkIfkJMACgkQbZzl
-qwQuAMlnGQCg95rW36dClosk6lTeCx2PL1ez4X4An2oeNiegls2z3zbEUNmFNbTv
-xKnMiEYEEhECAAYFAkIgaBYACgkQkjSQvrAJCJ8gJwCglBFzqyRkevyMl/miBSNR
-nNPhZncAoIwrukOULpFQFxMxMclto4q1WSTniEYEEhECAAYFAkKjffYACgkQ28bt
-MhfFXd00QQCglajeQuKgpcCV93dOIZPK9P0PFFoAn228bsDp/BT6BFfDkt3hR/5k
-uqDWiEYEEhECAAYFAkYC03MACgkQFsE7X7fkrpLSRwCeLYBasjba++k2WQEowPT2
-pGDPzm8An0zGKD5u40GomfZ9G7cH6RNoooSUiEYEExECAAYFAkIgWlwACgkQXCn1
-HbPKKYoi/QCfVtWgyVPIQyQTmnlp+ArgK/KqdmsAn1q9SKvTCt5LaWiNdOaaaMZ1
-vqRdiEYEExECAAYFAkIsPNQACgkQKeFPmTkbOSgnsgCeMzWyqFZpO9Q+53cIaD9L
-xUYcL0IAoI4wp88dZrf8AAulC+JLTQG/s2AtiEYEExECAAYFAkJlGkkACgkQYgOK
-S92bmRCCvACfZ6J/xvlyu4HPFt0ITqeuyVNoyRIAnirUn3YTR/k4y/x9y/g6xuGk
-tnjTiEYEExECAAYFAkL5Mq0ACgkQ7RaUf2ShlE3R0gCgjZNXiuHXJxvoX+0ooM8d
-4KJiR6QAni5BxaDCAolS+ArVnpWMzcemfWS0iF4EExECAB4FAkIWCiUCGwMGCwkI
-BwMCAxUCAwMWAgECHgECF4AACgkQk13vRKCTJit5PwCdFQGHH1ic+HrkYepRec/H
-zVLznC4An05vhLBYGsCUk9BqPx+ljUohEwVqiHwEEAECAAYFAkYBB0cACgkQ5FNQ
-9HyoM22CfgL+KfSDdHRJV/AV8PR79iyxxq98YNJiThJICEV++svstYA7ZvaSlOmB
-56/FKgtc4oHvgAijzq5qS8wM30msrKaAOR6RuinEN/UUqX6PNt2JIxjMPx3fmbXk
-DV0Zfv8kXWlBiJwEEAECAAYFAkYA+YIACgkQ+8eNYiejqU2CegP/bTb6XEavDGVc
-RGkXJ264JHkj6RM1ym59G0BZBprbcQyiw+NOrb66JjYjOeFIWgfwgs4+eQKizXRK
-iS34MEBIU1GomAAbJPd9h0w7Vu9zPz2CpaewEihTOxSoPOn9oVKnefqgmECfmcML
-mbJdncruuCUbxkWsVV1iH1pwL5yEzq2InAQQAQIABgUCRgOO6gAKCRAff6kIA1j8
-vVlIA/4oGXPYeuC8h3wEzRjiVrvuFGOy06mdYH7B6L+zV5XLbBH9vqZ7ehk+jaEg
-rwqmEWZnXSyfL73FI72tbnBA7N1V+tpk9WcPyBUsHfMNk4PGGwtbDv9chnv9h6Mg
-WdESSZUfbW4B/qJHoQLbn5jgLYXwPYM9QO4Dn/HXIZWT95CrjIicBBMBAgAGBQJC
-IIhoAAoJEHSfHm9VX8il5R4D/jIa7qAV2fMp7UMEUrSt5xs7kq+tYByvESfVLtv9
-11iDFGHBrl2EkDRc4oV4Wul6blWHm5Q9Lu+cVwx6694fi9jQv7yRnHOhtCrFkejR
-N9lVwBavxPsgTO7RhzsZAPPRejRDgHcLu7wLxXMg3Kz+5nGBYdOgYEMQ2ti9vrwl
-IHMBiJwEEwECAAYFAkJlGl4ACgkQxSga5QRk5+W1OwP+Pyg8SnrpyFNlea6xw/fe
-v5HjiHOxhgazbr3EzJDEWcIpu5Zn7w2gTX/bzCdNWbkM+JqLovhWerdjqmZU8uBh
-HiuPxlo6ir8MZvi2oE/fQbI/dKFhThtcLZWY5KjMuG0a7iKMhXYApmlvW3rRR9n9
-MgmFbDPLyWm23aJbmIEe+b6JASIEEAECAAwFAkIfujsFAwASdQAACgkQlxC4m8pX
-rXyG2AgAr097M8KCs7yMxB3w70QXfeUoFCAXleGjc3Ch/Eu9Bln1SOnve5CyElEQ
-QAL4jhU+fp98VHWZZ4aTdAzcEkbds8jcBJc1dZa0cd4f4fhl2f1mIa/0Gqp49xPo
-jDUTCOl7qITAybo7rmNg00vKOfgch/IbezDwwVlqJREgI1r2qBralvxaqBTfRA2N
-2GEf4jv0v9sDrEI8npl0KX2FRcTHiGaeOpq9DF3YI0hP1UxejL8+JFgSieHAi82d
-3F29y9b+YY1jTdayPRLSsYPdZ2NbnW7zpv4c6QYaEGj+eKkCDP7JKGeUZEwktbL5
-+cUK2VZfuH7tmMQcahuZd3ddu5XNEYkBIgQQAQIADAUCQjFQzQUDABJ1AAAKCRCX
-ELibyletfDsXCACliLa1BFJFeRuua+cxT6lRU1g9f53mduC5CpnypCjBXLdYqaNr
-MHj60DPNqM6aKYY6IRKR1jLukGRYsJwVqJ1YXmsy4qASoxa0zYrd8MsiQSmSPfBk
-ltVvO+sZrXM+15ax/2z4fGFhUMVVgdFyMnqmixtMvWB+SsnqKU8yxdTEOckkhRJu
-dRMipsexnZKuDkHxNaqo/23CNvkqWlxI7SbnprNgPXS3RZn97P23BUlBI3nHsGgd
-EBAoGbgZROIOmYFYJB6Pqubbnsq2Z8pf6nh/mVGdZhrNhGOwlqjiWE42Tewdhih8
-2hOkrpdjOJqTB+RktB9xOamGCBC6bl4LBhwHiQEiBBABAgAMBQJCQnReBQMAEnUA
-AAoJEJcQuJvKV618xJ8IAMpAwq8sa2z0WuipRC/BtpfpMsM5oC8D1L5uynpyWRtz
-n+3kdxZvXI0lcvpGo8MyLhYQapORWh5BTl6lRP8b+toqNS/ttdaaejPhmMxfab9Z
-VnEMhP8ZuJPGnsFSpWDVUwE3y4Bf9QWe6M76cEHxPLmm5Zy/9H8BZxs3L007hGHz
-uDuy7/eD0o8VHCGpHIcOBenyAH7Q0mlzR5vTcP1wCoU8MG/z3qQ2g2jkyit42njp
-UWNAo/fqvK37sm1aI870K27TBcyBOu0Seio+2OEptKMQYd7WlW7D2Yp37aGLNvy3
-ffnX4jeLOWvgqyIfKgRr424Yvkg4wPgEiJhoUJTM17KJASIEEAECAAwFAkJUM3EF
-AwASdQAACgkQlxC4m8pXrXwwrAgAs7/256odaX42os+3e760sQ+hdEtRZ+BmZ4Uz
-bz3KCXEvdWy/wBl8qO1CnBq5CT7uplkniDjlp2YyitxBW9xEbhwNsITkWhs791b+
-6F3PaP93dFGYl7rVDgPKtsWhSfhO3T2PIIeF9m+6okmGQWhI35bwpXDbiOgmkJPG
-Ma1adIrp7DuhgLndwZeB0cHlaotfyHzmhxPUKcHGaouvhLbZt9ql6QG57TS+yfA7
-FKp14HxUUBhciJWQHDLmwdf8JO6fOx1LqMvwt3DluwiurifgS56ptpZZ40gvWipr
-STSjFP0kbrrq3Mj9ky0KiErPzD0bi3FzhIfT1P9cegeZtGIzV4kBIgQQAQIADAUC
-QmX+3AUDABJ1AAAKCRCXELibyletfBVOB/9oP26tTyHX/nsu2QnpnN6JHQQoaRNA
-O1fnsBfYGQiGcoR0oB/+DFflRGheB28IBKbY1/9kMA4gMMnXeJDD6JRhJ36t8IVa
-4zOm7lMqXZWG/DLEUPv+n/LsSxdqiX+h0DYp66cg4s4aMDHu9x7lRX+TUvRyZpuc
-m3cQOoOeLDAeVA5hH93iD8Z6Dqf71ZVxeLh/+hXx9j+Ekr4ykqlutMiNK6Nl2wN3
-WF4OwhmM0V9MEHb/bL8d/RTJGelnNy3clF72pZtPxv/7rSorwPVtY0IxAGSd7qrO
-tbhQrOkR9BfUI5uu1n6bPYwU747HP/4FrG3g14jKU8ZL+Mrw4wkKnt89iQEiBBAB
-AgAMBQJCdyV3BQMAEnUAAAoJEJcQuJvKV618m0EH/RbFoZhgZM7I5p7VkDiCmehh
-lFxMN4DPWJV4Fv5Mod1G86TR2F0oFrswcP1JMW2/RT1oTGEznMpjWGFUpkCFI2rP
-ysVqlfTD5rE9Pb891NQtYjcKGbLuRLf3UaOgS5zdSsfPDqKVxP2qFizKMQ2YiWYe
-TGcsGDs7Cchb7Npe1UZHHWk2osv2F4z4R5tRRiVTQoFbqlGagBnSII2htOWftsSI
-q7O9QAkBzOZkJbx3iwpK+8vD3DRdEDFoVbYkvYBsZC1GbRYYy0Wmb5GMz6MqONcD
-2imhBnmIdEijnAaHpFrToUK4IDnyBZt8mkxy9kR1kMvpIbtzy5EpaxLVBt/UEa+J
-ASIEEAECAAwFAkKJ0MoFAwASdQAACgkQlxC4m8pXrXyCUQgAig3CGkcxVCETc9Sl
-AAPM+l+yuNJvpBPieAkbbamxIUH0G6SL7AjujHVr9tfpIeW0iJIWl5zwIzvDxmc9
-CBZEcaYT8t+90KSQ+v6XKQGeK2tJZTk6Nx0JTkmLF9WQU6Qi/4JBIrnMzIdlNx6p
-9LzK/ooGcg+JTWZx5RWoPip7KcZNVIoed8nM0JXvVvByAiL2emDMJ8/Mgs1V/cum
-GyHjlX3KkNl6Gs5QokDM7Rl8+cdhRxzm1ntCaHWHilY+3qFNrdKRVixwp2xnoqix
-rNcn5RwDPpEr+0Yv6jPe/R4PAT7l1kxGN+cA2b3xaikjJl4oJdf+H4GOmUwTW7Bx
-qYlZn4kBIgQQAQIADAUCQpztZwUDABJ1AAAKCRCXELibyletfJqeB/0ZX5MC4bCj
-is38lqwAQY4gpjHy/xPTCMshuzp5GghW9xXfiFAeA3W6GENLSHfA2w1B2AkbwIBY
-Fk8qMkhpwg5z7CNPeBUIViiZnL1HhNVUxr8oBCe98KvsirpaHbJPzSy5vzCF4v84
-EttHiMPZga7enO4SJ9Kc8Bpe8FkyzRhcihXn11JUBSi9Ba8B7KK2aSYIkEb9zy4K
-enQmqsm6/WtL+bxIJiHXGbNa4w/WsiQu6ftoT6mDR1PKV79kUiOklMZsWiqhy6Yp
-0OfX83iUJ/Nd1PcAJtzZLzfAdlj9EgwN4LMwb7PmdZD9rcH94N5iE1Zynd4Jr4mR
-MBzIYgTBwHWEiQEiBBABAgAMBQJCt1fBBQMAEnUAAAoJEJcQuJvKV618CTUIAKTN
-bHCnUVxjX6mbeumZtNO99RWDr5W404uWNwnlzrAPRiHlun0p0AS0l+d7k/GcBf56
-O8/zmZ4+TUQUHp3nz4A+CxPnIaur2meoa134egaL3PmLCSCydW2qCPhQfqrFZsgI
-q9Y8yBw2qPNuuE6vrVHOBaPyTZNCQUSlPr9v8AgR1adkJjZayKa1JUTTP1CQ4htQ
-rmMzVuk8axvB6fo2PO8tJPLS7GbhDnlZaVK/Aaq13lSYwBr58RdWSqUiQ9bzWU35
-qOXWSJbveS1C4rkbLzHxTCa6cCVIV/APAKD/f/DB7V/RUDJbE4WK3/9f/JyW5i2F
-hUk8FHhC3jOVtYgCyu2JASIEEAECAAwFAkLRGaMFAwASdQAACgkQlxC4m8pXrXwQ
-vQgAhSn8nA+kFgKCpPgVxGEsPE2CE4aYmF51eAXaou1wC/XHhhy5xIwEUYSfXBEn
-ePNilY6IGG0lc8l2oOi7LpooqhBdi0onveK8/WSLl6IDOds25v9ugnqmqwHHyNy5
-tkzN8o/WToqLxIt3pJ+ZGK5nJiR7H5UwY0DbIIbyhkBg3YZ/4+PDOLo/n96DKSjh
-BvmI9hJQoVHm1/YrlLtdqoMd2jsdZvBn912dD0JpXKv7Cm3+W6xh0QxshHB7zWoK
-hax3H3GHaEC0crVkwMil4ELTuzsqDUI71emH2YFY50JHfKBpywr96BrcKmjSeJNj
-RMnFKLRHrMfAYqYIycU3MzSWhIkBIgQQAQIADAUCQtG/nwUDABJ1AAAKCRCXELib
-yletfJ28B/46uNxE4pNlsAo44zbwC5FiHsIVCg27EakyPehRfzxaxTbRw++oVU3P
-4cTrHaMOOoCX9feTufT2WwEY/Ta585/oagemHsNiqHErnVNSWX2kyDQmDfodm0N2
-PfS3Dem7uqY2Qh9jnIfpHq0R0a/3kMwpyBm1Ce0clUoF4Ci02NL6TTA26Y2dt8rD
-NMBXTmGOLmQNbuS7RYm/UDqNMt63B6YeedNCJPMbub/09K+cLSmTed2neCrA88E8
-NTAQhlSgUwuiRjSunTE8tusUVj9AQbPr3HG+PDho90O4Ixc9IOiKqhg0w+1S17BS
-EqYKjj0ymPkTlh6JIILmgcpbELNMt4YViQEiBBABAgAMBQJC7MaDBQMAEnUAAAoJ
-EJcQuJvKV618x4cH/ioTHiO9hinMj3T/KyjP9f2xn74gy+NquPcsaaouNLJimMhZ
-ZynMh69Riuo8bxgY+V92WztpXdREcDZNgKusy3x19Z1FEqY5QgBaNpfVceTRkOrv
-AmvbmiHog1P5+5KN6Bw0fTvAETQ/chRCG6YITqXE2Fv6jt4m0spiVPU5P7zcK8XY
-9BSLnUVnAhOD7Xkk2xVbkAwY7NPWzQnaqf4Y6qRCDfj52gqjjxwR2juDvFWp9AaB
-sVjMZQp9Yn4hXwDEh/b80HXs2GivhXjt3fGMVy/zrWc3icxRFhQgQsMaxtIolr5q
-Y3zYNOk8ptpWzv/SoiEpPY1j6M22DMifoBQar5WJASIEEAECAAwFAkLtbMMFAwAS
-dQAACgkQlxC4m8pXrXyORQf/RhgoMF5LMqyoU0jGya7mH56l4FPFoqHHLf/PNLhi
-V45tVD+hgkjAg8gxuIDXEdK0TLdnswcajb8AbRcaoWuZJI9K/ZGy1BXlX2uTsCqw
-KDMVLoFGfeGnU1rKsJ2BgUxD8ZeTN1gKbNhbtj7Gz0imIYVWte6VelBeBcmM6X3N
-OOJGqKTtYry8Oj93/3AtnykfwG8u3RsavFgB7fJwqKKOGUNtAGvY2AY4fq9J9w+y
-spxAFXlnVVqAbCuzZ/77jLehLHIhfN1hTC64x8zM4nOLntVbBhED6s8ExJuOY/Bz
-rVJ3hjRSv9RwOKHPfpr21rHOw3p9ZP4KAQbmuUeQbJSmc7QmR2F2aW4gQXRraW5z
-b24gPGdhdmluQDE2c3F1YXJlZC5jby51az6IRQQQEQIABgUCQvnPUQAKCRDtytXl
-Kjtj6VwMAJddHXsHnE/EhzaD6PhyK5Ze7VG8AJ9CtbMIKVqPB63fScUVmS1S9mwf
-VYhGBBARAgAGBQJCHoyHAAoJECCZtky/FUkL9+MAoL4vanv7nQWpJD0iBtTQcB8G
-GlzqAKCsABd+jZVomcT+/tZesg6POR0i1YhGBBARAgAGBQJCLxalAAoJEKC0u6up
-WJVVGEYAn2dRve1WSJD29V0ZVvYR1itOfljJAJ9Lw85WmrZPVVPCyFJbfoCOomSL
-kIhGBBARAgAGBQJCcVywAAoJEJvEtz4jrSPJKxoAnRraGctTbAvxXyTzI/1ngh+t
-3tBNAKCsFdvgbhHliSdk7Hkz6YJsxxOWKIhGBBARAgAGBQJEaFcZAAoJEP/A8UyE
-xxtu4swAn1V+yDPvA/Y8/yW1IHQgC029Ggv1AJ9j+ArlW/pRSNHR2hxYZLoKXOod
-KIhGBBARAgAGBQJGAQh6AAoJELfMbHyYBCKoGVUAn0xzfsfs7TtXW1kYaDmNVVCY
-X/YEAKDfZ1LDWSgvZD64xng54DPHYkpFS4hGBBARAgAGBQJGAba/AAoJEKlp3XNu
-qV5nF5YAnifczPRJ87iv8KH8wWgPaeGKrTovAKDH/GTkd/xiJgVRKxGaGIL4HTOq
-+4hGBBARAgAGBQJGAmK4AAoJEP3EfXaEwL2sGbUAn0QwRCzTmAf7SAFXhjBFDeWy
-Mb+oAJ9soen7TjeGQE4MzRTZb1Wdn5IGM4hGBBARAgAGBQJGAnRMAAoJEFE2UCdD
-S/Bwb+YAnRkmKKkfTRG7sqBUwYWT8XYRsYfvAJ9Rr98VXR7FmGrugc+1lIWvCR+9
-l4hGBBIRAgAGBQJCG26gAAoJEKmfJLRnNFGqL3kAniWPc7N5X5oxU0g8HF9/Ij/R
-ooDNAJ9XKG3+2TxLLxIDV+8gRrkuxtpojohGBBIRAgAGBQJCH5CXAAoJEG2c5asE
-LgDJLy0AnigKzZ4uwcPAboRof2CA5PibfmCwAJ92Ck7/yrtD9nA9bNLcxyf2/b8k
-yIhGBBIRAgAGBQJCIGgbAAoJEJI0kL6wCQifYf0AnAwmeD11Vp3YbiZgERek4cBs
-yx2jAJ9HUL4wr5kejXa7M4WGl6XzKUKgq4hGBBIRAgAGBQJCo334AAoJENvG7TIX
-xV3dcT0AoLaMacjQacauUwXmyHkIJxe2XuOvAKCOL6QmFDLBVm4CENk8D/6hw8zX
-RIhGBBIRAgAGBQJGAtNuAAoJEBbBO1+35K6SV58AniFi4z/vj8izUfxgV4iNLLfD
-NGAiAJ9Y3QfIanz35nByphBBE+uUYkc3TYhGBBMRAgAGBQJCLDzXAAoJECnhT5k5
-GzkoGU0AnikdJ+IRwoKc18RpCBS8sN8WpRq0AJsH7N0jpNXMiuew7MbPlcJQmtlC
-NIhGBBMRAgAGBQJCZRpSAAoJEGIDikvdm5kQlvsAniAoA9LuDNfagUhjOykwnjSL
-Es9uAKCYDFPF9U9s7tGG1UIpvi+KV8QHb4hGBBMRAgAGBQJC+TKwAAoJEO0WlH9k
-oZRNFf4An3lspQZqxEBdJ1BzMuv6H5a0BOhMAJ9yT2ya+9Y3GFQnxf5zk1oiLkFC
-Z4heBBMRAgAeBQJCFgZnAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEJNd70Sg
-kyYrmQIAoIe9ImVDl3Epc7nmYkNVNP1J4nPQAKCVSSsVGj6pKNypVYdLFnpljQ6N
-XohhBBMRAgAhAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheABQJCcOT5AhkBAAoJEJNd
-70SgkyYrqD8AoK1V7D/hBy13g0+fdL1VpZHU/1vfAKCL4K50ndPJ0dXXJU12rvVa
-41nRU4h8BBABAgAGBQJGAQdHAAoJEORTUPR8qDNt0jMDAIs4fEoXn0pzkafFSYh5
-xo/h0o9JN6FfWYFeOxEsBciYY7mVUK4z8lzud1PWd3Rlny9FdK3n26zmRcaj3S+J
-inUqMXS8UKKy0nU/nGabjEqE0QXSU9x3juevusoW3m/6NYicBBABAgAGBQJGAPmC
-AAoJEPvHjWIno6lNlJsEAJp12FbcoCt569B8UtykLVVhugemPV7cdUtL4920vg8v
-X31XStwtw316rJchNY1ovPgK8Kui67Sx/TWnVPLI94Boe4Aml0EifGLUxQItWtdi
-KTD7K28zGE+NepcEiJ2q0YAxm5W9wWdC2PBiBQclqHfgmUllVupm26lukcuM8Ukf
-iJwEEAECAAYFAkYDjuQACgkQH3+pCANY/L1H2gP8CkvR2sa1ipy9QAr3H4kOYtAg
-96Fx1E9/nUKXs0Qtif3jzW/8fs3VuoZkmcFivOQaBG7C2CgeiH1edSMbFJWJ4C5N
-7xoh80tOEN5KFV0PDg61NqaOwx9sJvROKAOUCe5d2eSGrGaDXVMiIb+10IfpfGWl
-7L3iUBMQnx8SU7K/18yInAQTAQIABgUCQiCIhwAKCRB0nx5vVV/IpVNDA/0YquqA
-re7TrjDdjfIVa9pEnrDFkAX4/BNSJMtlt9zkMbOSBWg+VWsrkDiw0YFmxehajDJY
-dvYjekmYk8g3j6Qe3YgHtfUjtCd3lrboZwexxfErjViUr9+sw60EHjzlPL5Si0yu
-7f7wmB7l27ACml2B/j6QTULuHAi4jB2AvKUflYicBBMBAgAGBQJCZRpoAAoJEMUo
-GuUEZOflgH0D/1QAKSca0w14IzT8Bxsgpg53Ku7rhNaE2QCh3XJz86J9C/comssc
-XZHx65ebnaQSsaLbldOwC2eUIV5IBAvyvhY613HSRJ4NounWZhuG4/3jSSuflBcF
-mF4A3rIKJMukZJkfxxXwC2U3EOyyKtMvdXrh+SWXsIWUZvqw0zr3W0kbiQEiBBAB
-AgAMBQJCH7o7BQMAEnUAAAoJEJcQuJvKV618KC4IAJds4thabREpL8+hZ6bG1QuG
-dgL89W4DYjQ8OOUoxcVpFP0K0R/SRKJ2L58txRddT4lB0sSFt2wC0n96KHA1O3xy
-wUNlA7KlQ3Dqmbg8AMb46vjqAv1gGkjfIBooqJwTidbw0xL25FrsyLUzDm6K09w5
-0KDgmgmGqNJgopbVwffWwgrTwuDSzDAbysZ9KWwwhMUSzB/7nW9jeLT+bl7dCKD/
-oZ8WvK7MBBkCRcthtnC6dE0nNf+qxnNaPoreTWO3yuvkPFT72Q1cPRz7zalcqIIW
-omyohjG40oI4WY/tJ2V1kz4D+lXF1exLmT2uKk8j6e3o5dNl1Xwoxgq1c2HGjEOJ
-ASIEEAECAAwFAkIxUM0FAwASdQAACgkQlxC4m8pXrXxq9QgAo0AKz2W8OB6pTelO
-cGkPccdOMKn8EHKLfiHz7kG0u7F/e3seAVo+0vwS7VaEyF8tktvK0gypaSZgjc3e
-92062blZYtVxDr1MDPErc6RXVO0KMviaXSvmWZfvHP8mexnelYgP0BQ0tTeuwH0W
-be79mQyOQy8amp1hGVtRSj/7N2sVT8ACrXhCSQ7UyzrTUp76pmupXSHK+JdZ08We
-ddV5Dj1MWEmeFTG11GU4EYajkMY12wamxSQ7dedv5/3WUnJPoS9adWES+SGdjyQS
-aKjTj6s/YD3I0/rI/mZJp18wzXyoJ7CBSGodSH6bMsuOwHuvA5RPhriDC9IP/bmL
-lcwPAYkBIgQQAQIADAUCQkJ0XwUDABJ1AAAKCRCXELibyletfGaRB/sEiTbNAzN/
-OH85K1gziaD5ABpv2w1nYKy1Rs9kE3I0jhkRf0286lWIz/zPuGizjM2yObbVt3nn
-kmPlg9MCEHNjzLx27o+FEFhCbaQZeucwDE+5j5B/OKLrdFWX6VBSkLgFpn3gCGSq
-2RJ0GRTRt+3KwGJSrGyim/Vgi/fPrYyxKoeut478tyOY5FAcIjgTBXqygZKOWx2J
-2jN5Tyecnk0uW/4j5bf1AP2RyXVs5xHUp6exC2l2wcZ/XSkjXZ2bNzBSCJViCgoo
-2AqAVFbCbR605giuB8h3ifSiG61jNCWoObxhK8+aGr1DR7XU17o5v0cnI2QR61ld
-SB+bdn1sRCXUiQEiBBABAgAMBQJCVDNxBQMAEnUAAAoJEJcQuJvKV618BswH/0Ni
-1adU3lzw1BzlYKLjNf0YOjLYoTIFVloHPzvFoABQlKM/rLsgC6aEAJhoOMl92VP6
-/YqfTMJwJ68OAF+zZPePy9VXwgUf3+tnjkA/WqHkRZm68Q3yysvIBC1iCG/OosEG
-qb8MzxOnCABNYojqCR+EVX/FgGRM8XejeR+QV4v1Bfz0x7kN5jKKmFPAWu1qprZN
-y2HRFa5FbbUjibjsgILv460zymiVlcLzuE3oWoRAMqyjO14Yh17d0w3LmQPSGu9j
-g1IFzyRAmL3g+nR8e76d37blYj0N5h+X+HO2nTyWL8RzEOL9QhntJghhDyMwxjPD
-l+XmmB8u9gAwvY6DCgWJASIEEAECAAwFAkJl/twFAwASdQAACgkQlxC4m8pXrXzM
-2Qf/UW0NmElMRMC+Qr0Ju+XeQKtL/5YCq5efmOZqoGOISLuvFVOx26gXa5GF7HJ3
-XVZqYen4BMwNPNgqpQyGUPHjpxmdPHk8SRWNGT4MHwdDFcbirwYYSIfEuzFj4YuU
-D6fr7ZLJJoklnE0ZL+vphKx3NLdOmgFwVIudMXNlqw+A+Ho10LD32nByGFrl85Gv
-hhPnyR5Ody7Obsuu+P3Jt+UXIIgeSvEdz1z6l6CLiAA/mYEGtY9uq6kr1w6yJfKs
-4Hjd1erkskz4PuURB2fDirBSapLewMWZqvnUnm+Rooq4oqXSZeuYKIfQ82zKK3Ll
-COEGGk/8VxBOEaLkpfq2UzEU34kBIgQQAQIADAUCQncldwUDABJ1AAAKCRCXELib
-yletfDdmB/9D3aedIN5l1Y35y64NqKUXXU8lK1vpSMbB6ECeEEkLq02G14jhERIr
-AOiPDHvmzPAqcuWFNI2z3/O8ocw4GqRrMhl59W+k+Fa5xG2TuFL9rKMg+29brBEu
-4cmfR9bIIsRMCt/lD11hneTVeYnsqff4vavZOUn2vluAM50SHJ/qH9JJcP8IptAM
-h3tI9iLnjVTD34RUzXY9DF0aa7IpVnieiKf0MiJPRW3OmK5IqsnLy+HK/DGmEtgM
-6y9GhoPe1OFNVPLlEojtC5jNri/PgqegBhpoklwNAeMIpti+bKVcQVd847ZEJMJj
-TvB1gi35RTHRfJ0fQDG6yoh8AQKEAIFqiQEiBBABAgAMBQJCidDKBQMAEnUAAAoJ
-EJcQuJvKV618tHUH/2F/pQ76YWtEJ0leKk0hdBolRoE+f7sTHYDp6H2RDmCQ77v4
-OAsIy0VllA0/5deXflFKbSJQEoNvP2MJmu08htt+2MbZK+6wu/WeSC54S+EftpXR
-pGx9+ohdVk9oHYsKcC3XwV0ZEz3ADzXQ42Ho0XT6HvOLhx+0LD2OuM9AN89tqmGh
-XCphcTIERcp86uWCumhNrEVTpVb3XFe7Sqas0Ed08aEFUjt3s1fVM81GRJeYS6pv
-2YOSIBqPnAE6CEM9xUtJkp1udSN5h6nSclqDmTcMYqulxw361DRUFITtcTli01nm
-dVkn7JNCxF5LXKJvNpbk02CSoOSokZjgeivfv4uJASIEEAECAAwFAkKc7WcFAwAS
-dQAACgkQlxC4m8pXrXxiowgAipp4d5knG6mtnkhIiRo5G00qfafMmeZT6sbHRtSd
-yPv3WBOiwsUvdbFkVpisBaht/x/mLBvoR/UTR14oKhdDxgINNLCIaYIiPU6+mwRh
-nZwMkckQ8iowP9e4vOXxsgK1l5xCsSPXERxEbll7+w8JBcYzcVmWgG6g+gZlMlBb
-1NNazuWdqKlBJvEa5k6w/Z0tFlppbdywb8cj/3N+CNvJncrGqJIHxxmWnZunyqqE
-A8ZXZYxICErjwoJ0gpO3VyRySi6rgTCLiKsJa7X9Hget6wNOVbinb75oua+q/W54
-6bEX0RtqQy/7Hq4eYqng8JWdtVFxpSNK9xvyiGGGIR8GHYkBIgQQAQIADAUCQrdX
-wQUDABJ1AAAKCRCXELibyletfEriB/4lTWmdr0SV6oCF1qJcQa95niBj90TuAqvT
-UoDQhiaYjhF/fPJ/A1XD0iAZ/Ktx3/y3JQueyi3subiv1Mk3nlJ8s6YBeX31vYe5
-OqyUf0/BrBd1nUcncwqpspCRzZ2/LdARWeDP3vGMx3VH1AgeJhJbJFR+LjnRrXJy
-tVegvttQERGinwfbi46gk2391/l4hOFkiDqXsLrxf1qJkR4s/sg0I6yFzjf+LlAL
-dikF5VCdrWV+mv9/1ouTdvQc6h82+xOaD/PnV+1yfYL6xs6MERbr7UL7OJ3NC+DD
-0Srmipdmblr9/yqJq1pxwFkr0msERxIto5OToPcbC5LkxGH4IgEaiQEiBBABAgAM
-BQJC0RmjBQMAEnUAAAoJEJcQuJvKV618JZIIAJ6924Ck3o7XlC+xlA9OcPvmBGQD
-0TEaG39SPhmY80qkb+VD6L1Gbk6FShMQaktf1VVbNG8w4enBuLiS6nX9/BsqmYGm
-pwm4S6M8ksxdKqYdowPuuDc4qV2+kldF5S9JieJ64b8V2dsPGzYbrh8xzTrr4qH+
-o08CMxmtsscL3gTlNflCOiRFcHDyNR6YkZmgjKICDP6mV9pmBmKkbkV0JI6cgD0J
-4NIm65hWly0jWIRwfoq3wC0/9JetFu8WvPuVEpAwDgSJSD+VaKkUOukCZMK/WzeX
-m6Q0c0M5W7tsvIZPD4+qJ/srszJSs7Y/f12RCnRtvK6Pg8yPUAw+ZB37dN6JASIE
-EAECAAwFAkLRv58FAwASdQAACgkQlxC4m8pXrXyMfQgAujnPNjg5zzdvph2aCDux
-d9suHD0CYTx4lTbUwLVPfRJQtxzg1YEb42Sqk/w8KI0W676jv7zbcMVz7C9wZpnM
-qBYsHc8XaF34e5NwUgE3JK+NJiz3TTZIf47laZfbj/sYzR9NOTYK54YoVtYiLEGq
-T551CvPMg5+fBVVRjlubRUC+BpcZfiYdL3xvD3VDT2kMZi4ZoKAhfmd2gz7wdhOt
-T7v6ctORND6wMk28BCZ8/q15/2egmOii4FsJp8SP5AM5HKOwaWicRh2v3SHfEhV7
-yR0ng4V/N1gCXb6nj01zEpub38qNgJB5tM2Sggrc48myIUHrIzykzbRMagG3+4C2
-gokBIgQQAQIADAUCQuzGgwUDABJ1AAAKCRCXELibyletfPzPB/9KXj/yEW9vhSE/
-5xK0ZtMICfdxL+FeHUWmX6y51oM7tWqlo035FbzN4VbwB609Qz5E7yDMjNoUwOZ4
-KIrhh/k7neszxGB4s2voU32K/nSl2oiTcJ5iGtYkO9TvFqa8D6G1ZzikXctwKvaE
-AMpqtjOg+sxlbA3tsqaqATQ2VfLvuIFoaIPNuIXqnyjQDkb0jr/25CHLy50nWFNX
-y+FVQkcgMsE3eM7DUHOpBaQw/CnbnR/+XDeu3TtsOjgrsVY943oZ1MWDqJxYLH1K
-uW/cq4VMTgkVAz79BmkFJxLq1FXFB5Ed4VBcjy02BYnzxmffHZ+rDCF/UJR8zBPr
-o7waOa0RiQEiBBABAgAMBQJC7WzDBQMAEnUAAAoJEJcQuJvKV618V1wH+wVAa0Vg
-1eevzpgwWDgDutTLitE+2W+uJnec4oi5jSP55Rg8/vcMzV60SbdJeSgXIlKbHz69
-YvrRWzU87Jqyp2POECHRiyOOXFunlqWoPd7MZzXbVSQ+rNscMUHFiI2zg1vbMnY/
-iRLv3whYXCjVIYr1AUx5RQyQ9LMKzLcppwXxxkuqfbdYoi1/ayUEtMGmB5v4C/YF
-96hv2qbgf7jNFMq5sH7IN1DNrQpi0B82LNmYdJLxK2tkgdr5jarcw3/uknCVz+6P
-wDHek5WlYiSGn4a8r0cKsas8i5/cwu5b1gpeetnfQVkzu01IQ/17P9CSB9J5VVt4
-hE3hITs/jTmsYzq5Ag0EQhYGdxAIANWAPhDo3kdh1QoXfk+oe0Rw60fYgLSmcexZ
-Kj6gEoMlZC0NPPtJQO2UjWEjesfce6HDxfFGj6LuqKY2QoioRJaTxBbDEDstnPp8
-+gCms+p4DvBqNXdfxV+jHaspbtqbQNpWcl+6MLKD1OciEluygBnVFPrfvgJRFT+O
-S1uOjRfafUA0cl9HlKZdHgY/sRfX5CFLQyGLu2NYVsj1i+AI9PYmrP4ucKHkTDr5
-cBWq3wzi/HHUq/tT+1UL3P/hjiTjbmzRjF4Ygm+18so2wvz4qT6HAFLmsvEobc1v
-odJaELRvl0Se5FG8ZEaYJpDXzDqs/G0+hPoPT8eXgUr87pd3nzMAAwUH/im19ug/
-qDBWGFykIIPo6P5upkwg8Umiihk3CvfkpZonsRSRpg/YVX7MJ/v0/wwJ41GPgFIG
-/NiKQc2kxxPgO9AKYJ0lXMS7fyLXgZgY0TD2s6tvnXWX16cmMp2MJYDaPNJf4MY2
-ImW7VgfU00AzZAheBpJKdB/+8/ncRRqKljsWDStmG0Y0iazNzaX1tWMB8ug875Ne
-GsSnBUWylh7MuaXVJMAnBjsxj4rw2KR/TD9i+M+RADRXisUcZJMMZ1q0RXCs5FRT
-T6yxHLHnLL/A1LlQLQ5TVJ94Hhda3O9xWLsL2mDRcga8qbcruoBhzg/ip9YzWZSu
-fERzv62KdVRt9jSISQQYEQIACQUCQhYGdwIbDAAKCRCTXe9EoJMmK7wSAJ9+rbAF
-c1hAq4PIfgnpiErVWkaOiwCfcQSb29qCLTwsVXBkqZr02JdmGdg=
-=w86g
+7SZDdibo6eXfhwU4u9zuhYD3iQEcBBABAgAGBQJKzAXOAAoJEJBXh4mJ2FR+iUQH
+/AnF5sUjG5f04NOiO0FXe5uc95oWdvMrOjuLJSEl0hcZewS8nGmNi55Az2hv1FdC
+T0UVMt2Ti8Ba9rL0EQ01uRpBlzr2tuLlqm1GFkfG5uHBpatzkg4cY01IF7YixwhZ
+qIULBag+kXbWJE0fMb8WsBmnvov7x47yAq+Yg3MdQUZRjeg6hmKe96dhlFtFtnn/
+KkFgJcmrq96ldSwPRyd2WGWHm3GbM1T6L7XnjXBN/a7SAYwWoixMBynJAK3M9CmM
+UBoqChflbeFLdWoI4kAlchJ7VCNg+KdRefRdOGqkGpyC19nhuoTxDTcMZc3rAS4N
+y9l97vYwka3Nfs1jwZkqRIKJAhwEEAEIAAYFAk8Ss9YACgkQbmvkJeuDwr1S6hAA
+iiJEULPr4fzAl8Q+8Gj6bnjRCq3JJnk5xXdiLjWVydDOn0J/yIAkCWlLXyzz4Y9R
+Hr7CCreLT9Q9LLKKF7oMB3ZQ3NIf5n4N31+ASqGBjnbLf06Fy1DZz96ojyR2DfXp
+Qs0QrIFFa27XFMkj/wNNZ4EejJz3QfrP6aoEc3GbPl1P20FaB2mj7dwU3Xz4TJtg
+bmW8CU6tI7Sn3IO73MajxW4P/UHi//613tmpTz95WdfpdKwkOn4WBNhJTPF3rEkr
+q1qXF0kCy1lc7s51xbDp5g0gsJ2zYE48207XFtGI27ZAld2uJW1VbcExLCZ2BMLK
+TZAwtTbkURti0NmiiQuyLuWOjcHgmvGvG0c0Gpw8xaHDMT3ce/XdzjBF8CQOJjlb
+8aQbBqAJ8U0QJ35AsI0zlxUxgIJkyWaHKW+ZfpiKGoe3yYYz4aVh2TBXK5ab6SXg
+kCQq3jrTLDQkp2JHj5KrUqyFq+XiYIJXnYYq8yAFHGNI7rqyxX2xP9BuV8KmJHHE
+GeTvViSCqQOymRB5D42r+0wKxpvheRiYyjLamon6bPlGLDRX2430/78qJseaojUj
+xJmmbC/ItTDRs4efTfLTTVqw3Lauh8liL7R3fbMRg5GuQFYY+2GGr+g9wXzI88zG
+4XLYOm8pN+IUoGDSDO+Nyqs/+KhsQDd1QYhFlaOgJS6IYwQTEQIAIwIbAwIeAQIX
+gAYLCQgHAwIEFQIIAwQWAgMBBQJMbk4xAhkBAAoJEJNd70SgkyYrUbsAoIujXfn6
+LRakax4Z9rgk7XADluj9AKCPRgE38V+fOmaqia/pCDSxBEZu04kCHAQTAQIABgUC
+UZfMXAAKCRBueCrAPJsM+YQLD/oCKI31QlhdlqVd8E4vkV2PAJlrKOmCZfA8npTz
+R0vBcoZ0Wr4EpslgE0fjoLb0bwVVk1203xcDQvnXJpdctU9p7zR6cKiWfj757F50
+RJmSJ0xKlcrpAwTqHQJz/Nic434MhyUrSr4as0SJqubhvwC2RgDpLzCsyqoZ/UUH
+1nzA374ynBulbiaqIEK3uBuP7ZReFbNPrAyjVX1AQ/Cm3bYVtAhIxnsHoykWmNiP
+g+HcWitvzPNb7pDWHAaRrhsdOWWhey0RXd0o0czegH1nK8+Q+ZT3/+F6msQvDnoK
+K/d56JWijTCLkSnwGm9W0hQjaWdqIQrfiq+g1rTHKQPj0L5dIdYDgnE445MKBAaJ
+Iewz+lQxyOg3xjDe9Zqq3MnE8oV7vc9eP7pRnEtESHZ5KUE86OAdarQUa9DWkmUO
+5+7noyHJqzEy6tto94nr6ajPWLpzjFjV//q+PTmXGaohlKnVaa/kgevh+aoCI0hB
+3HaTCIiggOppYMtjstWnqM2KhOdnZMVB6L2r4TBbzPyGkAm4P7r5RsjNGbvm+B3+
+KsqA1L72FWxZsojsvHtnK+sFCmQ8N9zWwAkELDZPC938nvW8mTlYTEJShb5tJpin
+dVletXzoCRlM9HbswmHpPykH/x43kxWZJOzjxGbd2oPgOtLuxQx8PDM9Bqye70p5
+EQ7f+7QmR2F2aW4gQXRraW5zb24gPGdhdmluQDE2c3F1YXJlZC5jby51az6IRQQQ
+EQIABgUCQvnPUQAKCRDtytXlKjtj6VwMAJddHXsHnE/EhzaD6PhyK5Ze7VG8AJ9C
+tbMIKVqPB63fScUVmS1S9mwfVYhGBBARAgAGBQJCHoyHAAoJECCZtky/FUkL9+MA
+oL4vanv7nQWpJD0iBtTQcB8GGlzqAKCsABd+jZVomcT+/tZesg6POR0i1YhGBBAR
+AgAGBQJCLxalAAoJEKC0u6upWJVVGEYAn2dRve1WSJD29V0ZVvYR1itOfljJAJ9L
+w85WmrZPVVPCyFJbfoCOomSLkIhGBBARAgAGBQJCcVywAAoJEJvEtz4jrSPJKxoA
+nRraGctTbAvxXyTzI/1ngh+t3tBNAKCsFdvgbhHliSdk7Hkz6YJsxxOWKIhGBBAR
+AgAGBQJEaFcZAAoJEP/A8UyExxtu4swAn1V+yDPvA/Y8/yW1IHQgC029Ggv1AJ9j
++ArlW/pRSNHR2hxYZLoKXOodKIhGBBARAgAGBQJGAQh6AAoJELfMbHyYBCKoGVUA
+n0xzfsfs7TtXW1kYaDmNVVCYX/YEAKDfZ1LDWSgvZD64xng54DPHYkpFS4hGBBAR
+AgAGBQJGAba/AAoJEKlp3XNuqV5nF5YAnifczPRJ87iv8KH8wWgPaeGKrTovAKDH
+/GTkd/xiJgVRKxGaGIL4HTOq+4hGBBARAgAGBQJGAmK4AAoJEP3EfXaEwL2sGbUA
+n0QwRCzTmAf7SAFXhjBFDeWyMb+oAJ9soen7TjeGQE4MzRTZb1Wdn5IGM4hGBBAR
+AgAGBQJGAnRMAAoJEFE2UCdDS/Bwb+YAnRkmKKkfTRG7sqBUwYWT8XYRsYfvAJ9R
+r98VXR7FmGrugc+1lIWvCR+9l4hGBBIRAgAGBQJCG26gAAoJEKmfJLRnNFGqL3kA
+niWPc7N5X5oxU0g8HF9/Ij/RooDNAJ9XKG3+2TxLLxIDV+8gRrkuxtpojohGBBIR
+AgAGBQJCH5CXAAoJEG2c5asELgDJLy0AnigKzZ4uwcPAboRof2CA5PibfmCwAJ92
+Ck7/yrtD9nA9bNLcxyf2/b8kyIhGBBIRAgAGBQJCIGgbAAoJEJI0kL6wCQifYf0A
+nAwmeD11Vp3YbiZgERek4cBsyx2jAJ9HUL4wr5kejXa7M4WGl6XzKUKgq4hGBBIR
+AgAGBQJCo334AAoJENvG7TIXxV3dcT0AoLaMacjQacauUwXmyHkIJxe2XuOvAKCO
+L6QmFDLBVm4CENk8D/6hw8zXRIhGBBIRAgAGBQJGAtNuAAoJEBbBO1+35K6SV58A
+niFi4z/vj8izUfxgV4iNLLfDNGAiAJ9Y3QfIanz35nByphBBE+uUYkc3TYhGBBMR
+AgAGBQJCLDzXAAoJECnhT5k5GzkoGU0AnikdJ+IRwoKc18RpCBS8sN8WpRq0AJsH
+7N0jpNXMiuew7MbPlcJQmtlCNIhGBBMRAgAGBQJCZRpSAAoJEGIDikvdm5kQlvsA
+niAoA9LuDNfagUhjOykwnjSLEs9uAKCYDFPF9U9s7tGG1UIpvi+KV8QHb4hGBBMR
+AgAGBQJC+TKwAAoJEO0WlH9koZRNFf4An3lspQZqxEBdJ1BzMuv6H5a0BOhMAJ9y
+T2ya+9Y3GFQnxf5zk1oiLkFCZ4heBBMRAgAeBQJCFgZnAhsDBgsJCAcDAgMVAgMD
+FgIBAh4BAheAAAoJEJNd70SgkyYrmQIAoIe9ImVDl3Epc7nmYkNVNP1J4nPQAKCV
+SSsVGj6pKNypVYdLFnpljQ6NXoheBBMRAgAeAhsDBgsJCAcDAgMVAgMDFgIBAh4B
+AheABQJMbk4rAAoJEJNd70SgkyYr5toAnRMWhFd+rtu2FM1pM4lJQI0NpE44AKCJ
+TFssAe0s8d2C+OkqO4Y2LYLLdoh8BBABAgAGBQJGAQdHAAoJEORTUPR8qDNt0jMD
+AIs4fEoXn0pzkafFSYh5xo/h0o9JN6FfWYFeOxEsBciYY7mVUK4z8lzud1PWd3Rl
+ny9FdK3n26zmRcaj3S+JinUqMXS8UKKy0nU/nGabjEqE0QXSU9x3juevusoW3m/6
+NYicBBABAgAGBQJGAPmCAAoJEPvHjWIno6lNlJsEAJp12FbcoCt569B8UtykLVVh
+ugemPV7cdUtL4920vg8vX31XStwtw316rJchNY1ovPgK8Kui67Sx/TWnVPLI94Bo
+e4Aml0EifGLUxQItWtdiKTD7K28zGE+NepcEiJ2q0YAxm5W9wWdC2PBiBQclqHfg
+mUllVupm26lukcuM8UkfiJwEEAECAAYFAkYDjuQACgkQH3+pCANY/L1H2gP8CkvR
+2sa1ipy9QAr3H4kOYtAg96Fx1E9/nUKXs0Qtif3jzW/8fs3VuoZkmcFivOQaBG7C
+2CgeiH1edSMbFJWJ4C5N7xoh80tOEN5KFV0PDg61NqaOwx9sJvROKAOUCe5d2eSG
+rGaDXVMiIb+10IfpfGWl7L3iUBMQnx8SU7K/18yInAQTAQIABgUCQiCIhwAKCRB0
+nx5vVV/IpVNDA/0YquqAre7TrjDdjfIVa9pEnrDFkAX4/BNSJMtlt9zkMbOSBWg+
+VWsrkDiw0YFmxehajDJYdvYjekmYk8g3j6Qe3YgHtfUjtCd3lrboZwexxfErjViU
+r9+sw60EHjzlPL5Si0yu7f7wmB7l27ACml2B/j6QTULuHAi4jB2AvKUflYicBBMB
+AgAGBQJCZRpoAAoJEMUoGuUEZOflgH0D/1QAKSca0w14IzT8Bxsgpg53Ku7rhNaE
+2QCh3XJz86J9C/comsscXZHx65ebnaQSsaLbldOwC2eUIV5IBAvyvhY613HSRJ4N
+ounWZhuG4/3jSSuflBcFmF4A3rIKJMukZJkfxxXwC2U3EOyyKtMvdXrh+SWXsIWU
+Zvqw0zr3W0kbiQEiBBABAgAMBQJCH7o7BQMAEnUAAAoJEJcQuJvKV618KC4IAJds
+4thabREpL8+hZ6bG1QuGdgL89W4DYjQ8OOUoxcVpFP0K0R/SRKJ2L58txRddT4lB
+0sSFt2wC0n96KHA1O3xywUNlA7KlQ3Dqmbg8AMb46vjqAv1gGkjfIBooqJwTidbw
+0xL25FrsyLUzDm6K09w50KDgmgmGqNJgopbVwffWwgrTwuDSzDAbysZ9KWwwhMUS
+zB/7nW9jeLT+bl7dCKD/oZ8WvK7MBBkCRcthtnC6dE0nNf+qxnNaPoreTWO3yuvk
+PFT72Q1cPRz7zalcqIIWomyohjG40oI4WY/tJ2V1kz4D+lXF1exLmT2uKk8j6e3o
+5dNl1Xwoxgq1c2HGjEOJASIEEAECAAwFAkIxUM0FAwASdQAACgkQlxC4m8pXrXxq
+9QgAo0AKz2W8OB6pTelOcGkPccdOMKn8EHKLfiHz7kG0u7F/e3seAVo+0vwS7VaE
+yF8tktvK0gypaSZgjc3e92062blZYtVxDr1MDPErc6RXVO0KMviaXSvmWZfvHP8m
+exnelYgP0BQ0tTeuwH0Wbe79mQyOQy8amp1hGVtRSj/7N2sVT8ACrXhCSQ7UyzrT
+Up76pmupXSHK+JdZ08WeddV5Dj1MWEmeFTG11GU4EYajkMY12wamxSQ7dedv5/3W
+UnJPoS9adWES+SGdjyQSaKjTj6s/YD3I0/rI/mZJp18wzXyoJ7CBSGodSH6bMsuO
+wHuvA5RPhriDC9IP/bmLlcwPAYkBIgQQAQIADAUCQkJ0XwUDABJ1AAAKCRCXELib
+yletfGaRB/sEiTbNAzN/OH85K1gziaD5ABpv2w1nYKy1Rs9kE3I0jhkRf0286lWI
+z/zPuGizjM2yObbVt3nnkmPlg9MCEHNjzLx27o+FEFhCbaQZeucwDE+5j5B/OKLr
+dFWX6VBSkLgFpn3gCGSq2RJ0GRTRt+3KwGJSrGyim/Vgi/fPrYyxKoeut478tyOY
+5FAcIjgTBXqygZKOWx2J2jN5Tyecnk0uW/4j5bf1AP2RyXVs5xHUp6exC2l2wcZ/
+XSkjXZ2bNzBSCJViCgoo2AqAVFbCbR605giuB8h3ifSiG61jNCWoObxhK8+aGr1D
+R7XU17o5v0cnI2QR61ldSB+bdn1sRCXUiQEiBBABAgAMBQJCVDNxBQMAEnUAAAoJ
+EJcQuJvKV618BswH/0Ni1adU3lzw1BzlYKLjNf0YOjLYoTIFVloHPzvFoABQlKM/
+rLsgC6aEAJhoOMl92VP6/YqfTMJwJ68OAF+zZPePy9VXwgUf3+tnjkA/WqHkRZm6
+8Q3yysvIBC1iCG/OosEGqb8MzxOnCABNYojqCR+EVX/FgGRM8XejeR+QV4v1Bfz0
+x7kN5jKKmFPAWu1qprZNy2HRFa5FbbUjibjsgILv460zymiVlcLzuE3oWoRAMqyj
+O14Yh17d0w3LmQPSGu9jg1IFzyRAmL3g+nR8e76d37blYj0N5h+X+HO2nTyWL8Rz
+EOL9QhntJghhDyMwxjPDl+XmmB8u9gAwvY6DCgWJASIEEAECAAwFAkJl/twFAwAS
+dQAACgkQlxC4m8pXrXzM2Qf/UW0NmElMRMC+Qr0Ju+XeQKtL/5YCq5efmOZqoGOI
+SLuvFVOx26gXa5GF7HJ3XVZqYen4BMwNPNgqpQyGUPHjpxmdPHk8SRWNGT4MHwdD
+FcbirwYYSIfEuzFj4YuUD6fr7ZLJJoklnE0ZL+vphKx3NLdOmgFwVIudMXNlqw+A
++Ho10LD32nByGFrl85GvhhPnyR5Ody7Obsuu+P3Jt+UXIIgeSvEdz1z6l6CLiAA/
+mYEGtY9uq6kr1w6yJfKs4Hjd1erkskz4PuURB2fDirBSapLewMWZqvnUnm+Rooq4
+oqXSZeuYKIfQ82zKK3LlCOEGGk/8VxBOEaLkpfq2UzEU34kBIgQQAQIADAUCQncl
+dwUDABJ1AAAKCRCXELibyletfDdmB/9D3aedIN5l1Y35y64NqKUXXU8lK1vpSMbB
+6ECeEEkLq02G14jhERIrAOiPDHvmzPAqcuWFNI2z3/O8ocw4GqRrMhl59W+k+Fa5
+xG2TuFL9rKMg+29brBEu4cmfR9bIIsRMCt/lD11hneTVeYnsqff4vavZOUn2vluA
+M50SHJ/qH9JJcP8IptAMh3tI9iLnjVTD34RUzXY9DF0aa7IpVnieiKf0MiJPRW3O
+mK5IqsnLy+HK/DGmEtgM6y9GhoPe1OFNVPLlEojtC5jNri/PgqegBhpoklwNAeMI
+pti+bKVcQVd847ZEJMJjTvB1gi35RTHRfJ0fQDG6yoh8AQKEAIFqiQEiBBABAgAM
+BQJCidDKBQMAEnUAAAoJEJcQuJvKV618tHUH/2F/pQ76YWtEJ0leKk0hdBolRoE+
+f7sTHYDp6H2RDmCQ77v4OAsIy0VllA0/5deXflFKbSJQEoNvP2MJmu08htt+2MbZ
+K+6wu/WeSC54S+EftpXRpGx9+ohdVk9oHYsKcC3XwV0ZEz3ADzXQ42Ho0XT6HvOL
+hx+0LD2OuM9AN89tqmGhXCphcTIERcp86uWCumhNrEVTpVb3XFe7Sqas0Ed08aEF
+Ujt3s1fVM81GRJeYS6pv2YOSIBqPnAE6CEM9xUtJkp1udSN5h6nSclqDmTcMYqul
+xw361DRUFITtcTli01nmdVkn7JNCxF5LXKJvNpbk02CSoOSokZjgeivfv4uJASIE
+EAECAAwFAkKc7WcFAwASdQAACgkQlxC4m8pXrXxiowgAipp4d5knG6mtnkhIiRo5
+G00qfafMmeZT6sbHRtSdyPv3WBOiwsUvdbFkVpisBaht/x/mLBvoR/UTR14oKhdD
+xgINNLCIaYIiPU6+mwRhnZwMkckQ8iowP9e4vOXxsgK1l5xCsSPXERxEbll7+w8J
+BcYzcVmWgG6g+gZlMlBb1NNazuWdqKlBJvEa5k6w/Z0tFlppbdywb8cj/3N+CNvJ
+ncrGqJIHxxmWnZunyqqEA8ZXZYxICErjwoJ0gpO3VyRySi6rgTCLiKsJa7X9Hget
+6wNOVbinb75oua+q/W546bEX0RtqQy/7Hq4eYqng8JWdtVFxpSNK9xvyiGGGIR8G
+HYkBIgQQAQIADAUCQrdXwQUDABJ1AAAKCRCXELibyletfEriB/4lTWmdr0SV6oCF
+1qJcQa95niBj90TuAqvTUoDQhiaYjhF/fPJ/A1XD0iAZ/Ktx3/y3JQueyi3subiv
+1Mk3nlJ8s6YBeX31vYe5OqyUf0/BrBd1nUcncwqpspCRzZ2/LdARWeDP3vGMx3VH
+1AgeJhJbJFR+LjnRrXJytVegvttQERGinwfbi46gk2391/l4hOFkiDqXsLrxf1qJ
+kR4s/sg0I6yFzjf+LlALdikF5VCdrWV+mv9/1ouTdvQc6h82+xOaD/PnV+1yfYL6
+xs6MERbr7UL7OJ3NC+DD0Srmipdmblr9/yqJq1pxwFkr0msERxIto5OToPcbC5Lk
+xGH4IgEaiQEiBBABAgAMBQJC0RmjBQMAEnUAAAoJEJcQuJvKV618JZIIAJ6924Ck
+3o7XlC+xlA9OcPvmBGQD0TEaG39SPhmY80qkb+VD6L1Gbk6FShMQaktf1VVbNG8w
+4enBuLiS6nX9/BsqmYGmpwm4S6M8ksxdKqYdowPuuDc4qV2+kldF5S9JieJ64b8V
+2dsPGzYbrh8xzTrr4qH+o08CMxmtsscL3gTlNflCOiRFcHDyNR6YkZmgjKICDP6m
+V9pmBmKkbkV0JI6cgD0J4NIm65hWly0jWIRwfoq3wC0/9JetFu8WvPuVEpAwDgSJ
+SD+VaKkUOukCZMK/WzeXm6Q0c0M5W7tsvIZPD4+qJ/srszJSs7Y/f12RCnRtvK6P
+g8yPUAw+ZB37dN6JASIEEAECAAwFAkLRv58FAwASdQAACgkQlxC4m8pXrXyMfQgA
+ujnPNjg5zzdvph2aCDuxd9suHD0CYTx4lTbUwLVPfRJQtxzg1YEb42Sqk/w8KI0W
+676jv7zbcMVz7C9wZpnMqBYsHc8XaF34e5NwUgE3JK+NJiz3TTZIf47laZfbj/sY
+zR9NOTYK54YoVtYiLEGqT551CvPMg5+fBVVRjlubRUC+BpcZfiYdL3xvD3VDT2kM
+Zi4ZoKAhfmd2gz7wdhOtT7v6ctORND6wMk28BCZ8/q15/2egmOii4FsJp8SP5AM5
+HKOwaWicRh2v3SHfEhV7yR0ng4V/N1gCXb6nj01zEpub38qNgJB5tM2Sggrc48my
+IUHrIzykzbRMagG3+4C2gokBIgQQAQIADAUCQuzGgwUDABJ1AAAKCRCXELibylet
+fPzPB/9KXj/yEW9vhSE/5xK0ZtMICfdxL+FeHUWmX6y51oM7tWqlo035FbzN4Vbw
+B609Qz5E7yDMjNoUwOZ4KIrhh/k7neszxGB4s2voU32K/nSl2oiTcJ5iGtYkO9Tv
+Fqa8D6G1ZzikXctwKvaEAMpqtjOg+sxlbA3tsqaqATQ2VfLvuIFoaIPNuIXqnyjQ
+Dkb0jr/25CHLy50nWFNXy+FVQkcgMsE3eM7DUHOpBaQw/CnbnR/+XDeu3TtsOjgr
+sVY943oZ1MWDqJxYLH1KuW/cq4VMTgkVAz79BmkFJxLq1FXFB5Ed4VBcjy02BYnz
+xmffHZ+rDCF/UJR8zBPro7waOa0RiQEiBBABAgAMBQJC7WzDBQMAEnUAAAoJEJcQ
+uJvKV618V1wH+wVAa0Vg1eevzpgwWDgDutTLitE+2W+uJnec4oi5jSP55Rg8/vcM
+zV60SbdJeSgXIlKbHz69YvrRWzU87Jqyp2POECHRiyOOXFunlqWoPd7MZzXbVSQ+
+rNscMUHFiI2zg1vbMnY/iRLv3whYXCjVIYr1AUx5RQyQ9LMKzLcppwXxxkuqfbdY
+oi1/ayUEtMGmB5v4C/YF96hv2qbgf7jNFMq5sH7IN1DNrQpi0B82LNmYdJLxK2tk
+gdr5jarcw3/uknCVz+6PwDHek5WlYiSGn4a8r0cKsas8i5/cwu5b1gpeetnfQVkz
+u01IQ/17P9CSB9J5VVt4hE3hITs/jTmsYzqIYQQTEQIAIQIbAwYLCQgHAwIDFQID
+AxYCAQIeAQIXgAUCQnDk+QIZAQAKCRCTXe9EoJMmK6g/AKCtVew/4Qctd4NPn3S9
+VaWR1P9b3wCgi+CudJ3TydHV1yVNdq71WuNZ0VOJARwEEAECAAYFAkrMBc4ACgkQ
+kFeHiYnYVH56zQgAnWxQNtMw4eVCB4d/4VYmKdwGpP9czakdkyQkZH5vQv4BNYhQ
+ZhpiISbzssHf5T3Li09CAJIwuaBmBO4eN2MfAeuYn5YqLSy0orkSyZE4NjEOSg48
+KaMaT2OzTwNs2Y+yto/Yz9LKQTeWZHhS53zElvqQSa1mJijuuKxSCSfGOE0WIOc+
+lWwnp9ECWWcRb0jHVl3vwgQ4rBKahSB24hWkuo5J85NBm0CZa+ZK0+6qnQNR/AiT
+7qOKxUKgof8VQ/iB+iyyIT4azhSy26zNZKhigKeg3HaYrU+IkSd6SbPjBYt+1ONt
+0jtc6Y9qj9jtEEQqapAeeSI5K62kWUOyBWAyjokCHAQTAQIABgUCUZfMXAAKCRBu
+eCrAPJsM+V1/D/kBtBb8rNHbadKvTaGcGu8Bd4Lz12P0CUy1H5Ia+el0A1imaYJ8
+aFNmFlE/LDS2R73zxvIi9p/wD9i6TglndOb+O+oKkwZlEsx/8rcui6NCpCXmArpH
+s3BIMP3cz43FBBcvSHqwu0d/ZKHCHShrcTKzUWABNc6kQ/nU1jnVljp575kKln7z
+S5tzPWY/U3ZwORZwEKW2S8OVpSnUSvJicNZyEkYJ7JO/WUWTdgNCCAKacc2VmS9e
+/i2qMh8o4MIzUwacG32GeWp+966FZK9TD4UxuB5Q2kTMS0TR7FQxDrliCYoKUjeA
+bJHzj2P96pruns3Y8wUHOgxEMlJH3C1xkW94QyzNRc2r1rZM5Zbm/hfJ5Cg0JJSO
+p11oweUAFu3mya5hm6FL/ycKD26JXOWx47UOTYvwKAKlz+48Cj1aW0+RGSVwyABi
+ZI2XHVxuRGL7yl0KlU4TCCsx+ziWeTUQPXP6026QRdmaG6CB15GezdnAPcb6O6Ct
+3+I59LiKY0Lw4WyN+urI/y2nA+P2b7Bkqv6FFjRa9D8Tn3a1NVh46GBCSQlWDUAv
+byF3rD3Jjyv/G3IizgMsFw82rDE45avkiq8XeBFDjQmm6JcxwyCIs1n9kO4TyZzQ
+D9E+LKYy15KIYIC1NXPqu6eGED5sAInZ5Ws+5wzmMwSQ6QARrepVfsPmnrQwR2F2
+aW4gQXRraW5zb24gKEZyZWVCU0Qga2V5KSA8Z2F2aW5ARnJlZUJTRC5vcmc+iGME
+ExECACMCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAUCUA3Q4QIZAQAKCRCTXe9E
+oJMmK+cDAJwNJwhK9w+uByztkA33QZpiQ3DTWwCgiuVxb8Qmr/QZndBFQsoHO362
+oXKIRgQQEQIABgUCSltg3AAKCRDtytXlKjtj6YonAJ92cnZOiLvl0xQygGGBXU9F
+OgpHLACdEZ+g4NUPA0Pyieuq9okFvgA82WSIcgQTEQIAMgUCSvhkQisaaHR0cDov
+L3d3dy5wb2xsaW5nZXIub3JnLnVrL3BncC1wb2xpY3kudHh0AAoJEGB6yoUweI/v
+xvUAn1C6moTEBBhVpmKuNHCHhcYLYmhSAKCaT1aZG7+xJ99MNZkPhGsIzmrSO4kB
+HAQQAQIABgUCSswFzgAKCRCQV4eJidhUftZSB/0V6cMaSfwA2nqNxqO1yErM2jaq
+zgsgB07pPEXLJdIkKFhUY9ntcR+mLq48VAbaqkJQX83ivxSGFwa9UADvbnvXETVB
+iTPUjJ6whkXxDxHGfGe1V9/+ySbRtjVJ7n1sf9Oq4JJzczXBH/8lDxnD7UP+DKC5
+ureEFVwjCOmIvHuORGEebxbfiVy2eiFmIo503XB63I9LxE3YvTukQBj0R5/ADuyc
+GTdW8NNOcJmaB1x+bnfF274xzqDjoh9ZecFr6bedMgG1asCPexeLB5ddq8jblZFB
+nTElzh7QgAmP40lSJmu7KzUGzOG+GoAjdvFIi/ZHw9Ho+djn8VN3kxkes3JriQIc
+BBABCAAGBQJPErPWAAoJEG5r5CXrg8K9w08P/3NnFLKDfrSQay0JRZ1+EcL0dS6e
+1eo4fpeNWMuXasqG7B4+Mrdi7n+R2knxrjc3DbimhTnraIZ2uXSEdlScKDLYrQCr
+7SDy8741tXAKoolOwyTKcmi6zX8fWE3eh3b9jxu8oZOZHkOpcxe9PCrXRgqbeWFU
+TSKRitBCVbTUiZUSxCHMKIRZMCYmllcSVKnDNvZTycCoX3DxkiRFEx+I35/PCU6D
+WaIHKUQ8yZmy1vTIKBkPTrhAa5zYwFQNA7Acrem49WitP25vwrFMmd06UT1rLcEo
+XANtZvpnkHnVe7lO+2RGFWVce9PIUg0tipl0RdHeLZIy/OH0/qSXLipR0t5GCGQy
+3ZWRzIg7Fa/g8zBnA9r37sW3iENOA57mttXr34MCcTMpkhlaLG3+QHzBC81oZt+W
+iqtvgqjlCYvV7MlAKkAeRuIHLyiroPWfdo9g9/A8IYKo6vYu6ZL/zIizFrO4IsUL
+wDr5cOlVK3Ix9vJ+jH0mfSuac3RY0ejNi/wf0wtf6CXvuDGWR6YYRSg2vHNl0DuT
+ZU37O31vUOwgpA/7/FFUTdkE2NrM2EV4rnzcyNwzGjWfb3EMEF9A7/+QEYRhxn8P
+eNQ9/opD90rz3AkP66nbSJKpVBG3g4elI4/E8/oqF1QhrrDWIGk2dqra6yCK7u3v
+gL8gZsEMkDIfmfE9iGAEExECACAFAkbK5pUCGwMGCwkIBwMCBBUCCAMEFgIDAQIe
+AQIXgAAKCRCTXe9EoJMmK0KnAJwPBhj4uOdhe2cheGw/ujQz+HzNsQCghjy8yyud
+9WQYyY5xNLt1f6j2OMGJAhwEEwECAAYFAlGXzFwACgkQbngqwDybDPmUGRAAg4SX
+bltp3mIyoHtDxzZc7RpW14BHbfJoSj2eSs+XQCVzpQKbEbNAA/BgZvjm5JevU262
+ukXN/Z7qgXpBpseV0mQIUzIx4eBzt+MQMC/ee6U8AjYNiv7CXvIwZ1hPKAxow+Wg
+z8kTrTNTGiWfR2Cf61NjQb2YSKFczNPf7E8YnMM7QvIXCRENQYYluHduBtVCTFZz
+lvF2DzEMpqyTaiChMmJilAYsrHEYs5Yr5QChoL1sg90y3+bMckbsBq+kYY1Pxp4E
+M5JpBrh+tc/GTacFTLfjA2lIHpt7SEtSKsnpJXSPmZi2y6twBcxCQPrx1muWg+Fo
+9TnkS7nsgZ5EyQ51CZth+XCo4faxA2d+GS9yECXpPoKQMpBOeTQxSDBnImACo/cC
+4RjkDHub8XmT/NC9Yj0Wxyl23/5U3R+BbhqAZZSjaQes3UJG+uDxElj1RKCkHCpg
+NHcf3jxTk4Zy3UVt2wYyQS6kO1j6BIAni2ev7F3w/xvj3rCkq3oYW/XsgOiXZJHY
+v6z1fnGxdntEqI9ashwqKC3jKlSDTdMe0k3YM5PO+hIzejcXc3rvrZRSgWm8qMG4
+YpBYmMBypSWN7eTThG8MQeo+yglsz6vOYr6zLLaHEFDFkSOglxc2OK5/RZz1IsbS
+Mp534463UW5jjIkSZkrUaC7G94dwaQYS2q/NFUm0LkdhdmluIEF0a2luc29uIDxn
+YXZpbi5hdGtpbnNvbkB1cnkueW9yay5hYy51az6IYAQTEQIAIAUCRsrmPQIbAwYL
+CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEJNd70SgkyYrqB0An0X8ExRUsSoOcqTd
+qQURqVr2+SAzAJ9k0KhnjLYbx2XABZKiVQmyorHJ9ohGBBARAgAGBQJCHoyCAAoJ
+ECCZtky/FUkLqHQAn23EagCCaMqo9abGq/4LjUL8LS1sAJ9JyocY9kcGTibnGCA0
+nI4f/GtVvYhGBBARAgAGBQJCLxadAAoJEKC0u6upWJVVUZkAoJTQdP1f4XkSpsz7
+sWr+WYKbsPYsAJ4kf36u+tNYMfpZAkAn1z7SRzqSQohGBBARAgAGBQJCcVynAAoJ
+EJvEtz4jrSPJxGMAoJMgXLZGckNWPlqnmu2t1dnh1f4lAJ4s20LKKdhlFufDwU8e
+LKJx5cMr44hGBBARAgAGBQJC+c9UAAoJEO3K1eUqO2PpS+oAniSTbLVkfoEMEH+K
+QZo42XNPdBonAJ9OcJnZWUbqsVYatJD6y+Qw54DXXIhGBBARAgAGBQJEaFcdAAoJ
+EP/A8UyExxtu8hEAn2JS6wl+q08ErLXKycLDtm7X977OAKCIdtzHgUidRk7+LFki
+aX4Zs44qnIhGBBARAgAGBQJGAQh6AAoJELfMbHyYBCKoilsAoNpaJzw4Yad826+E
+HrxQMEkvUzC4AJ413afVx32vtejj80fgUxPIlWQXWYhGBBARAgAGBQJGAbbDAAoJ
+EKlp3XNuqV5nMV4AoJk0lrG51g4xSwXWLK4zcUcQ96rpAJ4t2LbwWr+rL7CBH0si
+jGlwPptRkIhGBBARAgAGBQJGAmLDAAoJEP3EfXaEwL2sxlUAn1Nn+NFRL6MetgSb
+/wIwczTjV6s5AKCGo790xx82TJIUsGX0M1eiCVrrRYhGBBARAgAGBQJGAnRSAAoJ
+EFE2UCdDS/BwAakAnRRzPU1RdkwlcRzKfsa09Pu89wMcAJ9SsjSxABVIy0Fi6Ex8
+jLRxcZW/0ohGBBIRAgAGBQJCG26cAAoJEKmfJLRnNFGqzqkAn3CD3ElGdAHz5Izb
+3rH2iAEe7CCSAKC/SHBAEXUaBUXn/IN1oN9a/eVnaYhGBBIRAgAGBQJCH5CTAAoJ
+EG2c5asELgDJZxkAoPea1t+nQpaLJOpU3gsdjy9Xs+F+AJ9qHjYnoJbNs982xFDZ
+hTW078SpzIhGBBIRAgAGBQJCIGgWAAoJEJI0kL6wCQifICcAoJQRc6skZHr8jJf5
+ogUjUZzT4WZ3AKCMK7pDlC6RUBcTMTHJbaOKtVkk54hGBBIRAgAGBQJCo332AAoJ
+ENvG7TIXxV3dNEEAoJWo3kLioKXAlfd3TiGTyvT9DxRaAJ9tvG7A6fwU+gRXw5Ld
+4Uf+ZLqg1ohGBBIRAgAGBQJGAtNzAAoJEBbBO1+35K6S0kcAni2AWrI22vvpNlkB
+KMD09qRgz85vAJ9Mxig+buNBqJn2fRu3B+kTaKKElIhGBBMRAgAGBQJCIFpcAAoJ
+EFwp9R2zyimKIv0An1bVoMlTyEMkE5p5afgK4CvyqnZrAJ9avUir0wreS2lojXTm
+mmjGdb6kXYhGBBMRAgAGBQJCLDzUAAoJECnhT5k5GzkoJ7IAnjM1sqhWaTvUPud3
+CGg/S8VGHC9CAKCOMKfPHWa3/AALpQviS00Bv7NgLYhGBBMRAgAGBQJCZRpJAAoJ
+EGIDikvdm5kQgrwAn2eif8b5cruBzxbdCE6nrslTaMkSAJ4q1J92E0f5OMv8fcv4
+OsbhpLZ404hGBBMRAgAGBQJC+TKtAAoJEO0WlH9koZRN0dIAoI2TV4rh1ycb6F/t
+KKDPHeCiYkekAJ4uQcWgwgKJUvgK1Z6VjM3Hpn1ktIheBBMRAgAeBQJCFgolAhsD
+BgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEJNd70SgkyYreT8AnRUBhx9YnPh65GHq
+UXnPx81S85wuAJ9Ob4SwWBrAlJPQaj8fpY1KIRMFaoh8BBABAgAGBQJGAQdHAAoJ
+EORTUPR8qDNtgn4C/in0g3R0SVfwFfD0e/YsscavfGDSYk4SSAhFfvrL7LWAO2b2
+kpTpgeevxSoLXOKB74AIo86uakvMDN9JrKymgDkekbopxDf1FKl+jzbdiSMYzD8d
+35m15A1dGX7/JF1pQYicBBABAgAGBQJGAPmCAAoJEPvHjWIno6lNgnoD/202+lxG
+rwxlXERpFyduuCR5I+kTNcpufRtAWQaa23EMosPjTq2+uiY2IznhSFoH8ILOPnkC
+os10Sokt+DBASFNRqJgAGyT3fYdMO1bvcz89gqWnsBIoUzsUqDzp/aFSp3n6oJhA
+n5nDC5myXZ3K7rglG8ZFrFVdYh9acC+chM6tiJwEEAECAAYFAkYDjuoACgkQH3+p
+CANY/L1ZSAP+KBlz2HrgvId8BM0Y4la77hRjstOpnWB+wei/s1eVy2wR/b6me3oZ
+Po2hIK8KphFmZ10sny+9xSO9rW5wQOzdVfraZPVnD8gVLB3zDZODxhsLWw7/XIZ7
+/YejIFnREkmVH21uAf6iR6EC25+Y4C2F8D2DPUDuA5/x1yGVk/eQq4yInAQTAQIA
+BgUCQiCIaAAKCRB0nx5vVV/IpeUeA/4yGu6gFdnzKe1DBFK0recbO5KvrWAcrxEn
+1S7b/ddYgxRhwa5dhJA0XOKFeFrpem5Vh5uUPS7vnFcMeuveH4vY0L+8kZxzobQq
+xZHo0TfZVcAWr8T7IEzu0Yc7GQDz0Xo0Q4B3C7u8C8VzINys/uZxgWHToGBDENrY
+vb68JSBzAYicBBMBAgAGBQJCZRpeAAoJEMUoGuUEZOfltTsD/j8oPEp66chTZXmu
+scP33r+R44hzsYYGs269xMyQxFnCKbuWZ+8NoE1/28wnTVm5DPiai6L4Vnq3Y6pm
+VPLgYR4rj8ZaOoq/DGb4tqBP30GyP3ShYU4bXC2VmOSozLhtGu4ijIV2AKZpb1t6
+0UfZ/TIJhWwzy8lptt2iW5iBHvm+iQEiBBABAgAMBQJCH7o7BQMAEnUAAAoJEJcQ
+uJvKV618htgIAK9PezPCgrO8jMQd8O9EF33lKBQgF5Xho3NwofxLvQZZ9Ujp73uQ
+shJREEAC+I4VPn6ffFR1mWeGk3QM3BJG3bPI3ASXNXWWtHHeH+H4Zdn9ZiGv9Bqq
+ePcT6Iw1Ewjpe6iEwMm6O65jYNNLyjn4HIfyG3sw8MFZaiURICNa9qga2pb8WqgU
+30QNjdhhH+I79L/bA6xCPJ6ZdCl9hUXEx4hmnjqavQxd2CNIT9VMXoy/PiRYEonh
+wIvNndxdvcvW/mGNY03Wsj0S0rGD3WdjW51u86b+HOkGGhBo/nipAgz+yShnlGRM
+JLWy+fnFCtlWX7h+7ZjEHGobmXd3XbuVzRGJASIEEAECAAwFAkIxUM0FAwASdQAA
+CgkQlxC4m8pXrXw7FwgApYi2tQRSRXkbrmvnMU+pUVNYPX+d5nbguQqZ8qQowVy3
+WKmjazB4+tAzzajOmimGOiESkdYy7pBkWLCcFaidWF5rMuKgEqMWtM2K3fDLIkEp
+kj3wZJbVbzvrGa1zPteWsf9s+HxhYVDFVYHRcjJ6posbTL1gfkrJ6ilPMsXUxDnJ
+JIUSbnUTIqbHsZ2Srg5B8TWqqP9twjb5KlpcSO0m56azYD10t0WZ/ez9twVJQSN5
+x7BoHRAQKBm4GUTiDpmBWCQej6rm257KtmfKX+p4f5lRnWYazYRjsJao4lhONk3s
+HYYofNoTpK6XYziakwfkZLQfcTmphggQum5eCwYcB4kBIgQQAQIADAUCQkJ0XgUD
+ABJ1AAAKCRCXELibyletfMSfCADKQMKvLGts9FroqUQvwbaX6TLDOaAvA9S+bsp6
+clkbc5/t5HcWb1yNJXL6RqPDMi4WEGqTkVoeQU5epUT/G/raKjUv7bXWmnoz4ZjM
+X2m/WVZxDIT/GbiTxp7BUqVg1VMBN8uAX/UFnujO+nBB8Ty5puWcv/R/AWcbNy9N
+O4Rh87g7su/3g9KPFRwhqRyHDgXp8gB+0NJpc0eb03D9cAqFPDBv896kNoNo5Mor
+eNp46VFjQKP36ryt+7JtWiPO9Ctu0wXMgTrtEnoqPtjhKbSjEGHe1pVuw9mKd+2h
+izb8t3351+I3izlr4KsiHyoEa+NuGL5IOMD4BIiYaFCUzNeyiQEiBBABAgAMBQJC
+VDNxBQMAEnUAAAoJEJcQuJvKV618MKwIALO/9ueqHWl+NqLPt3u+tLEPoXRLUWfg
+ZmeFM289yglxL3Vsv8AZfKjtQpwauQk+7qZZJ4g45admMorcQVvcRG4cDbCE5Fob
+O/dW/uhdz2j/d3RRmJe61Q4DyrbFoUn4Tt09jyCHhfZvuqJJhkFoSN+W8KVw24jo
+JpCTxjGtWnSK6ew7oYC53cGXgdHB5WqLX8h85ocT1CnBxmqLr4S22bfapekBue00
+vsnwOxSqdeB8VFAYXIiVkBwy5sHX/CTunzsdS6jL8Ldw5bsIrq4n4EueqbaWWeNI
+L1oqa0k0oxT9JG666tzI/ZMtCohKz8w9G4txc4SH09T/XHoHmbRiM1eJASIEEAEC
+AAwFAkJl/twFAwASdQAACgkQlxC4m8pXrXwVTgf/aD9urU8h1/57LtkJ6ZzeiR0E
+KGkTQDtX57AX2BkIhnKEdKAf/gxX5URoXgdvCASm2Nf/ZDAOIDDJ13iQw+iUYSd+
+rfCFWuMzpu5TKl2VhvwyxFD7/p/y7EsXaol/odA2KeunIOLOGjAx7vce5UV/k1L0
+cmabnJt3EDqDniwwHlQOYR/d4g/Geg6n+9WVcXi4f/oV8fY/hJK+MpKpbrTIjSuj
+ZdsDd1heDsIZjNFfTBB2/2y/Hf0UyRnpZzct3JRe9qWbT8b/+60qK8D1bWNCMQBk
+ne6qzrW4UKzpEfQX1CObrtZ+mz2MFO+Oxz/+Baxt4NeIylPGS/jK8OMJCp7fPYkB
+IgQQAQIADAUCQncldwUDABJ1AAAKCRCXELibyletfJtBB/0WxaGYYGTOyOae1ZA4
+gpnoYZRcTDeAz1iVeBb+TKHdRvOk0dhdKBa7MHD9STFtv0U9aExhM5zKY1hhVKZA
+hSNqz8rFapX0w+axPT2/PdTULWI3Chmy7kS391GjoEuc3UrHzw6ilcT9qhYsyjEN
+mIlmHkxnLBg7OwnIW+zaXtVGRx1pNqLL9heM+EebUUYlU0KBW6pRmoAZ0iCNobTl
+n7bEiKuzvUAJAczmZCW8d4sKSvvLw9w0XRAxaFW2JL2AbGQtRm0WGMtFpm+RjM+j
+KjjXA9opoQZ5iHRIo5wGh6Ra06FCuCA58gWbfJpMcvZEdZDL6SG7c8uRKWsS1Qbf
+1BGviQEiBBABAgAMBQJCidDKBQMAEnUAAAoJEJcQuJvKV618glEIAIoNwhpHMVQh
+E3PUpQADzPpfsrjSb6QT4ngJG22psSFB9Buki+wI7ox1a/bX6SHltIiSFpec8CM7
+w8ZnPQgWRHGmE/LfvdCkkPr+lykBnitrSWU5OjcdCU5JixfVkFOkIv+CQSK5zMyH
+ZTceqfS8yv6KBnIPiU1mceUVqD4qeynGTVSKHnfJzNCV71bwcgIi9npgzCfPzILN
+Vf3Lphsh45V9ypDZehrOUKJAzO0ZfPnHYUcc5tZ7Qmh1h4pWPt6hTa3SkVYscKds
+Z6KosazXJ+UcAz6RK/tGL+oz3v0eDwE+5dZMRjfnANm98WopIyZeKCXX/h+BjplM
+E1uwcamJWZ+JASIEEAECAAwFAkKc7WcFAwASdQAACgkQlxC4m8pXrXyangf9GV+T
+AuGwo4rN/JasAEGOIKYx8v8T0wjLIbs6eRoIVvcV34hQHgN1uhhDS0h3wNsNQdgJ
+G8CAWBZPKjJIacIOc+wjT3gVCFYomZy9R4TVVMa/KAQnvfCr7Iq6Wh2yT80sub8w
+heL/OBLbR4jD2YGu3pzuEifSnPAaXvBZMs0YXIoV59dSVAUovQWvAeyitmkmCJBG
+/c8uCnp0JqrJuv1rS/m8SCYh1xmzWuMP1rIkLun7aE+pg0dTyle/ZFIjpJTGbFoq
+ocumKdDn1/N4lCfzXdT3ACbc2S83wHZY/RIMDeCzMG+z5nWQ/a3B/eDeYhNWcp3e
+Ca+JkTAcyGIEwcB1hIkBIgQQAQIADAUCQrdXwQUDABJ1AAAKCRCXELibyletfAk1
+CACkzWxwp1FcY1+pm3rpmbTTvfUVg6+VuNOLljcJ5c6wD0Yh5bp9KdAEtJfne5Px
+nAX+ejvP85mePk1EFB6d58+APgsT5yGrq9pnqGtd+HoGi9z5iwkgsnVtqgj4UH6q
+xWbICKvWPMgcNqjzbrhOr61RzgWj8k2TQkFEpT6/b/AIEdWnZCY2WsimtSVE0z9Q
+kOIbUK5jM1bpPGsbwen6NjzvLSTy0uxm4Q55WWlSvwGqtd5UmMAa+fEXVkqlIkPW
+81lN+ajl1kiW73ktQuK5Gy8x8UwmunAlSFfwDwCg/3/wwe1f0VAyWxOFit//X/yc
+luYthYVJPBR4Qt4zlbWIAsrtiQEiBBABAgAMBQJC0RmjBQMAEnUAAAoJEJcQuJvK
+V618EL0IAIUp/JwPpBYCgqT4FcRhLDxNghOGmJhedXgF2qLtcAv1x4YcucSMBFGE
+n1wRJ3jzYpWOiBhtJXPJdqDouy6aKKoQXYtKJ73ivP1ki5eiAznbNub/boJ6pqsB
+x8jcubZMzfKP1k6Ki8SLd6SfmRiuZyYkex+VMGNA2yCG8oZAYN2Gf+Pjwzi6P5/e
+gyko4Qb5iPYSUKFR5tf2K5S7XaqDHdo7HWbwZ/ddnQ9CaVyr+wpt/lusYdEMbIRw
+e81qCoWsdx9xh2hAtHK1ZMDIpeBC07s7Kg1CO9Xph9mBWOdCR3ygacsK/ega3Cpo
+0niTY0TJxSi0R6zHwGKmCMnFNzM0loSJASIEEAECAAwFAkLRv58FAwASdQAACgkQ
+lxC4m8pXrXydvAf+OrjcROKTZbAKOOM28AuRYh7CFQoNuxGpMj3oUX88WsU20cPv
+qFVNz+HE6x2jDjqAl/X3k7n09lsBGP02ufOf6GoHph7DYqhxK51TUll9pMg0Jg36
+HZtDdj30tw3pu7qmNkIfY5yH6R6tEdGv95DMKcgZtQntHJVKBeAotNjS+k0wNumN
+nbfKwzTAV05hji5kDW7ku0WJv1A6jTLetwemHnnTQiTzG7m/9PSvnC0pk3ndp3gq
+wPPBPDUwEIZUoFMLokY0rp0xPLbrFFY/QEGz69xxvjw4aPdDuCMXPSDoiqoYNMPt
+UtewUhKmCo49Mpj5E5YeiSCC5oHKWxCzTLeGFYkBIgQQAQIADAUCQuzGgwUDABJ1
+AAAKCRCXELibyletfMeHB/4qEx4jvYYpzI90/ysoz/X9sZ++IMvjarj3LGmqLjSy
+YpjIWWcpzIevUYrqPG8YGPlfdls7aV3URHA2TYCrrMt8dfWdRRKmOUIAWjaX1XHk
+0ZDq7wJr25oh6INT+fuSjegcNH07wBE0P3IUQhumCE6lxNhb+o7eJtLKYlT1OT+8
+3CvF2PQUi51FZwITg+15JNsVW5AMGOzT1s0J2qn+GOqkQg34+doKo48cEdo7g7xV
+qfQGgbFYzGUKfWJ+IV8AxIf2/NB17Nhor4V47d3xjFcv861nN4nMURYUIELDGsbS
+KJa+amN82DTpPKbaVs7/0qIhKT2NY+jNtgzIn6AUGq+ViQEiBBABAgAMBQJC7WzD
+BQMAEnUAAAoJEJcQuJvKV618jkUH/0YYKDBeSzKsqFNIxsmu5h+epeBTxaKhxy3/
+zzS4YleObVQ/oYJIwIPIMbiA1xHStEy3Z7MHGo2/AG0XGqFrmSSPSv2RstQV5V9r
+k7AqsCgzFS6BRn3hp1NayrCdgYFMQ/GXkzdYCmzYW7Y+xs9IpiGFVrXulXpQXgXJ
+jOl9zTjiRqik7WK8vDo/d/9wLZ8pH8BvLt0bGrxYAe3ycKiijhlDbQBr2NgGOH6v
+SfcPsrKcQBV5Z1VagGwrs2f++4y3oSxyIXzdYUwuuMfMzOJzi57VWwYRA+rPBMSb
+jmPwc61Sd4Y0Ur/UcDihz36a9taxzsN6fWT+CgEG5rlHkGyUpnOIcgQTEQIAMgUC
+SvhkCCsaaHR0cDovL3d3dy5wb2xsaW5nZXIub3JnLnVrL3BncC1wb2xpY3kudHh0
+AAoJEGB6yoUweI/vElAAoKhaHQoLS0cSGV1d3CmEvUz9jBZmAJ0cEfuNOJi3INQW
+FmK6by9nw7WlCokBHAQQAQIABgUCSswFzgAKCRCQV4eJidhUfhjzB/4xG3ODin66
+3KgxFBlqMLNWby/7pD3IoW4qCRsC+7LPjygEs2XMhltY/tUZKxuuNpMw9H894Rzq
+nbpF3Xf3V/1RjpdZxm5LHdroO6DYf0Db/Ly/0FoK5DgZmq8RRJYmQEzvJZTGlpi6
+3Uc6FoOPjwcIMA3uyjeib/yfTsvPa43R/SG84f91tDsqSQsNz/c2LJSq21GNfpJu
+Y0ulxuaZ+y6ZD2etLnZy3Nqu3o5LK1XfO5jIU+0A0NFB6qs+rX5pD3fJMl88CYho
+IOqWblFPozNR1iZ0OQubtlah+P4eJ1ddg0RSr+otkqV5yGdpgSGcrw86fl9v59x/
+SJ/89C4iegnaiQIcBBABCAAGBQJPErPWAAoJEG5r5CXrg8K9mTAP/1+/+jJCr+CW
+kAjHgmAOAJ9+SfyjwVh3r6RjJ1/u2FHEDrpC4pGcKoBRkXzze8iIaG63xd2507rc
+p07z8mPnRHKC25D6SaPbC8pblympBaAyyT5z/SO1pmhdqSlFovyXkGPehtI3A/ow
+cOq3C+sBk6KIiFpBdBicuBL0PhJsp35SUqfaKKdiMUT/8sldG2wTOTimrUI2AdLq
+PzBclkpY8fPHnlsaesMAujWA00ET5sd+CEpi8EFiIxPAWREBQ0yxQVDjaY+Ho7Yk
+CkW5aNyqyMLlp1Z5x3Pv9G0C05kPrdIRcmP0oze4r2/sJ+ipSqf8ciH02UTdvwwn
+2LvLGMlgmOtW0ZCy3zcFW+Nd2wvCSPmJWinxCvqQvE+1ECLNY0SCTD86SIhiRF2Y
+oB1MhM2FVVsVhdIwlrxC3gYWpEFyR0hVHhxkjxmacCg0uVenmPUpYzpJH6vNb/T1
+puOytGIoSKBAP2Zi9kYpsaRUtakmVPIVxRJ4/Pb1IqRbNuuodQcx32qbLCoJnKs2
+2PpyWeluVDEiASSuoZNssrdE2wsxWG0jZcbBzpIt0mp6/SP7wPaJWsoIWNB1jVnr
+krFXBtqsEAiccLd7aomAvx1WLIMNL06pFYrG18hBBI9l2C+wTmxwyoUSx3d4laZJ
+W0ZT369fJJhp78F3wR4+y+7rxCPHYG7iiQIcBBMBAgAGBQJRl8xcAAoJEG54KsA8
+mwz5gZgP/jxNhYZk/wzPKrRjneoymY9il8rCvEBd8yVuAFHN89pfv5kPk8HnGkmb
+XV/YJWNm1OaFyjehon9KCZR39d8gPGYh4Ju4aeL2E+DZSWKyktIj5RjGFqU6SWwg
+uA2Y/BL3VTK31C6aMOxE8dxT2tykCd/o77aYeDrI9dfUxgb3lqje/WahyQ1s5pC4
+cGyXnCOiYMtgzyCX71DVb7a9Yr6TiSWq1j76LFyKqkvoavY/ySDlR8NUI3cZQBag
+pDZ6T9szcvrkCtjjCE3jbftRXcQmT3cTnyRmmQdqIc85JWhOxtBSrZRt/8oy1P0K
+fItqejY1JfFBTs8okJ+8iu7B2DZyVSuzQIBZ2OH9hgkFBZ5yc5lZ1YItj14v7PXG
+3j1FcTGvckSuC2k/H5pusrSGy4TMclOSHnpFTiFZb9+Pt5hil5EIbA9gqfVEfa/V
+Lkwna4G2sq3S5W2keylyjVswj3XcApRLIzAupwgjm6uuDav+HwhJL4JdQ4DJ6qDY
+8ZcIZ70W1JaGSNknzvJwwyqbhyvVUHj3AL1DP6VKM/DKIQUKC6bFmj+NTLIQbH4q
+p3/7/66ceXT00owHip75FQtgjIGNuOXBUrdFFyHF1QITPdDwX9q5dfP73rA99UtE
+TAh6u3RlEn/cMteMdpsIi0aka2b7sOWPv5TASTIjqNsvWR+18OpvtDhHYXZpbiBB
+dGtpbnNvbiAoV29yayBlLW1haWwpIDxnYXZpbi5hdGtpbnNvbkB5b3JrLmFjLnVr
+PohiBBMRAgAiBQJM94U/AhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCT
+Xe9EoJMmKzWnAJ44UjheVhDuoWnYPib0hs9fVXJgKQCgl87FnXTOKasVgVpr4U06
+sDOgDZqJAhwEEAEIAAYFAk8Ss9YACgkQbmvkJeuDwr2Feg//SvpSy4Bq/SoF1Shp
++/IJaqCjbA45DHerTFB8RgOCXagSQI/thmY75ZB0/Q2nNTG8CsKQYpceOd8ZXI8u
+7us8peOMV4UTp5FbGkNTFiDwh0isAVLJiSxxMn1jlR5xuCvGK2LAtbJmw8vdUbSY
+YnCLUzXN5rRB4z+XqvpGXkiPLPm3YwJ9Q1hjITjMD56cyWIEXCI9dspFNQMrMlp7
+64XnDMhxhMCcfElEbAiDTboOBRoBshnKPT8xyWMplvwAxnA6vblPNnvV5vuuInKZ
+bbxZ54EZNz5xlMkteqbb69/zmJxNxukAlBgekh357BmCFsjbVkN45HCgY8ue9Ge9
+jypyvLU7Dji+uprGb8clqXak2qy1nrvJSeG+46G3bUN3dhNMylRGJjkDgD900P4y
+YKyCssS3xTWqxmcAggBJC22kh/+5WpN8V5zhGGa04TFBnjPLUf6OpxZgHOUDxEYa
+1sDxOUvlzF+cHKhRW7izcQlfBjoUeK11E2ucy6xuFS8fCtiK9l8vw8TiseGLhJW/
+5DHc2ADTNbxuvcummQU7Ue1O9J2cAWsSgVtipcsfVALmXFZ8PY1Mt77aYgORx+Y+
+NkSNbhXQkcRNwPBcTICgWAowXrt7CpUtSduLT1Z892OIGHyHPDZK9vBhrG/AOBtt
+kXZsi1LDwalRotIJBDsa+73o316JAhwEEwECAAYFAlGXzFwACgkQbngqwDybDPlG
+URAAhzEqhvA6HqhtkN3B4Gmk2ugdjHkP/xqS0rq6BgXeNsX7i0Ozk1VIe8ymWTtH
+SH2zWFQsGb7zgVAXq5mJEzE++PxAfbpypshJwrXgPzXc5jDtdRVVjCuLzDgIriQ+
+kYwDo1fn3/d+sIwsCR1+V4frXwLzpP83Xo/4rmf8TMykEVJLNXL+mNrOJSaoSIWA
+NTiz7Uy2gOpD+Mb6i/xK/OnVhvQXJQ6nYkTce0XQCIMkn/wZpu+kCl91/xURyafH
+ZsEeC8oV4UIeuoodaei1PtZ+E8c9fBAijygmSPq/t1bOy74/AV98MDXFXoLEr/kX
++sdfyql6xz9K9Hsb2CpZizg6fylg1c4iSdQQ4sdMGYYXB7epyP3q+kDwF0Fz0+xu
+tD6CImzPyNX4MPUz+5yVAR93Yv3GK1GH4CABlcWTfzYzXcQij8JQM+gw2n6fFZLM
+iHT7L0z/gSYZi8E0JYW9uZFg59HX5A6TcuYLS9l7qKjdKB8C8cZ+CHw0ZDiY5YgU
+t6zLiWZ/7/AspcimRZ7okmE64qJvffVdu5S6ACJC1/XtoOVEHEAcL1SLVK4AiPSU
+oyLJFbo0reeypN0vp1UgDzsKRDXLeAXeFvYOP7ekkeaIuRXNAM28OHaXt5xiT3ju
+BwUjFIF8NLBdDzfjtArSd1R7zOxWJYBlnRgKxQIusHGppYe5Ag0EQhYGdxAIANWA
+PhDo3kdh1QoXfk+oe0Rw60fYgLSmcexZKj6gEoMlZC0NPPtJQO2UjWEjesfce6HD
+xfFGj6LuqKY2QoioRJaTxBbDEDstnPp8+gCms+p4DvBqNXdfxV+jHaspbtqbQNpW
+cl+6MLKD1OciEluygBnVFPrfvgJRFT+OS1uOjRfafUA0cl9HlKZdHgY/sRfX5CFL
+QyGLu2NYVsj1i+AI9PYmrP4ucKHkTDr5cBWq3wzi/HHUq/tT+1UL3P/hjiTjbmzR
+jF4Ygm+18so2wvz4qT6HAFLmsvEobc1vodJaELRvl0Se5FG8ZEaYJpDXzDqs/G0+
+hPoPT8eXgUr87pd3nzMAAwUH/im19ug/qDBWGFykIIPo6P5upkwg8Umiihk3Cvfk
+pZonsRSRpg/YVX7MJ/v0/wwJ41GPgFIG/NiKQc2kxxPgO9AKYJ0lXMS7fyLXgZgY
+0TD2s6tvnXWX16cmMp2MJYDaPNJf4MY2ImW7VgfU00AzZAheBpJKdB/+8/ncRRqK
+ljsWDStmG0Y0iazNzaX1tWMB8ug875NeGsSnBUWylh7MuaXVJMAnBjsxj4rw2KR/
+TD9i+M+RADRXisUcZJMMZ1q0RXCs5FRTT6yxHLHnLL/A1LlQLQ5TVJ94Hhda3O9x
+WLsL2mDRcga8qbcruoBhzg/ip9YzWZSufERzv62KdVRt9jSISQQYEQIACQUCQhYG
+dwIbDAAKCRCTXe9EoJMmK7wSAJ9+rbAFc1hAq4PIfgnpiErVWkaOiwCfcQSb29qC
+LTwsVXBkqZr02JdmGdg=
+=/71Z
 -----END PGP PUBLIC KEY BLOCK-----
 ]]></programlisting>
diff --git a/share/xml/freebsd.sch b/share/xml/freebsd.sch
index 3d39ef9009..1039991552 100644
--- a/share/xml/freebsd.sch
+++ b/share/xml/freebsd.sch
@@ -1,307 +1,312 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 
 <!-- $FreeBSD$ -->
 
 <schema xmlns="http://purl.oclc.org/dsdl/schematron"
   xmlns:db="http://docbook.org/ns/docbook"
   xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 
   <ns prefix="db" uri="http://docbook.org/ns/docbook"/>
 
   <pattern name="Check file reference validity">
     <rule context="//db:imagedata|//db:graphic">
       <report test="contains(@fileref, '.')">Image reference (<xsl:value-of select="@fileref"/>) cannot have an extension; the proper format is inferred by the output type to generate.</report>
       <report test="@format">Image reference (<xsl:value-of select="@fileref"/>) format must not be specified; it is inferred by the output type to generate.</report>
     </rule>
   </pattern>
 
   <pattern name="Check filenames">
     <rule context="//db:filename">
       <report test="@role = 'directory'">Filename (<xsl:value-of select="."/>) has role="directory"; use class="directory"</report>
     </rule>
   </pattern>
 
   <pattern name="Check cross-reference validity">
     <rule context="//db:link">
       <assert test="* or normalize-space()">Link (<xsl:value-of select="@linkend"/>) element must have a content; or use xref to auto-generate the linking text.</assert>
     </rule>
   </pattern>
 
   <pattern name="Check callout validity">
     <rule context="/">
       <report test="//db:screenco">Callouts with screenco are not supported; use screen and co instead.</report>
       <report test="//db:programlistingco">Callouts with programlistingco are not supported; use programlisting and co instead.</report>
       <report test="//db:graphicco">Callouts on graphics are not supported.</report>
     </rule>
   </pattern>
 
   <pattern name="Check profiling attributes">
     <rule context="//*/@edition">
       <assert test="(. = 'online') or (. = 'print')">Invalid edition value (<xsl:value-of select="."/>); must be either 'online' or "print".</assert>
     </rule>
     <rule context="//*/@os">
       <assert test="(. = 'freebsd8') or (. = 'freebsd9') or (. = 'freebsd10')">Invalid os value (<xsl:value-of select="."/>); must be either 'freebsd8', 'freebsd9' or 'freebsd10'.</assert>
     </rule>
   </pattern>
 
   <pattern name="Check titles">
     <rule context="//db:book|//db:article|//db:chapter|//db:section|//db:sect1|//db:sect2|//db:sect3|//db:sect4|//db:sect5">
       <assert test="db:title or db:info/db:title">There must be a title either in the the doc component (<xsl:value-of select="@xml:id"/>) or in the info element.</assert>
       <report test="db:title and db:info/db:title">There must be exactly one title for a doc component (<xsl:value-of select="@xml:id"/>).</report>
     </rule>
   </pattern>
 
   <pattern name="Check tables">
     <rule context="//db:entry">
       <report test="@colname and @spanname">You cannot use both colname and spanname attributes on table entries.</report>
     </rule>
     <rule context="//db:tgroup">
       <report test="@cols != count((db:thead/db:row|db:tbody/db:row)[1]//db:entry)">The number of columns does not match the specified value (in section <xsl:value-of select="(ancestor::db:sect5[last()]|ancestor::db:sect4[last()]|ancestor::db:sect3[last()]|ancestor::db:sect2[last()]|ancestor::db:sect1[last()]|ancestor::db:chapter[last()])[last()]/@xml:id"/>).</report>
     </rule>
+    <rule context="//db:table">
+      <report test=".//db:programlisting">Programlisting is not allowed in tables (in section <xsl:value-of select="(ancestor::db:sect5[last()]|ancestor::db:sect4[last()]|ancestor::db:sect3[last()]|ancestor::db:sect2[last()]|ancestor::db:sect1[last()]|ancestor::db:chapter[last()])[last()]/@xml:id"/>).</report>
+      <report test=".//db:screen">The screen element is not allowed in tables (in section <xsl:value-of select="(ancestor::db:sect5[last()]|ancestor::db:sect4[last()]|ancestor::db:sect3[last()]|ancestor::db:sect2[last()]|ancestor::db:sect1[last()]|ancestor::db:chapter[last()])[last()]/@xml:id"/>).</report>
+      <report test=".//db:footnote">Footnote is not allowed in tables (in section <xsl:value-of select="(ancestor::db:sect5[last()]|ancestor::db:sect4[last()]|ancestor::db:sect3[last()]|ancestor::db:sect2[last()]|ancestor::db:sect1[last()]|ancestor::db:chapter[last()])[last()]/@xml:id"/>).</report>
+    </rule>
   </pattern>
 
   <!-- DB 5.0 constraints -->
 
   <pattern name="Glossary 'firstterm' type constraint">
      <rule context="db:firstterm[@linkend]">
         <assert test="local-name(//*[@xml:id=current()/@linkend]) = 'glossentry' and namespace-uri(//*[@xml:id=current()/@linkend]) = 'http://docbook.org/ns/docbook'">@linkend on firstterm must point to a glossentry.</assert>
      </rule>
   </pattern>
   <pattern name="Footnote reference type constraint">
      <rule context="db:footnoteref">
         <assert test="local-name(//*[@xml:id=current()/@linkend]) = 'footnote' and namespace-uri(//*[@xml:id=current()/@linkend]) = 'http://docbook.org/ns/docbook'">@linkend on footnoteref must point to a footnote.</assert>
      </rule>
   </pattern>
   <pattern name="Glossary 'glossterm' type constraint">
      <rule context="db:glossterm[@linkend]">
         <assert test="local-name(//*[@xml:id=current()/@linkend]) = 'glossentry' and namespace-uri(//*[@xml:id=current()/@linkend]) = 'http://docbook.org/ns/docbook'">@linkend on glossterm must point to a glossentry.</assert>
      </rule>
   </pattern>
   <pattern name="Synopsis fragment type constraint">
      <rule context="db:synopfragmentref">
         <assert test="local-name(//*[@xml:id=current()/@linkend]) = 'synopfragment' and namespace-uri(//*[@xml:id=current()/@linkend]) = 'http://docbook.org/ns/docbook'">@linkend on synopfragmentref must point to a synopfragment.</assert>
      </rule>
   </pattern>
   <pattern name="Glosssary 'see' type constraint">
      <rule context="db:glosssee[@otherterm]">
         <assert test="local-name(//*[@xml:id=current()/@otherterm]) = 'glossentry' and namespace-uri(//*[@xml:id=current()/@otherterm]) = 'http://docbook.org/ns/docbook'">@otherterm on glosssee must point to a glossentry.</assert>
      </rule>
   </pattern>
   <pattern name="Glossary 'seealso' type constraint">
      <rule context="db:glossseealso[@otherterm]">
         <assert test="local-name(//*[@xml:id=current()/@otherterm]) = 'glossentry' and namespace-uri(//*[@xml:id=current()/@otherterm]) = 'http://docbook.org/ns/docbook'">@otherterm on glossseealso must point to a glossentry.</assert>
      </rule>
   </pattern>
   <pattern name="Glossary term definition constraint">
      <rule context="db:termdef">
         <assert test="count(db:firstterm) = 1">A termdef must contain exactly one firstterm</assert>
      </rule>
   </pattern>
   <pattern name="Cardinality of segments and titles">
      <rule context="db:seglistitem">
         <assert test="count(db:seg) = count(../db:segtitle)">The number of seg elements must be the same as the number of segtitle elements in the parent segmentedlist</assert>
      </rule>
   </pattern>
   <pattern name="Root must have version">
      <rule context="/db:para">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:set">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:book">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:dedication">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:acknowledgements">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:colophon">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:appendix">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:chapter">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:part">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:preface">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:section">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:article">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:sect1">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:sect2">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:sect3">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:sect4">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:sect5">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:reference">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:refentry">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:refsection">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:refsect1">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:refsect2">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:refsect3">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:glossary">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:bibliography">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:index">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:setindex">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
      <rule context="/db:toc">
         <assert test="@version">The root element must have a version attribute.</assert>
      </rule>
   </pattern>
   <pattern name="Element exclusion">
      <rule context="db:annotation">
         <assert test="not(.//db:annotation)">annotation must not occur in the descendants of annotation</assert>
      </rule>
      <rule context="db:caution">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of caution</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of caution</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of caution</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of caution</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of caution</assert>
      </rule>
      <rule context="db:important">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of important</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of important</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of important</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of important</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of important</assert>
      </rule>
      <rule context="db:note">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of note</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of note</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of note</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of note</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of note</assert>
      </rule>
      <rule context="db:tip">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of tip</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of tip</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of tip</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of tip</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of tip</assert>
      </rule>
      <rule context="db:warning">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of warning</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of warning</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of warning</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of warning</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of warning</assert>
      </rule>
      <rule context="db:caption">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of caption</assert>
         <assert test="not(.//db:equation)">equation must not occur in the descendants of caption</assert>
         <assert test="not(.//db:example)">example must not occur in the descendants of caption</assert>
         <assert test="not(.//db:figure)">figure must not occur in the descendants of caption</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of caption</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of caption</assert>
         <assert test="not(.//db:sidebar)">sidebar must not occur in the descendants of caption</assert>
         <assert test="not(.//db:table)">table must not occur in the descendants of caption</assert>
         <assert test="not(.//db:task)">task must not occur in the descendants of caption</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of caption</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of caption</assert>
      </rule>
      <rule context="db:equation">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of equation</assert>
         <assert test="not(.//db:equation)">equation must not occur in the descendants of equation</assert>
         <assert test="not(.//db:example)">example must not occur in the descendants of equation</assert>
         <assert test="not(.//db:figure)">figure must not occur in the descendants of equation</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of equation</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of equation</assert>
         <assert test="not(.//db:table)">table must not occur in the descendants of equation</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of equation</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of equation</assert>
      </rule>
      <rule context="db:example">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of example</assert>
         <assert test="not(.//db:equation)">equation must not occur in the descendants of example</assert>
         <assert test="not(.//db:example)">example must not occur in the descendants of example</assert>
         <assert test="not(.//db:figure)">figure must not occur in the descendants of example</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of example</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of example</assert>
         <assert test="not(.//db:table)">table must not occur in the descendants of example</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of example</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of example</assert>
      </rule>
      <rule context="db:figure">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of figure</assert>
         <assert test="not(.//db:equation)">equation must not occur in the descendants of figure</assert>
         <assert test="not(.//db:example)">example must not occur in the descendants of figure</assert>
         <assert test="not(.//db:figure)">figure must not occur in the descendants of figure</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of figure</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of figure</assert>
         <assert test="not(.//db:table)">table must not occur in the descendants of figure</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of figure</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of figure</assert>
      </rule>
      <rule context="db:table">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of table</assert>
         <assert test="not(.//db:equation)">equation must not occur in the descendants of table</assert>
         <assert test="not(.//db:example)">example must not occur in the descendants of table</assert>
         <assert test="not(.//db:figure)">figure must not occur in the descendants of table</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of table</assert>
         <assert test="not(.//db:informaltable)">informaltable must not occur in the descendants of table</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of table</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of table</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of table</assert>
      </rule>
      <rule context="db:footnote">
         <assert test="not(.//db:caution)">caution must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:epigraph)">epigraph must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:equation)">equation must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:example)">example must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:figure)">figure must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:footnote)">footnote must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:important)">important must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:indexterm)">indexterm must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:note)">note must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:sidebar)">sidebar must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:table)">table must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:task)">task must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:tip)">tip must not occur in the descendants of footnote</assert>
         <assert test="not(.//db:warning)">warning must not occur in the descendants of footnote</assert>
      </rule>
      <rule context="db:sidebar">
         <assert test="not(.//db:sidebar)">sidebar must not occur in the descendants of sidebar</assert>
      </rule>
   </pattern>
 </schema>